Bug 812495 - 'Open Containing Folder' on a search result doesn't work (Xfce).
Summary: 'Open Containing Folder' on a search result doesn't work (Xfce).
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-search-tool
Version: 17
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Rui Matos
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-14 00:55 UTC by Sergio
Modified: 2013-08-01 12:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-01 12:29:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Sergio 2012-04-14 00:55:30 UTC
Description of problem: Selecting a search result and clicking on 'Open Containing Folder' opens the file with the first available application for it instead of opening the file manager (Thunar, in Xfce).


Version-Release number of selected component (if applicable):
gnome-search-tool.i686 3.4.0-1.fc17

How reproducible: always.


Steps to Reproduce:
1. Perform a search, say, in a pictures folder
2. Right-click one result and we get some options, for instance: 'Open with GIMP', 'Open with Ristretto'(Xfce image viewer), 'Open containing folder', 'Move to trash' and 'Save results as...'
3. Clicking on 'Open containing folder', instead of opening the folder in the default file manager (Thunar, in Xfce) opens the image in GIMP, which is the first option from the list.
  
Actual results:
"opens the file with the first available application for it"

Expected results:
"opens the containing folder with default file manager"

Additional info:
All the other options on the list work properly.

I'm using Xfce 4.10 from a fedorapeople repo, not 4.8 from fedora-updates.

Comment 1 Sergio 2012-10-20 22:50:07 UTC
I installed gnome-search-tool 3.6.0-1.fc18 in the Xfce live-CD (Alpha TC6) to see if the bug persisted in F18 and it doesn't even open.

[liveuser@localhost ~]$ gnome-search-tool 

** (gnome-search-tool:2133): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(gnome-search-tool:2133): GLib-GIO-ERROR **: Settings schema 'org.gnome.nautilus.preferences' is not installed

Trace/breakpoint trap (core dumped)

Comment 2 Fedora End Of Life 2013-07-04 04:02:21 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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.

Comment 3 Fedora End Of Life 2013-08-01 12:29:41 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.