Bug#1074155: src:ktextaddons: fails to migrate to testing for too long: FTBFS

[Paul Gevers]

Source: ktextaddons
Version: 1.5.2-2.1
Severity: serious
Control: close -1 1.5.4-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1073394

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:ktextaddons has been trying to migrate for 
31 days [2]. Hence, I am filing this bug. The version in unstable fails 
to build from source as reported in bug 1073394.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=ktextaddons



OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: Bug#1057755: Qt WebEngine Security Support In Stable

[Paul Gevers]

Hi Soren,

On 14-12-2023 08:45, Soren Stoutner wrote:

How do you recommend we change that?


I think you're having the right discussion. I'm not a Stable Release 
Manager so I don't feel authoritative about stable. However, in my 
*personal* opinion and reflected in a proposal [1] I'm driving (about 
changes during the freeze, so targeting unstable and testing), we could 
be accepting more new upstream release *if* upstream release processes 
and criteria align with our stability criteria. In nearly all cases I 
expect that to mean a stable branch with strict documented rules and QA 
processes to guard quality.


Paul

[1] 
https://salsa.debian.org/elbrus/memos/-/blob/main/vetted-upstream-stable-versions.md


OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: Bug#1057755: Qt WebEngine Security Support In Stable

[Paul Gevers]

Hi Soren,

On 14-12-2023 04:49, Soren Stoutner wrote:

Currently there is no real security support for Qt WebEngine in stable, which
is an oversight that might surprise many Debian users.


It's explicitly documented in the release notes: 
https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#limited-security-support 
so I wouldn't call it an oversight.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1057662: src:k3b: fails to migrate to testing for too long: new Build-Depends not available everywhere

[Paul Gevers]

Source: k3b
Version: 22.12.3-1
Severity: serious
Control: close -1 23.08.2-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:k3b has been trying to migrate for 31 days 
[2]. Hence, I am filing this bug. The version in unstable has a new 
Build-Depends that's not available on armel, ppc64el and s390x. Please 
help the maintainer of qtwebengine5-dev to get that package available on 
those architectures, drop the Build-Depends or request the removal of 
your package on those architectures.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=k3b


OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: Bug#1036867: unblock: qt6-base/6.4.2+dfsg-10

[Paul Gevers]

Hi,

On 28-05-2023 10:58, Patrick Franz wrote:

unblock qt6-base/6.4.2+dfsg-10


Unblocked, thanks.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1032674: /usr/bin/plasmashell: when killing a window via the grouped task bar, the task bar disappears

[Paul Gevers]

Package: plasma-workspace
Version: 4:5.27.0-1
Severity: normal
File: /usr/bin/plasmashell

Dear maintainers,

Thank you for maintaining KDE in Debian, it must be a hell of a job. I
want to share the following annoyance which is probably due to a crash
and auto restart (so an annoyance, but probably it really should be
fixed). When I have multiple windows of the same program (qgit in my
case) I have their entries grouped in the task bar. If I hover over
their entry in the task bar, multiple minified windows appear with a
close button. When I press the close button of the minified window I
want to close, the task bar dissapears for several seconds. When the
bar returns I can see that `plasmashell` got started in the same
minute as the disappearance.

I traced it a bit with the one-liner below. `plasmashell` actually
seems to stay running until the task bar reappears, at which moment
the start time and ID get bumped. So maybe the problem lies elsewhere,
please tell me if you need more from me trace back the culprit.

Paul

paul@mulciber ~ $ while true ; do ps aux | grep /usr/bin/plasmashell | grep -v 
grep ; echo . ; sleep 1 ; done
paul  220257  1.4  8.3 3211068 309192 ?  Rsl  20:47   0:10 
/usr/bin/plasmashell --no-respawn
.
paul  220257  1.4  8.6 3211068 319060 ?  Ssl  20:47   0:10 
/usr/bin/plasmashell --no-respawn
.
paul  220257  1.4  8.2 3211068 305960 ?  Ssl  20:47   0:10 
/usr/bin/plasmashell --no-respawn
.
paul  220257  1.4  7.5 3211068 279624 ?  Ssl  20:47   0:10 
/usr/bin/plasmashell --no-respawn
.
paul  220257  1.4  7.4 3211068 275072 ?  Ssl  20:47   0:10 
/usr/bin/plasmashell --no-respawn
.
paul  220858 54.0  1.7 378372 64852 ?Rsl  20:59   0:00 
/usr/bin/plasmashell --no-respawn
.
paul  220858 42.2  3.5 1234588 130732 ?  Dsl  20:59   0:00 
/usr/bin/plasmashell --no-respawn
.
paul  220858 43.6  4.6 1505996 173336 ?  Rsl  20:59   0:01 
/usr/bin/plasmashell --no-respawn
.
paul  220858 48.8  5.3 2043572 198924 ?  Rsl  20:59   0:01 
/usr/bin/plasmashell --no-respawn
.
paul  220858 43.4  5.7 2060256 214048 ?  Ssl  20:59   0:01 
/usr/bin/plasmashell --no-respawn


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-workspace depends on:
ii  dbus-user-session [default-dbus-session-bus]1.14.6-1
ii  dbus-x11 [dbus-session-bus] 1.14.6-1
ii  drkonqi 5.26.90-1
ii  frameworkintegration5.103.0-1
ii  gdb-minimal [gdb]   13.1-2
ii  init-system-helpers 1.65.2
ii  iso-codes   4.13.0-1
ii  kactivitymanagerd   5.26.90-1
ii  kded5   5.103.0-1
ii  kinit   5.103.0-1
ii  kio 5.103.0-1
ii  kpackagetool5   5.103.0-1
ii  kwin-common 4:5.26.90-1
ii  libappstreamqt2 0.16.1-1
ii  libc6   2.36-8
ii  libcolorcorrect54:5.27.0-1
ii  libcrypt1   1:4.4.33-2
ii  libfontconfig1  2.14.1-4
ii  libfreetype62.12.1+dfsg-4
ii  libgcc-s1   12.2.0-14
ii  libgps283.22-4.1+b1
ii  libice6 2:1.0.10-1
ii  libicu7272.1-3
ii  libkf5activities5   5.103.0-1
ii  libkf5activitiesstats1  5.103.0-1
ii  libkf5archive5  5.103.0-1
ii  libkf5authcore5 5.103.0-1
ii  libkf5baloo55.103.0-2
ii  libkf5bookmarks55.103.0-1
ii  libkf5calendarevents5   5.103.0-1
ii  libkf5completion5   5.103.0-1
ii  libkf5config-bin5.103.0-1
ii  libkf5configcore5   5.103.0-1
ii  libkf5configgui55.103.0-1
ii  libkf5configwidgets55.103.0-1
ii  libkf5coreaddons5   5.103.0-1
ii  

Bug#1017613: kwin-x11 session stops working (semi-freeze) every few days

[Paul Gevers]

Hi,

On Thu, 18 Aug 2022 08:47:45 -0400 Ralf Jung  wrote:

Also see https://bugs.kde.org/show_bug.cgi?id=457847.


That bug was determined to be caused by 
https://gitlab.freedesktop.org/mesa/mesa/-/issues/7674.  I *think* (but 
haven't confirmed yet as that doesn't seem trivial to do) that that bug 
should be fixed in mesa 22.3 which is in bookworm since 2023-01-02 (and 
in unstable since 2022-12-01). So if this bug reoccurs for somebody, it 
would be good to update the bug report.


I had the same issue as in this report and decided today to investigate. 
However, my system updated mesa yesterday, so if my searching is true, 
the bug should be gone for me.


I think this bug (and maybe similar bugs) should be reassigned to mesa, 
raised in severity and closed... (or just the latter).


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013550: sddm: FTBFS: XorgDisplayServer.cpp:68:42: error: use of deleted function ‘QCharRef& QCharRef::operator=(char)’

[Paul Gevers]

Dear Pino,

On Fri, 24 Jun 2022 12:04:19 +0200 Lucas Nussbaum  wrote:

During a rebuild of all packages in sid, your package failed to build
on amd64.


This bug has been marked pending for 2.5 months now. Can you please upload?

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1020307: src:qtfeedback-opensource-src: fails to migrate to testing for too long: uploader built arch:all binaries

[Paul Gevers]

Source: qtfeedback-opensource-src
Version: 5.0~git20180903.a14bd0b-3
Severity: serious
Control: close -1 5.0~git20180903.a14bd0b-4
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:qtfeedback-opensource-src has been trying 
to migrate for 61 days [2]. Hence, I am filing this bug.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=qtfeedback-opensource-src



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1012535: cantor: fails to build from source

[Paul Gevers]

Source: cantor
Version: 4:21.12.3-1
Severity: serious
Tags: ftbfs
Justification: ftbfs

Hi,

As part of the pseudo libluajit transition [1] I scheduled a rebuild
of cantor. It failed to build everywhere [2]. As can be seen on the
reproducible build project page, the build already fails in bookworm,
so not related to the libluajit changes in unstable.

Paul

[1] https://release.debian.org/transitions/html/libluajit2-support.html
[2] https://buildd.debian.org/status/package.php?p=cantor
[3] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cantor.html

qt6-declarative fails to build on s390x

[Paul Gevers]

Hi all,

Today I stumbled upon some packages that failed to migrate to testing 
because they switched their build dependency to qt6-declarative. It 
seems to me that this package is relatively new and a replacement for 
something we already had for a while. Apparently that built on s390x, so 
this failure feels like a regression.


Can somebody maybe look at why qt6-declarative fails on s390x and fix it?

Paul

https://buildd.debian.org/status/fetch.php?pkg=qt6-declarative=s390x=6.2.2%2Bdfsg-4=1644966259=0

-- Build files have been written to: /<>/obj-s390x-linux-gnu
make[1]: Leaving directory '/<>'
   dh_auto_build -a -O--buildsystem=cmake\+ninja
cd obj-s390x-linux-gnu && LC_ALL=C.UTF-8 ninja -j2 -v
[1/2549] cd /<>/obj-s390x-linux-gnu/src/qmltyperegistrar && 
/usr/bin/cmake -E cmake_autogen 
/<>/obj-s390x-linux-gnu/src/qmltyperegistrar/CMakeFiles/qmltyperegistrar_autogen.dir/AutogenInfo.json 
None && /usr/bin/cmake -E touch 
/<>/obj-s390x-linux-gnu/src/qmltyperegistrar/qmltyperegistrar_autogen/timestamp 
&& /usr/bin/cmake -E cmake_transform_depfile Ninja gccdepfile 
/<> /<>/src/qmltyperegistrar 
/<>/obj-s390x-linux-gnu 
/<>/obj-s390x-linux-gnu/src/qmltyperegistrar 
/<>/obj-s390x-linux-gnu/src/qmltyperegistrar/qmltyperegistrar_autogen/deps 
/<>/obj-s390x-linux-gnu/CMakeFiles/d/43adb0291f7798469ad331ae4b3d28658a39659d3080b682c231b04dadff33f0.d
[2/2549] /usr/bin/c++ -DQT_CORE_LIB -DQT_NO_CAST_FROM_ASCII 
-DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_EXCEPTIONS 
-DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_USE_QSTRINGBUILDER 
-D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE 
-I/<>/obj-s390x-linux-gnu/src/qmltyperegistrar/qmltyperegistrar_autogen/include 
-I/<>/src/qmltyperegistrar 
-I/<>/obj-s390x-linux-gnu/src/qmltyperegistrar 
-I/<>/src/qmltyperegistrar/../qmlcompiler -isystem 
/usr/include/s390x-linux-gnu/qt6/QtCore -isystem 
/usr/include/s390x-linux-gnu/qt6 -isystem 
/usr/lib/s390x-linux-gnu/qt6/mkspecs/linux-g++ -isystem 
/usr/include/s390x-linux-gnu/qt6/QtCore/6.2.2 -isystem 
/usr/include/s390x-linux-gnu/qt6/QtCore/6.2.2/QtCore -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE 
-fvisibility=hidden -fvisibility-inlines-hidden -Wall -Wextra 
-fno-exceptions -pthread -Wsuggest-override -MD -MT 
src/qmltyperegistrar/CMakeFiles/qmltyperegistrar.dir/qmltyperegistrar_autogen/mocs_compilation.cpp.o 
-MF 
src/qmltyperegistrar/CMakeFiles/qmltyperegistrar.dir/qmltyperegistrar_autogen/mocs_compilation.cpp.o.d 
-o 
src/qmltyperegistrar/CMakeFiles/qmltyperegistrar.dir/qmltyperegistrar_autogen/mocs_compilation.cpp.o 
-c 
/<>/obj-s390x-linux-gnu/src/qmltyperegistrar/qmltyperegistrar_autogen/mocs_compilation.cpp
[3/2549] cd /<>/obj-s390x-linux-gnu/src/qml && 
/usr/lib/qt6/libexec/qlalr --no-debug --qt 
/<>/src/qml/parser/qqmljs.g
[4/2549] /usr/bin/c++ -DQT_CORE_LIB -DQT_NO_CAST_FROM_ASCII 
-DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_EXCEPTIONS 
-DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_USE_QSTRINGBUILDER 
-D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE 
-I/<>/obj-s390x-linux-gnu/src/qmltyperegistrar/qmltyperegistrar_autogen/include 
-I/<>/src/qmltyperegistrar 
-I/<>/obj-s390x-linux-gnu/src/qmltyperegistrar 
-I/<>/src/qmltyperegistrar/../qmlcompiler -isystem 
/usr/include/s390x-linux-gnu/qt6/QtCore -isystem 
/usr/include/s390x-linux-gnu/qt6 -isystem 
/usr/lib/s390x-linux-gnu/qt6/mkspecs/linux-g++ -isystem 
/usr/include/s390x-linux-gnu/qt6/QtCore/6.2.2 -isystem 
/usr/include/s390x-linux-gnu/qt6/QtCore/6.2.2/QtCore -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE 
-fvisibility=hidden -fvisibility-inlines-hidden -Wall -Wextra 
-fno-exceptions -pthread -Wsuggest-override -MD -MT 
src/qmltyperegistrar/CMakeFiles/qmltyperegistrar.dir/__/qmlcompiler/qqmljsstreamwriter.cpp.o 
-MF 
src/qmltyperegistrar/CMakeFiles/qmltyperegistrar.dir/__/qmlcompiler/qqmljsstreamwriter.cpp.o.d 
-o 
src/qmltyperegistrar/CMakeFiles/qmltyperegistrar.dir/__/qmlcompiler/qqmljsstreamwriter.cpp.o 
-c /<>/src/qmlcompiler/qqmljsstreamwriter.cpp
[5/2549] /usr/bin/c++ -DQT_CORE_LIB -DQT_NO_CAST_FROM_ASCII 
-DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_EXCEPTIONS 
-DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_USE_QSTRINGBUILDER 
-D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE 
-I/<>/obj-s390x-linux-gnu/src/qmltyperegistrar/qmltyperegistrar_autogen/include 
-I/<>/src/qmltyperegistrar 
-I/<>/obj-s390x-linux-gnu/src/qmltyperegistrar 
-I/<>/src/qmltyperegistrar/../qmlcompiler -isystem 
/usr/include/s390x-linux-gnu/qt6/QtCore -isystem 
/usr/include/s390x-linux-gnu/qt6 -isystem 
/usr/lib/s390x-linux-gnu/qt6/mkspecs/linux-g++ -isystem 
/usr/include/s390x-linux-gnu/qt6/QtCore/6.2.2 -isystem 
/usr/include/s390x-linux-gnu/qt6/QtCore/6.2.2/QtCore -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE 
-fvisibility=hidden -fvisibility-inlines-hidden 

Bug#999451: kwin-x11: drawing windows is delayed making reading and typing tedious

[Paul Gevers]

Hi Diederik,

On 11-11-2021 12:31, Diederik de Haas wrote:
> And it's not enabled with me too and I also have no recollection of disabling 
> it. But the attached screenshot gives a (pretty good) hint as to why it got 
> disabled: (apparent) previous KWin crashes.

Nice screenshot. For the record, that hint wasn't there on my system.
The other settings are the same, minus I have "OpenGL 2.0" as "Rendering
backend".

Paul

PS
lshw says this about my display
 description: VGA compatible controller
 product: CometLake-U GT2 [UHD Graphics]
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 logical name: /dev/fb0
 version: 02
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm vga_controller bus_master
cap_list fb
 configuration: depth=32 driver=i915 latency=0
mode=1920x1080 resolution=1920,1080 visual=truecolor xres=1920 yres=1080
 resources: iomemory:600-5ff iomemory:400-3ff irq:148
memory:602200-6022ff memory:40-400fff
ioport:4000(size=64) memory:c-d



OpenPGP_signature
Description: OpenPGP digital signature

Bug#999451: kwin-x11: drawing windows is delayed making reading and typing tedious

[Paul Gevers]

Hi Norbert,

On 11-11-2021 09:58, Norbert Preining wrote:
> Can you check whether
>   Start compositor on startup
> is selected in the Plasma settings?

It was disabled. Immediately after enabling it, the issues seem to be gone.

I don't believe I ever changed the setting, so it got into this state
somehow without me being involved I think.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#999451: kwin-x11: drawing windows is delayed making reading and typing tedious

[Paul Gevers]

Package: kwin-x11
Version: 4:5.23.2-1
Severity: important

Dear maintainers,

First off, thanks for maintaining KDE in Debian, I enjoy using it.

Since a recent upgrade (after the issues we had with only half (or
less) of the stack migrating to testing) I'm experiencing issues with
drawing of windows. The issue is that it seems that windows
(e.g. konsole) are only drawn after some delay or after switching back
and forth to another window. Especially the cursor position is often
at a different place that it shows, making typing mistakes very
difficult to correct. Also e.g. scrolling through messages in
Thunderbird is difficult, as the window is only properly refreshed
after I stop scrolling, until then the window is messed up. I tried to
make a screen shot of the situation, but it seems that also the
screenshot tool (Spectacle) ensures that the window is properly
refresh the moment it takes the screenshot. The issue is less of a
problem in Emacs, as that seems to force the refresh by itself much
more often (although I do see glitches with the cursor jumping).

I'm aware that the issue may not be with kwin, but it's the package I
thought of first, please reassign if you think the issue is more
likely to be elsewhere. Also please let me know if I can provide you
with more information to help solve the issue.

My system is an up-to-date testing environment. I delayed reporting
this issue in the hope that it was caused by other to-be-migrated
packages from unstable, but the issue is annoying me now for more than
a week (I estimate) and I have no clue which package from unstable I
should be looking out for.

Paul


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kwin-x11 depends on:
ii  kwin-common   4:5.23.2-1
ii  libc6 2.32-4
ii  libepoxy0 1.5.9-2
ii  libgcc-s1 11.2.0-10
ii  libkf5configcore5 5.86.0-1
ii  libkf5coreaddons5 5.86.0-1
ii  libkf5crash5  5.86.0-1
ii  libkf5i18n5   5.86.0-1
ii  libkf5quickaddons55.86.0-1
ii  libkf5windowsystem5   5.86.0-1
ii  libkwaylandserver5 [libkwaylandserver5-5.23]  5.23.2-1
ii  libkwineffects13  4:5.23.2-1
ii  libkwinglutils13  4:5.23.2-1
ii  libkwinxrenderutils13 4:5.23.2-1
ii  libqt5core5a  5.15.2+dfsg-12
ii  libqt5dbus5   5.15.2+dfsg-12
ii  libqt5gui55.15.2+dfsg-12
ii  libqt5widgets55.15.2+dfsg-12
ii  libqt5x11extras5  5.15.2-2
ii  libstdc++611.2.0-10
ii  libx11-6  2:1.7.2-2+b1
ii  libxcb-composite0 1.14-3
ii  libxcb-keysyms1   0.4.0-1+b2
ii  libxcb-randr0 1.14-3
ii  libxcb-render01.14-3
ii  libxcb-shape0 1.14-3
ii  libxcb-xfixes01.14-3
ii  libxcb1   1.14-3
ii  libxi62:1.8-1

kwin-x11 recommends no packages.

kwin-x11 suggests no packages.

-- no debconf information

Re: Bug#996767: upgrade-reports: KDE unstartable

[Paul Gevers]

Control: reassign 996767 kde-standard

Hi Hype,

Thanks for your report about the issues you encounter.

On 18-10-2021 13:16, Hype_the_Time wrote:
> Language maybe used my output of the shell: German
> This bug report is a day old but a new apt upgrade didnt fixed it

Interesting you choose to file this bug against upgrade-reports. Am I
correct you did so because you upgraded from bullseye to testing?

> When i try logging in in any KDE type(X11 or Wayland) it isn't working it lets
> me select and login but fails and sends me back to login Screen every else
> works. I AM NOT 100% sure its not only my PC cause i changed some less
> important hardware but didn't worked when i tried changing it again either. 
> Was
> updated to date before the restart.
> 
> I saw the day after that i actaully was able to start things via Alt + F2
> anyhow but i do not know why. Things like the Key shortcuts and other Stuff
> like the bottom left which opens when pressing the windows key do noz work for
> example too.

It seems your problem is related to KDE, hence I reassign to the
kde-standard package in the hope the maintainers there can help you further.

> After definition its important would have
> choiced less important otherwise.
> 
> My previous release is: 
> Upgraded too: Newest Packages ( apt get update + upgrade 4 hours ago)
> Archive date:   on your mirror or .disk/info on your CD/DVD set>
> Upgrade date: <17.10.2021 at about 16-17 a clock german time >
> uname -a before upgrade: 
> uname -a after upgrade:  (2021-10-03) x86_64 GNU/Linux
>>
> Method: 
> 
> Contents of /etc/apt/sources.list:
> 
> only not #
> deb http://deb.debian.org/debian/ bookworm main contrib non-free
> 
> 
> - Were there any non-Debian packages installed before the upgrade?  If
>   so, what were they?
> 
> There was no software installed or removed on the same since the previos 
> update
> where everything worked
> 
> - Was the system pre-update a pure sarge system? If not, which packages
>   were not from sarge?
> 
> I do not know/ understand what is meant

Understandably, the question is supposed to have said "oldstable" or
"buster".

> - Did any packages fail to upgrade?
> 
> Nothing seen in terminal
> 
> - Were there any problems with the system after upgrading?
> 
> Well as described up
> 
> Further Comments/Problems:
> 
> Nothing more to add
> 
> Please attach the output of "COLUMNS=200 dpkg -l" (or "env COLUMNS ...",
> depending on your shell) from before and after the upgrade so that we
> know what packages were installed on your system.
> 
> well i dont have the thing from before either but current:
> 
>  Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
> | Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
>  Halb installiert/Trigger erWartet/Trigger anhängig
> |/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
> ||/ Name  Version

[...]

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#996732: src:kget: fails to migrate to testing for too long: build-depends not satisfiable

[Paul Gevers]

Source: kget
Version: 4:20.12.2-1
Severity: serious
Control: close -1 4:21.08.0-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:kget has been trying to migrate for 64
days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bookworm, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=kget




OpenPGP_signature
Description: OpenPGP digital signature

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

[Paul Gevers]

Control: reassign -1 plasma-workspace

@ Qt/KDE maintainers: slightly random chosen reassignment

Hi Malvin,

Thanks for your report. Unfortunately it fell through the cracks for
some time. I have reassigned you bug report to one of the packages you
reported you reinstalled, I hope the Qt/KDE maintainers are better able
to triage than I am.

Paul

