Bug 480754 - Monitor flickers, after disconnecting the HDMI and reconnecting it, the monitor works perfectly but a crash had occured
Summary: Monitor flickers, after disconnecting the HDMI and reconnecting it, the monit...
Status: RESOLVED DUPLICATE of bug 464377
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: master
Platform: Neon Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi, qt6
Depends on:
Blocks:
 
Reported: 2024-02-02 23:52 UTC by Marko B
Modified: 2024-02-05 21:58 UTC (History)
1 user (show)

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


Attachments
New crash information added by DrKonqi (93.32 KB, text/plain)
2024-02-02 23:52 UTC, Marko B
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marko B 2024-02-02 23:52:11 UTC
Application: plasmashell (6.0.80)

Qt Version: 6.6.1
Frameworks Version: 5.249.0
Operating System: Linux 6.5.0-15-generic x86_64
Windowing System: Wayland
Distribution: KDE neon Unstable Edition
DrKonqi: 6.0.80 [CoredumpBackend]

-- Information about the crash:
I had previously also reported this same bug. I'm running latest updates from KDE Neon Unstable. Same laptop, intel i7 9th gen + nvidia 1660ti, same duo monitor setup, usb-c (dp) + HDMI. The usb-c display connects and works while the HDMI display has also conencted but with WILD flickering, like very bad. After disconnecting HDMI, and reconnecting it, this crash occurs, but not the monitor works. One of the other things I noticed is that SOMETIMES the USB-C monitor does not connect at all, like the system does not recognise it. This happens sometimes, (fresh boot, not after sleeping) but a restart fixes it. Hope this crash report helps :)

The crash can be reproduced every time.

-- Backtrace (Reduced):
#6  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140112036567744) at ./nptl/pthread_kill.c:44
#7  __pthread_kill_internal (signo=6, threadid=140112036567744) at ./nptl/pthread_kill.c:78
#8  __GI___pthread_kill (threadid=140112036567744, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#9  0x00007f6e64242476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#10 0x00007f6e642287f3 in __GI_abort () at ./stdlib/abort.c:79


Reported using DrKonqi
Comment 1 Marko B 2024-02-02 23:52:12 UTC
Created attachment 165489 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Nate Graham 2024-02-05 21:58:18 UTC
> I had previously also reported this same bug.
Please do not intentionally submit duplicate bug reports. Normally I'd ask you to locate the bug report you already submitted so we can follow up there, but from

#16 0x000055f397e0e860 in ScreenPool::screenInvariants() (this=0x55f399ed8280) at ./shell/screenpool.cpp:336
#17 0x000055f397e8b93d in ScreenPool::handleOutputOrderChanged(QList<QString> const&) (this=0x55f399ed8280, newOrder=<optimized out>) at ./shell/screenpool.cpp:308

I can see that it's Bug 464377.

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