Package Details: notify-osd-customizable 0.9.35-3

Git Clone URL: https://aur.archlinux.org/notify-osd-customizable.git (read-only)
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
Licenses: GPL
Conflicts: notify-osd
Provides: notification-daemon, notify-osd
Submitter: 4javier
Maintainer: 4javier
Last Packager: 4javier
Votes: 113
Popularity: 1.133999
First Submitted: 2010-05-28 12:02
Last Updated: 2015-06-08 10:35

Required by (33)

Sources (2)

Latest Comments

4javier commented on 2015-05-20 14:01

For me it works. Probably there's something strange in your system configuration. I'm sorry, but I can't do anything about it.

joacoej commented on 2015-05-20 13:29

I unisnstalled. Anyway, my ~/.notify-osd is exactly as it comes for default.
If you find a way to do it, please send me an email.
Thank you

4javier commented on 2015-05-17 18:26

can you post your ~/.notify-osd?

joacoej commented on 2015-05-17 18:02

No, I don't.

4javier commented on 2015-05-17 09:11

Make this test:
1) open a terminal and issue "notify-send test"
2) lower volume

Do you see two notifications stacked?

joacoej commented on 2015-05-17 04:47

Yes, dynamic, I confused. Anyway, it doesn't stack. Probably, it was programed to work this way, I read some threads regarding this function, but they couldn't make it to stack notifications, even in Ubuntu.

4javier commented on 2015-05-15 19:47

dYnamic

joacoej commented on 2015-05-15 18:32

I'm not sure it's strange, because it's not the first time I see a tutorial telling people to do something with that folder (/etc/skel) and, according to other people's comments, I'm not the only one finding it empty.

I tried to set slot-allocation to dinamic, but it didn't wotk. Mayve it just works like this nad one have to reprogram it if one wants it to work different.

4javier commented on 2015-05-15 17:28

This package doesn't install the conf file into /usr/share, but it's strange that you don't find it in /etc/skel. Post pacman -Ql notify-osd-customizable

1)
Try to set into the same file
slot-allocation = dynamic

2)
I don't know

joacoej commented on 2015-05-15 16:01

Anyway, I did what you said and changed the ~/.notify-osd and added "bubble-close-on-click = 1" and it now works fine, but just with composite activated.
What I changed last time wasn't this archive, but another, I don't remember the folder where the archive was, but probably was /usr/share.

Thank you very much

if it doesn't bother you, I have some more questions:
1) Is there a way to watch more than one notification at the same time? I can only watch one at the time, becasue they don't stack. For example, if I decrease the volume I can see the notification, but if, before the volume notification fades out, I increase the screen brightness, I can't watch this notification.

2) Is there a way of making "bubble-close-on-click" work without composite?

joacoej commented on 2015-05-15 15:48

I went to /etc/skel, but the folder is completely empty.

4javier commented on 2015-05-15 15:04

You shouldn't add any line. Just copy /etc/skel/.notify-osd into your home ~/.notify-osd, and change te value of bubble-close-on-click (already present in the file) to 1.

joacoej commented on 2015-05-15 14:47

Hello 4javier. I would like to know how did you get to make the bubble close on click.
I tried activating composite and adding this line to the notify-osd-customizable configuration archive:
bubble-close-on-click = 1

and then I tried with:
bubble-close-on-click = 0

But it didn't work.

Thank you.

4javier commented on 2014-11-10 19:27

it happens for every notifications?

xorgx3 commented on 2014-11-10 14:29

yes, every. vlc, chromium, firefox, totem. this same is with any other notifcation daemon like xfce4-notifyd.

4javier commented on 2014-11-10 13:16

I use a mixed system based on openbox. I have many components of xfce installed.
Do you have this problem with every application running in fullscreen?

xorgx3 commented on 2014-11-10 13:04

it probably depends of desktop manager. I am using xfce4, and you?
It working if i previous run notification, and then open fullscreen. If i want open notification when fullscreen is present, it doesn't work.

4javier commented on 2014-11-10 11:47

just tried vlc playingi n fullscreen, and my notifications show up.

xorgx3 commented on 2014-11-09 21:08

only for me notifications doesn't appears when i use apps in fullscreen?

