Created attachment 323712 [details] dmesg Description of problem: When I - login to GNOME session - launch something (like xterm and so on) - type a, (backspace), 5, so on my computer beeps, which is very annoying Version-Release number of selected component (if applicable): kernel-2.6.27.5-109.fc10.i686 xorg-x11-drv-i810-2.5.0-3.fc10.i386 xorg-x11-server-Xorg-1.5.2-12.fc10.i386 How reproducible: 100% Steps to Reproduce: 1. See above 2. 3.
Created attachment 323713 [details] Xorg.0.log Note: there is no xorg.conf
Once changing to iniscripts. initscripts-8.86-1 This can be reproduced by the following: - Reboot without rhgb option and with runlevel 3 - login to tty1 as root (not tty1 is used) - on tty1, type $ init 5 - X launches, on tty1, not on tty7 - On tty1 (now gdm login session appears) type username - Every time I type 'a' or so, annoying beep can be heared - Now CTRL-ALT-F2 - login on tty2 as root, then type $ init 3 - Then CTRL-ALT-F1 - on tty1, _some garbage messages are now shown_ - on tty1, once type CTRL-C and again $ init 5 - This time X lauches on tty7
(In reply to comment #2) > Once changing to iniscripts. > initscripts-8.86-1 > > This can be reproduced by the following: > > - Reboot without rhgb option and with runlevel 3 > - login to tty1 as root (not tty1 is used) This is "now tty1 is used"...
If we're not going down the road of managing gdm force-tty behavior from the event files themselves, then plymouth needs to not write the magic file on runlevel 3.
fix building as plymouth-0.6.0-0.2008.11.17.2
It seems that I am still seeing this issue with kernel-2.6.27.5-109.fc10 plymouth-0.6.0-0.2008.11.17.2.fc10
did you rebuild your initrd after installing the latest plymouth? you can do that with /usr/libexec/plymouth/plymouth-update-initrd (or reinstall your kernel)
(In reply to comment #7) > did you rebuild your initrd after installing the latest plymouth? > you can do that with > /usr/libexec/plymouth/plymouth-update-initrd > (or reinstall your kernel) Ah, thanks. Actually that works.
Closing, thank you.
*** Bug 471504 has been marked as a duplicate of this bug. ***