Bug 88019

Summary: Links in the form of .desktop files should act as real directories file open/save dialog
Product: [Frameworks and Libraries] frameworks-kio Reporter: Gerold Strobel <gerryst>
Component: Open/save dialogsAssignee: David Faure <faure>
Status: CONFIRMED ---    
Severity: wishlist CC: bugseforuns, ce, eljefedelito, joao_neto, kdelibs-bugs, nate
Priority: NOR    
Version: 5.45.0   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Gerold Strobel 2004-08-25 11:07:01 UTC 
Version:           Unbekannt (using KDE 3.3.0, Gentoo)
Compiler:          gcc version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)
OS:                Linux (i686) release 2.6.8.1

When clicking on links to devices (e.g. a Windows partition, DVD-ROM) in the file open/save dialog, those links should be treated as links and not as simple files (like .desktop files in this example).


On the Desktop such a link would mount the device, and open a new Konqueror window.
In the file open/save dialog, the device should be mounted and its contents be displayed in the dialog.

I know there is a shortcut named "devices" in the file open/save dialog. Yet not every person new to KDE / computers may think about using that.
Comment 1 Christoph Feck 2009-08-27 02:35:52 UTC 
Moving from "kio/kfile" component to "kfile" product, helps sorting out duplicates.
Comment 2 Nate Graham 2018-04-11 19:30:03 UTC 
In KDE Frameworks 5, the "create link to device" functionality itself is in a bad state: the .desktop file it creates gets opened in Kate, not the file browser, and the original issue is still present :/ I've seen zero bugs about this before, so I have to wonder how heavily used this functionality is...
Comment 3 Nate Graham 2018-04-11 20:32:25 UTC 
*** Bug 134723 has been marked as a duplicate of this bug. ***
Comment 4 Nate Graham 2018-04-13 15:11:14 UTC 
*** Bug 59847 has been marked as a duplicate of this bug. ***
Comment 5 Nate Graham 2018-04-13 17:43:20 UTC 
*** Bug 282015 has been marked as a duplicate of this bug. ***