GNOME Bugzilla – Bug 521637
crash in Image Viewer: open *.jpg file became t...
Last modified: 2008-03-10 19:32:18 UTC
Version: 2.20.3 What were you doing when the application crashed? open *.jpg file became this message Distribution: Solaris Express Community Edition snv_83a X86 Gnome Release: 2.20.2 2008-01-28 (Sun Microsystems, Inc.) BugBuddy Version: 2.20.1 X Vendor: Sun Microsystems, Inc. X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Murrina-LiNsta Icon Theme: Tango Memory status: size: 124588032 vsize: 124588032 resident: 39133184 share: 2977792 rss: 39133184 rss_rlim: 0 CPU usage: start_time: 0 rtime: 1316 utime: 12401809 stime: 766961 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 192000
Thread 1 (LWP 1)
Thread 6 (Thread 3 (LWP 3)): #-1 0xd1304cd5 in __pollsys () from /usr/lib/libc.so.1 No symbol table info available. Thread 5 (Thread 2 ): #-1 0xd1300c99 in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 4 (LWP 2 ): #-1 0xd1300c99 in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 3 (LWP 3 ): #-1 0xd1304cd5 in __pollsys () from /usr/lib/libc.so.1 No symbol table info available. Thread 2 (Thread 1 (LWP 1)): #-1 0xd13056d5 in __waitid () from /usr/lib/libc.so.1 No symbol table info available. Thread 1 (LWP 1 ): #-1 0xd13056d5 in __waitid () from /usr/lib/libc.so.1 No symbol table info available. #-1 0xd13056d5 in __waitid () from /usr/lib/libc.so.1 ----------- .xsession-errors (7478 sec old) --------------------- /etc/X11/gdm/Xsession: Beginning session setup... stty: : そのようなデバイスもアドレスもありません。 /etc/X11/gdm/Xsession: Setup done, will execute: /usr/dt/config/Xsession.jds --------------------------------------------------
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 version 2.22.0. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 519910 ***