Tell me more ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.
up vote 4 down vote favorite

Maybe I'm doing something wrong, but shouldn't the commands (run separately)

notify-send -t 1 "test"
notify-send -t 1000 "test"
notify-send -t 10000 "test"

Have different timeouts? The first being nearly instantaneous, the second one taking 1 sec and the third 100 seconds. In all cases it seems to take about six seconds.

I'm using the development branch of Precise, if this isn't an issue in the released version I'll close this as being too localized, but I'm unable to test it now.

share|improve this question
1  
yes they do I confirmed – Ringtail Mar 7 '12 at 21:43
For me it works as expected using XFCE4. – Grumbel Mar 7 '12 at 22:45
@BlueXrider you see the same problem as I do? If so, what version are you using? – Hooked Mar 8 '12 at 15:29
I confirmed the test code is working correctly. I get the time outs as directed. – Ringtail Mar 8 '12 at 16:12

2 Answers

up vote 9 down vote accepted

This is a known bug: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/390508

share|improve this answer
This is not really a bug. It's a design decision. – Eren Tantekin Jun 25 '12 at 21:12
9  
A wrong design decision can be a bug. – Boris Bukh Jun 29 '12 at 21:42
2  
When software claims to do one thing while it does another thing, it is a bug. If the developers don't want us to consider it as bug, then don't claim that it acts like it doesn't. – hakermania Sep 24 '12 at 15:50
up vote 3 down vote

This was an intentionally implemented contravention of established conventions without disqualification in the host terminal environment. ie. notify-send should no longer exist since it compromises the well-established expected and documented functionality, so instead, a new command notify-graffiti should now exist - What???? Wait a second ... all those scripts that use the "conventional" command name spelling will be compromised!?! by changing the convention of how the command name is spelled?!?! - hmmm This philosophy is exceptionally, paradoxically hypocritical as espoused by the Unity desktop terminal interface.

It can't be done both ways - preserving some conventions ie. the name of a command and yet not others, the functionality of a command as documented. If the functionality is to be compromised then so too should the command name so as to maintain integrity, conventionality, consistency, etc. of the user "experience", or is that user "frustration", "annoyance", "irritation", ...

ref:

Bookmark:
notify-send ignores timeout?

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.