[Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
I don't quite understand either, and I try to be as inclusive as
possible in life, but my complaint is that there is an "official" stance
to ignore the requests for a warning on the "official" documentation
that says something works that does not.
That is inhernetly saying, "yes I officially said A works, but I also
officially decided that I will not have A work and also not mention that
it does not work."
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in notify-osd package in Ubuntu:
Won't Fix
Status in notify-osd package in Arch Linux:
New
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ "expire-time", 't', 0,G_OPTION_ARG_INT, &expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
Matthew Paul Thomas (mpt) we don't know how many people are annoyed with
this bug vs those who are not because today, we simply don't have as
many competent programmers as we did a decade ago (before the tech
industry boom) that will delve this deep into a problem amoung the
programming community.
Obviously with this many comments and complaints alone we could say that
this is an issue that isn't going away.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in notify-osd package in Ubuntu:
Won't Fix
Status in notify-osd package in Arch Linux:
New
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ "expire-time", 't', 0,G_OPTION_ARG_INT, &expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
It would be great if they would accept that, but this is an issue they
"won't fix".
If they did accept your manual page fix, someone down the line would
say, "hey, wouldn't it be great if we could add a timeout option?"
Then the cycle of madness repeats (with a longer circumferance).
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in notify-osd package in Ubuntu:
Won't Fix
Status in notify-osd package in Arch Linux:
New
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ "expire-time", 't', 0,G_OPTION_ARG_INT, &expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
Yeah I know, I still see the OSD staying on and wondered, oh if there
were just some way to make it disappear faster if it wasn't important.
Hey, there must be a timeout option... oh wait, I'm not going to fall
for that one again.
We can waste our time on more productive issues that plaque the world
that we are MUCH MORE LIKELY TO AGREE UPON, such as:
1. Abortion.
2. Which religion is the one true religion.
3. How to school your children.
4. Reducing the diviorce rate.
Just look at all those topics where so many people agree on and have
resolved things so well, seriously, look at them, then look at this
ridiculous issue.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in notify-osd package in Ubuntu:
Won't Fix
Status in notify-osd package in Arch Linux:
New
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ "expire-time", 't', 0,G_OPTION_ARG_INT, &expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
Where is the illogical reasoning where:
A group of people encountered a timeout option that was not working,
spent many hours of their time, lives, and energy, to figure out what
was causing it, and only to find out it does nothing but did not warm
them of so?
They posted about this, and have asked for:
1. At least a warning.
2. An option to enable or disable it.
3. To make it work as documented.
So the logical reasoning is to say, "no we won't do that and we won't
tell you about it, only way to find out is the same way everyone else
did by ending up here on this thread".
> The people who have tried to figure out why the timeout does > not work
> are going by out-of-date notify-send documentation. nh2 > kindly attached
> a patch that adds the sentence "Currently ignored" to the > timeout flag
> description. Unfortunately that implies that the change is > temporary,
> when it is not; a viable patch would just remove mention of > the flag
altogether.
Latest version does not reflect that... still.
> It is not the responsibility of a software project to contain > the union
> of all features or options provided by its predecessors. That > leads to
> overcomplexity and to increasingly unreliable and > unmaintainable
software.
This is not the union of all features, it's clearly something that needs
to be addressed and we have proven it with this thread alone.
Let's look at Windows and Linux:
Windows is commercially based, they include "features" that sell, how
often does Windows crash?
Linux is community based, anyone can contribute, the features that
people want get in. How often does Linux crash?
Having more features does not always result in overcomplexity,
increasingly unreliable, and unmaintainable software. We want meaningful
features that people are asking for, not just something that would be
"neat".
We've wasted so many days and weeks on this topic, it needs to be
addressed, not just "won't fix".
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in “notify-osd” package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ "expire-time", 't', 0,G_OPTION_ARG_INT, &expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
Well let's approach this logically, scientifically, sensibly, and
reasonably.
We have an easy opportunity to add a "choice", to have the option or
not. But we are choosing not to have a choice.
The whole point of Ubuntu and free software is to be better than
commercial, to actually have the best and brightest minds contribute,
not highschool hackers who just want to make a buck and write buggy
code.
We should somehow at the very least, come half way and allow a choice
for to have the expire option or not.
Just because no one else does it does not mean we should not have that
option (note I am not saying that we absolutely must have it, but a
choice).
We can choose to use Linux, Windows, or Mac, or something else entirely,
we can and should have a choice to enable such a timeout/expire in our
OSD displays. Note that I said choice to enable or disable on the server
side, not explicitly accepting expire arguments on the client side.
With regards to the "silent majority", we don't know how many people
have come across this bug, we don't know how many people want it or do
not want it.
But we have many comments from people who have spent many hours trying
to figure out why the expire timeout was not being detected so I think
placing a warning about the expire timeout not being accepted is
reasonable.
Throughout history, having fewer choices has always, eventually, led to
monopolies, dictators, and single source dominations. I don't think we
are close to that with NotifyOSD, but we are going in that direction if
we explicitly deny such a choice.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in “notify-osd” package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ "expire-time", 't', 0,G_OPTION_ARG_INT, &expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
Re: [Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
I was not out to program anything the day I found out about this
problem.
I was writing a shell script just to get something displayed on screen
after a key press. I found out about notify-osd and used it, it took 5
seconds for me to figure out how to use it.
Then I realized that notifications were backlogged and I couldn't figure
out why. notify-send did not warn that the expiration timeouts were
being ignored.
If you call me a programmer just for writing a shell script I feel
disproportionately-honored.
It's just a shell script, that I spent two days trying to figure out
what was wrong and my time is valuable, there was no notice that an
option was being ignored.
My gripe is that it was being ignored and no warning was being printed
as it was. That will waste a lot of people's time, and cause a lot of
users to wonder who the bad programmer was to see a notification on
screen repeat for several minutes and no way to get rid of it.
My workaround for killing the backlog stack was:
#!/bin/bash
pkill notify-osd
notify-send "Current value is $VALUE"
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in Notify OSD:
Won't Fix
Status in “notify-osd” package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ "expire-time", 't', 0,G_OPTION_ARG_INT, &expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
Re: [Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
Thanks for the patch, though I think eventually this issue needs to be
worked out and agreed upon.
-Vanessa
On Tue, 2013-12-24 at 04:44 +, Heather Van Wilde wrote:
> @vanessax Buried in the comments is a patch that is supposed to restore
> full functionality. But that, for one, doesn't address the core issue,
> and secondly, does nothing to prevent the next change done to notify-osd
> by Ubuntu devs to rebreak the system down the road.
>
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in Notify OSD:
Won't Fix
Status in “notify-osd” package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ "expire-time", 't', 0,G_OPTION_ARG_INT, &expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 497703] Re: NotifyOSD slow with repetitive notifications
I think this problem is either related to or compounded by another issue
about timeouts that is unresolved, there is a long standing bug #390508
discussed here: https://bugs.launchpad.net/ubuntu/+source/notify-
osd/+bug/390508
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/497703
Title:
NotifyOSD slow with repetitive notifications
Status in “notify-osd” package in Ubuntu:
Confirmed
Bug description:
Binary package hint: notify-osd
When a notification appears one after another the OSD tends to lag and
respond slowly.
For example when I increase volume (from my netbook's volume hotkey) and hold
or repetitively press it, it will respond slowly.
It seems like a similar problem when numerous notifications (that
aren't volume notifications) appear over top of each other and it
waits for the older one to disappear first, then shows the newer one
later.
Volume and other notifications should not appear as if they popped up
one after another, but rather as if the OSD was one window with
dynamic text (and icons,etc) that change in real time, as
notifications occur, and not wait for the older ones to disappear.
(Also, ideally, clicking a notifcation should take you to the program
it came from, and/or close the OSD pop up {but this isn't really a bug
so i'll go post it on brainstorm as well} )
ProblemType: Bug
Architecture: i386
Date: Thu Dec 17 01:58:42 2009
DistroRelease: Ubuntu 9.10
GtkTheme: Inverted
IconTheme: elementary_2.2
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: ASUSTeK Computer INC. 1005HA
Package: notify-osd 0.9.24-0ubuntu1
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-16-generic
root=UUID=0e4e4399-5b80-4763-8f60-a87a999551e6 ro quiet splash
ProcEnviron:
LANG=en_CA.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
RelatedPackageVersions:
xserver-xorg 1:7.4+3ubuntu10
libgl1-mesa-glx 7.6.0-1ubuntu4
libdrm2 2.4.14-1ubuntu1
xserver-xorg-video-intel 2:2.9.0-1ubuntu2
xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SourcePackage: notify-osd
Uname: Linux 2.6.31-16-generic i686
WindowManager: compiz
dmi.bios.date: 09/23/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0905
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1005HA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0905:bd09/23/2009:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1005HA
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/497703/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 507832] Re: notifications never cleared when new ones keep comming
I think this problem is either related to or compounded by another issue about timeouts that is unresolved, there is a long standing bug #390508 discussed here: https://bugs.launchpad.net/ubuntu/+source/notify- osd/+bug/390508 -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/507832 Title: notifications never cleared when new ones keep comming Status in “notify-osd” package in Ubuntu: Confirmed Bug description: Binary package hint: notify-osd Running Karmic (Ubuntu 9.10) Using: 0.9.24-0ubuntu What should happen: After a set time (3 seconds I believe?) notifications should disappear, even when new notifications are appearing. What happens: When new notifications keep coming, old notifications never get cleared. This could cause an overdose of notifications that don't clear when many things happen at once. How to reproduce: Get a first notification, and then trigger additional notifications. One way to get notifications is to keep changing the track in Rhythmbox. I used Rhythmbox for the initial notification and than changed the system volume with extra keyboard keys, this also triggers a notification. Not a major issue, but i'm sure it will drive some people crazy if such a stack-up triggers for whatever reason. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/507832/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 723980] Re: default display time is way too long and non configurable
They don't seem to want to change the timeout or make it configurable, here is the full discussion about that https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/390508 -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/723980 Title: default display time is way too long and non configurable Status in “notify-osd” package in Ubuntu: Confirmed Bug description: Binary package hint: notify-osd The default display time for notification bubbles of 10 sec.'s is too long and represents the most common specific complaint. (the #1 complaint is nothing is configurable. I use 2 sec.'s here, but a reasonable setting for all may be 4-5 sec.'s, or make it a configurable setting (gconf ? Seeing that notify-osd may be rebuilt before release, (possibly due to bug #670785), maybe some consideration to adjusting.. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: notify-osd 0.9.29-0ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 Uname: Linux 2.6.38-5-generic i686 Architecture: i386 Date: Wed Feb 23 17:20:02 2011 GtkTheme: Ambiance IconTheme: ubuntu-mono-dark InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202) MachineType: alienware alienware ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 LC_MESSAGES=en_US.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-5-generic root=UUID=b6b70e8e-15d5-4586-ab14-296274f29264 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.6~3ubuntu7 libgl1-mesa-glx 7.10.1~git20110215.cc1636b6-0ubuntu2 libdrm2 2.4.23-1ubuntu3 xserver-xorg-video-intel 2:2.14.0-1ubuntu10 xserver-xorg-video-ati N/A SourcePackage: notify-osd WindowManager: gnome-wm dmi.bios.date: 01/29/2004 dmi.bios.vendor: Intel Corp. dmi.bios.version: BZ87510A.86A.0091.P21.0401291113 dmi.board.name: D875PBZ dmi.board.vendor: Intel Corporation dmi.board.version: AAC26680-205 dmi.chassis.type: 2 dmi.chassis.vendor: alienware dmi.chassis.version: alienware dmi.modalias: dmi:bvnIntelCorp.:bvrBZ87510A.86A.0091.P21.0401291113:bd01/29/2004:svnalienware:pnalienware:pvr:rvnIntelCorporation:rnD875PBZ:rvrAAC26680-205:cvnalienware:ct2:cvralienware: dmi.product.name: alienware dmi.sys.vendor: alienware glxinfo: Error: [Errno 2] No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/723980/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1176365] Re: Support for ADHD accessibility
I think this is related to an issue with intentionally ignoring the timeout argument, there is a long discussion about the issue/bug #390508 here: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/390508 -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1176365 Title: Support for ADHD accessibility Status in Notify OSD: New Status in “notify-osd” package in Ubuntu: Triaged Bug description: Apologies if I'm submitting my concerns to the wrong place. I've been unable to find any mention of accessibility in relation to notifyOSD anywhere on the web. As someone with ADHD, I find an unskippable 10 second timeout to be extremely disruptive. This is especially true when there are many notification fading in and out in the corner of my eye. The notifications might as well take up my whole screen. That's not an exaggeration and it's not meant to be a snarky insult. I'm being honest and sincere when I say that the default behavior makes my computer nearly unusable . . . *for me*. I acknowledge that I am not the most common user example, but there are accommodations in Ubuntu for other disabilities. Those accommodation are generally far more effort to implement than click-to-close behavior or a configurable time-out. As things are now, I am relying on kludgey, third party solutions to make my computer usable. To manage notifications about this bug go to: https://bugs.launchpad.net/notify-osd/+bug/1176365/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1205660] Re: Users cannot dispel notifications if they are disrupting work
Allowing an option for the user to specify on the server side, such as click to close, would seem like a good option to me. (yes, I am aware of the fact that notifications are inherently not interactive) -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1205660 Title: Users cannot dispel notifications if they are disrupting work Status in “notify-osd” package in Ubuntu: Confirmed Bug description: There is no method for users to dispel notifications. Current behaviour: when the user hovers the mouse over the notification it blurs. This serves no useful purpose * the notification is blurred, so it is not readable, it is sufficiently opaque to make it a nuisance, It conflicts with the original spec of "pausing the notification" (https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/796596) By changing the nature of the notification to include any method of dispelling the notification (hotkey, clickable notifications, button on notification bar), users are not held hostage to the time out. Disabling notifications or changing the time out globally is NOT a solution. requirements of fix: *disable blurring of notifications *add method of dispelling notifications that ALSO works for fullscreen apps. The code for a closable notification already exists in "ppa:leolik/leolik" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1205660/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 390508] Re: notifyOSD ignores the expire timeout parameter
Having spent 5 minutes learning about notify-osd and then 6 hours trying
to figure out what the problem was and finally coming across this, it's
appearent there is a dichotomous debate over this timeout issue.
I'm not sure if it's already mentioned before, but isn't there a way for
the user to set the server to recognize timeouts? At least this way we
don't have the fork and hack the code just to make a new notify-osd-
that-recognizes-timeout.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in Notify OSD:
Won't Fix
Status in “notify-osd” package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ "expire-time", 't', 0,G_OPTION_ARG_INT, &expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
