Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 280775 - [New ebuild] x11-misc/notify-osd-0.9.16
Summary: [New ebuild] x11-misc/notify-osd-0.9.16
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Default Assignee for New Packages
URL: https://launchpad.net/notify-osd
Whiteboard:
Keywords: EBUILD, InVCS
: 314701 320697 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-08-08 16:15 UTC by Mikel Olasagasti
Modified: 2011-03-13 11:48 UTC (History)
7 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
notify-osd-0.9.16.ebuild (notify-osd-0.9.16.ebuild,685 bytes, text/plain)
2009-08-08 16:15 UTC, Mikel Olasagasti
Details
notify-osd-0.9.16.ebuild (notify-osd-0.9.16.ebuild,744 bytes, text/plain)
2009-08-08 16:27 UTC, Mikel Olasagasti
Details
patch to make pidgin work with notify-osd (pidgin-notify-osd.patch,3.09 KB, patch)
2009-10-18 14:57 UTC, Tommaso Pasini
Details | Diff
patch to reduce the default timeout for the notifications (fix_timeout.patch,452 bytes, patch)
2009-10-18 15:02 UTC, Tommaso Pasini
Details | Diff
x11-themes/notify-osd-icons-0.3.ebuild (notify-osd-icons-0.3.ebuild,992 bytes, text/plain)
2010-04-12 00:41 UTC, coderoar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mikel Olasagasti 2009-08-08 16:15:08 UTC
Canonical's on-screen-display notification agent
Comment 1 Mikel Olasagasti 2009-08-08 16:15:36 UTC
Created attachment 200595 [details]
notify-osd-0.9.16.ebuild

notify-osd-0.9.16.ebuild
Comment 2 Mikel Olasagasti 2009-08-08 16:27:09 UTC
Created attachment 200596 [details]
notify-osd-0.9.16.ebuild

Use versionator
Comment 3 James Earl Spahlinger 2009-08-09 21:56:27 UTC
Thank you for this ebuild, you may also want to investigate putting your ebuild in the sunrise overlay which is located at http://www.gentoo.org/proj/en/sunrise/. When/if the ebuild is put into sunrise, please let us know on this bug.

Comment 4 Tommaso Pasini 2009-10-17 17:13:44 UTC
notify-osd provides /usr/share/dbus-1/services/org.freedesktop.Notifications.service which is already provided by notification-daemon; so to be able to install the former, the latter has to be removed.

This causes a dependency problem since there are ebuilds explicitly depending on notification-daemon, among them x11-libs/libnotify and net-wireless/blueman. E.g. libnotify shoud be modified from

PDEPEND="|| ( x11-misc/notification-daemon
        x11-misc/xfce4-notifyd )"

to

PDEPEND="|| ( x11-misc/notification-daemon
        x11-misc/xfce4-notifyd
        x11-misc/notify-osd )"

Should I open new bugs for each ebuild and make them block this one?

Moreover, there is a bug with pidgin-libnotify which doesn't work correctly, the behaviour is similar to this http://666kb.com/i/b6lhhgwixpiknvgh1.png
Comment 5 Gilles Dartiguelongue (RETIRED) gentoo-dev 2009-10-17 17:25:57 UTC
(In reply to comment #4)
> notify-osd provides
> /usr/share/dbus-1/services/org.freedesktop.Notifications.service which is
> already provided by notification-daemon; so to be able to install the former,
> the latter has to be removed.
> 
> This causes a dependency problem since there are ebuilds explicitly depending
> on notification-daemon, among them x11-libs/libnotify and net-wireless/blueman.
> E.g. libnotify shoud be modified from
> 
> PDEPEND="|| ( x11-misc/notification-daemon
>         x11-misc/xfce4-notifyd )"
> 
> to
> 
> PDEPEND="|| ( x11-misc/notification-daemon
>         x11-misc/xfce4-notifyd
>         x11-misc/notify-osd )"
> 
> Should I open new bugs for each ebuild and make them block this one?

