Re: [Qemu-discuss] Empty window since qemu 1.6.x

[emre]

Hermann J Beckers wrote:
> Am 24.01.2014 13:15, schrieb emre:
> > Hermann J Beckers wrote:
> > > Since version 1.6.x I get an empty QEMU window, whenever I start a VM
> > > (also tested with 1.7.0) and qemu-system-x86-64 uses up to 90 % cpu
> > > time. OS is openSUSE 12.3 and 13.1 (no difference).
> ...
>
> > >
> > You might try upgrading "cairo"
> > This was the case for slackware 14.1.
> Thank you for the answer. But openSUSEs yast thinks everything cairo* 
> is uptodate:
>
> "python3-cairo-1.10.0-13.1.2.x86_64
> python3-cairo-devel-1.10.0-13.1.2.x86_64
> libcairo-gobject2-1.12.16-3.1.3.x86_64
> python-gobject-cairo-3.10.2-4.1.x86_64
> python-cairo-1.10.0-12.1.2.x86_64
> libcairo2-1.12.16-3.1.3.x86_64
> cairomm-devel-32bit-1.10.0-12.2.2.x86_64
> perl-Cairo-1.090-5.1.1.x86_64
> python-cairo-devel-1.10.0-12.1.2.x86_64
> libcairomm-1_0-1-1.10.0-12.2.2.x86_64
> libcairo2-32bit-1.12.16-3.1.3.x86_64
> libcairo-gobject2-32bit-1.12.16-3.1.3.x86_64
> cairo-devel-32bit-1.12.16-3.1.3.x86_64
> libcairo-script-interpreter2-32bit-1.12.16-3.1.3.x86_64
> cairo-devel-1.12.16-3.1.3.x86_64
> python3-gobject-cairo-3.10.2-4.1.x86_64
> conky-cairo-1.9.0-22.12.x86_64
> libcairo-script-interpreter2-1.12.16-3.1.3.x86_64
> cairomm-devel-1.10.0-12.2.2.x86_64
> libcairomm-1_0-1-32bit-1.10.0-12.2.2.x86_64
> "
>
> Only perl-Cairo can be updated from 1.090-5.1.1 to 1.103-2.1.3 but 
> that implies a lot of other changes I would rather not do. Trying one 
> of the preconfigured rpms from the openSUSE build service give errors 
> when adding the repository. Rebuilding/-compiling the source-rpm gives 
> a python error.
>
> Any other ideas?
>
> Hermann-Josef Beckers
Yes, it seems up to date...   cairo 1.12.16 being the latest.

This what I got from the slackpackage that fixed my very similar issue:
usr/lib64/libcairo.la
usr/lib64/cairo/
usr/lib64/cairo/cairo-sphinx.so.0.0.0
usr/lib64/cairo/cairo-sphinx.la
usr/lib64/libcairo-gobject.la
usr/lib64/libcairo-script-interpreter.la
usr/lib64/libcairo-script-interpreter.so.2.11200.16
usr/lib64/libcairo-gobject.so.2.11200.16
usr/lib64/libcairo.so.2.11200.16
usr/include/
usr/include/cairo/
usr/include/cairo/cairo-pdf.h
usr/include/cairo/cairo-script-interpreter.h
usr/include/cairo/cairo-ft.h
usr/include/cairo/cairo-ps.h
usr/include/cairo/cairo-script.h
usr/include/cairo/cairo-version.h
usr/include/cairo/cairo-gobject.h
usr/include/cairo/cairo-gl.h
usr/include/cairo/cairo-tee.h
usr/include/cairo/cairo-deprecated.h
usr/include/cairo/cairo-svg.h
usr/include/cairo/cairo-xcb.h
usr/include/cairo/cairo.h
usr/include/cairo/cairo-xlib-xrender.h
usr/include/cairo/cairo-xml.h
usr/include/cairo/cairo-xlib.h
usr/include/cairo/cairo-features.h

If I were trying it, I would get the source cairo, compile/install in a 
user directory [and possibly updating and dependencies of cairo], 
compile qemu referencing the cairo in the user directory and test it 
making sure my LD_LIBRARY_PATH pointed to the user directory (check with 
'ldd') and if it solves the issue, you have your answer (and would 
probably push the info up to the relevant SUSE developers).  If it 
doesn't, then I start installing more things in my 'user development' 
area... [I have gone so far as upgrading g++ - which actually got 
something working in the past ... not qemu-related].
But maybe all you need to do is downgrade qemu or search the SUSE forums ?
That's really all I can offer, as I am no expert with SUSE or the qemu 
source.

-E.