dbus-monitor --session (as user)
with or without any other arguments returns (same as yesterday):
signal time=1706316157.761804 sender=org.freedesktop.DBus -> destination=:1.798 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired string ":1.798" signal time=1706316157.762037 sender=org.freedesktop.DBus -> destination=:1.798 serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost string ":1.798"
However, it doesn't really bother me at this point. After killing the process it did not return, even after hibernating and resuming.
Thanks,
Gianluca
On Sat, 27 Jan 2024, deloptes via tde-users wrote:
Gianluca Interlandi via tde-users wrote:
Not sure what this means. The error message may be related to hibernating. I hibernate using `systemctl hibernate` and when I resume the screen is not locked (which is what I prefer), but it could be that some process wants to lock it?
Yes killing the kdesktop_lock locks the screen and the process is restarted And those two messages you see are normal (the monitor also registers to the dbus)
I forgot to mention dbus-monitor --session "interface=org.freedesktop.DBus"
or dbus-monitor --session "destination=org.freedesktop.DBus"
because I forgot that this interface is also available in the user session. There are more messages to expect there - this is why I filter on interface or destination, but if you do not see anything, you could simply use one of those dbus-monitor --session or dbus-monitor --system
tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://gianluca.today/
Department of Bioengineering University of Washington, Seattle WA U.S.A. -----------------------------------------------------