| Age | Commit message (Collapse) | Author | Files | Lines |
|
Add new UI elements to configure default timeout, allow persistent
notifications, and to display countdown on all notification messages.
|
|
Countdown was only visible for notifications that had action buttons.
This change adds a 'show-countdown' gsetting to display it instead on
all non-persisntent notifications.
|
|
Add persistence support with resident/transient hints, fix icon
precedence order (according to spec), and implement desktop-entry icons.
Also added new 'default-timeout' and 'enable-persistence' gsettings to
allow users to control timeout and persistence behavior.
Spec is on https://specifications.freedesktop.org/notification-spec/1.3/
Fixes https://github.com/mate-desktop/mate-notification-daemon/issues/132
Fixes https://github.com/mate-desktop/mate-notification-daemon/issues/137
Fixes https://github.com/mate-desktop/mate-notification-daemon/issues/138
Fixes https://github.com/mate-desktop/mate-notification-daemon/issues/149
|
|
Returning an error for a dbus method is counted as handling a method invocation. Return true in the handler to avoid a use-after-free.
|
|
|
|
Allow to set coutdown color from .countdown:selected for all themes
Fix the countdown for slider theme and draw transparent background for countdown
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
remove exit / replace with gtk_main_quit
[ 7590.265881] mate-notificati[76519]: segfault at 55ac5111c67a ip 00007d1d4fc09d61 sp 00007ffd0bf06698 error 4 in libgobject-2.0.so.0.8000.0[7d1d4fbdc000+37000] likely on CPU 0 (core 0, socket 0)
[ 7590.265910] Code: 01 00 00 00 4c 89 ce 48 89 e5 e8 da e6 ff ff 5d 85 c0 0f 95 c0 0f b6 c0 c3 f3 0f 1e fa 48 85 ff 74 47 48 8b 07 48 85 c0 74 3f <48> 8b 00 48 3d fc 03 00 00 77 2c 48 8d 15 cd 53 02 00 48 c1 e8 02
|
|
|
|
|
|
We had weird errors about the URI gem not being at the right version:
> You have already activated uri 0.13.1, but your Gemfile requires uri
> 0.13.0. Since uri is a default gem, you can either remove your
> dependency on it or try updating to a newer version of bundler that
> supports uri as a default gem. (Gem::LoadError)
This is supposed to fix it for now.
https://travis-ci.community/t/deployments-are-failing-due-to-uri-dependency/14375/4
|
|
Fixes #218.
|
|
|
|
|
|
|
|
|
|
|
|
When loaded as in-process applet, we must not call `textdomain()` or we
will override mate-panel's text domain. Instead, properly use
gi18n-lib.h header that provides the same API but uses the compile-time
`GETTEXT_PACKAGE` value for each call.
Actually drop the whole i18n setup logic that is provided already by
mate-panel's factory macros.
Fixes #219.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Relying on D-Bus activation to launch org.freedesktop.Notifications can
result in selecting the wrong implementation if multiple daemons are
installed.
Fix this by launching m-n-d with the session rather than depending on
D-Bus activation. We keep D-Bus activation for the moment for backward
compatibility and to re-start the daemon in otherwise non-problematic
situations if it crashes.
Fixes #133 and #174.
|
|
This allows to run as a regular session service that does not exit, but
also as a well-behaved D-Bus-activated service. Make the default
behavior not to exit, but when activated through D-Bus.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Snap packages are unable to trigger the notification daemon in a fully
confined package, because the snapd apparmor rules state that the target
of the dbus call must specify that it is labelled `unconfined`. See
https://forum.snapcraft.io/t/snapd-doesnt-allow-notification-daemon-to-be-activatable/22912/1
for the details.
Signed-off-by: Dani Llewellyn <[email protected]>
|