[SOLVED]A lot of different services relating to dbus-broker are failin

Pena · 2024-03-12 19:28:40

So im unshure if this has to do with the recent decision to make dbus-broker the default implementation or if its just a coicidence/me not mantaining my own OS.

The most noticeable failing is Dunst, which refuses to pop up, for some reason if i boot up the pc and force him to show up by running the program, he displays some error relating to VirtualBox, which right now is a battle i dont wanna fight (yesterday or so i was distracted and ended up deleting the kernel and destroying the bootloader)

Next is yakuake which refuses to pop open when pressing F12, he works fine if manually executed via shell

mar 12 19:19:25 micron dbus-broker-launch[6905]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░ 
░░ A service file is a ini-type configuration file.
░░ 
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░ 
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.
mar 12 19:19:25 micron dbus-broker-launch[6905]: Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░ 
░░ A service file is a ini-type configuration file.
░░ 
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░ 
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.
mar 12 19:19:25 micron dbus-broker-launch[6905]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
mar 12 19:19:25 micron dbus-broker-launch[6905]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
mar 12 19:19:25 micron dbus-broker-launch[6905]: Service file '/usr/share//dbus-1/services/org.knopwob.dunst.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░ 
░░ A service file is a ini-type configuration file.
░░ 
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░ 
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.
mar 12 19:19:25 micron dbus-broker-launch[6905]: Ignoring duplicate name 'org.freedesktop.Notifications' in service file '/usr/share//dbus-1/services/org.knopwob.dunst.service'
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░ 
░░ A service file is a ini-type configuration file.
░░ 
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also

Edit: Solved tag, title had to be shortned

Last edited by Pena (2024-03-18 19:38:29)

seth · 2024-03-12 20:13:41

*NEVER* use -x w/ journalctl, it's pure spam.
The dbus-broker messages there

mar 12 19:19:25 micron dbus-broker-launch[6905]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
mar 12 19:19:25 micron dbus-broker-launch[6905]: Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
mar 12 19:19:25 micron dbus-broker-launch[6905]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
mar 12 19:19:25 micron dbus-broker-launch[6905]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
mar 12 19:19:25 micron dbus-broker-launch[6905]: Service file '/usr/share//dbus-1/services/org.knopwob.dunst.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
mar 12 19:19:25 micron dbus-broker-launch[6905]: Ignoring duplicate name 'org.freedesktop.Notifications' in service file '/usr/share//dbus-1/services/org.knopwob.dunst.service'

are just noise.

Plasma 6 now defaults to wayland, what might be an issue.
Do things still work when explcitly starting an X11 session?

Pena · 2024-03-12 20:19:51

seth wrote:

*NEVER* use -x w/ journalctl, it's pure spam.
The dbus-broker messages there

mar 12 19:19:25 micron dbus-broker-launch[6905]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
mar 12 19:19:25 micron dbus-broker-launch[6905]: Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
mar 12 19:19:25 micron dbus-broker-launch[6905]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
mar 12 19:19:25 micron dbus-broker-launch[6905]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
mar 12 19:19:25 micron dbus-broker-launch[6905]: Service file '/usr/share//dbus-1/services/org.knopwob.dunst.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
mar 12 19:19:25 micron dbus-broker-launch[6905]: Ignoring duplicate name 'org.freedesktop.Notifications' in service file '/usr/share//dbus-1/services/org.knopwob.dunst.service'

are just noise.

Plasma 6 now defaults to wayland, what might be an issue.
Do things still work when explcitly starting an X11 session?

Im sorry i was unaware tipically i just do -xe or -xeu

I was pretty shure i am running an x11 instance but just to be safe:

loginctl show-session 2 -p Type
Type=x11

I forgot to mention that my system is a mess as i worked with plasma for a year or so but migrated to Openbox later, but never got to fully migrate/get rid of everything,
I've checked dolphin, konsole, etc... and they seem to run without any issues...

seth · 2024-03-12 20:36:00

ps aux | grep dunst
systemctl --user status dunst

he displays some error relating to VirtualBox

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855

Yakuake seems only dbus activated

qdbus org.kde.yakuake
echo $DBUS_SESSION_BUS_ADDRESS

i worked with plasma for a year or so but migrated to Openbox later

How do you run the session? Startx?
Please post your xinitrc (and see the last link below) in that case.

Pena · 2024-03-12 21:08:24

