Bug#1072425: k3b: FTBFS with ffmpeg 7.0: k3bf fmpegwrapper.cpp:143:26: error: ‘AVCodecContext’ {aka ‘struct AVCodecContext’} has no member named ‘channels’ xt’ {aka ‘struct AVCodecContext’} has n o m

[Diederik de Haas]

Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=485432
Control: tag -1 +upstream

On 2 Jun 2024 15:20:46 +0200 Sebastian Ramacher  wrote:
> Source: k3b
> Version: 23.08.3-1
> Severity: important
> Tags: trixie sid ftbfs
> Usertags: ffmpeg-7.0
> 
> Hi,
> 
> during a rebuild of the reverse dependencies for the transition to
> ffmpeg 7.0, your package failed to build

In the upstream git repo there are 2 commits on 2024-04-13 which probably do 
fix the FTBFS issue, but don't make it compatible with ffmpeg 7.0.
F.e. it now just returns '0' for the number of channels with ffmpeg 7.0, while 
it does return the actual value when < 7.0 ...

So, linking to those commits seems pointless.

signature.asc
Description: This is a digitally signed message part.

Bug#1050240: libqt5location5: Tiles not loading

[Raymond de Vries]

Package: libqt5location5
Version: 5.15.8+dfsg-3
Severity: grave
Tags: bookworm
Justification: renders package unusable
X-Debbugs-Cc: raym...@orphiction.nl

Dear Maintainer,

Tiles are not loaded by qtlocation without this change.

The maintainer already showed that is fix is possible using unstable. A similar
fix is created for bookworm and now tiles are loaded as expected.


-- System Information:
Debian Release: 12.1
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-11-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 libqt5location5 depends on:
ii  libc6  2.36-9+deb12u1
ii  libgcc-s1  12.2.0-14
ii  libqt5core5a [qtbase-abi-5-15-8]   5.15.8+dfsg-11
ii  libqt5gui5 5.15.8+dfsg-11
ii  libqt5positioning5 5.15.8+dfsg-3
ii  libqt5positioningquick55.15.8+dfsg-3
ii  libqt5qml5 [qtdeclarative-abi-5-15-8]  5.15.8+dfsg-3
ii  libqt5qmlmodels5   5.15.8+dfsg-3
ii  libqt5quick5-gles  5.15.8+dfsg-1
ii  libstdc++6 12.2.0-14

libqt5location5 recommends no packages.

libqt5location5 suggests no packages.

-- no debconf information
Index: 
qtlocation-everywhere-src-5.15.8/src/location/labs/qsg/qgeomapobjectqsgsupport.cpp
===
--- 
qtlocation-everywhere-src-5.15.8.orig/src/location/labs/qsg/qgeomapobjectqsgsupport.cpp
 2022-11-10 21:42:35.0 +0100
+++ 
qtlocation-everywhere-src-5.15.8/src/location/labs/qsg/qgeomapobjectqsgsupport.cpp
  2023-08-22 12:03:25.950516809 +0200
@@ -158,7 +158,7 @@
 if (!root)
 return;
 
