Package Details: notify-osd-customizable 0.9.35-6

Git Clone URL: https://aur.archlinux.org/notify-osd-customizable.git (read-only, click to copy)
Package Base: notify-osd-customizable
Description: daemon that displays passive pop-up notifications, with leolik patch added
Upstream URL: https://launchpad.net/~leolik/+archive/leolik
Keywords: eol to-be-deleted unmaintained unneeded
Licenses: GPL
Conflicts: notify-osd
Provides: notification-daemon, notify-osd
Submitter: 4javier
Maintainer: MarsSeed
Last Packager: 4javier
Votes: 122
Popularity: 0.000000
First Submitted: 2010-05-28 12:02 (UTC)
Last Updated: 2018-10-19 10:21 (UTC)

Required by (36)

Sources (2)

Pinned Comments

MarsSeed commented on 2024-01-28 23:09 (UTC)

This is an old variant version of extra repo's notify-osd.

Dear users, please kindly migrate to that package, or to another notification-daemon.

4javier commented on 2020-04-13 21:00 (UTC)

@dreamkey I'm sorry but I don't use this package anymore. And the last release of the original library is from 2012. I'd suggest to look for an alternative.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 15 Next › Last »

11backslashes commented on 2013-01-23 18:03 (UTC)

Building fails for me, as it is not detecting automake-1.13 as a valid version.

4javier commented on 2012-11-15 18:28 (UTC)

Updated. Modfied versioning a little to be more coherent, this could break aur helpers recognition during first update to new version.

4javier commented on 2012-06-26 10:27 (UTC)

Problem solved. As American_jesus told some comments ago, libexec workaround is still needed. The only difference from last release, is that I uncommented the sed line. On my system this problem didn't happen probably because I didn't remove the package with pacman -R before installing the new one with pacman -U, and the file didn't get overwrited. This seems to me a strange behaviour that should be investigated. Any help is appreciated.

nikolardo commented on 2012-06-25 11:24 (UTC)

When using notify-send without launching notify-osd first, terminal gives no messages at all. (It doesn't stall there either, it just moves on as if it was executed perfectly.)

4javier commented on 2012-06-24 22:09 (UTC)

The behaviour you expect is exactly what it does on my system. If you try to notify-send without launch /usr/lib/notify-osd-customizable/notify-osd first, what it outputs on terminal?

nikolardo commented on 2012-06-24 18:28 (UTC)

It's working now! I think it was failing to start on its own - when using the plain notify-osd package, killing it and then using notify-send would launch a notification, with this one I have to manually start it the way you mentioned, whereas earlier it would start on its own when called through notify-send. So I'll just start it at boot! Thanks!

4javier commented on 2012-06-21 21:00 (UTC)

on my system your .notify-osd works like a charm :-/ Try to kill notify-osd and to re-launch it in a terminal through /usr/lib/notify-osd-customizable/notify-osd. Then post the output. You can also try to launch a notification from terminal with notify-send hello world

nikolardo commented on 2012-06-21 20:46 (UTC)

slot-allocation = fixed bubble-expire-timeout = 10sec bubble-vertical-gap = 5px bubble-horizontal-gap = 5px bubble-corner-radius = 37,5% bubble-icon-size = 30px bubble-gauge-size = 6px bubble-width = 240px bubble-background-color = ffffff bubble-background-opacity = 90% text-margin-size = 10px text-title-size = 100% text-title-weight = bold text-title-color = 000000 text-title-opacity = 100% text-body-size = 90% text-body-weight = normal text-body-color = 000000 text-body-opacity = 100% text-shadow-opacity = 100%

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 15 Next › Last »