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

[Cristian Aravena Romero]

Hello,

$ journalctl -b

[...]

oct 26 07:26:57 romanescu spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

Best regards,
--
Cristian Aravena Romero (caravena)

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: spice-vdagent 0.17.0-1ubuntu2
Uname: Linux 4.19.0-gnu x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 26 14:34:00 2018
InstallationDate: Installed on 2017-10-13 (378 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
SourcePackage: spice-vdagent
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Peter Goodall (pjgoodall)]

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 (...) gnome-session-binary[1191]: Unrecoverable failure in required component org.gnome.Shell.desktop
Nov 09 08:07:52 (...) spice-vdagent[1637]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Nov 09 08:07:52 (...) gnome-session-binary[1391]: WARNING: App 'spice-vdagent.desktop' exited with code 1
Nov 09 08:07:52 (...) gnome-session-binary[1391]: Entering running state
Nov 09 08:09:19 (...) spice-vdagent[2048]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Nov 09 08:09:19 (...) gnome-session-binary[1785]: WARNING: App 'spice-vdagent.desktop' exited with code 1
Nov 09 08:09:19 (...) gnome-session-binary[1785]: Entering running state

[Serdar Sağlam (serdarsaglam)]

spice-vdagent
Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

Ubuntu 18.10 AMD A10 9600P
Hp

[Sebastien Bacher (seb128)]

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

[chuckz (mzakuta)]

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: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
3. systemd: Failed to start Service for snap application canonical-livepatch.canonical-livepatchd.

Running ubuntu 18.10. Machine freezes randomly and disconnects the wired connection.

[Luís Louro (lapisdecor)]

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 0000:00:1f.6 eno1: 10/100 speed: disabling TSO
[ 9.163802] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[ 12.577491] PKCS#7 signature not signed with a trusted key
[ 12.577523] vboxdrv: loading out-of-tree module taints kernel.
[ 12.578400] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[ 12.602825] vboxdrv: Found 6 processor cores
[ 12.624573] vboxdrv: TSC mode is Invariant, tentative frequency 3095999268 Hz
[ 12.624575] vboxdrv: Successfully loaded version 5.2.10_Ubuntu (interface 0x00290001)
[ 12.637952] PKCS#7 signature not signed with a trusted key
[ 12.638961] VBoxNetFlt: Successfully started.
[ 12.651862] PKCS#7 signature not signed with a trusted key
[ 12.652723] VBoxNetAdp: Successfully started.
[ 12.666487] PKCS#7 signature not signed with a trusted key
[ 12.667240] VBoxPciLinuxInit
[ 12.672532] vboxpci: IOMMU not found (not registered)
[ 31.920956] rfkill: input handler disabled

[Peter Goodall (pjgoodall)]

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]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Nov 23 13:55:56 [xxx] gnome-session-binary[2237]: Unrecoverable failure in required component org.gnome.Shell.desktop
Nov 23 13:55:58 [xxx] dbus-daemon[2626]: [session uid=121 pid=2626] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.2' (uid=121 pid=2633 comm="/usr/lib/gnome-session/gnome-session-check-acceler" label="unconfined")
Nov 23 13:55:58 [xxx] at-spi-bus-launcher[2635]: dbus-daemon[2640]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=121 pid=2633 comm="/usr/lib/gnome-session/gnome-session-check-acceler" label="unconfined")
Nov 23 13:56:01 [xxx] spice-vdagent[2794]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Nov 23 13:56:02 [xxx] gnome-session[2632]: gnome-session-binary[2632]: WARNING: App 'spice-vdagent.desktop' exited with code 1
Nov 23 13:56:02 [xxx] gnome-session-binary[2632]: WARNING: App 'spice-vdagent.desktop' exited with code 1
Nov 23 13:56:02 [xxx] gnome-session-binary[2632]: Entering running state
Nov 23 13:56:09 [xxx] dbus-daemon[2929]: [session uid=1000 pid=2929] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.6' (uid=1000 pid=3013 comm="/usr/lib/gnome-session/gnome-session-check-acceler" label="unconfined")
Nov 23 13:56:09 [xxx] at-spi-bus-launcher[3014]: dbus-daemon[3019]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=3013 comm="/usr/lib/gnome-session/gnome-session-check-acceler" label="unconfined")
Nov 23 13:56:12 [xxx] spice-vdagent[3193]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Nov 23 13:56:13 [xxx] gnome-session[2935]: gnome-session-binary[2935]: WARNING: App 'spice-vdagent.desktop' exited with code 1
Nov 23 13:56:13 [xxx] gnome-session-binary[2935]: WARNING: App 'spice-vdagent.desktop' exited with code 1
Nov 23 13:56:13 [xxx] gnome-session-binary[2935]: Entering running state
Nov 23 13:56:15 [xxx] gnome-session[2935]: gnome-session-binary[2935]: WARNING: Application 'org.gnome.SettingsDaemon.XSettings.desktop' killed by signal 11
Nov 23 13:56:15 [xxx] gnome-session-binary[2935]: WARNING: Application 'org.gnome.SettingsDaemon.XSettings.desktop' killed by signal 11
Nov 23 14:34:52 [xxx] gnome-session-c[9688]: Theme parsing error: gtk.css:9707:17: negative values are not allowed.

