Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
After logging in with KDM4 KDM restarts
View unanswered posts
View posts from last 24 hours
View posts from last 7 days

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
bastibasti
Guru
Guru


Joined: 27 Nov 2006
Posts: 581

PostPosted: Thu Dec 24, 2009 12:01 pm    Post subject: After logging in with KDM4 KDM restarts Reply with quote

Hi,

if I enter my username and password in KDM, it goes to blackscreen, and then restarts

KDM.LOG gives

Code:

Fatal server error:
Server is already active for display 0
        If this server is no longer running, remove /tmp/.X0-lock
        and start again.           


Any ideas?
Back to top
View user's profile Send private message
gami
Apprentice
Apprentice


Joined: 02 Jun 2006
Posts: 297

PostPosted: Thu Dec 24, 2009 2:25 pm    Post subject: Reply with quote

Please post some more information, especially about the versions of xorg-server, mesa and your video driver. You might also try if setting "Enabled=false" in the "[Compositing]" section of ~/.kde4/share/config/kwinrc works for you; I have observed this behaviour sometimes when there were issues with the OpenGL driver.
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana

PostPosted: Thu Dec 24, 2009 2:31 pm    Post subject: Reply with quote

You forgot to mention whether you tried removing lockfile or not.
Back to top
View user's profile Send private message
bastibasti
Guru
Guru


Joined: 27 Nov 2006
Posts: 581

PostPosted: Thu Dec 24, 2009 7:47 pm    Post subject: Reply with quote

I dont need to remove the lockfile, as my /tmp is tmpfs. It will be gone after each restart...

I will try the compositing option...
Back to top
View user's profile Send private message
bastibasti
Guru
Guru


Joined: 27 Nov 2006
Posts: 581

PostPosted: Thu Dec 24, 2009 8:18 pm    Post subject: Reply with quote

EDIT: Tried both, none works.

Can I ask a question? Does KDM login stop X? I thought it must be kept alive?
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana

PostPosted: Thu Dec 24, 2009 8:25 pm    Post subject: Reply with quote

I'd check Xorg log and ~/.xsession-errors
Back to top
View user's profile Send private message
bastibasti
Guru
Guru


Joined: 27 Nov 2006
Posts: 581

PostPosted: Sat Dec 26, 2009 3:22 pm    Post subject: Reply with quote

~/.xsession-errors does not exist !?????

Xorg.log also tells kdm_greet error while loading shared library libQtDBus.so.4 is missing...
Back to top
View user's profile Send private message
VoidMage
Watchman
Watchman


Joined: 14 Oct 2006
Posts: 6196

PostPosted: Sat Dec 26, 2009 3:45 pm    Post subject: Reply with quote

bastibasti wrote:
Xorg.log also tells kdm_greet error while loading shared library libQtDBus.so.4 is missing...

For the moment, focus on this - emerge it.
Back to top
View user's profile Send private message
bastibasti
Guru
Guru


Joined: 27 Nov 2006
Posts: 581

PostPosted: Sun Dec 27, 2009 9:59 pm    Post subject: Reply with quote

I tried to use equery belongs.... but it didnt show any package.

Does anone know which package that is?
Back to top
View user's profile Send private message
d2_racing
Bodhisattva
Bodhisattva


Joined: 25 Apr 2005
Posts: 13047
Location: Ste-Foy,Canada

PostPosted: Sun Dec 27, 2009 10:45 pm    Post subject: Reply with quote

Can you post this :

Code:

# cat /etc/rc.conf
# cat  /etc/env.d/90session
Back to top
View user's profile Send private message
bastibasti
Guru
Guru


Joined: 27 Nov 2006
Posts: 581

PostPosted: Sun Dec 27, 2009 11:31 pm    Post subject: Reply with quote

Hi,

rc.conf:
Code:

# Global OpenRC configuration settings

# Set to "YES" if you want the rc system to try and start services
# in parallel for a slight speed improvement. When running in parallel we
# prefix the service output with it's name as the output will get       
# jumbled up.                                                           
# WARNING: whilst we have improved parallel, it can still potentially lock
# the boot process. Don't file bugs about this unless you can supply     
# patches that fix it without breaking other things!                     
rc_parallel="no"                                                         

# Set rc_interactive to "YES" and you'll be able to press the I key during
# boot so you can choose to start specific services. Set to "NO" to disable
# this feature.                                                           
rc_interactive="YES"                                                       

