** Changed in: egl-wayland
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1949924
Title:
yelp crashes in wayland session with NVIDIA 470
To manage noti
pyfai? the list only shows aptdaemon failing on arm64, and it has been
failing for a long time now, so we can disregard that one
--
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/1947820
Title
I can confirm crash on latest 20.04 is still there.
--
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/1871959
Title:
Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
To manag
This bug was fixed in the package egl-wayland - 1:1.1.9-1.1
---
egl-wayland (1:1.1.9-1.1) unstable; urgency=medium
* Non-maintainer upload
* d/p/egl-wayland-retrieve-DRM-device-name-before-acquiring-.patch:
- Cherry picked upstream commit to fix lock issue (LP: #1949924)
--
see Debian bugs
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994873
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994955
we can't keep valgrind enabled, or libdrm.pc would be broken
** Bug watch added: Debian Bug tracker #994873
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=99487
Public bug reported:
Impact]
New hardware support for AMD's Beige Goby needs a commit backported to
mesa. This is only needed on focal, skipping hirsute (no kernel support
there). Fixed in impish and up.
[Test plan]
Install updates, boot a BG machine and check that the desktop has full
hardware
For autopkgtest for pyfai/0.19.0+dfsg1-1build1, it prompts 'timed out',
but I don't know what's the reason.
autopkgtest [08:38:39]: test command2: - - - - - - - - - - results - - - - - -
- - - -
command2 FAIL timed out
autopkgtest [08:38:40]: summary
command1
/etc/default/grub
>> i915.force_probe=pci:v8086d4C9Asv*sd*bc03sc*i* (this is my i915
>> driver module alias)
but, you can get PCI Device ID, with lspci -nnk command
>> i915.force_probe=PCI_Device_ID (no BusID)
update-grub
/etc/environment
>> export LIBGL_DRI2_DISABLE=true
>> export LIBG
All autopkgtests for the newly accepted xorg-server
(2:1.20.13-1ubuntu1~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
aptdaemon/1.1.1+bzr982-0ubuntu32.3 (arm64)
Please visit the excuses page listed below and investigate
All autopkgtests for the newly accepted xorg-server
(2:1.20.13-1ubuntu1~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
aptdaemon/1.1.1+bzr982-0ubuntu32.3 (arm64)
Please visit the excuses page listed below and investigate
Hello,
Thanks for your answers. I did a full update/upgrade and install latest
displaylink driver. I'll let you know if crash still here.
"X server crash in iris driver" subject is still open, no news since 8
months. Any way to know if it's still in progress or if it's on pause? I
just try to kno
11 matches
Mail list logo
