xfce4-appfinder crashed with SIGSEGV in g_slice_alloc()

Bug #1814129 reported by David Kastrup
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xfce4-appfinder (Ubuntu)
New
Undecided
Unassigned

Bug Description

No idea what this is about.

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: xfce4-appfinder 4.13.2-1
ProcVersionSignature: Ubuntu 4.18.0-11.12-lowlatency 4.18.12
Uname: Linux 4.18.0-11-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu19
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jan 31 01:42:40 2019
ExecutablePath: /usr/bin/xfce4-appfinder
ExecutableTimestamp: 1545999336
InstallationDate: Installed on 2011-10-14 (2665 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: xfrun4
ProcCwd: /home/dak
SegvAnalysis:
 Segfault happened at: 0x7fa374a7d76a <g_slice_alloc+506>: mov (%rbx),%rdx
 PC (0x7fa374a7d76a) ok
 source "(%rbx)" (0x0000002c) 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-appfinder
StacktraceTop:
 g_slice_alloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_alloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_with_properties () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: xfce4-appfinder 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
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1814112, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-amd64-retrace
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.