Description of problem: spicec always insists on starting a +0+0 and will not recognize the standard X -geometry option to override it. Observing the startup closely, it apparently makes one window, immediately destroys it, then makes the "real" window it is going to use. Whatever it is doing during startup apparently makes it impossible to override the initial window position via my .fvwmrc file. Version-Release number of selected component (if applicable): spice-client-0.6.3-4.fc14.x86_64 fvwm-2.5.30-2.fc14.x86_64 How reproducible: every time Steps to Reproduce: 1.run spicec to connect to a KVM 2.see a mystery frame appear for an instant 3.see final window appear positioned at 0,0 Actual results: always comes up at 0,0 Expected results: I should be able to specify the position Additional info:
Turning on some fvwm debug options reveals that spicec creates the initial window, which gets properly placed by fvwm according to my .fvwmrc file, then spicec requests the window to move to 0,0 (God knows why). Using the fvwm FixedPPosition style finally enabled me to make the window stay put.
I've a patch fixing this, I'll attach it here. This will go upstream after review.
Created attachment 468880 [details] Patch allowing the window manager to place our window where it wants
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.