Bug 681763 - KDE application is used as file-manager on GNOME desktop
Summary: KDE application is used as file-manager on GNOME desktop
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ondrej Holy
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-03 07:41 UTC by Akira TAGOH
Modified: 2015-02-17 13:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 13:40:02 UTC
Type: ---


Attachments (Terms of Use)

Description Akira TAGOH 2011-03-03 07:41:23 UTC
Description of problem:
When clicking Places->Desktop on the fallback session in f15 Alpha, gwenview KDE application is invoked.

Version-Release number of selected component (if applicable):
gvfs-1.7.2-2.fc15

How reproducible:
always

Steps to Reproduce:
1.install f15 alpha and @kde-desktop packages
2.log in to the fallback session
3.click Places->Desktop from the panel
  
Actual results:
gwenview is invoked.

Expected results:
nautilus or any GNOME applications should be used

Additional info:
I have some applications installed that supports MimeType=inode/directory like:
$ for i in $(find /usr/share/applications -name '*.desktop'); do grep -i mime $i|grep inode/directory>/dev/null && echo $i; done
/usr/share/applications/gnome-nautilus.desktop
/usr/share/applications/kde4/dolphin.desktop
/usr/share/applications/kde4/filelight.desktop
/usr/share/applications/kde4/kfmclient_dir.desktop
/usr/share/applications/kde4/gwenview.desktop

Comment 1 Fedora End Of Life 2013-04-03 17:46:27 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 2 Fedora Admin XMLRPC Client 2013-05-23 14:36:18 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora End Of Life 2015-01-09 16:35:47 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.

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 4 Fedora End Of Life 2015-02-17 13:40:02 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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.