4javier commented on 2013-10-26 00:53

Updated.
A patch to fix this bug https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1191565 has been added.

4javier commented on 2013-10-26 00:52

Updated.
A patch to fix [url=https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1191565]this bug[/url] has been added.

carstene1ns commented on 2013-10-26 00:22

Seems there is a new build, don't know if something changed, though.
0.9.35+13.10.20130917.1-0ubuntu1-leolik~ppa0

gothmog.todi commented on 2013-10-16 16:50

I found out what the problem was: (somewhat surprisingly) both of them only work with a composition manager running. I did not expect that to be necessary, at least not for bubble-close-on-click.

4javier commented on 2013-10-16 16:04

They work both.
bubble-prevent-fade seems to work upside-down... if I set it to 1, it let the bubble fade out when pointer hovers over it. If I set it to 0, bubble reamins solid.

bubble-close-on-click works as expected.

Remember to kill notify-osd process for the changes to take effect.

gothmog.todi commented on 2013-10-16 13:27

Does this actually work for anybody? Neither "bubble-prevent-fade" nor "bubble-close-on-click" seem to have any effect on the notification pop-ups on my system. Is there some other setting I have to set?

yulrizka commented on 2013-10-16 11:45

This page explain what capability this package does

http://www.webupd8.org/2013/04/configurable-notifyosd-updated-for.html

4javier commented on 2013-07-26 13:36

Just a repackaging to correct the url. Now it points to leolik launchpad page, where customization options are listed, instead that to notify-osd upstream page.

Anonymous comment on 2013-07-26 11:59

hey, the description says "with leolik patch added" and that it "allows you to customize", but where does it give any details on that actual patch or in what way you can actually "customize" please? Does it allow a custom "-t <delay>" for user-defined notifications which stock notify-osd will gladly ignore? Maybe a link to it if no documentation exists?
Please be more verbose about what this package actually allows you to do so I don't have to download/build it to find out.

4javier commented on 2013-07-14 23:22

It's correctly listed as makedepend.

Anonymous comment on 2013-07-13 19:29

It seems that gnome-common is also a dependency, but isn't listed above.

4javier commented on 2013-01-26 17:57

added confilcts field, fixed automake problem thanks to nitropowered.

OramahMaalhur commented on 2013-01-26 17:31

Hello
Please add into PKGBUILD
conflicts=('notify-osd')

Anonymous comment on 2013-01-26 11:10

There is no need to create new files for the automake problem. Just export AUTOMAKE env variable before installing from shell.

export AUTOMAKE=automake

4javier commented on 2013-01-24 12:17

There's an upstream problem with gnome-autogen.sh: it has hardcoded inside the automake package versions to look for. Current version for Arch is 1.13, but it doesn't check over 1.12.
https://bugzilla.gnome.org/show_bug.cgi?id=690920
This issue has already pointed out to devs, but they prefer to wait for an upstream fix.
https://bugzilla.gnome.org/show_bug.cgi?id=690920
Same thing occurs for aclocal-1.13
The possible solutions for me would involve really dirty hacks which i prefer to avoid. So sorry, but if you want to build this package at this time, you have to create two symlinks to point to newer versions of these executables.

ln -s /usr/bin/automake-1.13 /usr/bin/automake-1.12
ln -s /usr/bin/aclocal-1.13 /usr/bin/aclocal-1.12

Otherwise, you have to wait for a gnome-common package update.

4javier commented on 2013-01-24 12:16

There's an upstream problem with gnome-autogen.sh: it has hardcoded inside the automake package versions to look for. Current version for Arch is 1.13, but it doesn't check over 1.12.
https://bugzilla.gnome.org/show_bug.cgi?id=690920
This issue has already pointed out to devs, but they prefer to wait for an upstream fix.
https://bugzilla.gnome.org/show_bug.cgi?id=690920
Same thing occurs for aclocal-1.13
The possible solutions for me would involve really dirty hacks which i prefer to avoid. So sorry, but if you want to build this package at this time, you have to create two symlinks to point to newer versions of these executables.

ln -s /usr/bin/automake-1.13 /usr/bin/automake-1.12
ln -s /usr/bin/aclocal-1.13 /usr/bin/aclocal-1.12

