Bug 1383425 - QXL driver does not automatically adjust resolution on kernels past 3.16
Summary: QXL driver does not automatically adjust resolution on kernels past 3.16
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: libkscreen
Version: 25
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Daniel Vrátil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-10 15:03 UTC by bancfc
Modified: 2017-12-12 11:04 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 11:04:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 356864 0 None None None 2016-11-18 07:33:33 UTC
KDE Software Compilation 370494 0 None None None 2016-10-18 14:50:28 UTC

Description bancfc 2016-10-10 15:03:39 UTC
Description of problem:

QXL can no longer automatically adjust screen resolution with very vanilla kernel whether distro provided or compiled past 3.16.

This should be visible on every virtualized guest setup but I will specify the environment I run just in case its not reproducible:

Debian stable (Jessie) i386 guest, Wih KDE desktop environment. Running a kernel greater than 3.16.


A workaround is to disable KMS but that is a very ugly workaround. Also in the case of hardened kernels comes at a price of reduced protection.

Reference:

https://forums.grsecurity.net/viewtopic.php?f=3&t=4449#p16533

Comment 1 Pavel Grunt 2016-10-10 15:35:23 UTC
The solution is to implement handling of the monitor hotplug event in the window manager of KDE, like GNOME did in mutter and gnome-settings-daemon

(I don't think Fedora is correct product for Debian)

Comment 2 bancfc 2016-10-11 12:54:41 UTC
So should I report it to KDE then?

> (I don't think Fedora is correct product for Debian)

I tried looking for an "other distro" label but couldn't find one.

Comment 3 Pavel Grunt 2016-10-11 13:15:18 UTC
(In reply to bancfc from comment #2)
> So should I report it to KDE then?
yes

the GNOME bugs related to the issue:
https://bugzilla.gnome.org/show_bug.cgi?id=711216
https://bugzilla.gnome.org/show_bug.cgi?id=702804#c9

see also these bugs for more info:
https://bugzilla.redhat.com/show_bug.cgi?id=1153709
https://bugzilla.redhat.com/show_bug.cgi?id=1290586
> 
> > (I don't think Fedora is correct product for Debian)
> 
> I tried looking for an "other distro" label but couldn't find one.

upstream bugzilla of the component is more appropriate when the problem is not specific to a distro:
https://bugs.freedesktop.org/enter_bug.cgi?product=xorg

Comment 4 bancfc 2016-10-12 13:26:58 UTC
Reported to KDE and got a reply from Martin Gräßlin:

https://bugs.kde.org/show_bug.cgi?id=370494#c1

Although he will look at fixing it it's his opinion that the best solution would be to implement the code in virt-viewer for generic cross-DE compatibility.

Comment 5 Pavel Grunt 2016-10-12 13:31:29 UTC
thanks, but it is a purely guest issue - so cannot be fixed in virt-viewer

Comment 6 Christophe Fergeau 2016-10-12 15:19:15 UTC
This used to be handled in spice-vdagent, but changed when the kernel kms qxl driver was introduced. Your desktop environment is going to be watching for new monitors appearing, it's going to try to remember their preferred resolution/position/..., having another program (spice-vdagent) trying to configure things on its own is very likely to be conflicting with that, and to cause some weird corner cases. So the decision was made to let the desktop environment handle this as it has full knowledge of what it wants to do with the screens.

Comment 7 bancfc 2016-10-20 18:10:53 UTC
Thanks Pavel for taking this up with the KDE guys.

Comment 8 Pavel Grunt 2016-11-18 07:33:34 UTC
Per https://bugs.kde.org/show_bug.cgi?id=370494#c17 is fixed upstream -> reassigning to KDE component

Comment 9 Rex Dieter 2016-11-18 12:29:35 UTC
Quoting upstream bug 
"So git master has all the patches in place, and I'll look into backporting these bits to Plasma 5.8.4."

Comment 10 Fedora End Of Life 2017-11-16 19:11:25 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 11 Fedora End Of Life 2017-12-12 11:04:39 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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