You are not logged in.
- Topics: Active | Unanswered
#1 2025-10-05 10:56:02
- archiee25
- Member
- Registered: 2025-10-05
- Posts: 2
Issue with programs dealing with dbus after yesterday update
Hi everyone, I am kinda new to archlinux, used to use EOS but after switching I can't get help from those folks
After yesterday update , on start up I am having issues with starting dusnt,copyq and thunar
and all seems to be connected with they can't get the dbus name (the DNS like naming it uses) properly.
If I kill the dunst process with -9 and relaunch it it kinda works. but still could not figure out how to fix thunar. if use them in a fresh boot they they read from stdin and do nothing.
Offline
#2 2025-10-05 13:38:27
- seth
- Member
- From: Don't DM me only for attention
- Registered: 2012-09-03
- Posts: 68,770
Re: Issue with programs dealing with dbus after yesterday update
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Post the actual errors you get.
On a limb:
hostnamectlOffline
#3 2025-10-05 16:06:02
- archiee25
- Member
- Registered: 2025-10-05
- Posts: 2
Re: Issue with programs dealing with dbus after yesterday update
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Post the actual errors you get.On a limb:
hostnamectl
Sorry if not doing it based on rules, as I said I am new this forum and used to rules of EOS forums.
I have to take screenshots as copyq program sends some errors that showup as desktop notifications on startup.
I will send them when get home. But the issue should be from the update. I have my dotfiles as git and don't made any changes to the system other than running a `pacman -Syu`.
Offline
#4 2025-10-05 19:07:27
- seth
- Member
- From: Don't DM me only for attention
- Registered: 2012-09-03
- Posts: 68,770
Re: Issue with programs dealing with dbus after yesterday update
This isn't about board rules - nobody would be able to make an informed comment about the situation w/o some actual data.
If I kill the dunst process with -9 and relaunch it it kinda works.
The critical element would thus be the dunst process, the hostnamectl command will show whether you've a static hostname, otherwise the hostname change after dunst has started might be an issue.
An alternative problem could be a broken session bus (notably if you're using xinit, see the last link below) and in general, post any errors you get (if so) when starting dunst.
Offline