Re: [OT] initramfstools 0.144 safe to use?

[Diederik de Haas]

On Thu Aug 22, 2024 at 10:48 AM CEST, Martin Steigerwald wrote:
> Bug#1079273: initramfs-tools: Error with initramfs-tools during apt full-
> upgrade on Debian Sid and reiserfsck
>
> https://bugs.debian.org/1079273
>
> It is off topic, I know. But as the kmod warning really was helpful to me,
> I thought I just write this mail. This does not seem to be as severe as
> the kmod thing however.

Rule of thumb: If you see errors during generation of initramfs, do not
reboot but investigate first. If ``ls -lh /boot/initrd*`` does NOT show
anything out of the ordinary (wrt the updated initramfs), then you're
probably fine.

And in general: if there are problems, it's *very* likely APT warned you
about in advance and/or during execution.
So don't use `-y` and read what APT tells you and then use common sense.

With the kmod issue, I did see the errors mentioned in the bug
report(s), so I investigated it.
I reported it here given the severity AND it came *together* with KDE
related updates which could (and did) fix previous KDE related issues.
After those updates I wanted to reboot directly. Luckily I didn't
because I choose to first investigate the reported problem.
Given by the messages on #debian-next, that's apparently not something
that everyone does ;-P

Cheers,
  Diederik


signature.asc
Description: PGP signature

Re: DO NOT UPGRADE KMOD to 33+20240816-1

[Diederik de Haas]

On Wed Aug 21, 2024 at 5:41 PM CEST, Helge Reimer wrote:
> Am Montag, 19. August 2024, 16:58:15 CEST schrieb Sedat Dilek:
> > dracut-install package needs to be rebuilt against latest libkmod2.
>
> Xanmod Kernel was also updated and initramfs-tools ran smoothly.
> dracut-install version is 103-1.1

And version 103-1.1 is that rebuilt:

```
Changed-By: Marco d'Itri 
Changes:
 dracut (103-1.1) unstable; urgency=medium
 .
   * no changes non-maintainer upload to rebuild the package with a newer
 libkmod2 (see #1079022)
```
src: 
https://tracker.debian.org/news/1557452/accepted-dracut-103-11-source-into-unstable/


signature.asc
Description: PGP signature

Re: DO NOT UPGRADE KMOD to 33+20240816-1

[Diederik de Haas]

On Mon Aug 19, 2024 at 8:50 PM CEST, Diederik de Haas wrote:
> On Mon Aug 19, 2024 at 8:26 PM CEST, Sedat Dilek wrote:
> > From [1]:
> >
> > I have rebuilt dracut-install (103-1) against libkmod-dev:amd64 
> > (33+20240816-1).
> >
> > This fixes the issue for me.
> >
> > Link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug79031#26 [1]
> >
> > On Mon, Aug 19, 2024 at 4:58 PM Sedat Dilek  wrote:
> > >
> > > dracut-install package needs to be rebuilt against latest libkmod2.
> > >
> > > See Build-Depends-of dracut-install.
> > >
>
> Yes, the kmod maintainer already said that here:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug79022#10

Not sure what happened here, so proper link:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug79022#10



signature.asc
Description: PGP signature

Re: DO NOT UPGRADE KMOD to 33+20240816-1

[Diederik de Haas]

On Mon Aug 19, 2024 at 8:26 PM CEST, Sedat Dilek wrote:
> From [1]:
>
> I have rebuilt dracut-install (103-1) against libkmod-dev:amd64 
> (33+20240816-1).
>
> This fixes the issue for me.
>
> Link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug79031#26 [1]
>
> On Mon, Aug 19, 2024 at 4:58 PM Sedat Dilek  wrote:
> >
> > dracut-install package needs to be rebuilt against latest libkmod2.
> >
> > See Build-Depends-of dracut-install.
> >

Yes, the kmod maintainer already said that here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug79022#10

Would've been nice if some coordination would've happened that would
have rebuilt dracut-install upon/before uploading. But that didn't
happen, so warning others seemed like the next best thing.


signature.asc
Description: PGP signature

Re: DO NOT UPGRADE KMOD to 33+20240816-1

[Diederik de Haas]

