FS#73503 - [nvidia-dkms] PLEASE ENTER SUMMARY
Attached to Project:
Arch Linux
Opened by Eric Blau (eblau) - Tuesday, 25 January 2022, 21:30 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 26 January 2022, 08:01 GMT
Opened by Eric Blau (eblau) - Tuesday, 25 January 2022, 21:30 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 26 January 2022, 08:01 GMT
|
Details
Description: After running for some time, I get a HUGE
amount of dbus spam in the systemd journal:
Jan 25 16:22:36 eric-thinkpad-home dbus-daemon[1433]: [system] Rejected: destination has a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus)) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1" destination=":1.107861" (uid=1000 pid=347480 comm="/opt/zoom/zoom zoommtg://nutanix.zoom.us/join?acti") Jan 25 16:22:36 eric-thinkpad-home dbus-daemon[1433]: [system] Rejected: destination has a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus)) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1" destination=":1.107861" (uid=1000 pid=347480 comm="/opt/zoom/zoom zoommtg://nutanix.zoom.us/join?acti") Jan 25 16:22:36 eric-thinkpad-home dbus-daemon[1433]: [system] Rejected: destination has a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus)) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1" destination=":1.107861" (uid=1000 pid=347480 comm="/opt/zoom/zoom zoommtg://nutanix.zoom.us/join?acti") ... The issue is discussed in this upstream thread: https://forums.developer.nvidia.com/t/bug-nvidia-v495-29-05-driver-spamming-dbus-enabled-applications-with-invalid-messages/192892?u=rangelalvarado1 The workaround in that thread to create a fake systemd service that executes a dbus command to black-hole the messages does work: /usr/bin/dbus-test-tool black-hole --system --name=nvidia.powerd.server The upstream thread indicates that Gentoo picked up some upstream patch to fix the issue. It does not appear to be fixed in any 495.xx upstream release. Additional info: * package version(s): 495.46-2 Steps to reproduce: Not sure of the exact steps but after using my laptop for several hours, if I run "journalctl -f" in a window, I notice this spam occurring. |
This task depends upon
Closed by Antonio Rojas (arojas)
Wednesday, 26 January 2022, 08:01 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#72903
Wednesday, 26 January 2022, 08:01 GMT
Reason for closing: Duplicate
Additional comments about closing:
Comment by Eric Blau (eblau) -
Tuesday, 25 January 2022, 21:33 GMT
Sorry, I forgot to fill in the summary field and doesn't look like
I can change it now.