Can not eject mass storage media player device

[Mats Taraldsvik]

Binary package hint: banshee

Ubuntu version: 9.10
Software version: banshee 1.4.3-6
Expected result:
  When I click on "Eject Sansa Clip (msc)" or choose same option from context menu disk should be unmounted
Actual Result:
  An error is reported:
"Could not eject Media Player: org.freedesktop.Hal.Device.Volume.UnknownFailure: Cannot open /media/.hal-mtab"

Ejecting works as expected in nautilus so I guess that it may be related to migration to devicekit-disks.

( The error is different from bug #416278, but they may be related. )

ProblemType: Bug
Architecture: amd64
Date: Fri Oct 16 14:13:44 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: banshee 1.4.3-6
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.42-generic
SourcePackage: banshee
Uname: Linux 2.6.31-13-generic x86_64

[Mats Taraldsvik (meastp)]

I upgraded and got the new banshee, but the issue is still there :

ProblemType: Bug
Architecture: amd64
Date: Sun Oct 18 12:33:09 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: banshee 1.5.1~git2260a87-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: banshee
Uname: Linux 2.6.31-14-generic x86_64

[Stewart G. (birbeck)]

I can confirm this bug with Ubuntu 9.10 (Karmic) Release Candidate 64-bit and Banshee 1.5.1 with my T-Mobile G1 (Android, MTP). Can unmount and eject device from Nautilus, but not from Banshee.

[Chow Loong Jin (hyperair)]

Noted. This is related to the HAL->Devkit-Disks transition. Another related bug
is Bug #382941.

--
Kind regards,
Chow Loong Jin (GPG: 0x8F02A411)
Ubuntu Contributing Developer

[flan_suse (flansuse)]

I can confirm this bug on the following system:

openSUSE 11.2
GNOME 2.28
Banshee 1.5.2
Sansa Clip+ (MSC mode)

[Johannes Mockenhaupt (mockenh-deactivatedaccount)]

A patch for this has been committed in the upstream trunk, so the next upstream release should fix this bug: http://git.gnome.org/cgit/banshee/commit/?id=3aac4c2f77b30de378065222b4261bcb9fcf12bd

[Chow Loong Jin (hyperair)]

The said commit has already been released into Ubuntu, so I'm marking this as fix released. If you can still reproduce this bug with Banshee 1.7.1 which can be found in the Banshee Unstable PPA and Ubuntu Maverick, please feel free to reopen this bug.