** Changed in: f-spot
Importance: Unknown = Medium
--
crashes when a filename uses :
https://bugs.launchpad.net/bugs/475811
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: f-spot
Status: Incomplete = Fix Released
--
crashes when a filename uses :
https://bugs.launchpad.net/bugs/475811
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This is fixed in Ubuntu 10.10 now. Thanks for reporting.
** Changed in: f-spot (Ubuntu)
Status: Triaged = Fix Released
--
crashes when a filename uses :
https://bugs.launchpad.net/bugs/475811
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: f-spot
Status: Unknown = Incomplete
--
crashes when a filename uses :
https://bugs.launchpad.net/bugs/475811
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Upstream bug has been marked as duplicate of bug
https://bugzilla.gnome.org/show_bug.cgi?id=559093.
** Bug watch added: GNOME Bug Tracker #559093
https://bugzilla.gnome.org/show_bug.cgi?id=559093
** Changed in: f-spot
Remote watch: GNOME Bug Tracker #603028 = GNOME Bug Tracker #559093
--
There is a notice in Mono's Uri.cs that there is a difference between
Mono 1.2 and Mono 2.0 in how scheme name characters are checked:
// Check scheme name characters as specified in RFC2396.
// Note: different checks in 1.x and 2.0
Well, I can confirm this issue. I'm using f-spot for years (with some
files containing colons in their name) and recently (after update) only
that made the application crash. I can provide you with a little python
script I wrote to rename files and database entries, but that would not
solve the
Thanks for your bug report. This bug has been reported to the developers
of the software. You can track it and make comments here:
https://bugzilla.gnome.org/show_bug.cgi?id=603028
** Bug watch added: GNOME Bug Tracker #603028
https://bugzilla.gnome.org/show_bug.cgi?id=603028
** Changed in:
Could somebody having the bug add .config/f-spot/photos.db there or
explain how to import a buggy image?
--
crashes when a filename uses :
https://bugs.launchpad.net/bugs/475811
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Sebastien: the easiest way to import a 'buggy' image (?) is to remove
the colon from the name... or is that not what you meant?
To get f-spot to run as it is (without any patches) I'd suggest changing
the name of the picture on the filesystem and in the database. Even
though you could %-encode
the question is to know how you managed to get f-spot crashing due such
files since it refuses to import files using a ':'
--
crashes when a filename uses :
https://bugs.launchpad.net/bugs/475811
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
11 matches
Mail list logo
