No screen after todays updates

[roger]

Hi,

after todays updates, i get no screen-output on login screen. The boot-splash comes as usual. when switching to gdm-login, finito, black!

---------- Post added at 10:25 AM ---------- Previous post was at 10:19 AM ----------

FOUND:

Something is blocking boot, while boot, the last message is:
Stopping Systemd Syslog Kernel Buffer Bridge

Eventually Selinux related, as booting with selinux=0 boots as expected.

[kraekan]

Hi,

after todays updates, i get no screen-output on login screen. The boot-splash comes as usual. when switching to gdm-login, finito, black!

---------- Post added at 10:25 AM ---------- Previous post was at 10:19 AM ----------

FOUND:

Something is blocking boot, while boot, the last message is:
Stopping Systemd Syslog Kernel Buffer Bridge

Eventually Selinux related, as booting with selinux=0 boots as expected.

Had the same. I think enforcing=0 is preferred to avoid labelling problems.

[Umbi67]

Hi,

after todays updates, i get no screen-output on login screen. The boot-splash comes as usual. when switching to gdm-login, finito, black!

---------- Post added at 10:25 AM ---------- Previous post was at 10:19 AM ----------

FOUND:

Something is blocking boot, while boot, the last message is:
Stopping Systemd Syslog Kernel Buffer Bridge

Eventually Selinux related, as booting with selinux=0 boots as expected.

Same problem .... same solution !! Thanks !!

[Boricua]

Had the same. I think enforcing=0 is preferred to avoid labelling problems.

Applied and working, thanks! . Of all these updates, any idea which one(s) would be the offending rpm(s)?

[katastrophal]

I think it's systemd (again).

[williamove]

The fix worked well for me too. I am amazed at the speed with which you sort out problems and find solutions. I am a long time Ubuntu user, who came to Fedora looking for Gnome 3 and I am quite imressed with what I have found.

bill

[Boricua]

I think it's systemd (again).

Thanks again katastrophal. Applying a quarantine to the suspect .

[kurtdriver]

Thanks again katastrophal. Applying a quarantine to the suspect .

Can you please report on the results?

[roger]

i tried, if it could be a relabelling issue after the update and did a complete relabelling from filesystem. It is still the same error.

[kurtdriver]

Oh well, thanks. selinux=0 it is.

[troyatlarge]

I had the same thing this morning, or I think the same thing. Mine appeared to load where you guys had your stop - technically it said:

Starting sandboxstopping systemd Syslog Kernel Log Buffer Bridge .......
[OK]

and would not move beyond that.

In any event, how do you get selinux=0 placed in the system??

[Boricua]

Can you please report on the results?

No problem. Right now I'm in a slow connection but will try tonight.

---------- Post added at 10:58 AM ---------- Previous post was at 10:54 AM ----------

I had the same thing this morning, or I think the same thing. Mine appeared to load where you guys had your stop - technically it said:

Starting sandboxstopping systemd Syslog Kernel Log Buffer Bridge .......
[OK]

and would not move beyond that.

In any event, how do you get selinux=0 placed in the system??

What I did was modifying the kernel parameters in grub and adding enforcing=0. I noted that my system was stopping at different levels each time I reboot.

[DBelton]

man I sure got a surprise!

I updated, and went to reboot. systemd locked up as others have noted.

I tried again with enforcing=0 and it worked.. But now for the big surprise...

I had some programs installed for my work in a folder.. (the folder isn't configurable on my system and the apps won't work if they have been altered in any way)

Well, systemd just flat out took that folder over, no warning, no nothing, and wrote all kinds of stuff into it... I can't get to my apps any more. WTF is up with that??? these apps have been working great for over 10 years on every linux box I have put them on, and now they get overwritten?

*sighz* I don't know who to cuss out more.. systemd for just taking over a folder, or the gooberment for having stuff in a non-standard folder and it's not configurable.

[roger]

you can change the state of selinux in 2 ways:

either set in the boot prompt selinux=0 for a complette disable of selinux or enforcing=0 which means permissive mode at the end of the line.

alternatively, you can change it directly and fix in /etc/selinux/config. just set selinux-policy to either permissive or disabled.

The difference is, that if you disable selinux, no policy will be loaded at all, whilst in permissive mode selinux works as expected, the only difference is that you get a warning instead of a block.

hth
Roger

[kurtdriver]

You could also set it in /boot/grub/grub.conf.
If you can't boot to a command line, you can change it with a liveCD.