On Fri, Apr 20, 2012 at 06:54:24PM -0700, Linda Walsh wrote:
When I try to run yast2, I get
> sudo yast2 Error: "/var/tmp/kdecache-law" is owned by uid 5013 instead of uid 0.
--- So I think...ok...that's weird, it wants law's kdecache to be owned by root..
ok, I'm game (changed ownership)...
Then I go to do a kernel build (another kde using app)...which I usually build as normal user...
scripts/kconfig/qconf Kconfig # # using defaults found in arch/x86/configs/x86_64_defconfig # Error: "/var/tmp/kdecache-law" is owned by uid 0 instead of uid 5013. Error: "/var/tmp/kdecache-law" is owned by uid 0 instead of uid 5013. Error: "/tmp/kde-law" is owned by uid 0 instead of uid 5013. Error: "/tmp/kde-law" is owned by uid 0 instead of uid 5013.
Um....
I think yast2 is the one at fault here...
It shouldn't expect that /var/tmp/kdecache-law would be owned by other than law!... or is that just silly?
This worked on 11.4.
I think 12.1 should be declared null and void as far as moving the support dates for previous releases 'forward', since from my own experience, and others, it doesn't seem it was read to be released, yet was because "It was the date".
You likely blame openSUSE quality for something you changed on your system actually... You probably changed your sudo configuration to keep environment variables, which it is not set to do by default. This is why some KDE environment variables pass through your sudo call. WHat is in the "Defaults env...." variables in your /etc/sudoers? I bet you removed the "Defaults env_reset" line. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org