-if (m_mapObjectsRootNode && m_mapObjectsRootNode->parent())
+if (m_mapObjectsRootNode && !m_mapObjectsRootNode->parent())
 root->appendChildNode(m_mapObjectsRootNode.get());
 
 if (!m_mapObjectsRootNode) {

Bug#1034679: libkf5coreaddons5: Prints debug info to stdout (when using `gitk`)

[Diederik de Haas]

Package: libkf5coreaddons5
Version: 5.103.0-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I'm not sure exactly when it started happening, but lately when I run
`gitk` I get a whole bunch of what I consider debug info printed in my
Konsole window:

diederik@prancing-pony:~$ gitk 
arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi
kf.coreaddons: Checking for plugins in ("/usr/bin/kf5/kio", 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_file.so" 
supports protocols ("file")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_ftp.so" 
supports protocols ("ftp")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_ghelp.so" 
supports protocols ("ghelp")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_help.so" 
supports protocols ("help")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_http.so" 
supports protocols ("http", "https", "webdav", "webdavs")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_remote.so" 
supports protocols ("remote")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_trash.so" 
supports protocols ("trash")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/metainfo.so" 
supports protocols ("metainfo")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_bluetooth.so" 
supports protocols ("bluetooth")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_obexftp.so" 
supports protocols ("obexftp")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/baloosearch.so" 
supports protocols ("baloosearch")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/tags.so" supports 
protocols ("tags")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/timeline.so" 
supports protocols ("timeline")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/applications.so" 
supports protocols ("applications", "programs")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/desktop.so" 
supports protocols ("desktop")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_fonts.so" 
supports protocols ("fonts")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/ldap.so" supports 
protocols ("ldap", "ldaps")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/akonadi.so" 
supports protocols ("akonadi")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_kamera.so" 
supports protocols ("camera")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kdeconnect.so" 
supports protocols ("kdeconnect")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/about.so" supports 
protocols ("about")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/activities.so" 
supports protocols ("activities")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/archive.so" 
supports protocols ("ar", "sevenz", "tar", "zip")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/bookmarks.so" 
supports protocols ("bookmarks")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/filter.so" supports 
protocols ("bzip", "bzip2", "gzip", "lzma", "xz", "zstd")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/fish.so" supports 
protocols ("fish")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/info.so" supports 
protocols ("info")
kf.kio.core: 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_filenamesearch.so" supports 
protocols ("filenamesearch")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/man.so" supports 
protocols ("man")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/mtp.so" supports 
protocols ("mtp")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/nfs.so" supports 
protocols ("nfs")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/recentdocuments.so" 
supports protocols ("recentdocuments")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/recentlyused.so" 
supports protocols ("recentlyused")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/sftp.so" supports 
protocols ("sftp")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/smb.so" supports 
protocols ("cifs", "smb")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/thumbnail.so" 
supports protocols ("thumbnail")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_msits.so" 
supports protocols ("ms-its")
kf.kio.core: Loading deprecated protocol file, please port it to JSON metadata 
"/usr/share/kservices5/ksvn+file.protocol"
kf.kio.core: Loading deprecated protocol file, please port it to JSON metadata 
"/usr/share/kservices5/ksvn+http.protocol"
kf.kio.core: Loading deprecated protocol file, please port it to JSON metadata 
"/usr/share/kservices5/ksvn+https.protocol"
kf.kio.core: Loading deprecated protocol file, please port it to JSON metadata 
"/usr/share/kservices5/ksvn+ssh.protocol"
kf.kio.core: Loading deprecated protocol file, please 

Bug#1005134: Adding fwupd and plasma-discover-backend-fwupd as default packages to install on KDE to prompt the user for firmware updates

[Diederik de Haas]

On 07 Feb 2022 17:36:53 + mYnDstrEAm  wrote:
> Please add fwupd and plasma-discover-backend-fwupd as a default package

https://bugs.debian.org/1003973 is a/the bug where default installation of 
fwupd is discussed.

> included on Debian12/KDE. This would make "Discover" show available firmware
> updates. There would be a tray notification about available updates on KDE
> and updating firmware can be integrated into the updating process.

The plasma-discover-backend-fwupd package is already a suggest of 
plasma-discover, so possibly a recommends instead is requested here?
I'll leave that and a possible reassignment of this bug up to the maintainers, 
but please don't make too hard to install KDE without discover.


signature.asc
Description: This is a digitally signed message part.

Bug#961551: partitionmanager: Does not start - "Session bus not found"

[Diederik de Haas]

On Tuesday, 25 January 2022 21:56:06 CET scott092...@aol.com wrote:
> I just now ran partitionmanager from the terminal, and as usual, got no info
> in the displayed window.
> 
> Here is the terminal output:
> 
> 
> scott@ASUS-Prime-B350MA:~$ partitionmanager
> Could not load plugin for core backend  "" :  "The shared library was not
> found." Loaded backend plugin:  "pmsfdiskbackendplugin"

At this point you should've gotten a prompt by PolicyKit (KDE Agent) for your 
(user) password and after that, you should've seen:
> "Using backend plugin: pmsfdiskbackendplugin (1)"

And after that you should see your partitions loaded in the GUI.

So maybe you're missing a required program? I don't know which, but check 
whether you have 'udisks2' and/or 'policykit-1' installed.

Cheers,
  Diederik

BTW: it looks like it's not properly responding to the 'Cancel' button and a 
failed 'login' attempt brings back the password dialog. Endlessly AFAICT.
After (way?) more then 5 attempts for each, the only way out appears to be to 
provide the correct password.
I'd say that's a bug too, but a different one.

signature.asc
Description: This is a digitally signed message part.

Bug#1004204: libqt5webenginecore5: Fails to upgrade to Sid version

[Diederik de Haas]

Control: severity -1 important

On Saturday, 22 January 2022 19:02:27 CET Elijah wrote:
> pkg-deb (subprocess): decompressing archive
> '/var/cache/apt/archives/libqt5webenginecore5_5.15.8+dfsg-1_amd64.deb'
> (size=39497412) member 'data.tar': lzma error: compressed data is corrupt

What happens if you delete that file and do a new apt update && apt upgrade?

On my Sid system the upgrade to 5.15.8+dfsg-1 was successful, so downgrading 
the severity to important.

signature.asc
Description: This is a digitally signed message part.

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

[Diederik de Haas]

Hi Paul,

On Thursday, 11 November 2021 14:56:29 CET Paul Gevers wrote:
> 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".

It was my assumption that you (and others) didn't get that hint, otherwise you 
(and others) would (very) likely have mentioned it.
The hint I got explains why the setting was/got disabled, without people 
recollecting that they had disabled it and that's why I shared it :-)

Cheers,
  Diederik

signature.asc
Description: This is a digitally signed message part.

Bug#998203: yakuake's icon does not come in mate notification area

[Diederik de Haas]

On Monday, 1 November 2021 11:57:52 CET shirish शिरीष wrote:
> Because there is no notification, it is difficult to know when Yakuake
> has started or not.

AFAIK it's always started as soon as you log in.
I would actually find an item in the notification area/systray a regression/bug 
as it's meant to be out of your way/sight, but available when you need it (via 
F12 by default).
It could be that it does actually put out a notification via the notification 
system (ie a 'popup'), but I have disabled that as I found even that annoying.

So the answer to 'when is it available?' is: Always.

signature.asc
Description: This is a digitally signed message part.

Bug#998203: yakuake's icon does not come in mate notification area

[Diederik de Haas]

On Sunday, 31 October 2021 23:42:13 CET shirish शिरीष wrote:
> I am running yakuake on Debian-mate. But it seems that in the
> notification area for some reason yakuake is not seen :( . Sharing a
> screenshot of the notification area.

I'm running fully KDE and I don't have a notification entry for yakuake and in 
System Tray Settings there isn't an entry for yakuake either, so I'm inclined 
to think it's working as intended. Konsole doesn't have an entry either.
If I'm misunderstanding your bug report, can you clarify what you think you 
are missing?

signature.asc
Description: This is a digitally signed message part.

Bug#993546: kmail: KMail sees different signing key on same mail when enabling debian-keyring

[Diederik de Haas]

Control: reassign -1 libqgpgme7 1.16.0-1
Control: retitle -1 GPGMe does not take additional keyring into account to find 
keys.
Control: affects -1  kmail

On woensdag 15 september 2021 10:56:59 CEST Sandro Knauß wrote:
> > Thanks for your assistance. I've save the signature as 'signature.asc' and
> > the signed part of the email msg to 'attempt3-dos.txt'
> 
> great. Can you now do the same test. commenting/uncommenting the keyring
> line in the gpgconf? And kill gpg-agent in between to make 100% sure, that
> no left overs are taken.

I've rename 'signature.asc' to 'joostvb-signature.asc' and 'attempt3-dos.txt'
to 'joostvb-signed-msg-part-dos.txt' and ran the tests you requested.

=
$ killall gpg-agent
$ ps aux | grep gpg-agent | grep -v grep
$ vim ~/.gnupg/gpg.conf 
$ tail -n1 ~/.gnupg/gpg.conf 
#keyring /usr/share/keyrings/debian-keyring.gpg
$ ps aux | grep gpg-agent | grep -v grep
diederik   12992  0.0  0.0 154884  3600 ?SLs  12:32   0:00 
/usr/bin/gpg-agent --supervised
$ gpg --verify joostvb-signature.asc joostvb-signed-msg-part-dos.txt 
gpg: Signature made di 31 aug 2021 16:07:34 CEST
gpg:using RSA key 92AAD901B21B4BC79A47A03054F1A66317486713
gpg: Good signature from "Joost E. van Baal (Nederland, 1970)" [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal-Ilić" [full]
Primary key fingerprint: B8FA C2E2 5047 5B8C E940  A919 5793 0DAB 0B86 B067
 Subkey fingerprint: 92AA D901 B21B 4BC7 9A47  A030 54F1 A663 1748 6713
$ killall gpg-agent
$ ps aux | grep gpg-agent | grep -v grep
$ vim ~/.gnupg/gpg.conf 
$ tail -n1 ~/.gnupg/gpg.conf 
keyring /usr/share/keyrings/debian-keyring.gpg
$ ps aux | grep gpg-agent | grep -v grep
diederik   13025  1.2  0.0 228616  3608 ?SLs  12:33   0:00 
/usr/bin/gpg-agent --supervised
$ gpg --verify joostvb-signature.asc joostvb-signed-msg-part-dos.txt 
gpg: Signature made di 31 aug 2021 16:07:34 CEST
gpg:using RSA key 92AAD901B21B4BC79A47A03054F1A66317486713
gpg: Good signature from "Joost E. van Baal (Nederland, 1970)" [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal-Ilić" [full]
Primary key fingerprint: B8FA C2E2 5047 5B8C E940  A919 5793 0DAB 0B86 B067
 Subkey fingerprint: 92AA D901 B21B 4BC7 9A47  A030 54F1 A663 1748 6713
=

On woensdag 15 september 2021 13:16:21 CEST you wrote:
> That seems fine, as the gpg-agent has restarted. So I think we are ready to
> move this bug to gpgme. But anyways this all sounds like an upstream bug,
> so properly you have to create a bug at https://dev.gnupg.org/

I'll wait what the gpgme maintainers have to say first, before I('ll have to)
go through the trouble of creating an account there ...

Cheers,
  Diederik

signature.asc
Description: This is a digitally signed message part.

Bug#993546: kmail: KMail sees different signing key on same mail when enabling debian-keyring

[Diederik de Haas]

On zondag 12 september 2021 19:57:17 CEST Sandro Knauß wrote:
> But first make sue, that you are really have an valid bug. Please verify the
> signature in a konsole via gpg --verify. I expect, that it will fail with
> the same error.

Thanks for your assistance. I've save the signature as 'signature.asc' and the 
signed part of the email msg to 'attempt3-dos.txt'

$ gpg --verify signature.asc attempt3-dos.txt 
gpg: Signature made di 31 aug 2021 16:07:34 CEST
gpg:using RSA key 92AAD901B21B4BC79A47A03054F1A66317486713
gpg: Good signature from "Joost E. van Baal (Nederland, 1970)" [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal-Ilić" [full]
Primary key fingerprint: B8FA C2E2 5047 5B8C E940  A919 5793 0DAB 0B86 B067
 Subkey fingerprint: 92AA D901 B21B 4BC7 9A47  A030 54F1 A663 1748 6713

Hoping/expecting to validate the message against my keyring with "gpg --verify 
attempt3-dos.txt" failed as "gpg --verify" wants the signature file as first 
parameter.

Let me know what else I can do.

Cheers,
  Diederik

signature.asc
Description: This is a digitally signed message part.

Bug#993546: kmail: KMail sees different signing key on same mail when enabling debian-keyring

[Diederik de Haas]

Hoi,

On zondag 12 september 2021 19:57:17 CEST Sandro Knauß wrote:
> I'm quite sure, that this is not the issue of Kmail, as Kmail is using the
> GPGME to talk to gpg. So it will be an issue of libqgpgme7.

Ok. I noticed the issue in KMail, so I reported it against that package.
Feel free to reassign to an (more) appropriate package.

> But first make sure, that you are really have an valid bug. Please verify the
> signature in a konsole via gpg --verify. I expect, that it will fail with
> the same error.

How can I do that?

I've saved the msg as an mbox file and ran 'gpg --verify' on it:
gpg --verify Joostvb-orig-signed-msg.mbox 
gpg: no signed data
gpg: can't hash datafile: No data

That looks weird as it's certainly a signed msg. 
Let's try mutt (me = mutt newbie):
mutt -f Joostvb-orig-signed-msg.mbox
I see "1  Ns " ;  to view it and I see:
[-- Begin signature information --]
Good signature from: Joost E. van Baal (Nederland, 1970)
  aka: 
  
  created: 
[-- End signature information --]

After 'i' to Exit, the lowercase 's' turned into a capital 'S'. 
Which IIUC indicates a valid signature.

So mutt seems happy. ~/.gnupg/gpg.conf had the debian-keyring enabled.

After disabling debian-keyring:
gpg --verify Joostvb-orig-signed-msg.mbox 
gpg: no signed data
gpg: can't hash datafile: No data
mutt -f Joostvb-orig-signed-msg.mbox
I see "1  s " ;  to view it and I see:
[-- Begin signature information --]
Good signature from: Joost E. van Baal (Nederland, 1970)
  aka: 
  
  created: 
[-- End signature information --]

After Exit, the lowercase 's' turned into a capital 'S' again. 

So with mutt everything _looks_ the same with the debian-keyring
enabled or disabled, while there is a difference in KMail.

> Keep in mind that Joot's using a subkey to sign ( 0x54F1A66317486713), this
> subkey needs to be available also to verify the signature.
> 
> > When doing "gpg --list-keys 0x57930DAB0B86B067" (or long key ID)
> > (with "list-options show-keyring=yes" in my gpg.conf) I see the same key
> > present in my keyring (pubring.kbx) and in Debian's debian-keyring.gpg.
> 
> As I was told you alsoways have to use --with-colons when using
> gpg --list-keys  --with-colons  to get ideas about the key status.

With debian-keyring disabled:
$ gpg --with-colons --list-keys 0x57930DAB0B86B067
tru::1:1631360998:1645731991:3:1:5
pub:f:4096:1:57930DAB0B86B067:1129127891:::f:::scESC::23:1630521551:1 
http\x3a//keyring.debian.org\x3a11371:
fpr:B8FAC2E250475B8CE940A91957930DAB0B86B067:
uid:f1129129467::D3568B2F561D7D224C0894CE39E650FC67F0755B::Joost E. van 
Baal (Nederland, 1970):1630521551:1:
uid:f1129129236::404399E9298441B5AFF1F09D9A6314F6D0DF12FF::Joost van Baal 
:1630521551:1:
uid:f1129129331::06AF0BE4F14BBC6BEDF47674B6BCD74AEBBA5FA5::Joost van Baal 
:1630521551:1:
uid:f1129129295::83F7EC80DEAB05929AE4829E7FE6A07468F1B557::Joost van Baal 
:1630521551:1:
uid:f1129129358::ECC854CC7EAFC26121A339FF41A0D1917097C7D7::Joost van Baal 
:1630521551:1:
uid:f1129129385::1857D9EC456DEEE1C4FC2C1207E9C2B9A8F844E2::Joost van Baal 
:1630521551:1:
uid:f1223447825::0BC514AB9B9027517C311BEDC30A59E551EB4D16::Joost van Baal 
:1630521551:1:
uid:f1318359511::9E04CD3B93ECF31B7BAC1315EBAE5D5B987EF556::Joost van 
Baal-Ilić:1630521551:1:
sub:e:4096:1:A96539F624525E9E:1129128272:1223736272:s::23:
fpr:C5B85256C175C10CBD0832A4A96539F624525E9E:
sub:e:4096:1:F98CBB23C0BC6980:1223447515:1318055515:s::23:
fpr:ABB0F0BF85D70496B35D0B7CF98CBB23C0BC6980:
sub:e:2048:1:33517A72A5E6B0C8:1318359158:1476039158:s::23:
fpr:B9563AB8479744C26035A9F933517A72A5E6B0C8:
sub:f:4096:1:54F1A66317486713:1476171990:1728387017:s::23:
fpr:92AAD901B21B4BC79A47A03054F1A66317486713:
sub:f:4096:1:F4E66A7265F23E7B:1476172439:1728387066:e::23:
fpr:A9202D9E6ADD2C7E7301DEE8F4E66A7265F23E7B:
sub:e:2048:1:88FEF971404CA6BE:1318359224:1476039224:e::23:
fpr:2A3FED2354D9264FBF0184D688FEF971404CA6BE:
sub:e:4096:1:5B19798443FF7C14:1129128610:1223736610:e::23:
fpr:7C2AB7A44CD6F96538CD88F05B19798443FF7C14:
sub:e:4096:1:8A551DB0EC34F0AE:1223447782:1318055782:e::23:
fpr:9B60E5A6C3DBCAB264A56F4E8A551DB0EC34F0AE:

With debian-keyring enabled:
$ gpg --with-colons --list-keys 0x57930DAB0B86B067
tru::1:1631360998:1645731991:3:1:5
pub:f:4096:1:57930DAB0B86B067:1129127891:::f:::scESC::23:1630521551:1 
http\x3a//keyring.debian.org\x3a11371:
fpr:B8FAC2E250475B8CE940A91957930DAB0B86B067:
uid:f1129129467::D3568B2F561D7D224C0894CE39E650FC67F0755B::Joost E. van 
Baal (Nederland, 1970):1630521551:1:

Bug#993441: kleopatra: Creates unsafe ~/.gnupg when not already present

[Diederik de Haas]

On dinsdag 7 september 2021 11:32:28 CEST Peter Green wrote:
>  > Version: 4:21.08.0-1
> 
> You filed this against the version in sid? 

I run Sid as my daily driver, so yes. That's what I (almost?) always do.

> have you investigated whether earlier versions are also affected?

No, I did not.

signature.asc
Description: This is a digitally signed message part.

Bug#993546: kmail: KMail sees different signing key on same mail when enabling debian-keyring

[Diederik de Haas]

On donderdag 2 september 2021 23:15:47 CEST Diederik de Haas wrote:
> KMail reports (after I signed it)

The signing part is irrelevant for reproducing the bug.
I experienced the exact same problem before I signed it.

signature.asc
Description: This is a digitally signed message part.

Bug#993546: kmail: KMail sees different signing key on same mail when enabling debian-keyring

[Diederik de Haas]

Package: kmail
Version: 4:21.08.0-2
Severity: normal

Recently I received a signed email from Debian Developer joostvb@d.o.
I imported his public key to my keyring as follows:
gpg --keyserver keyring.debian.org --recv-keys 
0xB8FAC2E250475B8CE940A91957930DAB0B86B067

When selecting that mail, KMail reports (after I signed it):
Message was signed by joos...@mdcc.cx (Key ID: 0x57930DAB0B86B067).
The signature is valid and the key is fully trusted.

Excellent, exactly as I expected.
Joost's key is also part of the debian-keyring with the (exact) same
fingerprint. I figured it would be useful to have DD's key in gpg's
keyring, so I added the following to ~/.gnupg/gpg.conf:
keyring /usr/share/keyrings/debian-keyring.gpg

But when I then first select an(y) other email and then select Joost's
email again, KMail reports the following:
Message was signed on  with unknown key 
0x92AAD901B21B4BC79A47A03054F1A66317486713.
The validity of the signature cannot be verified.
Status: Good signature

When doing "gpg --list-keys 0x57930DAB0B86B067" (or long key ID) 
(with "list-options show-keyring=yes" in my gpg.conf) I see the same key
present in my keyring (pubring.kbx) and in Debian's debian-keyring.gpg.

If I then disable the "keyring ... debian-keyring.gpg" line again, all
is well again and enabling brings the problem back.
I've also started with a completely new ~/.gnupg and could still
reproduce the problem.

I have no clue how this can happen or be explained,
but it sounds like a bug to me.

Cheers,
  Diederik

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

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

Versions of packages kmail depends on:
ii  akonadi-server   4:21.08.0-1
ii  kdepim-runtime   4:21.08.0-1
ii  kio  5.85.0-2
ii  libc62.31-17
ii  libgcc-s111.2.0-3
ii  libgpgmepp6  1.16.0-1
ii  libkf5akonadiagentbase5 [libkf5akonadiagentbase5-21.08]  4:21.08.0-1
ii  libkf5akonadicontact5 [libkf5akonadicontact5-21.08]  4:21.08.0-1
ii  libkf5akonadicore5abi2 [libkf5akonadicore5-21.08]4:21.08.0-1
ii  libkf5akonadimime5 [libkf5akonadimime5-21.08]4:21.08.0-1
ii  libkf5akonadisearch-bin  4:21.08.0-1
ii  libkf5akonadisearch-plugins  4:21.08.0-1
ii  libkf5akonadisearchdebug5 [libkf5akonadisearchdebug5-21.08]  4:21.08.0-1
ii  libkf5akonadisearchpim5 [libkf5akonadisearchpim5-21.08]  4:21.08.0-1
ii  libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-21.08]  4:21.08.0-1
ii  libkf5bookmarks5 5.85.0-2
ii  libkf5calendarcore5abi2  5:5.85.0-2
ii  libkf5calendarutils5 [libkf5calendarutils5-21.08]4:21.08.0-1
ii  libkf5codecs55.85.0-2
ii  libkf5completion55.85.0-2
ii  libkf5configcore55.85.0-2
ii  libkf5configgui5 5.85.0-2
ii  libkf5configwidgets5 5.85.0-2
ii  libkf5contacts5  5:5.85.0-2
ii  libkf5coreaddons55.85.0-2
ii  libkf5crash5 5.85.0-2
ii  libkf5dbusaddons55.85.0-2
ii  libkf5grantleetheme-plugins  21.08.0-1
ii  libkf5gravatar5abi2 [libkf5gravatar5-21.08]  4:21.08.0-1
ii  libkf5guiaddons5 5.85.0-2
ii  libkf5i18n5  5.85.0-2
ii  libkf5iconthemes55.85.0-2
ii  libkf5identitymanagement5 [libkf5identitymanagement5-21.08]  21.08.0-1
ii  libkf5itemmodels55.85.0-2
ii  libkf5itemviews5 5.85.0-2
ii  libkf5jobwidgets55.85.0-2
ii  libkf5kcmutils5  5.85.0-2
ii  libkf5kiocore5   5.85.0-2
ii  libkf5kiofilewidgets5

Bug#993441: kleopatra: Creates unsafe ~/.gnupg when not already present

[Diederik de Haas]

Package: kleopatra
Version: 4:21.08.0-1
Severity: grave
Tags: security
Justification: user security hole
X-Debbugs-Cc: Debian Security Team 

I had previously 'improved' my gnupg configuration, but that is (now)
deprecated.
So I moved my ~/.gnupg directory to a backup location to start anew.

If I then start Kleopatra, but don't do anything with it, that directory
gets created, but with the wrong permissions:
diederik@bagend:~$ stat .gnupg/
  File: .gnupg/
  Size: 4096Blocks: 8  IO Block: 4096   directory
Device: 10304h/66308d   Inode: 12845182Links: 3
Access: (0755/drwxr-xr-x)  Uid: ( 1000/diederik)   Gid: ( 1000/diederik)

Running a gpg command from a Konsole window reports the issue:
diederik@bagend:~$ gpg --list-keys
gpg: WARNING: unsafe permissions on homedir '/home/diederik/.gnupg'


If I uninstall Kleopatra and remove the ~/.gnupg directory (again) and
then do 'gpg --list-keys', I get:
diederik@bagend:~$ gpg --list-keys
gpg: directory '/home/diederik/.gnupg' created
gpg: keybox '/home/diederik/.gnupg/pubring.kbx' created
gpg: /home/diederik/.gnupg/trustdb.gpg: trustdb created
diederik@bagend:~$ stat .gnupg/
  File: .gnupg/
  Size: 4096Blocks: 8  IO Block: 4096   directory
Device: 10304h/66308d   Inode: 12845180Links: 2
Access: (0700/drwx--)  Uid: ( 1000/diederik)   Gid: ( 1000/diederik)

So Kleopatra creates ~/.gnupg with incorrect permissions when the
directory doesn't exist.

Cheers,
  Diederik

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

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

Versions of packages kleopatra depends on:
ii  dirmngr2.2.27-2
ii  gnupg  2.2.27-2
ii  gpgsm  2.2.27-2
ii  libassuan0 2.5.5-1
ii  libc6  2.31-17
ii  libgcc-s1  11.2.0-3
ii  libgpg-error0  1.42-3
ii  libgpgme11 1.16.0-1
ii  libgpgmepp61.16.0-1
ii  libkf5codecs5  5.85.0-2
ii  libkf5configcore5  5.85.0-2
ii  libkf5configgui5   5.85.0-2
ii  libkf5configwidgets5   5.85.0-2
ii  libkf5coreaddons5  5.85.0-2
ii  libkf5crash5   5.85.0-2
ii  libkf5dbusaddons5  5.85.0-2
ii  libkf5i18n55.85.0-2
ii  libkf5iconthemes5  5.85.0-2
ii  libkf5itemmodels5  5.85.0-2
ii  libkf5libkleo5 [libkf5libkleo5-21.08]  4:21.08.0-1
ii  libkf5mime5abi1 [libkf5mime5-21.08]21.08.0-1
ii  libkf5notifications5   5.85.0-3
ii  libkf5textwidgets5 5.85.0-2
ii  libkf5widgetsaddons5   5.85.0-2
ii  libkf5windowsystem55.85.0-2
ii  libkf5xmlgui5  5.85.0-3
ii  libqgpgme7 1.16.0-1
ii  libqt5core5a   5.15.2+dfsg-10
ii  libqt5dbus55.15.2+dfsg-10
ii  libqt5gui5 5.15.2+dfsg-10
ii  libqt5network5 5.15.2+dfsg-10
ii  libqt5printsupport55.15.2+dfsg-10
ii  libqt5widgets5 5.15.2+dfsg-10
ii  libstdc++6 11.2.0-3
ii  paperkey   1.6-1
ii  pinentry-qt1.1.1-1

kleopatra recommends no packages.

kleopatra suggests no packages.

-- no debconf information

Bug#993254: sorry wrong tag

[Diederik de Haas]

Control: tag -1 -a11y

On zondag 29 augustus 2021 13:42:40 CEST k_f wrote:
> the accessibility tag is wrong



signature.asc
Description: This is a digitally signed message part.

Re: Proposal: drop Salsa CI testing for now

[Diederik de Haas]

[I shouldn't have a meaningful voice in this, but my 0.02 ...]

Normally I would be strongly against disabling tests ...

On woensdag 18 augustus 2021 21:26:04 CEST Nicholas D Steeves wrote:
> I'm also concerned that the situation is fundamentally wrong: If tests
> need to be updated with every new release, something is wrong with the
> tests, or the infrastructure...  Tests and infrastructure are supposed
> to be the controls that enable meaningful results when testing for
> correct functionality in the face of changes.

But I 100% agree with this.
Tests are meant to guard against regressions, so updating tests should be a 
rarity. If they need to be updated for every release, then they're utterly 
meaningless. It's easy to introduce new bugs in the tests or you change the 
test to get the results you desire. In the former case you should (probably) 
have tests for the tests and in the latter case you're just fooling yourself 
and others and creating a false sense of security. Which is BAD.

signature.asc
Description: This is a digitally signed message part.

Bug#989671: kontact: Trying to archive a Mail folder makes it crash

[Diederik de Haas]

Package: kontact
Version: 4:21.04.1-1
Severity: important

I'm filing it against kontact, but kmail is maybe more appropriate.
However with kontact I could generate a stacktrace, which failed with
kmail, so therefor I chose kontact. Feel free to reassign.

In 'Local Folder' I have a Mail-Achive folder with 2 subfolders 
for 2 of my mail accounts.
Earlier today I moved a bunch of mails from my (IMAP) account to the
corresponding Mail-Archive folder and that seems to went fine.
When you right-click on a folder, you can choose 'Archive Folder...' to
make an export of that folder to a .tar.bz2 file and I use that for
backup purposes. It starts the process (no idea where the/a temp file is
created though) and then at some point it crashes.

=== KCrash output 1 ===
Application: Kontact (kontact), signal: Aborted

[KCrash Handler]
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#5  0x7fe28cc98537 in __GI_abort () at abort.c:79
#6  0x7fe28ced27ec in __gnu_cxx::__verbose_terminate_handler () at 
../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95
#7  0x7fe28cedd966 in __cxxabiv1::__terminate (handler=) at 
../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:48
#8  0x7fe28cedd9d1 in std::terminate () at 
../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:58
#9  0x7fe28ceddc65 in __cxxabiv1::__cxa_throw 
(obj=obj@entry=0x55c80b21ebd0, tinfo=0x7fe1d83ef348 , dest=0x7fe1d82b01f0 
) at 
../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:95
#10 0x7fe1d8265b41 in Akonadi::Item::throwPayloadException 
(this=this@entry=0x55c818322738, spid=spid@entry=-1, mtid=mtid@entry=-1) at 
./src/core/item.cpp:463
#11 0x7fe1b900ae92 in Akonadi::Item::payload 
> (this=0x55c818322738) at /usr/include/KF5/AkonadiCore/item.h:791
#12 MailCommon::BackupJob::processMessage (this=0x7fe270009790, item=...) at 
./src/job/backupjob.cpp:232
#13 0x7fe1b900b048 in MailCommon::BackupJob::itemFetchJobResult 
(this=0x7fe270009790, job=0x7ffef3a31cd0) at ./src/job/backupjob.cpp:271
#14 0x7fe28d2eb5a6 in QtPrivate::QSlotObjectBase::call (a=0x7ffef3a31e20, 
r=0x7fe270009790, this=0x55c8016c4130) at 
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#15 doActivate (sender=0x7fe19c46a4b0, signal_index=6, 
argv=argv@entry=0x7ffef3a31e20) at kernel/qobject.cpp:3886
#16 0x7fe28d2e4900 in QMetaObject::activate 
(sender=sender@entry=0x7fe19c46a4b0, m=m@entry=0x7fe28e40dca0 
, local_signal_index=local_signal_index@entry=3, 
argv=argv@entry=0x7ffef3a31e20) at kernel/qobject.cpp:3946
#17 0x7fe28e3b76fc in KJob::result (this=this@entry=0x7fe19c46a4b0, 
_t1=, _t1@entry=0x7fe19c46a4b0, _t2=...) at 
./obj-x86_64-linux-gnu/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:636
#18 0x7fe28e3b8433 in KJob::finishJob (this=0x7fe19c46a4b0, 
emitResult=) at ./src/lib/jobs/kjob.cpp:94
#19 0x7fe28d2e0ff1 in QObject::event (this=0x7fe19c46a4b0, 
e=0x55c80c32d5d0) at kernel/qobject.cpp:1314
#20 0x7fe28dd7715f in QApplicationPrivate::notify_helper (this=, receiver=0x7fe19c46a4b0, e=0x55c80c32d5d0) at kernel/qapplication.cpp:3632
#21 0x7fe28d2b4fca in QCoreApplication::notifyInternal2 
(receiver=0x7fe19c46a4b0, event=0x55c80c32d5d0) at 
kernel/qcoreapplication.cpp:1063
#22 0x7fe28d2b7a01 in QCoreApplicationPrivate::sendPostedEvents 
(receiver=0x0, event_type=0, data=0x55c7ff9a28f0) at 
kernel/qcoreapplication.cpp:1817
#23 0x7fe28d30ce93 in postEventSourceDispatch (s=0x55c7ffadae00) at 
kernel/qeventdispatcher_glib.cpp:277
#24 0x7fe2836e1e6b in g_main_dispatch (context=0x7fe270005000) at 
../../../glib/gmain.c:3325
#25 g_main_context_dispatch (context=0x7fe270005000) at 
../../../glib/gmain.c:4043
#26 0x7fe2836e2118 in g_main_context_iterate 
(context=context@entry=0x7fe270005000, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4119
#27 0x7fe2836e21cf in g_main_context_iteration (context=0x7fe270005000, 
may_block=may_block@entry=1) at ../../../glib/gmain.c:4184
#28 0x7fe28d30c51f in QEventDispatcherGlib::processEvents 
(this=0x55c7ffadbd60, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#29 0x7fe28d2b398b in QEventLoop::exec (this=this@entry=0x7ffef3a32210, 
flags=..., flags@entry=...) at 
../../include/QtCore/../../src/corelib/global/qflags.h:69
#30 0x7fe28d2bbc00 in QCoreApplication::exec () at 
../../include/QtCore/../../src/corelib/global/qflags.h:121
#31 0x55c7fe2cb02b in main (argc=, argv=) at 
./src/main.cpp:208
[Inferior 1 (process 2390) detached]

