No edit summary |
|||
| Line 29: | Line 29: | ||
kill -s SIGUSER $(pidof gam_server) | kill -s SIGUSER $(pidof gam_server) | ||
* all gam_server [https://bugzilla.redhat.com/buglist.cgi?component=gamin&product=Fedora&list_id=5925423 bugs] | |||
* most long lived bug [https://bugzilla.redhat.com/show_bug.cgi?id=917848 deadlocks, leading to all KDE applications hanging] | |||
=== DBUS === | === DBUS === | ||
Revision as of 10:33, 24 September 2016
Some loose, partially undocumented, but useful debugging methods found here and there in discussions, bug comments etc.
KDE4 ()
KDE5 (F24)
kwin_x11
export KWIN_USE_INTEL_SWAP_EVENT=0 # only affects intel IGPs export KWIN_EXPLICIT_SYNC=0 # most likely candidate on nvidia GPUs export KWIN_USE_BUFFER_AGE=0 # well, you tried, but hey ... ;-) kwin_x11 --replace &
xdotool lets you programatically (or manually) simulate keyboard input and mouse activity, move and resize windows, etc. It does this using X11's XTEST extension and other Xlib functions.
For example if screen is locked
xdotool key "XF86LogGrabInfo"
dumbs all device grabs into /var/log/Xorg.0.log file. It can be run from character based consoles by prefixing it with DISPLAY=:0
gam_server
Sending a SIGUSR2 to running gam_server makes it dump its debugging information into /tmp/gamin_debug_*
kill -s SIGUSER $(pidof gam_server)
- all gam_server bugs
- most long lived bug deadlocks, leading to all KDE applications hanging
DBUS
DBUS can be followed using dbus-monitor, it can be lousy thou and hard to follow. Wireshark has dissector for dbus these days but it doesn't do that good job on it.
dbus-monitor
.xsession-errors
Users $HOME/.xsession-errors