Le 19 janvier 2010 11:09, Rémi Moyen <rmo...@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-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
