Public bug reported:
Description:
this feature tracks the updates of mesa 3d for TGL support.
We will update the commitid list as necessary
Target Release: 20.10
Target version: TBD
** Affects: intel
Importance: Undecided
Status: New
** Affects: mesa (Ubuntu)
Importance:
Launchpad has imported 24 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1648475.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Your Xorg logs are showing:
[ 4864.686] (WW) modeset(0): hotplug event: connector 93's link-state
is BAD, tried resetting the current mode. You may be leftwith a black
screen if this fails...
where connector 93 is the DisplayPort. Please try a different monitor
cable, or just replugging it.
**
** Package changed: gdm3 (Ubuntu) => xorg-server (Ubuntu)
--
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/1853328
Title:
gdm-x-session loops printing its mode lines to syslog
To manage
[775834.395] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage
[775834.395] (WW) glamor: Failed to allocate 5x5 FBO due to GL_OUT_OF_MEMORY.
[775834.395] (WW) glamor: Expect reduced performance.
[776320.877] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage
[776320.877] (EE)
If a different monitor cable does not work then please try a different
monitor if you can. There is some kind of hardware fault here.
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Your kernel log also mentions problems with the same hardware:
[ 1723.813855] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable
link training
[ 2612.326756] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable
link training
--
You received this bug notification
You have been subscribed to a public bug:
On waking from, generally a long sleep, my laptop loops in gdm. I get a
continuous stream of:
Nov 20 15:34:15 X1 /usr/lib/gdm3/gdm-x-session[2674]: (--) modeset(0): HDMI max
TMDS frequency 31KHz
Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]:
Tracking in:
https://errors.ubuntu.com/problem/af88d9cd45acf4632e47789e4661be6a47b4dbf1
** Tags added: bionic disco xenial
** Description changed:
+ https://errors.ubuntu.com/problem/af88d9cd45acf4632e47789e4661be6a47b4dbf1
+
+ ---
+
I'm using a Dell XPS 9380 ("developer edition") connected
*** This bug is a duplicate of bug 1853120 ***
https://bugs.launchpad.net/bugs/1853120
** This bug has been marked a duplicate of bug 1853120
Xorg crashes with SIGBUS in drmmode_load_cursor_argb_check
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
*** This bug is a duplicate of bug 1853120 ***
https://bugs.launchpad.net/bugs/1853120
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
xorg-server. This problem was most recently seen with package version
2:1.20.5+git20191008-0ubuntu1,
** Summary changed:
- Fractional scaling has significant visible tearing on a 4k display in Xorg
sessions
+ Fractional scaling has significant visible tearing in Xorg sessions
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1852752
Title:
DPMS does not switch off the
*** This bug is a duplicate of bug 1846398 ***
https://bugs.launchpad.net/bugs/1846398
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1846398, so it is being marked as such. Please
** Summary changed:
- Xorg crashes with a bus error in OsLookupColor when using a second display
+ Xorg crashes with SIGBUS in drmmode_load_cursor_argb_check
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
Sounds like you're not getting a login screen, is that right?
It wouldn't be surprising given it's a rare and not well tested:
Intel(R) Core(TM) i5 CPU M 460 @ 2.53GHz
Please try editing /etc/gdm3/custom.conf and uncomment:
#WaylandEnable=false
then reboot.
** Package changed:
You have been subscribed to a public bug:
I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480
laptop with two external displays. The laptop itself is closed (internal
display is not used).
In a gnome xorg session, there is severe tearing on parts of the screen
when dragging
Since Xorg is using the modeset driver here I think this might be an
issue with the Raspberry Pi kernel driver(s)
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Summary changed:
- DPMS does not switch off the monitor back light
+ DPMS does not switch off the monitor back light on
I can see a couple of pixel-layout-related settings here:
dithering depth: auto
supported: auto, 6 bpc, 8 bpc
dithering mode: auto
supported: auto, off, static 2x2, dynamic 2x2, temporal
The nouveau kernel driver provides them regardless of the
Does the problem occur if you log into 'Ubuntu on Wayland' ?
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which
** Summary changed:
- Touchpad not working
+ Dell Inspiron 3558 touchpad stopped working in kernel 4.15.0-72 (but
4.15.0-70 is OK)
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu-X,
Public bug reported:
The touchpad is not detected by my Dell Inspiron 3000 series laptop,
this happened after my kernel was updated from 4.15.0-70 to 4.15.0-72.
If I enter Ubuntu Advanced Options to my previous kernel (4.15.0-70) my
touchpad works correctly.
ProblemType: Bug
DistroRelease:
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
*** This bug is a duplicate of bug 1848741 ***
https://bugs.launchpad.net/bugs/1848741
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1848741, so it is being marked as such. Please
Sorry I can't see a problem in that screenshot. Can you provide more?
** Tags added: nouveai
** Tags removed: nouveai
** Tags added: nouveau
** Summary changed:
- Pixel pattern error in over
+ [nouveau] Pixel pattern error in over
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
**
** Package changed: xorg (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1852117
Title:
non appare nessuna applicazione
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1421808 ***
https://bugs.launchpad.net/bugs/1421808
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1421808 / bug 1787332 / bug 1787338, so it is
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1852071
Title:
[HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys
works as
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1852083
Title:
[HP ZBook Studio G5, Ubuntu 18.04.3 LTS, bluetooth mouse] Choppy/laggy
Although you are completely right about "I guess an udev rule to disable
Wayland for GMA500 is all that is needed."
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Importance: Undecided => Low
** Changed in: mutter (Ubuntu)
Status: New => Triaged
It appears GMA500 is the infamous Poulsbo with PowerVR GPU:
https://en.wikipedia.org/wiki/Intel_GMA#GMA_500
This means it is closed source and we can't support it :(
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Although you are complete right about "I guess an udev rule to disable
Wayland for GMA500 is all that is needed."
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1852023
Title:
Wayland doesn't
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.
You can subscribe and participate further through the new bug through
this link to our GitLab instance:
(In reply to nv28m from comment #71)
> nouveau.agpmode=0 seems to work here too, also after comming back from
> suspend.
>
> Still I think I'm stuck with the modesetting driver with the bit 24 hack in
> boot/suspend scripts. The scrolling and rxvt performance is just better.
The parameter name
I also have this problem. Everything unaccelerated comes up as trash,
even on the kernel framebuffer (if acceleration was switched off). Or
for example I can see most of the graphics ok, but if I use ShadowFB
then the whole screen is unusable. And the cursor is garbage too most of
the time.
This
I reached to retreive my video bios version*:
cat /proc/driver/nvidia/cards/0
Model: GeForce4 4200 Go
IRQ: 11
Video BIOS: 04.28.20.31.c1
Card Type: AGP
DMA Size: 32 bits
DMA Mask: 0x
Maybe you will like to check against your own and tell me you need
something else from me.
* not that
nouveau.agpmode=0 seems to work here too, also after comming back from
suspend.
Still I think I'm stuck with the modesetting driver with the bit 24 hack
in boot/suspend scripts. The scrolling and rxvt performance is just
better.
--
You received this bug notification because you are a member of
Guys, if I can help in any maneer I'd be glad. I want you to know my
video adapter is flashed with a bios update I found long time ago on
dell's site (in my memory, this was a bios update for Windows).
--
You received this bug notification because you are a member of Ubuntu-X,
which is
I ended in Ubuntu 12.04 with latest nvidia-96(-updates maybe). The
Laptop sleeps now for weeks and I won't wake it up. I Just can say that
once I admitted that vino won't work with desktop effects, I decided to
use this laptop with gnome-shell no-effects only, and with the latest
drivers state
Hi, I do not know if it may be still relevant after nv28m dicoveries but
here's some quick info (with a debian testing fully updated a month
ago).
Booting with plain nouveau (agp v2 4x): distorted mouse, nothing new
here :(
I tried to boot the following kernel command lines:
*
(In reply to Ilia Mirkin from comment #64)
> (In reply to comment #63)
> >
> > Option 3 could definately tell if it's only used for a particular memory
> > configuration of this chip, or it's more general (e.g. first 2 options).
>
> I've fired off a question to NVIDIA, hopefully they'll
(In reply to AndrewK from comment #73)
> (In reply to nv28m from comment #71)
> > nouveau.agpmode=0 seems to work here too, also after comming back from
> > suspend.
> >
> > Still I think I'm stuck with the modesetting driver with the bit 24 hack in
> > boot/suspend scripts. The scrolling and
agpmode and modeset are not even remotely related I'm afraid. With 4.3
onward one should be using nouveau.config="NvAGP=0" as documented [1]
[1] http://nouveau.freedesktop.org/wiki/KernelModuleParameters/#config
--
You received this bug notification because you are a member of Ubuntu-X,
which
Yes, it was taken after several attempts, that's why it was already set.
I've made a better dump and sent it in e-mail now. According to this
it's set the first time it's written to.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
(In reply to Ilia Mirkin from comment #75)
> (In reply to AndrewK from comment #73)
> > (In reply to nv28m from comment #71)
> > > nouveau.agpmode=0 seems to work here too, also after comming back from
> > > suspend.
> > >
> > The parameter name seems to be changed. nouveau.modeset=0 is what
(In reply to Emil Velikov from comment #77)
> agpmode and modeset are not even remotely related I'm afraid. With 4.3
> onward one should be using nouveau.config="NvAGP=0" as documented [1]
>
> [1] http://nouveau.freedesktop.org/wiki/KernelModuleParameters/#config
Yes. The syntax given seems to
On Lubuntu 14.04.3 (I think it's Kernel 3.19.x) "nouveau.agpmode=0" also works,
although standby still doesn't seem to work.
What I want to note though, is, that activating the Shadow Framebuffer in
/etc/X11/xorg.conf.d/20-nouveau.conf results in a substantial performance
increase regarding
I've wasted a lot of time with the mmio registers to find out why things
go slow. But it seems it's something else.
Just loading the nvidia kernel module without starting X is enough to
make nouveau go fast after kexec.
I did an mmio trace while loading the module, but it only wrote 140 to
0,
Even more interesting, your trace actually has
[0] 1012.956817 MMIO32 R 0x100080 0xe100 PFB+0x80 => 0xe100
[0] 1012.956820 MMIO32 W 0x100080 0xe100 PFB+0x80 <= 0xe100
Which means that it _starts out_ at 0xe100. Was this trace done on a
clean boot, or had the nvidia module
BTW, interesting. In your VBIOS, it tells us to do
0xcbf2: 7a 80 00 10 00 00 00 00 e0 ZM_REG
R[0x100080] = 0xe000
Which is why that bit gets lost on resume (but not on kexec, since init
scripts don't run, since the adapter is already init'd). Good to know,
that means that
(In reply to comment #63)
> For the first two options I think it could be useful to grep through all
> those dumps collected over the years and check which cards have this set.
Yeah, I'll try to have a look later on.
>
> Option 3 could definately tell if it's only used for a particular memory
>
For the first two options I think it could be useful to grep through all
those dumps collected over the years and check which cards have this
set.
Option 3 could definately tell if it's only used for a particular memory
configuration of this chip, or it's more general (e.g. first 2 options).
By
I ignore if it's related, but my Dell D800 with nv28 burts many-many-many beeps
on boot until the grub menu displays. Feel free to ask any thing.
Regards
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
(In reply to comment #61)
> At the end I got what I wanted. The winner is:
> nvapoke 00100080 e100
>
> This register is e000 after suspend or after clean boot. So all this
> trouble only because of a single bit was not set ;(
Fantastic! I was secretly hoping that by ignoring the issue
I've e-mailed the dump file.
I've put in 3 markers, one before starting xinit /usr/bin/urxvt, one in
urxvt before quiting, and one after xinit returned.
I hope it's useful. Thanks! I can try to repeat the same thing using the
nouveau driver, if needed.
--
You received this bug notification
I had the feeling that there's not much chance that the dump alone will
help. So I did some debugging on my own, after all it can't be that hard
if I have the hardware at hand to play with ;)
First I've collected all writes locations out from the dump, and ignored
the part which looked like a
Doing a suspend to RAM restores the original trashing behaviour. I'm not
sure, but maybe the screen update is slower as well now.
This is a Dell D800:
01:00.0 VGA compatible controller: NVIDIA Corporation NV28M [GeForce4 Ti 4200
Go AGP 8x] (rev a1)
X.Org X Server 1.15.1
Release Date: 2014-04-13
(In reply to comment #55)
> So something is initialized by the nvidia driver, which is not touched by
> nouveau but is required for correct operation.
>
> Is there a way I could help? Like dumping register states with/without the
> nvidia init?
You could do a mmiotrace of the nvidia driver. It's
The default Debian kernel is not very debug friendly, so I've dumped the ROMs
with nvagetbios. There are two versions, as I made a firmware update later to
see if it helps. (e-mailed)
The MMIO dumps are comming soon, tomorrow or so. This is a slow machine
and the kernel compile takes a while
I just discovered this bug as I acquired a Dell Inspiron 8500 a few
weeks back and ran into the same problem. In fact, on my machine (same
nVidia graphics), the problem even seems worse: Any attempt at using the
nouveau driver so far has not only produced the distortions described by
the original
** Changed in: nouveau
Status: Confirmed => Unknown
** Bug watch added:
gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues #29
https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/29
--
You received this bug notification because you are a member of Ubuntu-X,
** Summary changed:
- Screen brightness adjustment delay
+ Screen brightness adjustment delay in Xorg sessions only
** Package changed: linux (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: Confirmed => New
** Also affects: xorg-server (Ubuntu)
Importance:
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: unity (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Please avoid reporting multiple issues in a single bug.
The tearing issue is bug 1846398 already so the remaining issues are
"Ubuntu operates slow with system apps and 3rd party apps; system hangs
and crashes; and more". Are you saying Ubuntu is only slow when you are
using fractional scaling?
Which GUI are you using that exhibits the problem?
** Summary changed:
- Xorg freeze on high disk or cpu load or random
+ GUI freeze on high disk or CPU load, but disabling swap fixes it
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Confirmed
Thanks. I've now added this bug to the performance tracking list:
https://trello.com/c/pe5mRmx7
** Summary changed:
- gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just
to update the screen
+ gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just
** Changed in: nouveau
Status: Confirmed => Unknown
** Bug watch added:
gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues #100
https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/100
--
You received this bug notification because you are a member of
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.
You can subscribe and participate further through the new bug through
this link to our GitLab instance:
I downloading & booted Xubuntu 20.04 daily and played there.
same hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
on same box. adding xscreensaver & using 'flurry', I got the same jerky/choppy
response here once packages added & running.
I could see the xscreensaver dialog box where I click
This bug only is present on Wayland.
--
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/1850874
Title:
gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU
cores just to update the
** Changed in: linux
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1848900
Title:
[amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3
This might be bug 1798790.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-430 in Ubuntu.
https://bugs.launchpad.net/bugs/1851910
Title:
[nvidia] Display does not show up (short flashes)
To manage notifications about
Please try editing /etc/gdm3/custom.conf and then uncomment:
#WaylandEnable=false
And then reboot.
** Tags added: nvidia
** Summary changed:
- Display does not show up (short flashes)
+ [nvidia] Display does not show up (short flashes)
** Package changed: xorg (Ubuntu) =>
Please also tell us exactly which browsers exhibit the bug.
** Package changed: xorg (Ubuntu) => ubuntu
** Summary changed:
- Xorg freeze
+ GUI freeze
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Package changed: xorg (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1851649
Title:
Package bug
To manage notifications about this bug go to:
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
** Summary changed:
- Xorg freeze
+ GUI freeze
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Please open two Terminal windows.
In one run:
dmesg -w
In the other run:
journalctl -f
Now wait and reproduce the freeze a few times. Each time look at those
two Terminal windows and tell us if you see any particular messages just
after each freeze.
--
You received this bug notification
** Package changed: xorg (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1851018
Title:
xorg have some bugs.
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1809407 ***
https://bugs.launchpad.net/bugs/1809407
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please execute the following command only once, as it will
automatically gather debugging information, in a terminal:
*** This bug is a duplicate of bug 1809407 ***
https://bugs.launchpad.net/bugs/1809407
Actually this sounds like bug 1809407 so let's just assume it is unless
proven otherwise.
** This bug has been marked a duplicate of bug 1809407
[nvidia] Corrupted wallpaper after resuming from suspend
I think the Gnome Shell developers have been working on how that code
(efficient screen updates for VMs) works in Wayland sessions. But I
don't know the details. Let's hope mutter 3.36 performs better in that
area.
--
You received this bug notification because you are a member of Ubuntu-X,
which
*** This bug is a duplicate of bug 1824753 ***
https://bugs.launchpad.net/bugs/1824753
Sounds like Qt bug 1824753
** This bug has been marked a duplicate of bug 1824753
When I pass the Qt application to the secondary monitor the characters of
the application increase
--
You received
Comment #16 is confusing because it sounds like you're now talking about
multiple unrelated issues. It is also confusing because comment #16
suggests this bug occurs in Wayland only but comment #13 looks like it's
from Xorg.
Is this bug affecting Wayland sessions only?
** Changed in: gnome-shell
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.
You can subscribe and participate further through the new bug through
this link to our GitLab instance:
** Changed in: nouveau
Status: Confirmed => Unknown
** Bug watch added:
gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues #335
https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/335
--
You received this bug notification because you are a member of
** Bug watch added: gitlab.freedesktop.org/drm/amd/issues #956
https://gitlab.freedesktop.org/drm/amd/issues/956
** Also affects: linux via
https://gitlab.freedesktop.org/drm/amd/issues/956
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
89 matches
Mail list logo