[MdMax (mdmaxlp)]

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 required component org.gnome.Shell.desktop
déc. 03 21:40:25 Yorkfield gnome-session-binary[1004]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
déc. 03 21:40:26 Yorkfield dbus-daemon[1188]: [session uid=120 pid=1188] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.2' (uid=120 pid=1195 comm="/usr/lib/gnome-session/gnome-session-check-acceler" label="unconfined")
déc. 03 21:40:26 Yorkfield at-spi-bus-launcher[1196]: dbus-daemon[1201]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=120 pid=1195 comm="/usr/lib/gnome-session/gnome-session-check-acceler" label="unconfined")
déc. 03 21:40:31 Yorkfield spice-vdagent[1324]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
déc. 03 21:40:31 Yorkfield gnome-session[1194]: gnome-session-binary[1194]: WARNING: App 'spice-vdagent.desktop' exited with code 1
déc. 03 21:40:31 Yorkfield gnome-session-binary[1194]: WARNING: App 'spice-vdagent.desktop' exited with code 1
déc. 03 21:40:31 Yorkfield gnome-session-binary[1194]: Entering running state
déc. 03 21:40:42 Yorkfield dbus-daemon[1390]: [session uid=1000 pid=1390] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.6' (uid=1000 pid=1492 comm="/usr/lib/gnome-session/gnome-session-check-acceler" label="unconfined")
déc. 03 21:40:42 Yorkfield at-spi-bus-launcher[1493]: dbus-daemon[1498]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=1492 comm="/usr/lib/gnome-session/gnome-session-check-acceler" label="unconfined")
déc. 03 21:40:43 Yorkfield gnome-session[1396]: gnome-session-binary[1396]: WARNING: Could not parse desktop file gnome-power-manager.desktop or it references a not found TryExec binary
déc. 03 21:40:43 Yorkfield gnome-session-binary[1396]: WARNING: Could not parse desktop file gnome-power-manager.desktop or it references a not found TryExec binary
déc. 03 21:40:43 Yorkfield gnome-session[1396]: gnome-session-binary[1396]: WARNING: Could not parse desktop file evolution-alarm-notify.desktop or it references a not found TryExec binary
déc. 03 21:40:43 Yorkfield gnome-session-binary[1396]: WARNING: Could not parse desktop file evolution-alarm-notify.desktop or it references a not found TryExec binary
déc. 03 21:40:43 Yorkfield gnome-session[1396]: gnome-session-binary[1396]: WARNING: Could not parse desktop file bluetooth-applet.desktop or it references a not found TryExec binary
déc. 03 21:40:43 Yorkfield gnome-session-binary[1396]: WARNING: Could not parse desktop file bluetooth-applet.desktop or it references a not found TryExec binary
déc. 03 21:40:43 Yorkfield gnome-session[1396]: gnome-session-binary[1396]: WARNING: Could not parse desktop file gnome-at-session.desktop or it references a not found TryExec binary
déc. 03 21:40:43 Yorkfield gnome-session-b...

[Gerhard Beck (gerhardbeck-de)]

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 timeout expired, or the network connection was broken.
11:26:38 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
11:25:53 gnome-session-b: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Fehler beim Aufruf von StartServiceByName für org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1

[Sebastien Bacher (seb128)]

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?

[Gerhard Beck (gerhardbeck-de)]

In my case the system is slowing down very much and I search for the reason. Don't know whether this is one.

[Histesh Shah (chimak111)]

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
- between host and guest and
- just in the guest and
- just in the host.

I have to shut down the VM to be able to copy/paste again in the host.

Seems very similar to https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9 but without the freezes reported there.

