System is rendered useless after Plasma 5.4.3 update KDEInit couldn't launch

[Ed Greshko]

On 11/17/2015 11:01 AM, Sudhir Khanger wrote:
> ---- On Sun, 15 Nov 2015 13:45:16 +0530 *Ed Greshko <ed.greshko at greshko.com>* wrote ---- 
>
>     I really needed to get some work done so I did
>
>     dnf downgrade --allowerasing plasma-breeze plasma-breeze-common plasma-desktop
>     plasma-desktop-doc plasma-milou plasma-nm plasma-nm-mobile plasma-nm-openconnect
>     plasma-nm-openvpn plasma-nm-pptp plasma-nm-strongswan plasma-nm-vpnc
>     plasma-systemsettings
>     plasma-workspace plasma-workspace-common plasma-workspace-drkonqi
>     plasma-workspace-geolocation plasma-workspace-geolocation-libs plasma-workspace-libs
>
>
> $ sudo dnf downgrade --allowerasing plasma-breeze plasma-breeze-common plasma-desktop
> plasma-desktop-doc plasma-milou plasma-nm plasma-nm-mobile plasma-nm-openconnect
> plasma-nm-openvpn plasma-nm-pptp plasma-nm-strongswan plasma-nm-vpnc
> plasma-systemsettings plasma-workspace plasma-workspace-common plasma-workspace-drkonqi
> plasma-workspace-geolocation plasma-workspace-geolocation-libs plasma-workspace-libs
> Last metadata expiration check performed 0:23:27 ago on Tue Nov 17 08:06:22 2015.
> Package plasma-desktop-doc of lowest version already installed, cannot downgrade it.
> No match for available package: plasma-nm-mobile-5.3.0-1.fc22.x86_64
> No match for available package: plasma-nm-mobile-5.4.3-1.fc22.x86_64
> No match for available package: plasma-nm-strongswan-5.3.0-1.fc22.x86_64
> No match for available package: plasma-nm-strongswan-5.4.3-1.fc22.x86_64
> Error: package plasma-workspace-5.4.3-1.fc22.x86_64 requires plasmashell >= 5.4, but
> none of the providers can be installed
>
I suppose I should have said YMMV.

Anyway things are working well with the following waiting to be updated...

kde-style-breeze.x86_64                           5.4.3-2.fc22           updates
libkworkspace5.x86_64                             5.4.3-1.fc22           updates
plasma-breeze.x86_64                              5.4.3-2.fc22           updates
plasma-breeze-common.noarch                       5.4.3-2.fc22           updates
plasma-desktop.x86_64                             5.4.3-1.fc22           updates
plasma-desktop-doc.noarch                         5.4.3-1.fc22           updates
plasma-milou.x86_64                               5.4.3-1.fc22           updates
plasma-nm.x86_64                                  5.4.3-1.fc22           updates
plasma-nm-mobile.x86_64                           5.4.3-1.fc22           updates
plasma-nm-openconnect.x86_64                      5.4.3-1.fc22           updates
plasma-nm-openvpn.x86_64                          5.4.3-1.fc22           updates
plasma-nm-pptp.x86_64                             5.4.3-1.fc22           updates
plasma-nm-strongswan.x86_64                       5.4.3-1.fc22           updates
plasma-nm-vpnc.x86_64                             5.4.3-1.fc22           updates
plasma-systemsettings.x86_64                      5.4.3-1.fc22           updates
plasma-workspace.x86_64                           5.4.3-1.fc22           updates
plasma-workspace-common.x86_64                    5.4.3-1.fc22           updates
plasma-workspace-drkonqi.x86_64                   5.4.3-1.fc22           updates
plasma-workspace-geolocation.x86_64               5.4.3-1.fc22           updates
plasma-workspace-geolocation-libs.x86_64          5.4.3-1.fc22           updates
plasma-workspace-libs.x86_64                      5.4.3-1.fc22           updates
sddm-breeze.noarch                                5.4.3-1.fc22           updates

But I may do what was suggested elsewhere in update from updates-testing for the plasma
and kf5 stuff.  Just need to wait until I can be assured of the time to recover if things
go horribly wrong....


-- 
In reality, some people should stick to running Windows and others should stay away from
computers altogether.