Package: notify-sharp / 0.4.0~r3032-6

Metadata

Package Version Patches format
notify-sharp 0.4.0~r3032-6 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
01_pkg config path.patch | (download)

notify-sharp.pc.in | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 fix pkg-config paths
02_reverse_cap_check.patch | (download)

src/Notification.cs | 9 3 + 6 - 0 !
1 file changed, 3 insertions(+), 6 deletions(-)

 reverse the patch merged upstream which swallows actions in
             notifications.  It is more appropriate for applications to make
             that decision rather than a library.
03 use dbus sharp.patch | (download)

Makefile.in | 4 2 + 2 - 0 !
configure | 98 49 + 49 - 0 !
configure.ac | 10 5 + 5 - 0 !
docs/Makefile.in | 4 2 + 2 - 0 !
src/Global.cs | 2 1 + 1 - 0 !
src/Makefile.am | 2 1 + 1 - 0 !
src/Makefile.in | 6 3 + 3 - 0 !
src/Notification.cs | 2 1 + 1 - 0 !
8 files changed, 64 insertions(+), 64 deletions(-)

 usage of new dbus-sharp bindings
04 fix app name derivation.patch | (download)

src/Notification.cs | 7 6 + 1 - 0 !
1 file changed, 6 insertions(+), 1 deletion(-)

 use getentryassembly() to derive app_name
Bug-Ubuntu: https://bugs.launchpad.net/bugs/825769
Bug: https://bugzilla.gnome.org/show_bug.cgi?id=656533
05 fix crash when notification updates fail.patch | (download)

src/Notification.cs | 12 9 + 3 - 0 !
1 file changed, 9 insertions(+), 3 deletions(-)

 [patch] fixed application crash in gtk+ callback when notification
 updates fail

For an example how this can crash an application see here:
https://www.smuxi.org/issues/show/809