What is bizarre, is that while this SL viewer does act as a dbus server (for being sent and acting upon “SLURLs” by processing requests by other viewers or a web browser), it does so only on the session bus (not on the system bus), and only for a custom service and methods that do not involve at all upowerd. String "The name was not provided by any.
Running dbus-monitor -system, I get, when the OpenGL app is running, messages such as: method call time=1635081664.325234 sender=:1.19 -> destination= serial=21792 path=/nvidia/powerd/datapacket interface= member=AutoflDatapacketĮrror time=1635081664.325251 sender= -> destination=:1.19 error_name=.ServiceUnknown reply_serial=21792
#Blackhole driver full
With NVIDIA v495.29.05 drivers, I am seeing a big problem with weird/invalid dbus messages being sent to a dbus-enabled OpenGL software (a Second Life viewer in this case).Īfter a few minutes of running the 3D software, the /var/log/messages log fills up at an alarming rate (over 100 messages per second, leading to hundreds of MB large log files in a matter of just a few minutes) with messages such as: Oct 24 14:55:32 localhost dbus-daemon: Rejected: destination has a full message queue, 0 matched rules type="error", sender="(unset)" ((bus)) interface="(unset)" member="(unset)" error name=".ServiceUnknown" requested_reply="1" destination=":1.25" (uid=0 pid=12679 comm="./bin/cool_vl_viewer-bin")
0 kommentar(er)