I think SDDM launches automatically X11 for me, im unshure as this was like 5 years ago, i dont have a xinitrc in the home directory. However when i worked on a bPI device i remember also having sddm and still having the xinitrc at home directory, Is there a way for me to know where the X instance is being launched?

seth · 2024-03-12 21:10:36

loginctl session-status

Pena · 2024-03-13 16:03:47

so i presume its launched by sddm automatically?

├─3596 /usr/lib/sddm/sddm-helper --socket /tmp/sddm-auth-d8476505-7df6-406a-9c53-e6666e0a2bf5 --id 1 --sta>
         ├─3630 /usr/bin/kwalletd6 --pam-login 12 14
         ├─3631 /usr/bin/openbox --startup "/usr/lib/openbox/openbox-autostart OPENBOX"
         ├─3648 notify-send "VBoxClient: the VirtualBox kernel service is not running.  Exiting."
         ├─3665 polybar main
         ├─3666 redshift -l 39.749535 -8.807683
         ├─3667 xrootgif -q -a /home/micron/sav/Configs/wallpaper3.gif
         ├─3668 yakuake
         ├─3706 picom --config sav/Configs/Scripts/picom.conf
         ├─3730 bash /home/micron/.config/polybar/scripts/check-network
         ├─4494 /bin/dash
         ├─4599 /usr/lib/firefox-developer-edition/firefox
         ├─4693 /usr/lib/firefox-developer-edition/firefox -contentproc -parentBuildID 20240308173419 -prefsLen 345>
         ├─4724 /usr/lib/firefox-developer-edition/firefox -contentproc -childID 1 -isForBrowser -prefsLen 34684 -p>
         ├─4812 /usr/lib/firefox-developer-edition/firefox -contentproc -childID 2 -isForBrowser -prefsLen 39941 -p>
         ├─4896 /usr/lib/firefox-developer-edition/firefox -contentproc -parentBuildID 20240308173419 -sandboxingKi>
         ├─4912 /usr/lib/firefox-developer-edition/firefox -contentproc -childID 3 -isForBrowser -prefsLen 32916 -p>
         ├─4939 /opt/vdhcoapp/vdhcoapp /home/micron/.mozilla/native-messaging-hosts/net.downloadhelper.coapp.json {>
         ├─4940 /usr/lib/firefox-developer-edition/firefox -contentproc -childID 4 -isForBrowser -prefsLen 32916 -p>
         ├─4943 /usr/lib/firefox-developer-edition/firefox -contentproc -childID 5 -isForBrowser -prefsLen 32916 -p>
         ├─5034 /usr/lib/firefox-developer-edition/firefox -contentproc -childID 6 -isForBrowser -prefsLen 32916 -p>
         ├─5044 /usr/lib/firefox-developer-edition/firefox -contentproc -childID 7 -isForBrowser -prefsLen 32916 -p>
         ├─5114 /usr/lib/firefox-developer-edition/firefox -contentproc -childID 8 -isForBrowser -prefsLen 32916 -p>
         ├─5157 konsole
         ├─5167 /bin/zsh
         ├─5474 sleep 0.5
         ├─5529 /bin/zsh
         ├─5530 /usr/bin/lua /usr/share/z.lua/z.lua --add /home/micron
         ├─5533 /bin/zsh
         ├─5534 /usr/bin/lua /usr/share/z.lua/z.lua --add /home/micron
         ├─5537 /bin/zsh
         ├─5538 /usr/bin/lua /usr/share/z.lua/z.lua --add /home/micron
         ├─5539 loginctl session-status
         └─5540 less

seth · 2024-03-13 16:15:30

Don't copypaste out out of the pager, it truncates the output. Redirect it into a file or pastebin service.
It looks like you're using SDDM to start an openbox session, what about the output of the commands in #4 ?

Edit: though yakuake is already running at this point, the qdbus access is only interesting when there's no yakuake service (yet)

Last edited by seth (2024-03-13 16:16:13)

Pena · 2024-03-13 17:28:21

http://0x0.st/HFiL.txt
for the qdbus command
and for the other its

unix:path=/run/user/1000/bus

seth · 2024-03-13 18:08:39

So yakuake responds; in case there was no previous instance, it must have been dbus activated.

There's a bunch of threads concerning shortcuts on KDE being broken and this might be part of that - https://bugs.kde.org/show_bug.cgi?id=482712

As for dunst, does

qdbus org.freedesktop.Notifications
dunstctl count

respond?

Pena · 2024-03-13 22:01:58

qdbus org.freedesktop.Notifications results in:

Error: org.freedesktop.DBus.Error.NoReply
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Dunstctl count results in:

Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to communicate with dunst, is it running? Or maybe the version is outdated. You can try 'dunstctl debug' as a next debugging step.

Dunstctl debug results in:

Dunst is not running.

seth · 2024-03-13 22:24:42

So org.freedesktop.Notifications desn't kick off dunst.

cat /usr/share/dbus-1/services/org.knopwob.dunst.service
systemctl --user status dunst

Edit:

ls -l /etc/dbus-1/services ~/.local/share/dbus-1/services

Last edited by seth (2024-03-13 22:27:08)

Pena · 2024-03-14 13:58:26

I saw the edit but do to the results i will still post the other commands:

cat /usr/share/dbus-1/services/org.knopwob.dunst.service

[D-BUS Service]
Name=org.freedesktop.Notifications
Exec=/usr/bin/dunst
SystemdService=dunst.service

systemctl --user status dunst                                                                          13:56:10
○ dunst.service - Dunst notification daemon
     Loaded: loaded (/usr/lib/systemd/user/dunst.service; static)
     Active: inactive (dead)
       Docs: man:dunst(1)

LANG=en_US.UTF-8 ls -l /etc/dbus-1/services ~/.local/share/dbus-1/services                             13:57:47
ls: cannot access '/etc/dbus-1/services': No such file or directory
ls: cannot access '/home/micron/.local/share/dbus-1/services': No such file or directory

Edit:
on /etc/dbus-1/ theres pretty much nothing only a folder relating to system-d and inside it its empty

Last edited by Pena (2024-03-14 13:59:33)

seth · 2024-03-14 15:17:38

This looks all normal and like dbus should kickoff dunst.
Make sure dunst isn't running

sudo journalctl -fe

and in a second terminal

qdbus org.freedesktop.Notifications

Does that trigger any messages in the journal?

Pena · 2024-03-14 20:55:14

Interesting, i first tried to check the results without doing anything really just to see the result, and then i tried to pack it into a file and the following is the result

⤷  micron☩  ~ qdbus org.freedesktop.Notifications                                                                    20:48:16
Error: org.freedesktop.DBus.Error.NameHasNoOwner
Could not activate remote peer: unit failed.
⤷  micron☩  ~ qdbus org.freedesktop.Notifications                                                                    20:48:58
Error: org.freedesktop.DBus.Error.NoReply
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

on the other side not much is happening until it fails really
http://0x0.st/HF16.txt

seth · 2024-03-14 21:47:16

Maybe not much, but probably enough.

mar 14 20:48:58 micron plasma_waitforname[3129]: org.kde.knotifications: WaitForName: Service was not registered within timeout
mar 14 20:48:58 micron systemd[3075]: dbus-:1.2-org.freedesktop.Notifications@0.service: Main process exited, code=exited, status=1/FAILURE
mar 14 20:48:58 micron systemd[3075]: dbus-:1.2-org.freedesktop.Notifications@0.service: Failed with result 'exit-code'.
mar 14 20:48:58 micron systemd[3075]: Started dbus-:1.2-org.freedesktop.Notifications@1.service.
mar 14 20:49:37 micron systemd[1]: libvirtd.service: Deactivated successfully.
mar 14 20:49:58 micron plasma_waitforname[5814]: org.kde.knotifications: WaitForName: Service was not registered within timeout
mar 14 20:49:58 micron systemd[3075]: dbus-:1.2-org.freedesktop.Notifications@1.service: Main process exited, code=exited, status=1/FAILURE
mar 14 20:49:58 micron systemd[3075]: dbus-:1.2-org.freedesktop.Notifications@1.service: Failed with result 'exit-code'.
mar 14 20:50:23 micron Tor[2884]: Failed to find node for hop #1 of our path. Discarding this circuit.

It seems the plasma notification service takes precedence over dunst but fails:

ls -l /usr/share/dbus-1/services

Pena · 2024-03-18 18:02:00

heres the result of the ls under services

http://0x0.st/XrTU.txt

i did a systemctl --user status and heres some info about org.kde.notifications

app-dbus\x2d:1.2\x2dorg.freedesktop.Notifications.slice - Slice /app/dbus-:1.2-org.freedesktop.Notifications
     Loaded: loaded
     Active: active since Mon 2024-03-18 16:35:35 WET; 1h 21min ago
      Tasks: 0
     Memory: 136.0K (peak: 1.7M)
        CPU: 18ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/app-dbus\x2d:1.2\x2dorg.freedesktop.Notifications.slice

mar 18 16:35:35 micron systemd[2772]: Created slice Slice /app/dbus-:1.2-org.freedesktop.Notifications.
mar 18 16:36:35 micron plasma_waitforname[2826]: org.kde.knotifications: WaitForName: Service was not registered within timeout
mar 18 16:37:35 micron plasma_waitforname[3868]: org.kde.knotifications: WaitForName: Service was not registered within timeout
mar 18 17:45:55 micron plasma_waitforname[76183]: org.kde.knotifications: WaitForName: Service was not registered within timeout

seth · 2024-03-18 18:42:40

-rw-r--r-- 1 root root 114 mar 13 12:11 org.kde.plasma.Notifications.service

What if you move that somewhere_else™?
Also please post its content.

Pena · 2024-03-18 19:34:09

Good news,
it just werks™

Although whenever i try to force dunst to display something it results in

CRITICAL: [dbus_cb_name_lost:1175] Cannot acquire 'org.freedesktop.Notifications': Name is acquired by 'dunst' with PID '2837'.

this however shouldn't be a real problem and is likely they just changed the codebase or i have suffered some kind of mandela effect
notify-send however makes dunst work like a charm

Inside that file

[D-BUS Service]
Name=org.freedesktop.Notifications
Exec=/usr/bin/plasma_waitforname org.freedesktop.Notifications

it is compliant with other output thats been sent.
I should really learn how dbus operates and stuff revolving around it

Edit: fix semantics, im tired and phrases are just getting mumbled

Last edited by Pena (2024-03-18 19:35:09)

Pena · 2024-03-18 19:37:10

Although all the issues haven't really been solved since this seems to be largely due to plasma and kde, and dunst is working ill close it to avoid necroposting

seth · 2024-03-18 22:22:37

CRITICAL: [dbus_cb_name_lost:1175] Cannot acquire 'org.freedesktop.Notifications': Name is acquired by 'dunst' with PID '2837'.

Where does that come from (process name in the journal?) - something else still tries to become the notification server.

The KDE service should probably contain some OnlyShowIn, NotShowIn key, but you can try to override it in /etc/dbus-1/services/org.kde.plasma.Notifications.service

[D-BUS Service]
Name=org.freedesktop.Not
Exec=/usr/bin/false

Pena · 2024-03-19 16:13:59

Oh seth, i guess i forgot to be more verbose
but my guess would be that a new instance of dunst would try to vecome the notification server

the command used would be something like

dunst "some message"

seth · 2024-03-19 17:23:55

No, I meant the process that issues

CRITICAL: [dbus_cb_name_lost:1175] Cannot acquire 'org.freedesktop.Notifications': Name is acquired by 'dunst' with PID '2837'.

To talk to dunst you'd use "dunstify" or "notify-send".
If you actually tried to start a new dunst instance (the command in #22) that'd certainly cause the error, though.

Pena · 2024-03-21 00:30:47

I was unaware of dusntify maybe it was the original comand i was trying to do however i was already aware of notify send(after all it was the command i used to test it)

and yes that was what i was saying in 22, regardless ill just paru regularly and hope yakuake fix itself if not in some months ill open a new issue here

Arch Linux

#1 2024-03-12 19:28:40

[SOLVED]A lot of different services relating to dbus-broker are failin

#2 2024-03-12 20:13:41

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#3 2024-03-12 20:19:51

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#4 2024-03-12 20:36:00

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#5 2024-03-12 21:08:24

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#6 2024-03-12 21:10:36

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#7 2024-03-13 16:03:47

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#8 2024-03-13 16:15:30

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#9 2024-03-13 17:28:21

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#10 2024-03-13 18:08:39

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#11 2024-03-13 22:01:58

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#12 2024-03-13 22:24:42

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#13 2024-03-14 13:58:26

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#14 2024-03-14 15:17:38

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#15 2024-03-14 20:55:14

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#16 2024-03-14 21:47:16

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#17 2024-03-18 18:02:00

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#18 2024-03-18 18:42:40

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#19 2024-03-18 19:34:09

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#20 2024-03-18 19:37:10

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#21 2024-03-18 22:22:37

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#22 2024-03-19 16:13:59

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#23 2024-03-19 17:23:55

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

#24 2024-03-21 00:30:47

Re: [SOLVED]A lot of different services relating to dbus-broker are failin

Board footer