Bug#1055813: (no subject)

[Rik Mills]

Fixed upstream with: 
https://invent.kde.org/network/kdenetwork-filesharing/-/commit/6cbdd2bd71b3d6f030f06114978743414d4f

Bug#1055813: Install samba feature/button fails to install samba via packagelkit

[Rik Mills]

Package: kdenetwork-filesharing
Version: 4:22.12.3-1

STEPS TO REPRODUCE
1. Install kdenetwork-filesharing
2. In dolphin right click a folder you wish to share, and click properties.
2. Select the 'Share' tab in the properties window.
3. Click  the button to install the distro samba package.

OBSERVED RESULT

An expected polkit dialog to authorise packagekit to install the
distro samba package does not appear.
The message "The samba package failed to install" is displayed instead.

EXPECTED RESULT

A polkit auth diagog should appear, and upon successful admin password
entry the distro samba package should be installed and the sharing
options enabled.

Ref: https://bugs.kde.org/show_bug.cgi?id=472145

Bug#1021032: (no subject)

[Rik Mills]

On Mon, 3 Oct 2022 07:46:54 +0100 Rik Mills  wrote:

Comment from the launchpad counterpart to this bug below:

https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1991418/comments/10

"So, hate to rain on your parade, but as I wrote yesterday, the problem 
doesn't occur with upstream (building manually) 3.0.17.4. So there are 
ostensibly no patches to backport from upstream 3.0.18-rc2. This is 
probably an issue in the Debian packaging or at least that is triggered 
by Debian packaging.


Since it seems to affect only the Qt UI, it is most probably a problem 
with the last Qt update. Again, please check with --no-embedded-video."


Running with --no-embedded-video does indeed work, but as expected is 
ugly with the video in a separate floating window.

Bug#1021032: (no subject)

[Rik Mills]

Comment from the launchpad counterpart to this bug below:

https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1991418/comments/10

"So, hate to rain on your parade, but as I wrote yesterday, the problem 
doesn't occur with upstream (building manually) 3.0.17.4. So there are 
ostensibly no patches to backport from upstream 3.0.18-rc2. This is 
probably an issue in the Debian packaging or at least that is triggered 
by Debian packaging.


Since it seems to affect only the Qt UI, it is most probably a problem 
with the last Qt update. Again, please check with --no-embedded-video."

Bug#1016785: Can't change user password on a "System Settings" (polkit dialog doesn't appear)

[Rik Mills]

Reported upstream in: https://bugs.kde.org/show_bug.cgi?id=459309

Fixed by: 
https://invent.kde.org/plasma/plasma-workspace/-/commit/84dcfc45b9a354827b9bbf6ae58902d04e8fe915

Bug#1017593: Haruna: haruna watch file should point to the official release tarball location

[Rik Mills]

Package: haruna
Version: 0.8.0-1

The haruna watch file incorrectly points to .tar.gz tarball generated 
from git tags on invent.kde.org


watch files for KDE projects should point to the official release 
tarballs on download.kde.org


In this case in: https://download.kde.org/stable/haruna/ in .xz format

PS. 0.9.0 is out :D

Bug#1011624: kdesu: kdesu fails to authenticate with sudo from testing/unstable

[Rik Mills]

Package: kdesu
Version: 5.93.0-1
Severity: serious

kdesu fails to authenticate with sudo from testing/unstable.

Examples: launching ksystemlog from the main menu, or trying to run 
krusader root mode option via its 'Tools > Start Krusader Root Mode' 
menu entry. Assuming that the current user is a member of the sudo group.


On entering the correct password authentication is refused, stating that 
possibly an incorrect password has been entered.


It appears that kdesu fails to cope with the sudo config CVE fix in this 
commit:


https://salsa.debian.org/sudo-team/sudo/-/commit/59db341d46aa4c26b54c1270e69f2562e7f3d751

KDE bug: https://bugs.kde.org/show_bug.cgi?id=452532

The issue can be worked around by adding /etc/sudoers.d/kdesu with the 
contents


