Bug 308301 - Dolphin should show devicenames (/dev/sdXY)
Summary: Dolphin should show devicenames (/dev/sdXY)
Status: RESOLVED DUPLICATE of bug 307883
Alias: None
Product: dolphin
Classification: Applications
Component: panels: places (other bugs)
Version First Reported In: 2.1
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-12 18:18 UTC by Franky
Modified: 2012-10-20 01:05 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Franky 2012-10-12 18:18:30 UTC
This is something i miss in dolphin very much. As Example: i am using two Harddrives, one IDE and one SATA Harddrive. Because of this, sometimes is the SATA harddrive mounted on /dev/sdA, after a Reboot, the IDE hardrive is /dev/sdA and the SATA hardrive is mounted on /dev/sdB. This seems to be an issue by the kernel.

So sometimes it is really confusing, because i do not now, wich Partition i see in Dolphin. 

The only thing i could do, is to mark every Partition with an appropritae label. But if the devicenames are shown, it would be nicer.

Maybe its possible to  make an Entry "Property" in the contextmenü of the places/devices panel, where we find the devicenames (/dev/sdXY)?

Reproducible: Always

Actual Results:  
No Devicenames (/dev/XY) are shown.

Expected Results:  
The devicename of a partition should somewhere shown
Comment 1 Frank Reininghaus 2012-10-18 17:16:30 UTC
Thanks for the report. This looks somewhat related to bug 307883.
Comment 2 Franky 2012-10-19 16:59:10 UTC
Oh, havn't found this report, because i searched for Dolphin...

Yes, if the Places-Panel in Dolphin is the same Code-snippet as in the File open-Dialog, these two reports belong together.

If so, you could close this Bug or mark it as duplicate with https://bugs.kde.org/show_bug.cgi?id=307883

Thanky for your reply.
Comment 3 Jekyll Wu 2012-10-20 01:05:46 UTC

*** This bug has been marked as a duplicate of bug 307883 ***