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? towards the end of zypper dup it executed some pl script or so and used cpu time visible via top for several tens of seconds, whose name was something about btrfs online defrag or such, but odd enough my system has zero btrfs partitions or disks, only ext3 or ext4 here or something. wondering what that btrfs related perl script is actually doing all those tens of seconds. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org