Bug 659998

Summary:	setting file "/root/.kde4/share/config/kdedrc" isn't writeable Contact the system administrator
Product:	[openSUSE] openSUSE 11.4	Reporter:	Forgotten User vs5edErKRK <forgotten_vs5edErKRK>
Component:	KDE4 Applications	Assignee:	E-mail List <kde-maintainers>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Minor
Priority:	P3 - Medium	CC:	bitdealer, bugreports, ctrippe, melchiaros, publio.escipion.el.africano, wstephenson
Version:	RC 2
Target Milestone:	---
Hardware:	x86-64
OS:	SUSE Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	a screenshot of the popup(german language)

Description Forgotten User vs5edErKRK 2010-12-16 19:21:43 UTC

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; sv-SE; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13

When I for the first time open File Manager - Super User Mode I get an error message which is translated from Swedish that says: setting file "/root/.kde4/share/config/kdedrc" isn't writeable Contact the system administrator

Reproducible: Always

Steps to Reproduce:
1.Istall Milestone 5 x86_64 with KDE desktop
2.log in as user.
3.open File Manager - Super User Mode and enter root password.
Actual Results:  
it says: setting file "/root/.kde4/share/config/kdedrc" isn't writeable Contact the system administrator

Expected Results:  
Dolphin should have opened the directory

Installed Milestone 5 with Virtualbox on a Windows host.

Comment 1 Christian Trippe 2011-01-04 17:52:35 UTC

I can reproduce this with a fresh install of Milestone 5.

Comment 2 Will Stephenson 2011-02-09 13:17:57 UTC

Only happens on the first run, after that the files are created.

Comment 3 Christian Trippe 2011-02-11 18:37:17 UTC

*** Bug 671145 has been marked as a duplicate of this bug. ***

Comment 4 Rainer Hurtado Navarro 2011-02-20 06:53:27 UTC

It is still present.
dom feb 20 06:52:45 UTC 2011

"(changed during the 2011-02-20 Open-Bugs-Day about bugs for obsolete versions of openSUSE)"

Comment 5 Rainer Hurtado Navarro 2011-02-20 06:57:48 UTC

Sorry for the following, but the 3 windows piled one over other.
In fact, there were 3 messages:
1. "Setting file <</root/.kde4/share/config/kdedrc>> isn't writable. Contact
the system administrator"
2. "Setting file <</root/.kde4/share/config/knotifyrc>> isn't writable. Contact
the system administrator"
3. "Setting file <</root/.kde4/share/config/dolphinrc>> isn't writable. Contact
the system administrator"

"(changed during the 2011-02-20 Open-Bugs-Day about bugs for obsolete versions
of openSUSE)"

Comment 6 Rainer Hurtado Navarro 2011-02-20 16:37:42 UTC

Let me state something I have checked: this bug just occurs during a fresh installation, because if /root existed, as if it were the case of an OS update, there will be no issue.
It might be reproduced in an updated Os by
mv /root /root2
mkdir /root
"(changed during the 2011-02-20 Open-Bugs-Day about bugs for obsolete versions
of openSUSE)"
dom feb 20 16:37:31 UTC 2011

Comment 7 Rainer Hurtado Navarro 2011-03-05 22:12:58 UTC

Persists in 11.4 RC2
(upgrade scheme 11.2 > 11.4 RC 1 > 11.4 RC 2)
N. B.: I omitted to say that I just not only mkdir root and leave empty, but I also take the files and directories from /etc/skel to fill the new root.
However, empty or just filled with /etc/skel, this issue still takes place in RC2, except if there were a previous root KDE settings.

Comment 8 melchiaros melchiaros 2011-05-02 14:45:00 UTC

I´ve got the same problem with a openSUSE 11.4 final, in which I switched to tumbleweed standard repro and the 2.6.38 kernel.

It is running in VirtualBox4.0.6 so when there is interest I can make a export of the virtual machine and provide it to you.
It´s a 64bit guest, so you need hardware virtualisation abilities on you CPU.
A screen shot(german language) will be added.

Comment 9 melchiaros melchiaros 2011-05-02 14:47:36 UTC

Created attachment 427552 [details]
a screenshot of the popup(german language)

Comment 10 Christian Trippe 2013-01-21 09:05:30 UTC

I've never seen this with 12.1 or later, assuming it is fixed. If you still can reproduce it please reopen.