Well, one of them does. Not sure if this is one for KDE or not either. Left hand panel “Devices” usually picks up your partitions and external devices, etc, right. Like mine picks up everything as it should including Root and Home and the Windows partition. When you click on the root partition it shows /var/tmp/ instead of… root. How do you ‘re-point’ it to root?
Thanks.
Use the “Arrow” at the top (2 clicks & click on root folder)
BTW, if I am going to make changes that I want to keep, I always start from a root terminal.
Thanks. Even in root every time I click the ‘Go Up’ arrow once it jumps up to the red root folder under ‘Places’ but ‘Devices’ location for root stays the same. I don’t see a visible way to make it stick though.
You should be able to edit the path of the “Places” entry by right-clicking on it.
Never seen anything like this though.
Where exactly do you click on? Maybe post a screen shot.
Do you click on the partition below “Devices” or on “Root Folder” below “Places”?
Under ‘Devices’ click on “Suse Root Btrfs” and it should show / but as you can see shows /var/tmp/ as default.
http://s21.postimg.org/kxvansqeb/snapshot1.jpg](http://postimg.org/image/kxvansqeb/)
Click the Up arrow and it jumps to the red root folder under “Places” but it’s now /var/ and no /tmp
http://s16.postimg.org/64yxava9t/snapshot2.jpg](http://postimg.org/image/64yxava9t/)
Click arrow again and we arrive at /
http://s23.postimg.org/i8kk250dz/snapshot3.jpg](http://postimg.org/image/i8kk250dz/)
Question is; how do I get Devices >> “Suse Root Btrfs” = / by simply clicking it??
Ok, it’s probably getting confused by the subvolumes of your btrfs filesystem (/var/tmp is one of them IIRC).
I cannot test this at the moment because I’m not using btrfs here on this system.
Question is; how do I get Devices >> “Suse Root Btrfs” = / by simply clicking it??
Why don’t you just click on the red “Root” folder below “Places” instead?
That’s intended to navigate you to /.
You can also jump to / in the “breadcrumb” navigation bar, by clicking on it.
Don’t get me wrong there’s no problem accessing root any other way, it’s not an issue as such. I just wanted to know how to change that location under Devices because if you right click for “Add Entry” it gives every option but won’t let you choose / . Every KDE install I’ve ever had has always allowed you to access / through Devices, I just wondered why that had changed here.
You can’t.
dolphin (actually this panel is part of kdelibs) gets this path from solid, which in turn akss udisks2 about the drives/partitions.
Apparently something goes wrong there.
What does “solid-hardware details /org/freedesktop/UDisks2/block_devices/sda1” say? (replace /dev/sda1 with the device name of your root partition)
In particular the “StorageAccess.filePath” entry.
And “udisksctl info /dev/sda1”?
Here the “MountPoints” would be interesting.
Every KDE install I’ve ever had has always allowed you to access / through Devices, I just wondered why that had changed here.
Nothing has changed here. It still works fine on my system with reiserfs as root.
As I said, KDE or udisks2 might get confused by the subvolumes of your btrfs root filesystem.
Probably a bug somewhere. I think I read something about a similar problem in the KDE forums.
Try to remove/comment out the entries from /etc/fstab and reboot as a test. But I’m not sure whether this would give other problems or not.
So that’s on your own risk.
Sorry for the delay. It’s definitely a Btrfs thing btw, happens on TW and 13.2.
StorageAccess.filePath = ‘/var/tmp’ (string)
The udisksctl info tells me it requires one of these options
-p, --object-path >> Object to get information about
-b, --block-device >> Block device to get information about
-d, --drive >> Drive to get information about
and none work for me. 
Well, this does not happen on my 13.2 system with btrfs as root (no separate /home btw.).
StorageAccess.filePath = ‘/var/tmp’ (string)
Ok, so this is where dolphin gets it from, obviously.
The udisksctl info tells me it requires one of these options
-p, --object-path >> Object to get information about
-b, --block-device >> Block device to get information about
-d, --drive >> Drive to get information about
and none work for me.
Yeah, sorry.
It should have been “udisksctl info -b /dev/sda1”.
Also not happening here on Tumbleweed with root on btrfs and /home included.
That’s Btrfs Root (sda5)
linux-d6i9:/home/me # udisksctl info -b /dev/sda5
/org/freedesktop/UDisks2/block_devices/sda5:
org.freedesktop.UDisks2.Block:
Configuration: ('fstab', {'fsname': <b'UUID=ccdb1061-67b6-4f3a-8a64-ac1c6fce04d5'>, 'dir': <b'/'>, 'type': <b'btrfs'>, 'opts': <b'defaults'>, 'freq': <0>, 'passno': <0>}), ('fstab', {'fsname': <b'UUID=ccdb1061-67b6-4f3a-8a64-ac1c6fce04d5'>, 'dir': <b'/boot/grub2/i386-pc'>, 'type': <b'btrfs'>, 'opts': <b'subvol=boot/grub2/i386-pc'>, 'freq': <0>, 'passno': <0>}), ('fstab', {'fsname': <b'UUID=ccdb1061-67b6-4f3a-8a64-ac1c6fce04d5'>, 'dir': <b'/boot/grub2/x86_64-efi'>, 'type': <b'btrfs'>, 'opts': <b'subvol=boot/grub2/x86_64-efi'>, 'freq': <0>, 'passno': <0>}), ('fstab', {'fsname': <b'UUID=ccdb1061-67b6-4f3a-8a64-ac1c6fce04d5'>, 'dir': <b'/opt'>, 'type': <b'btrfs'>, 'opts': <b'subvol=opt'>, 'freq': <0>, 'passno': <0>}), ('fstab', {'fsname': <b'UUID=ccdb1061-67b6-4f3a-8a64-ac1c6fce04d5'>, 'dir': <b'/srv'>, 'type': <b'btrfs'>, 'opts': <b'subvol=srv'>, 'freq': <0>, 'passno': <0>}), ('fstab', {'fsname': <b'UUID=ccdb1061-67b6-4f3a-8a64-ac1c6fce04d5'>, 'dir': <b'/tmp'>, 'type': <b'btrfs'>, 'opts': <b'subvol=tmp'>, 'freq': <0>, 'passno': <0>}), ('fstab', {'fsname': <b'UUID=ccdb1061-67b6-4f3a-8a64-ac1c6fce04d5'>, 'dir': <b'/usr/local'>, 'type': <b'btrfs'>, 'opts': <b'subvol=usr/local'>, 'freq': <0>, 'passno': <0>}), ('fstab', {'fsname': <b'UUID=ccdb1061-67b6-4f3a-8a64-ac1c6fce04d5'>, 'dir': <b'/var/crash'>, 'type': <b'btrfs'>, 'opts': <b'subvol=var/crash'>, 'freq': <0>, 'passno': <0>}), ('fstab', {'fsname': <b'UUID=ccdb1061-67b6-4f3a-8a64-ac1c6fce04d5'>, 'dir': <b'/var/lib/mailman'>, 'type': <b'btrfs'>, 'opts': <b'subvol=var/lib/mailman'>, 'freq': <0>, 'passno': <0>}), ('fstab', {'fsname': <b'UUID=ccdb1061-67b6-4f3a-8a64-ac1c6fce04d5'>, 'dir': <b'/var/lib/named'>, 'type': <b'btrfs'>, 'opts': <b'subvol=var/lib/named'>, 'freq': <0>, 'passno': <0>}), ('fstab', {'fsname': <b'UUID=ccdb1061-67b6-4f3a-8a64-ac1c6fce04d5'>, 'dir': <b'/var/lib/pgsql'>, 'type': <b'btrfs'>, 'opts': <b'subvol=var/lib/pgsql'>, 'freq': <0>, 'passno': <0>}), ('fstab', {'fsname': <b'UUID=ccdb1061-67b6-4f3a-8a64-ac1c6fce04d5'>, 'dir': <b'/var/log'>, 'type': <b'btrfs'>, 'opts': <b'subvol=var/log'>, 'freq': <0>, 'passno': <0>}), ('fstab', {'fsname': <b'UUID=ccdb1061-67b6-4f3a-8a64-ac1c6fce04d5'>, 'dir': <b'/var/opt'>, 'type': <b'btrfs'>, 'opts': <b'subvol=var/opt'>, 'freq': <0>, 'passno': <0>}), ('fstab', {'fsname': <b'UUID=ccdb1061-67b6-4f3a-8a64-ac1c6fce04d5'>, 'dir': <b'/var/spool'>, 'type': <b'btrfs'>, 'opts': <b'subvol=var/spool'>, 'freq': <0>, 'passno': <0>}), ('fstab', {'fsname': <b'UUID=ccdb1061-67b6-4f3a-8a64-ac1c6fce04d5'>, 'dir': <b'/var/tmp'>, 'type': <b'btrfs'>, 'opts': <b'subvol=var/tmp'>, 'freq': <0>, 'passno': <0>}), ('fstab', {'fsname': <b'UUID=ccdb1061-67b6-4f3a-8a64-ac1c6fce04d5'>, 'dir': <b'/.snapshots'>, 'type': <b'btrfs'>, 'opts': <b'subvol=.snapshots'>, 'freq': <0>, 'passno': <0>})]
CryptoBackingDevice: '/'
Device: /dev/sda5
DeviceNumber: 2053
Drive: '/org/freedesktop/UDisks2/drives/WDC_WD5003AZEX_0_WD_WCC3F3017341'
HintAuto: false
HintIconName:
HintIgnore: false
HintName:
HintPartitionable: true
HintSymbolicIconName:
HintSystem: true
Id: by-id-ata-WDC_WD5003AZEX-00MK2A0_WD-WCC3F3017341-part5
IdLabel: oS Root BtrFS
IdType: btrfs
IdUUID: ccdb1061-67b6-4f3a-8a64-ac1c6fce04d5
IdUsage: filesystem
IdVersion:
MDRaid: '/'
MDRaidMember: '/'
PreferredDevice: /dev/sda5
ReadOnly: false
Size: 86114304000
Symlinks: /dev/disk/by-id/ata-WDC_WD5003AZEX-00MK2A0_WD-WCC3F3017341-part5
/dev/disk/by-id/scsi-0ATA_WDC_WD5003AZEX-0_WD-WCC3F3017341-part5
/dev/disk/by-id/scsi-1ATA_WDC_WD5003AZEX-00MK2A0_WD-WCC3F3017341-part5
/dev/disk/by-id/scsi-350014ee209eda2b8-part5
/dev/disk/by-id/scsi-SATA_WDC_WD5003AZEX-0_WD-WCC3F3017341-part5
/dev/disk/by-id/scsi-SATA_WDC_WD5003AZEX-_WD-WCC3F3017341-part5
/dev/disk/by-id/wwn-0x50014ee209eda2b8-part5
/dev/disk/by-label/oS\x20Root\x20BtrFS
/dev/disk/by-path/pci-0000:00:1f.2-ata-1.0-part5
/dev/disk/by-uuid/ccdb1061-67b6-4f3a-8a64-ac1c6fce04d5
org.freedesktop.UDisks2.Filesystem:
MountPoints: /var/tmp
/var/spool
/var/opt
/var/log
/var/lib/pgsql
/var/lib/named
/var/lib/mailman
/var/crash
/usr/local
/tmp
/srv
/opt
/boot/grub2/x86_64-efi
/boot/grub2/i386-pc
/.snapshots
/
org.freedesktop.UDisks2.Partition:
Flags: 0
IsContained: true
IsContainer: false
Name:
Number: 5
Offset: 189191421952
Size: 86114304000
Table: '/org/freedesktop/UDisks2/block_devices/sda'
Type: 0x83
UUID: 00096793-05
Hm, I just noticed that I can indeed reproduce the problem in my Tumbleweed VM.
The underlying cause seems clear:
Apparently solid (KDE’s hardware abstraction layer) seems to just take the first entry of this list, which is in fact “/var/tmp”.
Unfortunately I don’t see a way to fix or workaround this at the moment. E.g. rearranging the /etc/fstab had no effect.
So that’s probably worth a KDE bug report. Solid probably should take the last entry instead of the first one, shouldn’t be hard to change. But the question is whether the correct one to take will always be the last…
Hm.
OTOH, maybe udisks2 should sort those MountPoints differently, i.e. / at the top, so it might be seen as bug there. I don’t know.
This is probably an issue nobody really thought about yet, as normally you only have one mount point per partition.
I’ll stick a bug report in later today. Thanks again.
Btw, a similar issue is discussed here:
https://forum.kde.org/viewtopic.php?f=225&t=122802
And meanwhile I also found the likely relevant difference between my two systems (the 13.2 one where I don’t see the problem, and the Tumbleweed VM where I can reproduce it):
The Tumbleweed VM has entries in the fstab for each subvolume, whereas my 13.2 system doesn’t (this was actually a 13.1 installation ugraded via “zypper dup”).
So you could try to remove (or comment out) all the subvolumes in /etc/fstab to “fix” it. Those entries should not really be necessary anyway I think.