Can't login after tonights update

[tdockery97]

We are forced to add extra clicks to our workflow. Are there more features coming, or are we stuck with a whole lot of eye candy with no advancements in usability. I don't mean for this be rant-like ... just stating the facts ma'am just the facts.

That's exactly what I was wondering about Gnome 3 GoinEasy9. It just feels like half the functionality of Gnome 2 has been taken away and nothing useful added. The launch dock in Gnome 3 isn't new; I have AWN dock in Gnome 2. The screen that shows all the applications isn't new; I can select "all applications" in my Gnome 2 menu. Plus in Gnome 2 I can easily change themes and/or a myriad of desktop settings that I don't see in Gnome 3. And it does indeed take more clicks to do most things.

I imagine when Gnome 2 came out there were similar discussions, but we are supposed to be advancing, not regressing. Gnome devs seem to want to compete with Enlightenment, but I see no need to do so.

Just my $.02

[Raphos]

I imagine when Gnome 2 came out there were similar discussions, but we are supposed to be advancing, not regressing.

This is not the final release of Gnome 3 (I hope).

What is unfair is that you can't switch back to compiz-gnome and in the "standard" mode there are a lot of applications missing. After reboot, you automatically fall back in Gnome 3.

I really disagree with "if you want Gnome you must use Gnome 3 !".

[tox]

ok this time i did a reinstall. with the 64bit version, seems to running fine now, now hard lockups ( yet )

[Fenrin]

I did update my F15 a few hours before and now the boot stucks short before the GDM login manager would appear.

These 2 lines are the last things I can see:

stopping systemd syslog kernel Log Buffer Bridge
Starting Permit User Sessions...

Booting into console mode or booting of older kernel doesn't work either. Has anyone else this issue too?

I'm back in F14 for a while.

[jvinla]

Fenrin, I have the same problem. After an update and (attempted) reboot, its stopping at the same spot. I have not found a workaround yet.

[GoinEasy9]

After the update, my F15 install stops at "Starting LSB: Start up yhe NFS file locking service failed, see 'systenctl status nfslock.service' for details". Then, I left it for a few minutes and it came up with, Network Manager failed, then abrt failed, both with sysctl status errors. <sigh>

[tuxor]

I had the same problem and filed a bug:
https://bugzilla.redhat.com/show_bug.cgi?id=689093

But this issue turned out to be related to the latest update to rsyslog:
https://bugzilla.redhat.com/show_bug.cgi?id=689089

So basically, what you will have to do is:

# grep rsyslogd /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

To do this, edit the grub kernel-line by adding "systemd.unit=rescue.target".
Alternatively, set SELinux to permissive in /etc/selinux/config.

[jvinla]

Thanks for the info tuxor,

I used another system to set SELinux to disabled and was then able to login.

[tuxor]

Thanks for the info tuxor,

I used another system to set SELinux to disabled and was then able to login.

You should really rather use "permissive". Disabling SELinux completely might harm your label configuration. Of course, if you don't want to use SELinux at all anyway, this is the right thing to do.

[Fenrin]

...
So basically, what you will have to do is:

# grep rsyslogd /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

To do this, edit the grub kernel-line by adding "systemd.unit=rescue.target".
...

ok thank you. Now it works fine again. Booting only by adding systemd.unit=rescue.target was not succesful, but after adding 3 additionally for console mode it booted. And after entering these two lines it boots normal again

[tuxor]

Booting only by adding systemd.unit=rescue.target was not succesful

interesting, because this was the way I did it

[jonathan47]

I had the same problem and filed a bug:
https://bugzilla.redhat.com/show_bug.cgi?id=689093

But this issue turned out to be related to the latest update to rsyslog:
https://bugzilla.redhat.com/show_bug.cgi?id=689089

So basically, what you will have to do is:

# grep rsyslogd /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

To do this, edit the grub kernel-line by adding "systemd.unit=rescue.target".
Alternatively, set SELinux to permissive in /etc/selinux/config.

Thanks Tuxor. Worked for me. I had the same problem using KDE.