Your message dated Sun, 8 Feb 2026 12:09:47 +0100
with message-id
<calxbnguz6cnmc3svuu8zdgrjckp8ecbzv1w634cuxqdrrk4...@mail.gmail.com>
and subject line Re: Bug#1125491: Acknowledgement (full-upgrade: Fresh KDE
plasma install, switching sources to testing, 'update && upgrade &&
full-upgrade' results in libopenconnect5, libpskc0t64, plasma-nm,
plasma-welcome being removed)
has caused the Debian Bug report #1125491,
regarding full-upgrade: Fresh KDE plasma install, switching sources to testing,
'update && upgrade && full-upgrade' results in libopenconnect5, libpskc0t64,
plasma-nm, plasma-welcome being removed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1125491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125491
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: full-upgrade
Severity: critical
Justification: breaks unrelated software
X-Debbugs-Cc: [email protected]
Debian testing with KDE plasma breaks on a fresh install.
- A fresh install with default settings, gnome disabled and KDE Plasma enabled.
- Making the user administrator through the users-setting.
- Disabling the updates source, changing trixie to testing in the
/etc/apt/sources.list
- sudo apt update
- sudo apt upgrade
- sudo apt full-upgrade
This results in the packages libopenconnect5, libpskc0t64, plasma-nm,
plasma-welcome being removed.
This has been tested today and yesterday, on two different pieces of hardware,
located on two different locations.
Installing the system with gnome instead of KDE Plasma does work and doesn't
result in these packages being removed
-- System Information:
Debian Release: forky/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.63+deb13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
I've re-run the steps as described above and come to the conclusion that
the issue is no longer present. Closing due to being fixed.
On Wed, 14 Jan 2026 at 20:49, Debian Bug Tracking System <
[email protected]> wrote:
> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 1125491:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125491.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> As you requested using X-Debbugs-CC, your message was also forwarded to
> [email protected]
> (after having been given a Bug report number, if it did not have one).
>
> If you wish to submit further information on this problem, please
> send it to [email protected].
>
> Please do not send mail to [email protected] unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1125491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125491
> Debian Bug Tracking System
> Contact [email protected] with problems
>
--- End Message ---