On Mon Aug 19, 2024 at 11:54 AM CEST, Diederik de Haas wrote:
> Why report this to the KDE mailing list?
>
> Because yesterday I had what looks like a *partial* upgrade of KDE packages,
> and saw some 'funny' things* (which is ofc expected in Sid from time to time).
> ...
>
> *) I'm guessing that's what Aurélien's message is about ...

Note that I do NOT have any KDE (related) packages installed from
Experimental, which (IIUC) is what Aurélien's message is about.

My Dolphin icon is still black (instead of blue), but the (other)
'funny' things I did see are now fixed.
So AFAICT the (whole) bunch of libkf6* packages that (also) got
installed with today's Sid upgrade appear to be fine.

HTH,
  Diederik


signature.asc
Description: PGP signature

DO NOT UPGRADE KMOD to 33+20240816-1

[Diederik de Haas]

Why report this to the KDE mailing list?

Because yesterday I had what looks like a *partial* upgrade of KDE packages,
and saw some 'funny' things* (which is ofc expected in Sid from time to time).
So today I upgraded again and wanted to reboot immediately after that.
Then I noticed the following line/error:

/usr/lib/dracut/dracut-install: symbol lookup error: 
/usr/lib/dracut/dracut-install: undefined symbol: kmod_module_get_weakdeps, 
version LIBKMOD_5

Luckily I decided to investigate/report this problem before I rebooted ...
as through bug #1079022 and #1079031 I learned of people having unbootable
systems as a bug in kmod made my initramfs shrink from 37M to 9.5M!

So do NOT upgrade to kmod 33+20240816-1

If you already did downgrade kmod to the Testing version via (f.e.):

aptitude install kmod/testing libkmod2/testing

And then hold kmod to that version (32+20240611-1)

Cheers,
  Diederik

*) I'm guessing that's what Aurélien's message is about ...

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

Re: Kadressbook and Google

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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.

Re: Postpone update

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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?

[Diederik de Haas]

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!

[Diederik de Haas]

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!

[Diederik de Haas]

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!

[Diederik de Haas]

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!

[Diederik de Haas]

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!

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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.

Re: Plasma 5.23 upload to unstable is complete

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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.

Re: Digikam and 4:21

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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: Plasma 5.17.5 available in experimental

[Diederik de Haas]

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.

Re: phonon-backend-gstreamer-common has been kept back

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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.

Re: KDE Frameworks 5.62 coming to unstable

[Diederik de Haas]

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

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

Thanks :-)

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

Re: Akonadi 4:18.08.3-8 in experimental

[Diederik de Haas]

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

[Diederik de Haas]

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

[Diederik de Haas]

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.

Re: Transition of Qt to 5.12.5

[Diederik de Haas]

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.

Re: For those with a broken KMail

[Diederik de Haas]

On vrijdag 3 augustus 2018 01:08:06 CEST Diederik de Haas wrote:
> Just checked the available and installed kio packages and the one that stood
> out was kdepimlibs-kio-plugins, which is not installed on my system. So it
> can be that it should be defined as a Depends or Recommends (although new
> Recommends don't get automatically installed, so could just be a thing on
> my system).
> 
> Will install that package in a moment

That would install a whole bunch of qt4 stuff, so didn't do it


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

Re: For those with a broken KMail

[Diederik de Haas]

On woensdag 1 augustus 2018 01:00:28 CEST Lisandro Damián Nicanor Pérez Meyer 
wrote:
> If you upgraded and found that KMail is not showing the message bodies don't
> worry, please wait some more hours for the new kf5-messagelib upload.
> 
> Found the bug upstream and Maxy pointed me to the fix, I have tested it and
> it works.

That issue is indeed fixed, but upon starting Kontact/KMail I still get 'some' 
"KIO Exec error" with the following text in a popup screen.
(Plain text, not rendered)

File not found: data:text/html;charset=UTF-8,%3C%3Fxml version%3D%221.0%22 
encoding%3D%22utf-8%22%3F%3E%0A%3C%21DOCTYPE html PUBLIC %22-
%2F%2FW3C%2F%2FDTD XHTML 1.0 Transitional%2F%2FEN%22 
%22http%3A%2F%2Fwww.w3.org%2FTR%2Fxhtml1%2FDTD%2Fxhtml1-transitional.dtd%22%3E%0A%0A%3Chtml
 
