Summary: | If LXDE session is running the kbd input on tty1 is broken (need to press keys twice) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alex <lk> |
Component: | Current packages | Assignee: | LXDE team (DEFUNCT) <lxde+disabled> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | anarchy, xmw |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Requested Xorg.0.log file |
Description
Alex
2012-05-23 09:25:08 UTC
This behaviour sound familiar, Can you post the output of `ps ax | egrep (tty|X)` and the current (newest) /var/log/Xorg.*.log file _after_ you logged in on the lxdm/LXDE session? I assume that any agetty battles with X for the input of an particular terminal. These are the results: ps ax | egrep '(tty|X)' 2960 tty7 Ss+ 0:01 /usr/bin/X :0 vt07 -nolisten tcp 3115 tty1 Ss+ 0:00 /sbin/agetty 38400 tty1 linux 3116 tty2 Ss+ 0:00 /sbin/agetty 38400 tty2 linux 3117 tty3 Ss+ 0:00 /sbin/agetty 38400 tty3 linux 3199 ? Ss 0:00 /usr/bin/lxsession -s LXDE -e LXDE 3215 ? S 0:00 lxpanel --profile LXDE 3216 ? S 0:00 pcmanfm --desktop --profile LXDE 3512 pts/0 S+ 0:00 egrep (tty|X) /var/log/Xorg.0.log is attahced. I did a reboot just before to make things clear and have not attempted in anyway to log in on tty1. I clearly have logged into lxde because I'm writing this in a graphical environment. What drives me crazy that my other x86 is free of this trouble. As I wrote it has /etc/lxdm/xinitrc file but again as I wrote, bringing this file on the problematic system did not resolve the issue. Created attachment 312793 [details]
Requested Xorg.0.log file
Due to HDD crash I had to reinstall the sytem from scratch on x86 laptop and now I can say that the behavior is identical on all 3 laptops I have: input on the tty1 is broken. I do not know what have significantly changed in the renewed x86 but at least now I have a filling that this is platform independent feature. Not sure this helps a lot but is an info anyway. As this is a pretty old bug may I ask if this still happens with latest versions of the LXDE packages? Closing as obsolete, please re-open if you can reproduce on a current system. |