![]() Registered Member ![]()
|
I tried to install KDE 4 into /opt/kde. I followed the instructions from BLFS. Now I am getting this error : "Unable to save bookmarks in /opt/kde/share//user-places.xbel. Reported errror was: Insufficient permissions in target directory.. This error message will only be shown once. The cause of the error needs to be fixed as quickly as possible which is most likely a full hard drive."
I am now using Plasma 5, I thought I could install KDE 4 along with Plasma 5. I made a symlink from /opt/kde to $HOME/.local and everything is loading fine. Why is /opt/kde read instead of $HOME/.local ? |
![]() Registered Member ![]()
|
It is okay, it was caused by some environment variable.
|
![]() Registered Member ![]()
|
which was . . . ? |
![]() Registered Member ![]()
|
I'm running Linux Mint KDE 18.1 Plasma and I'm seeing this error message:
I have a 2TB hard drive with 'oodles' of space so I doubt disk space is my problem. I have checked my permission for the /home/me/.local/share/ and chmod -R to 755 which now shows my permissions as:
I'm new to KDE (not Linux) and from googleing the subject this seems to be a recurring issue. Anyone have any idea how I resolve this, only appears to be happening with KDE apps? |
![]() Registered Member ![]()
|
OK I seem to have filed this now by changing ownership from root to me as follows:
Note: substitute /me/ for your username. |
![]() Registered Member ![]()
|
chown doesn't solve the problem; after a few hours, the file is back in root's ownership.
|
![]() Registered Member ![]()
|
You should also ensure there isn't a stray root process which is also updating the file in the background and changing the owner on it.
airdrik, proud to be a member of KDE forums since 2008-Dec.
|
![]() Registered Member ![]()
|
There is no other process updating the file. I have tried adding sudo to the startup application command, no difference.
The warning dialogue says it's only going to display once, and it then displays 10 times. I've tried using the audit logging tool to see which process is accessing the file, and according to that, the file is not being accessed! Maybe because of the error, that is true. Screenshot of multiple error reports: https://pasteboard.co/I9Yd8U0.png |
![]() Registered Member ![]()
|
Another option you can try is to leave it owned by root, but grant public read/write permission:
Unless whatever it is that is updating the owner to root is also resetting the permission bits that should at least satisfy whatever else is trying to access it. You might also file a bug to bugs.kde.org as the devs may have better ideas or suggestions.
airdrik, proud to be a member of KDE forums since 2008-Dec.
|
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]