After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 449285 - crash in Image Viewer: Rotaring CCW
crash in Image Viewer: Rotaring CCW
Status: RESOLVED DUPLICATE of bug 394888
Product: eog
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-19 21:41 UTC by tomm
Modified: 2007-06-25 17:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description tomm 2007-06-19 21:41:47 UTC
Version: 2.18.2

What were you doing when the application crashed?
Rotaring CCW


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Fedora

Memory status: size: 71811072 vsize: 71811072 resident: 25063424 share: 20471808 rss: 25063424 rss_rlim: 4294967295
CPU usage: start_time: 1182289245 rtime: 108 utime: 97 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/eog'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208514848 (LWP 4562)]
[New Thread -1243006064 (LWP 4566)]
[New Thread -1210614896 (LWP 4565)]
(no debugging symbols found)
0x00129402 in __kernel_vsyscall ()

Thread 3 (Thread -1210614896 (LWP 4565))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 ??
  • #11 ??
  • #12 eog_job_call_action
  • #13 ??
  • #14 ??
    from /lib/libglib-2.0.so.0
  • #15 start_thread
    from /lib/libpthread.so.0
  • #16 clone
    from /lib/libc.so.6


----------- .xsession-errors (16 sec old) ---------------------
Error: Document has not the mandatory ending %EOF
Error: Document has not the mandatory ending %EOF
Error: Document has not the mandatory ending %EOF
Error: Document has not the mandatory ending %EOF
Error: Document has not the mandatory ending %EOF
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00067 (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3200003 (Export Fil)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3200003 (Export Fil)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
** ERROR **: file eog-window.c: line 1415 (job_save_handle_error): should not be reached
aborting...
Xlib: unexpected async reply (sequence 0x16a1)!
--------------------------------------------------
Comment 1 Felix Riemann 2007-06-25 17:24:43 UTC
Although the trace has holes I would say this is a duplicate of bug 394888 based on this log message:

** ERROR **: file eog-window.c: line 1415 (job_save_handle_error): should not
be reached


----
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 394888 ***