signon-ui crashed with SIGSEGV in QObjectPrivate::deleteChildren()

Bug #1158151 reported by Olnei Araujo
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
signon-ui (Ubuntu)
New
Undecided
Unassigned

Bug Description

signon-ui crashed with SIGSEGV in QObjectPrivate::deleteChildren()

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: signon-ui 0.13bzr13.03.19-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-10.19-generic 3.8.2
Uname: Linux 3.8.0-10-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.9.2-0ubuntu2
Architecture: amd64
Date: Wed Mar 20 22:55:05 2013
Disassembly: => 0x0: Não é possível acessar a memória no endereço 0x0
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/signon-ui
InstallationDate: Installed on 2013-03-03 (17 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130303)
MarkForUpload: True
ProcCmdline: /usr/bin/signon-ui
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=pt_BR:
 LANG=pt_BR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x0: Não é possível acessar a memória no endereço 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
 source "0x0" (0x00000000) not located in a known VMA region (needed readable region)!
SegvReason:
 executing NULL VMA
 reading NULL VMA
Signal: 11
SourcePackage: signon-ui
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 QObjectPrivate::deleteChildren() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
Title: signon-ui crashed with SIGSEGV in QObjectPrivate::deleteChildren()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

Revision history for this message
Olnei Araujo (olneiaa) 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 #1157363, 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.

Other bug subscribers

Remote bug watches

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