Hello,

I wanted notification-daemon to start as user classic service, not from .xinitrc as usually do. Made classic service using obexd service from bluetoothd-s6serv package, as a pattern and enabled it. But didn't succeed, because of:

1. message from: s6opts list

notification-daemon :: down (exitcode 1) 0 seconds, normally up, want up, ready 0 seconds

2. message from: log file

@ 40000 ... Unable to init server: Could not connect: Connection refused
@ 40000 ... (notification-daemon:9916): Gtk-WARNING **: 09:41:34.145: cannot open display:

Some lessons are skipped to learned, obviously. Any help?

Thanks.
no your fault, i think a bug is here about the load of the environment, i need to investigate it...
6 days later
yes, trouble exist for the inherit of the global environment variable.
Anyway change your run file by this one 
# !/usr/local/bin/execlineb -P
fdmove -c 2 1
importas -i display CK_SESSION_X11_DISPLAY 
importas -i USER USER
export DISPLAY $display 
export XAUTHORITY /home/${USER}/.Xauthority 
/usr/lib/notification-daemon-1.0/notification-daemon
this should work
... yes, it works in jwm environment, but as I do not utilize jwm, it don't works for me. Many thanks anyway.
can you explain me the link between the service and the WM?
May you explain what you use and your purpose?
... your last question answer first ...

@ May you explain what you use and your purpose?

... my motif for starting notification-daemon as user service and not from .xinitrc, as intended, was curiosity and practising s6 possibilities ...

... and, logically, your first question answer last ...

@ can you explain me the link between the service and the WM?

... could not start notification-daemon service after applied your finding to run file, with the same messages of error ... after that installed notification-daemon service in latest Obarun live iso, again just for curiosity, disabled starting it from jwm-start file and enabled it by s6opts ... and discovered that works perfectly ... So, obviously, in jwm evironment works and in my custom (no:openbox, jwm, xfce4 or plasma) don't.

Again, many thanks, as you allready provided viable extra solution for arch wiki recomendation of starting notification-daemon, for users that don't have DE.
a month later
Hello Eric,

yesterday while I was tinkering again to solve the problem, discovered that after removing
session optional pam_ck_connector.so noX11
from the end of /etc/pam.d/system-login file, I was able to start notification-daemon as user classic service.

It was appended there following this, and because I don't utilize display manager, albeit I was aware of
Note: This specific change at the /etc/pam.d/system-login isn't necessary depending of your .xinitrc declaration file or if you use a display manager.
Now I am wonder ... whether the lesson wasn't learned well or wasn't written well, or the devil is in the detail ... as always is?
Now I am wonder ... whether the lesson wasn't learned well or wasn't written well, or the devil is in the detail ... as always is?
Maybe the three :)

By the way, the corresponding sentence was rectified on the wiki

Powered by Obarun