went from a 42.2 beta1 to beta2 via zypper dup from inside desktop kde session.

eventually i walked away from the machine came back uncertain if the
screensaver had kicked in or not, but mousecursor was the only thing visible on
screen at that point in time.

went over to alt+f2 and +f3 console screens and watched top and ps and lsof
zypper and tail zypper history and such stuff to be able to tell if there was
still anything going on or if zypper had finished and what not.

during this time i have observed weird scenario, first i had thought at some
language (lang or similar) named packages zypper was working on every now and
then but later also with certain lib.... and kde..... packages the progress
(tail and so on) was going nowhere when i left it there on alt+f2 or +f3
screen.

and always at those times, going back to the mouse cursor alt+f7 kde-leftover
screen then the disk activity led became acive again and the zypper history
file (tail) and zypperlog again gotton "bumped" and activity returned to there
and rpm and zypper and all went on.

of course I aware of facts that memory swapping when going from console to
graphical desktop and so on, but i kid you not, if i hadnt created (moved
around the mouse or merely going to alt+f7 screen) activity the zypper progress
would somehow much longer be stalled or hanging at certain packages or not
going anywhere.

first i had thought about coincidently seeing disk activity because of memory
stuff and swapping when i was visiting the kde screen but after a while it
became apparent that it needed those interactive mouse or whatnot events or
merely reactivating the alt+f7 graphic stack or its related leftover programs
or pids or whatever then again advanced the zypper dup progress forward.

weird. what is the actual official way to do zypper dup? only from inside a ssh
and inside a screen terminal there? i remember that there used to be a problem
with some old suse to next suse when the screen command had been upgraded as
well and thus killed or became blocked or hung or something and there used to
be some problems with even this way of running zypper dup inside screen.

thanks.