=== end KCrash output 1 ===

Then I rebooted my machine and tried again. And it crashed again:

=== KCrash output 2 ===
Application: Kontact (kontact), signal: Aborted

[KCrash Handler]
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#5  0x7f2bfb2e2537 in __GI_abort () at abort.c:79
#6  0x7f2bfb51c7ec in __gnu_cxx::__verbose_terminate_handler () at 
../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95
#7  

Bug#971065: korganizer: org.kde.korgac.desktop executable

[Diederik de Haas]

On zondag 27 september 2020 07:39:42 CEST Helge Kreutzmann wrote:
> Package: korganizer
> Version: 4:20.04.1-2
> Severity: minor
> 
> In the logs I get the following error message:
> Aug 15 21:46:20 samd systemd[232194]: Configuration file
> /etc/xdg/autostart/org.kde.korgac.desktop is marked executable. Please
> remove executable permission bits. Proceeding anyway.
> 
> And indeed, it is the only executable desktop file in this directory.
> 
> Please consider removing the executable bit.

If I download the .deb file and look inside it, that file has 644 permissions, 
iow no executable bit set.

https://invent.kde.org/pim/korganizer/-/commit/14138650407be94cdecabecd40d1435420df8fdd
is the upstream commit from 2017-03-02 where the executable bit
was removed.
I don't know why +x is set on your system, but the package seem fine.

signature.asc
Description: This is a digitally signed message part.

Bug#986452: Updating metadata and found the cause

[Diederik de Haas]

Control: tag -1 affects kmail

The problem is caused by an incorrect modification of
https://salsa.debian.org/qt-kde-team/kde/messagelib/-/commits/master/debian/patches/series

Instead of adding (twice) a new/extra patch, it replaced the series.
Kind of like using '>' while you meant using '>>'.

signature.asc
Description: This is a digitally signed message part.

Bug#986452: libkf5messagelist5abi1: KMail fails to start because it can't load libKF5MessageList.so.5abi1

[Diederik de Haas]

Package: libkf5messagelist5abi1
Version: 4:20.08.3-3
Severity: important

Since upgrading of libkf5messagelist5abi1 KMail fails to load with the
following error message (I actually load it via Kontact):
"Cannot load part for Mail.
Cannot load library /usr/lib/x86_64-linux-gnu/qt5/plugins/kmailpart.so: 
(libKF5MessageList.so.5abi1: kan gedeeld objectbestand niet openen: 
Bestand of map bestaat niet)"

Translation of last part: 
"can't load shared object: file or folder not found"
(I want my system in English, but more and more Dutch things creep in)

The testing version (4:20.08.3-2) has this file list:
$ dpkg -L libkf5messagelist5abi1 | grep -v '/usr/share/doc'
/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libKF5MessageList.so.5.15.3.abi1
/usr/share
/usr/lib/x86_64-linux-gnu/libKF5MessageList.so.5abi1

The unstable version (4:20.08.3-3) has this file list:
$ dpkg -L libkf5messagelist5abi1 | grep -v '/usr/share/doc'
/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libKF5MessageList.so.5.15.3
/usr/share
/usr/lib/x86_64-linux-gnu/libKF5MessageList.so.5

So the [.]abi1 suffix is no longer there.
My guess is that either the [.]abi1 suffix should be added back again or
the component(s) that are linked to it, should be recompiled to link to
the new name.

