Re: Kadressbook and Google
On Wednesday, 8 May 2024 16:15:03 CEST Soren Stoutner wrote: > > And how else do you sync your contacts between your smartphone and KDE for > > free? I'm definitely open to good suggestions. > > In my case a host a Nextcloud instance. For Android sync, I use DAVx5. > > https://f-droid.org/en/packages/at.bitfire.davdroid/[1] Same here, except it's still (a very old) Owncloud here ;-P But I basically only use it for Contact and Calendar syncing. signature.asc Description: This is a digitally signed message part.
Re: Plasmashell crash: debugging symbols
On Tuesday, 24 October 2023 13:50:25 CEST piorunz wrote: > > Piotr didn't read/apply the whole of the Backtrace wiki page, that's their > > only 'mistake'. > > Yes, for that I am sorry. No need to apologize :) I put 'mistake' in quotes as I don't consider it a mistake, just a step in a learning process. signature.asc Description: This is a digitally signed message part.
Re: Plasmashell crash: debugging symbols
On Tuesday, 24 October 2023 10:51:46 CEST Cosmo wrote: > piorunz is so incompetent that he managed to discredit the whole of Debian > in front of one of the prominent kde project managers. Nice job Piotr didn't read/apply the whole of the Backtrace wiki page, that's their only 'mistake'. You OTOH, only sent a rude, useless and patronizing reply to this list, while making assumptions about someone's competence. If that wasn't bad enough, you also added to the upstream bug report: - a rude, useless and possibly insulting message to the upstream maintainer - instructing them to update the *community* *wiki* page wrt Debian - assuming Nathan is unfamiliar with Debian "you, Mr. Graham, who doesn't know Debian at all" (another assumption, formulated quite rudely) - while you're factually incorrect (the KDE wiki links to the Debian wiki page with all the needed info) So if anything, YOU have discredited Debian. Please refrain from doing such things in the future. signature.asc Description: This is a digitally signed message part.
Re: Plasmashell crash: debugging symbols
On Tuesday, 24 October 2023 13:16:18 CEST piorunz wrote: > On 24/10/2023 12:03, Grzegorz Szymaszek wrote: > > On Tue, Oct 24, 2023 at 11:57:46AM +0100, piorunz wrote: > >> This KDE guideline should definitely be improved: > >> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_u > >> seful_crash_reports#Debian > >> > >> It doesn't say anything about additional debugging repository available > >> in Debian! [...] > > > > "See also the Debian document on How to get a Backtrace." links to > > https://wiki.debian.org/HowToGetABacktrace > > Thanks! This is my fault entirely for missing this. The KDE guideline links to that Debian wiki page. The only thing that could be improved is: 's/-dbg/-dbgsym/g' signature.asc Description: This is a digitally signed message part.
Re: Plasmashell crash: debugging symbols
On Monday, 23 October 2023 20:19:42 CEST piorunz wrote: > Can anyone tell me, how to obtain debugging symbols for KDE, so I can > backtrace a crash with debugger properly? I use Debian Stable. Thank you. Add the following line to your /etc/apt/sources.list and do `apt update` deb http://debug.mirrors.debian.org/debian-debug bookworm-debug main non-free-firmware Then you will find the dbgsym packages. > #2 0x7fe7678a8e9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + > 0x4e9b) With `apt-file search libKF5Crash.so.5` you'll find it belongs to the libkf5crash5 package and then do `aptitude search libkf5crash5` and you should find a package with a `-dbgsym` suffix and you install that package. Repeat that for all the libraries in your stacktrace and when you then generate a new stacktrace, it should contain all the info you want/need. HTH, Diederik signature.asc Description: This is a digitally signed message part.
Re: Question about Plasma 5.27.5 and Frameworks 5.106
On Friday, 19 May 2023 13:11:01 CEST Luc Castermans wrote: > I just upgraded the machine which was messed up earlier, fixed later, using: > > aptitude install -t experimental '~i ~V5\.27\.2' > aptitude install -t experimental '~i ~V5\.103\.0' I hadn't upgraded to those packages, but earlier today I did reboot my laptop and when I logged in, my desktop was completely blank and no longer had the icons and plasma widgets I had on them. After doing `aptitude safe-upgrade '~i~V5\.27\.2' -t experimental` and another reboot (maybe a logout/login would be sufficient; we'll never know), I had my normal desktop back. I haven't yet tried upgrade Frameworks, but the Plasma package update definitely fixed an issue on my laptop. Cheers, Diederik signature.asc Description: This is a digitally signed message part.
Re: Question about Plasma 5.27.5 and Frameworks 5.106
On Friday, 19 May 2023 09:19:31 CEST Martin Steigerwald wrote: > % aptitude install -t experimental '~i ~V5\.27\.2' You can use 'safe-upgrade' instead of 'install' signature.asc Description: This is a digitally signed message part.
Re: Question about Plasma 5.27.5 and Frameworks 5.106
On Friday, 19 May 2023 10:09:56 CEST Aurélien COUDERC wrote: > Also if people here could find the time to try and mix some .2 and .5 > packages and report back, that would be useful to confirm it doesn't break > more than it fixes. In particular mixing core components like kwin, > libkscreen, plasmas workspace/desktop would be interesting tests. If you have an exact list of packages + versions, I can test those exact combinations (which seems more useful then a random mix). signature.asc Description: This is a digitally signed message part.
Bug#1034679: libkf5coreaddons5: Prints debug info to stdout (when using `gitk`)
Package: libkf5coreaddons5
Version: 5.103.0-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm not sure exactly when it started happening, but lately when I run
`gitk` I get a whole bunch of what I consider debug info printed in my
Konsole window:
diederik@prancing-pony:~$ gitk
arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi
kf.coreaddons: Checking for plugins in ("/usr/bin/kf5/kio",
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_file.so"
supports protocols ("file")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_ftp.so"
supports protocols ("ftp")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_ghelp.so"
supports protocols ("ghelp")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_help.so"
supports protocols ("help")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_http.so"
supports protocols ("http", "https", "webdav", "webdavs")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_remote.so"
supports protocols ("remote")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_trash.so"
supports protocols ("trash")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/metainfo.so"
supports protocols ("metainfo")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_bluetooth.so"
supports protocols ("bluetooth")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_obexftp.so"
supports protocols ("obexftp")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/baloosearch.so"
supports protocols ("baloosearch")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/tags.so" supports
protocols ("tags")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/timeline.so"
supports protocols ("timeline")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/applications.so"
supports protocols ("applications", "programs")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/desktop.so"
supports protocols ("desktop")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_fonts.so"
supports protocols ("fonts")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/ldap.so" supports
protocols ("ldap", "ldaps")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/akonadi.so"
supports protocols ("akonadi")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_kamera.so"
supports protocols ("camera")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kdeconnect.so"
supports protocols ("kdeconnect")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/about.so" supports
protocols ("about")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/activities.so"
supports protocols ("activities")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/archive.so"
supports protocols ("ar", "sevenz", "tar", "zip")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/bookmarks.so"
supports protocols ("bookmarks")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/filter.so" supports
protocols ("bzip", "bzip2", "gzip", "lzma", "xz", "zstd")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/fish.so" supports
protocols ("fish")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/info.so" supports
protocols ("info")
kf.kio.core:
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_filenamesearch.so" supports
protocols ("filenamesearch")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/man.so" supports
protocols ("man")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/mtp.so" supports
protocols ("mtp")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/nfs.so" supports
protocols ("nfs")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/recentdocuments.so"
supports protocols ("recentdocuments")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/recentlyused.so"
supports protocols ("recentlyused")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/sftp.so" supports
protocols ("sftp")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/smb.so" supports
protocols ("cifs", "smb")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/thumbnail.so"
supports protocols ("thumbnail")
kf.kio.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_msits.so"
supports protocols ("ms-its")
kf.kio.core: Loading deprecated protocol file, please port it to JSON metadata
"/usr/share/kservices5/ksvn+file.protocol"
kf.kio.core: Loading deprecated protocol file, please port it to JSON metadata
"/usr/share/kservices5/ksvn+http.protocol"
kf.kio.core: Loading deprecated protocol file, please port it to JSON metadata
"/usr/share/kservices5/ksvn+https.protocol"
kf.kio.core: Loading deprecated protocol file, please port it to JSON metadata
"/usr/share/kservices5/ksvn+ssh.protocol"
kf.kio.core: Loading deprecated protocol file, please
Re: Postpone update
On Wednesday, 12 April 2023 13:18:46 CEST Martin Steigerwald wrote: > There are issues with Plasma with most recent Qt 5.15.8+dfsg-6. I am > aware of the following two: > > 1) Screen cannot be locked. After locking screen desktop is basically > frozen but still shown. > > 2) Krunner segfaults, thus neither Alt-Space and in case still configure > Alt-F2 will work. > > There may be other issues. When I put my system to 'sleep' and then wake up again, I can't (really) interact with my system anymore and I have to do "Ctl+Alt+Backspace" which I think just kills the X server and then I can login again via sddm. signature.asc Description: This is a digitally signed message part.
Re: Okular locked up my system and left no evidence
On Friday, 10 February 2023 07:46:36 CET Borden wrote: > which may be more productive. What would be even more productive is the following: - log in remotely before doing another test and open a screen/tmux session (or open several distinct remote logins) and start: - htop - tail -f ~/.xsession-errors - journalctl --user -b -f - any other program which may be useful IYO Then start okular from Konsole, but give it a lower priority with `nice` (and `ionice`). Possibly useful to `tee` the Konsole output to a file too. If it behaves so bad again, you should be able to kill okular (f.e.). And then file a bug report with a sample PDF as Alex suggested and provide any info you obtained which may help to solve this issue. You didn't specify which Debian and Okular version you had this issue with. In case of Testing or Sid, the "/topic" from #debian-next comes to mind: "testing → bookworm | you may need to debug sometimes | ..." signature.asc Description: This is a digitally signed message part.
Re: Plasma 5.27 beta (5.26.90) coming to unstable
On Wednesday, 25 January 2023 10:47:54 CET bagattin jerome wrote:
> I have the following error when I try to launch tileseditor
> (META+T): janv. 25 08:18:54 debian kwin_wayland_wrapper[952]: Failed to
> load QUrl("file:///usr/share/kwin/effects/tileseditor/qml/main.qml"):
> (file:///usr/share/kwin/effects/tileseditor/qml/main.qml:15:1:
That is in kwin-data ...
> module "org.kde.KWin.Effect.WindowView" is not installed
>
> I can't find org.kde.KWin.Effect.WindowView module,
> I certainly miss something or dependencies are missing ?
... but this one doesn't seem to exist according to `apt-file search`.
My guess is that it's in KWin's upstream src/effects/windowview/ directory.
signature.asc
Description: This is a digitally signed message part.
Re: Plasma 5.27 beta (5.26.90) coming to unstable
On Tuesday, 24 January 2023 14:53:29 CET Diederik de Haas wrote: > > Ah, held back due to libkf5screen7 still at 4:5.26.5-1 > > FWIW: kscreen version 4:5.26.90-1 (now) depends on libkf5screen8 > > I did not have libkf5screen7 installed, even though I do have kscreen > installed. What seems odd is that kscreen is now at version 4:5.26.90-1, but > libkf5screen8 is not installed or available ... > while it is a depends (>= 4:5.26.90) ?!? > > So far everything seems to be working fine here \o/ Just did the upgrade on my laptop and libkf5screen7 was replaced by libkf5screen8 and also on my laptop everything seems to work fine \o/ signature.asc Description: This is a digitally signed message part.
Re: Plasma 5.27 beta (5.26.90) coming to unstable
On 24 January 2023 22:09:49 CET, "Miguel A. Vallejo" wrote: >My apt only finds version 5.26.90-1 > >Am I doing something wrong? Nope. That is the version number of the beta as also mentioned in Subject
Re: Plasma 5.27 beta (5.26.90) coming to unstable
On Tuesday, 24 January 2023 11:58:25 CET Martin Steigerwald wrote: > Ah, held back due to libkf5screen7 still at 4:5.26.5-1 FWIW: kscreen version 4:5.26.90-1 (now) depends on libkf5screen8 I did not have libkf5screen7 installed, even though I do have kscreen installed. What seems odd is that kscreen is now at version 4:5.26.90-1, but libkf5screen8 is not installed or available ... while it is a depends (>= 4:5.26.90) ?!? So far everything seems to be working fine here \o/ Cheers, Diederik signature.asc Description: This is a digitally signed message part.
Re: Careful with dist-upgrade in unstable at the moment
On Thursday, 22 December 2022 14:31:38 CET Martin Steigerwald wrote: > > On Wednesday, 21 December 2022 11:42:17 CET Diederik de Haas wrote: > > > I think they above quoted script is absolutely horrific. > > > > I made that statement for 2 reasons: > > 1) It tries do a dist-upgrade 'at all cost' (imo ofc) > > 2) `dpkg --set-selection` completely messes up APT's 'database' wrt > > manually and automatically installed packages ... which in turn > > causes the need to full-/dist-upgrade. > > I made no statement at all about this script. So in case you were > assuming that I somehow intended to justify it, That was not my intention. Sorry if I made it appear that way. If I want to address an issue to someone personally, I'd put that person in the To: field, like I have done now. If I want to address the 'general public', I sent it to the list. The `dpkg --set-selection` command imo 'messes up' the packages state as it they all get marked as manually installed and therefor it was for me related to what I said above that in my previous mail. signature.asc Description: This is a digitally signed message part.
Re: Careful with dist-upgrade in unstable at the moment
On Thursday, 22 December 2022 09:16:50 CET Martin Steigerwald wrote: > > I find it way easier to have apt reduce the problem riskless first. > > It's a shorter list of actions to review. > > Good argument. My argument is that in the usual situation trying "apt > full-upgrade" first will save me one command. With "apt upgrade" I often > enough would have to use "apt full-upgrade" afterwards. IMO that indicates that the 'state' of your packages could be improved. I *rarely* have to do a full-upgrade to get things fully upgraded. And when not all packages get upgraded, that usually means something 'special' is going on, like now with the Qt transition. On Wednesday, 21 December 2022 11:42:17 CET Diederik de Haas wrote: > I think they above quoted script is absolutely horrific. I made that statement for 2 reasons: 1) It tries do a dist-upgrade 'at all cost' (imo ofc) 2) `dpkg --set-selection` completely messes up APT's 'database' wrt manually and automatically installed packages ... which in turn causes the need to full-/dist-upgrade. Run the following command and mark as automatically installed all those you don't need to have marked as manually installed: $ aptitude search '?narrow(~i!~M~n^lib,!~essential!~prequired)' That command finds all packages which are marked as manually installed, have a name which starts with 'lib' and are not of priority essential or required. HTH signature.asc Description: This is a digitally signed message part.
Re: Careful with dist-upgrade in unstable at the moment
On Wednesday, 21 December 2022 11:01:07 CET Sedat Dilek wrote:
> P.S.: If you are Debian/unstable AMD64 user and are experienced
> enough, you can try on YOUR OWN RISK.
>
> To pass daily dist-upgrades I did the following:
>
> [ Set all QT v5.15.6 packages on hold ]
> root# VER="5.15..6" ; for p in $( dpkg -l | grep $VER | awk '/^ii/
> {print $2}' ) ; do echo "[ $p ]" ; echo "$p" "hold" | dpkg
> --set-selections ; done
I must be sounding like a broken record player (by now), but:
Stop using *dist-*upgrade by DEFAULT.
And apparently it's (also) needed to say that apt/apt-get/aptitude tells you
what it's about to do. If it's telling you that it'll remove (almost) all of
KDE and you don't want that, you can say 'No' and not go through with that.
The normal/safe-upgrade is what you should be using by default and only when
you want to force something, you'd do a dist-/full-upgrade and then you
evaluate what it's about to do and when you think "Yes, that's what I want",
then and only then you go through with it.
I think they above quoted script is absolutely horrific.
My 0.02
signature.asc
Description: This is a digitally signed message part.
Re: kded5 crashes
On Wednesday, 7 December 2022 11:49:21 CET luca.pedrielli wrote: > i removed apper and things seems to be better. > waiting for confirmation from the other guys too. I didin't have apper installed to begin with, so maybe that's why I wasn't seeing it? > now only plasmashell crashes ;) > ... > #1 0x7f488f65aef2 raise (libc.so.6 + 0x3bef2) > #2 0x7f4891a93be1 > _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5be1) > #3 0x7f488f65af90 n/a (libc.so.6 + 0x3bf90) > #4 0x7f4882a1c158 n/a (vmwgfx_dri.so + 0x61c158) > #5 0x7f4882a1c343 n/a (vmwgfx_dri.so + 0x61c343) > #6 0x7f4882dcbcad n/a (vmwgfx_dri.so + 0x9cbcad) > #7 0x7f4882575083 n/a (vmwgfx_dri.so + 0x175083) > #8 0x7f48824b0a23 n/a (vmwgfx_dri.so + 0xb0a23) > #9 0x7f48824b40cc n/a (vmwgfx_dri.so + 0xb40cc) > #10 0x7f48898f9104 n/a (libGLX_mesa.so.0 + 0x43104) > #11 0x7f48898e2a38 n/a (libGLX_mesa.so.0 + 0x2ca38) > #12 0x7f488ce49ccc n/a (libGLX.so.0 + 0x4ccc) dri, GLX and mesa all point to graphics subsystem, so it's probably useful to share the GPU that you're using. signature.asc Description: This is a digitally signed message part.
Re: kded5 crashes
On Tuesday, 6 December 2022 13:45:40 CET Miguel A. Vallejo wrote: > Since a few days ago I've been experiencing problems with KDE in a > fully upgraded Sid. > > The symptoms are always the same: kded5 crashes a few minutes after > boot and then icons from no KDE programs (like Telegram) disappears > from the system tray. > > A lot of errors in syslog from plasmashell, kwin_x11 and kded5 itself. > Any ideas? It looks like I'm not having those issues, but your report did prompt me to look in syslog ... and that looks like KDE's debug log?!? # tail -n30 /var/log/syslog 2022-12-07T01:44:35.502916+01:00 prancing-pony plasmashell[9550]: kf.sonnet.clients.hunspell: isCorrect : "debug" 2022-12-07T01:44:35.503214+01:00 prancing-pony plasmashell[9550]: kf.sonnet.clients.hunspell: result : true 2022-12-07T01:44:35.503469+01:00 prancing-pony plasmashell[9550]: kf.sonnet.clients.hunspell: isCorrect : "log" 2022-12-07T01:44:35.503814+01:00 prancing-pony plasmashell[9550]: kf.sonnet.clients.hunspell: result : true 2022-12-07T01:44:36.222321+01:00 prancing-pony kwin_x11[1152]: kwin_tabbox: == "Alt+Tab" or "Alt+Shift+Backtab" 2022-12-07T01:44:36.313043+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:36.581574+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:40.218135+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:41.013394+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:43.030635+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:43.063486+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:43.414862+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:43.511189+01:00 prancing-pony kglobalaccel5[15433]: org.kde.konsole: Undecodable sequence: CSI >4;m 2022-12-07T01:44:43.511966+01:00 prancing-pony kglobalaccel5[15433]: org.kde.konsole: Undecodable sequence: CSI >4;m 2022-12-07T01:44:43.605965+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:44.554500+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:46.121951+01:00 prancing-pony kernel: [75486.661010] rmi4_f12 rmi4-00.fn12: Failed to read object data. Code: -6. 2022-12-07T01:44:46.830757+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:47.562204+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:47.937241+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:48.066014+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:48.207457+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:48.955986+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:49.223484+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:49.510930+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:50.131426+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:50.195366+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:51.078386+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:51.250778+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:51.616006+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event I don't think that's supposed to happen? signature.asc Description: This is a digitally signed message part.
Re: Thank for your the ambitious plan for Bookworm
On Wednesday, 23 November 2022 16:56:43 CET Aurélien COUDERC wrote:
> >That indeed looks quite good :-)
> >Please do inform the Release Team about it (even if it's not 100% final).
>
> Ah yes, I still havn't do that.
> What's best ? Filing a pre-approval bug ?
I don't know tbh, best to ask to the Release Team directly.
But the important/'critical' thing is that they are aware of it ('at all').
And the sooner the better so that they can take these things into account and
it also give 'you' and the RT more wiggle room, if needed.
So just start the dialog and when things need to be made 'official', they'll
tell you and how (I presume).
Cheers,
Diederik
signature.asc
Description: This is a digitally signed message part.
Re: Thank for your the ambitious plan for Bookworm
On Saturday, 12 November 2022 11:50:53 CET Martin Steigerwald wrote: > Dear Debian/Kubuntu Qt/KDE team developers, > > thank you dearly for the ambitious plan you set out in: > https://wiki.debian.org/PkgQtKde/BookwormReleasePlans That indeed looks quite good :-) Please do inform the Release Team about it (even if it's not 100% final). > In case you'd like some of us to test something from experimental at > some time, just let us know. Indeed. Happy to help here! signature.asc Description: This is a digitally signed message part.
Re: Any way to prevent Konqueror starting every time after KDE login?
On vrijdag 28 oktober 2022 06:58:45 CEST local10 wrote: > there was no Konqueror window open when I was logging out of KDE Check if there's still a konqueror process running and kill that before logging out. Does that 'fix' it? signature.asc Description: This is a digitally signed message part.
Re: Plasma 5.26 coming to unstable - Thank you!
On zondag 16 oktober 2022 14:00:52 CEST Aurélien COUDERC wrote: > Now that the login screen bug seems to be fixed for everyone, I'd like to > strongly recommend everyone who switched to the breeze SDDM theme due to > the bug to switch back to debian-breeze. > > Debian-breeze is the default that our users will see and we need to get it > as much exposure as possible before it reaches testing. I can confirm that the issue is fixed. In the "Login Screen (SDDM)" System Settings screen, I do not have a preview though, while (just) "Breeze" does. (I also have a "Debian Maui" and _another_ (?) "Debian Breeze" theme in that screen and both don't have a preview either) HTH, Diederik signature.asc Description: This is a digitally signed message part.
Re: Plasma 5.26 coming to unstable - Thank you!
On vrijdag 14 oktober 2022 20:36:44 CEST Aurélien COUDERC wrote: > >Should the following be added to that file for the tiny char issue? > >fontSize=10 > > I dont know but fixing the wallpaper path also fixes the font size for me so > I'd prefer not touching anything else if not required. I did not expect that. I hadn't checked it myself (yet) though. > In any case I've uploaded plasma-workspace 4:5.26.0-2 with the fix and I've > synchronised the theme conf file with the upstream one as you suggest. Thanks! signature.asc Description: This is a digitally signed message part.
Re: Plasma 5.26 coming to unstable - Thank you!
On Friday, 14 October 2022 14:49:01 CEST Aurélien COUDERC wrote: > Alternatively you can add the following line : > background=/usr/share/desktop-base/active-theme/login/background.svg > > at the end of this file : > /usr/share/sddm/themes/debian-breeze/theme.conf > > until the package is fixed. Thanks. > > >the password chars were REALLY tiny. I could still login though. Should the following be added to that file for the tiny char issue? fontSize=10 Diffing the theme.conf files also showed this item: needsFullUserModel=false But I have no idea what that is for (and thus whether it's needed). signature.asc Description: This is a digitally signed message part.
Re: Plasma 5.26 coming to unstable - Thank you!
On Wednesday, 12 October 2022 17:07:35 CEST Joe McEntire wrote: > I noticed the very tiny lettering too, switched themes from debian breeze to > just breeze and swapped background to homewold and all is well. That was an interesting hint ... I switched (too) from Debian Breeze to just Breeze, logged out and everything was normal again. I then switched back to Debian Breeze, logged out and I no longer had a background (image) and the letters were tiny again. So for now I've switched back to (just) Breeze. signature.asc Description: This is a digitally signed message part.
Re: Plasma 5.26 coming to unstable - Thank you!
On Wednesday, 12 October 2022 11:07:05 CEST Sedat Dilek wrote: > No background wallpaper in SDDM (white background) - only visible is > the box where I can type my password. I did have a background wallpaper in SDDM, but the password chars were REALLY tiny. I could still login though. signature.asc Description: This is a digitally signed message part.
Re: plasma 5.25 / PIM 22.04
On Monday, 20 June 2022 13:10:45 CEST Diederik de Haas wrote: > - I had created a Filter rule, to filter out all the crypto spam. That rule > seems to be gone now (and possibly others; I only have the rules from the > Anti-Spam wizard left). And now I get the attached popup every time I start > Kontact/KMail and I don't see how I can do something useful with it. The rule is gone, but I also no longer get the popup :-) The problem was initially not just present directly after upgrade or after the first reboot, but later on. I have no idea what made it go away, but I'm glad it did. If needed, I can recreate the filter rule. signature.asc Description: This is a digitally signed message part.
Re: plasma 5.25 / PIM 22.04
On Sunday, 19 June 2022 19:43:47 CEST Diederik de Haas wrote: > I was now able to install kdepim-addons again. Since I did that/those upgrade(s), I noticed 2 things: - Before, when I logged into my KDE session I always got a request for my KWallet password and when I then opened Kontact/KMail, I didn't get asked (again) as it had access to passwords it needed. After, I don't get asked on KDE session login, but when actually starting Kontact/KMail. Not problematic, just different. - I had created a Filter rule, to filter out all the crypto spam. That rule seems to be gone now (and possibly others; I only have the rules from the Anti-Spam wizard left). And now I get the attached popup every time I start Kontact/KMail and I don't see how I can do something useful with it. FTR: I didn't blank out account names; the list is just empty. So it seems to be aware that there is/was such a (custom) filter, but otherwise it seems to be gone? signature.asc Description: This is a digitally signed message part.
Re: plasma 5.25 / PIM 22.04
On Friday, 17 June 2022 08:04:58 CEST Patrick Franz wrote: > I was planning to upload KDE PIM 22.04.2 very soon (maybe this weekend > already). And that of course will then be build against Qt 5.15.4. Thanks for that update :-) I was now able to install kdepim-addons again. signature.asc Description: This is a digitally signed message part.
Re: plasma 5.25
On Thursday, 16 June 2022 07:40:07 CEST Aurélien COUDERC wrote:
> Le 16 juin 2022 07:31:39 GMT+02:00, Luc Castermans
a écrit :
> >Yesterday I was able to install Plasma 5.25 from Experimental. All good
> >sofar.
>
> good to know, thanks for the feedback.
>
> There's an ongoing Qt 5 transition so I won't upload to unstable just now to
> avoid it and the Plasma transition stepping onto each other's toes.
I seem to have run into an issue:
# aptitude install kdepim-addons libkpimitinerary5 -t experimental
The following NEW packages will be installed:
kdepim-addons libkpimitinerary-data{a} libkpimitinerary5{b}
libkpimpkpass5{a} libphonenumber8{a}
0 packages upgraded, 5 newly installed, 0 to remove and 176 not upgraded.
Need to get 2,690 kB of archives. After unpacking 13.9 MB will be used.
The following packages have unmet dependencies:
libkpimitinerary5 : Depends: qtdeclarative-abi-5-15-2 which is a virtual
package, provided by:
- libqt5qml5 (5.15.2+dfsg-10), but 5.15.4+dfsg-3
is installed
- libqt5qml5 (5.15.2+dfsg-6), but 5.15.4+dfsg-3
is installed
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) kdepim-addons [Not Installed]
2) libkpimitinerary5 [Not Installed]
In a prior upgrade step, I removed those packages, assuming I'd be able to
install them later, but it looks like some/most packages are compiled against
qtdeclarative-abi-5-15-4, but others against qtdeclarative-abi-5-15-2 ?
signature.asc
Description: This is a digitally signed message part.
Re: Akonadi using 100% CPU resources
On vrijdag 15 april 2022 12:10:55 CEST piorunz wrote: > You mean I can install them manually, and they will stay as manually > installed? Manually installed applications, or applications marked as such, are (at least with aptitude) treated differently. > So only akonadi-server* kaddressbook* kde-standard* kdepim-runtime* > kmail* knotes* korganizer* task-kde-desktop* will be gone effectively? When you installed task-kde-desktop, that installs 'the whole bunch' and apparently several of them you don't want. All the parts were automatically installed, so removing one would remove task-kde-desktop which removes them all again. So by choosing (i.e. explicitly installing (thus 'manually')) a narrower focused meta package and/or marking the applications that you do want as manually installed, then removing task-kde-desktop (or kmail f.e.) will not remove the whole bunch. > Shouldn't I have task-kde-desktop installed to track all packages > required by entire KDE? So my Testing system evolves with changing deps? You don't want to have all packages that are part of task-kde-desktop, so that (meta) package was the wrong choice for you. Each application *should* have their own (versioned) dependencies, so you don't need task-kde-desktop for that. It's not always 100% smooth though, but that's the consequence of running Testing. Often when 'disruptions' are expected, someone posts a message to this list saying so. Technically speaking they are bugs that should be fixed. HTH, Diederik signature.asc Description: This is a digitally signed message part.
Re: Akonadi using 100% CPU resources
On vrijdag 15 april 2022 12:40:34 CEST Martin Steigerwald wrote: > KRunner module my trigger starting Akonadi I think contact search is enabled by default, so that could be it. signature.asc Description: This is a digitally signed message part.
Re: Can't sign pdf documents with Okular in Debian
On Monday, 21 March 2022 13:16:17 CET Adriano Vilela Barbosa wrote: > I'm running Debian Testing ... > Last night an update came along which brought libpoppler from version > 20.09 to version 22.02. However, nothing changed after the update: > I'm still unable to sign pdfs. > > So, I wonder if anybody here is able to sign pdfs using Okular in > Debian and, if so, what's required to get that working. https://tracker.debian.org/news/1312522/accepted-okular-421123-2-source-into-unstable/ A rebuild of Okular was needed to enable that functionality and earlier today the above update was done, so it should work with okular version 4:21.12.3-2. signature.asc Description: This is a digitally signed message part.
Re: Plasma 5.24 coming to testing
On donderdag 17 maart 2022 13:55:59 CET Gregorio Rodrigo wrote: > I am facing a small bug/problem/new feature. I use a left handed mouse but > the configuration is not saved every time I plug/unplug the mouse. It was > working before the upgrade (left handled with the mouse, right handled with > the touch mouse). Then file a bug report for it. (I don't know against which package though) A new (upstream) version typically brings new features, bugfixes AND new bugs. By reporting them, they can be addressed. signature.asc Description: This is a digitally signed message part.
Re: Plasma 5.24 coming to testing
On woensdag 16 maart 2022 23:03:03 CET Borden wrote: > Is it safe to upgrade in testing yet? There are dozens of packages in the > update queue and I'm afraid to hit dist-upgrade after the previous Plasma > upgrade hobbled my computer for over a month. A quick look at man:/apt didn't show a '-s' from simulate being present, but if you have aptitude installed, I know it supports that. But 'even' apt upgrade should ask for a confirmation before doing an actual upgrade. So if that looks sane, then go for it. If it doesn't, then don't. And maybe stop using dist-upgrade by default? The normal (safe-)upgrade is most of the time all you need. HTH, Diederik signature.asc Description: This is a digitally signed message part.
Plasma 5.24 coming to Bookworm/testing
Hi, On the 14h apt update 'round' I noticed the following packages became available: bluedevil drkonqi kactivitymanagerd kde-config-sddm kgamma5 kinfocenter kmenuedit konsole konsole-kpart kscreen ksshaskpass kwayland-integration kwrited layer-shell-qt libkf5baloowidgets-bin libkf5baloowidgets5 libkf5screen-bin libkf5screen7 liblayershellqtinterface5 libokular5core9 libpam-kwallet-common libpam-kwallet5 libssh2-1 milou okular okular-extra- backends plasma-disks plasma-nm plasma-pa polkit-kde-agent-1 yakuake Which is ~ 30 packages, but the whole of 5.24 is 100+ IIRC, so only a part has transitioned to testing now. So doing an (full-)upgrade *now* is probably not a good idea. Wait a few days or when it looks like all packages are available to prevent getting a version mismatch and any problems that may arise from it. Unless you know how to deal with potential problems and want to see if you can potentially help improve things, then now could be a good time to break your installation and help figuring out how to fix it ;-) Cheers, Diederik signature.asc Description: This is a digitally signed message part.
Re: Plasma 5.24 coming to unstable
On Sunday, 27 February 2022 16:41:28 CET Patrick Franz wrote: > > Thanks for the advice, but too late for me: my KDE is broken now. > > You should ideally warn one or two days before packages are uploaded. > > I disagree with having to give a warning 2 days in advance. If you run > unstable, you should read mailing-lists, hang around in IRC and/or > install apt-listbugs. On top of that, if you don't have the capacity to fix a broken Sid system, you shouldn't be running Sid. Running Sid is a great way to learn more about your system and if it breaks, figuring out how to fix it yourself is the most useful thing. If you need help, feel free to post your question(s) here and others may try to help. Packaged get uploaded to Sid all the time, so it should be fully expected and any announcement is courteous, but imo unneeded. signature.asc Description: This is a digitally signed message part.
Bug#1005134: Adding fwupd and plasma-discover-backend-fwupd as default packages to install on KDE to prompt the user for firmware updates
On 07 Feb 2022 17:36:53 + mYnDstrEAm wrote: > Please add fwupd and plasma-discover-backend-fwupd as a default package https://bugs.debian.org/1003973 is a/the bug where default installation of fwupd is discussed. > included on Debian12/KDE. This would make "Discover" show available firmware > updates. There would be a tray notification about available updates on KDE > and updating firmware can be integrated into the updating process. The plasma-discover-backend-fwupd package is already a suggest of plasma-discover, so possibly a recommends instead is requested here? I'll leave that and a possible reassignment of this bug up to the maintainers, but please don't make too hard to install KDE without discover. signature.asc Description: This is a digitally signed message part.
Bug#961551: partitionmanager: Does not start - "Session bus not found"
On Tuesday, 25 January 2022 21:56:06 CET scott092...@aol.com wrote: > I just now ran partitionmanager from the terminal, and as usual, got no info > in the displayed window. > > Here is the terminal output: > > > scott@ASUS-Prime-B350MA:~$ partitionmanager > Could not load plugin for core backend "" : "The shared library was not > found." Loaded backend plugin: "pmsfdiskbackendplugin" At this point you should've gotten a prompt by PolicyKit (KDE Agent) for your (user) password and after that, you should've seen: > "Using backend plugin: pmsfdiskbackendplugin (1)" And after that you should see your partitions loaded in the GUI. So maybe you're missing a required program? I don't know which, but check whether you have 'udisks2' and/or 'policykit-1' installed. Cheers, Diederik BTW: it looks like it's not properly responding to the 'Cancel' button and a failed 'login' attempt brings back the password dialog. Endlessly AFAICT. After (way?) more then 5 attempts for each, the only way out appears to be to provide the correct password. I'd say that's a bug too, but a different one. signature.asc Description: This is a digitally signed message part.
Bug#1004204: libqt5webenginecore5: Fails to upgrade to Sid version
Control: severity -1 important On Saturday, 22 January 2022 19:02:27 CET Elijah wrote: > pkg-deb (subprocess): decompressing archive > '/var/cache/apt/archives/libqt5webenginecore5_5.15.8+dfsg-1_amd64.deb' > (size=39497412) member 'data.tar': lzma error: compressed data is corrupt What happens if you delete that file and do a new apt update && apt upgrade? On my Sid system the upgrade to 5.15.8+dfsg-1 was successful, so downgrading the severity to important. signature.asc Description: This is a digitally signed message part.
Bug#999451: kwin-x11: drawing windows is delayed making reading and typing tedious
Hi Paul, On Thursday, 11 November 2021 14:56:29 CET Paul Gevers wrote: > Nice screenshot. For the record, that hint wasn't there on my system. > The other settings are the same, minus I have "OpenGL 2.0" as "Rendering > backend". It was my assumption that you (and others) didn't get that hint, otherwise you (and others) would (very) likely have mentioned it. The hint I got explains why the setting was/got disabled, without people recollecting that they had disabled it and that's why I shared it :-) Cheers, Diederik signature.asc Description: This is a digitally signed message part.
Bug#998203: yakuake's icon does not come in mate notification area
On Monday, 1 November 2021 11:57:52 CET shirish शिरीष wrote: > Because there is no notification, it is difficult to know when Yakuake > has started or not. AFAIK it's always started as soon as you log in. I would actually find an item in the notification area/systray a regression/bug as it's meant to be out of your way/sight, but available when you need it (via F12 by default). It could be that it does actually put out a notification via the notification system (ie a 'popup'), but I have disabled that as I found even that annoying. So the answer to 'when is it available?' is: Always. signature.asc Description: This is a digitally signed message part.
Bug#998203: yakuake's icon does not come in mate notification area
On Sunday, 31 October 2021 23:42:13 CET shirish शिरीष wrote: > I am running yakuake on Debian-mate. But it seems that in the > notification area for some reason yakuake is not seen :( . Sharing a > screenshot of the notification area. I'm running fully KDE and I don't have a notification entry for yakuake and in System Tray Settings there isn't an entry for yakuake either, so I'm inclined to think it's working as intended. Konsole doesn't have an entry either. If I'm misunderstanding your bug report, can you clarify what you think you are missing? signature.asc Description: This is a digitally signed message part.
Re: Plasma 5.23 upload to unstable is complete
On Sunday, 17 October 2021 00:24:47 CEST Patrick Franz wrote: > * A minor hiccup seems to be that the keybinding for KRunner (Alt+F2/ > Alt+Space) seems to have been lost as the option appears twice in > systemsettings. But you can easily restore the default setting for the > keybinding in the settings. I also lost all my custom keybinding (Win+T=Konsole f.e.), but I've been able to set them again. With a previous upgrade I lost my keyboard shortcut for the Application Launcher (just the Win key) and I wasn't able to set it back myself. But for a completely unknown reason to me, at some point that keyboard shortcut was set to Win again. I've now lost it again and I don't know how to set it back to just the Win key. Does anyone know how to set it to just the Win key? Cheers, Diederik signature.asc Description: This is a digitally signed message part.
Re: Plasma 5.23 25th Annivery Release coming to unstable
On Friday, 15 October 2021 05:37:18 CEST Patrick Franz wrote: > Unfortunately, the upload is not complete and upgrading only half of the > packages can leave Plasma in an unusable state. Yep ;-P After installing (also) the updates from the 08:00 (CEST) repo update round, it worked again *for me* (afaict). But as Martin said, it's called Unstable for a reason ;) Cheers, Diederik signature.asc Description: This is a digitally signed message part.
Re: Plasma 5.23 25th Annivery Release coming to unstable
On Thursday, 14 October 2021 19:16:46 CEST Martin Steigerwald wrote: > > The best way to do that is not using *dist*-upgrade but the > > normal/safe- upgrade method ... > > Sometimes dist upgrade might be necessary as new packages are introduced > or old ones are removed. Trying dist upgrade also often gives a good > indication whether the builds are complete. IME it's *rarely* needed. Normally aptitude safe-upgrade installs and removes packages as needed. There is a common (?) misconception that it doesn't do that. What it does not, is remove packages that are marked as *manually* installed because that indicates that you (apparently) had a reason to explicitly install it. If "aptitude search '~i!~M'" returns (many) packages that you don't think should be marked as manually installed, that indicates that the 'state' of those packages are probably wrong. With "aptitude markauto " or "apt-mark auto " you can change that. HTH, Diederik signature.asc Description: This is a digitally signed message part.
Re: Plasma 5.23 25th Annivery Release coming to unstable
On Thursday, 14 October 2021 17:15:00 CEST Martin Steigerwald wrote: > As usually take care with "apt dist-upgrade". Wait until the builds are > complete. The best way to do that is not using *dist*-upgrade but the normal/safe- upgrade method ... signature.asc Description: This is a digitally signed message part.
Re: Broken KDE in Sid/Unstable
On zondag 19 september 2021 17:10:51 CEST Miguel A. Vallejo wrote: > Removing ~/.config/plasma-org.kde.plasma.desktop-appletsrc and relogin > did the trick, but lost all the personalization. I've had similar problems a number of times now in the last few weeks. Lost my task bar a couple of times and last week several widgets on my desktop and other icons I had on my desktop got moved around. So far the problems have not been as severe as you reported. But I rarely use dist/full-upgrade; (almost) always safe-upgrade. 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
Control: reassign -1 libqgpgme7 1.16.0-1
Control: retitle -1 GPGMe does not take additional keyring into account to find
keys.
Control: affects -1 kmail
On woensdag 15 september 2021 10:56:59 CEST Sandro Knauß wrote:
> > Thanks for your assistance. I've save the signature as 'signature.asc' and
> > the signed part of the email msg to 'attempt3-dos.txt'
>
> great. Can you now do the same test. commenting/uncommenting the keyring
> line in the gpgconf? And kill gpg-agent in between to make 100% sure, that
> no left overs are taken.
I've rename 'signature.asc' to 'joostvb-signature.asc' and 'attempt3-dos.txt'
to 'joostvb-signed-msg-part-dos.txt' and ran the tests you requested.
=
$ killall gpg-agent
$ ps aux | grep gpg-agent | grep -v grep
$ vim ~/.gnupg/gpg.conf
$ tail -n1 ~/.gnupg/gpg.conf
#keyring /usr/share/keyrings/debian-keyring.gpg
$ ps aux | grep gpg-agent | grep -v grep
diederik 12992 0.0 0.0 154884 3600 ?SLs 12:32 0:00
/usr/bin/gpg-agent --supervised
$ gpg --verify joostvb-signature.asc joostvb-signed-msg-part-dos.txt
gpg: Signature made di 31 aug 2021 16:07:34 CEST
gpg:using RSA key 92AAD901B21B4BC79A47A03054F1A66317486713
gpg: Good signature from "Joost E. van Baal (Nederland, 1970)" [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal-Ilić" [full]
Primary key fingerprint: B8FA C2E2 5047 5B8C E940 A919 5793 0DAB 0B86 B067
Subkey fingerprint: 92AA D901 B21B 4BC7 9A47 A030 54F1 A663 1748 6713
$ killall gpg-agent
$ ps aux | grep gpg-agent | grep -v grep
$ vim ~/.gnupg/gpg.conf
$ tail -n1 ~/.gnupg/gpg.conf
keyring /usr/share/keyrings/debian-keyring.gpg
$ ps aux | grep gpg-agent | grep -v grep
diederik 13025 1.2 0.0 228616 3608 ?SLs 12:33 0:00
/usr/bin/gpg-agent --supervised
$ gpg --verify joostvb-signature.asc joostvb-signed-msg-part-dos.txt
gpg: Signature made di 31 aug 2021 16:07:34 CEST
gpg:using RSA key 92AAD901B21B4BC79A47A03054F1A66317486713
gpg: Good signature from "Joost E. van Baal (Nederland, 1970)" [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal " [full]
gpg: aka "Joost van Baal-Ilić" [full]
Primary key fingerprint: B8FA C2E2 5047 5B8C E940 A919 5793 0DAB 0B86 B067
Subkey fingerprint: 92AA D901 B21B 4BC7 9A47 A030 54F1 A663 1748 6713
=
On woensdag 15 september 2021 13:16:21 CEST you wrote:
> That seems fine, as the gpg-agent has restarted. So I think we are ready to
> move this bug to gpgme. But anyways this all sounds like an upstream bug,
> so properly you have to create a bug at https://dev.gnupg.org/
I'll wait what the gpgme maintainers have to say first, before I('ll have to)
go through the trouble of creating an account there ...
Cheers,
Diederik
signature.asc
Description: This is a digitally signed message part.
Bug#993546: kmail: KMail sees different signing key on same mail when enabling debian-keyring
On zondag 12 september 2021 19:57:17 CEST Sandro Knauß wrote: > But first make sue, that you are really have an valid bug. Please verify the > signature in a konsole via gpg --verify. I expect, that it will fail with > the same error. Thanks for your assistance. I've save the signature as 'signature.asc' and the signed part of the email msg to 'attempt3-dos.txt' $ gpg --verify signature.asc attempt3-dos.txt gpg: Signature made di 31 aug 2021 16:07:34 CEST gpg:using RSA key 92AAD901B21B4BC79A47A03054F1A66317486713 gpg: Good signature from "Joost E. van Baal (Nederland, 1970)" [full] gpg: aka "Joost van Baal " [full] gpg: aka "Joost van Baal " [full] gpg: aka "Joost van Baal " [full] gpg: aka "Joost van Baal " [full] gpg: aka "Joost van Baal " [full] gpg: aka "Joost van Baal " [full] gpg: aka "Joost van Baal-Ilić" [full] Primary key fingerprint: B8FA C2E2 5047 5B8C E940 A919 5793 0DAB 0B86 B067 Subkey fingerprint: 92AA D901 B21B 4BC7 9A47 A030 54F1 A663 1748 6713 Hoping/expecting to validate the message against my keyring with "gpg --verify attempt3-dos.txt" failed as "gpg --verify" wants the signature file as first parameter. Let me know what else I can do. Cheers, Diederik signature.asc Description: This is a digitally signed message part.
Bug#993546: kmail: KMail sees different signing key on same mail when enabling debian-keyring
Hoi, On zondag 12 september 2021 19:57:17 CEST Sandro Knauß wrote: > I'm quite sure, that this is not the issue of Kmail, as Kmail is using the > GPGME to talk to gpg. So it will be an issue of libqgpgme7. Ok. I noticed the issue in KMail, so I reported it against that package. Feel free to reassign to an (more) appropriate package. > But first make sure, that you are really have an valid bug. Please verify the > signature in a konsole via gpg --verify. I expect, that it will fail with > the same error. How can I do that? I've saved the msg as an mbox file and ran 'gpg --verify' on it: gpg --verify Joostvb-orig-signed-msg.mbox gpg: no signed data gpg: can't hash datafile: No data That looks weird as it's certainly a signed msg. Let's try mutt (me = mutt newbie): mutt -f Joostvb-orig-signed-msg.mbox I see "1 Ns " ; to view it and I see: [-- Begin signature information --] Good signature from: Joost E. van Baal (Nederland, 1970) aka: created: [-- End signature information --] After 'i' to Exit, the lowercase 's' turned into a capital 'S'. Which IIUC indicates a valid signature. So mutt seems happy. ~/.gnupg/gpg.conf had the debian-keyring enabled. After disabling debian-keyring: gpg --verify Joostvb-orig-signed-msg.mbox gpg: no signed data gpg: can't hash datafile: No data mutt -f Joostvb-orig-signed-msg.mbox I see "1 s " ; to view it and I see: [-- Begin signature information --] Good signature from: Joost E. van Baal (Nederland, 1970) aka: created: [-- End signature information --] After Exit, the lowercase 's' turned into a capital 'S' again. So with mutt everything _looks_ the same with the debian-keyring enabled or disabled, while there is a difference in KMail. > Keep in mind that Joot's using a subkey to sign ( 0x54F1A66317486713), this > subkey needs to be available also to verify the signature. > > > When doing "gpg --list-keys 0x57930DAB0B86B067" (or long key ID) > > (with "list-options show-keyring=yes" in my gpg.conf) I see the same key > > present in my keyring (pubring.kbx) and in Debian's debian-keyring.gpg. > > As I was told you alsoways have to use --with-colons when using > gpg --list-keys --with-colons to get ideas about the key status. With debian-keyring disabled: $ gpg --with-colons --list-keys 0x57930DAB0B86B067 tru::1:1631360998:1645731991:3:1:5 pub:f:4096:1:57930DAB0B86B067:1129127891:::f:::scESC::23:1630521551:1 http\x3a//keyring.debian.org\x3a11371: fpr:B8FAC2E250475B8CE940A91957930DAB0B86B067: uid:f1129129467::D3568B2F561D7D224C0894CE39E650FC67F0755B::Joost E. van Baal (Nederland, 1970):1630521551:1: uid:f1129129236::404399E9298441B5AFF1F09D9A6314F6D0DF12FF::Joost van Baal :1630521551:1: uid:f1129129331::06AF0BE4F14BBC6BEDF47674B6BCD74AEBBA5FA5::Joost van Baal :1630521551:1: uid:f1129129295::83F7EC80DEAB05929AE4829E7FE6A07468F1B557::Joost van Baal :1630521551:1: uid:f1129129358::ECC854CC7EAFC26121A339FF41A0D1917097C7D7::Joost van Baal :1630521551:1: uid:f1129129385::1857D9EC456DEEE1C4FC2C1207E9C2B9A8F844E2::Joost van Baal :1630521551:1: uid:f1223447825::0BC514AB9B9027517C311BEDC30A59E551EB4D16::Joost van Baal :1630521551:1: uid:f1318359511::9E04CD3B93ECF31B7BAC1315EBAE5D5B987EF556::Joost van Baal-Ilić:1630521551:1: sub:e:4096:1:A96539F624525E9E:1129128272:1223736272:s::23: fpr:C5B85256C175C10CBD0832A4A96539F624525E9E: sub:e:4096:1:F98CBB23C0BC6980:1223447515:1318055515:s::23: fpr:ABB0F0BF85D70496B35D0B7CF98CBB23C0BC6980: sub:e:2048:1:33517A72A5E6B0C8:1318359158:1476039158:s::23: fpr:B9563AB8479744C26035A9F933517A72A5E6B0C8: sub:f:4096:1:54F1A66317486713:1476171990:1728387017:s::23: fpr:92AAD901B21B4BC79A47A03054F1A66317486713: sub:f:4096:1:F4E66A7265F23E7B:1476172439:1728387066:e::23: fpr:A9202D9E6ADD2C7E7301DEE8F4E66A7265F23E7B: sub:e:2048:1:88FEF971404CA6BE:1318359224:1476039224:e::23: fpr:2A3FED2354D9264FBF0184D688FEF971404CA6BE: sub:e:4096:1:5B19798443FF7C14:1129128610:1223736610:e::23: fpr:7C2AB7A44CD6F96538CD88F05B19798443FF7C14: sub:e:4096:1:8A551DB0EC34F0AE:1223447782:1318055782:e::23: fpr:9B60E5A6C3DBCAB264A56F4E8A551DB0EC34F0AE: With debian-keyring enabled: $ gpg --with-colons --list-keys 0x57930DAB0B86B067 tru::1:1631360998:1645731991:3:1:5 pub:f:4096:1:57930DAB0B86B067:1129127891:::f:::scESC::23:1630521551:1 http\x3a//keyring.debian.org\x3a11371: fpr:B8FAC2E250475B8CE940A91957930DAB0B86B067: uid:f1129129467::D3568B2F561D7D224C0894CE39E650FC67F0755B::Joost E. van Baal (Nederland, 1970):1630521551:1:
Bug#993441: kleopatra: Creates unsafe ~/.gnupg when not already present
On dinsdag 7 september 2021 11:32:28 CEST Peter Green wrote: > > Version: 4:21.08.0-1 > > You filed this against the version in sid? I run Sid as my daily driver, so yes. That's what I (almost?) always do. > have you investigated whether earlier versions are also affected? No, I did not. signature.asc Description: This is a digitally signed message part.
Bug#993546: kmail: KMail sees different signing key on same mail when enabling debian-keyring
On donderdag 2 september 2021 23:15:47 CEST Diederik de Haas wrote: > KMail reports (after I signed it) The signing part is irrelevant for reproducing the bug. I experienced the exact same problem before I signed it. signature.asc Description: This is a digitally signed message part.
Bug#993546: kmail: KMail sees different signing key on same mail when enabling debian-keyring
Package: kmail Version: 4:21.08.0-2 Severity: normal Recently I received a signed email from Debian Developer joostvb@d.o. I imported his public key to my keyring as follows: gpg --keyserver keyring.debian.org --recv-keys 0xB8FAC2E250475B8CE940A91957930DAB0B86B067 When selecting that mail, KMail reports (after I signed it): Message was signed by joos...@mdcc.cx (Key ID: 0x57930DAB0B86B067). The signature is valid and the key is fully trusted. Excellent, exactly as I expected. Joost's key is also part of the debian-keyring with the (exact) same fingerprint. I figured it would be useful to have DD's key in gpg's keyring, so I added the following to ~/.gnupg/gpg.conf: keyring /usr/share/keyrings/debian-keyring.gpg But when I then first select an(y) other email and then select Joost's email again, KMail reports the following: Message was signed on with unknown key 0x92AAD901B21B4BC79A47A03054F1A66317486713. The validity of the signature cannot be verified. Status: Good signature When doing "gpg --list-keys 0x57930DAB0B86B067" (or long key ID) (with "list-options show-keyring=yes" in my gpg.conf) I see the same key present in my keyring (pubring.kbx) and in Debian's debian-keyring.gpg. If I then disable the "keyring ... debian-keyring.gpg" line again, all is well again and enabling brings the problem back. I've also started with a completely new ~/.gnupg and could still reproduce the problem. I have no clue how this can happen or be explained, but it sounds like a bug to me. Cheers, Diederik -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: arm64 Kernel: Linux 5.10.0-8-amd64 (SMP w/16 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kmail depends on: ii akonadi-server 4:21.08.0-1 ii kdepim-runtime 4:21.08.0-1 ii kio 5.85.0-2 ii libc62.31-17 ii libgcc-s111.2.0-3 ii libgpgmepp6 1.16.0-1 ii libkf5akonadiagentbase5 [libkf5akonadiagentbase5-21.08] 4:21.08.0-1 ii libkf5akonadicontact5 [libkf5akonadicontact5-21.08] 4:21.08.0-1 ii libkf5akonadicore5abi2 [libkf5akonadicore5-21.08]4:21.08.0-1 ii libkf5akonadimime5 [libkf5akonadimime5-21.08]4:21.08.0-1 ii libkf5akonadisearch-bin 4:21.08.0-1 ii libkf5akonadisearch-plugins 4:21.08.0-1 ii libkf5akonadisearchdebug5 [libkf5akonadisearchdebug5-21.08] 4:21.08.0-1 ii libkf5akonadisearchpim5 [libkf5akonadisearchpim5-21.08] 4:21.08.0-1 ii libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-21.08] 4:21.08.0-1 ii libkf5bookmarks5 5.85.0-2 ii libkf5calendarcore5abi2 5:5.85.0-2 ii libkf5calendarutils5 [libkf5calendarutils5-21.08]4:21.08.0-1 ii libkf5codecs55.85.0-2 ii libkf5completion55.85.0-2 ii libkf5configcore55.85.0-2 ii libkf5configgui5 5.85.0-2 ii libkf5configwidgets5 5.85.0-2 ii libkf5contacts5 5:5.85.0-2 ii libkf5coreaddons55.85.0-2 ii libkf5crash5 5.85.0-2 ii libkf5dbusaddons55.85.0-2 ii libkf5grantleetheme-plugins 21.08.0-1 ii libkf5gravatar5abi2 [libkf5gravatar5-21.08] 4:21.08.0-1 ii libkf5guiaddons5 5.85.0-2 ii libkf5i18n5 5.85.0-2 ii libkf5iconthemes55.85.0-2 ii libkf5identitymanagement5 [libkf5identitymanagement5-21.08] 21.08.0-1 ii libkf5itemmodels55.85.0-2 ii libkf5itemviews5 5.85.0-2 ii libkf5jobwidgets55.85.0-2 ii libkf5kcmutils5 5.85.0-2 ii libkf5kiocore5 5.85.0-2 ii libkf5kiofilewidgets5
Bug#993441: kleopatra: Creates unsafe ~/.gnupg when not already present
Package: kleopatra Version: 4:21.08.0-1 Severity: grave Tags: security Justification: user security hole X-Debbugs-Cc: Debian Security Team I had previously 'improved' my gnupg configuration, but that is (now) deprecated. So I moved my ~/.gnupg directory to a backup location to start anew. If I then start Kleopatra, but don't do anything with it, that directory gets created, but with the wrong permissions: diederik@bagend:~$ stat .gnupg/ File: .gnupg/ Size: 4096Blocks: 8 IO Block: 4096 directory Device: 10304h/66308d Inode: 12845182Links: 3 Access: (0755/drwxr-xr-x) Uid: ( 1000/diederik) Gid: ( 1000/diederik) Running a gpg command from a Konsole window reports the issue: diederik@bagend:~$ gpg --list-keys gpg: WARNING: unsafe permissions on homedir '/home/diederik/.gnupg' If I uninstall Kleopatra and remove the ~/.gnupg directory (again) and then do 'gpg --list-keys', I get: diederik@bagend:~$ gpg --list-keys gpg: directory '/home/diederik/.gnupg' created gpg: keybox '/home/diederik/.gnupg/pubring.kbx' created gpg: /home/diederik/.gnupg/trustdb.gpg: trustdb created diederik@bagend:~$ stat .gnupg/ File: .gnupg/ Size: 4096Blocks: 8 IO Block: 4096 directory Device: 10304h/66308d Inode: 12845180Links: 2 Access: (0700/drwx--) Uid: ( 1000/diederik) Gid: ( 1000/diederik) So Kleopatra creates ~/.gnupg with incorrect permissions when the directory doesn't exist. Cheers, Diederik -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: arm64 Kernel: Linux 5.10.0-8-amd64 (SMP w/16 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kleopatra depends on: ii dirmngr2.2.27-2 ii gnupg 2.2.27-2 ii gpgsm 2.2.27-2 ii libassuan0 2.5.5-1 ii libc6 2.31-17 ii libgcc-s1 11.2.0-3 ii libgpg-error0 1.42-3 ii libgpgme11 1.16.0-1 ii libgpgmepp61.16.0-1 ii libkf5codecs5 5.85.0-2 ii libkf5configcore5 5.85.0-2 ii libkf5configgui5 5.85.0-2 ii libkf5configwidgets5 5.85.0-2 ii libkf5coreaddons5 5.85.0-2 ii libkf5crash5 5.85.0-2 ii libkf5dbusaddons5 5.85.0-2 ii libkf5i18n55.85.0-2 ii libkf5iconthemes5 5.85.0-2 ii libkf5itemmodels5 5.85.0-2 ii libkf5libkleo5 [libkf5libkleo5-21.08] 4:21.08.0-1 ii libkf5mime5abi1 [libkf5mime5-21.08]21.08.0-1 ii libkf5notifications5 5.85.0-3 ii libkf5textwidgets5 5.85.0-2 ii libkf5widgetsaddons5 5.85.0-2 ii libkf5windowsystem55.85.0-2 ii libkf5xmlgui5 5.85.0-3 ii libqgpgme7 1.16.0-1 ii libqt5core5a 5.15.2+dfsg-10 ii libqt5dbus55.15.2+dfsg-10 ii libqt5gui5 5.15.2+dfsg-10 ii libqt5network5 5.15.2+dfsg-10 ii libqt5printsupport55.15.2+dfsg-10 ii libqt5widgets5 5.15.2+dfsg-10 ii libstdc++6 11.2.0-3 ii paperkey 1.6-1 ii pinentry-qt1.1.1-1 kleopatra recommends no packages. kleopatra suggests no packages. -- no debconf information
Bug#993254: sorry wrong tag
Control: tag -1 -a11y On zondag 29 augustus 2021 13:42:40 CEST k_f wrote: > the accessibility tag is wrong signature.asc Description: This is a digitally signed message part.
Re: Digikam and 4:21
On vrijdag 27 augustus 2021 20:13:39 CEST MERLIN Philippe wrote: > Sorry, for me the result of . > export LANG=C; apt dist-upgrade -V Maybe don't (normally) use dist-upgrade? The normal/safe- upgrade is all you need in 99% of cases. That sometimes, like in this case, means you have to wait a couple of days longer. If after say a week it still shows a bunch of un-upgraded packages, then you can try out (-s = simulate) whether an dist/full-upgrade is actually needed. It often is an indication that the package metadata is suboptimal. It has baffled me for years now that people seem to default to using dist- upgrade. I'm using Sid as my daily driver for ~ a decade now. signature.asc Description: This is a digitally signed message part.
Re: KDEPIM 21.08: blank settings window in KMail
On donderdag 26 augustus 2021 18:35:25 CEST Martin Steigerwald wrote: > > I first upgraded my version 5.83 packages to the ones in unstable: > > aptitude safe-upgrade ~i~V5.83.0 -t experimental > > In Experimental. You're absolutely correct. I mentioned it as I saw various 5.83 programs/libraries and you apparently already had some programs from Norbert installed. > But it could be that this was related to the library mentioned above, so > yeah, could be that some other 5.83 libraries were in use. As mentioned above, that was my 'suspicion' (from the output you posted earlier). signature.asc Description: This is a digitally signed message part.
Re: KDEPIM 21.08: blank settings window in KMail
On donderdag 26 augustus 2021 14:35:08 CEST Martin Steigerwald wrote: > > Can those of you who see this problem, please try the kmail package > > https://download.opensuse.org/repositories/home:/npreining:/ > > debian-kde:/apps2108/Debian_Unstable/amd64/ > > kmail_21.08.0-1~np1_amd64.deb (for > > Debian_Unstable, for testing use Debian_Testing) > > It should be installable as is. > > Not with Debian Unstable packages: > > LANG=en dpkg -i kmail_21.08.0-1~np1_amd64.deb > (Reading database ... 417884 files and directories currently installed.) > Preparing to unpack kmail_21.08.0-1~np1_amd64.deb ... > Unpacking kmail (4:21.08.0-1~np1) over (4:21.08.0-1~np1) ... > dpkg: dependency problems prevent configuration of kmail: > kmail depends on libkf5coreaddons5 (>= 5.84.0); however: > Version of libkf5coreaddons5:amd64 on system is 5.83.0-2. > kmail depends on libkf5kcmutils5 (>= 5.85.0-1~np1); however: > Version of libkf5kcmutils5:amd64 on system is 5.83.0-2. > kmail depends on libkf5xmlgui5 (>= 5.85.0-1~np1); however: > Version of libkf5xmlgui5:amd64 on system is 5.83.0-2. I first upgraded my version 5.83 packages to the ones in unstable: aptitude safe-upgrade ~i~V5.83.0 -t experimental Started KMail and settings window still didn't work. I did it without logging out or anything, so there's a reasonable chance the 5.83 versions were still in use. I downloaded only kmail_21.08.0-1~np1_amd64.deb and after a reboot, so 5.85 was surely in use, I did 'sudo dpkg -i kmail_21.08.0-1~np1_amd64.deb': [sudo] password for diederik: dpkg: warning: downgrading kmail from 4:21.08.0-1 to 4:21.08.0-1~np1 (Reading database ... 698466 files and directories currently installed.) Preparing to unpack kmail_21.08.0-1~np1_amd64.deb ... Unpacking kmail (4:21.08.0-1~np1) over (4:21.08.0-1) ... Setting up kmail (4:21.08.0-1~np1) ... Processing triggers for libc-bin (2.31-17) ... Processing triggers for mailcap (3.70) ... Processing triggers for hicolor-icon-theme (0.17-2) ... And now KMail's settings window does work :-) Cheers, Diederik signature.asc Description: This is a digitally signed message part.
Re: KDEPIM 21.08 coming to unstable
On maandag 23 augustus 2021 09:21:59 CEST Martin Steigerwald wrote: > Norbert is uploading KDEPIM / Akonadi 21.08. Please wait for builds to > complete their work. > > In generally be careful. Unstable is much more unstable again If you stick to using 'safe-upgrade' you should be fine in Unstable. You will see sth like "and 51 not upgraded" and that is fine. When all the dependencies are there, safe-upgrade will upgrade KDEPIM/Akonadi too. signature.asc Description: This is a digitally signed message part.
Re: Proposal: drop Salsa CI testing for now
[I shouldn't have a meaningful voice in this, but my 0.02 ...] Normally I would be strongly against disabling tests ... On woensdag 18 augustus 2021 21:26:04 CEST Nicholas D Steeves wrote: > I'm also concerned that the situation is fundamentally wrong: If tests > need to be updated with every new release, something is wrong with the > tests, or the infrastructure... Tests and infrastructure are supposed > to be the controls that enable meaningful results when testing for > correct functionality in the face of changes. But I 100% agree with this. Tests are meant to guard against regressions, so updating tests should be a rarity. If they need to be updated for every release, then they're utterly meaningless. It's easy to introduce new bugs in the tests or you change the test to get the results you desire. In the former case you should (probably) have tests for the tests and in the latter case you're just fooling yourself and others and creating a false sense of security. Which is BAD. signature.asc Description: This is a digitally signed message part.
Bug#989671: kontact: Trying to archive a Mail folder makes it crash
Package: kontact Version: 4:21.04.1-1 Severity: important I'm filing it against kontact, but kmail is maybe more appropriate. However with kontact I could generate a stacktrace, which failed with kmail, so therefor I chose kontact. Feel free to reassign. In 'Local Folder' I have a Mail-Achive folder with 2 subfolders for 2 of my mail accounts. Earlier today I moved a bunch of mails from my (IMAP) account to the corresponding Mail-Archive folder and that seems to went fine. When you right-click on a folder, you can choose 'Archive Folder...' to make an export of that folder to a .tar.bz2 file and I use that for backup purposes. It starts the process (no idea where the/a temp file is created though) and then at some point it crashes. === KCrash output 1 === Application: Kontact (kontact), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #5 0x7fe28cc98537 in __GI_abort () at abort.c:79 #6 0x7fe28ced27ec in __gnu_cxx::__verbose_terminate_handler () at ../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95 #7 0x7fe28cedd966 in __cxxabiv1::__terminate (handler=) at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:48 #8 0x7fe28cedd9d1 in std::terminate () at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:58 #9 0x7fe28ceddc65 in __cxxabiv1::__cxa_throw (obj=obj@entry=0x55c80b21ebd0, tinfo=0x7fe1d83ef348 , dest=0x7fe1d82b01f0 ) at ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:95 #10 0x7fe1d8265b41 in Akonadi::Item::throwPayloadException (this=this@entry=0x55c818322738, spid=spid@entry=-1, mtid=mtid@entry=-1) at ./src/core/item.cpp:463 #11 0x7fe1b900ae92 in Akonadi::Item::payload > (this=0x55c818322738) at /usr/include/KF5/AkonadiCore/item.h:791 #12 MailCommon::BackupJob::processMessage (this=0x7fe270009790, item=...) at ./src/job/backupjob.cpp:232 #13 0x7fe1b900b048 in MailCommon::BackupJob::itemFetchJobResult (this=0x7fe270009790, job=0x7ffef3a31cd0) at ./src/job/backupjob.cpp:271 #14 0x7fe28d2eb5a6 in QtPrivate::QSlotObjectBase::call (a=0x7ffef3a31e20, r=0x7fe270009790, this=0x55c8016c4130) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #15 doActivate (sender=0x7fe19c46a4b0, signal_index=6, argv=argv@entry=0x7ffef3a31e20) at kernel/qobject.cpp:3886 #16 0x7fe28d2e4900 in QMetaObject::activate (sender=sender@entry=0x7fe19c46a4b0, m=m@entry=0x7fe28e40dca0 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffef3a31e20) at kernel/qobject.cpp:3946 #17 0x7fe28e3b76fc in KJob::result (this=this@entry=0x7fe19c46a4b0, _t1=, _t1@entry=0x7fe19c46a4b0, _t2=...) at ./obj-x86_64-linux-gnu/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:636 #18 0x7fe28e3b8433 in KJob::finishJob (this=0x7fe19c46a4b0, emitResult=) at ./src/lib/jobs/kjob.cpp:94 #19 0x7fe28d2e0ff1 in QObject::event (this=0x7fe19c46a4b0, e=0x55c80c32d5d0) at kernel/qobject.cpp:1314 #20 0x7fe28dd7715f in QApplicationPrivate::notify_helper (this=, receiver=0x7fe19c46a4b0, e=0x55c80c32d5d0) at kernel/qapplication.cpp:3632 #21 0x7fe28d2b4fca in QCoreApplication::notifyInternal2 (receiver=0x7fe19c46a4b0, event=0x55c80c32d5d0) at kernel/qcoreapplication.cpp:1063 #22 0x7fe28d2b7a01 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55c7ff9a28f0) at kernel/qcoreapplication.cpp:1817 #23 0x7fe28d30ce93 in postEventSourceDispatch (s=0x55c7ffadae00) at kernel/qeventdispatcher_glib.cpp:277 #24 0x7fe2836e1e6b in g_main_dispatch (context=0x7fe270005000) at ../../../glib/gmain.c:3325 #25 g_main_context_dispatch (context=0x7fe270005000) at ../../../glib/gmain.c:4043 #26 0x7fe2836e2118 in g_main_context_iterate (context=context@entry=0x7fe270005000, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4119 #27 0x7fe2836e21cf in g_main_context_iteration (context=0x7fe270005000, may_block=may_block@entry=1) at ../../../glib/gmain.c:4184 #28 0x7fe28d30c51f in QEventDispatcherGlib::processEvents (this=0x55c7ffadbd60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #29 0x7fe28d2b398b in QEventLoop::exec (this=this@entry=0x7ffef3a32210, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #30 0x7fe28d2bbc00 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #31 0x55c7fe2cb02b in main (argc=, argv=) at ./src/main.cpp:208 [Inferior 1 (process 2390) detached] === end KCrash output 1 === Then I rebooted my machine and tried again. And it crashed again: === KCrash output 2 === Application: Kontact (kontact), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #5 0x7f2bfb2e2537 in __GI_abort () at abort.c:79 #6 0x7f2bfb51c7ec in __gnu_cxx::__verbose_terminate_handler () at ../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95 #7
Bug#971065: korganizer: org.kde.korgac.desktop executable
On zondag 27 september 2020 07:39:42 CEST Helge Kreutzmann wrote: > Package: korganizer > Version: 4:20.04.1-2 > Severity: minor > > In the logs I get the following error message: > Aug 15 21:46:20 samd systemd[232194]: Configuration file > /etc/xdg/autostart/org.kde.korgac.desktop is marked executable. Please > remove executable permission bits. Proceeding anyway. > > And indeed, it is the only executable desktop file in this directory. > > Please consider removing the executable bit. If I download the .deb file and look inside it, that file has 644 permissions, iow no executable bit set. https://invent.kde.org/pim/korganizer/-/commit/14138650407be94cdecabecd40d1435420df8fdd is the upstream commit from 2017-03-02 where the executable bit was removed. I don't know why +x is set on your system, but the package seem fine. signature.asc Description: This is a digitally signed message part.
Bug#986452: Updating metadata and found the cause
Control: tag -1 affects kmail The problem is caused by an incorrect modification of https://salsa.debian.org/qt-kde-team/kde/messagelib/-/commits/master/debian/patches/series Instead of adding (twice) a new/extra patch, it replaced the series. Kind of like using '>' while you meant using '>>'. signature.asc Description: This is a digitally signed message part.
Bug#986452: libkf5messagelist5abi1: KMail fails to start because it can't load libKF5MessageList.so.5abi1
Package: libkf5messagelist5abi1 Version: 4:20.08.3-3 Severity: important Since upgrading of libkf5messagelist5abi1 KMail fails to load with the following error message (I actually load it via Kontact): "Cannot load part for Mail. Cannot load library /usr/lib/x86_64-linux-gnu/qt5/plugins/kmailpart.so: (libKF5MessageList.so.5abi1: kan gedeeld objectbestand niet openen: Bestand of map bestaat niet)" Translation of last part: "can't load shared object: file or folder not found" (I want my system in English, but more and more Dutch things creep in) The testing version (4:20.08.3-2) has this file list: $ dpkg -L libkf5messagelist5abi1 | grep -v '/usr/share/doc' /. /usr /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libKF5MessageList.so.5.15.3.abi1 /usr/share /usr/lib/x86_64-linux-gnu/libKF5MessageList.so.5abi1 The unstable version (4:20.08.3-3) has this file list: $ dpkg -L libkf5messagelist5abi1 | grep -v '/usr/share/doc' /. /usr /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libKF5MessageList.so.5.15.3 /usr/share /usr/lib/x86_64-linux-gnu/libKF5MessageList.so.5 So the [.]abi1 suffix is no longer there. My guess is that either the [.]abi1 suffix should be added back again or the component(s) that are linked to it, should be recompiled to link to the new name. Downgrading libkf5messagelist5abi1 (and it's dependencies) to the testing version makes KMail work again. On my system that meant these packages: kf5-messagelib-data libkf5messagecomposer5abi1 libkf5messagecore5abi1 libkf5messagelist5abi1 libkf5messageviewer5abi1 libkf5mimetreeparser5abi1 libkf5templateparser5 libkf5webengineviewer5abi1 -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-5-amd64 (SMP w/16 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libkf5messagelist5abi1 depends on: ii kf5-messagelib-data 4:20.08.3-3 ii kio 5.78.0-4 ii libc62.31-11 ii libgcc-s110.2.1-6 ii libkf5akonadicore5abi2 [libkf5akonadicore5-20.08]4:20.08.3-2 ii libkf5akonadimime5 [libkf5akonadimime5-20.08]4:20.08.3-1 ii libkf5akonadisearchpim5 [libkf5akonadisearchpim5-20.08] 4:20.08.3-1 ii libkf5configcore55.78.0-4 ii libkf5configgui5 5.78.0-4 ii libkf5configwidgets5 5.78.0-2 ii libkf5coreaddons55.78.0-4 ii libkf5i18n5 5.78.0-2 ii libkf5iconthemes55.78.0-2 ii libkf5itemmodels55.78.0-2 ii libkf5kiocore5 5.78.0-4 ii libkf5messagecore5abi1 [libkf5messagecore5-20.08]4:20.08.3-3 ii libkf5mime5abi1 [libkf5mime5-20.08] 20.08.3-1 ii libkf5pimcommon5abi2 [libkf5pimcommon5-20.08]4:20.08.3-1 ii libkf5pimcommonakonadi5abi1 [libkf5pimcommonakonadi5-20.08] 4:20.08.3-1 ii libkf5textwidgets5 5.78.0-2 ii libkf5widgetsaddons5 5.78.0-2 ii libkf5xmlgui55.78.0-2 ii libqt5core5a 5.15.2+dfsg-5 ii libqt5gui5 5.15.2+dfsg-5 ii libqt5widgets5 5.15.2+dfsg-5 ii libstdc++6 10.2.1-6 libkf5messagelist5abi1 recommends no packages. libkf5messagelist5abi1 suggests no packages. -- no debconf information
Bug#973933: turns out it was wayland that crashed
It turns out that the wayland plasma session got selected and that crashed. This is possibly/probably fixed with the -2 upload which happened a couple of hours ago. Manually selecting the 'normal' plasma session and then I could log in. OP: Can you check whether the wayland session was (automatically) selected for you too? And if so, does the problem still occur when you select the 'normal' plasma session? signature.asc Description: This is a digitally signed message part.
Bug#973933: touch /etc/environment didn't help
Control: tag -1 confirmed Did a 'touch /etc/environment' and restarted sddm.service, but the problem remained. Output is the same as in my previous message, minus the pam_env error line. Usually from within KDE, I can get a backtrace (DrKonqi?) easily, but that won't work in this case as I can't login to KDE. If you can provide me with the needed steps to do it without logging in, I'd be happy to provide that info. signature.asc Description: This is a digitally signed message part.
Bug#973933: sddm: Unable to open env file: /etc/environment: No such file or directory
Package: sddm
Version: 0.19.0-1
Followup-For: Bug #973933
Got a very big upgrade (hadn't started my Sid system for several days), which
included sddm and after a reboot I got the sddm login screen.
But after giving my credentials, I got thrown back to the login screen.
'systemctl status sddm.service' told me:
Unable to open env file: /etc/environment: No such file or directory
● sddm.service - Simple Desktop Display Manager
Loaded: loaded (/lib/systemd/system/sddm.service; enabled; vendor preset:
enabled)
Active: active (running) since Mon 2020-11-09 23:14:48 CET; 8min ago
Docs: man:sddm(1)
man:sddm.conf(5)
Main PID: 3641 (sddm)
Tasks: 27 (limit: 77031)
Memory: 35.6M
CGroup: /system.slice/sddm.service
├─3641 /usr/bin/sddm
└─3854 /usr/lib/xorg/Xorg -nolisten tcp -auth
/var/run/sddm/{a330fe19-b614-4bb4-9329-d7d6240b8ca7} -background none -noreset
-displayfd 18 -seat seat0 vt7
nov 09 23:15:58 bagend sddm[3641]: Socket server started.
nov 09 23:15:58 bagend sddm[3641]: Loading theme configuration from
"/usr/share/sddm/themes/debian-maui/theme.conf"
nov 09 23:15:58 bagend sddm[3641]: Greeter starting...
nov 09 23:15:58 bagend sddm-helper[3885]: [PAM] Starting...
nov 09 23:15:58 bagend sddm-helper[3885]: [PAM] Authenticating...
nov 09 23:15:58 bagend sddm-helper[3885]: [PAM] returning.
nov 09 23:15:58 bagend sddm-helper[3885]: pam_unix(sddm-greeter:session):
session opened for user sddm by (uid=0)
nov 09 23:15:58 bagend sddm-helper[3885]: pam_env(sddm-greeter:session): Unable
to open env file: /etc/environment: No such file or directory
nov 09 23:15:58 bagend sddm[3641]: Greeter session started successfully
nov 09 23:15:58 bagend sddm[3641]: Message received from greeter: Connect
I indeed do not have that file (I do have /etc/environment.d/90qt-a11y.conf),
but that shouldn't make sddm crash.
Downgrading sddm and sddm-theme-debian-maui to the testing version
(0.18.1-1) made me able to login again.
After sending this bug report, I'll try to see whether a 'touch
/etc/environment' would fix the problem as well.
Anyway, it shouldn't have crashed on it imo.
Notable difference with OP is that I use KDE as my DE.
Cheers,
Diederik
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'),
(101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.9.0-1-amd64 (SMP w/16 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages sddm depends on:
ii adduser 3.118
ii debconf [debconf-2.0] 1.5.74
ii libc6 2.31-4
ii libgcc-s1 10.2.0-16
ii libpam0g1.3.1-5
ii libqt5core5a5.15.1+dfsg-2
ii libqt5dbus5 5.15.1+dfsg-2
ii libqt5gui5 5.15.1+dfsg-2
ii libqt5network5 5.15.1+dfsg-2
ii libqt5qml5 5.15.1+dfsg-3
ii libqt5quick55.15.1+dfsg-3
ii libstdc++6 10.2.0-16
ii libsystemd0 246.6-2
ii libxcb-xkb1 1.14-2
ii libxcb1 1.14-2
ii qml-module-qtquick2 5.15.1+dfsg-3
ii x11-common 1:7.7+21
ii xauth 1:1.0.10-1
ii xserver-xorg [xserver] 1:7.7+21
Versions of packages sddm recommends:
pn haveged
ii libpam-systemd 246.6-2
ii sddm-theme-debian-maui [sddm-theme] 0.19.0-1
Versions of packages sddm suggests:
ii libpam-kwallet5 5.19.5-3
pn qtvirtualkeyboard-plugin
-- debconf information:
sddm/daemon_name: /usr/bin/sddm
* shared/default-x-display-manager: sddm
Bug#972355: qtav: FTBFS with Qt 5.15: error: field 'clip_path' has incomplete type 'QPainterPath'
Control: forwarded -1 https://github.com/wang-bin/QtAV/issues/1309 Control: tag -1 upstream fixed-upstream Fix is not yet included in a release though. Someone has opened an issue requesting that: https://github.com/wang-bin/QtAV/issues/1334 signature.asc Description: This is a digitally signed message part.
Re: Plasma 5.17.5 available in experimental
On dinsdag 21 januari 2020 06:37:07 CET Pino Toscano wrote: > as it was mentioned already in other threads on this list, > Plasma 5.17.5 is available in experimental. I used the following command to upgrade: aptitude full-upgrade ~i~V5.14.5 -t experimental So far I haven't seen any issues :) signature.asc Description: This is a digitally signed message part.
Bug#946522: akonadi-backend-sqlite: akonadi don't start and kmail don't work
On dinsdag 10 december 2019 15:37:12 CET Martin Jean-Fabrice wrote: > *** Reporter, please consider answering these questions, where appropriate > *** > >* What led up to the situation? >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the outcome of this action? >* What outcome did you expect instead? > > *** End of the template - remove these template lines *** Just "It doesn't work" is NOT a basis to fix a potential problem. Those lines I quoted above are meant to remind a bug reporter, ie you, to provide some information which allows the maintainer (and others) to find the actual problem which in turn can lead to a solution. It's fine to ask for help *how* to provide more detailed/technical information, but those questions above can be answered without any technical knowledge. For example: * What led up to the situation? I upgraded from version 4:18.08.3-1 to version 4:19.08.3-1 and where it did work before, it no longer does. Other pieces which may prove to be useful is share the output of running the following commands from a terminal: $ kmail and $ akonadictl restart It's not a problem at all if you didn't know those commands and that they could prove useful. See bug reporting as starting a dialog. HTH signature.asc Description: This is a digitally signed message part.
Bug#946199: akonadi-backend-postgresql: akonadictl fails to start with postgresql backend
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.
Re: phonon-backend-gstreamer-common has been kept back
On woensdag 13 november 2019 11:39:08 CET Andrey Rahmatullin wrote:
> On Wed, Nov 13, 2019 at 12:01:51AM +0100, Diederik de Haas wrote:
> > I don't know if "Debian Package Tracker" is a Web Shortcuts which is part
> > of a normal installation or if I have added it manually myself.
> > The "Shortcut URL:" is "https://tracker.debian.org/pkg/\{@};
> >
> > Using that, you can easily select each package name and then look it up in
> > "tracker.debian.org" and see what the status is. If you see "Removed
> > from unstable" and/or " REMOVED from testing", then
> > you should get rid of it in most cases.
>
> Just use apt-show-versions, filtering by "No available version in archive".
That's indeed useful to quickly identify the cruft :)
Still, it doesn't show even close the amount of information that I get through
tracker.d.o. (I've become a big fan of t.d.o)
https://tracker.debian.org/pkg/kopete shows me the following:
Versions that are present in o-o-stable, oldstable, stable, experimental (thus
not in testing or sid). In the 'news' section I can click on the link
"Removed 4:17.08.3-2.1 from unstable" which tells me:
--- Reason ---
RoQA; Obsolete libs - Qt4
--
and a link to https://bugs.debian.org/935659 and that bug tells me:
"The current unstable version is Qt4. There is a Qt5 version in
experimental, but the maintainer has not yet concluded it's appropriate
to include in a future release. Once the Qt5 version is ready, it can
be uploaded to unstable to re-introduce the package. In the meantime,
it doesn't make sense to block further progress on removing Qt4."
So now I know that kopete was removed because its using Qt4 and that that is
apparently (and rightfully) considered obsolete. If you do the t.d.o thing a
number of times you'd likely/rightfully concluded that all Qt4 apps/libs are
removed from the unstable/testing archives. You can/should conclude that maybe
you ought to remove those as well.
In the case of kopete you'd have also learned that there is a version in
experimental which uses Qt5 and that the maintainer currently thinks it is
unsuitable to end up in a next stable release. This could change in the future
and you could decide for yourself to help with that by installing the version
from experimental anyway and reporting bugs if you encounter them. Ofc all the
caveats of experimental applies and also the warning by the maintainer in this
specific case. In any case, you have enough info to make an informed decision.
signature.asc
Description: This is a digitally signed message part.
Re: phonon-backend-gstreamer-common has been kept back
On dinsdag 12 november 2019 23:18:36 CET Miguel A. Vallejo wrote:
> The following packages were automatically installed and are no longer
> required: espeak-ng-data festival festival-freebsoft-utils festlex-cmu
> festlex-poslex festvox-kallpc16k icoutils kate-data katepart
> kde-runtime-data kdelibs-bin kdelibs5-data kdelibs5-plugins kdoctools
> kmouth libattica0.4 libbctoolbox1 libbzrtp0 libdbusmenu-qt2
> libdotconf0 libespeak-ng1 libestools2.5 libgadu3 libgpgme++2v5
> libilmbase23 libkabc4 libkactivities6 libkatepartinterfaces4
> libkcmutils4 libkde3support4 libkdeclarative5 libkdesu5 libkdeui5
> libkdewebkit5 libkdnssd4 libkemoticons4 libkfile4 libkhtml5 libkio5
> libkjsapi4 libkjsembed4 libkldap4 libkmediaplayer4 libkmime4
> libknewstuff2-4 libknewstuff3-4 libknotifyconfig4 libkntlm4 libkopete4
> libkparts4 libkpimidentities4 libkpimtextedit4 libkpimutils4 libkpty4
> libkresources4 libkrosscore4 libktexteditor4 libmeanwhile1
> libmediastreamer-base10 libmediastreamer-voip10 libntrack-qt4-1
> libntrack0 libopenexr23 libortp13 libotr5 libpcaudio0 libphonon4
> libplasma3 libpolkit-qt-1-1 libqca2 libqca2-plugins libqimageblitz4
> libqjson0 libqt4-opengl libqt4-qt3support libqtwebkit4 libsolid4
> libsonic0 libspeechd2 libthreadweaver4 libutempter0
> ntrack-module-libnl-0 oxygen-icon-theme plasma-scriptengine-javascript
> sound-icons speech-dispatcher speech-dispatcher-audio-plugins
> speech-dispatcher-espeak-ng speech-dispatcher-festival
> Use 'apt autoremove' to remove them.
I always get very suspicious when I see such a large list, but it looks like
you have quite a lot of cruft on your system.
I don't know if "Debian Package Tracker" is a Web Shortcuts which is part of a
normal installation or if I have added it manually myself.
The "Shortcut URL:" is "https://tracker.debian.org/pkg/\{@};
Using that, you can easily select each package name and then look it up in
"tracker.debian.org" and see what the status is. If you see "Removed
from unstable" and/or " REMOVED from testing", then you should get
rid of it in most cases.
This will take some time, but IMO is time well spend.
signature.asc
Description: This is a digitally signed message part.
Re: phonon-backend-gstreamer-common has been kept back
On dinsdag 12 november 2019 23:42:35 CET Diederik de Haas wrote: > As Luigi already indicated, you have old cruft (QT4) installed and you > should get rid of them. > The easiest way is to say Yes to the above suggestion. > And then install phonon4qt5-backend-gstreamer, which will then also upgrade > phonon-backend-gstreamer-common And I forgot the most important part: do it with aptitude! As you noticed, apt/apt-get is not so smart and happily removes your whole system. Aptitude has a powerful dependency resolver and you've just witnessed that. signature.asc Description: This is a digitally signed message part.
Re: phonon-backend-gstreamer-common has been kept back
On dinsdag 12 november 2019 23:18:36 CET Miguel A. Vallejo wrote: > The following packages have unmet dependencies: > phonon-backend-gstreamer : Depends: phonon-backend-gstreamer-common (= > 4:4.9.1-1) but it is not going to be installed > The following actions will resolve these dependencies: > > Remove the following packages: > 1) jovie [4:16.08.0-1+b1 (now)] > 2) kde-runtime [4:17.08.3-2.1 (now)] > 3) kopete [4:17.08.3-2.1 (now)] > 4) phonon [4:4.10.3-2 (now)] > 5) phonon-backend-gstreamer [4:4.9.1-1 (now)] > > Leave the following dependencies unresolved: > 6) kdelibs5-plugins recommends kde-runtime > 7) libkopete4 recommends kopete (= 4:17.08.3-2.1) As Luigi already indicated, you have old cruft (QT4) installed and you should get rid of them. The easiest way is to say Yes to the above suggestion. And then install phonon4qt5-backend-gstreamer, which will then also upgrade phonon-backend-gstreamer-common HTH signature.asc Description: This is a digitally signed message part.
Re: phonon-backend-gstreamer-common has been kept back
On dinsdag 12 november 2019 20:47:19 CET Miguel A. Vallejo wrote: > I noticed that phonon-backend-gstreamer-common have been keep back > since several weeks ago in Sid. If I try to update it manually apt > wants to remove the entire KDE. I don't have that problem on my Sid box. Can you share the output/result of "aptitude safe-upgrade phonon-backend-gstreamer-common" ? and if it's any different also from "full-upgrade"? signature.asc Description: This is a digitally signed message part.
Re: Upgrading to PostgreSQL 12
On zaterdag 2 november 2019 10:16:20 CET Martin Steigerwald wrote: > Hmmm, to me that looks like you are using a system wide PostgreSQL > database. I am using a user based one. > > For a PostgreSQL database using as the user and using ~/.local/share/ > akonadi/db_data the KDE Userbase wiki has some instructions: > https://userbase.kde.org/Akonadi/Postgres_update I wasn't even aware of a user based one and I don't have a ~/.local/share/ akonadi/db_data file/dir. I set up my akonadi DB following https://www.enricozini.org/blog/2015/akonadi-install/ > Also there might be an issue for user based PostgreSQL: > Akonadi refuses to start after upgrade to PostgreSQL 12: column > "version" of relation "schemaversiontable" already exists > https://bugs.kde.org/412629 I haven't seen that. > The Debian bug report https://bugs.debian.org/941763 For some (imo) weird reason every new version of PostgreSQL needs to be explicitly added to QT, which also means a new (minor) update to QT is needed. And that's why I never just upgrade to a new version of PostgreSQL before making sure QT supports it. All other packages I upgrade without further research (ofc I do have apt-listbugs installed to get notified of RC bugs) I should've done an akonadictl restart/fsck/vacuum after the upgrade, but didn't. I just did that and it had a collection with ~10k unreferenced RIDs (which is unusually large). I have no idea whether that had anything to do with the upgrade though. I just consider that an oddity with akonadi that happens from time to time. I also have to do 'akonadictl restart' twice before I see lines like this: Application '/usr/bin/akonadi_imap_resource' exited normally... Mail, calendar and contacts all seem to work after the upgrade and that's good enough for me. signature.asc Description: This is a digitally signed message part.
Upgrading to PostgreSQL 12
In Sid the various PostgreSQL packages have been upgraded to version 12 and I've just successfully upgraded to them. I've read people say that upgrading PostgreSQL was complicated, but that's not my experience. Here is what I did: - quit KMail/Kontact/etc $ akonadictl stop [$ stop any other programs if they use postgresql] # # pg_dropcluster --stop 12 main # pg_upgradecluster 11 main I then usually reboot the machine to make sure it'll use PostgreSQL 12 for akonadi. If you verified that KMail still works, you can remove the old cluster with # pg_dropcluster 11 main # If you were using postgresql-11-pg-checksums, you'll have to manually install postgresql-12-pg-checksums package HTH, Diederik signature.asc Description: This is a digitally signed message part.
Re: Akonadi 4:18.08.3-8 in experimental
Hi, On maandag 28 oktober 2019 12:33:30 CET Sandro Knauß wrote: > Mmh, okay now the question is, if Akonadi was functional before you deleted > that file. Yes, it was functional. AFAIK akonadi uses my OS credentials, so it doesn't/ shouldn't need any creds that could be stored in that file. > Because at least for me, I would argue, that AppArmor is blocking > the access to ~/.pgpass seems reasonable, as the Postgres database that > Akonadi spins up, don't need access to that file. Agreed. > That's what AppArmor is made for, to block applications to access files, that > they should not have access to. But I'm very new to the AppArmor world, > that's why I don't have any strong option. I don't know much about AppArmor either. I understand the general concept, but usually I'm mostly 'annoyed' by the pop-ups as I don't (really) know what to do about it and consequently just click them away. This issue about accessing ~/.pgpass is probably the first instance that I practically see the advantage of AppArmor. It's possibly useful to figure out whether this is a bug in akonadi or not. signature.asc Description: This is a digitally signed message part.
Re: Akonadi 4:18.08.3-8 in experimental
On vrijdag 25 oktober 2019 12:08:12 CEST John Scott wrote: > You probably have apparmor-notify installed which displays the > notifications. That is correct. signature.asc Description: This is a digitally signed message part.
Re: Akonadi 4:18.08.3-8 in experimental
On donderdag 24 oktober 2019 21:30:22 CEST Sandro Knauß wrote: > thanks for the reply. How this notification is displayed? Like any > notification e.g. "new mail" or is just seen in dmesg? I don't have "new mail" notifications, but I'd guess that's what I meant. Every time an issue with AppArmor happens I get a system/Plasma notification about it. I can then also view them through "Notifications" 'tab' from the system tray. HTH, Diederik signature.asc Description: This is a digitally signed message part.
Bug#940872: KDE Frameworks 5.62 coming to unstable
On donderdag 26 september 2019 22:56:08 CEST Bob Weber wrote: > Another trick that worked on 2 machines here is to set the numlock on in > /etc/sddm.conf. > > My general section of sddm.conf looks like this now: > > [General] > HaltCommand= > RebootCommand= > Numlock=on > > Hope this helps. This fixed the issue I had which I mentioned in the CC-ed bug reports. Thanks :-) signature.asc Description: This is a digitally signed message part.
Re: KDE Frameworks 5.62 coming to unstable
On donderdag 26 september 2019 22:56:08 CEST Bob Weber wrote: > Another trick that worked on 2 machines here is to set the numlock on in > /etc/sddm.conf. > > My general section of sddm.conf looks like this now: > > [General] > HaltCommand= > RebootCommand= > Numlock=on > > Hope this helps. This fixed the issue I had which I mentioned in the CC-ed bug reports. Thanks :-) signature.asc Description: This is a digitally signed message part.
Re: Akonadi 4:18.08.3-8 in experimental
On woensdag 23 oktober 2019 04:06:29 CEST Diederik de Haas wrote: > Right after sending that, I get the following notification: > Profile: /usr/bin/akonadiserver > Operation: open > Name: /home/diederik/.pgpass > Denied: r > Logfile: /var/log/kern.log > For more information, visit https://wiki.debian.org/AppArmor > > I've now gotten this 4 times (in a couple of minutes) In about 25 minutes I got 59 of them (grep "/home/diederik/.pgpass" /var/log/ kern.log | wc -l) Oct 23 04:22:19 bagend kernel: [ 1457.768963] audit: type=1400 audit(1571797339.880:116): apparmor="DENIED" operation="open" profile="/usr/ bin/akonadiserver" name="/home/diederik/.pgpass" pid=1882 comm="0x5633fb5bf4a0-" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Apart from timestamp and comm="0x" values, they're all exactly the same. $ ls -la .pgpass -rw--- 1 diederik diederik 0 mrt 10 2016 .pgpass My guess that file got automatically created sometime (pgadmin3?) or have created it myself but (apparently) emptied its contents. My first guess was to leave the file for debugging purposes, but a 0-byte file shouldn't be hard to recreate ;-) so I removed it. ... Approx 15 minutes later, I haven't had any more of those messages in either a notification window/popup or in /var/log/kern.log signature.asc Description: This is a digitally signed message part.
Re: Akonadi 4:18.08.3-8 in experimental
On woensdag 23 oktober 2019 04:02:45 CEST Diederik de Haas wrote: > On dinsdag 24 september 2019 22:30:38 CEST Sandro Knauß wrote: > > I uploaded Akonadi 4:18.08.3-8 to experimental, the main reason is, that I > > want to test further AppArmor support. If you use unstable, please give it > > a try and give feedback if you see any new issues. > > I just upgraded with "aptitude install ~i~V4:18.08.3-7 -t experimental" and > rebooted (to ensure everything would start fresh) and it seems to work. > Using PostgreSQL 11 here Right after sending that, I get the following notification: Profile: /usr/bin/akonadiserver Operation: open Name: /home/diederik/.pgpass Denied: r Logfile: /var/log/kern.log For more information, visit https://wiki.debian.org/AppArmor I've now gotten this 4 times (in a couple of minutes) signature.asc Description: This is a digitally signed message part.
Re: Akonadi 4:18.08.3-8 in experimental
On dinsdag 24 september 2019 22:30:38 CEST Sandro Knauß wrote: > I uploaded Akonadi 4:18.08.3-8 to experimental, the main reason is, that I > want to test further AppArmor support. If you use unstable, please give it a > try and give feedback if you see any new issues. I just upgraded with "aptitude install ~i~V4:18.08.3-7 -t experimental" and rebooted (to ensure everything would start fresh) and it seems to work. Using PostgreSQL 11 here signature.asc Description: This is a digitally signed message part.
Bug#931737: kdepim-runtime: Imap session login cancelled
On woensdag 16 oktober 2019 03:54:45 CEST you wrote: > you can change the config of OpenSSL to allow lower TLS versions to work. > Better would be to urge that mail provider to upgrade their mail software as > TLS < 1.2 really isn't secure. >From https://lists.debian.org/debian-kde/2018/11/msg1.html : Changing back the defaults in /etc/ssl/openssl.cnf to previous system wide defaults can be done using: MinProtocol = None CipherString = DEFAULT It's recommended that you contact the remote site in case the defaults cause problems. signature.asc Description: This is a digitally signed message part.
Re: Transition of Qt to 5.12.5
On maandag 21 oktober 2019 21:20:38 CEST Martin Steigerwald wrote: > Careful with "apt dist-upgrade" Use safe-upgrade signature.asc Description: This is a digitally signed message part.
Bug#940872: Bug#942654: kde-baseapps: Numlock state not changed per settings during startup or screenlock
On zaterdag 19 oktober 2019 19:18:36 CEST Brian R. wrote: > I've set numlock "on" at login in KDE system settings, but after recent > updates, the numlock state is no longer applied per user settings. Numlock > must be turned on manually. Sounds like you have the same problem as I reported here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940872#15 It seems to be the exact opposite of what the OP filed, but I suspect it's all the same issue. signature.asc Description: This is a digitally signed message part.
Bug#940872: plasma-framework: Num lock key is always ON at startup, even if in the configuration is forced to OFF
On zaterdag 21 september 2019 10:35:17 CEST Antonio wrote: > after updating to the kde 5.62 framework the num lock key is always on > at startup even if in the settings it was forced to stay off I have the same problem, but reverse. No matter what setting I have in Input Devices, it will not turn ON. This did work before. I also tried with a new user, but that made no difference. In my BIOS I have specified to turn NumLock on and when booting both Fn and Numlock lights are on. Same when GRUB loads. After that, both lights get turned off and during the boot sequence up until I see SDDM's login screen, the Fn light turns back on, but not the NumLock light. signature.asc Description: This is a digitally signed message part.
Bug#923200: libpolkit-qt5-1-1 depends on libpam-systemd
On woensdag 16 oktober 2019 16:25:51 CEST Joshua Hudson wrote: > Should I really have to provide an empty virtual package? I'm using > pam_group so sound keeps playing in bkg while current virtual console has > another user. At least one DD thinks it should be a dependency. I haven't yet seen a response from the package maintainer. https://bugs.debian.org/794537 seems to be the bug you want fixed. An alternative solution would indeed be to create a package yourself (locally) which "Provides: logind" signature.asc Description: This is a digitally signed message part.
Bug#935587: updating metadata
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=403950 Control: tag -1 upstream fixed-upstream signature.asc Description: This is a digitally signed message part.
Bug#931737: kdepim-runtime: Imap session login cancelled
On dinsdag 9 juli 2019 21:45:13 CEST Diego Russo wrote: > With Debian Buster akonadi does not work anymore with aruba imap server, My guess is that it is caused by the default configuration of OpenSSL 1.1, which requires TLS 1.2 iirc. If that aruba imap server is using old software that doesn't support that version, then it won't be able to connect. I ran into a seemingly similar situation when OpenSSL 1.1 entered Sid, but I can't remember if/where I wrote things down wrt this and/or reported it. But you can change the config of OpenSSL to allow lower TLS versions to work. Better would be to urge that mail provider to upgrade their mail software as TLS < 1.2 really isn't secure. Hopefully this gives you enough hints to search for the actual solution. signature.asc Description: This is a digitally signed message part.
Bug#923200: libpolkit-qt5-1-1 depends on libpam-systemd
On donderdag 11 juli 2019 21:53:33 CEST Demi wrote: > I have to agree with Joshua -- programs like marble or kdenlive work > just fine without systemd On woensdag 20 maart 2019 15:44:30 CEST Michael Biebl wrote: > The dependency seems correct. > policykit without a working logind session seems pretty much useless. Fixed in 0.112.0-7.1 (in Sid atm) ? >From changelog: * Apply patch from Mark Hindley to Use new logind virtual packages instead of libpam-systemd (Closes: #925344) signature.asc Description: This is a digitally signed message part.
Bug#918492: metadata
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=398324 signature.asc Description: This is a digitally signed message part.
Bug#940565: No problem here
Control: tag -1 +moreinfo +unreproducible Control: severity -1 important I noticed you specified the source package and not the binary package to report the bug against. Normally not much of an issue, but it looks like you didn't use or didn't share the whole output of reportbug, because it's missing the list of installed packages, which can be rather crucial. Note that there are 2 groups of binary packages: python-pyside2.* and python3- pyside2.* whereas the former is for python2 and the latter for python3. I didn't have any pyside2 packages installed, so I tried it with a clean slate: # aptitude install python3-pyside2.qtcore $ echo "import PySide2.QtCore as core" > test.py $ python test.py Traceback (most recent call last): File "test.py", line 1, in import PySide2.QtCore as core ImportError: No module named PySide2.QtCore $ python3 test.py $ This output is exactly as expected. If I install python-pyside2.qtcore, then the Traceback output disappears. As I couldn't reproduce the issue, I set the tags accordingly and as the issue doesn't happen for everyone, I lowered the severity. signature.asc Description: This is a digitally signed message part.
Bug#889919: Updating metadata
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=409375 signature.asc Description: This is a digitally signed message part.