no, this is normal and will be changed if notify-osd enters the tree, you just have to copy the ebuild to your overlay and do the change to not be annoyed until then.

 
> Moreover, there is a bug with pidgin-libnotify which doesn't work correctly,
> the behaviour is similar to this http://666kb.com/i/b6lhhgwixpiknvgh1.png

This is not a bug but a difference in how notify-osd handles some aspects of the specification, please look for this in upstream bug tracker, there is most likeky open issues about various programs doing that (evolution, gnome-power-manager, ...)
Comment 6 Tommaso Pasini 2009-10-18 14:57:49 UTC
Created attachment 207486 [details, diff]
patch to make pidgin work with notify-osd

(In reply to comment #5)
> no, this is normal and will be changed if notify-osd enters the tree, you just
> have to copy the ebuild to your overlay and do the change to not be annoyed
> until then.

Of course, that's what I did, I was just suggesting that getting the ebuild into portage requires some extra work.

> 
> > Moreover, there is a bug with pidgin-libnotify which doesn't work correctly,
> > the behaviour is similar to this http://666kb.com/i/b6lhhgwixpiknvgh1.png
> 
> This is not a bug but a difference in how notify-osd handles some aspects of
> the specification, please look for this in upstream bug tracker, there is most
> likeky open issues about various programs doing that (evolution,
> gnome-power-manager, ...)
> 

I've found the solution: the problem is that pidgin-libnotify sends interactive messages but notify-osd only manages non-interactive ones, so pidgin-libnotify has to popup dialog windows.

I've found a patch here http://aur.archlinux.org/packages.php?ID=24562 which I slightly edited because the file paths at the top of the file are wrong. Now the notifications work; the only issue I see now is that notifications only appear one at a time (http://www.yalmagazine.org/homepage/_media/docs/notify-osd-screenshot.png -> this should be the correct behaviour) while, e.g., guifications shows more at the same time; maybe this is a bug in notify-osd code, I don't know.
You can reproduce this behaviour with a command like
notify-send "hello" && notify-send "hello2"

The "philosophical" problem about this patch is that the user can no more interact with the notifications, this can be seen as a regression; but the ebuild could just tell the user to install notification-daemon.

I don't have evolution so I can't tell anything about it, but networkmanager and gnome-power-manager work correctly.
Comment 7 Tommaso Pasini 2009-10-18 15:02:29 UTC
Created attachment 207488 [details, diff]
patch to reduce the default timeout for the notifications

I notice that the default timeout for the notifications is 10 seconds; added the time to fade in and fade out, it is even more, and it is definitely annoying. The only way to change this behaviour is patching the file defaults.c; the patch I'm uploading reduces the timeout to 3 seconds which is, I think, way better.
Comment 8 Gilles Dartiguelongue (RETIRED) gentoo-dev 2009-10-18 16:37:46 UTC
(In reply to comment #7)
> Created an attachment (id=207488) [details]
> patch to reduce the default timeout for the notifications
> 
> I notice that the default timeout for the notifications is 10 seconds; added
> the time to fade in and fade out, it is even more, and it is definitely
> annoying. The only way to change this behaviour is patching the file
> defaults.c; the patch I'm uploading reduces the timeout to 3 seconds which is,
> I think, way better.

this is wrong, notifications from notify-osd are really made to be even less intrusive that its predecessors, 10 seconds leaves the user the time to finish what he is doing and then read the popup, making it disappear after 3 seconds will get you the stress of looking at the notification fast enough before it disappears. This should probably be configurable but is something to be pushed upstream not here.
Comment 9 Tommaso Pasini 2009-10-18 18:04:29 UTC
(In reply to comment #8)
> 10 seconds leaves the user the time to finish
> what he is doing and then read the popup

Yeah, you mean, finish reading a whole book and stuff like that? :-)
Just try to use it with the 10 seconds timeout and tell me what you think, I got annoyed after maybe half an hour.
Comment 10 Gilles Dartiguelongue (RETIRED) gentoo-dev 2009-10-18 18:20:01 UTC
well I do use notify-osd on my laptop and desktop, and I think it's perfectly fine.
Comment 11 Tommaso Pasini 2009-10-18 18:37:32 UTC
And do you see only one notification at a time or is this a bug only on my system?
Comment 12 Gilles Dartiguelongue (RETIRED) gentoo-dev 2009-10-18 19:01:27 UTC
the example you provided produces only one notification indeed.
Comment 13 Tommaso Pasini 2009-10-18 19:11:50 UTC
I posted this before

notify-send "hello" && notify-send "hello2"

and it produces two messages. I see "hello" coming up, then the notification disappears and "hello2" comes up. I think they should be displayed all at once, shouldn't they?
Comment 14 Tommaso Pasini 2009-10-18 19:50:12 UTC
Sorry, I've found that the "one bubble at a time" behaviour is a feature and not a bug. So this is something dependent on upstream decisions and not something to be "resolved" here.
Comment 15 Matt Enright 2010-03-11 12:50:14 UTC
Slightly unrelated, but if there's interest going forward with getting notify-osd into the tree, is it worth considering adding a virtual/notification-daemon and an eselect wrapper for the daemon? Between the reference impl, notify-osd, the xfce daemon, and foreseeing the functionality being built into gnome-shell as well it seems like it wouldn't be the worst idea ever.
Comment 16 Gilles Dartiguelongue (RETIRED) gentoo-dev 2010-03-11 13:37:43 UTC
(In reply to comment #15)
> Slightly unrelated, but if there's interest going forward with getting
> notify-osd into the tree, is it worth considering adding a
> virtual/notification-daemon
yes, probably, but as there is only one place concerned a simple || () dep should do it just fine.

> and an eselect wrapper for the daemon? Between the
> reference impl, notify-osd, the xfce daemon, and foreseeing the functionality
> being built into gnome-shell as well it seems like it wouldn't be the worst
> idea ever.

that is not possible, each notify daemon installs it's own dbus service description and each daemon does not support what the other daemons do so the description is not interchangeable.

For the record, I've been using notify-osd for a while now and haven't seen much problem with it so I think at some point I'll just include it in the tree.
Comment 17 Pacho Ramos gentoo-dev 2010-04-11 15:19:38 UTC
*** Bug 314701 has been marked as a duplicate of this bug. ***
Comment 18 coderoar 2010-04-12 00:41:33 UTC
Created attachment 227445 [details]
x11-themes/notify-osd-icons-0.3.ebuild

icons for notify-osd
Comment 19 Gilles Dartiguelongue (RETIRED) gentoo-dev 2010-05-20 08:57:20 UTC
*** Bug 320697 has been marked as a duplicate of this bug. ***
Comment 20 rafnov 2010-07-08 08:48:44 UTC
Trying to emerge notify-osd from local overlay I get following block:

Calculating dependencies... done!
[ebuild  N    ] x11-misc/notify-osd-0.9.16  0 kB [1]
[blocks B     ] x11-misc/notification-daemon ("x11-misc/notification-daemon" is blocking x11-misc/notify-osd-0.9.16)

Total: 1 package (1 new), Size of downloads: 0 kB
Conflict: 1 block (1 unsatisfied)
Portage tree and overlays:
 [0] /usr/portage
 [1] /usr/local/overlay

 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  ('ebuild', '/', 'x11-misc/notify-osd-0.9.16', 'merge') pulled in by
    notify-osd

  ('installed', '/', 'x11-misc/notification-daemon-0.4.0-r1', 'nomerge') pulled in by
    x11-misc/notification-daemon required by ('installed', '/', 'x11-libs/libnotify-0.4.5', 'nomerge')

How do you fix this?
Comment 21 Tommaso Pasini 2010-07-08 09:05:45 UTC
Notify-osd and notification-daemon are mutually exclusive, to install one the other must not be installed.

Remember that there are ebuilds depending on notification-daemon, you have to edit those to depend on notify-osd.
Comment 22 blackdream 2010-07-25 00:07:55 UTC
(In reply to comment #18)
> Created an attachment (id=227445) [details]
> x11-themes/notify-osd-icons-0.3.ebuild
> 
> icons for notify-osd
> 

how to use it?
Comment 23 Samuli Suominen (RETIRED) gentoo-dev 2011-03-13 11:48:55 UTC
0.9.30 in portage