Bug 371048

Summary:	kwin_wayland crash at session login
Product:	[Plasma] kwin	Reporter:	m.rbizarre
Component:	wayland-generic	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	crash
Priority:	NOR
Version First Reported In:	5.8.0
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	kwin_wayland dump file

Description m.rbizarre 2016-10-17 23:17:30 UTC

Hello,
Since recently i was using kaos, and i occasionally tried the wayland session to watch the progresses.

Since i change my graphic card (4950 -> fury), if i log to the wayland session, i just get a quick black screen and it go back to sddm. Then i move to kde neon and i install every wayland related packages. I have the same problem if i go to wayland session.

I tried to look at ksystemlog, and i presume the problem come from this : 
kwin_wayland[5360]: segfault at 968 ip 00007f3fe2a954fa sp 00007ffe995fca90 error 4 in libX11.so.6.3.0[7f3fe2a6d000+135000]

Also if i log out and kill sddm, wayland session work if i run this command : kwin_wayland --libinput --xwayland "plasmashell --platform wayland"

Reproducible: Always




kde neon stable with padoka PPA
amdgpu + radeonsi
sapphire fury
evga x79 sli + core i7 3820

Comment 1 Martin Flöser 2016-10-18 05:33:21 UTC

Please provide a backtrace of the crash. Without we are not able to investigate. All we have now is that it crashed somewhere in libX11 which is not a very helpful information as we use that a few times in KWin and in libraries.

Maybe check whether coredumpctl caught the crash.

Comment 2 m.rbizarre 2016-10-20 23:05:15 UTC

marc@marc-PC:~$ coredumpctl info 1666
           PID: 1666 (kwin_wayland)
           UID: 1000 (marc)
           GID: 1000 (marc)
        Signal: 11 (SEGV)
     Timestamp: ven. 2016-10-21 00:46:06 CEST (15min ago)
  Command Line: /usr/bin/kwin_wayland --xwayland --libinput --exit-with-session=/usr/lib/x86_64-linux-gnu/libexec/startplasma
    Executable: /usr/bin/kwin_wayland
 Control Group: /user.slice/user-1000.slice/session-3.scope
          Unit: session-3.scope
         Slice: user-1000.slice
       Session: 3
     Owner UID: 1000 (marc)
       Boot ID: 2c361b42820c477d800e5b98113b926a
    Machine ID: 6ac3536027bb42158f9245cae0ea13ff
      Hostname: marc-PC
      Coredump: /var/lib/systemd/coredump/core.kwin_wayland.1000.2c361b42820c477d800e5b98113b926a.1666.1477003566000000000000.xz
       Message: Process 1666 (kwin_wayland) of user 1000 dumped core.
                
                Stack trace of thread 1666:
                #0  0x00007f24697d54fa XInternAtom (libX11.so.6)
                #1  0x00007f245a1eb8ca n/a (libkvantum.so)
                #2  0x00007f247240e4ea n/a (n/a)

Comment 3 m.rbizarre 2016-10-20 23:05:46 UTC

Created attachment 101672 [details]
kwin_wayland dump file

Comment 4 Martin Flöser 2016-10-21 05:53:46 UTC

hmm the core doesn't give me anything useful.

What is interesting is the: XInternAtom

KWin code does not have any XInternAtom call anymore which means that was from a library or plugin that kwin loads. Any third party widget style or window decoration?

Comment 5 Martin Flöser 2016-10-21 05:57:53 UTC

reopening to investigate the XInternAtom usage

Comment 6 m.rbizarre 2016-10-22 15:18:12 UTC

It seems i find the problem. I am using kvantum arc theme and forget to turn it off. I use the breeze complete set and now i can login to my wayland session.

However it seems that this problem wasn't related to kvantum in the past. When i install kde neon on my system i tried the wayland session with breeze and it crash the same way, it seems recent update correct the problem.

Anyway sorry for the false report

Comment 7 Martin Flöser 2016-10-23 13:47:53 UTC

Thanks for the update