Corrupted config file if width/height are defined from keyboard

This creates some pretty serious breakage!

nautilus-image-manipulator fails to start after setting a custom resolution due to the float value.

As a workaround I let it create the config, set the values to integars, and chmod 444 the config file. Now it works each time, but I can only use the value I set initially or I would need to change the config file manually again.

You should try my dev branch :
https://code.launchpad.net/~razerraz/nautilus-image-manipulator/nautilus-image-manipulator

On 12/17/2012 11:23 PM, tekstr1der wrote:
> This creates some pretty serious breakage!
>
> nautilus-image-manipulator fails to start after setting a custom
> resolution due to the float value.
>
> As a workaround I let it create the config, set the values to integars,
> and chmod 444 the config file. Now it works each time, but I can only
> use the value I set initially or I would need to change the config file
> manually again.
>

Sorry guys, I had the bug email turned off for some reason and didn't realize that these bugs were being filed. I've solved this issue in r193.

r193

v1.2

This bug was fixed in the package nautilus-image-manipulator - 1.1-2
Sponsored for Emilien Klein (emilien-klein)

---------------
nautilus-image-manipulator (1.1-2) unstable; urgency=low

  * Fix 2 upstream bugs, patches already applied upstream and released in v1.2:
    - debian/patches/fix-702044: Corrupted config file if width/height are
        defined from keyboard (Closes: #702044)
    - debian/patches/fix-702045: Upload to 1fichier.com not working
        (Closes: #702045)

 -- Emilien Klein <email address hidden> Sat, 02 Mar 2013 09:29:45 +0100

If you wish to get this bug fixed in quantal, please follow the procedure outlined here:
https://wiki.ubuntu.com/StableReleaseUpdates

Specifically:
1) update the bug description as per above page including testcase
2) attach a debdiff (should be a simple change to use correct version number, target release and include this and the other bugs reference numbers) (well you can have just one debdiff for two bugs, if you do them together)
3) subscribe ubuntu-sponsors team to get this sponsored

After that, it will be queue for SRU team to review the package and publish it into -proposed pocket. After that it must be verified as per test-case in the bug description, if not verified in a timely manner the update will be removed from -proposed pocket. If verification is successful, the update will be published in -updates pocket.

Thanks Dmitrijs for syncing the package for Raring from Debian. I'll follow the steps for the Quantal update.

quantal has seen the end of its life and is no longer receiving any updates. Marking the quantal task for this ticket as "Won't Fix".