I do not recommend that as a solution. The open source 'nouveau' driver
generally causes more problems than it solves. And performance is
significantly lower than the proprietary driver.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
^^^
Daniel, I wrote that answer mostly for the bug you mentioned, but as I
mentioned in my answer, it fixes the corrupted background bug as well.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
^^^
That is bug 1892440. It is not relevant here.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1855757
Title:
[nvidia] Background image corrupted after standby or
For now you can easily fix this without any third-party applications by
following these instructions: https://askubuntu.com/a/1269431/1119550
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
the real bug is why it's not using the native driver.. run apport-
collect which should add relevant logs etc for mesa
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1889992
Title:
Ubuntu Focal
I guess my only request is that:
if (EDID_version >= 1.4 && EDID_supports_10bit) then
don't restrict "max bpc"
endif
** Also affects: linux via
https://gitlab.freedesktop.org/drm/intel/-/issues/1890
Importance: Unknown
Status: Unknown
--
You received this bug notification
I guess my only request is that:
if (EDID_version > 1.4 && EDID_supports_10bit) then
don't restrict "max bpc"
endif
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1890772
Title:
No
Thanks for understanding.
There's an upstream bug discussing this similar issue, we can follow their
effort there.
https://gitlab.freedesktop.org/drm/intel/-/issues/1890
** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #1890
https://gitlab.freedesktop.org/drm/intel/-/issues/1890
I can't see any problems in the attached files. Can you please attach a
photo of the problem?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
No problem. It's not up to me anyway...
Long term, to get the GUI work done you will need to request
enhancements in both of these projects:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues
https://gitlab.gnome.org/GNOME/mutter/-/issues
Short term, to get the default changed you
I think different from #32.
To adding a GUI configure bpc is a long-term plan.
Before that,the default behavior should be designed to get the best user
experience.
As we all know, there're lot of hardware components on the pipline of display
path(e.g. socket, converter, dongle, cable, monitor)
11 matches
Mail list logo
