Re: Workflow to package the full KDE Plasma desktop
Hey, actually you should send those requests to the packagers discussion list: pkg-kde-t...@alioth-lists.debian.net The list debian-qt-kde@lists.debian.org is not discussion and only the bug mailing list. > I'm afraid my request might be hard to understand, but I'm trying for > several weeks to *build the latest stable KDE plasma from source* on my > Debian Bookworm. But using the documented method (kdesrc-build and stuff), > it always end up with a broken desktop session that does not boot... Actually we also try to get the last plasma version into testing. Hopefully we get an ACK from the release team. Currently you can grab the last Plasma version from experimental. We package the KDE packages with out scripts you find under: https://salsa.debian.org/qt-kde-team/pkg-kde-dev-scripts Unfortunately it is not documented or only very few bits are documented :( That's why don't hesitate to ask and we try together to improve the documentation. A new person with new questions is always a good motivation to do so. A good place for questions is also IRC #debian-qt-kde (on irc.debian.org) or the corresponding Matrix channel. We also are happy if more people join our team and help packaging KDE software. Regards, hefee 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
Hey, 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. 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. 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. > I have no clue how this can happen or be explained, > but it sounds like a bug to me. So far I know gnupg does want to get rid of multiple keyrings statched together. So maybe you find one of the bugs with statching. But you may get more up-to-date news from gnupg mantainers in Debian. hefee signature.asc Description: This is a digitally signed message part.
Bug#970450: akonadi-server: akonadi fails to start if the XDG variables point outside of $HOME
Hey,
Apparmor does not know any environmental variables, so it cannot handle your
case. In your usecase you have to update the @{xdg_data_home} and
@{xdg_config_home} inside usr.bin.akonadiserver to point to the correct
directories, than Apparmor should be fine with your setup. Or update /etc/
apparmor/tunables/home.
As this is not a default setup and I see no way how Apparmor rules could be
better written to support your usecase. It seems it is more like a general
user request for Apparmor.
Regards,
hefee
signature.asc
Description: This is a digitally signed message part.
Bug#986404: libkf5messagecomposer5abi1: Explicit saved encryption setting are not reused
Package: libkf5messagecomposer5abi1 Version: 4:20.08.3-2 Severity: normal When you select a explicit PGP Key for a emailaddress (Contact Preferences) those should be taken into account, when sending the next mail. Those setting are totally ignored at the moment. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (400, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-5-amd64 (SMP w/4 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 libkf5messagecomposer5abi1 depends on: ii kf5-messagelib-data 4:20.08.3-2 ii kio 5.78.0-4 ii libc6 2.31-11 ii libgcc-s1 10.2.1-6 ii libgpgmepp6 1.14.0-1+b2 ii libkf5akonadicontact5 [libkf5akonadicontact5-20.08] 4:20.08.3-1 ii libkf5akonadicore5abi2 [libkf5akonadicore5-20.08] 4:20.08.3-1 ii libkf5akonadimime5 [libkf5akonadimime5-20.08] 4:20.08.3-1 ii libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-20.08] 4:20.08.3-1 ii libkf5calendarcore5abi2 5:5.78.0-2 ii libkf5codecs5 5.78.0-2 ii libkf5completion5 5.78.0-3 ii libkf5configcore5 5.78.0-4 ii libkf5configgui5 5.78.0-4 ii libkf5contacts5 5:5.78.0-2 ii libkf5coreaddons5 5.78.0-4 ii libkf5i18n5 5.78.0-2 ii libkf5identitymanagement5 [libkf5identitymanagement5-20.08] 20.08.3-1 ii libkf5jobwidgets5 5.78.0-2 ii libkf5kiocore55.78.0-4 ii libkf5kiofilewidgets5 5.78.0-4 ii libkf5kiogui5 5.78.0-4 ii libkf5kiowidgets5 5.78.0-4 ii libkf5libkdepim5 [libkf5libkdepim5-20.08] 4:20.08.3-1 ii libkf5libkleo5 [libkf5libkleo5-20.08] 4:20.08.3-1 ii libkf5mailtransport5 [libkf5mailtransport5-20.08] 20.08.3-1 ii libkf5mailtransportakonadi5 [libkf5mailtransportakonadi5-20. 20.08.3-1 ii libkf5messagecore5abi1 [libkf5messagecore5-20.08] 4:20.08.3-2 ii libkf5messageviewer5abi1 [libkf5messageviewer5-20.08] 4:20.08.3-2 ii libkf5mime5abi1 [libkf5mime5-20.08] 20.08.3-1 ii libkf5mimetreeparser5abi1 [libkf5mimetreeparser5-20.08] 4:20.08.3-2 ii libkf5pimcommon5abi2 [libkf5pimcommon5-20.08] 4:20.08.3-1 ii libkf5pimcommonakonadi5abi1 [libkf5pimcommonakonadi5-20.08] 4:20.08.3-1 ii libkf5pimtextedit5abi2 [libkf5pimtextedit5-20.08] 20.08.3-1 ii libkf5sonnetui5 5.78.0-2 ii libkf5templateparser5 [libkf5templateparser5-20.08] 4:20.08.3-2 ii libkf5widgetsaddons5 5.78.0-2 ii libkf5xmlgui5 5.78.0-2 ii libqgpgme71.14.0-1+b2 ii libqt5core5a 5.15.2+dfsg-5 ii libqt5dbus5 5.15.2+dfsg-5 ii libqt5gui55.15.2+dfsg-5 ii libqt5network55.15.2+dfsg-5 ii libqt5widgets55.15.2+dfsg-5 ii libstdc++610.2.1-6 libkf5messagecomposer5abi1 recommends no packages. libkf5messagecomposer5abi1 suggests no packages. -- debconf-show failed
Bug#964963: Icons mail-thread-ignored.png and mail-thread-watched.png not correctly displayed
Control: tags -1 + fixed-upstream
Patch was merged within 20.12.
--
On Montag, 13. Juli 2020 15:44:08 CEST Sven Bartscher wrote:
> Package: libkf5messagelist5abi1
> Version: 4:20.04.1-1
> Severity: minor
>
> kmail apparently doesn't display icons for ignored or watched threads
> in message lists or the design editor for message lists. The icon
> seems to be missing, because libkf5messagelist loads the icons in
> messagelist/core/theme.cppL1267 as follows:
>
> << new
> QPixmap(QIcon::fromTheme(QStringLiteral("messagelist/pics/mail-thread-watch
> .png")).pixmap(mIconSize, mIconSize)) << new
> QPixmap(QIcon::fromTheme(QStringLiteral("messagelist/pics/mail-thread-ignor
> ed.png")).pixmap(mIconSize, mIconSize))
>
> However, I could find no theme in the Debian repository providing this
> path. Instead I found these close fits:
>
> $ apt-file search mail-thread-ignored
> breeze-icon-theme:
> /usr/share/icons/breeze-dark/actions/16/mail-thread-ignored.svg
> breeze-icon-theme:
> /usr/share/icons/breeze-dark/actions/22/mail-thread-ignored.svg
> breeze-icon-theme:
> /usr/share/icons/breeze-dark/actions/24/mail-thread-ignored.svg
> breeze-icon-theme:
> /usr/share/icons/breeze/actions/16/mail-thread-ignored.svg
> breeze-icon-theme:
> /usr/share/icons/breeze/actions/22/mail-thread-ignored.svg
> breeze-icon-theme:
> /usr/share/icons/breeze/actions/24/mail-thread-ignored.svg
> deepin-icon-theme:
> /usr/share/icons/bloom/actions/24/mail-thread-ignored.svg kmail:
> /usr/share/doc/HTML/en/kmail2/mail-thread-ignored.png
> numix-icon-theme: /usr/share/icons/Numix/16/actions/mail-thread-ignored.svg
> numix-icon-theme: /usr/share/icons/Numix/22/actions/mail-thread-ignored.svg
> papirus-icon-theme:
> /usr/share/icons/Papirus-Dark/16x16/actions/mail-thread-ignored.svg
> papirus-icon-theme:
> /usr/share/icons/Papirus-Dark/22x22/actions/mail-thread-ignored.svg
> papirus-icon-theme:
> /usr/share/icons/Papirus-Dark/24x24/actions/mail-thread-ignored.svg
> papirus-icon-theme:
> /usr/share/icons/Papirus/16x16/actions/mail-thread-ignored.svg
> papirus-icon-theme:
> /usr/share/icons/Papirus/22x22/actions/mail-thread-ignored.svg
> papirus-icon-theme:
> /usr/share/icons/Papirus/24x24/actions/mail-thread-ignored.svg
> papirus-icon-theme:
> /usr/share/icons/ePapirus/16x16/actions/mail-thread-ignored.svg
> papirus-icon-theme:
> /usr/share/icons/ePapirus/22x22/actions/mail-thread-ignored.svg
> papirus-icon-theme:
> /usr/share/icons/ePapirus/24x24/actions/mail-thread-ignored.svg
>
> My guess is, that the paths for these icons need to be adjusted to
> match one of these icons.
>
> -- System Information:
> Debian Release: bullseye/sid
> APT prefers testing-debug
> APT policy: (990, 'testing-debug'), (990, 'testing'), (102,
> 'unstable-debug'), (102, 'unstable'), (101, 'experimental-debug'), (101,
> 'experimental') Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.7.0-1-amd64 (SMP w/12 CPU cores)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8
> (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) 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.04.1-1
> ii kio 5.70.1-1
> ii libc62.30-8 ii
> libgcc-s110.1.0-4 ii
> libkf5akonadicore5abi2 [libkf5akonadicore5-20.04]4:20.04.1-2+b1
> ii libkf5akonadimime5 [libkf5akonadimime5-20.04]
> 4:20.04.1-1 ii libkf5akonadisearchpim5 [libkf5akonadisearchpim5-20.04]
> 4:20.04.1-1 ii libkf5completion5
> 5.70.0-1 ii libkf5configcore5
> 5.70.0-1 ii libkf5configgui5
> 5.70.0-1 ii libkf5configwidgets5
> 5.70.0-1 ii libkf5coreaddons5
> 5.70.0-1 ii libkf5i18n5
> 5.70.0-1 ii libkf5iconthemes5
> 5.70.0-1 ii libkf5itemmodels5
> 5.70.0-1.1 ii libkf5kiocore5
> 5.70.1-1 ii libkf5messagecore5abi1 [libkf5messagecore5-20.04]
> 4:20.04.1-1 ii libkf5mime5abi1 [libkf5mime5-20.04]
> 20.04.1-1 ii libkf5pimcommon5abi2 [libkf5pimcommon5-20.04]
> 4:20.04.1-1 ii libkf5pimcommonakonadi5abi1 [libkf5pimcommonakonadi5-20.04]
> 4:20.04.1-1 ii libkf5textwidgets5
> 5.70.0-1 ii libkf5widgetsaddons5
> 5.70.0-1 ii
Bug#985080: Akonadi server crashes because of Apparmor rules
Hi, > the Akonadi server permanently crashes on login after upgrading to Bullseye. I cannot reproduce this on my setup an using Akonadi server the whole time. So I'm interested, why this happens for you and not for me. What resources are you using? I use only a private IMAP server with MariaDB as Akonadi backend and using X11 (not Wayland). > It would be good if the Apparmor rules of the Akonadi server were > functional. In the current state, the Akonadi server is unfortunately not > usable without user adjustments. This is not true for me and also other distros use these Apparmor rules and are happy ( at least I did not got any negative feedback/patches for around 6 months). So it seems like you triggered a test case other did not catch, so it would be helpful if you describe your setup, to get this patch upstream. regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#982221: k3b: please stop using cdrkit
Hey, Upstream k3b is searching for new maintainers, k3b is currently only in low level bugfixing and such a big change like switching away from cdrkit is out of scrope [1]. And it is too much work for the current Debian maintainers. Any help is welcomed. The discussion started, as Debian won't ship cdrkit ( wodim and genisoimage) anymore in bookworm [#982221]. hefee [1] https://bugs.kde.org/show_bug.cgi?id=432684 [#982221] https://bugs.debian.org/982221 -- On Sonntag, 7. Februar 2021 16:27:19 CET Chris Hofstaedtler wrote: > Package: k3b > Version: 20.12.2-1 > Severity: important > > Dear k3b Maintainers, > > your package depends on wodim and genisoimage, both built from > cdrkit sources. cdrkit does not have a path forward, please switch > away from it rather soon. I'm told xorriso and libburnia are > alternatives and are alive and doing well. > > It's been suggested cdrkit should not be in bookworm. > > Chris signature.asc Description: This is a digitally signed message part.
Bug#942078: [high quality bug] baloo crash, can't recover; forced reindex does not fix; unusable via dolphin C-f
Hey, > The crash is not specific to jack_capture_90.mp3; except for a period of > time a couple of weeks long leading up to the original bug. But do you see any pattern? I cannot reproduce it, too. > Has anyone on the team tried testing baloo with a large $HOME? Yes I think myself. Baloo indexed 1.387.086 files (mixed content) ; 650GB source file =>10GB baloo database. According your description of the bug, that is bigger than your dataset and be enough to reproduce. Why do you think we do not use the software they maintain? Baloo is working great for me, I haven't seen issues for a long long time. Okay what can you do to tackle down the bug: * debug symbols for libKF5BalooEngine.so.5 and liblmdb.so.0, so that we know what line triggers the segfault. because the interesting part is without debug symbols. * can you reproducible trigger the crash with jack_capture_90.mp3, or any other file? * did you checked upstream bug tracker - to find any matching bug? As this is an upstream issue, it needs to be fixed by upstream anyways, so we need to clarify if the issue is still at a current version. Otherwise create a bugreport at bugs.kde.org, they should also know better what infos they need to fix the issue. * start a Debian unstable VM/ KDE neon VM and try to reproduce the issue > It could take up to a month to reproduce this bug, and by then the reply will be "ignore for bullseye". This is a contributing factor to why baloo is in perpetual beta (I'd argue alpha, but subjectivity ;-)) Yes I know the timeframe small between the freeze and release to tackle down complicated issues. But please don't forget the other side. What should maintainers do if, they cannot reproduce the issue and upstream does not have stable LTS branches and doing monthly releases? The first thing is checking the current version: If it is fixed, than one can search for the bugfix to backport it or file the bug upstream otherwise. But without checking against the current version upstream reply most of the time: please update first. So I cannot reproduce it nor Norbert. Mark the bug as "unreproducible" is a valid approach, as we cannot tell if it is fixed or not. With more information it may be possible to decide. That's why the question is so important: Can you reproduce it somehow, so we are able to see the same issue? hefee signature.asc Description: This is a digitally signed message part.
Bug#951588: kontact: akonadi is not operational
control: tags -1 + moreinfo control: severity -1 important Hey, please retry with the current version in testing/unstable and give us more information what you have tried to do before kontact returns with a segfault. Maybe this issue is more for the Akonadi package? At least from what I can tell is that is works for a lot of people, so I lower the severity. hefee On Dienstag, 18. Februar 2020 14:34:53 CET Alberto Fuentes wrote: > Package: kontact > Version: 4:19.08.3-1 > Severity: grave > Justification: renders package unusable > > Application: Akonadi Control (akonadi_control), signal: Aborted > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > [Current thread is 1 (Thread 0x7ff192558800 (LWP 1433258))] > > Thread 5 (Thread 0x7ff189e1f700 (LWP 1433262)): > #0 0x7ff195d5abef in __GI___poll (fds=0x7ff1800021e0, nfds=1, > timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 > #1 0x7ff19510710e in ?? () from > /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff19510722f in > g_main_context_iteration () from > /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 > #3 0x7ff1962e381b in > QEventDispatcherGlib::processEvents(QFlags) > () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > #4 0x7ff19628c71b in > QEventLoop::exec(QFlags) () from > /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > #5 0x7ff1960cd731 in QThread::exec() () from /usr/lib/x86_64-linux- > gnu/libQt5Core.so.5 > #6 0x7ff196bf14e6 in ?? () from > /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7ff1960ce8b2 in ?? () > from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff195c52fb7 in > start_thread (arg=) at > pthread_create.c:486 > #9 0x7ff195d651af in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 > > Thread 4 (Thread 0x7ff18a703700 (LWP 1433261)): > #0 0x7ff195d5abef in __GI___poll (fds=0x55fdcd713ff0, nfds=2, > timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 > #1 0x7ff19510710e in ?? () from > /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff195107473 in > g_main_loop_run () from /usr/lib/x86_64-linux- gnu/libglib-2.0.so.0 > #3 0x7ff18b9c89e6 in ?? () from > /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7ff19512fd7d in ?? () > from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff195c52fb7 in > start_thread (arg=) at > pthread_create.c:486 > #6 0x7ff195d651af in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 > > Thread 3 (Thread 0x7ff18af04700 (LWP 1433260)): > #0 0x7ff195d5abef in __GI___poll (fds=0x55fdcd6ffb90, nfds=1, > timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 > #1 0x7ff19510710e in ?? () from > /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff19510722f in > g_main_context_iteration () from > /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 > #3 0x7ff195107281 in ?? () from > /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff19512fd7d in ?? () > from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff195c52fb7 in > start_thread (arg=) at > pthread_create.c:486 > #6 0x7ff195d651af in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 > > Thread 2 (Thread 0x7ff1912c6700 (LWP 1433259)): > #0 0x7ff195d5abef in __GI___poll (fds=0x7ff1912c5ca8, nfds=1, > timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 > #1 0x7ff194ff1cf7 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 > #2 0x7ff194ff391a in xcb_wait_for_event () from /usr/lib/x86_64-linux- > gnu/libxcb.so.1 > #3 0x7ff191eabca0 in ?? () from /usr/lib/x86_64-linux- > gnu/libQt5XcbQpa.so.5 > #4 0x7ff1960ce8b2 in ?? () from > /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff195c52fb7 in > start_thread (arg=) at > pthread_create.c:486 > #6 0x7ff195d651af in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 > > Thread 1 (Thread 0x7ff192558800 (LWP 1433258)): > [KCrash Handler] > #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 > #7 0x7ff195c90535 in __GI_abort () at abort.c:79 > #8 0x55fdcbc662e2 in akMessageHandler (type=QtFatalMsg, msg=..., > context=...) at ./src/shared/akdebug.cpp:205 > #9 akMessageHandler (type=, context=..., msg=...) at > ./src/shared/akdebug.cpp:194 > #10 0x55fdcbc6834e in (anonymous namespace)::RemoteLogger::dbusLogger > (type=QtFatalMsg, ctx=..., msg=...) at ./src/shared/akremotelog.cpp:178 > #11 0x7ff1960c64b1 in ?? () from > /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7ff1960c65c9 in ?? () > from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7ff196096a44 in > QMessageLogger::fatal(char const*, ...) const () from > /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > #14 0x55fdcbc3c4e1 in AgentManager::AgentManager (this=0x7ffd636395f0, > verbose=, parent=) at > /usr/include/x86_64-linux- gnu/qt5/QtCore/qlogging.h:91 > #15 0x55fdcbc3e374 in main (argc=, argv=) > at ./src/akonadicontrol/main.cpp:76 > [Inferior 1 (process 1433258) detached] > > > > -- System Information: >
Bug#974860: Forwarded to upstream
Hey Silvério, thanks for forwanrding the bugs to upstream. I see you tried to update the Debian Bug Tracker(BTS) two times. Pino already properly updated your bugs. Okay I was not exactly clear about the correct syntax. There are two way to interact with BTS. You can use sending mails to cont...@debian.org, than you have to send: Forwarded 974860 https://bugs.kde.org/show_bug.cgi?id=430719 Or you send the mail to the bug itself ( 974...@bugs.debian.org) than you have to prefix the command with Control: Control: Forwarded 974860 https://bugs.kde.org/show_bug.cgi?id=430719 Additionally you are able to replace the current bugnumber with -1 so you can shorten this to: Control: Forwarded -1 https://bugs.kde.org/show_bug.cgi?id=430719 and please use only text-only mails. In the beginning it is hard to remember the differences and make a lot a failures. Sorry for not being that precise. You can find the documentation at https://bugs.debian.org. There is also a CLI from devscripts package the command is called bts. hefee signature.asc Description: This is a digitally signed message part.
Re: Bug#977693: gtk+3.0: Wayland primary selection interoperability with GTK clients on Plasma Desktop
Hey, > > Upstream GTK developer Emmanuele Bassi said that there are no more gtk3 > > dot releases planned (at least not before GTK 4.0 is released). > > That seems to be outdated information: GTK 4.0.0 has been released now > (I uploaded it to experimental NEW since it has a new SONAME and needs > a newer version of Pango), and a 3.24.24 point release also happened. great. > > Emmanuale recommends cherry-picking this patch from the gtk-3-24 stable > > branch to distro packages: > > > > https://gitlab.gnome.org/GNOME/gtk/-/commit/9a693c7228a88b76a007aed41b101d > > 89d084cf9b > That's included in 3.24.24, in testing since 2020-12-14. Thanks for this info. > > > To verify that the patch works: > > 1. Log into a Plasma Wayland session > > I'll try to test this at some point, but it's very likely to be quicker > for a Plasma user to upgrade their GTK 3 version than it is for me to > install Plasma. I tested it on my machine (Debian unstable with libgtk-3-common 3.24.24-1) and still I cannot copy text from Firefox to other clients. I'll forward your text to the distributions mailinglist, as I'm not an upstream developer of Plasma. And the primary mail with the request for backport came from the plasma team. regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#974827: kmail: Navigate through emails in email message windows: next, previous, next unread, previous unread
Hey,
The bug is not a Debian specific one, so it should be reported and fixed
upstream at KDE:
https://bugs.kde.org
Please also leave a comment here at this bugreport with the url of the
upstream bug, so we are able to track the upstream bug status. To do this
properly add a line to the mail with:
Control: Forwarded -1 {url}
at the beginning of your response, than BTS (Debian Bugtracker) will do its
magic.
hefee
--
> when opening emails in windows on their own the next email has to opened by
> closing the current window, selecting the next one in the folder and opening
> it in another window. It would be desirable to be able to navigate through
> email from within the email window.
> Fun fact, this was an unanswered question on stackexchange 4 years and 9
> mtónths ago: https://unix.stackexchange.com/questions/259812/next-unread->
> message-shortcut-in-kmail-message-window
>
> This is amplified by kmail's misbehaviour on KDE Wayland. Through the
> inability to show the email in the preview pane, emails have to be opened
> in email message windows on Wayland (see
> https://bugs.kde.org/show_bug.cgi?id=414955)
>
>
>
> -- System Information:
> Debian Release: bullseye/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
> 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:20.08.2-3+b1 ii kdepim-runtime
> 4:20.08.2-4 ii kio
> 5.74.0-2 ii libc6
>2.31-4 ii libgcc-s1
> 10.2.0-16 ii libgpgmepp6
> 1.14.0-1+b1 ii libkf5akonadiagentbase5 [libkf5akonadiagentbase5-20.08]
> 4:20.08.2-3+b1 ii libkf5akonadicontact5 [libkf5akonadicontact5-20.08]
> 4:20.08.2-3 ii libkf5akonadicore5abi2 [libkf5akonadicore5-20.08]
> 4:20.08.2-3+b1 ii libkf5akonadimime5 [libkf5akonadimime5-20.08]
> 4:20.08.2-2 ii libkf5akonadisearch-bin
>4:20.08.2-2 ii libkf5akonadisearch-plugins
> 4:20.08.2-2 ii libkf5akonadisearchdebug5
> [libkf5akonadisearchdebug5-20.08] 4:20.08.2-2 ii libkf5akonadisearchpim5
> [libkf5akonadisearchpim5-20.08] 4:20.08.2-2 ii
> libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-20.08] 4:20.08.2-3+b1
> ii libkf5bookmarks5 5.74.0-2
> ii libkf5calendarcore5abi2 5:5.74.0-2
> ii libkf5calendarutils5 [libkf5calendarutils5-20.08]
> 4:20.08.2-2 ii libkf5codecs5
> 5.74.0-2 ii libkf5completion5
> 5.74.0-2 ii libkf5configcore5
> 5.74.0-2 ii libkf5configgui5
> 5.74.0-2 ii libkf5configwidgets5
> 5.74.0-2 ii libkf5contacts5
> 5:5.74.0-2 ii libkf5coreaddons5
> 5.74.0-2 ii libkf5crash5
> 5.74.0-2 ii libkf5dbusaddons5
> 5.74.0-2 ii libkf5grantleetheme-plugins
> 20.08.2-2 ii libkf5gravatar5abi2 [libkf5gravatar5-20.08]
> 4:20.08.2-2 ii libkf5guiaddons5
> 5.74.0-3 ii libkf5i18n5
> 5.74.0-3 ii libkf5iconthemes5
> 5.74.0-2 ii libkf5identitymanagement5 [libkf5identitymanagement5-20.08]
> 20.08.2-2 ii libkf5itemmodels5
> 5.74.0-2 ii libkf5itemviews5
> 5.74.0-2 ii libkf5jobwidgets5
> 5.74.0-2 ii libkf5kcmutils5
> 5.74.0-2 ii libkf5kiocore5
> 5.74.0-2 ii libkf5kiofilewidgets5
> 5.74.0-2 ii libkf5kiogui5
> 5.74.0-2 ii libkf5kiowidgets5
> 5.74.0-2 ii libkf5kontactinterface5 [libkf5kontactinterface5-20.08]
> 20.08.2-2 ii libkf5ksieveui5 [libkf5ksieveui5-20.08]
> 4:20.08.2-2 ii libkf5ldap5abi1 [libkf5ldap5-20.08]
Bug#974860: kmail: When moving an email into a subfolder on KDE Plasma Wayland the context menu does not appear at the target subfolder
Hey,
The bug is not a Debian specific one, so it should be reported and fixed
upstream at KDE:
https://bugs.kde.org
Please also leave a comment here at this bugreport with the url of the
upstream bug, so we are able to track the upstream bug status. To do this
properly add a line to the mail with:
Control: Forwarded -1 {url}
at the beginning of your response, than BTS (Debian Bugtracker) will do its
magic.
hefee
--
On Sonntag, 15. November 2020 17:36:31 CET Silvério Santos wrote:
> Package: kmail
> Version: 4:20.08.2-4
> Severity: minor
>
> Dear Maintainer,
>
> On KDE Plasma Wayland: Drag and drop an email into a subfolder. A context
> menu appears to choose whether to move here, copy here or cancel. This
> context menu appears where the email was located before/where it was
> clicked to drag it into the target folder. This of course is misleading
> because of the expression "... here" twice in the options, as they do not
> match the place they are referring to.
> The menu should appear at the target folder instead, where the mouse button
> is released.
>
>
>
> -- System Information:
> Debian Release: bullseye/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
> 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:20.08.2-3+b1 ii kdepim-runtime
> 4:20.08.2-4 ii kio
> 5.74.0-2 ii libc6
>2.31-4 ii libgcc-s1
> 10.2.0-16 ii libgpgmepp6
> 1.14.0-1+b1 ii libkf5akonadiagentbase5 [libkf5akonadiagentbase5-20.08]
> 4:20.08.2-3+b1 ii libkf5akonadicontact5 [libkf5akonadicontact5-20.08]
> 4:20.08.2-3 ii libkf5akonadicore5abi2 [libkf5akonadicore5-20.08]
> 4:20.08.2-3+b1 ii libkf5akonadimime5 [libkf5akonadimime5-20.08]
> 4:20.08.2-2 ii libkf5akonadisearch-bin
>4:20.08.2-2 ii libkf5akonadisearch-plugins
> 4:20.08.2-2 ii libkf5akonadisearchdebug5
> [libkf5akonadisearchdebug5-20.08] 4:20.08.2-2 ii libkf5akonadisearchpim5
> [libkf5akonadisearchpim5-20.08] 4:20.08.2-2 ii
> libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-20.08] 4:20.08.2-3+b1
> ii libkf5bookmarks5 5.74.0-2
> ii libkf5calendarcore5abi2 5:5.74.0-2
> ii libkf5calendarutils5 [libkf5calendarutils5-20.08]
> 4:20.08.2-2 ii libkf5codecs5
> 5.74.0-2 ii libkf5completion5
> 5.74.0-2 ii libkf5configcore5
> 5.74.0-2 ii libkf5configgui5
> 5.74.0-2 ii libkf5configwidgets5
> 5.74.0-2 ii libkf5contacts5
> 5:5.74.0-2 ii libkf5coreaddons5
> 5.74.0-2 ii libkf5crash5
> 5.74.0-2 ii libkf5dbusaddons5
> 5.74.0-2 ii libkf5grantleetheme-plugins
> 20.08.2-2 ii libkf5gravatar5abi2 [libkf5gravatar5-20.08]
> 4:20.08.2-2 ii libkf5guiaddons5
> 5.74.0-3 ii libkf5i18n5
> 5.74.0-3 ii libkf5iconthemes5
> 5.74.0-2 ii libkf5identitymanagement5 [libkf5identitymanagement5-20.08]
> 20.08.2-2 ii libkf5itemmodels5
> 5.74.0-2 ii libkf5itemviews5
> 5.74.0-2 ii libkf5jobwidgets5
> 5.74.0-2 ii libkf5kcmutils5
> 5.74.0-2 ii libkf5kiocore5
> 5.74.0-2 ii libkf5kiofilewidgets5
> 5.74.0-2 ii libkf5kiogui5
> 5.74.0-2 ii libkf5kiowidgets5
> 5.74.0-2 ii libkf5kontactinterface5 [libkf5kontactinterface5-20.08]
> 20.08.2-2 ii libkf5ksieveui5 [libkf5ksieveui5-20.08]
> 4:20.08.2-2 ii libkf5ldap5abi1 [libkf5ldap5-20.08]
> 20.08.2-2 ii libkf5libkdepim5
Bug#974821: kmail: some attachments are not shown with setting header/standard in eMail window
Hey,
The bug is not a Debian specific one, so it should be reported and fixed
upstream at KDE:
https://bugs.kde.org
Please also leave a comment here at this bugreport with the url of the
upstream bug, so we are able to track the upstream bug status. To do this
properly add a line to the mail with:
Control: Forwarded -1 {url}
at the beginning of your response, than BTS (Debian Bugtracker) will do its
magic.
hefee
On Sonntag, 15. November 2020 09:50:09 CET Silvério Santos wrote:
> Package: kmail
> Version: 4:20.08.2-4
> Severity: normal
>
> Dear Maintainer,
>
> when view/header/standard is configured some attachments are not shown in
> the email window, so that there is no indication of an attachment there.
> Switching to view/header/decorative shows the attachments in the same email
> window's header section.
>
> Example code for not shown attachment with standard header ([UUID] is a
> placeholder):
> --Apple-Mail=_[UUID]
> Content-Disposition: inline;
> filename="filename.pdf"
> Content-Type: application/pdf;
> x-unix-mode=0644;
> name="filename.pdf"
> Content-Transfer-Encoding: base64
>
> [code]
>
> Example code for shown attachment with standard header:
> --multipart_alternative.123456789--
>
> --multipart_mixed.987654321
> Content-Type: application/pdf
> Content-Length: 42000
> Content-Disposition: attachment; filename="filename.pdf"
> Content-Transfer-Encoding: base64
>
> [code]
>
>
>
> -- System Information:
> Debian Release: bullseye/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
> 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:20.08.2-3+b1 ii kdepim-runtime
> 4:20.08.2-4 ii kio
> 5.74.0-2 ii libc6
>2.31-4 ii libgcc-s1
> 10.2.0-16 ii libgpgmepp6
> 1.14.0-1+b1 ii libkf5akonadiagentbase5 [libkf5akonadiagentbase5-20.08]
> 4:20.08.2-3+b1 ii libkf5akonadicontact5 [libkf5akonadicontact5-20.08]
> 4:20.08.2-3 ii libkf5akonadicore5abi2 [libkf5akonadicore5-20.08]
> 4:20.08.2-3+b1 ii libkf5akonadimime5 [libkf5akonadimime5-20.08]
> 4:20.08.2-2 ii libkf5akonadisearch-bin
>4:20.08.2-2 ii libkf5akonadisearch-plugins
> 4:20.08.2-2 ii libkf5akonadisearchdebug5
> [libkf5akonadisearchdebug5-20.08] 4:20.08.2-2 ii libkf5akonadisearchpim5
> [libkf5akonadisearchpim5-20.08] 4:20.08.2-2 ii
> libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-20.08] 4:20.08.2-3+b1
> ii libkf5bookmarks5 5.74.0-2
> ii libkf5calendarcore5abi2 5:5.74.0-2
> ii libkf5calendarutils5 [libkf5calendarutils5-20.08]
> 4:20.08.2-2 ii libkf5codecs5
> 5.74.0-2 ii libkf5completion5
> 5.74.0-2 ii libkf5configcore5
> 5.74.0-2 ii libkf5configgui5
> 5.74.0-2 ii libkf5configwidgets5
> 5.74.0-2 ii libkf5contacts5
> 5:5.74.0-2 ii libkf5coreaddons5
> 5.74.0-2 ii libkf5crash5
> 5.74.0-2 ii libkf5dbusaddons5
> 5.74.0-2 ii libkf5grantleetheme-plugins
> 20.08.2-2 ii libkf5gravatar5abi2 [libkf5gravatar5-20.08]
> 4:20.08.2-2 ii libkf5guiaddons5
> 5.74.0-3 ii libkf5i18n5
> 5.74.0-3 ii libkf5iconthemes5
> 5.74.0-2 ii libkf5identitymanagement5 [libkf5identitymanagement5-20.08]
> 20.08.2-2 ii libkf5itemmodels5
> 5.74.0-2 ii libkf5itemviews5
> 5.74.0-2 ii libkf5jobwidgets5
> 5.74.0-2 ii libkf5kcmutils5
> 5.74.0-2 ii libkf5kiocore5
> 5.74.0-2 ii libkf5kiofilewidgets5
> 5.74.0-2 ii libkf5kiogui5
Bug#973505: akregator: Feeds no longer update
control: tags -1 + moreinfo control: severity -1 normal Hey, > library /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so: > (/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.15' not found > (required by /lib/x86_64-linux-gnu/libQt5Network.so.5)) I cannot reproduce the issue you described. And from my side it seems, like you mixed packages, that are build against different qt versions. Can you verify that it is still an issue? Regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#970127: kmail: Kmail depends on libsasl2-modules to send out mails via SMTP
reassign 970127 kdepim-runtime 4:20.08.2-3 thanks signature.asc Description: This is a digitally signed message part.
Bug#972606: plasma-workspace FTFBS: cmake error / some missing dependency
Hey, > Sandro removed it (again) in 5.74.0-1 :-/ I'll fix it soon. sorry for that, I looked via git log and havn't seen your patch, sorry for that. > Sandro: when planning to remove dependencies from a -dev file, please > rebuild the reverse dependencies to check everything still works > (currently kdelibs4support has only 12 users in unstable). That is also a good thing to do. Now I also learned that kdelibs4support is the only one in Frameworks, that have dependencies at the dev package, that are not part of the build dependencies. I will surly remember that. hefee signature.asc Description: This is a digitally signed message part.
Bug#972226: kjots: FTBFS with KDEPIM 20.08
Package: kjots Version: 4:5.0.2-2 Severity: normal Tags: ftbfs Hey, kjots failed to build against KDEPIM 20.08: /<>/obj-x86_64-linux-gnu/src/kontact_plugin/kontact_kjotsplugin_autogen/EWIEGA46WW/../../../../../src/kontact_plugin/kjots_plugin.h:66:13: error: ‘ReadOnlyPart’ in namespace ‘KParts’ does not name a type 66 | KParts::ReadOnlyPart *createPart() Q_DECL_OVERRIDE; | ^~~~ there is alaready an patch upstream to fix this: https://invent.kde.org/pim/kjots/-/commit/bcf49fb95bee12bbc4bef0578285ad296deafcae You can build against new KDEPIM 20.08 with the repo: http://qt-kde-team.debian.net/ hefee
Bug#828021: extra-cmake-modules: please make the build reproducible (umask, toolchain)
control: Forwarded -1 https://invent.kde.org/frameworks/extra-cmake-modules/-/merge_requests/35 Hey, finally after some years I pushed the patch upstream (hopefully it gets accepted). hefee signature.asc Description: This is a digitally signed message part.
Bug#951388: [akonadi-backend-postgresql] apparmor profile unsuitable
Forwarded: https://invent.kde.org/pim/akonadi/-/merge_requests/32 Hey, I have pushed the needed changes to upstream. The AppArmor profile is living there. hefee -- On Samstag, 15. Februar 2020 21:08:15 CEST Bastien Roucariès wrote: > Package: akonadi-backend-postgresql > Version: 4:19.08.3-1 > Severity: grave > Justification: renders package unusable > Tags: patch > > Dear Maintainer, > > Please find the following update for apparmor > > Please apply > > Bastien signature.asc Description: This is a digitally signed message part.
Re: [pkg-apparmor] PostgreSQL AppArmor profiles
Hey,
> There are two unrelated things in this discussion:
thanks for clarification.
> a) the need to update the pstgresql_akonadi AppArmor profile when using
>the internal postgres service (= this mail)
>
> b) Sedat switched to using the system wide postgres (not relevant for
>the AppArmor profile, except that it of course avoids the profile for
>the internal postgres service)
>
> > (This in itself is not really supported by Akonadi; normally Akonadi
> > is taking care about starting and stopping the database itself). So
> > what is the advantage of starting/stopping postgres outside of
> > Akonadi?
>
> I use Akonadi with my system-wide MySQL, so let me answer from my POV:
> It avoids running another MySQL instance (I have a system-wide MySQL
> running anyway), and my _impression_ (no hard facts) is that it works a
> bit more stable than with the Akonadi-internal MySQL. I can only guess,
> but maybe the internal MySQL gets stopped the hard way on logout if the
> regular stop takes too long?
>
> Again: This is only my impression, I don't have hard facts.
I use the internal MYSQL and didn't need to tweak anything. Maybe you would
have to tweak the internal mysql settings for a better experience. The
settings of akonadi are very conservative. But that is a totally unrelated
topic.
>
> > > > BEFORE: profile postgresql_akonadi {
> > > > AFTER: profile postgresql_akonadi flags=(attach_disconnected) {
> > >
> > > Right, the flags=(attach_disconnected) addition is the correct
> > > fix.
> >
> > What does this flag do?
>
> The starting point was this message:
>
> [Thu Sep 3 15:27:34 2020] audit: type=1400 audit(1599139654.969:28):
> apparmor="DENIED" operation="file_mmap" info="Failed name lookup -
> disconnected path" error=-13 profile="postgresql_akonadi" name=""
> pid=2126 comm="postgres" requested_mask="wr" denied_mask="wr"
> fsuid=1000 ouid=1000
>
> As you can see, the message in this specific case is about name=""
>
> The simplified explanation is that with attach_disconnected, this will
> become name="/" - attach_disconnected prepends a / to paths that
> aren't connected to the root filesystem namespace.
Okay but what does name="/" do? why this helps? So far I understand the audit
message, it tries to start "postgres" without shipping the complete path. But
postgres command is never in normal path as this exists under /usr/lib/
postgresql/XX/bin/postgres so executing postgres fails anyway.
But maybe we move this discussion to a Merge request to upstream, that we can
than backport, so also others can learn:
https://invent.kde.org/pim/akonadi/-/merge_requests/29
> > Does this mean, that every postgres service I
> > start will be run under this profile?
>
> No.
>
> > Or can AppArmour distinguish
> > between the system wide postgresql@12-main.service and the akonadi
> > one (akonadi-dileks)?
>
> Yes, because the akonadi profile probably (at least I guess so, I don't
> use Debian and never looked at the Akonadi profile) has a rule saying
> /usr/bin/postgresql Cx -> postgresql_akonadi,
> which means "if akonadi executes postgres, use the postgresql_akonadi
> child profile".
>
> For the system-wide postgresql, the "if akonadi executes postgres"
> condition won't match ;-)
>
> > Because keep in mind the profile
> > postgresql_akonadi should only be added to this instance that is
> > connected to akonadi and not the other postgres clusters. The idea of
> > the profiles is that the non Akonadi instances of postgres and mysql
> > don't get any akonadi profile attached.
>
> Right, and this won't change with the added flag.
Okay thanks this helps already a lot.
hefee
signature.asc
Description: This is a digitally signed message part.
Re: [pkg-apparmor] PostgreSQL AppArmor profiles
Hey,
Christian is trying to replace the Akonadi internal postgres service with a
system wide service. Is that correct?
(This in itself is not really supported by Akonadi; normally Akonadi is taking
care about starting and stopping the database itself). So what is the
advantage of starting/stopping postgres outside of Akonadi?
> > BEFORE: profile postgresql_akonadi {
> > AFTER: profile postgresql_akonadi flags=(attach_disconnected) {
>
> Right, the flags=(attach_disconnected) addition is the correct fix.
What does this flag do? Does this mean, that every postgres service I start
will be run under this profile? Or can AppArmour distinguish between the system
wide postgresql@12-main.service and the akonadi one (akonadi-dileks)? Because
keep in mind the profile postgresql_akonadi should only be added to this
instance that is connected to akonadi and not the other postgres clusters. The
idea of the profiles is that the non Akonadi instances of postgres and mysql
don't get any akonadi profile attached.
hefee
signature.asc
Description: This is a digitally signed message part.
Re: [Nicholas D Steeves] Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now
Hey, > Also replying to debian-qt-kde, in case some team members are not > following debian-kde. this list is for bugreports only. If you want to reach the Maintainer team you need to use the pkg-kde-t...@alioth-lists.debian.net. hefee signature.asc Description: This is a digitally signed message part.
Bug#961647: akonadi: FTBFS on armel: missing -latomic
Hey, Whoo I'm quite impressed to have two different solutions that fast! Thank you both for proposing me solutions. You made my day! > The easy workaround is in debian/rules: > > ifneq (,$(filter $(DEB_HOST_ARCH), armel m68k mipsel powerpc sh4)) > export DEB_LDFLAGS_MAINT_APPEND = -Wl,--no-as-needed -latomic > -Wl,--as-needed endif thanks for this easy workaround! I implemented that one for now. > It might, but due to gcc defaulting to -Wl,--as-needed it wouldn't be an issue. There is also https://phabricator.kde.org/D16184 that only links libatomic if necessary. I will propose a proper patch upstream based on the patch you proposed. Maybe we integrate CheckAtomic into extra-cmake-modules. hefee signature.asc Description: This is a digitally signed message part.
Bug#961647: akonadi: FTBFS on armel: missing -latomic
Hey, > This is caused by a missing -latmoic. See also > https://buildd.debian.org/status/fetch.php?pkg=akonadi=armel=4%3A20 > .04.1-1=1590553675=0 thanks for this fast scan and also proposing a solution. But I have no example of how I need to modify cmake to end up having -latomic for armel being added. Do you know anything? I found one solution to add atomic everywhere, but this may be an overkill: https://github.com/mavlink/mavros/pull/790/files So far I see the libboost-atomic1.67-dev is already installed, that means I don't have to install anything additionally. So at least I don't have to modify build-depends. hefee signature.asc Description: This is a digitally signed message part.
Bug#841762: kdeconnect: More information about kedconnectd crashing
Hey, > I've been quite surprised to find that this bug report was first filled > in 2016 because I've only began experiencing it for about a week. Using > testing I waited for a week to see if a fix would come. Now's the time > for the BR. well this is a bug, that needs to be solved by upstream, so please file a bugreport at https://bugs.kde.org > It's also sad that we can't strace which system call causes the crash > nor use gdb (even without debugging information). > > --8<--8<--8<--8<--8<--8<--8<--8<-- > ~$ LC_ALL=C strace /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd > strace: test_ptrace_get_syscall_info: PTRACE_TRACEME: Operation not > permitted strace: ptrace(PTRACE_TRACEME, ...): Operation not permitted > +++ exited with 1 +++ > ~$ gdb /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd > [...] > (No debugging symbols found in > /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd) (gdb) run > Starting program: /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd > warning: Could not trace the inferior process. > warning: ptrace: Operation not permitted > During startup program exited with code 127. > --8<--8<--8<--8<--8<--8<--8<--8<-- Your user needs to have the ptrace permission in order to use gdb successfully [1]. And you need to install the symbols files: kdeconnect-dbgsym from the repo: deb http://debug.mirrors.debian.org/debian-debug/ unstable-debug main hefee [1] https://wiki.ubuntu.com/SecurityTeam/Roadmap/ KernelHardening#ptrace_Protection signature.asc Description: This is a digitally signed message part.
Bug#961558: libkf5xmlgui5: removes KGestureMap, which breaks older kdebugdialog5 (package: libkf5kdelibs4support5-bin)
Hey, > It's nice you uploaded a new version, but you picked 5.59 as the breaks > version, while 5.62 is surely still affected. nrgh, that was a typo. hefee signature.asc Description: This is a digitally signed message part.
Bug#961558: libkf5xmlgui5: removes KGestureMap, which breaks older kdebugdialog5 (package: libkf5kdelibs4support5-bin)
Hey Jiri, please do report such an issue on the package, that breaks and not at the source of the problem, that would gives us automatically the version of libkf5kdelibs4support5-bin. If not always make sure that both versions are included in the bugreport. I expect, that you use the version still on unstable. as the version on experimental runs fine. hefee signature.asc Description: This is a digitally signed message part.
Re: kcalcore_19.08.3+really5.69.0-1~_source.changes ACCEPTED into experimental
Hey, you may wonder, what I have done here. As kcalcore is waiting in the NEW queue because of the new doc package I sneaked a version into experimental to test kdepim 20.04 and prepare the transition for kcalcore. As a workaround I also had to repack the orig.tar.xz to have a different hash value, because dak refuses to use orig.tar.xz that are waiting in the NEW queue and checking this by hash and not by filename. The version number, that will hit sid will still be epoch 5, this upload is only a workaround. hefee -- On Montag, 4. Mai 2020 02:03:27 CEST Debian FTP Masters wrote: > kcalcore (4:19.08.3+really5.69.0-1~) experimental; urgency=medium > . >* Disable to create the libkf5calendarcore-doc package, to have a version > in experimental to build against. >* Manipulate the epoch and upstream version, so it get accepted by Debian > archive. signature.asc Description: This is a digitally signed message part.
Bug#946365: kmail becomes unresponsive with active preview pane on wayland-plasma
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=414955
Thanks for forwarding to upstream. But you have to send this mail to the bug
report to the 946...@bugs.debian.org address not to me - I'm not the BTS ;D
Forwarding your mail to BTS.
hefee
On Sonntag, 8. Dezember 2019 17:06:49 CET Silvério Santos wrote:
> Control: Forwarded -1 https://bugs.kde.org/show_bug.cgi?id=414955[1]
> Done.
>
> Am Sonntag, 8. Dezember 2019, 12:08:46 CET schrieben Sie:
> > Hey,
> >
> > Currently a next KDE PIM version is hitting testing, so please give the
> > new
> > version (19.08.3) a try and if the bug is not fixed report it upstream:
> > https://bugs.kde.org
> >
> > Please also leave a comment here at this bugreport with the upstream bug,
> > so we are able to track the upstream bug status. To do this properly add
> > a line with:
> > Control: Forwarded -1 {url}
> >
> > at the beginning of your response, than BTS (Debian Bugtracker) will do
> > its
> > magic.
> >
> > hefee
>
>
> [1] https://bugs.kde.org/show_bug.cgi?id=414955
signature.asc
Description: This is a digitally signed message part.
Bug#946365: kmail becomes unresponsive with active preview pane on wayland-plasma
Control: reassign -1 libkf5webengineviewer5abi1 4:18.08.3-5
Control: affects -1 kmail
Hey,
Currently a next KDE PIM version is hitting testing, so please give the new
version (19.08.3) a try and if the bug is not fixed report it upstream:
https://bugs.kde.org
Please also leave a comment here at this bugreport with the upstream bug, so
we are able to track the upstream bug status. To do this properly add a line
with:
Control: Forwarded -1 {url}
at the beginning of your response, than BTS (Debian Bugtracker) will do its
magic.
hefee
--
On Sonntag, 8. Dezember 2019 00:05:25 CET Silvério Santos wrote:
> Package: kmail
> Version: 4:18.08.3-4
> Severity: important
>
> Dear Maintainer,
>
> Started kmail on wayland-plasma with active preview pane. The preview stays
> black at the beginning. When e.g. hovering with the mouse over the preview,
> clicking on a different email or changing the folder the whole kmail
> software stops reacting and the title bar shows an unresponsive
> notification. No crash notification.
>
> When not interacting with the enabled preview pane the software stays
> responsive, even the settings can be reached to disable preview, which makes
> kmail work fine. EMail content can then be viewed in separately opened
> windows by doubleclicking them. Disabling HTML preference does not help.
>
> This problem does not happen with the preview pane disabled and in either
> configuration on X-Window.
>
> Running Debian testing, KMail 18.08.3-4
>
>
>
>
> -- System Information:
> Debian Release: bullseye/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
> (charmap=UTF-8) 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:18.08.3-11 ii kdepim-runtime
>4:18.08.3-6 ii kio
> 5.62.1-2+b1 ii libc6
>2.29-3 ii libgcc1
> 1:9.2.1-21 ii libgpgmepp6
> 1.13.1-1 ii libkf5akonadiagentbase5 [libkf5akonadiagentbase5-18.08]
> 4:18.08.3-11 ii libkf5akonadicontact5 [libkf5akonadicontact5-18.08]
>4:18.08.3-4 ii libkf5akonadicore5abi2 [libkf5akonadicore5-18.08]
> 4:18.08.3-11 ii libkf5akonadimime5 [libkf5akonadimime5-18.08]
> 4:18.08.3-3 ii libkf5akonadisearch-bin
> 4:18.08.3-3 ii libkf5akonadisearch-plugins
> 4:18.08.3-3 ii libkf5akonadisearchdebug5
> [libkf5akonadisearchdebug5-18.08] 4:18.08.3-3 ii libkf5akonadisearchpim5
> [libkf5akonadisearchpim5-18.08] 4:18.08.3-3 ii
> libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-18.08] 4:18.08.3-11
> ii libkf5bookmarks5
> 5.62.0-1+b1 ii libkf5calendarcore5abi2 [libkf5calendarcore5-18.08]
> 4:18.08.3-3 ii libkf5calendarutils5 [libkf5calendarutils5-18.08]
> 4:18.08.3-4 ii libkf5codecs5
> 5.62.0-1 ii libkf5completion5
> 5.62.0-1+b1 ii libkf5configcore5
>5.62.0-1+b1 ii libkf5configgui5
> 5.62.0-1+b1 ii libkf5configwidgets5
>5.62.0-1+b1 ii libkf5contacts5 [libkf5contacts5-18.08]
> 4:18.08.3-4 ii libkf5coreaddons5
>5.62.0-1 ii libkf5crash5
> 5.62.0-1+b1 ii libkf5dbusaddons5
> 5.62.0-1 ii libkf5followupreminder5
> [libkf5followupreminder5-18.08] 4:18.08.3-4 ii
> libkf5grantleetheme-plugins 18.08.3-3 ii
> libkf5gravatar5abi2 [libkf5gravatar5-18.08] 4:18.08.3-3
> ii libkf5guiaddons5 5.62.0-2
> ii libkf5i18n5 5.62.0-1
> ii libkf5iconthemes5
> 5.62.0-1+b1 ii libkf5identitymanagement5 [libkf5identitymanagement5-18.08]
> 18.08.3-4 ii libkf5itemmodels5
> 5.62.0-1 ii libkf5itemviews5
> 5.62.0-1+b1 ii libkf5jobwidgets5
>5.62.0-1+b1 ii libkf5kcmutils5
> 5.62.0-1+b1 ii
Bug#946141: [akonadi-backend-sqlite] Failed to commit transaction for database update
Hey, so youupgrading Akonadi, what version you had before? To use akonadiserver directly is not recommended. Please use akonadictl and enable debugging via .config/QtProject/qtlogging.ini. And one line is not in English: > org.kde.pim.akonadiserver: Creating socket directory with name "" > failed: Выполнено can you please translate this, or un with LANG=C [cmd], so everthing is in English. hefee -- > Akonadi failed to start: > > $ akonadiserver --start-without-control --verbose > org.kde.pim.akonadiserver: Starting up the Akonadi Server... > QSqlDatabasePrivate::addDatabase: duplicate connection name > 'initConnection', old connection removed. > org.kde.pim.akonadiserver: sqlite version is "3.30.1" > org.kde.pim.akonadiserver: sqlite journal mode is "wal" > org.kde.pim.akonadiprivate: StandardDirs::saveDir: failed to create > directory ' "/run/user/1000/akonadi" ' > QDir::mkpath: Empty or null file name > org.kde.pim.akonadiserver: Creating socket directory with name "" > failed: Выполнено > org.kde.pim.akonadiserver: Could not create socket directory for Akonadi. > org.kde.pim.akonadiserver: Database > "/home/alexs/.local/share/akonadi/akonadi.db" opened using driver "QSQLITE3" > org.kde.pim.akonadiserver: Running DB initializer > org.kde.pim.akonadiserver: checking table "SchemaVersionTable" > org.kde.pim.akonadiserver: checking table "ResourceTable" > org.kde.pim.akonadiserver: checking table "CollectionTable" > org.kde.pim.akonadiserver: checking table "MimeTypeTable" > org.kde.pim.akonadiserver: checking table "PimItemTable" > org.kde.pim.akonadiserver: checking table "FlagTable" > org.kde.pim.akonadiserver: checking table "PartTypeTable" > org.kde.pim.akonadiserver: checking table "PartTable" > org.kde.pim.akonadiserver: checking table "CollectionAttributeTable" > org.kde.pim.akonadiserver: checking table "TagTypeTable" > org.kde.pim.akonadiserver: checking table "TagTable" > org.kde.pim.akonadiserver: checking table "TagAttributeTable" > org.kde.pim.akonadiserver: checking table > "TagRemoteIdResourceRelationTable" > org.kde.pim.akonadiserver: checking table "RelationTypeTable" > org.kde.pim.akonadiserver: checking table "RelationTable" > org.kde.pim.akonadiserver: checking table "PimItemFlagRelation" > org.kde.pim.akonadiserver: checking table "PimItemTagRelation" > org.kde.pim.akonadiserver: checking table "CollectionMimeTypeRelation" > org.kde.pim.akonadiserver: checking table "CollectionPimItemRelation" > org.kde.pim.akonadiserver: DB initializer done > org.kde.pim.akonadiserver: skipping update 2 > org.kde.pim.akonadiserver: skipping update 3 > org.kde.pim.akonadiserver: skipping update 4 > org.kde.pim.akonadiserver: skipping update 8 > org.kde.pim.akonadiserver: skipping update 10 > org.kde.pim.akonadiserver: skipping update 12 > org.kde.pim.akonadiserver: skipping update 13 > org.kde.pim.akonadiserver: skipping update 14 > org.kde.pim.akonadiserver: skipping update 15 > org.kde.pim.akonadiserver: skipping update 16 > org.kde.pim.akonadiserver: skipping update 17 > org.kde.pim.akonadiserver: skipping update 18 > org.kde.pim.akonadiserver: skipping update 19 > org.kde.pim.akonadiserver: skipping update 20 > org.kde.pim.akonadiserver: skipping update 21 > org.kde.pim.akonadiserver: skipping update 22 > org.kde.pim.akonadiserver: skipping update 23 > org.kde.pim.akonadiserver: skipping update 24 > org.kde.pim.akonadiserver: skipping update 25 > org.kde.pim.akonadiserver: skipping update 26 > org.kde.pim.akonadiserver: skipping update 28 > org.kde.pim.akonadiserver: skipping update 30 > org.kde.pim.akonadiserver: skipping update 31 > org.kde.pim.akonadiserver: skipping update 33 > org.kde.pim.akonadiserver: skipping update 35 > org.kde.pim.akonadiserver: DbUpdater: update to version: 36 mandatory: true > org.kde.pim.akonadiserver: Starting database update to version 36 > org.kde.pim.akonadiserver: Updating foreign keys in table "CollectionTable" > org.kde.pim.akonadiserver: Creating table CollectionTable_new with > foreign keys > org.kde.pim.akonadiserver: Copying values from CollectionTable to > CollectionTable_new (this may take a very long of time...) > org.kde.pim.akonadiserver: SQL error when updating table CollectionTable > org.kde.pim.akonadiserver: Query: CREATE TABLE CollectionTable_new (id > INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, remoteId TEXT, > remoteRevision TEXT, name TEXT NOT NULL, parentId BIGINT, resourceId > BIGINT NOT NULL, enabled BOOL NOT NULL DEFAULT 1, syncPref TINYINT > DEFAULT 2, displayPref TINYINT DEFAULT 2, indexPref TINYINT DEFAULT 2, > cachePolicyInherit BOOL NOT NULL DEFAULT 1, cachePolicyCheckInterval > INTEGER NOT NULL DEFAULT -1, cachePolicyCacheTimeout INTEGER NOT NULL > DEFAULT -1, cachePolicySyncOnDemand BOOL NOT NULL DEFAULT 0, > cachePolicyLocalParts TEXT, queryString TEXT, queryAttributes TEXT, > queryCollections TEXT, isVirtual BOOL DEFAULT 0, CONSTRAINT > CollectionTable_newparentId_Collectionid_fk FOREIGN
Bug#946199: akonadi-backend-postgresql: akonadictl fails to start with postgresql backend
control: severity -1 important Hey, I'm lowering the severity, as this package is not unfit for testing. It was used for serveral moths in experimental, where people used also Postgresql backend without any issues. hefee -- On Freitag, 6. Dezember 2019 12:57:03 CET Diederik de Haas wrote: > 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#946199: akonadi-backend-postgresql: akonadictl fails to start with postgresql backend
Hey, do you have apparmor enabled? Maybe the Apparmor profile does not match anymore. Can you give it a try with aa-disable postgresql_akonadi? hefee -- >* What led up to the situation? >akonadi-backend-postgresql upgrade > >* What exactly did you do (or not do) that was effective (or > ineffective)? > >restart akonadictl, withou any effect, restart postgresql, on different >system with version 11 and 12. Postgresql connection is still available > >* What was the outcome of this action? >None >* What outcome did you expect instead? >Akonadi working > > > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, > 'stable-updates'), (500, 'stable-debug'), (500, 'buster-fasttrack'), (500, > 'unstable'), (500, 'testing'), (500, 'stable'), (100, 'buster-backports') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr > (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages akonadi-backend-postgresql depends on: > ii libqt5sql5-psql 5.12.5+dfsg-2 > > Versions of packages akonadi-backend-postgresql recommends: > ii akonadi-server 4:19.08.3-1 > ii postgresql 12+210 > > akonadi-backend-postgresql suggests no packages. > > -- no debconf information signature.asc Description: This is a digitally signed message part.
Bug#945161: accountwizard: Broken dependencies (KLineEdit)
Hey, I can't reproduce your issue, so I need your input. First can try to replace KLineEdit with QLineEdit the file (you need root permission to do that): /usr/share/akonadi/accountwizard/kolab/kolabwizard.ui Does this already fix the issue? Is kdepim-runtime installed and/or libkf5completion5? hefee -- > The accountwizard tries to instantiate widgets that are not installed when I > try to setup a Kolab client, so this seems to be a dependency issue. The > output from the program is: > > $ accountwizard > org.kde.knewstuff.core: Using a deprecated location for the knsrc file > "accountwizard.knsrc" - please contact the author of the software which > provides th "QFormBuilder was unable to create a widget of the class > 'KLineEdit'." "Empty widget item in QFormLayout 'formLayout'." > "QFormBuilder was unable to create a widget of the class 'KLineEdit'." > "Empty widget item in QFormLayout 'formLayout'." > "QFormBuilder was unable to create a custom widget of the class > 'KPasswordLineEdit'; defaulting to base class 'QWidget'." Kross: "Error > error=TypeError: Result of expression 'page.widget().nameEdit' [undefined] > is not an object. lineno=27 trace=\n() at /usr/share/akona > > This means that I cannot enter the name, nor the password, due to the > widgets not being properly instantiated. > > > -- System Information: > Debian Release: bullseye/sid > APT prefers testing > APT policy: (600, 'testing'), (500, 'unstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores) > Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set > LC_ALL to default locale: No such file or directory UTF-8), > LANGUAGE=en_US:en (charmap=locale: Cannot set LC_ALL to default locale: No > such file or directory UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages accountwizard depends on: > ii kio 5.62.1-2 > ii libc6 2.29-3 > ii libgcc1 1:9.2.1-19 > ii libgpgmepp6 1.13.1-1 > ii libkf5akonadicore5abi2 [libkf5akonadicore5-18.08] > 4:18.08.3-11 ii libkf5akonadimime5 [libkf5akonadimime5-18.08] >4:18.08.3-3 ii libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-18.08] > 4:18.08.3-11 ii libkf5codecs5 > 5.62.0-1 ii libkf5configcore5 >5.62.0-1 ii libkf5coreaddons5 > 5.62.0-1 ii libkf5crash5 > 5.62.0-1 ii libkf5dbusaddons5 > 5.62.0-1 ii libkf5i18n5 >5.62.0-1 ii libkf5identitymanagement5 [libkf5identitymanagement5-18.08] > 18.08.3-4 ii libkf5itemviews5 > 5.62.0-1 ii libkf5kcmutils5 > 5.62.0-1 ii libkf5kiocore5 > 5.62.1-2 ii libkf5krosscore5 > 5.62.0-1 ii libkf5ldap5abi1 [libkf5ldap5-18.08] > 18.08.3-3 ii libkf5libkdepim5 [libkf5libkdepim5-18.08] > 4:18.08.3-4 ii libkf5libkleo5 [libkf5libkleo5-18.08] > 4:18.08.3-4 ii libkf5mailtransport5 [libkf5mailtransport5-18.08] > 18.08.3-4 ii libkf5mailtransportakonadi5 > [libkf5mailtransportakonadi5-18. 18.08.3-4 ii libkf5mime5abi1 > [libkf5mime5-18.08] 18.08.3-3 ii > libkf5newstuffcore5 5.62.0-1 ii > libkf5notifications5 5.62.0-1 ii > libkf5pimcommon5abi2 [libkf5pimcommon5-18.08] 4:18.08.3-4 > ii libkf5wallet-bin 5.62.0-1 > ii libkf5wallet5 5.62.0-1 > ii libkf5widgetsaddons5 5.62.0-1 > ii libkf5xmlgui5 > 5.62.0-1+b1 ii libqgpgme7 > 1.13.1-1 ii libqt5core5a > 5.12.5+dfsg-2 ii libqt5dbus5 > 5.12.5+dfsg-2 ii libqt5gui5 > 5.12.5+dfsg-2 ii libqt5widgets5 > 5.12.5+dfsg-2 ii libqt5xml5 > 5.12.5+dfsg-2 ii libstdc++6
Re: Calligra and Akonadi
Hey pino,
> > Why this is not built and shipped and still we have the dependency?
>
> I do not see any akonadi dependency in the binary packages, can you
> please explain exactly what you see?
what I mean is, if it is only checked at buildtime but no binary package
depend on it, why it was added to Build-Depends in first place?
Why we do not ship the calligra_semanticitem_{contact,event} plugins?
> This is because the tracker for the transition is partially wrong:
> - it considers "affected" all the sources that only build-depend on PIM
> packages: while this is generally correct, it ought to check both the
> actual bad _and_ good runtime dependencies instead
You are totally right, the ben file is not that exact that it could be. But
first it is one of my first transition that I triggered, so I'm not that
familiar with the ben syntax.
> - the "good" check seems correctly checking for the "new library names"
> - the "bad" check is basically "everything that does not depend on
> depend on the new names"... which is wrong -- it ought to explicitly
> check for the _old_ names instead
the bad state is the hard one to describe.
bad state:
a package depend on libfoo5
good state:
a package depend on libfoo5 and libfoo-18.08
> - calligra is considered "bad"
> - libkf5sieve, kf5-messagelib, kmail, libkf5mailcommon, and kmail are
> considered "bad" in all the architectures where they are not actually
> built
> - maybe (although I'm not sure about this) also all the "?!" states
>
> Please fix the ben file for this transition, so its status can be
> checked properly.
Well the next kdepim transition is easier as bad is libfoo-18.08 and good is
libfoo-19.08.
hefee
signature.asc
Description: This is a digitally signed message part.
Calligra and Akonadi
Hey pino,
thanks for your last update of calligra! That at least makes it build again
*yeah* But for me it seems like, the whole Akonadi dependency isn't used at
all. So far my digging into calligra code:
Akoandi and CalCore, Contacts is only used for plugins/semanticitems/
{contact,event} but as far I scanned though the build log these two plugins
are not built at all. I only can see the
calligra_semanticitem_{contact,event}.mo but those files are explitly deleted
with the comment
"# Remove translations of stuff not shipped"
Why this is not built and shipped and still we have the dependency?
hefee
signature.asc
Description: This is a digitally signed message part.
Bug#944853: calligra: FTBFS with Qt 5.12
Source: calligra Version: 1:3.1.0+dfsg-5 Severity: normal Hey, calligra can't be build anmore within the sid enviornment. It fails with: /<>/sheets/plugins/calendar/CalendarToolWidget.cpp:47:39: error: incomplete type ‘QDate’ used in nested name specifier 47 | QDate first_day_in_month = QDate::currentDate(); see https://buildd.debian.org/status/fetch.php?pkg=calligra=amd64=1%3A3.1.0%2Bdfsg-5%2Bb2=1573859614=0 hefee -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#943760: akregator: Cannot copy text from akregator
Control: reassign -1 qtwebengine-opensource-src 5.11.3+dfsg-2 Control: severity -1 normal Control: affects -1 akregator Hey, I can't reproduce this. And this sound not really like an big issue, that's why I lowered the severity to normal. I expect, that this is mostly an issue within QtWebEngine, as akregator only using that for the internal web browser. What Desktop Environment you are using? I'm using KDE Plasma Desktop. Do you also have issues to copy text within other applications like kmail? hefee -- On Dienstag, 29. Oktober 2019 13:39:39 CET Leos Pohl wrote: > Package: akregator > Version: 4:18.08.3-2 > Severity: important > > Dear Maintainer, > When i try to copy selected text inside akregator, the text does > not get copied. I can use either ctrl+c or right-click mouse and click > copy. Then I try to paste it to e.g. a web browser, the clipboard is > either empty or its content is from some previous copy action in other > program. > > > -- System Information: > Debian Release: 10.1 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, > 'stable') Architecture: amd64 (x86_64) > > Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= > (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages akregator depends on: > ii kinit5.54.0-1 > ii kio 5.54.1-1 > ii libc62.28-10 > ii libgcc1 1:8.3.0-6 > ii libkf5codecs55.54.0-1 > ii libkf5completion55.54.0-1 > ii libkf5configcore55.54.0-1+deb10u1 > ii libkf5configgui5 5.54.0-1+deb10u1 > ii libkf5configwidgets5 5.54.0-1 > ii libkf5coreaddons55.54.0-1 > ii libkf5crash5 5.54.0-1 > ii libkf5grantleetheme-plugins 18.08.3-1 > ii libkf5grantleetheme5 18.08.3-1 > ii libkf5i18n5 5.54.0-1 > ii libkf5iconthemes55.54.0-1 > ii libkf5jobwidgets55.54.0-1 > ii libkf5kcmutils5 5.54.0-1 > ii libkf5kiocore5 5.54.1-1 > ii libkf5kiogui55.54.1-1 > ii libkf5kiowidgets55.54.1-1 > ii libkf5kontactinterface5 18.08.3-1 > ii libkf5libkdepim-plugins 4:18.08.3-2 > ii libkf5libkdepim5 4:18.08.3-2 > ii libkf5messageviewer5abi1 4:18.08.3-2 > ii libkf5mimetreeparser5abi14:18.08.3-2 > ii libkf5notifications5 5.54.0-1 > ii libkf5notifyconfig5 5.54.0-1 > ii libkf5parts5 5.54.0-1 > ii libkf5pimcommon5abi2 4:18.08.3-2 > ii libkf5pimtextedit5abi2 18.08.3-1 > ii libkf5service-bin5.54.0-1 > ii libkf5service5 5.54.0-1 > ii libkf5syndication5abi1 18.08.3-1 > ii libkf5textwidgets5 5.54.0-1 > ii libkf5webengineviewer5abi1 4:18.08.3-2 > ii libkf5widgetsaddons5 5.54.0-1 > ii libkf5xmlgui55.54.0-1 > ii libqt5core5a 5.11.3+dfsg1-1 > ii libqt5dbus5 5.11.3+dfsg1-1 > ii libqt5gui5 5.11.3+dfsg1-1 > ii libqt5network5 5.11.3+dfsg1-1 > ii libqt5printsupport5 5.11.3+dfsg1-1 > ii libqt5webenginecore5 5.11.3+dfsg-2+b1 > ii libqt5webenginewidgets5 5.11.3+dfsg-2+b1 > ii libqt5widgets5 5.11.3+dfsg1-1 > ii libqt5xml5 5.11.3+dfsg1-1 > ii libstdc++6 8.3.0-6 > > akregator recommends no packages. > > akregator suggests no packages. > > -- no debconf information signature.asc Description: This is a digitally signed message part.
Bug#886428: Crashes on nouveau with mesa 17.3.1
Control: reassign -1 libkf5webengineviewer5abi1 4:18.08.3-2 Control: affects -1 kmail Hey, I think, that the issue is QtWebEngine and not kmail in itself. That's why I reassign to QtWebEngine. Russell Coker using a little bit different workaround to solve this issue: https://etbe.coker.com.au/2019/11/03/kmail-crashing-libgl/ Can someone reproduce the issue with testing or unstable, as there is Qt 5.12 and still the same kmail version than in stable? Regards, hefee -- On Sonntag, 3. November 2019 10:26:28 CET Dmitriy Istselemov wrote: > Package: kmail > Version: 4:18.08.3-1 > Followup-For: Bug #886428 > > Dear Maintainer, > The problem still exist. The workaround with setting the environment > QT_XCB_FORCE_SOFTWARE_OPENGL=1 works for me. > > Here is what is found in dmesg: > [ 71.515660] nouveau :01:00.0: Xorg[1012]: Unknown handle 0x005a > [ 71.515664] nouveau :01:00.0: Xorg[1012]: validate_init > [ 71.515666] nouveau :01:00.0: Xorg[1012]: validate: -2 > > And here is the output from the terminal: > > geser@WORKSTATION-Deb ~ $ kmail > No text-to-speech plug-ins were found. > qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 2949, > resource id: 10485826, major code: 130 (Unknown), minor code: 3 > qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 2961, > resource id: 10485826, major code: 130 (Unknown), minor code: 3 > qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 2975, > resource id: 10485826, major code: 130 (Unknown), minor code: 3 > qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 2991, > resource id: 10485826, major code: 130 (Unknown), minor code: 3 > qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 5764, > resource id: 10485826, major code: 130 (Unknown), minor code: 3 > qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 5784, > resource id: 10485826, major code: 130 (Unknown), minor code: 3 > qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 5788, > resource id: 10485826, major code: 130 (Unknown), minor code: 3 > *** KMail got signal 11 (Exiting) > *** Dead letters dumped. > /tmp/messageviewer_ByYTXj.index.2 was removed . > /tmp/messageviewer_oJnWHg.index.2 was removed . > nouveau: kernel rejected pushbuf: Неправильный дескриптор файла > nouveau: ch13: krec 0 pushes 1 bufs 10 relocs 0 > nouveau: ch13: buf 0002 0004 0004 > nouveau: ch13: buf 0001 0016 0002 0002 > nouveau: ch13: buf 0002 0014 0002 0002 > nouveau: ch13: buf 0003 0007 0002 0002 > nouveau: ch13: buf 0004 000a 0002 0002 > nouveau: ch13: buf 0005 000b 0002 0002 > nouveau: ch13: buf 0006 0008 0002 0002 > nouveau: ch13: buf 0007 0006 0004 0004 > nouveau: ch13: buf 0008 0015 0002 0002 > nouveau: ch13: buf 0009 000f 0002 0002 > nouveau: ch13: psh 039aec 03a738 > nouveau:0x0004721c > nouveau:0x0fac6881 > nouveau:0x00086ff4 > nouveau:0x0780 > nouveau:0x0416 > nouveau:0x00146200 > nouveau:0x > nouveau:0x20ec > nouveau:0x00e6 > nouveau:0x0040 > nouveau:0x > nouveau:0x00087240 > nouveau:0x0780 > nouveau:0x0416 > nouveau:0x00047224 > nouveau:0x0001 > nouveau:0x00047538 > nouveau:0x > nouveau:0x000475d0 > nouveau:0x > nouveau:0x00086c00 > nouveau:0x0780 > nouveau:0x0416 > nouveau:0x00086e04 > nouveau:0x0780 > nouveau:0x0416 > nouveau:0x00086e14 > nouveau:0x > nouveau:0x > nouveau:0x00086e24 > nouveau:0x > nouveau:0x > nouveau:0x00086e34 > nouveau:0x > nouveau:0x > nouveau:0x00086e44 > nouveau:0x > nouveau:0x > nouveau:0x00086e54 > nouveau:0x > nouveau:0x > nouveau:0x00086e64 > nouveau:0x > nouveau:0x > nouveau:0x00086e74 > nouveau:0x > nouveau:0x > nouveau:0x00086e84 > nouveau:0x > nouveau:0x > nouveau:0x00086e94 > nouveau:0x > nouveau:0x > nouveau:0x00086ea4 > nouveau:0x > nouveau:0x > nouveau:0x00086eb4 > nouveau:0x > nouveau:0x > nouveau:0x00086ec4 > nouveau:0x > nouveau:0x > nouveau:0x00086ed4 > nouveau:0x > nouveau:0x > nouveau:0x00086ee4 >
KSyndication to Sid
Hey Maxy, I tested now successfully, the syndication version in experimental ( for Akregator). The only change I want to happen before we publish it for sid is: to rename the lib to remove this abi1, that will trigger a transition. https://salsa.debian.org/qt-kde-team/kde/syndication/merge_requests/2 hefee signature.asc Description: This is a digitally signed message part.
Bug#941120: akonadi-backend-postgresql: fails to stop postgresql 11
Hey, thanks for your reply. > I am not sure how many Debian users use stable Akonadi with PostgreSQL > and PostgreSQL even appears to pick up the running processes after a > subsequent "akonadictl start". Considering all this, the only annoyance > and confusion is that some PostgreSQL processes keep lingering around. > Some users may be confused about this. > > Okay, all in all, not all that convincing arguments for stable. I just > thought if you do all the other fixes, you could put this one in as well. > I considered it to be low risk. well the prepared version for stable got already accepted, so there is no open end. All in all it seems for me like you say, it is just annoying. I fixed it for debian/buster branch already, but let's see if we need to bundle it with other fixes. > As the fix is in Akonadi 19.04, you may consider to close the bug right > away or close it when uploading Akonadi 19.08 or newer packages. Please do not close the bug, as it is not fixed! this should be done if 19.08+ packages enters Debian. hefee signature.asc Description: This is a digitally signed message part.
Bug#942415: transition: meta-kde
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hey, KDEPIM doesn't garantee ABI stability within there libraries only for one release. Our current system is to bump the ABI, when KDEPIM break their ABI. But this has the downside, that we mix different library versions in testing while a new version is populating to testing and doesn't make our users happy. That's why we want to switch from a symbols based approach to a approach, where we use virtual packages to bundle KDEPIM as one product. That should also help britney to move KDEPIM only to testing if everything is ready to move to testing. I prepared the 57 source package of KDEPIM in experimental (38 library packages and 19 leaf packages). Additionally to those packages, there are 10 "external" packages, that are not part of KDEPIM, but needs to be recompiled, to have dependencies against those virtual packages. From my point of view this needs a transition. I'm not sure, what ben rules you want, I can create ben rules for all 38 packages, but as the 57 packages are get a new upload anyways, those get recompiled anyways. So I decided to start with those 18 packages, that affects by the external packages, those are: blogilo (broken in sid anyways / upstream is dead) calligra calligraplan kio-gdrive kjots kmymoney kraft zanshin Ben files title = "akonadicalendar"; is_affected = .build-depends ~ /libkf5akonadicalendar-dev/; is_good = .depends ~ /libkf5akonadicalendar5-18.08/; is_bad = !.depends ~ /libkf5akonadicalendar5-18.08/; title = "kldap"; is_affected = .build-depends ~ /libkf5ldap-dev/; is_good = .depends ~ /libkf5ldap5-18.08/; is_bad = !.depends ~ /libkf5ldap5-18.08/; title = "akonadi"; is_affected = .build-depends ~ /libkf5akonadi-dev|libkf5akonadiserver-dev/; is_good = .depends ~ /libkf5akonadiagentbase5-18.08|libkf5akonadicore5-18.08|libkf5akonadiprivate5-18.08|libkf5akonadiwidgets5-18.08|libkf5akonadixml5-18.08/; is_bad = !.depends ~ /libkf5akonadiagentbase5-18.08|libkf5akonadicore5-18.08|libkf5akonadiprivate5-18.08|libkf5akonadiwidgets5-18.08|libkf5akonadixml5-18.08/; title = "akonadisearch"; is_affected = .build-depends ~ /libkf5akonadisearch-dev/; is_good = .depends ~ /libkf5akonadisearchcore5-18.08|libkf5akonadisearchdebug5-18.08|libkf5akonadisearchpim5-18.08|libkf5akonadisearchxapian5-18.08/; is_bad = !.depends ~ /libkf5akonadisearchcore5-18.08|libkf5akonadisearchdebug5-18.08|libkf5akonadisearchpim5-18.08|libkf5akonadisearchxapian5-18.08/; title = "messagelib"; is_affected = .build-depends ~ /libkf5messagecomposer-dev|libkf5messagecore-dev|libkf5messagelist-dev|libkf5messageviewer-dev|libkf5mimetreeparser-dev|libkf5templateparser-dev|libkf5webengineviewer-d ev/; is_good = .depends ~ /libkf5messagecomposer5-18.08|libkf5messagecore5-18.08|libkf5messagelist5-18.08|libkf5messageviewer5-18.08|libkf5mimetreeparser5-18.08|libkf5templateparser5-18.08|libkf5webengine viewer5-18.08/; is_bad = !.depends ~ /libkf5messagecomposer5-18.08|libkf5messagecore5-18.08|libkf5messagelist5-18.08|libkf5messageviewer5-18.08|libkf5mimetreeparser5-18.08|libkf5templateparser5-18.08|libkf5webengin$ viewer5-18.08/; title = "kimap"; is_affected = .build-depends ~ /libkf5imap-dev/; is_good = .depends ~ /libkf5imap5-18.08/; is_bad = !.depends ~ /libkf5imap5-18.08/; title = "akonadicontact"; is_affected = .build-depends ~ /libkf5akonadicontact-dev|libkf5contacteditor-dev/; is_good = .depends ~ /libkf5akonadicontact5-18.08|libkf5contacteditor5-18.08/; is_bad = !.depends ~ /libkf5akonadicontact5-18.08|libkf5contacteditor5-18.08/; title = "kontactinterface"; is_affected = .build-depends ~ /libkf5kontactinterface-dev/; is_good = .depends ~ /libkf5kontactinterface5-18.08/; is_bad = !.depends ~ /libkf5kontactinterface5-18.08/; title = "pimtextedit"; is_affected = .build-depends ~ /libkf5pimtextedit-dev/; is_good = .depends ~ /libkf5pimtextedit5-18.08/; is_bad = !.depends ~ /libkf5pimtextedit5-18.08/; title = "calendarcore"; is_affected = .build-depends ~ /libkf5calendarcore-dev/; is_good = .depends ~ /libkf5calendarcore5-18.08/; is_bad = !.depends ~ /libkf5calendarcore5-18.08/; title = "libkdepim"; is_affected = .build-depends ~ /libkf5akonadisocialutils-dev|libkf5libkdepim-dev/; is_good = .depends ~ /libkf5libkdepim5-18.08|libkf5libkdepimakonadi5-18.08/; is_bad = !.depends ~ /libkf5libkdepim5-18.08|libkf5libkdepimakonadi5-18.08/; title = "pimgapi"; is_affected = .build-depends ~ /libkpimgapi-dev/; is_good = .depends ~ /libkpimgapiblogger5-18.08|libkpimgapicalendar5-18.08|libkpimgapicontacts5-18.08|libkpimgapicore5-18.08|libkpimgapidrive5-18.08|libkpimgapilatitude5-18.08|libkpimgapimaps5-18.08| libkpimgapitasks5-18.08/; is_bad = !.depends ~ /libkpimgapiblogger5-18.08|libkpimgapicalendar5-18.08|libkpimgapicontacts5-18.08|libkpimgapicore5-18.08|libkpimgapidrive5-18.08|libkpimgapilatitude5-18.08|libkpimgapimaps5-18.08| libkpimgapitasks5-18.08/; title = "kblog"; is_affected
Bug#941120: akonadi-backend-postgresql: fails to stop postgresql 11
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=386173#c20 Hey Martin, as I don't use postgresql as backend, can you explain, why this bug it that annoying, so I should fix that also for stable? Thanks, hefee btw. please use forwarded and other features directly, while you create bug reports, so they more metadata right away. By the syntax with Control: -1 ... This make it easier to track status later on. -- On Mittwoch, 25. September 2019 09:41:48 CEST Martin Steigerwald wrote: > Package: akonadi-backend-postgresql > Version: 4:18.08.3-8 > Severity: normal > > Dear Sandro, > > you may like to consider > > Git commit 565700f7fc1d73e337600109867fc01cc647cf13 by Daniel Vrátil. > Committed on 20/06/2019 at 09:51. > Pushed by dvratil into branch 'Applications/19.04'. > > Check Postgres status by checking return code of pg_ctl > > Summary: > The current code which was checking the standard output of "pg_ctl status", > doesn't work with non-English locale, causing Akonadi to leave Postgres > running after shutdown, because it thinks the db is no longer running. > FIXED-IN: 5.11.3 > > https://bugs.kde.org/show_bug.cgi?id=386173#c20 > > for Akonadi for buster. > > Thanks, > Martin > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, > 'experimental') Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.2.16-tp520 (SMP w/4 CPU cores; PREEMPT) > Kernel taint flags: TAINT_OOT_MODULE > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de > (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash > Init: sysvinit (via /sbin/init) > LSM: AppArmor: enabled > > Versions of packages akonadi-backend-postgresql depends on: > ii libqt5sql5-psql 5.11.3+dfsg1-4 > > Versions of packages akonadi-backend-postgresql recommends: > ii akonadi-server 4:18.08.3-8 > ii postgresql 11+207 > > akonadi-backend-postgresql suggests no packages. > > -- no debconf information signature.asc Description: This is a digitally signed message part.
Bug#941481: kalarm: The Akonadi personal information management service is not running
Control: tags -1 moreinfo Hey, > When installing kalarm on mate desktop environment, program is not working. > It shows just message > "The Akonadi personal information management service is not running. This > application cannot be used without it". Pressing button Start does nothing. > In console there is output > > $ LC_ALL=C kalarm > org.kde.pim.kidentitymanagement: IdentityManager: There was no default > identity. Marking first one as default. > org.kde.pim.akonadicore: Unable to execute akonadi_control, falling back to > D-Bus auto-launch > [...] > > There are probably missing dependencies for kalarm package - when I install > also package kontact with its dependencies, kalarm starts working well. can you try if this is fixed, if you only install akoandiserver or do you need kdepim-runtime, too? hefee signature.asc Description: This is a digitally signed message part.
Bug#941763: libqt5sql5-psql: basic support postgresql-12
Package: libqt5sql5-psql Version: 5.12.5+dfsg-1 Severity: important Control: affects -1 akonadi-backend-postgresql Today, I installed Postgresql 12 and akonadi refuses to start. Two years ago, a similar issue (bug #876421, #879960) with postgresql 10. >From the code it seems that Postgres 12 isn't supprted at all: https://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/sqldrivers/psql/qsql_psql.cpp#n1080 -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libqt5sql5-psql depends on: ii libc6 2.29-2 ii libpq512.0-1 ii libqt5core5a [qtbase-abi-5-11-3] 5.11.3+dfsg1-4 ii libqt5sql55.11.3+dfsg1-4 ii libstdc++69.2.1-8 pn qtbase-abi-5-12-5 pn qtbase-abi-5-7-1 libqt5sql5-psql recommends no packages. libqt5sql5-psql suggests no packages.
Bug#941118: akonadi-server: fails to start after upgrade to 4:18.08.3-8: apparmor denied access to pg_ctl
Hey intrigeri, I now pushed a first version of Akonadi with the new AppArmor profile, but as you see down here it fails and I'm not sure, what went wrong. What we need to do to debug this? Those AppArmor profiles are in place: https://salsa.debian.org/qt-kde-team/kde/akonadi/blob/master/debian/apparmor/ usr.bin.akonadiserver https://salsa.debian.org/qt-kde-team/kde/akonadi/blob/master/debian/apparmor/ postgresql_akonadi hefee -- On Mittwoch, 25. September 2019 09:58:24 CEST Martin Steigerwald wrote: > > I upgraded and then rebooted the system. > > > > After upgrading to Akonadi 4:18.08.3-8, Akonadi does not start > > anymore: > > > > % akonadictl start > > Connecting to deprecated signal > > QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString > > ) org.kde.pim.akonadicontrol: Application 'akonadiserver' exited > > normally... > > > > I believe the failure may be due to this: > > > > Sep 25 09:21:06 merkaba kernel: [ 266.556167][ T37] audit: > > type=1400 audit(1569396066.434:45): apparmor="DENIED" > > operation="exec" profile="postgresql_akonadi" name="/bin/dash" > > pid=3833 comm="pg_ctl" requested_mask="x" denied_mask="x" fsuid=1000 > > ouid=0 > > […] > > > Also setting to complain mode does not help: > > > > % aa-complain postgresql_akonadi > > Setting /etc/apparmor.d/postgresql_akonadi to complain mode. > > > > Although access does get allowed then: > > > > Sep 25 09:30:14 merkaba kernel: [ 814.345508][ T37] audit: > > type=1400 audit(1569396614.227:51): apparmor="ALLOWED" > > operation="exec" profile="postgresql_akonadi" name="/bin/dash" > > pid=5328 comm="pg_ctl" requested_mask="x" denied_mask="x" fsuid=1000 > > ouid=0 target="postgresql_akonadi//null-/bin/dash" > > Oh, it does help. Akonadi starts again, just did not notice it > initially. > > The pattern in > > % grep pg_ctl /etc/apparmor.d/postgresql_akonadi > /usr/lib/postgresql/*/bin/pg_ctl mrix, > > seems to be okay tough: > > % ls -l /usr/lib/postgresql/*/bin/pg_ctl > -rwxr-xr-x 1 root root 59888 Sep 24 22:09 /usr/lib/postgresql/11/bin/ > pg_ctl > > However I am no AppArmor expert… > > Best, signature.asc Description: This is a digitally signed message part.
Bug#939013: akonadi: Akonadi components crash on logout
Source: akonadi Version: 4:18.08.3-5 Severity: important Tags: upstream Forwarded: https://bugs.kde.org/show_bug.cgi?id=401692 Akonadi components tend to crash, if you shutdown Akonadi. That is surely not a behavior, that is intended. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#939012: akonadi: Multiple merge candidates, aborting
Source: akonadi Version: 4:18.08.3-5 Severity: important Tags: upstream Forwarded: https://bugs.kde.org/show_bug.cgi?id=338658 Users see notificcations about "Multiple merge candidates, aborting", this leads to a corrupt Akonadi database and things get wore and wore over time. The bugfix itself describe what is done: "Introduce a recovery codepath when Multiple Merge Candidates error occurs during Item merging. Since clients generally do not use merging, this really only happens during ItemSync. In such case we quitely delete all the conflicting items from the database and reschedule the collection sync. The next sync should then succeed and bring the collection into a consistent state. Note that this does not fix the Multiple Merge Candidates bug - it can still happen (and we still don't know how), but Akonadi should now be able to recover from it automatically without user intervention, thus making this issue less of a PITA." -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#935981: akonadi: Akonadi stops anwsering any requests and ends in deadlock
Source: akonadi Version: 4:18.08.3-5 Severity: important Forwarded: https://bugs.kde.org/show_bug.cgi?id=399167 Symptoms: After a while Akonadi stops responing any request and you can not interact with Akonadi anymore. It seems to hit many people rather badly -- akonadi won't answer to any requests once hitting that bug, and even a reboot only help very temporarily (until the faulty folder gets synced again). Upstream has already proposed patches for this bug see either https://bugs.kde.org/show_bug.cgi?id=399167 these to patches should fix this bug: https://commits.kde.org/akonadi/15c91a0ac93051465b37807efceb6e9fd36cb73b https://commits.kde.org/akonadi/4fb179ce46ad3e7da8b25c921b0c8a68f9dfb4ee -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#926996: kmail: CVE-2019-10732: decryption based on replying to PGP or S/MIME encrypted emails
Control: reassign -1 kf5-messagelib The code lies in kf5-messagelib, that's why I reassign the bug. Please update the security tracker accordingly. > Discussion on https://bugs.kde.org/show_bug.cgi?id=404698 seems to > indicate the issue is getting resolved upstream. Yes I fixed the bug upstream and will hopefully find time the next days to backport it to 18.08. hefee signature.asc Description: This is a digitally signed message part.
Bug#905697: kdepimlibs: don't depend on libical
Hi, thanks a lot for the patch. I already pushed a new version, with your patch added. hefee -- On Sonntag, 31. März 2019 22:35:05 CEST Giovanni Mascellani wrote: > user debian-rele...@lists.debian.org > > usertags 905697 + bsp-2019-03-fr-paris > thank you > > Hi, > > On Thu, 14 Feb 2019 10:07:42 +0100 Emilio Pozuelo Monfort > > wrote: > > kde-runtime has dozens of rdeps, so unless its dep on kdepimlibs can be > > broken somehow, this would be much harder to solve for buster. > > Hoping it might be helpful, I ported kdepimlibs to libical3. This should > finally make us able to remove libical2, I believe. With the attached > patch kdepimlibs compiles, but I did not try to use it (I am not a KDE > user, and much less a KDE PIM user). Could KDE maintainers test it? > > My patch was mostly adapted from [1]. I am also attaching another patch > that explicitly sets QT_SELECT to version 4, so that build does not fail > even if Qt 5 is available. > > [1] > https://github.com/KDE/kcalcore/commit/27eaa211b23a6bb0bcba5a91cf7cadfc1e888 > e21?diff=unified > > HTH, Giovanni. signature.asc Description: This is a digitally signed message part.
Bug#876905: Fwd: Re: [SECURITY] CVE-2019-7443 (kauth) in kdelibs
Hey, FreeBSD removed Qt4 compelty last weekend from their repo. hefee -- Forwarded Message -- Subject: Re: [SECURITY] CVE-2019-7443 (kauth) in kdelibs Date: Samstag, 23. März 2019, 22:54:08 CET From: Tobias C. Berner To: Sandro Knauß, Adriaan de Groot Moin moin On FreeBSD we just solved this be removing that stuff too [KDE4 and things depending on it was removed 2018-12-31, Qt4 last weekend.] https://svnweb.freebsd.org/ports?view=revision=495967 I was kind of scared of having a big backlash to this action -- though there was none in the end. So as an advice from kde@FreeBSD's side: just pull the plug and remove that stuff :) mfg Tobias On Sat, 23 Mar 2019 at 12:35, Sandro Knauß wrote: > Hi, > > > kdelibs last release was 4.14.35 in August 2017. > > > > kdelibs is no longer maintained. > > > > Qt 4 last release was 4.8.7 in May 2015. > > > > Qt 4 is no longer maintained. > > > > Our suggestion is to stop using any qt4/kdelibs based software and move > to > > the future if you're concerned about security and/or want to use > maintained > > software. > > It is not that we do not try it, to remove Qt4 from Debian. We try since > Aug > 2017 to reach this goal to remove all qt4/kdelibs software, but still > there is > a lot depending on qt4/kdelibs: > > https://wiki.debian.org/Qt4Removal > > (If you have any notes about status of packages aka dead by upstream - > input > is very welcomed). > > In next Debian Buster released in some months we still need to ship qt4/ > kdelibs. > > Regards, > > hefee signature.asc Description: This is a digitally signed message part.
Bug#922727: CVE-2019-7443
Hey, > Shall we cherrypick/backport the patch on our own, then or rather ignore it > given the vast majority of applications uses kf5 now? I would recommend to cherrypick/backport. I think the base hasn't changed a lot, so it will be easy to backport. Unfortunately we sill have several applications that are using kde4libs. > > as kdelibs is EOL so not security support by KDE > > anymore. > > Ok, then let's remove the whole KDE4/Qt4 stack for bullseye (I suppose > that's the maintainer's plan anyway?) Yeah this was the plan for Buster already: https://wiki.debian.org/Qt4Removal at least we hardy reached a sub goal for Buster: https://wiki.debian.org/Qt4WebKitRemoval hefee signature.asc Description: This is a digitally signed message part.
Bug#922727: CVE-2019-7443
Hey, > The security bug filed against kauth in #921995 also seems to affect > kde4libs, the code is in kdecore/auth/backends/dbus/DBusHelperProxy.cpp? yes, it is likely, that also kde4libs is affected. kauth is KDE Frameworks. As the birth of KDE Frameworks is a split of kdelibs. I think KDE doesn't mention kdelibs as affected, as kdelibs is EOL so not security support by KDE anymore. (Only in Debian kdelibs was renamed to kde4libs, as there were package name conflicts. That's why I'm normally talking about kdelibs.) hefee signature.asc Description: This is a digitally signed message part.
Bug#895632: kdav: autopkgtest fails with new release while succeeded in the past
Version: 18.08.3-1 As the build tests are flaky anyways, we disabled the autopkgtest for Buster. hefee -- On Freitag, 13. April 2018 19:54:40 CET Paul Gevers wrote: > Source: kdav > Version: 17.12.3-1 > Severity: normal > User: ci-t...@tracker.debian.org > Usertags: regression > > With the upload of version 17.12.3-1 of kdav, the > autopkgtest¹ started to fail with the following error: > > Running tests... > /usr/bin/ctest --force-new-ctest-process -j1 > Test project > /tmp/autopkgtest-lxc.m0yqmrr9/downtmp/build.7In/src/obj-x86_64-linux-gnu > Start 1: kdav-davcollection > 1/5 Test #1: kdav-davcollection ... Passed0.03 sec > Start 2: kdav-davitem > 2/5 Test #2: kdav-davitem . Passed0.01 sec > Start 3: kdav-davurl > 3/5 Test #3: kdav-davurl .. Passed0.01 sec > Start 4: kdav-davitemfetchjob > 4/5 Test #4: kdav-davitemfetchjob .***Failed0.02 sec > * Start testing of DavItemFetchJobTest * > Config: Using QtTest library 5.9.2, Qt 5.9.2 (x86_64-little_endian-lp64 > shared (dynamic) release build; by GCC 7.3.0) > PASS : DavItemFetchJobTest::initTestCase() > QWARN : DavItemFetchJobTest::runSuccessfullTest() kf5.kdbusaddons: Can > not find 'kdeinit5' executable at > "/usr/share/pkg-kde-tools/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games: > /usr/games" > "/tmp/autopkgtest-lxc.m0yqmrr9/downtmp/build.7In/src/obj-x86_64-linux-gnu/b > in, /usr/lib/qt5/bin" > QWARN : DavItemFetchJobTest::runSuccessfullTest() kf5.kio.core: KIO > Connection server not listening, could not connect > QWARN : DavItemFetchJobTest::runSuccessfullTest() kf5.kio.core: > couldn't create slave: "Can not create socket for launching io-slave for > protocol 'http'." > FAIL! : DavItemFetchJobTest::runSuccessfullTest() > 'fakeServer.isAllScenarioDone()' returned FALSE. () >Loc: > [/tmp/autopkgtest-lxc.m0yqmrr9/downtmp/build.7In/src/autotests/davitemfetchj > obtest.cpp(42)] PASS : DavItemFetchJobTest::cleanupTestCase() > Totals: 2 passed, 1 failed, 0 skipped, 0 blacklisted, 9ms > * Finished testing of DavItemFetchJobTest * > > Start 5: kdav-davitemslistjob > 5/5 Test #5: kdav-davitemslistjob . Passed0.01 sec > > 80% tests passed, 1 tests failed out of 5 > > Total Test time (real) = 0.09 sec > > The following tests FAILED: > 4 - kdav-davitemfetchjob (Failed) > Errors while running CTest > make[3]: *** [Makefile:99: test] Error 8 > > > Paul > > ¹ https://ci.debian.net/packages/k/kdav/unstable/amd64/ signature.asc Description: This is a digitally signed message part.
Bug#910731: kaddressbook: crashes at startup
Hey, okay the initial issue is solved, that is great. Btw. please use the bugnumber-qu...@bugs.debian.org rarely, because than maintainers like me don't gets any mails, that's why I missed your conversation. > > I suppose this means that kaddressbook should depend on akonadi-server. thanls for spotting this, I'll fix that soon. Often people use complete kdepim that's why these inter kdepim dependencies are sometimes not complete. hefee signature.asc Description: This is a digitally signed message part.
Bug#730048: kmail does not properly quote From field when replying
Control: tags -1 -moreinfo Control: found -1 4:18.08.1-1 Control: found -1 4:4.14.1-1+deb8u1 Hey, well the bug is an upstream one, so please report back there, that you can reproduce it with a new version. It is too much work for me to forward your input. https://bugs.kde.org/show_bug.cgi?id=343812 hefee -- On Dienstag, 15. Januar 2019 18:43:49 CET LeJacq, Jean Pierre wrote: > Here's an update for kmail in buster which is at the following version: > > $ apt-cache policy kmail > kmail: > Installed: 4:18.08.1-1 > Candidate: 4:18.08.1-1 > Version table: > *** 4:18.08.1-1 500 > 500 http://ftp.us.debian.org/debian buster/main amd64 Packages > 2 http://ftp.us.debian.org/debian unstable/main amd64 Packages > 100 /var/lib/dpkg/status > > The bug continues to exist. Unfortunately, the option to make the identity > sticky is gone rendering my workaround unusable. signature.asc Description: This is a digitally signed message part.
Bug#921624: kmail: Crash during/after filtering inbox, probably related to Qt WebEngine integration
Control: forwarded -1 https://bugs.kde.org/404052 Hey, it does not looks like a packaging issue so far. It may a duplicate of #923490. hefee -- On Donnerstag, 7. Februar 2019 13:08:17 CET Martin Steigerwald wrote: > Dear Sandro, > > Better late than never, I managed to report the KMail crashes during/after > filtering inbox upstream. See: > > Bug 404052 - Crash during/after filtering inbox, probably related to Qt > WebEngine integration https://bugs.kde.org/404052 > > This may or may not be a packaging related issue. > > Thanks, > Martin signature.asc Description: This is a digitally signed message part.
Bug#923562: kmail: fails to copy sent email to sent mail folder
Control: tags -1 +moreinfo Hey, for what resource this happens? maildir, imap, google imap? did you checked akonadiconsole also logging tab may be interessed. hefee signature.asc Description: This is a digitally signed message part.
Bug#922270: kmail - "Name" column in message window can not made smaller
Control: tags -1 +moreinfo Hey Hans, > I got into a minor problem. In the window (where the "Kmail-folder", > "Inbox", "Sent" etc. folders appear), it is not possible, to resize the > firs column (called "name"). > > The first column is very, very, very large and on the buttom of the window > there appeared a slider. I can resize with the mouse by slide to the far right and than use the mouse when the cursor changes to the "change size cursor" and than keep the left mouse button pressend and move the mouse to the left. Than the mouse jumps back to the first position but keep moving to the left. That makes the name column smaller and smaller. Yes it looks visually completly broken ;D hefee signature.asc Description: This is a digitally signed message part.
Bug#923292: kmail randomly crashes when closing windows
Control: tags -1 +moreinfo Please start kmail from console and enable Qt logging before like I described at #923288. Please attach a backtrace of the crash, so we can analyse what is going on. hefee On Montag, 25. Februar 2019 23:24:54 CET Juha Jäykkä wrote: > Package: kmail > Version: 4:18.08.3-1 > Severity: normal > > Dear Maintainer, > > I do not like the "message preview pane", so I open each message in a > separate window to read them. Sometimes, and as far as I can tell, at > random, kmail will crash with a SIGSEGV when such message window OR compose > message window is closed. It does not matter what causes the window to > close, even sending a message sometimes causes a crash. > > Cheers, > Juha > > -- System Information: > Debian Release: buster/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, > 'experimental') Architecture: amd64 (x86_64) > > Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores) > Kernel taint flags: TAINT_WARN > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: > LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) (ignored: > LC_ALL set to en_GB.UTF-8) 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:18.08.3-4 > ii kdepim-runtime 4:18.08.3-1 > ii kio 5.54.1-1 > ii libc62.28-7 > ii libgcc1 1:8.2.0-21 > ii libgpgmepp6 1.12.0-6 > ii libkf5akonadiagentbase5 4:18.08.3-4 > ii libkf5akonadicontact54:18.08.3-1 > ii libkf5akonadicore5abi2 4:18.08.3-4 > ii libkf5akonadimime5 4:18.08.3-1 > ii libkf5akonadisearch-bin 4:18.08.3-1 > ii libkf5akonadisearch-plugins 4:18.08.3-1 > ii libkf5akonadisearchdebug54:18.08.3-1 > ii libkf5akonadisearchpim5 4:18.08.3-1 > ii libkf5akonadiwidgets5abi14:18.08.3-4 > ii libkf5bookmarks5 5.54.0-1 > ii libkf5calendarcore5abi2 4:18.08.3-1 > ii libkf5calendarutils5 4:18.08.3-2 > ii libkf5codecs55.54.0-1 > ii libkf5completion55.54.0-1 > ii libkf5configcore55.54.0-1 > ii libkf5configgui5 5.54.0-1 > ii libkf5configwidgets5 5.54.0-1 > ii libkf5contacts5 4:18.08.3-1 > ii libkf5coreaddons55.54.0-1 > ii libkf5crash5 5.54.0-1 > ii libkf5dbusaddons55.54.0-1 > ii libkf5followupreminder5 4:18.08.3-2 > ii libkf5grantleetheme-plugins 18.08.3-1 > ii libkf5gravatar5abi2 4:18.08.3-1 > ii libkf5guiaddons5 5.54.0-1 > ii libkf5i18n5 5.54.0-1 > ii libkf5iconthemes55.54.0-1 > ii libkf5identitymanagement518.08.3-2 > ii libkf5itemmodels55.54.0-1 > ii libkf5itemviews5 5.54.0-1 > ii libkf5jobwidgets55.54.0-1 > ii libkf5kcmutils5 5.54.0-1 > ii libkf5kiocore5 5.54.1-1 > ii libkf5kiofilewidgets55.54.1-1 > ii libkf5kiowidgets55.54.1-1 > ii libkf5kontactinterface5 18.08.3-1 > ii libkf5ksieveui5 4:18.08.3-2 > ii libkf5libkdepim-plugins 4:18.08.3-2 > ii libkf5libkdepim5 4:18.08.3-2 > ii libkf5libkdepimakonadi5 4:18.08.3-2 > ii libkf5libkleo5 4:18.08.3-2 > ii libkf5mailcommon5abi24:18.08.3-2 > ii libkf5mailtransport5 18.08.3-2 > ii libkf5mailtransportakonadi5 18.08.3-2 > ii libkf5messagecomposer5abi1 4:18.08.3-1 > ii libkf5messagecore5abi1 4:18.08.3-1 > ii libkf5messagelist5abi1 4:18.08.3-1 > ii libkf5messageviewer5abi1 4:18.08.3-1 > ii libkf5mime5abi1 18.08.3-1 > ii libkf5mimetreeparser5abi14:18.08.3-1 > ii libkf5notifications5 5.54.0-1 > ii libkf5notifyconfig5 5.54.0-1 > ii libkf5parts5 5.54.0-1 > ii libkf5pimcommon5abi2 4:18.08.3-2 > ii libkf5pimcommonakonadi5abi1 4:18.08.3-2 > ii libkf5pimtextedit5abi2 18.08.3-1 > ii libkf5sendlater5 4:18.08.3-2 > ii libkf5service-bin5.54.0-1 > ii libkf5service5 5.54.0-1 > ii libkf5sonnetui5 5.54.0-1 > ii libkf5templateparser54:18.08.3-1 > ii libkf5textwidgets5 5.54.0-1 > ii libkf5tnef5 4:18.08.3-1 > ii libkf5wallet-bin 5.54.0-1 > ii libkf5wallet55.54.0-1 > ii libkf5webengineviewer5abi1 4:18.08.3-1 > ii libkf5widgetsaddons5 5.54.0-1 > ii libkf5windowsystem5 5.54.0-1 > ii libkf5xmlgui55.54.0-1 > ii libqgpgme7 1.12.0-6 > ii libqt5core5a 5.11.3+dfsg-5 > ii libqt5dbus5 5.11.3+dfsg-5 > ii libqt5gui5 5.11.3+dfsg-5 > ii libqt5network5 5.11.3+dfsg-5 > ii
Bug#923293: kmail: mailbox contents displayed wrong
Control: tags -1 +moreinfo Please use the Notification Monitor and Job tracker tab in akonadiconsole to find out more information about what is going on. You have to enabled both before the issue happen, so see if the needed jobs/notifications are triggerd. In the end of this, it will not be a Debian issue, so you need to to report the bug upstream: https://bugs.kde.org. Please leave a note about the concrete link to the upstream bugreport, so we can track the state inhere. hefee -- On Montag, 25. Februar 2019 23:22:48 CET Juha Jäykkä wrote: > Package: kmail > Version: 4:18.08.3-1 > Severity: normal > > Dear Maintainer, > > kmail will often show mailbox contents wrong: it will show the correct > number of unread messages in the folders pane, but the actual messages > displayed do not show all those unread messages (presumably not all read > messages are shown either but not sure). > > Checking the akonadi status from akonadiconsole shows all the messages, > including the ones kmail does not show, so kmail somehow gets out of sync > with akonadi. > > This can be worked around by restarting kmail, but given the frequency that > this happens, several times a day, it makes kmail's usability quite > abysmal. signature.asc Description: This is a digitally signed message part.
Bug#923291: kmail: syncing inbox(es) never finishes
Control: tags -1 +moreinfo Control: reassign -1 akonadi-server 4:18.08.3-4 Control: affects -1 kmail Hey Juha, thanks for giving input about the current state of kmail. Unfortunately these are not enough information to tackle down the issue. Your issue sounds that a Akonadi Resource is stuck. Please use akonadiconsole for debugging. At frist enable logging at the logging tab. go to the Agent tab select the resource that got stuck and select "Show task list" and print the output. The queues should all be empty if the sync was successful. We may properly to distinguish the issue for google, as goolge's imap implementation is wired, so let's focus on opensource mailserver dovecot first. > Steps to reprocude: start kmail, let it run for a while, checking inboxes > either manually or letting the automatic interval check do it for you. In > less than 15 minutes at least one of the inboxes gets stuck. I can't reproduce it on my setup. And I use 5 different accounts dovecot and kolab. Do you have stable inet for your tests? If inet went away while syncing, than sometime Akonadi don't recover. Also putting my laptop to sleep while currently if syncing breaks Akonadi sometimes. But in the end of this, it will not be a Debian issue, so you need to to report the bug upstream: https://bugs.kde.org. Please leave a note about the concrete link to the upstream bugreport, so we can track the state inhere. hefee signature.asc Description: This is a digitally signed message part.
Bug#923288: kmail does not exit
Control: tags -1 +moreinfo Hey Juha, thanks for giving input about the current state of kmail. Unfortunately these are not enough information to tackle down the issue. Enable logging for Qt: ~/.config/QtProject/qtlogging.ini [Rules] *.warning=true *.critical=true *=true qt.*=false sonnet.*=false and start kmail form a konsole. That may gives us the needed information. After the debug session replace *=true with *=false otherwise your .xsessions- errors will get big very soon. is Ctrl+C in konsole enough to stop kmail in that situation? hefee signature.asc Description: This is a digitally signed message part.
Bug#900895: kmail: KMail malfunctioning: Red email folders, no emails can be viewed; "Unable to fetch item from backend (collection-1): Unable to contact resource"
Control: tags -1 +moreinfo
Control: reassign -1 kdepim-runtime 4:16.04.2-2+b2
Control: forcemerge -1 900957
Thanks for reporting the issue and sorry for not responding for so long time.
The bug is actually in the maildir_resource that is shipped within kdepim-
runtime package, that why reassign the bug.
It would be super great if you could test your setup with kmail on Debian
Buster, that is currently in testing. Because kdepim fixed serveral issues for
maildir resource.
hefee
On Mittwoch, 27. Februar 2019 05:33:12 CET Jens Radloff wrote:
> I recorded another occurrence of this behaviour with the debugger in the
> Akonadi Console. This time, below the output field on the "All" tab, the
> following additional error messages gets displayed:
>
> --- Quote Beginning ---
>
> AgentBase(akonadi_maildir_resource_0): Verbindung zum Akonadi-Dienst kann
> nicht hergestellt werden. => Can be translated as "Cannot establish
> connection to Akonadi service"
> NotificationManager::notify ( { Type: "Items" Operation: "Modify" Items: { {
> ID: "32532" RemoteID: "1551182744.R329.punk" Remote Revision: "" Mime Type:
> "message/rfc822" } } Session: "akonadi_maildir_resource_0" Resource:
> "akonadi_maildir_resource_0" Destination Resource: "" Parent Collection:
> "9" Parent Destination Collection: "-1" Parts: "QSet(PLD:HEAD, PLD:RFC822,
> PLD:ENVELOPE)" Added Flags: "QSet()" Removed Flags: "QSet()" Added Tags:
> "QSet()" Removed Tags: "QSet()" } )
> NotificationManager::notify ( { Type: "Items" Operation: "Modify" Items: { {
> ID: "32536" RemoteID: "1551196645.R430.punk:2,S" Remote Revision: "" Mime
> Type: "message/rfc822" } } Session: "akonadi_maildir_resource_0" Resource:
> "akonadi_maildir_resource_0" Destination Resource: "" Parent Collection:
> "7" Parent Destination Collection: "-1" Parts: "QSet(PLD:HEAD, PLD:RFC822,
> PLD:ENVELOPE)" Added Flags: "QSet()" Removed Flags: "QSet()" Added Tags:
> "QSet()" Removed Tags: "QSet()" }
>
> -- Quote End
>
> Then I restarted Akonadi with "akonadictl restart" in a command shell window
> and did not close this window, but provoked the behavior again. The console
> window returned the following debugging information about the time when the
> behaviour occurred again:
>
> --- Quote Beginning ---
>
> akonadicore_log: Invalid command, the world is going to end!
> QIODevice::read (QLocalSocket): device not open
> akonadi_maildir_resource: /build/akonadi-EKz4jf/akonadi-16.04.3/src/private/
> protocol.cpp:1590: Akonadi::Protocol::HelloResponse::HelloResponse(const
> Akonadi::Protocol::Command&): Zusicherung »d_func()->commandType ==
> Command::Invalid || d_func()->commandType == (Command::Hello |
> Command::_ResponseBit)« nicht erfüllt.
> void Akonadi::Server::NotificationSource::serviceUnregistered(const
> QString&) Notification source "akonadi_maildir_resource_0_4955_mdI52n" now
> serving: () ProcessControl: Application /usr/bin/akonadi_maildir_resource
> stopped unexpectedly ( "Der Prozess ist abgestürzt" ) => Can be translated
> as "The process has crashed"
> Application '/usr/bin/akonadi_maildir_resource' crashed too often. Giving
> up! Shutting down "/subscriber/akonadi_maildir_resource_0_4955_mdI52n" ...
> Lost connection to resource
> "org.freedesktop.Akonadi.Resource.akonadi_maildir_resource_0" , discarding
> cached interface
> Shutting down "akonadi_maildir_resource_0" ...
> Shutting down "0x55b505adb7b0" ...
>
> --- Quote End ---
>
> This bug issue is a duplicate of
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900957
signature.asc
Description: This is a digitally signed message part.
Bug#923490: kmail: random segfaults while idle
Control: reassign -1 qtwebengine 5.11.3+dfsg-2 Control: affects -1 kmail Control: retitle -1 QtWebEnigne make kmail random segfault while idle The complete backtrace looks not to be complete, as I don't see any reference to any libkf5X nor to kmail. For me it looks like an issue in qtwebegine, that's why I reassign it to qtwebengine. hefee On Donnerstag, 28. Februar 2019 23:15:06 CET Juha Jäykkä wrote: > Package: kmail > Version: 4:18.08.3-1 > Severity: important > > Dear Maintainer, > > Kmail sometimes sigsegvs while (seemingly) idle. Needless to say this > seriously degrades its usability. I think this has only ever happened while > moving the mouse pointer across the window. Just moving, not clicking > anything, not using mouse scroll wheel, just moving the pointer, not even > stopping while kmail window is focused, so tooltip texts etc should not be > activating. > > Backtrace follows. > > Application: KMail (kmail), signal: Segmentation fault > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > [Current thread is 1 (Thread 0x7f7c358dbf00 (LWP 7560))] > > Thread 39 (Thread 0x7f7b44bec700 (LWP 9712)): > #0 0x7f7c4afc63a9 in futex_reltimed_wait_cancelable (private=0, > reltime=0x7f7b44beb400, expected=0, futex_word=0x7f7b44beb5e8) at > ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f7c4afc63a9 in > __pthread_cond_wait_common (abstime=0x7f7b44beb4a0, mutex=0x7f7b44beb598, > cond=0x7f7b44beb5c0) at pthread_cond_wait.c:533 #2 0x7f7c4afc63a9 in > __pthread_cond_timedwait (cond=0x7f7b44beb5c0, mutex=0x7f7b44beb598, > abstime=0x7f7b44beb4a0) at pthread_cond_wait.c:667 #3 0x7f7c4480fa37 > in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at > /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f7c4481230a > in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at > /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f7c448123f2 > in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at > /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f7c44816981 > in > base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent* > ) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 > 0x7f7c44817c7f in base::internal::SchedulerWorker::Thread::ThreadMain() > () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 > 0x7f7c44820c81 in base::(anonymous namespace)::ThreadFunc(void*) () at > /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f7c4afbffa3 > in start_thread (arg=) at pthread_create.c:486 #10 > 0x7f7c4d78680f in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 > > Thread 38 (Thread 0x7f7b453ed700 (LWP 9711)): > #0 0x7f7c4afc63a9 in futex_reltimed_wait_cancelable (private=0, > reltime=0x7f7b453ec400, expected=0, futex_word=0x7f7b453ec5e8) at > ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f7c4afc63a9 in > __pthread_cond_wait_common (abstime=0x7f7b453ec4a0, mutex=0x7f7b453ec598, > cond=0x7f7b453ec5c0) at pthread_cond_wait.c:533 #2 0x7f7c4afc63a9 in > __pthread_cond_timedwait (cond=0x7f7b453ec5c0, mutex=0x7f7b453ec598, > abstime=0x7f7b453ec4a0) at pthread_cond_wait.c:667 #3 0x7f7c4480fa37 > in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at > /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f7c4481230a > in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at > /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f7c448123f2 > in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at > /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f7c44816981 > in > base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent* > ) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 > 0x7f7c44817e61 in base::internal::SchedulerWorker::Thread::ThreadMain() > () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 > 0x7f7c44820c81 in base::(anonymous namespace)::ThreadFunc(void*) () at > /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f7c4afbffa3 > in start_thread (arg=) at pthread_create.c:486 #10 > 0x7f7c4d78680f in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 > > Thread 37 (Thread 0x7f7b4df11700 (LWP 9710)): > #0 0x7f7c4afc63a9 in futex_reltimed_wait_cancelable (private=0, > reltime=0x7f7b4df10400, expected=0, futex_word=0x7f7b4df105e8) at > ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f7c4afc63a9 in > __pthread_cond_wait_common (abstime=0x7f7b4df104a0, mutex=0x7f7b4df10598, > cond=0x7f7b4df105c0) at pthread_cond_wait.c:533 #2 0x7f7c4afc63a9 in > __pthread_cond_timedwait (cond=0x7f7b4df105c0, mutex=0x7f7b4df10598, > abstime=0x7f7b4df104a0) at pthread_cond_wait.c:667 #3 0x7f7c4480fa37 > in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at > /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f7c4481230a > in
Bug#922255: libkgapi: FTBFS randomly (failing tests)
Hey, Yes it is known, that the tests are flaky. Upstream also fighting with this fact and improving slowly... Please give the build another try. hefee -- On Mittwoch, 13. Februar 2019 21:16:24 CET Santiago Vila wrote: > Package: src:libkgapi > Version: 18.08.3-1 > Severity: important > Tags: ftbfs > > Dear maintainer: > > I tried to build this package in buster but it failed: > > > [...] > debian/rules build-indep > /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.pl > --with=kf5,pkgkde-symbolshelper dpkg-buildflags --export=make > > debian/dhmk_env.mk > /usr/bin/make -f debian/rules dhmk_run_configure_commands > DHMK_TARGET="configure" make[1]: Entering directory '/<>' > dh_testdir # [-i] > dh_auto_configure '--buildsystem=kf5' --parallel # [-i] > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu > -DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DKDE_INSTALL_USE_QT_SYS_PATHS=ON .. -- The C compiler identification is > GNU 8.2.0 > -- The CXX compiler identification is GNU 8.2.0 > -- Check for working C compiler: /usr/bin/cc > -- Check for working C compiler: /usr/bin/cc -- works > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > > [... snipped ...] > > * Finished testing of TaskCreateJobTest * > > Start 25: tasks-taskdeletejobtest > 25/37 Test #25: tasks-taskdeletejobtest ... Passed0.24 sec > Start 26: tasks-taskfetchjobtest > 26/37 Test #26: tasks-taskfetchjobtest Passed0.24 sec > Start 27: tasks-taskmodifyjobtest > 27/37 Test #27: tasks-taskmodifyjobtest ... Passed0.24 sec > Start 28: tasks-taskmovejobtest > 28/37 Test #28: tasks-taskmovejobtest . Passed0.24 sec > Start 29: tasks-tasklistcreatejobtest > 29/37 Test #29: tasks-tasklistcreatejobtest ... Passed0.24 sec > Start 30: tasks-tasklistdeletejobtest > 30/37 Test #30: tasks-tasklistdeletejobtest ... Passed0.24 sec > Start 31: tasks-tasklistfetchjobtest > 31/37 Test #31: tasks-tasklistfetchjobtest Passed0.23 sec > Start 32: tasks-tasklistmodifyjobtest > 32/37 Test #32: tasks-tasklistmodifyjobtest ... Passed0.24 sec > Start 33: drive-aboutfetchjobtest > 33/37 Test #33: drive-aboutfetchjobtest ... Passed0.23 sec > Start 34: drive-changefetchjobtest > 34/37 Test #34: drive-changefetchjobtest .. Passed0.23 sec > Start 35: drive-filecopyjobtest > 35/37 Test #35: drive-filecopyjobtest . Passed0.24 sec > Start 36: drive-filecreatejobtest > 36/37 Test #36: drive-filecreatejobtest ... Passed0.25 sec > Start 37: drive-filesearchquerytest > 37/37 Test #37: drive-filesearchquerytest . Passed0.22 sec > > 97% tests passed, 1 tests failed out of 37 > > Total Test time (real) = 10.13 sec > > The following tests FAILED: >24 - tasks-taskcreatejobtest (Failed) > Errors while running CTest > make[3]: *** [Makefile:86: test] Error 8 > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > dh_auto_test: cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=-j1 returned > exit code 2 make[2]: *** [debian/rules:12: override_dh_auto_test] Error 2 > make[2]: Leaving directory '/<>' > make[1]: *** [/usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: > pre_build-indep_dh_auto_test] Error 2 make[1]: Leaving directory > '/<>' > make: *** [/usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:112: > debian/dhmk_build-indep] Error 2 dpkg-buildpackage: error: debian/rules > build-indep subprocess returned exit status 2 > --- > - > > (The above is just how the build ends and not necessarily the most relevant > part) > > The build was made in my autobuilder with "dpkg-buildpackage -A", where > it fails randomly, but it seems to fail almost always here: > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libkgapi. > html > > where you can get a full build log if you need it. > > If this is really a bug in one of the build-depends, please use reassign and > affects, so that this is still visible in the BTS web page for this > package. > > Thanks. signature.asc Description: This is a digitally signed message part.
Bug#921987: mysqld-akonadi: Could not open required defaults file
Hey, > I used mysql and not mariadb. well mysql is not in buster. mysql-5.5 is oldstable So using mysql can't be a supported case. I strongly encourage you to switch to mariadb! If you need to use mysql, than you find a workaround at the upstream bugreport: https://bugs.kde.org/show_bug.cgi?id=399346 > As I changed to sqlite3 I can't test with mariadb. So you get the error with sqlite3 backend? The sqlite3 backend is not recommended to be used in production. As sqlite3 lacks about many features of a proper sql database. > Some times ago I tested mariadb, but mariadb didn't start, I forget the exact message, but it complaned about unknown version 5.7. I'm using mariadb without issues for several years now. We had an issue with fresh installations, that was solved with 18.08.3-2. But without any concrete log messages I can't help. regards hefee signature.asc Description: This is a digitally signed message part.
Bug#921987: mysqld-akonadi: Could not open required defaults file
Hey, > I have the same problem and it didn't go away. > Using the version from testing solved the problem. > Using the version from sid and the problem reappeared. > Strace showed the message ACCESS DENIED on > ~/.local/share/akonadi/mysql.conf. Now, I'm using the version from testing. do you use mysql or mariadb? Can you debug more into this issue? I can't reproduce this issue on sid with mariadb-server 1:10.3.12-2 and apparmor 2.13.2-7. hefee signature.asc Description: This is a digitally signed message part.
Bug#905697: kdepimlibs: don't depend on libical
Hey, for me it looks like we won't be able to get kdepimlibs without libical 2 for buster. Keep in mind, that kdepimlibs is an old grufted lib set that we also would like to kill. But we also have other packages depending on it like: * basket * kopete (it has a QT5 version in experimental, but this is suitable as replacement yet). and other that may can be killed. extract libical 2 out of kdepimlibs is not that simple, as the whole interface will leak into akonadi-calendar, calcore, calutils,... In short I won't have the time to do the work and test it in the near future. I added pino to this bug report, as pino successfully extracted other parts of old kdelibs/kdepimlibs. hefee -- On Donnerstag, 17. Januar 2019 12:11:46 CET Emilio Pozuelo Monfort wrote: > On 11/01/2019 13:37, Emilio Pozuelo Monfort wrote: > > On 08/08/2018 10:38, Emilio Pozuelo Monfort wrote: > >> Source: kdepimlibs > >> Version: 4:4.14.10-10 > >> Severity: serious > >> Control: block 884128 with -1 > >> > >> Hi, > >> > >> libical2 from src:libical is superseded by libical3 (src:libical3). > >> > >> Please either port kdepimlibs to libical3 or try to disable the > >> libical support, so that we can only ship src:libical3 in buster. > > > > Could someone who knows kdepimlibs take a look at this? Can we disable > > libical support in kdepimlibs for buster? This is the last blocker for > > the libical 2 removal. > > Hi Sandro, > > Lisandro said you may be able to help with this. Do you know if libical > support could be disabled in kdepimlibs, or if the newer version libical3 > could be used? > >From [1] it seems that libical is kind of optional, though I don't know if > >we > can disable the bits to drop that or if those bits have rdeps. Since > kdepimlibs is the last rdep of the old libical version, fixing this would > allow us to drop that one from buster. Otherwise the RC bugs that it has > will need to be fixed and we'll have to ship with two versions of the > library. > > Thanks, > Emilio > > [1] > https://sources.debian.org/src/kdepimlibs/4:4.14.10-10/CMakeLists.txt/#L81 signature.asc Description: This is a digitally signed message part.
Bug#921646: kdepim-runtime: akonadi_imap_resource fails to download gmail content
Hey, thanks for your input. So far your bugreport sounds like gmail banning the account temporarily for exceeding some limit. They do such things. So just retry some hours later, than you should download more. Hopefully that helps. Unfortunately we do not have a way to display those bans to users. hefee signature.asc Description: This is a digitally signed message part.
Bug#921584: Free the results when QSqlQuery::finished() is called
Ah short report, why those patches are needed. Without the patches all DB requests will pile up in RAM and Akonadi will use more and more RAM with time. Keeping the query around in the caches cause them to use insane amount of memory, if the last query happened to return a lot of results. signature.asc Description: This is a digitally signed message part.
Bug#921535: Some patches for Akonadi
Ah short report, why those patches are needed. Without the patches all DB requests will pile up in RAM and Akonadi will use more and more RAM with time. Keeping the query around in the caches cause them to use insane amount of memory, if the last query happened to return a lot of results. signature.asc Description: This is a digitally signed message part.
Bug#910902: Mariadb provides my_print_defaults not anymore at mariadb-server-core
Control: reassign -1 mariadb-server 1:10.3.12-2 Control: affects -1 akonadi-backend-mysql Control: severity -1 serious Hey, mariadb moved my_print_defaults from mysql-server-core to mariadb-server. So akonadi-backend-mysql do now need to depend at mariadb-server. As "my_print_defaults" is only needed at first start of akonadi it is a pity if we would that for now rely on a full istalled mariadb-server. Can you please clearify why this move was done? hefee signature.asc Description: This is a digitally signed message part.
Bug#908869: blogilo: FTBFS with pimtextedit 18.08.1
Control: block 909288 by -1 Control: severity -1 serious Hey, the kdepim 18.08 transition has now started. Raising the severity to RC. hefee -- On Samstag, 15. September 2018 13:00:04 CEST Sandro Knauß wrote: > Package: blogilo > Version: 4:17.08.3-2 > Severity: important > > Hey, > > the package do not build against new upcoming KDE Pim 18.08.1. As > KPimTextEdit has changed its interface. here the relevant buildlog: > > In file included from > /<>/composereditorwebengine/src/private/composerwebengine_p.cp > p:33: /usr/include/KF5/KPIMTextEdit/kpimtextedit/inserthtmldialog.h:27:10: > fatal error: kpimtextedit_private_export.h: No such file or directory > #include "kpimtextedit_private_export.h" > ^~~ > compilation terminated. > > Regards, > > hefee signature.asc Description: This is a digitally signed message part.
Bug#909288: transition: kdepim 18.08
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition KDE Pim 18.08 has updated ist API and ABI, that makes it nessasary to bump some ABIs. Most of the packages, that needs to be rebuild are inside KDE Pim itself so only following "external" packages are affected: ktorrent kio-gdrive blogilo kjots zanshin digikam kraft (calligraplan) I build all rdepends and I have only two issues: * blogilo has fallen out of KDE Pim can't be build anymore [#908869] * calligraplan depend on the build packages, but the features that use KDE Pim are disabled, so no need to build them within the transition. This transistion includes/replaces following auto detected transitions: auto-akonadi auto-kalarmcal auto-kcalcore auto-kdav auto-kf5-messagelib auto-kldap auto-kpimtextedit auto-ksmtp auto-libkf5eventviews auto-libkf5gravatar auto-libkf5mailcommon auto-libkf5pimcommon auto-libkgapi auto-syndication These 15 transitions share nearly all rdepdens. I don't see any blocker from my side, to wait. hefee -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#908870: korganizer: Tuen Ng Festival date in 2019 is wrong
Control: Forwarded -1 https://bugs.kde.org/show_bug.cgi?id=398670 The bug tracker of Debian can handle the forwarded command to get status updates automatically. hefee -- On Samstag, 15. September 2018 15:55:37 CEST Michael Tsang wrote: > https://bugs.kde.org/show_bug.cgi?id=398670 > > On Saturday 15 September 2018 21:12:22 HKT Sandro Knauß wrote: > > Control: reassign -1 src:kholidays > > Control: notfound -1 4:17.12.3-2 > > Control: found -1 1:5.49.0-1 > > Control: tags -1 +upstream > > > > Hey, > > > > Thanks for your bugreport. The bug itself is not not korganizer it is > > kholidays as kholidays has the list of all holidays. The bug itself is not > > a Debian one, it is an upstream bug. So please open an upstream bug > > report at https://bugs.kde.org and leave a note about the upstream > > bugreport here. > > > > If you have any questions, do not hesitate to ask. > > > > hefee signature.asc Description: This is a digitally signed message part.
Bug#908870: korganizer: Tuen Ng Festival date in 2019 is wrong
Control: reassign -1 src:kholidays Control: notfound -1 4:17.12.3-2 Control: found -1 1:5.49.0-1 Control: tags -1 +upstream Hey, Thanks for your bugreport. The bug itself is not not korganizer it is kholidays as kholidays has the list of all holidays. The bug itself is not a Debian one, it is an upstream bug. So please open an upstream bug report at https://bugs.kde.org and leave a note about the upstream bugreport here. If you have any questions, do not hesitate to ask. hefee -- On Samstag, 15. September 2018 13:15:43 CEST Michael Tsang wrote: > Package: korganizer > Version: 4:17.12.3-2 > Severity: normal > Tags: l10n > > Dear Maintainer, > > The date of Tuen Ng Festival in Hong Kong is wrong in korganizer. The > calendar shows 7 May 2019, however, according to the gov't website, it > should be 7 June 2019. > > The authoritative source can be found below. > > https://www.gov.hk/en/about/abouthk/holiday/2019.htm > > -- System Information: > Debian Release: buster/sid > APT prefers testing > APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.18.0-1-amd64 (SMP w/8 CPU cores) > Locale: LANG=en_HK.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), > LANGUAGE=en_GB:en_HK:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages korganizer depends on: > ii kdepim-runtime 4:17.12.3-2 > ii kio 5.49.0-1 > ii libc62.27-6 > ii libgcc1 1:8.2.0-6 > ii libkf5akonadicalendar5abi1 4:17.12.3-1 > ii libkf5akonadicontact54:17.12.3-2 > ii libkf5akonadicore5abi1 4:17.12.3-3 > ii libkf5akonadimime5 4:17.12.3-1 > ii libkf5akonadinotes5 4:17.12.3-1 > ii libkf5akonadisearchpim5 4:17.12.3-1 > ii libkf5akonadiwidgets5abi14:17.12.3-3 > ii libkf5calendarcore5abi1 4:17.12.3-1 > ii libkf5calendarsupport5abi1 4:17.12.3-1 > ii libkf5calendarutils5 4:17.12.3-1 > ii libkf5codecs55.49.0-1 > ii libkf5completion55.49.0-1 > ii libkf5configcore55.49.0-1 > ii libkf5configgui5 5.49.0-1 > ii libkf5configwidgets5 5.49.0-1 > ii libkf5contacts5 4:17.12.3-1 > ii libkf5coreaddons55.49.0-1 > ii libkf5crash5 5.49.0-1 > ii libkf5dbusaddons55.49.0-1 > ii libkf5eventviews54:17.12.3-2 > ii libkf5holidays5 1:5.49.0-1 > ii libkf5i18n5 5.49.0-1 > ii libkf5iconthemes55.49.0-1 > ii libkf5identitymanagement517.12.3-1 > ii libkf5incidenceeditor5abi1 17.12.3-2 > ii libkf5itemmodels55.49.0-1 > ii libkf5itemviews5 5.49.0-1 > ii libkf5jobwidgets55.49.0-1 > ii libkf5kcmutils5 5.49.0-1 > ii libkf5kdepimdbusinterfaces5 4:17.12.3-1 > ii libkf5kiocore5 5.49.0-1 > ii libkf5kiowidgets55.49.0-1 > ii libkf5kontactinterface5 17.12.3-1 > ii libkf5libkdepim-plugins 4:17.12.3-1 > ii libkf5libkdepim5 4:17.12.3-1 > ii libkf5libkdepimakonadi5 4:17.12.3-1 > ii libkf5mailtransport5 17.12.3-1 > ii libkf5mailtransportakonadi5 17.12.3-1 > ii libkf5mime5abi1 17.12.3-2 > ii libkf5newstuff5 5.49.0-1 > ii libkf5notifications5 5.49.0-1 > ii libkf5parts5 5.49.0-1 > ii libkf5pimcommon5abi1 4:17.12.3-1 > ii libkf5pimcommonakonadi5 4:17.12.3-1 > ii libkf5pimtextedit5abi1 17.12.3-2 > ii libkf5service-bin5.49.0-1 > ii libkf5service5 5.49.0-1 > ii libkf5widgetsaddons5 5.49.0-1 > ii libkf5windowsystem5 5.49.0-1 > ii libkf5xmlgui55.49.0-1 > ii libphonon4qt5-4 4:4.10.1-1 > ii libqt5core5a 5.11.1+dfsg-8 > ii libqt5dbus5 5.11.1+dfsg-8 > ii libqt5gui5 5.11.1+dfsg-8 > ii libqt5widgets5 5.11.1+dfsg-8 > ii libstdc++6 8.2.0-6 > ii phonon4qt5 4:4.10.1-1 > > korganizer recommends no packages. > > korganizer suggests no packages. > > -- no debconf information signature.asc Description: This is a digitally signed message part.
Bug#907345: After upgrading from 5.10.1+dfsg-6 to 5.10.1+dfsg-7 akonadi imap stops working - possibly OpenSSL 1.1.1
Hey, > I think this bug-report can be closed. you can do this by your own if you send a mail at 907345-d...@bugs.debian.org. > The problems disappears if openssl is also upgraded to version 1.1.1~~pre9-1 > (from 1.1.0h-4). So this problem only exists with openssl < 1.1.1~~pre9-1. Wait - this is all very strange you say you have Qt 5.10.1+dfsg-6 installed and OpenSSL 1.1.1~~pre9-1. Qt is 5.11 in testing/unstable and for sure it is built aganist OpenSSL 1.1.0. Futher more qtbase-opensource-src is delayed because of issues with OpenSSL 1.1.1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907015 well but untangle this, may be not worth doing it - if it works for you now. So we have at least one datapoint, that OpenSSL may improve situations for users :D hefee signature.asc Description: This is a digitally signed message part.
Bug#907427: openssl 1.1.1 breaks ssl tests
Source: qtbase-opensource-src, kimap Version: kimap/18.07.90-1 Control: block 907015 by -1 When I built my KDE PIM packages locally I built against openssl 1.1.0h-4 and I had no issues running the KIMAP tests. With openssl 1.1.1~~pre9-1 (experimental) the tests breaks. See [1] for more examples. You may want to merge with #907340 or #907340, as those are also failings tests because of openssl 1.1.1. hefee [1] https://buildd.debian.org/status/package.php?p=kimap=experimental [...] QWARN : LoginJobTest::shouldUseSsl(any protocol with anyssl version) "Error loading local certificate, error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small" QWARN : LoginJobTest::shouldUseSsl(any protocol with anyssl version) QAbstractSocket::SocketError(21) QWARN : LoginJobTest::shouldUseSsl(any protocol with anyssl version) "Unable to init SSL Context: " QWARN : LoginJobTest::shouldUseSsl(any protocol with anyssl version) QAbstractSocket::SocketError(20) QWARN : LoginJobTest::shouldUseSsl(any protocol with anyssl version) "The remote host closed the connection" QWARN : LoginJobTest::shouldUseSsl(any protocol with anyssl version) QAbstractSocket::RemoteHostClosedError QWARN : LoginJobTest::shouldUseSsl(any protocol with anyssl version) org.kde.pim.kimap: Connection to server lost 0 FAIL! : LoginJobTest::shouldUseSsl(any protocol with anyssl version) 'login->exec()' returned FALSE. () Loc: [/<>/autotests/loginjobtest.cpp(250)] [...] -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libqt5network5 depends on: ii libc6 2.27-5 ii libqt5core5a [qtbase-abi-5-11-0] 5.11.1+dfsg-7 ii libqt5dbus5 5.11.1+dfsg-7 ii libssl1.1 1.1.1~~pre9-1 ii libstdc++68.2.0-4 ii zlib1g1:1.2.11.dfsg-1 libqt5network5 recommends no packages. libqt5network5 suggests no packages. -- no debconf information
Bug#907230: kmail-account-wizard: FTBFS with Qt 5.11
Control: fixed -1 4:18.07.90-1 Hey, these bugs are handled with the new upstream version of KDE PIM, that is currently sitting in experimental and NEW queue. But at least I have compile the whole new KDE PIM against Qt 5.11. Please check before filing those bugs if a new version waits in experimental/NEW queue. hefee -- signature.asc Description: This is a digitally signed message part.
Bug#907148: Bug#907154: akonadi-import-wizard: FTBFS in buster/sid (invalid use of incomplete type 'class QAction')
Control: fixed -1 4:18.07.90-1 Hey, these bugs are handled with the new upstream version of KDE PIM, that is currently sitting in experimental and NEW queue. But at least I have compile the whole new KDE PIM against Qt 5.11. Please check before filing those bugs if a new version waits in experimental/NEW queue. hefee signature.asc Description: This is a digitally signed message part.
Bug#906653: libkf5ksieve: FTBFS in buster/sid ('class QFontMetrics' has no member named 'width')
Control: fixed -1 4:18.07.90-1 The sources of 18.07.90 are with Qt 5.11 compatible. This bug is solved with a new version (currently in experimental/NEW). hefee -- On Sonntag, 19. August 2018 13:19:56 CEST Santiago Vila wrote: > Package: src:libkf5ksieve > Version: 4:17.12.3-1 > Severity: serious > Tags: ftbfs > > Dear maintainer: > > I tried to build this package in buster but it failed: > > > [...] > debian/rules build-indep > /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.pl > --with=kf5,pkgkde-symbolshelper dpkg-buildflags --export=make > > debian/dhmk_env.mk > /usr/bin/make -f debian/rules dhmk_run_configure_commands > DHMK_TARGET="configure" make[1]: Entering directory '/<>' > dh_testdir # [-i] > dh_auto_configure '--buildsystem=kf5' --parallel # [-i] > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None > -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var > -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" > -DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DKDE_INSTALL_USE_QT_SYS_PATHS=ON .. -- The C compiler identification is > GNU 8.2.0 > -- The CXX compiler identification is GNU 8.2.0 > -- Check for working C compiler: /usr/bin/cc > -- Check for working C compiler: /usr/bin/cc -- works > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > > [... snipped ...] > >^ > /<>/src/ksieveui/vacation/legacy/vacationutils.cpp:72:41: > warning: 'SpamDataExtractor' is deprecated [-Wdeprecated-declarations] > KSieveUi::Legacy::SpamDataExtractor sdx; > ^~~ > In file included from > /<>/src/ksieveui/vacation/legacy/vacationutils.cpp:25: > /<>/src/ksieveui/vacation/legacy/vacationscriptextractor.h:83: > 27: note: declared here class KSIEVEUI_DEPRECATED SpamDataExtractor : public > GenericInformationExtractor ^ > /<>/src/ksieveui/vacation/legacy/vacationutils.cpp:73:54: > warning: 'DomainRestrictionDataExtractor' is deprecated > [-Wdeprecated-declarations] > KSieveUi::Legacy::DomainRestrictionDataExtractor drdx; > ^~~~ > In file included from > /<>/src/ksieveui/vacation/legacy/vacationutils.cpp:25: > /<>/src/ksieveui/vacation/legacy/vacationscriptextractor.h:145 > :27: note: declared here class KSIEVEUI_DEPRECATED > DomainRestrictionDataExtractor : public GenericInformationExtractor > ^~ > /<>/src/ksieveui/vacation/legacy/vacationutils.cpp:74:37: > warning: 'DateExtractor' is deprecated [-Wdeprecated-declarations] > KSieveUi::Legacy::DateExtractor dtx; > ^~~ > In file included from > /<>/src/ksieveui/vacation/legacy/vacationutils.cpp:25: > /<>/src/ksieveui/vacation/legacy/vacationscriptextractor.h:209 > :27: note: declared here class KSIEVEUI_DEPRECATED DateExtractor : public > GenericInformationExtractor ^ > [ 16%] Building CXX object > src/ksieveui/CMakeFiles/KF5KSieveUi.dir/vacation/legacy/vacationscriptextra > ctor.cpp.o cd /<>/obj-x86_64-linux-gnu/src/ksieveui && > /usr/bin/c++ -DBUILD_TESTING -DKCOREADDONS_LIB -DKF5KSieveUi_EXPORTS > -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB > -DQT_DISABLE_DEPRECATED_BEFORE=0x06 -DQT_GUI_LIB -DQT_NETWORK_LIB > -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_CAST_TO_ASCII > -DQT_NO_DEBUG -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT > -DQT_NO_SIGNALS_SLOTS_KEYWORDS -DQT_NO_URL_CAST_FROM_STRING > -DQT_POSITIONING_LIB -DQT_PRINTSUPPORT_LIB -DQT_QML_LIB -DQT_QUICK_LIB > -DQT_USE_FAST_CONCATENATION -DQT_USE_FAST_OPERATOR_PLUS > -DQT_USE_QSTRINGBUILDER -DQT_WEBCHANNEL_LIB -DQT_WEBENGINECORE_LIB > -DQT_WEBENGINEWIDGETS_LIB -DQT_WIDGETS_LIB -DQT_XML_LIB > -DTRANSLATION_DOMAIN=\"libksieve\" -D_GNU_SOURCE -D_LARGEFILE64_SOURCE > -I/<>/obj-x86_64-linux-gnu/src/ksieveui > -I/<>/src/ksieveui > -I/<>/obj-x86_64-linux-gnu/src/ksieveui/KF5KSieveUi_autogen/in > clude -I/<>/src/ksieveui/util > -I/<>/src/kmanagesieve -I/< > >/obj-x86_64-linux-gnu/src/kmanagesieve -I/<>/src > -I/<>/obj-x86_64-linux-gnu/src -I/<>/src/parser > -isystem /usr/include/KF5/PimCommon -isystem /usr/include/KF5/pimcommon > -isystem /usr/include/KF5 -isystem /usr/include/x86_64-linux-gnu/qt5 > -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem > /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem > /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem > /usr/include/KF5/KIOCore -isystem /usr/include/KF5/KCoreAddons -isystem > /usr/include/KF5/KService -isystem /usr/include/KF5/KConfigCore -isystem > /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem > /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem > /usr/include/KF5/KConfigWidgets -isystem
Bug#906219: Bug#906220: kcalutils FTBFS with Qt 5.11
Control: tag -1 pending I currently prepare the new usptream version 18.08, that will upload soon to experimental, that fixes the issue. hefee signature.asc Description: This is a digitally signed message part.
Re: Bug#905559: Bug#902263: Affecting Qt transition
Hey, > That's totally understandable from your part. Now the test has clearly > failed. The regression could either be in Qt or in some part of the KDE PIM > stack (not the meta package). ktexteditor is KDE Frameworks and not KDE PIM. For KDE PIM the argument of not being up-to-date and not being ready for Qt 5.11 may be/is valid. But Framworks is uptodate with 5.47 (released in June) and it should be Qt 5.11 ready - So you should considering filing a bug about this regression upstream. hefee signature.asc Description: This is a digitally signed message part.
Bug#899274: KMail does not always remember the desired message list columns
Hey, > Are you sure? Because the qt bug is marked as fixed, but I still have this > issue as well (fully updated Sid system). Well also Arch mention this bug and hopefully they are all patched already in master :D But I do not understand the bugtracker for Qt within which version what is fixed. 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. According to arch there are (maybe) more bugs with patches needed: qheaderview-restore.patch "https://code.qt.io/cgit/qt/qtbase.git/patch/?id=4a04eea4; qtbug-66444.patch "https://code.qt.io/cgit/qt/qtbase.git/patch/?id=9395f35c; qtbug-66420.patch "https://code.qt.io/cgit/qt/qtbase.git/patch/?id=fa091640; qtbug-66816.patch "https://code.qt.io/cgit/qt/qtbase.git/patch/?id=e4e87a2e; hefee signature.asc Description: This is a digitally signed message part.
Bug#899274: KMail does not always remember the desired message list columns
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 Hey, I can confirm this bug. On kdepim-us...@kde.org it was mentioned that this issue is a Qt one. Here the the mail: On Samstag, 10. März 2018 12:19:45 CEST Colin J Thomson wrote: > > > > Were you guys able to have kmail remember which columns to display (or > > > > rather none to display other than Name)? > > > > > > Nope. It forgets, and I have to set it each time. It still is annoying. > > > > That must be a bug. Reported it? > > 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 hefee signature.asc Description: This is a digitally signed message part.
Re: Bug#894741: kcharselect crash when going to "Mathematical Symbols > Mathematical Operators" characters block
Version: 4:17.08.3-1 Hello, I can't reproduce the crash with 17.08.3 for Noto Sans. So I think the issue is fixed meanwhile. If it is still an issue within that version, please repopen and give a mode detailed crash report. hefee -- On Dienstag, 3. April 2018 20:35:26 CEST Alexander Kernozhitsky wrote: > Package: kcharselect > Version: 4:16.08.0-1+b1 > Severity: important > > Dear Maintainer, > > Going to "Mathematical Symbols > Mathematical Operators" character block > crashes the application. The crash happens only when a specific font is set > (tested on Noto Sans, on many other fonts this bug is not reproducible). > > -- System Information: > Debian Release: 9.4 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, > 'stable') Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores) > Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), > LANGUAGE=ru_RU:ru (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages kcharselect depends on: > ii libc6 2.24-11+deb9u3 > ii libkf5configcore5 5.28.0-2 > ii libkf5configgui5 5.28.0-2 > ii libkf5configwidgets5 5.28.0-2 > ii libkf5coreaddons5 5.28.0-2 > ii libkf5i18n5 5.28.0-2 > ii libkf5widgetsaddons5 5.28.0-3 > ii libkf5xmlgui5 5.28.0-1 > ii libqt5core5a 5.7.1+dfsg-3+b1 > ii libqt5gui55.7.1+dfsg-3+b1 > ii libqt5widgets55.7.1+dfsg-3+b1 > ii libstdc++66.3.0-18+deb9u1 > > kcharselect recommends no packages. > > kcharselect suggests no packages. > > -- no debconf information signature.asc Description: This is a digitally signed message part.
Bug#886214: kdepim lost kjots
Control: tags -1 +wontfix Hey, thanks for your bugreport. But it was upstream that has moved kjots to unmaintained. The kdepim package in Debian is the meta package, that installs everything that upstream bundles. hefee Here a mail from upstream (30.10.17): KJots are no longer part of the KDE PIM release, but you can still install KJots as a standalone application (there's a kjots package), and no migration should be required for that (but better make backups, just to be sure). We have decided to remove KJots from KDE PIM, because we don't have the time and resources anymore to maintain it, but I still sort of keep it alive and compiling, but there's basically no feature development, just the most important bugfixes. signature.asc Description: This is a digitally signed message part.
Bug#899128: kdepim: Limit CVE-2017-17689 (EFAIL) even more for kmail
Control: tags -1 +patch
Hey,
I now created a debdiff for kdepim. The patch depdends on the new symbol that
was added in new messageviewer (see #899127).
hefeediff -Nru kdepim-16.04.3/debian/changelog kdepim-16.04.3/debian/changelog
--- kdepim-16.04.3/debian/changelog 2017-06-17 12:12:03.0 +0200
+++ kdepim-16.04.3/debian/changelog 2018-05-19 19:11:15.0 +0200
@@ -1,3 +1,15 @@
+kdepim (4:16.04.3-4~deb9u2) stretch; urgency=high
+
+ * Team upload.
+
+ [ Sandro Knauß ]
+ * Limit CVE-2017-17689 (EFAIL) for kmail (Closes: #899128)
+- Added upstream patch (modified to apply)
+ upstream-Distinguish-between-settings-and-explicit-overrides-.patch
+- Update dependendy against kf5-messagelib
+
+ -- Sandro Knauß <he...@debian.org> Sat, 19 May 2018 19:11:15 +0200
+
kdepim (4:16.04.3-4~deb9u1) stretch; urgency=high
* Team upload.
diff -Nru kdepim-16.04.3/debian/control kdepim-16.04.3/debian/control
--- kdepim-16.04.3/debian/control 2017-06-17 12:12:03.0 +0200
+++ kdepim-16.04.3/debian/control 2018-05-19 18:21:40.0 +0200
@@ -73,7 +73,7 @@
libkf5messagecomposer-dev,
libkf5messagecore-dev (>= 5.2.0~),
libkf5messagelist-dev,
- libkf5messageviewer-dev (>= 5.2.0~),
+ libkf5messageviewer-dev (>= 4:16.04.3-3~deb9u2),
libkf5mime-dev (>= 15.12~),
libkf5newstuff-dev (>= 5.19.0~),
libkf5notifyconfig-dev (>= 5.19.0~),
diff -Nru kdepim-16.04.3/debian/patches/series kdepim-16.04.3/debian/patches/series
--- kdepim-16.04.3/debian/patches/series 2017-06-17 12:12:03.0 +0200
+++ kdepim-16.04.3/debian/patches/series 2018-05-19 17:49:42.0 +0200
@@ -5,3 +5,4 @@
fix_crash_when_a_second_instance_of_KAlarm_is_started.patch
konsolekalendar_help.patch
fix-CVE-2017-9604.patch
+upstream-Distinguish-between-settings-and-explicit-overrides-.patch
diff -Nru kdepim-16.04.3/debian/patches/upstream-Distinguish-between-settings-and-explicit-overrides-.patch kdepim-16.04.3/debian/patches/upstream-Distinguish-between-settings-and-explicit-overrides-.patch
--- kdepim-16.04.3/debian/patches/upstream-Distinguish-between-settings-and-explicit-overrides-.patch 1970-01-01 01:00:00.0 +0100
+++ kdepim-16.04.3/debian/patches/upstream-Distinguish-between-settings-and-explicit-overrides-.patch 2018-05-19 18:18:28.0 +0200
@@ -0,0 +1,115 @@
+From 88558f6273650a03d2828027e04116564ca18f20 Mon Sep 17 00:00:00 2001
+From: Volker Krause <vkra...@kde.org>
+Date: Thu, 26 Apr 2018 18:44:24 +0200
+Subject: [PATCH 3/9] Distinguish between settings and explicit overrides for
+ external content
+
+Summary: See D12391 and D12393 in messagelib.
+
+Reviewers: mlaurent, dvratil, knauss
+
+Reviewed By: knauss
+
+Subscribers: #kde_pim
+
+Tags: #kde_pim
+
+Differential Revision: https://phabricator.kde.org/D12394
+---
+ kmail/kmmainwidget.cpp| 6 +++---
+ kmail/kmreadermainwin.cpp | 4 ++--
+ kmail/kmreadermainwin.h | 2 +-
+ kmail/kmreaderwin.cpp | 9 +++--
+ kmail/kmreaderwin.h | 3 ++-
+ 5 files changed, 15 insertions(+), 9 deletions(-)
+
+--- a/kmail/kmmainwidget.cpp
b/kmail/kmmainwidget.cpp
+@@ -513,7 +513,7 @@ void KMMainWidget::folderSelected(const
+ readFolderConfig();
+ if (mMsgView) {
+ mMsgView->setDisplayFormatMessageOverwrite(mFolderDisplayFormatPreference);
+-mMsgView->setHtmlLoadExtOverride(mFolderHtmlLoadExtPreference);
++mMsgView->setHtmlLoadExtDefault(mFolderHtmlLoadExtPreference);
+ }
+
+ if (!mCurrentFolder->isValid() && (mMessagePane->count() < 2)) {
+@@ -1593,7 +1593,7 @@ void KMMainWidget::slotOverrideHtmlLoadE
+ mFolderHtmlLoadExtPreference = !mFolderHtmlLoadExtPreference;
+
+ if (mMsgView) {
+-mMsgView->setHtmlLoadExtOverride(mFolderHtmlLoadExtPreference);
++mMsgView->setHtmlLoadExtDefault(mFolderHtmlLoadExtPreference);
+ mMsgView->update(true);
+ }
+ }
+@@ -4391,7 +4391,7 @@ void KMMainWidget::itemsReceived(const A
+ mMsgView->setMessage(copyItem);
+ // reset HTML override to the folder setting
+ mMsgView->setDisplayFormatMessageOverwrite(mFolderDisplayFormatPreference);
+-mMsgView->setHtmlLoadExtOverride(mFolderHtmlLoadExtPreference);
++mMsgView->setHtmlLoadExtDefault(mFolderHtmlLoadExtPreference);
+ mMsgView->setDecryptMessageOverwrite(false);
+ mMsgActions->setCurrentMessage(copyItem);
+ }
+--- a/kmail/kmreadermainwin.cpp
b/kmail/kmreadermainwin.cpp
+@@ -72,14 +72,14 @@
+
+ using namespace MailCommon;
+
+-KMReaderMainWin::KMReaderMainWin(MessageViewer::Viewer::DisplayFormatMessage format, bool htmlLoadExtOverride,
++KMReaderMainWin::KMReaderMainWin(MessageViewer::Viewer::DisplayFormatMessage format, bool htmlLoadExtDefault,
+ char *name)
+ : KMail::SecondaryWindow(name ? name : &
Bug#899127: kf5-messagelib: Limit CVE-2017-17689 (EFAIL) even more for kmail
Hey,
I now created a debdiff for kf5-messagelib. This patch touches the public ABI
and adds one function, but this should not be a problem. Should I update the
messageveiwer.symbols, too? And what I should add there, as there should not
been Debian revision added.
hefeediff -Nru kf5-messagelib-16.04.3/debian/changelog kf5-messagelib-16.04.3/debian/changelog
--- kf5-messagelib-16.04.3/debian/changelog 2017-06-17 09:08:12.0 +0200
+++ kf5-messagelib-16.04.3/debian/changelog 2018-05-19 17:16:55.0 +0200
@@ -1,3 +1,16 @@
+kf5-messagelib (4:16.04.3-3~deb9u2) stretch; urgency=high
+
+ * Team upload.
+
+ [ Sandro Knauß ]
+ * Limit outcome of CVE-2017-17689: kmail: efail attack against S/MIME
+(Closes: #899127)
+- Added upstream patches (modified to apply to old source):
+ * upstream-Distinguish-between-settings-and-explicit-override-f.patch
+ * upstream-Load-external-references-in-encrypted-emails-only-on.patch
+
+ -- Sandro Knauß <he...@debian.org> Sat, 19 May 2018 17:16:55 +0200
+
kf5-messagelib (4:16.04.3-3~deb9u1) stretch; urgency=high
* Team upload.
diff -Nru kf5-messagelib-16.04.3/debian/patches/series kf5-messagelib-16.04.3/debian/patches/series
--- kf5-messagelib-16.04.3/debian/patches/series 2017-06-17 09:08:12.0 +0200
+++ kf5-messagelib-16.04.3/debian/patches/series 2018-05-19 16:13:08.0 +0200
@@ -1,3 +1,5 @@
upstream_add_copying_files.patch
make-it-impossible-to-override-css-settings-from-a-h.patch
fix-CVE-2017-9604.patch
+upstream-Load-external-references-in-encrypted-emails-only-on.patch
+upstream-Distinguish-between-settings-and-explicit-override-f.patch
diff -Nru kf5-messagelib-16.04.3/debian/patches/upstream-Distinguish-between-settings-and-explicit-override-f.patch kf5-messagelib-16.04.3/debian/patches/upstream-Distinguish-between-settings-and-explicit-override-f.patch
--- kf5-messagelib-16.04.3/debian/patches/upstream-Distinguish-between-settings-and-explicit-override-f.patch 1970-01-01 01:00:00.0 +0100
+++ kf5-messagelib-16.04.3/debian/patches/upstream-Distinguish-between-settings-and-explicit-override-f.patch 2018-05-19 17:10:27.0 +0200
@@ -0,0 +1,152 @@
+From 0bb1c5b12745b801f1aa4d6c630911845409e8ee Mon Sep 17 00:00:00 2001
+From: Volker Krause <vkra...@kde.org>
+Date: Thu, 26 Apr 2018 18:31:36 +0200
+Subject: [PATCH 33/44] Distinguish between settings and explicit override for
+ external content
+
+Summary:
+This will allow KMail to properly communicate the difference also when
+using per-folder settings for loading external references. This in turn
+makes D12391 also work in that case.
+
+Reviewers: mlaurent, dvratil, knauss
+
+Reviewed By: knauss
+
+Subscribers: #kde_pim
+
+Tags: #kde_pim
+
+Differential Revision: https://phabricator.kde.org/D12393
+---
+ messageviewer/src/viewer/viewer.cpp | 10 --
+ messageviewer/src/viewer/viewer.h | 15 +--
+ messageviewer/src/viewer/viewer_p.cpp | 17 ++---
+ messageviewer/src/viewer/viewer_p.h | 19 +++
+ 4 files changed, 46 insertions(+), 15 deletions(-)
+
+--- a/messageviewer/src/viewer/viewer.cpp
b/messageviewer/src/viewer/viewer.cpp
+@@ -258,10 +258,16 @@ void Viewer::setDisplayFormatMessageOver
+ d->setDisplayFormatMessageOverwrite(format);
+ }
+
+-void Viewer::setHtmlLoadExtOverride(bool override)
++void Viewer::setHtmlLoadExtDefault(bool loadExtDefault)
+ {
+ Q_D(Viewer);
+-d->setHtmlLoadExtOverride(override);
++d->setHtmlLoadExtDefault(loadExtDefault);
++}
++
++void Viewer::setHtmlLoadExtOverride(bool loadExtOverride)
++{
++Q_D(Viewer);
++d->setHtmlLoadExtOverride(loadExtOverride);
+ }
+
+ void Viewer::setAppName(const QString )
+--- a/messageviewer/src/viewer/viewer.h
b/messageviewer/src/viewer/viewer.h
+@@ -203,8 +203,19 @@ public:
+ /** Get the load external references override setting */
+ bool htmlLoadExtOverride() const;
+
+-/** Override default load external references setting */
+-void setHtmlLoadExtOverride(bool override);
++/** Default behavior for loading external references.
++ * Use this for specifying the external reference loading behavior as
++ * specified in the user settings.
++ * @see setHtmlLoadExtOverride
++ */
++void setHtmlLoadExtDefault(bool loadExtDefault);
++
++/** Override default load external references setting
++ * @warning This must only be called when the user has explicitly
++ * been asked to retrieve external references!
++ * @see setHtmlLoadExtDefault
++ */
++void setHtmlLoadExtOverride(bool loadExtOverride);
+
+ /** Is html mail to be supported? Takes into account override */
+ bool htmlMail() const;
+--- a/messageviewer/src/viewer/viewer_p.cpp
b/messageviewer/src/viewer/viewer_p.cpp
+@@ -217,7 +217,7 @@ ViewerPrivate::ViewerPrivate(Viewer *aPa
+ mDisplayFormatMessageOverwrite = MessageViewer::Viewer::UseGlobalSetting;
+
Bug#898634: kmail: efail attack against S/MIME
> There's a misunderstanding. My point isn't about PGP/MIME (which is indeed > handled by gnupg, even if through gpgme), but about S/MIME, which I really > don't think it handled by anything related to gnupg. It is - the binary and package is called gpgsm and is part of gnupg souce tarball. GPGME itself can handle PGP/MIME and S/MIME (if gpgsm is installed) content transparently. You only tell GPGME what to use. hefee signature.asc Description: This is a digitally signed message part.
Bug#898634: kmail: efail attack against S/MIME
> Ok. Other clients like Evolution and Trojita also had an issue with DNS > prefetching which could be re-enabled in Webkit. Not sure on what library > KMail relies for HTML rending but it might be worth checking that too? > > See https://bugs.webkit.org/show_bug.cgi?id=182924 for the webkit bug (with > links to the Evolution and Trojita ones). KMail using QtWebEngine ( based on Chromium engine) to display content. So far I think it is not affected as it is not listed in the efail paper: https://efail.de/efail-attack-paper.pdf, page 20 > > There are some small patches, that disable this setting for encrypted > > messages, to enforce a user interaction: > > > > https://phabricator.kde.org/D12391 > > https://phabricator.kde.org/D12393 > > https://phabricator.kde.org/D12394 > > > > For me applying the patches makes sense to improve security for users, but > > disabling the external resource loading completely would break workflows. > > Those patches are applied for the following Debian packages, where the > > setting > > is used for everything: > > libmessageviewer5 << 4:18.04.1 > > kmail < 4:18.04.1 > > Thanks, that's good to know. Should I prepare a update with those patches for stable? > > For a more detailed look for KMail and EFail see the dot.kde article: > > > > https://dot.kde.org/2018/05/15/efail-and-kmail > > That article indicates KMail uses GnuPG for S/MIME, which I find a bit > weird. Okay it is simplyfied a lot - but in the end... GPGME itself using gpg-agent etc. to request the work, so in the end it is the normal GnuPG pipeline, that is doing the work, without parsing comandline output :) But for more detailed look I wrote a blog post about the whole crypto stack some while ago: https://exote.ch/blogs/sandro/kontact-and-gnupg-under-windows/ hefee signature.asc Description: This is a digitally signed message part.
Bug#898634: kmail: efail attack against S/MIME
Hey, For S/MIME the situation is that it is a conceptional weakness in the standard to remove the target vector completely. In KMail we have the best handling that we can get at the moment (with default settings). KMail never access resources from the internet without asking the user or an explicit change of the default setting: Settings > Configure KMail > Security > Reading > Allow messages to load external references from the Internet There are some small patches, that disable this setting for encrypted messages, to enforce a user interaction: https://phabricator.kde.org/D12391 https://phabricator.kde.org/D12393 https://phabricator.kde.org/D12394 For me applying the patches makes sense to improve security for users, but disabling the external resource loading completely would break workflows. Those patches are applied for the following Debian packages, where the setting is used for everything: libmessageviewer5 << 4:18.04.1 kmail < 4:18.04.1 As already mentioned, the underlying problem is the S/MIME conceptional weaknes, that can't be fixed by those patches. The stack KMail is using for decryption is GPGME Qt backend that is packaged in gpgme1.0 for testing/sid and gpgmepp for stable and older. I'm not sure, how this should be handled in Debian correctly. For a more detailed look for KMail and EFail see the dot.kde article: https://dot.kde.org/2018/05/15/efail-and-kmail hefee -- On Montag, 14. Mai 2018 15:33:02 CEST Yves-Alexis Perez wrote: > Source: kmail > Severity: grave > Tags: security > Justification: user security hole > > Hi, > > as you may already know, a paper was published this morning describing a > vulnerability known as efail against S/MIME and PGP/MIME implementations > in various mail clients. > > This vulnerability allows an attacker with read/write access to > encrypted mail to retrieve the plaintext provided HTML mails are > enabled, as well as loading of remote content. > > The paper indicates that the PGP/MIME implementation in kmail is not > vulnerable, but the S/MIME is. > > It might be possible that the vulnerability is in an underlying library, > so feel free to reassign if needed. > > It's likely we'll have to issue a DSA for this. > > Regards, signature.asc Description: This is a digitally signed message part.
Bug#895802: libqt5widgets5: Can't select parent nodes in QTreeView
Package: libqt5widgets5 Version: 5.10.1+dfsg-5 Severity: normal Control: forwarded -1 https://bugreports.qt.io/browse/QTBUG-67724 Control: affects -1 konversation Hey, I see a behavior change with Qt 5.10 in Konversation. With 5.9.2 I could select the the parent/root nodes in Konversation(File > "Server list"). With Qt 5.10.1 this is not possible anymore. See the attached image. I can't select the line "freenode" nor "debian" with the mouse anymore. I can select the children "chat.freenode.net" and "irc.debian.org". Additionally (maybe it should be splitted to another issue) I can't collapse/uncollapse the tree anymore by clicking "v". hefee -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libqt5widgets5 depends on: ii libc6 2.27-3 ii libqt5core5a [qtbase-abi-5-10-0] 5.10.1+dfsg-5 ii libqt5gui55.10.1+dfsg-5 ii libstdc++68-20180414-1 libqt5widgets5 recommends no packages. libqt5widgets5 suggests no packages. -- no debconf information
Bug#895670: kaddressbook: Can't edit postal addresses anymore
Hey, > when I want to edit the postal-address of a person in kaddressbook or want > to add a new one the tab with the postal adress(es), in German called > "Ort", does not appear, there is only the line: "Fehlende Module. Bitte > prüfen Sie ihre Installation" (Missing modules. Check your installation.) > > Starting kaddressbook out of a terminal I get the line: > "org.kde.pim.contacteditor: error during loading contacteditor plugin : > "Die dynamische Bibliothek konnte nicht gefunden werden." > But libkf5contacteditor5:amd64 is installed (4:17.12.3-2). My resources are > vcf-files. > > Maybe I'm missing something, but an addressbook where you can't add or edit > postal addresses seems a little bit useless for me. So it would be nice, if > this feature reappeared. > > Thanks for maintaining the package. It sounds like you don't have kdepim-addons installed. Please try again with kdepim-addons installed. hefee signature.asc Description: This is a digitally signed message part.
Accepted kdepim-addons 17.12.3-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 03 Apr 2018 19:24:24 +0200 Source: kdepim-addons Binary: kdepim-addons Architecture: source Version: 17.12.3-2 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers <debian-qt-kde@lists.debian.org> Changed-By: Sandro Knauß <he...@debian.org> Description: kdepim-addons - Addons for KDE PIM applications Closes: 894587 Changes: kdepim-addons (17.12.3-2) unstable; urgency=medium . * Team upload. . [ Bas Couwenberg ] * Add Breaks/Replaces on akonadi-contacts-data (<= 4:17.08.3-2). (closes: #894587) Checksums-Sha1: ef8ab24fd15e0c1949f77fd6e6a6eb8f2bc479da 4233 kdepim-addons_17.12.3-2.dsc 6c20d3a1d94d2a2fe43f9fea1bb5910219734e68 14288 kdepim-addons_17.12.3-2.debian.tar.xz 5afba861030bbf98787fb38cef7313ac42163ec5 23913 kdepim-addons_17.12.3-2_source.buildinfo Checksums-Sha256: 9b33951aa4292f5402dea7620c6fb14adc05dc943220cff0805ea93224faf8ac 4233 kdepim-addons_17.12.3-2.dsc 4d5e12034aadec38964147f6445676e9ebb3b13a888e7891bee4d55de7762e6f 14288 kdepim-addons_17.12.3-2.debian.tar.xz 0bae6828072541bd50079c37f4a07c52b53febb4814948e5c69771f6a9dc9cde 23913 kdepim-addons_17.12.3-2_source.buildinfo Files: b148950670d17b34920b9699f9f3653b 4233 kde optional kdepim-addons_17.12.3-2.dsc a8e575b1ad68ec84fef95024b041c149 14288 kde optional kdepim-addons_17.12.3-2.debian.tar.xz 51ebc3de4f4caf374067502e7848c7ab 23913 kde optional kdepim-addons_17.12.3-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEOewRoCAWtykmSRoG462wCFBgVjYFAlrDuN8RHGhlZmVlQGRl Ymlhbi5vcmcACgkQ462wCFBgVjY/KxAAi5FYo75akEHNA4PlZsaWWxY3KxBUQWTp ut/Bc7iA6JQLjUHgDU1XN2ExbQWShAwofieNNwtgrEchrc+b7mgEgxdUPD8LWmhw v4FSL4HvwkenWAxP2GjLl8Y0bH5NBcxzNyuANsmt7czWAar/lHpgsseYuOarmMmZ HwY35c2VEHszEdABhOMf9kKhOg82xlCXVyZZPy6K1sOUcDMFL7KMGAC2kjUz+1wH Gr9fvGDKR1rCO5A/4NIy1kM6rE0jau74lcK8pHRLfVzicyYW25Y5FwXTNFA7iQPq 6YtyHf5qhrXd6valeO8gmktFE2wyxWnsk48KNN484HV5YkhWULanf9eOM8kmT7M+ mLuIRkF5pulTgojNqyAweKSvEc6FqFpaJYjtFSeFhwmkJYrbCdxf3TTelYWfOREq h7aTmtI+qOWrtWcLB2fmUU8N2JFk0GMXg6qo9xZ69vo/ABNRTW1JWSteFOgvnj3s thQbQrsCwzT5EhqOuzIWy0JscySxbgPkMSLAT27QvnFqkfBXGTh4W+p4zsmWInhM dxJMiizxNoL2SWFZZS8rLdsxcADQu4+TRkKvitt2jSjxjrwuRr80Cf77VzSADdmR hbymLLAijOi2g7Qy70PwvBF6r4slWITzUXCeBz49sCAncSLx2yLRMtNUXY1Vfuqb mSSlems7z+8= =sS1U -END PGP SIGNATURE-
Accepted meta-kde 5:100 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 01 Apr 2018 18:36:17 +0200 Source: meta-kde Binary: kde-plasma-desktop kde-standard kde-full kdeaccessibility kdeadmin kde-baseapps kdeedu kdegames kdegraphics kdemultimedia kdenetwork kdepim kdesdk kdetoys kdeutils kdewebdev kde-sc-dev-latest Architecture: source Version: 5:100 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org> Changed-By: Sandro Knauß <he...@debian.org> Description: kde-baseapps - base applications from the official KDE release (metapackage) kde-full - complete KDE Software Compilation for end users kde-plasma-desktop - KDE Plasma Desktop and minimal set of applications kde-sc-dev-latest - ensure that the latest KDE Development Platform is installed kde-standard - KDE Plasma Desktop and standard set of applications kdeaccessibility - accessibility packages from the official KDE release kdeadmin - system administration tools from the official KDE release kdeedu - educational applications from the official KDE release kdegames - games from the official KDE release kdegraphics - graphics applications from the official KDE release kdemultimedia - multimedia applications from the official KDE release kdenetwork - networking applications from the official KDE release kdepim - Personal Information Management apps from the official KDE releas kdesdk - Software Development Kit from the official KDE release kdetoys- desktop toys from the official KDE release kdeutils - general-purpose utilities from the official KDE release kdewebdev - web development apps from the official KDE release Changes: meta-kde (5:100) unstable; urgency=medium . * Team upload. . [ Pino Toscano ] * Remove kstars from kdeedu, since it is no more shipped as part of its releases. * Add minuet to kdeedu. . [ Sandro Knauß ] * Update kdepim to 17.12.3 * Remove blogilo from kdepim metapackages (dead upstream). * Use secure copyright format uri. * add lintian-override for kde-sc-dev-latest. * bump compat level to 11 (no changes needed). * Update Vcs links to salsa. Checksums-Sha1: e08fcd9c4f36d9ac5120274d2fa5487d17357361 2673 meta-kde_100.dsc 3239bf6c2a040b55b8e35b5c890573c54b7f9242 15836 meta-kde_100.tar.xz 8be5f507f139866f7db55d27127e9c77d98ca412 6511 meta-kde_100_source.buildinfo Checksums-Sha256: 0408b16223a83a09a073dbaf2289f3ec9c6007b05e4c173ff971646c95fc6461 2673 meta-kde_100.dsc b3e608f25ad96ceee4dbfd6d330a2f71809c990f568970315d63d49fc97fc7a5 15836 meta-kde_100.tar.xz c8f17ce6fed8dbe656365fbb241e27270d6894034d5c00ac251854593eada990 6511 meta-kde_100_source.buildinfo Files: aa9a9f2f92fde735af8ce15616ffa633 2673 metapackages optional meta-kde_100.dsc 621ba10d665fafb96ea3e4255058a45a 15836 metapackages optional meta-kde_100.tar.xz 3486c7f2547bc251c05a281f0d8de8d6 6511 metapackages optional meta-kde_100_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEOewRoCAWtykmSRoG462wCFBgVjYFAlrBCukRHGhlZmVlQGRl Ymlhbi5vcmcACgkQ462wCFBgVjYG/A/8CLxtue2M5rjua1IkTuygfFJurTG5gkG/ vSpyDY9DCHWe/sgVIvkMfuDJNM3vF1+yHXbSZvXsmyv8cFUlVqnyozvuhbDepuPV PgXZoh280lALfuAZDcZVuexgdL4v1pIa2hUWhWfvrlSOIdS9P0uoqHaKkEBvgHK3 qCAKejTNTSV5vCld7/yt9bV5E9KLyg0+EIWKYfknTItASoF8/GGB2FPpwBeClNI/ ApHGTko4M8K+G8Zmis+mZekQJM+n7RTnNFeJcBBcB+X9Tc+cSHQV9S4z+BTnyrj3 2W1Hk7Y8fFGJeyo7w7J8dwdo3fR+dv8NPLa+n2AYx6IpludUxrJzLypt7HeObEqR GzL804xKkKfrmoj5JswPtT3hTmooM65j7hh9P9qeqWP1zaueBEECGg0Pytf57mB2 baTpcbY06XnuMVEC+SeLzZx7/huaqLJ94ItzQsHhhgwBihx04aN5/qkylBkDvzSq 37Zog45AYnjwblX9EAQ1+xRHEZIKRXQcdfjHDQ3JrRGpArL2+hhY7V0q3JFD7PlM +MFtSgdALQl7GvknoUCOcRRU4Ze+DSdvkVEQZAB94CImYHgwhVYlnH4dQsnEubOh SNJnX3W0oeSFALMJhgV9HtMGs+a6z1sHSPLO+7BaNElTgSHY2pd6DX+i03BQp/iC sf5iab3V8Lg= =ysXc -END PGP SIGNATURE-
Accepted akonadi-contacts 4:17.12.3-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 01 Apr 2018 03:02:05 +0200 Source: akonadi-contacts Binary: akonadi-contacts-data libkf5akonadicontact-dev libkf5akonadicontact5 libkf5contacteditor-dev libkf5contacteditor5 Architecture: source Version: 4:17.12.3-2 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers <debian-qt-kde@lists.debian.org> Changed-By: Sandro Knauß <he...@debian.org> Description: akonadi-contacts-data - Akonadi contacts access library - data files libkf5akonadicontact-dev - Akonadi contacts access library - development files libkf5akonadicontact5 - Akonadi contacts access library libkf5contacteditor-dev - Akonadi contacts editor library - development files libkf5contacteditor5 - Akonadi contact editor library Changes: akonadi-contacts (4:17.12.3-2) unstable; urgency=medium . * Team upload. . [ Sandro Knauß ] * remove duplicate categories file and fix all build. Checksums-Sha1: c5820d3b9d9b02475ef5ae3e5c1f6e7ee52022f9 3432 akonadi-contacts_17.12.3-2.dsc 68001e8a4c9e573a3c0fe2827bf8f479b043fed8 14996 akonadi-contacts_17.12.3-2.debian.tar.xz b23fce2fdcce38243fd19c489c5b7716b7c3197c 23465 akonadi-contacts_17.12.3-2_source.buildinfo Checksums-Sha256: 8e2e6ad244894ed60772d56a29d2199702a45953a0c52dd2d6655fe0aabf6a68 3432 akonadi-contacts_17.12.3-2.dsc e26c44956cba7fcec2d2e1d24320d7990d74e0fe8050dabed423963e875b5033 14996 akonadi-contacts_17.12.3-2.debian.tar.xz 26855cb98628832fabf3ea620b48b7408f14999a961b23e4be8b9901bc862757 23465 akonadi-contacts_17.12.3-2_source.buildinfo Files: c758dfa73111ddc351fe450d8a941c7b 3432 libs optional akonadi-contacts_17.12.3-2.dsc 079af55a8aab65d9549a9c0ecfa09c0c 14996 libs optional akonadi-contacts_17.12.3-2.debian.tar.xz 588469198ef344cef280079060cd8133 23465 libs optional akonadi-contacts_17.12.3-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEOewRoCAWtykmSRoG462wCFBgVjYFAlrAL6URHGhlZmVlQGRl Ymlhbi5vcmcACgkQ462wCFBgVjZYzw/+OWgy6dGZzeeWu9u5MnNbXSS79Tcobo54 b/DP31xlVHFt41Jha77BOXHZ0X5KnljoXc+SEBQGmqokNOAR0pdcQKkViQqSnOHf f7LI6NtcZKdjusOErdx0La3hMPZ7/rtl3fmGu2NUYhcFDRfdReacXBN3oiRvar9A CSzj2mXNvAGiOcw5ZL7RPkm7T3AwR2NrQ1yfgNIiyuubD9ZJ4OME9i8w5LBroIrt oGZzCbKJ3TvdX9zw+c9n6kCmLHOh9ZfqdNAe405Uu5ZpWpw2oAGHjsQRuCZJW282 2Qb8oOaFT2vuxr634l7Iiu46ovP7r3KikZPq2jzXFdkSSIQTRo5d6DTB0OE7M0p1 eDxAr2dKcCUsSYseOhAfUQvIwHlokPZF75knf6Me4Ir269WZhJTBP9uc6eNXkUMF v/QqOqx3ICCtUFfYBv7EyYyyGkvUtb3PblAZdruDXo1bQ5K69PFW37S8nhTW+oQQ ojxq+Uu42R/B5klcWWBkBZbZBadazrGSUQp1L5F+NkgzGdr+xit1wLHZR3X6T1yw y+2szxuDEtLAKAUhimi6uLV8oyuzOTVeSmuosMqWnHnVnI8S6rGIMKcdtpOC8MGx MFHJASJqsCWIwjsW+t5GABl4wZHPqm77B77uNBDKN2o2YyCBK2JYOkr6L4u3TbFx 36tij4wOhl0= =j2QP -END PGP SIGNATURE-
