Nokia E72 connection in Media transfer mode incomplete
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gvfs (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I tried to connect my Nokia E72 by USB in Media transfer mode. It is recognised and the dialogue regarding how I want to open the device appears (two instances of this open) along with an error message (see attachment). The device is recognised in rhythmbox but no media is present. Ok no media was present but after about 5 minutes whilst reporting this it has appeared. So it is very delayed.
I then clicked on a song to start playing it and it did infact start. When I clicked another song to change rhtymbox froze and then closed. When I reopened rhythmbox the songs were again not recognised and I got the error message (Media player device error Unable to open the Nokia E72 device). When this dialogue box was closed my phone disappeared from Rhythmbox but was still in the launcher.
Also two instances of my device appear in the launcher.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gvfs-backends 1.12.0-0ubuntu3
ProcVersionSign
Uname: Linux 3.2.0-22-
ApportVersion: 2.0-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Sun Apr 8 23:56:21 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANGUAGE=en_GB:en
LANG=en_GB.UTF-8
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gvfs
Title: gvfsd-gphoto2 crashed with SIGSEGV in pthread_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
| uzi3k (uzi3k) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| visibility: | private → public |
| tags: | removed: need-i386-retrace |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #946255, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.