Comments
jrimpo
No, I'll get on that.
I have an issue that seems to only appear with the latest testing kernel 4.2.6. At boot, it does not appear my firmware raid is mounting properly, and because of that my LVM partitions are not mounting so the system can't boot.
It doesn't have this problem on 4.2.5. It might be a kernel problem rather than an mdadm problem.
My problem may be related to the recent mdadm update, though that hasn't caused problems with the previous kernel. The system was unable to mount my LVM partitions - which are also on firmware raid which also appears to have not mounted properly.
I'm unable to boot with this kernel, while 4.2.5 works fine...
At boot, I'm seeing: i915 0000:00:02.0: registered panic notifier
Does seem to fix it, only issue I have is it is not automatically updating with 'dnf update', I have to force reinstall to get the package to update. Not sure if this is a dnf issue or a package issue.
Just completed in install overwriting a previous install. No issues encountered.
After running a grub2-mkconfig, the grub entry is back to normal.
I have the same garbled grub entry, but it appears to be running fine.
This update works fine in Gnome but is basically unusable in KDE.
I must be having a similar issue as nucleo. I'm running on KDE, and navigating the remote filesystem is almost impossible. Is there perhaps a missing dependency going on or incompatibility with the KDM?
Both cheese and the control center user photo screen are now crashing as soon as the camera turns on. I'm having other kernel-related problems, though, so I'm not sure what the exact source of the problem is. Cheese was working previously and control-center crashed at a different point in the photo-taking process.
Not sure how to rate. The previous error is no longer there, but a new error has shown up in it's place - again.
Does seem to fix cheese, maybe not control-center bug.
#1281535