#181 2025-05-23 07:02:14

Head_on_a_Stick

Member

From: London

Registered: 2015-09-29

Posts: 9,068

Website

Re: Carbon Bugs

I don't think BunsenLabs uses a keyring for the session.

Can you post the systemd journal contents from a suspend attempt? That might reveal something.

---

Para todos todo, para nosotros nada

kozimodo

Member

Registered: 2015-10-04

Posts: 118

Re: Carbon Bugs

May 24 08:42:21 lappy kernel: ata1.00: Features: Dev-Sleep
May 24 08:44:54 lappy systemd-logind[692]: The system will suspend now!
May 24 08:44:54 lappy NetworkManager[735]: <info>  [1748090694.7098] manager: sleep: sleep requested (sleeping: no  enabled: yes)
May 24 08:44:54 lappy ModemManager[833]: <msg> [sleep-monitor-systemd] system is about to suspend
May 24 08:44:54 lappy NetworkManager[735]: <info>  [1748090694.7298] device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
May 24 08:44:54 lappy NetworkManager[735]: <info>  [1748090694.7606] manager: NetworkManager state is now ASLEEP
May 24 08:44:54 lappy NetworkManager[735]: <info>  [1748090694.7681] device (wlp1s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
May 24 08:44:54 lappy NetworkManager[735]: <info>  [1748090694.9962] device (wlp1s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
May 24 08:44:55 lappy NetworkManager[735]: <info>  [1748090695.0899] device (wlp1s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
May 24 08:44:55 lappy systemd[1]: Reached target sleep.target - Sleep.
May 24 08:44:55 lappy systemd[1]: Starting systemd-suspend.service - System Suspend...
May 24 08:44:55 lappy systemd-sleep[2048]: Performing sleep operation 'suspend'...
May 24 08:44:55 lappy kernel: PM: suspend entry (deep)
May 24 08:45:10 lappy kernel: printk: Suspending console(s) (use no_console_suspend to debug)
May 24 08:45:10 lappy kernel: ACPI: PM: Preparing to enter system sleep state S3
May 24 08:45:10 lappy kernel: ACPI: PM: Low-level resume complete
May 24 08:45:10 lappy kernel: ACPI: PM: Waking up from system sleep state S3
May 24 08:45:12 lappy systemd-sleep[2048]: System returned from sleep operation 'suspend'.
May 24 08:45:12 lappy kernel: PM: suspend exit
May 24 08:45:12 lappy bluetoothd[785]: Controller resume with wake event 0x0
May 24 08:45:13 lappy systemd[1]: systemd-suspend.service: Deactivated successfully.
May 24 08:45:13 lappy systemd[1]: Finished systemd-suspend.service - System Suspend.
May 24 08:45:13 lappy systemd[1]: Stopped target sleep.target - Sleep.
May 24 08:45:13 lappy systemd[1]: Reached target suspend.target - Suspend.
May 24 08:45:13 lappy systemd[1]: Stopped target suspend.target - Suspend.
May 24 08:45:13 lappy systemd-logind[692]: Operation 'suspend' finished.
May 24 08:45:13 lappy ModemManager[833]: <msg> [sleep-monitor-systemd] system is resuming
May 24 08:45:13 lappy NetworkManager[735]: <info>  [1748090713.2950] manager: sleep: wake requested (sleeping: yes  enabled: yes)
-- Boot 467b719116c84b7ca05d30df0a7c4324 --
May 24 08:45:47 lappy kernel: ata1.00: Features: Dev-Sleep

kozimodo

Member

Registered: 2015-10-04

Posts: 118

Re: Carbon Bugs

Interestingly, this appears to be a problem when the computer is plugged in.  When it's running on battery power, it drops into suspend without problems.

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,558

Website

Re: Carbon Bugs

It looks as if the bluetooth metapackage needs two versions, for pulse and pipewire.

Why? We're not releasing both a pipewire/wireplumber and a pulseaudio version of Carbon, are we?

No, that's true. How about people upgrading from Boron though? If they've installed bunsen-meta-bluetooth then they'll have the pulse package removed and pipewire added. As long as the rest of their system has been upgraded to pipewire I guess it should be OK just to edit the metapackage...

(Probably good to test at some point.)

Anyway I can't think of any reason right now why changing pulseaudio-module-bluetooth to libspa-0.2-bluetooth in bunsen-meta-bluetooth should cause upgrade problems. I've just uploaded bunsen-welcome 13.1-2 with that change.

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,039

Website

Re: Carbon Bugs

^ Thanks for the update!

---

No, he can't sleep on the floor. What do you think I'm yelling for?!!!

greenjeans

Member

Registered: 2025-01-18

Posts: 227

Website

Re: Carbon Bugs

Interestingly, this appears to be a problem when the computer is plugged in.  When it's running on battery power, it drops into suspend without problems.

That sounds like a setting in your power manager, both the ones I use in different installs have options to do multiple different things depending on whether you're on battery power or plugged in. I can turn off the ability to sleep in either case through the power manager GUI.

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,039

Website

Re: Carbon Bugs

^ In which case, start typing "power" into the Main Menu (or go to "User Settings"), open "Power Management", then System>On battery

-edit- Oops, got what you were asking backwards, @Kozimodo. Works on battery not plugged in.

Last edited by hhh (2025-06-02 01:30:46)

---

No, he can't sleep on the floor. What do you think I'm yelling for?!!!

kozimodo

Member

Registered: 2015-10-04

Posts: 118

Re: Carbon Bugs

I understand that I can turn off suspend when it’s plugged in — I have it set to suspend because I want it to.  But based on the fact that on battery power, it suspends without problem but requests authentication under power suggests to me that it’s an upstream xfce problem.

But thank you all for your input.

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,558

Website

Re: Carbon Bugs

A new live-build is in Sid and we should see it in Trixie in a few days. Once bunsen-configs is done and micko01's new packages are in the main repo, I'll try an iso build...

I think the most important things on my end are:

• labbe-icons-ng - mostly complete

• material-solarized-suruplusplus-ng - nearly done

• xwwall - nearly done, which depends on the next point

• gtk3dialog which is done but needs to be formally introduced to the bunsen repo. As it's external, because it is available to any linux/*nix system, it presents different requirements for inclusion

I'll get most, if not all, of this done by the end of next weekend.

OK I've forked xwwal, xwwall-debian, gtk3dialog and gtk3dialog-debian to BL, and given you admin access so you can make any changes you want (including deleting).

If you're OK with the code as it is now (ie you've posted no objection here) I'll build and upload to the BL repos in a day or two.

I'll do the same for labbe-icons-ng and material-solarized-suruplusplus-gtkicons but there is an issue with the changelog file for labbe-icons-ng, because it's older than the latest changes to the repo. And material-solarized has almost no commit history so I can't do a check there. Really, I think the top changelog entry should go in last of all, just before building and uploading the package.

Last edited by johnraff (2025-06-04 02:33:29)

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,558

Website

Re: Carbon Bugs

...there is an issue with the changelog file for labbe-icons-ng, because it's older than the latest changes to the repo.

Perhaps the easiest way to fix this would be if you just edit the date in the changelog file to today, so it comes after any changes to the package itself. If you use dch then dch -e should do it.

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 494

Website

Re: Carbon Bugs

...there is an issue with the changelog file for labbe-icons-ng, because it's older than the latest changes to the repo.

Perhaps the easiest way to fix this would be if you just edit the date in the changelog file to today, so it comes after any changes to the package itself. If you use dch then dch -e should do it.

I just used dch -r. That simply updated to today's date. Pushed.

EDIT: did the same for material-solarized-suruplusplus-gtkicons.

Last edited by micko01 (2025-06-04 10:32:02)

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,558

Website

Re: Carbon Bugs

^Ah yes, I've never used it but -r looks like the one for this job.

And I'll get on with building and uploading those four packages.

Last edited by johnraff (2025-06-05 01:49:23)

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,558

Website

Re: Carbon Bugs

BTW is the labbe-material-icons repo still in use?
If not, delete it from BL?

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,558

Website

Re: Carbon Bugs

These four packages are now in the BL carbon repo:

labbe-icons-ng_12.7-1
material-solarized-suruplusplus-gtkicons_12.6-1
gtk3dialog_0.1.2-1
xwwall_0.2.4-1

Lintian had a few things to say, but it was mostly small things that don't really apply to derivative distros, or trailing whitespace and spelling errors. You might want to check them out at your leisure.

gtk3dialog had a lot of "missing source" errors, but I think that's a long line length thing that came up before. I'm pasting in the whole lintian (+pedantic and info) output below.

More important, gtk3dialog fails to build without some extra packages in debian/control Build-Depends:

meson, ninja-build, bison, flex

The lack of meson triggered an error exit, and I noticed ninja in debian/rules so added that too. Then missing bison caused an exit, and likewise flex was referred to in the same file so I added that too. After that it built OK. You might want to consider whether any of those packages need to have versions specified.

Here's the full Lintian output for your delectation. It's quite likely all of those can be ignored:

running Lintian...

N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/button.html]
N: 
N:   The source of the following file is missing. Lintian checked a few
N:   possible paths to find the source, and did not find it.
N:   
N:   Please repack your package to include the source or add it to
N:   "debian/missing-sources" directory.
N:   
N:   Please note, that very-long-line-length-in-source-file tagged files are
N:   likely tagged source-is-missing. It is a feature not a bug.
N: 
N:   Visibility: error
N:   Show-Always: no
N:   Check: files/source-missing
N: 
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/checkbox.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/chooser.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/colorbutton.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/comboboxentry.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/comboboxtext.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/edit.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/entry.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/eventbox.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/expander.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/fontbutton.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/frame.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/hbox.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/hscale.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/menu.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/menubar.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/menuitem.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/notebook.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/pixmap.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/progressbar.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/radiobutton.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/spinbutton.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/statusbar.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/terminal.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/text.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/timer.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/togglebutton.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/tree.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/vbox.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/vscale.html]
N:
E: gtk3dialog source: source-is-missing [doc/gtk3dialog/reference/window.html]
N:
I: gtk3dialog-doc: bash-term-in-posix-shell '${arg1:0:1}' [usr/share/doc/gtk3dialog/examples/playmusic/funcPlaylistCreate:37]
N: 
N:   This script is marked as running under /bin/sh, but it seems to use a
N:   feature found in bash but not in the SUSv3 or POSIX shell specification.
N:   
N:   Some examples are:
N:   
N:   - == in a test, it should use = instead - read without a variable in the
N:   argument - function to define a function - source instead of . - . command
N:   args, passing arguments to commands via source is not supported -
N:   {foo,bar} instead of foo bar - [[ test ]] instead of [ test ] (requires a
N:   Korn shell) - type instead of which or command -v
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: shell/non-posix/bash-centric
N: 
N:
I: gtk3dialog-doc: bash-term-in-posix-shell '${name:0:1}' [usr/share/doc/gtk3dialog/examples/playmusic/funcPlay:36]
N:
I: gtk3dialog-doc: bash-term-in-posix-shell '${name:0:1}' [usr/share/doc/gtk3dialog/examples/playmusic/funcrcfileRead:34]
N:
I: gtk3dialog source: debian-watch-file-is-missing
N: 
N:   This source package is not Debian-native but it does not have a
N:   debian/watch file. This file is used for automatic detection of new
N:   upstream versions by the Debian External Health Status project and other
N:   project infrastructure. If this package is maintained upstream, please
N:   consider adding a debian/watch file to detect new releases.
N:   
N:   If the package is not maintained upstream or if upstream uses a
N:   distribution mechanism that cannot be meaningfully monitored by uscan and
N:   the Debian External Health Status project, please consider adding a
N:   debian/watch file containing only comments documenting the situation.
N: 
N:   Please refer to Upstream source location: debian/watch (Section 4.11) in
N:   the Debian Policy Manual and the uscan(1) manual page for details.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: debian/watch
N: 
N:
I: gtk3dialog source: duplicate-long-description gtk3dialog gtk3dialog-doc [debian/control]
N: 
N:   The listed binary packages all share the same extended description.
N:   
N:   Please add some additional, useful information to the extended
N:   descriptions that explain what is in each package and how it differs from
N:   the next.
N:   
N:   It is not okay to rely only on package naming conventions to indicate what
N:   is inside.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: debian/control/field/description/duplicate
N: 
N:
I: gtk3dialog: hardening-no-bindnow [usr/bin/gtk3dialog]
N: 
N:   This package provides an ELF binary that lacks the "bindnow" linker flag.
N:   
N:   This is needed (together with "relro") to make the "Global Offset Table"
N:   (GOT) fully read-only. The bindnow feature trades startup time for
N:   improved security. Please consider enabling this feature or consider
N:   overriding the tag (possibly with a comment about why).
N:   
N:   If you use dpkg-buildflags, you may have to add hardening=+bindnow or
N:   hardening=+all to DEB_BUILD_MAINT_OPTIONS.
N:   
N:   The relevant compiler flags are set in LDFLAGS.
N: 
N:   Please refer to https://wiki.debian.org/Hardening for details.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: binaries/hardening
N: 
N:
I: gtk3dialog-doc: possible-documentation-but-no-doc-base-registration
N: 
N:   The package ships a .html or .pdf file under /usr/share/doc/. Those files
N:   are usually documentation, but no files are registered in doc-base.
N:   
N:   Files in folders named examples are exempt from this tag.
N: 
N:   Please refer to Registering Documents using doc-base (Section 9.10) in the
N:   Debian Policy Manual for details.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: menus
N: 
N:
I: gtk3dialog: spelling-error-in-binary enought enough [usr/bin/gtk3dialog]
N: 
N:   Lintian found a spelling error in the given binary. Lintian has a list of
N:   common misspellings that it looks for. It does not have a dictionary like
N:   a spelling checker does.
N:   
N:   If the string containing the spelling error is translated with the help of
N:   gettext or a similar tool, please fix the error in the translations as
N:   well as the English text to avoid making the translations fuzzy. With
N:   gettext, for example, this means you should also fix the spelling mistake
N:   in the corresponding msgids in the *.po files.
N:   
N:   You can often find the word in the source code by running:
N:   
N:    grep -rw <word> <source-tree>
N:   
N:   This tag may produce false positives for words that contain non-ASCII
N:   characters due to limitations in strings.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: binaries/spelling
N: 
N:
I: gtk3dialog: spelling-error-in-binary occured occurred [usr/bin/gtk3dialog]
N:
I: gtk3dialog: synopsis-is-a-sentence "graphical gui building application for x11 or wayland."
N: 
N:   The package synopsis (also known as the "short" description, ie. the first
N:   line in the package's "Description:" field) either ends with a full stop
N:   "." character or starts another sentence.
N:   
N:   This is not necessary as the synopsis does not need to be a full sentence.
N:   It is recommended that a single descriptive phrase is used instead.
N:   
N:   Note also that the synopsis is not part of the rest of the "long"
N:   Description: field.
N: 
N:   Please refer to The package synopsis, or short description (Section 6.2.2)
N:   in the Debian Developer's Reference for details.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: fields/description
N:   Renamed from: description-synopsis-might-not-be-phrased-properly
N: 
N:
I: gtk3dialog-doc: synopsis-is-a-sentence "graphical gui building application docs for x11 or wayland."
N:
I: gtk3dialog: typo-in-manual-page desription description [usr/share/man/man5/gtk3dialog.5.gz:35]
N: 
N:   Lintian found a spelling error in a manual page. Lintian has a list of
N:   common misspellings that it looks for. It does not have a dictionary like
N:   a spelling checker does.
N:   
N:   If the string containing the spelling error is translated with the help of
N:   gettext (with the help of po4a, for example) or a similar tool, please fix
N:   the error in the translations as well as the English text to avoid making
N:   the translations fuzzy. With gettext, for example, this means you should
N:   also fix the spelling mistake in the corresponding msgids in the *.po
N:   files.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: documentation/manual
N:   Renamed from: spelling-error-in-manpage
N: 
N:
I: gtk3dialog: typo-in-manual-page heirarchy hierarchy [usr/share/man/man1/gtk3dialog.1.gz:102]
N:
I: gtk3dialog-doc: wrong-section-according-to-package-name misc => doc
N: 
N:   This package has a name suggesting that it belongs to a section other than
N:   the one it is currently categorized in.
N: 
N:   Visibility: info
N:   Show-Always: no
N:   Check: fields/section
N: 
N:
P: gtk3dialog-doc: example-interpreter-in-usr-local /usr/local/bin/gtk3dialog [usr/share/doc/gtk3dialog/examples/miscellaneous/standalone_file]
N: 
N:   This package contains an example script that looks for an interpreter in a
N:   directory in /usr/local. Since Debian does not install anything in
N:   /usr/local, the example script would probably need modifications before a
N:   user could run it.
N: 
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: scripts
N: 
N:
P: gtk3dialog source: trailing-whitespace [debian/control:19]
N: 
N:   This file contains lines with trailing whitespace characters.
N:   
N:   Whilst often harmless and unsightly, such extra whitespaces can also cause
N:   tools to interpret the whitespace characters literally. The tool diff(1)
N:   does not like them, either. They are best avoided.
N:   
N:   Some of these problems can be hard to track down.
N:   
N:   Whitespace at the end of lines may be removed with the following:
N:   
N:    $ sed -i -e 's@[[:space:]]*$@@g' debian/control debian/changelog
N:   
N:   If you use Emacs, you can also use "M-x wh-cl" (whitespace-cleanup).
N:   
N:   However, if you wish to only remove trailing spaces and leave trailing
N:   tabs (eg. for Makefiles), you can use the following code snippet:
N:   
N:    $ sed -i -e 's@[ ]*$@@g' debian/rules
N:   
N:   To remove empty lines from the end of a file, you can use:
N:   
N:    $ sed -i -e :a -e '/^\n*$/{$d;N;};/\n$/ba' debian/rules
N: 
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: debian/trailing-whitespace
N:   Renamed from: file-contains-trailing-whitespace
N: 
N:
P: gtk3dialog source: trailing-whitespace [debian/control:28]
N:
X: gtk3dialog-doc: duplicate-files usr/share/doc/gtk3dialog/examples/button/COPYING-elementary-icons usr/share/doc/gtk3dialog/examples/pfeme/COPYING-elementary-icons usr/share/doc/gtk3dialog/examples/pfeme/COPYING-fast-forward-icons usr/share/doc/gtk3dialog/examples/togglebutton/COPYING-elementary-icons
N: 
N:   The package ships the two (or more) files with the exact same contents.
N:   
N:   Duplicates can often be replaced with symlinks by running:
N:   
N:      jdupes -rl debian/${binary}/usr
N:   
N:   ... after they are installed, eg. in override_dh_link. In addition, please
N:   consider reporting this upstream.
N:   
N:   Note: empty files are exempt from this check.
N: 
N:   Please refer to the jdupes(1) manual page for details.
N: 
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: files/duplicates
N:   This tag is experimental.
N: 
N:
X: gtk3dialog-doc: duplicate-files usr/share/doc/gtk3dialog/examples/button/no.svg usr/share/doc/gtk3dialog/examples/togglebutton/false.svg
N:
X: gtk3dialog-doc: duplicate-files usr/share/doc/gtk3dialog/examples/button/yes.svg usr/share/doc/gtk3dialog/examples/togglebutton/true.svg
N:
X: gtk3dialog-doc: duplicate-files usr/share/doc/gtk3dialog/examples/chooser/chooser_deprecated usr/share/doc/gtk3dialog/examples/miscellaneous/chooser
N:
X: gtk3dialog-doc: duplicate-files usr/share/doc/gtk3dialog/examples/hbox/hbox usr/share/doc/gtk3dialog/examples/vbox/vbox
N:
X: gtk3dialog-doc: duplicate-files usr/share/doc/gtk3dialog/examples/hbox/hbox_attributes usr/share/doc/gtk3dialog/examples/vbox/vbox_attributes
N:
X: gtk3dialog-doc: duplicate-files usr/share/doc/gtk3dialog/examples/pfeme/funcWidgetSchedule usr/share/doc/gtk3dialog/examples/playmusic/funcWidgetSchedule
N:
X: gtk3dialog-doc: duplicate-files usr/share/doc/gtk3dialog/examples/pfeme/funcrcGet usr/share/doc/gtk3dialog/examples/pfontview/funcrcGet
N:
X: gtk3dialog-doc: duplicate-files usr/share/doc/gtk3dialog/examples/pfeme/funcrcSet usr/share/doc/gtk3dialog/examples/pfontview/funcrcSet
N:
X: gtk3dialog-doc: duplicate-files usr/share/doc/gtk3dialog/examples/pfeme/functmpGet usr/share/doc/gtk3dialog/examples/pfontview/functmpGet usr/share/doc/gtk3dialog/examples/playmusic/functmpGet
N:
X: gtk3dialog-doc: duplicate-files usr/share/doc/gtk3dialog/examples/pfeme/functmpSet usr/share/doc/gtk3dialog/examples/pfontview/functmpSet usr/share/doc/gtk3dialog/examples/playmusic/functmpSet
N:
X: gtk3dialog source: update-debian-copyright 2024 vs 2025 [debian/copyright:15]
N: 
N:   The most recent copyright year mentioned for files in ./debian lags behind
N:   the year in the timestamp for the most recent changelog entry.
N: 
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: debian/copyright/dep5
N:   This tag is experimental.
N: 
N:
X: gtk3dialog source: upstream-metadata-file-is-missing
N: 
N:   This source package is not Debian-native but it does not have a
N:   debian/upstream/metadata file.
N:   
N:   The Upstream MEtadata GAthered with YAml (UMEGAYA) project is an effort to
N:   collect meta-information about upstream projects from any source package.
N:   This file is in YAML format and it is used in to feed the data in the
N:   UltimateDebianDatabase. For example, it can contains the way the authors
N:   want their software be cited in publications and some bibliographic
N:   references about the software.
N:   
N:   Please add a debian/upstream/metadata file.
N: 
N:   Please refer to https://dep-team.pages.debian.net/deps/dep12/ and
N:   https://wiki.debian.org/UpstreamMetadata for details.
N: 
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: debian/upstream/metadata
N:   This tag is experimental.
N: 
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1050 > 512 [examples/timer/clock:52]
N: 
N:   The source file includes a line length that is well beyond the normally
N:   human made code line length.
N:   
N:   This very long line length does not allow Lintian to do correctly some
N:   source file checks.
N:   
N:   This line could also be the result of some text injected by a computer
N:   program, and thus could lead to FTBFS bugs.
N:   
N:   Last but not least, long line in source code could be used to obfuscate
N:   the source code and to hide stuff like backdoors or security problems.
N:   
N:   It could be due to jslint source comments or other build tool comments.
N:   
N:   You may report this issue upstream.
N: 
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: files/contents/line-length
N:   Renamed from: insane-line-length-in-source-file
N:   This tag is experimental.
N: 
N:   Screen: autotools/long-lines
N:     Advocates: "Russ Allbery" <rra@debian.org>
N:     Reason: 
N:             Upstream sources using autoconf have traditionally been
N:             distributed with generated ./configure scripts as well as
N:             other third-party m4 macro files such as libtool.
N:             
N:             When paired with automake, there may also be some intermediate
N:             Makefile.in files.
N:             
N:             A lot of sources potentially contain such files, but they are
N:             not actionable by either the Debian distributor or by the
N:             upstream maintainer.
N:             
N:             As a side note, modern Debian build protocols will re-create
N:             many of those files via dh_autoreconf. They are present merely
N:             to aid in bootstrapping systems where the GNU suite may not yet
N:             be available.
N:             
N:             Read more in Bug#996740.
N: 
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/button.html:300]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/checkbox.html:271]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/chooser.html:238]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/colorbutton.html:275]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/comboboxentry.html:302]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/comboboxtext.html:301]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/edit.html:251]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/entry.html:310]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/eventbox.html:186]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/expander.html:265]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/fontbutton.html:264]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/frame.html:187]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/hbox.html:235]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/hscale.html:295]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/menu.html:266]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/menubar.html:186]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/menuitem.html:304]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/notebook.html:244]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/pixmap.html:234]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/progressbar.html:230]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/radiobutton.html:271]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/spinbutton.html:290]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/statusbar.html:257]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/terminal.html:341]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/text.html:261]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/timer.html:250]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/togglebutton.html:304]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/tree.html:419]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/vbox.html:236]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/vscale.html:295]
N:
X: gtk3dialog source: very-long-line-length-in-source-file 1267 > 512 [doc/gtk3dialog/reference/window.html:263]

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 494

