Red Hat Bugzilla – Bug 152166
No way to type in path to executable when adding new mime types
Last modified: 2015-03-03 17:27:49 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Firefox/1.0.2 Fedora/1.0.2-1.3.1
Description of problem:
This is not a bug per se, but is extremely annoying for our sysadmins. Here is an example of what happens:
* User clicks on some new filetype and nautilus is not yet set up to handle that file. Say for example it is a .m3u file and we want it to open in xmms.
* User calls sysadmin for help, sysadmin uses the 'open with' button to try and link xmms to m3u files.
* There *used* to be a box where you could simply type in "/usr/bin/xmms" but this has been replaced by an annoying file browser where one must pointy-clicky all the way into /usr/bin, then deal with the further annoyance of watching hundreds of programs populate the window while trying to scroll down and select xmms. The frustration factor is compounded by the fact that the list is moving because of new items populating it so when sysadmin finds xmms it jumps down the list.
Please, for the love of god, bring back the text field where you can type the path to the executable. Think of the poor sysadmins.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Browse web until you find a mime type that is not associated with any program.
2. Clicky on linky
3. Try to use frustrating interface to associate proper program with filetype
Actual Results: Frustration
Expected Results: Bliss
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Fedora Core 3 is not maintained anymore.
Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release please reopen this bug and assign it to the corresponding