- Package:
- xserver-xorg-core
- Source:
- xorg-server
- Description:
- Xorg X server - core server
- Submitter:
- Trek
- Date:
- 2022-03-04 07:57:03 UTC
- Severity:
- normal
- Tags:
Dear maintainer, after the security upgrade from 2:1.16.4-1 to 2:1.16.4-1+deb8u1, I got flooded by dbus messages (which is not installed) every 10 seconds (EE) dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory) can you revert to the previous configuration where libdbus is not linked in? thanks!
with the latest update, the dbus dependency is gone and the error message is no more printed to the log thank you!
Control: reopen -1 Control: found -1 2:1.19.2-1+deb9u1 > Version: 2:1.16.4-1+deb8u1+b1 > with the latest update, the dbus dependency is gone and the error > message is no more printed to the log > thank you! I’m observing the same issue on Stretch (2:1.19.2-1+deb9u1.) I guess that the fix for Debian Bug#867492 (per DSA-3905-1) affected Stretch just as well. Could this please be rectified? TIA.
>> Version: 2:1.16.4-1+deb8u1+b1
>> with the latest update, the dbus dependency is gone and the error
>> message is no more printed to the log
> I’m observing the same issue on Stretch (2:1.19.2-1+deb9u1.)
[…]
Any progress on this one?
(I guess it’s the same bug as [1], reported over a year ago.)
[1] https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1562610
Bug #1562610 “/var/log/Xorg.0.log gets flooded with “(EE) dbus-…”
Curiously, while the Debian changelog indicates that
libdbus-1-dev became a build dependency back in 2:1.3.99.0-1
(2007), I don’t recall ever observing this specific issue.
Sure, it’s only 191 octets every 10 seconds, but in a month,
that easily becomes over 40 MiB:
Hi Ivan Shmakov, I tried your fix with the perl script. It opens a socket and appears to be listening, but does not close the connection (the message in Xorg.0.log says NoReply instead of FileNotFound). Am I missing the MIMEd Perl server? How to install it? Thanks, Roy
The bot is wrong, it's not "fixed-upstream". Upstream closed the issue without any resolution.