#61 2025-02-15 17:07:37

Head_on_a_Stick

Member

From: London

Registered: 2015-09-29

Posts: 9,093

Website

Re: Carbon Bugs

the "Exit" menu option doesn't seem to do anything

^ This is because bl-exit is defined in ~/.config/jgmenu/prepend.csv but it is not available.

I have fixed this by using deadbang's method instead:

sudo apt install obsession
sed -i 's/bl-exit/obsession-logout/' ~/.config/jgmenu/prepend.csv

Scrot or it didn't happen:

---

Para todos todo, para nosotros nada

greenjeans

Member

Registered: 2025-01-18

Posts: 241

Website

Re: Carbon Bugs

+1 for Obsession, one of those old unicorn programs that despite having no active development in years just continues to work. I even use it in my Mate installs just so I can have fast keyboard-shortcuts to shutdown or reboot.

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,681

Website

Re: Carbon Bugs

the "Exit" menu option doesn't seem to do anything

^ This is because bl-exit is defined in ~/.config/jgmenu/prepend.csv but it is not available.

Is the package bunsen-exit installed? And if not, could you post the output of 'cat /etc/bunsen/bunsen_install'  Thanks!

Let's not rebuild the whole BL desktop from the ground up...

---

...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

Head_on_a_Stick

Member

From: London

Registered: 2015-09-29

Posts: 9,093

Website

Re: Carbon Bugs

Is the package bunsen-exit installed?

That was it, thanks :-)

The full-upgrade to trixie caused the package to be removed so I needed to explicitly re-install bunsen-meta-all, which fixed things.

---

Para todos todo, para nosotros nada

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 2,710

Re: Carbon Bugs

This is a Carbon Labwc installation based on Unstable.

The selected theme is BL-Litium and only Thunar does not follow it (the default theme is always displayed).
What have I messed up in the configuration? 

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,681

Website

Re: Carbon Bugs

^How about other gtk apps?