Alittlemurkling commented on 2013-01-23 18:03

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

4javier commented on 2012-11-15 18:28

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

lahwaacz commented on 2012-08-29 09:49

I think this package doesn't need dconf as dependency, it works fine without it...

4javier commented on 2012-06-26 10:27

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

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

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

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

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

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%

4javier commented on 2012-06-20 21:42

@nikolardo
could you post please your .notify-osd?

nikolardo commented on 2012-06-20 21:28

@4javier
Yes, manually editing ~/.notify-osd causes the same problem.

4javier commented on 2012-06-20 17:51

Other programs that use notification have the problem too? Could you post the code of your program involved into this?

dkasak commented on 2012-06-19 18:33

4javier, I just tried it. It runs fine with the new vanilla notify-osd and there's no error message. I'll try testing some more later.

dkasak commented on 2012-06-19 18:33

4javier, I just tried it. It runs fine with the new vanilla notify-osd and there's no error message. I'll try testing some more later.

4javier commented on 2012-06-19 18:10

@nikolardo
did you try to manually edit ~/.notify-osd instead of using notifyconf?
@dkasak
do you have the same error with classical notify-osd package https://aur.archlinux.org/packages.php?ID=25256 ? (Updated pkgbuild is linked inside last comment)

dkasak commented on 2012-06-19 15:20

Confirming that there is a problem with the latest update. My Python app which uses pynotify spits out this when I try to run it:

glib.GError: Error calling StartServiceByName for org.freedesktop.Notifications:
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process /bin/sh exited with status 127

dkasak commented on 2012-06-19 15:20

Confirming that there is a problem with the latest update. My Python app which uses pynotify spits out this when I try to run it:

glib.GError: Error calling StartServiceByName for org.freedesktop.Notifications:
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process /bin/sh exited with status 127

nikolardo commented on 2012-06-16 00:04

Since the most recent update, notifications do not display. If I remove the notifyconf configuration file and reboot, I'll get standard white-on-grey notifications, but if I change anything in notifyconf (I like black text on white) and save, notifications no longer appear.

4javier commented on 2012-06-06 17:02

Not on my system. Did you clean your build directory?

American_Jesus commented on 2012-06-06 16:52

still need to be build with sed -i 's,/usr/lib/notify-osd/,@LIBEXECDIR@/,' data/org.freedesktop.Notifications.service.in

4javier commented on 2012-06-05 14:35

From changelog of 0.9.34 version
"5) New option from Ubuntu 12.04:
bubble-as-desktop-bg: Used Dash background color for bubble background color"
I think it works just with unity. Disabled by default.

4javier commented on 2012-05-17 21:00

vote for it https://bugs.archlinux.org/task/29935

hexadecagram commented on 2012-05-17 20:34

It also happens for xfce4-notifyd. Thank you for filing the bug report.

4javier commented on 2012-05-17 09:48

Hi, thanks for your report.
Probably is pacman's fault. If you try to install the gnome group, notification-daemon is not a dependency, but a package belonging to that group, so pacman treats it as if you're requesting explicit installation of the package, ignoring provide field. If you ask No to answer due to conflict field, it recognizes a generic problem about dependency chain and abort the operation. If nobody has a better explanation, I'll file a bugreport.

hexadecagram commented on 2012-05-17 06:34

Greetings,

I am able to build and install this just fine. However, if I try to install packages gnome and gnome-extra *afterward,* I get:

resolving dependencies...
looking for inter-conflicts...
:: notification-daemon and notify-osd-customizable are in conflict. Remove notify-osd-customizable? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: notification-daemon and notify-osd-customizable are in conflict

I commented-out the conflicts line in PKGBUILD, and pacman attempts to install notification-daemon, which I would rather not use. I also reversed the order of the conflicts and provides lines, to no avail. Adding notification-daemon to the IgnorePkg line in /etc/pacman.conf is a successful workaround.

It seems that PKGBUILD's conflicts and provides directives are not doing what is expected for this package.

4javier commented on 2012-04-17 13:02

Leolik told me that he still support notify-osd, and that he will update the patches meantime next ubuntu release. Be patient.

