Public bug reported:
The natty bzr branch of the installation guide says:
"However, Debian GNU/Linux maverick will not run on 386 or earlier processors."
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/natty/installation-guide/natty/annotate/head:/en/hardware/supported/i386.xml
The Maverick
There are two ways to rotate a JPEG: you can either re-encode the entire
image, or you can set an EXIF tag that says "when you display this
image, rotate it by 90 degrees.". f-spot does the latter, which I think
is probably the less intrusive way.
The original problem reported was that a camera wo
The upstream bug hasn't moved on much, but I've just tried to reproduce this in
Jaunty using my test image and been unable to. Would recommend that anyone else
experiencing the problem to try it in Jaunty.
--
Runs out of memory Importing photo with suspect EXIF data
https://bugs.launchpad.net/
This one would be quite difficult to fix; the problem is that it is unsafe to
rename photo files that f-spot knows about. If f-spot scanned the entire photo
directory structure to look for renamed photos every time it started, it would
make life unpleasant for people like me who have 7,000 phot
Confirmed that Michael Hudson's package for jaunty works for me.
--
Imports all photos to the root of the home directory
https://bugs.launchpad.net/bugs/354264
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The problem was caused by ubuntu_importer-targetdir-selector.dpatch:
+if (File.Exists(FSpot.Global.PhotoDirectory))
According to Microsoft's C# documentation, File.Exists will always
return false when passed a directory path. It should be calling
Directory.Exists. Having
Correction: the problem has not been resolved by editing the udev rules,
as I said in the preceding comment.
Initially it appeared to work, however after another 3 or 4 ejects it
started to immediately close the drive tray after ejecting. (I'm in the
process of ripping my entire CD collection).
-
I still have this problem after applying all the Intrepid recommended
updates, including udev-124-9
ii udev 124-9 rule-based device node and kernel
event mana
This is the drive I am using:
*-cdrom
description: DVD writer
product: DVD
Both eog and gthumb load the problem image without any warning or
error messages.
I copied the image to /tmp/foo and then imported it into f-spot, while
running it in debug mode as you suggested. Again I got the out of
memory error.
The debug output is attached.
Cheers,
Graham
** Attachment add
I apologise for not having stated that I am using Hardy and the f-spot
version:
||/ Name Version Description
+++--==
ii f-spot 0.4.3.1-0ubuntu1 personal photo
management
** Attachment added: "IMG_4147.JPG"
http://launchpadlibrarian.net/17795593/IMG_4147.JPG
--
Runs out of memory Importing photo with suspect EXIF data
https://bugs.launchpad.net/bugs/272822
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Public bug reported:
I have two images which, when imported into f-spot, will cause it to run
out of memory (at 1.1 GiB resident set size).
metacam cannot read the EXIF data and I suspect it may have been
corrupted:
$ metacam IMG_4147.JPG
File: IMG_4147.JPG
WARNING: Unknown field type 0
Standa
This mbox file displays the problem.
--
Doesn't display lines starting "From" correctly in mbox
https://launchpad.net/bugs/52899
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
In the mbox mailbox format it is necessary to escape lines beginning
"From ", as this is the message delimiter. Standard practice is to place
a ">" character at the start of the line.
mutt, however, displays these escaped lines as ">From ..."
I believe that it should not dis
14 matches
Mail list logo