Website

Re: Carbon Bugs

gtk3dialog had a lot of "missing source" errors, but I think that's a long line length thing that came up before. I'm pasting in the whole lintian (+pedantic and info) output below.

I do have a lintian-override for that.

gtk3dialog: source-is-missing [doc/gtk3dialog/reference/*.html]

More important, gtk3dialog fails to build without some extra packages in debian/control Build-Depends:

meson, ninja-build, bison, flex

The lack of meson triggered an error exit, and I noticed ninja in debian/rules so added that too. Then missing bison caused an exit, and likewise flex was referred to in the same file so I added that too. After that it built OK. You might want to consider whether any of those packages need to have versions specified.

Darn, forgot those - had them in a control somewhere.
meson (>= 1.0) IRRC.

With the lintian-overrides file in debian/source and appending

--lintian-opts --profile bunsenlabs

to the build command there *should* be not a peep out of lintian.

---

BTW is the labbe-material-icons repo still in use?
If not, delete it from BL?

No need for it any more. I'll just keep it on my GH account.

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,558

Website

Re: Carbon Bugs

With the lintian-overrides file in debian/source and appending

--lintian-opts --profile bunsenlabs

to the build command there *should* be not a peep out of lintian.

Anyway the package built OK so I uploaded it. But I won't push the edits I made to debian/control (the extra build-deps) - I'll leave that to you.

BTW is the labbe-material-icons repo still in use?
If not, delete it from BL?

No need for it any more. I'll just keep it on my GH account.

Sounds good.

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

wheresalice

New Member

Registered: 2025-07-01

Posts: 2

Re: Carbon Bugs

I tried an install via qemu this morning, using netinstall. I was a little surprised to see Dillo as the default browser, that's not something I've seen in years.

But the primary bug I wanted to report was what looks like a broken emoji in the menu, at the top next to "Type to search"

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,558

Website

Re: Carbon Bugs

^If you installed the "lite" or "base" version, you'll get Dillo as browser because it's much smaller and faster than Firefox. It's good enough for doing a quick search and reading documents, but "modern" websites will require Firefox or Chromium to be installed.

As to the menu search "icon", that's because the currently set icon emoji (from BL Boron) is not available in the currently used icon theme font (likewise). Details like this should be improved soon when an up-to-date version of bunsen-configs is uploaded. Please bear with us!

Last edited by johnraff (2025-07-01 11:07:45)

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,558

Website

Re: Carbon Bugs

But the primary bug I wanted to report was what looks like a broken emoji in the menu, at the top next to "Type to search"
https://i.imgur.com/ahsLToF.png

OK this is because the "base" and "lite" variants don't ship fonts-noto and its Recommend, fonts-noto-color-emoji. You can get the magnifying-glass glyph back at the top of the menu by running:

sudo apt install fonts-noto-color-emoji

It occupies 10.8 MB installed.

Alternatively, if you don't care so much about the magnifying-glass:
menu > User Settings > jgmenu > Edit Menu Content
and swap the commenting at the top so as not to use the emoji:

#@text,,6,6,150,20,2,left,top,auto,#000000 0,<span size="large">?︎</span>
@text,,6,6,150,20,2,left,top,auto,#000000 0,

Last edited by johnraff (2025-07-09 06:11:33)

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

dmontaine

Member

Registered: 2017-02-14

Posts: 79

Re: Carbon Bugs

When doing a carbon netinstall, only bunsen-meta-base works.  Both bunsen-meta-lite and bunsen-meta-all fail because the package qt5-style-plugins is missing.