4javier commented on 2012-04-16 21:03

The only thing I have been able to fix, has been background color. Slot-allocation and expiration time i.e don't work. I don't want to release a new version with these limitations. I'll try to contact leolik.

4javier commented on 2012-04-16 20:27

Trying again I figured out that my config file is not ignored at all, but some options doesn't work (e.g. bubble-background-color and slot-allocation). I'll try to debug and update the patches. Every help is welcome.

misc commented on 2012-04-16 19:37

I didn't do anything else, actually. It prints "reading settings from '/home/mememe/.notify-osd'" if started via the console and observes settings in that file (like "bubble-vertical-gap" and "bubble-close-on-click") as well as changing the gravity via gsettings. Haven't tested everything, though.

misc commented on 2012-04-16 19:36

I didn't do anything else, actually. It prints "reading settings from '/home/andreas/.notify-osd'" if started via the console and observes settings in that file (like "bubble-vertical-gap" and "bubble-close-on-click") as well as changing the gravity via gsettings. Haven't tested everything, though.

4javier commented on 2012-04-16 17:39

@misc
How did you built the package? I just applied the two patches to 0.9.34 and make goes fine, but when I install the package my ~/.notify-osd is ignored.

misc commented on 2012-04-16 15:41

@4javier: I've been using 0.9.34 since March now without any problems. .33 and .34 contain a number of important fixes, btw.

Anonymous comment on 2012-04-15 19:39

> even with solution that grimp3ur said

Hm, notify-osd_0.9.32-0ubuntu3-leolik~ppa1.tar.gz, just rechecked: works for me.
Are you using dconf or gsettings (via legacy gconf-backend)? // I didn't try dconf

Anonymous comment on 2012-04-02 14:20

gravity = 3 doesn't work for me - even with solution that grimp3ur said.

@hund - install xcompmgr to remove black borders

4javier commented on 2012-03-31 09:44

I'll wait a couple of days, then I'll apply the patch manually to last notify-osd.

misc commented on 2012-03-30 21:24

The two patches still apply fine to 0.9.34.

Anonymous comment on 2012-03-23 20:14

As for gravity = 3 issue, works if one comment out these lines from stack.c:

if (defaults_get_gravity (self->defaults) == GRAVITY_SOUTH_EAST)
bubble_get_position(bubble, &temp_x, &temp_y);

It's little bizarre, since it was after gravity-switch, but no symmetrical code for south-west
(i'm too lazy to properly examine the code).

//BTW: if you don't like dconf, you can use export GSETTINGS_BACKEND=gconf (of course, kludge)

nikolardo commented on 2012-02-24 17:35

Yeah, all set, sorry to bother.

4javier commented on 2012-02-24 17:22

just tried
==> Download dei sorgenti in corso...
-> Download di notify-osd_0.9.32-0ubuntu3-leolik~ppa1.tar.gz in corso...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 475k 100 475k 0 0 203k 0 0:00:02 0:00:02 --:--:-- 424k
-> È stato trovato notify-osd
Probably the server was down when you was building? Retry, please.

4javier commented on 2012-02-24 17:21

just tried
==> Download dei sorgenti in corso...
-> Download di notify-osd_0.9.32-0ubuntu3-leolik~ppa1.tar.gz in corso...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 475k 100 475k 0 0 203k 0 0:00:02 0:00:02 --:--:-- 424k
-> È stato trovato notify-osd
Probably the server was down when you was build? Retry, please.

nikolardo commented on 2012-02-24 17:00

curl: (52) Empty reply from server
==> ERROR: Failure while downloading notify-osd_0.9.32-0ubuntu3-leolik~ppa1.tar.gz
Aborting...
The build failed.

4javier commented on 2012-02-11 12:24

Thanks porc, I had already noticed exactly the same behaviour. The only thing I can do, it's to file a bug to leolik on launchpad, because gravity more than 2 are not allowed for the original notify-osd by canonical. This is why you don't find any report. I'll use directly this last comment of yours that's quite explanatory. :)

Anonymous comment on 2012-02-10 14:35

