Re: Warning to Plasma 6 / experimental users
Aurélien COUDERC - 19.08.24, 01:04:10 CEST: > TDLR : > *DON’T* upgrade to : > - libkf5globalaccel* version 5.115.0-6 > - libkf5plasma* and plasma-framework version 5.115.0-5 > it will break. > > *WAIT FOR* : > - libkf5globalaccel* version 5.115.0-7~exp1 > - libkf5plasma* and plasma-framework version 5.115.0-6~exp1 Thank you! I appreciate it. Best, -- Martin
Some feedback on KDE6 install
Hi, First a big thank to everyone involved. It was nearly smooth. I was running unstable + some experimental stuff and did: apt -t experimental install plasma-desktop kgamma digikam frameworkintegration6 powerdevil kscreen libkscreenlocker6 plasma-widgets-addons sddm Everything when well. And I then restarted. sddmd did pop up and I tough it was already fine. However when I logged in, the screen went back, stay so for one minute or so and then I was back to sddm prompt. So I though some pacage where missing and did an experimental upgrade from console login. I saw that some packages like dokphin, kwrite, kgamma, ... were missing and installed them. Just to discover that this did not fix the problem. So I was about to change my session type to fvwm that I keep when kde breaks, just to realize that during sddm upgrade, the session type was not set to plasma-x11. Changing it back to it, made login work successfully. I still have some minor annoyance (my taste): 1) The list of recent element is empty and generates errors on sqlite, 2) When using main menu to shutdown, I had the habit to use sleep instead of shutdown. Now I see only shutdown or cancel. 3) The battery icon is not always displayed. I have to enter the "hidden icons" menu to see it. Found no way to make it stick on menu bar. SOme other icons that I had are still there. Dunno why specifically this one disapperared. I do see the sleep option when I get back to the prompt after letting the PC unused. I can also use a special key. So far so good. Thanks for the good work. -- eric
DO NOT UPGRADE KMOD to 33+20240816-1
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: DO NOT UPGRADE KMOD to 33+20240816-1
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
Re: DO NOT UPGRADE KMOD to 33+20240816-1
Diederik de Haas - 19.08.24, 11:54:35 CEST: > 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! Thank you. Much appreciated. I decided to rather not do any update today or so :) and see from there. -- Martin
Re: Smaller Plasma bugs in unstable
Le lundi 19 août 2024, 12:15:19 CEST Diederik de Haas a écrit : > 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. Yes. And unstable should be again fully installable, and supporting both kf5 applications like Gear that we currently ship, and kf6 applications like Digikam. > 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. Yes, I saw that. Dolphin icon in Plasma and folder icons inside Gwenview (and probably other places) are black. Curriously enough, folder icons *inside* dolphin itself and in file browsing popups are fine. That’s the only issue I could find now that we’re running a dual kf5+kf6 stack and I don’t consider it a blocker. I’m betting on a small breakage of backwards compatibility in breeze-icons (which is supposed to be backwards compatible), or maybe just in our packaging ? If someone can analyse and find a fix I’m willing to upload it. But I won’t look into it myself, it’s both transitional and cosmetic issue and there are more important things to do. It’s fixed in Plasma 6 which is not 100% ready for unstable prime time yet. Happy hacking, -- Aurélien
Re: DO NOT UPGRADE KMOD to 33+20240816-1
dracut-install package needs to be rebuilt against latest libkmod2. See Build-Depends-of dracut-install. Diederik de Haas schrieb am Mo., 19. Aug. 2024, 12:02: > 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 ...
Re: DO NOT UPGRADE KMOD to 33+20240816-1
>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?bug=1079031#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. > > Diederik de Haas schrieb am Mo., 19. Aug. 2024, 12:02: >> >> 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 ...
Re: DO NOT UPGRADE KMOD to 33+20240816-1
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
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
ssh-agent not autostarting with Plasma 6
One of the lingering issues that now require a manual workaround for me is that ssh-agent isn't autostarting with Plasma 6 (installed in testing from experimental + unstable). With Plasma 5, systemd would start ssh-agent in user mode, but something isn't working out in Plasma 6 set up. The way I start it manually after each log-in: systemctl --user start ssh-agent Is it some upstream bug or something Debian specific in the mix of Plasma 6 systemd unit config files and openssh-client ones for ssh-agent? Does it work for anyone and may be I'm missing something? If not, should I file a bug, but not sure for which package or may be upstream? Thanks! Shmerl.
