Hi,
I've just updated F19 and after reboot I do not get the usual kdm login screen. The graphic screen with the F stays there forever.
I can login in text mode and run 'startx' and I get to the normal KDE session.
Looking at the logs I only noticed
[FAILED] Wait for Plymouh Boot Screen to quit
and in /var/log/messages
there is something about
Sep 21 15:24:35 localhost kdm[335]: plymouth --ping -> 0 Sep 21 15:24:35 localhost kdm[335]: plymouth is running ... Sep 21 15:24:35 localhost kdm[335]: plymouth deactivate -> 0 Sep 21 15:24:35 localhost kdm[335]: plymouth --has-active-vt -> 0 Sep 21 15:24:35 localhost kdm[335]: plymouth should quit when server starts Sep 21 15:24:36 localhost kdm[335]: plymouth is active on VT 1, reusing for :0 Sep 21 15:24:36 localhost kdm[335]: X server startup timeout, terminating Sep 21 15:24:36 localhost kdm[335]: X server for display :0 cannot be started, session disabled
any idea?
Am 21.09.2013 16:39, schrieb andrea:
I've just updated F19 and after reboot I do not get the usual kdm login screen. The graphic screen with the F stays there forever.
I can login in text mode and run 'startx' and I get to the normal KDE session.
Looking at the logs I only noticed [FAILED] Wait for Plymouh Boot Screen to quit
and in /var/log/messages
there is something about Sep 21 15:24:35 localhost kdm[335]: plymouth --ping -> 0 Sep 21 15:24:35 localhost kdm[335]: plymouth is running ... Sep 21 15:24:35 localhost kdm[335]: plymouth deactivate -> 0 Sep 21 15:24:35 localhost kdm[335]: plymouth --has-active-vt -> 0 Sep 21 15:24:35 localhost kdm[335]: plymouth should quit when server starts Sep 21 15:24:36 localhost kdm[335]: plymouth is active on VT 1, reusing for :0 Sep 21 15:24:36 localhost kdm[335]: X server startup timeout, terminating Sep 21 15:24:36 localhost kdm[335]: X server for display :0 cannot be started, session disabled
add the following params to the kernel line
rd.plymouth=0 plymouth.enable=0
somewhere at start of the boot process you need to press a key or whatever to see the grub-menu at all because "smart" people decided it is more beautiful to hide basic things from users
On 21/09/13 15:39, andrea wrote:
Hi,
I've just updated F19 and after reboot I do not get the usual kdm login screen. The graphic screen with the F stays there forever.
I can login in text mode and run 'startx' and I get to the normal KDE session.
Looking at the logs I only noticed
[FAILED] Wait for Plymouh Boot Screen to quit
and in /var/log/messages
there is something about
Sep 21 15:24:35 localhost kdm[335]: plymouth --ping -> 0 Sep 21 15:24:35 localhost kdm[335]: plymouth is running ... Sep 21 15:24:35 localhost kdm[335]: plymouth deactivate -> 0 Sep 21 15:24:35 localhost kdm[335]: plymouth --has-active-vt -> 0 Sep 21 15:24:35 localhost kdm[335]: plymouth should quit when server starts Sep 21 15:24:36 localhost kdm[335]: plymouth is active on VT 1, reusing for :0 Sep 21 15:24:36 localhost kdm[335]: X server startup timeout, terminating Sep 21 15:24:36 localhost kdm[335]: X server for display :0 cannot be started, session disabled
any idea?
in the end something damaged in /var/log/journal
google it, it turned out that some services took too long to start. not too sure, but renaming that folder fixed it.
On Saturday, September 21, 2013 07:34:42 PM andrea wrote:
[FAILED] Wait for Plymouh Boot Screen to quit
and in /var/log/messages
there is something about
Sep 21 15:24:35 localhost kdm[335]: plymouth --ping -> 0 Sep 21 15:24:35 localhost kdm[335]: plymouth is running ... Sep 21 15:24:35 localhost kdm[335]: plymouth deactivate -> 0 Sep 21 15:24:35 localhost kdm[335]: plymouth --has-active-vt -> 0 Sep 21 15:24:35 localhost kdm[335]: plymouth should quit when server starts Sep 21 15:24:36 localhost kdm[335]: plymouth is active on VT 1, reusing for :0 Sep 21 15:24:36 localhost kdm[335]: X server startup timeout, terminating Sep 21 15:24:36 localhost kdm[335]: X server for display :0 cannot be started, session disabled>
any idea?
in the end something damaged in /var/log/journal
google it, it turned out that some services took too long to start. not too sure, but renaming that folder fixed it.
What did you find "damaged" in /var/log/journal? I ask because I see this KDM failure as well, only on one of my machines, but journalctl --verify passes with flying colors. Also, when I issue systemctl restart display-manager after the initial failure, KDM starts properly.
-A
On 22/09/13 09:01, Anthony Messina wrote:
What did you find "damaged" in /var/log/journal? I ask because I see this KDM failure as well, only on one of my machines, but journalctl --verify passes with flying colors. Also, when I issue systemctl restart display-manager after the initial failure, KDM starts properly.
no idea
I followed this suggestion.
http://www.linuxquestions.org/questions/fedora-35/fedora-boot-problem-417546...
On 09/21/2013 07:52 AM, Reindl Harald wrote:
somewhere at start of the boot process you need to press a key or whatever to see the grub-menu at all because "smart" people decided it is more beautiful to hide basic things from users
It's not so much their hiding things from users that I object to, it's making it the default. Yes, you should be able to hide the menu if that's what floats your boat, but it shouldn't start out hidden; it should (IMAO) start out visible, with a fairly easy method of toggling. That way, newcomers to Linux will see the menu every time until they learn enough (and get enough confidence) to turn it off, and by that time, they should at least know that the menu's there even if they've forgotten how to toggle it. If nothing else, it should be active on a new install until firstboot runs. That way, if you need to boot into either rescue or CLI mode because your install b0rk, you've got the chance. (If so, firstboot can always ask if you want the menu, with an explanation for beginners of why it might be a Good Idea.)
On 21/09/13 15:39, andrea wrote:
Hi,
I've just updated F19 and after reboot I do not get the usual kdm login screen. The graphic screen with the F stays there forever.
I can login in text mode and run 'startx' and I get to the normal KDE session.
Looking at the logs I only noticed
[FAILED] Wait for Plymouh Boot Screen to quit
and in /var/log/messages
there is something about
Sep 21 15:24:35 localhost kdm[335]: plymouth --ping -> 0 Sep 21 15:24:35 localhost kdm[335]: plymouth is running ... Sep 21 15:24:35 localhost kdm[335]: plymouth deactivate -> 0 Sep 21 15:24:35 localhost kdm[335]: plymouth --has-active-vt -> 0 Sep 21 15:24:35 localhost kdm[335]: plymouth should quit when server starts Sep 21 15:24:36 localhost kdm[335]: plymouth is active on VT 1, reusing for :0 Sep 21 15:24:36 localhost kdm[335]: X server startup timeout, terminating Sep 21 15:24:36 localhost kdm[335]: X server for display :0 cannot be started, session disabled
any idea?
It happened again. The main console is stuck with the list of all services and the only error is
[FAILED] Failed to start Wait for Plymouth Boot Screen to Quit
I have run startx from an other console. Let's hope deleting the usual /var/... folder will fix it.
Andrea
On 16/10/13 20:07, andrea wrote:
It happened again. The main console is stuck with the list of all services and the only error is
[FAILED] Failed to start Wait for Plymouth Boot Screen to Quit
I have run startx from an other console. Let's hope deleting the usual /var/... folder will fix it.
yes it did the job. it is a lot more widespread the I though
andrea wrote:
It happened again. The main console is stuck with the list of all services and the only error is
[FAILED] Failed to start Wait for Plymouth Boot Screen to Quit
I have run startx from an other console. Let's hope deleting the usual /var/... folder will fix it.
My workaround for @work machines, edit /etc/systemd/journald.conf to contain:
Storage=volatile
(reboot). Haven't had any problems since.
-- Rex
Wed, 16 Oct 2013 15:26:09 -0500 Rex Dieter rdieter@math.unl.edu kirjoitti:
My workaround for @work machines, edit /etc/systemd/journald.conf to contain:
Storage=volatile
(reboot). Haven't had any problems since.
-- Rex
Now, why is that journald.conf there? As I look inside it, all line are commented out?
Only what helped first hand was to rename /var/log/journal into journal.org. Also I disabled Plymouth, because I don't see anything useful to me, only one thing more slower my old pc :).
Jarmo
jarmo wrote:
Wed, 16 Oct 2013 15:26:09 -0500 Rex Dieter rdieter@math.unl.edu kirjoitti:
My workaround for @work machines, edit /etc/systemd/journald.conf to contain:
Storage=volatile
(reboot). Haven't had any problems since.
-- Rex
Now, why is that journald.conf there? As I look inside it, all line are commented out?
I think those commented-out lines represent the software defaults.
Only what helped first hand was to rename /var/log/journal into journal.org.
That is a one-time equivalent to what I suggested (which essentially clears journal on every boot, not just when you do it manually).
-- Rex
-
Andrea -
Anthony Joseph Messina -
jarmo -
Joe Zeff -
Reindl Harald -
Rex Dieter