xmlns%3D%22http%3A%2F%2Fwww.w3.org%2F1999%2Fxhtml%22%3E%0A%3Chead%3E%0A  
%3Cstyle type%3D%22text%2Fcss%22%3E%0A  %2F%2A%3C%21%5BCDATA%5B%2A%2F%0A
%40import %22main.css%22%3B%0A  %2F%2A%5D%5D%3E%2A%2F%0A%0A.links %7B%0A
margin%3A auto%3B%0A%7D%0A%0A.links td %7B%0Apadding-top%3A 5px%3B%0A
padding-bottom%3A 5px%3B%0A%7D%0A%0A  %3C%2Fstyle%3E%0A%0A  
%3Ctitle%3EKontact%3C%2Ftitle%3E%0A%3C%2Fhead%3E%0A%0A%3Cbody%3E%0A  %3Cdiv 
id%3D%22header%22%3E%3Cimg 
src%3D%22file%3A%2F%2F%2Fusr%2Fshare%2Ficons%2Fbreeze-dark%2Fapps%2F48%2Fkontact.svg%22
 align%3D%22top%22 height%3D%22128%22 
width%3D%22128%22 alt%3D%22kontact%22 title%3D%22%22 %2F%3E%0A%3Cdiv 
id%3D%22title%22%3E%0A%3Ch1%3EKontact%3C%2Fh1%3EThe KDE Personal 
Information Management Suite.%0A%3C%2Fdiv%3E%0A  %3C%2Fdiv%3E%0A%0A  
%3Cdiv id%3D%22box%22%3E%0A%3Cdiv id%3D%22boxInner%22%3E%0A%0A%3Cdiv 
class%3D%22center%22%3E%0A%3Ch2%3EWelcome to Kontact 5.7.3%3C%2Fh2%3E%0A
%3Cp%3EKontact handles your e-mail%2C address book%2C calendar%2C to-do list 
and more.%3C%2Fp%3E%0A%3C%2Fdiv%3E%0A%0A%3Ctable class%3D%22links%22%3E%0A
%3Ctr%3E%0A%3Ctd%3E%0A%3Ca 
href%3D%22exec%3A%2Fhelp%3Forg.kde.kontact%22%3E%3Cimg 
src%3D%22file%3A%2F%2F%2Fusr%2Fshare%2Ficons%2Fbreeze-dark%2Factions%2F22%2Fhelp-contents.svg%22
 align%3D%22top%22 height%3D%2248%22 
width%3D%2248%22 alt%3D%22help-contents%22 title%3D%22%22 %2F%3E%3C%2Fa%3E%0A   
 
%3Ctd%3E%0A%3Ctd%3E%0A%3Ca 
href%3D%22exec%3A%2Fhelp%3Forg.kde.kontact%22%3ERead 
Manual%3C%2Fa%3E%3Cbr%2F%3E%0A%3Csmall%3ELearn more about Kontact 
and its components%3C%2Fsmall%3E%0A%3C%2Ftd%3E%0A%3C%2Ftr%3E%0A
%3Ctr%3E%0A%3Ctd%3E%0A%3Ca 
href%3D%22http%3A%2F%2Fkontact.org%22%3E%3Cimg 
src%3D%22file%3A%2F%2F%2Fusr%2Fshare%2Ficons%2Fbreeze-dark%2Fapps%2F48%2Fkontact.svg%22
 align%3D%22top%22 height%3D%2248%22 
width%3D%2248%22 alt%3D%22kontact%22 title%3D%22%22 %2F%3E%3C%2Fa%3E%0A
%3Ctd%3E%0A%3Ctd%3E%0A%3Ca 
href%3D%22http%3A%2F%2Fkontact.org%22%3EVisit Kontact 
Website%3C%2Fa%3E%3Cbr%2F%3E%0A%3Csmall%3EAccess online resources 
and tutorials%3C%2Fsmall%3E%0A%3C%2Ftd%3E%0A%3C%2Ftr%3E%0A
%3Ctr%3E%0A%3Ctd%3E%0A%3Ca 
href%3D%22exec%3A%2Faccountwizard%22%3E%3Cimg 
src%3D%22file%3A%2F%2F%2Fusr%2Fshare%2Ficons%2Fbreeze-dark%2Factions%2F24%2Ftools-wizard.svg%22
 align%3D%22top%22 height%3D%2248%22 
