On 02/09/17 16:42, John Pilkington wrote:
On 02/09/17 15:47, Leigh Scott wrote:
> It could be a selinux issue, see this commit
>
>
https://pkgs.rpmfusion.org/cgit/nonfree/xorg-x11-drv-nvidia.git/commit/?i...
>
>
> or maybe having nvidia-drm.modeset=1 enabled has killed kde as well :-)
>
>
https://bugzilla.rpmfusion.org/show_bug.cgi?id=4632
>
> without any logs it's just a guess (why do users nearly always fail to
> include logs?).
OK, thanks for the info, and your interest in the problem. I can't do
anything about it for a few days.
When something like this happens, my first priority is usually to
discover some way of getting back to a working system. Then I posted a
heads-up. Finding the right log, and a way to post it from an
arbitrarily broken box, isn't (fortunately) a typical user task.
It's good to be able to report that the problem has gone away.
$ uname -r
4.12.9-200.fc25.x86_64
$ rpm -qa | grep 384.59
xorg-x11-drv-nvidia-devel-384.59-4.fc25.x86_64
kmod-nvidia-4.12.9-200.fc25.x86_64-384.59-1.fc25.x86_64
akmod-nvidia-384.59-1.fc25.x86_64
kmod-nvidia-384.59-1.fc25.x86_64
xorg-x11-drv-nvidia-384.59-4.fc25.x86_64
xorg-x11-drv-nvidia-cuda-libs-384.59-4.fc25.x86_64
xorg-x11-drv-nvidia-libs-384.59-4.fc25.x86_64
kmod-nvidia-4.12.8-200.fc25.x86_64-384.59-1.fc25.x86_64
kmod-nvidia-4.11.12-200.fc25.x86_64-384.59-1.fc25.x86_64
xorg-x11-drv-nvidia-kmodsrc-384.59-4.fc25.x86_64
John P