update-notifier crashed with SIGSEGV in g_object_ref()

Bug #1032925 reported by gogo
640
This bug affects 144 people
Affects Status Importance Assigned to Milestone
update-notifier (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

update-notifier crashed with SIGSEGV in g_object_ref()

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: Sat Aug 4 07:19:23 2012
ExecutablePath: /usr/bin/update-notifier
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
ProcCmdline: update-notifier
ProcEnviron:
 PATH=(custom, no user)
 LANG=hr_HR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fe4c9651db1 <g_object_ref+17>: cmpq $0x50,(%rax)
 PC (0x7fe4c9651db1) ok
 source "$0x50" ok
 destination "(%rax)" (0x00000001) 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_cclosure_marshal_VOID__OBJECTv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () 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
 g_signal_emit_by_name () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
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

Revision history for this message
gogo (trebelnik-stefina) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_object_ref (_object=_object@entry=0x25c2ae0) at /build/buildd/glib2.0-2.33.6/./gobject/gobject.c:2883
 g_cclosure_marshal_VOID__OBJECTv (closure=0x25cc100, return_value=<optimized out>, instance=0x25b0230, args=<optimized out>, marshal_data=0x0, n_params=<optimized out>, param_types=0x25a68d0) at /build/buildd/glib2.0-2.33.6/./gobject/gmarshal.c:1297
 _g_closure_invoke_va (closure=0x25cc100, return_value=0x0, instance=0x25b0230, args=0x7fffff8f1778, n_params=1, param_types=0x25a68d0) at /build/buildd/glib2.0-2.33.6/./gobject/gclosure.c:840
 g_signal_emit_valist (instance=instance@entry=0x25b0230, signal_id=signal_id@entry=209, detail=detail@entry=0, var_args=var_args@entry=0x7fffff8f1778) at /build/buildd/glib2.0-2.33.6/./gobject/gsignal.c:3211
 g_signal_emit_by_name (instance=0x25b0230, detailed_signal=0x7fe4bb1e3f31 "mount-added") at /build/buildd/glib2.0-2.33.6/./gobject/gsignal.c:3393

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
tags: removed: need-amd64-retrace
gogo (trebelnik-stefina)
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
Christopher (soft-kristal) wrote :

Happened on reboot after upgrade to 3.5.0-11.

Revision history for this message
Sebastian Bugiu (sebastian-bugiu) wrote :

On reboot after upgrade to 3.5.0-11 also

Revision history for this message
Colin Keenan (colinkeenan) wrote :

Happened after ctrl-alt-backspace because Compiz locked up using 100% CPU.

I was reading a blog using Google Chrome and suddenly I couldn't scroll anymore and Chrome wasn't responding at all, so I did ctrl-alt-F1 and killall chrome. That worked without error, but ctrl-alt-f7 showed nothing changed on my desktop - it still showed Chrome stuck at the same place. So, I did ctrl-alt-f1 and ran top. Sure enough, chrome was not running anymore, but compiz was using 100% cpu. I tried a few other commands to stop and start Compiz and Unity, but didn't really know what I was doing, so ended up doing ctrl-alt-f7 then ctrl-alt-backspace. After logging back in, I got this and other errors.

Revision history for this message
jerrylamos (jerrylamos) wrote :

Beta 1 Quantal. Had just closed Firefox and saw the Apport window.

Note, I don't even use Update. It's turned off in Software Sources as much as I can. I do update/dist-upgrade daily when I want to and don't need Update crashing in to whatever I'm doing. Yes, the "general public" after release should have update running.

Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

Happened to me after logging out and in again, up-to-date quantal amd64

Revision history for this message
Christopher (soft-kristal) wrote :

Bug reported after upgrade to 3.5.0-16.

Revision history for this message
Wajih Letaief (mawale) wrote :

Happened after logging on an up-to-date quantal 32 bits when i launched an update from the CLI (sudo apt-get update && sudo apt-get upgrade)

Revision history for this message
Atilio Quintero (atilioquintero) wrote :

Happened when i loggin after poweron

Revision history for this message
muntasir (13badhan) wrote :

happended just after a reboot

Revision history for this message
Michael Vogt (mvo) wrote :

This is #22 on errors.ubuntu.com as of today. I don't see update-notifier code in the backtrace, just library code so this might be a bug in one of the libs. Or its some sort of memory corruption triggering a crash. Bug #1032953 looks a little bit similar.

Revision history for this message
Michael Vogt (mvo) wrote :

Hm, the backtrace show that there is a "mount-added" signal
...
#4 0x00007fe4c9667710 in g_signal_emit_by_name (instance=0x25b0230, detailed_signal=0x7fe4bb1e3f31 "mount-added") at /build/buildd/glib2.0-2.33.6/./gobject/gsignal.c:3393
        var_args = {{gp_offset = 16, fp_offset = 48, overflow_arg_area = 0x7fffff8f18b0, reg_save_area = 0x7fffff8f17c0}}
        detail = 0
        signal_id = 209
        __PRETTY_FUNCTION__ = "g_signal_emit_by_name"
...

this indicates there might be a link to Bug #1032953 as this looks releated to gvfs and keeping track of the mounts.

Revision history for this message
Michael Vogt (mvo) wrote :

Releated to the "mount-added" call, update-notifier is using a:
    monitor = g_volume_monitor_get();
and connects the mount-added,mount-changed signals to it. Its using it for the entire duration of the daemon
running, so if upgrading gvfs make the monitor somehow invalid that might explain the crash. Another potential
source might be that some plugin is loaded by gvfs after the plugins got upgraded. Not sure if that matters though.

tags: added: raring
Revision history for this message
Brian Murray (brian-murray) wrote :

update-notifier no longer monitors volumes, but rather uses and upstart user job to detect if a CD has been inserted, subsequently I am setting this to Won't Fix.

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

Additionally, looking at the errors bucket for this bug we can see that it does not affect Ubuntu 13.10.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers