[SOLVED] cpu at 100% w/ startx == error in config of .xinitrc app

Question

Hi all!
I got some serious trouble after reconfiguring cdm (because of display problems): starting X leads to 100% cp making it unusable. htop says root (usage 66%) and user (usage <1%) have been starting X, with the same .xserverauth-id (process no of root here = 1800; user = 1799.
Usually I start X via .xinitrc, which I didn't touch. Uninstalling cdm and reistalling xorg-server and utils didn't help. And finally, I also can't reinstall cdm, because the project's homepage is down!
So what to do now? I mean, working on CLI (like now) is only temporal fun...
edit: so though actually there's no cdm anymore, X keeps on being launched twice.
edit2: now trying cdm-git; soon getting tuned again
Last edited by nexus7 (2011-11-20 18:29:58)

Answer 1

Installed cdm-git, and no changes: when X has been started, the machine
becomes unbearable slow, the cpu is running
hot at 100% with two X instances:
$ htop
PID USER CPU% MEM% Command
1638 root 60 3 /usr/bin/X :0 -nolisten tcp -dpi 96 vt7 -auth /tmp/serverauth.HryZB8shaS
1618 nexus7 0.0 0.1 /bin/sh /usr/bin/startx /home/nexus7/.xinitrc xmonad -- /usr/bin/X :0 -nolisten tcp -dpi 96 vt7
1637 nexus7 0.0 0.0 xinit /home/nexus7/.xinitrc/ xmonad -- /usr/bin/X :0 -nolisten tcp -dpi 96 vt7 -auth /tmp/serverauth.HryZB8shaS
My files:
# /etc/inittab
# Boot to console
id:3:initdefault:
# Boot to X11
#id:5:initdefault
rc::sysinit:/etc/rc.sysinit
rs:S1:wait:/etc/rc.single
rm:2345:wait/etc/rc.multi
rh:06:wait:/etc/rc.shutdown
su:S:wait/sbin/sulogin -p
# -8 options fixes umlauts problem on login
c1:2345:respawn:/sbin/agetty -8 -s 38400 tty1 linux
c2:2345:respawn:/sbin/agetty -8 -s 38400 tty2 linux
c3:2345:respawn:/sbin/agetty -8 -s 38400 tty3 linux
c4:2345:respawn:/sbin/agetty -8 -s 38400 tty4 linux
c5:2345:respawn:/sbin/agetty -8 -s 38400 tty5 linux
c6:2345:respawn:/sbin/agetty -8 -s 38400 tty6 linux
# Serial Virtual Console for KVM and others VMs
#s0:2345:respawn:/sbin/agetty -8 -s 9600 ttyS0 linux
# Hypervisor Virtual Console for Xen and KVM
#h0:2345:respawn:/sbin/agetty -8 -s 38400 hvc0 linux
Example lines for starting a login manager
#x:5:respawn:/usr/bin/xdm -nodaemon
#x:5:respawn:/usr/sbin/gdm -nodaemon
#x:5:respawn:/usr/bin/kdm -nodaemon
#x:5:respawn:/usr/bin/slim >/dev/null 2>&1
# End of file
(all display managers commented, as said in the wiki)
### GLOBAL CONFIGURATION ###
# Set CDM theme and dialog options
theme=cdm
countfrom=1
# List all WM binary names
wmbinlist=(xmonad)
# List all WM display names
wmdisplist=(XMonad)
# Allow console login?
allowconsole=yes
# Allow shutdown?
allowshutdown=yes
shutdowncommand='sudo shutdown -h now'
rebootcommand='sudo shutdown -r now'
# Allow suspend?
# Note that this option requires pm-utils
allowsuspend=no
suspendcommand='sudo pm-suspend'
allowhibernate=no
hibernatecommand='sudo pm-hibernate'
# Set configuration for specific users?
userconfig=(courtney)
### USER CONFIGURATION ###
courtney() {
# Set CDM theme
theme=lime
# List user allowed WM binary names
wmbinlist=(openbox-session)
# List user allowed WM display names
wmdisplist=(Openbox)
# Allow console login?
allowconsole=yes
# Allow shutdown?
allowshutdown=no
# Set specific display for user
# (Not honored unless locktty=yes)
# display=1
### SYSTEM CONFIGURATION ###
# Set default display
display=0
# Where should first X tty be spawned?
xtty=7
# Restrict tty? (By default, cdm increments X tty, this setting
# allows administrators to lock users into one specific tty by
# setting the display=N option on a per-user basis.)
locktty=no
# Enable login shell (fixes issues with some keymaps, uses bash).
# Note that your bash scripts won't have any terminal as stdin when
# started in this way. This may break some commands, including stty,
# unless you explicitly check for [ -t 0 ] or that every login shell
# is also interactive. However, we're sending stdout and stderr to
# /dev/null, so you won't see the complaints.
loginshell=no
# The use of consolekit has recently become manditory with hal. However,
# some users might prefer not using either one. If you don't want to
# use consolekit, set the following variable to "no".
consolekit=yes
# Timeout for waiting for X session to register with consoleKit
consolekittime=30
# Additional arguments to pass to X server
# When usexinit=yes, we use ~/.xinitrc when it exists or
# /etc/X11/xinit/xinitrc
# when it doesn't. These are passed the chosen window manager as $1; note
# that
# the stock /etc/X11/xinit/xinitrc ignores this and always starts twm and
# three
# xterms. Your custom xinitrc should start the window manager supplied as $1
# instead. There is a sample xinitrc included at
# /usr/share/cdm/xinitrc.skel.
# If usexinit=no, then we instead call the chosen window manager directly.
usexinit=yes
# Additional arguments to pass to X server; it will be called as:
# exec /usr/bin/X :$display $serverargs vt$((xtty+display))
serverargs="-nolisten tcp -dpi 96"
Do this configs suffice?
IMO in the end it doesn't matter, if cdm starts X or not...