mate-desktop / mate-notification-daemon Goto Github PK

Quite a shot-in-the-dark, so excuse me if this is the wrong place to report this.

While testing mate-GTK3 it seems that the sound- and battery indicators never follow the theme.

Other theme:

Thanks!

Occurred in fedora 22. Forwarded from https://bugzilla.redhat.com/show_bug.cgi?id=1224782

Description of problem:
Played a song in rhythmbox

Version-Release number of selected component:
mate-notification-daemon-1.10.0-1.fc22

Additional info:
reporter: libreport-2.5.1
backtrace_rating: 4
cmdline: /usr/libexec/mate-notification-daemon
crash_function: _g_log_abort
executable: /usr/libexec/mate-notification-daemon
global_pid: 26578
kernel: 4.0.4-301.fc22.x86_64
runlevel: N 5
type: CCpp
uid: 1000
var_log_messages: [System Logs]:\n-- Logs begin at Mon 2015-05-18 08:44:34 BST, end at Mon 2015-05-25 18:18:06 BST. --

Truncated backtrace:

Thread no. 1 (10 frames)
 #0 _g_log_abort at gmessages.c:315
 #3 g_return_if_fail_warning at gmessages.c:1088
 #4 gtk_widget_get_realized at gtkwidget.c:6076
 #5 gtk_widget_dispose at gtkwidget.c:8797
 #7 gtk_box_forall at gtkbox.c:1251
 #8 notify_daemon_notify_handler at daemon.c:1365
 #9 dbus_glib_marshal_notification_daemon_VOID__STRING_UINT_STRING_STRING_STRING_BOXED_BOXED_INT_POINTER at notificationdaemon-dbus-glue.h:102
 #10 invoke_object_method at dbus-gobject.c:1906
 #11 object_registration_message at dbus-gobject.c:2168
 #12 _dbus_object_tree_dispatch_and_unlock at dbus-object-tree.c:1018```

