update-notifier crashed with SIGSEGV in signal_emit_unlocked_R()

Bug #1244944 reported by Hugo Loyola
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-notifier (Ubuntu)
Expired
Medium
Unassigned

Bug Description

no

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: update-notifier 0.119ubuntu8.6
ProcVersionSignature: Ubuntu 3.5.0-42.65~precise1-generic 3.5.7.21
Uname: Linux 3.5.0-42-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
Date: Fri Oct 25 15:01:13 2013
Disassembly: => 0x81564b98: No se puede acceder a la memoria en la dirección 0x81564b98
ExecutablePath: /usr/bin/update-notifier
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213)
MarkForUpload: True
ProcCmdline: update-notifier
ProcEnviron:
 LANGUAGE=es_CL:es
 PATH=(custom, no user)
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x81564b98: No se puede acceder a la memoria en la dirección 0x81564b98
 PC (0x81564b98) not located in a known VMA region (needed executable region)!
 source "0x81564b98" (0x81564b98) not located in a known VMA region (needed readable region)!
SegvReason:
 executing unknown VMA
 reading unknown VMA
Signal: 11
SourcePackage: update-notifier
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: update-notifier crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: Upgraded to precise on 2013-06-06 (141 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Hugo Loyola (hugoe-loyolat) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 signal_emit_unlocked_R (node=<optimized out>, detail=789, instance=<optimized out>, emission_return=0x0, instance_and_params=0x7fff5c1988d0) at /build/buildd/glib2.0-2.32.4/./gobject/gsignal.c:3685
 g_signal_emit_valist (instance=<error reading variable: Cannot access memory at address 0x2fffffe4d>, signal_id=<optimized out>, detail=<error reading variable: Cannot access memory at address 0x2fffffe41>, var_args=<optimized out>) at /build/buildd/glib2.0-2.32.4/./gobject/gsignal.c:3330

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in update-notifier (Ubuntu):
importance: Undecided → Medium
summary: - update-notifier crashed with SIGSEGV in g_signal_emit_valist()
+ update-notifier crashed with SIGSEGV in signal_emit_unlocked_R()
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Paul White (paulw2u) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time.

Changed in update-notifier (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for update-notifier (Ubuntu) because there has been no activity for 60 days.]

Changed in update-notifier (Ubuntu):
status: Incomplete → Expired
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.