It happens to me with compiz and avant-window navigator, and also with no panel at all.
I've noticed that the notifications will show only if I send the notifications while it is set on another corner.
For example: gravity is set to 1
Send 10 notifications. Let it show 3 of them.
Set gravity to 3.
It'll show the other 7 notifications, but no more if I send them when gravity is already set to 3.
My first thought was that it is an upstream bug, but it seemed strange not to find any report anywhere.

4javier commented on 2012-02-09 11:19

I just find out that I have this problem too. :/
Please, everyone who uses this package could try if it's a generic problem, or if it happens only in specific circumnstances?
Set gravity to 3:
gsettings set com.canonical.notify-osd gravity 3
test new settings:
notify-send test -t 2000
For me it just worked a couple of time. I use openbox, cairo-compmgr and tint2. (I think one of these could be the culprit.)

Anonymous comment on 2012-02-08 16:06

I can't see the notifications when i set them to show in the bottom-right corner. I think that's what ali was trying to say. I can see them when i set them on the other positions.

4javier commented on 2012-01-20 01:11

Oh, so this was the error Berseker complained about, too. My apologise to Yaourt, he's a clean guy :D
Fixed.

ixaphire commented on 2012-01-19 21:48

==> ERROR: Invalid syntax for optdepend : 'notifyconf:gui to customize notifies appearence'

Please put one space after a colon ;)

4javier commented on 2011-12-18 19:06

explain deeply your problem, please.

ali commented on 2011-12-17 22:26

I have a problem with setting the "gravity 3" other work.

Lorem-Ipsum commented on 2011-12-16 14:41

Thanks, working now.

4javier commented on 2011-12-14 18:20

clean your build directory and try again, that's the problem fixed by last pkgrel.

Lorem-Ipsum commented on 2011-12-14 17:16

The build fails for me with:

