wrapper-2.0 crashed with SIGSEGV in g_slice_alloc()

Bug #1811479 reported by David Kastrup
74
This bug affects 16 people
Affects Status Importance Assigned to Milestone
xfce4-panel (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Right after system update.

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: libxfce4panel-2.0-4 4.13.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-11.12-lowlatency 4.18.12
Uname: Linux 4.18.0-11-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu18
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Sat Jan 12 01:32:48 2019
ExecutablePath: /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0
InstallationDate: Installed on 2011-10-14 (2646 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libwhiskermenu.so 1 10485771 whiskermenu Whisker\ Menu Show\ a\ menu\ to\ easily\ access\ installed\ applications
SegvAnalysis:
 Segfault happened at: 0x7fb0b568976a <g_slice_alloc+506>: mov (%rbx),%rdx
 PC (0x7fb0b568976a) ok
 source "(%rbx)" (0x0000002b) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xfce4-panel
StacktraceTop:
 g_slice_alloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_list_append () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_queue_push_tail () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: wrapper-2.0 crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev pulse-access sambashare

Revision history for this message
David Kastrup (dak) wrote :
information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xfce4-panel (Ubuntu):
status: New → Confirmed
Revision history for this message
Chris Guiver (guiverc) wrote :

Xubuntu 19.04 DAILY (live) QA-Test (20190325)
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

general play using menu, I'd earlier added another panel, updates were downloading & installing and whilst using menu crash appeared.

No unusual behavior was noticed.
http://iso.qa.ubuntu.com/qatracker/milestones/398/builds/190273/testcases/1303/results/

Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1811479

tags: added: iso-testing
Revision history for this message
BertN45 (bertnijhof) wrote :

OK It also happened on my 19.10 development branch

Revision history for this message
Chris Guiver (guiverc) wrote :

Xubuntu 19.10 (daily) install from a very recent QA-Test install booted for a test of something related to a ask-ubuntu question.

This is dell optiplex 780 so not the machine mentioned in a prior comment, I'd just logged in and was trying to adjust my right display (it's portrait-left tilted) and crash was reported.

(Something isn't right; I thought I'd adjusted my displays to match my setup; but it's responding as if I only have a single display connected)

Revision history for this message
Sean Davis (bluesabre) wrote :

Is this issue still occurring in a recent supported release (focal, impish, jammy)?

Changed in xfce4-panel (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xfce4-panel (Ubuntu) because there has been no activity for 60 days.]

Changed in xfce4-panel (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

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