Today, after updating, there is a fatal grubby error while installing the new kernel (something like "no suitable template found") so there is no grub entry for it.
Also, for the past few days, Rawhide hangs during shutdown, forcing me to hard power off, This continues even after today's selinux-policy update which at least allows logging in again.
I'm not sure what component to file a bug under for either of these.
On 14/01/12 20:08, Andre Robatino wrote:
Also, for the past few days, Rawhide hangs during shutdown, forcing me to hard power off, This continues even after today's selinux-policy update which at least allows logging in again.
I'm not sure what component to file a bug under for either of these.
ditto on the forced shutdown.
On Sat, Jan 14, 2012 at 08:08:21PM +0000, Andre Robatino wrote:
Also, for the past few days, Rawhide hangs during shutdown, forcing me to hard power off.
That would be most likely https://bugzilla.redhat.com/show_bug.cgi?id=781657 See comment #2 (and #3) in particular. It resolved that issue for me.
This continues even after today's selinux-policy update
That bug above is not a selinux fault.
Michal
On 14/01/12 22:06, Michal Jaegermann wrote:
That would be most likely https://bugzilla.redhat.com/show_bug.cgi?id=781657 See comment #2 (and #3) in particular. It resolved that issue for me.
Thanks for the info.
Michal Jaegermann <michal <at> harddata.com> writes:
That would be most likely https://bugzilla.redhat.com/show_bug.cgi?id=781657 See comment #2 (and #3) in particular. It resolved that issue for me.
The procedure described worked for me exactly once, the first time I tried it. After that, it doesn't work anymore, even though the file edit is persistent. See https://bugzilla.redhat.com/show_bug.cgi?id=781657#c8 . The other problem, with grubby not updating grub.cfg, I can work around by recreating it with grub2-mkconfig - it creates entries for all the kernels, including the latest one. I'm guessing it's a grubby bug but haven't filed it yet - I want to see the exact error when the next kernel appears.
On Mon, Jan 16, 2012 at 05:54:21AM +0000, Andre Robatino wrote:
Michal Jaegermann <michal <at> harddata.com> writes:
That would be most likely https://bugzilla.redhat.com/show_bug.cgi?id=781657 See comment #2 (and #3) in particular. It resolved that issue for me.
The procedure described worked for me exactly once, the first time I tried it.
No idea. It still works for me after many reboots. Are you sure that you do not have any typos in /lib/systemd/system/syslog.socket? If not then what 'systemctl status syslog.socket' has to say? As https://bugzilla.redhat.com/show_bug.cgi?id=781657#c5 notes: "syslog-related problems are often nasty" and I do not know hot to try to debug that.
Michal
Michal Jaegermann <michal <at> harddata.com> writes:
No idea. It still works for me after many reboots. Are you sure that you do not have any typos in /lib/systemd/system/syslog.socket? If not then what 'systemctl status syslog.socket' has to say? As https://bugzilla.redhat.com/show_bug.cgi?id=781657#c5 notes: "syslog-related problems are often nasty" and I do not know hot to try to debug that.
See https://bugzilla.redhat.com/show_bug.cgi?id=781657#c11 . It's working for me now. I'm sure the original edit was correct, since it worked once, and the edit itself was persistent (though not its effect).
-
Andre Robatino -
Frank Murphy -
Michal Jaegermann