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 498894 - crash in Image Viewer: I asked for a slide show...
crash in Image Viewer: I asked for a slide show...
Status: RESOLVED DUPLICATE of bug 320206
Product: eog
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-22 03:24 UTC by Charles R. Twardy
Modified: 2007-11-22 12:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Charles R. Twardy 2007-11-22 03:24:27 UTC 
Version: 2.18.1

What were you doing when the application crashed?
I asked for a slide show at 1s per slide.  Pictures were 7 megapixel.  Screen was 1024x768.  It showed 1 slide. After 5-10s, I hit escape. It went back to a regular window.  I think the crash was already underway. Soon after, it reported a crash.


Distribution: Debian lenny/sid
Gnome Release: 2.20.1 2007-10-26 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.18-1-powerpc #1 Sat Oct 21 16:15:47 CEST 2006 ppc
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 168120320 vsize: 168120320 resident: 108429312 share: 14622720 rss: 108429312 rss_rlim: 4294967295
CPU usage: start_time: 1195701367 rtime: 6338 utime: 5870 stime: 468 cutime:7 cstime: 28 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/X11/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 0x30044b00 (LWP 9242)]
[New Thread 0x3272b4d0 (LWP 9249)]
[New Thread 0x309f74d0 (LWP 9243)]
(no debugging symbols found)
0x0f243994 in waitpid () from /lib/libpthread.so.0

+ Trace 179200

Thread 1 (Thread 0x30044b00 (LWP 9242))

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


----------- .xsession-errors (5274 sec old) ---------------------
** (nm-applet:6576): WARNING **: <WARNING>	 nma_dbus_init (): nma_dbus_init() could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.10" is not allowed to own the service "or
** (nm-applet:6576): WARNING **: <WARNING>	 nma_dbus_init (): nma_dbus_init() could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.10" is not allowed to own the service "or
** (nm-applet:6576): WARNING **: <WARNING>	 nma_dbus_init (): nma_dbus_init() could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.10" is not allowed to own the service "or
** (nm-applet:6576): WARNING **: <WARNING>	 nma_dbus_init (): nma_dbus_init() could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.10" is not allowed to own the service "or
** (nm-applet:6576): WARNING **: <WARNING>	 nma_dbus_init (): nma_dbus_init() could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.10" is not allowed to own the service "or
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Felix Riemann 2007-11-22 12:37:29 UTC 
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 version 2.20. You may want to check for a software upgrade.


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