[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[virt-tools-list] virt-manager crashes at startup with awesome WM



I am using virt-manager 0.9.1 with ubuntu 12.04 in awesome WM.

Virt-manager crashes about once in a day. After the crash it does not
start again without machine reboot. The following error can be seen when
I am trying start virt-manager with --debug

virt-manager --debug
2012-09-26 16:10:08,652 (cli:71): virt-manager startup
2012-09-26 16:10:08,652 (virt-manager:300): Launched as:
/usr/share/virt-manager/virt-manager.py --debug
2012-09-26 16:10:08,652 (virt-manager:301): GTK version: (2, 24, 10)
2012-09-26 16:10:08,652 (virt-manager:302): virtManager import: <module
'virtManager' from '/usr/share/virt-manager/vir
2012-09-26 16:10:08,721 (engine:555): No inspection thread because
libguestfs is too old, not available, or libvirt is 
2012-09-26 16:10:08,723 (systray:138): Showing systray: False
2012-09-26 16:10:08,724 (engine:346): About to connect to uris
['qemu:///system']
2012-09-26 16:10:08,766 (manager:171): Showing manager
2012-09-26 16:10:08,799 (engine:471): window counter incremented to 1
2012-09-26 16:10:08,800 (manager:171): Showing manager
2012-09-26 16:10:08,800 (connection:991): Scheduling background open
thread for qemu:///system
2012-09-26 16:10:08,800 (connection:1177): Background 'open connection'
thread is running
2012-09-26 16:10:08,804 (connection:1227): Background open thread
complete, scheduling notify
The program 'virt-manager' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
  (Details: serial 343 error_code 165 request_code 155 minor_code 8)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error()
   function.)


Quick google search indicates that others are also suffering from the
same problem: https://bugzilla.redhat.com/show_bug.cgi?id=843590#c1

-Petteri


-- 
 ___.  /     \  .___
 "Y/|\ | 0 o / /|\Y"
   '^^V  /|\ 'v'^^'


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]