After connecting an external drive its file system mounted on /media/<LABEL> . In Dolphin and Konqueror by clicking the space bar opens the directory /media/<LABEL>. But then do "bind" directory from the /media/<label> anywhere, clicking on the menu space will open the directory that you specified when bind. In my case, after the bind /media/USB_DATA/kde-4.11/x86_64/packages to /usr/portage/packages opens the /usr/portage/packages . Most likely this is a problem not only file managers , KDE and 4.11 overall. The screenshot shows the string "/dev/sdb3 on /usr/portage/packages type ext3 (rw, nosuid, nodev, relatime, data = ordered)", but in fact implemented mount " /media/USB_DATA/kde-4.11/x86_64/packages on /usr/portage/packages type ext3 (rw, nosuid, nodev, relatime, data = ordered) ". This line is visible because in my system created a symbolic link to "/etc/mtab -> /proc/mounts", a similar problem , if there is a symbolic link instead of the normal file /etc/mtab , just a line in the output of repairs will be the same like the latter said . Reproducible: Always Steps to Reproduce: 1. Connect the external drive and mount the file system. 2. Make a bind directory, located on the file system external drive anywhere. 3. Through the menu "places" go to the file system of the drive.
Thanks for the bug report. I'm not sure if I really understand what the problem is, but since you say that this is most likely not a file manager-related problem, and you say that this is reproducible in Dolphin and Konqueor (and it seems that it's not being caused by the view engine which they both share), I'll reassign and hope that someone else understands the problem and assigns this report appropriately.
(In reply to comment #1) > Thanks for the bug report. I'm not sure if I really understand what the > problem is, but since you say that this is most likely not a file > manager-related problem, and you say that this is reproducible in Dolphin > and Konqueor (and it seems that it's not being caused by the view engine > which they both share), I'll reassign and hope that someone else understands > the problem and assigns this report appropriately. I apologize for my English. I'll try to describe the problem a little bit different way, step by step. 1. Connect usb drive to your computer. 2. Mount the file system storage means KDE. 3. Open the file manager or call the dialog open / save file. 4. Click on the drive icon in the menu places. 5. Will showed contents of the usb drive. 6. Remount a subtree drive file system somewhere else. "mount-o bind /media/<external_drive>/<folder> /mnt/external_folder" 7. Again, Open File Manager, or call the dialog open / save file. 8. Click on the drive icon in the menu places. 9. Will be shown the contents of the subtree ("/mnt/external_folder") file system USB drive and not the contents of the disk ("/media/<external_drive>"). In addition, I have set up an external drive mounted under /media, not /run/<username>/ ENV {ID_FS_USAGE} ==" filesystem ", ENV {UDISKS_FILESYSTEM_SHARED} =" 1 "
Konstantin I Hello. I apologize that I write to you to bypass the bug tracker, but I see that the bug report has remained unchanged. Here is a description of the problem right? Try to run it, the toga is clear what the problem is. ============================================================= I apologize for my English. I'll try to describe the problem a little bit different way, step by step. 1. Connect usb drive to your computer. 2. Mount the file system storage means KDE. 3. Open the file manager or call the dialog open / save file. 4. Click on the drive icon in the menu "places". 5. Will showed contents of the usb drive. 6. Remount a subtree drive file system somewhere else. "mount -o bind /media/<external_drive>/<folder> /mnt/external_folder" 7. Again, Open File Manager, or call the dialog open / save file. 8. Click on the drive icon in the menu "places". 9. Will be shown the contents of the subtree ("/mnt/external_folder") file system USB drive and not the contents of the disk ("/media/<external_drive>"). In addition, I have set up an external drive mounted under /media, not /run/<username>/ ENV {ID_FS_USAGE} ==" filesystem ", ENV {UDISKS_FILESYSTEM_SHARED} =" 1 " ============================================================= ####################################################################### ####################################################################### Hi, > Hello. > > I apologize that I write to you to bypass the bug tracker, but I see that > the bug report has remained unchanged. please note that I work on Dolphin in my very limited spare time, and that I barely have enough time to go through the bug reports which are related to Dolphin (which yours most likely isn't). Regards, Frank ####################################################################### ####################################################################### Excuse me, but yet again I write to you. You understand the problem and the steps to reproduce it? Konstantin I. ####################################################################### ####################################################################### Hi, > Excuse me, but yet again I write to you. You understand the problem and the > steps to reproduce it? no, I don't. I've never seen nor used the mount command with such options, and therefore, I have no idea if what you have reported is a bug or not. Moreover, I'm pretty sure that the behavior you've observed is not caused by any code inside Dolphin, nor by anything in kdelibs that I have any knowledge about, and therefore, I cannot help you. Please add any further information directly to the bug report, and do not send me any more private messages about this issue. Thanks. ####################################################################### ####################################################################### In Gnome, and other environments if the external drive is mounted on /media, but at least in /run/username/media, the menu "places" transition takes place wherever mounted file system drive. No matter mounted subdirectory of a file system drive anywhere or not. This is a mistake. Well, apparently you're not really using Linux, just not when you do not have to mount a subdirectory option 'bind'. mount -o bind /dev /mnt/system/dev mount -t proc none /mnt/system/proc chroot /mnt/system Your statement is absurd. This is the last post. ####################################################################### ####################################################################### Hi, I had asked you to not send me any further messages, but since you chose to ignore this, please let me respond to one of your statements. > In Gnome, and other environments if the external drive is mounted on /media, > but at least in /run/username/media, the menu "places" transition takes > place wherever mounted file system drive. > > No matter mounted subdirectory of a file system drive anywhere or not. This > is a mistake. > > Well, apparently you're not really using Linux, just not when you do not > have to mount a subdirectory option 'bind'. > > mount -o bind /dev /mnt/system/dev > mount -t proc none /mnt/system/proc > chroot /mnt/system > > Your statement is absurd. My statement was that I had never used mount with the "bind" option. I'm not really sure what's absurd about that, because I can use Linux for my everyday needs just fine without ever needing that option (BTW, about 99% of my everyday needs can be fulfilled without ever running "mount" from the command line at all). Please do not send further replies. If you do, I will not respond, but post this entire conversation in the bug report, where it belongs. Best regards, Frank ####################################################################### However, Frank, the problem remains a problem, no matter you are using any functional or not. Do not be like an ostrich bury his head in the sand and say, I know nothing, I do not need it.
Not sure if udisk2 supports bind mounts, but if it does, Solid should understand it.
(In reply to comment #4) > Not sure if udisk2 supports bind mounts, but if it does, Solid should > understand it. Thanks for the idea. I'll check your guess. Most likely it is true, in the distributions Fedora 19 and Debian is stable / testing using udisks-1. * and they do not have this problem. I only wish that kdelibs-4.1 * does not support udisks-1. * Without the patch. But on the other hand, if the problem is in udisks-2. * Then you need to write it to the developers udisks. In particular, if the problem manifests itself in other environments.
(In reply to comment #4) > Not sure if udisk2 supports bind mounts, but if it does, Solid should > understand it. Sorry, incorrect wording: "Then you need to write it to the developers udisks. In particular, if the problem manifests itself in other environments." Я имел ввиду вот это : Then I'll write about it to the developers udisks. In particular, if the problem is manifested in other environments.
(In reply to comment #4) > Not sure if udisk2 supports bind mounts, but if it does, Solid should > understand it. Unfortunately, I made a mistake in the description of actions that lead to the problem . I just set up the system after installation, so completing the user's session in the GUI . So, what's inaccuracy : the problem with the transition to the menu "Places" are reproduced if the steps above , and then make the completion of the session in the GUI . In the new session in the file manager menu "Places" to go to the file system external drive.
This bug is reported on libsolid which is the kdelibs4 version of the solid library. It is now in maintenance mode. If you think it should still be fixed in the KDE Frameworks 5 version of solid please move it to or report a bug on frameworks-solid.
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug. Please try again with the latest version and submit a new bug to frameworks-solid if your issue persists. Thank you!