+++ This bug was initially created as a clone of Bug #1006205 +++ Cloning bug 999804 for RHEL-7 since RHEL-7 is affected too. +++ This bug was initially created as a clone of Bug #999804 +++ Description of problem: This appears to be some kind of regression. In Fedora 24 I see: Aug 15 22:03:00 formenos.lan spice-vdagent[1909]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Aug 15 22:03:00 formenos.lan gnome-session[1323]: gnome-session-binary[1323]: WARNING: App 'spice-vdagent.desktop' exited with code 1 Aug 15 22:03:00 formenos.lan gnome-session-binary[1323]: WARNING: App 'spice-vdagent.desktop' exited with code 1 How reproducible: Always Steps to Reproduce: 1. Install spice-vdagent 2. logout system 3. login system Actual results: Aug 15 22:03:00 formenos.lan spice-vdagent[1909]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Aug 15 22:03:00 formenos.lan gnome-session[1323]: gnome-session-binary[1323]: WARNING: App 'spice-vdagent.desktop' exited with code 1 Aug 15 22:03:00 formenos.lan gnome-session-binary[1323]: WARNING: App 'spice-vdagent.desktop' exited with code 1 in journald logs Expected results: No such error messages should be output. Additional info [m8ram@formenos ~]$ rpm -q spice-vdagent spice-vdagent-0.16.0-3.fc24.x86_64 --- Additional comment from Hans de Goede on 2013-08-27 11:21:37 EDT --- This is fixed upstream: http://cgit.freedesktop.org/spice/linux/vd_agent/commit/?id=99a2628b0ff04e0aadd130e45aa2598c4df64690 Moving to POST --- Additional comment from Hans de Goede on 2013-09-10 05:02:13 EDT --- This is fixed in spice-vdagent-0.14.0-5.el7 moving to MODIFIED. --- Additional comment from Hans de Goede on 2014-03-11 03:37:02 EDT --- This has long been fixed, closing this with a resolution of CURRENTRELEASE.
I see that this bug's severity is set as "medium". However, because of this bug user cannot login to the system. Thus, according to the severity descriptions, I think this bug should be set as an "urgent" bug, unless there is a workaround for it. If so, I would like to learn it. Or please kindly explain the reason of "medium" severity. Thank you.
It doesn't say that the device is missing, try disabling selinux (In reply to dx486107 from comment #1) > I see that this bug's severity is set as "medium". However, because of this > bug user cannot login to the system. Why is not possible to login ? > Thus, according to the severity > descriptions, I think this bug should be set as an "urgent" bug, unless > there is a workaround for it. If so, I would like to learn it. Or please > kindly explain the reason of "medium" severity. Thank you.
(In reply to Pavel Grunt from comment #2) > It doesn't say that the device is missing, try disabling selinux just to check if it changes anything ;) > > (In reply to dx486107 from comment #1) > > I see that this bug's severity is set as "medium". However, because of this > > bug user cannot login to the system. > > Why is not possible to login ? > > > Thus, according to the severity > > descriptions, I think this bug should be set as an "urgent" bug, unless > > there is a workaround for it. If so, I would like to learn it. Or please > > kindly explain the reason of "medium" severity. Thank you.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
No response for a while, so closing