On 23-04-2021 20:56, Malvin Gattinger wrote:
> Package: upgrade-reports
> Severity: important
> 
> My previous release is: buster (fully updated)
> I am upgrading to: bullseye
> Archive date: Fri Apr 23 14:17:55 UTC 2021
> Upgrade date: Fri Apr 23 16:00:00 UTC 2021
> uname -a before upgrade: Linux hostname 4.19.0-16-amd64 #1 SMP Debian
> 4.19.181-1 (2021-03-19) x86_64 GNU/Linux
> uname -a after upgrade: Linux hostname 5.10.0-6-amd64 #1 SMP Debian
> 5.10.28-1 (2021-04-09) x86_64 GNU/Linux
> Method: apt upgrade --without-new-pkgs && apt full-upgrade
> 
> I have now upgraded three different machines from (fully updated) Buster
> to Bullseye, and all three times KDE Plasma was not usable afterwards.
> 
> Symptoms:
> - No panels are shown and instead of the desktop/background the screen
> is black.
> - Right-click on the desktop works, but the settings do not allow me to
> set a background image.
> - Pressing the super key opens the launcher menu, next to where the
> panel should be shown.
> - Alt+Tab works, kwin is running normally
> - krunner was unusable on two of the machines, but worked on the third.
> 
> I think the same problems was described by a reddit user here:
> https://www.reddit.com/r/debian/comments/li4vvc/debian_bullseye_has_entered_softfreeze/gnbp9up/?context=3
> 
> 
> WORKAROUND:
> The problem goes away after reinstalling everything that is installed
> and has "plasma" in the name, but unfortunately I cannot say which of
> those package reinstalls is actually doing the trick:
> 
> sudo apt install --reinstall kdeplasma-addons-data libkf5plasma5:amd64
> libkf5plasmaquick5:amd64 libplasma-geolocation-interface5
> libreoffice-plasma plasma-dataengines-addons:amd64 plasma-desktop
> plasma-desktop-data plasma-disks plasma-framework plasma-integration
> plasma-nm plasma-pa plasma-runners-addons:amd64
> plasma-wallpapers-addons:amd64 plasma-widgets-addons plasma-workspace
> plasma-workspace-data
> 
> 
> After this and logging out and back in, all of KDE Plasma works as normal.
> 



OpenPGP_signature
Description: OpenPGP digital signature

Bug#980228: kservice: flaky autopkgtest

[Paul Gevers]

Source: kservice
Version: 5.70.0-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

