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 509668 - eog crashed with SIGSEGV in g_type_check_is_value_type()
eog crashed with SIGSEGV in g_type_check_is_value_type()
Status: RESOLVED DUPLICATE of bug 519910
Product: eog
Classification: Core
Component: general
2.21.x
Other Linux
: Normal critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-15 15:17 UTC by Pedro Villavicencio
Modified: 2008-03-03 16:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Pedro Villavicencio 2008-01-15 15:17:23 UTC 
This bug has been reported here:

https://bugs.launchpad.net/ubuntu/+source/eog/+bug/182511

"What I did:
 - open a zip archive with Archive Manager
 - select an image in it and click. Eog will open the image.
 - close the Archive Manager
 - click minimize button on the Eog window.
 - application crashed.

Unfortunately I couldn't reproduce it this way. So, I don't know if these actions caused the crash. I hope that attached logs will help though"

".

+ Trace 185445

Thread 1 (process 14689)

  • #0 update_image_pos
    at eog-window.c line 632
  • #1 eog_window_list_store_image_removed
    at eog-window.c line 4655
  • #2 IA__g_cclosure_marshal_VOID__BOXED
    at /build/buildd/glib2.0-2.15.1/gobject/gmarshal.c line 566
  • #3 IA__g_closure_invoke
    at /build/buildd/glib2.0-2.15.1/gobject/gclosure.c line 490
  • #4 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.15.1/gobject/gsignal.c line 2440
  • #5 IA__g_signal_emit_valist
    at /build/buildd/glib2.0-2.15.1/gobject/gsignal.c line 2199
  • #6 IA__g_signal_emit
    at /build/buildd/glib2.0-2.15.1/gobject/gsignal.c line 2243
  • #7 IA__gtk_tree_model_row_deleted
    at /build/buildd/gtk+2.0-2.12.3/gtk/gtktreemodel.c line 1537
  • #8 IA__gtk_list_store_remove
    at /build/buildd/gtk+2.0-2.12.3/gtk/gtkliststore.c line 969
  • #9 eog_list_store_remove
    at eog-list-store.c line 335
  • #10 vfs_monitor_dir_cb
    at eog-list-store.c line 413
  • #11 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
    from /usr/lib/libglib-2.0.so.0
  • #20 ??
    from /lib/tls/i686/cmov/libpthread.so.0
  • #21 main_context_list
    from /usr/lib/libglib-2.0.so.0
  • #22 ??
  • #23 ??
    from /usr/lib/libglib-2.0.so.0
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 g_idle_dispatch
    at /build/buildd/glib2.0-2.15.1/glib/gmain.c line 4142 
Backtrace stopped: frame did not save the PC"
Comment 1 Claudio Saavedra 2008-01-15 15:53:15 UTC 
I am unable to reproduce it with 2.21.4. Though there are some minor issues with eog when the image is deleted by file-roller (the application icon, title, and image information in the status bar remains as if the image still were open).

Could you guys test if this is reproducible for you with 2.21.3 and 2.21.4?
Comment 2 Pedro Villavicencio 2008-01-16 11:41:00 UTC 
eog 2.21.4 just landed into Hardy. I'll ask to the reporter and let you know, thanks Claudio.
Comment 3 Pedro Villavicencio 2008-02-13 18:24:23 UTC 
reporter confirmed that the bug is fixed with latest package, thanks!.
Comment 4 Pedro Villavicencio 2008-02-25 17:55:23 UTC 
It seems to be still an issue with eog 2.21.90: https://bugs.edge.launchpad.net/ubuntu/+source/eog/+bug/195236
Comment 5 Felix Riemann 2008-03-03 16:24:50 UTC 
The trace indicates that this is the same as bug 519910 except that here the removal of an image triggers it. This should be caught by the fix for bug 519910 as well.

Please reopen if I was wrong. :-)
----------------------------------------------------------------------------------
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 ***