width%3D%2248%22 alt%3D%22tools-wizard%22 title%3D%22%22 %2F%3E%3C%2Fa%3E%0A

%3Ctd%3E%0A%3Ctd%3E%0A%3Ca 
href%3D%22exec%3A%2Faccountwizard%22%3ESetup your 
Accounts%3C%2Fa%3E%3Cbr%2F%3E%0A%3Csmall%3EPrepare Kontact for 
use%3C%2Fsmall%3E%0A%3C%2Ftd%3E%0A
%3C%2Ftr%3E%0A%3C%2Ftable%3E%0A%0A%3Cspan%3E%3Ca 
href%3D%22exec%3A%2Fswitch%22%3ESkip this 
introduction%3C%2Fa%3E%3C%2Fspan%3E%0A%0A%3C%2Fdiv%3E%0A  
%3C%2Fdiv%3E%0A%3C%2Fbody%3E%0A%3C%2Fhtml%3E%0A%0A%3C%21-- vim%3Aset sw%3D2 et 
nocindent smartindent%3A --%3E%0A

Just checked the available and installed kio packages and the one that stood 
out was kdepimlibs-kio-plugins, which is not installed on my system.
So it can be that it should be defined as a Depends or Recommends (although 
new Recommends don't get automatically installed, so could just be a thing on 
my system).

Will install that package in a moment, but wanted to catch that 'very useful' 
error message first ;-)

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

Re: Kwallet does not work

[Diederik de Haas]

On zaterdag 5 mei 2018 17:50:59 CEST Diederik de Haas wrote:
> On zaterdag 5 mei 2018 17:39:18 CEST MERLIN Philippe wrote:
> > On Debian Sid AMD64
> > Since last update Kwallet is out, i don't know why and how i can correct
> > this problem.
> > 
> > What can i do, google does not help me.
> 
> See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897687
> and the issue seems to be fixed with kwallet-pam 5.12.1-3

Just installed that version and the problem indeed went away.
While the bug was reported with an OpenBox install, I noticed the issue today 
as well on my KDE/Plasma session (before I installed -3).


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

Re: Kwallet does not work

[Diederik de Haas]

On zaterdag 5 mei 2018 17:39:18 CEST MERLIN Philippe wrote:
> On Debian Sid AMD64
> Since last update Kwallet is out, i don't know why and how i can correct
> this problem.
> 
> What can i do, google does not help me.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897687
and the issue seems to be fixed with kwallet-pam 5.12.1-3


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

Re: KMail's folder pane

[Diederik de Haas]

On vrijdag 13 april 2018 18:43:16 CEST Lisandro Damián Nicanor Pérez Meyer 
wrote:
> There seems to be some bugs with Qt 5.10.1. Arch added three patches:
> 
>  se>
> 
> I'll definitely not be able to try them at very least until monday.
> Hopefully.

I can wait, it's at most a minor annoyance :-)


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

Re: KMail's folder pane

[Diederik de Haas]

On donderdag 12 april 2018 22:58:26 CEST Xavier Brochard wrote:
> > Try to reduce the size of the "Name" header. See screenshots 1 and 2
> 
> I've forgot something :
> Enable the Unread/Total/Size columns, then try to resize Name column, then
> close kmail and restart. Disable the Unread/Total/Size columns.
> Works for me.

That worked for me too ... until I closed kontact and started it up again.
And at other times the columns just re-appear out of the blue.

I guess it's time again to start with a brand new KDE system. Hopefully I can 
get Kontact/KMail working with PostgreSQL 10 on my laptop ...


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

KMail's folder pane

[Diederik de Haas]

From "Qt 5.10.1 transition just started" thread:
> > I just upgraded too and rebooted. Most things seem to work, but trying to
> > change a (mail) folder in KMail now doesn't do anything like it's not
> > registering the click on a folder at all. The 'Jump to Folder' (shortcut
> > 'J') does work and allowed me to see the message from this ML.
> 
> Turns out to be a false alarm.
> I quit KMail (Kontact really) and started it up again and then I saw 4
> columns instead of just 1 I was used to and only saw when I had the above
> described issue. Widening that pane so all columns were visible made me
> able to click it. And later on after hiding the extra columns, things were
> back to what I was used to and working 