$ apt policy qemu-kvm
qemu-kvm:
  Installed: 1:2.11+dfsg-1ubuntu7.9
  Candidate: 1:2.11+dfsg-1ubuntu7.9

$ apt policy virt-manager
virt-manager:
  Installed: 1:1.5.1-0ubuntu1.1
  Candidate: 1:1.5.1-0ubuntu1.1

/var/log/syslog has
Feb 24 14:03:23 kububb spice-vdagent[1508]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

as the only spice-related entry.

[Tero Gusto (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, which stopped the error occurring in the log.

I don't need the Spice vdagent service, so is there an elegant way to prevent the service from even trying to run?

The easiest solution would be to uninstall spice-vdagent, but that doesn't seem to be possible, since it would also remove ubuntu-desktop, which would be unfortunate, to say the least.

[Sebastien Bacher (seb128)]

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?

[Charles Green (chick)]

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.

[Simon Falardeau (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.

[Antonio (tonecas)]

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
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
abr 03 04:06:25 Work spice-vdagent[1742]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
abr 03 04:06:25 Work dbus-daemon[1500]: [session uid=1000 pid=1500] Activating service name='ca.desrt.dconf' requested by ':1.48' (uid=1000 pid=1728 comm="light
abr 03 04:06:25 Work dbus-daemon[1500]: [session uid=1000 pid=1500] Successfully activated service 'ca.desrt.dconf'
abr 03 04:06:25 Work dbus-daemon[824]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1
abr

cat /var/log/syslog* | grep -i spice-vdagent

Apr 3 04:05:59 Work ureadahead[311]: ureadahead:spice-vdagentd: Ignored relative path
Apr 3 04:05:59 Work ureadahead[311]: ureadahead:spice-vdagentd.target.wants: Ignored relative path
Apr 3 04:06:25 Work spice-vdagent[1742]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Apr 2 21:13:31 Work spice-vdagent[12780]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

inxi -F

System: Host: Work Kernel: 4.15.0-46-generic x86_64 bits: 64 Desktop: Xfce 4.12.3 Distro: Ubuntu 18.04.2 LTS
Machine: Device: desktop Mobo: ASRock model: B450M Pro4 serial: N/A
           UEFI [Legacy]: American Megatrends v: P1.10 date: 06/19/2018
CPU: Quad core AMD Ryzen 5 2400G with Radeon Vega Graphics (-MT-MCP-) cache: 2048 KB
           clock speeds: max: 3600 MHz 1: 1653 MHz 2: 2062 MHz 3: 1646 MHz 4: 1602 MHz 5: 1738 MHz 6: 1589 MHz
           7: 1669 MHz 8: 1609 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series]
           Display Server: x11 (X.Org 1.19.6 ) drivers: ati,amdgpu (unloaded: modesetting,fbdev,vesa,radeon)
           Resolution: 1920x1080@59.93hz
           OpenGL: renderer: AMD RAVEN (DRM 3.23.0, 4.15.0-46-generic, LLVM 7.0.0) version: 4.5 Mesa 18.2.8
Audio: Card-1 Advanced Micro Devices [AMD] Device 15e3 driver: snd_hda_intel
           Card-2 Advanced Micro Devices [AMD/ATI] Device 15de driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.15.0-46-generic
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
           IF: enp31s0 state: up speed: 1000 Mbps duplex: full mac: 70:85:c2:a1:d0:f3

[Otyugh (otyugh-u)]

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, openoffice, stellaris, and chromium, when the system ground to a halt, the mouse became choppy, and after clicking on something (eg terminal) it would take minutes to open. I wanted to try 'top' in a terminal but the computer just hung. I had to reset. The 'important' errors just prior to the crash in the log:

Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

Unrecoverable failure in required component org.gnome.Shell.desktop

I am running ubuntu 18.10 and it's been pretty reliable overall. This is a regular computer, not a virtual machine.

Hope that helps,
Mike

[Eldronin (gowerrobert)]

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 more frequent right before logging me out.

Before my last update, copying text would simply close the application from which I copied text. Now copying just causes a freeze about 1 in 5 times.

Here is my gnu log:
16:17:01 cron: pam_env(cron:session): non-alphanumeric key '"' in /etc/environment', ignoring
16:16:05 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
16:16:00 gdm-session-wor: pam_env(gdm-password:session): non-alphanumeric key '"' in /etc/environment', ignoring
16:15:54 gnome-session-b: CRITICAL: We failed, but the fail whale is dead. Sorry....
16:14:38 sudo: pam_env(sudo:session): non-alphanumeric key '"' in /etc/environment', ignoring
16:04:43 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
16:04:37 gdm-session-wor: pam_env(gdm-password:session): non-alphanumeric key '"' in /etc/environment', ignoring
16:04:21 gnome-session-b: CRITICAL: We failed, but the fail whale is dead. Sorry....
15:55:38 pulseaudio: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
15:55:37 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
15:55:30 gdm-session-wor: pam_env(gdm-password:session): non-alphanumeric key '"' in /etc/environment', ignoring
15:55:14 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
15:55:08 gdm-session-wor: pam_env(gdm-launch-environment:session): non-alphanumeric key '"' in /etc/environment', ignoring
15:55:04 gnome-session-b: Unrecoverable failure in required component org.gnome.Shell.desktop
15:55:04 gdm-session-wor: pam_env(gdm-launch-environment:session): non-alphanumeric key '"' in /etc/environment', ignoring
15:55:02 gnome-session-b: CRITICAL: We failed, but the fail whale is dead. Sorry....
15:17:01 cron: pam_env(cron:session): non-alphanumeric key '"' in /etc/environment', ignoring
10:57:03 sudo: pam_env(sudo:session): non-alphanumeric key '"' in /etc/environment', ignoring
10:31:39 pkexec: pam_env(polkit-1:session): non-alphanumeric key '"' in /etc/environment', ignoring
10:28:45 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 timeout expired, or the network connection was broken.
10:28:27 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
10:28:00 gdm-session-wor: pam_env(gdm-autologin:session): non-alphanumeric key '"' in /etc/environment', ignoring

and in my /var/log/syslog file here are the lines containing "Error" right after being logged out due to a freeze:

GDBus.Error:org.freedesktop.DBus.E...

[William S Gregory (0c-bill)]

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 directly after login, occasional hangups, and also one two reproducible issues...

1.) I run Google Chrome in nearly every session. I like to listen to music using the Youtube website. As time passes and I open, close, and move forward through the playsists on the site Chrome will become less and less responsive. It will occassionally crash the application too. It will usually be fixed by completely closing the application and running it again. Maybe it is a due to an issue which can be triggered through Java or JScript?

2.) My reason for the Java/JScript angle is that I discovered I cannot use Open Office - certain features in it will freeze my entire desktop session completely. This leaves the mouse able to move but nothing else works at all. The same is true for several other select applications - all of which I have removed form the machine. But one thing all the applications have in common is heavy reliance on Java/JScript.

So, perhaps the use of a JVM can help to trigger this issue reliable and thus find the actual source of the bug?

Anybody else able to confirm or refute this idea?

[William S Gregory (0c-bill)]

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 the previous post caused any inconvenience.

[Eric-Pierre Fabre (eric-pierre)]

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 result:
Desktop extended to 4k screen.

Setup:
4.18.0-20-generic #21~18.04.1-Ubuntu SMP Wed May 8 08:43:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

If more information are needed, ask please.
BR
Eric

[Howard (kelvinfuhao)]

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 gnome-session[1032]: gnome-session-binary[1032]: WARNING: App 'spice-vdagent.desktop' exited with code 1
6月 09 23:57:06 ubuntu gnome-session-binary[1032]: WARNING: App 'spice-vdagent.desktop' exited with code 1
6月 09 23:57:06 ubuntu gnome-session-binary[1032]: Entering running state

[Howard (kelvinfuhao)]

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 23:57:06 ubuntu gnome-session[1032]: gnome-session-binary[1032]: WARNING: App 'spice-vdagent.desktop' exited with code 1
Jun 9 23:57:06 ubuntu gnome-session-binary[1032]: WARNING: App 'spice-vdagent.desktop' exited with code 1
Jun 9 23:57:06 ubuntu gnome-shell[1077]: Error looking up permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.impl.portal.PermissionStore was not provided by any .service files
Jun 9 23:57:06 ubuntu gnome-shell[1077]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1477]: reference to undefined property "MetaWindowXwayland"
Jun 9 23:57:06 ubuntu ModemManager[779]: <info> Couldn't check support for device '/sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0': not supported by any plugin
Jun 9 23:57:06 ubuntu dbus-daemon[670]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.62' (uid=121 pid=1311 comm="/usr/lib/gnome-settings-daemon/gsd-color " label="unconfined")
Jun 9 23:57:06 ubuntu gnome-session-binary[1032]: Entering running state
Jun 9 23:57:06 ubuntu xbrlapi.desktop[1391]: openConnection: connect: 没有那个文件或目录
Jun 9 23:57:06 ubuntu xbrlapi.desktop[1391]: cannot connect to braille devices daemon brltty at :0
Jun 9 23:57:06 ubuntu systemd[1]: Starting Manage, Install and Generate Color Profiles...
Jun 9 23:57:06 ubuntu colord[1392]: failed to get edid data: EDID length is too small
Jun 9 23:57:06 ubuntu dbus-daemon[670]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Jun 9 23:57:06 ubuntu systemd[1]: Started Manage, Install and Generate Color Profiles.
Jun 9 23:57:06 ubuntu gsd-color[1311]: failed to get edid: unable to get EDID for output
Jun 9 23:57:06 ubuntu gsd-color[1311]: unable to get EDID for xrandr-Virtual-1: unable to get EDID for output
Jun 9 23:57:16 ubuntu systemd[1]: Created slice User Slice of hfu.

[Howard (kelvinfuhao)]

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...

[Eric-Pierre Fabre (eric-pierre)]

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 color of my background) on both screen...
To have any things displayed I need to use CTRL + ALT + F1.

