[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: KDE 3.5.7 in unstable and yes, we're working in KDE 4!



On Wednesday 23 May 2007 19:36, Arthur Marsh wrote:
> Arthur Marsh wrote, on 2007-05-23 14:14:
> > Ana Guerrero wrote, on 2007-05-22 22:13:
> >> Hello,
> >>
> >> KDE 3.5.7 is being released today and it is already available in
> >> unstable.
> >> If you're using i386 the update should go fine, if you're using another
> >> arch, like amd64, some packages will not be available for your arch yet.
> >>
> >> If you update while you're using your desktop enviroment and you
> >> notice some strange behaviour, please restart your desktop enviroment.
> >> At the same time we have been working in kde 3.5.7, we have started to
> >> work in packaging KDE 4, and we're aiming to publish packages for the
> >> next
> >> official development snapshot.
> >>
> >> If you want to know how to contribute, take a look at our website:
> >> http://pkg-kde.alioth.debian.org/
> >>
> >> Ana
> >
> > I had major problems with my upgrade.
> >
> > After rebooting having installed kde 3.5.7-1, I would get the graphical
> > login screen, but once I logged in I was left with the blue background
> > and nothing else. The mouse moved and I could use ctrl alt F1 .. F6 and
> > ctrl alt backspace but I could not get the desktop loading.
> >
> > I finally returned to the desktop by some difficult to reproduce method
> > of copying the /var/run/xauth/* file to ~/.Xauthority attempting to
> > login via VT7 and then in a console session setting DISPLAY to ":0.0"
> > and running startkde.
> >
> > I'm at a real loss on how to go about finding the actual problem and
> > fixing things properly. Any suggestions?
> >
> > (I'm copying this into Debian bug #425526, where I reported this).
>
> I'm still no better off after purging kdm, re-installing kdm and
> dependent kde packages at Etch level (normally I run Sid), reinstalling
> hal, dbus, pam and their associated libraries. I've also tried changing
> between 2.6.20, 2.6.21 and 2.6.22 kernels to no avail.
>
> Doing a graphical login results in one or two processes of the form:
>
>
> /bin/sh /etc/kde3/kdm/Xsession /usr/bin/startkde
>
> but nothing else under my username until I login via a console session,
> set DISPLAY=":0.0", then run
>
> nohup startkde &
>
> which brings up a kde desktop session which sooner or later crashes.
>
> Please visit bugs.debian.org and enter 425526 for the details.
>
> I am eager for any more suggestions to try.

How about try moving your .kde/ to .kde.orig and try logging in again.  If 
that works, then some configuration files in your .kde are not happy with the 
upgrade.  Or you can try creating another user and logging in via that user 
and seeing if things work.  Then it is a matter of tracking down the 
offending settings in your original .kde/

John



Reply to: