Description of problem: Every spicec window is named "SPICEc:0". This is not real useful if you are working with multiple virtual machines and want to find the window for a particular one. Please provide a way to set the window manager title in the spice client. Version-Release number of selected component (if applicable): spice-client-0.6.3-4.fc14.x86_64
Created attachment 468521 [details] patch to add --title option Add a title option is pretty trivial. I'm enclosing the patch I just created to do it.
Hi, Thanks for using spice, for the bug reports and for the patch. I did a very similar patch myself yesterday, but did not get around to update this bug yet. I'm also working on your other 2 bug reports. Once I've fixes for all 3, and they are reviewed upstream I'll build an updated spice package as a Fedora update. Regards, Hans
I think the problem should better be tackled in a different way. The spice protocol should be extended so the spice client can get meta informations about the virtual machine (with the name being the most important one). With vnc we have that: If you start your virtual machine using 'qemu -name $something' then connect to it using vnc the vnc client will display the name automatically, there is no need to set it manually.
Yep, getting the name automatically would make a lot of sense, but the --title option was a lot simpler to add :-). I also noticed that the window manager class is not set by spicec. Having the class be SPICEc all the time even if the title is changed could be handy for window managers to simplify spice window recognition.
FYI: There is a gtk-based client in development. It is already usable although isn't complete yet. It should be alot less annonying as gtk does sane window management for us. http://gitorious.org/spice-gtk/spice-gtk
(In reply to comment #3) > I think the problem should better be tackled in a different way. The spice > protocol should be extended so the spice client can get meta informations about > the virtual machine (with the name being the most important one). > > With vnc we have that: If you start your virtual machine using 'qemu -name > $something' then connect to it using vnc the vnc client will display the name > automatically, there is no need to set it manually. I agree in principal, but this is not how things currently work. If the client is launched from the cmdline, currently we are stuck with a fixed title. And if the client is started through the RHEV-M interface using the browser xpi and the controller interface. Sinds we will likely need to support overriding the title to the controller interface, even if set through to the to-be-written protocol extension, for the near future. It makes sense to also add a --title cmdline option because: 1) It is almost zero code as we need title overriding code anyways 2) It will still be useful when connecting to virtual machines which are running a version of the spice protocol which does not pass the title info (which will be around for a while yet)
Created attachment 468878 [details] PATCH to set the wm_class Here is a patch to set the wm_class in case you're interested. This will go upstream after review.
spice-protocol-0.6.4-1.fc14,spice-0.6.4-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/spice-protocol-0.6.4-1.fc14,spice-0.6.4-1.fc14
spice-protocol-0.6.4-1.fc14, spice-0.6.4-1.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update spice-protocol spice'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/spice-protocol-0.6.4-1.fc14,spice-0.6.4-1.fc14
spice-protocol-0.6.4-1.fc14, spice-0.6.4-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.