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 520712 - crash in Image Viewer: I ran "eog filename.png"...
crash in Image Viewer: I ran "eog filename.png"...
Status: RESOLVED DUPLICATE of bug 500203
Product: eog
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-06 10:51 UTC by Adam Powell
Modified: 2008-03-06 11:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Adam Powell 2008-03-06 10:51:38 UTC 
Version: 2.20.4

What were you doing when the application crashed?
I ran "eog filename.png" and it crashed.  Error message:

EOG-ERROR **: file eog-util.c: line 301 (eog_util_dot_dir): assertion failed: (exists)
aborting...

I confirmed that the file exists and other applications can open it, e.g. display from imagemagick.


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (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: LighthouseBlue
Icon Theme: Sandy

Memory status: size: 22016000 vsize: 22016000 resident: 7557120 share: 6320128 rss: 7557120 rss_rlim: 4294967295
CPU usage: start_time: 1204800500 rtime: 198 utime: 153 stime: 45 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 0xb6c0e6c0 (LWP 24351)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 191493

Thread 1 (Thread 0xb6c0e6c0 (LWP 24351))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    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_logv
    from /usr/lib/libglib-2.0.so.0
  • #10 g_log
    from /usr/lib/libglib-2.0.so.0
  • #11 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #12 eog_util_dot_dir
  • #13 ??
  • #14 ??
  • #15 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (61522 sec old) ---------------------
** (nm-applet:4136): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.15" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:4136): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.15" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:4136): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.15" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:4136): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.15" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:4136): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.15" is not allowed to own the service "org.freedesktop.Networ
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Baptiste Mille-Mathias 2008-03-06 10:55:35 UTC 
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Lucas Rocha 2008-03-06 11:19:16 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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