[kscreenlocker] [Bug 450542] New: Black screen after unplugging external monitors when laptop screen is disabled
https://bugs.kde.org/show_bug.cgi?id=450542 Bug ID: 450542 Summary: Black screen after unplugging external monitors when laptop screen is disabled Product: kscreenlocker Version: 5.24.1 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: greeter Assignee: plasma-b...@kde.org Reporter: sbutcher+b...@gmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY Removing the external displays (via thunderbolt dock) while the screenlocker is active results in a black screen on the laptop STEPS TO REPRODUCE 1. Attach laptop to dock and use external monitors ONLY (laptop screen disabled) 2. Lock screen (e.g. with super key+L) 3. Detach usb c dock cable OBSERVED RESULT Screen is black except for mouse cursor, cannot access desktop or screenlocker EXPECTED RESULT Expect to see the screenlocker password prompt with wallpaper background SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Graphics platform: X11 , Intel TigerLake-LP GT2 [Iris Xe Graphics] Distro: kubuntu 21.10 with backports PPA ADDITIONAL INFORMATION Other bugs seem to relate to compositing, and are fixable by switching ctrl-alt-f2 and back again to ctrl-alt-f1. However, this is not the same bug. My current workaround is : hit ctrl-alt-f2 and type "ps -ef | grep kscreenlocker_greet" then kill the PID of the process. Hit ctrl-alt-f1 and the screenlocker password prompt appears as expected. I can reproduce this at will. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 450542] Black screen after unplugging external monitors when laptop screen is disabled
https://bugs.kde.org/show_bug.cgi?id=450542 Simon B changed: What|Removed |Added Keywords||reproducible -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454441] New: kwin occasional crash during alt-tab
https://bugs.kde.org/show_bug.cgi?id=454441 Bug ID: 454441 Summary: kwin occasional crash during alt-tab Product: kwin Version: 5.24.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: sbutcher+b...@gmail.com Target Milestone: --- Created attachment 149234 --> https://bugs.kde.org/attachment.cgi?id=149234&action=edit backtrace SUMMARY Using xorg. CPU: 11th Gen Intel i7-1165G7 (8) @ 2.800GHz GPU: Intel TigerLake-LP GT2 [Iris Xe Graphics] Application: kwin_x11 (5.24.5) Qt Version: 5.15.3 Frameworks Version: 5.94.0 Operating System: Linux 5.15.0-30-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04 LTS DrKonqi: 5.24.5 [KCrashBackend] STEPS TO REPRODUCE 1. Happened twice today during alt-tab (with reboots done in-between) 2. Once during a teams call and another time using firefox OBSERVED RESULT Kwin crash, desktop stays running but the kde bug reporter appears, and stack trace generated. EXPECTED RESULT Kwin doesn't crash SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- Backtrace: Application: KWin (kwin_x11), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140058780362048) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140058780362048) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=140058780362048, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7f61fe7fe476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f61fe7e47f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7f61f2710144 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #10 0x7f61f337938f in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #11 0x7f61f2976782 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #12 0x7f620145c384 in ?? () from /lib/x86_64-linux-gnu/libkwin.so.5 #13 0x7f61ff976783 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f6201433c98 in KWin::Scene::paintScreen(QRegion const&, QRegion const&, QRegion*, QRegion*, KWin::RenderLoop*, QMatrix4x4 const&) () from /lib/x86_64-linux-gnu/libkwin.so.5 #15 0x7f62014f5060 in KWin::SceneOpenGL::paint(KWin::AbstractOutput*, QRegion const&, QList const&, KWin::RenderLoop*) () from /lib/x86_64-linux-gnu/libkwin.so.5 #16 0x7f6201396071 in KWin::Compositor::composite(KWin::RenderLoop*) () from /lib/x86_64-linux-gnu/libkwin.so.5 #17 0x7f620139fa06 in KWin::X11Compositor::composite(KWin::RenderLoop*) () from /lib/x86_64-linux-gnu/libkwin.so.5 #18 0x7f61ff976783 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f6201355b16 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*) () from /lib/x86_64-linux-gnu/libkwin.so.5 #20 0x7f6201422297 in KWin::RenderLoopPrivate::dispatch() () from /lib/x86_64-linux-gnu/libkwin.so.5 #21 0x7f61ff976783 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f61ff97a7ee in QTimer::timeout(QTimer::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f61ff96c32f in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f61fef15713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f61ff93ee2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f61ff9973db in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f61ff995897 in QEventDispatcherUNIX::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f61f9703142 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #29 0x7f61ff93d74b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7f61ff945ce4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x55e56e671bad in ?? () #32 0x7f61fe7e5d90 in __libc_start_call_main (main=main@entry=0x55e56e671770, argc=argc@entry=1, argv=argv@entry=0x7ffcb35db648) at ../sysdeps/nptl/libc_start_call_main.h:58 #33 0x7f61fe7e5e40 in __libc_start_main_impl (main=0x55e56e671770, argc=1, argv=0x7ffcb35db648, init=, fini=, rtld_fini=, stack_end=0x7ffcb35db638) at ../csu/libc-start.c:392 #34 0x55e56e672eb5 in ?? () [Inferior 1 (process 2690) detached] -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 437471] Cannot unlock KDE lockscreen after undocking while laptop screen was off
https://bugs.kde.org/show_bug.cgi?id=437471 --- Comment #7 from Simon B --- I say this tentatively, as this bug has plagued me for a long time, but... plasma 5.27.1 seems to fix this for me. Can anyone else confirm? wake-up time is a little long but after about 15s the laptop screen comes alive, which it never did before -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Simon B changed: What|Removed |Added CC||sbutcher+b...@gmail.com --- Comment #34 from Simon B --- Is it still occurring with plasma 5.27.x? Some similar bugs got resolved with this release -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421135] Flickering Issue with Blur enabled
https://bugs.kde.org/show_bug.cgi?id=421135 Simon B changed: What|Removed |Added CC||sbutcher+b...@gmail.com --- Comment #16 from Simon B --- Created attachment 152683 --> https://bugs.kde.org/attachment.cgi?id=152683&action=edit Konsole flickering badly when blur is enabled Still happening for me on 5.24.6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 Simon B changed: What|Removed |Added CC|sbutcher+b...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450542] Black screen after unplugging external monitors when laptop screen is disabled
https://bugs.kde.org/show_bug.cgi?id=450542 --- Comment #2 from Simon B --- Another observation. This only seems to occur with 2 external monitors. With one external monitor and the laptop screen off, removing the usb C cable to the dock while the laptop is sleeping, results in a working lock-screen on resume. With 2 external monitors and the laptop screen off, the problem occurs. The only way to recover is ctrl-alt-f2 and kill kscreenlocker_greet process, then returning to ctrl-alt-f1 shows the lock screen as usual. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450542] Black screen after unplugging external monitors when laptop screen is disabled
https://bugs.kde.org/show_bug.cgi?id=450542 Simon B changed: What|Removed |Added Product|kscreenlocker |plasmashell CC||aleix...@kde.org Version|5.24.1 |5.24.4 Component|greeter |Multi-screen support Target Milestone|--- |1.0 --- Comment #1 from Simon B --- Having disabled the option to lock the screen on sleep, i realised this is not a kscreenlocker_greet issue. Workflow: 1) laptop with 2 monitors attached via usb c to Dell dock (e.g. WD19 but also another Dell monitor with integrated usb c dock) 2) laptop display disabled, monitor display enabled. 3) set computer to sleep 4) remove usb C cable 5) wake laptop from sleep 6) black screen (although ctrl-alt-f2 shows a vty) if i now plug the usb c cable back in, the display returns to the monitors, and i can then remove the usb c dock cable and regain visible screen on the laptop display. so in summary, plasma doesn't recognise the display settings have changed when resuming from sleep, unless i plug the dock back in again and remove it. this is repeatable every time (and obviously an issue if you grab your laptop to go to a meeting or a train journey when it is sleeping attached to the dock) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 Simon B changed: What|Removed |Added CC||sbutcher+b...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451235] right click menu entries not readable in wayland
https://bugs.kde.org/show_bug.cgi?id=451235 Simon B changed: What|Removed |Added CC||sbutcher+b...@gmail.com --- Comment #1 from Simon B --- I get the same thing happening on my external monitors which are attached via usb C dock. The right-click menu appears normally on the laptop display, but not the other 2 displays. GPU: Intel TigerLake-LP GT2 [Iris Xe Graphics] Running wayland and plasma 5.24.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443640] New: System settings panel turns black after sleep/resume
https://bugs.kde.org/show_bug.cgi?id=443640 Bug ID: 443640 Summary: System settings panel turns black after sleep/resume Product: kwin Version: 5.22.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: sbutcher+b...@gmail.com Target Milestone: --- Created attachment 142372 --> https://bugs.kde.org/attachment.cgi?id=142372&action=edit screenshot showing the black panel on system settings SUMMARY After sleep/resume STEPS TO REPRODUCE 1. Open system settings, click on "system information" 2. Click Sleep, to send the PC to sleep 3. Wake the computer and login again. OBSERVED RESULT The right-hand pane which previously showed the system information is now black. Clicking other sections (e.g. audio) shows some info, but KDE connect or printers remains black Clicking back to system information remains black again. To workaround: resize the window, and the panel stops being black. See this video for a demonstration https://www.youtube.com/watch?v=WAL3IV__HOo EXPECTED RESULT Expect to see system information, without a black panel SOFTWARE/OS VERSIONS Linux/KDE Plasma: kubuntu 21.04 w/backports (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Graphics platform: X11 ADDITIONAL INFORMATION Nvidia RTX 2060 card, dual monitor configuration Driver Version: 470.63.01 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 437471] Cannot unlock KDE lockscreen after undocking while laptop screen was off
https://bugs.kde.org/show_bug.cgi?id=437471 Simon B changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=450542 CC||sbutcher+b...@gmail.com --- Comment #6 from Simon B --- *** Bug 450542 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450542] Black screen after unplugging external monitors when laptop screen is disabled
https://bugs.kde.org/show_bug.cgi?id=450542 Simon B changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=437471 Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #5 from Simon B --- Pretty sure this is describing the same behaviour as 437471 *** This bug has been marked as a duplicate of bug 437471 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450542] Black screen after unplugging external monitors when laptop screen is disabled
https://bugs.kde.org/show_bug.cgi?id=450542 Simon B changed: What|Removed |Added Version|5.24.4 |5.26.2 --- Comment #3 from Simon B --- This bug persists in plasma 5.26.2 1) 2 external monitors via thunderbolt dock, laptop display off. 2) Set laptop to Sleep 3) unplug the cable to the dock 4) open the laptop lid to wake the laptop, and the screenlocker doesn't revert to using the laptop screen when the external monitors are removed while asleep. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450542] Black screen after unplugging external monitors when laptop screen is disabled
https://bugs.kde.org/show_bug.cgi?id=450542 --- Comment #4 from Simon B --- Perhaps related, I find this in the dmesg output upon wake-up. [Mon Oct 31 10:09:25 2022] i915 :00:02.0: [drm] *ERROR* [ENCODER:338:DDI TC3/PHY TC3][DPRX] Failed to enable link training [Mon Oct 31 10:09:26 2022] i915 :00:02.0: [drm] *ERROR* failed to allocate vcpi -- You are receiving this mail because: You are watching all bug changes.