Maybe it was there yesterday too, but I just noticed a horizontal scroll bar 
while there is no need for that. Looking more closely I see that there is 
another column, next to the Name column, which does not have a header and the 
area is completely empty. It doesn't look like there is a way to remove it, 
like I could with the Unread/Total/Size columns. Trying to manuallly resize 
the Name column doesn't work as it looks like it detects its the only column 
and so resizes itself back to the old state.

As usual, a picture is worth a 1000 words. See attachment.

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

Re: KDEPIM 17.12: pane that show message structure missing?

[Diederik de Haas]

On donderdag 12 april 2018 12:11:43 CEST Rob Brewer wrote:
> Thanks Xavier, but I have the same problem as Martin, but I can't find the
> option you suggested. The third menu here is "View" but I can't see any item
> that relates to "affichage" which is presumably "Display" in english.
> 
> kdepim Version: 4:17.12.3+5.101

The following was posted to debian-qt-kde ML, I assume by accident:

Use Settings, Configure Toolbar,
Move Show Message Structure

Reinhard


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

Re: Qt 5.10.1 transition just started

[Diederik de Haas]

On woensdag 11 april 2018 21:08:56 CEST Diederik de Haas wrote:
> I just upgraded too and rebooted. Most things seem to work, but trying to
> change a (mail) folder in KMail now doesn't do anything like it's not
> registering the click on a folder at all. The 'Jump to Folder' (shortcut
> 'J') does work and allowed me to see the message from this ML.

Turns out to be a false alarm.
I quit KMail (Kontact really) and started it up again and then I saw 4 columns 
instead of just 1 I was used to and only saw when I had the above described 
issue. Widening that pane so all columns were visible made me able to click 
it. And later on after hiding the extra columns, things were back to what I 
was used to and working :)


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

Re: Qt 5.10.1 transition just started

[Diederik de Haas]

On woensdag 11 april 2018 14:06:22 CEST Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Today it was safe for me to update on a machine with almost all the related
> packages involved. So far so good.

I just upgraded too and rebooted. Most things seem to work, but trying to 
change a (mail) folder in KMail now doesn't do anything like it's not 
registering the click on a folder at all. The 'Jump to Folder' (shortcut 'J') 
does work and allowed me to see the message from this ML.


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

Re: Qt 5.10.1 transition just started

[Diederik de Haas]

On zondag 8 april 2018 02:07:45 CEST Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Beware when you upgrade! 

This is a reminder that people should not use 'apt/aptitude full-upgrade' or 
'apt-get dist-upgrade'. You don't need it in 99.9% of the cases.
The 'apt upgrade' and 'aptitude safe-upgrade' commands contain sanity checks 
which prevent you from breaking packages (dependencies).

If you do 'aptitude safe-upgrade' and it then says 'and 83 not upgraded', that 
is fine. Usually it's 0 or equal to the number of packages I've put on hold 
myself, but especially during Qt transitions it tend to get (this) high.

The right response is to wait.

It can take a few days, but it'll sort itself out over time.
If I think it's taking too long (usually a week, but I give Qt transitions a 
bit more time), I do 'aptitude full-upgrade -s'. The '-s' stands for simulate 
and it will tell you what it will do without actually doing it (you can do 
this as normal user too).
It will then tell you which packages will break with a full-upgrade and why.

In most cases you can then conclude that apt/aptitude was indeed smart and you 
should just wait a bit more.

There is another case and that is when it needs to remove a package which is 
marked as *manually* installed. With 'aptitude safe-upgrade' it has no problem 
removing packages marked as automatically installed (as dependency from 
another package). But it will not touch packages marked as manually installed 
with the logic "Apparently you have your reasons and I'll respect that".

It could be that a package is marked as manually installed, but being marked 
as automatically installed would be more appropriate. Library packages in most 
cases should be marked as automatically installed for example.
You can change the state with 'aptitude markauto ' or 'aptitude 
unmarkauto ' and thereby improve the state of your package manager.

