View previous topic :: View next topic |
Author |
Message |
Dragonlord Guru
Joined: 22 Aug 2004 Posts: 446 Location: Switzerland
|
Posted: Wed Oct 14, 2009 10:13 am Post subject: KDM(4.x) fails to start KDE |
|
|
Uprade to KDE4 and now KDM stops working. That is KDM itself works but when I enter the login informations the screen flickers a couple of times and I'm back to the KDM login screen. I can start KDE using XDM for example hence it has to be a KDM related problem. The kdm logs show this:
Quote: | This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
X.Org X Server 1.6.3.901 (1.6.4 RC 1)
Release Date: 2009-8-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.30-gentoo-r4 x86_64
Current Operating System: Linux dragtop 2.6.30-gentoo-r4 #5 SMP Tue Aug 18 15:35:07 CEST 2009 x86_64
Build Date: 05 October 2009 12:24:27PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Oct 13 12:32:02 2009
(==) Using config file: "/etc/X11/xorg.conf"
(EE) Failed to load module "type1" (module does not exist, 0)
(EE) Failed to load module "freetype" (module does not exist, 0)
(EE) Failed to load module "xtrap" (module does not exist, 0)
(EE) Failed to load module "dri" (module does not exist, 0)
(EE) Failed to load module "dri2" (module does not exist, 0)
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 server
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 server
(EE) XKB: No components provided for device Virtual core keyboard
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 server
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 server |
No idea why there are errors with dri and what not else. 3D acceleratio ( aka DRI ) is running without a problem ( can play my game-in-dev without a problem ). Any ideas what could cause KDM to fail? Login using XDM is rather annoying so I'd like to have KDM back ( since I could not figure out a way to run KDE from the console itself like it worked with older versions ). _________________ DragonDreams: Leader and Head Programmer |
|
Back to top |
|
|
ctxnop n00b
Joined: 12 Aug 2009 Posts: 21
|
Posted: Wed Oct 14, 2009 5:32 pm Post subject: |
|
|
Same thing here.
kdm.log wrote: |
X.Org X Server 1.6.5
Release Date: 2009-10-11
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.30-gentoo-r5 x86_64
Current Operating System: Linux desktop 2.6.31-gentoo-r2 #1 SMP PREEMPT Wed Oct 14 13:40:45 CEST 2009 x86_64
Build Date: 13 October 2009 07:01:28PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 14 18:59:37 2009
(==) Using config file: "/etc/X11/xorg.conf"
(EE) Failed to load module "dri2" (module does not exist, 0)
(EE) Failed to load module "dri" (module does not exist, 0)
expected keysym, got XF86TouchpadToggle: line 122 of inet
expected keysym, got XF86TouchpadToggle: line 122 of inet
|
Don't understand why it try to load dri while xorg.conf do not load it, but nevermind for now, X work, startx work as well (but do not start kde).
I'll try to downgrade kdm. |
|
Back to top |
|
|
ctxnop n00b
Joined: 12 Aug 2009 Posts: 21
|
Posted: Wed Oct 14, 2009 5:36 pm Post subject: |
|
|
downgrade kdm didn't work :/ |
|
Back to top |
|
|
wfahren n00b
Joined: 04 Aug 2007 Posts: 32
|
Posted: Wed Oct 14, 2009 6:16 pm Post subject: |
|
|
Not sure if this is the same problem you are having but see the same error I had.
I had the same problem when I upgraded my laptop to 4.3.2 from 4.3.1. With KDM I could not login. it would load kdm but when I logged in it would return me right back to the login screen.
kdm.log gave me the clue.
Code: |
tail -f /var/log/kdm.log
(EE) XKB: No components provided for device Virtual core keyboard
|
Then googled the error and found this:
answer down at the bottom
Found out I have the consolekit use flag enable
Code: |
euse -i consolekit
global use flags (searching: consolekit)
************************************************************
no matching entries found
local use flags (searching: consolekit)
************************************************************
[+ D ] consolekit (gnome-base/gdm):
Allow proper handling of removable media according to who is actually present on the machine.
[+ D ] consolekit (gnome-base/gnome-volume-manager):
Use sys-auth/consolekit to determine policy on removable media.
[+ D ] consolekit (kde-base/kdm):
Enables support for authorization using consolekit
[+ D ] consolekit (net-wireless/bluez):
Use sys-auth/pambase[consolekit] to determine access to bluetooth devices based on whether a user is logged in locally or remotely
[+ D ] consolekit (sys-apps/hal):
Enables HAL to interact with consolekit for determining whether a given process is running on behalf of the person setting at the console.
[+ D ] consolekit (sys-auth/pambase):
Enable pam_ck_connector module on local system logins. This allows for console logins to make use of ConsoleKit authorization.
[+ D ] consolekit (x11-apps/xinit):
Enable consolekit integration for the privileges detection.
|
looked in my /etc/init.d and sure enough there is a consolekit init.
Works now......added it to my default rc run.
Edit.....
After thinking about it I used eselect to set my default profile to
[2] default/linux/x86/10.0/desktop *
I'll bet thats what enabled the use flag consolekit and not the upgrade to 4.3.2 |
|
Back to top |
|
|
Dragonlord Guru
Joined: 22 Aug 2004 Posts: 446 Location: Switzerland
|
Posted: Wed Oct 14, 2009 6:57 pm Post subject: |
|
|
Yeah, figured that one out with the consolekit too but over a detour. Powerdevil reported something not working and it had been consolekit. I started it and noticed somehow that kdm seem to use this useflag too. Running kdm with consolekit started did the trick. I'm still hating the KDE4 GUI ( it's totally fucked up and counter-intuitive and windumb-like ) but I guess I have to get used to it since GenToo considers it stable now _________________ DragonDreams: Leader and Head Programmer |
|
Back to top |
|
|
ctxnop n00b
Joined: 12 Aug 2009 Posts: 21
|
Posted: Wed Oct 14, 2009 8:15 pm Post subject: |
|
|
Thanks a lot, starting consolkit fix my problem too |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|