gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-session (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
This is a follow up of Bug #1915870, now created with apport-cli -c.
ProblemType: Crash
DistroRelease: Ubuntu 20.10
Package: gnome-session-bin 3.38.0-1ubuntu1
ProcVersionSign
Uname: Linux 5.8.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckR
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Mon Feb 22 10:37:00 2021
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/libexec/
InstallationDate: Installed on 2020-11-15 (98 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcCmdline: /usr/libexec/
SegvAnalysis:
Segfault happened at: 0x0: Cannot access memory at address 0x0
PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: gnome-session
StacktraceTop:
?? ()
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: gnome-session-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
mtime.conffile.
separator:
information type: | Private → Public |
summary: |
- gnome-session-check-accelerated-gl-helper crashed with SIGSEGV + gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in + cso_destroy_context() [r300_dri.so] |
Here is some more system information. See journal.txt.