http://bugzilla.opensuse.org/show_bug.cgi?id=1003402 http://bugzilla.opensuse.org/show_bug.cgi?id=1003402#c2 Stefan Quandt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |squan@web.de --- Comment #2 from Stefan Quandt --- Same for me with a desktop computer with "nVidia GM206 [GeForce GTX 960]": After installation of any Leap 42.2 beta 1/2/3 I get a black screen after booting into a plasma/KDE session. The only thing which works is launching the 'task manager' window with Ctrl-Esc. This sometimes shows a STOPPED plasmashell process (i.e. it is intercepted by DrKonqi while crashing (with no DrKonqi window popping up though)). Also the threads for the three beta releases of Leap 42.2 on forums.opensuse.org contain user reports for this issue. There seem to be problems with nouveau in general and the following pages indicate that there is at least some progress: https://nwrickert2.wordpress.com/2016/07/21/opensuse-leap-42-2-alpha3/ https://nwrickert2.wordpress.com/2016/09/02/opensuse-leap-42-2-beta1/ https://nwrickert2.wordpress.com/2016/09/25/opensuse-leap-42-2-beta2/ Still there seems to be a general problem of plasmashell with noveau, at least with certain NVidia graphic cards. Inspectiong my /var/log/Xorg.0.log on a beta installation shows the following error (EE) Unknown chipset: NV126 which according to https://bugs.freedesktop.org/show_bug.cgi?id=94728#c2 may mean that kernel 4.6 and mesa 11.2 is required. And indeed, when running a tumbleweed live CD (which currently comes with kernel 4.8 and mesa 12.0) I do *not* have crashes of plasmashell. Does this mean that the upcoming Leap 42.2 release will not work with out of the box nouveau/plasmashell with newer NVidia graphics cards? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1003402 http://bugzilla.opensuse.org/show_bug.cgi?id=1003402#c10 Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrmazda@earthlink.net --- Comment #10 from Felix Miata --- Host mcp61 TW #1: # zypper se -si | egrep 'nouveau|x11-serv' i | libXvMC_nouveau | package | 12.0.3-143.1 | i586 | OSS i | libdrm_nouveau2 | package | 2.4.71-1.1 | i586 | OSS i | libvdpau_nouveau | package | 12.0.3-143.1 | i586 | OSS i | xorg-x11-server | package | 7.6_1.18.4-1.2 | i586 | OSS # cat /proc/cmdline root=LABEL=st160os133 ipv6.disable=1 net.ifnames=0 splash=0 noresume vga=791 video=1024x768@60 video=1440x900@60 nouveau.noaccel=1 3 # lspci | grep VGA 00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) Plasmashell dumps core and locks up UI if I leave nouveau.noaccel=1 off cmdline, but Plasma from startx in multi-user.target seems perfectly fine with it and Xorg's modeset(0) driver. Same host also has freshly updated x86_64 42.2. With nouveau.noaccel=1 on cmdline and starting from either startx in multi-user, or from KDM, and using Oxygen wherever possible instead of Breeze, whether using nouveau or modeset driver, plasmashell is not dumping core (to /var/lib/systemd/coredump), but kactivitymanage is. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1003402 http://bugzilla.opensuse.org/show_bug.cgi?id=1003402#c29 --- Comment #29 from Neil Rickert --- I seem to have confused people with comment #9. Sorry about that. All I meant was that desktop effects are still working. In any case, here is the situation with 42.2 RC1. It is working well, as long as I use LIBGL_ALWAYS_SOFTWARE=1 in the environment (set from a shell startup file). While it was running well, I switched to XRender. Maybe that doesn't actually do anything with that environment setting. I also edited "kwinrc" to set OpenGLIsUnsafe=true After that, I logged out. Then I logged in without the environment setting. And plasmashell crashed. So it is "LIBGL_ALWAYS_SOFTWARE=1" that works for me. Nothing else is helping. I see a request for a backtrace. In the past, Kcrash has provided those. But in this case it is not showing up. Maybe I can get it with "gdb" and the coredump, but some hints would help. Looking at "/var/lib/systemd/coredump", I see: # ls -tr core.plymouthd.0.7f466745a5054929af5b6c409d4924f3.320.1476781929000000.xz core.plymouthd.0.52725b8459f64a4083eb94d2f4a34514.320.1476803614000000.xz core.kactivitymanage.1001.52725b8459f64a4083eb94d2f4a34514.2852.1476804511000000.xz core.kactivitymanage.1001.52725b8459f64a4083eb94d2f4a34514.3702.1476804800000000.xz core.kactivitymanage.1001.52725b8459f64a4083eb94d2f4a34514.4527.1476804890000000.xz core.plasmashell.1001.52725b8459f64a4083eb94d2f4a34514.4733.1476804838000000.xz core.kactivitymanage.1001.52725b8459f64a4083eb94d2f4a34514.5185.1476805293000000.xz core.kactivitymanage.1001.52725b8459f64a4083eb94d2f4a34514.5948.1476807629000000.xz core.gvfsd-network.1001.52725b8459f64a4083eb94d2f4a34514.9269.1476808299000000.xz core.gvfsd-network.1001.52725b8459f64a4083eb94d2f4a34514.9276.1476808299000000.xz core.plymouthd.0.d863f0d432dd4e13b51036444908b879.344.1476850955000000.xz core.org_kde_powerde.1001.d863f0d432dd4e13b51036444908b879.2787.1476850985000000.xz core.plymouthd.0.6ab3fc1618044cb6926bfa3b113f391e.329.1476881201000000.xz It seems that plasmashell is not the only thing crashing. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1003402 http://bugzilla.opensuse.org/show_bug.cgi?id=1003402#c34 Neil Rickert changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(nwr10cst-oslnx@ya | |hoo.com) | --- Comment #34 from Neil Rickert --- Created attachment 698178 --> http://bugzilla.opensuse.org/attachment.cgi?id=698178&action=edit transcript of gdb session This is my attempt to get trace info from the existing coredump (a "script" transcript file from a terminal session). It might not be useful. It seems that the dump is truncated. -- You are receiving this mail because: You are on the CC list for the bug.