With 'aptitude search '~i!?automatic' or '~i!~M' (they do exactly the same) 
you'll get a list of installed packages which are marked as manually (=not 
automatic) installed.
See 'Search term reference' on https://aptitude.alioth.debian.org/doc/en/
ch02s04s05.html or in your preferred aptitude-doc package for all kinds of 
search terms you can use to tailor your search result.
You often can just place those next to each other ('~i' + '!~M' above) but if 
you're not getting results you expected, try combining them with '?
narrow(term1, term2)' like this:
aptitude search '?narrow(~i!~M~slibs,~n^lib)'

HTH,
  Diederik

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

Re: Issues Setting Up KDE Development Environment in Stretch

[Diederik de Haas]

On maandag 26 februari 2018 10:14:39 CET Christian Hilberg wrote:
> This even works with foreign architectures, as long as QEMU supports
> them. For the Raspi, I set up a Raspbian-Lite chroot, copy
> /usr/bin/qemu-arm-static into it, and am good to go for cross-development on
> my host.

Do you have some more details you can share about this? (i.e. precise 
instructions)

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

Re: Some KDE applications still outdated

[Diederik de Haas]

On woensdag 29 november 2017 02:55:45 CET Marco Valli wrote:
> Maxi, thanks and you have all my solidarity - for what it's worth...

LOL.

Maxi has done a lot on updating packages, but this round I  saw a whole lot of 
Pino. So, thanks Pino for your work!

Cheers,
  Diederik


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

Re: libblockdev-part2

[Diederik de Haas]

On donderdag 31 augustus 2017 10:25:23 CEST Jimmy Johnson wrote:
> As you can probably see, I'm trying to figure what is stopping 
> libblockdev-part2 from being upgraded..

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873748
But it has been fixed now, so the updated binaries shouldn't take long to 
arrive in the archives and thereby resolve the dependency issue.


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

Re: Warning! Current udisks2 in Sid is broken

[Diederik de Haas]

On donderdag 31 augustus 2017 00:31:17 CEST Miguel A. Vallejo wrote:
> The following packages have unmet dependencies:
> libblockdev-part2 : Depends: sgdisk (>= 0.8.6) but it is not installable
> 
> Package sgdisk is not available, but is referred to by another package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
> 
> E: Package 'sgdisk' has no installation candidate
> 
> It is still broken.

Correct. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873748


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

Re: Qt 5.7.1 => 5.9.1

[Diederik de Haas]

On woensdag 16 augustus 2017 08:56:52 CEST Martin Steigerwald wrote:
> Please be careful to wait till its complete. Use
> 
> apt upgrade
> 
> instead of
> 
> apt dist-upgrade

Imo, one should only use dist-upgrade when you want to force something 
(different from the '-f' parameter), which normally involves (removing)  
manually installed packages. 
Otherwise there is no need for it or you probably shouldn't do it anyway, just 
wait till the next update and that will likely solve it.


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

Re: improving the UX with the default KDE installation

[Diederik de Haas]

Hi Maxy!

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

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

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

Re: improving the UX with the default KDE installation

[Diederik de Haas]

On vrijdag 31 maart 2017 13:27:14 CEST Maximiliano Curia wrote:
> if you prepare a diff of the changes with a rationale for each change we'll
> consider  them. But please take into account that statements like "I don't
> use it" are no reason enough to drop a dependency as the specific tool
> surely provides a functionality to the desktop user.

