Bug 444123 - switching activity with meta+tab crashes KWin
Summary: switching activity with meta+tab crashes KWin
Status: RESOLVED DUPLICATE of bug 441547
Alias: None
Product: kwin
Classification: Plasma
Component: activities (show other bugs)
Version: 5.23.1
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2021-10-20 15:58 UTC by kinghat
Modified: 2021-10-25 15:43 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description kinghat 2021-10-20 15:58:39 UTC 
SUMMARY
i have two activities from 5.22 days and if i meta + tab between them plasma(?) crashes. im not sure what exactly crashes as i dont get a report/crash notification and the dialog to gather logs and report, but all apps are killed and it looks like plasma starts from scratch.

STEPS TO REPRODUCE
1. have at leas two activities. mine have 4 virtual desktops in a grid.
2. meta + tab to switch between them.
3. profit

OBSERVED RESULT
everything is killed and plasma is started fresh. no report of said crash from crash reporter.

EXPECTED RESULT
switch to the next/previous activity.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.23
KDE Plasma Version: 5.23.1
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-38-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i7-5600U CPU @ 2.60GHz
Memory: 11.6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION
noticed this in 5.23 but waited for 5.23.1 to see if it would be fixed.

meta + q and picking activity from there doesnt seem to cause a crash.
Comment 1 hammerheadlemon 2021-10-20 17:10:11 UTC 
I am seeing similar, except not a complete crash but partial freeze/slowdown to the point of UI being unusable.
Comment 2 Nate Graham 2021-10-21 12:59:08 UTC 
Sounds like KWin is crashing. Can you please get a backtrace of kwin_wayland? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
Comment 3 kinghat 2021-10-23 04:36:15 UTC 
hey nate, sorry for the slow reply: https://0bin.net/paste/5TwFNyqj#m7TJjUsbOkitCh2S9iQn5aeQEsaUDo0xjME52BUidgB
Comment 4 Nate Graham 2021-10-25 14:59:05 UTC 
Thanks! Unfortunately we are missing some debug symbols:

#1  0x00007f4dc1619d99 in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so
#2  0x00007f4dc1626233 in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so
#3  0x00007f4dc1626983 in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so

Can you install debug symbols for the rest of KWin and attach a new backtrace with all of the symbols.

Thanks again!
Comment 5 kinghat 2021-10-25 15:18:40 UTC 
im not sure which symbols to get. am i even on the right track here?
https://0bin.net/paste/QhtDZ3sc#OrrA9HUV-fWrSsui2DBm639J7msszRAMY9tz5jUqVnK
Comment 6 Vlad Zahorodnii 2021-10-25 15:43:44 UTC 

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