[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2020-03-16 Thread Betros Abraha
** Changed in: spice-vdagent (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800196 Title: spice-vdagent[1345]: Cannot access vdagent virtio channel

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2020-02-14 Thread Sze Attila
I I did it! 1.) I opened the /etc/xdg/autostart/spice-vdagent.desktop file with "sudo gedit". 2.) I modified the file to: [Desktop Entry] Name=Spice vdagent Comment=Agent for Spice guests Exec=/usr/bin/spice-vdagent Terminal=false Type=Application Categories=

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2020-02-14 Thread Sze Attila
Hi Yas and everyone on this page! I'm totally 'rookie' in the world of Ubuntu LinuX.. I just some weeks ago arrived from "Bill's World" :D and firstly must to say a big sorry about my English. I have some important question about your "bug solution". Repeat: I'm really 'rookie' so please don't

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-10-17 Thread markackerm...@gmail.com
Thanks Yas Your suggestion reiterated here worked for me! Basically adding the line: X-GNOME-Autostart-enabled=false To the files: /etc/xdg/autostart/spice-vdagent.desktop /usr/share/gdm/autostart/LoginWindow/spice-vdagent.desktop Then stop and disable the service: $ sudo systemctl stop

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-09-15 Thread Tero Gusto
Thanks for sharing yas! That approach seems to take care of the problem, it doesn't show up in my log any longer. Now all I need is to get rid of the "Unrecoverable failure in required component org.gnome.Shell.desktop", for a totally clean log after a fresh boot in Ubuntu 18.04 ... -- You

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-09-15 Thread yas
Hi all, I've found this messages in systemd journal but in my case it was a bare metal install of Ubuntu 18.04, so I don't see the need to have spice-vdagent installed (that I understand is for virtual machine guest). Remove it is not an option because it will remove ubuntu-desktop. I tried

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-06-10 Thread Eric-Pierre Fabre
Hi all, We have found a workaround, for the display not usable. I give it here for people like me who were stuck... with dell. Since I cannot comment my post #24, here a summary: Step to reproduce: Plug HDMI cable 4k ready, of course connected to 4k screen. Actual result: Purpul screen (default

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-06-10 Thread Howard
I have a suggestion that if the ubuntu can backup itself when upgrade ,when if it crashed , I can restore it, now I have to rollback it to a very old version... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-06-10 Thread Howard
Hi all, I have the same problems... I just upgraded my system... It freaks me out... journalctl -b | grep -E 'spice-vdagent|gnome-session' 6月 09 23:57:05 ubuntu spice-vdagent[1306]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 6月 09 23:57:06 ubuntu

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-06-10 Thread Howard
Jun 9 23:57:05 ubuntu spice-vdagent[1306]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Jun 9 23:57:05 ubuntu dbus-daemon[670]: [system] Successfully activated service 'org.freedesktop.PackageKit' Jun 9 23:57:05 ubuntu systemd[1]: Started PackageKit Daemon. Jun 9

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-06-09 Thread Eric-Pierre Fabre
Hi all, I have the same issue with a dell laptop Inspiron 15. Step to reproduce: Plug HDMI cable 4k ready, of course connected to 4k screen. Actual result: Purpul screen (default color of my background) on both screen... To have any things displayed I need to use CTRL + ALT + F1. Expected

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-06-07 Thread William S Gregory
Wish I had the ability to edit a post... Scratch most of my last post. There is a problem with vdagent~, but I just refuted my previous post. I do have the error, but I am 99.9% certain that it does not cause the problems that I am experiencing which brought me to this bug report. Apologies if

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-06-07 Thread William S Gregory
I am wondering if a JVM can be used to more reliably trigger the bug and thus help isolate it? Hopefully someone else reading this has an opinion... Below is my experience and the reason why I am considering this idea: I have had what I first believed were random black screens, restarts

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-05-09 Thread Eldronin
I have the same issue. I'm using Ubuntu 18.04.2 LTS on a Dell desktop Mostly when copying text, but sometimes when also opening a pdf and other applications, the system freezes for approx 30 seconds. After freezing for 3 or so times, it also logs me out. It also appears that the freezes become

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-05-09 Thread Eldronin
I have the same issue. I'm using Ubuntu 18.04.2 LTS on a Dell desktop Mostly when copying text, but sometimes when also opening a pdf and other applications, the system freezes for approx 30 seconds. After freezing for 3 or so times, it also logs me out. It also appears that the freezes become

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-04-27 Thread Otyugh
I'm not a programmer/developer, but just a user. I can answer this question, however: "Could people having the issue describe exactly what they are doing to trigger it and what's the visible impact? Is that only a warning in the journal log?" In my case I was just doing my normal stuff,

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-04-02 Thread Antonio
Same problem here, on boot: sudo journalctl -xe abr 03 04:06:25 Work dbus-daemon[1500]: [session uid=1000 pid=1500] Successfully activated service 'org.freedesktop.Notifications' abr 03 04:06:25 Work systemd[1465]: Started XFCE notifications service. -- Subject: Unit UNIT has finished start-up

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-04-02 Thread Simon Falardeau
I have the problem every time I login, within ~30 seconds, without doing anything. I get an error popup asking to ignore or report the problem. When I click on "report problem", the popup disappears and not sure if anything occurs. -- You received this bug notification because you are a member

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-03-16 Thread Charles Green
I cant speak to other peoples issues - I trigger the message in the system journal, by booting my system. I understand gdm3 starts the spice-vdagent program? I have not noted any ill effects, and I've been simply ignoring it. -- You received this bug notification because you are a member of

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-03-14 Thread Sebastien Bacher
Could people having the issue describe exactly what they are doing to trigger it and what's the visible impact? Is that only a warning in the journal log? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-03-12 Thread Tero Gusto
I am also getting this error in my Ubuntu 18.04 logs during boot. I tried disabling it under Startup Applications: Spice vdagent /usr/bin/spice-vdagent Agent for Spice guests ... yet I still get the error. I tested the service path by temporarily renaming /usr/bin/spice-vdagent and rebooting,

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-02-24 Thread Histesh Shah
Summary: a feature is not working: copy/paste works initially as expected but then fails. Kubuntu 18.04 host and various other Ubuntu 18.04 and 18.10 flavors as guest. I don't see any slowdown but copy/paste initially works between host and guest (either way) and then stops working altogether -

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2018-12-07 Thread Gerhard Beck
In my case the system is slowing down very much and I search for the reason. Don't know whether this is one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800196 Title: spice-vdagent[1345]: Cannot

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2018-12-07 Thread Sebastien Bacher
It's still unclear to me what's the problem is here? Is that only the warning in the log or is there a feature not working? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800196 Title:

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2018-12-07 Thread Gerhard Beck
Same problem on 18.04 LTS: 11:26:56 pulseaudio: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: 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

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2018-12-03 Thread MdMax
Hello, Same problem here: $ journalctl -b | grep -E 'spice-vdagent|gnome-session' déc. 03 21:40:25 Yorkfield gnome-session[1004]: gnome-session-binary[1004]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 déc. 03 21:40:25 Yorkfield gnome-session-binary[1004]: Unrecoverable failure in

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2018-11-22 Thread Peter Goodall
I've extended my search in journalctl. Hope this helps: % journalctl -b | grep -E 'spice-vdagent|gnome-session' Nov 23 13:55:56 [xxx] gnome-session[2237]: gnome-session-binary[2237]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Nov 23 13:55:56 [xxx] gnome-session-binary[2237]:

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2018-11-22 Thread Luís Louro
Same error on Ubuntu 18.04 4.15.0-39-generic I can't use virtualization because the system reboots when using it. Also I have short time random black screen and random reboots. final part of dmesg: [9.163753] e1000e :00:1f.6 eno1: 10/100 speed: disabling TSO [9.163802] IPv6:

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2018-11-21 Thread chuckz
I am getting these logs on boot: 1. Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 2. from gnome-session-be: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver:

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2018-11-20 Thread Sebastien Bacher
Thank you for your bug report, do you have other problems or only that warning? https://bugzilla.redhat.com/show_bug.cgi?id=1497637 describes a similar warning ** Changed in: spice-vdagent (Ubuntu) Importance: Undecided => Low ** Bug watch added: Red Hat Bugzilla #1497637

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2018-11-19 Thread Serdar Sağlam
spice-vdagent Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Ubuntu 18.10 AMD A10 9600P Hp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800196 Title:

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2018-11-08 Thread Peter Goodall
Is there a related error happening with gnome-session-binary? >journalctl -b SYSLOG_IDENTIFIER=spice-vdagent SYSLOG_IDENTIFIER=gnome- session-binary Nov 09 08:07:47 (...) gnome-session-binary[1191]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Nov 09 08:07:47 (...)

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2018-11-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: spice-vdagent (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800196