ping https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840844 ?
(it's about adding kdeconnect to kde-standard)

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

Re: Kmail attachment and drag and drop

[Diederik de Haas]

On maandag 23 januari 2017 09:05:13 CET Valerio Passini wrote:
> Maybe I'm wrong but I recall that some versions ago kmail was able to put 
> attachments in a message simply by drag'n'dropping a file from dolphin. Now 
> doing this simple action gives as a result a line in the message leading to
> the real attachment that instead is not attached at all (for example
> file:///home/ valerio/Documents/blahblah.file)

I thought it was possible too, but I encountered the same thing yesterday when 
trying drag-n-drop. 
I think it worked with KMail2 as well, but maybe I'm mistaken.

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

Re: Not able to use OpenGL contexts on Plasma

[Diederik de Haas]

On vrijdag 25 november 2016 14:24:18 CET Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Example: install qtbase5-examples and run:
> 
>   /usr/lib//qt5/examples/widgets/graphicsview/chip/chip
> 
> The chip example starts perfectly but after clicking on "OpenGL" on any of
> the  views either a black screen or a static image of the chips is showed.

I've tried it and it works fine here with the nvidia-driver package installed. 
What could also be relevant is that "xserver-xorg-core xserver-xorg-input-
evdev xserver-xorg-video-fbdev xserver-xorg-video-nouveau" on my system 
haven't been upgraded yet as the nvidia-driver doesn't support the new xorg 
ABI yet.

HTH,
  Diederik

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

Re: KDE Frameworks 5.28.0

[Diederik de Haas]

On woensdag 23 november 2016 23:04:04 CET Martin Steigerwald wrote:
> upgrade / safe-upgrade holds packages back if installing them would cause
> new  packages to be installed or installed ones to be removed. dist-upgrade
> / full- upgrade upgrades these too.

Wrong. It won't remove _manually_ installed packages and for good reason as 
you explicitly installed those. And this time I'll leave it at that


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

Re: Some problems with the last updates

[Diederik de Haas]

On zaterdag 5 november 2016 20:25:32 CET Andrey Rahmatullin wrote:
> > If so, that is/was your problem and you'll likely have various qt5 package
> > at  version 5.7.1~20161021+dfsg-N.
> > Downgrade those packages to their version in testing and there's a
> > reasonable  chance things start working again. See also
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843208#10

The current state is that it's highly likely that a bug in qtdeclarative-
opensource-src (source package) version 5.7.1~20161021-4 is the cause for the 
issue various people are seeing.
One of the Debian Qt maintainers filed the following bug for it: 
https://bugreports.qt.io/browse/QTBUG-56932

In Debian the following bugs have been reported which are likely all caused by 
this issue:
https://bugs.debian.org/843250
https://bugs.debian.org/843332

and probably more will follow ...

> I wonder if rebuilding some packages locally is easier than downgrading a
> lot of packages? If yes, which ones?

No, that will not help you or anyone else, since the problem is in an 
(important) part of qt5 5.7.1 itself.
As you (Andrey) already noticed and reported back, downgrading to the version 
in testing works and I think that it is the only solution for now.
Aptitudes resolver should be able to help in downgrading all those packages.

HTH,
  Diederik

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

Re: Some problems with the last updates

[Diederik de Haas]

On zaterdag 5 november 2016 09:08:36 CET Valerio Passini wrote:
> 2 - My plasma session is damaged. Don't know exactly what it's missing but
> plasmashell crashes on login leaving a black screen and the applications
> launched in the previous session (luckily konsole).
> Please, can you tell me some fixes?

Did you do 'apt-get dist-upgrade'? 
If so, that is/was your problem and you'll likely have various qt5 package at 
version 5.7.1~20161021+dfsg-N.
Downgrade those packages to their version in testing and there's a reasonable 
chance things start working again. See also 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843208#10

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

Re: Compositing Problem

[Diederik de Haas]

On donderdag 27 oktober 2016 02:38:10 CEST Jimmy Johnson wrote:
> Downgrading to Jessie-backports  works, but cause package management
> problems. I wonder if backporting  the free driver would work too.

Not likely. It would only work if both nouveau and nvidia had a working driver 
and both introduced a bug around the same time which made it not work.
It can happen, but statistically highly unlikely.

The jessie-backports workaround was just to get back to an older known working 
driver and apparently ppl found that easier then using snapshot.debian.org.

When you're using testing or sid, I highly recommend getting familiar with 
snapshot.debian.org as it allows you to downgrade to any version that was 
released to debian.

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

Re: Compositing Problem

[Diederik de Haas]

On donderdag 20 oktober 2016 11:04:54 CEST David Baron wrote:
> 1. Previous bug reassigned to 304xx of AceofPeguins Freecell game failing
> to  start apparently healed itself, no new 304xx so maybe something else!

I haven't seen a reference to that bug in this discussion, so here it is:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840342



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

Re: Compositing Problem

[Diederik de Haas]

On donderdag 20 oktober 2016 08:53:50 CEST Thom Castermans wrote:
> running nvidia-debugdump --list

Or run nvidia-detect and it'll tell you straight away which driver is most 
appropriate.


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

Re: plasma 5.8 upgrade - white desktop i.s.o. sddm login

[Diederik de Haas]

On zondag 9 oktober 2016 21:50:27 CEST Luc Castermans wrote:
> Don't think missing kwin is the problem. 

Agreed.

> I notice an awfull lot, 1048 kworker processes running. is this normal?

I have 21, so 1048 seems (a bit) excessive.

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

Re: plasma 5.8 upgrade - white desktop i.s.o. sddm login

[Diederik de Haas]

On zondag 9 oktober 2016 16:37:33 CEST Luc Castermans wrote:
> Could I still be missing packages?

At what version is kwin? That package had to go through NEW and was therefor 
added to the archives later then the others, but it is available now.

If you didn't use 'aptitude safe-upgrade', you may want to do so in the future 
as it would've hold of upgrades which weren't ready ;-)

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

Re: kf5 5.25 in testing, systray elements not working

[Diederik de Haas]

On donderdag 1 september 2016 11:49:55 CEST Andy G Wood wrote:
> The fix for this may have already been posted in debian-kde:
> 
> From: Diederik de Haas 
> Subject: Re: KDE Frameworks 5.25 and KDE Applications 16.08
> Date: Thu, 25 Aug 2016 17:19:23 +0200
> 
> > When you miss several icons in the systray (and their functionality),
> > make 
> > sure you 'Unlock Widgets' and log out and back in again.
> > This is reported at https://bugs.debian.org/835383

It gets even better with the recent uploads/upgrades in sid, likely plasma-
workspace and plasma-desktop to version 5.7.4-1, as it looks like it works 
again with Locked Widgets too :-)

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

