You are not logged in.

#1 2024-01-31 04:52:53

Ralf
Member
From: Ruhrgebiet
Registered: 2013-03-15
Posts: 56

[solved] How to disable gtk3 client side decoration?

Hi,

is it still possible to disable gtk3 client side decoration?

I use extra/openbox, not a desktop environment.

Recently, every now and then, the GTK theme randomly changes into an abomination during a session. I finally managed to find a programme that is guaranteed to always trigger this problem, extra/atril, with "Theme parsing error: csd.css" and the like.

I don't need atril, but unfortunately the problem is occasionally triggered by other programmes, not always, but randomly so to speak.

To be on the safe side, I rebuild aur/gtk3-nocsd-git and replaced my customised gtk-theme-name=Arc-RM-Cornflower with Adwaita in .config/gtk-3.0/settings.ini, but the problem remained.

In the next step I replaced extra/gtk3 and aur/gtk3-nocsd-git with chaotic-aur/gtk3-classic, but that didn't change anything, the problem still occurs. I can't tell yet if it will continue to occur randomly, but atril still triggers it.

Are any of you still able to get rid of client side decoration without any problems?

Regards,
Ralf

Last edited by Ralf (2024-01-31 14:47:03)

Offline

#2 2024-01-31 08:47:19

dreieck
Member
Registered: 2012-10-08
Posts: 64

Re: [solved] How to disable gtk3 client side decoration?

I use "gtk3-classic" (upstream, chaotic-aur, AUR) and with this I have no client side decoration with GTK3 (e.g. "gedit").

(Regarding your theme change: I see with claws mail that after "something" (some time) after a fresh launch of 'claws-mail' the fonts and some font colours change, and this stays persistent until programme restart. 
That does not sound like your issue.)

Regards!

Offline

#3 2024-01-31 08:55:35

Ralf
Member
From: Ruhrgebiet
Registered: 2013-03-15
Posts: 56

Re: [solved] How to disable gtk3 client side decoration?

False alarm, I have now installed gtk3 only and no problems with a new user account, but my old user account still has this problem. Some config must still be fishy.

Offline

#4 2024-01-31 14:47:20

Ralf
Member
From: Ruhrgebiet
Registered: 2013-03-15
Posts: 56

Re: [solved] How to disable gtk3 client side decoration?

Hi,

the issue is most likely solved.

At first I've done a lot of

  grep -i csd .*

and similar

  grep -i csd

commands, to no avail.

After hours of testing with a newly created user account and my old user account, by disabling this and that on the old user account and coping over dirs and files to the new user account, I could always cause the problem by starting atril on my old user account, no matter if I tried gtk3 alone, gtk3 with gtk3-nocsd-git or gtk3-classic. The problem only rarely occurred in the newly created user account.

I finally removed dbus-broker-units and dbus-broker and installed dbus-daemon-units.

This seems to have solved the problem, regardless of whether I use gtk3 alone, gtk3 with gtk3-nocsd-git or gtk3-classic.

By the way, I have no client side decoration with programs like evolution, sylpheed, roxterm and many others, no matter if I use gtk3 alone, gtk3 with gtk3-nocsd-git or gtk3-classic. Roughly speaking, it doesn't seem to make any difference, but I went back to the old setup and use gtk3 with gtk3-nocsd-git.

The culprit was probably a combination of my openbox customised with scripts and dbus-broker.

Regards,
Ralf

Offline

#5 2024-01-31 15:13:28

seth
Member
Registered: 2012-09-03
Posts: 58,717

Re: [solved] How to disable gtk3 client side decoration?

