Red Hat Bugzilla – Bug 1269506
spice-vdagentd crashes in a VM when GDM autologin is enabled
Last modified: 2015-11-02 12:15:46 EST
Description of problem:
This seems to happen in a VM when I enable automatic login in GNOME. On boot, instead of gdm I see only a black screen. I can switch to other TTYs and log in using text mode. There is spice-vdagentd traceback in journal, I suspect that's what kills gdm. When I try to reboot, I have to wait 90 seconds before systemd kills some processes.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (5 frames)
#3 __open_memstream at memstream.c:85
#4 __vsyslog_chk at ../misc/syslog.c:167
#5 __syslog_chk at ../misc/syslog.c:129
#6 update_active_session_connection at src/vdagentd.c:645
#7 main_loop at src/vdagentd.c:881
Created attachment 1080660 [details]
Created attachment 1080661 [details]
Created attachment 1080662 [details]
Created attachment 1080663 [details]
Created attachment 1080664 [details]
Created attachment 1080665 [details]
Created attachment 1080666 [details]
Created attachment 1080667 [details]
Created attachment 1080668 [details]
Created attachment 1080669 [details]
Created attachment 1080670 [details]
Created attachment 1080671 [details]
Created attachment 1080672 [details]
Created attachment 1080683 [details]
full system journal
This is full journal from an attempt to boot in a VM with GDM autologin enabled. 14:10:21 timestamp is roughly the time when I see only black screen instead of gdm and then I switch to tty2 and try to reboot, which takes 90 seconds.
This problem is fixed by this update:
Proposing as a FinalFreezeException, this will allow autologin in VMs without updating your system first. If this is not stable, people will have troubles disabling autologin to get working graphics again (you need to edit /etc/gdm/custom.conf).
The bodhi update has been pushed to stable, closing.