kservice is a key package, which is why we noticed an autopkgtest
failures as part of our checks on the status of bullseye. I looked into
the history of your autopkgtest [1] and it fails regularly on nearly all
architectures. I copied some of the output at the bottom of this report
(but it's not always the same).

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Please do get in touch if we need to dive into this together. Or if you
want to discuss this issue.

Paul

https://ci.debian.net/packages/k/kservice/

https://ci.debian.net/data/autopkgtest/testing/amd64/k/kservice/9693624/log.gz

autopkgtest [21:20:54]: test testsuite: [---
Openbox-Message: Unable to find a valid menu file
"/var/lib/openbox/debian-menu.xml"
kbuildsycoca5 running...
cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=-j1
Running tests...
/usr/bin/ctest --force-new-ctest-process -j1
Test project
/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/obj-x86_64-linux-gnu
  Start  1: ksycocatest
 1/11 Test  #1: ksycocatest ..***Failed0.69 sec
* Start testing of KSycocaTest *
Config: Using QtTest library 5.15.2, Qt 5.15.2
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 10.2.1
20201207), debian unknown
QDEBUG : KSycocaTest::initTestCase() created
"/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/share/kservicetypes5/fakeGlobalServiceType.desktop"
PASS   : KSycocaTest::initTestCase()
QSYSTEM: KSycocaTest::ensureCacheValidShouldCreateDB()
"kf5-applications.menu"  not found in
("/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/config/menus")
PASS   : KSycocaTest::ensureCacheValidShouldCreateDB()
kbuildsycoca5 running...
"kf5-applications.menu"  not found in
("/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/config/menus")
QDEBUG : KSycocaTest::kBuildSycocaShouldEmitDatabaseChanged() waiting
for signal
QDEBUG : KSycocaTest::kBuildSycocaShouldEmitDatabaseChanged() got signal
QDEBUG : KSycocaTest::kBuildSycocaShouldEmitDatabaseChanged() created
"/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/share/kservicetypes5/fakeGlobalServiceType.desktop"
PASS   : KSycocaTest::kBuildSycocaShouldEmitDatabaseChanged()
QDEBUG : KSycocaTest::dirInFutureShouldRebuildSycocaOnce() Time changed
for
/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/share/kservicetypes5
QDEBUG : KSycocaTest::dirInFutureShouldRebuildSycocaOnce()
QDateTime(2021-01-14 21:21:00.812 UTC Qt::LocalTime)
QDateTime(2021-01-14 21:22:00.000 UTC Qt::LocalTime)
QSYSTEM: KSycocaTest::dirInFutureShouldRebuildSycocaOnce()
"kf5-applications.menu"  not found in
("/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/config/menus")
QDEBUG : KSycocaTest::dirInFutureShouldRebuildSycocaOnce() Time changed
back for
/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/share/kservicetypes5
QDEBUG : KSycocaTest::dirInFutureShouldRebuildSycocaOnce()
QDateTime(2021-01-14 21:21:00.838 UTC Qt::LocalTime)
QDateTime(2021-01-14 21:21:00.000 UTC Qt::LocalTime)
PASS   : KSycocaTest::dirInFutureShouldRebuildSycocaOnce()
QDEBUG : KSycocaTest::dirTimestampShouldBeCheckedRecursively() Time
changed for
/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/config/menus/fakeSubserviceDirectory
QDEBUG : KSycocaTest::dirTimestampShouldBeCheckedRecursively()
QDateTime(2021-01-14 21:21:00.838 UTC Qt::LocalTime)
QDateTime(2021-01-14 21:22:00.000 UTC Qt::LocalTime)
QDEBUG : KSycocaTest::dirTimestampShouldBeCheckedRecursively() Waited
1s, calling ensureCacheValid (should rebuild)
QSYSTEM: KSycocaTest::dirTimestampShouldBeCheckedRecursively()
"kf5-applications.menu"  not found in
("/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/config/menus")
QDEBUG : KSycocaTest::dirTimestampShouldBeCheckedRecursively() Waited
1s, calling ensureCacheValid (should not rebuild)
PASS   : KSycocaTest::dirTimestampShouldBeCheckedRecursively()
QDEBUG : KSycocaTest::recursiveCheckShouldIgnoreLinksGoingUp() Time
changed for
/tmp/autopkgtest-lxc.njuieowm/downtmp/build.9Mh/src/debian/.debhelper/generated/_source/home/.qttest/config
QDEBUG : KSycocaTest::recursiveCheckShouldIgnoreLinksGoingUp()
QDateTime(2021-01-14 

Bug#955567: kalgebra: Output is always blank

[Paul Gevers]

Control: tags -1 buster

Hi Charles,

On 28-12-2020 20:51, Charles Samuels wrote:
> On Monday, December 28, 2020 11:30:18 AM PST Paul Gevers wrote:
>> I tried to reproduce this in current testing and for me it works. Is
>> this issue still a problem for you?
> 
> Yes it is still an issue (stable).

I can then only assume it got fixed in the mean time (in
unstable/testing). Tagging this bug as appropriate, but leaving it open
for now just in case somebody wants to jump in.

> Curiously, when I right click on the output area, the popup menu with "Clear" 
> is positioned in relation to the desktop and not the place I clicked at (so 
> if 
> you click at coordinate 100x100 in the area, the popup appears at 100x100 
> global coordinates).
> 
> I use KDE's desktop scaling (1.5x). I tried disabling that and then 
> restarting 
> kalgebra (without logging out) with no change.
> 
> I see nothing interesting in .xsession-errors or kalgebra's output

I can't offer much help, as I'm not familiar with the KDE stack. I was
mostly interested from the release process point of view.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#955567: kalgebra: Output is always blank

[Paul Gevers]

Control: notfound -1 4:20.08.0-1

Hi Charles,

On Thu, 02 Apr 2020 16:57:16 + (UTC) Charles Samuels
 wrote:
> KAlgebra shows nothing in its output screen. This only applies
> to the algebraic displays, the graphs and dictionary tabs seem
> to work fine.
> 
> Reproduce: Enter any equation into the input text box and press enter.
> 
> Expected: The result of the equation and the equation inputted should be 
> visible.
> 
> Actual: Nothing appears. Even the border of the frame appears missing.
> 
> Also: Right clicking on the empty area causes a context menu to appear
> in the wrong place. I'm not sure if that's related.

I tried to reproduce this in current testing and for me it works. Is
this issue still a problem for you?

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#943462: [polkit-kde-agent-1] Fails to start with elogind

[Paul Gevers]

Hi all,

On Fri, 25 Oct 2019 07:04:40 +0500 Alex Volkov 
wrote:
> I'm using elogind 239.3+20190131-1+debian1 and the agent fails to start
> at the kde launch with the following diagnostics:

Any progress on this? The bullseye freeze is approaching.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#942078: [high quality bug] baloo crash, can't recover; forced reindex does not fix; unusable via dolphin C-f

[Paul Gevers]

Hi all,

On Wed, 09 Oct 2019 18:53:25 -0400 Nicholas D Steeves
 wrote:
> Recently baloo has been crashing whenever I log in.  Today I decided it
> was a persistent and serious enough problem that a serious bug was
> warranted.  I've attached the backtrace produced by drkonqi.  Here is
> some additional info that I hope will help quickly resolve this bug.

Any progress on this? The bullseye freeze is approaching. baloo-kf5 is a
key package so isn't autoremoved. Hence it's on the Release Team's radar.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#962172: baloo-kf5: autopkgtest regression: dh_acc: error: abi-compliance-checker

[Paul Gevers]

Source: baloo-kf5
Version: 5.70.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of baloo-kf5 the autopkgtest of baloo-kf5 fails in
testing when that autopkgtest is run with the binary packages of
baloo-kf5 from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
baloo-kf5  from testing5.70.0-1
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
baloo-kf5/5.70.0-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=baloo-kf5

https://ci.debian.net/data/autopkgtest/testing/amd64/b/baloo-kf5/5757117/log.gz

autopkgtest [23:08:43]: test acc: [---
cc1: warning: command line option ‘-std=c++11’ is valid for C++/ObjC++
but not for C
Can't "next" outside a loop block at /usr/bin/abi-compliance-checker
line 10171.
dh_acc: error: abi-compliance-checker -q -l baloo-kf5-dev -v1 5.70.0-1
-dump debian/baloo-kf5-dev.acc -dump-path
debian/baloo-kf5-dev/usr/lib/x86_64-linux-gnu/dh-acc/baloo-kf5-dev_5.70.0-1.abi.tar.gz
returned exit code 5
autopkgtest [23:08:51]: test acc: ---]



signature.asc
Description: OpenPGP digital signature

Bug#960714: libkeduvocdocument: autopkgtest failure: kdeinit5: not found

[Paul Gevers]

Source: libkeduvocdocument
Version: 4:17.08.3-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails. I copied some
of the output at the bottom of this report. Can you please investigate
the situation and fix it? You seem to be missing a test dependency.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1]
https://ci.debian.net/data/autopkgtest/testing/amd64/libk/libkeduvocdocument/5496019/log.gz

autopkgtest [18:12:57]: test testsuite: [---
debian/tests/testsuite.xsession: 4: kdeinit5: not found
dh_auto_test: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
debian/tests/testsuite.xsession: 1: kdeinit5_shutdown: not found
autopkgtest [18:12:58]: test testsuite: ---]



signature.asc
Description: OpenPGP digital signature

Bug#958351: plasma-mediacenter: autopkgtest needs update for new version of debhelper: failure on warning

[Paul Gevers]

Source: plasma-mediacenter
Version: 5.7.5-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, debhel...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:debhelper

Dear maintainer(s),

With a recent upload of debhelper the autopkgtest of plasma-mediacenter
fails in testing when that autopkgtest is run with the binary packages
of debhelper from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
debhelper  from testing13
plasma-mediacenter from testing5.7.5-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. You can
prevent failure on output to stderr by add the "allow-stderr"
restriction if you don't want such failures.

Currently this regression is blocking the migration of debhelper to
testing [1]. Of course, debhelper shouldn't just break your autopkgtest
(or even worse, your package), but it seems to me that the change in
debhelper was intended and your package needs to update to the new
situation.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from debhelper should really
add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=debhelper

https://ci.debian.net/data/autopkgtest/testing/amd64/p/plasma-mediacenter/5068495/log.gz

autopkgtest [01:39:03]: test testsuite: [---
dh_auto_test: warning: Compatibility levels before 10 are deprecated
(level 9 in use)
cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=-j1
Running tests...
/usr/bin/ctest --force-new-ctest-process -j1
Test project
/tmp/autopkgtest-lxc.yfcatxg0/downtmp/build.Oe3/src/obj-x86_64-linux-gnu
Start 1: pmctest-medialibrarytest
1/9 Test #1: pmctest-medialibrarytest .   Passed   36.02 sec
Start 2: pmctest-singletonfactorytest
2/9 Test #2: pmctest-singletonfactorytest .   Passed0.02 sec
Start 3: pmctest-pmcmediatest
3/9 Test #3: pmctest-pmcmediatest .   Passed0.02 sec
Start 4: pmctest-mediatest
4/9 Test #4: pmctest-mediatest    Passed0.02 sec
Start 5: pmctest-mediacentertest
5/9 Test #5: pmctest-mediacentertest ..   Passed0.00 sec
Start 6: pmctest-itemcachetest
6/9 Test #6: pmctest-itemcachetest    Passed0.02 sec
Start 7: pmctest-pmcalbumtest
7/9 Test #7: pmctest-pmcalbumtest .   Passed0.02 sec
Start 8: pmctest-pmcartisttest
8/9 Test #8: pmctest-pmcartisttest    Passed0.02 sec
Start 9: pmctest-runtimedatatest
9/9 Test #9: pmctest-runtimedatatest ..   Passed0.02 sec

100% tests passed, 0 tests failed out of 9

Total Test time (real) =  36.16 sec
autopkgtest [01:39:39]: test testsuite: ---]
autopkgtest [01:39:40]: test testsuite:  - - - - - - - - - - results - -
- - - - - - - -
testsuiteFAIL stderr: dh_auto_test: warning: Compatibility
levels before 10 are deprecated (level 9 in use)
autopkgtest [01:39:40]: test testsuite:  - - - - - - - - - - stderr - -
- - - - - - - -
dh_auto_test: warning: Compatibility levels before 10 are deprecated
(level 9 in use)



signature.asc
Description: OpenPGP digital signature

Bug#952464: clazy: flaky arm64 autopkgtest: unable to execute command: Segmentation fault

[Paul Gevers]

Hi Pino,

Thanks for the well written response.

On 25-02-2020 20:41, Pino Toscano wrote:
> The test is not flaky.

I can see why you say that now, but from my PoV (the release team) it is.

>> With a recent upload of gcc-10 to unstable, the autopkgtest of clazy
>> failed on arm64 in testing when that autopkgtest was run with the binary
>> packages of gcc-10 from unstable.
> 
> The failures have nothing to do with gcc-10.

Sorry if it wasn't more clear from the next line that I didn't imply that.

> Although, as I said, the issue "fixed itself" until the next
> src:llvm-defaults switch, this is slightly less problematic.

llvm-defaults and gcc-10 were blocked for some days by the clazy
regression on arm64. Can you explain why gcc-10 wasn't blocked by this
issue on amd64? Also, the failures on arm64 started before the
llvm-defaults upload [1] blocking glibc for some days. Do you also
understand that?

> In the meanwhile: because of what I said above, I'm demoting the
> severity of this bug to important. Also, Paul, please re-enable the
> autopkgtest of clazy on ci.debian.net, as they will pass now.

I didn't disable the autopkgtest on ci.d.n. I told our migration
software (britney) to ignore the regression on arm64. I have removed
that hint.

Paul

[1]
https://ci.debian.net/data/autopkgtest/testing/arm64/c/clazy/4223149/log.gz



signature.asc
Description: OpenPGP digital signature

Bug#952464: clazy: flaky arm64 autopkgtest: unable to execute command: Segmentation fault

[Paul Gevers]

Source: clazy
Version: 1.6-2
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

With a recent upload of gcc-10 to unstable, the autopkgtest of clazy
failed on arm64 in testing when that autopkgtest was run with the binary
packages of gcc-10 from unstable. I looked into the history of your
autopkgtest and it fails very often.

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests. Please either fix the test to be more robust, or or use the
"flaky" restriction for the offending test until a solution has been found.

I copied the output at the bottom of this report. All the failing tests
that I inspected look like it, albeit the test that fails differs
between runs.

I'll have the migration software ignore the results of your autopkgtest
on arm64 until this bug is fixed.

Paul

https://ci.debian.net/data/autopkgtest/testing/arm64/c/clazy/4369731/log.gz

Qt version: 51205
Qt headers: /usr/include/aarch64-linux-gnu/qt5
clang -Xclang -load -Xclang ClazyPlugin.so -Xclang -add-plugin -Xclang
clazy  -Wno-unused-value -Qunused-arguments -std=c++14 -isystem
/usr/include/aarch64-linux-gnu/qt5 -fPIC -L /usr/lib/aarch64-linux-gnu
-Xclang -plugin-arg-clazy -Xclang qt4-compat  -c  -Xclang
-plugin-arg-clazy -Xclang old-style-connect clazy/qt4compat2.cpp
Qt version: 51205
Qt headers: /usr/include/aarch64-linux-gnu/qt5
clang -Xclang -load -Xclang ClazyPlugin.so -Xclang -add-plugin -Xclang
clazy  -Wno-unused-value -Qunused-arguments -std=c++14 -isystem
/usr/include/aarch64-linux-gnu/qt5 -fPIC -L /usr/lib/aarch64-linux-gnu
-c  -Xclang -plugin-arg-clazy -Xclang old-style-connect -Xclang
-plugin-arg-clazy -Xclang export-fixes clazy/onlyQt1.cpp
Qt version: 51205
Qt headers: /usr/include/aarch64-linux-gnu/qt5
clang -Xclang -load -Xclang ClazyPlugin.so -Xclang -add-plugin -Xclang
clazy  -Wno-unused-value -Qunused-arguments -std=c++14 -isystem
/usr/include/aarch64-linux-gnu/qt5 -fPIC -L /usr/lib/aarch64-linux-gnu
-Xclang -plugin-arg-clazy -Xclang only-qt  -c  -Xclang -plugin-arg-clazy
-Xclang old-style-connect clazy/onlyQt2.cpp
Qt version: 51205
Qt headers: /usr/include/aarch64-linux-gnu/qt5
clang -Xclang -load -Xclang ClazyPlugin.so -Xclang -add-plugin -Xclang
clazy  -Wno-unused-value -Qunused-arguments -std=c++14 -isystem
/usr/include/aarch64-linux-gnu/qt5 -fPIC -L /usr/lib/aarch64-linux-gnu
-c -Wno-deprecated-declarations -Xclang -plugin-arg-clazy -Xclang
raw-environment-function raw-environment-function/main.cpp
Qt version: 51205
Qt headers: /usr/include/aarch64-linux-gnu/qt5
clang -Xclang -load -Xclang ClazyPlugin.so -Xclang -add-plugin -Xclang
clazy  -Wno-unused-value -Qunused-arguments -std=c++14 -isystem
/usr/include/aarch64-linux-gnu/qt5 -fPIC -L /usr/lib/aarch64-linux-gnu
-c  -Xclang -plugin-arg-clazy -Xclang inefficient-qlist
inefficient-qlist/main.cpp
Qt version: 51205
Qt headers: /usr/include/aarch64-linux-gnu/qt5
clang -Xclang -load -Xclang ClazyPlugin.so -Xclang -add-plugin -Xclang
clazy  -Wno-unused-value -Qunused-arguments -std=c++14 -isystem
/usr/include/aarch64-linux-gnu/qt5 -fPIC -L /usr/lib/aarch64-linux-gnu
-c  -Xclang -plugin-arg-clazy -Xclang qenums qenums/main.cpp
Running: clang -Xclang -load -Xclang ClazyPlugin.so -Xclang -add-plugin
-Xclang clazy  -Wno-unused-value -Qunused-arguments -std=c++14 -isystem
/usr/include/aarch64-linux-gnu/qt5 -fPIC -L /usr/lib/aarch64-linux-gnu
-c  -Xclang -plugin-arg-clazy -Xclang rule-of-three
rule-of-three/bug403193.cpp
output_file=rule-of-three/bug403193.cpp.out
[FAIL] rule-of-three (Failed to build test. Check
rule-of-three/bug403193.cpp.out for details)
---
Contents of rule-of-three/bug403193.cpp.out:
Stack dump:
0.  Program arguments: /usr/lib/llvm-8/bin/clang -cc1 -triple
aarch64-unknown-linux-gnu -emit-obj -mrelax-all -disable-free
-disable-llvm-verifier -discard-value-names -main-file-name
bug403193.cpp -mrelocation-model pic -pic-level 2 -mthread-model posix
-mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases
-fuse-init-array -target-cpu generic -target-feature +neon -target-abi
aapcs -fallow-half-arguments-and-returns -dwarf-column-info
-debugger-tuning=gdb -coverage-notes-file
/tmp/autopkgtest-lxc.ji5ue40b/downtmp/build.xGK/src/tests/bug403193.gcno
-resource-dir /usr/lib/llvm-8/lib/clang/8.0.1 -isystem
/usr/include/aarch64-linux-gnu/qt5 -internal-isystem
/usr/bin/../lib/gcc/aarch64-linux-gnu/8/../../../../include/c++/8
-internal-isystem
/usr/bin/../lib/gcc/aarch64-linux-gnu/8/../../../../include/aarch64-linux-gnu/c++/8
-internal-isystem
/usr/bin/../lib/gcc/aarch64-linux-gnu/8/../../../../include/aarch64-linux-gnu/c++/8
-internal-isystem
/usr/bin/../lib/gcc/aarch64-linux-gnu/8/../../../../include/c++/8/backward

Bug#949902: qtwebsockets-opensource-src ftbfs on s390x: timeout too short

[Paul Gevers]

Source: qtwebsockets-opensource-src
Version: 5.12.5-2
Severity: serious
Justification: ftbfs
Tags: ftbfs sid bullseye

Dear maintainer,

We did a rebuild of all packages linking against libqt5quick5, see bug
#948199. However, you package FTBFS on s390x due to a test timeout. Can
you please investigate how this test can be made more robust?

Paul

https://buildd.debian.org/status/package.php?p=qtwebsockets-opensource-src

FAIL!  : tst_QWebSocket::tst_errorString() QTestLib: This test case
check ("errorSpy.count())) == (1)))") failed because the requested
timeout (5000 ms) was too short, 5050 ms would have been sufficient this
time.
   Loc: [tst_qwebsocket.cpp(580)]



signature.asc
Description: OpenPGP digital signature

Bug#949677: mesa breaks build of kcrash, konsole and libkscreen as tested in autopkgtest migration setup

[Paul Gevers]

Hi Timo,

On 24-01-2020 18:52, Timo Aaltonen wrote:
> On 23.1.2020 23.08, Paul Gevers wrote:
>> Hi Timo,
>>
>> On 23-01-2020 22:01, Timo Aaltonen wrote:
>>> Look at the error above, the file shipped by qtbase5-dev requires
>>> libEGL.so which the libegl-dev dependency provides. It used to be in
>>> libglvnd-dev but moved to a new package when the EGL headers were added
>>> upstream.
>>
>> So, libglvnd-dev should add a versioned breaks on the old qtbase5-dev,
>> right?
> 
> Uh no...
> 
> The old qtbase5-dev (5.12.5+dfsg-2, in testing) depends on
> libgl1-mesa-dev. libgl1-mesa-dev (in testing) used to pull in
> libglvnd-dev which had libEGL.so. New libgl1-mesa-dev depends only on
> libgl-dev, so you don't get the libEGL.so symlink anymore. I guess
> libgl1-mesa-dev should depend on libegl-dev too, for now.

If you don't have objections for such a relation that the package
doesn't really need itself, that would work too.

Paul

Bug#949677: mesa breaks build of kcrash, konsole and libkscreen as tested in autopkgtest migration setup

[Paul Gevers]

Hi Timo,

On 23-01-2020 22:01, Timo Aaltonen wrote:
> Look at the error above, the file shipped by qtbase5-dev requires
> libEGL.so which the libegl-dev dependency provides. It used to be in
> libglvnd-dev but moved to a new package when the EGL headers were added
> upstream.

So, libglvnd-dev should add a versioned breaks on the old qtbase5-dev,
right?

Paul

Bug#949677: mesa breaks build of kcrash, konsole and libkscreen as tested in autopkgtest migration setup

[Paul Gevers]

Hi Timo,

On 23-01-2020 19:32, Timo Aaltonen wrote:
> The relevant part of the build log was:
> 
> CMake Error at
> /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfig.cmake:27 (message):
>   The imported target "Qt5::Gui" references the file
> 
>  "/usr/lib/x86_64-linux-gnu/libEGL.so"
> 
>   but this file does not exist.
> 
> 
> So you need at least qtbase5-dev version 5.12.5+dfsg-3 which added
> libegl-dev to it's Depends.

Which package (source or binary) do you refer here with "you"? As I
noted before, the interesting thing is that the autopkgtest passes both
in a pure testing environment and a pure unstable environment, but not
in testing with the following packages from unstable:
unstable/main amd64 libglvnd0 amd64 1.3.0-7 [51.5 kB]
unstable/main amd64 libglapi-mesa amd64 19.3.2-1 [69.9 kB]
unstable/main amd64 libgl1-mesa-dri amd64 19.3.2-1 [9,187 kB]
unstable/main amd64 libglx-mesa0 amd64 19.3.2-1 [182 kB]
unstable/main amd64 libglx0 amd64 1.3.0-7 [34.6 kB]
unstable/main amd64 libgl1 amd64 1.3.0-7 [88.8 kB]
unstable/main amd64 libglx-dev amd64 1.3.0-7 [16.2 kB]
unstable/main amd64 libgl-dev amd64 1.3.0-7 [100 kB]
unstable/main amd64 libgl1-mesa-dev amd64 19.3.2-1 [49.1 kB]
unstable/main amd64 libgbm1 amd64 19.3.2-1 [70.5 kB]
unstable/main amd64 libegl-mesa0 amd64 19.3.2-1 [139 kB]
unstable/main amd64 libegl1 amd64 1.3.0-7 [34.1 kB]

A successful run in testing doesn't pull in libegl-dev either, so it
seems that the file is not a hard requirement.

Paul

Bug#949677: mesa breaks build of kcrash, konsole and libkscreen as tested in autopkgtest migration setup

[Paul Gevers]

Source: mesa, kcrash, konsole, libkscreen
Control: found -1 mesa/19.3.2-1
Control: found -1 kcrash/5.62.0-1
Control: found -1 konsole/4:19.08.1-2
Control: found -1 libkscreen/4:5.14.5-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of mesa the autopkgtest of kcrash, konsole and
libkscreen fails in testing during building of the source package when
that autopkgtest is run with the binary packages of mesa from unstable.
It passes when run with only packages from testing. In tabular form (for
kcrash):
   passfail
mesa   from testing19.3.2-1
kcrash from testing5.62.0-1
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

It also passes in unstable. Nearly always that points at missing
versioned dependencies somewhere, so it would be good to track that
down, such that the autopkgtest pass in our migration tests as well.

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of mesa to testing
[1]. Due to the nature of this issue, I filed this bug report against
all packages. Can you please investigate the situation and reassign the
bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
mesa/19.3.2-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=mesa

https://ci.debian.net/data/autopkgtest/testing/amd64/k/kcrash/4071010/log.gz


Determining if the function shmat exists passed with the following output:
Change Dir:
/tmp/autopkgtest-lxc.ov32kph5/downtmp/build.7JK/src/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/make cmTC_c5c84/fast && make[2]: Entering
directory
'/tmp/autopkgtest-lxc.ov32kph5/downtmp/build.7JK/src/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_c5c84.dir/build.make
CMakeFiles/cmTC_c5c84.dir/build
make[3]: Entering directory
'/tmp/autopkgtest-lxc.ov32kph5/downtmp/build.7JK/src/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_c5c84.dir/CheckFunctionExists.c.o
/usr/bin/cc -D_GNU_SOURCE -D_LARGEFILE64_SOURCE  -g -O2
-fdebug-prefix-map=/tmp/autopkgtest-lxc.ov32kph5/downtmp/build.7JK/src=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -std=iso9899:1990 -fno-common -Wall -Wextra
-Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long
-Wpointer-arith -Wundef -Wmissing-format-attribute -Wwrite-strings
-Werror=implicit-function-declaration -DCHECK_FUNCTION_EXISTS=shmat   -o
CMakeFiles/cmTC_c5c84.dir/CheckFunctionExists.c.o   -c
/usr/share/cmake-3.15/Modules/CheckFunctionExists.c
Linking C executable cmTC_c5c84
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_c5c84.dir/link.txt
--verbose=1
/usr/bin/cc -g -O2
-fdebug-prefix-map=/tmp/autopkgtest-lxc.ov32kph5/downtmp/build.7JK/src=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -std=iso9899:1990 -fno-common -Wall -Wextra
-Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long
-Wpointer-arith -Wundef -Wmissing-format-attribute -Wwrite-strings
-Werror=implicit-function-declaration -DCHECK_FUNCTION_EXISTS=shmat
-Wl,--enable-new-dtags -Wl,-z,relro -Wl,--as-needed
CMakeFiles/cmTC_c5c84.dir/CheckFunctionExists.c.o  -o cmTC_c5c84
make[3]: Leaving directory
'/tmp/autopkgtest-lxc.ov32kph5/downtmp/build.7JK/src/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: Leaving directory
'/tmp/autopkgtest-lxc.ov32kph5/downtmp/build.7JK/src/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'



dh_auto_configure: cd obj-x86_64-linux-gnu && cmake
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON
-DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles"
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu
-DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc
-DKDE_INSTALL_USE_QT_SYS_PATHS=ON -DBUILD_QCH=ON .. returned exit code 1
make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 2
make[1]: Leaving directory
'/tmp/autopkgtest-lxc.ov32kph5/downtmp/build.7JK/src'
make: *** [debian/rules:7: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit
status 2




signature.asc
Description: OpenPGP digital signature

Bug#945174: pyside2 Build-Depends on libqt5datavisualization5-dev which isn't available on mipsel/mips64el

[Paul Gevers]

Source: pyside2
Version: 5.13.2-1
Severity: serious
Tags: ftbfs
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

In commit 5e39f9e [1] you added a new build dependency on
libqt5datavisualization5-dev, however, that package is not available on mipsel
and mips64el, while your package built on those architectures in the past. If
this BD can't be worked around, please request removal in unstable of the
binary packages of pyside2 on those architectures.

Paul

PS: your package is also failing on other architectures. There is the python
3.8 transition going on, so that may (or may not) be related.

[1] 
https://salsa.debian.org/qt-kde-team/qt/pyside2/commit/5e39f9e28972f0c90c4ca1bb8bb411f44e435477

- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3VrUAACgkQnFyZ6wW9
dQodggf/TDvuJ1mFPdoHNFcFJzd8mUfafLLZO/2ltWwji/Uwp2WS3MN4p2v5AZ5a
1jXaAin4edCXrVT6jdTYbW/bSlbQCg2OCha98qs0N8de9BKbA3t45UKMUV69tbc9
fJY9MF54K7fLq9PtoCYjPzoPjTT7M4SnUPAhZeI2AmimaZxes/XMsqGf65aGU6/8
fs3yz7IHcYmAOFLHvrSALQN/EkOz3tKWjk+cnFUr6lIouZSf5CXjXECgiCqI2bFQ
qC+nEawlEDLnqztSBLGXI776XChXr3PEv1dIw0yZomz5ejPZ9SoNTflsOvsPSLOz
AoAXpkHI5NZuK2Xj+MR2SJY0x6F6mw==
=Oalw
-END PGP SIGNATURE-

Bug#939687: clazy: FTBFS on armel: undefined reference to symbol '__atomic_load_4@@LIBATOMIC_1.0'

[Paul Gevers]

Source: clazy
Version: 1.5-1
Severity: serious
Tags: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainer,

During a binNMU of clazy during the llvm-defaults transition, you package FTBFS
on armel. Can you please check and fix the situation?

The last part of the log message as currently shown on 
https://buildd.debian.org/status/fetch.php?pkg=clazy=armel=1.5-1%2Bb1=1567623182=0
 reads:

[100%] Linking CXX executable bin/clazy-standalone
/usr/bin/cmake -E cmake_link_script CMakeFiles/clazy-standalone.dir/link.txt 
--verbose=1
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wno-class-memaccess 
-Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -fno-common -Woverloaded-virtual 
-Wcast-qual -fno-strict-aliasing -pedantic -Wno-long-long -Wall -W 
-Wno-unused-parameter -Wwrite-strings -fno-exceptions -fno-rtti -fPIC  
-Wl,-z,relro -Wl,-z,now -latomic -rdynamic 
CMakeFiles/clazy-standalone.dir/src/ClazyStandaloneMain.cpp.o  -o 
bin/clazy-standalone  -L/usr/lib/llvm-8/lib 
-Wl,-rpath,/usr/lib/llvm-8/lib:/<>/obj-arm-linux-gnueabi/lib: 
lib/ClazyPlugin.so /usr/lib/llvm-8/lib/libclangFrontend.a 
/usr/lib/llvm-8/lib/libclangDriver.a /usr/lib/llvm-8/lib/libclangCodeGen.a 
/usr/lib/llvm-8/lib/libclangSema.a /usr/lib/llvm-8/lib/libclangAnalysis.a 
/usr/lib/llvm-8/lib/libclangRewriteFrontend.a 
/usr/lib/llvm-8/lib/libclangRewrite.a /usr/lib/llvm-8/lib/libclangAST.a 
/usr/lib/llvm-8/lib/libclangASTMatchers.a /usr/lib/llvm-8/lib/libclangParse.a 
/usr/lib/llvm-8/lib/libclangLex.a /usr/lib/llvm-8/lib/libclangBasic.a 
/usr/lib/llvm-8/lib/libclangARCMigrate.a /usr/lib/llvm-8/lib/libclangEdit.a 
/usr/lib/llvm-8/lib/libclangFrontendTool.a 
/usr/lib/llvm-8/lib/libclangRewrite.a 
/usr/lib/llvm-8/lib/libclangSerialization.a 
/usr/lib/llvm-8/lib/libclangTooling.a 
/usr/lib/llvm-8/lib/libclangStaticAnalyzerCheckers.a 
/usr/lib/llvm-8/lib/libclangStaticAnalyzerCore.a 
/usr/lib/llvm-8/lib/libclangStaticAnalyzerFrontend.a 
/usr/lib/llvm-8/lib/libclangSema.a /usr/lib/llvm-8/lib/libLLVM-8.so 
/usr/lib/llvm-8/lib/libclangAnalysis.a 
/usr/lib/llvm-8/lib/libclangRewriteFrontend.a 
/usr/lib/llvm-8/lib/libclangRewrite.a /usr/lib/llvm-8/lib/libclangAST.a 
/usr/lib/llvm-8/lib/libclangASTMatchers.a /usr/lib/llvm-8/lib/libclangParse.a 
/usr/lib/llvm-8/lib/libclangLex.a /usr/lib/llvm-8/lib/libclangBasic.a 
/usr/lib/llvm-8/lib/libclangARCMigrate.a /usr/lib/llvm-8/lib/libclangEdit.a 
/usr/lib/llvm-8/lib/libclangFrontendTool.a 
/usr/lib/llvm-8/lib/libclangSerialization.a 
/usr/lib/llvm-8/lib/libclangTooling.a 
/usr/lib/llvm-8/lib/libclangStaticAnalyzerCheckers.a 
/usr/lib/llvm-8/lib/libclangStaticAnalyzerCore.a 
/usr/lib/llvm-8/lib/libclangStaticAnalyzerFrontend.a 
/usr/lib/llvm-8/lib/libLLVM-8.so 
/usr/bin/ld: lib/ClazyPlugin.so: undefined reference to symbol 
'__atomic_load_4@@LIBATOMIC_1.0'
/usr/bin/ld: /usr/lib/gcc/arm-linux-gnueabi/9/libatomic.so: error adding 
symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
make[3]: *** [CMakeFiles/clazy-standalone.dir/build.make:128: 
bin/clazy-standalone] Error 1
make[3]: Leaving directory '/<>/obj-arm-linux-gnueabi'
make[2]: *** [CMakeFiles/Makefile2:76: CMakeFiles/clazy-standalone.dir/all] 
Error 2
make[2]: Leaving directory '/<>/obj-arm-linux-gnueabi'
make[1]: *** [Makefile:155: all] Error 2
make[1]: Leaving directory '/<>/obj-arm-linux-gnueabi'
dh_auto_build: cd obj-arm-linux-gnueabi && make -j4 "INSTALL=install 
--strip-program=true" returned exit code 2
make: *** [debian/rules:19: build-arch] Error 255

- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (200, 'testing'), (100, 
'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.2.0-2-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl1z/eoACgkQnFyZ6wW9
dQob6Qf+IBuxWmNSd6kwO4kHCm16SInrB4a3Rs2/PIcFopnGiQKY7UNza6iLcw2f
dd+uaLJkKQzYRq6IMHAfEQe7vjF3lB1oITyJNKx4VRpxQ8fMBkwVQsNsErs2ACBu
GFmFNoJaEWlaC0rZcpoHIZU2x98jhQheGv/hfQ2L8FaoKUqwo2PRGgFKoR0kGLvN
N6KZottKecx8M0BiIdyTHi1YC/c5VWqXue5vWRLmLpOPqs40+xZQClcutfhD/F0U
nSYRQPuYW+I0cdFObARzY80kqGqg6lwGGEb3SczUHSAuTPfLMFvaVCNL1FZN7TCg
FgGro3JPdiKOclpK9OL+KHI3JJMgUQ==
=Tiwf
-END PGP SIGNATURE-

Bug#929882: buildd.debian.org: possible conflict between the "dhelp" package and the KDE packages on debian buster

[Paul Gevers]

Hi khelpcenter maintainers,

On Sat, 01 Jun 2019 21:30:41 +0200 pnd23  wrote:
> KDE packages install their documentation files in /usr/share/doc/HTML on 
> buster
> (in debian 8 this was: /usr/share/doc/kde/HTML). The "dhelp" package erases
> this folder when it rebuilds its index. The KHelpcenter documentation gets
> erased this way.

This bug got cloned to khelpcenter to make sure that you change your
package to conflict with the unfixed version of dhelp, to prevent the
above issue from happening. I expect that dhelp may be removed from
buster, but if the package isn't removed from the users system, the
issue may still occur.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#784479: [kde4libs] Qt4's WebKit removal

[Paul Gevers]

Hi Scott,

On Tue, 15 Jan 2019 11:03:33 + Scott Kitterman
 wrote:

> I think rebuilding the rdepends is a reasonable next step.  I'll try
> that and see if anything is affected.

Did you get around to do this?

Paul



signature.asc
Description: OpenPGP digital signature

KDE/Qt tests [was Re: Bug#906694: purpose: autopkgtest regression]

[Paul Gevers]

Hi Maximiliano, others

On Mon, 3 Dec 2018 11:24:15 -0300 Maximiliano Curia
 wrote:
> About the kde frameworks uploads, they are handled in a bundle, and breaks 
> and 
> dependencies are added so they migrate to testing as needed, the same breaks 
> and dependencies can cause temporary uninstallability in unstable, thus, 
> having a lot of temporary regressions, in order to have a "smoother" testing.
> 
> At the same time, the autopkgtest run (mostly) upstream's unittests (mostly 
> the ones that can't be run as part of the build). But, sadly, upstream 
> doesn't 
> enforce running their unittests as part of their development nor release 
> process, so, some regressions in part of their unittests is "normal". This 
> fits "nicely" with the current way Debian delays the transitions to testing, 
> which gives enough time to unstable users to report real regressions in 
> behaviour.
> 
> All of this is to explain that, currently, a report about autopkgtest issues 
> is not really useful to us, and would be time better spent reporting them 
> directly upstream (if it applies). Furthermore, once the autopkgtest are used 
> to block the migration to testing completely, we would be forced to to simply 
> drop most of the tests (as long as upstream doesn't change their policy 
> regarding unittest).
> 
> This can be considered as a documentation of the current state of affairs 
> regarding kde frameworks and kde plasma. No response needed.

However, currently regressions due to glibc in kio, kdelibs4support,
khtml and kparts are blocking the migration of glibc to testing. Should
we be ignoring those regressions as well? If that is the case, can you
please already start removing the tests, as they also hamper other
packages, or maybe you want to mark them as "flaky" [1]. All four fail
on the abi-compliance test.

Paul

[1]
https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst



signature.asc
Description: OpenPGP digital signature

Bug#914045: qtbase-opensource-src breaks lots of autopkgtests

[Paul Gevers]

Hi Lisandro,

Thanks for the reply.

On 18-11-18 21:47, Lisandro Damián Nicanor Pérez Meyer wrote:
> None of the qtbase changes should be triggering this. *But* all the packages 
> are being built with qttools5-dev-tools 5.11.2-4 instead of 5.11.2-5, and 
> that 
> might be the issue, as the latest version contains a fix for some clang stuff:
> 
> 
> 
> Ideally this tests should be retried with qttools-dev-tools 5.11.2-5. Can 
> that 
> be done? No enough build power here to try myself.

I've just triggered one package (kpackage), but if this is really the
case, it should normally be fixed in the dependency registration
somehow, e.g. most likely a versioned breaks in qtbase-opensource-src on
the broken version of qttools5-dev-tools. I guess that waiting one day
will fix the issue also (if/when qttools-opensource-src migrates).

Paul



signature.asc
Description: OpenPGP digital signature

Bug#914045: qtbase-opensource-src breaks lots of autopkgtests

[Paul Gevers]

Source: qtbase-opensource-src
Version: 5.11.2+dfsg-6
Severity: important
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks

Dear maintainers,

With a recent upload of qtbase-opensource-src the autopkgtest of quite a
few packages fail in testing when their autopkgtest are run with the
binary packages of qtbase-opensource-src from unstable. They pass when
run with only packages from testing. In tabular form:
   passfail
qtbase-opensource-src  from testing5.11.2+dfsg-6
(e.g.) krunner from testing5.49.0-1
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report. I checked
several packages and the error is extremely similar. I have the feeling
that there is a versioned (test) dependency missing somewhere. On the
other hand, I don't know the KDE/Qt stack, so maybe this can/should be
"fixed" by a versioned breaks. I note explicitly that it's the source of
krunner from testing that is build with qtbase-opensource-src from
unstable, while e.g. extra-cmake-modules is still from testing (as it
isn't required by any dependency or breaks relation to come from unstable).

Currently this regression is contributing to the delay of the migration
of qtbase-opensource-src to testing [1]. Due to dependencies, there are
quite a few packages waiting for that migration as well AFAICT. Can you
please investigate the situation.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
qtbase-opensource-src/5.11.2+dfsg-6. I.e. due to versioned dependencies
or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=qtbase-opensource-src

https://ci.debian.net/data/autopkgtest/testing/amd64/k/krunner/1331006/log.gz

CMake Error at src/cmake_install.cmake:119 (file):
  file INSTALL cannot find

"/tmp/autopkgtest-lxc.p952k2pe/downtmp/build.LIE/src/obj-x86_64-linux-gnu/src/KF5Runner.qch".
Call Stack (most recent call first):
  cmake_install.cmake:88 (include)


make[1]: *** [Makefile:65: install] Error 1
make[1]: Leaving directory
'/tmp/autopkgtest-lxc.p952k2pe/downtmp/build.LIE/src/obj-x86_64-linux-gnu'
dh_auto_install: cd obj-x86_64-linux-gnu && make V=1 -j2 install
DESTDIR=/tmp/autopkgtest-lxc.p952k2pe/downtmp/build.LIE/src/debian/tmp
AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" returned
exit code 2
make: *** [debian/rules:7: binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess
returned exit status 2



signature.asc
Description: OpenPGP digital signature

Bug#913457: krunner: autopkgtest regression

[Paul Gevers]

Source: krunner
Version: 5.51.0-1
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of packages in the KDE stack the autopkgtest of
krunner fails in testing when that autopkgtest is run with those binary
packages from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
krunnerfrom testing5.51.0-1
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is contributing to the delay of the migration
of quite a few packages in the KDE stack to testing [1]. Can you please
investigate the situation? If needed, please change the bug's severity.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] Installation with a limited set of packages failed. (You can see
what packages were added from the second line of the log file quoted
below. The migration software adds source package from unstable to the
list if they are needed to install packages from kio/5.51.0-1. I.e. due
to versioned dependencies or breaks/conflicts.) Therefore a lot of
packages were allowed to be installed from unstable.
[1] https://qa.debian.org/excuses.php?package=kio

https://ci.debian.net/data/autopkgtest/testing/amd64/k/krunner/1296207/log.gz

autopkgtest [05:27:10]: test testsuite: [---
cd obj-x86_64-linux-gnu && make V=1 -j1 test ARGS\+=-j1
Running tests...
/usr/bin/ctest --force-new-ctest-process -j1
Test project
/tmp/autopkgtest-lxc.lg6u_5gj/downtmp/build.LxM/src/obj-x86_64-linux-gnu
Start 1: runnercontexttest
1/2 Test #1: runnercontexttest    Passed0.05 sec
Start 2: dbusrunnertest
Errors while running CTest
2/2 Test #2: dbusrunnertest ...***Failed   11.20 sec
* Start testing of DBusRunnerTest *
Config: Using QtTest library 5.11.2, Qt 5.11.2
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 8.2.0)
PASS   : DBusRunnerTest::initTestCase()
QWARN  : DBusRunnerTest::testMatch() org.kde.plasma: unversioned plugin
detected, may result in instability
QWARN  : DBusRunnerTest::testMatch() org.kde.plasma: unversioned plugin
detected, may result in instability
QWARN  : DBusRunnerTest::testMatch() org.kde.plasma: unversioned plugin
detected, may result in instability
FAIL!  : DBusRunnerTest::testMatch() 'spy.wait()' returned FALSE. ()
   Loc:
[/tmp/autopkgtest-lxc.lg6u_5gj/downtmp/build.LxM/src/autotests/dbusrunnertest.cpp(106)]
QWARN  : DBusRunnerTest::testMatch() QProcess: Destroyed while process
("/tmp/autopkgtest-lxc.lg6u_5gj/downtmp/build.LxM/src/obj-x86_64-linux-gnu/bin/testremoterunner")
is still running.
QWARN  : DBusRunnerTest::testMulti() org.kde.plasma: unversioned plugin
detected, may result in instability
QWARN  : DBusRunnerTest::testMulti() org.kde.plasma: unversioned plugin
detected, may result in instability
QWARN  : DBusRunnerTest::testMulti() org.kde.plasma: unversioned plugin
detected, may result in instability
FAIL!  : DBusRunnerTest::testMulti() 'spy.wait()' returned FALSE. ()
   Loc:
[/tmp/autopkgtest-lxc.lg6u_5gj/downtmp/build.LxM/src/autotests/dbusrunnertest.cpp(159)]
QWARN  : DBusRunnerTest::testMulti() QProcess: Destroyed while process
("/tmp/autopkgtest-lxc.lg6u_5gj/downtmp/build.LxM/src/obj-x86_64-linux-gnu/bin/testremoterunner")
is still running.
QWARN  : DBusRunnerTest::testMulti() QProcess: Destroyed while process
("/tmp/autopkgtest-lxc.lg6u_5gj/downtmp/build.LxM/src/obj-x86_64-linux-gnu/bin/testremoterunner")
is still running.
PASS   : DBusRunnerTest::cleanupTestCase()
Totals: 2 passed, 2 failed, 0 skipped, 0 blacklisted, 11134ms
* Finished testing of DBusRunnerTest *


50% tests passed, 1 tests failed out of 2

Total Test time (real) =  11.25 sec

The following tests FAILED:
  2 - dbusrunnertest (Failed)
make: *** [Makefile:87: test] Error 8
dh_auto_test: cd obj-x86_64-linux-gnu && make V=1 -j1 test ARGS\+=-j1
returned exit code 2



signature.asc
Description: OpenPGP digital signature

Bug#910780: korganizer: autopkgtest regression

[Paul Gevers]

Source: korganizer
Version: 4:18.08.1-1
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of korganizer the autopkgtest of korganizer fails
in unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
korganizer from testing4:18.08.1-1
all others from testingfrom unstable

I copied some of the output at the bottom of this report.

Currently this regression is contributing to the delay of the migration
to testing [1]. Can you please investigate the situation and fix it? If
needed, please change the bug's severity.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=korganizer

https://ci.debian.net/data/autopkgtest/unstable/amd64/k/korganizer/1124885/log.gz
autopkgtest [05:49:29]: test testsuite: [---
libKF5Plasma.so.5 was not found.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher'
kdeinit5: Launched KLauncher, pid = 18483, result = 0
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeinit5: opened connection to :99
cd obj-x86_64-linux-gnu && make -j2 test ARGS\+=-j2
Running tests...
/usr/bin/ctest --force-new-ctest-process -j2
Test project
/tmp/autopkgtest-lxc.2sb4baxc/downtmp/build.OiE/src/obj-x86_64-linux-gnu
Start 1: testkodaymatrix
Start 2: akonadi-sqlite-koeventpopupmenutest
1/4 Test #1: testkodaymatrix ...***Failed0.17 sec
* Start testing of KODayMatrixTest *
Config: Using QtTest library 5.11.1, Qt 5.11.1
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 8.2.0)
PASS   : KODayMatrixTest::initTestCase()
FAIL!  : KODayMatrixTest::testMatrixLimits() 'range ==
iterator2.value()' returned FALSE. ()
   Loc:
[/tmp/autopkgtest-lxc.2sb4baxc/downtmp/build.OiE/src/src/autotests/testkodaymatrix.cpp(61)]
PASS   : KODayMatrixTest::cleanupTestCase()
Totals: 2 passed, 1 failed, 0 skipped, 0 blacklisted, 4ms
* Finished testing of KODayMatrixTest *

Start 3: noteeditdialogtest
2/4 Test #3: noteeditdialogtest    Passed0.40 sec
Start 4: reparentingmodeltest
3/4 Test #4: reparentingmodeltest ..   Passed0.05 sec
4/4 Test #2: akonadi-sqlite-koeventpopupmenutest ...   Passed2.16 sec

75% tests passed, 1 tests failed out of 4

Total Test time (real) =   2.16 sec

The following tests FAILED:
  1 - testkodaymatrix (Failed)
Errors while running CTest
make: *** [Makefile:111: test] Error 8
dh_auto_test: cd obj-x86_64-linux-gnu && make -j2 test ARGS\+=-j2
returned exit code 2
kdeinit5: terminate KDE.
klauncher: Exiting on signal 1
autopkgtest [05:49:32]: test testsuite: ---]





signature.asc
Description: OpenPGP digital signature

Re: glibc and abi-compliance-checker break multiple KDE autopkgtests

[Paul Gevers]

Dear all,

On 09-09-18 22:04, Paul Gevers wrote:
> On 09/06/18 21:13, Paul Gevers wrote:
>> So it seems they are requested by something, and because the are not
>> available in testing, apt-get is not limited by our pinning to take them
>> from unstable. I believe it must be a "Provides" of some sort. What I
>> want to know (and I will spend some time on it) is what in the
>> dependency chain makes us end up with this as an option.
> 
> I was not able to figure out in the time I spend on it why apt-get ended
> up with installing those packages. Does anybody know the right commands
> and their arguments to figure out this specific question?
> 
> Paul
> PS: the last line that I used was:
> apt-cache dotty $(echo $(apt-cache showsrc kf5-kdepim-apps-libs | grep
> Binary | sed s/Binary:// | sed s/,//g) | sort --unique) dh-acc
> exuberant-ctags | grep '++8'

I went ahead and let glibc and abi-compliance-checker migrate to
testing. I ran reference runs of the failing tests today to check if
everything is all-right, and it is.

So this is a versioned Depends/Breaks/Conflicts issue somewhere. I am
very uncomfortable about this, because today qtbase-opensource-src
started to be hit by the same issue.

Paul
@ qtbase-opensource-src maintainers, this conversation starts here:
https://lists.debian.org/debian-ci/2018/09/msg00010.html



signature.asc
Description: OpenPGP digital signature

Re: glibc and abi-compliance-checker break multiple KDE autopkgtests

[Paul Gevers]

Hi all,

On 09/06/18 21:13, Paul Gevers wrote:
> So it seems they are requested by something, and because the are not
> available in testing, apt-get is not limited by our pinning to take them
> from unstable. I believe it must be a "Provides" of some sort. What I
> want to know (and I will spend some time on it) is what in the
> dependency chain makes us end up with this as an option.

I was not able to figure out in the time I spend on it why apt-get ended
up with installing those packages. Does anybody know the right commands
and their arguments to figure out this specific question?

Paul
PS: the last line that I used was:
apt-cache dotty $(echo $(apt-cache showsrc kf5-kdepim-apps-libs | grep
Binary | sed s/Binary:// | sed s/,//g) | sort --unique) dh-acc
exuberant-ctags | grep '++8'



signature.asc
Description: OpenPGP digital signature

Bug#908270: baloo-widgets: autopkgtest regression

[Paul Gevers]

Source: baloo-widgets
Version: 4:18.08.0-1
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of baloo-widgets the autopkgtest of baloo-widgets
fails in testing when that autopkgtest is run with the binary packages
of baloo-widgets from unstable. It passes when run with only packages
from testing. I copied some of the output at the bottom of this report.

Currently this regression is contributing to the delay of the migration
to testing [1]. Can you please investigate the situation and fix it? If
needed, please change the bug's severity.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=baloo-widgets

https://ci.debian.net/data/autopkgtest/testing/amd64/b/baloo-widgets/952039/log.gz

1/4 Test #2: filemetadatawidgettest ...***Failed0.03 sec
qt.qpa.screen: QXcbConnection: Could not connect to display
Could not connect to any X display.

Start 3: filemetadataitemcounttest
2/4 Test #3: filemetadataitemcounttest ***Failed0.02 sec
qt.qpa.screen: QXcbConnection: Could not connect to display
Could not connect to any X display.

Start 4: filemetadatadatedisplaytest
3/4 Test #4: filemetadatadatedisplaytest ..***Failed0.02 sec
qt.qpa.screen: QXcbConnection: Could not connect to display
Could not connect to any X display.

4/4 Test #1: extractortest    Passed0.08 sec

25% tests passed, 3 tests failed out of 4

Total Test time (real) =   0.08 sec

The following tests FAILED:
  2 - filemetadatawidgettest (Failed)
  3 - filemetadataitemcounttest (Failed)
  4 - filemetadatadatedisplaytest (Failed)



signature.asc
Description: OpenPGP digital signature

Re: glibc and abi-compliance-checker break multiple KDE autopkgtests

[Paul Gevers]

Hi

On 06-09-18 16:39, Antonio Terceiro wrote:
>>> Does this mean that libc++-8-dev is breaking the ABI of the Qt/KDE
>>> packages? Luckily libc++-8-dev will not migrate to testing due to
>>> https://bugs.debian.org/714686 Does it need a "Breaks" then?
>>
>> Actually due to a bug in the migration process this package migrated to
>> testing on 2018-08-26 despite the RC bug. It has been removed from
>> testing during last night.
>>
>>> Does anybody know why libc++-8-dev is installed when glibc or
>>> abi-compliance-checker come from unstable? It seems that package is
>>> providing something that in testing is provided by libc++-dev (Or
>>> somewhere else in the dependency chain this goes "wrong" and leads to
>>> this outcome).
>>
>> I have been able to install libc++-dev along glibc 2.27-6, so I wonder
>> if it is not just a matter of regenerating the testing chroot following
>> the libc++-8-dev removal from testing.
> 
> the containers on ci.debian.net are recreated from scratch once a day,
> so this should solve itsef, I guess?

I don't know. In the failing cases, libc++-8-dev was installed from
unstable, not from testing:
Get:2 http://deb.debian.org/debian unstable/main amd64 libc++abi1-8
amd64 1:8~svn340819-1 [81.3 kB]
Get:3 http://deb.debian.org/debian unstable/main amd64 libc++1-8 amd64
1:8~svn340819-1 [214 kB]
Get:4 http://deb.debian.org/debian unstable/main amd64 libc++-8-helpers
all 1:8~svn340819-1 [28.3 kB]
Get:5 http://deb.debian.org/debian unstable/main amd64 libc++-8-dev
amd64 1:8~svn340819-1 [1,473 kB]

So it seems they are requested by something, and because the are not
available in testing, apt-get is not limited by our pinning to take them
from unstable. I believe it must be a "Provides" of some sort. What I
want to know (and I will spend some time on it) is what in the
dependency chain makes us end up with this as an option.

Paul



signature.asc
Description: OpenPGP digital signature

Re: glibc and abi-compliance-checker break multiple KDE autopkgtests

[Paul Gevers]

Hi

On 06-09-18 11:53, Samuel Thibault wrote:
> Samuel Thibault, le jeu. 06 sept. 2018 11:44:45 +0200, a ecrit:
>> Paul Gevers, le jeu. 06 sept. 2018 11:22:46 +0200, a ecrit:
>>> On 06-09-18 11:19, Samuel Thibault wrote:
>>>> It'd be useful for the abi-compliance-checker test to actually output
>>>> error messages,
>>>>
>>>> https://ci.debian.net/data/autopkgtest/testing/amd64/k/kf5-kdepim-apps-libs/944759/log.gz
>>>>
>>>> it not very talkative :)
>>>
>>> I agree, but I found that there are more logs in the artifacts.
>>
>> Ah, right. They seem to only point at c++ headers, so it'd rather be a
>> g++ issue?
> 
> All the passed artifacts I can find have libc++-dev 6.0.1-1, not
> libc++-8-dev 1:8~svn340819-1.

Does this mean that libc++-8-dev is breaking the ABI of the Qt/KDE
packages? Luckily libc++-8-dev will not migrate to testing due to
https://bugs.debian.org/714686 Does it need a "Breaks" then?

Does anybody know why libc++-8-dev is installed when glibc or
abi-compliance-checker come from unstable? It seems that package is
providing something that in testing is provided by libc++-dev (Or
somewhere else in the dependency chain this goes "wrong" and leads to
this outcome).

This is maybe also the reason why the autopkgtest of these packages fail
already longer in unstable. Apparently the wrong libc++*-dev package
gets installed.

Paul

PS to all: if we determine how this goes wrong and if I can't get the CI
framework to do the right thing and this is outside of glibc and
abi-compliance-checker, I'll ask the migration software to ignore these
failures.



signature.asc
Description: OpenPGP digital signature

Re: glibc and abi-compliance-checker break multiple KDE autopkgtests

[Paul Gevers]

Hi Samuel, all,

On 06-09-18 11:19, Samuel Thibault wrote:
> It'd be useful for the abi-compliance-checker test to actually output
> error messages,
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/k/kf5-kdepim-apps-libs/944759/log.gz
> 
> it not very talkative :)

I agree, but I found that there are more logs in the artifacts.

Paul



signature.asc
Description: OpenPGP digital signature

glibc and abi-compliance-checker break multiple KDE autopkgtests

[Paul Gevers]

Dear glibc, abi-compliance-checker and Qt/KDE maintainers,

With recent upload of glibc and abi-compliance-checker the autopkgtest
of libkf5calendarsupport, kf5-kdepim-apps-libs and akonadi-calendar
started to fail when run in testing with either glibc or
abi-compliance-checker from unstable. These autopkgtests all run
abi-compliance-checker and fail on it.

Currently these regressions are contributing to the delay of the
migration of glibc [1] and abi-compliance-checker [2] to testing. Could
you please help to investigate the situation? Normally I would file bugs
but because the similarity between the packages that fail for glibc and
abi-compliance-checker and the fact that three packages fail I fell back
to this e-mail, as it seems to be too much coincidence.

Feel free to ask help about the CI side of things from the Debian-CI
team (in CC).

More information about this e-mail can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=glibc
[2] https://qa.debian.org/excuses.php?package=abi-compliance-checker




signature.asc
Description: OpenPGP digital signature

Bug#908108: libkf5mailimporter: flaky autopkgtest different failures in different runs

[Paul Gevers]

Source: libkf5mailimporter
Version: 4:17.12.3-1
Severity: important
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainers,

With a recent upload of glibc the autopkgtest of libkf5mailimporter
started to fail when run in testing. The test was retried and failed
again, but this time on a different error. The third time it passed. I
copied the output below.

Could you please investigate and make your autopkgtest more robust?
Please contact me if you need help and you think I can provide that (I
am not subscribed to this bug). If this flakiness can't really be fixed,
consider setting the "flaky" restriction (see
https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst).

Recent discussion of gating migration by autopkgtests on debian-devel
[1] noted that if this is going to work, and in particular if we are
going to *block* migration when it causes autopkgtest regressions rather
than merely delaying it, intermittent autopkgtest failures are likely to
have to be considered RC due to their impact on the tested package's
dependencies; for now I've filed it as important.

Paul

[1] https://lists.debian.org/debian-devel/2018/05/msg00061.html

https://ci.debian.net/data/autopkgtest/testing/amd64/libk/libkf5mailimporter/944753/log.gz

96% tests passed, 1 tests failed out of 25

Total Test time (real) =   1.24 sec

The following tests FAILED:
  4 - mailimporter-filtersylpheedtest (Failed)

https://ci.debian.net/data/autopkgtest/testing/amd64/libk/libkf5mailimporter/939739/log.gz

96% tests passed, 1 tests failed out of 25

Total Test time (real) =   1.39 sec

The following tests FAILED:
  2 - mailimporter-filtericedovetest (Failed)





signature.asc
Description: OpenPGP digital signature

Bug#903314: kwayland: flaky autopkgtest: kwayland-testPlasmaWindowModel Exception: SIGPIPE

[Paul Gevers]

Control: reassign -1 src:kwayland 4:5.47.0-1

On Sun, 8 Jul 2018 20:13:14 +0200 Paul Gevers  wrote:
> Source: plasma-framework

This was obviously wrong. Reassigning to the right package.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#907340: qtbase-opensource-src breaks purpose autopkgtest possibly due to new openssl

[Paul Gevers]

Source: qtbase-opensource-src, purpose
Version: qtbase-opensource-src/5.11.1+dfsg-7
Version: purpose/5.47.0-1
X-Debbugs-CC: debian...@lists.debian.org, open...@packages.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Control: block 907015 by -1

Dear maintainers,

With a recent upload of qtbase-opensource-src the autopkgtest of purpose
started to fail in testing. I copied the output below.

I suspect that this regression is due to the fact that
qtbase-opensource-src was build with the 1.1.1* version of openssl which
incorporates changes regarding the default minimum level of security,
hence the CC. I suggest to discuss with the openssl maintainers how to
best fix this situation. I added a block relation on a tracking bug for
this as well.

Currently this regression is contributing to the delay of the migration
of qtbase-opensource-src to testing [1] and I assigned this bug to both
source packages (qtbase-opensource-src, purpose). Could you please
investigate the situation and reassign the bug to the right package? If
needed, please change the bug's severity as appropriate. I just filed a
similar bug against the qtbase-opensource-src, kdeconnect combination;
#907339, if both these issue are fully due to qtbase-opensource-src,
they should probably be merged)

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=qtbase-opensource-src

https://ci.debian.net/data/autopkgtest/testing/amd64/p/purpose/883222/log.gz

autopkgtest [05:31:24]: test testsuite: [---
Openbox-Message: Unable to find a valid menu file
"/var/lib/openbox/debian-menu.xml"
libKF5Parts.so.5 was not found.
libKF5Plasma.so.5 was not found.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher'
kdeinit5: Launched KLauncher, pid = 20788, result = 0
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeinit5: opened connection to :99
cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=-j1
Running tests...
/usr/bin/ctest --force-new-ctest-process -j1
Test project
/tmp/autopkgtest-lxc.d450qx99/downtmp/build.4qo/src/obj-x86_64-linux-gnu
Start 1: alternativesmodeltest
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so'
kf5.kio.kio_http: Can't communicate with kded_kcookiejar!
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so'
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'
kdeinit5: PID 20805 terminated.
kdeinit5: PID 20817 terminated.
kdeinit5: PID 20806 terminated.
1/2 Test #1: alternativesmodeltest ***Failed5.40 sec
* Start testing of AlternativesModelTest *
Config: Using QtTest library 5.11.1, Qt 5.11.1
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 8.2.0)
PASS   : AlternativesModelTest::initTestCase()
QDEBUG : AlternativesModelTest::runJobTest() missing mandatory argument
"destinationPath"
QDEBUG : AlternativesModelTest::runJobTest() missing mandatory argument
"destinationPath"
QWARN  : AlternativesModelTest::runJobTest() kf5.kservice.services:
KMimeTypeTrader: couldn't find service type "KParts/ReadOnlyPart"
Please ensure that the .desktop file for it is installed; then run
kbuildsycoca5.
FAIL!  : AlternativesModelTest::runJobTest() 's.count() || s.wait()'
returned FALSE. ()
   Loc:
[/tmp/autopkgtest-lxc.d450qx99/downtmp/build.4qo/src/autotests/alternativesmodeltest.cpp(74)]
PASS   : AlternativesModelTest::bigBufferTest()
PASS   : AlternativesModelTest::disablePluginTest()
PASS   : AlternativesModelTest::blacklistTest()
PASS   : AlternativesModelTest::cleanupTestCase()
Totals: 5 passed, 1 failed, 0 skipped, 0 blacklisted, 5383ms
* Finished testing of AlternativesModelTest *

Start 2: menutest
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so'
kf5.kio.kio_http: Can't communicate with kded_kcookiejar!
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher.
kdeinit5: preparing to launch

Bug#907339: qtbase-opensource-src breaks kdeconnect autopkgtest possibly due to new openssl

[Paul Gevers]

Source: qtbase-opensource-src, kdeconnect
Version: qtbase-opensource-src/5.11.1+dfsg-7
Version: kdeconnect/1.3.1-1
X-Debbugs-CC: debian...@lists.debian.org, open...@packages.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Control: block 907015 by -1

Dear maintainers,

With a recent upload of qtbase-opensource-src the autopkgtest of
kdeconnect started to fail in testing. I copied the output below.

I suspect that this regression is due to the fact that
qtbase-opensource-src was build with the 1.1.1* version of openssl which
incorporates changes regarding the default minimum level of security,
hence the CC. I suggest to discuss with the openssl maintainers how to
best fix this situation. I added a block relation on a tracking bug for
this as well.

Currently this regression is contributing to the delay of the migration
of qtbase-opensource-src to testing [1] and I assigned this bug to both
source packages (qtbase-opensource-src, kdeconnect). Could you please
investigate the situation and reassign the bug to the right package? If
needed, please change the bug's severity as appropriate. I suspect that
in the current state, you want to block migration of
qtbase-opensource-src to testing.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=qtbase-opensource-src

https://ci.debian.net/data/autopkgtest/testing/amd64/k/kdeconnect/883103/log.gz

autopkgtest [04:09:56]: test testsuite: [---
Openbox-Message: Unable to find a valid menu file
"/var/lib/openbox/debian-menu.xml"
kbuildsycoca5 running...
cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=-j1
Running tests...
/usr/bin/ctest --force-new-ctest-process -j1
Test project
/tmp/autopkgtest-lxc.at0u7euo/downtmp/build.Gev/src/obj-x86_64-linux-gnu
  Start  1: pluginloadtest
 1/10 Test  #1: pluginloadtest ...   Passed0.16 sec
  Start  2: sendfiletest
 2/10 Test  #2: sendfiletest .   Passed0.14 sec
  Start  3: networkpackettests
 3/10 Test  #3: networkpackettests ...   Passed0.01 sec
  Start  4: testsocketlinereader
 4/10 Test  #4: testsocketlinereader .   Passed0.02 sec
  Start  5: testsslsocketlinereader
 5/10 Test  #5: testsslsocketlinereader ..***Exception: Child
aborted309.65 sec
* Start testing of TestSslSocketLineReader *
Config: Using QtTest library 5.11.1, Qt 5.11.1
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 8.2.0)
PASS   : TestSslSocketLineReader::initTestCase()
FAIL!  : TestSslSocketLineReader::testTrustedDevice()
'm_clientSocket->isEncrypted()' returned FALSE. (Client is not encrypted)
   Loc:
[/tmp/autopkgtest-lxc.at0u7euo/downtmp/build.Gev/src/tests/testsslsocketlinereader.cpp(134)]

=== Received signal at function time: 30ms, total time: 309636ms,
dumping stack ===
=== End of stack trace ===
QFATAL : TestSslSocketLineReader::testUntrustedDevice() Test function
timed out
FAIL!  : TestSslSocketLineReader::testUntrustedDevice() Received a fatal
error.
   Loc: [Unknown file(0)]
Totals: 1 passed, 2 failed, 0 skipped, 0 blacklisted, 309637ms
* Finished testing of TestSslSocketLineReader *

  Start  6: kdeconnectconfigtest
 6/10 Test  #6: kdeconnectconfigtest .   Passed0.07 sec
  Start  7: lanlinkprovidertest
 7/10 Test  #7: lanlinkprovidertest ..***Failed   19.93 sec
* Start testing of LanLinkProviderTest *
Config: Using QtTest library 5.11.1, Qt 5.11.1
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 8.2.0)
QDEBUG : LanLinkProviderTest::initTestCase() kdeconnect.core: onStart
PASS   : LanLinkProviderTest::initTestCase()
QDEBUG : LanLinkProviderTest::pairedDeviceTcpPacketReceived()
kdeconnect.core: Preventing duplicate broadcasts
QDEBUG : LanLinkProviderTest::pairedDeviceTcpPacketReceived()
kdeconnect.core: Broadcasting identity packet
QDEBUG : LanLinkProviderTest::pairedDeviceTcpPacketReceived()
kdeconnect.core: Starting client ssl (but I'm the server TCP socket)
FAIL!  : LanLinkProviderTest::pairedDeviceTcpPacketReceived()
'spy3.wait()' returned FALSE. ()
   Loc:
[/tmp/autopkgtest-lxc.at0u7euo/downtmp/build.Gev/src/tests/lanlinkprovidertest.cpp(141)]
FAIL!  : LanLinkProviderTest::pairedDeviceUdpPacketReceived()
'!spy.isEmpty() || spy.wait()' returned FALSE. ()
   Loc:
[/tmp/autopkgtest-lxc.at0u7euo/downtmp/build.Gev/src/tests/lanlinkprovidertest.cpp(168)]
QDEBUG : LanLinkProviderTest::unpairedDeviceTcpPacketReceived()
kdeconnect.core: Broadcasting identity packet
QDEBUG : LanLinkProviderTest::unpairedDeviceTcpPacketReceived()
kdeconnect.core: Starting client ssl (but I'm the server TCP socket)
FAIL!  : LanLinkProviderTest::unpairedDeviceTcpPacketReceived()
'spy3.wait()' returned FALSE. ()
   Loc:

Bug#906694: purpose: autopkgtest regression

[Paul Gevers]

Source: purpose
Version: 5.49.0-1
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With the upload of 5.49.0-1 the autpkgtest of your package started to
fail in unstable and testing. I copied the output below.

Currently this regression is contributing to the delay of the migration
to testing [1]. Could you please investigate the situation and fix it?
If needed, please change the bug's severity as appropriate.

Two days ago there has been quite some uploads in the KDE stack which
triggered a lot of regressions, which seem to be resolved once all
packages were build. This regression however seems to remain, I am
totally sure if it is not merely waiting for some other package, but I
don't think so.

More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=purpose

https://ci.debian.net/data/autopkgtest/testing/amd64/p/purpose/845553/log.gz

autopkgtest [06:34:59]: test testsuite: [---
Openbox-Message: Unable to find a valid menu file
"/var/lib/openbox/debian-menu.xml"
libKF5Parts.so.5 was not found.
libKF5Plasma.so.5 was not found.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher'
kdeinit5: Launched KLauncher, pid = 20492, result = 0
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeinit5: opened connection to :99
cd obj-x86_64-linux-gnu && make -j2 test ARGS\+=-j2
Running tests...
/usr/bin/ctest --force-new-ctest-process -j2
Test project
/tmp/autopkgtest-lxc.ob13vu9y/downtmp/build.g9E/src/obj-x86_64-linux-gnu
Start 1: alternativesmodeltest
Start 2: menutest
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so'
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so'
kf5.kio.kio_http: Can't communicate with kded_kcookiejar!
kf5.kio.kio_http: Can't communicate with kded_kcookiejar!
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so'
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so'
kf5.kio.kio_http: Can't communicate with kded_kcookiejar!
kf5.kio.kio_http: Can't communicate with kded_kcookiejar!
kf5.kio.kio_file:  Couldn't rename  "/tmp/purposetest.part"  to
"/tmp/purposetest"
kdeinit5: PID 20520 terminated.
kdeinit5: PID 20531 terminated.
kdeinit5: PID 20521 terminated.
1/2 Test #2: menutest .***Failed2.50 sec
* Start testing of MenuTest *
Config: Using QtTest library 5.11.1, Qt 5.11.1
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 8.1.0)
PASS   : MenuTest::initTestCase()
QWARN  : MenuTest::runJobTest()
qrc:/org/kde/purpose/RunningJob.qml:46:16: Unable to assign ulong to double
QWARN  : MenuTest::runJobTest() kf5.kservice.services: KMimeTypeTrader:
couldn't find service type "KParts/ReadOnlyPart"
Please ensure that the .desktop file for it is installed; then run
kbuildsycoca5.
QDEBUG : MenuTest::runJobTest() job failed with error " /tmp/purposetest"
FAIL!  : MenuTest::runJobTest() Compared values are not the same
   Actual   (error): 157
   Expected (0): 0
   Loc:
[/tmp/autopkgtest-lxc.ob13vu9y/downtmp/build.g9E/src/autotests/menutest.cpp(74)]
PASS   : MenuTest::cleanupTestCase()
Totals: 2 passed, 1 failed, 0 skipped, 0 blacklisted, 2414ms
* Finished testing of MenuTest *

kdeinit5: PID 20515 terminated.
kdeinit5: PID 20513 terminated.
2/2 Test #1: alternativesmodeltest    Passed3.07 sec

50% tests passed, 1 tests failed out of 2

Total Test time (real) =   3.08 sec

The following tests FAILED:
  2 - menutest (Failed)
Errors while running CTest
make: *** [Makefile:133: test] Error 8
dh_auto_test: cd obj-x86_64-linux-gnu && make -j2 test ARGS\+=-j2
returned exit code 2
kdeinit5: PID 20530 terminated.
kdeinit5: terminate KDE.
klauncher: Exiting on signal 1
autopkgtest [06:35:04]: test testsuite: ---]



signature.asc
Description: OpenPGP digital signature

Bug#905559: Bug#902263: Affecting Qt transition

[Paul Gevers]

Dear all,

To be sure, I don't want to block/delay anything here, I just want
autopkgtests to be taken seriously. If you as the maintainer of
ktexteditor say please ignore my test for migration, who am I to say
you're wrong. However, you have also added that test for a reason.

On 06-08-18 15:33, Lisandro Damián Nicanor Pérez Meyer wrote:
> I used i, d, v, y, shift+p. I even retried them just now in case I missed 
> something.

What does idvyP (insert mode; add characters d v y P) have to do with
the failing test case? Lot's of vim code seems to go all right, there is
only 1 regression.

> I might be missing something, but at this point:
> 
> - If there is a regression:
> 
> * it would be small and can be worked around by using the normal editing
>   mode.

As long as this is the only thing, I agree with you, but if you don't
know what's wrong you don't actually know. (Albeit the amount of passing
tests says something, but once you let this one into testing, the whole
autopkgtest of ktexteditor becomes worthless until this issue is fixed
somehow).

> * odds are highly on the bug-on-kdepim side, as Qt 5.11.1 is just a patch
>   release of 5.11.0 which has been shipped in other distros for months
>   already (we skip even releases due to the fact that we need to do
>   transitions).

I don't know which package you exactly mean with kdepim as that is a
meta-package that is the same in unstable and testing since 2018-06-10.
All source packages with kdepim in the name are also the same in
unstable and testing (haven't checked binary rebuilds). But if the
package you are really referring to is the same in unstable and testing,
it can't cause the regression. Is it the same? If so, than the
regression isn't a bug there. If not, maybe we can investigate (by
testing) and check if that needs its migration blocked or delayed.

> * If the bug is in kdepim then the best way to solve it would be to psuh a
>   new version, for which we need a transition.

And delay or prevent the version in unstable from migrating to testing?
Depending on severity I guess.

> - No users have complained about this so far, and we do have lots of users 
> using unstable and reporting bugs. This has proven to be a nice regression 
> method so far ;-)

Of course.

> So I think the best way to go here is just let Qt migrate.

In 3 days that happens if we don't do anything. I'll let the RT judge if
that is worth waiting for or if migration is more urgent.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#905559: Bug#902263: Affecting Qt transition

[Paul Gevers]

Dear Lisandro,

On 06-08-18 13:35, Lisandro Damián Nicanor Pérez Meyer wrote:
> On one side Maxy told me that many autopkg tests would need fixing due to, if 
> my mind does not fails, gcc 8.

It may have slipped in, because the autopkgtests were so much broken for
a while that I didn't check carefully if a regression was in the Qt
stack. After a while, the abi-compliance check was broken in the
reference as well, so maybe regressions due to gcc are now hidden.
Luckily the abi-compliance checker is now fixed and there are very
limited regressions in the Qt stack at this moment, ktexteditor is the
only one I am aware of.

> On the other I took a look at the failed test (keys mapping in vi input mode) 
> an tried with kate on my machine running Qt 5.11 without issues, so I'm 
> suspecting the issue is indeed in the test itself.

As I have kate on my system (buster, not fully up-to-date), I tried to
reproduce the reference as it seems that the test is doing something
simple. It appears to create a sting, executes some vim commands and
checks that the outcome is as expected. So it seems unlikely to me that
this should change. To me, either the old code was doing something
weird, or the new code is doing it wrong. The test says "Vim is weird"
so it really looks like the old result is correct. Weirdly enough I get
the same results as the "new" results of the test. So I suspect I am
doing something wrong, as I should get the reference. Which keys did you
press? Do you know what they _should_ do (my vim knowledge is close to
containing only ":q").

j (one line down) V (not in the vim man but Kate says "visual line") j
(one line down) ~ (not in the vim man but Kate capitalizes the by now
two selected lines) u (undo last change)  (switch back to normal
mode, doesn't do anything AFAICT) ` (?, doesn't do anything AFAICT) [
(?, doesn't do anything AFAICT) r (replace one character at the current
position) [ (this is now inserted as the first character of the third
line for me, overwriting the x).

Paul



signature.asc
Description: OpenPGP digital signature

Bug#905559: Bug#902263: Affecting Qt transition

[Paul Gevers]

Dear all,

On 06-08-18 11:16, Niels Thykier wrote:
> Could you please confirm that the autopkgtest regression for
> ktexteditor (marked on the excuses for qtbase-opensource-src) is benign?

I believe there is a regression, at least in the autopkgtest. I filed
bug 905559 for that already.

Paul

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905559



signature.asc
Description: OpenPGP digital signature

Bug#905559: new qt stack appears to break ktexteditor autopkgtest: 65 - vimode_keys (Failed)

[Paul Gevers]

Source: ktexteditor
Version: 5.47.0-1
User: debian...@lists.debian.org
Usertags: needs-update

Dear maintainers,

After the recent qt transitions and the fixing of all the fall-out by
uploading a new version of abi-compliance-checker, the autopkgtest of
ktexteditor remains failing in unstable and testing (with either
qtdeclarative-opensource-src/5.11.1-4 or
qtbase-opensource-src/5.11.1+dfsg-6). I copied the output below. I'm
filing this bug because this seems to be a real regression, were
ktexteditor and/or its autopkgtest needs fixing.

I believe this regression is the last item delaying the migration of the
qt stack to testing. Could you please investigate the situation and if
needed reassign the bug to the right package?

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/k/ktexteditor/776729/log.gz

>>> running command  "\\:map foo l\\foorX"  on text  "xxx"
QDEBUG : KeysTest::MappingTests() Executing command directly from
ViModeTest:
 "map foo l"
foo
function() { [code] }
QDEBUG : KeysTest::MappingTests() Actual text:
 "xxx\norX"
Should be (for this test to pass):
 "abXxxx"
XFAIL  : KeysTest::MappingTests() 'map' is reserved for other stuff in
Kate command line
   Loc:
[/tmp/autopkgtest-lxc.m0shrvs8/downtmp/build.uNe/src/autotests/src/vimode/keys.cpp(439)]
QDEBUG : KeysTest::MappingTests()



signature.asc
Description: OpenPGP digital signature

Bug#904027: plasma-nm: [regression] agent isn't available after resume

[Paul Gevers]

Package: plasma-nm
Version: 4:5.13.1-1

On 2018-07-15 at 15:03:20 UTC+02 I upgraded my buster system. Since then
I am having issues with NetworkManager not being able to connect to WiFi
because the agent isn't available after resuming from suspend. I think
(but have no way to confirm) that it also failed right after the upgrade.

'''
jul 18 15:35:12 testavoira NetworkManager[13003]: 
[1531920912.6830] device (wlp2s0): No agents were available for this
request.
'''

I am told that that the desktop should be the one providing the service
in the desktop session (I hope I phrase this correctly). So I think that
should be provided by plasma-nm, no idea how all this works as plasma-nm
wasn't even upgraded in that run.

Since then I have been writing my network password via $(nmcli agent)
but that is rather annoying.

Please reassign this bug elsewhere if you know where the issue is.
Please contact me if you need more information or debugging effort from
my side.

Paul

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (200,
'testing'), (50, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.16.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-nm depends on:
ii  kio 5.47.0-1
ii  libc6   2.27-3
ii  libkf5completion5   5.47.0-1
ii  libkf5configcore5   5.47.0-1
ii  libkf5configwidgets55.47.0-1
ii  libkf5coreaddons5   5.47.0-1
ii  libkf5dbusaddons5   5.47.0-1
ii  libkf5declarative5  5.47.0-1
ii  libkf5i18n5 5.47.0-1
ii  libkf5iconthemes5   5.47.0-1
ii  libkf5kdelibs4support5  5.47.0-1
ii  libkf5kiowidgets5   5.47.0-1
ii  libkf5modemmanagerqt6   5.47.0-1
ii  libkf5networkmanagerqt6 5.47.0-1
ii  libkf5notifications55.47.0-1
ii  libkf5service-bin   5.47.0-1
ii  libkf5service5  5.47.0-1
ii  libkf5solid55.47.0-1
ii  libkf5wallet-bin5.47.0-1
ii  libkf5wallet5   5.47.0-1
ii  libkf5widgetsaddons55.47.0-1
ii  libkf5windowsystem5 5.47.0-1
ii  libopenconnect5 7.08-3
ii  libqca-qt5-22.1.3-2
ii  libqt5core5a5.10.1+dfsg-7
ii  libqt5dbus5 5.10.1+dfsg-7
ii  libqt5gui5  5.10.1+dfsg-7
ii  libqt5network5  5.10.1+dfsg-7
ii  libqt5qml5  5.10.1-4
ii  libqt5quick55.10.1-4
ii  libqt5widgets5  5.10.1+dfsg-7
ii  libqt5xml5  5.10.1+dfsg-7
ii  libstdc++6  8.1.0-9
ii  mobile-broadband-provider-info  20170903-1
ii  network-manager 1.12.0-4
ii  plasma-framework5.47.0-1
ii  qml-module-org-kde-kcoreaddons  5.47.0-1

plasma-nm recommends no packages.

Versions of packages plasma-nm suggests:
pn  network-manager-openconnect  
pn  network-manager-openvpn  
pn  network-manager-pptp 
pn  network-manager-vpnc 

-- no debconf information


Start-Date: 2018-07-01  20:26:52
Commandline: apt dist-upgrade
Requested-By: paul (1000)
Install: cryptsetup-initramfs:amd64 (2:2.0.3-4, automatic), 
libfribidi-dev:amd64 (0.19.7-2, automatic), cryptsetup-run:amd64 (2:2.0.3-4, 
automatic), python3-blends:amd64 (0.7.0, automatic), python3-psycopg2:amd64 
(2.7.5-1+b1, automatic)
Upgrade: speech-dispatcher-espeak-ng:amd64 (0.8.8-1, 0.8.8-5), 
speech-dispatcher-audio-plugins:amd64 (0.8.8-1, 0.8.8-5), 
libkf5notifications-data:amd64 (5.46.0-1, 5.47.0-1), cryptsetup-bin:amd64 
(2:2.0.2-1, 2:2.0.3-4), libkf5kiowidgets5:amd64 (5.46.0-1, 5.47.0-1), 
libgcc-7-dev:amd64 (7.3.0-21, 7.3.0-24), libx265-160:amd64 (2.8-3, 2.8-4), 
firebird3.0-server-core:amd64 (3.0.3.32900.ds4-3+b1, 3.0.3.32900.ds4-4), 
libsoup-gnome2.4-1:amd64 (2.62.1-1, 2.62.2-2), libkf5krosscore5:amd64 
(5.46.0-1, 5.47.0-1), libkf5xmlrpcclient-data:amd64 (5.46.0-1, 5.47.0-1), 
libguestfs-hfsplus:amd64 (1:1.38.1-1, 1:1.38.1-1+b1), 
qml-module-org-kde-kquickcontrolsaddons:amd64 (5.46.0-1, 5.47.0-1), 
kactivities-bin:amd64 (5.46.0-1, 5.47.0-1), libkf5kdelibs4support5:amd64 
(5.46.0-1, 5.47.0-1), qml-module-org-kde-kquickcontrols:amd64 (5.46.0-1, 
5.47.0-1), libwin-hivex-perl:amd64 (1.3.15-1+b1, 1.3.15-1+b2), 
libkf5kdelibs4support-data:amd64 (5.46.0-1, 5.47.0-1), libkf5texteditor5:amd64 
(5.46.0-1, 5.47.0-1), libkf5config-data:amd64 (5.46.0-1, 5.47.0-1), 
libkf5purpose-bin:amd64 (5.46.0-1, 5.47.0-1), libkf5idletime5:amd64 (5.46.0-1, 
5.47.0-1), libpython3.6-minimal:amd64 (3.6.6~rc1-4, 3.6.6-1), 
libservlet3.1-java:amd64 (8.5.31-1, 8.5.32-1), libkf5attica5:amd64 (5.46.0-1, 

Bug#903314: kwayland: flaky autopkgtest: kwayland-testPlasmaWindowModel Exception: SIGPIPE

[Paul Gevers]

Source: plasma-framework
Version: 4:5.47.0-1
Severity: important
User: debian...@lists.debian.org
Usertags: flaky

While inspecting regressions in autopkgtest results¹, I noticed that
your package failed multiple times² without apparent changes and passed
later again. I think all cases had the error that I copied below. The
last regression was involved in delaying the migration of glibc.

Could you please investigate and make your autopkgtest more robust?
Please contact me if you need help and you think I can provide that (I
am not subscribed to this bug).

Recent discussion of gating migration by autopkgtests on debian-devel³
noted that if this is going to work, and in particular if we are going
to *block* migration when it causes autopkgtest regressions rather than
merely delaying it, intermittent autopkgtest failures are likely to have
to be considered RC due to their impact on the tested package's
dependencies; for now I've filed it as important.

Paul

¹ https://ci.debian.net/packages/k/kwayland
²
https://ci.debian.net/data/autopkgtest/testing/amd64/k/kwayland/576520/log.gz
https://ci.debian.net/data/autopkgtest/unstable/amd64/k/kwayland/490414/log.gz
https://ci.debian.net/data/autopkgtest/unstable/amd64/k/kwayland/565583/log.gz
https://ci.debian.net/data/autopkgtest/unstable/amd64/k/kwayland/560563/log.gz
https://ci.debian.net/data/autopkgtest/unstable/amd64/k/kwayland/01/log.gz
³ https://lists.debian.org/debian-devel/2018/05/msg00061.html

https://ci.debian.net/data/autopkgtest/testing/amd64/k/kwayland/576520/log.gz

25/41 Test #25: kwayland-testPlasmaWindowModel
.***Exception: SIGPIPE 14.55 sec
* Start testing of PlasmaWindowModelTest *
Config: Using QtTest library 5.10.1, Qt 5.10.1
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 7.3.0)
PASS   : PlasmaWindowModelTest::initTestCase()
PASS   : PlasmaWindowModelTest::testRoleNames(display)
PASS   : PlasmaWindowModelTest::testRoleNames(decoration)
PASS   : PlasmaWindowModelTest::testRoleNames(AppId)
PASS   : PlasmaWindowModelTest::testRoleNames(Pid)
PASS   : PlasmaWindowModelTest::testRoleNames(IsActive)
PASS   : PlasmaWindowModelTest::testRoleNames(IsFullscreenable)
PASS   : PlasmaWindowModelTest::testRoleNames(IsFullscreen)
PASS   : PlasmaWindowModelTest::testRoleNames(IsMaximizable)
PASS   : PlasmaWindowModelTest::testRoleNames(IsMaximized)
PASS   : PlasmaWindowModelTest::testRoleNames(IsMinimizable)
PASS   : PlasmaWindowModelTest::testRoleNames(IsMinimized)
PASS   : PlasmaWindowModelTest::testRoleNames(IsKeepAbove)
PASS   : PlasmaWindowModelTest::testRoleNames(IsKeepBelow)
PASS   : PlasmaWindowModelTest::testRoleNames(VirtualDesktop)
PASS   : PlasmaWindowModelTest::testRoleNames(IsOnAllDesktops)
PASS   : PlasmaWindowModelTest::testRoleNames(IsDemandingAttention)
PASS   : PlasmaWindowModelTest::testRoleNames(SkipTaskbar)
PASS   : PlasmaWindowModelTest::testRoleNames(SkipSwitcher)
PASS   : PlasmaWindowModelTest::testRoleNames(IsShadeable)
PASS   : PlasmaWindowModelTest::testRoleNames(IsShaded)
PASS   : PlasmaWindowModelTest::testRoleNames(IsMovable)
PASS   : PlasmaWindowModelTest::testRoleNames(IsResizable)
PASS   : PlasmaWindowModelTest::testRoleNames(IsVirtualDesktopChangeable)
PASS   : PlasmaWindowModelTest::testRoleNames(IsCloseable)
PASS   : PlasmaWindowModelTest::testRoleNames(Geometry)
PASS   : PlasmaWindowModelTest::testAddRemoveRows()
PASS   : PlasmaWindowModelTest::testDefaultData(display)
PASS   : PlasmaWindowModelTest::testDefaultData(decoration)
PASS   : PlasmaWindowModelTest::testDefaultData(AppId)
PASS   : PlasmaWindowModelTest::testDefaultData(IsActive)
PASS   : PlasmaWindowModelTest::testDefaultData(IsFullscreenable)
PASS   : PlasmaWindowModelTest::testDefaultData(IsFullscreen)
PASS   : PlasmaWindowModelTest::testDefaultData(IsMaximizable)
PASS   : PlasmaWindowModelTest::testDefaultData(IsMaximized)
PASS   : PlasmaWindowModelTest::testDefaultData(IsMinimizable)
PASS   : PlasmaWindowModelTest::testDefaultData(IsMinimized)
PASS   : PlasmaWindowModelTest::testDefaultData(IsKeepAbove)
PASS   : PlasmaWindowModelTest::testDefaultData(IsKeepBelow)
PASS   : PlasmaWindowModelTest::testDefaultData(VirtualDesktop)
PASS   : PlasmaWindowModelTest::testDefaultData(IsOnAllDesktops)
PASS   : PlasmaWindowModelTest::testDefaultData(IsDemandingAttention)
PASS   : PlasmaWindowModelTest::testDefaultData(IsShadeable)
PASS   : PlasmaWindowModelTest::testDefaultData(IsShaded)
PASS   : PlasmaWindowModelTest::testDefaultData(SkipTaskbar)
PASS   : PlasmaWindowModelTest::testDefaultData(IsMovable)
PASS   : PlasmaWindowModelTest::testDefaultData(IsResizable)
PASS   : PlasmaWindowModelTest::testDefaultData(IsVirtualDesktopChangeable)
PASS   : PlasmaWindowModelTest::testDefaultData(IsCloseable)
PASS   : PlasmaWindowModelTest::testDefaultData(Geometry)
PASS   : PlasmaWindowModelTest::testDefaultData(Pid)
PASS   : PlasmaWindowModelTest::testIsActive()
PASS   : PlasmaWindowModelTest::testIsFullscreenable()
PASS   : 

Bug#902850: plasma-framework: flaky autopkgtest: DialogNativeTest::position() Compared values are not the same

[Paul Gevers]

Source: plasma-framework
Version: 5.46.0-1
Severity: important
User: debian...@lists.debian.org
Usertags: flaky

While inspecting regressions in autopkgtest results¹, I noticed that
your package failed multiple times²³ without apparent changes and passed
later again. I think all cases had the error that I copied below. The
last regression was involved in delaying the migration of xorg-server.

Could you please investigate and make your autopkgtest more robust?
Please contact me if you need help and you think I can provide that (I
am not subscribed to this bug).

Recent discussion of gating migration by autopkgtests on debian-devel⁶
noted that if this is going to work, and in particular if we are going
to *block* migration when it causes autopkgtest regressions rather than
merely delaying it, intermittent autopkgtest failures are likely to have
to be considered RC due to their impact on the tested package's
dependencies; for now I've filed it as important.

Paul

¹ https://ci.debian.net/packages/p/plasma-framework/testing/amd64/
²
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/plasma-framework/479454/log.gz
³
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/plasma-framework/386329/log.gz
⁴
https://ci.debian.net/data/autopkgtest/testing/amd64/p/plasma-framework/541592/log.gz
⁵ https://lists.debian.org/debian-devel/2018/05/msg00061.html

https://ci.debian.net/data/autopkgtest/testing/amd64/p/plasma-framework/541592/log.gz

11/14 Test #11: dialognativetest .***Failed0.41 sec
* Start testing of DialogNativeTest *
Config: Using QtTest library 5.10.1, Qt 5.10.1
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 7.3.0)
QWARN  : DialogNativeTest::initTestCase() kf5.kcoreaddons.kdirwatch:
Cannot watch QRC-like path ":/icons/hicolor/index.theme"
PASS   : DialogNativeTest::initTestCase()
PASS   : DialogNativeTest::size()
FAIL!  : DialogNativeTest::position() Compared values are not the same
   Actual   (m_dialog->y()): 0
   Expected (49)   : 49
   Loc:
[/tmp/autopkgtest-lxc.a5u4pbl8/downtmp/build.YAX/src/autotests/dialognativetest.cpp(96)]
PASS   : DialogNativeTest::cleanupTestCase()
Totals: 3 passed, 1 failed, 0 skipped, 0 blacklisted, 355ms
* Finished testing of DialogNativeTest *



signature.asc
Description: OpenPGP digital signature

Bug#902844: baloo-kf5: flaky autopkgtest

[Paul Gevers]

Source: baloo-kf5
Version: 5.46.0-1
Severity: important
User: debian...@lists.debian.org
Usertags: flaky

While inspecting regressions in autopkgtest results¹, I noticed that
your package failed multiple times²³⁴⁵ without apparent changes and
passed later again. I spotted at least to two errors that I copied
below, but they are not always together, and there may be more. The last
regression was involved in delaying the migration of xorg-server.

Could you please investigate and make your autopkgtest more robust?
Please contact me if you need help and you think I can provide that (I
am not subscribed to this bug).

Recent discussion of gating migration by autopkgtests on debian-devel⁶
noted that if this is going to work, and in particular if we are going
to *block* migration when it causes autopkgtest regressions rather than
merely delaying it, intermittent autopkgtest failures are likely to have
to be considered RC due to their impact on the tested package's
dependencies; for now I've filed it as important.

Paul

¹ https://ci.debian.net/packages/b/baloo-kf5/testing/amd64/
²
https://ci.debian.net/data/autopkgtest/unstable/amd64/b/baloo-kf5/497552/log.gz
³
https://ci.debian.net/data/autopkgtest/unstable/amd64/b/baloo-kf5/479452/log.gz
⁴
https://ci.debian.net/data/autopkgtest/unstable/amd64/b/baloo-kf5/451349/log.gz
⁵
https://ci.debian.net/data/autopkgtest/testing/amd64/b/baloo-kf5/541452/log.gz
⁶ https://lists.debian.org/debian-devel/2018/05/msg00061.html

https://ci.debian.net/data/autopkgtest/testing/amd64/b/baloo-kf5/541452/log.gz

23/37 Test  #4: querytest ***Failed0.08 sec
* Start testing of QueryTest *
Config: Using QtTest library 5.10.1, Qt 5.10.1
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 7.3.0)
PASS   : QueryTest::initTestCase()
PASS   : QueryTest::testTermEqual()
PASS   : QueryTest::testTermStartsWith()
PASS   : QueryTest::testTermAnd()
FAIL!  : QueryTest::testTermOr() Compared values are not the same
   Loc:
[/tmp/autopkgtest-lxc.fx7kbu5r/downtmp/build.XfS/src/autotests/integration/querytest.cpp(149)]
PASS   : QueryTest::testTermPhrase()
PASS   : QueryTest::cleanupTestCase()
Totals: 6 passed, 1 failed, 0 skipped, 0 blacklisted, 76ms
* Finished testing of QueryTest *

31/37 Test #28: fileindexerconfigtest ***Failed0.31 sec
* Start testing of Baloo::Test::FileIndexerConfigTest *
Config: Using QtTest library 5.10.1, Qt 5.10.1
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 7.3.0)

--%<-

QWARN  :
Baloo::Test::FileIndexerConfigTest::testShouldFolderBeIndexedHidden(d1)
Failed enumerating UDisks2 objects:
"org.freedesktop.DBus.Error.ServiceUnknown"
 "The name org.freedesktop.UDisks2 was not provided by any .service files"
FAIL!  :
Baloo::Test::FileIndexerConfigTest::testShouldFolderBeIndexedHidden(d1)
Compared values are not the same
   Actual   (cfg->shouldFolderBeIndexed(path)): 0
   Expected (shouldBeIndexed) : 1
   Loc:
[/tmp/autopkgtest-lxc.fx7kbu5r/downtmp/build.XfS/src/autotests/unit/file/fileindexerconfigtest.cpp(203)]

--%<-

Totals: 93 passed, 1 failed, 0 skipped, 0 blacklisted, 294ms
* Finished testing of Baloo::Test::FileIndexerConfigTest *



signature.asc
Description: OpenPGP digital signature

Re: new version of systemd seems to break autopkgtests of policykit-1, kwin and python-dbusmock

[Paul Gevers]

Hi systemd and kwin maintainers,

On 23-06-18 14:38, Paul Gevers wrote:
>> The breakage in kwin looks unrelated to me (maybe caused by the libinput
>> update, dunno).
> 
> To avoid any doubt, I have triggered a reference run, with only testing
> (results in a hour or so). But the last successful run was on 19 June
> and had libinput 1.10.7-1, which is the same version that systemd was
> tested with. I checked the log of the systemd run, and nothing spurious
> was installed from unstable, only the systemd binaries. On the other
> hand, the test for libinput 1.11.1-1 had the same issue, and also there
> no spurious packages from unstable were installed. So I fear we already
> regressed testing and the systemd maintainers can further ignore the
> kwin failure.

The reference run of kwin in testing passed¹. Really the only delta I
can spot, before and after the build (apparently the order of output can
vary), is the version of systemd's binary packages.

@kwin maintainers, do you have any idea how the libinput run and the
systemd run can fail in seemingly the same way, while it seems that both
runs were done with all binaries from testing (where a pure testing run
passes) and only their own respective binaries from unstable.

Paul

¹ https://ci.debian.net/data/autopkgtest/testing/amd64/k/kwin/498051/log.gz



signature.asc
Description: OpenPGP digital signature

Re: new version of systemd seems to break autopkgtests of policykit-1, kwin and python-dbusmock

[Paul Gevers]

Hi Michael,

On 23-06-18 13:44, Michael Biebl wrote:
> you are quick!

YW.

> Am 23.06.2018 um 13:30 schrieb Paul Gevers:

> I already tracked down the reason for the policykit-1 failure

Great, you're quick. ;)

> and it is
> indeed a regression/behaviour change in systemd. Another affected
> package is avahi-daemon (which also uses systemctl unmask --runtime),
> unfortunately it doesn't have an autopkgtest yet.
> 
> Yay for autopkgtests!

Indeed.

> We already have another, unrelated RC bug in systemd which will prevent
> testing migration for now.

I noticed. That was the major reason why I didn't want to file another
one just yet.

> The breakage in kwin looks unrelated to me (maybe caused by the libinput
> update, dunno).

To avoid any doubt, I have triggered a reference run, with only testing
(results in a hour or so). But the last successful run was on 19 June
and had libinput 1.10.7-1, which is the same version that systemd was
tested with. I checked the log of the systemd run, and nothing spurious
was installed from unstable, only the systemd binaries. On the other
hand, the test for libinput 1.11.1-1 had the same issue, and also there
no spurious packages from unstable were installed. So I fear we already
regressed testing and the systemd maintainers can further ignore the
kwin failure.

Paul



signature.asc
Description: OpenPGP digital signature

new version of systemd seems to break autopkgtests of policykit-1, kwin and python-dbusmock

[Paul Gevers]

Dear systemd maintainers, all,

With the upload of version 239-1 of systemd the autopkgtests of the
policykit-1, kwin and python-dbusmock started to fail¹.

It appear that policykit-1 fails to install since the 239-1 version of
systemd with (in the unstable test run, in the testing test run as well
as in the python-dbusmock test run):
Setting up policykit-1 (0.105-20) ...
--runtime cannot be used with unmask
dpkg: error processing package policykit-1 (--configure):
 installed policykit-1 package post-installation script subprocess
returned error exit status 1
dpkg: dependency problems prevent configuration of autopkgtest-satdep:
 autopkgtest-satdep depends on policykit-1; however:
  Package policykit-1 is not configured yet.

This looks very serious to me, can you, together with the maintainers of
the failing packages (which I CC'ed), please investigate if the failure
is really caused by systemd or if policykit-1 needs updating. In the
latter case, I think a "Breaks" in systemd is very much justified.
(Please let me know when this happens, I may have to help autopkgtest a
bit due to bug #896023).

In the kwin case, it is currently failing in unstable for some time
already and detected regressions in quite some packages in the KDE
stack, but the error in this test is different:
FAIL!  : KeyboardLayoutTest::testWindowPolicy() Compared values are not
the same
   Actual   (((xkb->layoutName(



 : "English (US)"
   Expected (([]() noexcept -> QString { enum { Size = sizeof(u""
"German")/2 - 1 }; static const QStaticStringData qstring_literal
= { { { { -1 } }, Size, 0, 0, sizeof(QStringData) }, u"" "German" };
QStringDataPtr holder = { qstring_literal.data_ptr() }; const QString
qstring_literal_temp(holder); return qstring_literal_temp; }())): "German"
   Loc:
[/tmp/autopkgtest-lxc.53qdzf_7/downtmp/build.4ZO/src/autotests/integration/keyboard_layout_test.cpp(393)]

More information about this email and the reason of it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Let me know if you need my help. Thanks for considering

Paul

¹ https://qa.debian.org/excuses.php?package=systemd



signature.asc
Description: OpenPGP digital signature

Re: kwin autopkgtest fails in unstable since 2018-05-26 and regresses 24 kde package

[Paul Gevers]

Dear KDE maintainers,

[tl;dr: I don't think xorg-server and/or mesa caused the regression in
kwin]

On 18-06-18 15:25, Paul Gevers wrote:
> On 18-06-18 15:17, Paul Gevers wrote:
>> Because all but the last source package appear to come from the kde
>> suite, I checked the last log⁴. The installation was clean, in the sense
>> that no fall-backs occurred and only packages from xorg-server were
>> installed from unstable. It appears that xorg-server is introducing
>> regressions in the autopkgtest of kwin. How bad is this?
> 
> May this be related to
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900352
> ? If yes, I'll shut up.

I ran a test where I tried to filter out and prevent xorg* and mesa
related packages from unstable¹. It still failed. This either means that
the KDE stack introduced this regression itself, or one of the still not
filtered packages from unstable cause the issue. If your interested,
could you check which packages from unstable in that log you would want
to have from testing instead to have a fair test? (Right at the top
you'll see which packages I specified that should be taken from unstable
if they are going to be installed.)

In the mean time, I have started creating a more up-to-date set of
references for all packages in testing. As a result it may *appear* that
there are now more packages in the KDE stack that seem to regress with
the latest KDE stack upload (e.g. krunner, kservice and
plasma-framework). However, I suspect that that may be because these
packages were only tested during the uploading phase, when not all
packages were build yet. I have (and will continue to if new regressions
appear) retriggered those tests.

Thanks for considering.

Paul

¹ https://ci.debian.net/data/autopkgtest/testing/amd64/k/kwin/489052/log.gz



signature.asc
Description: OpenPGP digital signature

Bug#902039: kate4: autopkgtest regularly times out

[Paul Gevers]

Source: kate4
Version: 4:4.14.3-4
User: debian...@lists.debian.org
Usertags: timeout

Dear maintainer,

Your package has an autopkgtest. Great. However, I noticed it sometimes
is on the list of slow tests (it takes more than an hour on the
ci.debian.net infrastructure, which is in principle fine as long as it
has a purpose). I took a quick look and noticed that the test regularly
times out (> 200 times in 2 years; after ~2:47 hours). This rather puts
unnecessary stress on the infrastructure. What is more, when you fix the
regression test to pass again under normal circumstances, if the
time-out issue isn't solved, this will make your test flaky.

Could you please investigate and prevent the test from timing out? In
the absence of a solution, I think you should rather disable the test,
as the last time it ran successfully was 2016-06-18. Fixing the test to
pass again would be very nice.

Thanks for considering.

Paul

PS: most recent test log with time out:
https://ci.debian.net/data/autopkgtest/unstable/amd64/k/kate4/487150/log.gz



signature.asc
Description: OpenPGP digital signature

Re: kwin autopkgtest fails in unstable since 2018-05-26 and regresses 24 kde package

[Paul Gevers]

Hi

On 18-06-18 15:17, Paul Gevers wrote:
> Because all but the last source package appear to come from the kde
> suite, I checked the last log⁴. The installation was clean, in the sense
> that no fall-backs occurred and only packages from xorg-server were
> installed from unstable. It appears that xorg-server is introducing
> regressions in the autopkgtest of kwin. How bad is this?

May this be related to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900352
? If yes, I'll shut up.

Paul



signature.asc
Description: OpenPGP digital signature

Re: kwin autopkgtest fails in unstable since 2018-05-26 and regresses 24 kde package

[Paul Gevers]

[Resending with a better e-mail address for xorg-server]

Dear KDE maintainers, dear xorg-server maintainers

On 18-06-18 11:20, Paul Gevers wrote:
> The autopkgtest of kwin¹ started failing in unstable on 2018-05-26 with
> the errors copied below. Unfortunately the migration software triggered
> tests in testing² did not catch the culprit as there are currently 24
> KDE packages that are said to cause regression (I'll retrigger all of
> them as some may still be hanging in there from the mass upload of
> several days ago, however it will be some hours before the results are
> in due to the long testtime of kwin).

Retrying them all reduced the set to 22 packages:
kactivities-kf5
kauth
kcompletion
kconfig
kconfigwidgets
kcoreaddons
kcrash
kdeclarative
kglobalaccel
ki18n
kiconthemes
kio
knewstuff
knotifications
kpackage
kservice
ktextwidgets
kwayland
kwidgetsaddons
kwindowsystem
kxmlgui
xorg-server

Because all but the last source package appear to come from the kde
suite, I checked the last log⁴. The installation was clean, in the sense
that no fall-backs occurred and only packages from xorg-server were
installed from unstable. It appears that xorg-server is introducing
regressions in the autopkgtest of kwin. How bad is this?

Paul

⁴ https://ci.debian.net/data/autopkgtest/testing/amd64/k/kwin/472335/log.gz





signature.asc
Description: OpenPGP digital signature

Re: kwin autopkgtest fails in unstable since 2018-05-26 and regresses 24 kde package

[Paul Gevers]

Dear KDE maintainers, dear xorg-server maintainers

On 18-06-18 11:20, Paul Gevers wrote:
> The autopkgtest of kwin¹ started failing in unstable on 2018-05-26 with
> the errors copied below. Unfortunately the migration software triggered
> tests in testing² did not catch the culprit as there are currently 24
> KDE packages that are said to cause regression (I'll retrigger all of
> them as some may still be hanging in there from the mass upload of
> several days ago, however it will be some hours before the results are
> in due to the long testtime of kwin).

Retrying them all reduced the set to 22 packages:
kactivities-kf5
kauth
kcompletion
kconfig
kconfigwidgets
kcoreaddons
kcrash
kdeclarative
kglobalaccel
ki18n
kiconthemes
kio
knewstuff
knotifications
kpackage
kservice
ktextwidgets
kwayland
kwidgetsaddons
kwindowsystem
kxmlgui
xorg-server

Because all but the last source package appear to come from the kde
suite, I checked the last log⁴. The installation was clean, in the sense
that no fall-backs occurred and only packages from xorg-server were
installed from unstable. It appears that xorg-server is introducing
regressions in the autopkgtest of kwin. How bad is this?

Paul

⁴ https://ci.debian.net/data/autopkgtest/testing/amd64/k/kwin/472335/log.gz



signature.asc
Description: OpenPGP digital signature

Bug#901734: /usr/bin/plasmashell: recently taskbar becames unreadable after some time of use

[Paul Gevers]

Hi Maximiliano,

On 18-06-18 14:22, Maximiliano Curia wrote:
> I would suspect that this is related to a change in xorg 1.20, maybe the
> change to DRI3 by default in some video drivers (including modesetting).
> 
> I haven't seen this behaviour, though (using modesetting + intel).
> 
> What video card are you using?

If you don't mean this from $(lspci), which command should I run?:
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Kabini [Radeon HD 8240 / R3 Series]

Paul



signature.asc
Description: OpenPGP digital signature

kwin autopkgtest fails in unstable since 2018-05-26 and regresses 24 kde package

[Paul Gevers]

Dear KDE maintainers,

The autopkgtest of kwin¹ started failing in unstable on 2018-05-26 with
the errors copied below. Unfortunately the migration software triggered
tests in testing² did not catch the culprit as there are currently 24
KDE packages that are said to cause regression (I'll retrigger all of
them as some may still be hanging in there from the mass upload of
several days ago, however it will be some hours before the results are
in due to the long testtime of kwin). I manually tried to figure it out
by looking at the history, but I wasn't able to find the root cause either.

Could you please help investigate what is wrong and help assign a bug to
the right package? Either to fix the autopkgtest of kwin, adapt kwin to
the new situation, or assign a bug to the appropriate package.

Please also note that it is possible that the test fails unreproducible
(i.e. it is flaky). If that is the case, the prefered solution is to fix
it of course. If that turns out to be difficult, bug 851558 is pending,
which enables a package to define a test as flaky. Until the next
version of autopkgtest is uploaded and deployed, I have the authority to
instruct the migration software to ignore the failing results from kwin
if you let me know.

By the way, are you sure you can't easily avoid the build of the source
before running the test? The autopkgtest takes typically more than one
hour on the ci.debian.net infrastructure (that is why I looked into
this), which is considered rather long. Most of that time is used for
building the package. Of course it's fine if it is really needed.

Thanks for maintaining KDE in Debian.

Paul

¹ https://ci.debian.net/packages/k/kwin/unstable/amd64/
² https://wiki.debian.org/ContinuousIntegration/DebianSetup
³ https://bugs.debian.org/851558

https://ci.debian.net/data/autopkgtest/unstable/amd64/k/kwin/471660/log.gz

 90/122 Test  #90: kwin-testMoveResize
.***Failed0.43 sec
* Start testing of KWin::MoveResizeWindowTest *
Config: Using QtTest library 5.10.1, Qt 5.10.1
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 7.3.0)
X-Server started on display :0
QWARN  : KWin::MoveResizeWindowTest::initTestCase()
kf5.kcoreaddons.desktopparser: Property type "Url" is not a known
QVariant type. Found while parsing property definition for
"X-KWin-Video-Url" in "/usr/share/kservicetypes5/kwineffect.desktop"
PASS   : KWin::MoveResizeWindowTest::initTestCase()
XFAIL  : KWin::MoveResizeWindowTest::testMove() First event is ignored
   Loc:
[/tmp/autopkgtest-lxc.uqkvy7vz/downtmp/build.8Sb/src/autotests/integration/move_resize_window_test.cpp(169)]
PASS   : KWin::MoveResizeWindowTest::testMove()
PASS   : KWin::MoveResizeWindowTest::testResize()
PASS   : KWin::MoveResizeWindowTest::testPackTo(left)
PASS   : KWin::MoveResizeWindowTest::testPackTo(up)
PASS   : KWin::MoveResizeWindowTest::testPackTo(right)
PASS   : KWin::MoveResizeWindowTest::testPackTo(down)
PASS   : KWin::MoveResizeWindowTest::testPackAgainstClient(left)
PASS   : KWin::MoveResizeWindowTest::testPackAgainstClient(up)
PASS   : KWin::MoveResizeWindowTest::testPackAgainstClient(right)
PASS   : KWin::MoveResizeWindowTest::testPackAgainstClient(down)
PASS   : KWin::MoveResizeWindowTest::testGrowShrink(grow vertical)
PASS   : KWin::MoveResizeWindowTest::testGrowShrink(grow horizontal)
PASS   : KWin::MoveResizeWindowTest::testGrowShrink(shrink vertical)
PASS   : KWin::MoveResizeWindowTest::testGrowShrink(shrink horizontal)
PASS   : KWin::MoveResizeWindowTest::testPointerMoveEnd(BTN_RIGHT)
PASS   : KWin::MoveResizeWindowTest::testPointerMoveEnd(BTN_MIDDLE)
PASS   : KWin::MoveResizeWindowTest::testPointerMoveEnd(BTN_SIDE)
PASS   : KWin::MoveResizeWindowTest::testPointerMoveEnd(BTN_EXTRA)
PASS   : KWin::MoveResizeWindowTest::testPointerMoveEnd(BTN_FORWARD)
PASS   : KWin::MoveResizeWindowTest::testPointerMoveEnd(BTN_BACK)
PASS   : KWin::MoveResizeWindowTest::testPointerMoveEnd(BTN_TASK)
PASS   : KWin::MoveResizeWindowTest::testPointerMoveEnd(118)
PASS   : KWin::MoveResizeWindowTest::testPointerMoveEnd(119)
PASS   : KWin::MoveResizeWindowTest::testPointerMoveEnd(11a)
PASS   : KWin::MoveResizeWindowTest::testPointerMoveEnd(11b)
PASS   : KWin::MoveResizeWindowTest::testPointerMoveEnd(11c)
PASS   : KWin::MoveResizeWindowTest::testPointerMoveEnd(11d)
PASS   : KWin::MoveResizeWindowTest::testPointerMoveEnd(11e)
PASS   : KWin::MoveResizeWindowTest::testPointerMoveEnd(11f)
PASS   : KWin::MoveResizeWindowTest::testClientSideMove(wlShell)
PASS   : KWin::MoveResizeWindowTest::testClientSideMove(xdgShellV5)
PASS   : KWin::MoveResizeWindowTest::testClientSideMove(xdgShellV6)
PASS   : KWin::MoveResizeWindowTest::testPlasmaShellSurfaceMovable(normal)
PASS   : KWin::MoveResizeWindowTest::testPlasmaShellSurfaceMovable(desktop)
PASS   : KWin::MoveResizeWindowTest::testPlasmaShellSurfaceMovable(panel)
PASS   : KWin::MoveResizeWindowTest::testPlasmaShellSurfaceMovable(osd)
QWARN  : 

Bug#901746: kirigami2: versioned depends on extra-cmake-modules too low and broken autopkgtest

[Paul Gevers]

Source: kirigami2
Version: 5.47.0-1
User: debian...@lists.debian.org
Usertags: regression

The autopkgtest run of kirigami2¹ that was triggered by the migration
software failed. Looking at the log file, I see that the build of
kirigami2 failed with the error copied at the bottom of this report.

I don't know cmake, but is seems to suggest the Build-Depends on
extra-cmake-modules should be bumped to 5.47.0~.

Your package is currently being delayed from migration to testing by 13
days (15 now, while with a passing test it would be 2).

Just a note, I hope you read the note about the "build-needed"
restriction carefully as the intention of autopkgtest is to test
as-installed packages:

Please use this considerately, as for large builds it unnecessarily
builds the entire project when you only need a tiny subset (like the
tests/ subdirectory). It is often possible to run ``make -C tests``
instead, or copy the test code to ``$AUTOPKGTEST_TMP`` and build it
there with some custom commands. This cuts down the load on the
Continuous Integration servers and also makes tests more robust as
it prevents accidentally running them against the built source tree
instead of the installed packages.

Oh, and the irony, a successful test doesn't seem to test anything:

autopkgtest [14:01:24]: test testsuite: [---
Openbox-Message: Unable to find a valid menu file
"/var/lib/openbox/debian-menu.xml"
cd obj-x86_64-linux-gnu && make -j2 test ARGS\+=-j2
Running tests...
/usr/bin/ctest --force-new-ctest-process -j2
Test project
/tmp/autopkgtest-lxc.yk37kd2b/downtmp/build.K2H/src/obj-x86_64-linux-gnu
No tests were found!!!
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":99"
  after 837 requests (837 known processed) with 0 events remaining.
autopkgtest [14:01:30]: test testsuite: ---]
autopkgtest [14:01:30]: test testsuite:  - - - - - - - - - - results - -
- - - - - - - -
testsuitePASS

From:
https://ci.debian.net/data/autopkgtest/unstable/amd64/k/kirigami2/468227/log.gz

Could you please fix your autopkgtest.

Paul

¹
https://ci.debian.net/data/autopkgtest/testing/amd64/k/kirigami2/466107/log.gz

CMake Warning at CMakeLists.txt:51 (find_package):
  Could not find a configuration file for package "ECM" that is compatible
  with requested version "5.47.0".

  The following configuration files were considered but not accepted:

/usr/share/ECM/cmake/ECMConfig.cmake, version: 5.46.0



CMake Error at CMakeLists.txt:58 (include):
  include could not find load file:

ECMSetupVersion


CMake Error at CMakeLists.txt:59 (include):
  include could not find load file:

ECMGenerateHeaders


CMake Error at CMakeLists.txt:61 (include):
  include could not find load file:

ECMPoQmTools


CMake Error at CMakeLists.txt:62 (include):
  include could not find load file:

ECMQMLModules


CMake Error at CMakeLists.txt:63 (include):
  include could not find load file:

KDEInstallDirs


CMake Error at CMakeLists.txt:64 (include):
  include could not find load file:

KDECMakeSettings


CMake Error at CMakeLists.txt:65 (include):
  include could not find load file:

ECMQtDeclareLoggingCategory


CMake Error at CMakeLists.txt:66 (include):
  include could not find load file:

ECMAddQch


CMake Error at CMakeLists.txt:67 (include):
  include could not find load file:

KDECompilerSettings


CMake Error at
/usr/share/cmake-3.11/Modules/CMakePackageConfigHelpers.cmake:249 (message):
  Variable KF5_INCLUDE_INSTALL_DIR does not exist
Call Stack (most recent call first):
  CMakeLists.txt:74 (configure_package_config_file)


-- Configuring incomplete, errors occurred!



signature.asc
Description: OpenPGP digital signature

Bug#901734: /usr/bin/plasmashell: recently taskbar becames unreadable after some time of use

[Paul Gevers]

Subject: /usr/bin/plasmashell: recently taskbar becames unreadable after some 
time of use
Package: plasma-workspace
Version: 4:5.12.5-1
Severity: normal
File: /usr/bin/plasmashell

Dear KDE maintainers,

Recently I had multiple occurances where the taskbar of my KDE session suddenly
became unreadable. As an example, I have attached a screen shot of the task bar
in such a case.

I haven't figured out what triggers the task bar to behave like that.
Nevertheless I already wanted to report the issue. If you have debugging
tips, feel free to contact me for more info.

Thanks for maintaining KDE in Debian.

Paul

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (200, 'testing'), (50, 
'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.16.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-workspace depends on:
ii  dbus-x11 1.12.8-2
ii  drkonqi  5.12.5-1
ii  frameworkintegration 5.46.0-1
ii  gdb-minimal [gdb]7.12-6+b2
ii  iso-codes3.79-1
ii  kactivitymanagerd5.12.5-1
ii  kde-cli-tools4:5.12.5-1
ii  kded55.46.0-1
ii  kinit5.46.0-1
ii  kio  5.46.0-1
ii  kpackagetool55.46.0-1
ii  kwin-common  4:5.12.5-1
ii  libappstreamqt2  0.12.0-3
ii  libc62.27-3
ii  libcln6  1.3.4-4
ii  libcolorcorrect5 4:5.12.5-1
ii  libgcc1  1:8.1.0-5
ii  libgps23 3.17-5+b1
ii  libice6  2:1.0.9-2
ii  libkf5activities55.46.0-1
ii  libkf5auth5  5.46.0-1
ii  libkf5baloo5 5.46.0-1
ii  libkf5bookmarks5 5.46.0-1
ii  libkf5calendarevents55.46.0-1
ii  libkf5completion55.46.0-1
ii  libkf5config-bin 5.46.0-1
ii  libkf5configcore55.46.0-1
ii  libkf5configgui5 5.46.0-1
ii  libkf5configwidgets5 5.46.0-1
ii  libkf5coreaddons55.46.0-1
ii  libkf5crash5 5.46.0-1
ii  libkf5dbusaddons55.46.0-1
ii  libkf5declarative5   5.46.0-1
ii  libkf5globalaccel-bin5.46.0-1
ii  libkf5globalaccel5   5.46.0-1
ii  libkf5guiaddons5 5.46.0-1
ii  libkf5holidays5  1:5.46.0-1
ii  libkf5i18n5  5.46.0-1
ii  libkf5iconthemes55.46.0-1
ii  libkf5idletime5  5.46.0-1
ii  libkf5itemviews5 5.46.0-1
ii  libkf5jobwidgets55.46.0-1
ii  libkf5js55.46.0-1
ii  libkf5jsembed5   5.46.0-1
ii  libkf5kdelibs4support5   5.46.0-1
ii  libkf5kiocore5   5.46.0-1
ii  libkf5kiofilewidgets55.46.0-1
ii  libkf5kiogui55.46.0-1
ii  libkf5kiowidgets55.46.0-1
ii  libkf5networkmanagerqt6  5.46.0-1
ii  libkf5newstuff5  5.46.0-1
ii  libkf5notifications5 5.46.0-1
ii  libkf5notifyconfig5  5.46.0-1
ii  libkf5package5   5.46.0-1
ii  libkf5plasma55.46.0-1
ii  libkf5plasmaquick5   5.46.0-1
ii  libkf5prison55.46.0-1
ii  libkf5quickaddons5   5.46.0-1
ii  libkf5runner55.46.0-1
ii  libkf5service-bin5.46.0-1
ii  libkf5service5   5.46.0-1
ii  libkf5solid5 5.46.0-1
ii  libkf5texteditor55.46.0-1
ii  libkf5textwidgets5   5.46.0-1
ii  libkf5wallet-bin 5.46.0-3
ii  libkf5wallet55.46.0-3
ii  libkf5waylandclient5 4:5.46.0-1
ii  libkf5widgetsaddons5 5.46.0-1
ii  libkf5windowsystem5  5.46.0-1
ii  libkf5xmlgui55.46.0-1
ii  libkscreenlocker55.12.2-1
ii  libksgrd7   

Re: new KDE stack appears to break baloo-widgets/4:17.08.3-1 autopkgtest in testing

[Paul Gevers]

Hi Maximiliano,

On 31-05-18 12:07, Maximiliano Curia wrote:
> ¡Hola Paul!
> 
> El 2018-05-30 a las 21:29 +0200, Paul Gevers escribió:
> My experience sending mails as @debian.org to lists.debian.org is that
> mails get a spam score and so they may be considered as spam if any
> other rule gives your mail some extra points. That's the reason why I'm
> sending the mails as gnuservers.com.ar.

I am sending my e-mails to localhost which is forwarding the local port
to respighi exactly for similar reasons. I don't have good alternatives
as my ISP is using anti-spam measures that make my own e-mails end up in
my spam box for lists.debian.org lists. This has been working well for
the last two years or so.

> Anyway, could you resend us those mails?

Attached one, they were all the same, minus packages and versions. I
don't think it matters much anymore after our discussion.

>> No, I don't, that is why I ask you as the maintainer. But if you have
>> reasons for the "we currently don't care" for the baloo-widgets
>> autopkgtest, I could have helped you to speed up the migration if the
>> gain is worth that regression.
> 
> All right, I had misunderstood your original email.
> 
> Given that the test is also failing in upstream's ci, and no user seems
> to have any "new" issue with baloo, I don't see any gain in sending an
> rc bug to block the transition.

Do you want me to speed up the migration then?

Paul
--- Begin Message ---
Dear maintainers,

[This e-mail is automatically sent. V3.2 (20180518)]

tl;dr: kcoreaddons/5.46.0-1 appears to break baloo-widgets/4:17.08.3-1 
autopkgtest in testing
see: https://ci.debian.net/packages/b/baloo-widgets/testing/amd64/
and https://qa.debian.org/excuses.php?package=kcoreaddons

As recently announced [1] Debian is now running autopkgtests in testing
to check if the migration of a new source package causes regressions. It
does this with the binary packages of the new version of the source
package from unstable.

With a recent upload of kcoreaddons the autopkgtest of baloo-widgets
started to fail in testing [2]. This is currently delaying the migration
of kcoreaddons version 5.46.0-1 [3].

This e-mail is meant to trigger prompt direct communication between the
maintainers of the involved packages as one party has insight in what
changed and the other party insight in what is being tested. Please
therefore get in touch with each other with your ideas about what the
causes of the problem might be, proposed patches, etc. A regression in a
reverse dependency can be due to one of the following reasons (of course
not complete):
* new bug in the candidate package (fix the package)
* bug in the test case that only gets triggered due to the update (fix
  the reverse dependency, but see below)
* out-of-date reference date in the test case that captures a former bug
  in the candidate package (fix the reverse dependency, but see below)
* deprecation of functionality that is used in the reverse dependency
  and/or its test case (discussion needed)
* regression due to other packages from unstable that are installed to 
  fulfill (versioned) Depends (contact maintainers of those).
Triaging tips are being collected on the Debian Wiki [4].

Unfortunately sometimes a regression is only intermittent. Ideally this
should be fixed, but it may be OK to just have the autopkgtest retried
(a link is available in the excuses [3]).

There are cases where it is required to have multiple packages migrate
together to have the test cases pass, e.g. when there was a bug in a
regressing test case of a reverse dependency and that got fixed. In that
case the test cases need to be triggered with both packages from
unstable (reply to this e-mail and/or contact the ci-team [5]) or just
wait until the aging time is over (if the fixed reverse dependency
migrates before that time, the failed test can be retriggered [3]).

Of course no system is perfect. In case a framework issue is suspected,
don't hesitate to raise the issue via BTS or to the ci-team [5] (reply to
me is also fine for initial cross-check).

To avoid stepping on peoples toes, this e-mail does not automatically
generate a bug in the BTS, but it is highly recommended to forward this
e-mail there (psuedo-header boilerplate below [6,7]) in case it is
clear which package should solve this regression.

It can be appropriate to file an RC bug against the depended-on package,
if the regression amounts to an RC bug in the depending package, and to
keep it open while the matter is investigated. That will prevent
migration of an RC regression.

If the maintainers of the depending package don't have available effort
to fix a problem, it is appropriate for the maintainers of the
depended-on package to consider an NMU of the depending package. Any
such an NMU should take place in accordance with the normal NMU rules.

Neither of the above steps should be seen as hostile; 

Re: new KDE stack appears to break baloo-widgets/4:17.08.3-1 autopkgtest in testing

[Paul Gevers]

Hi Maximiliano,

On 30-05-18 15:22, Maximiliano Curia wrote:
> El 2018-05-30 a las 10:35 +0200, Paul Gevers escribió:
>> Last week I send you multiple (automatically generated) e-mails about
>> KDE packages that appeared to break the autopkgtest of baloo-widgets. I
>> am wondering if you investigated the current breakage of the breakage.
>> If the regression is only in the autopkgtest and not in the
>> baloo-widgets itself (I interpret the non-action as meaning that, as
>> baloo-widgets in unstable isn't updated) I'd like to know, because if
>> baloo-widgets is broken by the new versions, we need to file an RC bug
>> in the next couple of days to prevent the KDE stack from migrating to
>> testing.
> 
> The last mail I have from you is dated 2018-05-11 and it's about
> kpackage autopkgtest, not about baloo, so I'm not sure if the messages
> were lost or wasn't sent with your name on it. Could you please check if
> the mail reached this list and send us a link to it?

Hmm, I can't find the messages on lists.debian.org with their message-id
(tried two), so they are probably lost (they were sent as I CC-ed myself
and I received the messages).

For the record, all sent on 2018-05-20 around 19:56 UTC+02:
Message-ID: <1526839020.2732131-elb...@testavoira.debian.org>
Message-ID: <1526839018.9428892-elb...@testavoira.debian.org>
Message-ID: <1526839016.5067074-elb...@testavoira.debian.org>
Message-ID: <1526839019.5896761-elb...@testavoira.debian.org>
Message-ID: <1526839018.344501-elb...@testavoira.debian.org>
Message-ID: <1526839017.09134-elb...@testavoira.debian.org>
Message-ID: <1526839017.724839-elb...@testavoira.debian.org>

> Other than the autopkgtest failures have you found anything that
> justifies an rc bug? So far the autopkgtest failures are only a delay in
> the transition, and kde has enough sid users that track most breakages.

No, I don't, that is why I ask you as the maintainer. But if you have
reasons for the "we currently don't care" for the baloo-widgets
autopkgtest, I could have helped you to speed up the migration if the
gain is worth that regression.

Paul



signature.asc
Description: OpenPGP digital signature

new KDE stack appears to break baloo-widgets/4:17.08.3-1 autopkgtest in testing

[Paul Gevers]

Dear Debian/Kubuntu Qt/KDE Maintainers,

Last week I send you multiple (automatically generated) e-mails about
KDE packages that appeared to break the autopkgtest of baloo-widgets. I
am wondering if you investigated the current breakage of the breakage.
If the regression is only in the autopkgtest and not in the
baloo-widgets itself (I interpret the non-action as meaning that, as
baloo-widgets in unstable isn't updated) I'd like to know, because if
baloo-widgets is broken by the new versions, we need to file an RC bug
in the next couple of days to prevent the KDE stack from migrating to
testing.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#898443: kpackage: flaky autopkgtest

[Paul Gevers]

Source: kpackage
Version: 5.42.0-2
Severity: important
User: debian...@lists.debian.org
Usertags: flaky

While inspecting regressions in autopkgtest results¹, I noticed that
your package kpackage fails regularly (5.45.0-1 hasn't even passed once
yet), without obvious changes. As far as I checked, the error is nearly
always the same (copied below).

Could you please investigate and make your autopkgtest more robust?
Please contact me if you need help and you think I can provide that (I
am not subscribed to this bug).

Recent discussion of gating migration by autopkgtests on debian-devel²
noted that if this is going to work, and in particular if we are going
to *block* migration when it causes autopkgtest regressions rather than
merely delaying it, intermittent autopkgtest failures are likely to have
to be considered RC due to their impact on the tested package's
dependencies; for now I've filed it as important.

Simon McVittie has previously proposed³ a way to mark autopkgtests as
unsuitable for gating CI, while still having them available for
convenient manual testing (and optionally run, but with their results
disregarded, on the real CI infrastructure so that their reliability can
be assessed), but this isn't currently possible. If the autopkgtest
can't be made reliable then it would make sense to disable it for the
moment.

Paul

¹ https://ci.debian.net/packages/k/kpackage/unstable/amd64/
² https://lists.debian.org/debian-devel/2018/05/msg00061.html
³ https://bugs.debian.org/851558

autopkgtest [13:54:56]: test testsuite: [---
cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=-j8
Running tests...
/usr/bin/ctest --force-new-ctest-process -j8
Test project
/tmp/autopkgtest-lxc.m3zi8kbh/downtmp/build.JS4/src/obj-x86_64-linux-gnu
  Start  1: plasma-fallbackpackagetest
  Start  2: plasma-packagestructuretest
  Start  3: plasma-plasmoidpackagetest
  Start  4: plasma-rccpackagetest
  Start  6: testfallbackpackage-appstream
  Start  7: testpackage-appstream
  Start  8: testpackage-nodisplay-appstream
  Start  9: testjsonmetadatapackage-appstream
 1/11 Test  #7: testpackage-appstream ...   Passed0.11 sec
 2/11 Test  #8: testpackage-nodisplay-appstream .   Passed0.11 sec
 3/11 Test  #3: plasma-plasmoidpackagetest ..***Failed0.11 sec
* Start testing of PlasmoidPackageTest *
Config: Using QtTest library 5.9.2, Qt 5.9.2 (x86_64-little_endian-lp64
shared (dynamic) release build; by GCC 7.3.0)
PASS   : PlasmoidPackageTest::initTestCase()
QDEBUG : PlasmoidPackageTest::createAndInstallPackage()
PlasmoidPackage::init()
QDEBUG : PlasmoidPackageTest::createAndInstallPackage() cleaning up
QDEBUG : PlasmoidPackageTest::createAndInstallPackage()
QDEBUG : PlasmoidPackageTest::createAndInstallPackage()CreateAndInstall
QDEBUG : PlasmoidPackageTest::createAndInstallPackage() Create test
package "/home/debci/.qttest/share/packageRoot"
QDEBUG : PlasmoidPackageTest::createAndInstallPackage() Created
"/home/debci/.qttest/share/packageRoot/plasmoid_to_package"
QDEBUG : PlasmoidPackageTest::createAndInstallPackage() OUT:
"plasmoid_to_package"
QDEBUG : PlasmoidPackageTest::createAndInstallPackage() THIS IS A
PLASMOID SCRIPT THING
FAIL!  : PlasmoidPackageTest::createAndInstallPackage()
'QFile::exists(packagePath)' returned FALSE. ()
   Loc:
[/tmp/autopkgtest-lxc.m3zi8kbh/downtmp/build.JS4/src/autotests/plasmoidpackagetest.cpp(277)]
QDEBUG : PlasmoidPackageTest::createAndInstallPackage() cleaning up
QDEBUG : PlasmoidPackageTest::createAndUpdatePackage()
PlasmoidPackage::init()
QDEBUG : PlasmoidPackageTest::createAndUpdatePackage() cleaning up
QDEBUG : PlasmoidPackageTest::createAndUpdatePackage()
QDEBUG : PlasmoidPackageTest::createAndUpdatePackage()CreateAndUpdate
QDEBUG : PlasmoidPackageTest::createAndUpdatePackage() Create test
package "/home/debci/.qttest/share/packageRoot"
QDEBUG : PlasmoidPackageTest::createAndUpdatePackage() Created
"/home/debci/.qttest/share/packageRoot/plasmoid_to_package"
QDEBUG : PlasmoidPackageTest::createAndUpdatePackage() OUT:
"plasmoid_to_package"
QDEBUG : PlasmoidPackageTest::createAndUpdatePackage() THIS IS A
PLASMOID SCRIPT THING
QDEBUG : PlasmoidPackageTest::createAndUpdatePackage() Installing
"/home/debci/.qttest/share/packageRoot/testpackage.plasmoid"
QDEBUG : PlasmoidPackageTest::createAndUpdatePackage()
 package installed true ""
QDEBUG : PlasmoidPackageTest::createAndUpdatePackage() "Not installing
version 1.1 of plasmoid_to_package. Version 1.1 already installed."
QDEBUG : PlasmoidPackageTest::createAndUpdatePackage() Create test
package "/home/debci/.qttest/share/packageRoot"
QDEBUG : PlasmoidPackageTest::createAndUpdatePackage() Created
"/home/debci/.qttest/share/packageRoot/plasmoid_to_package"
QDEBUG : PlasmoidPackageTest::createAndUpdatePackage() OUT:
"plasmoid_to_package"
QDEBUG : PlasmoidPackageTest::createAndUpdatePackage() THIS IS A
PLASMOID SCRIPT 

Bug#898083: kdepim-addons: autopkgtest times out

[Paul Gevers]

Source: kdepim-addons
Version: 17.12.3-1
Severity: normal
User: debian...@lists.debian.org
Usertags: timeout

Since the upload of version 17.12.3-1 of kdepim-addons, the autopkgtest¹
are timing out (~ 3 hours) while previous runs tested in about 40
minutes (and failed). There is output to the log (copied below). Could
you please investigate how to get rid of the timeout? And please fix
your test to actually pass, but that is less important now.

I have blacklisted kdepim-addons for now.

Don't hesitate to ask for help for the Debian CI team² if you need help
solving this issue.

Paul

¹ https://ci.debian.net/packages/k/kdepim-addons/unstable/amd64/
² #debci on oftc or debian...@lists.debian.org

autopkgtest [17:40:53]: test testsuite: [---
Openbox-Message: Unable to find a valid menu file
"/var/lib/openbox/debian-menu.xml"
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher'
kdeinit5: Launched KLauncher, pid = 20147, result = 0
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeinit5: opened connection to :99
cd obj-x86_64-linux-gnu && make -j2 -Oline test ARGS\+=-j2
Running tests...
autopkgtest [20:27:34]: ERROR: timed out on command "su -s /bin/bash
debci -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 ||
true;  . ~/.profile >/dev/null 2>&1 || true;
buildtree="/tmp/autopkgtest-lxc.rdb2i6d2/downtmp/build.6DT/src"; mkdir
-p -m 1777 --
"/tmp/autopkgtest-lxc.rdb2i6d2/downtmp/testsuite-artifacts"; export
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.rdb2i6d2/downtmp/testsuite-artifacts";
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755
"/tmp/autopkgtest-lxc.rdb2i6d2/downtmp/autopkgtest_tmp"; export
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.rdb2i6d2/downtmp/autopkgtest_tmp";
export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive;
export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=2; unset LANGUAGE
LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES
LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT
LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo
$$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f
/tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; chmod
+x
/tmp/autopkgtest-lxc.rdb2i6d2/downtmp/build.6DT/src/debian/tests/testsuite;
touch /tmp/autopkgtest-lxc.rdb2i6d2/downtmp/testsuite-stdout
/tmp/autopkgtest-lxc.rdb2i6d2/downtmp/testsuite-stderr;
/tmp/autopkgtest-lxc.rdb2i6d2/downtmp/build.6DT/src/debian/tests/testsuite
2> >(tee -a /tmp/autopkgtest-lxc.rdb2i6d2/downtmp/testsuite-stderr >&2)
> >(tee -a /tmp/autopkgtest-lxc.rdb2i6d2/downtmp/testsuite-stdout);"
(kind: test)
autopkgtest [20:27:34]: test testsuite: ---]



signature.asc
Description: OpenPGP digital signature

Bug#898082: libkf5mailcommon: autopkgtest times out

[Paul Gevers]

Source: libkf5mailcommon
Version: 4:17.12.3-1
Severity: normal
Control: user debian...@lists.debian.org
Control: usertags -1 timeout

Since the upload of version 4:17.12.3-1 of libkf5mailcommon, the
autopkgtest¹ are timing out (~ 3 hours) while previous runs tested in
about 20 minutes (and failed). There is output to the log (copied
below). Could you please investigate how to get rid of the timeout? And
please fix your test to actually pass, but that is less important now.

I have blacklisted 4:17.12.3-1 for now.

Don't hesitate to ask for help for the Debian CI team² if you need help
solving this issue.

Paul

¹ https://ci.debian.net/packages/libk/libkf5mailcommon/unstable/amd64/
² #debci on oftc or debian...@lists.debian.org

autopkgtest [17:12:31]: test testsuite: [---
cd obj-x86_64-linux-gnu && make -j2 -Oline test ARGS\+=-j2
Running tests...
autopkgtest [19:59:11]: ERROR: timed out on command "su -s /bin/bash
debci -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 ||
true;  . ~/.profile >/dev/null 2>&1 || true;
buildtree="/tmp/autopkgtest-lxc.9rqu_sd7/downtmp/build.AcF/src"; mkdir
-p -m 1777 --
"/tmp/autopkgtest-lxc.9rqu_sd7/downtmp/testsuite-artifacts"; export
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.9rqu_sd7/downtmp/testsuite-artifacts";
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755
"/tmp/autopkgtest-lxc.9rqu_sd7/downtmp/autopkgtest_tmp"; export
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.9rqu_sd7/downtmp/autopkgtest_tmp";
export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive;
export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=2; unset LANGUAGE
LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES
LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT
LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo
$$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f
/tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; chmod
+x
/tmp/autopkgtest-lxc.9rqu_sd7/downtmp/build.AcF/src/debian/tests/testsuite;
touch /tmp/autopkgtest-lxc.9rqu_sd7/downtmp/testsuite-stdout
/tmp/autopkgtest-lxc.9rqu_sd7/downtmp/testsuite-stderr;
/tmp/autopkgtest-lxc.9rqu_sd7/downtmp/build.AcF/src/debian/tests/testsuite
2> >(tee -a /tmp/autopkgtest-lxc.9rqu_sd7/downtmp/testsuite-stderr >&2)
> >(tee -a /tmp/autopkgtest-lxc.9rqu_sd7/downtmp/testsuite-stdout);"
(kind: test)
autopkgtest [19:59:12]: test testsuite: ---]



signature.asc
Description: OpenPGP digital signature

Bug#898081: kdelibs4support: autopkgtest times out

[Paul Gevers]

Source: kdelibs4support
Version: 5.42.0-2
Severity: normal
User: debian...@lists.debian.org
Usertags: timeout

Since the upload of version 5.42.0-2 of kdelibs4support, the
autopkgtest¹ are timing out (~ 3 hours) while previous runs tested in
about 20 minutes (and failed). There is output to the log (copied
below). Could you please investigate how to get rid of the timeout? And
please fix your test to actually pass, but that is less important now.

I have blacklisted kdelibs4support for now.

Don't hesitate to ask for help for the Debian CI team² if you need help
solving this issue.

Paul

¹ https://ci.debian.net/packages/k/kdelibs4support/unstable/amd64/
² #debci on oftc or debian...@lists.debian.org

autopkgtest [10:23:13]: test testsuite: [---
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-debci'
kbuildsycoca5 running...
Openbox-Message: Unable to find a valid menu file
"/var/lib/openbox/debian-menu.xml"
cd obj-x86_64-linux-gnu && make -j2 -Oline test ARGS\+=-j2
Running tests...
dbus-daemon[17350]: [session uid=105 pid=17350] Activating service
name='org.kde.kded5' requested by ':1.0' (uid=105 pid=17369
comm="/tmp/autopkgtest-lxc.7bwod5uu/downtmp/build.RQw/sr")
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-debci'
dbus-daemon[17350]: [session uid=105 pid=17350] Successfully activated
service 'org.kde.kded5'
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kded/networkstatus.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kded/remotenotifier.so"
kf5.kded: No X-KDE-DBus-ServiceName found in
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kded/proxyscout.so"
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-debci'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-debci'
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher'
kdeinit5: Launched KLauncher, pid = 17386, result = 0
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-debci'
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-debci'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-debci'
kdeinit5: opened connection to :99
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/libexec/kf5/kconf_update' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/libexec/kf5/kconf_update'
kdeinit5: PID 17389 terminated.
kf5.kded: could not find kded module with id "ktimezoned"
kf5.kded: attempted to load an invalid module.
kf5.kded: could not find kded module with id "ktimezoned"
kf5.kded: attempted to load an invalid module.
kf5.kded: could not find kded module with id "ktimezoned"
kf5.kded: attempted to load an invalid module.
kf5.kded: could not find kded module with id "ktimezoned"
kf5.kded: attempted to load an invalid module.
kf5.kded: could not find kded module with id "ktimezoned"
kf5.kded: attempted to load an invalid module.
kf5.kded: could not find kded module with id "ktimezoned"
kf5.kded: attempted to load an invalid module.
kf5.kded: could not find kded module with id "ktimezoned"
kf5.kded: attempted to load an invalid module.
kf5.kded: could not find kded module with id "ktimezoned"
kf5.kded: attempted to load an invalid module.
kf5.kded: could not find kded module with id "ktimezoned"
kf5.kded: attempted to load an invalid module.
kf5.kded: could not find kded module with id "ktimezoned"
kf5.kded: attempted to load an invalid module.
kf5.kded: could not find kded module with id "ktimezoned"
kf5.kded: attempted to load an invalid module.
kf5.kded: could not find kded module with id "ktimezoned"
kf5.kded: attempted to load an invalid module.
kf5.kded: could not find kded module with id "ktimezoned"
kf5.kded: attempted to load an invalid module.
autopkgtest [13:09:53]: ERROR: timed out on command "su -s /bin/bash
debci -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 ||
true;  . ~/.profile >/dev/null 2>&1 || true;
buildtree="/tmp/autopkgtest-lxc.7bwod5uu/downtmp/build.RQw/src"; mkdir
-p -m 1777 --
"/tmp/autopkgtest-lxc.7bwod5uu/downtmp/testsuite-artifacts"; export
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.7bwod5uu/downtmp/testsuite-artifacts";
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755
"/tmp/autopkgtest-lxc.7bwod5uu/downtmp/autopkgtest_tmp"; export
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.7bwod5uu/downtmp/autopkgtest_tmp";
export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive;
export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=2; unset LANGUAGE
LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES
LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT
LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo
$$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f

Bug#895632: kdav: autopkgtest fails with new release while succeeded in the past

[Paul Gevers]

Source: kdav
Version: 17.12.3-1
Severity: normal
User: ci-t...@tracker.debian.org
Usertags: regression

With the upload of version 17.12.3-1 of kdav, the
autopkgtest¹ started to fail with the following error:

Running tests...
/usr/bin/ctest --force-new-ctest-process -j1
Test project
/tmp/autopkgtest-lxc.m0yqmrr9/downtmp/build.7In/src/obj-x86_64-linux-gnu
Start 1: kdav-davcollection
1/5 Test #1: kdav-davcollection ...   Passed0.03 sec
Start 2: kdav-davitem
2/5 Test #2: kdav-davitem .   Passed0.01 sec
Start 3: kdav-davurl
3/5 Test #3: kdav-davurl ..   Passed0.01 sec
Start 4: kdav-davitemfetchjob
4/5 Test #4: kdav-davitemfetchjob .***Failed0.02 sec
* Start testing of DavItemFetchJobTest *
Config: Using QtTest library 5.9.2, Qt 5.9.2 (x86_64-little_endian-lp64
shared (dynamic) release build; by GCC 7.3.0)
PASS   : DavItemFetchJobTest::initTestCase()
QWARN  : DavItemFetchJobTest::runSuccessfullTest() kf5.kdbusaddons: Can
not find 'kdeinit5' executable at
"/usr/share/pkg-kde-tools/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
"/tmp/autopkgtest-lxc.m0yqmrr9/downtmp/build.7In/src/obj-x86_64-linux-gnu/bin,
/usr/lib/qt5/bin"
QWARN  : DavItemFetchJobTest::runSuccessfullTest() kf5.kio.core: KIO
Connection server not listening, could not connect
QWARN  : DavItemFetchJobTest::runSuccessfullTest() kf5.kio.core:
couldn't create slave: "Can not create socket for launching io-slave for
protocol 'http'."
FAIL!  : DavItemFetchJobTest::runSuccessfullTest()
'fakeServer.isAllScenarioDone()' returned FALSE. ()
   Loc:
[/tmp/autopkgtest-lxc.m0yqmrr9/downtmp/build.7In/src/autotests/davitemfetchjobtest.cpp(42)]
PASS   : DavItemFetchJobTest::cleanupTestCase()
Totals: 2 passed, 1 failed, 0 skipped, 0 blacklisted, 9ms
* Finished testing of DavItemFetchJobTest *

Start 5: kdav-davitemslistjob
5/5 Test #5: kdav-davitemslistjob .   Passed0.01 sec

80% tests passed, 1 tests failed out of 5

Total Test time (real) =   0.09 sec

The following tests FAILED:
  4 - kdav-davitemfetchjob (Failed)
Errors while running CTest
make[3]: *** [Makefile:99: test] Error 8


Paul

¹ https://ci.debian.net/packages/k/kdav/unstable/amd64/











signature.asc
Description: OpenPGP digital signature

Bug#895631: libkf5libkdepim: autopkgtest fails with new release while succeeded in the past

[Paul Gevers]

Source: libkf5libkdepim
Version: 4:17.12.3-1
Severity: normal
User: ci-t...@tracker.debian.org
Usertags: regression

With the upload of version 17.12.3-1 of libkf5libkdepim, the
autopkgtest¹ started to fail with the following error:

autopkgtest [15:29:56]: test acc: [---
objdump: /usr/lib/x86_64-linux-gnu/libc++.so: File format not recognized
objdump: /usr/lib/x86_64-linux-gnu/libc.so: File format not recognized
objdump: /usr/lib/x86_64-linux-gnu/libm.so: File format not recognized
objdump: /usr/lib/x86_64-linux-gnu/libpthread.so: File format not recognized
cc1: warning: command line option ‘-std=c++11’ is valid for C++/ObjC++
but not for C
dh_acc: abi-compliance-checker -q -l libkf5libkdepim-dev -v1 4:17.12.3-1
-dump debian/libkf5libkdepim-dev.acc -dump-path
debian/libkf5libkdepim-dev/usr/lib/x86_64-linux-gnu/dh-acc/libkf5libkdepim-dev_4:17.12.3-1.abi.tar.gz
returned exit code 5

Paul

¹ https://ci.debian.net/packages/libk/libkf5libkdepim/unstable/amd64/









signature.asc
Description: OpenPGP digital signature

Bug#895628: akonadi-search: autopkgtest fails with new release while succeeded in the past

[Paul Gevers]

Source: akonadi-search
Version: 4:17.12.3-1
Severity: normal
User: ci-t...@tracker.debian.org
Usertags: regression

With the upload of version 17.12.3-1 of akonadi-search, the
autopkgtest¹ started to fail with the following error:

autopkgtest [04:01:09]: test acc: [---
objdump: /usr/lib/x86_64-linux-gnu/libc++.so: File format not recognized
objdump: /usr/lib/x86_64-linux-gnu/libc.so: File format not recognized
objdump: /usr/lib/x86_64-linux-gnu/libm.so: File format not recognized
objdump: /usr/lib/x86_64-linux-gnu/libpthread.so: File format not recognized
cc1: warning: command line option ‘-std=c++11’ is valid for C++/ObjC++
but not for C
dh_acc: abi-compliance-checker -q -l libkf5akonadisearch-dev -v1
4:17.12.3-1 -dump debian/libkf5akonadisearch-dev.acc -dump-path
debian/libkf5akonadisearch-dev/usr/lib/x86_64-linux-gnu/dh-acc/libkf5akonadisearch-dev_4:17.12.3-1.abi.tar.gz
returned exit code 5

Paul

¹ https://ci.debian.net/packages/a/akonadi-search/unstable/amd64/







signature.asc
Description: OpenPGP digital signature

Bug#895588: kleopatra: autopkgtest fails with new release while succeeded in the past

[Paul Gevers]

Source: kleopatra
Version: 4:17.12.3-1
Severity: normal
User: ci-t...@tracker.debian.org
Usertags: regression

With the upload of version 17.12.3-1 of kleopatra, the
autopkgtest¹ started to fail with the following error:

Running tests...
/usr/bin/ctest --force-new-ctest-process -j2
Test project
/tmp/autopkgtest-lxc.wntks_s5/downtmp/build.2Eg/src/obj-x86_64-linux-gnu
Start 1: test_verify
1/1 Test #1: test_verify ..***Failed2.10 sec
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-debci'
* Start testing of VerifyTest *
Config: Using QtTest library 5.9.2, Qt 5.9.2 (x86_64-little_endian-lp64
shared (dynamic) release build; by GCC 7.3.0)
PASS   : VerifyTest::initTestCase()
FAIL!  : VerifyTest::testVerify() Compared values are not the same
   Actual   ((quint64) sig.creationTime()): 0
   Expected (Q_UINT64_C(1189650248))  : 1189650248
   Loc:
[/tmp/autopkgtest-lxc.wntks_s5/downtmp/build.2Eg/src/tests/test_verify.cpp(173)]
PASS   : VerifyTest::testDecryptVerifyOpaqueSigned()
PASS   : VerifyTest::cleanupTestCase()
Totals: 3 passed, 1 failed, 0 skipped, 0 blacklisted, 2022ms
* Finished testing of VerifyTest *


0% tests passed, 1 tests failed out of 1

Total Test time (real) =   2.11 sec

The following tests FAILED:
  1 - test_verify (Failed)
Errors while running CTest
make: *** [Makefile:99: test] Error 8

Paul

¹ https://ci.debian.net/packages/k/kleopatra/unstable/amd64/





signature.asc
Description: OpenPGP digital signature

Bug#895303: libkf5pimcommon: autopkgtest fails with new release while succeeded in the past

[Paul Gevers]

Source: libkf5pimcommon
Version: 4:17.12.3-1
Severity: normal
User: ci-t...@tracker.debian.org
Usertags: regression

With the upload of version 17.12.3-1 of libkf5pimcommon, the
autopkgtest¹ started to fail.

Among others:

objdump: /usr/lib/x86_64-linux-gnu/libc++.so: File format not recognized
objdump: /usr/lib/x86_64-linux-gnu/libc.so: File format not recognized
objdump: /usr/lib/x86_64-linux-gnu/libm.so: File format not recognized
objdump: /usr/lib/x86_64-linux-gnu/libpthread.so: File format not recognized
cc1: warning: command line option ‘-std=c++11’ is valid for C++/ObjC++
but not for C
dh_acc: abi-compliance-checker -q -l libkf5pimcommon-dev -v1 4:17.12.3-1
-dump debian/libkf5pimcommon-dev.acc -dump-path
debian/libkf5pimcommon-dev/usr/lib/x86_64-linux-gnu/dh-acc/libkf5pimcommon-dev_4:17.12.3-1.abi.tar.gz
returned exit code 5

Paul

¹ https://ci.debian.net/packages/libk/libkf5pimcommon/unstable/amd64/



signature.asc
Description: OpenPGP digital signature

Bug#857994: qtwebchannel-opensource-src: Please do not depend on npm

[Paul Gevers]

Control: tags -1 patch

@ BSP Mönchengladbach

On Fri, 17 Mar 2017 00:40:28 +0100 Jérémy Lal <kapo...@melix.org> wrote:
> Would qtwebchannel5-examples be broken without npm ?

Two examples seem to need npm when one wants to see the example in
action. However, I think that without npm from Debian, the examples are
still valuable to read and there are multiple other examples present as
well.

I propose the attached debdiff to fix this dependency, which demotes the
dependency to suggests. Please let me know if you want me to upload as
attached.

Paul
diff -Nru qtwebchannel-opensource-src-5.7.1/debian/changelog 
qtwebchannel-opensource-src-5.7.1/debian/changelog
--- qtwebchannel-opensource-src-5.7.1/debian/changelog  2016-12-16 
12:49:43.0 +0100
+++ qtwebchannel-opensource-src-5.7.1/debian/changelog  2017-03-18 
12:37:30.0 +0100
@@ -1,3 +1,11 @@
+qtwebchannel-opensource-src (5.7.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Demote qtwebchannel5-examples dependency on npm to suggest to enable
+removal of npm in testing (Closes: #857994)
+
+ -- Paul Gevers <elb...@debian.org>  Sat, 18 Mar 2017 12:37:30 +0100
+
 qtwebchannel-opensource-src (5.7.1-1) unstable; urgency=medium
 
   [ Sandro Knauß ]
diff -Nru qtwebchannel-opensource-src-5.7.1/debian/control 
qtwebchannel-opensource-src-5.7.1/debian/control
--- qtwebchannel-opensource-src-5.7.1/debian/control2016-12-16 
12:45:28.0 +0100
+++ qtwebchannel-opensource-src-5.7.1/debian/control2017-03-18 
12:37:30.0 +0100
@@ -68,10 +68,10 @@
 Multi-Arch: same
 Depends: libqt5webchannel5 (= ${binary:Version}),
  nodejs [!armel !powerpc],
- npm [!armel !powerpc],
  ${misc:Depends},
  ${shlibs:Depends}
 Pre-Depends: ${misc:Pre-Depends}
+Suggests: npm [!armel !powerpc],
 Description: Web communication library for Qt - Examples
  Qt WebChannel enables peer-to-peer communication between the host (QML/C++
  application) and the client (HTML/JavaScript application). The transport


signature.asc
Description: OpenPGP digital signature

Re: Bug#767905: kwallet: after upgrade from jessie to stretch kwalletmanager doesn't see my old wallets

[Paul Gevers]

Hi Matthew,

On 20-06-16 14:11, Matthew Cope wrote:
> Do you get an error code 42 ("Unknown encryption scheme.")?
> The problem you describe sounds similar to the issue I reported in bug 
> #799300 
> [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799300].

Yes, I did get error code 42 (albeit without the text what it means). If
I, by the way, wait to long with pressing "Cancel", the wallet manager
dies with a segmentation fault. Is there interest to get the kde trace
for that?

Paul



signature.asc
Description: OpenPGP digital signature

Re: Bug#767905: kwallet: after upgrade from jessie to stretch kwalletmanager doesn't see my old wallets

[Paul Gevers]

Hmm,

On 19-06-16 19:53, Paul Gevers wrote:
> So I installed kde-runtime again and with the Migration block still
> removed, I was able to import one wallet (the password for the first
> wallet it tried to open was in second one, as it is a legacy wallet that
> I don't always remember to update when I update my passwords). I'll
> figure it out thanks.

And I fail to migrate my main wallet, it doesn't seem to accept my
password. My main wallet was already of the gpg type, so maybe that is
related? The blog mentioned before said: "that’ll eventually be the
moment to switch to GPG wallets." Also the following quote worries me
slightly: "The migration assistant will preserve wallet names" as the
wallet created with KDE5 has the same name (default) as my old wallet.

So of my three original wallets, I am have so far only been able to
import one older one.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#767905: kwallet: after upgrade from jessie to stretch kwalletmanager doesn't see my old wallets

[Paul Gevers]

Hi all,

On 19-06-16 11:29, Martin Steigerwald wrote:
> I get the impression you may need to delete the "[Migration]" configuration 
> block completely.

Did that, didn't help.

> Please review the complete blog entry and the comments and check whether you 
> find a solution that works for you. I suggest you try exactly the steps 
> Valentin described and also have kde-runtime installed for /usr/bin/kwalletd. 
> (But I think your kwallet system wouldn´t work otherwise, so I bet it is 
> installed.)

kde-runtime was NOT installed. It was one of the requirements that got
uninstalled to let me migrate to stretch. But that would be an other
bug, however unfortunately I lost my logging do a failure to hibernate
so I can't properly report it.

So I installed kde-runtime again and with the Migration block still
removed, I was able to import one wallet (the password for the first
wallet it tried to open was in second one, as it is a legacy wallet that
I don't always remember to update when I update my passwords). I'll
figure it out thanks.

Seems like a dependency is missing here or there.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#767905: kwallet: after upgrade from jessie to stretch kwalletmanager doesn't see my old wallets

[Paul Gevers]

Hi

On 15-06-16 09:16, Martin Steigerwald wrote:
> I bet you can have it have another go at it by setting alreadyMigrated to 
> false
> 
> martin@merkaba:~/.config> grep Migr kwalletrc
> [Migration]
> alreadyMigrated=true

paul@ruapehu ~ $ cat .config/kwalletrc
[Wallet]
First Use=false

That is all there was in my kwalletrc file.

> and restarting KWallet. You may need to restart your Plasma session in order 
> to do that, or restart the kwallet service manually (but I didn´t find it in 
> background services kcm).

I terminated logged out of KDE, restarted with "startx" and still, the
wallets are not migrated. The kwalletrc after restart still looks like

paul@ruapehu ~ $ cat .config/kwalletrc
[Wallet]
First Use=false
[Migration]
alreadyMigrated=false

Paul



signature.asc
Description: OpenPGP digital signature

Bug#767905: kwallet: after upgrade from jessie to stretch kwalletmanager doesn't see my old wallets

[Paul Gevers]

Package: kwalletmanager
Version: 4:16.04.1-1
Followup-For: Bug #767905
Control: severity -1 serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I just upgraded my system from jessie (with only jessie-backports as additional
archive) to stretch and now, after reboot, my old wallets aren't
available. Would be good if the new kwalletmanager would pick up my old wallets
automatically.

paul@ruapehu ~ $ ll .kde/share/apps/kwallet/
total 68
drwx--  2 paul paul  4096 jun 13 19:51 .
drwx-- 34 paul paul  4096 jun 13 20:06 ..
- -rw---  1 paul paul  2242 jun 13 19:51 kdewallet.kwl
- -rw-r--r--  1 paul paul56 mrt 27  2015 kdewallet.salt
- -rw---  1 paul paul 15644 apr 12 20:00 kdewallet_stromboli.kwl
- -rw-r--r--  1 paul paul56 dec 18  2014 kdewallet_stromboli.salt
- -rw---  1 paul paul 21044 apr 12 20:00 kdewallet_wollumbin.kwl
- -rw-r--r--  1 paul paul56 dec  6  2014 kdewallet_wollumbin.salt
- -rw-r--r--  1 paul paul56 apr 26  2015 wollumbin.salt

Seems like the new wallet lives here:
paul@ruapehu ~ $ ll .local/share/kwalletd/
total 12
drwxr-xr-x  2 paul paul 4096 jun 13 20:08 .
drwxr-xr-x 26 paul paul 4096 jun 13 20:14 ..
- -rw---  1 paul paul  678 jun 13 20:08 kdewallet.kwl

Please let me know if you need more information.

Paul

- -- System Information:
Debian Release: stretch/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing'), (60, 'unstable'), 
(50, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kwalletmanager depends on:
ii  libc6   2.19-18+deb8u4
ii  libkf5archive5  5.22.0-1
ii  libkf5auth5 5.22.0-1
ii  libkf5codecs5   5.22.0-1
ii  libkf5configcore5   5.22.0-1
ii  libkf5configwidgets55.22.0-1
ii  libkf5coreaddons5   5.22.0-1
ii  libkf5dbusaddons5   5.22.0-1
ii  libkf5i18n5 5.22.1-1
ii  libkf5iconthemes5   5.22.0-1
ii  libkf5itemviews55.22.0-1
ii  libkf5kdelibs4support5  5.22.0-2
ii  libkf5notifications55.22.0-1
ii  libkf5service-bin   5.22.0-1
ii  libkf5service5  5.22.0-1
ii  libkf5textwidgets5  5.22.0-1
ii  libkf5wallet-bin5.22.0-1
ii  libkf5wallet5   5.22.0-1
ii  libkf5widgetsaddons55.22.0-1
ii  libkf5xmlgui5   5.22.0-1
ii  libqt5core5a5.5.1+dfsg-17
ii  libqt5dbus5 5.5.1+dfsg-17
ii  libqt5gui5  5.5.1+dfsg-17
ii  libqt5widgets5  5.5.1+dfsg-17
ii  libqt5xml5  5.5.1+dfsg-17
ii  libstdc++6  6.1.1-4

kwalletmanager recommends no packages.

kwalletmanager suggests no packages.

- -- Configuration Files:
/etc/dbus-1/system.d/org.kde.kcontrol.kcmkwallet.conf 
5a742298b5cdad91bf96decd31eaeff8 [Errno 2] No such file or directory: 
u'/etc/dbus-1/system.d/org.kde.kcontrol.kcmkwallet.conf 
5a742298b5cdad91bf96decd31eaeff8'

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJXXv5IAAoJEJxcmesFvXUK9r4IAMc0UEdCDvoXotLn45i6E2ED
j6U7wUaBS+rnIS/1SOzXbBw9RkdtrbBrJ/0urHQpMb/ZmrHYjrIZylR72GYYOVDM
jN5rcbq3Y/OAoGscLtwuCRoCOKqqwYpSjuZ61mege8aiEQ3ORQZho3aFUPxnQ/Fu
0o6J/LJSgppac9pF+eb9PgxP4O/AZhHYYTiSCjwo1WPtE3IBmjONbBYJ7jCOcEgw
FOV5qZZWzboPpyDZwRaZMJ08X2eptPf5Hg2RwIcNsLEjIi7deCG322yfDsUErwk4
enX5mngnhtrbRywsERtc/evxizRHtHrHty0vuH66ohJ44LlUtzjQF1LKQOu+UdU=
=zXZv
-END PGP SIGNATURE-

Bug#689339: kwalletmanager: the kwalletmanager GUI does not appear

[Paul Gevers]

 I recently installed wheezy KDE on my laptop. I am used to manage my
 passwords with kwalletmanager. However, if I select the kwallet manager in
 the K-menu, start it via ALT-F2 or start if from command line, I don't see
 any GUI.
 
 Check in the dock area (the triangle in the taskbar, next to the clock).
 
 Can you find it there?

Indeed it is there, sorry for not looking (I never use that triangle, so
I didn't think of it). On my previous install (Ubuntu) I could pop-up
the gui by running kwalletmanager from command line or ALT-F2.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#689339: kwalletmanager: the kwalletmanager GUI does not appear

[Paul Gevers]

Package: kwalletmanager
Version: 4:4.8.4-2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I recently installed wheezy KDE on my laptop. I am used to manage my passwords 
with kwalletmanager. However, if I select the kwallet manager in the K-menu, 
start it via ALT-F2 or start if from command line, I don't see any GUI.

It seems to be running:
paul@wollumbin ~ $ ps aux | grep wallet
paul  3324  0.0  0.5 283440 16108 ?S18:54   0:00 
/usr/bin/kwalletd
paul  4002  0.4  0.6 287636 17384 pts/0S18:56   0:00 
/usr/bin/kwalletmanager

Also, when I start it from command line I get a warning, but the exit status is 
ok:
paul@wollumbin ~ $ kwalletmanager  echo ok
QDBusConnection: session D-Bus connection created before QCoreApplication. 
Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. 
Application may misbehave.
ok

If I stop kwallet and start it again I get an additional warning:
paul@wollumbin ~ $ kwalletmanager  echo ok
QDBusConnection: session D-Bus connection created before QCoreApplication. 
Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. 
Application may misbehave.
Connecting to deprecated signal 
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
ok

Please let me know if I can help more to get this issue fixed.

- -- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-3-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kwalletmanager depends on:
ii  kde-runtime  4:4.8.4-1
ii  libc62.13-35
ii  libkdecore5  4:4.8.4-3
ii  libkdeui54:4.8.4-3
ii  libkio5  4:4.8.4-3
ii  libqt4-dbus  4:4.8.2+dfsg-2
ii  libqt4-xml   4:4.8.2+dfsg-2
ii  libqtcore4   4:4.8.2+dfsg-2
ii  libqtgui44:4.8.2+dfsg-2
ii  libstdc++6   4.7.1-7

kwalletmanager recommends no packages.

kwalletmanager suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlBpzq0ACgkQHNUte6r+CGqB+ACeMkzBbJzUkccOqc4tNijCrm0S
BdwAn3FEKBbaY+DHRgCtReo+Bw2azR9s
=UZYq
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20121001171116.4011.53709.report...@wollumbin.marsaxlokk.homelinux.org