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 317194 - EOG crash when trying to open a jpeg file over a mounted USB drive
EOG crash when trying to open a jpeg file over a mounted USB drive
Status: RESOLVED OBSOLETE
Product: eog
Classification: Core
Component: image viewer
2.12.x
Other All
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
: 356705 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-09-26 00:25 UTC by Roshan Kamath
Modified: 2007-03-18 03:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Attachments
Test case .jpg image (probably not useful) (978.14 KB, image/jpeg)
2005-09-26 00:29 UTC, Roshan Kamath
Details

Description Roshan Kamath 2005-09-26 00:25:19 UTC
Steps to reproduce:
This crash happened only 'once' - and I couldn't reproduce it again after
remounting my drive. Anyway, this is the sequence of steps I had followed before
the crash happened. I've pasted two bug-buddy stack traces for more details.

1. Mount a Compact Flash card as a generic USB drive.
2. Open the mounted location in Nautilus. 
3. Open the 'offending' image from that card (default app is EOG)
4. EOG viewer crashed an instant after displaying the image.

Stack trace:
Distribution: Fedora Core release 4 (Stentz)
Package: EOG
Severity: Normal
Version: GNOME2.12.0 2.12.0
Gnome-Distributor: Red Hat, Inc
Synopsis: EOG crash when trying to open a jpeg file over a mounted USB drive
Bugzilla-Product: EOG
Bugzilla-Component: general
Bugzilla-Version: 2.12.0
BugBuddy-GnomeVersion: 2.0 (2.12.0)

Debugging Information:


==== Stack Trace from First Attempt =====

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)
`shared object read from target memory' has disappeared; keeping its
symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208101200 (LWP 2699)]
[New Thread -1250309200 (LWP 2813)]
[New Thread -1210332240 (LWP 2710)]
0x00579402 in __kernel_vsyscall ()

Thread 2 (Thread -1250309200 (LWP 2813))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_module_info_get
    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 /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 eog_collection_item_get_type
  • #11 eog_job_call_action
  • #12 eog_image_list_iter_equal
  • #13 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #14 start_thread
    from /lib/libpthread.so.0
  • #15 clone
    from /lib/libc.so.6

Other information:
Incidentally, I had noticed that Nautilus had also failed to generate the
thumbnail for the image. So it points to a core problem somewhere outside of
EOG. However, I'm still raising this bug in the hope that it can be forwarded
upstream, if required, after adequate analysis.

I'm running a 2.6.13-1.1553_FC5smp kernel (selinux disabled), glibc-2.3.90-12
, glib-1.2.10-16 from the Fedora yum repos.
Comment 1 Roshan Kamath 2005-09-26 00:29:52 UTC
Created attachment 52647 [details]
Test case .jpg image (probably not useful)

I've attached the image that was causing EOG to crash. However, I think it is
probably not useful since I was unable to reproduce the crash after unmounting
and then remounting the compact flash as a USB drive.
Comment 2 Christian Kirbach 2005-11-25 21:48:30 UTC
Thanks for reporting.
This should be fixed in Gnome 2.12.2 (and newer releases).
If not, please reopen Bug #311925

*** This bug has been marked as a duplicate of 311925 ***
Comment 3 Claudio Saavedra 2006-09-21 18:00:50 UTC
*** Bug 356705 has been marked as a duplicate of this bug. ***
Comment 4 Claudio Saavedra 2006-09-21 18:04:38 UTC
I have my doubts about this bug being a duplicated of bug #311925. According with simple duplicated finder[1], it is not. After checking the stacktraces, I think it is not the case.

I will reopen it, as there are some bug reports that are duplicated of this one, and not of bug #311925.

[1] http://bugzilla.gnome.org/dupfinder/simple-dup-finder.cgi?id=311925
Comment 5 Claudio Saavedra 2007-03-18 03:25:09 UTC
Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.