gnome-clocks crashed with GError in function(): GDBus.Error:org.freedesktop.Notifications.MaxNotificationsExceeded: Exceeded maximum number of notifications

Bug #1063371 reported by hexa-
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-clocks (Ubuntu)
New
Medium
Unassigned

Bug Description

Timer was going to 0:00:00 when crash report came up. Application didn't appear to be crashed however.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-clocks 0.1.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
Date: Sun Oct 7 20:22:31 2012
ExecutablePath: /usr/bin/gnome-clocks
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gnome-clocks
PythonArgs: ['/usr/bin/gnome-clocks']
SourcePackage: gnome-clocks
Title: gnome-clocks crashed with GError in function(): GDBus.Error:org.freedesktop.Notifications.MaxNotificationsExceeded: Exceeded maximum number of notifications
UpgradeStatus: Upgraded to quantal on 2012-09-25 (12 days ago)
UserGroups: adm admin audio cdrom debian-tor dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
hexa- (mweinelt-deactivatedaccount) wrote :
tags: removed: need-duplicate-check
Changed in gnome-clocks (Ubuntu):
importance: Undecided → Medium
Jeremy Bícha (jbicha)
information type: Private → Public
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.