GNOME Bugzilla – Bug 367788
crash in Image Viewer:
Last modified: 2007-09-08 01:52:59 UTC
Version: 2.16.1 What were you doing when the application crashed? Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 93011968 vsize: 0 resident: 93011968 share: 0 rss: 20099072 rss_rlim: 0 CPU usage: start_time: 1162228896 rtime: 0 utime: 132 stime: 0 cutime:128 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/eog' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226000192 (LWP 19966)] [New Thread -1269048416 (LWP 19968)] [New Thread -1226855520 (LWP 19967)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 80543
Thread 3 (Thread -1226855520 (LWP 19967))
*** Bug 368746 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please add a brief description of how to reproduce this bug. You'll also need to add a stack trace; please see http://live.gnome.org/GettingTraces for more information about how to do so. Thanks in advance! please install the gtk+ package
*** Bug 371220 has been marked as a duplicate of this bug. ***
*** Bug 377367 has been marked as a duplicate of this bug. ***
*** Bug 380927 has been marked as a duplicate of this bug. ***
*** Bug 385043 has been marked as a duplicate of this bug. ***
It would be very nice if people who see this could reproduce it with an eog started from a terminal and report the warning that it spews at the time of the crash back here.
*** Bug 385947 has been marked as a duplicate of this bug. ***
*** Bug 389112 has been marked as a duplicate of this bug. ***
*** Bug 389423 has been marked as a duplicate of this bug. ***
*** Bug 391788 has been marked as a duplicate of this bug. ***
*** Bug 393453 has been marked as a duplicate of this bug. ***
*** Bug 394998 has been marked as a duplicate of this bug. ***
*** Bug 394121 has been marked as a duplicate of this bug. ***
I have supplied a description and stack trace on my duplicate bug http://bugzilla.gnome.org/show_bug.cgi?id=394121 I crash happens after rotating and saving the file, it just seg faults. let me know what other information you need, here is the beginning of the stack trace fyi, for the full trace refer my duplicate. Cheers Brin Gdk-ERROR **: file gdkregion-generic.c: line 1082 (miUnionNonO): assertion failed: (y1 < y2) aborting... Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1260078176 (LWP 14957)] 0xb7904bdf in gdk_rectangle_union () from /usr/lib/libgdk-x11-2.0.so.0
thank you brinley. Claudio, if you see traces with debug symbols, please copy the relevant parts. We are still missing some debug info here, altough "y1 < y2" provides the crucial hint why gdk_region_get_rectangles () fails. If someone could please install the gtk+ debug package package
+ Trace 102798
Thread 1 (Thread -1226389312 (LWP 14929))
Does anyone know where i can get the libgtk2.0-*-dbgsym_2.10.6-0ubuntu3_i386.ddeb from? As http://people.ubuntu.com/~pitti/ddebs only has version *ubuntu1* (not ubuntu3) I assume this is the correct dbgsym for gtk2+ Regards Brin
*** Bug 400408 has been marked as a duplicate of this bug. ***
Created attachment 81138 [details] screenshot of the offending dialog I tried to reproduce this bug but I just can't trigger the crash. However, it calls my attention that the dialog is drawn in a strange way. Over the frame, there is a dirty region. I attach a screenshot here. HTH
This is Similar to what i get when it crashes, It crashes for me after a rotation to a portrait and saving. I'm not sure if its a leftover portrait your seeing behind your preview? For me it only draws about 3/4 of the preview on the dialog box, other times the dialog box is just all grey when it crashes. I'll try and grab a screenshot. Brin
*** Bug 404549 has been marked as a duplicate of this bug. ***
*** Bug 405112 has been marked as a duplicate of this bug. ***
*** Bug 407032 has been marked as a duplicate of this bug. ***
*** Bug 408483 has been marked as a duplicate of this bug. ***
*** Bug 411084 has been marked as a duplicate of this bug. ***
*** Bug 416225 has been marked as a duplicate of this bug. ***
I am not sure, but maybe the stack trace in bug 382961 is of help to you. It features additional debugging information. Although the cause of it is apparently not the same dialog as in this bug but it is crashing at the same assertion after invalidating a display region.
*** Bug 417947 has been marked as a duplicate of this bug. ***
Uhm, sorry I actually meant bug 382691 in comment 27.
all duplicates are are for eog 2.16 thanks Felix, it certainly crashes on the exact line in the exact file on precisely the same expression, hence I strongly assume this is a duplicate. the other report has a superb trace and developer comments, so marking this report a duplicate of the other. *** This bug has been marked as a duplicate of 382691 ***
(In reply to comment #30) > all duplicates are are for eog 2.16 > > thanks Felix, it certainly crashes on the exact line in the exact file on > precisely the same expression, hence I strongly assume this is a duplicate. > > the other report has a superb trace and developer comments, so marking this > report a duplicate of the other. > > > > *** This bug has been marked as a duplicate of 382691 *** Is it really a duplicate? Stacktraces look different to me.
*** Bug 419990 has been marked as a duplicate of this bug. ***
*** Bug 425119 has been marked as a duplicate of this bug. ***
*** Bug 427679 has been marked as a duplicate of this bug. ***
*** Bug 432129 has been marked as a duplicate of this bug. ***
*** Bug 436603 has been marked as a duplicate of this bug. ***
*** Bug 436445 has been marked as a duplicate of this bug. ***
*** Bug 442376 has been marked as a duplicate of this bug. ***
*** Bug 444218 has been marked as a duplicate of this bug. ***
*** Bug 444285 has been marked as a duplicate of this bug. ***
*** Bug 472716 has been marked as a duplicate of this bug. ***