update-notifier crashed with SIGSEGV in gdu_device_is_removable()

Bug #749937 reported by MAKAPOH
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
update-notifier (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: update-notifier

Ubuntu 11.04

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: update-notifier 0.111ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Fri Apr 1 10:28:57 2011
ExecutablePath: /usr/bin/update-notifier
InstallationMedia: Xubuntu 10.10 "Maverick Meerkat" - Release i386 (20101008.1)
ProcCmdline: update-notifier
ProcEnviron:
 LANGUAGE=ru_RU:en
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x29b5e7 <gdu_device_is_removable+7>: mov 0xc(%eax),%eax
 PC (0x0029b5e7) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: update-notifier
StacktraceTop:
 gdu_device_is_removable () from /usr/lib/libgdu.so.0
 g_cclosure_marshal_VOID__OBJECT () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: update-notifier crashed with SIGSEGV in gdu_device_is_removable()
UpgradeStatus: Upgraded to natty on 2011-03-25 (9 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
MAKAPOH (makapoh) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gdu_device_is_removable (device=0x0) at gdu-device.c:949
 up_check_mount_point_for_packages (mount_point=0x9a10508 "\030\215\241\t\032", data=0x9a521a0) at gdu.c:185
 g_cclosure_marshal_VOID__OBJECT (closure=0x9a32dd8, return_value=0x0, n_param_values=2, param_values=0x9a650c8, invocation_hint=0xbf80a170, marshal_data=0x0) at /build/buildd/glib2.0-2.28.4/./gobject/gmarshal.c:638
 g_closure_invoke (closure=0x9a32dd8, return_value=0x0, n_param_values=2, param_values=0x9a650c8, invocation_hint=0xbf80a170) at /build/buildd/glib2.0-2.28.4/./gobject/gclosure.c:767
 signal_emit_unlocked_R (node=0x9a14f60, detail=0, instance=0x9a10508, emission_return=0x0, instance_and_params=0x9a650c8) at /build/buildd/glib2.0-2.28.4/./gobject/gsignal.c:3252

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in update-notifier (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in update-notifier (Ubuntu):
status: New → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This crash occurred in update-notifier's monitoring of disks for a disc that contains Ubuntu packages. Beginning with Ubuntu 13.10 this code has been replaced with an upstart user session job and subsequently this crash can no long occur. Therefore this bug is being marked as invalid.

Changed in update-notifier (Ubuntu):
status: Confirmed → Invalid
importance: Medium → Low
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.