> Likely because they don't know how to get to the right log Leigh?
>
> Dave
>
> On 2 September 2017 at 15:47, Leigh Scott wrote:
It would take the user less than 10 minutes to google howto provide logging or
many hours for me to ask, I could always retire nvidia to make more time :P
Or they c
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/?id=f157a9e1b75320f0ac55208f89b1cf09b10be948
or maybe having nvidia-drm.modeset=1 enabled has k
Am 02.09.2017 um 17:27 schrieb Dave Pawson:
Likely because they don't know how to get to the right log Leigh?
and how do they imagine help then instead get ignore dby people tired
about it? http://www.catb.org/esr/faqs/smart-questions.html#beprecise
frankly system logs on linux are no rock
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/?id=f157a9e1b75320f0ac55208f89b1cf09b10be948
or maybe having nvidia-drm.modeset=1 enabled has killed kde as well :-)
https://bugzilla.rpmfus
Likely because they don't know how to get to the right log Leigh?
Dave
On 2 September 2017 at 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/?id=f157a9e1b75320f0ac55208f89b1cf09b10be948
>
> or ma
It could be a selinux issue, see this commit
https://pkgs.rpmfusion.org/cgit/nonfree/xorg-x11-drv-nvidia.git/commit/?id=f157a9e1b75320f0ac55208f89b1cf09b10be948
or maybe having nvidia-drm.modeset=1 enabled has killed kde as well :-)
https://bugzilla.rpmfusion.org/show_bug.cgi?id=4632
without an
On 08/31/2017 07:06 AM, John Pilkington wrote:
> On 30/08/17 22:43, Ed Greshko wrote:
>> On 08/31/2017 04:58 AM, John Pilkington wrote:
>>> No one else has reported seeing this so I pursued it a bit further
>>
>>
>> You got nVidia 384.59 from updates-testing, yes? Could that be why others
>> aren'
On 30/08/17 22:43, Ed Greshko wrote:
On 08/31/2017 04:58 AM, John Pilkington wrote:
No one else has reported seeing this so I pursued it a bit further
You got nVidia 384.59 from updates-testing, yes? Could that be why
others aren't seeing it?
I can't check now, and could be mistaken, but
On 08/31/2017 04:58 AM, John Pilkington wrote:
> No one else has reported seeing this so I pursued it a bit further
You got nVidia 384.59 from updates-testing, yes? Could that be why others
aren't
seeing it?
___
rpmfusion-users mailing list -- rpmfus
On 26/08/17 22:36, John Pilkington wrote:
This is working with 4.11.12-200. With 4.12.8-200 the KDE login screen
is ok but progresses only to give two black screens (monitor and TV)
with a cursor that can be moved between them.
No one else has reported seeing this so I pursued it a bit furthe
This is working with 4.11.12-200. With 4.12.8-200 the KDE login screen
is ok but progresses only to give two black screens (monitor and TV)
with a cursor that can be moved between them.
___
rpmfusion-users mailing list -- rpmfusion-users@lists.rpmfusi
11 matches
Mail list logo
