After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 579340 - Import saves images in home root
Import saves images in home root
Status: RESOLVED NOTGNOME
Product: f-spot
Classification: Other
Component: Import
0.5.x
Other Linux
: Normal normal
: ---
Assigned To: F-spot maintainers
F-spot maintainers
: 582426 582632 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-04-17 19:59 UTC by Tiefflieger
Modified: 2009-12-24 11:23 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tiefflieger 2009-04-17 19:59:02 UTC
Initially reported at https://bugs.edge.launchpad.net/ubuntu/+source/f-spot/+bug/353989

When I import images from my Canon Ixus 65, they are copied to my home root instead of being copied to the folder (ie "Bilder") specified at preferences.

When I import an image stored somewhere on my PC, everything seems to be just fine.

I didn't have the problem until march 30th 2009 (At least that's the date of the first image stored in my home root).


Appeared on up to date german Jaunty 64bit, Fspot v0.5.0.3

Unlike in other similar bug reports, there is neither a warning nor a folder called "Photos" is being created.
Comment 1 Stephane Delcroix 2009-04-28 08:42:41 UTC
ubuntu use a modified version of the "import from camera" dialog. please confirm that this happen on "official" f-spot version.
Comment 2 Tiefflieger 2009-04-28 15:50:38 UTC
Depends on what you mean by "official": It happens at the F-Spot version officially shipped with Ubuntu Jaunty
Comment 3 Maxxer 2009-04-28 16:27:12 UTC
(In reply to comment #2)
> Depends on what you mean by "official": It happens at the F-Spot version
> officially shipped with Ubuntu Jaunty

that is a MODIFIED version by Ubuntu. 
You should reproduce the problem with F-Spot downloaded from f-spot.org.
thanks
Comment 4 Tiefflieger 2009-04-28 18:18:11 UTC
Why? If I have a modified version, why should I try another version of F-Spot I will never use? I reported the problem for the ubuntu-version and was redirected here.
Now I'm a bit confused, it's like I'm reporting that my blue car is broken and you tell me that I should try the red one :-)
Comment 5 Maxxer 2009-04-28 19:26:46 UTC
(In reply to comment #4)
> Why? If I have a modified version, why should I try another version of F-Spot I
> will never use? I reported the problem for the ubuntu-version and was
> redirected here.

Because if the problem doesn't happen with the original version, then you're filing the bug to the wrong place.

i.e., have a look at ubuntu's f-spot changelog in march:
http://changelogs.ubuntu.com/changelogs/pool/main/f/f-spot/f-spot_0.5.0.3-1ubuntu6/changelog


so, as said in comment #2, Ubuntu has a modified import process, so PLEASE try (or have someone else do) the original version.


> Now I'm a bit confused, it's like I'm reporting that my blue car is broken and
> you tell me that I should try the red one :-)

no, it's not a matter of "color" but of "pieces".

Comment 6 Tiefflieger 2009-04-29 21:15:00 UTC
First of all, thanks for your patient answerings :-)
(In reply to comment #5)
> (In reply to comment #4)
> > Why? If I have a modified version, why should I try another version of F-Spot I
> > will never use? I reported the problem for the ubuntu-version and was
> > redirected here.
> 
> Because if the problem doesn't happen with the original version, then you're
> filing the bug to the wrong place.
> 
Ok, so let's say the bug appears only in the ubuntu version, then https://bugs.edge.launchpad.net/ubuntu/+source/f-spot/+bug/353989 would indeed have been the right place, right?
 
> so, as said in comment #2, Ubuntu has a modified import process, so PLEASE try
> (or have someone else do) the original version.
>
Basically, I don't mind testing the original version. But Ubuntu warns about trying upstream versions, on good cause I think - I don't want to break something if I uninstall the upstream version afterwards, I know what crawling in symlinks & file versions means... :-/

Comment 7 Maxxer 2009-04-30 07:07:29 UTC
(In reply to comment #6)
> Ok, so let's say the bug appears only in the ubuntu version, then
> https://bugs.edge.launchpad.net/ubuntu/+source/f-spot/+bug/353989 would indeed
> have been the right place, right?

yes.

> Basically, I don't mind testing the original version. But Ubuntu warns about
> trying upstream versions, on good cause I think - I don't want to break
> something if I uninstall the upstream version afterwards, I know what crawling
> in symlinks & file versions means... :-/

You can compile and run F-Spot into a subdirectory, without touching your system installation. The procedure is similar to the one explained here:
http://f-spot.org/How_To_Build_from_HEAD
in case you want to try ;)  (always make backups!)
if you need further help in building please ask on irc or on the mailing list.
Comment 8 Maxxer 2009-05-13 17:47:01 UTC
*** Bug 582426 has been marked as a duplicate of this bug. ***
Comment 9 Justin J Stark 2009-05-13 18:47:28 UTC
I compiled f-spot from source and its behavior seems to be the same as the version in ubuntu in this regard.  The target directory is set as the home folder by default which is bad behavior.

A quick workaround for this was adding

cd ~/Media/Photos

at the beginning of /usr/bin/f-spot.  The target directory seems to default to the current directory.
Comment 10 Maxxer 2009-05-14 06:51:10 UTC
confirmed as ubuntu only bug:

https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/354264/comments/9


i'll leave this open to let others find it until they release a fix
Comment 11 Maxxer 2009-05-14 18:43:54 UTC
*** Bug 582632 has been marked as a duplicate of this bug. ***
Comment 12 Tobias Mueller 2009-12-24 11:23:19 UTC
This seems to be NOTGNOME then, also a fix is released: https://bugs.edge.launchpad.net/ubuntu/+source/f-spot/+bug/354264