Bug 785497 - Thunar does not open default application when file is double clicked.
Summary: Thunar does not open default application when file is double clicked.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: Thunar
Version: 16
Hardware: i686
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-29 05:25 UTC by Randy Berry
Modified: 2013-02-14 01:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-14 01:35:54 UTC
Type: ---


Attachments (Terms of Use)

Description Randy Berry 2012-01-29 05:25:31 UTC
Description of problem:
Thunar does not open default application when file is double clicked. Right clicking and selecting default application works but double left clicking does not. The busy mouse courser comes up but does nothing. 

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

Thunar-1.3.0-4.fc16.i686

How reproducible:
Always.

Steps to Reproduce:
1. Double click on a file (text for example)

  
Actual results:
The busy mouse courser comes up but does nothing. 


Expected results:
When double clicking on a text file for example gedit should open the file.

Additional info:

Comment 1 Kevin Fenzi 2012-02-05 19:39:43 UTC
This happens all the time on any files?

Can you quit any Thunar sessions, confirm it's not running (ps aux | grep Thunar), then start it manually from a Terminal and see if it spews any debugging or errors?

Comment 2 Randy Berry 2012-02-05 20:39:03 UTC
 I can't seem to reproduce it every instance today. It did it once earlier but won't do it for me now. I did kill Thunar --daemon and tried it without it and double clicking without the daemon running works as expected. Then I reloaded the daemon and tried it again and it still works. I see no debug in the terminal it runs clean.

 I have noticed that it is only text files that default to gedit. If I double click on an odt it opens them with libreoffice without event, a pdf opens in document viewer without event and archives open with file roller. I'll keep an eye on it and pass on the exact details if it happens again.

Comment 3 Christoph Wickert 2012-02-06 12:49:40 UTC
Can you please check what file type this acutually is and then look up what is supposed to open it?

$ file -i apt-packages.txt 
apt-packages.txt: text/plain; charset=us-ascii

As you see it's text/plain.

$ grep text/plain ~/.local/share/applications/mimeapps.list 
text/plain=fedora-geany.desktop;fedora-leafpad.desktop;

As you can see I use geany as default and leafpad ad alternative. Not lets make sure that the default "fedora-geany.desktop" file is in place:

$ find /usr/share/applications/ ~/.local/share/applications/ -name fedora-geany.desktop
/usr/share/applications/fedora-geany.desktop

Yes, it's there.

Comment 4 Y-H 2012-06-13 07:29:22 UTC
I'm experiencing this problem with Gedit and Thunar.

gedit-3.2.6-1.fc16.x86_64
Thunar-1.3.0-4.fc16.x86_64 

When, from Thunar, I try double clicking to open a text file, nothing happens. On the next immediate attempt, the file opens in Gedit, but the mouse turns into a spinning wheel for a while. On the other hand, if i select the file, right click, and select "Open with 'gedit'" the file opens immediately but the mouse sometimes (always?) turns into a spinning wheel.

No problems whatsoever opening text files from Pcmanfm, which makes me think that there's something wrong with Thunar.

Comment 5 Christoph Wickert 2012-06-13 07:32:44 UTC
Can you do the same as I did in comment 3 and post the output here?

Comment 6 Y-H 2012-06-14 02:29:25 UTC
$ file -i test.txt 
test.txt: text/plain; charset=us-ascii

$ grep text/plain ~/.local/share/applications/mimeapps.list
text/plain=gedit.desktop

Comment 7 Y-H 2012-06-23 07:46:34 UTC
I get a spinning wheel sometimes when I open JPEG images from Thunar too, when the default image application is set to eog (Eye of GNOME).

Comment 8 Fedora End Of Life 2013-01-16 23:10:41 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Fedora End Of Life 2013-02-14 01:36:06 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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