• Re: Is 5.27 expected before freeze?

    From Martin Steigerwald@21:1/5 to All on Sun Jan 8 23:10:01 2023
    Steven Robbins - 08.01.23, 22:32:00 CET:
    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.

    Review my post "Thank for your the ambitious plan for Bookworm" or go
    directly to:

    https://wiki.debian.org/PkgQtKde/BookwormReleasePlans

    --
    Martin

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Steven Robbins@21:1/5 to All on Sun Jan 8 15:32:00 2023
    This is a multi-part message in MIME format.

    --nextPart10206612.nUPlyArG6x
    Content-Transfer-Encoding: 7Bit
    Content-Type: text/plain; charset="us-ascii"

    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

    --nextPart10206612.nUPlyArG6x
    Content-Disposition: attachment; filename="patch"
    Content-Transfer-Encoding: 7Bit
    Content-Type: text/x-patch; charset="unicode-2-0-utf-8"; name="patch"

    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() || (o
  • From =?UTF-8?Q?Lisandro_Dami=C3=A1n_Nica@21:1/5 to Steven Robbins on Sun Jan 22 20:30:01 2023
    Hi,

    On Sun, 8 Jan 2023 at 18:39, Steven Robbins <steve@sumost.ca> wrote:

    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.

    Indeed, see https://bugs.kde.org/show_bug.cgi?id=450068

    My
    understanding is that this will be in the 5.27 release.

    Exactly. But considering the type of change it wouldn't be strange if
    after that something else needs to be changed too. But a much needed
    fix non the less.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)