Bug 479654 - Plasma Crashed after switching the Primary screen right after the first install
Summary: Plasma Crashed after switching the Primary screen right after the first install
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (other bugs)
Version First Reported In: master
Platform: Neon Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi, qt6
Depends on:
Blocks:
 
Reported: 2024-01-11 16:51 UTC by Lamdarer
Modified: 2024-01-29 20:50 UTC (History)
2 users (show)

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


Attachments
New crash information added by DrKonqi (69.58 KB, text/plain)
2024-01-11 16:51 UTC, Lamdarer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lamdarer 2024-01-11 16:51:43 UTC
Application: plasmashell (5.91.90)

Qt Version: 6.6.1
Frameworks Version: 5.248.0
Operating System: Linux 6.2.0-39-generic x86_64
Windowing System: Wayland
Distribution: KDE neon Unstable Edition
DrKonqi: 5.91.90 [CoredumpBackend]

-- Information about the crash:
I installed KDE Neon from a live USB, restarted the PC.
Than I looged in(btw ENTER was nont recognised after typing my password, I had to manualy click ENTER with the mouse after I wrote my password),
after loggin, without using the KDE-Welcome Application->
Right-click on Deskop->
configure screens/Display->
Select the second of my 2 screens-> Make Primary
=> KDE crashed and told me to do this bug report, however it only took 1sec or so for Plasma to restart and reinitiate the Taskbar on my new Primary screen.

Will see if I can reproduce this, after updating or encounter other bugs.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#6  0x00007f5e05e82db4 in QtPrivate::QMetaTypeForType<QList<QString> >::getDtor()::{lambda(QtPrivate::QMetaTypeInterface const*, void*)#1}::_FUN(QtPrivate::QMetaTypeInterface const*, void*) () at /lib/x86_64-linux-gnu/libQt6Core.so.6
#7  0x00007f5e079a4e82 in QtWaylandClient::QWaylandWindow::createDecoration() () at /lib/x86_64-linux-gnu/libQt6WaylandClient.so.6
#8  0x00007f5e0125c6cc in QtWaylandClient::QWaylandGLContext::makeCurrent(QPlatformSurface*) () at /lib/x86_64-linux-gnu/libQt6WaylandEglClientHwIntegration.so.6
#9  0x00007f5e065d8c9e in QOpenGLContext::makeCurrent(QSurface*) () at /lib/x86_64-linux-gnu/libQt6Gui.so.6
[...]
#12 0x00007f5e064c1d46 in QRhi::beginFrame(QRhiSwapChain*, QFlags<QRhi::BeginFrameFlag>) () at /lib/x86_64-linux-gnu/libQt6Gui.so.6


Reported using DrKonqi
Comment 1 Lamdarer 2024-01-11 16:51:44 UTC
Created attachment 164815 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 fanzhuyifan 2024-01-11 17:30:30 UTC
The backtrace is missing debug symbols for these lines:

#6  0x00007f5e0759d29f in  () at /lib/x86_64-linux-gnu/libQt6Quick.so.6
#7  0x00007f5e074f803a in  () at /lib/x86_64-linux-gnu/libQt6Quick.so.6
#8  0x00007f5e06346588 in QWindow::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt6Gui.so.6

Could you install debug symbols and attach the backtrace following the instructions here? Thanks!
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
Comment 3 Lamdarer 2024-01-12 16:57:59 UTC
(In reply to fanzhuyifan from comment #2)
> The backtrace is missing debug symbols for these lines:
> 
> #6  0x00007f5e0759d29f in  () at /lib/x86_64-linux-gnu/libQt6Quick.so.6
> #7  0x00007f5e074f803a in  () at /lib/x86_64-linux-gnu/libQt6Quick.so.6
> #8  0x00007f5e06346588 in QWindow::event(QEvent*) () at
> /lib/x86_64-linux-gnu/libQt6Gui.so.6
> 
> Could you install debug symbols and attach the backtrace following the
> instructions here? Thanks!
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl

Thanks for the reply, not sure if I got it right(btw I wasnt able to reproduce this bug):

(gdb) bt
#0  0x00007f5e052969fc in ?? ()
#1  <signal handler called>
#2  0x00007f5d5bffdf58 in ?? ()
#3  0x000055a2a99ab570 in ?? ()
#4  0x000055a2a99ab580 in ?? ()
#5  0x0000000000000007 in ?? ()
#6  0x00007f5cf08b4500 in ?? ()
#7  0x31317f5cf00d97f0 in ?? ()
#8  0x0000000000000000 in ?? ()
Comment 4 Bug Janitor Service 2024-01-27 03:45:45 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Lamdarer 2024-01-27 09:42:28 UTC
Tried to provide the info with https://bugs.kde.org/show_bug.cgi?id=479654#c3
Not sure if I did it right, also I don't have the Beta installed anymore, but I will check if I can reproduce it once I install the next Beta.
Comment 6 Nate Graham 2024-01-29 20:50:15 UTC
Ok, thanks.