Bug #574
Smuxi crashes with "0 is not a valid notification ID"
Status: | Closed | Start: | 03/07/2011 | |
Priority: | Urgent | Due date: | ||
Assigned to: | Mirco Bauer | % Done: | 100% |
|
Category: | Frontend GNOME | |||
Target version: | 0.8.9 | |||
Complexity: | Found in Version: | |||
Votes: | 0 |
Description
When a notification is shown because of a highlight and you switch to that tab then Smuxi sometimes crashes with:
Exception Type: System.Exception Exception Message: org.freedesktop.DBus.GLib.UnmappedError.NotificationDaemonErrorQuark.Code100: 0 is not a valid notification ID Exception StackTrace: at Notifications.INotificationsProxy.CloseNotification (UInt32 id) [0x00000] in <filename unknown>:0 at Notifications.Notification.Close () [0x00000] in <filename unknown>:0 at Smuxi.Frontend.Gnome.NotifyManager.DisposeNotification (Smuxi.Frontend.Gnome.ChatView chatView) [0x00000] in <filename unknown>:0 at Smuxi.Frontend.Gnome.NotifyManager.OnMainWindowNotebookSwitchPage (System.Object sender, Gtk.SwitchPageArgs e) [0x00000] in <filename unknown>:0 at (wrapper delegate-invoke) Gtk.SwitchPageHandler:invoke_void__this___object_SwitchPageArgs (object,Gtk.SwitchPageArgs) at Gtk.Notebook.SwitchPageSignalCallback (IntPtr arg0, IntPtr arg1, UInt32 arg2, IntPtr gch) [0x00000] in <filename unknown>:0
Associated revisions
Revision b1cdb1518f00a69478aa8127e3e2f99361bc63ae
[Frontend-GNOME] Don't rely on the Closed signal of notifications. (closes: #574)
The Closed signal might not be raised and would leave old notifications behind
which we will try to re-close leading to an exception.
Revision 36598e7cd46b96a9a194fb78ed05b93206d776aa
[Frontend-GNOME] Don't try to close already expired notifications (references: #574)
The notification daemon will return an error response if we try to close
a notification that expired and was already closed.
History
Updated by Mirco Bauer 4985 days ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset b1cdb1518f00a69478aa8127e3e2f99361bc63ae.
Updated by Mirco Bauer 4979 days ago
This issue can be temporarily workarounded by disabling notifications in the preferences.