You are not logged in.
My KDE installation refuses to start after recent upgrades. I get to the KDM login manager, and after I enter password, the screen goes blank for a while and then I get back to KDM. I never see, even for a few seconds, KDE familiar startup icons (disk, etc).
I can successfully start other desktop environments (I am in razor-qt right now), but I'd like to get back to my familiar KDE. I searched the forums, but there seems to be nothing recent. There is old thread, referenced in the wiki KDE page, that suggests disabling compositing in /home/user/.kde4/share/config/kwinrc. I tried that and it had no effect.
Neither journalctl nor X11's log seem to report problems. But I am not really sure what I should be looking for.
Any suggestion?
I am running the proprietary nvidia driver.
Cheers,
Stefano
Offline
Anything interesting in kdm.log?
Offline
Hmm, I hadn't thought of kdm.log. There are a couple of lines that may point to the problem:
klauncher(1154) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
However, I have no idea why the DBUS server would not have been started.
Stefano
Offline
Further info:
1. In light of the output from kdm.log my problem seems to be similar to this one: https://bbs.archlinux.org/viewtopic.php?id=168923 which, hower, is not solved either.
2. Once I log into qt-razor, I have dbus running:
[stefano@gorgias ~]$ systemctl -a | grep bus
dbus.service loaded active running D-Bus System Message Bus
dbus.socket loaded active running D-Bus System Message Bus Socket
So the problems may be that kde does not correctly start the dbus service?
Offline
does same thing happen with another user, or if you backup your ~/.kde4 and start with fresh session?
Offline
Bingo! With a fresh sessions (.kde4 backed up) KDE now starts. It's not that useful, though, without my personal settings. Any idea on how to hunt down the source of the problem? There are a gazillion files in kde4/share..
Offline
Bisect... copy half the config files to your new user and test: if it works move half the remaining ones, if it doesn't remove half of them... and so on.
Offline
It's usually related to kwin or plasma, but would also help if you'd check your pacman log and tell us what exactly have you upgraded.
Last edited by Xabre (2013-10-03 19:59:26)
Offline
There could exist such a migrate script which deletes old configs with conflicts or change necessary lines in configs, but here it's - laziness to do that
I'd be very grateful to have same desktop to one machine
KDE 4 is a great desktop environment for all machines ![]()
http://ispconfig.lt - ISPConfig 3 based hosting. Coming Soon!
Offline
I'm facing the same situation after the last upgrades and I'm also running proprietary Nvidia driver. I have quite similar lines in kdm.log.
Loading extension XINERAMA
klauncher(307) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(301)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
kdmgreet(301)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X serverI just took a look at my pacman.log and here are the packages upgraded last time before this problem.
[2013-10-08 23:15] [PACMAN] Running 'pacman --color auto -Sy'
[2013-10-08 23:15] [PACMAN] synchronizing package lists
[2013-10-08 23:16] [PACMAN] starting full system upgrade
[2013-10-08 23:16] [PACMAN] Running 'pacman --color auto -S -u'
[2013-10-08 23:16] [PACMAN] starting full system upgrade
[2013-10-08 23:16] [PACMAN] upgraded device-mapper (2.02.100-1 -> 2.02.103-1)
[2013-10-08 23:16] [PACMAN] upgraded lib32-glib2 (2.36.4-1 -> 2.38.0-1)
[2013-10-08 23:16] [PACMAN] upgraded lib32-atk (2.8.0-1 -> 2.10.0-1)
[2013-10-08 23:16] [PACMAN] upgraded lib32-gdk-pixbuf2 (2.28.2-1 -> 2.30.0-1)
[2013-10-08 23:16] [PACMAN] upgraded lib32-pango (1.34.1-1 -> 1.36.0-1)
[2013-10-08 23:16] [PACMAN] upgraded lib32-gtk2 (2.24.20-2 -> 2.24.21-1)
[2013-10-08 23:16] [PACMAN] upgraded lib32-mesa (9.2.0-1 -> 9.2.1-1)
[2013-10-08 23:16] [PACMAN] upgraded lirc-utils (1:0.9.0-62 -> 1:0.9.0-63)
[2013-10-08 23:16] [PACMAN] upgraded lvm2 (2.02.100-1 -> 2.02.103-1)
[2013-10-08 23:16] [PACMAN] upgraded mpg123 (1.15.4-1 -> 1.16.0-1)
[2013-10-08 23:16] [PACMAN] upgraded s-nail (14.4.3-1 -> 14.4.4-1)
[2013-10-08 23:16] [PACMAN] upgraded tzdata (2013f-1 -> 2013g-1)Is it possible that tzdata has something to do with this? I see it was upgraded and there are error lines mentioning it. Or are they just failing because D-Bus wasn't started?
Btw, I was able to circumvent the problem by logging in after choosing "failsafe" in KDM settings.
Last edited by Tha-Fox (2013-10-10 19:41:11)
Offline
I doubt that's the issue. I have those errors in kdm.log, too, but no problem logging in. (Well, unless I will next time I reboot which is far from impossible.)
But if, so, it would mean that now caused failure to login but that KDE wasn't bothered by the error before the update. i.e. the error isn't introduced by the 2013-10-07 update.
Last edited by cfr (2013-10-10 23:51:50)
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline