-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2016-09-09 a las 13:41 +0200, cagsm escribió:
briefly: I had noticed during upgrade from 42.1 to 42.2 beta1 via zypper dup via kterm in kde from live running 42.1 kde system: inside the kde after zypper dup went through, the kde start menu would not react any more those reboot commands, i clicked reboot or restart or whatsitcalled several times, waited but nothing happened. eventually i went to a real console session alt+Fn or something and issued reboot there. It rebooted. is the kde session supposed to go defunct on certain parts of it as thousand of packages and libraries have been replaced after a zypper dup and thus kde rendered dysfunctional or certain scripts or targets missing from the then replaced 42.1 state as soon as it became a not yet rebooted 42.2?
This is expected. My recommendation is to run "zypper dup" from a text console, not inside X. More so as the "length of the jump" increases. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlfS1RsACgkQja8UbcUWM1x+UgD/S3hJbLs457v95iTyxuw81sNH XVV6BFD7CIsFT6YVIkIA/1bCydQEeyeVKDZJWoSffJ5RRetYZKoGV1c5rSnd31SS =kjJo -----END PGP SIGNATURE-----