[Expired for notification-daemon (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: notification-daemon (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
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)
Hi,
does anyone still experience this bug ? I didn't for a long time now...
(but I migrated to Hardy Heron)
--
Notifications won't work. Error After Logout/In again Ubuntu 7.04
https://bugs.launchpad.net/bugs/114885
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Only workarounds are currently present here. If you find anything out,
please post it here to help debug and fix this issue.
--
Notifications won't work. Error After Logout/In again Ubuntu 7.04
https://bugs.launchpad.net/bugs/114885
You received this bug notification because you are a member of U
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 ?
--
Notifications won't work. Error After Logout/In again Ubuntu 7.04
https://bugs.launchpad.net/bugs/114885
You received this bug not
Hervé, that's opensource code and you are welcome to send patches, such
comments are not useful there
--
Notifications won't work. Error After Logout/In again Ubuntu 7.04
https://bugs.launchpad.net/bugs/114885
You received this bug notification because you are a member of Ubuntu
Bugs, which is th
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!
--
Notifications won't work. Error After Logout/In again Ubuntu 7.04
https://bugs.launchpad.net/bugs/114885
You received this bug notification be
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 unabl
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
** Changed in: notification-daemon (Ubuntu)
Importance: Undecided => Medium
Status: New => Confirmed
--
Notifications won't work. Error After Logout/In again Ubuntu 7.04
https://bugs.launchpad.net/bugs/114885
You received this bug notification because you are a member of Ubuntu
Bugs, wh
-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 st
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.
--
Notifications won't work. Error After Logout/In again Ubuntu 7.04
https://bugs.launchpad.net/bugs/114885
You received this bu
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
...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 a
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 t
> 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
--
Notifications won't work. Error After Logo
On Thu, 2007-06-07 at 20:53 +, 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-se
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
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.
--
Notifications won't work. Error After Logout/In again Ubuntu 7.04
https://bugs.launchpad.net/bugs/114885
You received this bug noti
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.
--
Notifications won't work. Error After Logout/In again Ubuntu 7.04
https://bugs.launchpad.net/bugs/114885
You received this bug noti
20 matches
Mail list logo
