From kde-core-devel Mon Jul 21 15:13:48 2008 From: Lubos Lunak Date: Mon, 21 Jul 2008 15:13:48 +0000 To: kde-core-devel Subject: Re: KDE 4.1 login fails for new user Message-Id: <200807211713.48812.l.lunak () suse ! cz> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=121665327204695 On Tuesday 15 of July 2008, David Jarvie wrote: > On Tue 15 July 2008 16:09:58 you wrote: > > On Saturday 12 July 2008, David Jarvie wrote: > > > I removed the ~/.kde directory and tried to log in using KDE 4.1 (SVN > > > yesterday). It showed the error message "Could not start > > > kstartupconfig4. Check your installation." before aborting the login. > > > The error code being returned by kstartupconfig4 was 3. Repeating the > > > login attempt resulted in the same error. > > > > > > By my reading of the code, kdostartupconfig.cpp calls > > > > > > KStandardDirs::locateLocal( "config", "startupconfigkeys" ); > > > > > > and then tries to open the resultant file name in read-only mode - > > > hence the error. When you start with an empty ~/.kde, that file won't > > > exist, so AFAICS kstartupconfig4 will inevitably return the error code > > > 3. (The directory ~/.kde/share/config was created with correct user > > > permissions, presumably by that call, so there's no problem with write > > > access.) > > > > So basically this patch should help? No, unless ignoring problems counts as helping. > Yes, the patch fixes the problem. I didn't know whether the > startupconfigkeys file should be created empty, or whether the fault should > just be ignored, as in your patch. startkde: ... # see kstartupconfig source for usage mkdir -m 700 -p $kdehome mkdir -m 700 -p $kdehome/share mkdir -m 700 -p $kdehome/share/config cat >$kdehome/share/config/startupconfigkeys <