/usr/bin/ld: test_modules-exponential-blur.o: undefined reference to symbol 'expf@@GLIBC_2.2.5'
/usr/bin/ld: note: 'expf@@GLIBC_2.2.5' is defined in DSO /lib/libm.so.6 so try adding it to the linker command line
/lib/libm.so.6: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
make[2]: *** [test-modules] Error 1
make[2]: Leaving directory `/tmp/yaourt-tmp-llawwehttam/aur-notify-osd-customizable/src/notify-osd-0.9.32/tests'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/yaourt-tmp-llawwehttam/aur-notify-osd-customizable/src/notify-osd-0.9.32'
make: *** [all] Error 2

4javier commented on 2011-12-12 21:46

Probably yaourt is on drugs. From man pkgbuild

optdepends (array)
An array of packages (and accompanying reasons) that are not
essential for base functionality, but may be necessary to make full
use of the contents of this package. optdepends are currently for
informational purposes only and are not utilized by pacman during
dependency resolution. The format for specifying optdepends is:

optdepends=('fakeroot: for makepkg usage as normal user')

Obviously, if you find an official source for this rule, I'll update the PKGBUILD. :)

Berseker commented on 2011-12-12 21:16

optdepends=('notifyconf:gui to customize notifies appearence')

yaourt warns that the part after ":" is to be removed, I modified in

optdepends=('notifyconf')

in order to make it work

4javier commented on 2011-12-12 18:55

what's the problem with optdepends?

Berseker commented on 2011-12-12 18:41

please fix optdepend section :)

4javier commented on 2011-12-12 16:52

explain deeply your problem, and which versions show it.

Hund commented on 2011-12-12 16:26

I still have problems with black borders.

4javier commented on 2011-12-12 13:57

Shame on me...could I use the fact that I was joking with code at 3.00 A.M. as an extenuating circumnstance? :D
(P.s. I've been able to break my MBR too, at the same time -.-" )
Now 0.9.32-3 builds and works.

chmurli commented on 2011-12-12 06:02

lol dude,. here you can find all history od given pkg: http://pkgbuild.com/git/aur.git/tree/notify-osd-customizable click 'log'

4javier commented on 2011-12-12 01:59

ehmmm....don't update to 0.9.32-2, I erroneusly deleted last fix. Please, could someone post the PKGBUILD of 0.9.32-1 ? I accidentally removed it :lol:

4javier commented on 2011-12-11 22:42

Compilation issue fixed. I just copied the workaround from notify-osd AUR package (again :) ), 'cause I'm too idle to sed-manipulate this three files :P
http://bazaar.launchpad.net/~canonical-dx-team/notify-osd/oneiric/revision/444

chmurli commented on 2011-12-11 19:28

H, I have got error:
CCLD test-modules
/usr/bin/ld: test_modules-exponential-blur.o: undefined reference to symbol 'expf@@GLIBC_2.2.5'
/usr/bin/ld: note: 'expf@@GLIBC_2.2.5' is defined in DSO /lib/libm.so.6 so try adding it to the linker command line
/lib/libm.so.6: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
make[2]: *** [test-modules] Error 1

4javier commented on 2011-10-24 23:54

The problem is that notify-osd devs in this version hardcoded the address of the libexec directory, but let in the /data/Makefile.am this code
org.freedesktop.Notifications.service: org.freedesktop.Notifications.service.in
sed "s,@LIBEXECDIR@,$(libexecdir)," $< > $@
Thus, I think it's just an oversight.

American_Jesus commented on 2011-10-24 23:48

I had not realized that after running the notify-osd was normal that everything works itself
but now it works with the new fix, also tried logoff/login this time

4javier commented on 2011-10-24 23:47

Thanks American_Jesus, but I already solved the issue in a cleaner way. Thanks for your support and good night. :)

American_Jesus commented on 2011-10-24 23:46

I had not realized that after running the notify-osd was normal that everything works itself
but now it works with the new fix, also tried logoff/login this time

American_Jesus commented on 2011-10-24 23:39

fixed org.freedesktop.Notifications.service and org.freedesktop.Notifications.service.in, now is working fine.
Here's PKGBUILD http://pastie.org/pastes/2753466/text
and /usr/share/dbus-1/services/org.freedesktop.Notifications.service http://pastie.org/pastes/2753470/text

4javier commented on 2011-10-24 23:18

-.-"
It works just 'cause you first explicitly launch /usr/lib/notify-osd-customizable/notify-osd, creating the dbus session bus.
Try to reboot your system (or probably just logout/login) and to execute not that command. The program that uses notification will not find the bus: the better will be notification not displayed, the worst will be the program crashes.

American_Jesus commented on 2011-10-24 23:06

Sorry my fault, I was using 0.9.30 since 0.9.32 does not appear in the bottom-right corner

But still after upgrading to 0.9.32 everything works fine
i did this steps:
yaourt -U notify-osd-customizable-0.9.32-1-x86_64.pkg.tar.xz
pkill notify-osd
/usr/lib/notify-osd-customizable/notify-osd # to start notify-osd again
gsettings set com.canonical.notify-osd gravity 4 # 3 - bottom-right corner don't work
notify-send "Hello World"

and works fine, also tested with Turpial, Banshee and Pidgin (with pidgin-libnotify-notify-osd)

wheres my /usr/share/dbus-1/services/org.freedesktop.Notifications.service now with 0.9.32 http://pastie.org/2753334
It executes /usr/lib/notify-osd/notify-osd but is installed /usr/lib/notify-osd-customizable/notify-osd !

4javier commented on 2011-10-24 22:49

???
That's impossible. your $pkgdir/usr/share/dbus-1/services/org.freedesktop.Notifications.service is the wrong one. It executes /usr/lib/notify-osd/notify-osd
How can it becomes the right one on your filesystem??? During the pacman -U procedure??? WTF...
P.S.
Thanks for your time and your helpfulness.

American_Jesus commented on 2011-10-24 22:29

org.freedesktop.Notifications.service http://pastie.org/pastes/2753160/text

Here's my notify-osd-customizable with all build cached files http://dl.dropbox.com/u/785907/notify-osd-customizable.tar.gz

4javier commented on 2011-10-24 22:17

please post your $srcdir/notify-osd-0.9.32/data/org.freedesktop.Notifications.service.in
(I'm going crazy)

American_Jesus commented on 2011-10-24 21:31

pkglibexecdir = $(libexecdir)/notify-osd

I didn't change any of upstream files or applied any patch!

4javier commented on 2011-10-24 21:26

Into your compilation directory, could you please check the value of pkglibexecdir variable inside Makefile?

American_Jesus commented on 2011-10-24 20:47

# cat /usr/share/dbus-1/services/org.freedesktop.Notifications.service
[D-BUS Service]
Name=org.freedesktop.Notifications
Exec=/bin/sh -c 'if [ ! -x /usr/lib/notification-daemon/notification-daemon ] || [ "${GDMSESSION%.desktop}" = gnome ] || [ "${GDMSESSION%.desktop}" = gnome-classic ] || [ "${GDMSESSION%.desktop}" = guest-restricted ] || [ "${GDMSESSION%.desktop}" = gnome-classic-guest-restricted ] || [ "${GDMSESSION%.desktop}" = gnome-2d ] || [ "${GDMSESSION%.desktop}" = default -a "$(basename `readlink /etc/alternatives/x-session-manager`)" = gnome-session ] || [ "${GDMSESSION%.desktop}" = une ] || [ "${GDMSESSION%.desktop}" = unity-2d ]; then exec /usr/lib/notify-osd-customizable/notify-osd; else exec /usr/lib/notification-daemon/notification-daemon; fi'

I don't have any /usr/lib/notify-osd/notify-osd only /usr/lib/notify-osd-customizable/notify-osd

4javier commented on 2011-10-24 20:38

@American_Jesus
Thanks for your contri, it compiles perfectly. But after upgrade to this version, on my system notification doesn't work anymore and make apps that use it crash. I debugged the problem, it's because org.freedesktop.Notifications.service doesn't try to exec /usr/lib/notify-osd-customizable/notify-osd as before, but /usr/lib/notify-osd/notify-osd instead. Before I release this new version, I want to understand why this issue doesn't affect you.
Please, could you post your /usr/share/dbus-1/services/org.freedesktop.Notifications.service and tell me if on your system /usr/lib/notify-osd/notify-osd is present?

4javier commented on 2011-10-24 20:37

@American_Jesus
Thanks for your contri, it compiles perfectly. But after upgrade to this version, on my system notification doesn't work anymore and make apps that use it crash. I debugged the problem, it's because org.freedesktop.Notifications.service doesn't try to exec /usr/lib/notify-osd-customizable/notify-osd as before, but /usr/lib/notify-osd/notify-osd instead. Before I release this new version, I want to understand why this issue doesn't affect you.
Please, could you post your /usr/share/dbus-1/services/org.freedesktop.Notifications.service and tell me if on your system /usr/lib/notify-osd/notify-osd is present?

American_Jesus commented on 2011-10-24 17:25

I made a PKGBUILD and notify-osd-customizable.install instead of conf.install for 0.9.32

PKGBUILD http://pastie.org/pastes/2751599/text
notify-osd-customizable.install http://pastie.org/pastes/2751606/text

notify-osd bubbles are not working here in bottom-right corner, probably upstream issue, works in the rest of the corners.

alexmat commented on 2011-10-14 00:39

Thanks for giving it a shot.

4javier commented on 2011-10-13 09:53

I'm sorry, but I've just tried and patching fails, that diff is too old, probably /src/defaults.c changed many times during two years. You may ask to leolik if he's interested to fix and adopt it.

alexmat commented on 2011-10-13 08:46

Any chance of getting this font patch included?

https://bugs.launchpad.net/notify-osd/+bug/335383/comments/18

chneukirchen commented on 2011-08-26 13:46

For some reasons, after reinstalling, this displays in DjVu Serif now... any idea why it would not be Sans?

4javier commented on 2011-05-16 12:50

added two options to conf, disabled by default ('cause I don't like them :P ). Copy new .notify-osd from /etc/skel.

4javier commented on 2011-03-18 18:06

added a patch stolen from notify-osd package http://aur.archlinux.org/packages.php?ID=25256 to solve compilation issues. Thanks to those guys. I have no time to investigate what it actually does, but it works. :)

Anonymous comment on 2011-03-17 06:55

After upgrading to libnotify 0.7.1 I've got this:

make[2]: *** [test_modules-test-withlib.o] Error 1
make[2]: Leaving directory `/tmp/yaourt-tmp/aur-notify-osd-customizable/src/notify-osd-0.9.30/tests'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/yaourt-tmp/aur-notify-osd-customizable/src/notify-osd-0.9.30'
make: *** [all] Error 2
Aborting...
==> ERROR: Makepkg was unable to build notify-osd-customizable

