Config: notify_remove makes notifications cause segfaults

Bug #411152 reported by Michal Hruby
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Desktop Agnostic Library for GLib-based Projects
Fix Released
Critical
Mark Lee

Bug Description

Notifications aren't removed properly after call to config_client_notify_remove, and adding notifications for the same keys with different data results in calling the notification multiple times. (hopefully this isn't bug in the python binding)

Please see these pastebins:
http://pastebin.org/7728
http://pastebin.org/7734

Related branches

Mark Lee (malept)
summary: - ConfigClient [gconf]: notifications not removed properly
+ Config: notify_remove makes notifications cause segfaults
Revision history for this message
Mark Lee (malept) wrote :

I've been working on debugging this for at least a week. This affects both the gconf and keyfile implementations (I haven't tested the memory backend yet, although I imagine that it affects that one too). Any help fixing this is appreciated.

Also, for future reference (from the bug reporting guidelines):

> Please do not link to pastebins, as the lifetime of the bug may substantially exceed the lifetime of the
> pastebin entries. Please attach the information as text files to the bug instead.

Changed in libdesktop-agnostic:
assignee: nobody → Mark Lee (malept)
importance: Undecided → Critical
status: New → Triaged
Revision history for this message
Mark Lee (malept) wrote :

I think I fixed this in revision 242 of trunk.

tags: added: config segfault
Changed in libdesktop-agnostic:
milestone: none → 0.3.9
status: Triaged → Fix Committed
Revision history for this message
Michal Hruby (mhr3) wrote :

Indeed it was fixed in 242, and the multi-notification issue in 244.

Mark Lee (malept)
Changed in libdesktop-agnostic:
status: Fix Committed → Fix Released
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.