I have been experiencing a similar problem with a GeForce 7300 GT on a
Mac Pro 1,1. I also have visual artifacts in 18.04 and 20.04. With
18.04, there are no artifacts or other problems during installation from
a DVD, but when booting the installed system there are artifacts after
login and
** Tags added: hybrid multi-gpu nvidia
** Summary changed:
- display corruption
+ Display corruption with hybrid Intel+Nvidia GPUs
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
on kernel 5.8.5 fedora 32,touchpad does not work too.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
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/1872802
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
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/1872802
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
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/1872802
I'm currently running the latest KDE Neon (based on Ubuntu 20.04) and no
glitches so far even on Xorg. I can confirm that Fedora 32 also
presented the same graphical artifacts on Xorg.
Wayland Gnome sessions on both Ubuntu and Fedora were absent of
glitches.
--
You received this bug
Managed to reproduce on fresh download 20.10, too. OTOH, I remember
seeing that gone in some cases on 20.04. I wonder what the exact cases
are, as apparently this seems more complicated than "reproduces always".
** Tags added: groovy
--
You received this bug notification because you are a
** Changed in: oem-priority
Status: Triaged => Confirmed
--
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/1845801
Title:
[nvidia] Automatic login fails and then all
** Also affects: mutter (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-340 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-390 (Ubuntu Focal)
Importance: Undecided
Status: New
**
Public bug reported:
my display doesnt work properly.it mostly gets clubbed with previous window i
used in system.
Even now while i m reporting the bug,i face the same issue.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu
@Coiby Xu (coiby) ,i had tested by patch the kernel source in the file
:include/linux/input/elan-i2c-ids.h with MSFT0001 , ELAN3140
,04f33140,
but it doesn't work。
and sudo acpidump | grep -C3 ELAN result as follows:
ra@bogon Downloads]$ sudo acpidump | grep -C3 ELAN
[sudo] password for ra:
** Tags added: focal
--
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/1892136
Title:
reverse prime produces corrupted output on specific resolutions
To manage notifications about this bug
Just reproduced on 20.04.
xserver-xorg-core:
Installed: 2:1.20.8-2ubuntu2.2
Candidate: 2:1.20.8-2ubuntu2.2
No reproduction on 20.10 build, but it was tested on a different machine
and issue might be hw-dependent. Te be confirmed on the same computer
soon.
--
You received this bug
I mean only EDID version 1.4 and later advertises depth, so use that but
default to 8 bpc:
Set bpc to 8.
if ((EDID >= 1.4) && (a depth is advertised in byte 20 bits 6-4)) then
Set bpc to the depth advertised in the EDID.
endif
So for this bug it would stay with bpc=8, because the EDID is only
Hello Denial,
Do you mean if the monitor EDID < 1.4, set max bpc to 8 in kernel directly?
Do I understand it correctly?
--
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
... because the EDID this bug is about (comment #23) is version 1.3. So
it would get the default 8 bpc.
--
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 signal on 4K 60Hz
Silly question:
Why not just default to 8 bpc and then only increase it to maximum
10/12/14/16 bpc if byte 20, bits 6-4 say that deep colour is supported
by the monitor?
https://en.wikipedia.org/wiki/Extended_Display_Identification_Data#Structure,_version_1.4
--
You received this bug
** Also affects: hwe-next
Importance: Undecided
Status: New
--
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 signal on 4K 60Hz DisplayPort monitor by default,
reply to #39,
yes it's a trade off that we don't either want user get darkscreen when
then randomly plug display port for case like #38 or user get lower bpc on
their working display port.
So far, there seems no solid way to make sure both requirement.
--
You received this bug
Upstream is also working on the same kind of issue:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1391
--
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 signal on 4K
according to #40 and conversation on mattermost with Kai-Heng.
HWE is planning to add quirk for the faulty dongles so that the dark screen
during boot time[1] can be fixed.
[1] https://gitlab.freedesktop.org/drm/intel/-/issues/1890
--
You received this bug notification because you are a
22 matches
Mail list logo
