Bug 134627 - Typing a path in the run dialog opens up rhythmbox on that folder, not nautilus
Summary: Typing a path in the run dialog opens up rhythmbox on that folder, not nautilus
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox   
(Show other bugs)
Version: 3
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Colin Walters
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: 131589
TreeView+ depends on / blocked
 
Reported: 2004-10-05 07:25 UTC by Alexander Larsson
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version: 0.8.8-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-10-05 18:37:54 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Alexander Larsson 2004-10-05 07:25:33 UTC
It seems rhythmbox is somehow set up as the default for handling
folders. If i for instance type /tmp in the run dialog i get rhythmbox
instead of a nautilus window.

This can also be seen in the nautilus browser window. The information
sidebar for every folder you visit has an "open in music player" button.

Is this registration useful in some way? All i can see is it getting
in the way.

Comment 1 Alexander Larsson 2004-10-05 07:28:11 UTC
Hmmm. Removing rhythmbox doesn't give me a nautilus when i type a
pathname either. This is perhaps a deeper problem with the new
mimetype system.


Comment 2 Alexander Larsson 2004-10-05 10:09:43 UTC
gnome-vfs2-2.8.1-6 has a fix for the general problem. But with
rhythmbox installed we still get rhythmbox on typing in a folder in
the run dialog.

Comment 3 Alexander Larsson 2004-10-05 10:11:40 UTC
Another nitpick: The Open with property dialog for folders contains
just "Music Player" which is selected. This looks pretty strange.
Especially when its not actually used when you open the folder.


Note You need to log in before you can comment on or make changes to this bug.