4javier commented on 2010-12-07 12:13

Added one of the patch proposed for merging in future version of notify-osd, that solve pizman 0.20 problem (bubble's border cut), thanks to jarryson. Solved dotfile problem, I now hope the robot will not nuke my town anymore :P. Splitted building from packaging stage, like new packaging standards require. Deleted symlink of leolik patch, that was an error of mine :)
Everything should work now.

jarryson commented on 2010-12-07 03:08

https://code.launchpad.net/~pcjc2/notify-osd/fix_dropshadow/+merge/42804

please add this patch, fixed pixman 0.20 problem.

Anonymous comment on 2010-12-06 21:00

I am a robot. This is not an official message. You have accidentally tarred up some dotfiles. Examples:
.notify-osd
Suggestion: use "makepkg --source". Feel free to disregard this as you would any other comment. This robot will not post here again.

viniavila commented on 2010-12-06 16:12

It worked for me...
$ pacman -Qs pixman
local/pixman 0.18.4-1
Pixman library
And pixman blocked to upgrade in pacman.conf until new release for notify-osd.

4javier commented on 2010-11-27 11:45

Thamks revolt. I think i'll wait for a fix in next notify-osd release

AlexJF commented on 2010-11-27 10:59

The wrong shape is related to an incompatibility of notify-osd with pixman 0.20. Revert to 0.18 to fix it.

Anonymous comment on 2010-11-26 01:43

same here... shape looks like ugly

4javier commented on 2010-11-22 23:14

It just happened to me too. -.-'
Probably I didn't notice it before...

viniavila commented on 2010-11-22 16:37

Yes, for me, it happens with offical notification-osd too... It's not a problem with leolik's patch

4javier commented on 2010-11-22 13:00

Have you tried if this happens with official notification-osd package too? I don't think it's a problem of leolik patch.

caspian commented on 2010-11-21 21:08

All of a sudden my notify OSD bubble has wrong shape; like the down and right part of it was cut off. I didn't change anything in the configuration or anything. Here's the screenshot:
http://img228.imageshack.us/img228/5829/selection001q.png

Is anyone else experiencing this?

chiche commented on 2010-11-19 03:01

He subido una actualizacion del PKGBUILD para utilizar gnome-settings-daemon 2.32.1 http://aur.pastebin.com/rG9svEEh

4javier commented on 2010-10-13 16:32

First of all, try to build without yaourt, just by makepkg. Do you use some strange repo (testing and so on)?

Anonymous comment on 2010-10-13 13:44

I'm having troubles to build this one: http://aur.pastebin.com/3dzh0aZB

4javier commented on 2010-09-25 13:44

Pkgbuild deeply changed due to various reasons. I don't know if this patch is newer than the previous.

4javier commented on 2010-07-28 15:48

Sorry, but I get no error building manually by makepkg, pkgbuild is correct. Try to get some debug messages, so we can understand why packer fails.

Anonymous comment on 2010-07-14 13:24

Using packer I am told that "The build failed." Can't seem to find any errors.

4javier commented on 2010-07-06 21:18

I was sure it already did it. :/ Probably I was wrong. Fixed and updated to last leolik patch (ppa3)

Anonymous comment on 2010-07-06 18:01

Shouldn't provides be notify-osd? I had to customize checkgmail-notify-osd because of that.

4javier commented on 2010-05-29 12:30

The patch created by leolik let you customize the notify-osd appearence without re-compile the software.

4javier commented on 2010-05-28 14:22

I added this patch to notify-osd (i'm NOT the creator of the patch), so the daemon is configurable.

4javier commented on 2010-05-28 12:07

I added this patch to notify-osd (i'm NOT the creator of the patch), so the daemon is configurable. To do that, just create a file called .notify-osd in your home directory
Here http://aur.pastebin.com/7UEq7VAY the default settings to make it behave like in Karmic Koala and Lucid Linx