kdm not working after upgrade from KDE 3.5 to 4.3.4
in [Debian]
|
From: Jens Van Broeckhoven on 19 Jan 2010 10:20 On Tuesday 19 January 2010 12:45:27 Thierry Chatelet wrote: > On Tuesday 19 January 2010 12:09:47 Rémi Moyen wrote: > > Hi all, > > > > (this is my first post on this list, please excuse me if I make any > > mistakes...) > > > > I have a Debian testing system on which for a long time I kept old KDE > > 3.5 packages because I didn't want KDE 4 (I tried it around 4.0, > > didn't like), I figured it was time I gave it another try. So after an > > aptitude update, I did an aptitude dist-upgrade (something I hadn't > > done since at least 6-12 months -- I did a number of updates of > > specific packages in the mean time, though). > > > > aptitude offered me a solution which required removing a lot of > > packages (old KDE 3.5 ones), installing a lot of new ones, and > > updating some. The install went fine, without any error messages. I > > now have a bunch of KDE 4.3.1 packages (version 4:4.3.4-1, the latest > > in squeeze). > > > > I rebooted, got to the kdm welcome screen, obviously in KDE 4 style, > > and logged in... only to see kdm pop again! No error message. I'm not > > on this computer right now, but there wasn't any error message (nor > > anything that looked even remotely related) in /var/log/kdm.log. In > > the console, though, I can see when launching kdm some messages (sorry > > for not having copied down the exact formulation) along the line of > > "cannot copy file /etc/kde4/kdm/Xsession". > > This is a bug in kdm squeeze and sid. You have to log twice and it will > work. Thierry > For me, KDE didn't boot using KDM at all (most likely a security setting). However, KDM has an option to login without X and startx still works (no solution but good enough for me till everything is fixed). Jens. -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Michael Biebl on 19 Jan 2010 10:50 Thierry Chatelet wrote: > This is a bug in kdm squeeze and sid. You have to log twice and it will work. > Thierry This was actually an issue with consolekit and fixed consolekit packages are in unstable and will transition to testing in a few days. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
From: Rémi Moyen on 19 Jan 2010 17:50 Le 19 janvier 2010 11:09, Rémi Moyen <rmoyen(a)gmail.com> a écrit : > I rebooted, got to the kdm welcome screen, obviously in KDE 4 style, > and logged in... only to see kdm pop again! No error message. OK, I've got a bit more news, and that's not good news... First, about the missing files, I once more removed all KDE related packages, this time with --purge, and reinstalled. I don't know why, but this correctly unpacked all the files (in /etc/kde4/kdm). So at least that's one point fixed. But that's the only one... I tried to log in more than once (and more than twice, even!), it still doesn't work. So I don't think I'm affected by the afore-mentioned bug. I tried installing consolekit/unstable (since Michael Biebl indicated that the newest version fixes this bug), and I still have the problem. I tried installing xdm to replace kdm, xdm has the same problem (with both consolekit testing or unstable). I installed another window manager (IceWM) and chose it in the kdm options, still the same problem. Finally, I managed to launch xinit + icewm manually, and this works fine. I then tried, instead of launching icewm, to launch startkde (since it seems that's what .xsession would launch normally). I get the following messages: Rate 50.0 Hz not available for this size startkde: Starting up... kdeinit4_wrapper: Warning: connect(/home/remi/.kde/socket-laputa/kdeinit4__0) failed: : Connection refused Segmentation fault (core dumped) startkde: Shutting down... kdeinit4_wrapper: Warning: connect(/home/remi/.kde/socket-laputa/kdeinit4__0) failed: : Connection refused Error: Can not contact kdeinit4! startkde: Running shutdown scripts... startkde: Done. OK, I guess starting KDE requires more than calling startkde (but what else?). I tried calling kdeinit, it finishes immediately (but that could be normal if it's running as a daemon), and startkde still tells me "Communication error with KInit" and then another message "startkde: Could not start ksmserver. Check your installation.". ksmserver core dumps when I try launching it manually (but again, at that point, I'm not really expecting things to work manually). So my X server is working fine, but there is a problem with kdm (independently of the window manager I use), and there is a problem with KDE itself (?). Anyone got any clue as to what I could do? (I'm also unfortunately stuck with KDE 4 now, because when I tried to downgrade to kde/stable aptitude crashed, complaining about kdelibs4c2a depending on libkrb53 that it couldn't find, and downgrading manually libkrb53 seems to pull down an awful lot of things -- at this rate, I'm better off reinstalling the system from scratch, at least it would be clean...) -- Rémi Moyen -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: coldsun01 on 23 Jan 2010 17:50 I obviously have the same problem. When I launch startkde, I've got this problem : startkde: Starting up... kdeinit4_wrapper: Warning: connect(/home/fflorent/.kde/socket-monpc/kdeinit4__0) failed: : Connection refused /usr/bin/startkde: line 410: 7259 Erreur de segmentation kwrapper4 ksmserver $KDEWM startkde: Shutting down... kdeinit4_wrapper: Warning: connect(/home/fflorent/.kde/socket-monpc/kdeinit4__0) failed: : Connection refused Error: Can not contact kdeinit4! startkde: Running shutdown scripts... startkde: Done. It seems to be caused by an segmentation fault from ksmserver ... I also tried to reinstall all of my kde packages, that doesn't solve my problem. I have tried to log in many times as suggested on this thread : the problem's still here. But unlike R�my, I was on kde 4.3. I upgraded the packages yesterday. cheers, Florent -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
First
|
Prev
|
Pages: 1 2 Prev: problems using wicd on WPA2 secured networks Next: Warning: "Illegal" hostnames no longer work |