http://bugzilla.suse.com/show_bug.cgi?id=1099494 http://bugzilla.suse.com/show_bug.cgi?id=1099494#c11 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(aschnell@suse.com | |) --- Comment #11 from Michael Andres <ma@suse.com> --- Messages '[PLUGIN] PluginScript.cc(~PluginDumpStderr):' simply log the lines a plugin writes to it's stderr. So the message
! ERROR:root: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
was written by snapper.py not by libzypp. zypp timeout: According to the log:
snapper.py ->send PluginFrame[COMMITEND](0){370884} THROW: Not ready to read within timeout.
It's true that snapper.py does not acknowledge the receipt of the COMMITEND message (within 30 sec.). Due to this zypp stops serving the plugin.
snapper.py ->send PluginFrame[_DISCONNECT](0){0} snapper.py <-PluginFrame[ACK](0){0} snapper.py -> [0]
Zypp sends a _DISCONNECT to inform the plugin and the plugin acknowledges the receipt. If _DISCONNECT is acknowledged, zypp does not kill the script, but leaves it running in the background [1]. AFAICS the plugin is not killed by libzypp. OTOH it is not able to delay the transaction until it has completed (but that's actually intended). So what to change? [1] https://doc.opensuse.org/projects/libzypp/HEAD/zypp-plugins.html -- You are receiving this mail because: You are on the CC list for the bug.