Public bug reported: Casual browsing, and then boom "Oh no! Something has gone wrong" screen. Ubuntu 23.10, Lenovo ThinkPad P14s gen4 amd, AMDGPU open source drivers, also I switched to X Server from the default Wayland because of Wayland bugs.
A stack trace frame I got manually, but I didn't persist much:
```
─── Stack
───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────(138
results) [2033/2675]
[12] from 0x00007f62b1f63adb in __glXSendError+155 at ../src/GLX/libglx.c:805
arg dpy = 0x562471d040d0, errorCode = <optimized out>, resourceID = 0,
minorCode = <optimized out>, coreX11error = 0
[13] from 0x00007f62b5f0962f
(no arguments)
[14] from 0x00007f62b5f09d29
(no arguments)
[15] from 0x00007f62b5f0734e
(no arguments)
[16] from 0x00007f62b5ee347b
(no arguments)
[+]
─── Source
───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
789 if (dpyInfo == NULL || !dpyInfo->glxSupported) {
790 return;
791 }
792
793 LockDisplay(dpy);
794
795 error.type = X_Error;
796 error.errorCode = errorCode;
797 error.sequenceNumber = dpy->request;
798 error.resourceID = resourceID;
799 error.minorCode = minorCode;
800 error.majorCode = dpyInfo->glxMajorOpcode;
801 if (!coreX11error) {
802 error.errorCode += dpyInfo->glxFirstError;
803 }
804
805 _XError(dpy, &error);
806
807 UnlockDisplay(dpy);
808 }
809
810 static void NotifyXError(Display *dpy, unsigned char errorCode,
811 XID resourceID, unsigned char minorCode, Bool coreX11error,
812 __GLXvendorInfo *vendor)
813 {
814 if (vendor != NULL && vendor->glxvc->notifyError != NULL) {
815 Bool ret = vendor->glxvc->notifyError(dpy, errorCode, resourceID,
816 minorCode, coreX11error);
817 if (!ret) {
818 return;
819 }
820 }
821 __glXSendError(dpy, errorCode, resourceID, minorCode, coreX11error);
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
>>> p error
>>>
>>>
$1 = {
type = 0 '\000',
errorCode = 161 '\241',
sequenceNumber = 36705,
resourceID = 0,
minorCode = 23,
majorCode = 152 '\230',
pad1 = 182 '\266',
pad3 = 32610,
pad4 = 0,
pad5 = 0,
pad6 = 3056388541,
pad7 = 32610
}
```
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.1-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 15 09:43:27 2024
DisplayManager: gdm3
InstallationDate: Installed on 2023-11-25 (51 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
RelatedPackageVersions: mutter-common 45.2-0ubuntu2~really45.0
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2049368
Title:
gnome-shell crash while chaing Chromium browser tab
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2049368/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
