update-notifier crashed with SIGSEGV in g_object_ref()

[[e-mail]]

closed docky

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: update-notifier 0.120ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-7.7-generic 3.5.0
Uname: Linux 3.5.0-7-generic x86_64
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
Date: Fri Aug 3 15:31:19 2012
ExecutablePath: /usr/bin/update-notifier
ExecutableTimestamp: 1343765516
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120210)
ProcCmdline: update-notifier
ProcCwd: /home/francisco
ProcEnviron:
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f2d60381db1 <g_object_ref+17>: cmpq $0x50,(%rax)
 PC (0x7f2d60381db1) ok
 source "$0x50" ok
 destination "(%rax)" (0x0000008a) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: update-notifier
StacktraceTop:
 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_list_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
Title: update-notifier crashed with SIGSEGV in g_object_ref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 g_object_ref (_object=0x7f2d54015c90) at /build/buildd/glib2.0-2.33.6/./gobject/gobject.c:2883
 g_list_foreach (list=<optimized out>, list@entry=0x237f3a0, func=0x7f2d60381da0 <g_object_ref>, user_data=user_data@entry=0x0) at /build/buildd/glib2.0-2.33.6/./glib/glist.c:942
 get_mounts (volume_monitor=<optimized out>) at gdaemonvolumemonitor.c:59
 get_mounts (volume_monitor=<optimized out>) at /build/buildd/glib2.0-2.33.6/./gio/gunionvolumemonitor.c:119
 update_shadow_mount (volume=0x2382240) at gproxyvolume.c:252

[Launchpad Janitor (janitor)]

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

[Michael Vogt (mvo)]

From one of the dupes:
"""update-notifier is unstable and crashes after unplugging (or maybe even plugging) canon camera."""

[Michael Vogt (mvo)]

Looking at the backtrace it does not look like its a bug in update-notifier itself but in the "gvfs" library its using.

[greee (greee)]

also happen to me at each login on an i386 architecture
(update-notifier 0.126 on a Linux 3.5.0-18-generic)

Segv reason is "writing unknown VMA"

[Kevin John Panzke (kevpan815)]

This Bug Affects me too, however for me this Bug occured on Ubuntu 13.04 Unity Beta Freeze Build (03-28-2013) with all Bug Fixes installed on 03-31-2013 (Easter Sunday), bug occured right after updating 13.04 to Mainline Kernel 3.8.5 and then Rebooting the Computer.