From kde-core-devel  Tue Jul 15 21:32:11 2008
From: David Jarvie <djarvie () kde ! org>
Date: Tue, 15 Jul 2008 21:32:11 +0000
To: kde-core-devel
Subject: Re: KDE 4.1 login fails for new user
Message-Id: <200807152232.18670.djarvie () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=121615750824656
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1253362.GOzALGroRo"

--nextPart1253362.GOzALGroRo
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

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 kstartupconfig=
4.
> > Check your installation." before aborting the login. The error code bei=
ng
> > 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?
>
> --- kdostartupconfig.cpp        (revision 829274)
> +++ kdostartupconfig.cpp        (working copy)
> @@ -80,6 +80,8 @@ int main( int argc, char **argv )
>      kDebug() << "Running kdostartupconfig.";
>      KCmdLineArgs::init( argc, argv, &about ); // for KLocale not to
> complain about encoding QString keysname =3D KStandardDirs::locateLocal(
> "config", "startupconfigkeys" ); +    if (!QFile::exists(keysname))
> +        return 0; // nothing to do
>      QFile keys( keysname );
>      if( !keys.open( QIODevice::ReadOnly ))
>          return 3;

Yes, the patch fixes the problem. I didn't know whether the startupconfigke=
ys=20
file should be created empty, or whether the fault should just be ignored, =
as=20
in your patch.

=2D-=20
David Jarvie.
KAlarm author and maintainer.
http://www.astrojar.org.uk/kalarm

--nextPart1253362.GOzALGroRo
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBIfRdiTGZ1gSTAjlMRAo1SAJ9V3FOmWUTCLKvC6ypqlcWyF6Nc9gCgrXAf
38FqcdhXb1MQXdTxTDFh61U=
=9DTl
-----END PGP SIGNATURE-----

--nextPart1253362.GOzALGroRo--