qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [Bug 1548170] [NEW] qemu-kvm-spice spice server locks u


From: John Snow
Subject: Re: [Qemu-devel] [Bug 1548170] [NEW] qemu-kvm-spice spice server locks up when large user image is set
Date: Wed, 24 Feb 2016 16:35:54 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0


On 02/21/2016 11:06 PM, Christopher Snowhill wrote:
> Public bug reported:
> 
> QEMU emulator version 2.0.0 (Debian 2.0.0+dfsg-2ubuntu1.22), Copyright
> (c) 2003-2008 Fabrice Bellard
> 
> I have QEMU kvm spice installed, running a Windows 10 1511, freshly
> installed this morning, using VirtIO root volume, Ethernet, and QXL
> graphics through Spice. It successfully installed the latest updates,
> and installed Visual Studio 2010 Professional plus Service Pack 1 and
> updates.
> 
> Upon attempting to configure the following PNG as my account's user
> picture in the Settings control panel applet:
> 
> https://static.kode54.net/pwywcomm_christopher_8bpp.png
> 
> It added successfully, but then I noticed that Windows does not support
> alpha blended user pictures, and it blended it against white, so I
> quickly replaced it with the following:
> 
> https://static.kode54.net/pwywcomm_christopher_blended.png
> 
> Upon assigning that, with the other one still in the previous image
> buttons, Spice locked up completely. The VM was still running, as
> evidenced by a successful Remote Desktop session.
> 
> Do I need to replace my entire Qemu setup with a Git or hand built
> official version to verify that this isn't Ubuntu's fault?
> 
> ** Affects: qemu
>      Importance: Undecided
>          Status: New
> 

Were you able to revert the change and get SPICE to unlock, or otherwise
reproduce the issue? Are the two different PNG files sufficient for
reproducing the problem? Does it happen when you switch from one png to
another generically, or only these two?

Looks like it's working out OK for 2.5, but was the problem reproducible
for your ~2.0 version that we can safely say it's now fixed?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]