# If we need to drop to a shell, you can specify it here.
# If not specified we use $SHELL, otherwise the one specified in /etc/passwd,
# otherwise /bin/sh                                                         
# Linux users could specify /sbin/sulogin                                   
rc_shell=/sbin/sulogin                                                       

# Do we allow any started service in the runlevel to satisfy the depedency
# or do we want all of them regardless of state? For example, if net.eth0
# and net.eth1 are in the default runlevel then with rc_depend_strict="NO"
# both will be started, but services that depend on 'net' will work if either
# one comes up. With rc_depend_strict="YES" we would require them both to   
# come up.                                                                   
#rc_depend_strict="YES"                                                     

# rc_hotplug is a list of services that we allow to be hotplugged.
# By default we do not allow hotplugging.                         
# A hotplugged service is one started by a dynamic dev manager when a matching
# hardware device is found.                                                   
# This service is intrinsically included in the boot runlevel.               
# To disable services, prefix with a !                                       
# Example - rc_hotplug="net.wlan !net.*"                                     
# This allows net.wlan and any service not matching net.* to be plugged.     
# Example - rc_hotplug="*"                                                   
# This allows all services to be hotplugged                                                                                                                                         
#rc_hotplug="*"                                                                                                                                                                     
                                                                                                                                                                                   
# rc_logger launches a logging daemon to log the entire rc process to                                                                                                               
# /var/log/rc.log                                                                                                                                                                   
# NOTE: Linux systems require the devfs service to be started before                                                                                                               
# logging can take place and as such cannot log the sysinit runlevel.                                                                                                               
#rc_logger="YES"                                                                                                                                                                   
                                                                                                                                                                                   
# By default we filter the environment for our running scripts. To allow other                                                                                                     
# variables through, add them here. Use a * to allow all variables through.                                                                                                         
#rc_env_allow="VAR1 VAR2"                                                                                                                                                           
                                                                                                                                                                                   
# By default we assume that all daemons will start correctly.                                                                                                                       
# However, some do not - a classic example is that they fork and return 0 AND                                                                                                       
# then child barfs on a configuration error. Or the daemon has a bug and the                                                                                                       
# child crashes. You can set the number of milliseconds start-stop-daemon                                                                                                           
# waits to check that the daemon is still running after starting here.                                                                                                             
# The default is 0 - no checking.                                                                                                                                                   
#rc_start_wait=100                                                                                                                                                                 

# rc_nostop is a list of services which will not stop when changing runlevels.
# This still allows the service itself to be stopped when called directly.   
#rc_nostop=""

# rc will attempt to start crashed services by default.
# However, it will not stop them by default as that could bring down other
# critical services.
#rc_crashed_stop=NO
#rc_crashed_start=YES

##############################################################################
# MISC CONFIGURATION VARIABLES
# There variables are shared between many init scripts

# Set unicode to YES to turn on unicode support for keyboards and screens.
unicode="YES"

# Network fstypes. Below is the default.
net_fs_list="afs cifs coda davfs fuse fuse.sshfs gfs glusterfs lustre ncpfs nfs nfs4 ocfs2 shfs smbfs"

##############################################################################
# SERVICE CONFIGURATION VARIABLES
# These variables are documented here, but should be configured in
# /etc/conf.d/foo for service foo and NOT enabled here unless you
# really want them to work on a global basis.

# Some daemons are started and stopped via start-stop-daemon.
# We can set some things on a per service basis, like the nicelevel.
#export SSD_NICELEVEL="-19"

# Pass ulimit parameters
#rc_ulimit="-u 30"

# It's possible to define extra dependencies for services like so
#rc_config="/etc/foo"
#rc_need="openvpn"
#rc_use="net.eth0"
#rc_after="clock"
#rc_before="local"
#rc_provide="!net"

# You can also enable the above commands here for each service. Below is an
# example for service foo.
#rc_foo_config="/etc/foo"
#rc_foo_need="openvpn"
#rc_foo_after="clock"

# You can also remove dependencies.
# This is mainly used for saying which servies do NOT provide net.
#rc_net_tap0_provide="!net"

##############################################################################
# LINUX SPECIFIC OPTIONS

# This is the number of tty's used in most of the rc-scripts (like
# consolefont, numlock, etc ...)
rc_tty_number=12



