Description of problem: Ristretto often gets into a non responsive mode while viewing images in KDE. The image simply shakes within the viewing region and the process needs to be killed by kde. I have seen this behaviour with jpg images, but the effect is not necessarily dependent on particular images (?) Apparently it is GDK related. Version-Release number of selected component (if applicable): 0.0.22 How reproducible: use ristretto to open a folder full of jpg images in KDE Steps to Reproduce: 1. 2. 3. Actual results: when run from CLI this is the output ** (ristretto:12176): DEBUG: xfdesktop is not running (ristretto:12176): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed Killed Expected results: Additional info:I am attaching strace output. Importantly there was a segmentation fault before the effect.
Thanks for your bug report, but where is the strace? If you have problems, please look at http://fedoraproject.org/wiki/StackTraces
Created attachment 355213 [details] strace of ristretto in KDE strace
Sorry, I thought I had uploaded it last time. The file should be 40.9 MB after decompression
Sorry, but the strace is not that useful, especially when you have to dig though 40 M of text. Can you please give me a proper gdb stracktrace with the correct debuginfo installed? If you are running into problems, take a look at the wiki page I mentioned in comment #1.
Task : open a folder of animated gif wall papers (without play) ______________________________________________ $ gdb ristretto GNU gdb (GDB) Fedora (6.8.50.20090302-33.fc11) This GDB was configured as "x86_64-redhat-linux-gnu". (gdb) run Starting program: /usr/bin/ristretto [Thread debugging using libthread_db enabled] ** (ristretto:17118): DEBUG: xfdesktop is not running [New Thread 0x7fffefd77910 (LWP 17121)] [New Thread 0x7fffef376910 (LWP 17123)] [Thread 0x7fffefd77910 (LWP 17121) exited] [New Thread 0x7fffefd77910 (LWP 17125)] [Thread 0x7fffefd77910 (LWP 17125) exited] (ristretto:17118): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed (ristretto:17118): GdkPixbuf-CRITICAL **: gdk_pixbuf_copy: assertion `GDK_IS_PIXBUF (pixbuf)' failed Program received signal SIGSEGV, Segmentation fault. 0x00000035be60613e in IA__gdk_pixbuf_copy (pixbuf=0x96ced0) at gdk-pixbuf.c:294 294 g_return_val_if_fail (GDK_IS_PIXBUF (pixbuf), NULL); (gdb) bt #0 0x00000035be60613e in IA__gdk_pixbuf_copy (pixbuf=0x96ced0) at gdk-pixbuf.c:294 #1 0x000000000040f21a in cb_rstto_navigator_entry_update_image (entry=0xa5e660) at navigator.c:1372 #2 0x00000035bce381cb in g_timeout_dispatch (source=0x9a9d50, callback=0, user_data=0x700000008) at gmain.c:3260 #3 0x00000035bce37abe in g_main_dispatch (context=<value optimized out>) at gmain.c:1824 #4 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2377 #5 0x00000035bce3b278 in g_main_context_iterate (context=0x6552b0, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2455 #6 0x00000035bce3b6d5 in IA__g_main_loop_run (loop=0x6a6d90) at gmain.c:2663 #7 0x00000035c03279c7 in IA__gtk_main () at gtkmain.c:1205 #8 0x0000000000408d37 in main (argc=1, argv=0x7fffffffdfb8) at main.c:342 (gdb) quit The program is running. Quit anyway (and kill it)? (y or n) ________________________________________________________________ _____________________________________________________________________________ Ristretto terminated by KDE crash handler ______________________________________________ On another occasion it did not crash, but while viewing any particular picture, earlier pictures would start flashing.
Created attachment 355485 [details] gdb thread apply all bt
crash report attached same context, but #gdb thread apply all bt
Thanks a lot, this looks much more useful. Bug filed upstream as http://bugzilla.xfce.org/show_bug.cgi?id=5629
Please try the package from http://koji.fedoraproject.org/koji/taskinfo?taskID=1721311 and tell me if the problem still occurs.
Did you try the packages? I had to move them to http://cwickert.fedorapeople.org/temp/ in order to rescue them from being deleted. Please test them.
Does not seem to happen on F12 X86-64 with the packages. I had to force the install because of conflict with a similar version of ristretto
(In reply to comment #11) > Does not seem to happen on F12 X86-64 with the packages. What packages? The one from the repo or the one from fedorapeople.org? > I had to force the install because of conflict with a similar version of > ristretto There is no similar Version on Fedora 12, only 0.0.22-2.fc12, but not 0.0.22-2.fc12.1. These are to be found at http://koji.fedoraproject.org/koji/taskinfo?taskID=1730423
I forced the install of 0.0.22-2.fc12.1 over 0.0.22-2.fc12 Checked with 0.0.22-2.fc12.1 on two folders with many jpgs.
(In reply to comment #13) > I forced the install of 0.0.22-2.fc12.1 over 0.0.22-2.fc12 0.0.22-2.fc12.1 is greater than 0.0.22-2.fc12, so no need to force anything. Are you sure you used rpm -U rather than rpm -i? > Checked with 0.0.22-2.fc12.1 on two folders with many jpgs. Do you still have the possibility to test on F11?
Yes I used rpm -Uvh initially and then rpm --force -i My F11 install is a stable one
Ok, then please make sure you only have one version of ristretto installed and try to reproduce the error on F11. TIA.
Any chance to - try to reproduce the bug on F11 - test the updated packages from comment #10?
As I cannot reproduce this bug and don't get the required feedback, I'm going to close this report now. Feel free to reopen if it bites you again. Thanks for your report.