[Bug 19864] eog crashes on a specific .png file.

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=19864
Ubuntu | eog





------- Additional Comments From sivan at ubuntu.com  2005-11-20 15:25 UTC -------
Backtrace output:


(gdb) run /home/sivan/Desktop/sivan.png
Starting program: /usr/bin/eog /home/sivan/Desktop/sivan.png
[Thread debugging using libthread_db enabled]
[New Thread -1224071488 (LWP 3938)]
Instantiate job with id 1.
[New Thread -1226462288 (LWP 3941)]
Starting thread with id 0.
eog-image_load.c
load success: 1
n_images: 1/1
  1 /home/sivan/Desktop/sivan.png (581/380)
setting window size: 659/485
Instantiate job with id 2.
[New Thread -1236603984 (LWP 3943)]
Show exif data
Job 001: disposing ...
Job 001: disposing end
Starting thread with id 1.

Eog-ERROR **: file eog-collection-item.c: line 320 (job_thumb_create): assertion
failed: (*error != NULL)
aborting...

Program received signal SIGABRT, Aborted.
[Switching to Thread -1236603984 (LWP 3943)]
0xffffe410 in __kernel_vsyscall ()
(gdb) backtrace
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb72c79b1 in raise () from /lib/tls/i686/cmov/libc.so.6
#2  0xb72c92c9 in abort () from /lib/tls/i686/cmov/libc.so.6
#3  0xb744f7f4 in g_logv () from /usr/lib/libglib-2.0.so.0
#4  0xb744f828 in g_log () from /usr/lib/libglib-2.0.so.0
#5  0xb744f894 in g_assert_warning () from /usr/lib/libglib-2.0.so.0
#6  0x0807cbfa in job_thumb_create (job=0x82740b8, data=0x82667a8,
error=0x82740e0) at eog-collection-item.c:320
#7  0x0807092e in eog_job_call_action (job=0x82740b8) at eog-job.c:385
#8  0x0806f4bd in thread_start_func (data=0x1) at eog-job-manager.c:85
#9  0xb74628c4 in g_static_private_free () from /usr/lib/libglib-2.0.so.0
#10 0xb73d2361 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#11 0xb7367bde in clone () from /lib/tls/i686/cmov/libc.so.6


-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.