The crashing function hasn't changed since 2019, which is also when a
similar bug 1847044 was declared fixed. So I think the cause here is
more about connector_state==NULL (according to the above link), which
could make edid_data!=NULL but invalid. However there is no NULL check
for connector_state even in newer releases, so something else must be
preventing that pointer from being NULL.
** Also affects: mutter (Ubuntu Stonking)
Importance: Undecided
Status: Confirmed
** Also affects: mutter (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Resolute)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu Noble)
Status: New => Triaged
** Changed in: mutter (Ubuntu Noble)
Importance: Undecided => High
** Changed in: mutter (Ubuntu Resolute)
Status: New => Incomplete
** Changed in: mutter (Ubuntu Stonking)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2166959
Title:
gnome-shell crashed with SIGSEGV in meta_output_kms_read_edid when
GetResources is called during resume from suspend
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2166959/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
