Default mount points not suitable for photo import
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Canonical System Image |
Undecided
|
Unassigned | ||
| | mtp (Ubuntu) |
High
|
Unassigned | ||
| | shotwell (Ubuntu) |
Undecided
|
Unassigned | ||
Bug Description
When I plug my Ubuntu Phone into my desktop I want to be able to import photos easily into my photo manager of choice (Shotwell in my case but others are available apparently). The photos should be available via a "DCIM" folder, but they're in "Photos" which Shotwell doesn't find. While I could use the "Import from folder" and navigate my way to Photos, I'd rather it Just Worked.
Could we export photos over the "standard" DCIM folder to make this easier for everyone?
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: mtp-server 0.0.2+14.
Uname: Linux 3.4.0-4-mako armv7l
ApportVersion: 2.13.2-0ubuntu5
Architecture: armhf
Date: Mon Feb 24 01:01:39 2014
InstallationDate: Installed on 2014-02-23 (0 days ago)
InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140223.1)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_
SHELL=/bin/bash
SourcePackage: mtp
UpgradeStatus: No upgrade log present (probably fresh install)
| Changed in mtp (Ubuntu): | |
| importance: | Undecided → Wishlist |
Well, I'm not sure this is actually the "proper" way to do this: we don't *have* to have a DCIM directory. It just so happens it's only one of the few "well-known directories" that Shotwell defines. In the event that it does not manage to find them, it would scan the whole tree, which is also fine.
So I think this needs to happen in two parts: if there is a Photos or Images directory on the device, it makes sense for Shotwell to scan that.
Also, this appears to be failing because of some other issue in GPhoto or otherwise. I'll dig into it and fix the MTP data so that it works properly.
| Changed in mtp (Ubuntu): | |
| importance: | Wishlist → High |
| status: | Confirmed → Triaged |
| assignee: | nobody → Mathieu Trudel-Lapierre (mathieu-tl) |
Triaged/High since this is pretty obviously in part caused by an issue with the metadata about the device that we export over MTP.
There also needs to be a task for shotwell..
I've been testing this, it seems like the issue might be due to the session handling in the mtp daemon.
| tags: | added: qa-daily-testing rtm14 |
Did we not fix this already? I mentioned a session issue, but it seems like this would have been fixed separately from whatever the mount points might be.
| Changed in mtp (Ubuntu): | |
| assignee: | Mathieu Trudel-Lapierre (mathieu-tl) → nobody |
| John McAleely (john.mcaleely) wrote : | #7 |
". It just so happens it's only one of the few "well-known directories" that Shotwell defines."
I'm surprised at this assumption. DCIM (and filename rules) are part of now-ancient standards for digital cameras:
https:/
Mobile phones with cameras have by long convention also offered this filesystem layout. My current iOS 9 device still does this, for example.
This is nothing to do with Shotwell's preferences.
| Changed in shotwell (Ubuntu): | |
| status: | New → Invalid |
| Pat McGowan (pat-mcgowan) wrote : | #8 |
Still not sure this is necessary, did the metadata issue get resolved?
| Changed in canonical-devices-system-image: | |
| assignee: | nobody → John McAleely (john.mcaleely) |
| status: | New → Confirmed |
| Changed in canonical-devices-system-image: | |
| assignee: | John McAleely (john.mcaleely) → nobody |


Status changed to 'Confirmed' because the bug affects multiple users.