| View previous topic :: View next topic |
| Author |
Message |
tenspd137
Guru
Joined: 22 Aug 2006
Posts: 391
|
 Posted: Sat Nov 16, 2013 2:26 am Post subject: CDM (Console Display Manager) and consolekit issues |
 |
|
Hi all,
I have been using CDM as a display manager and have noticed some oddities. When I use consolekit, and tell CDM to register X session with it in /etc/cdmrc, my window manager (openbox or awesome) start up, but when I exit the computer freezes with the line:
cdm-xlaunch:Waiting for ConsoleKit to register X session
If I remove all the console kit stuff (preferred), I log in and select a WM, the WM does not start - it immediately brings me back to a login prompt. Then, if I login again and select a WM, it runs.
My /etc/cdmrc - I am remembering to change the consolkit part depending on whether I am tryin to use it or not
| Code: |
#!/bin/bash
#
# Example config file for cdm(1).
# Values set here is the default as in cdm(1).
# List of programs, commands with whitespaces should be quoted or escaped.
# If unset, all sessions in /etc/X11/Sessions or /usr/share/xsessions are
# offered as choices.
#
# (An example:)
binlist=(
'~/.xsession-openbox' # Launch your X session,
'~/.xsession-awesome'
'/bin/zsh --login' # or just execute your shell,
'/usr/bin/fbterm' # or start a frame buffer console,
# '/usr/bin/cdm ~/.submenu.cdmrc' # or go to a submenu :)
)
# List all program display names, one-by-one matched with $binlist.
# Names with whitespaces should be quoted or escaped.
#
# (Continued example:)
namelist=(OpenBox Awesome Console FBTerm)
# Type of the programs, one-by-one matched with $binlist.
# `C' for *C*onsole programs, which would be `exec'ed.
# `X' for *X* programs, which would be run with cdm-xlaunch(1).
#
# (Continued example:)
flaglist=(X X C C)
# Style for the cdm dialog, which is printed with dialog(1).
# Default to unset, causing dialog(1) to use the system wide default.
# See /usr/share/doc/cdm/themes for some nice choices.
dialogrc=
# Index of the first item in the menu.
countfrom=0
# Set default display.
display=0
# Where should the first X tty be spawned?
# special value `keep' causes to run X in current tty.
xtty=keep
# Should cdm(1) stick to the specified display?
locktty=no
# Use ConsoleKit for X session?
consolekit=yes
# Timeout for waiting for X session to register with ConsoleKit.
cktimeout=30
# Additional arguments to pass to X server, which is usually called as:
# /usr/bin/X :$display "${serverargs[@]}" vt$((xtty+display))
# Arguments with whitespaces should be quoted or escaped.
serverargs=(-nolisten tcp)
# Alternative method of calling startx(/setsid). Should only be set if cdm
# does not start X as expected (bash -x shows call to setsid startx, but for
# no apparent reason does not start X).
# Only provided in the hope it may be useful, not a guaranteed fix.
altstartx=no
|
my .xsession-awesome - again, I alter it depending on if I use consolekit or not
| Code: |
udiskie &
#exec ck-launch-session dbus-launch --sh-syntax --exit-with-session awesome >> ~/.awesome_stdout 2>> ~/.awesome_stderr
exec dbus-launch --sh-syntax --exit-with-session awesome >> ~/.awesome_stdout 2>> ~/.awesome_stderr
|
Ultimately, I would like to figure out why I have to login twice w/o consolekit, fix that, and dump consolekit all together. And no - I don't want to use systemd.
Any suggestions?
Thanks!
###############################EDIT#####################3
Figured it out -
removed all consolekit stuff, removed from default rc, changed /etc/cdmrc xtty=7 instead of xtty=keep, and all works as I expect w/o consolekit stuff. |
|
| Back to top |
|
 |
tenspd137
Guru
Joined: 22 Aug 2006
Posts: 391
|
| Posted: Sat Nov 16, 2013 5:39 am Post subject: Did not figure it out :( |
|
|
#####EDIT 2############################3
Just rebooted with no changes and seeing the same behavior, so I guess I did not figure it out. I tried tail -f /var/log/messages in another tty, but it just says that a session is opened then closed by me. No errors or anything like that. If I erase my Xorg.log files, and try it, after the first login attempt, there are no files generated, meaning X is never starting. Running out of log file ideas. Any other suggestions? |
|
| Back to top |
|
|
vortininja
n00b
Joined: 14 Aug 2018
Posts: 1
|
| Posted: Tue Aug 14, 2018 9:44 pm Post subject: |
|
|
| When this happened to me, I fixed it by preventing the 'xdm' service from running at 'default' |
|
| 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
|
|
Desktop Environments