Did you check the system journal which specific services were failing w/ dbus-broker?
(You can still access them, "sudo journalctl -b -1" for the previous one, you can skip sudo if you're in an relevant admin group)

Offline

#6 2024-01-31 15:42:20

Ralf
Member
From: Ruhrgebiet
Registered: 2013-03-15
Posts: 56

Re: [solved] How to disable gtk3 client side decoration?

With dbus-broker:

• rocketmouse@archlinux ~ 
$ sudo journalctl -b -9 | grep dbus | grep -i fail
Jan 31 04:42:24 archlinux dbus-broker-launch[488]: Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.
Jan 31 04:52:30 archlinux systemd[819]: dbus-:1.8-org.a11y.atspi.Registry@0.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 04:52:30 archlinux systemd[819]: dbus-:1.8-org.a11y.atspi.Registry@0.service: Failed with result 'exit-code'.
Jan 31 04:52:30 archlinux systemd[819]: dbus-:1.2-org.mate.SettingsDaemon@0.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 04:52:30 archlinux systemd[819]: dbus-:1.2-org.mate.SettingsDaemon@0.service: Failed with result 'exit-code'.
Jan 31 05:08:08 archlinux systemd[819]: dbus-:1.8-org.a11y.atspi.Registry@1.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 05:08:08 archlinux systemd[819]: dbus-:1.8-org.a11y.atspi.Registry@1.service: Failed with result 'exit-code'.
Jan 31 05:08:08 archlinux systemd[819]: dbus-:1.2-org.gnome.GConf@0.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 05:08:08 archlinux systemd[819]: dbus-:1.2-org.gnome.GConf@0.service: Failed with result 'exit-code'.
• rocketmouse@archlinux ~ 
$ sudo journalctl -b -8 | grep dbus | grep -i fail
Jan 31 05:08:35 archlinux dbus-broker-launch[481]: Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.
Jan 31 05:12:13 archlinux systemd[794]: dbus-:1.8-org.a11y.atspi.Registry@0.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 05:12:13 archlinux systemd[794]: dbus-:1.8-org.a11y.atspi.Registry@0.service: Failed with result 'exit-code'.
Jan 31 05:12:13 archlinux systemd[794]: dbus-:1.2-org.mate.SettingsDaemon@0.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 05:12:13 archlinux systemd[794]: dbus-:1.2-org.mate.SettingsDaemon@0.service: Failed with result 'exit-code'.
Jan 31 05:22:18 archlinux systemd[794]: dbus-:1.8-org.a11y.atspi.Registry@1.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 05:22:18 archlinux systemd[794]: dbus-:1.8-org.a11y.atspi.Registry@1.service: Failed with result 'exit-code'.
Jan 31 05:22:18 archlinux systemd[794]: dbus-:1.2-org.mate.SettingsDaemon@1.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 05:22:18 archlinux systemd[794]: dbus-:1.2-org.mate.SettingsDaemon@1.service: Failed with result 'exit-code'.
Jan 31 06:51:20 archlinux systemd[794]: dbus-:1.8-org.a11y.atspi.Registry@2.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 06:51:20 archlinux systemd[794]: dbus-:1.8-org.a11y.atspi.Registry@2.service: Failed with result 'exit-code'.
Jan 31 06:51:20 archlinux systemd[794]: dbus-:1.2-org.mate.SettingsDaemon@2.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 06:51:20 archlinux systemd[794]: dbus-:1.2-org.mate.SettingsDaemon@2.service: Failed with result 'exit-code'.
Jan 31 06:56:51 archlinux systemd[794]: dbus-:1.8-org.a11y.atspi.Registry@3.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 06:56:51 archlinux systemd[794]: dbus-:1.8-org.a11y.atspi.Registry@3.service: Failed with result 'exit-code'.
Jan 31 06:56:51 archlinux systemd[794]: dbus-:1.2-org.gnome.GConf@0.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 06:56:51 archlinux systemd[794]: dbus-:1.2-org.gnome.GConf@0.service: Failed with result 'exit-code'.
• rocketmouse@archlinux ~ 
$ sudo journalctl -b -7 | grep dbus | grep -i fail
Jan 31 06:57:27 archlinux dbus-broker-launch[482]: Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.
Jan 31 07:05:14 archlinux systemd[814]: dbus-:1.8-org.a11y.atspi.Registry@0.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 07:05:14 archlinux systemd[814]: dbus-:1.8-org.a11y.atspi.Registry@0.service: Failed with result 'exit-code'.
Jan 31 07:05:14 archlinux systemd[814]: dbus-:1.2-org.mate.SettingsDaemon@0.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 07:05:14 archlinux systemd[814]: dbus-:1.2-org.mate.SettingsDaemon@0.service: Failed with result 'exit-code'.
Jan 31 07:13:35 archlinux systemd[814]: dbus-:1.8-org.a11y.atspi.Registry@1.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 07:13:35 archlinux systemd[814]: dbus-:1.8-org.a11y.atspi.Registry@1.service: Failed with result 'exit-code'.
Jan 31 07:13:35 archlinux systemd[814]: dbus-:1.2-org.mate.SettingsDaemon@1.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 07:13:35 archlinux systemd[814]: dbus-:1.2-org.mate.SettingsDaemon@1.service: Failed with result 'exit-code'.
Jan 31 07:13:35 archlinux systemd[814]: dbus-:1.2-org.gnome.GConf@0.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 07:13:35 archlinux systemd[814]: dbus-:1.2-org.gnome.GConf@0.service: Failed with result 'exit-code'.

Now without dbus-broker:

• rocketmouse@archlinux ~ 
$ sudo journalctl -b -1 | grep dbus | grep -i fail
Jan 31 15:03:40 archlinux dbus-daemon[488]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Jan 31 15:03:41 archlinux dbus-daemon[488]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Jan 31 15:03:45 archlinux dbus-daemon[488]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Jan 31 15:03:48 archlinux dbus-daemon[488]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Jan 31 15:08:05 archlinux dbus-daemon[488]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Jan 31 15:09:11 archlinux dbus-daemon[488]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Jan 31 15:10:49 archlinux dbus-daemon[488]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Jan 31 15:11:49 archlinux dbus-daemon[488]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
• rocketmouse@archlinux ~ 
$ sudo journalctl -b -0 | grep dbus | grep -i fail | tail -5
Jan 31 16:34:22 archlinux dbus-daemon[503]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Jan 31 16:34:35 archlinux dbus-daemon[503]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Jan 31 16:34:39 archlinux dbus-daemon[503]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Jan 31 16:34:48 archlinux dbus-daemon[503]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Jan 31 16:34:58 archlinux dbus-daemon[503]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.

Offline

#7 2024-01-31 16:31:11

seth
Member
Registered: 2012-09-03
Posts: 58,717

Re: [solved] How to disable gtk3 client side decoration?

Looks partly like https://bbs.archlinux.org/viewtopic.php … 5#p2147685 but also the generic dbus-:1.2-org.gnome.GConf@0.service and dbus-:1.2-org.mate.SettingsDaemon@2.service are just failing and I assume they're more relevant wrt your gtk config.
Does the journal context say why they're failing (permission error etc.)

Ftr, there seem to be systematic errors/problems w/ the dbus-broker generated services (ie. if the dbus service doesn't reference a systemd service and dbus-broker just makes one up, presumingly from the Exec line)
Edit, x-ref: https://bbs.archlinux.org/viewtopic.php … 4#p2146584

Last edited by seth (2024-01-31 16:31:55)

Offline

#8 2024-01-31 17:45:10

Ralf
Member
From: Ruhrgebiet
Registered: 2013-03-15
Posts: 56

Re: [solved] How to disable gtk3 client side decoration?

Hi,

the journal context doesn't mention why they're failing, but dbus-broker cares about all countless stuff that I don't use at all.

• rocketmouse@archlinux ~ 
$ sudo journalctl -b -8 | grep dbus | grep -i fail -A5 -B5 | head -23
Jan 31 05:08:34 archlinux dbus-broker-launch[481]: Ready
Jan 31 05:08:35 archlinux dbus-broker-launch[481]: Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.
Jan 31 05:08:35 archlinux dbus-broker-launch[745]: Service file '/usr/share/dbus-1/services/nemo.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
Jan 31 05:08:35 archlinux dbus-broker-launch[745]: Service file '/usr/share/dbus-1/services/nemo.service' is not named after the D-Bus name 'org.Nemo'.
Jan 31 05:08:35 archlinux dbus-broker-launch[745]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share/dbus-1/services/org.freedesktop.FileManager1.service'
Jan 31 05:08:35 archlinux dbus-broker-launch[745]: Service file '/usr/share/dbus-1/services/org.gnome.Caribou.Antler.service' is not named after the D-Bus name 'org.gnome.Caribou.Keyboard'.
Jan 31 05:08:35 archlinux dbus-broker-launch[745]: Service file '/usr/share/dbus-1/services/org.nongnu.lash.service' is not named after the D-Bus name 'org.nongnu.LASH'.
--
Jan 31 05:08:57 archlinux systemd[794]: Started dbus-:1.2-org.gnome.GConf@0.service.
Jan 31 05:10:42 archlinux systemd[794]: Created slice Slice /app/dbus-:1.2-org.mate.SettingsDaemon.
Jan 31 05:10:42 archlinux systemd[794]: Created slice Slice /app/dbus-:1.2-org.mate.atril.Daemon.
Jan 31 05:10:42 archlinux systemd[794]: Started dbus-:1.2-org.mate.SettingsDaemon@0.service.
Jan 31 05:10:42 archlinux systemd[794]: Started dbus-:1.2-org.mate.atril.Daemon@0.service.
Jan 31 05:12:13 archlinux systemd[794]: dbus-:1.8-org.a11y.atspi.Registry@0.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 05:12:13 archlinux systemd[794]: dbus-:1.8-org.a11y.atspi.Registry@0.service: Failed with result 'exit-code'.
Jan 31 05:12:13 archlinux systemd[794]: dbus-:1.2-org.mate.SettingsDaemon@0.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 05:12:13 archlinux systemd[794]: dbus-:1.2-org.mate.SettingsDaemon@0.service: Failed with result 'exit-code'.
Jan 31 05:12:15 archlinux dbus-broker-launch[1805]: Service file '/usr/share/dbus-1/services/nemo.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
Jan 31 05:12:15 archlinux dbus-broker-launch[1805]: Service file '/usr/share/dbus-1/services/nemo.service' is not named after the D-Bus name 'org.Nemo'.
Jan 31 05:12:15 archlinux dbus-broker-launch[1805]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share/dbus-1/services/org.freedesktop.FileManager1.service'
Jan 31 05:12:15 archlinux dbus-broker-launch[1805]: Service file '/usr/share/dbus-1/services/org.gnome.Caribou.Antler.service' is not named after the D-Bus name 'org.gnome.Caribou.Keyboard'.
Jan 31 05:12:15 archlinux dbus-broker-launch[1805]: Service file '/usr/share/dbus-1/services/org.nongnu.lash.service' is not named after the D-Bus name 'org.nongnu.LASH'.
--

Lash is an excellent example. I never used lash, it's an ancient dependency.

• rocketmouse@archlinux ~ 
$ pacman -Qo /usr/share/dbus-1/services/org.nongnu.lash.service
/usr/share/dbus-1/services/org.nongnu.lash.service is owned by lash 0.6.0~rc2-14
• rocketmouse@archlinux ~ 
$ pacman -Qi lash
Name            : lash
Version         : 0.6.0~rc2-14
Description     : Session management system for JACK and ALSA
Architecture    : x86_64
URL             : http://lash.nongnu.org
Licenses        : GPL2
Groups          : None
Provides        : None
Depends On      : jack  python2
Optional Deps   : gtk2: for lash_panel, lash_save_button and lash_synth [installed]
Required By     : phasex-git
Optional For    : jack-keyboard
Conflicts With  : None
Replaces        : None
Installed Size  : 568.00 KiB
Packager        : Ralf Mardorf <ralf.mardorf@rocketmail.com>
Build Date      : Thu 05 Jul 2018 00:23:37 CEST
Install Date    : Thu 05 Jul 2018 00:24:01 CEST
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : None

With dbus-broker it takes care of the unused lash, with dbus-daemon-units it does not take care of it.

• rocketmouse@archlinux ~ 
$ sudo journalctl -b -8 | grep -i lash
Jan 31 05:08:35 archlinux dbus-broker-launch[745]: Service file '/usr/share/dbus-1/services/org.nongnu.lash.service' is not named after the D-Bus name 'org.nongnu.LASH'.
Jan 31 05:08:41 archlinux dbus-broker-launch[813]: Service file '/usr/share/dbus-1/services/org.nongnu.lash.service' is not named after the D-Bus name 'org.nongnu.LASH'.
Jan 31 05:12:15 archlinux dbus-broker-launch[1805]: Service file '/usr/share/dbus-1/services/org.nongnu.lash.service' is not named after the D-Bus name 'org.nongnu.LASH'.
Jan 31 05:22:19 archlinux dbus-broker-launch[3181]: Service file '/usr/share/dbus-1/services/org.nongnu.lash.service' is not named after the D-Bus name 'org.nongnu.LASH'.
Jan 31 06:51:21 archlinux dbus-broker-launch[8848]: Service file '/usr/share/dbus-1/services/org.nongnu.lash.service' is not named after the D-Bus name 'org.nongnu.LASH'.
• rocketmouse@archlinux ~ 
$ sudo journalctl -b -0 | grep -i lash
• rocketmouse@archlinux ~ 
$ sudo journalctl -b -1 | grep -i lash

I only get the theme parsing errors with dbus-broker.

• rocketmouse@archlinux ~ 
$ sudo journalctl -b -8 | grep csd.css -A4 -B5 | head -20
Jan 31 05:10:42 archlinux xdg-desktop-por[1005]: Theme parsing error: gtk-widgets.css:1232:14: Expected a string.
Jan 31 05:10:42 archlinux xdg-desktop-por[1005]: Theme parsing error: panel.css:12:25: The :insensitive pseudo-class is deprecated. Use :disabled instead.
Jan 31 05:10:42 archlinux xdg-desktop-por[1005]: Theme parsing error: panel.css:13:25: The :insensitive pseudo-class is deprecated. Use :disabled instead.
Jan 31 05:10:42 archlinux xdg-desktop-por[1005]: Theme parsing error: panel.css:48:28: The :prelight pseudo-class is deprecated. Use :hover instead.
Jan 31 05:10:42 archlinux xdg-desktop-por[1005]: Theme parsing error: panel.css:48:65: The :prelight pseudo-class is deprecated. Use :hover instead.
Jan 31 05:10:42 archlinux xdg-desktop-por[1005]: Theme parsing error: csd.css:20:25: The :insensitive pseudo-class is deprecated. Use :disabled instead.
Jan 31 05:10:42 archlinux xdg-desktop-por[1005]: Theme parsing error: csd.css:20:50: The :insensitive pseudo-class is deprecated. Use :disabled instead.
Jan 31 05:10:42 archlinux xdg-desktop-por[1005]: Theme parsing error: csd.css:53:35: The :insensitive pseudo-class is deprecated. Use :disabled instead.
Jan 31 05:10:42 archlinux xdg-desktop-por[1005]: Theme parsing error: csd.css:54:31: The :insensitive pseudo-class is deprecated. Use :disabled instead.
Jan 31 05:10:42 archlinux xdg-desktop-por[1005]: Theme parsing error: csd.css:150:14: not a number
Jan 31 05:10:42 archlinux xdg-desktop-por[1005]: Theme parsing error: csd.css:150:14: Expected a string.
Jan 31 05:10:42 archlinux xdg-desktop-por[1005]: Theme parsing error: csd.css:185:15: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'
Jan 31 05:10:42 archlinux xdg-desktop-por[1005]: Theme parsing error: csd.css:192:15: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'
Jan 31 05:10:42 archlinux xdg-desktop-por[1005]: Theme parsing error: csd.css:199:15: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'
Jan 31 05:10:42 archlinux xdg-desktop-por[1005]: Theme parsing error: csd.css:208:15: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'
Jan 31 05:10:42 archlinux xdg-desktop-por[1005]: Theme parsing error: csd.css:216:15: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow'
Jan 31 05:10:42 archlinux xdg-desktop-por[1005]: Theme parsing error: lightdm-gtk-greeter.css:13:14: Expected a string.
Jan 31 05:10:42 archlinux xdg-desktop-por[1005]: Theme parsing error: gtk-widgets.css:9:10: The 'engine' property is ignored
Jan 31 05:10:42 archlinux xdg-desktop-por[1005]: Theme parsing error: gtk-widgets.css:23:33: The style property GtkMenu:horizontal-padding is deprecated and shouldn't be used anymore. It will be removed in a future version
Jan 31 05:10:42 archlinux xdg-desktop-por[1005]: Theme parsing error: gtk-widgets.css:24:31: The style property GtkMenu:vertical-padding is deprecated and shouldn't be used anymore. It will be removed in a future version

Regards,
Ralf

Offline

#9 2024-01-31 17:50:25

Ralf
Member
From: Ruhrgebiet
Registered: 2013-03-15
Posts: 56

Re: [solved] How to disable gtk3 client side decoration?

The problem is solved for me for the time being. I've lost a whole day and have to catch up on work.

In the meantime, it seems to me that it's not my scripts in combination with dbus-broker, but that dbus--broker has been introduced into production environments in an immature way, like so many other things before it.

Offline

#10 2024-01-31 21:53:09

seth
Member
Registered: 2012-09-03
Posts: 58,717

Re: [solved] How to disable gtk3 client side decoration?

Service file '/usr/share/dbus-1/services/org.nongnu.lash.service' is not named after the D-Bus name 'org.nongnu.LASH'

This is uncritical, dbus-broker is a bit more of a stickler but this has no consequences.

I only get the theme parsing errors with dbus-broker.

They're all xdg-desktop-portal, so likely just follow ups to the overall dbus issues or the specific problems w/ the gconf and mate.settingsDaemon services.

'org.freedesktop.home1' is systemd spam and regardless of the dbus implementation.

The only real problem I can make out for now are the failing generic dbus-:1.2-org.gnome.GConf@0.service and dbus-:1.2-org.mate.SettingsDaemon@2.service (next to teh known issues w/ the likewise generic dbus-:1.8-org.a11y.atspi.Registry@0.service and jack2 service)

In the meantime, it seems to me that it's not my scripts in combination with dbus-broker

This isn't a script(?) issue at all, as mentioned dbus-brokers habit to generate systemd services on the fly seems to be bogus.

The problem is solved for me for the time being.

No, problem; I'm trying to structure the issues for the wider audience, you've been very helpful w/ your journal reports and there's no requirement of further action.

has been introduced into production environments in an immature way

Fedora is apparently running it since 2019, it'll also completely break your system if you've a typo in a config file lol

Offline

Board footer

Powered by FluxBB