Bugzilla – Bug 724347
xorg-x11-input: X server restarts after update
Last modified: 2013-02-19 09:19:37 UTC
Created attachment 456745 [details] Xorg.0.log I have just updated to factory du jour and at the end of the zypper run, the X server suddenly restarted. # rpm -qa --last | grep ^x xorg-x11-Xvnc-7.6_1.10.4-34.2 Fri Oct 14 22:31:20 2011 xorg-x11-driver-input-7.6-40.1 Fri Oct 14 22:31:18 2011 xorg-x11-driver-video-7.6-79.1 Fri Oct 14 22:31:16 2011 xorg-x11-server-extra-7.6_1.10.4-34.2 Fri Oct 14 22:31:14 2011 xkeyboard-config-2.2.1-3.8 Fri Oct 14 22:31:11 2011 xorg-x11-server-7.6_1.10.4-34.2 Fri Oct 14 22:31:08 2011 xorg-x11-7.6-65.1 Fri Oct 14 22:31:02 2011 xorg-x11-libXt-devel-7.6_1.0.9-13.1 Fri Oct 14 22:30:59 2011 xz-5.0.3-7.1 Fri Oct 14 22:30:58 2011 xz-devel-5.0.3-7.1 Fri Oct 14 22:30:57 2011 xli-20061110-137.5 Fri Oct 14 22:30:47 2011 xinetd-2.3.14-154.5 Fri Oct 14 22:30:47 2011 xlockmore-5.34-2.3 Fri Oct 14 22:30:46 2011 xorg-x11-libXt-32bit-7.6_1.0.9-13.1 Fri Oct 14 22:30:45 2011 xorg-x11-xauth-7.6-65.1 Fri Oct 14 22:30:44 2011 xorg-x11-libXt-7.6_1.0.9-13.1 Fri Oct 14 22:30:44 2011 With rpm --scripts I checked if any of these had a whacky %restart_on_update, which turns out to be not the case. Further investigation reveals: # rpm -q --scripts xorg-x11-driver-input postinstall scriptlet (using /bin/sh): # re-plug the input devices udevadm trigger --subsystem-match=input --action=change exit 0 [...] And Xorg.0.log.old shows: [ 17472.459] (II) Unloading evdev [ 17472.463] (II) config/udev: Adding input device PS/2+USB Mouse (/dev/input/ev [ 17472.465] Backtrace:[...see attachment...] Fatal server error: [ 17472.504] Caught signal 11 (Segmentation fault). Server aborting I have a plausible explanation for myself: the (old) X server process still running tried to dlopen and load a new, incompatible evdev.so. Or could it be a dup of bug #720571?
Thanks! Good catch! udevadm might also be the trigger for the Xserver crash in bnc #723777.
Yup, that's a clear dup of bnc #723777. Thanks for providing the right hint on how to trigger this! I was unable to reproduce this on my system but with your hint and many tries I eventually found it. *** This bug has been marked as a duplicate of bug 723777 ***