SUMMARY Dolphin open the wrong hard drive when clicking on it in "devices" section. STEPS TO REPRODUCE 1. Open dolphin 2. Click on my hard drive OBSERVED RESULT The wrong path is opened: /home/valentin/Nextcloud EXPECTED RESULT Open the hard drive root: /media/hdd/lvhdd SOFTWARE/OS VERSIONS Linux/KDE Plasma: 21.04.3, on KDE Neon 5.22.3 ADDITIONAL INFORMATION In my hard drives, I have an internal drive called "lvhdd" (lvm, ext4), this is configured like this in fstab: UUID=d82cd367-694a-49e8-b6ca-8a2dbb843483 /media/hdd/lvhdd ext4 defaults,nodiratime,noatime,auto,acl,errors=remount-ro 0 0 And there is some bind mounts for convenience: /media/hdd/lvhdd /home/valentin/lvhdd none bind 0 0 /media/hdd/lvhdd/Nextcloud /home/valentin/Nextcloud none bind 0 0 /media/hdd/lvhdd/git /home/valentin/git none bind 0 0 In Dolphin, I have added theses places: Home folder: /home/valentin Desktop: /home/valentin/Bureau Documents: /home/valentin/Documents Images: /home/valentin/Images Music: /home/valentin/Musique Videos: /home/valentin/Vidéos Downloads: /home/valentin/Téléchargements Trash: trash:/ git: /home/valentin/git Nextcloud: /home/valentin/Nextcloud And, in my devices I have: Windows 10 partition / (KDE Neon Root) A shortcut to my phone with KDE Connect LVHDD (the device who have this bug), who point to /media/hdd/lvhdd, but when the bug occurs, the tooltip display "/home/valentin/Nextcloud" for this device, which is the wrong path. When I click on LVHDD, the most of the time, instead of going to /media/hdd/lvhdd, dolphin goes on /home/valentin/Nextcloud, and select it on the places. This problems happens since the latest update (5.22.3) of KDE Neon, I never expected this problems before with the same configuration. I dont know why, but this doesn't seem to bug with all devices. NFS drives are working as expected, and removable devices like SD Cards seems to work as expected to. Thank you, Valentin CRÔNE
Hello, I found today a workaround: I removed all bind mounts, and reboot. And then dolphin open the good place. I think dolphin does a misunderstanding of the fstab and select the wrong mountpoint.
It seems Solid (the library that does the hardware/fs discovery) can mis-interpret your unconventional setup. ``` And there is some bind mounts for convenience: /media/hdd/lvhdd /home/valentin/lvhdd none bind 0 0 /media/hdd/lvhdd/Nextcloud /home/valentin/Nextcloud none bind 0 0 /media/hdd/lvhdd/git /home/valentin/git none bind 0 0 ``` Mounts to sub-dirs of an already mounted drive. Why don't you use simply shortcuts to those sub-dirs ? Once `/media/hdd/lvhdd` is mounted, this is easy enough.
I don't use symlinks at first because it causes problems with some programs. My home folder is on a small SSD, and the folders on the bind mount are on a big HDD. A bind mount is a standard feature on Linux, and there is no real reason to interpret: /A/B as /C/D My shortcut was created to point to /home/valentin/Nextcloud, so, why this is reinterpreted? Why dolphin don't just open the original folder? If it does, it will work as expected... But instead, a lib says: Hey, /home/valentin/Nextcloud is /media/hdd/lvhdd (which is wrong) and Dolphin opens the wrong path. If I really want a shortcut to my other location, I can create one myself. Does this "reinterpretation feature" have a sense for user created shortcuts? If not, it can be fixed more easilly I think.. Thank you :)
This should be fixed in recent KDE Frameworks version; do you still see this issue?