eog saves picture incorrectly (corrupts) after rotate

[Ward Back]

Binary package hint: eog

i cannot reproduce it - all i did was rotate a picture and save it. now the bottom 3/4 of the photo (JPG) is black. however, very serious bug indeed. i essentially lost a very important wedding photo forever due to this bug - please take it seriously. i can email the resulting picture (unless a further step in this bug reporting process can attach a file). i find it unbelievable to see that a Ubuntu default image viewing program can have serious bugs such as these. looks like i'm going to have to get involved.

ProblemType: Bug
Architecture: i386
Date: Mon Nov 19 08:01:14 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/eog
NonfreeKernelModules: nvidia
Package: eog 2.20.1-0ubuntu1
PackageArchitecture: i386
ProcCmdline: eog file:///home/antej/Desktop/Milena%20%26%20August%20wedding%2011-17-07/CIMG2014.JPG
ProcCwd: /home/antej
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: eog
Uname: Linux sivi 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

[Ward Back (wardback)]

here is the corrupt picture

[Pedro Villavicencio (pedro)]

Thanks for your report, It happens to you with every image or only with that one happened? Rotate and save in eog works fine for me.

[Ward Back (wardback)]

only with that one. i tried about 5-6 times to reproduce it with
various delays between the three actions (rotate,save,close eog)
without success. i was not doing anything else at the time (no other
applications were open).
please let me know if there is anything else i can do to help.
thank you very much.

On Nov 19, 2007 8:44 AM, Pedro Villavicencio <email address hidden> wrote:
> Thanks for your report, It happens to you with every image or only with
> that one happened? Rotate and save in eog works fine for me.
>
> ** Changed in: eog (Ubuntu)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
> Status: New => Incomplete
>
>
> --
> eog saves picture incorrectly (corrupts) after rotate
> https://bugs.launchpad.net/bugs/163797
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Sebastien Bacher (seb128)]

Having steps to trigger the issue would be required

[Ward Back (wardback)]

> I am sorry, but I disagree. I feel that if you analyze the procedure
> that does the actual saving of the file you could probably see the
> condition under which the saving can be interrupted, and the picture
> can be lost.
> If not, I think building a test procedure with different timings of
> the three steps to produce the file could also bear fruit.
> It might not be EOG's fault (it might be the OSs), but we can figure this out.
> I do not feel the issue is machine/hardware specific. If it happened
> once it could happen again. Maybe there should be a different
> procedure in place altogether, one that makes/saves a temporary copy
> of the image (say pict2.jpg), removes the original (pict.jpg into
> trash), and renames the pict2.jpg into pict.jpg. This way, if anything
> happens AT ALL to the picture, user can simply go back to the trash
> for the latest saved copy. Would you agree?
> However, I did see that there is a list of bugs sort of in the same
> family (but reproducible) that needs to be tackled first.
> I would love to find some free time during the holiday season and
> 'analyze the procedure' myself.
> So lets not worry about it for now, but thank you (very much) for your reply.

On Nov 28, 2007 9:24 AM, Sebastien Bacher <email address hidden> wrote:
> Having steps to trigger the issue would be required
>
>
> --
> eog saves picture incorrectly (corrupts) after rotate
> https://bugs.launchpad.net/bugs/163797
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.