After update mate-notification-daemon gived up, showing "glib.GError: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)".
I need it for Guake Terminal, I tried "mate-notification-proporties" and after clicking "Preview" shows up a window with error: "Błąd podczas wyświetlania powiadomienia: Message did not receive a reply (timeout by message bus)" (Polish text means "Error during showing notification".
OS: Arch Linux x86_64 (Linux tws 3.2.9-1-ARCH #1 SMP PREEMPT Thu Mar 1 09:31:13 CET 2012 x86_64 Intel(R) Core(TM)2 Duo CPU T5750 @ 2.00GHz GenuineIntel GNU/Linux)

Slider theme does not draw the correct bg color from gtk theme.
Means, if you change the gtk theme than the bg in notification theme should change too.
Currently the bg color is black, but with normal fg color (black) from most themes you can't read nothing.
The culprit is 0fb782d
Reverting this commit with git rebase works cleanly and fixes the issue.
I want to revert this commit for 1.12 because slider is the only theme which works correctly with gtk3.
We can fix the deprecated commit later, after 1.12 release.
@GiedriusS
@monsta
@flexiondotorg
@clefebvre
What do you think about and can you give me a GO ?

Hi,
I'm using the official debian packages.

mate-notification-daemon not autostart, and when send a notification with notify-send 'Testing' this command (And some programs that use theme in background) became blocked trying to send it.

In another terminal see dbus messages:

alumno@huayra:~$ dbus-monitor 
signal sender=org.freedesktop.DBus -> dest=:1.67 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
   string ":1.67"
method call sender=:1.67 -> dest=org.freedesktop.DBus serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
   string "eavesdrop=true"
signal sender=org.freedesktop.DBus -> dest=(null destination) serial=50 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.68"
   string ""
   string ":1.68"
method call sender=:1.68 -> dest=org.freedesktop.DBus serial=1 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=Hello
method call sender=:1.68 -> dest=org.freedesktop.DBus serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
   string "type='signal',sender='org.freedesktop.Notifications',interface='org.freedesktop.Notifications',path='/org/freedesktop/Notifications'"
method call sender=:1.68 -> dest=org.freedesktop.DBus serial=3 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
   string "type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',path='/org/freedesktop/DBus',arg0='org.freedesktop.Notifications'"
method call sender=:1.68 -> dest=org.freedesktop.DBus serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=StartServiceByName
   string "org.freedesktop.Notifications"
   uint32 0

After some time. . .

signal sender=org.freedesktop.DBus -> dest=(null destination) serial=51 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.68"
   string ":1.68"
   string ""
signal sender=org.freedesktop.DBus -> dest=(null destination) serial=52 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.69"
   string ""
   string ":1.69"
method call sender=:1.69 -> dest=org.freedesktop.DBus serial=1 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=Hello
method call sender=:1.69 -> dest=org.freedesktop.DBus serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
   string "type='signal',sender='org.freedesktop.Notifications',interface='org.freedesktop.Notifications',path='/org/freedesktop/Notifications'"
method call sender=:1.69 -> dest=org.freedesktop.DBus serial=3 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
   string "type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',path='/org/freedesktop/DBus',arg0='org.freedesktop.Notifications'"
method call sender=:1.69 -> dest=org.freedesktop.DBus serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=StartServiceByName
   string "org.freedesktop.Notifications"
   uint32 0
signal sender=org.freedesktop.DBus -> dest=(null destination) serial=53 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.69"
   string ":1.69"
   string ""

..and thre there notify-send is closed and return to shell..

I noticed in #97 that there is a feature to set the time out length along with a request in #37 to create a way to store notifications. Is there a way to implement setting this through the gui in the mate-notification-properties application? Perhaps being able to set it to a very high value(like one hour or so) would solve both issues?

incorrect-fsf-address in COPYING

Coco theme does not have round borders without compositor.

Per the downstream bug report at https://bugzilla.redhat.com/show_bug.cgi?id=1142441 I'm seeing a repeated segfault in notify_stack_set_location().

Full backtrace can be found in https://bugzilla.redhat.com/attachment.cgi?id=938192

When ever I get a notification from the daemon it causes the computer to slow way down and when I check the processes I see that the is using 100% of the cpu. The computer will return to normal after a sigterm the process. Most of my notifications come from Opera browser I don't know if there is a related compatibility issue. Screenshot -> https://www.dropbox.com/s/rwpa95enw9syegy/mate-notification-daemon-crash.png?raw=1

Did you help close this issue? Go claim the $65 bounty on Bountysource.

It is black or transparent. Screen:

From https://bugs.debian.org/792577

Dear Upstream,

"I'd suggest to add a functionality to the notification bar - similar to what other DEs such as Xfce and KDE have - so that one can review previous notifications until the user deletes those himself.

The reason for this request is simply that I'm using LinConnect to mirror my Android's notifications i.E. missed calls and SMS to my desktop but whenever I might receive important, it often still gets pass me because MATE by default won't save any notifications.

Possibly this behavior can be changed separtely via a settings window so users can decide what they want to keep and what not. " - Marcos Schnalke

You could implement it here or you could implement it in mate-tweak. This is another user who wants to have the same functionality, if it's feasible.

When I start notification-daemon in an i3wm on archlinux and try to send a notification via notifiy-send mate-notification-daemon crashes with the following message in terminal:

(mate-notification-daemon:20501): Wnck-CRITICAL **: wnck_window_is_on_workspace: assertion 'WNCK_IS_WORKSPACE (workspace)' failed
[1]    20501 trace trap (core dumped)  /usr/lib/mate-notification-daemon/mate-notification-daemon

orginal at fedora bugzilla.
https://bugzilla.redhat.com/show_bug.cgi?id=890728

rooksy 2012-12-29 03:43:10 EST

Version-Release number of selected component:
mate-notification-daemon-1.5.0-1.fc18

Additional info:
backtrace_rating: 4
cmdline: /usr/libexec/mate-notification-daemon
crash_function: _cairo_arc_in_direction
executable: /usr/libexec/mate-notification-daemon
kernel: 3.6.11-3.fc18.x86_64
uid: 1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #4 _cairo_arc_in_direction at cairo-arc.c:189
 #5 _cairo_default_context_arc at cairo-default-context.c:778
 #6 cairo_arc_negative at cairo.c:1684
 #7 draw_pie at nodoka-theme.c:485
 #8 countdown_expose_cb at nodoka-theme.c:595
 #9 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86
 #14 gtk_widget_event_internal at gtkwidget.c:5017
 #15 gtk_widget_send_expose at gtkwidget.c:4846
 #16 gtk_main_do_event at gtkmain.c:1610
 #17 _gdk_window_process_updates_recurse at gdkwindow.c:5429

backtrace:
https://bugzilla.redhat.com/attachment.cgi?id=670042
core_backtrace:
https://bugzilla.redhat.com/attachment.cgi?id=670044

Basil Mohamed Gohar 2013-04-08 23:57:28 EDT

I am still getting this error when I attempt to connect to my bluetooth headset. The connection works, but this error still occurs.

Sam Tygier 2013-04-20 16:07:06 EDT

recieving a call in ekiga

backtrace_rating: 4
cmdline: /usr/libexec/mate-notification-daemon
crash_function: _cairo_arc_in_direction
executable: /usr/libexec/mate-notification-daemon
kernel: 3.8.7-201.fc18.x86_64
package: mate-notification-daemon-1.5.1-1.fc18
reason: Process /usr/libexec/mate-notification-daemon was killed by signal 6 (SIGABRT)
uid: 1000
ureports_counter: 1
xsession_errors:

glad08 2013-07-22 12:51:36 EDT

Crash happens during kde-specific bug report master try to report another crash report (for kdevelop crash)

reporter: libreport-2.1.5
backtrace_rating: 4
cmdline: /usr/libexec/mate-notification-daemon
crash_function: _cairo_arc_in_direction
executable: /usr/libexec/mate-notification-daemon
kernel: 3.9.10-200.fc18.x86_64
package: mate-notification-daemon-1.6.0-2.fc18
reason: Process /usr/libexec/mate-notification-daemon was killed by signal 6 (SIGABRT)
runlevel: N 5
uid: 1000
xsession_errors:

Bob Bitton 2013-08-06 17:26:45 EDT

Rebooted my system and it showed up

reporter: libreport-2.1.5
backtrace_rating: 4
cmdline: /usr/libexec/mate-notification-daemon
core_backtrace:
crash_function: _cairo_arc_in_direction
executable: /usr/libexec/mate-notification-daemon
kernel: 3.9.11-200.fc18.i686
package: mate-notification-daemon-1.6.0-2.fc18
reason: Process /usr/libexec/mate-notification-daemon was killed by signal 6 (SIGABRT)
runlevel: N 5
uid: 1000
xsession_errors:

The Coco theme text area has more padding on the top than the bottom, making the notifications look goofy. This is most noticeable with a simple notification like that produced with the following command:
notify-send 'Test';

I believe the issue is line 447 of /src/themes/coco/coco-theme.c:
gtk_widget_set_margin_start (vbox, 8);

The above is setting a top margin without a corresponding bottom margin (unlike the matching lines 428 and 429). I believe the solution is to add a call to gtk_widget_set_margin_end. Further, as I've also noticed that the top margin is a few pixels more than the side margins, it seems like the current margin should be split between the top and bottom. So line 447 would be replaced with:

gtk_widget_set_margin_start (vbox, 4);
gtk_widget_set_margin_end (vbox, 4);

Also, when an icon is included, the spacing to the left of the content (the content consisting of the combination of image and text) is less than the spacing to the right. I believe line 93 is the culprit:
#define IMAGE_PADDING 10

The above is from:
notify-send --icon=gucharmap 'Test' '________________________________________________________';

I think line 93 needs to be changed to:
#define IMAGE_PADDING 15

origin downstream report:
https://bugzilla.redhat.com/show_bug.cgi?id=1233293
fedora 22 with glib2-2.44.1-1.1.fc22.x86_64

 Stuart D Gathman 2015-06-18 11:37:01 EDT

Description of problem:
Logs errors with every notification

Version-Release number of selected component (if applicable):
mate-notification-daemon-1.10.0-1.fc22.i686

How reproducible:
always

Steps to Reproduce:
1. use MATE desktop 
2. use journalctl -f to watch errors when notifications happen
3.

Actual results:
errors in log

Expected results:
no errors in log

I can reproduce it with running journalctl -f

MATE Notification Daemon seems to start for KDE Plasma 5, and pops up notifications during the start up of KDE Plasma Desktop, it's kind of hard to get a screenshot in that stage of start up...

cover art can be half the size of the screen. in notify-osd this is ok.

image: http://ompldr.org/vZDYxcQ

What the title says.

Also, it seems a little unnecessary using a checkbox for "use active monitor" in mate-notification-properties - "use active monitor" and "use all monitors" could be options provided in the "Monitor" combobox, couldn't they?

There are some keys in org.mate.NotificationDaemon schema that are only read by the daemon once. It does not connect to GSettings to listen to any changes in these keys. So if you change the values of these keys while the daemon is running, you'll have to restart the daemon in order for the changes to take effect.

I think this should be corrected.

The keys are:

• sound-enabled
• monitor-number
• use-active-monitor

The Free Software Foundation address in this file seems to be outdated or
misspelled. Ask upstream to update the address, or if this is a license file,
possibly the entire file with a new copy available from the FSF.

File: COPYING

The notification bubble does not show any text. I tested with multiple GTK+ themes.

Package versions:

• gtk3 3.18.5
• mate-notification-daemon (gtk3) 1.12.0

Please take over this [1] man page into the upstream code release of mate-notification-daemon.

[1] http://anonscm.debian.org/gitweb/?p=pkg-mate/mate-notification-daemon.git;a=blob_plain;f=debian/mate-notification-properties.1

The nodoka theme use the font color from the used gtk theme.
Which is bad for dark gtk themes which mostly use a light font color, i result notifications are unreadable (light font color on yellow background).
A solution is to hardcode to font color tho black.
I see no reason why nodoka theme should switch the font color with a fixed background color.

Filed as DebianBug#779870:

Dear Maintainer,

   * What led up to the situation?

I'm running a recent install of debian jessie with MATE. To use bluetooth, I
installed the blueman package. I wanted to copy files from one device to
another.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

On trying to configure the connection to another device via bluetooth, I am
asked to confirm the connection and password via a notification. The problem
ist that the notification does not stay in the upper right corner, but it is
moving rather quickly to the left. It's so fast I can't read it, I had to make
screenshots of it. But I never managed to click the "confirm" button, which is
in the notification.

   * What was the outcome of this action?

As I found no other way to confirm a connection, blueman renders useless, I had
to send the files via mail.

   * What outcome did you expect instead?

Setting up a bluetooth connection.


PS: m-n-d kept using ca. 60% of the CPU, I had to kill the process (I only
realised that some time later, because of fan noise).It's completely
reproducible for me.

I just got the upgrade to MATE 1.16. Notification text between <b></b> is no longer displayed bold. Instead, the codes and the text are displayed as notification: <b>New song reported by VLC</b>. I expect the text to be New song reported by VLC without the formatting codes.

I use Manjaro Linux.

complete output from rpmlint

[rave@mother ~]$ rpmlint /var/lib/mock/fedora-16-x86_64/mate-notification-daemon-1.4.0-5.fc16.x86_64.rpm
mate-notification-daemon.x86_64: W: spelling-error %description -l en_US freedesktop -> free desktop, free-desktop, desktop
mate-notification-daemon.x86_64: E: incorrect-fsf-address /usr/share/doc/mate-notification-daemon-1.4.0/COPYING
mate-notification-daemon.x86_64: W: non-conffile-in-etc /etc/mateconf/schemas/mate-notification-daemon.schemas
mate-notification-daemon.x86_64: W: no-manual-page-for-binary mate-notification-properties
mate-notification-daemon.x86_64: E: invalid-desktopfile /usr/share/applications/mate-notification-properties.desktop value "MATE;GTK;Settings;DesktopSettings;" for key "Categories" in group "Desktop Entry" contains an unregistered value "MATE"; values extending the format should start with "X-"
1 packages and 0 specfiles checked; 2 errors, 3 warnings.

I use Slider as the theme for notifications. However whenever I make a change to the appearance options or switch to another desktop background, the notification-daemon theme reverts to nodoka. I change the setting back manually each time using dconf editor. seems the only way to make it stick right now.

Not completely fubar by any means. Just a minor annoyance I would appreciate you looking into.

OS details:

Fedora 21 MATE-Compiz Spin 32-bit (same happened with Fedora 20 but I believe it is upstream and not anything to do with Fedora Project)
notification-daemon: * 2014-10-23 Wolfgang Ulbrich [email protected] - 1.8.1-1
mate-desktop: 1.8.1-9
mate-settings-daemon - 1.8.2-1

If you need any further info please ask. not sure what is needed. Thank you! Wolfgang is the package maintainer for Fedora Project's MATE-Compiz desktop environment.

I'm running Linux Mint 14 with MATE 1.4.0-1. Computer is a stock Dell Latitude D630 with the Nvidia graphics option. Notifications from the power manager and Banshee media player are appearing in the lower right-hand corner of my screen, protruding off the bottom and side of my screen. Any messages in these notifications are completely off the screen and it's impossible for me to read them. They continue to appear in this location regardless of where I have the pop-up notification location set in the Control Center. Notifications from other applications, such as Thunderbird, do appear in the proper location (currently set for the upper right-hand corner).

We have that key in schema and in daemon.h, but it's not really used anywhere.
Should it be deleted, or should some code using it be added to daemon and/or capplet?

It's pointless, clicking anywhere on the notification window closes it (plus normal notifications timeout in just a few seconds anyway, a feature request to set the timeout length would be nice) .

I tried to just edit the notification theme I'm using (standard), but it looks like the 4 available themes are hardcoded into the daemon itself? That's a weird way to implement themes, shouldn't they be separated?

Anyway, kudos to the MATE team. You've put together a very well integrated DE that's nearly as light on RAM usage as Xfce is. Cheers!

https://forums.bunsenlabs.org/viewtopic.php?pid=15789#p15789

I suspect after commit 2f0f21b this is now failing as the directory macros was removed. I can work around this by running "autopoint --force" which copies the required files. However I am not sure this is the correct way to handle this.

***** intltoolize *****
***** PWD: /var/tmp/portage/x11-misc/mate-notification-daemon-1.5.2/work/mate-notification-daemon-1.5.2
***** intltoolize --automake --copy --force

cp: kan het normale bestand ‘macros/intltool.m4’ niet aanmaken: Bestand of map bestaat niet
intltoolize: cannot copy '/usr/share/aclocal/intltool.m4' to 'macros/intltool.m4

no-manual-page-for-binary mate-notification-properties
Each executable in standard binary directories should have a man page.

Clicking on close button with standard theme crashed m-n-d.
build is from git master 20150728.c47626f
mate-notification-daemon-1.10.2-10.5.git20150728.c47626f.fc22.x86_64
stacktrace at: https://dl.dropboxusercontent.com/u/49862637/Mate-desktop/Bugs/m-n-d-standard-backtrace

#48 0x0000000000404b25 in main (argc=1, argv=0x7ffe02e5c808) at daemon.c:1799
        daemon = 0x1c6a0c0 [NotifyDaemon]
        connection = <optimized out>
        bus_proxy = <optimized out>
        error = 0x0
        res = <optimized out>
        request_name_result = 1

At-spi doesn't seem to be picking up the text of pop-up notifications. For example, in system -> preferences -> pop-up notifications, Orca doesn't speak the text of the notification that pops up when activating the preview button. Replacing mate-notification-daemon with notify-osd does appear to help in most cases, but it's not 100%, and removes the option to set where pop-up notifications appear on screen, as well as all options associated with pop-up notifications including the preview.

I've noticed this only with Mate notification daemon.
Some html elements are not displayed right.
But this one is even more disturbing.. if there's a & char in the string for notification , notification for body will just be empty.
To test run this in terminal :
notify-send "test & example"

It will turn that to a empty string.

This is another feature request. It would be neat if mate could turn application's notifications on and off, similar to gnome shell, but much more accessibly than gnome shell. I'd be willing to help implement this once my grasp of c is better.

This was observed on Manjaro Linux (Arch Linux):

• 1.12.0 breaks Pidgin libnotify functionality
• 1.10.2 works perfectly, showing new messages as a notification as they come in

Hello!

In current version of mate-notification-daemon (I have 1.2.0-2+oneiric) if you have multiple screens (I have two monitors attached) notifications are shown on screen that mouse is currently in. For example if I have my mouse in right screen notification is shown in right screen:

warning big image:

http://i.imgur.com/OEnwg.jpg

but If I have my mouse in the left screen notification is shown in the left screen:

warning big image:

http://i.imgur.com/hfjXd.jpg

So I would like to suggest couple solutions:

1. If I select 'Top Right' in notifications properties it should always shown in top right corner of the desktop (in this case right monitor top right corner). It shouldn't matter which screen is active. Same goes for other settings: 'bottom left' should always show notifications in bottom left corner of the desktop (in this in bottom left corner of left monitor).
2. User should be able to select in notification properties on which monitor notification is show. This a little bit harder to implement because displays can change dynamically and using saved selection can be hard if user changes screens configuration.

This bug is little bit annoying because I can't expect the notification to always show up in the same place, for example when I write code and use tdeamon (which uses notifications to show unit tests results) notifications tend to show all over the desktop.

I hope this description is clear. And thanks for all the great work you put into mate desktop! I really like it.

Krystian Kichewko

I have Mint 14 on a Thinkpad W500, running Compiz (what might have eventually been called MatePiz, but that died on the vine in November).

Everything works, it's an excellent platform, and Mate is very impressive (this from an XFCE user on Lucid for the last (mumble) years).

I'd like to adjust the depth of messages stored by the applet, and I'd like to continue to see messages display, even if they are not added to the applet.

I don't know if this is a bug or not. Depends on how it was designed. I hope it's configurable, though!

Googling showed me nothing - no one else noticed this, or discussed it, and I find no bug reports. My versions of the notification tools:

ii libmatenotify 1.4.1-1+precise amd64
i mate-notification-daemon 1.4.0-2+precise amd64

I did note that I'm running mate for precise when Mint 14 is equivalent to Quantal. Everything has been working unbelievably well, so I did not want to tamper. lol!

The Debian lintian system says it all...

I: mate-notification-daemon: desktop-entry-lacks-keywords-entry usr/share/applications/mate-notification-properties.desktop
N: 
N:    This .desktop file does either not contain a "Keywords" entry or it does
N:    not contain any keywords not already present in the "Name" or
N:    "GenericName" entries.
N:    
N:    .desktop files are organized in key/value pairs (similar to .ini files).
N:    "Keywords" is the name of the entry/key in the .desktop file containing
N:    keywords relevant for this .desktop file.
N:    
N:    The desktop-file-validate tool in the desktop-file-utils package is
N:    useful for checking the syntax of desktop entries.
N:    
N:    Refer to
N:    http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s05.html,
N:    http://bugs.debian.org/693918, and
N:    https://wiki.gnome.org/GnomeGoals/DesktopFileKeywords for details.
N:    
N:    Severity: wishlist, Certainty: certain
N:    
N:    Check: menu-format, Type: binary

The NEWS file in the 1.10.0 release lacks the changes information for 1.8.1 and 1.8.2.

Hello, need help. Sorry, I do not know English well. Please see the video: https://docs.google.com/file/d/0B2eWU3wmchq_c1ZFdmEzMGo3ZjA/
Can anybody help, how to prevent this issue with mate notification messages?
Besides changing Notification settings in Control center does not take effect when I try to change notification theme and position. It is always appear at right upper corner.
MATE 1.6 on Linux Mint 13.

As the title says the source language (International English I presume) has both Popup and Pop-Up in the translation pot file. Some langauges prefer one over the other but to have both in the source language pot confuses the issue and possibly confuses non-native English speakers as well. It is probably better to choose one over the other in pot files (all pot files not just this one) and let the translators choose the correct version for their individual translation efforts.

I have been trying kdbus lately and it occoured to me that mate-notification-daemon will exit with error-code 1, which then kdbus registers as failure. All services that exit cleanly should exit(0) or return(0) anyways.

See also:

systemd/systemd#313

Hi

The notification spec that mate-notification-daemon partially follows is here:
https://developer.gnome.org/notification-spec/

Which features are supported and which are not? It is my understanding that hyperlinks don't work.

All of my CFLAGS are dropped when running configure.

I should see -02 -pipe -march=native, but instead, with 1.12.1, I only see -Wall

Please update m-n-d so that it respects and doesn't throw away CFLAGS

I was looking into a weird problem where blueman would ask for a confirmation of pairing with no confirm/deny actions. All other themes are ok.

Below is a simple example python script to reproduce the problem.

from gi.repository import Notify

Notify.init("Blueman")

def test_cb():
    print "Test"

n = Notify.Notification.new("Test", "I am a test message", "dialog-question")
n.add_action("Confirm", "confirm", test_cb, None)

n.show()