Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error connecting to graphical console: could not get a reference to type class #39

Closed
irobayna opened this issue Feb 16, 2016 · 3 comments

Comments

@irobayna
Copy link

I got two computers with this awesome package installed, on one I did a brew update & brew upgrade and when I connect to the VMs and try to view the console, I get this error. On the other computer which has not been updated, the console works as expected.

@ne4u
Copy link

ne4u commented Apr 8, 2016

this fixed it for me:
brew uninstall --force gtk+3 libvirt-glib gtk-vnc spice-gtk libvirt pygobject3 virt-manager virt-viewer && brew install virt-manager virt-viewer

@jeffreywildman
Copy link
Owner

Thanks for the note @ne4u. I'll add a note in the FAQ on the mainpage.

@Swivelgames
Copy link
Contributor

Swivelgames commented Sep 6, 2018

As silly and off-topic as this may seem, I was chasing my tail for a good week until I figured out why this wasn't working for me. After uninstalling/installing virt-manager and virt-viewer again (so that I could use remote-viewer), I found that the reason I was getting my Socket I/O Timeout error was not related to virt-manager or virt-viewer at all.

I'm able to connect just fine on a different machine, but not on this one (oddly). In my particular instance, I use this crucial tool because it enables me to have near-zero latency (SPICE; as opposed to slower VNC) so that I can daily-use a Desktop VM hosted on my Proxmox hypervisor remotely.


My specific problem (yours may be totally different) turned out to be an issue with one of my package versions. Because I installed/updated to the latest and greatest version of virt-manager and virt-viewer, I then needed to update my packages on the server that was hosting my SPICE service.

In particular, specifically on Proxmox, this turned out to be the libpve-http-server-perl package, which simply needed to be updated to latest (in this case 2.0-10). Voilà! Connection worked perfectly.

Hope this helps someone; even if you're not using Promox: make sure that the packages on the other end are up to date!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants