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 588559 - crash in Image Viewer: I was viewing images in ...
crash in Image Viewer: I was viewing images in ...
Status: RESOLVED DUPLICATE of bug 583448
Product: eog
Classification: Core
Component: general
2.26.x
Other All
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-07-14 16:53 UTC by Jonathon Jongsma
Modified: 2009-07-14 17:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Jonathon Jongsma 2009-07-14 16:53:18 UTC
Version: 2.26.2

What were you doing when the application crashed?
I was viewing images in a directory while more images were being downloaded to that directory.  At the moment of the crash, I had just pressed the right-arrow to view the next image.  It's quite possible that the next image was only partially downloaded at the time that it was loaded.  So, in essence the image that it was trying to load was 'corrupt'.  Iit would be nice if eog could just display a warning about a corrupted image rather than crashing.


Distribution: Debian squeeze/sid
Gnome Release: 2.26.1 2009-04-14 (Debian)
BugBuddy Version: 2.26.0

System: Linux 2.6.30-1-amd64 #1 SMP Wed Jul 8 12:20:34 UTC 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10601901
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 326213632 vsize: 326213632 resident: 33718272 share: 12783616 rss: 33718272 rss_rlim: 18446744073709551615
CPU usage: start_time: 1247590105 rtime: 98 utime: 93 stime: 5 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7fd2eee88950 (LWP 14493)]
0x00007fd2f9f9b31f in __libc_waitpid (pid=15115, stat_loc=0x7fff8eb13ab0, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c

Thread 1 (Thread 0x7fd2fa5fb7d0 (LWP 14492))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.20.4/glib/gspawn.c line 382
  • #2 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.20.4/glib/gspawn.c line 694
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 exif_data_ref
    from /usr/lib/libexif.so.12
  • #6 eog_image_get_exif_info
  • #7 ??
    from /usr/lib/eog/plugins/libstatusbar-date.so
  • #8 IA__g_closure_invoke
    at /tmp/buildd/glib2.0-2.20.4/gobject/gclosure.c line 767
  • #9 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.20.4/gobject/gsignal.c line 3317
  • #10 IA__g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.20.4/gobject/gsignal.c line 2980
  • #11 IA__g_signal_emit
    at /tmp/buildd/glib2.0-2.20.4/gobject/gsignal.c line 3037
  • #12 gtk_icon_view_select_item
    at /tmp/buildd/gtk+2.0-2.16.4/gtk/gtkiconview.c line 3519
  • #13 eog_thumb_view_select_single
  • #14 ??
  • #15 _gtk_marshal_BOOLEAN__BOXED
    at /tmp/buildd/gtk+2.0-2.16.4/gtk/gtkmarshalers.c line 84
  • #16 IA__g_closure_invoke
    at /tmp/buildd/glib2.0-2.20.4/gobject/gclosure.c line 767
  • #17 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.20.4/gobject/gsignal.c line 3285
  • #18 IA__g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.20.4/gobject/gsignal.c line 2990
  • #19 IA__g_signal_emit
    at /tmp/buildd/glib2.0-2.20.4/gobject/gsignal.c line 3037
  • #20 gtk_widget_event_internal
    at /tmp/buildd/gtk+2.0-2.16.4/gtk/gtkwidget.c line 4764
  • #21 IA__gtk_propagate_event
    at /tmp/buildd/gtk+2.0-2.16.4/gtk/gtkmain.c line 2370
  • #22 IA__gtk_main_do_event
    at /tmp/buildd/gtk+2.0-2.16.4/gtk/gtkmain.c line 1601
  • #23 gdk_event_dispatch
    at /tmp/buildd/gtk+2.0-2.16.4/gdk/x11/gdkevents-x11.c line 2367
  • #24 g_main_dispatch
    at /tmp/buildd/glib2.0-2.20.4/glib/gmain.c line 1824
  • #25 IA__g_main_context_dispatch
    at /tmp/buildd/glib2.0-2.20.4/glib/gmain.c line 2377
  • #26 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.20.4/glib/gmain.c line 2455
  • #27 IA__g_main_loop_run
    at /tmp/buildd/glib2.0-2.20.4/glib/gmain.c line 2663
  • #28 IA__gtk_main
    at /tmp/buildd/gtk+2.0-2.16.4/gtk/gtkmain.c line 1205
  • #29 main
Current language:  auto; currently asm
Current language:  auto; currently c
The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (7479 sec old) ---------------------
(epiphany-browser:7963): Gdk-WARNING **: XID collision, trouble ahead
(epiphany-browser:7963): Gdk-WARNING **: XID collision, trouble ahead
(epiphany-browser:7963): Gdk-WARNING **: XID collision, trouble ahead
(epiphany-browser:7963): Gdk-WARNING **: XID collision, trouble ahead
(epiphany-browser:7963): Gdk-WARNING **: XID collision, trouble ahead
(epiphany-browser:7963): Gdk-WARNING **: XID collision, trouble ahead
(epiphany-browser:7963): Gdk-WARNING **: XID collision, trouble ahead
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Jonathon Jongsma 2009-07-14 16:57:31 UTC
OK, I just reproduced it again after all of the images had finished downloading.  So it does not seem to be related to partially-downloaded or incomplete images.  in fact, the image loaded fine (including metadata), but then I pressed left-arrow, and then right-arrow to return to the original image and I got the crash again.
Comment 2 Claudio Saavedra 2009-07-14 17:04:28 UTC
This looks like 583448. If you disable the statusbar metadata plugin, it should not happen.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 583448 ***