Using "Screen Mode" key (i.e. F8) we were able to have display properly set.
Hope this helps...
BR
Eric.

[yas (sayazyi)]

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 then to disable it with:
$ sudo systemctl disable spice-vdagent

But that was not enough. I found that it was being launched on startup (and that created the error and warning in the logs) so I located the spice-vdagent.desktop in different locations. Finally I found a solution confirming the way to disable it here:
https://access.redhat.com/solutions/2990871

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 spice-vdagentd
$ sudo systemctl disable spice-vdagentd

If I understand my case right this service should not be part of initialization if the installation is not a virtual machine supporting spice.
Hope this helps others with similar case, regards.

[Tero Gusto (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 ...

[[e-mail] (markackerman8)]

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 spice-vdagentd
$ sudo systemctl disable spice-vdagentd

Cheers, Mark

[Sze Attila (atishow)]

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 laugh on me.

1.) I find the /etc/xdg/autostart/spice-vdagent.desktop file
2.) I can't find /usr/share/gdm/autostart/LoginWindow/spice-vdagent.desktop file! There is just a "Spice vdagent" named file, not the "spice-vdagent.desktop" file.. weird. (screen save attached)

How must to do it... step by step?
3.) When I open the /etc/xdg/autostart/spice-vdagent.desktop file with "sudo gedit" the "spice-vdagent.desktop" file contains these lines:
[Desktop Entry]
Name=Spice vdagent
Comment=Agent for Spice guests
Exec=/usr/bin/spice-vdagent
Terminal=false
Type=Application
Categories=
X-GNOME-Autostart-Phase=Initialization
NoDisplay=true

