Bug 247195

Summary: x11/plasma5-plasma-desktop Log Out problem
Product: Ports & Packages Reporter: Ott Köstner <ottkostner>
Component: Individual Port(s)Assignee: freebsd-kde (group) <kde>
Status: Closed Works As Intended    
Severity: Affects Only Me CC: adridg, sv
Priority: --- Flags: bugzilla: maintainer-feedback? (kde)
Version: Latest   
Hardware: amd64   
OS: Any   
Attachments:
Description Flags
KDE Crach Handler report none

Description Ott Köstner 2020-06-12 07:17:31 UTC 
After upgrading KDE Plasma desktop to new version 5.19.0 I have problems logging out (get KCrash Handler error) -

Application: kwin_x11 (kwin_x11), signal: Segmentation fault

[KCrash Handler]
#7  0x0000000803282d1f in QThreadStorageData::get() const () at /usr/local/lib/qt5/libQt5Core.so.5
#8  0x0000000802af796b in QOpenGLContext::currentContext() () at /usr/local/lib/qt5/libQt5Gui.so.5
#9  0x0000000802af807f in QOpenGLContext::destroy() () at /usr/local/lib/qt5/libQt5Gui.so.5
#10 0x0000000802af87bc in QOpenGLContext::~QOpenGLContext() () at /usr/local/lib/qt5/libQt5Gui.so.5
#11 0x00000008038f3181 in __cxa_finalize (dso=0x8006f1000) at /usr/src/lib/libc/stdlib/atexit.c:238
#12 0x00000008006d7023 in  () at /usr/local/lib/libkwineffects.so.12
#13 0x00007fffffffe1c0 in  ()
#14 0x00000008006ef1b5 in _fini () at /usr/local/lib/libkwineffects.so.12
#15 0x00007fffffffe1c0 in  ()
#16 0x00000008002208a3 in objlist_call_fini (list=<optimized out>, root=<optimized out>, lockstate=<optimized out>) at /usr/src/libexec/rtld-elf/rtld.c:2634
[Inferior 1 (process 79341) detached]

Looking to the processes shows that after logout there is kwin_x11 process still running. If I kill it manually everything returns back to normal until I am trying to log out of KDE next time.
Comment 1 Ott Köstner 2020-06-12 10:19:15 UTC 
Created attachment 215479 [details]
KDE Crach Handler report
Comment 2 Adriaan de Groot freebsd_committer freebsd_triage 2021-04-23 21:52:23 UTC 
This looks vaguely like a library mismatch. Does it happen to you with current packages? With a new user? If so, is there something special -- openGL drivers come to mind, based on this backtrace -- about the hardware?
Comment 3 Ott Köstner 2021-04-27 12:33:14 UTC 
Have upgraded to the version 5.21.4. After upgrade the problem has gone.