Comment 24 for bug 530541

Have this desktopcouch problem with Lucid beta1

In my case it was not at startup but rather after using my desktop for 30 minutes or so.

I suspect it was triggered by the first time I used anything that wanted a desktopcouch connection,
 and also, in mycase, it is probably due to the older hardware on this desktop.

My /etc/hosts and desktopcouch version described here:

: #gnubyexample@amd754n(~) ;wc -l /etc/hosts
10 /etc/hosts
: #gnubyexample@amd754n(~) ;apt-cache policy desktopcouch
desktopcouch:
  Installed: 0.6.3-0ubuntu1
  Candidate: 0.6.3-0ubuntu1
  Version table:
 *** 0.6.3-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status
: #gnubyexample@amd754n(~) ;date;uname -a
Sun Mar 28 13:41:52 BST 2010
Linux amd754n 2.6.32-17-generic #26-Ubuntu SMP Fri Mar 19 23:58:53 UTC 2010 i686 GNU/Linux

My personal guess is that integrating desktopcouch into the Ubuntu desktop, is maybe going to
lead to the retirement of some aged hardware.
If (like me) you are running a really old single core desktop,
then it may be that desktopcouch cannot
start quick enough to service the desktop (Gwibber mainly)
( just a suggestion )

Might be worth noting if you are experiencing problems with desktopcouch and/or Gwibber,
and running low spec or aged processors such as...
... Pentium 4 or AMD Sempron or Intel Celeron perhaps.

The attachment I provide just gives more detail about the version of packages on my system related to desktopcouch.

On a personal note, if I wish to run Ubuntu Lucid on this old desktop, then I may need to look at using Empathy rather
than Gwibber for IM, and (if necessary) disable the indicator-applet to get rid of the desktopcouch integration.

Using Twitter in Gwibber is nice, and adds another argument for a new CPU maybe :)