Bug#822061: kalarm: KF5 version requires plasma-workspace to work properly

2022-11-03 Thread David Jarvie
This bug is no longer applicable. KAlarm no longer uses ktimezoned with Qt5 because it now uses QTimeZone. -- David Jarvie. KDE developer, KAlarm author.

Re: Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries

2022-11-03 Thread Soren Stoutner
On Friday, October 28, 2022 4:09:45 AM MST Agustin Martin wrote: > I am not particularly happy about this (see details below), but seems > we will have to package all these .bdic files because qtwebengine and > chromium use them. Since some .bdic may fail to build I would rather > prefer them to

Bug#954781: libqt5core5a: QT will not use Wayland on Gnome

2022-11-03 Thread Carlos Henrique Lima Melara
On Thu, Nov 03, 2022 at 06:02:03PM +0300, Dmitry Shachnev wrote: > > 3. The only problem is that qtwayland5 wayland platform plugin is not > > installed by default in a clean install of debian so applications fail > > to run wayland natively (fallback to xcb). > > > > I think we would need the

Bug#954781: libqt5core5a: QT will not use Wayland on Gnome

2022-11-03 Thread Renato Gallo
I think it should be more than a recommendation On Thu, Nov 3, 2022 at 4:06 PM Dmitry Shachnev wrote: > Hi Carlos! > > On Mon, Oct 31, 2022 at 06:55:49PM -0300, Carlos Henrique Lima Melara > wrote: > > Took a little while, sorry. Last week was pretty busy. I managed to try > > it today. I will

Bug#954781: libqt5core5a: QT will not use Wayland on Gnome

2022-11-03 Thread Dmitry Shachnev
Hi Carlos! On Mon, Oct 31, 2022 at 06:55:49PM -0300, Carlos Henrique Lima Melara wrote: > Took a little while, sorry. Last week was pretty busy. I managed to try > it today. I will attach the terminal output in the end. So my feedback > is below. > > 1. I wasn't able to reproduce the misplaced

Bug#1023408: kwin-wayland: black screen on tty1 after resume from hibernation instead of wayland logon screen

2022-11-03 Thread Dietmar Czekay
Package: kwin-wayland Version: 4:5.26.0-1 Severity: important Dear Maintainer, after sending the laptop to hibernation, the restart did not work. I see the boot message and end up in a black screen. Every terminal (Ctrl+Alt+2 for instance) works. terminal 7 shows a movable cursor. But terminal 1

qt6-tools_6.4.0-2_source.changes ACCEPTED into experimental

2022-11-03 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 03 Nov 2022 13:21:20 +0100 Source: qt6-tools Architecture: source Version: 6.4.0-2 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Patrick Franz Closes: 1015625

Processing of qt6-tools_6.4.0-2_source.changes

2022-11-03 Thread Debian FTP Masters
qt6-tools_6.4.0-2_source.changes uploaded successfully to localhost along with the files: qt6-tools_6.4.0-2.dsc qt6-tools_6.4.0-2.debian.tar.xz qt6-tools_6.4.0-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#1018004: marked as done (qt6-tools: does not build and link with system litehtml)

2022-11-03 Thread Debian Bug Tracking System
Your message dated Thu, 03 Nov 2022 12:35:41 + with message-id and subject line Bug#1018004: fixed in qt6-tools 6.4.0-2 has caused the Debian Bug report #1018004, regarding qt6-tools: does not build and link with system litehtml to be marked as done. This means that you claim that the

Bug#1015625: marked as done (qt6-tools: ftbfs with LTO (link time optimization) enabled)

2022-11-03 Thread Debian Bug Tracking System
Your message dated Thu, 03 Nov 2022 12:35:41 + with message-id and subject line Bug#1015625: fixed in qt6-tools 6.4.0-2 has caused the Debian Bug report #1015625, regarding qt6-tools: ftbfs with LTO (link time optimization) enabled to be marked as done. This means that you claim that the

Bug#1022972: konsole: Konsole does not handle arrow keys correctly anymore

2022-11-03 Thread Jonas Schäfer
Followup-For: Bug #1022972 Package: konsole Version: 4:22.08.1-1 Dear Maintainer, I can confirm the pinentry and konsole issue, but I'll focus on konsole, even though I suspect they may share a root cause. I found that konsole behaves correctly if I switch my keyboard layout to de nodeadkeys