(Jgmenu takes it's theme from the openbox theme by default, so looks "Lithium" in the scrot.)

How about other gtk themes - does Thunar follow them?

---

...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

Head_on_a_Stick

Member

From: London

Registered: 2015-09-29

Posts: 9,093

Website

Re: Carbon Bugs

only Thunar does not follow it

I've seen that before, it was a long time ago but it's ringing dbus bells in my head.

What happens if you start Thunar from a terminal? Does it return any error messages?

---

Para todos todo, para nosotros nada

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 2,710

Re: Carbon Bugs

^How about other gtk apps?

(Jgmenu takes it's theme from the openbox theme by default, so looks "Lithium" in the scrot.)

How about other gtk themes - does Thunar follow them?

^This carbon-wayland installation only has these packages. I guess I am still missing something from @micko01.

dpkg -l | grep bunsen
ii  bunsen-archive-keyring                     2023.01.14+bl13-1                   all          BunsenLabs GnuPG archive key
ii  bunsen-common                              13.0.1-1                            all          Various shared files for BunsenLabs
ii  bunsen-configs-wbase                       13.0-1.2                            all          config files for minimal wayland BunsenLabs Linux
ii  bunsen-images-base                         13.1-1                              all          Images for use with BunsenLabs
ii  bunsen-numix-icon-theme                    13.0-1                              all          Some substitute icons for the Numix icon theme.
ii  bunsen-os-release                          13.0-1                              all          Controls OS and vendor identification on BunsenLabs systems
ii  bunsen-python-apt-template                 13.0-1                              all          Provides a distribution template for python-apt
ii  bunsen-themes-base                         13.0-1                              all          GTK, Openbox, and other themes for BunsenLabs on Debian
ii  bunsen-thunar                              13.0-1                              all          Modify the behaviour of Thunar for BunsenLabs

Indeed, the gtk applications do not follow the theme.

Also, I was not able to run the mount in Thunar with mate-polkit. With the installation of the lxpolkit package, however, immediately.

I don't have the error with 'fastfetch -c neofetch' that @micko01 describes in the neighboring thread.

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 2,710

Re: Carbon Bugs

only Thunar does not follow it

I've seen that before, it was a long time ago but it's ringing dbus bells in my head.

What happens if you start Thunar from a terminal? Does it return any error messages?

You said it, I've seen it before too. 

These dbus are installed.

dpkg -l | grep dbus*
ii  dbus                                       1.16.0-1                            amd64        simple interprocess messaging system (system message bus)
ii  dbus-bin                                   1.16.0-1                            amd64        simple interprocess messaging system (command line utilities)
ii  dbus-daemon                                1.16.0-1                            amd64        simple interprocess messaging system (reference message bus)
ii  dbus-session-bus-common                    1.16.0-1                            all          simple interprocess messaging system (session bus configuration)
ii  dbus-system-bus-common                     1.16.0-1                            all          simple interprocess messaging system (system bus configuration)
ii  dbus-user-session                          1.16.0-1                            amd64        simple interprocess messaging system (systemd --user integration)
ii  libdbus-1-3:amd64                          1.16.0-1                            amd64        simple interprocess messaging system (library)
ii  libdbusmenu-glib4:amd64                    18.10.20180917~bzr492+repack1-4     amd64        library for passing menus over DBus
ii  libdbusmenu-gtk3-4:amd64                   18.10.20180917~bzr492+repack1-4     amd64        library for passing menus over DBus - GTK-3+ version
ii  libqt5dbus5t64:amd64                       5.15.15+dfsg-4                      amd64        Qt 5 D-Bus module
ii  libqt6dbus6:amd64                          6.7.2+dfsg-6                        amd64        Qt 6 D-Bus module
ii  policycoreutils-dbus                       3.8-1                               all          SELinux core policy utilities (D-Bus daemon)
ii  python3-dbus                               1.3.2-5+b4                          amd64        simple interprocess messaging system (Python 3 interface)
ii  xdg-dbus-proxy                             0.1.6-1                             amd64        filtering D-Bus proxy

There are no error message(s). Tested with thunar and xarchiver. The start is correct.

Head_on_a_Stick

Member

From: London

Registered: 2015-09-29

Posts: 9,093

Website

Re: Carbon Bugs

The X.Org log will probably have the details then but I have to say that this is fairly normal for Debian testing, it only works for some of the time. Might be best to wait until the transition freeze starts (2025-03-15) before trying out Carbon, things should be settled down by then with most packages available and few changes until the release.

The release is usually ~6 months after the freeze starts so there should be plenty of time.

---

Para todos todo, para nosotros nada

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 2,710

Re: Carbon Bugs

The X.Org log will probably have the details then but I have to say that this is fairly normal for Debian testing, it only works for some of the time. Might be best to wait until the transition freeze starts (2025-03-15) before trying out Carbon, things should be settled down by then with most packages available and few changes until the release.

The release is usually ~6 months after the freeze starts so there should be plenty of time.

OK, thanks for your time. 

Your suggestion convinces me. So, I will wait.

Head_on_a_Stick

Member

From: London

Registered: 2015-09-29

Posts: 9,093

Website

Re: Carbon Bugs

Hold on a minute...

The Thunar problem is caused by xfconf not working so try the dbus-x11 package; dbus-user-session is relatively new so perhaps dbus-x11 will be more reliable. EDIT: also remove dbus-user-session or it will be used in preference over dbus-x11.

Last edited by Head_on_a_Stick (2025-02-21 18:54:41)

---

Para todos todo, para nosotros nada

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 2,710

Re: Carbon Bugs

Problem solved!

@micko01 has published his latest repo in the neighboring thread.

I was missing the package tweaks-gtk.
Installed, started and updated the settings - Thunar switched to the desired theme. Perfect!

Thank you, micko01 

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 2,710

Re: Carbon Bugs

This is the error message from the terminal when calling keepassxc.

$ keepassxc
QSocketNotifier: Can only be used with threads started with QThread
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
QDBusTrayIcon encountered a D-Bus error: QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name org.kde.StatusNotifierWatcher was not provided by any .service files")

The error is that the icon does not appear in the systray of the sfwbar. Which package am I missing?

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,681

Website

Re: Carbon Bugs

...try the dbus-x11 package; dbus-user-session is relatively new so perhaps dbus-x11 will be more reliable. EDIT: also remove dbus-user-session or it will be used in preference over dbus-x11.

For quite some time now BL has been shipping both dbus-x11 and dbus-user-session by default. They seem to be able to coexist comfortably - apps that use dbus-x11 will call dbus-launch directly.
Previous discussions:
https://forums.bunsenlabs.org/viewtopic … 33#p110633
https://forums.bunsenlabs.org/viewtopic … 61#p112161

But dbus-x11 is very much a thing of the past, and only a few apps still use dbus-launch as far as I know.

---

...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

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 2,710

Re: Carbon Bugs

Thank you.
It was indeed missing dbus-x11

dpkg -l dbus* | grep ii
ii  dbus                    1.16.0-1     amd64        simple interprocess messaging system (system message bus)
ii  dbus-bin                1.16.0-1     amd64        simple interprocess messaging system (command line utilities)
ii  dbus-daemon             1.16.0-1     amd64        simple interprocess messaging system (reference message bus)
ii  dbus-session-bus-common 1.16.0-1     all          simple interprocess messaging system (session bus configuration)
ii  dbus-system-bus-common  1.16.0-1     all          simple interprocess messaging system (system bus configuration)
ii  dbus-user-session       1.16.0-1     amd64        simple interprocess messaging system (systemd --user integration)
ii  dbus-x11                1.16.0-1     amd64        simple interprocess messaging system (X11 deps)

However, the error message does not change. 

It has to do with wayland, because in another labwc installation on sid, there is no such problem. I ran out of ideas for the comparisons I made.

@johnraff, you have more important things to do! I'll find it one day.   

Head_on_a_Stick

Member

From: London

Registered: 2015-09-29

Posts: 9,093

Website

Re: Carbon Bugs

Which package am I missing?

If xdg-desktop-portal-wlr is already installed try xdg-desktop-portal-kde.

---

Para todos todo, para nosotros nada

unklar

Back to the roots 1.9

From: #! BL

Registered: 2015-10-31

Posts: 2,710

Re: Carbon Bugs

Which package am I missing?

If xdg-desktop-portal-wlr is already installed try xdg-desktop-portal-kde.

It wants to install 124 dependency packages and lots of kde applications...

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,181

Website

Re: Carbon Bugs

Which package am I missing?

If xdg-desktop-portal-wlr is already installed try xdg-desktop-portal-kde.

It wants to install 124 dependency packages and lots of kde applications...

Screw that.

---

I don't care what you do at home. Would you care to explain?

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,181

Website

Re: Carbon Bugs

Is the package bunsen-exit installed?

That was it, thanks :-)

The full-upgrade to trixie caused the package to be removed so I needed to explicitly re-install bunsen-meta-all, which fixed things.

I also noticed this with my recent dist-upgrade from boron to carbon... tons of packages removed by sudo apt --purge autoremove. Check automremove before executing, as always, and reinstall as necessary.

---

I don't care what you do at home. Would you care to explain?