This forum has been archived. All content is frozen. Please use KDE Discuss instead.
The Discussions and Opinions forum is a place for open discussion regarding everything related to KDE, within the boundaries of KDE Code of Conduct. If you have a question or need a solution for a KDE problem, please post in the apppropriate forum instead.

KDE stops loading after log-in screen

Tags: None
(comma "," separated)
ard
Registered Member
Posts
6
Karma
0
hi guys,

i've encountered pretty stubborn problem and couldn't find anything useful with search.
my problem is that after kernel upgrade to 3.2.0-27-generic, kde stops loading after the log-in screen. after entering username/password, login window disappears and i'm left with mouse cursor and default screen background. alt+tab works, but it shows that there are "no active windows" whatsoever.
i tried to check the X0 log in /var/ directory, but it seems to contain any major error messages. dmesg also does not have any major messages.
disk usage is mild, more that 16gb available, so this is not a space issue.

alt+f2 works and i can log in. i have deleted most of config files that starts with ".", but the problem is still there.

i've stopped kdm, deleted .xsession-error log file, started kdm and tried to log in to get a fresh log, so there it is:
Xsession: X session started for ard at Sun Aug 12 23:42:33 EEST 2012
localuser:ard being added to access control list
Setting IM through im-switch for locale=en_US.
Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 460/PCIe/SSE2
OpenGL version string: 4.2.0 NVIDIA 295.40
OpenGL shading language version string: 4.20 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 295.40
GPU class: GF100
OpenGL version: 4.2
GLSL version: 4.20
X server version: 1.11.3
Linux kernel version: 3.2
Direct rendering: yes
Requires strict binding: no
GLSL shaders: yes
Texture NPOT support: yes
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QStr ing,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.7'
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kded4: Fatal IO error: client killed
kdeinit4: Fatal IO error: client killed
klauncher: Exiting on signal 15
kdeinit4: Fatal IO error: client killed
x-window-manager: Fatal IO error: client killed
knotify4: Fatal IO error: client killed
kglobalaccel: Fatal IO error: client killed
kactivitymanagerd: Fatal IO error: client killed
User avatar
google01103
Manager
Posts
6668
Karma
25
can you create a new user and try it? the adduser <username> command is the easiest if you have it, else use: useradd <username> followed by passwd <username>

when you up'ed your Kernel did you also up the Nvidia driver?


OpenSuse Leap 42.1 x64, Plasma 5.x

User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Also, the log you posted indicates that X itself actually goes down midway through KDE startup, which is unusual.
Are you able to use Alt + F2 to launch a terminal, or plasma-desktop?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
ard
Registered Member
Posts
6
Karma
0
i've created new user and i still could not log in.
can't really remember if nvidia was updated, i usually do not check what software gets updated so i can check the update logs if they exist?
i'm able to switch sessions with alt+ctrl+f1/f2/... but alt+f2 does not work.

alt tab works but it shows that there are no windows to display.
User avatar
google01103
Manager
Posts
6668
Karma
25
the Nvidia drivers must be compiled for the kernel installed so if you up'ed the kernel and are using Nvidia drivers compiled for the previous kernel you would have an issue.

what is result of
Code: Select all
locate kernel | grep nvidia


what distro are you running? do you compile your Nvidia drivers?


OpenSuse Leap 42.1 x64, Plasma 5.x

ard
Registered Member
Posts
6
Karma
0
Code: Select all
locate kernel | grep nvidia

Code: Select all
/lib/modules/2.6.38-11-generic/kernel/drivers/video/nvidia
/lib/modules/2.6.38-11-generic/kernel/drivers/video/backlight/mbp_nvidia_bl.ko
/lib/modules/2.6.38-11-generic/kernel/drivers/video/nvidia/nvidiafb.ko
/lib/modules/3.0.0-17-generic/kernel/drivers/video/nvidia
/lib/modules/3.0.0-17-generic/kernel/drivers/video/nvidia/nvidiafb.ko
/lib/modules/3.2.0-23-generic/kernel/drivers/net/ethernet/nvidia
/lib/modules/3.2.0-23-generic/kernel/drivers/net/ethernet/nvidia/forcedeth.ko
/lib/modules/3.2.0-23-generic/kernel/drivers/video/nvidia
/lib/modules/3.2.0-23-generic/kernel/drivers/video/nvidia/nvidiafb.ko
/lib/modules/3.2.0-24-generic/kernel/drivers/net/ethernet/nvidia
/lib/modules/3.2.0-24-generic/kernel/drivers/net/ethernet/nvidia/forcedeth.ko
/lib/modules/3.2.0-24-generic/kernel/drivers/video/nvidia
/lib/modules/3.2.0-24-generic/kernel/drivers/video/nvidia/nvidiafb.ko
/lib/modules/3.2.0-25-generic/kernel/drivers/net/ethernet/nvidia
/lib/modules/3.2.0-25-generic/kernel/drivers/net/ethernet/nvidia/forcedeth.ko
/lib/modules/3.2.0-25-generic/kernel/drivers/video/nvidia
/lib/modules/3.2.0-25-generic/kernel/drivers/video/nvidia/nvidiafb.ko
/lib/modules/3.2.0-26-generic/kernel/drivers/net/ethernet/nvidia
/lib/modules/3.2.0-26-generic/kernel/drivers/net/ethernet/nvidia/forcedeth.ko
/lib/modules/3.2.0-26-generic/kernel/drivers/video/nvidia
/lib/modules/3.2.0-26-generic/kernel/drivers/video/nvidia/nvidiafb.ko
/lib/modules/3.2.0-27-generic/kernel/drivers/net/ethernet/nvidia
/lib/modules/3.2.0-27-generic/kernel/drivers/net/ethernet/nvidia/forcedeth.ko
/lib/modules/3.2.0-27-generic/kernel/drivers/video/nvidia
/lib/modules/3.2.0-27-generic/kernel/drivers/video/nvidia/nvidiafb.ko
/usr/src/nvidia-current-295.40/nv-kernel.o
/usr/src/nvidia-current-295.40/patches/buildfix_kernel_3.0.patch


i'm running latest kubuntu 12.10 and all updates are done via application manager. i'm trying to avoid compiling and building my own software to minimize the risk of failure.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
The log you posted before indicates that X itself actually goes down midway through KDE startup, which is unusual.
Are you able to use Alt + F2 to launch a terminal, or plasma-desktop?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
ard
Registered Member
Posts
6
Karma
0
no, i can't use alt+f2, nothing happens. only thing i can make kde do is alt+tab and it shows that there are no open windows.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Okay, it looks like the only thing that is starting is KWin. For the test of KDE, it seems to lose it's connection (or fail to establish) a connection to X, preventing startup from really getting into motion.

Does this happen under a new user as well (just to rule out local configuration issues)?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
ard
Registered Member
Posts
6
Karma
0
i've tried both - first deleted all local conf files, but after this failed i created new user and it failed again.
ard
Registered Member
Posts
6
Karma
0
bcooksley, where should i check what is starting and what looses connection to X, and why? what logs are not yet checked? it seems that i'm not the only one who is affected by this so i would like to know the culprit of this.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
My primary suspect here would be the Nvidia driver. Could you temporarily disable it in favour of Vesa or a similar basic driver?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]


Bookmarks



Who is online

Registered users: Baidu [Spider], Bing [Bot], Google [Bot], rblackwell