Ubuntu

tries to start Rythmbox-client instead of File Manager

Bug #772460 reported by gerti on 2011-04-28

This bug report is a duplicate of: Bug #662194: [SRU] Nautilus: 'Remember this application for ..." option should be made inactive by default. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Ubuntu	New	Undecided	Unassigned

Bug Description

when I click on something under "Places" nautilus is not started, but Rythmbox-client is attempted - and fails).
Same bug with Ubuntu 10.10 and not repaired with 11.4.
How can I change "preferreds" ?
(the "Preferred Applications still only encompass a very small selecrion)

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: nautilus 1:2.32.2.1-0ubuntu13
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Thu Apr 28 16:59:39 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110329.1)
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_DK.utf8
LC_MESSAGES=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

gerti (gerti) wrote on 2011-04-28:

Dependencies.txt Edit (5.4 KiB, text/plain; charset="utf-8")
GConfNonDefault.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (47.0 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (782 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (1.4 KiB, text/plain; charset="utf-8")
usr_lib_nautilus.txt Edit (312 bytes, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2011-04-28:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #667071, so it 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. Feel free to continue to report any other bugs you may find.

See the description of bug #667071 for a workaround for the problem.