https://bugzilla.novell.com/show_bug.cgi?id=283914 ------- Comment #8 from werner@novell.com 2007-06-14 04:25 MST ------- Beside this a `killall -15 xv' does not help after the SIGQUIT. The xv process is deadlocked. An "strace -f -p `pidof xv`" shows during the "killall -3 xv" the following: 18042 select(4, [3], [], NULL, NULL) = ? ERESTARTNOHAND (To be restarted) 18042 --- SIGQUIT (Quit) @ 0 (0) --- 18042 select(4, [3], [3], NULL, NULL) = 1 (out [3]) 18042 writev(3, [{"\224\10\7\0\0\1\7\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 28}], 1) = 28 seems that writing on the socket is brocken, that is that the socket is closed without confirmation and further writing will block xv. On 10.2 the socket is not closed and therefore the xv can use write(v) on the socket. Note, that xv uses SIGQUIT to relaod images, but libxcb on STABLE ignores the signal handler used by xv. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.