update-notifier crashed with SIGSEGV

Bug #347153 reported by CafeNinja
202
This bug affects 14 people
Affects Status Importance Assigned to Milestone
update-notifier (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: update-notifier

I'm not sure which fault this was. There are many SIGSEGV crashes reported. Once I've looked at the information collected by the bug reporter, then I'll relate/update the correct bug report.

CafeNinja

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/update-notifier
Package: update-notifier 0.76.6
ProcCmdline: update-notifier --startup-delay=60
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: update-notifier
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
Title: update-notifier crashed with SIGSEGV
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video

Revision history for this message
CafeNinja (cafeninja) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:hook_file_mark_as_seen (priv=0x9ed51f8, hf=0xa1c6348)
show_hooks (ta=0x9ed4768, focus_on_map=0) at hooks.c:446
check_update_hooks (ta=0x9ed4768) at hooks.c:680
file_monitor_periodic_check (data=0x9eff580)
g_timeout_dispatch (source=0x9f0abd8, callback=0x1,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in update-notifier:
importance: Undecided → Medium
Revision history for this message
CafeNinja (cafeninja) wrote :

I couldn't find more information about the error. Logs provided were from the crash report utility.

--
CafeNinaj

Revision history for this message
CafeNinja (cafeninja) wrote :

I've conduced apt-get update + upgrade. After reboot, this same crash report occurred again. I didn't see any difference in the content of the apport information and did not open a new bug. I just wanted to say that after the upgrade I just ran 76 packages, there was no change in this crash.

CafeNinja

Revision history for this message
CafeNinja (cafeninja) wrote :

I launched from cli. Seemed to complain that update-notifier was running, so I killed the process and launched it again via cli. No crash, notifications seemed to work. I've seen in jaunty that notification area applications sometimes launch twice. That is to say that I have frequently 2 pidgin instances upon login. Could these crashes/errors be from the udpate-notifier already running?

--
CafeNinja

visibility: private → public
Revision history for this message
Monkey (monkey-libre) wrote :

The bug need more information

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.