notification-daemon crashed with signal 5 in g_variant_get_boolean()

Bug #974603 reported by Kamil Rowiński
92
This bug affects 19 people
Affects Status Importance Assigned to Milestone
notification-daemon (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Just happen suddenly while normal workflow.

Description: Ubuntu precise (development branch)
Release: 12.04

Linux ubuntu 3.2.0-22-generic #35-Ubuntu SMP Tue Apr 3 18:33:15 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: notification-daemon 0.7.3-1
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
Date: Thu Apr 5 22:00:53 2012
ExecutablePath: /usr/lib/notification-daemon/notification-daemon
ProcCmdline: /usr/lib/notification-daemon/notification-daemon
Signal: 5
SourcePackage: notification-daemon
Title: notification-daemon crashed with signal 5 in g_variant_get_boolean()
UpgradeStatus: Upgraded to precise on 2012-02-24 (41 days ago)
UserGroups:

mtime.conffile..etc.xdg.autostart.notification.daemon.desktop: 2012-02-24T21:44:04.924355

Revision history for this message
Kamil Rowiński (spajderix) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceTop.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
Revision history for this message
Morlok8k (aoa-supercool) wrote :

Same issue. I just downloaded a file in chromium, when i saw the notification thing flash in the corner, then the error report program came up.

I think the message was going to be the one where it says its uploading the file to Ubuntu One.

Revision history for this message
Morlok8k (aoa-supercool) wrote :

got the bug again, when i got the file sync complete message. i was actually able to read it for a couple of seconds before it crashed though.

I think i might uninstall notifications... i've always hated them anyways.

Revision history for this message
Nick Jenkins (nickpj) wrote :

I'm also getting this in Ubuntu 11.10 (i.e. it's not just 12.04). Started about a week ago. No idea why it happens.

Revision history for this message
James Harkins (biz-dewdrop-world) wrote :

I'm also having the same problem.

This bug report (from Debian) seems to be relevant:

http://us.generation-nt.com/answer/bug-648378-notification-daemon-stops-displaying-pop-ups-after-20-unacknowledged-messages-help-205388441.html

~~
After 20 pop-ups that are not manually closed by clicking on them
notification-daemon stops showing pop-ups and returns the error:
error sender=:1.418 -> dest=:1.484 error_name=org.freedesktop.Notifications.MaxNotificationsExceeded rep string "Exceeded maximum number of notifications"

This error is generated in daemon.c at line 185. I commented out the
entire if statement and notifications started showing as expected.

The items are only removed from the queue when the notification is
manually closed by nd-queue.c::on_notification_close(). I am not sure
what the purpose of limiting the queue was, but the items should also
be dequeued when the pop-ups time out (in
nd-queue.c::on_bubble_destroyed), otherwise the queue will grow
forever, using more and more memory.
~~

If I read this right:

- It's what could be considered a memory leak: objects are put into the notification queue, but not discarded. That's the genius bit: The user has to click on it to clean up the notification queue, but after a few seconds, the user *can't* click on it anymore. Perfect!

- The limit on the queue size is a crude way to prevent memory from leaking indefinitely, but it also means (stupidly) that notifications *stop working altogether* after fewer than two dozen notifications are displayed. (!!!!)

If this analysis is correct, you can prevent the error by clicking on *every notification* before it disappears automatically.

Revision history for this message
christopher (paramore-chris) wrote :

it shows up every time i start my computer it happend right after i installed ubuntu 12.04 LTS about a week ago and has happend since it dont seem to mess with anything altho i have noticed that ubuntu is alot slower than it was when i had it installed before

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.