Downgrading libkf5messagelist5abi1 (and it's dependencies) to the
testing version makes KMail work again.

On my system that meant these packages:
kf5-messagelib-data libkf5messagecomposer5abi1 libkf5messagecore5abi1 
libkf5messagelist5abi1 libkf5messageviewer5abi1 libkf5mimetreeparser5abi1
libkf5templateparser5 libkf5webengineviewer5abi1


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

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

Versions of packages libkf5messagelist5abi1 depends on:
ii  kf5-messagelib-data  4:20.08.3-3
ii  kio  5.78.0-4
ii  libc62.31-11
ii  libgcc-s110.2.1-6
ii  libkf5akonadicore5abi2 [libkf5akonadicore5-20.08]4:20.08.3-2
ii  libkf5akonadimime5 [libkf5akonadimime5-20.08]4:20.08.3-1
ii  libkf5akonadisearchpim5 [libkf5akonadisearchpim5-20.08]  4:20.08.3-1
ii  libkf5configcore55.78.0-4
ii  libkf5configgui5 5.78.0-4
ii  libkf5configwidgets5 5.78.0-2
ii  libkf5coreaddons55.78.0-4
ii  libkf5i18n5  5.78.0-2
ii  libkf5iconthemes55.78.0-2
ii  libkf5itemmodels55.78.0-2
ii  libkf5kiocore5   5.78.0-4
ii  libkf5messagecore5abi1 [libkf5messagecore5-20.08]4:20.08.3-3
ii  libkf5mime5abi1 [libkf5mime5-20.08]  20.08.3-1
ii  libkf5pimcommon5abi2 [libkf5pimcommon5-20.08]4:20.08.3-1
ii  libkf5pimcommonakonadi5abi1 [libkf5pimcommonakonadi5-20.08]  4:20.08.3-1
ii  libkf5textwidgets5   5.78.0-2
ii  libkf5widgetsaddons5 5.78.0-2
ii  libkf5xmlgui55.78.0-2
ii  libqt5core5a 5.15.2+dfsg-5
ii  libqt5gui5   5.15.2+dfsg-5
ii  libqt5widgets5   5.15.2+dfsg-5
ii  libstdc++6   10.2.1-6

libkf5messagelist5abi1 recommends no packages.

libkf5messagelist5abi1 suggests no packages.

-- no debconf information

Re: Bug#984468: Pre-approval for uploading KDE Apps 20.12.3

[Ivo De Decker]

Hi,

On Thu, Mar 11, 2021 at 09:37:25AM +0100, Aurélien COUDERC wrote:
> For the sake of clarity / completeness the source packages for which I’m 
> requesting an unblock are:
> 
>   elisa-player/20.12.3-1
>   gwenview/4:20.12.3-1
>   juk/4:20.12.3-1
>   kdeconnect/20.12.3-1
>   kde-spectacle/20.12.3-1
>   konsole/4:20.12.3-1
>   kpmcore/20.12.3-1
>   krdc/4:20.12.3-1
>   marble/4:20.12.3-1
>   okular/4:20.12.3-1
>   palapeli/4:20.12.3-1

All unblocked.

Thanks,

Ivo

Bug#983018: qdbus: Needs package downgrade from Buster to Bullseye (missing epoch in transitional package)

[Ivo De Decker]

clone -1 -2
reassign -2 ftp.debian.org
retitle -2 dak: version checks for binaries not enforced when binary changes 
from any to all
severity -2 normal
tags -2 - pending

Hi,

On Thu, Feb 18, 2021 at 09:08:46AM +0100, Axel Beckert wrote:
> Hi,
> 
> on one system I wondered why qdbus is still on Qt4. Then I noticed that
> the version of the Qt4 qdbus package from Buster is higher (!) than the
> version of the Qt5 qdbus package in Bullseye:
> 
> $ apt-cache policy qdbus
> qdbus:
>   Installed: 4:4.8.7+dfsg-18+deb10u1
>   Candidate: 4:4.8.7+dfsg-18+deb10u1
>   Version table:
>  *** 4:4.8.7+dfsg-20 100
> 100 /var/lib/dpkg/status
>  5.15.2-3 990
> 900 https://debian.ethz.ch/debian bullseye/main i386 Packages

The current situation:

qdbus  | 5.15.2-3 | testing  | all
qdbus  | 5.15.2-3 | unstable | all
qdbus  | 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 | oldoldstable | amd64, 
armel, armhf, i386
qdbus  | 4:4.8.7+dfsg-11  | oldstable| amd64, 
arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
qdbus  | 4:4.8.7+dfsg-18+deb10u1  | stable   | amd64, 
arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x

Normally, version checks should prevent an upload to unstable of a binary that
has a lower version than in stable or testing. However, this is checked per
architecture, and it seems the check wasn't done because the binary changed
from arch: any to arch: all at the same time. This case should probably be
checked in dak as well (obviously also for arch: all to arch: any).

Cloning the bug to track the issue in dak.

Cheers,

Ivo

Bug#980318: cantor-backend-sage: Package description inaccurate: sagemath actually is available.

[Steven De Herdt]

Package: cantor-backend-sage
Version: 4:20.12.0-1
Severity: minor

Dear Maintainer,

I don't use cantor or sagemath myself, but I noticed that the
description of this package still claims sagemath being unavailable in
Debian.  Assuming the latter gets shipped in bullseye, this text should
be updated.

Thanks for maintaining!
-Steven


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

Kernel: Linux 5.9.0-5-amd64 (SMP w/4 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 cantor-backend-sage depends on:
pn  cantor 
ii  kio5.74.1-1
ii  libc6  2.31-5
ii  libgcc-s1  10.2.0-15
ii  libkf5completion5  5.74.0-2
ii  libkf5configcore5  5.74.0-2
ii  libkf5configgui5   5.74.0-2
ii  libkf5coreaddons5  5.74.0-2
ii  libkf5i18n55.74.0-3
ii  libkf5kiowidgets5  5.74.1-1
ii  libkf5pty5 5.74.0-2
ii  libkf5syntaxhighlighting5  5.74.0-2
ii  libkf5widgetsaddons5   5.74.0-3
ii  libkf5xmlgui5  5.74.0-2+b2
ii  libqt5core5a   5.15.2+dfsg-2
ii  libqt5gui5 5.15.2+dfsg-2
ii  libqt5widgets5 5.15.2+dfsg-2
ii  libstdc++6 10.2.0-15

cantor-backend-sage recommends no packages.

Versions of packages cantor-backend-sage suggests:
pn  sagemath  

Bug#973933: turns out it was wayland that crashed

[Diederik de Haas]

It turns out that the wayland plasma session got selected and that crashed. 
This is possibly/probably fixed with the -2 upload which happened a couple of 
hours ago.
Manually selecting the 'normal' plasma session and then I could log in.

OP: Can you check whether the wayland session was (automatically) selected for 
you too? And if so, does the problem still occur when you select the 'normal' 
plasma session?

signature.asc
Description: This is a digitally signed message part.

Bug#973933: touch /etc/environment didn't help

[Diederik de Haas]

Control: tag -1 confirmed

Did a 'touch /etc/environment' and restarted sddm.service, but the problem 
remained. Output is the same as in my previous message, minus the pam_env 
error line.
Usually from within KDE, I can get a backtrace (DrKonqi?) easily, but that 
won't work in this case as I can't login to KDE.
If you can provide me with the needed steps to do it without logging in, I'd 
be happy to provide that info.

signature.asc
Description: This is a digitally signed message part.

Bug#973933: sddm: Unable to open env file: /etc/environment: No such file or directory

[Diederik de Haas]

Package: sddm
Version: 0.19.0-1
Followup-For: Bug #973933

Got a very big upgrade (hadn't started my Sid system for several days), which 
included sddm and after a reboot I got the sddm login screen.
But after giving my credentials, I got thrown back to the login screen.
'systemctl status sddm.service' told me:
Unable to open env file: /etc/environment: No such file or directory


● sddm.service - Simple Desktop Display Manager
 Loaded: loaded (/lib/systemd/system/sddm.service; enabled; vendor preset: 
enabled)
 Active: active (running) since Mon 2020-11-09 23:14:48 CET; 8min ago
   Docs: man:sddm(1)
 man:sddm.conf(5)
   Main PID: 3641 (sddm)
  Tasks: 27 (limit: 77031)
 Memory: 35.6M
 CGroup: /system.slice/sddm.service
 ├─3641 /usr/bin/sddm
 └─3854 /usr/lib/xorg/Xorg -nolisten tcp -auth 
/var/run/sddm/{a330fe19-b614-4bb4-9329-d7d6240b8ca7} -background none -noreset 
-displayfd 18 -seat seat0 vt7

nov 09 23:15:58 bagend sddm[3641]: Socket server started.
nov 09 23:15:58 bagend sddm[3641]: Loading theme configuration from 
"/usr/share/sddm/themes/debian-maui/theme.conf"
nov 09 23:15:58 bagend sddm[3641]: Greeter starting...
nov 09 23:15:58 bagend sddm-helper[3885]: [PAM] Starting...
nov 09 23:15:58 bagend sddm-helper[3885]: [PAM] Authenticating...
nov 09 23:15:58 bagend sddm-helper[3885]: [PAM] returning.
nov 09 23:15:58 bagend sddm-helper[3885]: pam_unix(sddm-greeter:session): 
session opened for user sddm by (uid=0)
nov 09 23:15:58 bagend sddm-helper[3885]: pam_env(sddm-greeter:session): Unable 
to open env file: /etc/environment: No such file or directory
nov 09 23:15:58 bagend sddm[3641]: Greeter session started successfully
nov 09 23:15:58 bagend sddm[3641]: Message received from greeter: Connect

I indeed do not have that file (I do have /etc/environment.d/90qt-a11y.conf), 
but that shouldn't make sddm crash.
Downgrading sddm and sddm-theme-debian-maui to the testing version
(0.18.1-1) made me able to login again.
After sending this bug report, I'll try to see whether a 'touch
/etc/environment' would fix the problem as well.
Anyway, it shouldn't have crashed on it imo.

Notable difference with OP is that I use KDE as my DE.

Cheers,
  Diederik

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

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

Versions of packages sddm depends on:
ii  adduser 3.118
ii  debconf [debconf-2.0]   1.5.74
ii  libc6   2.31-4
ii  libgcc-s1   10.2.0-16
ii  libpam0g1.3.1-5
ii  libqt5core5a5.15.1+dfsg-2
ii  libqt5dbus5 5.15.1+dfsg-2
ii  libqt5gui5  5.15.1+dfsg-2
ii  libqt5network5  5.15.1+dfsg-2
ii  libqt5qml5  5.15.1+dfsg-3
ii  libqt5quick55.15.1+dfsg-3
ii  libstdc++6  10.2.0-16
ii  libsystemd0 246.6-2
ii  libxcb-xkb1 1.14-2
ii  libxcb1 1.14-2
ii  qml-module-qtquick2 5.15.1+dfsg-3
ii  x11-common  1:7.7+21
ii  xauth   1:1.0.10-1
ii  xserver-xorg [xserver]  1:7.7+21

Versions of packages sddm recommends:
pn  haveged  
ii  libpam-systemd   246.6-2
ii  sddm-theme-debian-maui [sddm-theme]  0.19.0-1

Versions of packages sddm suggests:
ii  libpam-kwallet5   5.19.5-3
pn  qtvirtualkeyboard-plugin  

-- debconf information:
  sddm/daemon_name: /usr/bin/sddm
* shared/default-x-display-manager: sddm

Bug#972355: qtav: FTBFS with Qt 5.15: error: field 'clip_path' has incomplete type 'QPainterPath'

[Diederik de Haas]

Control: forwarded -1 https://github.com/wang-bin/QtAV/issues/1309
Control: tag -1 upstream fixed-upstream

Fix is not yet included in a release though. Someone has opened an issue 
requesting that: https://github.com/wang-bin/QtAV/issues/1334

signature.asc
Description: This is a digitally signed message part.

Bug#929882: khelpcenter: please add conflict with dhelp and the KDE packages on debian buster

[Ivo De Decker]

Control: severity -1 important

Hi,

On Mon, Jun 10, 2019 at 09:43:17PM +0200, Paul Gevers wrote:
> 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.

As dhelp isn't in buster, and the version in bullseye is fixed, I'm
downgrading this bug. However, adding a conflict (or breaks) against the old
(broken) version of dhelp might still be a good thing, so I'm leaving this bug
open.

Thanks,

Ivo

Bug#946522: akonadi-backend-sqlite: akonadi don't start and kmail don't work

[Diederik de Haas]

On dinsdag 10 december 2019 15:37:12 CET Martin Jean-Fabrice wrote:
> *** Reporter, please consider answering these questions, where appropriate
> ***
> 
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
>* What outcome did you expect instead?
> 
> *** End of the template - remove these template lines ***

Just "It doesn't work" is NOT a basis to fix a potential problem.

Those lines I quoted above are meant to remind a bug reporter, ie you, to 
provide some information which allows the maintainer (and others) to find the 
actual problem which in turn can lead to a solution.

It's fine to ask for help *how* to provide more detailed/technical information, 
but those questions above can be answered without any technical knowledge.
For example:
* What led up to the situation?
I upgraded from version 4:18.08.3-1 to version 4:19.08.3-1 and where it did 
work before, it no longer does.

Other pieces which may prove to be useful is share the output of running the 
following commands from a terminal:
$ kmail
and 
$ akonadictl restart

It's not a problem at all if you didn't know those commands and that they 
could prove useful. See bug reporting as starting a dialog.

HTH

signature.asc
Description: This is a digitally signed message part.

Bug#946199: akonadi-backend-postgresql: akonadictl fails to start with postgresql backend

[Diederik de Haas]

On donderdag 5 december 2019 15:34:37 CET Sandro Knauß wrote:
> do you have apparmor enabled? Maybe the Apparmor profile does not match
> anymore. Can you give it a try with aa-disable postgresql_akonadi?

I have akonadi-backend-postgresql and apparmor enabled and it is working for 
me. I only have PostgreSQL 12 though.
https://lists.debian.org/debian-kde/2019/11/msg0.html shows the way I 
upgraded to PSQL 12 (and purged PSQL 11)

If you have both, but didn't upgrade your cluster (ie transfer your akonadi 
database to PSQL 12) and rebooted, then I think PSQL 12 uses the default PSQL 
port. If you didn't change your config, then akonadi is asking PSQL 12 for its 
data, but it can't find it.
That could be an explanation why it isn't working for Vincent-Xavier.

signature.asc
Description: This is a digitally signed message part.

Bug#940872: KDE Frameworks 5.62 coming to unstable

[Diederik de Haas]

On donderdag 26 september 2019 22:56:08 CEST Bob Weber wrote:
> Another trick that worked on 2 machines here is to set the numlock on in
> /etc/sddm.conf.
> 
> My general section of sddm.conf looks like this now:
> 
> [General]
> HaltCommand=
> RebootCommand=
> Numlock=on
> 
> Hope this helps.

This fixed the issue I had which I mentioned in the CC-ed bug reports.

Thanks :-)

signature.asc
Description: This is a digitally signed message part.

Bug#931737: kdepim-runtime: Imap session login cancelled

[Diederik de Haas]

On woensdag 16 oktober 2019 03:54:45 CEST you wrote:
> you can change the config of OpenSSL to allow lower TLS versions to work.
> Better would be to urge that mail provider to upgrade their mail software as
> TLS < 1.2 really isn't secure.

>From https://lists.debian.org/debian-kde/2018/11/msg1.html :
Changing back the defaults in /etc/ssl/openssl.cnf to previous system wide 
defaults can be done using:
   MinProtocol = None
   CipherString = DEFAULT
It's recommended that you contact the remote site in case the defaults cause 
problems.

signature.asc
Description: This is a digitally signed message part.

Bug#940872: Bug#942654: kde-baseapps: Numlock state not changed per settings during startup or screenlock

[Diederik de Haas]

On zaterdag 19 oktober 2019 19:18:36 CEST Brian R. wrote:
> I've set numlock "on" at login in KDE system settings, but after recent
> updates, the numlock state is no longer applied per user settings. Numlock
> must be turned on manually.

Sounds like you have the same problem as I reported here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940872#15
It seems to be the exact opposite of what the OP filed, but I suspect it's all 
the same issue.


signature.asc
Description: This is a digitally signed message part.

Bug#940872: plasma-framework: Num lock key is always ON at startup, even if in the configuration is forced to OFF

[Diederik de Haas]

On zaterdag 21 september 2019 10:35:17 CEST Antonio wrote:
> after updating to the kde 5.62 framework the num lock key is always on
> at startup even if in the settings it was forced to stay off

I have the same problem, but reverse.
No matter what setting I have in Input Devices, it will not turn ON.
This did work before. I also tried with a new user, but that made no 
difference.

In my BIOS I have specified to turn NumLock on and when booting both Fn and 
Numlock lights are on. Same when GRUB loads. After that, both lights get 
turned off and during the boot sequence up until I see SDDM's login screen, the 
Fn light turns back on, but not the NumLock light.


signature.asc
Description: This is a digitally signed message part.

Bug#923200: libpolkit-qt5-1-1 depends on libpam-systemd

[Diederik de Haas]

On woensdag 16 oktober 2019 16:25:51 CEST Joshua Hudson wrote:
> Should I really have to provide an empty virtual package? I'm using
> pam_group so sound keeps playing in bkg while current virtual console has
> another user.

At least one DD thinks it should be a dependency. I haven't yet seen a 
response from the package maintainer.
https://bugs.debian.org/794537 seems to be the bug you want fixed.
An alternative solution would indeed be to create a package yourself (locally) 
which "Provides: logind" 

signature.asc
Description: This is a digitally signed message part.

Bug#935587: updating metadata

[Diederik de Haas]

Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=403950
Control: tag -1 upstream fixed-upstream




signature.asc
Description: This is a digitally signed message part.

Bug#931737: kdepim-runtime: Imap session login cancelled

[Diederik de Haas]

On dinsdag 9 juli 2019 21:45:13 CEST Diego Russo wrote:
> With Debian Buster akonadi does not work anymore with aruba imap server,

My guess is that it is caused by the default configuration of OpenSSL 1.1, 
which requires TLS 1.2 iirc. If that aruba imap server is using old software 
that doesn't support that version, then it won't be able to connect.

I ran into a seemingly similar situation when OpenSSL 1.1 entered Sid, but I 
can't remember if/where I wrote things down wrt this and/or reported it.
But you can change the config of OpenSSL to allow lower TLS versions to work.
Better would be to urge that mail provider to upgrade their mail software as 
TLS < 1.2 really isn't secure.

Hopefully this gives you enough hints to search for the actual solution.

signature.asc
Description: This is a digitally signed message part.

Bug#923200: libpolkit-qt5-1-1 depends on libpam-systemd

[Diederik de Haas]

On donderdag 11 juli 2019 21:53:33 CEST Demi wrote:
> I have to agree with Joshua -- programs like marble or kdenlive work
> just fine without systemd

On woensdag 20 maart 2019 15:44:30 CEST Michael Biebl wrote:
> The dependency seems correct.
> policykit without a working logind session seems pretty much useless.

Fixed in 0.112.0-7.1 (in Sid atm) ?

>From changelog:
  * Apply patch from Mark Hindley to Use new logind virtual packages
instead of libpam-systemd (Closes: #925344)

signature.asc
Description: This is a digitally signed message part.

Bug#918492: metadata

[Diederik de Haas]

Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=398324



signature.asc
Description: This is a digitally signed message part.

Bug#940565: No problem here

[Diederik de Haas]

Control: tag -1 +moreinfo +unreproducible
Control: severity -1 important

I noticed you specified the source package and not the binary package to report 
the bug against. Normally not much of an issue, but it looks like you didn't 
use or didn't share the whole output of reportbug, because it's missing the 
list of installed packages, which can be rather crucial.

Note that there are 2 groups of binary packages: python-pyside2.* and python3-
pyside2.* whereas the former is for python2 and the latter for python3.

I didn't have any pyside2 packages installed, so I tried it with a clean 
slate:
# aptitude install python3-pyside2.qtcore
$ echo "import PySide2.QtCore as core" > test.py
$ python test.py
Traceback (most recent call last):
  File "test.py", line 1, in 
import PySide2.QtCore as core
ImportError: No module named PySide2.QtCore
$ python3 test.py
$

This output is exactly as expected.
If I install python-pyside2.qtcore, then the Traceback output disappears.

As I couldn't reproduce the issue, I set the tags accordingly and as the issue 
doesn't happen for everyone, I lowered the severity.

signature.asc
Description: This is a digitally signed message part.

Bug#889919: Updating metadata

[Diederik de Haas]

Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=409375



signature.asc
Description: This is a digitally signed message part.

Bug#914743: setting metadata

[Diederik de Haas]

Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=396980
Control: tag -1 fixed-upstream

Bug#922096: Bug#921552: sddm-theme-debian-maui: Maui decorations are missing after recent upgrades

[Steven De Herdt]

Control: fixed 922096 0.18.0-1

On Tue, 23 Apr 2019 23:50:52 +0200 =?ISO-8859-1?Q?Aur=E9lien_COUDERC?=
 wrote:
> 
> Took a bit of time but you may have seen that the fix did land in buster by 
> now. :)
> 
> 
> Cheers,
> —
> Aurélien
That's better, yes.  In the SDDM configuration module, the previews
still don't work (haven't looked into that), but at least the login
screen shows normally now.

Thanks for fixing this!
-Steven

Bug#917711: Bug triaged and submitted upstream

[Ivo De Decker]

Control: tags -1 patch pending

Hi Giovanni,

On Sat, Mar 30, 2019 at 02:12:29PM +0100, Giovanni Mascellani wrote:
> I triaged and submitted upstream this bug:
> 
>   https://github.com/steveire/grantlee/issues/51
> 
> The upstream bug contains my current understanding of the bug and asks
> for help on how to proceed, because I am not really sure on what is the
> best way forward.
> 
> I hope this helps fixing the bug!

It seems upstream came to the same conclusion as you. This patch was committed
upstream:

https://github.com/steveire/grantlee/commit/3cb4bd24e127b7f55d463d934cad27f8c07c4406

I uploaded an NMU based on that patch. Debdiff attached.

Cheers,

Ivo

