Hide Forgot
Description of problem: When installing a new VM using virt-install (thus invoking the virt-viewer) or simply using the virt-viewer, the following messages are thrown: (virt-viewer:23574): GSpice-WARNING **: Error calling 'org.gnome.SessionManager.Inhibit': GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files (virt-viewer:10960): GSpice-WARNING **: Error calling 'org.gnome.SessionManager.Inhibit': GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files (virt-viewer:10019): GSpice-WARNING **: Error calling 'org.gnome.SessionManager.Inhibit': GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files (virt-viewer:10019): GSpice-CRITICAL **: spice_session_set_shared_dir: assertion 'dir != NULL' failed (virt-viewer:10019): GSpice-CRITICAL **: spice_session_set_shared_dir: assertion 'dir != NULL' failed Version-Release number of selected component (if applicable): spice-gtk-0.26-5.el7.x86_64 spice-gtk-0.26-5.el7.i686 How reproducible: Run virt-install or virt-viewer Steps to Reproduce: 1. virt-viewer <domain> 2. or virt-install <....> with invoing virt-viewer 3. Actual results: Warning and error messages throw Expected results: No warning and error messages Additional info: The same behavior as described in 1175721 where it was fixed by releasing fixed upstream package.
Fixed in spice-gtk upstream: http://cgit.freedesktop.org/spice/spice-gtk/commit/?id=a75faf17146cb54137270e71d91c96599fba083c and http://cgit.freedesktop.org/spice/spice-gtk/commit/?id=6e86378ec9de4ca1610e1a47a099e8f772cdb3b5 and https://cgit.freedesktop.org/spice/spice-gtk/commit/?id=6163828e8cb15d539c80cc3f0bfb5008be9b2247
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2229.html