https://bugzilla.novell.com/show_bug.cgi?id=283914 phdm@macqel.be changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|phdm@macqel.be | ------- Comment #2 from phdm@macqel.be 2007-06-14 01:51 MST -------
From the documentation of John Bradley's xv :
"It is occasionally desirable to reload an image file because the contents of the file have changed. For example, [...] you have a program that generates images, and you d like to view these images without any manual intervention. xv provides a way to reload an image via an external signal. If you send the xv process a SIGQUIT signal ( kill -QUIT <pid> , or kill -3 <pid> on most systems), the program will reload the currently selected file." Up to now, this used to work perfectly. In opensuse 10.3, when I do the same (i.e. kill -QUIT <xv-pid>), the `xv' process begins to use 100% cpu time instead of displaying the new image. I surmise the problem arises from the replacment of libX11 by an xcb-ified version of libX11. I even replaced libX11 by opensuse 10.2's libX11 and kill -QUIT xv works perfectly again, so that shows that the problem lies in 10.3's libX11 or in xcb. How to reproduce summary : start xv with an image file to display : xv image.jpg & send the QUIT signal to xv (this should tell xv to reread and redisplay image.jpg): killall -QUIT xv xv now uses 100% CPU time :( -- 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.