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 536631 - crash in Image Viewer: I was opening a BMP imag...
crash in Image Viewer: I was opening a BMP imag...
Status: RESOLVED DUPLICATE of bug 536633
Product: eog
Classification: Core
Component: general
2.22.x
Other All
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-04 15:56 UTC by marco.balduzzi
Modified: 2008-06-05 12:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description marco.balduzzi 2008-06-04 15:56:39 UTC 
Version: 2.22.0

What were you doing when the application crashed?
I was opening a BMP image from an email, in Icedove..


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 36208640 vsize: 36208640 resident: 13185024 share: 9543680 rss: 13185024 rss_rlim: 4294967295
CPU usage: start_time: 1212594989 rtime: 40 utime: 32 stime: 8 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6bdb720 (LWP 28388)]
[New Thread 0xb6a28b90 (LWP 28389)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 199571

Thread 2 (Thread 0xb6a28b90 (LWP 28389))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 __kernel_vsyscall
  • #7 raise
    from /lib/i686/cmov/libc.so.6
  • #8 abort
    from /lib/i686/cmov/libc.so.6
  • #9 g_assertion_message
    from /usr/lib/libglib-2.0.so.0
  • #10 g_assertion_message_expr
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ?? 


----------- .xsession-errors (11875 sec old) ---------------------
[00000338] access_mms access warning: detected packet lost (6627705 != 6627704)
[00000338] access_mms access warning: detected packet lost (6627707 != 6627706)
[00000338] access_mms access warning: detected packet lost (6627709 != 6627708)
[00000338] access_mms access warning: detected packet lost (6627711 != 6627710)
[00000338] access_mms access warning: detected packet lost (6627713 != 6627712)
[00000338] access_mms access warning: detected packet lost (6627715 != 6627714)
[00000338] access_mms access warning: detected packet lost (6627717 != 6627716)
[00000338] access_mms access warning: detected packet lost (6627720 != 6627719)
[00000338] access_mms access warning: detected packet lost (6627722 != 6627721)
[00000338] access_mms access warning: detected packet lost (6627724 != 6627723)
[00000338] access_mms access warning: detected packet lost (6627726 != 6627725)
[00000338] access_mms access warning: detected packet lost (6627728 != 6627727)
[00000338] access_mms access warning: detected packet lost (6627730 != 6627729)
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Gianluca Borello 2008-06-05 10:45:51 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 Felix Riemann 2008-06-05 12:33:52 UTC 
This is apparently the same as bug 536633.

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