You are not logged in.
Ok so I've found the Issue. But can't seem to work out a fix.
Ever since a recent update (I know not which one) gdm/xorg keeps starting up on tty2 insted of 7
It wouldn't worry me but because agetty is configured on tty2 it causes my Xorg to die "randomly"
Using the gdm's default.conf or custom.conf to force it onto tty7 doesn't work.
I know the answer will be a simple one, I just don't happen to know it.
Oh.. to help you
I start up GDM in my rc.local (last thing it does)
I'm guessing that the auto-detect, to see what tty's are currently in use, in Xorg isnt working. OR the agetty isn't starting up before Xorg.
I'm assuming its the second one.
So anyway.. Thanks in advance for any and all help.
Edit: watch your language, cleaned up your topic title
Sorry bout that.
Last edited by insanemal (2009-08-14 02:32:52)
Offline
Make sure a line like this is in your /etc/inittab:
x:7:respawn:/usr/bin/gdb -nodaemon
And if you put this line in, then you no longer need gdb to start up in rc.local. I don't know why xorg dies, but it might fix the tty2 thing.
Last edited by Lexion (2009-08-05 14:57:54)
urxvtc / wmii / zsh / configs / onebluecat.net
Arch will not hold your hand
Offline
Ok first of.. Apologies..
GDM is actually in rc.conf not local. I always mix those up.
Also .. It only dies once per boot.
Xorg is starting on tty2, but so is getty. From what I can tell the getty gets grumpy that its not mapped to tty2 and its set to respawn so it does and kicks Xorg off the tty.
Then because tty1-6 are all now taken GDM restarts and ends up on tty7.
There are other distro's having this issue.. but that's mainly because they changed X to tty1. Their "fix" (read: dirty hack) to get things working is to comment out/stop via command line the getty on tty2. If it doesn't restart, things are fine.
Moreover..
Im not an inittab expert.. but that line doesn't look like it would do what I want.
I'm running at level 3. That looks like it is for level 7?
I mean in my current setup
x:3:respawn:/usr/sbin/gdm -nodaemon
could work.. and if I comment out the line
c2:2345:respawn:/sbin/agetty -8 38400 tty2 linux
Then I would be ok.
It just seems that something has changed in a package recently.
Or the getty's are starting up later than they used to.
Last edited by insanemal (2009-08-05 15:30:03)
Offline
My bad on the inittab thing. Sorry.
You can look at the pacman log (/var/log/pacman.log) to find out what packages have been changed/installed/removed over time.
urxvtc / wmii / zsh / configs / onebluecat.net
Arch will not hold your hand
Offline
I know what upgrades could have caused it. But That's the thing, It started yesterday morning. Im pretty sure that was the update with the new inittab and the mesa/dri upgrades.
The odd thing is my current inittab and the inittab.pacsave look the same. And if a new dri causes it, it means it was always an issue. So Im at a loss.
I'm more "worried" that when building a new Arch box I will encounter this same issue, as will anybody following any of the guides. As they all recomend starting gdm from your rc.conf as a daemon.
Offline
Just because the inittab and inittab.pacsave are the same doesn't mean that the inittab program doesn't interpret them the same.
And also, is gdm still starting in tty2?
urxvtc / wmii / zsh / configs / onebluecat.net
Arch will not hold your hand
Offline
at the moment it is.. But I have commented out the getty on tty2.
so its all good..
But Still no reall answer as to why this suddenly started.
Offline
Insanemal: this is why:
http://bbs.archlinux.org/viewtopic.php?id=76260
I don't see the benefit of running X on tty2 or anything, I just have two gettys running on tty1 and tty2, the rest has been disabled. X runs on tty7 like usual.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
Yeah I figured that was the cause.
But what I still don't get is why X is loading on tty2.
I don't want it on 2. I want it on 7. I did try to force it to 7 but it wouldn't work.
It feels like the GDM is grabbing the tty before the getty's load.
What I don't get is why the change caused that to happen.
Also my .pacsave and original inittab both used tty's (also the diff claims they are the same)
Offline
What about .pacnew ?
English is not my native language .
Offline
The Pacnew and the current file are identical.
This is why im really stumped.
Offline
The Pacnew and the current file are identical.
This is why im really stumped.
So you have 3 identical files .
"inittab" , "inittab.pacsave" & "inittab.pacnew" ?
English is not my native language .
Offline
I have gdm relatively early in rc.conf and got the same thing, the agettys getting spawned too late.
In /etc/gdm/custom.conf append this line in the [servers] section:
0=Standard vt7
Last edited by ap0 (2009-08-12 02:29:33)
Offline
ap0: you are a saint.
This is exactly the kind of fix I was hoping for.
The only thing that still remains odd is that my gdm starts as the last thing in my rc.conf, However I do start a lot of things in Background. That explains that quite nicely.
Offline
Well, this makes sense to me now:
We fixed a bug in the times there were no /dev/tty* devices on archlinux:
sed -i -e 's|/dev/tty%d|/dev/vc/%d|' daemon/getvt.c || return 1
Now it's the other way around. The results I remember from back then are frozen keyboard input on bootup, but not this behaviour.
Offline
So is there an "other way around" fix?
It just seems that this is starting to crop up a bit.
Offline
In /etc/gdm/custom.conf append this line in the [servers] section:
0=Standard vt7
This seems to have fixed my random logout issue. Thanks ap0!
If the advice you're given in this forum solves your issue, please mark the post as [SOLVED] in consideration to others.
"More than any time in history mankind faces a crossroads. One path leads to despair and utter hopelessness, the other to total extinction.
Let us pray that we have the wisdom to choose correctly." -- Woody Allen
Offline
ap0 wrote:In /etc/gdm/custom.conf append this line in the [servers] section:
0=Standard vt7
This seems to have fixed my random logout issue. Thanks ap0!
Hello I have the same problem... but this doesn't work for me...
First I don't have any [servers] tab in my custom.conf ... but anyway I create it and nothing gets fixed... I keep getting xorg dieing and gdm reloading...
Any ideas?
Offline
Hello I have the same problem... but this doesn't work for me...
First I don't have any [servers] tab in my custom.conf ... but anyway I create it and nothing gets fixed... I keep getting xorg dieing and gdm reloading...
Any ideas?
Hi, I've got the same problem, i added [servers] myself and the line also, I rebooted and I still have the problem. Any idea what to do?!
i'm runnig Archlinux x86_64.
Last edited by ArianHT (2009-12-07 14:30:59)
Offline
For the current version of gdm, you should just make sure gdm is launched as last daemon. This can be done by putting it as last daemon in DAEMONS, but also by placing it in inittab. Other configurations are not supported and will crash.
Offline
I've tried everything suggested in this thread and Xorg/GDM is still opening up in tty2 and I'm still experiencing random (and incredibly frustrating, I may add) freezes.
Offline
I've tried everything suggested in this thread and Xorg/GDM is still opening up in tty2 and I'm still experiencing random (and incredibly frustrating, I may add) freezes.
If you removed the agetty from tty2 you would not have the issue OR if you changed to run level 5 and called GDM from inittab. Both of these options resolve the issue.
Heck loading GDM as the last item in your deamons line sorts it out also.
Most of the options left in this thread are old.
Offline