From: "Peter Münster" <pmlists@free.fr>
To: help-gnu-emacs@gnu.org
Subject: Re: notifications-notify resets idle-time
Date: Mon, 13 Feb 2012 09:29:02 +0100 [thread overview]
Message-ID: <874nuvi1bl.fsf@micropit.couberia.bzh> (raw)
In-Reply-To: 87sjif21m2.fsf@gmx.de
On Sun, Feb 12 2012, Michael Albinus wrote:
> xd_read_message_1: Event received: DBUS_MESSAGE_TYPE_SIGNAL 2
> org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus NameAcquired
> (:1.240)
> idle time: 1.297380
Thanks! The only difference is, that you don't get a NotificationClosed
signal, but on my system I do:
--8<---------------cut here---------------start------------->8---
xd_read_message_1: Event received: DBUS_MESSAGE_TYPE_SIGNAL 1773 :1.10
/org/freedesktop/Notifications org.freedesktop.Notifications
NotificationClosed (221 1)
xd_read_message_1: Event stored: (:session 4 1773 :1.10
/org/freedesktop/Notifications org.freedesktop.Notifications
NotificationClosed notifications-on-closed-signal 221 1)
DBus-Event (dbus-event :session 4 1773 :1.10
/org/freedesktop/Notifications org.freedesktop.Notifications
NotificationClosed notifications-on-closed-signal 221 1)
idle time: 0.498186
--8<---------------cut here---------------end--------------->8---
So there are 2 issues:
- The NotificationClosed signal resets the idle-time, and IMO it should
not. (emacs issue)
- You don't get the NotificationClosed signal and that's probably a bug
of your notification system, perhaps this one:
https://bugs.kde.org/show_bug.cgi?id=228743
On my system, it's the notification-daemon-0.5.0.
According to the spec, the NotificationClosed signal should be sent:
http://www.galago-project.org/specs/notification/0.9/x408.html#signal-notification-closed
Should I make an emacs bug report?
Does anyone know a workaround?
--
Peter
next prev parent reply other threads:[~2012-02-13 8:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 22:08 notifications-notify resets idle-time Peter Münster
2012-02-11 9:57 ` Michael Albinus
2012-02-11 11:38 ` Peter Münster
2012-02-11 12:40 ` Michael Albinus
2012-02-11 12:51 ` Peter Münster
2012-02-11 16:00 ` Michael Albinus
2012-02-11 16:38 ` Peter Münster
2012-02-11 17:26 ` Michael Albinus
2012-02-11 19:06 ` Peter Münster
2012-02-12 9:16 ` Michael Albinus
2012-02-12 11:09 ` Peter Münster
2012-02-12 11:59 ` Michael Albinus
2012-02-12 20:37 ` Peter Münster
2012-02-12 21:17 ` Michael Albinus
2012-02-13 8:29 ` Peter Münster [this message]
2012-02-13 11:53 ` Michael Albinus
2012-02-13 15:42 ` Peter Münster
2012-02-13 16:43 ` Michael Albinus
2012-02-13 23:13 ` Peter Münster
2012-02-14 9:45 ` Michael Albinus
2012-03-04 21:24 ` Peter Münster
2012-03-05 14:51 ` Michael Albinus
2012-03-06 10:34 ` Michael Albinus
2012-03-06 14:53 ` Peter Münster
2012-03-07 7:58 ` Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874nuvi1bl.fsf@micropit.couberia.bzh \
--to=pmlists@free.fr \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.