0.7.0B3 Unable to activate NotifyOSD

[mgori]

Hello,

For some reason I am unable to activate NotifyOSD in 0.7.0B3. I have the NotifyOSD packages installed. Anyone also have this issue?

ubuntu:/mnt/dlinkfs/TV$ dpkg --get-selections | grep notify-osd
notify-osd install
notify-osd-icons install

Version: 0.7.0B3
OS: Ubuntu 11.10
Install: Linux repo
Skin: Plush
Firewall: N/A

[jcfp]

I think running the program with --daemon disables that setting automagically, with the setting checked but greyed out.

[shypike]

I think running the program with --daemon disables that setting automagically, with the setting checked but greyed out.

It shouldn't, I'll check.

[shypike]

I checked on my out-of-the-box Ubuntu 11.10 and "Notification" just works.
In plain mode and in daemon mode.
At least it does when running from source, I haven't checked the package.
Could there be user account issues, where SABnzbd uses another account than
the current interactive user?

[jcfp]

On closer inspection, this issue seems to be restricted to sab processes started by the init script, and in recent ubuntu releases only. In a 10.04 vm, it still works all the way, but in 11.10 even when the user running the program is the same as the desktop user, it won't display notifications for a sab process started from init. When starting from a shell notify works with and without --daemon though, at the very least for the logged-in desktop user. I suspect this could be an intentional modification on the ubuntu end somewhere, or it's a result of differences in the process' environment, particularly the presence of certain environment vars related to Xorg.

*** edit: think I found the problem ***
mgori: assuming you are indeed running sab as a service, try adding "export DISPLAY=:0.0" to /etc/default/sabnzbdplus. Without the quotes, on a line by itself. The display is usually 0.0 - if not, find the correct one by running echo $DISPLAY in a terminal. Don't know if this will work with processes started before there's any display active to begin with (i.e., the sab service on system boot), but at least it seems to fix things when restarting the service from the active desktop environment.

[mgori]

Yes I am running both SAB as a service. I will try what you mentioned. Thanks for the great support/help.