Bug 2294

Summary: nautilus does not invoke application associated with ordinary files
Product: Mageia Reporter: andré blais <andr999>
Component: RPM PackagesAssignee: Olav Vitters <olav>
Status: RESOLVED OLD QA Contact:
Severity: major    
Priority: Normal CC: andr55, dmorganec, mageia, marja11, stormi-mageia
Version: 1   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: nautilus-2.32.2.1-3.mga1.src.rpm CVE:
Status comment:

Description andré blais 2011-07-27 01:43:13 CEST
Description of problem:

If a user clicks on an ordinary file, nautilus does not invoke the application associated with the file type.
Instead it gives an error message :
"répertoire non trouvé" ("file not found")

Directories are properly displayed.

Version-Release number of selected component (if applicable):
See rpm

How reproducible:
Attempt to display a non-directory file using the default action of nautilus.

Steps to Reproduce:
1. Click on an ordinary file (non-directory) to invoke the default application associated with the particular type of file.
2. The error message (above) is displayed.

Note that using the context menu works.

Workaround :
Make another file manager the default under Gnome, such as pcmanfm.
Then files are displayed normally.
Manuel Hiebel 2011-07-27 15:49:35 CEST

CC: (none) => mageia

Manuel Hiebel 2011-07-28 17:31:15 CEST

CC: (none) => dmorganec, jani.valimaa

Comment 1 Samuel Verschelde 2011-10-01 03:51:46 CEST
Assigning to maintainer now that our maintainers database has an entry for
this package. Please assign back to bugsquad@mageia.org in case of a mistake
from me.

CC: (none) => stormi
Assignee: bugsquad => olav

andré blais 2011-10-09 07:28:03 CEST

CC: (none) => andre999mga

Comment 2 andré blais 2011-10-10 02:22:54 CEST
Is by any chance this bug related to bug #1539 ?
("Switching to a console terminal crashes X")

There it seems that an existing file is not found as well.  (Although I could well be mistaken.)
Comment 3 Marja Van Waes 2012-01-16 22:27:49 CET
Pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED.


@ Olav
Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.

CC: (none) => marja11

Comment 4 Olav Vitters 2012-01-16 22:59:01 CET
I don't understand the description. What is an ordinary file? Just double clicking on any file fails? Anything in ~/.xsession-errors?

Status: NEW => ASSIGNED

Jani Välimaa 2012-04-28 10:05:27 CEST

CC: jani.valimaa => (none)

Comment 5 Olav Vitters 2012-09-09 14:13:56 CEST
Cannot fix if I don't get a response. Closing as old, feel free to reopen.

Status: ASSIGNED => RESOLVED
Resolution: (none) => OLD