Sign up ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.

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.

Is there a way around behaviour? As the developers label this as a "feature" instead of a bug, I would like some alternatives.

share|improve this question

closed as off-topic by Pandya, Eric Carvalho, waltinator, KasiyA, BuZZ-dEE Jan 13 at 6:51

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – Pandya, Eric Carvalho, waltinator, KasiyA, BuZZ-dEE
If this question can be reworded to fit the rules in the help center, please edit the question.

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
Alternatively you can use notify-send "Text Here" ; sleep 3 ; killall notify-osd (where sleep 3 is example of expiration (actually killing) after 3 seconds)! – Pandya Jan 13 at 9:00

4 Answers 4

up vote 26 down vote accepted

This is a known bug:

share|improve this answer
This is not really a bug. It's a design decision. – Eren Tantekin Jun 25 '12 at 21:12
A wrong design decision can be a bug. – Boris Bukh Jun 29 '12 at 21:42
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
The etymology of “bug” is something creeping around that you didn't know existed. To call a design decision a bug doesn't even make sense. It's intended behavior. It's just a bad design. – Christopher Done Oct 31 '14 at 16:11
It was (in the end) marked as "Won't fix". – andrybak Nov 20 '14 at 15:42

As mentioned in one of the posts above, there is a design decision to disallow this feature. Fortunately for you, other people disagree as well and have set up a PPA and you can reverse this decision for your system as well.

To solve your problem just:

sudo add-apt-repository ppa:leolik/leolik 
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install libnotify-bin
pkill notify-osd


To add even more features to send-notify then you currently have:

sudo add-apt-repository ppa:amandeepgrewal/notifyosdconfig
sudo apt-get update
sudo apt-get install notifyosdconfig

For more information on the solution above, read this article:

Configurable Notification Bubbles for Ubuntu

share|improve this answer
Good point, +1 for the better answer ;) – A.B. Jul 30 at 17:48

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", ...


notify-send ignores timeout?

share|improve this answer
notify-send --expire-time=30000 "test"

show the notification 30s on Ubuntu 14.04.

notify-send --expire-time=60000 "test"

show it 1min.

share|improve this answer
You did read the other answers and comments, right? – saiarcot895 Jul 1 '14 at 14:21
Not all, why ? These commands are working well, no ? – Guillaume Jul 1 '14 at 14:37
Ah ok.. for 5 min, it's don't work any more :( – Guillaume Jul 1 '14 at 14:53

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