Bug 378784 – crash in Image Viewer: Dia-Show mit Eye-of-GNOM...

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 378784 - crash in Image Viewer: Dia-Show mit Eye-of-GNOM...


Summary:	crash in Image Viewer: Dia-Show mit Eye-of-GNOM...


Status:	RESOLVED DUPLICATE of bug 320206

Product:	eog
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	EOG Maintainers
QA Contact:	EOG Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-24 10:37 UTC by fmkuerten
Modified:	2006-11-26 14:30 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description fmkuerten 2006-11-24 10:37:51 UTC

Version: 2.16.1

What were you doing when the application crashed?
Dia-Show mit Eye-of-GNOME direkt von einem Hama-Kartenleser (35 in 1) an USB


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 160710656 vsize: 0 resident: 160710656 share: 0 rss: 120676352 rss_rlim: 0
CPU usage: start_time: 1164364274 rtime: 0 utime: 6692 stime: 0 cutime:5937 cstime: 0 timeout: 755 it_real_value: 0 frequency: 14

Backtrace was generated from '/usr/bin/eog'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

Comment 1 Susana 2006-11-24 13:12:10 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 fmkuerten 2006-11-24 14:53:59 UTC

Hi there, here's the missing stack-trace:

Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 89976832 vsize: 0 resident: 89976832 share: 0 rss: 49573888 rss_rlim: 0
CPU usage: start_time: 1164379752 rtime: 0 utime: 2034 stime: 0 cutime:1918 cstime: 0 timeout: 116 it_real_value: 0 frequency: 4

Backtrace was generated from '/usr/bin/eog'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1226529104 (LWP 5310)]
[New Thread -1262662752 (LWP 5312)]
[New Thread -1228563552 (LWP 5311)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 89027

Thread 1 (Thread -1226529104 (LWP 5310))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 eog_image_cache_add
at eog-image-cache.c line 84
#5 job_image_load_finished
at eog-full-screen.c line 709
#6 eog_job_call_finished
at eog-job.c line 442
#7 job_finished_cb
at eog-job-manager.c line 53
#8 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#9 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#10 g_main_context_check
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
at main.c line 637
#0 __kernel_vsyscall

Comment 3 fmkuerten 2006-11-24 14:57:38 UTC

The crash can be produced by changing several times between 'dia show', 'full screen view' and scrolling forward/backward thru the images manually.

Hope that helps
Frank

Comment 4 fmkuerten 2006-11-25 10:02:44 UTC

I've browsed a little thru the other bugs concerning eog. This crash might be the same as described in # 320206 (rather old bug). The cardreader has nothing to do with it, it occurs also with pics on harddisks. The error will only occur more often, because the media is slower (longer time to press ESC while picture is loading).

Comment 5 Felix Riemann 2006-11-26 14:30:54 UTC

Yes, I think you are right. Your stack trace fits the one in bug 320206. So I'm marking this as a duplicate:

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 320206 ***