Bug#507991: [eog] Crashes when trying to save write protected file

Matthias Bläsing matthias.blaesing at rwth-aachen.de
Thu Mar 19 11:28:07 UTC 2009


Hey,

excuse the late reply. I'm digging through a pile of emails. But yes, I
can reproduce it with (now) 2.24.3.1-1. I was able to get a backtrace
now:

mblaesing at enterprise:~$ gdb /usr/bin/eog
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(gdb) run
Starting program: /usr/bin/eog 
[Thread debugging using libthread_db enabled]
[New Thread 0xb694a750 (LWP 5407)]
[New Thread 0xb67a8b90 (LWP 5410)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb67a8b90 (LWP 5410)]
0x08078f15 in tmp_file_move_to_uri (image=<value optimized out>, 
    tmpfile=<value optimized out>, file=0x8bef310, overwrite=1, 
    error=0x930ca84) at eog-image.c:1339
1339	eog-image.c: No such file or directory.
	in eog-image.c
(gdb) backtrace
#0  0x08078f15 in tmp_file_move_to_uri (image=<value optimized out>, 
    tmpfile=<value optimized out>, file=0x8bef310, overwrite=1, 
    error=0x930ca84) at eog-image.c:1339
#1  0x0807a5c6 in eog_image_save_by_info (img=0x93350e0,
source=0x8be9860, 
    error=0x930ca84) at eog-image.c:1501
#2  0x08087c87 in eog_job_save_real_run (job=0x930ca78) at
eog-jobs.c:569
#3  0x08086f61 in eog_job_save_run (job=0x930ca78) at eog-jobs.c:590
#4  0x08086e6d in eog_render_thread (data=0x0) at eog-job-queue.c:84
#5  0xb7546e2f in g_thread_create_proxy (data=0x8a062d0)

at /build/buildd-glib2.0_2.20.0-1-i386-yJa20r/glib2.0-2.20.0/glib/gthread.c:635
#6  0xb7e30f50 in start_thread () from /lib/libpthread.so.0
#7  0xb744e5de in clone () from /lib/libc.so.6
(gdb) 

To get this trace I did this:

Placed tuz.png on the desktop, remove the write permission for me and
opened it in eog, rotated it left by 90° and pressed CTRL-S to save the
resulting image.

Here some more Info about the file - whether this is imported: I don't
know:
mblaesing at enterprise:~$ ls -lh Desktop/tuz.png 
-r--r--r-- 1 mblaesing mblaesing 280K 18. Mär 21:38 Desktop/tuz.png
mblaesing at enterprise:~$ file Desktop/tuz.png 
Desktop/tuz.png: PNG image, 1024 x 765, 8-bit/color RGBA, non-interlaced
mblaesing at enterprise:~$ 

I hope that helps

Greetings

Matthias


Am Freitag, den 23.01.2009, 15:42 +0100 schrieb Josselin Mouette:
> Le samedi 06 décembre 2008 à 18:41 +0100, Matthias Bläsing a écrit :
> > eog just gave me the problem, that it crashed without an obvious reason.
> > Some investigation revealed, that it crashed, when trying to save a
> > write protected file. Adding write permissions allowed me to save the
> > image without a crash.
> 
> I can’t seem to reproduce this with version 2.24.2-1.
> 
> Could you try it as well?
> 
> Thanks,
-- 
The man who trades freedom for security does not deserve,
nor will he receive either!

Benjamin Franklin








More information about the pkg-gnome-maintainers mailing list