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 448590 - crash in Image Viewer:
crash in Image Viewer:
Status: RESOLVED DUPLICATE of bug 441466
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-17 20:53 UTC by Michael Schönitzer
Modified: 2007-06-17 21:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Michael Schönitzer 2007-06-17 20:53:29 UTC 
Version: 2.18.2

What were you doing when the application crashed?



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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 163930112 vsize: 163930112 resident: 69861376 share: 33759232 rss: 69861376 rss_rlim: 4294967295
CPU usage: start_time: 1182112945 rtime: 1150 utime: 924 stime: 226 cutime:0 cstime: 3 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 -1208838432 (LWP 10092)]
[New Thread -1319421040 (LWP 10095)]
[New Thread -1211225200 (LWP 10094)]
(no debugging symbols found)
0x00d6d402 in __kernel_vsyscall ()

+ Trace 141730

Thread 1 (Thread -1208838432 (LWP 10092))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 eog_image_cache_add
  • #5 ??
  • #6 eog_job_call_finished
  • #7 ??
  • #8 g_cclosure_marshal_VOID__VOID
    from /lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #10 g_cclosure_marshal_VOID__VOID
    from /lib/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #12 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
Fenstermanager-Warnung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x5000003 (Als JPEG s)
Fenstermanager-Warnung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
** Message: drive = 0
** Message: volume = 0
** Message: Failed to close thumbnail pixbuf loader for /home/michi/Bilder/digi/2007/Sonnenblume/hpim3122b.jpg: Fehler beim Lesen einer JPEG-Bilddatei (Improper call to JPEG library in state 201)
** Message: Failed to close thumbnail pixbuf loader for /home/michi/Bilder/digi/2007/Sonnenblume/hpim3122b.jpg: Fehler beim Lesen einer JPEG-Bilddatei (Improper call to JPEG library in state 201)
warning: the debug information found in "/usr/lib/debug//usr/lib/gnome-vfs-2.0/modules/libfile.so.debug" does not match "/usr/lib/gnome-vfs-2.0/modules/libfile.so" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-jpeg.so.debug" does not match "/usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-jpeg.so" (CRC mis
warning: the debug information found in "/usr/lib/debug//usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so.debug" does not match "/usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so" (CRC misma
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-06-17 21:30:52 UTC 
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 441466 ***