diff -Nru grantlee5-5.1.0/debian/changelog grantlee5-5.1.0/debian/changelog
--- grantlee5-5.1.0/debian/changelog2016-10-24 09:35:52.0 +
+++ grantlee5-5.1.0/debian/changelog2019-04-15 14:53:13.0 +
@@ -1,3 +1,10 @@
+grantlee5 (5.1.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch datatime-fractional.diff to fix FTBFS (Closes: #917711)
+
+ -- Ivo De Decker   Mon, 15 Apr 2019 14:53:13 +
+
 grantlee5 (5.1.0-2) unstable; urgency=medium
 
   [ Helmut Grohne ]
diff -Nru grantlee5-5.1.0/debian/patches/datatime-fractional.diff 
grantlee5-5.1.0/debian/patches/datatime-fractional.diff
--- grantlee5-5.1.0/debian/patches/datatime-fractional.diff 1970-01-01 
00:00:00.0 +
+++ grantlee5-5.1.0/debian/patches/datatime-fractional.diff 2019-04-15 
14:53:13.0 +
@@ -0,0 +1,15 @@
+See
+https://github.com/steveire/grantlee/commit/3cb4bd24e127b7f55d463d934cad27f8c07c4406
+https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917711
+
+--- a/templates/defaultfilters/datetime.cpp
 b/templates/defaultfilters/datetime.cpp
+@@ -97,7 +97,7 @@
+ {
+   Q_UNUSED(autoescape)
+   auto d = QDateTime::fromString(getSafeString(input),
+- QStringLiteral("-MM-ddThh:mm:ss"));
++ QStringLiteral("-MM-ddThh:mm:ss.zzz"));
+ 
+   auto argString = getSafeString(argument);
+ 
diff -Nru grantlee5-5.1.0/debian/patches/series 
grantlee5-5.1.0/debian/patches/series
--- grantlee5-5.1.0/debian/patches/series   2016-10-24 09:35:52.0 
+
+++ grantlee5-5.1.0/debian/patches/series   2019-04-15 14:53:13.0 
+
@@ -1 +1,2 @@
 variantIsTrue-float-fix.diff
+datatime-fractional.diff

Bug#915319: kde-runtime FTBFS with samba 4.9

[Ivo De Decker]

Hi Giovanni,

On Sat, Mar 30, 2019 at 07:10:40PM +0100, Giovanni Mascellani wrote:
> I did some further diagnosis on this bug: the reason why CMake fails to
> discover libsmbclient is because CMake tries to compile a little program
> including libsmbclient.h using -std=c90, which is insufficient for
> libsmbclient.h. However libsmbclient.h works with more recent C
> standards, like the GCC default -std=gnu11.
> 
> The attached patch should fix the problem. I can NMU if this is ok for
> you. Probably it is not the cleanest solution ever (if would be better
> to fix CMake files from kdelibs5-dev), but it seems to work.

I would suggest you upload this NMU. If this isn't the right fix, it can
always be reverted.

Thanks,

Ivo

Bug#899128: kdepim: Limit CVE-2017-17689 (EFAIL) even more for kmail

[Ivo De Decker]

Hi,

On 04/09/2019 09:19 PM, Moritz Muehlenhoff wrote:


The tracker for CVE-2017-17689 doesn't list anything related to kdepim or
src:meta-kde for buster. Is the issue fixed in the binary kdepim (produced
by src:meta-kde) in buster? If so, that should probably be stated explicitly
in the tracker.


For buster the affected code is in src:kf5-messagelib and fixed in 4:18.08.1-1

In stretch the affected code is in src:kdepim

In Buster the binary package kdepim is now built out of src:meta-kde, but that
was never affected. That's we don't track src:meta-kde at all in
https://security-tracker.debian.org/tracker/CVE-2017-17689

Does that clarify?


Yes. I (incorrectly) assumed that the offending code had been in 
meta-kde in buster at some point. As that's not the case, there is 
nothing left to fix for buster.


Thanks for the clarification.

Ivo

Bug#899128: kdepim: Limit CVE-2017-17689 (EFAIL) even more for kmail

[Ivo De Decker]

Hi Salvatore,

On 4/8/19 10:59 PM, Salvatore Bonaccorso wrote:

Control: reassign -1 src:kdepim
On Mon, Apr 08, 2019 at 11:36:10AM +0200, Ivo De Decker wrote:

Hi,

On Sat, May 19, 2018 at 07:18:06PM +0200, Sandro Knauß wrote:

I now created a debdiff for kdepim. The patch depdends on the new symbol that
was added in new messageviewer (see #899127).


Does this bug still affect buster/sid? From the bug log and the tracker for
CVE-2017-17689, it look like kmail in buster/sid is not affected, but it would
be good if someone could confirm that.


I think the tracking problem was hiere that #899128 is associated with
src:meta-kde, but it should be src:kdepim (#899128) and respectively
kf5-messagelib was #899127. The issue was fixed in the kf5-messagelib
in version 4:18.08.1-1. In stretch src:kdepim was a source package,
whilst in buster kdepim is a binary package produced by kde-meta, but
the issue lies there in src:kf5-messagelib.


The tracker for CVE-2017-17689 doesn't list anything related to kdepim 
or src:meta-kde for buster. Is the issue fixed in the binary kdepim 
(produced by src:meta-kde) in buster? If so, that should probably be 
stated explicitly in the tracker.


The reassign means that the BTS thinks this issue doesn't affect buster 
anymore. I'm assuming that's correct.


Thanks,

Ivo

Bug#899128: kdepim: Limit CVE-2017-17689 (EFAIL) even more for kmail

[Ivo De Decker]

Hi,

On Sat, May 19, 2018 at 07:18:06PM +0200, Sandro Knauß wrote:
> I now created a debdiff for kdepim. The patch depdends on the new symbol that 
> was added in new messageviewer (see #899127).

Does this bug still affect buster/sid? From the bug log and the tracker for
CVE-2017-17689, it look like kmail in buster/sid is not affected, but it would
be good if someone could confirm that.

Thanks,

Ivo

Bug#784479: Bug#876905: qtwebkit should not be release with buster

[Ivo De Decker]

Control: tags -1 buster-ignore

On Thu, Apr 04, 2019 at 10:39:25PM +0200, Ivo De Decker wrote:
> On Tue, Apr 02, 2019 at 11:30:44PM +0200, Moritz Muehlenhoff wrote:
> > Sure, if the release team agrees with that approach, the canonical way to do
> > that would be to tag the bug as "buster-ignore".
> 
> OK, tagging 876905 ("qtwebkit should not be released with buster") and 784477
> ("[kde-runtime] Qt4's WebKit removal").

Also tagging #784479.

Ivo

Bug#784477: Bug#876905: qtwebkit should not be release with buster

[Ivo De Decker]

Control: tags -1 buster-ignore

Hi,

On Tue, Apr 02, 2019 at 11:30:44PM +0200, Moritz Muehlenhoff wrote:
> Sure, if the release team agrees with that approach, the canonical way to do
> that would be to tag the bug as "buster-ignore".

OK, tagging 876905 ("qtwebkit should not be released with buster") and 784477
("[kde-runtime] Qt4's WebKit removal").

Thanks,

Ivo

Bug#922096: sddm-theme-debian-maui: background image doesn't load, shows white screen

[Steven De Herdt]

Control: block -1 by 921678

Hi Dan

I noticed this bug too, but the error is actually in desktop-base.  Two
other reports of this bug were already moved from sddm-theme-debian-maui
to desktop-base.  That makes it non-obvious from the side of sddm that
the bug is known, so I will not move your report to the other package.

@Aurélien: Excuse my nagging, but can this be fixed in time for the
buster release?  If I understand the freeze process correctly there's
only little time left, right?

Thank you
-Steven

Bug#921552: sddm-theme-debian-maui: Maui decorations are missing after recent upgrades

[Steven De Herdt]

Control: reassign -1 desktop-base 10.0.0
Control: severity -1 minor
Control: merge -1 921678

This is actually a bug with the new "futurePrototype" theme in
desktop-base, to be fixed in an imminent upload.

Kind regards
-Steven

Bug#900997: print-manager: probability of package in buster?

[Steven De Herdt]

Dear maintainers

If a patch providing Antonio's proposed stop-gap message is provided, is
it still possible for print-manager to get into buster?  In that case, I
may possibly try to hack something like that.

Thanks for your work and consideration!
-Steven

Bug#910873: calligra: FTBFS with poppler 0.69.0-1

[Ivo De Decker]

Control: severity -1 serious
Control: tags -1 ftbfs

Hi,

On Fri, Oct 12, 2018 at 05:51:06PM +0200, Emilio Pozuelo Monfort wrote:
> Source: calligra
> Version: 1:3.1.0+dfsg-3
> Severity: important
> 
> Hi,
> 
> Your package fails to build against poppler 0.69, currently in experimental.
> In some cases there are patches in Ubuntu, the PTS has links.

The new poppler is in unstable, so this happens on the buildds now. Raising
severity.

https://buildd.debian.org/status/package.php?p=calligra=sid

> For the memCheck errors, you can just patch out those calls, those were
> noops anyway as we didn't build with DEBUG_MEM, see
> 
> https://cgit.freedesktop.org/poppler/poppler/commit/?id=c362ab1b97f20c5b73b3bad8d52015f679178748
> 
> I intend to update our poppler soon as there are some security fixes
> in the newer versions. I'd appreciate if you can take a look at this
> and apply any necessary fixes.

Cheers,

Ivo

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

[Ivo De Decker]

Hi,

On Fri, Nov 24, 2017 at 04:59:58PM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Control: tag -1 patch
> 
> There is patch available for this at  packages.git/tree/trunk/kdelibs-no-kdewebkit.patch?h=packages/kdelibs>
> 
> We might want to wait for the last tandem of KF5 apps though.

Is there anything still blocking this?

kde-runtime (#784477) seems to have a patch and libkdegames-kde4 (#875015) is
no longer in testing.

Cheers,

Ivo

Bug#900997: Different message asking for password?

[Steven De Herdt]

Hello folks

At the moment, this bug prevents a freshly installed buster with KDE as
desktop to have its printers configured.  If the message asking for
authentication is clarified, would that be enough to at least lower the
severity of this bug below RC?

Kind regards
-Steven

Bug#901488: Please provide static archives inside libtqt4-dev !

[Diederik de Haas]

On vrijdag 15 juni 2018 02:30:46 CEST Lisandro Damián Nicanor Pérez Meyer 
wrote:
> > No, because of porting, it doesn't. But that time, that's on my side.
> > Though please note that no Bitcoin forks got ported to qt5 in general,
> > ever (not Bitcoin core itself, not Litecoin, not Peercoin. among more
> > than 5000 cryptocurrencies they all use qt4 when the gui feature is
> > available).
> 
> Well, they better do the switch, there will be no Qt4 in the near future.

FTR: bitcoin-qt and litecoin-qt (which are also packaged for Debian ) are 
using QT5 for a while now.
Monero also uses QT5 and upstream is working on Debian packages [1]. I dunno 
if the plan is to also bring it to Debian, but I think there's a reasonable 
chance as they want to make it available for Tails.

If your favorite crypto currency hasn't been updated to use QT5, there's a 
reasonable chance it's pretty much unmaintained and that should raise some red 
flags. There are a LOT of crypto currency projects which cloned bitcoin a long 
time ago, changed a few parameters and thought they were done. Several don't 
even compile. That's not a Debian problem, but an upstream problem.


[1] https://github.com/monero-project/monero/issues/2395

signature.asc
Description: This is a digitally signed message part.

Bug#900895: Bug#900957: kmail: Unable to contact

[Diederik de Haas]

On donderdag 7 juni 2018 12:15:27 CEST Griera wrote:
> virtually every time while attempting to display emails, the colour of the
> names of all email folders in the KMail section turns red, and the status
> indicator line shows:
> "Unable to fetch item from backend (collection-1): Unable to contact
> resource"

This sounds very much the same as bug #900895


signature.asc
Description: This is a digitally signed message part.

Fwd: Package info

[Diederik de Haas]

Bug 875061 is about QT4 removal and I assumed it would therefor appear on this 
ML, but apparently not, thus forwarding.

--  Forwarded Message  --

Subject: Package info
Date: zaterdag 2 juni 2018, 01:50:56 CEST
From: Diederik de Haas 
To: 875...@bugs.debian.org

Some info on this package and it's state:
- The earliest bug report in BTS is from January 2012 ... with not a single 
response. With the other bugs, there has been 1 response in March 2012 ('try 
upstream') by the maintainer, none with the others (7 total, including this 
one)
- Latest upload is version 1.1-2 in 2012, but the latest upstream (https://
github.com/flaviotordini/musique/) version is 1.5 (from December 2016), which 
appears to be a QT5 version. Upstream doesn't seem very alive/active though.

HTH
-

signature.asc
Description: This is a digitally signed message part.

Bug#899274: KMail does not always remember the desired message list columns

[Diederik de Haas]

On woensdag 30 mei 2018 01:11:50 CEST Sandro Knauß wrote:
> But I do not understand the bugtracker for Qt within which version
> what is fixed.

I don't understand it either (apparently) as to me the bug you mentioned/
linked indicated to me it should've been fixed 'long' (in Sid terms) ago ;)

> And I know from a friend that this bug is fixed within Qt
> 5.11, as it was on the reason for him to switch to Qt 5.11 very early.

Excellent. As mentioned on debian-kde it is indeed a minor annoyance.

> According to arch there are (maybe) more bugs with patches needed

Main reason for my message was to point to Arch's patches. Good that upstream 
is aware :)

Thanks

signature.asc
Description: This is a digitally signed message part.

Bug#899274: KMail does not always remember the desired message list columns

[Diederik de Haas]

On dinsdag 22 mei 2018 14:20:38 CEST Sandro Knauß wrote:
> Control: reassign -1 src:qtbase-opensource-src 5.10.1+dfsg-6
> Control: forward -1 https://bugreports.qt.io/browse/QTBUG-65478
> Control: affects -1 kmail
> ...
> I can confirm this bug. On kdepim-us...@kde.org it was mentioned that this
> issue is a Qt one. Here the the mail:
> > 
> > Its a QT bug apparently, related to this:
> > https://bugreports.qt.io/browse/QTBUG-65478
> > Fixed in Fedora which probably doesn't help you. But FYI from the
> > Changelog:
> > - omit 0068-QHeaderView.patch, reports of regression'y behavior

Are you sure? Because the qt bug is marked as fixed, but I still have this 
issue as well (fully updated Sid system).
I reported it here: https://lists.debian.org/debian-kde/2018/04/msg00039.html 
and Lisandro mentioned that Arch had several patches related to it, here: 
https://lists.debian.org/debian-kde/2018/04/msg00047.html



signature.asc
Description: This is a digitally signed message part.

Fwd: Re: Bug#897667: qt4-x11: Please add support for new architecture "riscv64"

[Diederik de Haas]

Removing the bug also makes it not show up on debian-qt-kde ML, which is an 
unintended consequences, thus forwarding it there.

--  Forwarded Message  --

Subject: Re: Bug#897667: qt4-x11: Please add support for new architecture 
"riscv64"
Date: zaterdag 5 mei 2018, 00:18:10 CEST
From: Diederik de Haas <didi.deb...@cknow.org>
To: Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>, Lisandro 
Damián Nicanor Pérez Meyer <perezme...@gmail.com>
CC: Manuel A. Fernandez Montecelo <m...@debian.org>

[I removed the bug from the To/CC list as I think it isn't relevant for that 
bug, but more general for qt4 removal]

On vrijdag 4 mei 2018 18:45:08 CEST Manuel A. Fernandez Montecelo wrote:
> - phonon direclty depends on libqt4-dev too, so it needs to go.

I recently went on a trip to remove all qt4 dependencies of phonon from my Sid 
system and I succeeded in doing so ... but it wasn't exactly straight forward.
If you don't take special actions, it'll default to installing the qt4 version 
of phonon (at least partially).

This seems to be the main culprit:
$ aptitude why phonon-backend
i   desktop-base Suggests gnome | kde-standard | xfce4 | wmaker
p   kde-standard Depends  kopete (>= 4:17.08.3)
p   kopete   Depends  phonon   
p   phonon   Depends  phonon-backend-gstreamer | phonon-backend

So I was able to succeed because I don't use kde-standard, but kde-plasma-
desktop.
Also, the most logically/naturally named phonon packages (phonon-backend-X) 
install the qt4 version of it. If you know what you're doing and know you 
don't want qt4, then you'll install phonon4qt5-backend-X package(s), but my 
guess is that it requires specific action to do the 'right' thing.

There is now in experimental a version of kopete which no longer depends on 
kde4/qt4 stuff.  If it's ready to be uploaded to sid, I'd suggest to then 
update kde-standard to depend on that version asap.

(My uninformed and unqualified opinion is that you should start removing qt4 
*really* soon from the archives or it'll end up again in Buster)

My 0.02
-

signature.asc
Description: This is a digitally signed message part.

Bug#895386: qt3d5-dev: Package doesn't include dir /usr/include/x86_64-linux-gnu/qt5/Qt3DExtras

[José de Paula Rodrigues]

Package: qt3d5-dev
Version: 5.10.1+dfsg-3
Severity: important

Dear Maintainer,

When trying to build QGis 3.0 from source, at some point CMake reports
the following error:

CMake Error at 
/usr/lib/x86_64-linux-gnu/cmake/Qt53DExtras/Qt53DExtrasConfig.cmake:27 
(message):
  The imported target "Qt5::3DExtras" references the file

 "/usr/include/x86_64-linux-gnu/qt5/Qt3DExtras"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

 
"/usr/lib/x86_64-linux-gnu/cmake/Qt53DExtras/Qt53DExtrasConfig.cmake"

  but not all the files it references.

The directory and its contents is included in the upstream source tarball, but 
for some reason didn't make to the Debian package.

In fact, the source tarball has 13 directories under include:

~/software/qt3d-everywhere-src-5.10.1/include]$ ls -ld
Qt3DAnimation
Qt3DCore
Qt3DCoreTest
Qt3DExtras
Qt3DInput
Qt3DLogic
Qt3DQuick
Qt3DQuickAnimation
Qt3DQuickExtras
Qt3DQuickInput
Qt3DQuickRender
Qt3DQuickScene2D
Qt3DRender

whereas qt3d5-dev only has the following 8:

$ ls -d /usr/include/x86_64-linux-gnu/qt5/Qt3D*
/usr/include/x86_64-linux-gnu/qt5/Qt3DCore
/usr/include/x86_64-linux-gnu/qt5/Qt3DExtras
/usr/include/x86_64-linux-gnu/qt5/Qt3DInput
/usr/include/x86_64-linux-gnu/qt5/Qt3DLogic
/usr/include/x86_64-linux-gnu/qt5/Qt3DQuick
/usr/include/x86_64-linux-gnu/qt5/Qt3DQuickInput
/usr/include/x86_64-linux-gnu/qt5/Qt3DQuickRender
/usr/include/x86_64-linux-gnu/qt5/Qt3DQuickScene2D
/usr/include/x86_64-linux-gnu/qt5/Qt3DRender

Manually copying Qt3DExtras from the source tarball to the system include dir 
solves the problem for me; I believe the package should include all those files 
from the source tarball. Thanks.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.16.0minerva (SMP w/8 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)

Versions of packages qt3d5-dev depends on:
ii  libqt53danimation5   5.10.1+dfsg-3
ii  libqt53dcore55.10.1+dfsg-3
ii  libqt53dextras5  5.10.1+dfsg-3
ii  libqt53dinput5   5.10.1+dfsg-3
ii  libqt53dlogic5   5.10.1+dfsg-3
ii  libqt53dquick5   5.10.1+dfsg-3
ii  libqt53dquickanimation5  5.10.1+dfsg-3
ii  libqt53dquickextras5 5.10.1+dfsg-3
ii  libqt53dquickinput5  5.10.1+dfsg-3
ii  libqt53dquickrender5 5.10.1+dfsg-3
ii  libqt53dquickscene2d55.10.1+dfsg-3
ii  libqt53drender5  5.10.1+dfsg-3
ii  qtbase5-dev  5.10.1+dfsg-5

qt3d5-dev recommends no packages.

Versions of packages qt3d5-dev suggests:
ii  qt3d5-doc   5.10.1+dfsg-3
pn  qt3d5-doc-html  

-- no debconf information

Re: New QT Version - so again KDE problems

[Diederik de Haas]

On maandag 9 april 2018 12:59:27 CEST Wolfgang Schindler wrote:
> So if you now use discover or an 'apt full-upgrade'

I will give you one thing: discover is a dangerous package in Sid as it seems 
to miss the sanity logic that are available in apt or aptitude.
I *really* wish plasma-discover was at most a Suggest to plasma-desktop. It's 
annoying that I have to explicitly remove it after installing KDE.
I've brought this up before and got the response that discover is meant for 
stable (*). Sorry, but (imo) if your package is unfit for Sid, then it's unfit 
for Testing and thus should be unfit for Stable.

For the rest, I completely agree with what Stuart wrote.
I've written multiple times on the debian-kde ML that people should stop using 
full or dist-upgrade as you don't need in 99% of cases. The normal 
(safe-)upgrade is really all you need. I consider(ed) it condescending to post 
that to this ML.
If you'd done 'aptitude full-upgrade' it would've explicitly told you each and 
every package that would break and why. It then essentially asks "Do you want 
to break your system?" to which you can respond 'Y', but don't be surprised if 
it does exactly what you asked it to do ...

/me goes to write to write to debian-kde to say that again

(*) Since that response I uninstalled discover immediately and remove it 
immediately after installing KDE. It may have actually improved since, but 
I'll never know as I found that response unacceptable and 1000x more so as it 
is a package manager, potentially ruining your system. Which was exactly what 
it had done.

signature.asc
Description: This is a digitally signed message part.

Bug#894489: pulseaudio-equalizer: Please upgrade to Qt5 instead of Qt4

[Diederik de Haas]

Package: pulseaudio-equalizer
Version: 11.1-4
Severity: normal

I wanted to install pulseaudio-equalizer but bailed out when I saw this:
# aptitude install pulseaudio-equalizer
The following NEW packages will be installed:
  libqt4-designer{a} libqt4-help{a} libqt4-scripttools{a} libqt4-test{a}
  libqtassistantclient4{a} pulseaudio-equalizer python-qt4{a} python-qt4-dbus{a}

Afaik the plan is to remove qt4 from the archives before the Buster
release, so that means that this program/module should be upgraded to
Qt5. 
That's also the reason I choose severity normal instead of wishlist.
(It would also be great if the depends is more restrictive as I see no
reason to install qt(4) designer/help/test packages while only runtime things
should be needed)

Luckily I found a commit on the GitHub mirror of the PulseAudio repo:
https://github.com/pulseaudio/pulseaudio/commit/480e0e74f43565d7ece72141666961ae8cc2ed75

titled: qpaeq: port to PyQt5

Added debian-qt-kde@lists.debian.org as they track/manage the removal of
qt4 and it looks like this one was missed.

Cheers,
  Diederik

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

Kernel: Linux 4.15.0-2-amd64 (SMP w/16 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 pulseaudio-equalizer depends on:
ii  libc6 2.27-3
ii  libcap2   1:2.25-1.2
ii  libdbus-1-3   1.12.6-2
ii  libfftw3-single3  3.3.7-1
ii  libpulse0 11.1-4
ii  pulseaudio11.1-4
ii  python2.7.14-4
ii  python-dbus   1.2.6-1
pn  python-qt4
pn  python-qt4-dbus   
ii  python-sip4.19.8+dfsg-1

pulseaudio-equalizer recommends no packages.

pulseaudio-equalizer suggests no packages.

Re: Accepted akonadi 4:17.12.2-1 (source all amd64) into experimental, experimental

[Diederik de Haas]

On maandag 12 maart 2018 12:53:06 CET Sandro Knauß wrote:
> > Does that mean that postgresql is no longer supported?
> No - postgresql is still supported.

Phew. Thanks :)

signature.asc
Description: This is a digitally signed message part.

Re: Accepted akonadi 4:17.12.2-1 (source all amd64) into experimental, experimental

[Diederik de Haas]

On zondag 11 maart 2018 18:00:13 CET Sandro Knauß wrote:
> add akonadi-backend-postgresql.lintian-overrides to ignore empty
>  package.

Does that mean that postgresql is no longer supported?

signature.asc
Description: This is a digitally signed message part.

Bug#892130: qtchooser: qtconfig doesn't find qt5 version

[Erik de Castro Lopo]

Package: qtchooser
Version: 64-ga1b6736-5
Severity: normal

Dear Maintainer,

I run a few Qt apps in the Mate desktop environment. When I run `qtconfig` on 
the
commandline I get:

> qtconfig
qtconfig: could not exec '/usr/lib/qt5/bin/qtconfig': No such file or 
directory

When I use apt-file to search for "bin/qtconfig" I get:

> apt-file search bin/qtconfig
qt4-qtconfig: /usr/bin/qtconfig-qt4
qt4-qtconfig: /usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig
qtchooser: /usr/bin/qtconfig

so the error message above from "qtchooser" is pointing to an executable that 
does
not exist in Debain.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages qtchooser depends on:
ii  libc6   2.26-6
ii  libgcc1 1:8-20180218-1
ii  libstdc++6  8-20180218-1

qtchooser recommends no packages.

qtchooser suggests no packages.

-- no debconf information

Bug#884956: Debian testing

[Diederik de Haas]

On donderdag 22 februari 2018 09:44:21 CET wm4 wrote:
> So much for testing being better for stability.

If you want stability you should use Debian Stable.

If you want to use Testing or Sid, you should expect that things can break 
*and* be able to cope with that. If you're not yet there, but willing to 
learn, there are resources for that (#debian-next f.e.) and you should learn 
your way around your package manager. If you don't want to upgrade to -12, you 
hold your packages at -10, it really isn't that hard.

Whining surely isn't helping anyone.

signature.asc
Description: This is a digitally signed message part.

Bug#884956: Now hidpi scaling is even more broken

[Diederik de Haas]

On zondag 18 februari 2018 17:06:36 CET wm4 wrote:
> Debian doesn't provide an easy way to rollback

Like Lisandro already pointed out, there's testing if you use sid.
But there is always http://snapshot.debian.org which allows you to go back to 
any version ever uploaded to Debian (at least since a couple of years).

signature.asc
Description: This is a digitally signed message part.

Bug#883997: libkscreenlocker5: screen lock with photo slideshow eats up all memory and triggers oom killer

[Diederik de Haas]

On zondag 10 december 2017 10:19:24 CET Philipp Huebner wrote:
> Looking at syslog after the reboot, I see that oom killer was triggered
> several times, as there was no free RAM and no free SWAP left any more.
> It also shows that libkscreenlocker5 is using by far the most memory,
> and every time oom killer is invoked, libkscreenlocker5 is using even
> more memory than before, e.g. total_vm 7549136 -> 7589587.
> 
> For reference: this box has 16 GB of memory + 16 GB of swap and only
> runs standard office applications.

Sounds like Bug #874581


signature.asc
Description: This is a digitally signed message part.

Bug#837513: obsolete

[Diederik de Haas]

On woensdag 6 december 2017 22:47:19 CET Wolfgang Rohdewald wrote:
> Why do I actively have to search for kajongg bug reports?
> 
> Is there some way you can setup automatic notification for kajongg bugs?

Hit the 'Subscribe' button on https://tracker.debian.org/pkg/kajongg

signature.asc
Description: This is a digitally signed message part.

Bug#883435: akonadi-backend-postgresql: akonadictl start fails with Postgresql 10 installed, likely needs a rebuild

[Diederik de Haas]

Package: akonadi-backend-postgresql
Version: 4:17.08.0-1
Severity: important

Now that qt does support Postgresql 10 (#876421) I upgraded my
Postgresql packages to 10 and migrated the cluster (from 9.6).
After that I did 'akonadictl start' and noticed it was still using
Postgresql 9.6. So I purged that (and rebooted) and after that, akonadi
didn't want to start anymore. For some reason it's explicitly trying to
use pg_ctl from 9.6, but it should use the 10 version.

Konsole output:

$ akonadictl start
Connecting to deprecated signal 
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Could not start database server!
org.kde.pim.akonadiserver: executable: "/usr/lib/postgresql/9.6/bin/pg_ctl"
org.kde.pim.akonadiserver: arguments: ("start", "-w", "--timeout=10", 
"--pgdata=/home/diederik/.local/share/akonadi/db_data", "-o 
\"-k/tmp/akonadi-diederik.IOXa0T\" -h ''")
org.kde.pim.akonadiserver: process error: "execvp: No such file or directory"
org.kde.pim.akonadiserver: Failed to remove runtime connection config file
org.kde.pim.akonadicontrol: Application 'akonadiserver' exited normally...

So my guess is that akonadi-backend-postgresql needs to be rebuild so
that it gets linked to the current Postgresql version, which is 10 (in
both testing and sid).

(Even better would be if it would use the most recent version, but that
may be stretching it)

Cheers,
  Diederik

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

Kernel: Linux 4.14.0-1-amd64 (SMP w/4 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)

Versions of packages akonadi-backend-postgresql depends on:
ii  libqt5sql5-psql  5.9.2+dfsg-5

Versions of packages akonadi-backend-postgresql recommends:
ii  akonadi-server  4:17.08.0-1+b1
ii  postgresql  10+188

akonadi-backend-postgresql suggests no packages.

-- no debconf information

Bug#879960: libqt5sql5-psql: [libqt5sql5-psql] basic support postgresql-10

[Diederik de Haas]

On donderdag 23 november 2017 09:34:40 CET Dmitry Shachnev wrote:
> Thank you. The fix is applied in Git now, will be in the next upload.

\o/


signature.asc
Description: This is a digitally signed message part.

Bug#881973: kde-spectacle: Please build against libkf5kipi32.0.0 in experimental

[Diederik de Haas]

Package: kde-spectacle
Version: 16.08.3-2
Severity: wishlist

Currently you can't install gwenview from experimental together with
kde-spectacle as both kde-spectacle versions (sid+experimental) are
build against libkf5kipi31.0.0.
Therefor hereby the request for a rebuild of kde-spectacle in
experimental build against libkf5kipi32.0.0.

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/16 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)

Versions of packages kde-spectacle depends on:
ii  kio   5.37.0-2
ii  libc6 2.24-17
ii  libkf5configcore5 5.37.0-2
ii  libkf5configgui5  5.37.0-2
ii  libkf5configwidgets5  5.37.0-2
ii  libkf5coreaddons5 5.37.0-2
ii  libkf5dbusaddons5 5.37.0-2
ii  libkf5declarative55.37.0-2+b1
ii  libkf5i18n5   5.37.0-2
ii  libkf5kiocore55.37.0-2
ii  libkf5kiowidgets5 5.37.0-2
ii  libkf5kipi31.0.0  4:16.08.2-1
ii  libkf5notifications5  5.37.0-2
ii  libkf5screen-bin  4:5.10.5-2
ii  libkf5screen7 4:5.10.5-2
ii  libkf5service-bin 5.37.0-2
ii  libkf5service55.37.0-2
ii  libkf5widgetsaddons5  5.37.0-2
ii  libkf5windowsystem5   5.37.0-2
ii  libkf5xmlgui5 5.37.0-2
ii  libqt5core5a  5.9.2+dfsg-4
ii  libqt5dbus5   5.9.2+dfsg-4
ii  libqt5gui55.9.2+dfsg-4
ii  libqt5printsupport5   5.9.2+dfsg-4
ii  libqt5qml55.9.2-3
ii  libqt5quick5  5.9.2-3
ii  libqt5widgets55.9.2+dfsg-4
ii  libqt5x11extras5  5.9.2-1
ii  libstdc++67.2.0-16
ii  libxcb-cursor00.1.1-4
ii  libxcb-image0 0.4.0-1+b2
ii  libxcb-util0  0.3.8-3+b2
ii  libxcb-xfixes01.12-1
ii  libxcb1   1.12-1

kde-spectacle recommends no packages.

kde-spectacle suggests no packages.

-- no debconf information

Bug#879960: libqt5sql5-psql: [libqt5sql5-psql] basic support postgresql-10

[Diederik de Haas]

On Friday, October 27, 2017 11:34:08 PM CEST Damir R. Islamov wrote:
> Tags: patch
> 
>* QT-5.9.[1,2] (and future QT-5.10?) in the upstram do not support
> PostgreSQL 10.

Thanks for this patch! 
I ran into this problem with https://bugs.debian.org/cgi-bin/bugreport.cgi?
bug=876421 and thus far hadn't received a reply to it.
As PostgreSQL 10 is now the version in both Sid and Testing/Buster, this means 
PostgreSQL can't be used with qt, which is a shame.

Bug#869151: Confirmed

[Innocent De Marchi]

Hi,

It seems to me that there is a problem of incongruous dependencies.
Kolourpaint depends on libkf5kdelibs4support5, this kio but kio no
It depends on kinit. But kinit depends on kio. This way, when
installing kolourpaint, kinit is not installed.
I think it will be necessary to communicate this to those responsible
for the Qt/KDE packages

Regards!

I. De Marchi


> Hi, 
> 
> I had the same problem (in xfce). These are the messages in shell:
> 
> Icon theme "crystalsvg" not found.
> Can not find 'kdeinit5' executable at
> "/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
> "/usr/bin, /usr/lib/x86_64-linux-gnu/qt5/bin" Can not find 'kdeinit5'
> executable at
> "/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
> "/usr/bin, /usr/lib/x86_64-linux-gnu/qt5/bin" Can not find 'kdeinit5'
> executable at
> "/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
> "/usr/bin, /usr/lib/x86_64-linux-gnu/qt5/bin" kf5.kio.core: couldn't
> create slave: "No s'ha pogut comunicar amb el klauncher: The name
> org.kde.klauncher5 was not provided by any .service files"
> KServiceTypeTrader: serviceType "ThumbCreator" not found
> KServiceTypeTrader: serviceType "ThumbCreator" not found No file found
> for ".xml" , even though update-mime-info said it would exist. Either
> it was just removed, or the directory doesn't have executable
> permission... ("/usr/share/mime") KServiceTypeTrader: serviceType
> "ThumbCreator" not found KServiceTypeTrader: serviceType
> "ThumbCreator" not found Can not find 'kdeinit5' executable at
> "/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
> "/usr/bin, /usr/lib/x86_64-linux-gnu/qt5/bin" Can not find 'kdeinit5'
> executable at
> "/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
> "/usr/bin, /usr/lib/x86_64-linux-gnu/qt5/bin" kf5.kio.core: couldn't
> create slave: "No s'ha pogut comunicar amb el klauncher: The name
> org.kde.klauncher5 was not provided by any .service files"
> 
> The problem is solved by installing the kinit package. 
> Dear Maintainer, consider add kinit dependency on the package.
> 
> Regards!
> 
> I. De Marchi

Bug#869151: Confirmed

[Innocent De Marchi]

Hi, 

I had the same problem (in xfce). These are the messages in shell:

Icon theme "crystalsvg" not found.
Can not find 'kdeinit5' executable at
"/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
"/usr/bin, /usr/lib/x86_64-linux-gnu/qt5/bin" Can not find 'kdeinit5'
executable at
"/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
"/usr/bin, /usr/lib/x86_64-linux-gnu/qt5/bin" Can not find 'kdeinit5'
executable at
"/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
"/usr/bin, /usr/lib/x86_64-linux-gnu/qt5/bin" kf5.kio.core: couldn't
create slave: "No s'ha pogut comunicar amb el klauncher: The name
org.kde.klauncher5 was not provided by any .service files"
KServiceTypeTrader: serviceType "ThumbCreator" not found
KServiceTypeTrader: serviceType "ThumbCreator" not found No file found
for ".xml" , even though update-mime-info said it would exist. Either
it was just removed, or the directory doesn't have executable
permission... ("/usr/share/mime") KServiceTypeTrader: serviceType
"ThumbCreator" not found KServiceTypeTrader: serviceType "ThumbCreator"
not found Can not find 'kdeinit5' executable at
"/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
"/usr/bin, /usr/lib/x86_64-linux-gnu/qt5/bin" Can not find 'kdeinit5'
executable at
"/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
"/usr/bin, /usr/lib/x86_64-linux-gnu/qt5/bin" kf5.kio.core: couldn't
create slave: "No s'ha pogut comunicar amb el klauncher: The name
org.kde.klauncher5 was not provided by any .service files"

The problem is solved by installing the kinit package. 
Dear Maintainer, consider add kinit dependency on the package.

Regards!

I. De Marchi

Bug#877922: kwin-x11 carsh with qt-5.9.2

[Diederik de Haas]

On zaterdag 7 oktober 2017 12:15:18 CEST Eric Valette wrote:
> ii  libqt5x11extras5   5.9.1-2+b1

That package is still at the 'old' version. Wouldn't be surprised if that has 
something to do with it.


signature.asc
Description: This is a digitally signed message part.

Bug#876421: akonadi-backend-postgresql does not support PostgreSql 10

[Diederik de Haas]

Package: akonadi-backend-postgresql
Version: 4:16.04.3-6
Severity: important

Just got an upgrade of my postgres packages from 9.6 to 10 and upgraded
my (main) cluster containing my akonadi database.
While kmail does seem to work*, it looks like all my mails are now marked
as unread :-/
So did the 'standard' thing of 'akonadictl restart', 'akonadictl fsck', 
'akonadictl vacuum' and another 'akonadictl restart'.
I then noticed in my Konsole the following message:
"This version of PostgreSQL is not supported and may not work."

So, it looks like the current Qt version doesn't support PostgreSql
10. 

* It looks like it actually doesn't work.
First the sending from bugreport itself failed with the following message:
SMTP send failure: [SSL: VERSION_TOO_LOW] version too low (_ssl.c:719). Do you 
want to retry (or else save the report and exit)? [Y|n|q|?]? n

Although this seems like a reportbug problem and/or Qt issue.
So I then copied the message (text) reportbug saved to file into a new email, 
composed with KMail, but when I tried to send it, I got the following error 
message:
"Sending Message Failed - Kontact
There were problems trying to queue the message for sending: Unable to append 
item flags."

So now I'm sending this bug report from another machine where PostgreSql isn't 
updated yet.
I haven't tried the packages from experimental yet, but may just do so as 
KMail seems to be useless on the machine that has PostgreSql 10 ...

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

Kernel: Linux 4.12.0-2-amd64 (SMP w/4 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)

Versions of packages akonadi-backend-postgresql depends on:
ii  libqt5sql5-psql  5.9.1+dfsg-9

Versions of packages akonadi-backend-postgresql recommends:
ii  akonadi-server  4:16.04.3-6
ii  postgresql  10+185

akonadi-backend-postgresql suggests no packages.

-- no debconf information

Re: Qt4 in the context of OpenSSL 1.0 removal

[Diederik de Haas]

On zaterdag 26 augustus 2017 16:44:34 CEST Lisandro Damián Nicanor Pérez Meyer 
wrote:
> a) We remove SSL support letting lots of apps fail or silently use
> unencrypted  connections.

silently use unencrypted connections sound REALLY bad.
Either do it very *loudly* or let apps fail.

My 0.02


signature.asc
Description: This is a digitally signed message part.

Bug#872913: libkf5declarative5: KDE refuses to be installed (libkf5declarative5 and python-pyqt5 have dependencies not satisfied)

[Diederik de Haas]

> Last week, after an upgrade, KDE packages was automatically removed and
> since, I can't reinstall it (via kde-standard)
> 
> When I try, I have this error: libkf5declarative5 (and also python-pyqt5)
> depend qtbase-abi-5-7-1 which is a virtual package and is not provided by
> any available packages
> 
> qtbase-abi-x-x-x corresponds to the package libqt5core5a and it upgraded
> last week to version 5.9.1 (I think it's since this upgrade that I have
> this problem)

Various qt 5.9 packages are being uploaded to the unstable archives now, but 
as there are quite a few of them, they not all land in unstable at the same 
time. That's a consequence of running *unstable*, these things happen.

Your best course of action (imo) is adding testing to your sources and 
downgrade the 5.9 packages to the 5.7 ones ... and probably prefer testing 
(over unstable) and maybe also stick with testing instead of unstable.

My €0.02

signature.asc
Description: This is a digitally signed message part.

Bug#841951: [PATCH]: bitcoin-qt segfaults on startup

[Erik de Castro Lopo]

Lisandro Damián Nicanor Pérez Meyer wrote:

> As you can see in
> 
>   <https://codereview.qt-project.org/#/c/186122/1//ALL,unified>
> 
> the patch is not exactly right.

I've have be running with that patch in its current form since the start
of the year. Afaiac its works as intended.

> That needs to be fixed before we add that patch, be it locally or in upstream 
> (although upstream is much better).

So who is it that does that? 

Erik
-- 
------
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#841951: [PATCH]: bitcoin-qt segfaults on startup

[Erik de Castro Lopo]

Lisandro Damián Nicanor Pérez Meyer wrote:

> forwarded 841951 https://bugreports.qt.io/browse/QTBUG-58910
> thanks
> 
> Erik: if possible please subscribe to the upstream bug, maybe we can
> iron out another bug in the process.

To fix this issue locally, I have force (ie, quick and dirty) installed a
patched version of libqxcb-glx-integration.so, but every time I update that
package it breaks bitcoin-qt.

Since upstream seem to be in no hurry to fix this, can debian not ship 
a patched version, at least until upstream fixes it?

Erik
-- 
------
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#865389: plasma-desktop: incorrect German translation of icon sizes

[Diederik de Haas]

Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=381467



signature.asc
Description: This is a digitally signed message part.

Bug#861495: plasma-discover: recommend apt-config-auto-update instead of software-properties-kde

[Francesco De Vita]

On 30/04/17 00:41:17 CEST, Matthias Klumpp wrote:
> PackageKit aleady updates the cache periodically

By default? I have different machines with Stretch and the default kde 
installation, there was no evidence ever that that happened automatically. I 
always had to to check for updates manually in plasma-discover. Of course, I 
was able to set the automatic update via s-p-kde but it wasn't set by default.

> there is no point in having another tool trying to do the same in the
> background. The only thing that this might end in is two things fighting over
> the APT database lock in the background, which is undesired.

My suggestion was in fact to recommend apt-config-auto-update *instead of*
s-p-kde. About this point, what should be the default mechanism in Debian to 
update the cache and/or enable automatic updates? Something related to APT or 
PackageKit only? The manuals still suggest to use and configure apt to do that 
(mentioning apticron,  apt-config-auto-update and unattend-upgrades for the 
convenience of the users). And by the way, s-p-kde does exactly that by 
(also?) writing the file /etc/apt/apt.conf.d/10periodic. This is why I don't 
understand why the two packages cannot be interchangeable.

> > What benefits if I may ask? The sources.list can be edited already in
> > plasma-discover without s-p-kde,
> 
> You can only remove sources, you can't add or edit them

You're right. But I just tried to edit my sources with s-p-kde. It crashes 
when adding new sources and it automatically enables them and adds a commented 
deb-src line. I had to manually check for errors my sources.list anyway.  
Also, the interface is misleading due to bug 443643 [1] (a bug of 10 years 
ago).  In this way it is still better to edit the sources.list with a text 
editor.

> or look at which GPG keys ou have installed for them on your system

I don't know if you're talking about the same functionality provided by 
apt-key, but s-p-kde simply displays nothing under "Trusted software 
providers", while apt-key shows correctly all the keys.

> You can also not enable/disable backports or updates via a simple click.

Maybe yes but still the interface is misleading due to bug 721662 [2].

> > and what remains is the possibility to choose if
> > automatically install security updates (but I suppose unattended-upgrades
> > does exactly that) or download all the updates in background or just
> > notify about it.
> 
> These are exactly the features that might be broken, as they rely on
> other tools and s-p-kde doesn't interface well with PackageKit.
> Everything else works.

Well, because of the issues above, I'm not convinced of the benefits of this 
package. Right now I still think that the updates can be managed better by 
editing the proper files in /etc/apt/ and that the usage of apt-config-auto-
update and unattended-upgrades provides a better setting for the average user.

Thank you for the useful clarifications and for your time.

Regards
Francesco

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443643
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721662

Bug#861495: plasma-discover: recommend apt-config-auto-update instead of software-properties-kde

[Francesco De Vita]

On 29/04/17 20:23:58 CEST, Matthias Klumpp wrote:
> The apt-config-auto-update package enables automatic periodic cache
> updates on systems that *do not* use PackageKit. For systems where
> PackageKit is installed, the PK frontend uses PackageKit to request
> update information.

About the package cache, isn't it in common between apt and PackageKit based 
tools? If I issue an "apt update" I see that discover sees the updated cache. 
If so, I don't see why not use apt-config-auto-update, it provides a useful 
feature that I think many users expect by default.

> The software-properties-kde application allows configuring the update
> interval (does nothing here...) but also allows people to edit the
> software sources installed on the system. It's basically a GUI editor
> for /etc/apt/sources.list. And that is the reason why Discover depends
> on it.

But plasma-discover already has this feature, I can edit my sources.list with 
it and without software-properties-kde being installed.

> Granted, software-properties-kde has quite some flaws [...]
> Regardless of that, having it brings enough benefit to the users that
> it is included here. [...]
> The periodic updates / automatic updates function in software-properties-kde
> is broken if you use Discover, but its other functions warrant its inclusion
> still.

What benefits if I may ask? The sources.list can be edited already in
plasma-discover without s-p-kde, the periodic updates are broken if I use 
discover as you say, and what remains is the possibility to choose if 
automatically install security updates (but I suppose unattended-upgrades does 
exactly that) or download all the updates in background or just notify about 
it.

Thank you.

Regards
Francesco

Bug#861495: plasma-discover: recommend apt-config-auto-update instead of software-properties-kde

[Francesco De Vita]

Package: plasma-discover
Version: 5.8.5-3
Severity: wishlist

Dear Maintainer,

plasma-discover recommends software-properties-kde, a package that allows via 
GUI to:
- manage the entries in the sources.list
- set periodic update and automatic upgrades
- opt in/out from the popularity contest

However the software-properties-* packages still have important and old bugs 
unresolved that undermine the user experience and, by default, do not enable 
automatic updates when installed.

A better alternative could be the installation of plasma-discover with
apt-config-auto-update instead, which provides "configuration snippets for the 
Apt package manager to have it automatically update its package cache".

In this way:
- the sources.list can still be managed using plasma-discover directly
- automatic updates are enabled by default

Despite the lack of a couple of features provided by software-properties-kde, 
this configuration could be better for a basic installation.

Regards


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

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

Versions of packages plasma-discover depends on:
ii  appstream0.10.6-2
ii  kio  5.28.0-2
ii  libappstreamqt2  0.10.6-2
ii  libc62.24-10
ii  libkf5archive5   5.28.0-2
ii  libkf5attica55.28.0-1
ii  libkf5configcore55.28.0-2
ii  libkf5configgui5 5.28.0-2
ii  libkf5configwidgets5 5.28.0-2
ii  libkf5coreaddons55.28.0-2
ii  libkf5crash5 5.28.0-1
ii  libkf5dbusaddons55.28.0-1
ii  libkf5declarative5   5.28.0-1
ii  libkf5i18n5  5.28.0-2
ii  libkf5kiocore5   5.28.0-2
ii  libkf5kiowidgets55.28.0-2
ii  libkf5newstuff5  5.28.0-1
ii  libkf5notifications5 5.28.0-1
ii  libkf5service-bin5.28.0-1
ii  libkf5service5   5.28.0-1
ii  libkf5widgetsaddons5 5.28.0-2
ii  libkf5xmlgui55.28.0-1
ii  libpackagekitqt5-0   0.9.6-1
ii  libqt5core5a 5.7.1+dfsg-3+b1
ii  libqt5dbus5  5.7.1+dfsg-3+b1
ii  libqt5gui5   5.7.1+dfsg-3+b1
ii  libqt5qml5   5.7.1-2+b2
ii  libqt5quick5 5.7.1-2+b2
ii  libqt5widgets5   5.7.1+dfsg-3+b1
ii  libqt5xml5   5.7.1+dfsg-3+b1
ii  libstdc++6   6.3.0-14
ii  packagekit   1.1.5-2
ii  plasma-discover-common   5.8.5-3
ii  qml-module-org-kde-kirigami  1.1.0-1

Versions of packages plasma-discover recommends:
pn  software-properties-kde  

plasma-discover suggests no packages.

-- no debconf information

Bug#840844: improving the UX with the default KDE installation

[Diederik de Haas]

Hi Maxy!

On vrijdag 31 maart 2017 18:45:36 CEST Maximiliano Curia wrote:
> > ping https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840844 ? 
> > (it's about adding kdeconnect to kde-standard)
> 
> I thought I had replied to that/this request. I also use kdeconnect, but
> it's  only useful if the user has smartphone running Android, that it's
> also running kdeconnect. So, we might add a Suggests, but not a dependency.

My main goal for that bug was discoverability of kdeconnect and a Suggest 
would accomplish that. 
I use it all the time and for *me* it's the main gem in the KDE suit, so I 
wouldn't mind a Recommends either ;-P

signature.asc
Description: This is a digitally signed message part.

Bug#841951: [PATCH]: bitcoin-qt segfaults on startup

[Erik de Castro Lopo]

Hi,

The attached patch applied to the qtbase-opensource-src-5.7.1+dfsg
source packages fixes the segfault for me.

The 5.8.0 package in experimental without this patch still segfaults.
I haven't tried applying this patch to that version.

Cheers,
Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/
Description: qglxconvenience: Avoid NULL dereference

Index: qtbase-opensource-src-5.7.1+dfsg/src/platformsupport/glxconvenience/qglxconvenience.cpp
===
--- qtbase-opensource-src-5.7.1+dfsg.orig/src/platformsupport/glxconvenience/qglxconvenience.cpp
+++ qtbase-opensource-src-5.7.1+dfsg/src/platformsupport/glxconvenience/qglxconvenience.cpp
@@ -207,6 +207,9 @@ GLXFBConfig qglx_findConfig(Display *dis
 
 QXlibPointer visual(glXGetVisualFromFBConfig(display, candidate);
 
+if (! visual)
+continue;
+
 const int actualRed = qPopulationCount(visual->red_mask);
 const int actualGreen = qPopulationCount(visual->green_mask);
 const int actualBlue = qPopulationCount(visual->blue_mask);

C'est LA destination du mois ! 

[Dorian de BedyCasa]

USA, destination du mois
Pour afficher la version graphique (HTML) de cet e-mail, cliquez sur le
lien suivant ou copiez-le dans votre navigateur :
http://emailing.bedycasa.net/u/gm.php?prm=cC3fx4dTdz_290447167_1096458_56308


   Ce mois-ci la destination du mois est ...


Mon compte »
http://emailing.bedycasa.net/u/nrd.php?p=cC3fx4dTdz_56308_1096458_5_3_l=1033586

Toutes les destinations »
http://emailing.bedycasa.net/u/nrd.php?p=cC3fx4dTdz_56308_1096458_4_2_l=1033586

Rechercher un logement »
http://emailing.bedycasa.net/u/nrd.php?p=cC3fx4dTdz_56308_1096458_14_9_l=1033586

Louer son logement »
http://emailing.bedycasa.net/u/nrd.php?p=cC3fx4dTdz_56308_1096458_6_4_l=1033586

USA, destination du mois !
==
Bonjour ,

En février, les Etats-Unis d'Amérique sont notre destination du mois.
Venez découvrir la raison de leur incroyable réputation à travers 4
villes que nous vous proposons et vivez votre propre rêve américain
grâce à nos hébergeurs comme Eric, Sunny ou encore Fabienne
sélectionnés pour vous !

New-York

La ville emblématique des Etats-Unis qui ne se repose jamais.
Retrouvez-vous sur Times Square au milieu de la foule, des buildings et
des panneaux lumineux, ou bien en plein cœur de Central Park, le poumon
de la ville. N’oubliez pas de prendre des photos de la Big Apple du
haut de l’Empire State Building ou encore du Brooklyn Bridge. 

Vous pourriez aller chez Eric un très bon hébergeur BedyCasa qui aime
partager ses passions et vous donner des idées pour visiter NYC.

Je réserve à New-York pour 2 personnes
http://emailing.bedycasa.net/u/nrd.php?p=cC3fx4dTdz_56308_1096458_10_5_l=1033586

Los Angeles
===
Rendez-vous dans l’usine du 7ème art la plus connue au monde ! Vous
retrouverez de nombreuses activités autour du cinéma et de la série
comme une excursion aux studios Warner Bros d’Hollywood, ou encore une
promenade sur la Hollywood Walk of Fame où vous retrouverez la trace de
vos stars favorites. 

Enfin, prenez un vélo et partez dans le Venice Canals District qui vous
transportera dans une autre atmosphère, pour atterrir sur la plage
mythique Venice Beach. Traverser le broadwalk qui longe la mer et
terminer votre escapade au Pier de Santa Monica, avec ce petit parc
d’attraction au bord du Pacifique.

Nous vous conseillons un habitant comme Sunny, quelqu'un qui aime le
partage et qui saura bien vous accueillir dans ses appartements.

Je réserve à Los Angeles pour 2 personnes
http://emailing.bedycasa.net/u/nrd.php?p=cC3fx4dTdz_56308_1096458_17_10_l=1033586

Miami
=
La ville connue pour ses plages de sable blanc et à l’eau
turquoise, ses palmiers, et ses buildings en bord de mer ! La plage
South Beach est un bon endroit pour bronzer et se baigner, et vous
pourrez emprunter la  Miami Beach Broadwalk qui longe l’océan pour
arriver au point le plus au sud de Miami Beach, la South Pointe Park
offrant un joli point de vue avec les bateaux qui rentrent au port. 

C’est à Ocean Drive que vous retrouverez une ambiance des années 30
avec ses restaurants, ses bars et ses vieilles voitures. Si vous
cherchez à vous retrouver avec la nature, vous pourrez vous évader
dans les marécages des Everglades avec sa faune et flore variée.

L’appartement de Fabienne vous fera vivre des vacances dans une
ambiance floridienne puisqu’il est situé à Miami Beach au bord de
l’eau ! 

Je réserve à Miami pour 2 personnes
http://emailing.bedycasa.net/u/nrd.php?p=cC3fx4dTdz_56308_1096458_19_12_l=1033586

Parc national de Glacier

Une destination pour les amoureux de la nature ! Vous retrouverez dans
le nord-ouest des Etats-Unis à Glacier dans l’État de Washington des
chalets, maisons et appartements  de charme au milieu des montagnes. 

Situé à 1h30 du sud de Vancouver et à 2h du nord de Seattle, de
nombreuses activités vous attendent : une descente de ski ou de
snowboard au Mont Baker, du rafting ou de la pêche dans le Wild
Nooksack River, et un plongeon dans le lac Silver Lake Park !  

Je réserve à Glacier pour 2 personnes
http://emailing.bedycasa.net/u/nrd.php?p=cC3fx4dTdz_56308_1096458_18_11_l=1033586

Découvrez nos autres destinations
==

Je réserve à Londres  »
==

Je réserve à Paris »
===

Je réserve à Barcelone »
===

Je réserve à Montpellier »
=

==

Cum sociis natoque penati
Lorem ipsum dolor sitai

Facebook: https://goo.gl/iiPzpu
Twitter: https://goo.gl/7wBTs1
Instagram: https://goo.gl/lrJTZR
Youtube: https://goo.gl/pF6qiq
Pinterest: https://goo.gl/vzX7bY
GooglePlus: https://goo.gl/s1Lwka
LinkedIn: https://goo.gl/oVmMVX

Transporte de Carga desde los 4 puertos principales del pais

[Departamento de Gestion Comercial]

[1] web

[2] nuestros servicios

 forum

[3] contacto

servicios ofrecidos
transmaquina
transporte de carga y alquiler de maquinaria

estimados srs.


quedamos a sus ordenes como proveedores serios y motivados a prestarles un 
excelente servicio en toda venezuela.

en caso de necesitar servicios de:

transporte de carga
alquiler de maquinaria de construcción
alquiler de grúas telescopicas
tansporte de carga extradimensionada
transporte de cemento a granel

reciban un cordial saludo,

luis arriaga
gerente comercial
[4] ven...@transmaquina.com.ve
0424-1362899

[5] www.transmaquina.com.ve

[6] visitar página web

información adicional

cobertura geográfica
prestamos servicios en toda venezuela , ya que trabajamos como aliados en las 
principales ciudades del país.

venta de equipos
prestamos el servicio de venta de equipos. nos encargamos de publicidad de 
venta de camiones, gandolas, maquinaria, grúas y montacargas.
este mensaje fue enviado a t...@test.com por gerencia comercial - luis arriaga
caracas, miranda, venezuela, caracas, miranda  1070, venezuela

cancelar suscripción| administre su suscripción| remitir email| reportar abuso


 References:

1. u=5f04de7
2. u=5f04de7
3. u=5f04de9
4. mailto:ven...@transmaquina.com.ve
5. u=5f04dea
6. u=5f04deb

This message was sent to debian-qt-kde@lists.debian.org by 
vent...@transmaquina.com.ve

You can modify/update your subscription via the link below.

Unsubscribe from all mailings
http://lt.benchmarkurl.com/c/su?e=AA1B43=717D3=F60F9C1=9SyAHd8AObBBgZf8cJWwtbLq%2FMrC8iC0CjsSqTzIaCE%3D=A0B1119


Caracas, Miranda, Venezuela, Caracas, Miranda  1070, Venezuela

Email Marketing
BenchmarkEmail.com
 [http://lt.benchmarkurl.com]

Rematan de Camiones, 30 Gandolas, Maquinaria - Excelente Oportunidad

[Departamento Venta de Equipos]

equipos para la venta

en transmaquina estamos constantemente evolucionando buscando nuevas formas de 
prestarles servicios a nuestros clientes, es por esto que queremos presentarles 
nuestra división de venta de equipos.

actualmente contamos a la fecha con una cartera importante de equipos 
disponibles para la venta.

estos equipos estan disponibles para la venta inmediata y
todos nuestros clientes pueden aceptar pagos de contado y crédito bancario.
[1] solicitar listado de equipos

camiones y remolques
chuto
30
batea
11

cisterna de cemento
31

low boy
2

tara
11

volqueta
41
camion de mantenimiento mecanico

1

camion grua
5

camion mezclador (trompo)
2

camion volteo
41

volqueta
2
ambulancia
4

chevrolet
6

chrysler
2

ford
6

ford
1

jeep
5
torregruas y equipos de construcción

grua
 8

torre grua
 10
silo de cemento
 43

planta de concreto
 3

buldozer
 1

excavador (jumbo)
 2

manipuladora
 3

mini cargador
 15

retroexcavadora
 11

zambron
 12

elevadora
 1

montacarga
 7

compresor
 11

maquina de soldar
 17

planta electrica
 34

zorra
 20

equipos varios
compresor
11

maquina de soldar
17

planta electrica
34

zorra
20

en caso de estar interesados favor enviarnos un email a:

[2] ventadeequi...@transmaquina.com.ve

este mensaje fue enviado a t...@benchmarkemail.com por departamento venta de 
equipos
transporte progaven , caracas, miranda, venezuela, caracas, miranda  1070, 
venezuela

cancelar suscripción| administre su suscripción| remitir email| reportar abuso


 References:

1. mailto:ventadeequi...@transmaquina.com.ve
2. mailto:ventadeequi...@transmaquina.com.ve

This message was sent to debian-qt-kde@lists.debian.org by 
ventadeequip...@transmaquina.com.ve

You can modify/update your subscription via the link below.

Unsubscribe from all mailings
http://lt.benchmarkurl.com/c/su?e=AA1AF5=717D3=F60F9C1=9SyAHd8AObBBgZf8cJWwtbLq%2FMrC8iC0CjsSqTzIaCE%3D=A0B0CAF


Transporte Progaven , Caracas, Miranda, Venezuela, Caracas, Miranda  1070, 
Venezuela

Email Marketing
BenchmarkEmail.com
 [http://lt.benchmarkurl.com]

Cliquez, découvrez la destination du mois de Janvier !

[Dorian de BedyCasa]

L'Espagne, destination du mois
Pour afficher la version graphique (HTML) de cet e-mail, cliquez sur le
lien suivant ou copiez-le dans votre navigateur :
http://emailing.bedycasa.net/u/gm.php?prm=cC3fx4dTdz_290447167_1041406_39513


 Bonne année 2017 à tous ! Ce mois-ci la destination du mois est ...


Mon compte »
http://emailing.bedycasa.net/u/nrd.php?p=cC3fx4dTdz_39513_1041406_5_3

Toutes les destinations »
http://emailing.bedycasa.net/u/nrd.php?p=cC3fx4dTdz_39513_1041406_4_2

Rechercher un logement »
http://emailing.bedycasa.net/u/nrd.php?p=cC3fx4dTdz_39513_1041406_14_9

Louer son logement »
http://emailing.bedycasa.net/u/nrd.php?p=cC3fx4dTdz_39513_1041406_6_4

L'Espagne, destination du mois !

Bonjour ,

La nouvelle année vient tout juste de commencer. Nous en profitons donc
pour vous souhaiter à tous une belle année 2017 alliant la santé et
la réussite dans tous vos projets personnels et professionnels.

L’Espagne est notre destination du mois. Nous vous invitons à visiter
ce magnifique pays reconnu pour la diversité de ses paysages, cultures
et langues. Amanda et Cristina, toutes deux espagnoles, vous donnent
leurs meilleurs conseils pour visiter autrement la péninsule ibérique.


Barcelone
=
Ville emblématique de la Catalogne. Cristina vous conseille de suivre
les traces de Don Quichotte suivi d’une pause dans l'après-midi au
bar de Chuchos vers la Boqueria avant d'admirer la danse typique de
Barcelone : La Sardana.


Je réserve à Barcelone pour 2 personnes
http://emailing.bedycasa.net/u/nrd.php?p=cC3fx4dTdz_39513_1041406_10_5

Cordoue
===
Originaire d’Andalousie, Amanda vous propose de visiter Cordoue, ville
millénaire inscrite au patrimoine de l’humanité. Elle représente un
véritable héritage vivant de toutes les civilisations qui s’y sont
installées au cours de l’histoire. 

Dégustez l’une des meilleures tortillas de Cordoue au Bar Santos,
suivi d’un moment de détente dans les bains arabes. Finissez votre
soirée avec une visite nocturne* qui vous fera découvrir les légendes
et mystères de la ville.

*Pour toute réservation à Cordoue, recevez un code de réduction pour
"Córdoba misteriosa" en répondant à cet email


Je réserve à Cordoue pour 2 personnes
http://emailing.bedycasa.net/u/nrd.php?p=cC3fx4dTdz_39513_1041406_11_6

Valence
===
Troisième ville du pays en terme de population, Valence est une
destination incontournable d’Espagne. Reconnue notamment pour sa fête
“Fallas” qui a lieu en mars ou pour ses spécialités gastronomiques
comme la “Fideuà” ou la “Orxata”. Cristina et Amanda vous
conseille de visiter le “Oceanographic de Valencia”, le plus grand
aquarium d’Europe; ou encore le Zoo “Bioparc” en plein
centre-ville.



Je réserve à Valence pour 2 personnes
http://emailing.bedycasa.net/u/nrd.php?p=cC3fx4dTdz_39513_1041406_12_7

Madrid
==
Cristina vous propose sa journée type à Madrid, capitale de
l’Espagne : “Le matin il faut aller visiter le musée “Reina
Sofia”, prendre ensuite une pause le midi au Parc du Retiro, suivi
d’une découverte du musée du Prado. Enfin finir la journée avec une
Caña et un bocadillo de calamares.” Mais le meilleur conseil de
Cristina est : “perdez-vous dans la ville et découvrez les merveilles
que renferment les rues de la capitale, vous vous sentirez comme dans un
film d’Almodovar ”.


Je réserve à Madrid pour 2 personnes
http://emailing.bedycasa.net/u/nrd.php?p=cC3fx4dTdz_39513_1041406_13_8

==

Cum sociis natoque penati
Lorem ipsum dolor sitai

Facebook: https://goo.gl/iiPzpu
Twitter: https://goo.gl/7wBTs1
Instagram: https://goo.gl/lrJTZR
Youtube: https://goo.gl/pF6qiq
Pinterest: https://goo.gl/vzX7bY
GooglePlus: https://goo.gl/s1Lwka
LinkedIn: https://goo.gl/oVmMVX

==
Adresse:
BedyCasa
1348 Avenue de la mer - Raymond Dugrand
34000 Montpellier
France

Informations:
cont...@bedycasa.com
+33 (0)4 11 93 43 70
www.bedycasa.com

Catégories:
Paris
https://fr.bedycasa.com/chambre-a-louer/paris-30550.html?sort=popularity
New-York https://fr.bedycasa.com/chambre-a-louer/new-york-39466.html
La Havane https://fr.bedycasa.com/chambre-a-louer/la-havane-43930.html
Madrid https://fr.bedycasa.com/chambre-a-louer/madrid-30288.html
Londres https://fr.bedycasa.com/chambre-a-louer/londres-39324.html

Liens:
Comment ça marche?: https://fr.bedycasa.com/page/how-it-works.html
Rechercher un logement: https://fr.bedycasa.com
Louer son logement: https://fr.bedycasa.com/rent-out/step1
Toutes nos destinations: https://fr.bedycasa.com/sitemap/destination
Mon compte: https://fr.bedycasa.com/dashboard/

Se désabonner:
http://emailing.bedycasa.net/u/un.php?par=cC3fx4dTdz_1041406_39513_$sid$

Destinations du mois : La Réunion, La Martinique, La Guadeloupe et l'Île Maurice !

[Dorian de BedyCasa]

Pour afficher la version graphique (HTML) de cet e-mail, cliquez sur le
lien suivant ou copiez-le dans votre navigateur :
http://emailing.bedycasa.net/u/gm.php?prm=cC3fx4dTdz_290447167_1002364_42156



En ce mois de décembre, les Îles les plus actives sur BedyCasa sont...



La Réunion, La Martinique, La Guadeloupe et l’île Maurice
Destinations du mois de décembre



Bonjour

Je suis Magali, fondatrice de BedyCasa. Il y a plusieurs mois, nous nous
sommes lancés comme mission de faire découvrir à vous tous,
utilisateurs de BedyCasa, le peuple Cubain.

Nous sommes allés pendant près d’une semaine à Cuba, à la
rencontre des habitants, afin d’en savoir plus sur leur culture, leur
mode de vie.

Le premier mot qui me vient à l’esprit est : MAGIQUE. La vie là-bas
vous surprend à chaque coin de rue, la population vit avec peu, mais
vit et profite de ce qu’elle a. Un simple regard vous permet de
décrocher un sourire à un inconnu. La foule, les chants vous enivrent,
vous êtes transportés par l’atmosphère présente et vous vous
laissez emporter.

Je vous invite, en ce mois dédié à Cuba, à regarder les vidéos que
nous avons tournées en partenariat avec FrenchWood et AirFrance. Comme
dirait mon amie Yadira, "A mal tiempo, buena cara", quoi qu'il t'arrive,
garde le sourire !'

Découvrez mon article sur le BedyBlog !


La Réunion
===
Une île vivante, surprenante, constamment en mouvement. Sous un climat
ensoleillé et chaleureux, découvrez le piton de la Fournaise et toute
cette île merveilleuse.
Découvrez tous nos hébergeurs à La Réunion

Chez Patrice à Saint-André

Chez Nadine et Patrick à La Saline

La Martinique
=
Une île qui surprend par sa particularité de marier l’inconciliable
: pluie et soleil, bleus qui font mal aux yeux et verts tendres. Les
volcans et la végétation paradisiaque. 
Découvrez tous nos hébergeurs à La Martinique

Chez Kikina à Le Diamant

Chez Betty à Fort de France

La Guadeloupe
=
Les longues plages blanches de Sainte-Anne, les plages noires de
Trois-Rivières, anses bordées de mangroves et de cocotiers. Une île
tropicale, grouillante et pleine de vie.
Découvrez nos hébergeurs à La Guadeloupe


Chez Nicole à Pointe-noire

Chez Véronique à Petit-Canal

L'Île Maurice
==
Laissez-vous aller, au rythme des vagues. Une visite par-ci, une petite
visite par-là, et retour chez l’habitant ! 
Découvrez tous nos hébergeurs à l'Île Maurice

Chez Olivier à Port Louis

Chez Brigitte à Blue Bay

Découvrez toutes nos destinations
http://emailing.bedycasa.net/u/nrd.php?p=cC3fx4dTdz_42156_1002364_13_2

JEU CONCOURS CALENDRIER DE L'AVENT

===
On ne vous fait pas languir jusqu’au 25 décembre ! En partenariat
avec BedyCasa, OUIBUS vous offre des cadeaux dès maintenant. Pour cela,
c’est très simple: il vous suffit d’ouvrir chaque jour une fenêtre
de notre calendrier de l’avent. Tentez de gagner des week-ends pour 2
personnes, des films, des trajets OUIBUS ainsi que des centaines
d’autres surprises. 
Alors, prêt à gagner ?


Jouez ici
http://emailing.bedycasa.net/u/nrd.php?p=cC3fx4dTdz_42156_1002364_42_36
Vous souhaitez vous désabonner de notre super newsletter, c'est
possible, en cliquant ici , mais c'est dommage :( :
http://emailing.bedycasa.net/u/un.php?par=cC3fx4dTdz_1002364_42156_$sid$

Bug#846964: Kolourpaint 16.08.2: It is not possible to navigate by directories in Save as... form.

[Innocent De Marchi]

Package: kolourpaint4
Version: 4:16.08.2
Severity: normal

Dear Maintainer,

With the xfce desktop, the «Save as..» form don't show the directories.
I am ask to upstreams from this issue and it turns out that installing
the kio package solves the problem.

Consider to add kio package to kolourpaint dependencies.

Regards!

I. De Marchi

P.S. Sorry for the previus message: it was a mistake!

Bug#846963: Kolourpaint 16.08.2: It is not possible to navigate by directories in Save as... form.

[Innocent De Marchi]

Package: kolourpaint4
Version: 4:16.08.2
Severity: normal

Dear Maintainer,

With the xfce desktop, the «Save as..» form don't show

the directories.

Se Mantiene el Precio y se Rematan 114 Camiones y 30 Gandolas - Excelente Oportunidad

[Departamento Venta de Equipos]

equipos para la venta

en transmaquina estamos constantemente evolucionando buscando nuevas formas de 
prestarles servicios a nuestros clientes, es por esto que queremos presentarles 
nuestra división de venta de equipos.

actualmente contamos a la fecha con una cartera importante de equipos 
disponibles para la venta.

estos equipos estan disponibles para la venta inmediata y
todos nuestros clientes pueden aceptar pagos de contado y crédito bancario.
[1] solicitar listado de equipos

camiones y remolques
chuto
30
batea
11

cisterna de cemento
31

low boy
2

tara
11

volqueta
41
camion de mantenimiento mecanico

1

camion grua
5

camion mezclador (trompo)
2

camion volteo
41

volqueta
2
ambulancia
4

chevrolet
6

chrysler
2

ford
6

ford
1

jeep
5
torregruas y equipos de construcción

grua
 8

torre grua
 10
silo de cemento
 43

planta de concreto
 3

buldozer
 1

excavador (jumbo)
 2

manipuladora
 3

mini cargador
 15

retroexcavadora
 11

zambron
 12

elevadora
 1

montacarga
 7

compresor
 11

maquina de soldar
 17

planta electrica
 34

zorra
 20

equipos varios
compresor
11

maquina de soldar
17

planta electrica
34

zorra
20

en caso de estar interesados favor enviarnos un email a:

[2] ventadeequi...@transmaquina.com.ve

este mensaje fue enviado a t...@benchmarkemail.com por departamento venta de 
equipos
transporte progaven , caracas, miranda, venezuela, caracas, miranda  1070, 
venezuela

cancelar suscripción| administre su suscripción| remitir email| reportar abuso


 References:

1. mailto:ventadeequi...@transmaquina.com.ve
2. mailto:ventadeequi...@transmaquina.com.ve

This message was sent to debian-qt-kde@lists.debian.org by 
ventadeequip...@transmaquina.com.ve

You can modify/update your subscription via the link below.

Unsubscribe from all mailings
http://lt.bmetrack.com/c/su?e=A600A0=717D3=F60F9C1=9SyAHd8AObBBgZf8cJWwtbLq%2FMrC8iC0CjsSqTzIaCE%3D=A0B1125


Transporte Progaven , Caracas, Miranda, Venezuela, Caracas, Miranda  1070, 
Venezuela

Email Marketing
BenchmarkEmail.com
 [http://lt.bmetrack.com]