and 90session does not exist... ???
Back to top
View user's profile Send private message
d2_racing
Bodhisattva
Bodhisattva


Joined: 25 Apr 2005
Posts: 13047
Location: Ste-Foy,Canada

PostPosted: Sun Dec 27, 2009 11:40 pm    Post subject: Reply with quote

Ok that's fine, I don't see any config problem right now.
Back to top
View user's profile Send private message
dpshak
Apprentice
Apprentice


Joined: 05 May 2005
Posts: 183
Location: Wisconsin

PostPosted: Tue Dec 29, 2009 4:15 pm    Post subject: Reply with quote

Do you have 'consolekit' set to start automatically?

When I rebuilt this box, I installed KDE4 fresh (as opposed to over KDE3.5.#) and every time I tried to log in to KDM, it would accept my log-in creds, go to a black screen and then recycle to the log in screen. Finally, after much cursing (and reading) I finally stumbled over 'consolekit' and added it to the default run level. Problem solved!
Back to top
View user's profile Send private message
d2_racing
Bodhisattva
Bodhisattva


Joined: 25 Apr 2005
Posts: 13047
Location: Ste-Foy,Canada

PostPosted: Tue Dec 29, 2009 6:36 pm    Post subject: Reply with quote

Can you post this :

Code:

# emerge --info
# rc-update show
Back to top
View user's profile Send private message
VoidMage
Watchman
Watchman


Joined: 14 Oct 2006
Posts: 6196

PostPosted: Tue Dec 29, 2009 7:54 pm    Post subject: Reply with quote

As you could expect, libQtDBus.so.4 belongs to x11-libs/qt-dbus.
Back to top
View user's profile Send private message
Haakon
n00b
n00b


Joined: 16 Jan 2006
Posts: 22

PostPosted: Mon Jan 04, 2010 1:27 am    Post subject: Reply with quote

dpshak wrote:
Do you have 'consolekit' set to start automatically?

When I rebuilt this box, I installed KDE4 fresh (as opposed to over KDE3.5.#) and every time I tried to log in to KDM, it would accept my log-in creds, go to a black screen and then recycle to the log in screen. Finally, after much cursing (and reading) I finally stumbled over 'consolekit' and added it to the default run level. Problem solved!


This worked for me, thanks!

Odd thing, on my main desktop (the one I am on now) I don't need consolekit running and I can still login via kdm. I am pretty sure I killed all KDE 3.5 files and started from scratch, to include the configuration files in the home directories. The machine where I had this problem is a fresh install from ground up. No cheats like a system-wide tarball, etc...

Any ideas for the differences?
Back to top
View user's profile Send private message
d2_racing
Bodhisattva
Bodhisattva


Joined: 25 Apr 2005
Posts: 13047
Location: Ste-Foy,Canada

PostPosted: Mon Jan 04, 2010 3:54 am    Post subject: Reply with quote

Maybe Kde 4 needs consolekit or udev or something else cannot handle the creds like it used to.
Back to top
View user's profile Send private message
BonezTheGoon
Bodhisattva
Bodhisattva


Joined: 14 Jun 2002
Posts: 1408
Location: Albuquerque, NM -- birthplace of Microsoft and Gentoo

PostPosted: Sun Jan 17, 2010 9:20 pm    Post subject: Reply with quote

dpshak wrote:
Do you have 'consolekit' set to start automatically?

When I rebuilt this box, I installed KDE4 fresh (as opposed to over KDE3.5.#) and every time I tried to log in to KDM, it would accept my log-in creds, go to a black screen and then recycle to the log in screen. Finally, after much cursing (and reading) I finally stumbled over 'consolekit' and added it to the default run level. Problem solved!


Thanks!!!! You are a life-saver! Your cursing, searching, and stumbling has saved me a few of those steps! I really appreciate you sharing your experience!
_________________
mcgruff wrote:
I can't promise to be civil.


pjp wrote:
The greater evil is voting for the "lesser evil."
Back to top
View user's profile Send private message
d2_racing
Bodhisattva
Bodhisattva


Joined: 25 Apr 2005
Posts: 13047
Location: Ste-Foy,Canada

PostPosted: Mon Jan 18, 2010 1:03 am    Post subject: Reply with quote

In fact, consolekit is really needed nowadays for Gnome and KDE for sure.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
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