I have two different Linux operating systems (on two separate partitions) on my laptop. One is open SUSE and the second is PCLinuxOS and I frequently have to update files and folders from one to the other (the consequences of trying to keep both current!). When I am using openSUSE and want to access folders/files on the other OS, openSUSE asks for SU authorisation to access the other . . ./home file. Until recently, I could open ALL of the folders on the (other) /home file but now I can open some folders but not others. The Dolphin screen shows a warning at the bottom that "Could not enter folder /media… " ! I can then only access the folder by going into the menu and using the ‘File manager -Super User’ mode …AGAIN.
I suspect this action is necessary because I have had to previously open these specific folders in ‘Root mode’ to be able to ‘paste’ the moved file!
I would like to avoid this (double) ‘messy’ action - can you help me with some advice on how to change/avoid this
My system is a 32bit openSUSE 11.4 with KDE 4.6.0 and the 2nd OS is also KDE 4.6
On occasion, I’ve had this happen mid-session when Dolphin crashes while attempting to browse files from my digital camera, or SD card say, but I haven’t experienced this with internal disk partitions. In my case, I’ve found that restarting the desktop will correct the situation. (You might want to configure KDE to start with an empty session too). Anyway, it might also be a good idea to check your policy settings via
System Settings>>Actions Policy>>org.freedesktop>>The udisks Project>>… (you’ll need to enter your root password)
I have two different Linux operating systems (on two separate partitions) on my laptop. One is open SUSE and the second is PCLinuxOS and I frequently have to update files and folders from one to the other (the consequences of trying to keep both current!). When I am using openSUSE and want to access folders/files on the other OS, openSUSE asks for SU authorisation to access the other . . ./home file. Until recently, I could open ALL of the folders on the (other) /home file but now I can open some folders but not others. The Dolphin screen shows a warning at the bottom that "Could not enter folder /media… " ! I can then only access the folder by going into the menu and using the ‘File manager -Super User’ mode …AGAIN.
I suspect this action is necessary because I have had to previously open these specific folders in ‘Root mode’ to be able to ‘paste’ the moved file!
I would like to avoid this (double) ‘messy’ action - can you help me with some advice on how to change/avoid this
My system is a 32bit openSUSE 11.4 with KDE 4.6.0 and the 2nd OS is also KDE 4.6
Thanks w.
I would ask how are you mounting the other OS partition? If you add it to your fstab file, you can control who can access that partition and with what privileges. If it has been added, can you post a copy here for us to see?
I do not want to do that because - 1.I frequently change the 2nd. OS on the partition and - 2. I am not sure that I have the knowledge (or confidence) to do it and get it right !
I appreciate your suggestion however because it raised an option that I would not have thought of. Although I don’t know the “how”, I understand the “why”.
Thanks for the suggestion, I have checked and made some changes to the ‘Systems Settings - action policy…’ it is possible that because I am not familiar with the various ‘policy’ options, I am not changing the correct references however, anyway, I have been unable to change the status of being able to open the folders/files ie. I still have to open some folders with dolphin- su (root).
Shutting down kde and re-starting also makes no difference.
This issue is not a ‘life-changer’ but it is irritating and confounds me as to why I can open and use 11 of 14 folders but just 3 other specific ones that need su authority each time!!
I would welcome any other suggestions you may have,thanks again for your attention.
w.
You can also get to the settings via the device notifier - right-click click on device notifier icon. Something else to try: Create another user account with YaST, then log in to that account, and see whether the same issue exists.
Thanks deano, I did not consider these, so I tried both, but did not change the results - ie the other OS files that wouldn’t open, still will not open. I suspect the problem does relate to an attribute in the ‘Action policies’ - I need to check these further to find the solution.