Update has left packages in malformed state

Board index

Page 1 of 1 (6 posts)

Tags:

sandres Registered Member Posts 6 Karma 0	Update has left packages in malformed state Tue Feb 12, 2019 1:31 pm Hi, after updating yesterday I could not login using sddm or console. sddm just seemed to hang while pressing enter on the console seemed to press in an endless loop :/ Logging in from SSH and then getting a user session I tried to update again and the dependencies are messed up it seems: Code: Select all Entering ResolveByKeep 10% Dependencies are not satisfied for libkwinxrenderutils12:amd64 < none -> 4:5.15.0-0xneon+18.04+bionic+build27 @un uN Ib > Keeping package libkwinxrenderutils12:amd64 Dependencies are not satisfied for kwin-common:amd64 < 4:5.14.5-0xneon+18.04+bionic+build26 -> 4:5.15.0-0xneon+18.04+bionic+build27 @ii umU Ib > Keeping package kwin-common:amd64 Dependencies are not satisfied for kwin-common:amd64 < 4:5.14.5-0xneon+18.04+bionic+build26 \| 4:5.15.0-0xneon+18.04+bionic+build27 @ii umH Ib > Package kwin-common:amd64 kwin-common:amd64 Depends on kwin-data:amd64 < 4:5.14.5-0xneon+18.04+bionic+build26 -> 4:5.15.0-0xneon+18.04+bionic+build27 @ii umU > (= 4:5.14.5-0xneon+18.04+bionic+build26) Keeping Package kwin-data:amd64 due to Depends Dependencies are not satisfied for libkwineffects12:amd64 < none -> 4:5.15.0-0xneon+18.04+bionic+build27 @un uN Ib > Keeping package libkwineffects12:amd64 Dependencies are not satisfied for libkwinglutils12:amd64 < none -> 4:5.15.0-0xneon+18.04+bionic+build27 @un uN Ib > Keeping package libkwinglutils12:amd64 Dependencies are not satisfied for kde-style-breeze:amd64 < 4:5.14.5-0xneon+18.04+bionic+build25 -> 4:5.15.0-0xneon+18.04+bionic+build26 @ii umU Ib > Keeping package kde-style-breeze:amd64 Dependencies are not satisfied for kwin-x11:amd64 < 4:5.14.5-0xneon+18.04+bionic+build26 -> 4:5.15.0-0xneon+18.04+bionic+build27 @ii umU Ib > Keeping package kwin-x11:amd64 Dependencies are not satisfied for kde-style-breeze-qt4:amd64 < 4:5.14.5-0xneon+18.04+bionic+build25 -> 4:5.15.0-0xneon+18.04+bionic+build26 @ii umU Ib > Keeping package kde-style-breeze-qt4:amd64 Dependencies are not satisfied for breeze:amd64 < 4:5.14.5-0xneon+18.04+bionic+build25 -> 4:5.15.0-0xneon+18.04+bionic+build26 @ii umU Ib > Keeping package breeze:amd64 Dependencies are not satisfied for breeze:amd64 < 4:5.14.5-0xneon+18.04+bionic+build25 \| 4:5.15.0-0xneon+18.04+bionic+build26 @ii umH Ib > Package breeze:amd64 breeze:amd64 Depends on breeze-cursor-theme:amd64 < 4:5.14.5-0xneon+18.04+bionic+build25 -> 4:5.15.0-0xneon+18.04+bionic+build26 @ii umU > (= 4:5.14.5-0xneon+18.04+bionic+build25) Keeping Package breeze-cursor-theme:amd64 due to Depends Dependencies are not satisfied for breeze:amd64 < 4:5.14.5-0xneon+18.04+bionic+build25 \| 4:5.15.0-0xneon+18.04+bionic+build26 @ii umH Ib > Dependencies are not satisfied for breeze:amd64 < 4:5.14.5-0xneon+18.04+bionic+build25 \| 4:5.15.0-0xneon+18.04+bionic+build26 @ii umH Ib > Dependencies are not satisfied for breeze:amd64 < 4:5.14.5-0xneon+18.04+bionic+build25 \| 4:5.15.0-0xneon+18.04+bionic+build26 @ii umH Ib > Package breeze:amd64 breeze:amd64 Depends on kwin-style-breeze:amd64 < 4:5.14.5-0xneon+18.04+bionic+build25 -> 4:5.15.0-0xneon+18.04+bionic+build26 @ii umU > (= 4:5.14.5-0xneon+18.04+bionic+build25) Keeping Package kwin-style-breeze:amd64 due to Depends Dependencies are not satisfied for breeze:amd64 < 4:5.14.5-0xneon+18.04+bionic+build25 \| 4:5.15.0-0xneon+18.04+bionic+build26 @ii umH Ib > Dependencies are not satisfied for breeze:amd64 < 4:5.14.5-0xneon+18.04+bionic+build25 \| 4:5.15.0-0xneon+18.04+bionic+build26 @ii umH Ib > Dependencies are not satisfied for breeze:amd64 < 4:5.14.5-0xneon+18.04+bionic+build25 \| 4:5.15.0-0xneon+18.04+bionic+build26 @ii umH Ib > Package breeze:amd64 breeze:amd64 Depends on qml-module-qtquick-controls-styles-breeze:amd64 < 4:5.14.5-0xneon+18.04+bionic+build25 -> 4:5.15.0-0xneon+18.04+bionic+build26 @ii umU > (= 4:5.14.5-0xneon+18.04+bionic+build25) Keeping Package qml-module-qtquick-controls-styles-breeze:amd64 due to Depends Dependencies are not satisfied for libkwin4-effect-builtins1:amd64 < 4:5.14.5-0xneon+18.04+bionic+build26 -> 4:5.15.0-0xneon+18.04+bionic+build27 @ii umU Ib > Keeping package libkwin4-effect-builtins1:amd64 Dependencies are not satisfied for kwin-wayland:amd64 < 4:5.14.5-0xneon+18.04+bionic+build26 -> 4:5.15.0-0xneon+18.04+bionic+build27 @ii umU Ib > Keeping package kwin-wayland:amd64 Dependencies are not satisfied for kwin-wayland-backend-drm:amd64 < 4:5.14.5-0xneon+18.04+bionic+build26 -> 4:5.15.0-0xneon+18.04+bionic+build27 @ii umU Ib > Keeping package kwin-wayland-backend-drm:amd64 Policy breaks with upgrade of plasma-desktop:amd64 < 4:5.14.5-0xneon+18.04+bionic+build33 -> 4:5.15.0-0xneon+18.04+bionic+build34 @ii umU IPb > Keeping package plasma-desktop:amd64 Dependencies are not satisfied for plasma-desktop:amd64 < 4:5.14.5-0xneon+18.04+bionic+build33 \| 4:5.15.0-0xneon+18.04+bionic+build34 @ii umH Ib > Package plasma-desktop:amd64 plasma-desktop:amd64 Depends on plasma-desktop-data:amd64 < 4:5.14.5-0xneon+18.04+bionic+build33 -> 4:5.15.0-0xneon+18.04+bionic+build34 @ii umU > (= 4:5.14.5-0xneon+18.04+bionic+build33) Keeping Package plasma-desktop-data:amd64 due to Depends Dependencies are not satisfied for plasma-workspace:amd64 < 4:5.14.5-0xneon+18.04+bionic+build23 -> 4:5.15.0-0xneon+18.04+bionic+build24 @ii umU Ib > Keeping package plasma-workspace:amd64 Dependencies are not satisfied for plasma-workspace-wayland:amd64 < 4:5.14.5-0xneon+18.04+bionic+build23 -> 4:5.15.0-0xneon+18.04+bionic+build24 @ii umU Ib > Keeping package plasma-workspace-wayland:amd64 Calculating upgrade... Done The following packages have been kept back: breeze breeze-cursor-theme kde-style-breeze kde-style-breeze-qt4 kwin-common kwin-data kwin-style-breeze kwin-wayland kwin-wayland-backend-drm kwin-x11 libkwin4-effect-builtins1 plasma-desktop plasma-desktop-data plasma-workspace plasma-workspace-wayland qml-module-qtquick-controls-styles-breeze 0 upgraded, 0 newly installed, 0 to remove and 16 not upgraded. Is this already known? Kind regards, Sascha
apachelogger KDE Developer Posts 525 Karma 5 OS	Re: Update has left packages in malformed state Tue Feb 12, 2019 1:40 pm https://neon.kde.org/faq#command-to-update Annoyed with bbcode since 1999.
sandres Registered Member Posts 6 Karma 0	Re: Update has left packages in malformed state Tue Feb 12, 2019 1:54 pm Hi, did not know about `pkcon`. Updating a third time using discover solved it. Thanks. Looking how to change my flow of having my system up to date with `pkcon`. Anyhow, three apt repositories I use (chrome, vivaldi and erlang) are disabled according to pkcon refresh but they are not commented out in sources. According to man there is `repo-enable` but why (as other third party repos are not disabled) does `pkcon` handle them as disabled? Kind regards, Sascha
dfear Registered Member Posts 2 Karma 0	Re: Update has left packages in malformed state Fri Feb 15, 2019 1:23 am apachelogger wrote:https://neon.kde.org/faq#command-to-update Thanks. Didn't know these commands existed, always used "sudo apt update && sudo apt upgrade" or plasma discover to update my system.
dfear Registered Member Posts 2 Karma 0	Re: Update has left packages in malformed state Fri Feb 15, 2019 1:25 am Hi ran "pkcon refresh" followed by "pkcon update", and all the dependency problems disappeared. So how is pkcon able to fix problems that apt couldn't?
acheronuk KDE Developer Posts 122 Karma 2	Re: Update has left packages in malformed state Fri Feb 15, 2019 4:41 am dfear wrote:So how is pkcon able to fix problems that apt couldn't? apt could almost certainly have resolved this just as pkcon did if you had used the correct command. You said you use 'apt upgrade', which is wrong for Neon. If using apt, you should use 'apt full-upgrade' (or 'apt-get dist-upgrade' if going old school) with Neon, as Neon from time to time needs to remove old obsolete packages to make an upgrade work. 'pkcon update' handles that issue, as does 'apt full-upgrade' whereas 'apt upgrade' does not. This is why Neon recommends pkcon, as it has that one simple command that handles both cases. The apt man page: http://manpages.ubuntu.com/manpages/bio ... apt.8.html upgrade upgrade is used to install available upgrades of all packages currently installed on the system from the sources configured via sources.list(5). New packages will be installed if required to satisfy dependencies, but existing packages will never be removed. If an upgrade for a package requires the remove of an installed package the upgrade for this package isn't performed. full-upgrade full-upgrade performs the function of upgrade but will remove currently installed packages if this is needed to upgrade the system as a whole.