Notifications won't work. Error After Logout/In again Ubuntu 7.04

Same issue here, at the first login to gnome everything works fine, but at the following logins the notification-daemon won't work.
Restarting DBus doesn't help.

The problem may be solved by installing Galago, then killing the notification daemon and rebooting the computer.

Not sure why, but this seemed to have helped me.

Same problem here (plus drivemount applet do not appear when notifications are not working).

Between logins, if I switch to VT and log with my user, I can see 2 processes remaining from my last gdm session :
bonobo-activation-server and evolution-data-server
If I kill evolution-data-server, then bonobo-activation-server stops and notifications work again in next gdm login.
If I do not kill those processes, notifications do not work in next gdm login.

On Thu, 2007-06-07 at 20:53 +0000, Cedric Schieli wrote:
> Same problem here (plus drivemount applet do not appear when
> notifications are not working).
>
> Between logins, if I switch to VT and log with my user, I can see 2 processes remaining from my last gdm session :
> bonobo-activation-server and evolution-data-server
> If I kill evolution-data-server, then bonobo-activation-server stops and notifications work again in next gdm login.
> If I do not kill those processes, notifications do not work in next gdm login.
>

Thank you very much, have you noticed problems with the trash icon
applet not showing trash as full when this is happening?

> Thank you very much, have you noticed problems with the trash icon
> applet not showing trash as full when this is happening?

Yes, I confirm the trash icon remains empty when the problem happens.

BTW, the root cause of this bug seems to be #90258

This can't be... At first, it worked, the work around suggested in #90258 worked until reboot, at which time I started seeing the error again, so per instructions in #90258 I logged into a console after logging out of my gnome session and use ps awux |grep evolution

This revealed nothing...

So then, I did ps awux |grep cyclops

Only processes running were the ones on tty1, which was my terminal connection.

The problem continues to happen, no idea why or how to go about troubleshooting. However, it is definitely the same issues as Disk Mounter, ZeroConf, and the trash applet all exhibit the same behaviors, trash won't appear full, ZeroConf complains that notifications won't work and Disk Mounter simply won't load at all. Behavior continues until reboot.

...Workaround #2 for this bug...

In addition to the workaround suggested in #90258, there is another potential cause, after rebooting and looking at the problem new, when I did a ps awux |grep cyclops (my username is cyclops of course) then I found that bonobo-activation-server was still running after logout. I then used root to login so that no processes from cyclops should be active after logging out of the gdm session.

I found that this process, bonobo-activation-server was running as well as gpg-agent.

Now, killing gpg-agent did NOT cause b-a-s service to die. so after killing it manually I then logged into gdm again and ran Synaptic, searched for gpg-agent, found it, removed it.

Now, I logged out again, used root as before, found it was still running. Killed it, killed b-a-s, logged in again, then back out again.

Repeated the login to root and search for processes, I only found a gconf process. Skeptical, I didn't kill that process but I did log into gdm again, no notification error.

It appears that in addition to the evolution-data-server problem, gpg-agent also causes a problem in having bonobo-activation-server shut down.

I have also noticed nothing out of the ordinary with evolution since doing the workaround from the other bug report.

Once more...

The workaround was functional until next reboot, now, no process can be seen to be holding up bonobo, no idea where to go to solve this from here. I know a little about programming but I"m afraid looking through the source code for these things is like a child trying to read war and peace.

Help?

I'm surprised to find such complicated workarounds for this issue. My answer has always been just to reboot, as it only seems to happen when I log in for a second time.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Andrew Conkling wrote:
> I'm surprised to find such complicated workarounds for this issue. My
> answer has always been just to reboot, as it only seems to happen when I
> log in for a second time.
>

A full reboot is really a poor solution, a stable system should be able
to stay running indefinitely only shutting down for maintenance or the
occasional update.

The reason a lot of Linux users switched from windows was because they
wanted a system like that.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGpBx/StZoE1nza5gRAwl5AJ9/f4yEr4YY5E2rqJ/xz9q8Vlly3ACgkdBC
uK00XTcb+aZkEqfuhfFRVTs=
=jknv
-----END PGP SIGNATURE-----

Hi,

I want to mention the problem still occurs on Gusty... In fact I didn't encounter this bug in Feisty, but since I made a fresh Gusty install, every time I log in a second time, I get this 'Notification Daemon Error : notifications won't work error'.

Other symptoms are that my desktop settings are not takien into account for the new session (icon theme, compiz effects, ...)

Is the bug still worked on ? This is quite annoying oner month before Gusty release.

This is an issue with dbus which affect gnome-panel. For example tomboy as an applet ~/tomboy.log will shows up "[DEBUG]: Tomboy remote control disabled (DBus exception): Unable to open the session message bus" on second and afterwards login. Same goes for every dbus consumers. I have been unable to track it down to anything yet except maybe the session is not closed properly thus dbus-launch is not closed properly.
PS : I encounter the bug on debian too thus this affect the whole family.

Regards
Alban

I just experienced the same bug that killed music-applet.

And about rebooting the whole system... come on guys, we're not reimplementing Windows bugs!

Hervé, that's opensource code and you are welcome to send patches, such comments are not useful there

I have the same problem with a fresh install of Gutsy.
I got the same notification error just after the first logout then login...

Do you if there is some fixes ?

Only workarounds are currently present here. If you find anything out, please post it here to help debug and fix this issue.

Hi,

does anyone still experience this bug ? I didn't for a long time now... (but I migrated to Hardy Heron)

Thank you for reporting this bug to Ubuntu. Gutsy reached EOL in October, 2008.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

I've tried recreating this bug with Oneiric and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.

Please feel free to report any other bugs you may find.

[Expired for notification-daemon (Ubuntu) because there has been no activity for 60 days.]