Bug#664247: [Pkg-xfce-devel] Bug#664247: xfce4-notifyd: notifications never die

2013-06-28 Thread Juha Jäykkä
If I try to send a notification to xfce4-notifyd, the notification
stays on the screen until xfce4-notifyd is killed. This happens
regardless of the default timeout set with xfce4-notifyd-config.
 I am curious if you can reproduce this issue with xfce4-notifyd from
 unstable (0.2.4-2). There was bug that caused notification timeout not

No, I cannot. So, from my point of view, #664247 can be closed. I think the 
other problems you mention are different and should not be dealt with here.

Thanks.

-Juha

-- 
 ---
| Juha Jäykkä, ju...@iki.fi |
| http://koti.kapsi.fi/~juhaj/  |
 ---


signature.asc
Description: This is a digitally signed message part.


Bug#664247: [Pkg-xfce-devel] Bug#664247: xfce4-notifyd: notifications never die

2013-06-27 Thread Petr Gajdůšek
So 17. březen 2012, 15:40:20 CET
Juha Jäykkä ju...@iki.fi napsal:

   If I try to send a notification to xfce4-notifyd, the notification
   stays on the screen until xfce4-notifyd is killed. This happens
   regardless of the default timeout set with xfce4-notifyd-config.
[snip]


Hello,

I am curious if you can reproduce this issue with xfce4-notifyd from
unstable (0.2.4-2). There was bug that caused notification timeout not
working if the timeout was shorter than the fade time - 800ms. E.g.
`notify-send -t 5 test`. Enabled compositing was required to trigger
the issue and it is fixed since 0.2.3.
https://bugzilla.xfce.org/show_bug.cgi?id=8580

Another issue is xfce4-notifyd-config shows 1s default timeout even
if the real default is set to 0 (never) or negative number (should
default to 10s though). So if you run xfce4-notifyd-config and there is
1s and you close it without changing, the timeout may be actually
disabled (0). 

If I remember correctly I experienced even more serious malformat
of xfconf expire-timeout value - probably floating point number. But I
cannot reproduce it now or track the fixing commit git, so maybe I am
dreaming, it was log time ago, if even.

Anyway, I recommend to check what `xfconf-query -c xfce4-notifyd
-p /expire-timeout` really says.

Cheers,
Petr


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#664247: [Pkg-xfce-devel] Bug#664247: xfce4-notifyd: notifications never die

2012-03-17 Thread Yves-Alexis Perez
On sam., 2012-03-17 at 00:43 +, Juha Jäykkä wrote:
 Package: xfce4-notifyd
 Version: 0.2.2-1
 Severity: important
 
 If I try to send a notification to xfce4-notifyd, the notification
 stays on the screen until xfce4-notifyd is killed. This happens
 regardless of the default timeout set with xfce4-notifyd-config.
 
 If using pynotify to show the notification, the .close() method
 is able to get rid of the notification, but the timeout is still
 not respected.

What happens if you use notify-send? Maybe you *need* to call .close()?

Regards,
-- 
Yves-Alexis


signature.asc
Description: This is a digitally signed message part


Bug#664247: [Pkg-xfce-devel] Bug#664247: xfce4-notifyd: notifications never die

2012-03-17 Thread Juha Jäykkä
  If I try to send a notification to xfce4-notifyd, the notification
  stays on the screen until xfce4-notifyd is killed. This happens
  regardless of the default timeout set with xfce4-notifyd-config.
 What happens if you use notify-send? Maybe you *need* to call .close()?

Oh, sorry. I my report was a bit misleading: the first paragraph was meant to 
include a mention that this is the behaviour with notify-send and the second 
paragraph just a confirmation that the behaviour is NOT due to notify-send, 
hence due to xfce4-notifyd.

In short: it does not matter what client sends the notification, the behaviour 
is always the same.

Cheers,
-Juha

-- 
 ---
| Juha Jäykkä, ju...@iki.fi |
| http://www.maths.leeds.ac.uk/~juhaj   |
 ---


signature.asc
Description: This is a digitally signed message part.