Arch Linux

I can confirm this bug. Same slim version, x86_64.

Is there a reason you're not starting slim via the recommended way? By recommended I mean via /etc/rc.conf or /etc/inittab? Considering this bug is from 2008 I doubt the upstream devs are going to do anything about it. I'd rather not patch the source if this is not an essential feature.

I'm using inittab.

@thayer: and what should be the unrecommended way?
By the way I am using /etc/rc.conf

Both methods should be fine, but I was confused by the opening sentence that you're starting the daemon from TTY1 (I assumed you meant manually or something).

I'll take a closer look this morning and try to reproduce the problem.

So far I'm unable to reproduce this behaviour. Could you post the slim config (/etc/slim.conf) and slim startup script (either /etc/rc.conf or /etc/inittab respectively)?

Also, when did this behaviour start and is it only TTY1 that is affected?

@thayer: the problem is very common (just see the forum)
According to what I heard the broken tty is the one wich starts slim as daemon.

Thanks for the files, a cursory glance at our forums didn't turn up much other than this: http://bbs.archlinux.org/viewtopic.php?id=90662 (which was solved).

I think there's something else going on here, otherwise we would have heard about this much sooner (we've got a lot of slim users). I see a number of recent TTY problems relating to Intel KMS mode and/or keymaps. I'll see if I can dig up some more details, but in the meantime if you know of any recent Arch discussions regarding these slim problems please point me to them.

Edit: Nevermind about the threads, found some (FluxBB keyword searches could sure use some improvement). I'm looking into it.

http://bbs.archlinux.org/viewtopic.php?pid=716221
http://bbs.archlinux.org/viewtopic.php?id=78002

The topic was marked as solved because the author passed from slim to gdm. I can't consider that as a solved issue.
I frequent the Italian archlinux forum and some slim users have noticed this issue too -> http://www.archlinux.it/forum/viewtopic.php?id=7466 (But I think you can't understand Italian :P ). Anyhow there aren't solutions there.
I have an nvidia card and I use the nvidia proprietary driver (on x86_64).

I use xf86-video-ati.

I've updated the PKGBUILD using the upstream patch, but cannot test on x86_64. I don't want to commit this until I know it resolves the problem. To test:

1. grab and extract this tarball: http://cinderwick.ca/tmp/slim-pkgbuild-ttyfix.tar.gz
2. cd to extracted directory in a terminal
3. type 'makepkg -srci'

If either of you can try this for me, let me know if that takes care of things. It seems to work fine on 686 arch, but then again so does the unpatched version.

The pkgbuild needs the file 'slim.pam'

Sorry about that, I've updated the tarball:

http://cinderwick.ca/tmp/slim-pkgbuild-ttyfix.tar.gz

@thayer: now the problem seems solved! :)
I tried all ttys and I don't notice differences among them. Writing on the tty1 is normal as it should be.

Alright sounds good, I'll push out the update later this morning. Thanks for your help with this!