notification-daemon crashed with signal 5 in g_source_remove()

Bug #1273014 reported by martyfelker
244
This bug affects 70 people
Affects Status Importance Assigned to Milestone
notification-daemon (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Login to LXDE - Ubuntu 14.04

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: notification-daemon 0.7.6-1
Uname: Linux 3.13.0-031300-generic x86_64
ApportVersion: 2.13.1-0ubuntu2
Architecture: amd64
CurrentDesktop: LXDE
Date: Sun Jan 26 20:20:56 2014
ExecutablePath: /usr/lib/notification-daemon/notification-daemon
InstallationDate: Installed on 2014-01-26 (0 days ago)
InstallationMedia: Kubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130822)
ProcCmdline: /usr/lib/notification-daemon/notification-daemon
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: notification-daemon
StacktraceTop:
 g_source_remove () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 g_closure_invoke () 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
Title: notification-daemon crashed with signal 5 in g_source_remove()
UpgradeStatus: Upgraded to trusty on 2014-01-26 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo vboxusers

Revision history for this message
martyfelker (martyfelker-gmail) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_source_remove (tag=21) at /build/buildd/glib2.0-2.39.3/./glib/gmain.c:2211
 queue_update (queue=0x127a150) at nd-queue.c:929
 g_closure_invoke (closure=0x13ce1c0, return_value=0x0, n_param_values=1, param_values=0x7fff2d0fe010, invocation_hint=0x7fff2d0fdfb0) at /build/buildd/glib2.0-2.39.3/./gobject/gclosure.c:777
 signal_emit_unlocked_R (node=node@entry=0x1233d30, detail=detail@entry=0, instance=instance@entry=0x14342c0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff2d0fe010) at /build/buildd/glib2.0-2.39.3/./gobject/gsignal.c:3556
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fff2d0fe198) at /build/buildd/glib2.0-2.39.3/./gobject/gsignal.c:3312

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 notification-daemon (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in notification-daemon (Ubuntu):
status: New → Confirmed
information type: Private → Public
tags: added: utopic
tags: added: bugpattern-needed
Revision history for this message
Davide Capodaglio (davidecapod) wrote :

I have this bug on Lubuntu 14.04 i386; after having read that has been fixed upstream here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747465, I solved by installing the one in vivid (that has 0.7.6-2 that solves the problem), that works flawlessly on trusty. Got it from http://packages.ubuntu.com/vivid/notification-daemon

Revision history for this message
Alex Dehnert (adehnert) wrote :

notification-daemon generally crashes for me ~immediately on both my personal Trusty machines -- any chance of getting this backported?

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.