wrapper-2.0 crashed with SIGABRT in g_assertion_message_expr()

Bug #2058507 reported by corrado venturini
40
This bug affects 7 people
Affects Status Importance Assigned to Milestone
xfce4-panel (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Just started with a new install ox xubuntu 24.04

ProblemType: Crash
DistroRelease: Ubuntu 24.04
Package: libxfce4panel-2.0-4 4.18.4-1
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Wed Mar 20 17:43:26 2024
ExecutablePath: /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0
InstallationDate: Installed on 2024-03-20 (0 days ago)
InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240320)
ProcCmdline: /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libindicator-plugin.so 7 16777226 indicator Indicator\ Plugin Provides\ a\ panel\ area\ for\ Unity\ indicators.\ Indicators\ allow\ applications\ and\ system\ services\ to\ display\ their\ status\ and\ interact\ with\ the\ user.
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
Signal: 6
SignalName: SIGABRT
SourcePackage: xfce4-panel
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 main ()
Title: wrapper-2.0 crashed with SIGABRT in g_assertion_message_expr()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
separator:

Revision history for this message
corrado venturini (corradoventu) wrote :
information type: Private → Public
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 xfce4-panel (Ubuntu):
status: New → Invalid
tags: removed: need-amd64-retrace
Revision history for this message
corrado venturini (corradoventu) wrote :

attaching crash file

Revision history for this message
Francesco Castellana (xfranky) wrote :

Happening to me at every reboot after updating to Noble.

Attaching crash file.

Changed in xfce4-panel (Ubuntu):
status: Invalid → Confirmed
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.