Save photos... destination fail (multiple files)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gtkam (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Happens in both Ubuntu Desktop 12.10 and LinuxMint 14 MATE (both 64-bit)
Package: gtkam | Version: 0.1.18-1 | Architecture: amd64
Initialize camera, unmount if prompted, start gtkam. In gtkam select/save a single image to a chosen directory. Image is saved to target directory as expected. But...
Instead, choose multiple images in gtkam, right-click and Save. Choose/create a specific target directory location (other than $HOME) and then click 'Save'. The multiple images are downloaded and saved to root of user's $HOME directory instead of the target directory. EVERY TIME.
Other config changes in the 'Save photos...' window such as: 'What to save:' and 'Use filename(s) provided by camera' do not change this buggy behavior.
Help | Debug info:
gtkam 0.1.18
gtkam has been compiled with the following options:
+ x86_64-
+ no bonobo (for FIXME)
+ no gnome (for FIXME)
+ no gimp (plugin for The Gimp)
+ exif (for displaying exif information)
libgphoto2 2.4.14
libgphoto2 has been compiled with the following options:
+ gcc (C compiler used)
+ ltdl (for portable loading of camlibs)
+ EXIF (for special handling of EXIF files)
libgphoto2_port 0.8.0
libgphoto2_port has been compiled with the following options:
+ gcc (C compiler used)
+ ltdl (for portable loading of camlibs)
+ USB (libusb, for USB cameras)
+ serial (for serial cameras)
+ no resmgr (serial port access and locking)
+ no ttylock (serial port locking)
+ no lockdev (serial port locking)
apt-cache info:
gtkam:
Installed: 0.1.18-1
Candidate: 0.1.18-1
Version table:
*** 0.1.18-1 0
500 http://
100 /var/lib/
Changed in gtkam (Ubuntu): | |
status: | New → Incomplete |
tags: | added: mint-mate |
Welp, considering that this bug report was originally posted over eight years ago... for gtkam v. 0.1.18-1 ... while gtkam at present stands at gtkam 1.0 (Linux Mint 20.2 MATE [Ubuntu 20.04 variant]).
This bug report seems no longer relevant since none of what I posted originally, still applies today? I'd change it's status to 'closed' but it does not appear that I have the option to do so?
.