[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Is 5.27 expected before freeze?



Hello,

My system is afflicted by the "monitor not enabled after hot-connect" bug [BUG].  
This was previously discussed on Debian lists [DEBIAN].

I have done a bit of debugging and applied a fix locally that simply sets the 
enabled flag to true on each connected display.  This completely resolves the 
issue for my case.  I reported this in the upstream bug report but there was 
no reaction.

However, there was a note in the bug report stating that while no KDE 
developer has been able to reproduce the issue (!) but there was recently a 
"massive multiscreen overhaul" merged into upstream on 2022-12-15.  My 
understanding is that this will be in the 5.27 release.  I tried getting 
upstream sources for 5.27 suggested by Nate Graham [BUG2] but quickly got 
overwhelmed by the need to re-build more than just the five he listed.

Thus, I'm wondering whether there's an easier way for me to try 5.27 packages.  
I'm completely intimidated by the set of KDE packages in Debian.  So I'm 
curious whether there is any thought that 5.27 might be uploaded anytime soon.

Finally: I can confirm that the bug remains present in yesterday's upload of 
kscreen 5.26.5.  And for completeness, I am including my patch for any 
interested.

Thanks,
-Steve

[BUG] 
https://bugs.kde.org/show_bug.cgi?id=460341

[BUG2]
https://bugs.kde.org/show_bug.cgi?id=460341#c96

[DEBIAN] 
https://lists.debian.org/debian-devel/2022/10/msg00271.html
https://lists.debian.org/debian-kde/2022/10/msg00042.html
diff -u -r kscreen-5.26.5/debian/changelog kscreen-5.26.5-patched/debian/changelog
--- kscreen-5.26.5/debian/changelog	2023-01-06 17:21:57.000000000 -0600
+++ kscreen-5.26.5-patched/debian/changelog	2023-01-08 12:56:25.174429263 -0600
@@ -1,3 +1,10 @@
+kscreen (4:5.26.5-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Force enable of each connected screen.
+
+ -- Steve M. Robbins <smr@debian.org>  Sun, 08 Jan 2023 12:55:41 -0600
+
 kscreen (4:5.26.5-1) unstable; urgency=medium
 
diff -u -r kscreen-5.26.5/kded/daemon.cpp kscreen-5.26.5-patched/kded/daemon.cpp
--- kscreen-5.26.5/kded/daemon.cpp	2023-01-03 12:05:59.000000000 -0600
+++ kscreen-5.26.5-patched/kded/daemon.cpp	2023-01-08 12:59:11.546967586 -0600
@@ -353,6 +353,8 @@
     bool changed = false;
     const auto outputs = m_monitoredConfig->data()->outputs();
     for (const KScreen::OutputPtr &output : outputs) {
+        if (output->isConnected())
+            output->setEnabled(true);
         if (output->isConnected() && output->isEnabled()
             && (output->currentMode().isNull() || (output->followPreferredMode() && output->currentModeId() != output->preferredModeId()))) {
             qCDebug(KSCREEN_KDED) << "Current mode was" << output->currentModeId() << ", setting preferred mode" << output->preferredModeId();

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: