Fixed upstream with:
https://invent.kde.org/network/kdenetwork-filesharing/-/commit/6cbdd2bd71b3d6f030f06114978743414d4f
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.
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 (bui
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
Reported upstream in: https://bugs.kde.org/show_bug.cgi?id=459309
Fixed by:
https://invent.kde.org/plasma/plasma-workspace/-/commit/84dcfc45b9a354827b9bbf6ae58902d04e8fe915
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
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
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
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
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.
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
Could someone please make an upload to unstable with this change?
Kubuntu would like to see this change. Thanks.
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
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.
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
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*
>
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:
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
Confirmed from Kubuntu CI that plasma-workspace 5.12 stable branch and
master also FTBFS against the 0.11.8-1 upload.
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
and then synced to the
main ubuntu archive.
Thank you
Rik Mills
Kubuntu Developer
Also tracked in:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1728847
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.
>
>
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:
24 matches
Mail list logo