Public bug reported:

On every reboot, I get this message ("update-notifier crashed") after login 
into the unity session.
I don't see any other symptoms.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: update-notifier 0.134
ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
Uname: Linux 3.8.0-23-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
CrashCounter: 1
Date: Mon Jun 10 11:48:59 2013
Disassembly: => 0x7fce506521b1: Cannot access memory at address 0x7fce506521b1
ExecutablePath: /usr/bin/update-notifier
InstallationDate: Installed on 2013-02-26 (105 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: update-notifier
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x7fce506521b1:  Cannot access memory at address 
0x7fce506521b1
 PC (0x7fce506521b1) ok
 SP (0x7fff4ec45930) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: update-notifier
Stacktrace:
 #0  0x00007fce506521b1 in ?? ()
 No symbol table info available.
 #1  0x0000000000000000 in ?? ()
 No symbol table info available.
StacktraceTop:
 ?? ()
 ?? ()
Title: update-notifier crashed with SIGSEGV
UpgradeStatus: Upgraded to raring on 2013-04-19 (52 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo

** Affects: update-notifier (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-crash need-amd64-retrace raring

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1189777

Title:
  update-notifier crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1189777/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to