[Bug 1151290] New: Second X server (nvidia) on vt8 crashes with vncviewer
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 Bug ID: 1151290 Summary: Second X server (nvidia) on vt8 crashes with vncviewer Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: X11 3rd Party Driver Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: werner@suse.com QA Contact: sndirsch@suse.com Found By: --- Blocker: --- Created attachment 818839 --> http://bugzilla.opensuse.org/attachment.cgi?id=818839&action=edit /var/log/Xorg.1.log As subject shows I see very often crashes of the X xserver sometime in /usr/lib64/xorg/modules/drivers/nvidia_drv.so someties not as in the attached log file. Seems to happen if I swithc from vt8 to vt7 of the local screen with its X server. As I'm using VNC to work at hon on my workstations at SUSE this crashes are very nasty. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #818839|text/x-log |text/plain mime type| | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c1 --- Comment #1 from Stefan Dirsch <sndirsch@suse.com> --- Hmm. Never heard of such an issue. But not many customers are using two Xservers, especially not within an Optimus setup ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c2 --- Comment #2 from Dr. Werner Fink <werner@suse.com> --- It seems that the risk of catching this crash has been increased with the latest update /local/werner> rpm -q x11-video-nvidiaG04 x11-video-nvidiaG04-390.129-lp151.6.1.x86_64 /local/werner> rpm -q nvidia-gfxG04-kmp-default nvidia-gfxG04-kmp-default-390.129_k4.12.14_lp151.27-lp151.6.1.x86_64 as it happens very often. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c3 --- Comment #3 from Dr. Werner Fink <werner@suse.com> --- Created attachment 818846 --> http://bugzilla.opensuse.org/attachment.cgi?id=818846&action=edit /var/log/Xorg.1.log -- now with crash in nvidia_drv.so -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c5 --- Comment #5 from Dr. Werner Fink <werner@suse.com> --- (In reply to Stefan Dirsch from comment #4)
Crash in libpthread smells a bit like " Hardware Lock Elision" problem. Could you check whether you have the 'hle' CPU flag in your machine (cat /proc/cpuinfo | grep hle)? But that is just a shot in the dark. :-(
If you have it try this:
export LD_LIBRARY_PATH=/lib64/noelision/:$LD_LIBRARY_PATH
Treffer versenkt :) /local/werner> cat /proc/cpuinfo | grep -c ' hle ' 8 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c6 --- Comment #6 from Stefan Dirsch <sndirsch@suse.com> --- Ok. Could be just coincidence that your CPU has this feature. Did setting the environment variable help? Could be a bit tricky having it set for the Xserver start. And you probably don't want to set it for anything else. And you said the crashes don't happen immediately. Meanwhile there is some environmental variable in glibc for detailed setting of hle instead of turning it off, but I can't remember the name any longer and the possible settings and meanings. In my case (audacity) it didn't help and I still need to use the noelison libpthread library. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c7 --- Comment #7 from Dr. Werner Fink <werner@suse.com> --- (In reply to Stefan Dirsch from comment #6)
Ok. Could be just coincidence that your CPU has this feature.
Did setting the environment variable help? Could be a bit tricky having it set for the Xserver start.
And you probably don't want to set it for anything else.
And you said the crashes don't happen immediately.
I simpoky added in /etc/ld.so.conf the line /lib64/noelision before the include of the /etc/ld.so.conf.d/ files. Afterwards I used ldconfig ... is there any disasdvantage about noelision version of the libpthread for other threaded programs like e.g. firefox? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c8 --- Comment #8 from Dr. Werner Fink <werner@suse.com> --- For the records https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=800574 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c9 --- Comment #9 from Dr. Werner Fink <werner@suse.com> --- Created attachment 819539 --> http://bugzilla.opensuse.org/attachment.cgi?id=819539&action=edit /var/log/Xorg.1.log does not help :( -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c10 --- Comment #10 from Dr. Werner Fink <werner@suse.com> --- To be exact /local/werner> ldd /usr/bin/X | grep pthread libpthread.so.0 => /lib64/noelision/libpthread.so.0 (0x00007fb6e532f000) that is the ld.so configuration does works here but the cause could not be the HLE sandybridge bug. No idea if there is a ucode update in the ucode-intel package and currently the apache on opensuse.org has na hickup -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c11 --- Comment #11 from Stefan Dirsch <sndirsch@suse.com> --- Ok. So that was not the reason. Nice try. :-( Thanks for the pointer to the debian bug! Indeed looking for an update of ucode-intel package (Intel CPU/GPU firmware) is a good idea. You should at least try it. I'm afraid all you can do is install debug packages and enable writing core files, so you see some more useful information here. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c12 --- Comment #12 from Dr. Werner Fink <werner@suse.com> --- Created attachment 822336 --> http://bugzilla.opensuse.org/attachment.cgi?id=822336&action=edit /var/log/Xorg.1.log (In reply to Stefan Dirsch from comment #11)
Ok. So that was not the reason. Nice try. :-(
Thanks for the pointer to the debian bug! Indeed looking for an update of ucode-intel package (Intel CPU/GPU firmware) is a good idea. You should at least try it.
I'm afraid all you can do is install debug packages and enable writing core files, so you see some more useful information here.
Even with latest ucode-intel package ', the crahses remain :( -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c13 --- Comment #13 from Dr. Werner Fink <werner@suse.com> --- *** Bug 1158543 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c14 --- Comment #14 from Dr. Werner Fink <werner@suse.com> --- Send a bug report to linux-bugs@nvidia.com with the attached output of the nvidia-bug-report.sh script -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c16 --- Comment #16 from Dr. Werner Fink <werner@suse.com> --- Just trying 390.132 G04 with vt8 and vncviewer ... currently no crash yet -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c17 --- Comment #17 from Stefan Dirsch <sndirsch@suse.com> --- Thanks. Sounds promising. :-) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c18 --- Comment #18 from Dr. Werner Fink <werner@suse.com> --- Also the X server now seems to fork an daemon now which handles vt switching [ 85777.044] (II) AIGLX: Suspending AIGLX clients for VT switch [ 85784.886] (II) AIGLX: Resuming AIGLX clients after VT switch [ 85787.372] (II) AIGLX: Loaded and initialized i965 [ 85787.372] (II) GLX: Initialized DRI2 GL provider for screen 0 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c19 --- Comment #19 from Dr. Werner Fink <werner@suse.com> --- Nope [129038.120] (II) AIGLX: Suspending AIGLX clients for VT switch [134896.418] (II) AIGLX: Resuming AIGLX clients after VT switch [134896.453] (II) modeset(0): EDID vendor "AUO", prod id 4509 [134896.453] (II) modeset(0): Printing DDC gathered Modelines: [134896.454] (II) modeset(0): Modeline "1920x1080"x0.0 149.80 1920 1968 2068 2228 1080 1083 1084 1120 -hsync -vsync (67.2 kHz eP) [134896.469] (EE) [134896.469] (EE) Backtrace: [134896.469] (EE) 0: X (xorg_backtrace+0x65) [0x5578e0eb0f45] [134896.470] (EE) 1: X (0x5578e0cff000+0x1b5c19) [0x5578e0eb4c19] [134896.470] (EE) 2: /lib64/libpthread.so.0 (0x7f61e72ca000+0x12300) [0x7f61e72dc300] [134896.470] (EE) 3: X (0x5578e0cff000+0xdb16e) [0x5578e0dda16e] [134896.470] (EE) 4: X (0x5578e0cff000+0xdb38b) [0x5578e0dda38b] [134896.470] (EE) 5: X (xf86VTEnter+0x10b) [0x5578e0d988cb] [134896.470] (EE) 6: X (WakeupHandler+0xbd) [0x5578e0d6000d] [134896.470] (EE) 7: X (WaitForSomething+0x1d1) [0x5578e0eae761] [134896.471] (EE) 8: X (0x5578e0cff000+0x5c233) [0x5578e0d5b233] [134896.471] (EE) 9: X (0x5578e0cff000+0x6049c) [0x5578e0d5f49c] [134896.471] (EE) 10: /lib64/libc.so.6 (__libc_start_main+0xea) [0x7f61e6f30f8a] [134896.471] (EE) 11: X (_start+0x2a) [0x5578e0d4912a] [134896.471] (EE) [134896.471] (EE) Segmentation fault at address 0x73 [134896.471] (EE) Fatal server error: [134896.471] (EE) Caught signal 11 (Segmentation fault). Server aborting [134896.471] (EE) [134896.471] (EE) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c20 --- Comment #20 from Stefan Dirsch <sndirsch@suse.com> --- Ok. Thanks for giving it a try! As said G05/440.59 also is supposed to support your GPU. Not sure, which driver you've now used for testing ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c21 --- Comment #21 from Dr. Werner Fink <werner@suse.com> --- (In reply to Stefan Dirsch from comment #20)
Ok. Thanks for giving it a try! As said G05/440.59 also is supposed to support your GPU. Not sure, which driver you've now used for testing ...
/local/werner> foreach p (`rpmqpack | grep nvidia`) nvidia-computeG04-390.132-lp151.9.1.x86_64 nvidia-gfxG04-kmp-default-390.132_k4.12.14_lp151.27-lp151.9.1.x86_64 nvidia-glG04-390.132-lp151.9.1.x86_64 x11-video-nvidiaG04-390.132-lp151.9.1.x86_64 this is what Leap 15.1 had a least ... you mean I should give the G05 a try? /local/werner> sudo zypper se nvidia | grep G05 | nvidia-computeG05 | NVIDIA driver for computing with GPGPU | package | nvidia-gfxG05-kmp-default | NVIDIA graphics driver kernel module for GeForce 600 series and newer | package | nvidia-glG05 | NVIDIA OpenGL libraries for OpenGL acceleration | package | x11-video-nvidiaG05 | NVIDIA graphics driver for GeForce 600 series and newer | package -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c22 --- Comment #22 from Dr. Werner Fink <werner@suse.com> --- The diver should support NVIDIA Corporation GM107M [GeForce GTX 960M] That is the GeForce 900M Series (Notebooks): GeForce GTX 980, GeForce GTX 980M, GeForce GTX 970M, GeForce GTX 965M, GeForce GTX 960M, GeForce GTX 950M, GeForce 945M, GeForce 940MX, GeForce 930MX, GeForce 920MX, GeForce 940M, GeForce 930M, GeForce 920M, GeForce 910M -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c23 --- Comment #23 from Dr. Werner Fink <werner@suse.com> --- Found this after searching for the 900M series https://www.nvidia.com/Download/driverResults.aspx/157462/en-us -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c24 --- Comment #24 from Dr. Werner Fink <werner@suse.com> --- Created attachment 832012 --> http://bugzilla.opensuse.org/attachment.cgi?id=832012&action=edit /etc/X11/xorg.conf.d/99-local.conf I've removed 90-intel.conf to get nvidia ... see Section "ServerFlags" Option "DefaultServerLayout" "intel" # Option "DefaultServerLayout" "nvidia" # Option "DefaultServerLayout" "layout" Option "Xinerama" "false" Option "AutoAddGPU" "false" EndSection where currently intel is set ... using layout with Section "ServerLayout" Identifier "layout" Screen 0 "nvidia" 0 0 Inactive "intel" InputDevice "touchpad" # Option "SingleCard" "true" EndSection or Section "ServerLayout" Identifier "nvidia" Screen 0 "nvidia" 0 0 InputDevice "touchpad" EndSection cause sddm-helper to crash with exit 6 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c25 --- Comment #25 from Dr. Werner Fink <werner@suse.com> --- Hmmm ... now if I use nvidia direct or nvidia with inactive modesetting driver (both works!) the sddm-helper binary exists with error 6 Mar 05 14:54:17 tux systemd[1]: Started X Display Manager. Mar 05 14:54:18 tux sddm[4809]: Setting default cursor Mar 05 14:54:18 tux sddm[4809]: Running display setup script "/etc/X11/xdm/Xsetup" Mar 05 14:54:18 tux sddm[4809]: Display server started. Mar 05 14:54:18 tux sddm[4809]: Socket server starting... Mar 05 14:54:18 tux sddm[4809]: Socket server started. Mar 05 14:54:18 tux sddm[4809]: Loading theme configuration from "/usr/share/sddm/themes/breeze-openSUSE/theme.conf" Mar 05 14:54:18 tux sddm[4809]: Greeter starting... Mar 05 14:54:18 tux sddm[4809]: Adding cookie to "/run/sddm/{75eaa492-e375-45de-9b86-497ecd7cd14c}" Mar 05 14:54:18 tux sddm-helper[4825]: [PAM] Starting... Mar 05 14:54:18 tux sddm-helper[4825]: [PAM] Authenticating... Mar 05 14:54:18 tux sddm-helper[4825]: [PAM] returning. Mar 05 14:54:18 tux sddm[4809]: Greeter session started successfully Mar 05 14:54:18 tux sddm[4809]: Message received from greeter: Connect Mar 05 14:54:19 tux sddm[4809]: Auth: sddm-helper exited with 6 what does this mean? I'd like to use nvidia and not modesetting driver -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c26 --- Comment #26 from Dr. Werner Fink <werner@suse.com> --- seems that sddm upstream ignore such errors https://github.com/sddm/sddm/issues/651 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c27 --- Comment #27 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Dr. Werner Fink from comment #21)
this is what Leap 15.1 had a least ... you mean I should give the G05 a try?
Yes, I verified that your GPU is being supported by G05 driver. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c28 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fabian@ritter-vogt.de Flags| |needinfo?(fabian@ritter-vog | |t.de) --- Comment #28 from Dr. Werner Fink <werner@suse.com> --- (In reply to Stefan Dirsch from comment #27)
(In reply to Dr. Werner Fink from comment #21)
this is what Leap 15.1 had a least ... you mean I should give the G05 a try?
Yes, I verified that your GPU is being supported by G05 driver.
But sddm does not -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c29 --- Comment #29 from Dr. Werner Fink <werner@suse.com> --- One of those broken^H^H^H^H^Hmodern abort() programming -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c30 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt@suse.com Flags|needinfo?(fabian@ritter-vog | |t.de) | --- Comment #30 from Fabian Vogt <fvogt@suse.com> --- While sddm using abort() to handle such critical errors isn't right, doing it differently wouldn't fix the original issue. X still crashes. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c31 --- Comment #31 from Dr. Werner Fink <werner@suse.com> --- Adding the user sddm to the group video in /etc/group does solve the issue ... it seems that sddm has to have the permissions to open the nvidia devices below /dev Also the line xrandr --setprovideroutputsource modesetting NVIDIA-0 && xrandr --auto is not required anymore as the direct access of nvidia works in my ServerLayout section xrandr --listproviders Providers: number : 2 Provider 0: id: 0x243; cap: 0x1 (Source Output); crtcs: 0; outputs: 0; associated providers: 1; name: NVIDIA-0 Provider 1: id: 0x46; cap: 0xf (Source Output, Sink Output, Source Offload, Sink Offload); crtcs: 3; outputs: 4; associated providers: 1; name: modesetting output eDP-1-1 output DP-1-2 output HDMI-1-1 output HDMI-1-2 glxinfo | grep 'vendor string:' server glx vendor string: NVIDIA Corporation client glx vendor string: NVIDIA Corporation OpenGL vendor string: NVIDIA Corporation -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c32 --- Comment #32 from Dr. Werner Fink <werner@suse.com> --- (In reply to Fabian Vogt from comment #30)
While sddm using abort() to handle such critical errors isn't right, doing it differently wouldn't fix the original issue. X still crashes.
Ohnmm ... X does not crash ... that is the X server is up and shows its black background .. using the XUATHORITY variable with the sddm path I can start an xterm on the black screen. The sddm-helper seems not be allowed to open at least one of NVIDIA's devices below /dev ... what I expect is a valid error messages bfore doeing an abort(). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c33 --- Comment #33 from Stefan Dirsch <sndirsch@suse.com> --- Hmm. Interesting. Just noticed that on openSUSE 15.2 gdm is also in video group. Probably because Xserver, on which runs gdm greeter is being started as gdm user. Afterwards the Xserver for the Xsession is being started as the user, which logs into the greeter. Maybe we should do the same for sddm user and add sddm also to group video ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c34 --- Comment #34 from Dr. Werner Fink <werner@suse.com> --- (In reply to Stefan Dirsch from comment #33)
Hmm. Interesting. Just noticed that on openSUSE 15.2 gdm is also in video group. Probably because Xserver, on which runs gdm greeter is being started as gdm user. Afterwards the Xserver for the Xsession is being started as the user, which logs into the greeter.
Maybe we should do the same for sddm user and add sddm also to group video ...
I've submitted a fixed version of sddm for Tumbleweed/Factory -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c35 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED CC| |sndirsch@suse.com Component|X11 3rd Party Driver |KDE Workspace (Plasma) Resolution|--- |FIXED Assignee|xorg-maintainer-bugs@forge. |opensuse-kde-bugs@opensuse. |provo.novell.com |org QA Contact|sndirsch@suse.com |qa-bugs@suse.de --- Comment #35 from Stefan Dirsch <sndirsch@suse.com> --- Thanks. So let's close it as fixed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c36 Fabian Vogt <fabian@ritter-vogt.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- Flags| |needinfo?(sndirsch@suse.com | |) --- Comment #36 from Fabian Vogt <fabian@ritter-vogt.de> --- @sndirsch: The sddm submission got initially declined because we have udev/logind taking care of this. AFAICT by looking at the .changes and bug 1080742, nvidia-logind-acl-trick.conf is supposed to take care of this. So in this case, maybe something went wrong with sddm and logind. For now it's IMO ok as GDM does the same and so there's no reason to not allow sddm to do it too, but if there's a more general fix that's obviously better. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c37 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sndirsch@suse.com | |) | --- Comment #37 from Stefan Dirsch <sndirsch@suse.com> --- It is my understanding that the ACLs of these NVIDIA devices are only set for users, which are logged in. This is occurring neither for gdm nor sddm, right? Therefore I believe we still need this video group membership for gdm (and now als sddm). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c38 --- Comment #38 from Dr. Werner Fink <werner@suse.com> --- This bug is about crashing second X server and not sddm :) If required I'll open a second bug for this ... for Leap 15.2 this could be required. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1165987 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|KDE Workspace (Plasma) |X11 3rd Party Driver Assignee|opensuse-kde-bugs@opensuse. |xorg-maintainer-bugs@forge. |org |provo.novell.com QA Contact|qa-bugs@suse.de |sndirsch@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c39 --- Comment #39 from Dr. Werner Fink <werner@suse.com> --- Here we are: Bug boo#1165987 - The sddm user has no permissions on Nvidia based X servers -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c40 --- Comment #40 from Fabian Vogt <fabian@ritter-vogt.de> --- (In reply to Stefan Dirsch from comment #37)
It is my understanding that the ACLs of these NVIDIA devices are only set for users, which are logged in. This is occurring neither for gdm nor sddm, right?
SDDM uses PAM for creating a proper logind session for the greeter, so it's just like a normal user session. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c41 --- Comment #41 from Stefan Dirsch <sndirsch@suse.com> --- Hmm. Then why the group entry for gdm is needed? Or is it not? One should give it a try without. And if that works this begs the question why it's needed for sddm... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c42 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |IN_PROGRESS Flags| |needinfo?(werner@suse.com) --- Comment #42 from Stefan Dirsch <sndirsch@suse.com> --- Just had a try on Leap 15.1. gdm can start X for the greeter as user gdm even if not being in the video group. I removed it from the group and voila, ACLs of NVIDIA devices are set for user gdm. On Leap 15.1 sddm is still starting X as root user, so I couldn't try with sddm yet. Not sure, what I should do with this bug now. In the end it became a duplicate of boo#1165987, right? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c44 --- Comment #44 from Fabian Vogt <fvogt@suse.com> --- (In reply to Stefan Dirsch from comment #42)
Just had a try on Leap 15.1. gdm can start X for the greeter as user gdm even if not being in the video group. I removed it from the group and voila, ACLs of NVIDIA devices are set for user gdm.
On Leap 15.1 sddm is still starting X as root user, so I couldn't try with sddm yet.
Why not? I assume that the ACL is needed for hardware accelerated rendering, otherwise sddm-greeter wouldn't need it at all.
Not sure, what I should do with this bug now. In the end it became a duplicate of boo#1165987, right?
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c45 --- Comment #45 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Fabian Vogt from comment #44)
Just had a try on Leap 15.1. gdm can start X for the greeter as user gdm even if not being in the video group. I removed it from the group and voila, ACLs of NVIDIA devices are set for user gdm.
On Leap 15.1 sddm is still starting X as root user, so I couldn't try with sddm yet.
Why not? I assume that the ACL is needed for hardware accelerated rendering, otherwise sddm-greeter wouldn't need it at all.
I didn't claim anything different. Currently installing TW, where sddm now hopefully starts X as user sddm ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c46 --- Comment #46 from Fabian Vogt <fvogt@suse.com> --- (In reply to Stefan Dirsch from comment #45)
(In reply to Fabian Vogt from comment #44)
Just had a try on Leap 15.1. gdm can start X for the greeter as user gdm even if not being in the video group. I removed it from the group and voila, ACLs of NVIDIA devices are set for user gdm.
On Leap 15.1 sddm is still starting X as root user, so I couldn't try with sddm yet.
Why not? I assume that the ACL is needed for hardware accelerated rendering, otherwise sddm-greeter wouldn't need it at all.
I didn't claim anything different. Currently installing TW, where sddm now hopefully starts X as user sddm ...
sddm still runs X as root, even on TW. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c47 --- Comment #47 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Fabian Vogt from comment #46)
sddm still runs X as root, even on TW.
Then I don't understand, why it helps to add sddm to group video in order to prevent the abort() in sddm. But who knows what sddm else does with the nvidia devices ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c48 --- Comment #48 from Stefan Dirsch <sndirsch@suse.com> --- Werner, you're really using a weird setup. Two Xservers, both accessing the NVIDIA devices could be part of the problem. But, yeah. Try the latest NVIDIA driver G05/440.61. Maybe it fixes the issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c50 --- Comment #50 from Dr. Werner Fink <werner@suse.com> --- With G05/440.61 [ 57053.517] (II) NVIDIA(0): Setting mode "NULL" [ 57053.579] (--) synaptics: touchpad: touchpad found [ 57053.580] (II) event5 - Power Button: is tagged by udev as: Keyboard [ 57053.580] (II) event5 - Power Button: device is a keyboard [ 57053.581] (II) event7 - Video Bus: is tagged by udev as: Keyboard [ 57053.581] (II) event7 - Video Bus: device is a keyboard [ 57053.582] (II) event8 - Video Bus: is tagged by udev as: Keyboard [ 57053.582] (II) event8 - Video Bus: device is a keyboard [ 57053.582] (II) event2 - Power Button: is tagged by udev as: Keyboard [ 57053.582] (II) event2 - Power Button: device is a keyboard [ 57053.583] (II) event3 - Sleep Button: is tagged by udev as: Keyboard [ 57053.583] (II) event3 - Sleep Button: device is a keyboard [ 57053.584] (II) event9 - BisonCam, NB Pro: is tagged by udev as: Keyboard [ 57053.584] (II) event9 - BisonCam, NB Pro: device is a keyboard [ 57053.585] (II) event0 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard [ 57053.585] (II) event0 - AT Translated Set 2 keyboard: device is a keyboard [ 57053.585] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found [ 57054.632] (EE) [ 57054.632] (EE) Backtrace: [ 57054.632] (EE) 0: X (xorg_backtrace+0x65) [0x557ca03a2f45] [ 57054.632] (EE) 1: X (0x557ca01f1000+0x1b5c19) [0x557ca03a6c19] [ 57054.632] (EE) 2: /lib64/libpthread.so.0 (0x7f8ce6937000+0x12300) [0x7f8ce6949300] [ 57054.632] (EE) 3: X (0x557ca01f1000+0xdb618) [0x557ca02cc618] [ 57054.633] (EE) 4: X (0x557ca01f1000+0x12f86a) [0x557ca032086a] [ 57054.633] (EE) 5: X (FreeCursor+0x5b) [0x557ca024091b] [ 57054.633] (EE) 6: X (0x557ca01f1000+0xdb0ef) [0x557ca02cc0ef] [ 57054.633] (EE) 7: X (0x557ca01f1000+0xdb3bf) [0x557ca02cc3bf] [ 57054.633] (EE) 8: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f8ce2951000+0x4cf03f) [0x7f8ce2e2003f] [ 57054.633] (EE) [ 57054.633] (EE) Segmentation fault at address 0x29 [ 57054.633] (EE) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c51 --- Comment #51 from Stefan Dirsch <sndirsch@suse.com> --- Ok. :-( Nothing has changed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks|1165987 | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c52 --- Comment #52 from Dr. Werner Fink <werner@suse.com> --- Seen USE AFTER FREE at reboott after latest kernel update: [Sat Mar 14 09:39:09 2020] refcount_t: underflow; use-after-free. [Sat Mar 14 09:39:09 2020] WARNING: CPU: 7 PID: 1848 at ../lib/refcount.c:28 refcount_warn_saturate+0x8d/0xf0 [Sat Mar 14 09:39:09 2020] Modules linked in: af_packet scsi_transport_iscsi cmac bnep dmi_sysfs ftsteutates sunrpc btusb btrtl btbcm btintel uvcvideo bluetoo th videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev ecdh_generic mc ecc intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel _powerclamp snd_hda_codec_realtek coretemp snd_hda_codec_generic ledtrig_audio kvm_intel snd_hda_codec_hdmi kvm snd_hda_intel iTCO_wdt irqbypass iTCO_vendor_s upport mei_hdcp msr iwlmvm snd_hda_codec snd_hda_core crct10dif_pclmul snd_hwdep crc32_pclmul ghash_clmulni_intel mac80211 snd_pcm snd_seq libarc4 aesni_intel snd_seq_device iwlwifi snd_timer aes_x86_64 crypto_simd i915 cryptd glue_helper snd pcspkr cfg80211 mxm_wmi rtsx_pci_ms joydev i2c_i801 soundcore memstick rfkill mei_me i2c_algo_bit mei thermal battery ac acpi_pad button sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua nvidia_drm(POE) nvidia_modeset(POE) xfs libcrc32c nvidia_uvm(OE) rtsx_pci_sdmmc nvidia(POE) mmc_core [Sat Mar 14 09:39:09 2020] drm_kms_helper drm xhci_pci crc32c_intel xhci_hcd syscopyarea serio_raw sysfillrect sysimgblt fb_sys_fops rtsx_pci sr_mod ipmi_devintf cdrom usbcore ipmi_msghandler wmi video loop i2c_dev [Sat Mar 14 09:39:09 2020] CPU: 7 PID: 1848 Comm: X Tainted: P OE 5.3.18-lp152.5-default #1 openSUSE Leap 15.2 (unreleased) [Sat Mar 14 09:39:09 2020] Hardware name: TUXEDO N15_17RD,RD2 /N15_17RD,RD2 , BIOS 1.05.15 06/06/2016 [Sat Mar 14 09:39:09 2020] RIP: 0010:refcount_warn_saturate+0x8d/0xf0 [Sat Mar 14 09:39:09 2020] Code: 05 37 1f 06 01 01 e8 02 db bb ff 0f 0b c3 80 3d 2a 1f 06 01 00 75 ad 48 c7 c7 88 38 b3 a6 c6 05 1a 1f 06 01 01 e8 e3 da bb ff <0f> 0b c3 80 3d 0e 1f 06 01 00 75 8e 48 c7 c7 30 38 b3 a6 c6 05 fe [Sat Mar 14 09:39:09 2020] RSP: 0018:ffffa60f8145fd90 EFLAGS: 00010282 [Sat Mar 14 09:39:09 2020] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000006 [Sat Mar 14 09:39:09 2020] RDX: 0000000000000007 RSI: 0000000000000092 RDI: ffff970641bd9a10 [Sat Mar 14 09:39:09 2020] RBP: ffff9702c7616ce8 R08: 000000000000036d R09: 0000000000000000 [Sat Mar 14 09:39:09 2020] R10: dead000000000100 R11: 0000000000000001 R12: 0000000000000000 [Sat Mar 14 09:39:09 2020] R13: ffff970636baa800 R14: 0000000000000000 R15: 0000000000000008 [Sat Mar 14 09:39:09 2020] FS: 00007f1be4af8ec0(0000) GS:ffff970641bc0000(0000) knlGS:0000000000000000 [Sat Mar 14 09:39:09 2020] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [Sat Mar 14 09:39:09 2020] CR2: 00007f1be2430ef0 CR3: 0000000460134006 CR4: 00000000003606e0 [Sat Mar 14 09:39:09 2020] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [Sat Mar 14 09:39:09 2020] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [Sat Mar 14 09:39:09 2020] Call Trace: [Sat Mar 14 09:39:09 2020] nv_drm_atomic_helper_disable_all+0x263/0x2a0 [nvidia_drm] [Sat Mar 14 09:39:09 2020] nv_drm_master_drop+0x22/0x60 [nvidia_drm] [Sat Mar 14 09:39:09 2020] drm_drop_master+0x1e/0x30 [drm] [Sat Mar 14 09:39:09 2020] drm_master_release+0xa0/0xb0 [drm] [Sat Mar 14 09:39:09 2020] drm_file_free.part.13+0x235/0x290 [drm] [Sat Mar 14 09:39:09 2020] drm_release+0x9a/0xd0 [drm] [Sat Mar 14 09:39:09 2020] __fput+0xbe/0x250 [Sat Mar 14 09:39:09 2020] task_work_run+0x9f/0xc0 [Sat Mar 14 09:39:09 2020] exit_to_usermode_loop+0x10d/0x130 [Sat Mar 14 09:39:09 2020] do_syscall_64+0x1cd/0x1f0 [Sat Mar 14 09:39:09 2020] entry_SYSCALL_64_after_hwframe+0x49/0xbe [Sat Mar 14 09:39:09 2020] RIP: 0033:0x7f1be272cf24 [Sat Mar 14 09:39:09 2020] Code: 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 80 00 00 00 00 8b 05 ca c4 20 00 48 63 ff 85 c0 75 13 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 44 f3 c3 66 90 48 83 ec 18 48 89 7c 24 08 e8 [Sat Mar 14 09:39:09 2020] RSP: 002b:00007ffddc0d8c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000003 [Sat Mar 14 09:39:09 2020] RAX: 0000000000000000 RBX: 000000000000000a RCX: 00007f1be272cf24 [Sat Mar 14 09:39:09 2020] RDX: 0000556d5718a020 RSI: 0000000000000002 RDI: 000000000000000a [Sat Mar 14 09:39:09 2020] RBP: 0000556d571cb340 R08: 0000556d571c9c80 R09: 0000000000000000 [Sat Mar 14 09:39:09 2020] R10: 0000000000000079 R11: 0000000000000246 R12: 0000556d571e4380 [Sat Mar 14 09:39:09 2020] R13: 0000556d571e44e0 R14: 0000000000000000 R15: 0000000000000000 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c53 --- Comment #53 from Stefan Dirsch <sndirsch@suse.com> --- Hmm. I'm wondering whether you have NVIDIA's DRM KMS support enabled. From the README: Chapter 35. Direct Rendering Manager Kernel Modesetting (DRM KMS) ______________________________________________________________________________ The NVIDIA GPU driver package provides a kernel module, nvidia-drm.ko, which registers a DRM driver with the DRM subsystem of the Linux kernel. The capabilities advertised by this DRM driver depend on the Linux kernel version and configuration: o PRIME: This is needed to support graphics display offload in RandR 1.4. Linux kernel version 3.13 or higher is required, with CONFIG_DRM enabled. o Atomic Modeset: This is used for display of non-X11 based desktop environments, such as Wayland and Mir. Linux kernel version 4.1 or higher is required, with CONFIG_DRM and CONFIG_DRM_KMS_HELPER enabled. NVIDIA's DRM KMS support is still considered experimental. It is disabled by default, but can be enabled on suitable kernels with the 'modeset' kernel module parameter. E.g., modprobe -r nvidia-drm ; modprobe nvidia-drm modeset=1 Applications can present through NVIDIA's DRM KMS implementation using any of the following: o The DRM KMS "dumb buffer" mechanism to create and map CPU-accessible buffers: DRM_IOCTL_MODE_CREATE_DUMB, DRM_IOCTL_MODE_MAP_DUMB, and DRM_IOCTL_MODE_DESTROY_DUMB. o Using the EGL_EXT_device_drm, EGL_EXT_output_drm, and EGL_EXT_stream_consumer_egloutput EGL extensions to associate EGLStream producers with specific DRM KMS planes. 35A. KNOWN ISSUES o The NVIDIA DRM KMS implementation is currently incompatible with SLI. The X server will fail to initialize SLI if DRM KMS is enabled. o The NVIDIA DRM KMS implementation does not yet register an overlay plane: only primary and cursor planes are currently provided. o Buffer allocation and submission to DRM KMS using gbm is not currently supported. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c54 --- Comment #54 from Dr. Werner Fink <werner@suse.com> --- AFAICS from setup yes, check lsmod | grep nvidia.drm nvidia_drm 53248 9 nvidia_modeset 1118208 12 nvidia_drm drm_kms_helper 229376 2 nvidia_drm,i915 drm 544768 12 drm_kms_helper,nvidia_drm,i915 sudo cat /sys//module/nvidia_drm/parameters/modeset Y
cat /proc/cmdline | tr ' ' '\n' | grep mode nvidia-drm.modeset=1 nvidia_drm.modeset=1 modeset=1
or should I disable this ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c55 --- Comment #55 from Stefan Dirsch <sndirsch@suse.com> --- Yes, that would have been my idea. It's considered experimental and it's not the default therefore. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c56 --- Comment #56 from Dr. Werner Fink <werner@suse.com> --- (In reply to Stefan Dirsch from comment #55)
Yes, that would have been my idea. It's considered experimental and it's not the default therefore.
I've change it to modeset=0 for nvidia[-_]drm ... currently it seems stable on switching from vt8 to vt7 and back -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c57 --- Comment #57 from Dr. Werner Fink <werner@suse.com> --- Args ... now I had a crash on vt7 [ 5607.436] (EE) [ 5607.436] (EE) Backtrace: [ 5607.436] (EE) 0: /usr/bin/X (xorg_backtrace+0x65) [0x55af0184af45] [ 5607.436] (EE) 1: /usr/bin/X (0x55af01699000+0x1b5c19) [0x55af0184ec19] [ 5607.436] (EE) 2: /lib64/libpthread.so.0 (0x7efd36507000+0x12300) [0x7efd36519300] [ 5607.436] (EE) 3: /lib64/libc.so.6 (gsignal+0x110) [0x7efd36183160] [ 5607.436] (EE) 4: /lib64/libc.so.6 (abort+0x151) [0x7efd36184741] [ 5607.436] (EE) 5: /lib64/libc.so.6 (0x7efd3614d000+0x794a7) [0x7efd361c64a7] [ 5607.437] (EE) 6: /lib64/libc.so.6 (0x7efd3614d000+0x7fcc3) [0x7efd361cccc3] [ 5607.437] (EE) 7: /lib64/libc.so.6 (0x7efd3614d000+0x815c9) [0x7efd361ce5c9] [ 5607.437] (EE) 8: /usr/bin/X (FreeCursor+0x87) [0x55af016e8947] [ 5607.437] (EE) 9: /usr/bin/X (0x55af01699000+0xdb0ef) [0x55af017740ef] [ 5607.437] (EE) 10: /usr/bin/X (miPointerUpdateSprite+0x22a) [0x55af01837aba] [ 5607.437] (EE) 11: /usr/bin/X (0x55af01699000+0x19ed0a) [0x55af01837d0a] [ 5607.437] (EE) 12: /usr/bin/X (0x55af01699000+0xe957d) [0x55af0178257d] [ 5607.438] (EE) 13: /usr/bin/X (0x55af01699000+0x12fc16) [0x55af017c8c16] [ 5607.438] (EE) 14: /usr/bin/X (0x55af01699000+0x6532b) [0x55af016fe32b] [ 5607.438] (EE) 15: /usr/bin/X (0x55af01699000+0x692ec) [0x55af017022ec] [ 5607.438] (EE) 16: /usr/bin/X (WindowsRestructured+0x3a) [0x55af017024ca] [ 5607.438] (EE) 17: /usr/bin/X (MapWindow+0x242) [0x55af01720f12] [ 5607.438] (EE) 18: /usr/bin/X (0x55af01699000+0x5656b) [0x55af016ef56b] [ 5607.438] (EE) 19: /usr/bin/X (0x55af01699000+0x5c488) [0x55af016f5488] [ 5607.438] (EE) 20: /usr/bin/X (0x55af01699000+0x6049c) [0x55af016f949c] [ 5607.439] (EE) 21: /lib64/libc.so.6 (__libc_start_main+0xea) [0x7efd3616df8a] [ 5607.439] (EE) 22: /usr/bin/X (_start+0x2a) [0x55af016e312a] [ 5607.439] (EE) [ 5607.439] (EE) Fatal server error: [ 5607.439] (EE) Caught signal 6 (Aborted). Server aborting [ 5607.439] (EE) [ 5607.439] (EE) someone had calles abort() -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c58 --- Comment #58 from Stefan Dirsch <sndirsch@suse.com> --- Ok. So basically nothing has changed ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c59 --- Comment #59 from Dr. Werner Fink <werner@suse.com> --- Now on vt8 [ 6876.086] (EE) [ 6876.086] (EE) Backtrace: [ 6876.087] (EE) 0: X (xorg_backtrace+0x65) [0x5598aec25f45] [ 6876.087] (EE) 1: X (0x5598aea74000+0x1b5c19) [0x5598aec29c19] [ 6876.087] (EE) 2: /lib64/libpthread.so.0 (0x7fa8116cb000+0x12300) [0x7fa8116dd300] [ 6876.087] (EE) 3: X (0x5598aea74000+0xdb618) [0x5598aeb4f618] [ 6876.087] (EE) 4: X (0x5598aea74000+0x12f86a) [0x5598aeba386a] [ 6876.087] (EE) 5: X (FreeCursor+0x5b) [0x5598aeac391b] [ 6876.087] (EE) 6: X (0x5598aea74000+0xdb150) [0x5598aeb4f150] [ 6876.087] (EE) 7: X (miPointerUpdateSprite+0x22a) [0x5598aec12aba] [ 6876.087] (EE) 8: X (0x5598aea74000+0x19ed0a) [0x5598aec12d0a] [ 6876.087] (EE) 9: X (0x5598aea74000+0xe957d) [0x5598aeb5d57d] [ 6876.088] (EE) 10: X (0x5598aea74000+0x12fc16) [0x5598aeba3c16] [ 6876.088] (EE) 11: X (0x5598aea74000+0x6532b) [0x5598aead932b] [ 6876.088] (EE) 12: X (WindowHasNewCursor+0x37) [0x5598aeada7c7] [ 6876.088] (EE) 13: X (ChangeWindowAttributes+0xcf1) [0x5598aeafddd1] [ 6876.088] (EE) 14: X (0x5598aea74000+0x560f3) [0x5598aeaca0f3] [ 6876.088] (EE) 15: X (0x5598aea74000+0x5c488) [0x5598aead0488] [ 6876.088] (EE) 16: X (0x5598aea74000+0x6049c) [0x5598aead449c] [ 6876.088] (EE) 17: /lib64/libc.so.6 (__libc_start_main+0xea) [0x7fa811331f8a] [ 6876.088] (EE) 18: X (_start+0x2a) [0x5598aeabe12a] [ 6876.088] (EE) [ 6876.088] (EE) Segmentation fault at address 0x29 [ 6876.088] (EE) Fatal server error: [ 6876.089] (EE) Caught signal 11 (Segmentation fault). Server aborting -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c60 --- Comment #60 from Dr. Werner Fink <werner@suse.com> --- (In reply to Stefan Dirsch from comment #58)
Ok. So basically nothing has changed ...
Indeed -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Leap 15.1 |Leap 15.3 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1151290 http://bugzilla.opensuse.org/show_bug.cgi?id=1151290#c64 --- Comment #64 from Stefan Dirsch <sndirsch@suse.com> --- Ok. So nice try. :-( -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com