Hi!
When I try to boot Porteus from USB I get this error message: /home/guest/.kde4/share/config/knotifyrc was not writable. Please contact your system administrator.
Anyone can help?
[SOLVED] ~/.kde4/share/config/knotifyrc not writable
Get help with KDE specific problems
-
- Ronin
- Posts: 2
- Joined: 02 Aug 2014, 22:56
- Distribution: Porteus
- Location: Portugal
[SOLVED] ~/.kde4/share/config/knotifyrc not writable
Post#1 by JKostaRibeiro » 02 Aug 2014, 23:04
Last edited by JKostaRibeiro on 06 Aug 2014, 22:53, edited 1 time in total.
JKostaRibeiro
- Ed_P
- Contributor
- Posts: 8962
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Re: /home/guest/.kde4/share/config/knotifyrc not writable
Post#2 by Ed_P » 03 Aug 2014, 02:33
How did you write Porteus to the USB drive? Can you rewrite it? Is there a read/write switch on the USB drive? Is it in the Read only position?
Ed_P
- fanthom
- Moderator Team
- Posts: 5667
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: /home/guest/.kde4/share/config/knotifyrc not writable
Post#3 by fanthom » 03 Aug 2014, 06:56
probably knotifyrc got root's permissions somehow. you may fix that with running following command as root:
Code: Select all
chown 1000:1000 -R /home/guest
Please add [Solved] to your thread title if the solution was found.
fanthom
-
- White ninja
- Posts: 18
- Joined: 02 Aug 2014, 02:22
- Distribution: Porteus 3 and pclinuxOS
- Location: usa
Re: /home/guest/.kde4/share/config/knotifyrc not writable
Post#4 by router » 04 Aug 2014, 09:08
i had this happen when i experimented with moving my /changes folder to a different partition. i used root login to do it and i think that made some of the resulting files get inherited by root.
router
-
- Ronin
- Posts: 2
- Joined: 02 Aug 2014, 22:56
- Distribution: Porteus
- Location: Portugal
Re: /home/guest/.kde4/share/config/knotifyrc not writable
Post#5 by JKostaRibeiro » 06 Aug 2014, 16:20
Today, I installed porteus 3.0.1 and everything is running weel!
The problem was with porteus 3.0.0.
Tank you all!
The problem was with porteus 3.0.0.
Tank you all!
JKostaRibeiro