I've been trying to test kdm/plymouth integration on f13, and I thought I got the patching all right, but kdm still starts on vt7. Then, I noticed that /var/spool/gdm dir timestamp never changes on booting. If, prior to rebooting, I manually, touch /var/spool/gdm/force-display-on-active-vt X starts probably on vt1. So, by what mechanism is /var/spool/gdm/force-display-on-active-vt supposed to get created, or how could it be possibly failing? afaik, my oldish i945 video hardware supports plymouth, and I see the graphical boot ok.
s/probably/properly/ above, makes a little more sense that way. :)
Hi, Touching "/var/spool/gdm/force-display-on-active-vt" also works - always - with plymouth text mode (horizontal bar) non-kms. X is sitting on vt1. 'File' "force-display-on-active-vt" is removed/gone. After the next reboot - without touching the file - x sits again on vt7. Hope this helps. Martin Kho
Not really, but thanks. :) force-display-on-active-vt is supposed to get created only in when kms is used. That's my understanding, anyway.
nope, force-display-on-active-vt is created any time plymouth quit --retain-splash is run (as done by prefdm). Doesn't actually check for kms or not.
Hi, I suppose it's a very very dirty trick, but I changed in prefdm: elif [ "$DISPLAYMANAGER" = KDE ]; then preferred=/usr/bin/kdm to elif [ "$DISPLAYMANAGER" = KDE ]; then preferred=/usr/bin/kdm quit_arg="--retain-splash" Now X sits on vt1 :-) Martin Kho
I guess that's not a dirty trick, but the fix which needs to get into the package ASAP. /etc/X11/prefdm is owned by initscripts, reassigning.
Is there a particular version of KDM that grew support for this, or can we assume that anything in F-13 is good enough?
http://git.fedorahosted.org/git/?p=initscripts.git;a=commitdiff;h=4b63e3e866a7f3962cd2e304ab4c0145d8ce388a Will get pushed out in the next couple of days.
The current KDM builds in F12 updates and F13 both support this. This should also get added to the F12 initscripts (we've discussed this in the KDE SIG meeting, with Ray Strode (halfline) also present).
initscripts-9.02.2-1 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/initscripts-9.02.2-1
initscripts-9.10-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/initscripts-9.10-1.fc13
Thanks Martin! extra cookies and gold stars for you.
initscripts-9.02.2-1 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update initscripts'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/initscripts-9.02.2-1
the update for f13: https://admin.fedoraproject.org/updates/initscripts-9.11-1.fc13 now has sufficient karma to be pushed to stable; can you please submit it to stable, Bill? thanks.
It is submitted for stable.
initscripts-9.11-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
bodhi didn't show it as having been submitted...
initscripts-9.02.2-1 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.