Description of problem: Following instructions at https://fedoraproject.org/wiki/QA:Testcase_Virtualization_URL_Guest_Install results in an error followed by a hang of virt-viewer: ** (virt-viewer:7368): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-6NGy4Jqd2X: Connection refused Version-Release number of selected component (if applicable): # rpm -qa | egrep 'virt|qemu' | sort ipxe-roms-qemu-20140303-3.gitff1e7fc7.fc22.noarch libgovirt-0.3.3-1.fc22.x86_64 libvirt-client-1.2.13-2.fc22.x86_64 libvirt-daemon-1.2.13-2.fc22.x86_64 libvirt-daemon-config-network-1.2.13-2.fc22.x86_64 libvirt-daemon-driver-interface-1.2.13-2.fc22.x86_64 libvirt-daemon-driver-network-1.2.13-2.fc22.x86_64 libvirt-daemon-driver-nodedev-1.2.13-2.fc22.x86_64 libvirt-daemon-driver-nwfilter-1.2.13-2.fc22.x86_64 libvirt-daemon-driver-qemu-1.2.13-2.fc22.x86_64 libvirt-daemon-driver-secret-1.2.13-2.fc22.x86_64 libvirt-daemon-driver-storage-1.2.13-2.fc22.x86_64 libvirt-daemon-kvm-1.2.13-2.fc22.x86_64 libvirt-glib-0.2.0-1.fc22.x86_64 libvirt-python-1.2.13-1.fc22.x86_64 qemu-common-2.3.0-0.4.rc3.fc22.x86_64 qemu-img-2.3.0-0.4.rc3.fc22.x86_64 qemu-kvm-2.3.0-0.4.rc3.fc22.x86_64 qemu-system-x86-2.3.0-0.4.rc3.fc22.x86_64 virt-install-1.1.0-7.git6dbe19bd8.fc22.noarch virt-manager-1.1.0-7.git6dbe19bd8.fc22.noarch virt-manager-common-1.1.0-7.git6dbe19bd8.fc22.noarch virt-viewer-2.0-1.fc22.x86_64 How reproducible: Steps to Reproduce: 1. Install F22 on some-host 2. From another system: ssh -XC root@some-host 3. In ssh session, ensure packages are current: yum update 4. In ssh session, start an install: virt-install --name test-day-vm-x86_64 --ram 2048 --disk size=10 --location https://dl.fedoraproject.org/pub/alt/stage/22_Beta_RC2/Workstation/x86_64/os/ Actual results: === Starting install... Retrieving file vmlinuz... | 11 MB 00:00:01 !!! Retrieving file initrd.img... | 85 MB 00:00:04 !!! Allocating 'test-day-vm-x86_64.qcow2' | 10 GB 00:00:01 Creating domain... | 0 B 00:00:00 ** (virt-viewer:7368): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-6NGy4Jqd2X: Connection refused === Expected results: Successful connection with virt-viewer. Additional info: * Confirmed that xclock displays correctly, so it's not a $DISPLAY issue. * the vm is in fact running * so is virt-viewer # ps -eaf | egrep qemu qemu 7312 1 17 12:31 ? 00:01:16 /usr/bin/qemu-system-x86_64 -machine accel=kvm -name test-day-vm-x86_64 -S -machine pc-i440fx-2.3,accel=kvm,usb=off -cpu Opteron_G3 -m 2048 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid d992066f-5908-4bd2-ad46-ed0e505a6100 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/test-day-vm-x86_64.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-reboot -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -kernel /var/lib/libvirt/boot/virtinst-vmlinuz.hY0Irk -initrd /var/lib/libvirt/boot/virtinst-initrd.img.1Yi12b -append inst.repo=https://dl.fedoraproject.org/pub/alt/stage/22_Beta_RC2/Workstation/x86_64/os/ -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/var/lib/libvirt/images/test-day-vm-x86_64.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=24 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:e0:08:9a,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/test-day-vm-x86_64.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel1,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on root 7368 7275 0 12:31 pts/0 00:00:00 virt-viewer --connect qemu:///system --wait test-day-vm-x86_64 root 7452 7404 0 12:38 pts/2 00:00:00 grep -E --color=auto qemu
Additional information: gnome-terminal also fails the same way; it runs, but the window never appears.
Tried to reproduce on said machine. Just running plain virt-viewer does eventually launch, but it takes about 90 seconds. Given that the latency for me is so bad that key strokes are visibly delayed this isn't unexpected. Likely trying to run virt-viewer to actually connect to a VM and stream graphical updates will take much longer to load. So for me at least this appears to be working
What flags did you pass when you ssh'd into the system? I tried again and have been waiting for five hours and I sill haven't seen a window appear.
Just ssh -X. Once there I tried plain 'virt-viewer' without any domain specified.
This is related to ssh -X/Y from a f21 to f22: all gtk3 app is NOT working. f22 to f22 is ok:-). So xfce, emacs and gnome app is not working on f22 to a remote f21 X-server via ssh. Shall I make a new BUG? #1190291 is maybe related to it --- is this an f21 issue! but f21 to f21 is working for me.
(In reply to Lars S. Jensen from comment #6) > This is related to ssh -X/Y from a f21 to f22: all gtk3 app is NOT working. > f22 to f22 is ok:-). > So xfce, emacs and gnome app is not working on f22 to a remote f21 X-server > via ssh. > > Shall I make a new BUG? > > #1190291 is maybe related to it --- is this an f21 issue! > but f21 to f21 is working for me. Sounds bug worthy, but I'm not really sure where: probably gtk, but in my experience filing gtk bugs against Fedora doesn't get much attention...