User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
Firefox/60.0
Build Identifier: 

I think there are two problems here -- one with "zypper" and one with Gnome. 
But I'll list it with "zypper" since that was the command I was running.

Here's the error that I saw:

(496/590) Installing: gtk-vnc-lang-0.7.2-lp151.2.50.noarch
..............[error]
Installation of gtk-vnc-lang-0.7.2-lp151.2.50.noarch failed:
Error: Subprocess failed. Error: RPM failed: error: open of
/var/cache/zypp/packages/repo-oss/noarch/gtk-vnc-lang-0.7.2-lp151.2.50.noarch.rpm
failed: No such file or directory
error: gtk-vnc-lang-0.7.2-lp151.2.50.noarch: install failed
error: gtk-vnc-lang-0.7.2-lp151.2.48.noarch: erase skipped

Abort, retry, ignore? [a/r/i] (a): r

Background:  I was running "zypper dup" under a "screen" session within the
Gnome desktop.  This was with Leap 15.1 Beta.  The same problem has occcured
with Tumbleweed.

The package cache is on a home NFS server.  That's to allow sharing of
downloaded packages across systems.  And it mostly works.

I have seen it fail 4 times recently.  On each occasion, it failed while
running Gnome.  I have never had a similar failure with KDE or with Icewm.  So
I think there's a Gnome issue there.  When this first happened, I used "a"
(abort).  And that resulted in a message about skipping scripts.  This seemed
like a bad idea, so I have instead used "r" retry when this has happened again.
 And that seems to work.

The "zypper" bug:  Hitting "r" for retry does seem to work.  But the "zypper"
output never shows that the package was installed.  When I check that later, it
does show up as installed.

The "Gnome" bug: This only happens in Gnome.  It happens when I am doing
something away from the computer while the update is running.  When I return to
the computer, the screen is blank.  I move the mouse, and the lock screen
background shows up.  I hit enter, and I see the error message with the update
stopped (waiting) at that point.  I have screenlock turned off in Gnome, and I
have a 5 minute timeout for blanking the screen (in Gnome power settings).

It looks as if Gnome is doing something to break NFS after that 5 minute
timeout for blanking the screen.  And, to me, that seem wrong.  It should be
allowable to continue a running process even when the screen is blanked.

I will attach (1) a full transcript of the "screen" session running "zypper",
and (2) a small selection of possibly relevant lines from "/var/log/messages".

The obvious workaround is to not use Gnome when running "zypper dup".


Reproducible: Always