Bug 1268667 - sddm, lightm, and lxdm: Incorrect resolution after logout (qemu-kvm guest)
Summary: sddm, lightm, and lxdm: Incorrect resolution after logout (qemu-kvm guest)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: spice-vdagent
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christophe Fergeau
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-04 13:14 UTC by Giulio 'juliuxpigface'
Modified: 2015-10-17 09:30 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-10-17 09:30:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Giulio 'juliuxpigface' 2015-10-04 13:14:51 UTC
Description of problem:
After loggin out from a desktop session, the resolution changes and it's impossible to revert it. It's also impossible to reach some buttons of the GUIs. Mouseclicks doesn't also work properly.

I've encountered this with various login managers (kde's default one, xfce's default one and lxde's default one): the only one exception is gdm, which resizes correctly after the logout.

Version-Release number of selected component (if applicable):
spice-vdagent-0.16.0-1.fc23.i686

How reproducible:
- Always (with sddm, lightm, lxdm)
- Never (with gdm)

Steps to Reproduce:
1. Start an installed qemu-kvm guest with virt-manager.
2. Log in to a standard desktop session.
3. Log out.

Actual results:
The resolution doesn't fit all the GUI.

Expected results:
The resolution should contain all the GUI.

Additional info:
I'm pretty sure that this is a regression of a component (not sure if it's spice-vdagent fault, though), because I remember that logout was working fine during the F22 testing cycle.

Comment 1 Giulio 'juliuxpigface' 2015-10-17 09:30:00 UTC
Closing this as I can't reproduce the issue with 'spice-vdagent-0.16.0-2.fc23'.


Note You need to log in before you can comment on or make changes to this bug.