Double-clicking mp3 on smb share does nothing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rhythmbox (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
When you double-click an mp3 file that is on an smb share, rhythmbox opens but does not play the file.
If you right-click -> open with -> movie player, this works and plays the file.
Running "rhythmbox -d", then double clicking the file gives the error (full output below)
[_uri_handle_
-------
(18:53:54) [0x1a2e6d0] [rb_uri_
(18:53:54) [0x1a2e6d0] [rb_shell_load_uri] rb-shell.c:3835: adding uri smb://brikett/
_get_mime_
URI 'smb://
_get_mime_
(18:53:54) [0x1a2e6d0] [load_uri_
(18:53:54) [0x1a2e6d0] [rb_shell_
(18:53:54) [0x1a2e6d0] [rb_shell_
(18:53:54) [0x1a2e6d0] [load_uri_
(18:53:54) [0x1a2e6d0] [maybe_
(18:53:54) [0x1a2e6d0] [impl_add_uri] rb-library-
(18:53:54) [0x1a2e6d0] [load_uri_finish] rb-shell.c:3680: didn't want to do anything anyway
(18:53:54) [0x1a2e6d0] [start_import_job] rb-library-
(18:53:54) [0x1a2e6d0] [rhythmdb_
(18:53:54) [0x1a2e6d0] [next_uri] rhythmdb-
(18:53:54) [0x3b4fb20] [_uri_handle_
(18:53:54) [0x1a2e6d0] [next_uri] rhythmdb-
(18:53:54) [0x1a2e6d0] [emit_scan_
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: rhythmbox 2.96-0ubuntu4.1
ProcVersionSign
Uname: Linux 3.2.0-30-generic x86_64
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
Date: Sun Sep 16 18:54:32 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
SourcePackage: rhythmbox
UpgradeStatus: No upgrade log present (probably fresh install)
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.