Defaults!/usr/lib/*/libexec/kf5/kdesu_stub !use_pty

Bug#1006678: ukui-settings-daemon: FTBFS against libkscreen 5.24.2

[Rik Mills]

Package: ukui-settings-daemon
Version: 3.1.1-1
Severity: serious
Tags: ftbfs

In current Debian unstable (and Ubuntu Jammy), ukui-settings-daemon
FTBFS against the latest Plasma libkscreen 5.24.2.

xrandr-output.cpp: In static member function ‘static void
xrandrOutput::readInOutputs(KScreen::ConfigPtr, const QVariantList&)’:
xrandr-output.cpp:368:21: error: ‘class KScreen::Output’ has no member
named ‘setLogicalSize’
  368 | output->setLogicalSize(QSizeF());
  | ^~

Bug#1005003: fcitx-module-quickphrase-editor5: uninstallable with fcitx due to Provides: fcitx-module-quickphrase-editor

[Rik Mills]

Package: fcitx-module-quickphrase-editor5
Version: 1.2.7-1.1

In unstable:

~# apt-get install fcitx-module-quickphrase-editor5 fcitx
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 fcitx-modules : Breaks: fcitx-module-quickphrase-editor
E: Unable to correct problems, you have held broken packages.

fcitx-module-quickphrase-editor5 Provides:
fcitx-module-quickphrase-editor, hence the breakage.

This is similar to the situation fixed previously in (1.2.3-3).

fcitx-qt5 (1.2.3-3) unstable; urgency=medium

  * Team upload.
  * Rebuild after Debian Buster release.
  * debian/control:
+ Bump Standards-Version to 4.4.0.
+ Bump debhelper compat to v12.
+ No longer let fcitx5-module-quickphrase-editor provide
  fcitx-module-quickphrase-editor since the new fcitx is
  declaring "Breaks:" relationship on the latter one.
  * debian/libfcitx-qt5-1.symbols: Add new symbols.

Bug#1003003: libqalculate FTBFS on architectures where char is unsigned

[Rik Mills]

Reported here: https://github.com/Qalculate/libqalculate/issues/378

I note that these tests are entirely new in 3.22.0, so there is no
history of them previously passing.

Bug#983306: astrometry.net combines incompatible GPL licenses

[Rik Mills]

Package: astrometry.net
Version: 0.82+dfsg-1

As a result of the rejection of the stellarsolver source package by FTP
masters for combining incompatible GPL licenses.

https://lists.debian.org/debian-qt-kde/2021/02/msg00114.html

it was pointed out that the library tree in question (libkd) is copied
from the astrometry.net project sources, and that a similar issue exists
in it.

See: https://github.com/dstndstn/astrometry.net/issues/212

astrometry.net have resolved the issue by swapping the GPL2 only
licensed code (which was copied by astrometry.net from the linux kernel)
with the FreeBSD implementation.

https://github.com/dstndstn/astrometry.net/commit/e1b21dcf14d86f0f40bf1052011f89a0697c9541

however, if the license issue is/was valid, then as commented in the
upstream issue by DD Pino Toscano, it may render current and some
previous Debian binaries undistributable.

Bug#964558: Please change the ibus Recommends in ibus-data to a Suggests

[Rik Mills]

Could someone please make an upload to unstable with this change?
Kubuntu would like to see this change. Thanks.

Bug#963706: kdenlive with ffmpeg version 7:4.3-2 can't Render Project to MP4

[Rik Mills]

On 11/07/2020 04:14, Stephen Hwang wrote:
> I encountered bug #963706 last week, and was happy to see that it had been 
> addressed 
> in version 20.04.3-1 uploaded today, July 10. Unfortunately, the new version 
> does 
> not appear to fix the bug for me.

As previously mentioned, the issue is with MLT, and it is that which
requires a rebuild against the new ffmpeg. That is why this bug was not
fixed via the new kdenlive upload.

Bug#963706: (no subject)

[Rik Mills]

This can be fixed by a no-change rebuild of MLT against the new ffmpeg.
This has been done in Ubuntu, and confirmed to fix the issue.

Bug#934808: kbackup's docbook handbook files cannot be read by khelpcentre

[Rik Mills]

Package: kbackup
Version: 18.12.1-1
Version: 19.04.3-1

kbackup build gzips the produced .docbook files, meaning khelpcentre
cannot read them and reports the docs as missing.

Reproduce with 'Help > Help Centre Handbook' or by pressing F1 in kbackup

In debian/rules the package is built with simple dh $@

Additionally passing '--with kf5' to dh should ensure the .docbooks are
not compressed, so can be found and read by khelpcentre

Bug#861960: kmail fatal startup error "Invalid parent"

[Rik Mills]

On Thu, 07 Mar 2019 00:59:30 -0600 Nazar Zhuk  wrote:

> After the first time, KMail opens normally. I attempted the following to
> reproduce on subsequent launches but was not successful:
> 
> - stopped akonadi
> - deleted:
> ~/.cache
> ~/.config/akonadi*
> ~/.config/kmail*
> ~/.local/share/akonadi*
> ~/.local/share/kmail*
> 
> --
> Nazar

You also need to remove:

~/.config/specialmailcollectionsrc

to reproduce.

If that files exists with the default content, then there is no startup
crash.

Bug#915391: Regression: KDE's Kio fails to build on i386 and armhf with cmake >= 3.13

[Rik Mills]

Package: cmake
Version: 3.13.1-1

With cmake >= 3.13 the KDE Framework Kio fails to build on i386 and
armhf with the error shown below:

Confirmed on current debian unstable rebuilding kio from source. Also
confirmed in Ubuntu with 3.13.1-1 (now removed) synced to 19.04.

Report upstream: https://gitlab.kitware.com/cmake/cmake/issues/18669

and Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1806276


*** build error ***

In file included from /build/kio-5.51.0/src/core/slaveinterface.cpp:441:
/build/kio-5.51.0/obj-i686-linux-gnu/src/core/KF5KIOCore_autogen/include/moc_slaveinterface.cpp:
In static member function 'static void
KIO::SlaveInterface::qt_static_metacall(QObject*, QMetaObject::Call,
int, void**)':
/build/kio-5.51.0/obj-i686-linux-gnu/src/core/KF5KIOCore_autogen/include/moc_slaveinterface.cpp:171:22:
error: 'class KIO::SlaveInterface' has no member named 'open64'; did you
mean 'open'?
 case 10: _t->open64(); break;
  ^~
  open
/build/kio-5.51.0/obj-i686-linux-gnu/src/core/KF5KIOCore_autogen/include/moc_slaveinterface.cpp:280:84:
error: 'open64' is not a member of 'KIO::SlaveInterface'
 if (*reinterpret_cast<_t *>(_a[1]) ==
static_cast<_t>(::open64)) {

   ^~
/build/kio-5.51.0/obj-i686-linux-gnu/src/core/KF5KIOCore_autogen/include/moc_slaveinterface.cpp:
At global scope:
/build/kio-5.51.0/obj-i686-linux-gnu/src/core/KF5KIOCore_autogen/include/moc_slaveinterface.cpp:475:6:
error: no declaration matches 'void KIO::SlaveInterface::open64()'
 void KIO::SlaveInterface::open64()
  ^~~
/build/kio-5.51.0/obj-i686-linux-gnu/src/core/KF5KIOCore_autogen/include/moc_slaveinterface.cpp:475:6:
note: no functions named 'void KIO::SlaveInterface::open64()'
In file included from /build/kio-5.51.0/src/core/slaveinterface.cpp:19:
/build/kio-5.51.0/src/core/slaveinterface.h:102:22: note: 'class
KIO::SlaveInterface' defined here
 class KIOCORE_EXPORT SlaveInterface : public QObject
  ^~
make[3]: *** [src/core/CMakeFiles/KF5KIOCore.dir/build.make:517:
src/core/CMakeFiles/KF5KIOCore.dir/slaveinterface.cpp.o] Error 1
make[3]: *** Waiting for unfinished jobs
make[3]: Leaving directory '/build/kio-5.51.0/obj-i686-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:9841:
src/core/CMakeFiles/KF5KIOCore.dir/all] Error 2
make[2]: Leaving directory '/build/kio-5.51.0/obj-i686-linux-gnu'
make[1]: *** [Makefile:144: all] Error 2
make[1]: Leaving directory '/build/kio-5.51.0/obj-i686-linux-gnu'
dh_auto_build: cd obj-i686-linux-gnu && make V=1 -j4 "INSTALL=install
--strip-program=true" returned exit code 2
make: *** [debian/rules:7: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit
status 2

Bug#898958: peruse: does not start

[Rik Mills]

On 18/05/18 14:25, Juhani Numminen wrote:
> On Thu, 17 May 2018 22:01:59 +0200 Serge Kilimoff-Goriatchkine 
>  wrote:
> are you aware of the Ubuntu changes? Looks like they're related to this issue.
> https://patches.ubuntu.com/p/peruse/peruse_1.2+dfsg-2ubuntu1.patch

Yes, the issue has been brought to Simon and the KDE team's attention.

It is an unfortunate oversight that the wrong version of Kirigami was
assumed as required. While I could 'band aid fix' this in Ubuntu quite
easily, as we had not removed Kirigami v1 source anticipating packaging
persue at a much earlier time, in debian it has been removed.

Both peruse 1.2 branch and Kirigami v1 are unlikely to get much upstream
support in the form of bugfix updates, so at least for debian I think
the consensus was to entourage upstream KDE to release the new Kirigami
v2 based persue as soon as the KDE developer is happy to, and fix the
issue with nice new version of that.

Rik

Bug#888144: FTBFS with libappstreamqt-dev 0.11.8-1

[Rik Mills]

Confirmed from Kubuntu CI that plasma-workspace 5.12 stable branch and
master also FTBFS against the 0.11.8-1 upload.

Bug#888144: FTBFS with libappstreamqt-dev 0.11.8-1

[Rik Mills]

Appstream 0.11.8-1 synced to Ubuntu some hours ago, and is now causing
similar build failures.

For example in plasma-workspace:
https://launchpad.net/ubuntu/+source/plasma-workspace/4:5.11.5-0ubuntu2

Same failures also on Kubuntu CI, if I let that build against the bionic
proposed pocket where 0.11.8 currently sits.

Bug#880166: regression in dpkg-gensymbols output on symbols changes

[Rik Mills]

Hi, and happy new year

Could the patch from Dmitry Shachnev applied to dpkg soonish if that is ok?

I have patched it for Kubuntu's CI repositories, so temporarily our
symbols handling is not messed up, but it would obviously be better if
the correct output could be fixed at debian's end and then synced to the
main ubuntu archive.

Thank you

Rik Mills
Kubuntu Developer

Bug#880166: regression in dpkg-gensymbols output on symbols changes

[Rik Mills]

Also tracked in:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1728847

Bug#880166: regression in dpkg-gensymbols output on symbols changes

[Rik Mills]

On 30/10/17 09:13, Dmitry Shachnev wrote:
> The attached small patch fixes the issue for me. Tested with libjpeg-turbo,
> where one symbol was deliberately removed.
> 
> The previous if (defined $state) check was always true, because a //=
> operator is used to define $state two lines above.
> 
> --
> Dmitry Shachnev
> 

This patch appears to fix the issue for me on the libjpeg-turbo test
case, and builds on the kubuntu CI which was having issues on not seeing
the correct output in build logs.

Bug#880166: regression in dpkg-gensymbols output on symbols changes

[Rik Mills]

Package: dpkg
Version: 1.19.0.4

The output of dpkg-gensymbols has regressed when reporting new or
changed symbols

Previously the output stated:

dpkg-gensymbols: debian/libnameDEBIAN/symbols doesn't match completely
debian/libname.symbols

this now incorrectly states:

dpkg-gensymbols: warning: no debian/symbols file used as basis for
generating debian/libname/DEBIAN/symbols