Bug#989293: unblock: breeze/4:5.20.5-4

2021-05-31 Thread Norbert Preining
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: debian-qt-kde@lists.debian.org

Please unblock package breeze

[ Reason ]

The fix that was included in -3 introduced a different problem that was
recently fixed by upstream and pushed to stable branches.
KDE bug: 436473

The problem is that under certain circumstances the mouse cursor could
get stuck in form of resize icon.

Upstream comments are in the attached patch, I only include the
important paragraph here
> This was broken by accident in d201a1f187 ("Fix SplitterProxy not clearing
> when above another QSplitterHandle"), which moved the hide() call past the
> call to QCoreApplication::sendEvent. Previously that made isVisible() false,
> which also prevented the interception of the HoverLeave/HoverMove events.

[ Impact ]
If the bug remains unfixed, the mouse cursor might remain stuck in
resize form without a way to revert it.

[ Tests ]
Manual test trying to trigger the bug.

[ Risks ]
The code has been approved by upstream and included in 5.18 LTS and 5.20.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing


I attach only the patch that is added, the remaining changes are:
debian/changelog entry:
breeze (4:5.20.5-4) unstable; urgency=medium

  [ Norbert Preining ]
  * Upstream fix for cursor stuck in resize icon.

 -- Norbert Preining   Sun, 30 May 2021 05:58:28 +0900

and adding the patch to debian/patches/series.


unblock breeze/4:5.20.5-4
>From f99b7ef621c9c69544158d245699fd8104db6753 Mon Sep 17 00:00:00 2001
From: Fabian Vogt 
Date: Sat, 15 May 2021 17:45:54 +0200
Subject: [PATCH] Fix informing the underlying widget when leaving
 SplitterProxy

While the SplitterProxy is active, it intercepts all relevant events, so that
the underlying widget still thinks it's in the same "on splitter" state. When
the SplitterProxy is left, the underlying widget is sent a HoverLeave/HoverMove
event to make it aware of the new current cursor position. Without this, it
doesn't know that it's not supposed to be in the "on splitter" state, and when
it regains focus it just re-activates the SplitterProxy at the current cursor
position.

This was broken by accident in d201a1f187 ("Fix SplitterProxy not clearing
when above another QSplitterHandle"), which moved the hide() call past the
call to QCoreApplication::sendEvent. Previously that made isVisible() false,
which also prevented the interception of the HoverLeave/HoverMove events.

BUG: 436473
---
 kstyle/breezesplitterproxy.cpp | 11 +++
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/kstyle/breezesplitterproxy.cpp b/kstyle/breezesplitterproxy.cpp
index 0cf5685f..d4db407b 100644
--- a/kstyle/breezesplitterproxy.cpp
+++ b/kstyle/breezesplitterproxy.cpp
@@ -341,11 +341,14 @@ namespace Breeze
 // send hover event
 if( _splitter )
 {
-QHoverEvent hoverEvent(
-qobject_cast(_splitter.data()) ? 
QEvent::HoverLeave : QEvent::HoverMove,
-_splitter.data()->mapFromGlobal(QCursor::pos()), _hook);
-QCoreApplication::sendEvent( _splitter.data(), &hoverEvent );
+// SplitterProxy intercepts HoverLeave/HoverMove events to 
_splitter,
+// but this is meant to reach it directly. Unset _splitter to stop 
interception.
+auto splitter = _splitter;
 _splitter.clear();
+QHoverEvent hoverEvent(
+qobject_cast(splitter.data()) ? 
QEvent::HoverLeave : QEvent::HoverMove,
+splitter.data()->mapFromGlobal(QCursor::pos()), _hook);
+QCoreApplication::sendEvent( splitter.data(), &hoverEvent );
 }
 
 // kill timer if any
-- 
GitLab



Bug#987430: upgrade-reports: KDE Plasma without panels and without background after upgrade from Buster to Bullseye

2021-05-31 Thread Malvin Gattinger

Hi Norbert,


Does the script also contain the part of the re-installation?


Unfortunately no, the script only contains the upgrade to 
bullseye, but after that I rebooted and did not record the 
reinstall.



All that is really difficult to debug, though ...


Indeed. I now also installed a new virtual machine with buster, 
then tried to somewhat mimic which packages I have installed, and 
upgraded to bullseye. No problems this time, KDE worked fine.


So if nobody besides me reports this, maybe this bug should just 
be closed?


best,
Malvin



Bug#922213: plasma-desktop: KDE/Plasma creates invalid locale // Re: locales-all: Doesn't provide en_DE.UTF-8

2021-05-31 Thread Lisandro Damián Nicanor Pérez Meyer
Hi Steffen!

On Fri, 28 May 2021 at 03:15, Steffen Kaiser  wrote:
>
> Package: plasma-desktop
> Version: 4:5.20.5-4
> Followup-For: Bug #922213
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
>
> I'm using en_US.UTF-8 as interface language, but set Regional Settings |
> Formats to German.
>
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
>
> cat .config/plasma-localerc
> [Formats]
> LANG=en_DE.UTF-8

I don't seem able to set up this. Can you please provide me a way to
reproduce this bug?



Processing of layer-shell-qt_5.21.90-1_amd64.changes

2021-05-31 Thread Debian FTP Masters
layer-shell-qt_5.21.90-1_amd64.changes uploaded successfully to localhost
along with the files:
  layer-shell-qt_5.21.90-1.dsc
  layer-shell-qt_5.21.90.orig.tar.xz
  layer-shell-qt_5.21.90.orig.tar.xz.asc
  layer-shell-qt_5.21.90-1.debian.tar.xz
  layer-shell-qt-dbgsym_5.21.90-1_amd64.deb
  layer-shell-qt_5.21.90-1_amd64.buildinfo
  layer-shell-qt_5.21.90-1_amd64.deb
  liblayershellqtinterface-dev_5.21.90-1_amd64.deb
  liblayershellqtinterface5-dbgsym_5.21.90-1_amd64.deb
  liblayershellqtinterface5_5.21.90-1_amd64.deb

Greetings,

Your Debian queue daemon (running on host usper.debian.org)



layer-shell-qt_5.21.90-1_amd64.changes is NEW

2021-05-31 Thread Debian FTP Masters
binary:layer-shell-qt is NEW.
binary:liblayershellqtinterface-dev is NEW.
binary:liblayershellqtinterface5 is NEW.
binary:layer-shell-qt is NEW.
binary:liblayershellqtinterface-dev is NEW.
binary:liblayershellqtinterface5 is NEW.
source:layer-shell-qt is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports



Processing of ksystemstats_5.21.90-1_amd64.changes

2021-05-31 Thread Debian FTP Masters
ksystemstats_5.21.90-1_amd64.changes uploaded successfully to localhost
along with the files:
  ksystemstats_5.21.90-1.dsc
  ksystemstats_5.21.90.orig.tar.xz
  ksystemstats_5.21.90.orig.tar.xz.asc
  ksystemstats_5.21.90-1.debian.tar.xz
  ksystemstats-dbgsym_5.21.90-1_amd64.deb
  ksystemstats_5.21.90-1_amd64.buildinfo
  ksystemstats_5.21.90-1_amd64.deb

Greetings,

Your Debian queue daemon (running on host usper.debian.org)



ksystemstats_5.21.90-1_amd64.changes is NEW

2021-05-31 Thread Debian FTP Masters
binary:ksystemstats is NEW.
binary:ksystemstats is NEW.
source:ksystemstats is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports



Processed: BTS housekeeping and severity adjustments

2021-05-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 981054 2.0.25-2.1
Bug #981054 [openipmi] openipmi: Missing dependency on kmod
Marked as found in versions openipmi/2.0.25-2.1.
> severity 981054 serious
Bug #981054 [openipmi] openipmi: Missing dependency on kmod
Severity set to 'serious' from 'normal'
> severity 980466 serious
Bug #980466 [cervisia] cervisia: missing dependency on kinit package
Severity set to 'serious' from 'normal'
> severity 980171 serious
Bug #980171 [libobs-dev] libobs-dev: missing dependency on libsmde-dev
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
980171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980171
980466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980466
981054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems