[Ubuntu-x-swat] [Bug 1952999] Re: Wayland blocks the microphone of the webcam
'wayland' is just the protocol library so reassigning to Mutter which implements the protocol. Does this mean the webcam microphone works in Xorg? ** Package changed: wayland (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1952999 Title: Wayland blocks the microphone of the webcam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1952999/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1952999] [NEW] Wayland blocks the microphone of the webcam
Public bug reported: Jammy daily In the wayland session the microphone of the webcam is no available. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwayland-bin 1.19.0-2build1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 2 07:45:44 2021 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation Comet Lake UHD Graphics [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2081] InstallationDate: Installed on 2020-05-31 (549 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) MachineType: Intel(R) Client Systems NUC10i7FNH ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_nt06gx@/vmlinuz-5.13.0-20-generic root=ZFS=rpool/ROOT/ubuntu_nt06gx ro snd-intel-dspcfg.dsp_driver=1 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2019 dmi.bios.release: 5.16 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.4 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:br5.16:efr3.4:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:skuBXNUC10i7FNH:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy reproducible rls-jj-incoming single-occurrence ubuntu wayland-session ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1952999 Title: Wayland blocks the microphone of the webcam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1952999/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1952970] Re: mesa GLX change leads to wine showing GLXBadFBConfig
The attachment "wine-fix-updated.diff" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1952970 Title: mesa GLX change leads to wine showing GLXBadFBConfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952970/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1952932] Re: when choosing ubuntu on xorg the system opens with Activities then crashes "something went wrong that can't be recovered from" and then boots back to login.
*** This bug is a duplicate of bug 1952556 *** https://bugs.launchpad.net/bugs/1952556 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 1952556, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1952556 Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong." -- 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/1952932 Title: when choosing ubuntu on xorg the system opens with Activities then crashes "something went wrong that can't be recovered from" and then boots back to login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1952932/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1952970] Re: mesa GLX change leads to wine showing GLXBadFBConfig
Suggested patch. For now, I've been running mesa 20.0.x on the affected system from (21.0.x is in ubuntu-updates, 20.0.x in base ubuntu repo, so I downgraded to that and thank goodness for apt-mark hold...) But I can update it straight away to test any update that comes out. Thanks! --Henry ** Patch added: "wine-fix-updated.diff" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952970/+attachment/5544778/+files/wine-fix-updated.diff -- 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/1952970 Title: mesa GLX change leads to wine showing GLXBadFBConfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952970/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1952970] [NEW] mesa GLX change leads to wine showing GLXBadFBConfig
Public bug reported: A mesa GLX change (somewhere between the 20.0.4 and 21.0.3) causes both wine and Proton (on an older system that does not have Vulkan.. SandyBridge, OpenGL 3.3..) to exit with GLXBadFBConf when it tries to fire up OpenGL. Wine, for Direct3D support it tries to fire up (in order) Vulkan then progressively older OpenGL versions fro 4.5 down to 2.1 or maybe even 1.4 (of course the older the OpenGL the lower supported Direct3D version). Wine does not like getting an error back with the same transaction serial number as it sent out. See https://gitlab.freedesktop.org/mesa/mesa/-/issues/3969 Mesa issue 3969, The patch there throws in an "XNoOp()" to increment the transaction serial number. But the patch there caused issues in other apps, per https://gitlab.freedesktop.org/mesa/mesa/-/issues/4763 Mes issue 4763, They found XNoOp() increments the serial number, but xcb keeps a "shadow copy" of the serial number which is not incremented, causing problems. XFlush() increments the serial number, keeps xcb in sync and happy, with no real side effects (running XFlush() frequently would slow things down, but this code only runs when a GLX context is being created anyway which just doesn't happen all that frequently.) Please find attached a patch implementing the updated patch suggested in issue 4763. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libglx-mesa0 21.0.3-0ubuntu0.3~20.04.5 ProcVersionSignature: Ubuntu 5.13.0-22.22~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Dec 1 18:59:43 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Dell Picasso [1028:0a12] InstallationDate: Installed on 2020-05-05 (575 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 3505 ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=57669cb0-fd65-4eb0-9898-ed10f33d44d0 ro quiet splash nvme_core.io_timeout=300 nosmt vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2021 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.7 dmi.board.asset.tag: not specified dmi.board.name: 0RV9WY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.4.7 dmi.modalias: dmi:bvnDellInc.:bvr1.4.7:bd05/31/2021:br5.3:svnDellInc.:pnInspiron3505:pvr1.4.7:rvnDellInc.:rn0RV9WY:rvrA00:cvnDellInc.:ct10:cvr1.4.7:sku0A12: dmi.product.family: Inspiron dmi.product.name: Inspiron 3505 dmi.product.sku: 0A12 dmi.product.version: 1.4.7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- 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/1952970 Title: mesa GLX change leads to wine showing GLXBadFBConfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952970/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
Nice write up, I am back to my evdi device from a week and is working flawless now. Thanks -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1952932] [NEW] when choosing ubuntu on xorg the system opens with Activities then crashes "something went wrong that can't be recovered from" and then boots back to login.
Public bug reported: If after this crash, I choose Ubuntu on xorg, it actually loads Ubuntu (Wayland)., I am running an up to date version of 22.04 Jammy Jellyfish in a VirtualBox VM ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 1 09:48:06 2021 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.28, 5.13.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2021-10-24 (38 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) Lsusb: Bus 001 Device 010: ID 1058:1230 Western Digital Technologies, Inc. My Book (WDBFJK) Bus 001 Device 003: ID 0bda:58dc Realtek Semiconductor Corp. HP 1.0MP High Definition Webcam Bus 001 Device 009: ID 04b8:1137 Seiko Epson Corp. XP-4100 Series Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=a7759f50-03ba-4e51-bb83-fd8b08f86a95 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy reproducible ubuntu wayland-session -- 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/1952932 Title: when choosing ubuntu on xorg the system opens with Activities then crashes "something went wrong that can't be recovered from" and then boots back to login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1952932/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
After doing some deeper reading I've come across this bug via the DisplayLink GitHub Repo. As a developer, I recognize that this isn't really the responsiblity of the Canonical Ltd. to hunt down issues that don't relate back to the Core OS - to an extent - so it's not really THEIR fault that an unexpected side-effect was introduced in XServer. That being said, DisplayLink and their "external graphics card" platform powers an overwhelming majority of Home and Office Docking Stations, Conference Rooms, Backpack Adapters, etc. Ultimately frustrated end-users who don't care to dig deep into what the true issue is (including software developers) will give up and just blame Ubuntu and revert to the excuse "Linux is unstable and not a daily operating system" I personally think this is a bad look for Canonical and Ubuntu and will cause a loss in market share due to reduced confidence in the stability of the platform. Basically what I'm saying is - things like this that are glaringly obvious to end-users from the frontend perspective absolutely need to be prioritized and I hope that someone sees this and attempts to get this bug ultimately closed out. This bug has been open since 2020-04-25. I am writing this comment as of 2021-12-01. The bug located over at XServer looks to be closed as of 2020-5-29 - though it's unclear to me if it's completely merged into main. The two teams need to come together and figure this out because like I said previously - this is an extremely bad look from an end-user perspective and just adds to the invalid argument used for years that people use to complain about Linux instability. My Comment on DisplayLink GitHub: - https://github.com/DisplayLink/evdi/issues/61#issuecomment-983603462 - I am on a FRESH install of Ubuntu 20.04 as of October 6th 2021 that I updated many times before actually jumping into using it. - Reference - I started a new job that day and needed to jump into using Linux full time for the type of Software Development work I'd be doing - naturally I've used DisplayLink adapters flawlessly for years (on Windows) so it came as a shock to me that something so glaringly obvious is a problem in a major distribution like Ubuntu. XServer Bug Tracker (Closed): - https://gitlab.freedesktop.org/xorg/xserver/-/issues/1028 ** Bug watch added: github.com/DisplayLink/evdi/issues #61 https://github.com/DisplayLink/evdi/issues/61 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1952083] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1952083 Title: Add support for Beige Goby To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1952083/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1952083] Re: Add support for Beige Goby
This bug was fixed in the package mesa - 21.0.3-0ubuntu0.3~20.04.5 --- mesa (21.0.3-0ubuntu0.3~20.04.5) focal; urgency=medium * Add support for AMD Beige Goby. (LP: #1952083) -- Timo Aaltonen Mon, 22 Nov 2021 10:23:04 +0200 ** Changed in: mesa (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1952083 Title: Add support for Beige Goby To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1952083/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
Launchpad has imported 10 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1908448. 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 https://help.launchpad.net/InterBugTracking. On 2020-12-16T17:50:39+00:00 quentin wrote: Created attachment 1739727 The system journal entries at the time the problem occurs. Description of problem: Upgrading mesa-filesystem and mesa-dri-drivers from version 20.2.3-1 to version 20.2.4-1 results in: Oh no! Something has gone wrong. A problem has occurred and the system can't recover. Please contact a system administrator Version-Release number of selected component (if applicable): 20.2.4-1 How reproducible: Always Steps to Reproduce: 1. Upgrade to version 20.2.4-1 2. Reboot 3. Actual results: Oh no! message displayed as described above Expected results: Usual login screen displayed and able to login. Additional info: Dec 16 17:12:25 cain.armitage.org.uk /usr/libexec/gdm-x-session[1073]: dbus-daemon[1073]: [session uid=42 pid=1073] Activating service name='org.a11y.Bus' requested by ':1.0' (uid=42 pid=1079 comm="/usr/libexec/gnome-session-check-accelerated " label="system_u:system_r:xdm_t:s0-s0:c0.c1023") Dec 16 17:12:25 cain.armitage.org.uk /usr/libexec/gdm-x-session[1073]: dbus-daemon[1073]: [session uid=42 pid=1073] Successfully activated service 'org.a11y.Bus' Dec 16 17:12:25 cain.armitage.org.uk audit[1093]: ANOM_ABEND auid=4294967295 uid=42 gid=42 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 pid=1093 comm="gnome-session-c" exe="/usr/libexec/gnome-session-check-accelerated-gl-helper" sig=11 res=1 Dec 16 17:12:25 cain.armitage.org.uk kernel: gnome-session-c[1093]: segfault at 0 ip sp 7fffdca2fcb8 error 14 in gnome-session-check-accelerated-gl-helper[564e5cc21000+2000] Dec 16 17:12:25 cain.armitage.org.uk kernel: Code: Unable to access opcode bytes at RIP 0xffd6. Dec 16 17:12:26 cain.armitage.org.uk audit: BPF prog-id=48 op=LOAD Dec 16 17:12:26 cain.armitage.org.uk audit: BPF prog-id=49 op=LOAD Dec 16 17:12:26 cain.armitage.org.uk audit: BPF prog-id=50 op=LOAD Dec 16 17:12:26 cain.armitage.org.uk systemd[1]: Started Process Core Dump (PID 1099/UID 0). Dec 16 17:12:26 cain.armitage.org.uk audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@1-1099-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 16 17:12:26 cain.armitage.org.uk systemd-coredump[1100]: Process 1093 (gnome-session-c) of user 42 dumped core. Stack trace of thread 1093: #0 0x n/a (n/a + 0x0) Dec 16 17:12:27 cain.armitage.org.uk audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@1-1099-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 16 17:12:27 cain.armitage.org.uk systemd[1]: systemd-coredump@1-1099-0.service: Succeeded. Dec 16 17:12:27 cain.armitage.org.uk gnome-session-binary[1074]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 The first segfault appears to occur in `/usr/libexec/gnome-session-check-accelerated-gl-helper --print-renderer' gdb backtrace outputs Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/libexec/gnome-session-check-accelerated-gl-helper --print-renderer'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x in ?? () [Current thread is 1 (Thread 0x7fe0438f1740 (LWP 1093))] Missing separate debuginfos, use: dnf debuginfo-install elfutils-libelf-0.182-1.fc33.x86_64 expat-2.2.8-3.fc33.x86_64 glib2-2.66.3-1.fc33.x86_64 glibc-2.32-2.fc33.x86_64 libX11-1.6.12-3.fc33.x86_64 libX11-xcb-1.6.12-3.fc33.x86_64 libXau-1.0.9-4.fc33.x86_64 libXcomposite-0.4.5-3.fc33.x86_64 libXdamage-1.1.5-3.fc33.x86_64 libXext-1.3.4-4.fc33.x86_64 libXfixes-5.0.3-12.fc33.x86_64 libXxf86vm-1.1.4-14.fc33.x86_64 libdrm-2.4.102-2.fc33.x86_64 libedit-3.1-33.20191231cvs.fc33.x86_64 libffi-3.1-26.fc33.x86_64 libgcc-10.2.1-9.fc33.x86_64 libglvnd-1.3.2-2.fc33.x86_64 libglvnd-glx-1.3.2-2.fc33.x86_64 libselinux-3.1-2.fc33.x86_64 libxcb-1.13.1-5.fc33.x86_64 libxshmfence-1.3-7.fc33.x86_64 llvm-libs-11.0.0-1.fc33.x86_64 mesa-dri-drivers-20.2.3-1.fc33.x86_64 mesa-libGL-20.2.3-1.fc33.x86_64 mesa-libglapi-20.2.3-1.fc33.x86_64 ncurses-libs-6.2-3.20200222.fc33.x86_64 pcre-8.44-2.fc33.x86_64 pcre2-10.35-8.fc33.x86_64 sssd-client-2.4.0-2.fc33.x86_64
