Bug 55923
| Summary: | startx results in keyboard lockup and mingetty looping | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Raw Hide | Reporter: | Joshua J. Drake <jdrake> |
| Component: | XFree86 | Assignee: | Mike A. Harris <mharris> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-04-20 12:08:54 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Joshua J. Drake
2001-11-08 20:54:39 UTC
What are the permissions on /dev/tty1, or /dev/tty2? I am logged in running startx on tty1. crw--w---- 1 jdrake tty 4, 1 Nov 8 12:13 /dev/tty1 There is currently no login on tty2. crw------- 1 root root 4, 2 Nov 8 12:07 /dev/tty2 At first I was executing "startx & sleep 40 ; clear ;logout" but assuming that was the problem I reverted to not logging out and it still occurred. The first time I tried to restart X after upgrading was on tty1 and then on tty2. Additionally even after exiting X I cannot get back to console without logging in remotely and running startx as root and exiting it. After a while of testing I completely lost access to console and had to reboot remotely. It works for me. Looks like some sort of local misconfiguration issue. I have been struggling with the exact same problem, when X is started from inittab x respawns too fast with the identical keyboard local problem sometime after starting a session. I also cannot get back to console after lockup...I have not changed any configuration files. I use KDE but I started X explicitly from console and the same things happened. Something has changed some place perhaps not X itself that is causing the problem. I had this with three different computers!!!! OK.....I had dealt with this problem a couple of years ago. There is a file /etc/sysconfig/i18n which is read from /etc/profile.d/lang.sh which is executed from /etc/X11/prefdm. In this file there are three lines: LANG="en_US" SYSFONT="lat0-sun16" SYSFONTACM="iso01" The last two should not be there OR the whole file should not be there. When I do rpm -q -f /etc/sysconfig/i18n rpm sais this file does not belong to any package! It seems like something put it there but did not remove it. That file does not exist on my machine. Therefore I assume it could not be the problem. Furthermore I don't even use prefdm or and display manager.. It works fine if I run just enlighenment, but with gnome-session and enlightenment it locks up. Yes....the /etc/sysconfig/i18n did cure by "x" respawning too fast problem but the lockup is still there. In my case it is now happening when I leave the system with either xlock or kdm screens for a long time!! It used to happen every minute while typing in konsole window etc. and even with pure X with no window managers. What kernel are you running? MHARRIS (Mike?)....I think this is a real bug introduced by some other package in rawhide because it started happening to jdrake and me at about the same time. I downgraded two systems down to earlier rawhide/7.2 and they are not locking up anymore. it just happened again, but this time without gnome... what i did: 1. sitting in X, ctrl-alt-f3 to get back to console 2. typed in %s%s%s for login name 3. switched back to X 4. continued use as normal... now when mingetty timed out and respawned the "Operation not permitted" messages started the keyboard locked up and i could not do anything with it, but the mouse still worked.. using gcharmap to copy/paste to type i saw that no process was taking a large amount of cpu, but gkrellm was showing 99%.. upon trying to run startx -- -verbose 999 i got a bunch of "select returned 0" messages when the keyboard stopped responding... unlike before, I can't get back to console at all now, i will have to reboot.. i'm fairly sure that the problem lies with XFree86. It is still happening here too (XFree86-4.1.0-9 and latest rawhide always). In my case now keyboard locks after I leave the system at the kdm login screen for a long time - e.g. goes into black screen mode and it starts frantically restarting itself e.g. the screen is black but you see a line across coming on and off very fast....something is respawning very fast. Just a thought.....is everything compiled with the new png package? I had to recompile all of KDE-2.2.2 packages and qt, and some others that I noticed were having incompatibility problems if they were compiled with the older png. I have similar problems as follows: 1. sometimes my keyboard locks up (in X), mouse still works, system is still running, at the same time as the keyboard locks up the following lines appear in /var/log/messages: Dec 16 00:26:32 avenger /sbin/mingetty[1727]: /dev/tty2: cannot open tty: Operation not permitted If i try to leave X by closing it, the whole system goes black, i don't get back to the virtual console. If i cut/paste a reboot command by mouse (now i always have a root window with reboot pre-typed :), the system will reboot but i don't see any console messages. 2. if the system is left unattended in X it first goes screensaving (good), but then the screen starts flickering as if the screensaver switches on/off really fast. Moving the mouse heals it, hitting a key won't (as the keyboard is already frozen by this time). 3. if the system is left unattended in X (maybe 1 download running) its harddisk starts running, the system slows down completely. (keyboard don't work, mouse works at a rate of 1 click/minute). 4. not related but, at startup i get a message that X cannot establish a connection to the esound driver (not exactly these words), i have an option f1/f2/f3, pressing f2 always succeed to make the sound working. esound version: 0.2.22-5 XFree86 version: 4.1.0-12 enlightenment: 0.16.4-11 I have no gnome/KDE so this should be some core XFree86 bug(s). The problem is around at least since the beginning of november, but i always hoped a new upgrade will fix it. :( DEFERRING bug awaiting upstream XFree86.org fix in future release of XFree86. Since this bugzilla report was filed, there have been several major
updates to the X Window System, which may resolve this issue. Users
who have experienced this problem are encouraged to upgrade to the
latest version of Fedora Core, which can be obtained from:
http://fedora.redhat.com/download
If this issue turns out to still be reproduceable in the latest
version of Fedora Core, please file a bug report in the X.Org
bugzilla located at http://bugs.freedesktop.org in the "xorg"
component.
Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes that
become available for consideration in future updates.
Setting status to "CURRENTRELEASE".
|