CrunchBang Linux

Beepmode

Member

Registered: 2012-03-15

Posts: 42

[SOLVED] notify-osd has died?

I'm trying to get notifications (the bubbles that appear in the top-right corner) to do what I want but got in a bit of a muddle. It seems they've disappeared altogether.

I tried following these instructions: http://crunchbanglinux.org/forums/topic … ze-stable/.

However, when I run

notify-send test

or

notify-send test "Hello World"

bash says "notify-send: command not found".

I've checked if I got notify-osd installed:

apt-cache policy notify-osd:
  notify-osd:
  Installed: 0.9.34-2
  Candidate: 0.9.34-2

I then had a look at twmn (http://crunchbanglinux.org/forums/topic/15684/twmn/) but got stuck because there are unmet dependencies:

sudo apt-get install qt4-qmake libqt4-dev libboost1.49-dev libdbus-1-dev libxext-dev \
libboost-program-options1.49-dev libboost-system1.49-dev
libdbus-1-dev : Depends: pkg-config but it is not going to be installed
libxext-dev : Depends: libx11-dev but it is not going to be installed.

So, question is, how do I get notify-osd to work? Is there any way I can check whether or not it's still alive (display a dummy message)? Or is there a way to get twmn installed?

Last edited by Beepmode (2012-07-07 10:23:14)

pidsley

Window Mangler

Registered: 2012-05-23

Posts: 1,752

Re: [SOLVED] notify-osd has died?

What version of #! are you using? You have posted in the testing/unstable section, so I assume you are using Waldorf? But then I am confused, because the notify-osd instructions you reference are for Debian Squeeze (stable) Please post output of

uname -r

If you are using Waldorf, you are correct that it no longer uses notify-osd. Waldorf uses xfce4-notifyd.

You can send test messages like this:

notify-send -i info Information "Hi ${USER}, This is a Test"

What happens if you type this in a terminal:

cb-fortune

Last edited by pidsley (2012-07-03 21:27:29)

---

words to live by

Beepmode

Member

Registered: 2012-03-15

Posts: 42

Re: [SOLVED] notify-osd has died?

If you are using Waldorf, you are correct that it no longer uses notify-osd. Waldorf uses xfce4-notifyd.

No, I'm on CrunchBang 10 statler. Had a quick look at http://packages.debian.org/sid/xfce4-notifyd and it looks promising - will try and install it later.

pidsley

Window Mangler

Registered: 2012-05-23

Posts: 1,752

Re: [SOLVED] notify-osd has died?

OK, you posted in the wrong subforum, but no big deal. You might also look at dunst (another simple notify system): http://crunchbanglinux.org/forums/topic … on-system/

Last edited by pidsley (2012-07-03 21:31:26)

---

words to live by

Beepmode

Member

Registered: 2012-03-15

Posts: 42

Re: [SOLVED] notify-osd has died?

What happens if you type this in a terminal:

cb-fortune

This:

beep@crunchbang:~$ cb-fortune

** (process:2377): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'

** (process:2377): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags'

** (process:2377): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags'
/usr/bin/cb-fortune:30: Warning: (/tmp/buildd/glib2.0-2.32.3/./glib/gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0)
  if not n.show():
Traceback (most recent call last):
  File "/usr/bin/cb-fortune", line 30, in <module>
    if not n.show():
glib.GError: Unable to connect to server

No idea what it means. Did I break something?

Beepmode

Member

Registered: 2012-03-15

Posts: 42

Re: [SOLVED] notify-osd has died?

OK, you posted in the wrong subforum, but no big deal. You might also look at dunst (another simple notify system): http://crunchbanglinux.org/forums/topic … on-system/

Much obliged, will check that one as well.

Apologies for posting this in the wrong forum - still haven't got my head round stable / unstable etc. (I started worrying about the notifications because Icedove has it's own, rather ugly, notifications - and my Icedove is from the unstable repo. Hence I blindly assumed this was the right forum).

Last edited by Beepmode (2012-07-03 22:17:31)

Tuber

#! Member

From: Kapolei, Hawaii

Registered: 2012-02-03

Posts: 93

Re: [SOLVED] notify-osd has died?

No, I'm on CrunchBang 10 statler. ...

...my Icedove is from the unstable repo...

This is likely where your problems lie. The above implies you have both stable and unstable repos enabled. It's best to stick with one or the other to avoid dependancy issues. If there is some compelling reason to use Icedove from unstable, then you should just upgrade to unstable.

Last edited by Tuber (2012-07-04 18:28:59)

---

There are only 10 kinds of people in the world, those who understand binary, and those who don't.

Beepmode

Member

Registered: 2012-03-15

Posts: 42

Re: [SOLVED] notify-osd has died?

No, I'm on CrunchBang 10 statler. ...

...my Icedove is from the unstable repo...

This is likely where your problems lie. The above implies you have both stable and unstable repos enabled. It's best to stick with one or the other to avoid dependancy issues. If there is some compelling reason to use Icedove from unstable, then you should just upgrade to unstable.

My set-up was based on the excellent Living on the edge with #! thread. I've taken your advice though and am now running Sid. Thanks to all the information on these forums the move went surpringly smoothly. (I might need help with one or two issues but am trying to fix them myself first).

Anyway, I'll mark this one as solved.