You are not logged in.
Pages: 1
I have GDM which is started from inittab and it works fine, spawns on tty7.
But whenever I try to restart it, it terminates well but respawns on tty8. After every restart it respawns on tty8.
ps aux shows nothing running on tty7
Where is the problem?
Thanks in advance.
Offline
How many ttys do you have?
I have only three:
c1:2345:respawn:/sbin/mingetty --autologin karol tty1 linux
c2:2345:respawn:/sbin/agetty -8 38400 tty2 linux
c3:2345:respawn:/sbin/agetty -8 38400 tty3 linux
#c4:2345:respawn:/sbin/agetty -8 38400 tty4 linux
#c5:2345:respawn:/sbin/agetty -8 38400 tty5 linux
#c6:2345:respawn:/sbin/agetty -8 38400 tty6 linux
so X spawns on tty4 for me.
Offline
From 1 to 6.
As I said there is nothing running on tty7 and the first time Xorg spawns on tty7 fine.
Offline
This mailing list thread suggests killing console-kit-daemon before restarting gdm.
Offline
Whoa, it helps, thanks.
But isn't it a bug? Only tty7 gets stuck like this.
I don't want to kill another process each time I restart GDM ^^
Offline
I have no idea. I don't use it.
You could try seeing if you can make it stop launching in the first place, e.g. pacman -Rd consolekit or chmod a-x /usr/sbin/console-kit-daemon or ln -sf /bin/true /usr/sbin/console-kit-daemon
Offline
None of these helped.
I'll try KDE then ^^ Maybe it will be less annoying.
Heh, KDM has the same problem.
Last edited by Radzio (2010-08-28 14:03:09)
Offline
Same problem with me, except I don't use a display manager or a DE. I use .xinitrc and dwm.
Offline
And only tty7 gets stuck, right? It can freely respawn on any other tty but tty7 is blocked.
Offline
Console-kit is running as --no-daemon:
/usr/sbin/console-kit-daemon --no-daemon
So it should quit when its parent stops (Xorg).
However it does not and therefore blocks tty7.
In general it blocks the tty on which Xorg spawns the first time.
So it is a bug.
Another workaround (different than killing it each time) for this is to start /usr/sbin/console-kit-daemon as daemon (= without any options) before starting Xorg. Then everything is fine.
Offline
Not a solution perse, but how about leaving out a display manager entirely? To me it is just another possible source of bugs. I use mingettty to do autologin.
Last edited by rwd (2010-08-29 20:24:29)
Offline
Any guide?
Because simply running X from getty is stupid (bad guy comes, does Alt-F{1-6} and ^C).
Offline
Because simply running X from getty is stupid (bad guy comes, does Alt-F{1-6} and ^C).
Actually, no. Bad guy can't do that. Add the following to .bashrc:
if [[ -z "$DISPLAY" ]] && [[ $(tty) = /dev/tty1 ]]; then
startx &
logout
fi
This way no matter how X gets terminated, tty1 will logout immediately.
It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)
Offline
I tried that. It logouts me fine but console-kit-daemon still starts and blocks my tty7
So this bug is not related to GDM/KDM and happens every time one starts X.
Offline
Radzio wrote:Because simply running X from getty is stupid (bad guy comes, does Alt-F{1-6} and ^C).
Actually, no. Bad guy can't do that. Add the following to .bashrc:
if [[ -z "$DISPLAY" ]] && [[ $(tty) = /dev/tty1 ]]; then startx & logout fi
This way no matter how X gets terminated, tty1 will logout immediately.
Thanks, works like a charm ^^
I have the same problem with console-kit-daemon blocking tty7 whenever X-server is shut down. Does anyone know what console-kit-daemon is used for? All i know is that hal depends on it.
Offline
Probably it's meant to block ttys that are used by Xorg but it shouldn't block them from being re-used by Xorg. It should die with Xorg instance that spawned it IMHO.
Last edited by Radzio (2010-09-10 17:15:23)
Offline
console-kit-daemon is used in conjunction with policykit to give users some privileges. I.e. mounting usb media.
Such things break without console-kit-daemon running.
It is damn annoying when using qingy with it's prime feature: runnung X on same vt, you've logged in. First X launch blocks this vt with console-kit-daemon.
Found a nice workaround: add this to rc.local:
openvt -c 63 -f -- console-kit-daemon --no-daemon &
It will force console-kit-daemon to grab tty63. Out of sight, out of mind.
Anyway, the bug is here: https://bugs.freedesktop.org/show_bug.cgi?id=29920
let's give it some weight.
Last edited by Psycho_zs (2010-10-03 06:45:25)
Offline
Ok, I've added my comment. Hope it gets fixed soon.
Offline
It stopped holding tty!
Maybe it was a qingy update though..
...nope, it was my error in config. False alarm.
Last edited by Psycho_zs (2010-12-18 14:51:18)
Offline
Pages: 1