5.) Where must put it the "X-GNOME-Autostart-enabled=false" line in this file? At below is this correct..?
[Desktop Entry]
Name=Spice vdagent
Comment=Agent for Spice guests
Exec=/usr/bin/spice-vdagent
Terminal=false
Type=Application
Categories=
X-GNOME-Autostart-Phase=Initialization
X-GNOME-Autostart-enabled=false
NoDisplay=true

6.) When I changed and saved. Just copy this file into the "/usr/share/gdm/autostart/LoginWindow/" folder...? Because that folder not contains the "spice-vdagent.desktop file" there is just the "Spice vdagent" file... or maybe I must open this "Spice vdagent" with "sudo gedit" and write into that "X-GNOME-Autostart-enabled=false" line?

Thanx and waiting for your answers!
"May the Tux be with you, always."
:)

[Sze Attila (atishow)]

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=
X-GNOME-Autostart-Phase=Initialization
NoDisplay=false
X-GNOME-Autostart-enabled=false
3.) Saved
4.) After I did it same with the /usr/share/gdm/autostart/LoginWindow/spice-vdagent.desktop file.
(Interesting: when I browsing this folder with "Nautilus", just a "Spice vdagent" named file was there... but when I opened this folder with "sudo gedit" there a "spice-vdagent.desktop", so I opened.)
5.) Saved
6.) Finally: $ sudo systemctl stop spice-vdagentd and $ sudo systemctl disable spice-vdagentd
7.) Reboot... and the "Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0" error message is gone!
P.S: How the heck can modified my comments? I can't find..
:)