Summary: | Dolphin open the wrong path for my hard drive | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-solid | Reporter: | Crone123 <valentin> |
Component: | general | Assignee: | Lukáš Tinkl <lukas> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | a.samirh78, kdelibs-bugs, kfm-devel, meven29 |
Priority: | NOR | ||
Version: | 5.87.0 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Crone123
2021-07-17 21:36:51 UTC
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? |