GNOME Bugzilla – Bug 518015
crash in Image Viewer: Downloading an image, th...
Last modified: 2008-03-05 19:29:27 UTC
Version: 2.20.3 What were you doing when the application crashed? Downloading an image, though I'm not quite sure. Distribution: Solaris Express Community Edition snv_82 X86 Gnome Release: 2.20.2 2008-01-15 (Sun Microsystems, Inc.) BugBuddy Version: 2.20.1 X Vendor: Sun Microsystems, Inc. X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: blueprint Memory status: size: 129093632 vsize: 129093632 resident: 50454528 share: 786432 rss: 50454528 rss_rlim: 0 CPU usage: start_time: 0 rtime: 507 utime: 4858773 stime: 217804 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/eog' (no debugging symbols found) sol-thread active. Retry #1: Retry #2: Retry #3: Retry #4: [New LWP 1 ] [New Thread 1 (LWP 1)]
+ Trace 190056
Thread 1 (LWP 1)
Thread 6 (Thread 3 (LWP 3)): #-1 0xfef03555 in __pollsys () from /lib/libc.so.1 No symbol table info available. Thread 5 (Thread 2 ): #-1 0xfeeff509 in __lwp_park () from /lib/libc.so.1 No symbol table info available. Thread 4 (LWP 2 ): #-1 0xfeeff509 in __lwp_park () from /lib/libc.so.1 No symbol table info available. Thread 3 (LWP 3 ): #-1 0xfef03555 in __pollsys () from /lib/libc.so.1 No symbol table info available. Thread 2 (Thread 1 (LWP 1)): #-1 0xfef03f35 in _waitid () from /lib/libc.so.1 No symbol table info available. Thread 1 (LWP 1 ): #-1 0xfef03f35 in _waitid () from /lib/libc.so.1 No symbol table info available. #-1 0xfef03f35 in _waitid () from /lib/libc.so.1 ----------- .xsession-errors (15160 sec old) --------------------- couldn't set locale correctly couldn't set locale correctly /etc/X11/gdm/Xsession: Beginning session setup... /etc/X11/gdm/Xsession: Setup done, will execute: /usr/dt/config/Xsession.jds --------------------------------------------------
The actual problem seems to be the same as bug 519910 or bug 509668 (depending on whether a file was added or removed) if I go by the stacktrace. A fix for this will ship with EOG 2.22.0 next week. That it is actually crashing in g_log instead here seems to be a problem or at least specialty of Solaris (see bug 488564). Please reopen this bug if you can reproduce it with EOG 2.22 (once it is released). ---------------------------------------------------------------------------------- Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 519910 ***