This forum has been archived. All content is frozen. Please use KDE Discuss instead.

[resolved] KDE keeps going back to the login screen

Tags: None
(comma "," separated)
strycat
Registered Member
Posts
18
Karma
0
I hope this is the right place to post this.

So I installed kubuntu 10.10 on my box. Everything seems to go smoothly until I logged in. After I entered my password, the KDE startup panel appeared and the harddrive icon came into focus. However before any of the icons appeared it kicked me back to the login screen.

After lots of fiddling with it I gave up and thought I'd try Fedora 14 with KDE. That install went well, but again I had the same problem.

I finally gave up there and installed Ubuntu 10.10 and Gnome works just fine. Therefore my conclusion is that this is some KDE issue.

However I really prefer KDE (even this horror known as 4.x is better than the other options) and would like to get it working.

The main symptom other than the being kicked back to the login screen is that once this error/crash/whatever occurs you can no longer get to a console by hitting Ctrl-Alt-F1 (or any of the other function keys). As long as you don't attempt to login the console works fine, but after the login disaster the console is just a warped view of the background image.

The only other thing of potential use is my .xsession-errors file. The one below is from an attempt when I still had kubuntu installed.

Code: Select all
Xsession: X session started for strycat at Sat Nov  6 19:57:41 EDT 2010
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.
[: 225: ==: unexpected operator
startkde: Starting up...
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()
kbuildsycoca4 running...
QDBusObjectPath: invalid path ""
Fetched layout groups from X server:    layouts: ("us")    variants: ("")
X Error: BadValue (integer parameter out of range for operation) 2
  Major opcode: 102 (X_ChangeKeyboardControl)
  Resource id:  0xffffffc8
Fetched layout groups from X server:    layouts: ("us")    variants: ("")
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()

Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Invalid D-BUS member name 'idle-hint' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'is-local' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'x11-display-device' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'x11-display' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'display-device' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'remote-host-name' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'session-type' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'unix-user' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
<unknown program name>(1513)/ KStartupInfo::createNewStartupId: creating:  "zelas;1289087867;978179;1513_TIME0" : "unnamed app"
kded(1516)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.7'
QDBusObjectPath: invalid path ""
QObject::connect: Cannot connect (null)::deviceCreated(Device*) to Monolithic::deviceCreated(Device*)
QObject::connect: Cannot connect (null)::deviceDisappeared(Device*) to Monolithic::regenerateDeviceEntries()
QObject::connect: Cannot connect (null)::deviceRemoved(Device*) to Monolithic::regenerateDeviceEntries()
Object::disconnect: Unexpected null parameter
Object::disconnect: Unexpected null parameter
Object::disconnect: Unexpected null parameter
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()
kwin(1596) KWin::CompositingPrefs::detectDriverAndVersion: GL vendor is "VIA Technology"
kwin(1596) KWin::CompositingPrefs::detectDriverAndVersion: GL renderer is "Mesa DRI UniChrome (KM400) 20060710 x86/MMX+/3DNow!+/SSE"
kwin(1596) KWin::CompositingPrefs::detectDriverAndVersion: GL version is "1.2 Mesa 7.9-devel"
kwin(1596) KWin::CompositingPrefs::detectDriverAndVersion: Detected driver "unknown" , version ""
kdeinit4: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
klauncher: Exiting on signal 1
bluedevil-monolithic: Fatal IO error: client killed
kglobalaccel: Fatal IO error: client killed
XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"

      after 22 requests (8 known processed) with 0 events remaining.

kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.
QProcess: Destroyed while process is still running.
Qt-subapplication: Fatal IO error: client killed
kded4: Fatal IO error: client killed


Hopefully that is somehow helpful. If anyone knows how I can get KDE working on my computer, please let me know.

Thanks in advance.

Last edited by strycat on Fri Dec 24, 2010 3:05 pm, edited 2 times in total.
User avatar
Hans
Administrator
Posts
3304
Karma
24
OS
Could you please post more information about your system - which graphic card and driver?


Problem solved? Please click on "Accept this answer" below the post with the best answer to mark your topic as solved.

10 things you might want to do in KDE | Open menu with Super key | Mouse shortcuts
strycat
Registered Member
Posts
18
Karma
0
Hans wrote:Could you please post more information about your system - which graphic card and driver?

According to the Monitor dialog in Gnome, I've got an unknown 1920x1080 (16:9) monitor. It is actually an emachines E233H monitor.

The computer itself is an older Compaq Presario SR1313CL with a "3000+ AMD Sempron". I'm not sure what the video card is (the Gnome manager says it is VIA Technologies).
User avatar
Hans
Administrator
Posts
3304
Karma
24
OS
My guess is that this is the problem
Code: Select all
kwin(1596) KWin::CompositingPrefs::detectDriverAndVersion: GL vendor is "VIA Technology"
kwin(1596) KWin::CompositingPrefs::detectDriverAndVersion: GL renderer is "Mesa DRI UniChrome (KM400) 20060710 x86/MMX+/3DNow!+/SSE"
kwin(1596) KWin::CompositingPrefs::detectDriverAndVersion: GL version is "1.2 Mesa 7.9-devel"
kwin(1596) KWin::CompositingPrefs::detectDriverAndVersion: Detected driver "unknown" , version ""
kdeinit4: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
klauncher: Exiting on signal 1


so I've moved the topic to see if the KWin developers know anything about it.


Problem solved? Please click on "Accept this answer" below the post with the best answer to mark your topic as solved.

10 things you might want to do in KDE | Open menu with Super key | Mouse shortcuts
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
This is probably because VIA graphics are not too well supported on Linux. I'm surprised the driver is even offering Direct Rendering....

In any case, run the following command in a virtual terminal to disable Desktop Effects:
Code: Select all
kwriteconfig --file kwinrc --group Compositing --key Enabled --type bool false


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


Bookmarks



Who is online

Registered users: abc72656, Bing [Bot], daret, Google [Bot], lockheed, Sogou [Bot], Yahoo [Bot]