update-notifier crashed with SIGSEGV

Bug #1164769 reported by Ricardo Luiz on 2013-04-04
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-notifier (Ubuntu)
Undecided
Unassigned

Bug Description

the compiz package wrong process

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: update-notifier 0.132 [modified: usr/bin/update-notifier]
Uname: Linux 3.8.4-030804-generic i686
ApportVersion: 2.9.2-0ubuntu5
Architecture: i386
Date: Tue Apr 2 22:37:11 2013
Disassembly: => 0x4926b418: Não é possível acessar a memória no endereço 0x4926b418
ExecutablePath: /usr/bin/update-notifier
MarkForUpload: True
ProcCmdline: update-notifier
SegvAnalysis:
 Segfault happened at: 0x4926b418: Não é possível acessar a memória no endereço 0x4926b418
 PC (0x4926b418) ok
 source "0x4926b418" (0x4926b418) ok
 SP (0xbfe7efc0) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: update-notifier
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
ThreadStacktrace:
 .
 Thread 4 (LWP 2449):
 #0 0xb77de424 in ?? ()
 No symbol table info available.
 Não é possível acessar a memória no endereço 0x7
Title: update-notifier crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Ricardo Luiz (rluiz) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
ThreadStacktrace:
 .
 Thread 4 (LWP 2449):
 #0 0xb77de424 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7

tags: added: apport-failed-retrace
tags: removed: need-i386-retrace

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers