You are not logged in.
I had this problem using nvidia and intel graphics. So the title of the bug report is not completely accurate.
Offline
I use Nvidia. I have been using 4.3.2 since the day it came out. I've not faced this problem. Can anyone please tell me why this is happening to someusers? I'm really interested to know. i'm supposed to setup my bro's pc in a couple of days and was looking forward to install Arch with 4.3.2 on it. Since he is no computer geek, he won't be able to fix problems on his own, so I'd rather install slack for him. Any clue on why this is happening.
EDIT: Just saw the bug report, since he doesn't have ati card things are fine.
EDIT2:
I had this problem using nvidia and intel graphics. So the title of the bug report is not completely accurate.
I just saw this.. Oops
Last edited by sHyLoCk (2009-10-15 14:05:50)
Offline
For people who found this thread in the forums looking for a solution or workaround, the proposed solution from Musikolo does the job:
When kdm is not the last item in the DAEMONS-list in /etc/rc.conf, Xorg will start on tty3 instead of tty7. Moving kdm to the end of the line, will move Xorg back to tty7 and the problem will be gone
Offline
I know this is an old thread, but noticing the solution I was wondering why you even have kdm in rc.conf? I mean if you want graphical startup I think /etc/inittab is the way to go:
molinari@Helios ~]$ grep -v \# /etc/inittab
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
c1:2345:respawn:/sbin/agetty -8 38400 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
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
x:5:respawn:/usr/bin/kdm -nodaemon
Last edited by mcsaba77 (2009-10-24 19:00:52)
Offline
I know this is an old thread, but noticing the solution I was wondering why you even have kdm in rc.conf? I mean if you want graphical startup I think /etc/inittab is the way to go:
Why not? There's a nice kdm (or gdm) daemon in /etc/init.d/, so why not use it? (apart from this specific bug).
You can of course do it in /etc/inittab, just like you can compile your own kernel instead of using the stock kernel from Arch Linux...I just like to keep my system clean, therefore I use pacman for package management whenever possible and use the Arch Linux configuration files whenever possible in order to keep the system nice and clean.
Best Regards
Kenni
Last edited by Kenni (2009-10-24 20:18:12)
Offline
I think this problem is fixed with the lastest updates. I'm using kdm again and have not had any crashes since like a week or so.
Offline
Cool I haven't tested it after moving kdm to the end of the DAEMONS line. I'll test it within a few days and write a reply in the bugtracker, so we can get the dual-bug-bugreport closed
Offline
Do you run with the testing repository enabled?
I just did a full system upgrade (testing disabled) and my system still starts X on tty3 instead of tty7, if I don't put kdm as the last item in the DAEMONS line.
However, it doesn't seem to crash when I do things which made the system crash before the upgrade....BUT, now I'm not able to change to any of the virtual terminals by pressing Ctrl+Alt+[1,2,4,5,6]!!!
Anyway, I don't want to spend more time on this weird bug, just ensure that kdm is the last item in the DAEMONS line in /etc/rc.conf and you'll be fine
Offline
I don't really know if I had the tty problems you mention. I only noticed the crashes.
Offline
I don't really know if I had the tty problems you mention. I only noticed the crashes.
To test it out, just do this:
- When you are in KDM, presss Alt+Ctrl+F1. Should you get a tty1 (terminal)
- Being in tty1, press Alt+F3. If you get back to KDM, you have a problem because KDM shouldn't be there. Otherwise, if you get another terminal, everything is OK and you should get KDM by pressing Alt+F7.
In case KDM is using tty3, the only workaround found to far, is to change the kdm daemon to the end of you DAEMONS list in your /etc/rc.conf file. Please, have a look at this for details: http://bugs.archlinux.org/task/16587
Best regards!
Offline
It seems that the tty3 problem comes from the kdm configuration file : /usr/share/config/kdm/kdmrc
If your kdm is using tty3, you may have this config
ServerVTs=-3
ConsoleTTYs=tty1,tty2
then you can tell kdm to use tty7 instead
ServerVTs=-7
ConsoleTTYs=tty1,tty2,tty3,tty4,tty5,tty6
Offline
It seems that the tty3 problem comes from the kdm configuration file : /usr/share/config/kdm/kdmrc
If your kdm is using tty3, you may have this configServerVTs=-3 ConsoleTTYs=tty1,tty2
then you can tell kdm to use tty7 instead
ServerVTs=-7 ConsoleTTYs=tty1,tty2,tty3,tty4,tty5,tty6
Ok... but have you even read what this thread is all about? If you had, I suppose you would not have posted this. The problem is not how to make X start on a specific tty, it's about why the sequence of daemons unreleated to X, can cause X to start on tty3 and why this causes KDE to crash....
Offline
Hi,
@mcsaba77
I have replace my /usr/share/config/kdm/kdmrc for /usr/share/config/kdm/kdmrc.pacsave and I have noticed everything has sorted out!
Thanks a lot for the tip.
Best regards!
Offline
Hello.
I have the same problem of ramdon crashes and X on TTY3, but...
I have a Nvidia running in a x64 Arch AND gnome.
I've been looking a fix for a few days until end here. But looks like all of you have this weird bug only with KDE. I've moved GDM to the end of the DAEMONS-line. But Gnome is still on TTY3. At least, I hope, the crashes are gone.
My DAEMONS: DAEMONS=(syslog-ng !!network netfs crond hal fam stbd alsa bluetooth rpcbind wicd dbus sensord gdm)
Any ideas?
Last edited by [KNS]Kumo (2009-11-06 11:32:08)
Ore wa Kumo Da!
http://knsweb.net
Offline
Hi,
I don't use Gnome and, thus, I have no idea how its files are stored. However, I figure out there should be some sort of file similar to /usr/share/config/kdm/kdmrc but for Gnome, something like /usr/share/config/gdm/gdmrc. Check if you have it and, if so, try to replace it for the one ending in .pacsave. Of course, do a back up copy before chaging anything.
I hope it helps.
Best regards!
Last edited by Musikolo (2009-11-06 13:48:48)
Offline
Thans for the reply. I'm going to try it and tell you. BTW the crashes have ceased. So the fix also works in Gnome and Nvidia.
Ore wa Kumo Da!
http://knsweb.net
Offline