This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Configuration File kcmshellrc not writable

Tags: None
(comma "," separated)
User avatar
orbmiser
Registered Member
Posts
93
Karma
1
Right clicking clock adjust time & date gives

Code: Select all
kcmshell- KDialog

Configuration file "/home/orbmiser/.kde/share/config/kcmshellrc" not writable.
Please contact your system administrator



The File properties of kcmshellrc is designated Ownership User: root Group: root
Owner can Read & Write
Group Forbidden
Others Forbidden

Why am I getting this dialog? had it with 4.8.5 and still have it with 4.10.1
Any insights is appreciated.
.


User avatar
google01103
Manager
Posts
6668
Karma
25
because root is owner of the file, and you should be owner of the file

no idea how it got this way but you need to change ownership back to you

ps all file in this folder should be owned by you


OpenSuse Leap 42.1 x64, Plasma 5.x

User avatar
orbmiser
Registered Member
Posts
93
Karma
1
google01103 wrote:because root is owner of the file, and you should be owner of the file

no idea how it got this way but you need to change ownership back to you

ps all file in this folder should be owned by you


Yep all the others show orbmiser strange as never have changed file permissions thru terminal or dolphin ever.
But figured out to right-click file in dolphin and root action to ownership of active users seems to do the trick.

I figured I would need to do that but wanted to check first if this was normal permissions? and just a bug?
Tho curious who as in app,plasmoid or system event that changed those permissions.
.


User avatar
google01103
Manager
Posts
6668
Karma
25
if you use sudo instead of using kdesudo you can mess up your file permissions because (iirc) sudo will run as root using your (not it's) environmental variables which means that any file it affects it takes owner of, while running kdesudo it runs as root using it's own environmental variables. The environmental variable used affect thinks like the location of home and therefore config files. If you Google you'll probably find a more coherent explanation.


OpenSuse Leap 42.1 x64, Plasma 5.x

User avatar
orbmiser
Registered Member
Posts
93
Karma
1
google01103 wrote:if you use sudo instead of using kdesudo you can mess up your file permissions because (iirc) sudo will run as root using your (not it's) environmental variables which means that any file it affects it takes owner of, while running kdesudo it runs as root using it's own environmental variables. The environmental variable used affect thinks like the location of home and therefore config files. If you Google you'll probably find a more coherent explanation.


So how does that apply with Dolphin Action? Is the right click dolphin action kdesudo? or sudo?

Which I don't know why but my system clock is set to manually set and on reboot clock resets to UTC?

Code: Select all
sudo hwclock --debug
[sudo] password for orbmiser:
hwclock from util-linux 2.20.1
Using /dev interface to clock.
Last drift adjustment done at 1363125161 seconds after 1969
Last calibration done at 1363125161 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2013/03/12 21:57:14
Hw clock time : 2013/03/12 21:57:14 = 1363125434 seconds since 1969
Tue 12 Mar 2013 09:57:14 PM UTC  -0.625621 seconds


So getting real confused on this whole Time setting thing. As can't use NTP servers as they return wrong time +7 hrs? even tho have Los Angeles PST selected. Bios & Win 7 has right date & time but KDE seems to not want to stick with what others are set at.

The date command
orbmiser@Winterfell ~ $ date
Wed Mar 13 05:04:59 UTC 2013
Which is 7hrs ahead of hardware clock which is correct time and both stating UTC so am confused.


User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
I would suggest using your distribution tools (such as openSUSE's YaST) to set the system timezone and clock.

If you are dual booting with Windows, you probably want to uncheck "Clock is set to UTC time" or the equivalent, as Windows always sets the hardware clock to the local time, whilst the Linux default is for UTC time usually.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]


Bookmarks



Who is online

Registered users: Bing [Bot], daret, Google [Bot], Sogou [Bot]