You are not logged in.
Hi,
Since xfce 4.18 my systems log (on arch linux) is filled with these messages (every 10 minutes):
dbus-daemon[]: [session uid= pid=] Activating service name='org.xfce.Xfconf' requested by ':1.1215' (uid= pid= comm="xfce4-panel --display :0.0 --sm-client-id 23f7bc55")
jan 14 11:45:19 dbus-daemon[]: [session uid= pid=] Successfully activated service 'org.xfce.Xfconf'
Does anyone know why this is happening?
Thanks in advance!
Offline
This is because since 4.18, xfconfd terminates itself after 5 minutes of inactivity, whereas before it stayed running all the time. So as the panel saves its settings every 10 minutes (it was already the case before 4.18), it restarts xfconfd at that time.
Offline
Okay thanks.
This however raises another question.
Why is it smart to terminate xconfd after 5 minutes of inactivity if the panel needs it every 10 minutes?
Offline
Because of the modular nature of Xfce. Xfconf can be used for other components, without the panel necessarily being present. In fact, this was originally implemented for the use of Xfconf in a flatpak (for Ristretto). Otherwise, xfconfd kept running indefinitely after the application was closed.
Offline
Thanks!
Offline
Hello All!
Is there a way to stop this or at least suppress the logging?
My /var/log/messages files on filling up with this message, and it makes it hard to see the other entries.
-Thanks!
Last edited by patman5656 (2023-04-14 19:11:20)
Offline
I'd like to throw a quick post in here to say this is also becoming quite annoying for me; every time I want to look for something in /var/log/messages, I have to wade through masses of these messages. It would be really nice to know if there's a way to stop the log messages at least.
Specs
Software: Slackware Current x86_64, Xfce
Hardware: B550-F, 3800X, RX 6600, 32GB RAM
Offline
I believe its the dbus daemon that is generating those log entries (even though Xfconf is the generator). I can't find any info on blacklist capabilities with dbus logging.
...it makes it hard to see the other entries.
every time I want to look for something in /var/log/messages, I have to wade through masses of these messages.
For /var/log/messages, you could use something like:
cat /var/log/messages | grep -v Xfconf | more
...to be able to review the contents with the Xfconf entries filtered out.
For systemd journals, you could use the -p parameter to specify a range of priorities to display (this message being informational), so something like:
journalctl --user -p emerg..info
...to filter out informational and debug message (see: https://wiki.archlinux.org/title/System … rity_level).
I know this doesn't directly answer the question, but given that xfconf needs to operate in the this manner as discussed above and the dbus daemon doesn't appear to allow blacklisting of messages, this may be the best alternative.
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
For /var/log/messages, you could use something like:
cat /var/log/messages | grep -v Xfconf | more
...to be able to review the contents with the Xfconf entries filtered out.
Ah, thank you! I wasn't aware grep had an option to filter things out -- that works perfect for me.
Specs
Software: Slackware Current x86_64, Xfce
Hardware: B550-F, 3800X, RX 6600, 32GB RAM
Offline