gnome-shell crashes randomly

Bug #2061242 reported by Roman
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Don't yet understand what triggers it, maybe monitor connect/disconnect.

ProblemType: Crash
DistroRelease: Ubuntu 24.04
Package: gnome-shell 46.0-0ubuntu4
Uname: Linux 6.9.0-rc2 x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 13 20:29:01 2024
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2024-02-14 (60 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240212)
ProcAttrCurrent: Error: [Errno 22] Invalid argument
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
RelatedPackageVersions: mutter-common 46.0-1ubuntu6
Signal: 6
SignalName: SIGABRT
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker libvirt lpadmin ollama plugdev sudo users

Revision history for this message
Roman (vient1) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed as the report has a core dump which is invalid. The
corruption may have happened on the system which the crash occurred or during
transit.

Thank you for your understanding, and sorry for the inconvenience!

Changed in gnome-shell (Ubuntu):
status: New → Invalid
tags: removed: need-amd64-retrace
Revision history for this message
Roman (vient1) wrote (last edit ):

Hi Brian, my report once again got "invalid core dump" message. Strangely, now it took 2 weeks instead of 1 hour.

We've previously talked in https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2058693, you said to attach a .crash file and make report private, which I did. Can you access the report now? If not, how can I add you to it?

information type: Private → Public
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I can tell from the log that it's bug 2050865 which should be fix-released within weeks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.