telepathy-idle crashed with SIGSEGV in tp_handle_inspect()

Bug #1815963 reported by El jinete sin cabeza
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-idle (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Open Polari and full load CPU.

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: telepathy-idle 0.2.0-2build1
Uname: Linux 4.20.8-042008-generic x86_64
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 14 18:33:11 2019
ExecutablePath: /usr/lib/telepathy/telepathy-idle
InstallationDate: Installed on 2018-12-02 (74 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcCmdline: /usr/lib/telepathy/telepathy-idle
SegvAnalysis:
 Segfault happened at: 0x7f4f7769d5e0 <tp_handle_inspect+16>: mov (%rbx),%rdi
 PC (0x7f4f7769d5e0) ok
 source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-idle
StacktraceTop:
 tp_handle_inspect () from /usr/lib/x86_64-linux-gnu/libtelepathy-glib.so.0
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: telepathy-idle crashed with SIGSEGV in tp_handle_inspect()
UpgradeStatus: Upgraded to disco on 2018-12-02 (74 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
El jinete sin cabeza (ejsc-deactivatedaccount) wrote :
description: updated
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 telepathy-idle (Ubuntu):
status: New → Invalid
tags: removed: need-amd64-retrace
information type: Private → Public
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.