Bug 188937 - Using Device Notifier to mount a previously unmounted drive opens a new Dolphin window
Summary: Using Device Notifier to mount a previously unmounted drive opens a new Dolph...
Status: CONFIRMED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: RedHat Enterprise Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
: 194982 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-04-06 03:12 UTC by Patrick O'Callaghan
Modified: 2019-02-18 15:55 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick O'Callaghan 2009-04-06 03:12:21 UTC 
Version:            (using KDE 4.2.1)
OS:                Linux
Installed from:    RedHat RPMs

If I unmount a drive using Dolphin, the window stays open. However if I use Device Notifier to remount the same drive, I get a new Dolphin window. I would prefer one of two things to happen, either a) on unmounting the drive the window should disappear, or b) on remounting the drive the now-redundant open window should be reused if still open. My personal preference is for a), but some people like to mount from Dolphin itself, so b) might be better for them. This could be a configurable option.
Comment 1 Anne Wilson 2009-04-06 19:45:42 UTC 
I agree that some resolution is needed.  I would vote for option b, because the times when I have felt the need for this have usually been while I was using a split layout.  It's not a show-stopper - I can click on the device name in the Places panel - but it is an annoyance.
Comment 2 Jeroen van Meeuwen (Kolab Systems) 2012-08-24 16:19:55 UTC 
Resetting assignee to default as per bug #305719
Comment 3 Elvis Angelaccio 2016-12-26 16:34:39 UTC 
*** Bug 194982 has been marked as a duplicate of this bug. ***
Comment 4 dufferzafar 2019-02-18 15:55:15 UTC 
Wow, its been 10 years since the bug was filed. I too expected option a to happen.