xfce4-notifyd crashed with SIGSEGV in malloc_consolidate()

Bug #1751110 reported by bruno
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xfce4-notifyd (Ubuntu)
New
Undecided
Unassigned

Bug Description

the notifications software is constantly "stopping unexpectedly"

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: xfce4-notifyd 0.4.1-1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CrashCounter: 1
Date: Thu Feb 22 15:17:38 2018
ExecutablePath: /usr/lib/x86_64-linux-gnu/xfce4/notifyd/xfce4-notifyd
ProcCmdline: /usr/lib/x86_64-linux-gnu/xfce4/notifyd/xfce4-notifyd
ProcEnviron:
 LANG=pt_BR.UTF-8
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f33da81d108 <malloc_consolidate+312>: mov 0x8(%rbx),%rax
 PC (0x7f33da81d108) ok
 source "0x8(%rbx)" (0x00000009) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xfce4-notifyd
StacktraceTop:
 malloc_consolidate (av=av@entry=0x7f33dab6ec20 <main_arena>) at malloc.c:4490
 _int_malloc (av=av@entry=0x7f33dab6ec20 <main_arena>, bytes=bytes@entry=1120) at malloc.c:3706
 __libc_calloc (n=<optimized out>, elem_size=<optimized out>) at malloc.c:3439
 g_malloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_type_class_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: xfce4-notifyd crashed with SIGSEGV in malloc_consolidate()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

Revision history for this message
bruno (brunophelipe) wrote :
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 #1733293, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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