Re: Plasma 5.7.2 in Debian?

[Diederik de Haas]

On zaterdag 27 augustus 2016 23:12:50 CEST Luigi Toscano wrote:
> It's probably not this case, but in general safe-upgrade is not enough. 

I disagree. In general safe-upgrade is enough and only in 'exceptional' cases 
it is not.

> In some cases you need to remove a package to proceed and safe-upgrade (if I
> read its documentation correctly (*)) does not do that. So the status is
> fine when it's full-upgrade-proof (aka apt dist-upgrade).

Then either the documentation is outdated or it states that *manually* 
installed packages are not removed with safe-upgrade.
So if you do 'aptitude install ' then pkg1 will not be removed with 
'aptitude safe-upgrade' and imo that is the proper behavior as you've made 
explicit that you want pkg1 installed.

But if a package gets installed because it is a dependency or a recommends and 
thus marked as *automatically* installed, then safe-upgrade will remove it 
once it has determined that no other package needs it (depends/recommends).

There are cases where you do need to use full-upgrade, but that very likely 
means that a package is marked as manually installed, while it should've been 
marked as automatically installed. You can change that state through 'aptitude 
markauto ' or 'aptitude unmarkauto '.
And with that you can configure your system in a way that 'aptitude safe-
upgrade' really is all you need.

HTH,
  Diederik

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

Re: Plasma 5.7.2 in Debian?

[Diederik de Haas]

On zaterdag 27 augustus 2016 22:49:00 CEST Luigi Toscano wrote:
> Nothing breaks for me, because I have all 5.6.x packages on hold. The fact
> that 3 or 4 different users on IRC (including a DD) had their plasma-desktop
> packages removed means that there is a conflict $somewhere.

I was one of them and the problem was because I used plasma-discover (for the 
first time) on my laptop to update packages instead of aptitude what I normally 
do. While it did update several packages, it removed several others like 
plasma-desktop, plasma-workspace, sddm and a bunch of other critical packages 
for KDE *without* informing me about it and thus completely broke my KDE 
system.
The DD in question didn't pay proper intention and missed that the upgrade on 
his system would remove sddm and others.
On my desktop PC, I have several packages that don't get upgraded with 
'aptitude safe-upgrade' precisely because it would brake things. 
If I'd do 'aptitude full-upgrade' it would indeed remove a bunch of packages, 
including plasma-desktop and thus I don't do that.

> > I do think however it would be good to have all of plasma at same major 
> > version at least. So I love to see these in the newer version as well.
> 
> It's not a matter of good or bad, it's the same as Frameworks: maybe with
> some exceptions of "leaf" packages (like the icons for Frameworks), but the
> core packages should be available in the same version.

And that's precisely what's now being enforced and thus 'aptitude safe-
upgrade' won't upgrade to these latest packages until all relevant packages 
are at the same versions.

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