Public bug reported:
Can't sync iPod (touch 2G): when mounting in file manager, the access
address afc://[device uuid] appends a ":3" at the end, so it turns to
afc://[uuid]:3, which the file manager shows as an empty location.
Removing the ":3" at the end and entering afc://[device uuid] manualy
shows the iPod's root filesystem, which could in theory be managed by
gtkpod, Rhythmbox or Banshee.
However, I can't seem to find a way to disable the arbitrary ":3" added
automatically by the mounter.
This behaviour began after updating the library (it has worked fine before, in
the same OS in 2 different machines, being able to transfer music files).
I've googled for a week looking for a similar problem reported, and none was
found so far, hence the bug report.
Please let me know what other culprit there may be, to begin pinpointing the
cause somewhere else, if necessary. (gvfs, perhaps?)
ProblemType: Bug
DistroRelease: elementary 0.4.1
Package: libimobiledevice6 1.2.0+dfsg-3~ubuntu0.2 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic x86_64
NonfreeKernelModules: nvidia_uvm wl nvidia
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
CurrentDesktop: Pantheon
Date: Tue Dec 26 14:38:47 2017
InstallationDate: Installed on 2017-09-24 (93 days ago)
InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170814)
SourcePackage: libimobiledevice
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: libimobiledevice (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug loki third-party-packages
** Description changed:
Can't sync iPod (touch 2G): when mounting in file manager, the access
address afc://[device uuid] appends a ":3" at the end, so it turns to
afc://[uuid]:3, which the file manager shows as an empty location.
Removing the ":3" at the end and entering afc://[device uuid] manualy
shows the iPod's root filesystem, which could in theory be managed by
gtkpod, Rhythmbox or Banshee.
However, I can't seem to find a way to disable the arbitrary ":3" added
automatically by the mounter.
This behaviour began after updating the library (it has worked fine before,
in the same OS in 2 different machines, being able to transfer music files).
I've googled for a week looking for a similar problem reported, and none was
found so far, hence the bug report.
- Please let me know what other culprit there may be, to begin pinpointing the
cause somewhere else, if necessary.
+ Please let me know what other culprit there may be, to begin pinpointing the
cause somewhere else, if necessary. (gvfs, perhaps?)
ProblemType: Bug
DistroRelease: elementary 0.4.1
Package: libimobiledevice6 1.2.0+dfsg-3~ubuntu0.2 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic x86_64
NonfreeKernelModules: nvidia_uvm wl nvidia
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
CurrentDesktop: Pantheon
Date: Tue Dec 26 14:38:47 2017
InstallationDate: Installed on 2017-09-24 (93 days ago)
InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170814)
SourcePackage: libimobiledevice
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libimobiledevice in Ubuntu.
https://bugs.launchpad.net/bugs/1740159
Title:
Can't sync iPod (touch 2G): device recognized by file manager but not
by media players / managers
Status in libimobiledevice package in Ubuntu:
New
Bug description:
Can't sync iPod (touch 2G): when mounting in file manager, the access
address afc://[device uuid] appends a ":3" at the end, so it turns to
afc://[uuid]:3, which the file manager shows as an empty location.
Removing the ":3" at the end and entering afc://[device uuid] manualy
shows the iPod's root filesystem, which could in theory be managed by
gtkpod, Rhythmbox or Banshee.
However, I can't seem to find a way to disable the arbitrary ":3" added
automatically by the mounter.
This behaviour began after updating the library (it has worked fine before,
in the same OS in 2 different machines, being able to transfer music files).
I've googled for a week looking for a similar problem reported, and none was
found so far, hence the bug report.
Please let me know what other culprit there may be, to begin pinpointing the
cause somewhere else, if necessary. (gvfs, perhaps?)
ProblemType: Bug
DistroRelease: elementary 0.4.1
Package: libimobiledevice6 1.2.0+dfsg-3~ubuntu0.2 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic x86_64
NonfreeKernelModules: nvidia_uvm wl nvidia
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
CurrentDesktop: Pantheon
Date: Tue Dec 26 14:38:47 2017
InstallationDate: Installed on 2017-09-24 (93 days ago)
InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170814)
SourcePackage: libimobiledevice
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1740159/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
