Bug 1003701

Summary:	official nVidia G04 367 drivers do not work with Leap 42.2 and KDE, (Plasma) or gnome LXDE fine
Product:	[openSUSE] openSUSE Distribution	Reporter:	Forgotten User zfHS33mKgr <forgotten_zfHS33mKgr>
Component:	X11 3rd Party Driver	Assignee:	E-mail List <xorg-maintainer-bugs>
Status:	RESOLVED DUPLICATE	QA Contact:	Stefan Dirsch <sndirsch>
Severity:	Normal
Priority:	P5 - None	CC:	wbauer
Version:	Leap 42.2
Target Milestone:	---
Hardware:	x86-64
OS:	SUSE Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User zfHS33mKgr 2016-10-07 17:06:03 UTC

after several test installs with both Leap 42.2 beta 2 and beta 3 it seems obvious that the nVidia drivers from download.nvidia.com/opensuse/leap/42.2/ do crash both KDE Plasma and GNOME.

Hardware: nVidia Pascal GP104 - 1070, intel XEON E5v4 2630 CPU

Symptoms:
KDE - Plasma crash msg, ... cannot use OpenGL 2 ...
GNOME classic - only desktop icons are displayed no other normal desktop elements are shown.

LXDE is fine and useable with nVidia, desktop is accelerated.


With the nouveau driver KDE (Plasma), GNOME and LXDE are technically useable but  slow and not real responsive.

Comment 1 Wolfgang Bauer 2016-10-07 17:14:57 UTC

(In reply to Georg Schukat from comment #0)
> after several test installs with both Leap 42.2 beta 2 and beta 3 it seems
> obvious that the nVidia drivers from download.nvidia.com/opensuse/leap/42.2/
> do crash both KDE Plasma and GNOME.

Why did you report it against KDE then?
Reassigning...

Comment 2 Stefan Dirsch 2016-10-08 09:14:12 UTC

Sounds like a duplicate of bnc#1000625. Fixed packages will be available soon.

Check for RPM changelog ("rpm --changelog nvidia-gfxG04-kmp-default")

* Fr Sep 30 2016 sndirsch@suse.com
- %post: create symlinks and /usr/lib/tmpfiles.d snippet for udev so
  nvidia devices will get user ACLs by logind later (bnc#1000625)
- %postun cleanup: remove tmpfiles.d snippet

*** This bug has been marked as a duplicate of bug 1000625 ***