I'd like to see this bug finally resolved in the next Ubuntu. I care about this much more that whatever display stack or anything else is implemented. It's very important for users and developers to have notifications that are useful and convenient. It's also important to follow the freedesktop.org standards and your own documentation. Fix NotifyOSD in Ubuntu+1--add respect for the timeout parameter.
DNS Cache and Encryption::Earthsoft PT-Series Cards::Pantheon {3d,Lite,Lighter}::Mir = Ubuntu Lost in Space::Fix NotifyOSD
I don't know who this post is directed at, as most developers rarely post here or read this sub-forum. If you read Sebastion Bacher's last post in the report, there is no maintainer for notify-osd, and if there is no one to fix the bug, it won't get fixed. The only way to solve the problem is to fix the problem yourself, or find a developer that is willing to take on maintaining it.
Forum posting guidelinesMember:Not Canonical TeamUbuntu membership via Forums contributions
Actually I'd say the only bug there under 'some' consideration for being fixed is to patch the manpage to reflect no -t option. As far as officially it's been fairly well established what deviation from the current hard default of 10000ms is acceptable & nothing in that vein has occurred 723980 Here I settle for 2700ms which is about right for me, I've no apps that require control of timeout
I've patched notify-osd and change hard-coded values to ones that were useful to me. It's not that difficult. Why some of these values are hard-code is a mystery. So rather than fight the design decisions, I fixed it myself. I think I still have 9.04 on a system somewhere. I don't remember what I set the expire time, but I'm pretty sure I still have the build evironment. Here's a PPA for a more customizable notify-OSD, although my quick search shows that it may not work in 13.04: http://www.webupd8.org/2011/05/confi...bbles-for.html The pop-up locations were dumb--covering window controls and not user-changeable. There were several notify-osd design issues that were never addressed. If U remember, at that time, there was a desktop environment under development with similar design decisions.
Last edited by tgalati4; August 20th, 2013 at 05:20 AM.
------------------------------------- Oooh Shiny: PopularPages Unumquodque potest reparantur. Patientia sit virtus.
Thanks mc4man and tgalati4 for providing the op with the information he needs to solve his problem.
Originally Posted by tgalati4 Here's a PPA for a more customizable notify-OSD, although my quick search shows that it may not work in 13.04: http://www.webupd8.org/2011/05/confi...bbles-for.html I have been using ths PPA for a few years already, but thanks for posting the link in case anyone else needs it. Originally Posted by cariboo907 Thanks mc4man and tgalati4 for providing the op with the information he needs to solve his problem. I think you misunderstood. I don't need help; the bug needs to be fixed. It's been going for years now and all the previous developers will say is that Canonical choose this design and won't accept any changes to it.... that's rediculous, it's a terrible design.
Originally Posted by cariboo907 I don't know who this post is directed at, as most developers rarely post here or read this sub-forum. That's rather unfortunate. I would think a forum about the development of the next distribution would be something developers are at least reading....
In case anyone's interested, there's another option described here: Code: sudo apt-get install xfce4-notifyd
sudo apt-get install xfce4-notifyd
So the timeout is the only issue here? As mac4man stated, just change the man page. I didn't realize that I "me too" on the bug report. I guess it was when I was studying the Zenity program that I ran across it.
NoSnap-popey AnotherNoSnap https://github.com/popey/unsnap/tree/main
Originally Posted by quhttp://ubuntu-discourse.org/quotion I have been using ths PPA for a few years already, but thanks for posting the link in case anyone else needs it. I think you misunderstood. I don't need help; the bug needs to be fixed. It's been going for years now and all the previous developers will say is that Canonical choose this design and won't accept any changes to it.... that's rediculous, it's a terrible design. Try here. http://ubuntu-discourse.org/ According to Jorge Castro the devs pop in there.
Not a Canonical employee just a volunteer _____ Remove old kernels (Ensure you do the dry run first in step 6 )
View Tag Cloud
Ubuntu Forums Code of Conduct