desktopcouch-service crashed with RuntimeError in run_couchdb()

Bug #530541 reported by James Martin
This bug affects 632 people
Affects Status Importance Assigned to Milestone
desktopcouch
Fix Released
Critical
Chad Miller
desktopcouch (Ubuntu)
Fix Released
High
Ken VanDine
Lucid
Fix Released
High
Ken VanDine

Bug Description

Binary package hint: desktopcouch

Lucid alpha 3
desktopcouch-0.6.2-0ubuntu1

Trying to start Gwibber after update, I received this error.

ProblemType: Crash
Architecture: i386
Date: Tue Mar 2 03:28:39 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/desktopcouch/desktopcouch-service
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: desktopcouch 0.6.2-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/desktopcouch/desktopcouch-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
PythonArgs: ['/usr/lib/desktopcouch/desktopcouch-service']
SourcePackage: desktopcouch
Title: desktopcouch-service crashed with RuntimeError in run_couchdb()
Uname: Linux 2.6.32-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare video

Related branches

Revision history for this message
James Martin (tr4shb4t) wrote :
tags: removed: need-duplicate-check
James Martin (tr4shb4t)
visibility: private → public
Revision history for this message
Daniel Holm (danielholm) wrote :

I got the same issue.

tags: added: amd64
Revision history for this message
Bluppie (benhyper) wrote :

Me to :(

Ara Pulido (ara)
Changed in desktopcouch (Ubuntu):
status: New → Confirmed
Revision history for this message
Duane Hinnen (duanedesign) wrote :
Download full text (3.8 KiB)

On boot beam.smp takes 100 percent cpu. If i open Ubuntu One Preferences using System > Preferences > Ubuntu One or open Evoloution I get this error. Going to file:///home/duanedesign/.local/share/desktop-couch/couchdb.html it says 'Desktopcouch is not yet started. '

duanedesign@duanedesign-laptop:~$ ps auxww | grep beam
couchdb 1259 61.2 6.5 301216 185872 ? Sl 01:09 15:52 /usr/lib/erlang/erts-5.7.4/bin/beam.smp -Bd -K true -- -root /usr/lib/erlang -progname erl -- -home /var/lib/couchdb -- -noshell -noinput -smp auto -sasl errlog_type error -pa /usr/lib/couchdb/erlang/lib/couch-0.10.0/ebin /usr/lib/couchdb/erlang/lib/mochiweb-r97/ebin /usr/lib/couchdb/erlang/lib/ibrowse-1.5.2/ebin /usr/lib/couchdb/erlang/lib/erlang-oauth/ebin -eval application:load(ibrowse) -eval application:load(oauth) -eval application:load(crypto) -eval application:load(couch) -eval crypto:start() -eval ssl:start() -eval ibrowse:start() -eval couch_server:start([ "/etc/couchdb/default.ini", "/etc/couchdb/local.ini", "/etc/couchdb/default.ini", "/etc/couchdb/local.ini"]), receive done -> done end. -pidfile /var/run/couchdb/couchdb.pid -heart
1000 3107 66.3 5.7 294124 162448 ? Sl 01:29 4:13 /usr/lib/erlang/erts-5.7.4/bin/beam.smp -Bd -K true -- -root /usr/lib/erlang -progname erl -- -home /home/duanedesign -- -noshell -noinput -smp auto -sasl errlog_type error -pa /usr/lib/couchdb/erlang/lib/couch-0.10.0/ebin /usr/lib/couchdb/erlang/lib/mochiweb-r97/ebin /usr/lib/couchdb/erlang/lib/ibrowse-1.5.2/ebin /usr/lib/couchdb/erlang/lib/erlang-oauth/ebin -eval application:load(ibrowse) -eval application:load(oauth) -eval application:load(crypto) -eval application:load(couch) -eval crypto:start() -eval ssl:start() -eval ibrowse:start() -eval couch_server:start([ "/etc/couchdb/default.ini", "/etc/xdg/desktop-couch/compulsory-auth.ini", "/home/duanedesign/.config/desktop-couch/desktop-couchdb.ini"]), receive done -> done end. -pidfile /home/duanedesign/.cache/desktop-couch/desktop-couchdb.pid -heart
1000 3247 62.6 5.7 229104 161412 ? Sl 01:29 3:43 /usr/lib/erlang/erts-5.7.4/bin/beam.smp -Bd -K true -- -root /usr/lib/erlang -progname erl -- -home /home/duanedesign -- -noshell -noinput -smp auto -sasl errlog_type error -pa /usr/lib/couchdb/erlang/lib/couch-0.10.0/ebin /usr/lib/couchdb/erlang/lib/mochiweb-r97/ebin /usr/lib/couchdb/erlang/lib/ibrowse-1.5.2/ebin /usr/lib/couchdb/erlang/lib/erlang-oauth/ebin -eval application:load(ibrowse) -eval application:load(oauth) -eval application:load(crypto) -eval application:load(couch) -eval crypto:start() -eval ssl:start() -eval ibrowse:start() -eval couch_server:start([ "/etc/couchdb/default.ini", "/etc/xdg/desktop-couch/compulsory-auth.ini", "/home/duanedesign/.config/desktop-couch/desktop-couchdb.ini"]), receive done -> done end. -pidfile /home/duanedesign/.cache/desktop-couch/desktop-couchdb.pid -heart
1000 3377 53.6 5.6 223476 158980 ? Sl 01:30 2:59 /usr/lib/erlang/erts-5.7.4/bin/beam.smp -Bd -K true -- -root /usr/lib/erlang -progname erl -- -home /home/duanedesign -- -noshell -noinput -smp auto -sasl errlog_type error -pa /usr/lib/couchdb/erlang/lib/couch-0.10.0/ebin /usr/lib/co...

Read more...

Revision history for this message
Duane Hinnen (duanedesign) wrote :

 Everything worked fine, then i upgraded to Lucid and I have this bug. Seems my ~/.cache/desktop-couch/desktop-couchdb.pid is full of line breaks. Not sure how that happened in the upgrade.

duanedesign@duanedesign-laptop:~$ /usr/lib/desktopcouch/desktopcouch-service
2010-03-17 10:05:50,724 - Pid file does not contain int: '\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n'
2010-03-17 10:05:50,725 - Starting up personal couchdb.
2010-03-17 10:05:50,725 - Pid file does not contain int: '\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n'
2010-03-17 10:05:50,725 - Pid file does not contain int: '\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n'
Apache CouchDB has started, time to relax.
2010-03-17 10:05:50,842 - Pid file does not contain int: '\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n'
2010-03-17 10:05:51,244 - Pid file does not contain int: '\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n'
2010-03-17 10:05:51,344 - Pid file does not contain int: '\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n'
2010-03-17 10:05:51,445 - Pid file does not contain int: '\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n'
2010-03-17 10:05:51,646 - Pid file does not contain int: '\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n'
2010-03-17 10:05:52,147 - Pid file does not contain int: '\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n'
2010-03-17 10:05:53,150 - Pid file does not contain int: '\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n'
2010-03-17 10:05:56,154 - Pid file does not contain int: '\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n'
Traceback (most recent call last):
  File "/usr/lib/desktopcouch/desktopcouch-service", line 137, in <module>
    main()
  File "/usr/lib/desktopcouch/desktopcouch-service", line 84, in main
    pid = desktopcouch.find_pid(start_if_not_running=True, ctx=ctx)
  File "/usr/lib/python2.6/dist-packages/desktopcouch/__init__.py", line 35, in find_pid
    pid = start_local_couchdb.start_couchdb(ctx=ctx)
  File "/usr/lib/python2.6/dist-packages/desktopcouch/start_local_couchdb.py", line 247, in start_couchdb
    pid, port = run_couchdb(ctx=ctx)
  File "/usr/lib/python2.6/dist-packages/desktopcouch/start_local_couchdb.py", line 132, in run_couchdb
    raise RuntimeError("Can not start couchdb.")
RuntimeError: Can not start couchdb.

Changed in desktopcouch (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

A lot of crashes on gwibber seems to be related to this crash, marking this as Triaged, thanks.

Changed in desktopcouch (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
BK Box (bkbox) wrote :

Here is the log of desktopcouchdb in ~/.cache/desktop-couch/desktop-couch.log.

This can be duplicated very easily. I use Testdrive and start up a new LiveCD and start gwibber.

Revision history for this message
fretchen (fretchen) wrote :

I get this error everytimes that I open evolution.

Revision history for this message
Rick Spencer (rick-rickspencer3) wrote :

it appears that lots of users are hitting this issue, and it is causing problems for two key apps.

Changed in desktopcouch (Ubuntu):
importance: Medium → High
Changed in desktopcouch (Ubuntu Lucid):
assignee: nobody → Chad Miller (cmiller)
milestone: none → ubuntu-10.04-beta-2
Revision history for this message
Casey J Peter (caseyjp1) wrote :

issue occurs post patches as of this time stamp on startup of the "broadcast" application from the indicator applet.

Revision history for this message
Roman Yepishev (rye) wrote :

Hello,

In case you still experience this issue, could you please check what does the following command return for you?

$ wc -l /etc/hosts

The more lines/items this file has, the slower is startup. I expect that there are other factors that might slow couchdb startup, though.

Regarding duanedesign:
For some reason reading /etc/hosts took a lot of time. It reads and parses every line, thus it takes more time. We could increase the timeout for starting up couchdb, BUT the couchdb gets killed by its own heartbeat system:
 heart_beat_kill_pid = 4549
 heart_beat_timeout = 11
 heart: Wed Mar 24 17:31:07 2010: heart-beat time-out.
 Killed
heart: Wed Mar 24 17:31:08 2010: Executed "/usr/bin/couchdb -k". Terminating.

Now we have two questions, why it worked earlier - duanedesign started having the issue after upgrade to Lucid and 2 - how we can ask heartbeat to stop killing busy couchdbs.

Revision history for this message
Laurens Bosscher (laurens-laurensbosscher) wrote :

I'm using an ad blocking host file :

32723 /etc/hosts

I'll try to remove those entry's and try again.

Revision history for this message
Laurens Bosscher (laurens-laurensbosscher) wrote :

I went ahead and tried it again, after removing all ad blocking entries in the host file everything works as expected.

Revision history for this message
Yura Tolstik (yltsrc) wrote :

I've got this error with default /etc/hosts, which contains only 10 records

Revision history for this message
Dick Thomas (xpd259-deactivatedaccount) wrote :

I'm getting this error with the defaut /etc/hosts

Revision history for this message
Tomáš Honzák (thonzak) wrote :

I also have just 11 lines in /etc/hosts, however I do not seem to be experiencing the error anymore.

tom@quork:~$ LC_ALL=C apt-cache policy desktopcouch
desktopcouch:
  Installed: 0.6.3-0ubuntu1

Revision history for this message
hassan121 (k7rata121) wrote :

i have this error before and after the update !!

Revision history for this message
Magnus Itland (itlandm) wrote :

I have this error booting from a Transcend Jetflash 600 USB memory key on an Acer Aspire One, so naturally load time will be well above default, if that is related to the problem. It immediately precedes a Gwibber crash on every boot. However, Gwibber can later be started manually from the Programs menu.

Revision history for this message
Roman Yepishev (rye) wrote :

I have tested the Karmic version (desktopcouch - 0.5-0ubuntu1, couchdb-bin - 0.10.0-0ubuntu3) and it looks like this a real regression in couchdb. The startup time for karmic couchdb with 103569 is 2-5 seconds.

Revision history for this message
Roman Yepishev (rye) wrote :

I believe that something might be wrong with heartbeat/couchdb interaction, as the comments regarding startup from LiveCD/memory key suggest.

Revision history for this message
Rich Magahiz (milkfish) wrote :

I got this the first time starting gwibber running off the Lucid beta1 livecd.

Revision history for this message
Laura Czajkowski (czajkowski) wrote :

Happens when I start up for the first time there is a crash report waiting for me

Revision history for this message
Rich Magahiz (milkfish) wrote :

My bug report is for the version shipping with the beta. When I use the latest stable on Karmic, which looks quite different, it seems to come right up the first time.

Revision history for this message
GaryW (gnubyexample) wrote :

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 :)

Revision history for this message
Igor Wawrzyniak (igor-tumus) wrote :

Got this on Lucid Beta when I opened "Me menu" and tried to add a new account. Haven't used gwibber on this machine yet. Default /etc/hosts.

Revision history for this message
timuckun (timuckun) wrote :

This occurs in a chain of crashes. Gwibber fails, this fails and do does a desktop applet.

The end result is that the wifi network is super slow and need to reboot.

Revision history for this message
John McGuckian (jaymac) wrote :

I'm running Ubuntu 10.04 beta1 64bit on a Sony Vaio with 4GB Ram, and Core 2 Duo P8600 @2.4GHz.

I get simultaneous crashes in the three following programs randomly and also when I try to start Gwibber:

gwibber
gwibber-service
desktopcouch-service

When I start gwibber from the terminal, I get hundreds of these lines:

WARNING:root:Reading pid file caused error. [Errno 5] Input/output error: '/home/john/.cache/desktop-couch/desktop-couchdb.pid'

Followed by this:

Traceback (most recent call last):
  File "/usr/bin/gwibber", line 67, in <module>
    client.Client()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 447, in __init__
    self.w = GwibberClient()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 29, in __init__
    self.model = gwui.Model()
  File "/usr/lib/python2.6/dist-packages/gwibber/gwui.py", line 42, in __init__
    self.settings = util.SettingsMonitor()
  File "/usr/lib/python2.6/dist-packages/gwibber/util.py", line 91, in __init__
    DEFAULT_SETTINGS)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/util/couch.py", line 66, in __init__
    self.database = CouchDatabase(dbname, create=True)
  File "/usr/lib/python2.6/dist-packages/desktopcouch/records/server.py", line 53, in __init__
    port = desktopcouch.find_port(ctx=ctx)
  File "/usr/lib/python2.6/dist-packages/desktopcouch/__init__.py", line 51, in find_port
    return _direct_access_find_port(pid=pid, ctx=ctx)
  File "/usr/lib/python2.6/dist-packages/desktopcouch/__init__.py", line 75, in __find_port__linux
    pid = find_pid(start_if_not_running=True, ctx=ctx)
  File "/usr/lib/python2.6/dist-packages/desktopcouch/__init__.py", line 35, in find_pid
    pid = start_local_couchdb.start_couchdb(ctx=ctx)
  File "/usr/lib/python2.6/dist-packages/desktopcouch/start_local_couchdb.py", line 247, in start_couchdb
    pid, port = run_couchdb(ctx=ctx)
  File "/usr/lib/python2.6/dist-packages/desktopcouch/start_local_couchdb.py", line 132, in run_couchdb
    raise RuntimeError("Can not start couchdb.")
RuntimeError: Can not start couchdb.

Revision history for this message
John McGuckian (jaymac) wrote :

Update:
I deleted my ~/.cache/desktop-couch/desktop-couchdb.pid file and it now works.

Revision history for this message
igi (igor-cali) wrote :

Is that the solution? If yes, can be automatically get fixed on next update?

Revision history for this message
Henk de Groot (henk-de-groot1) wrote :

I'm not sure my bug is related but I think my desktopcouch service crashed here because my network was not up. It took the WLAN card some time to find the AP this time. Desktopcouch service normally works when the AP is found in time. It is used by gwibber. I do not have any subscriptions in gwibber; I had twitter but deleted it for now because of the memory hog issue in the gwibber-service.

This is a clean 10.04 B1 (not an upgraded 9.10) with all the latest updates.

Revision history for this message
Natim (site-remy) wrote :

I have the upgrade from 9.10 and I also get this problem very often.

Revision history for this message
Aruna Lakmal (aruna-lakmal) wrote :

I get this error mostly reboot the system.

Revision history for this message
Stefano Offizia (stefano-offizia) wrote : Re: [Bug 530541] Re: desktopcouch-service crashed with RuntimeError in run_couchdb()

The same goes good my case ...

Il 05/04/2010 19:31, Aruna Lakmal ha scritto:
> I get this error mostly reboot the system.
>

--
Fuoco di Vesta che fuor dal Tempio irrompe...Con ali e fiamme la Giovinezza va!...Fiaccole Ardenti sull'Are e sulle Tombe noi siamo le speranze della Nuova età.

Revision history for this message
Masahumi (surgkw) wrote :

me too >Aruna Lakmal

Revision history for this message
merovius (merovius) wrote :

Evolution does it for me. I think it is related to Ubuntu One which does not work correctly for me either. Using Lucid.

Revision history for this message
JoeInnes (joeinnes+launchpad) wrote :

I agree with merovius, I think it is related to Ubuntu One, which doesn't work correctly for me: . Mine crashes at startup with default /etc/hosts file. From the error messages I get from the Ubuntu One client, set_write_limit is not greater than 0, so probably some kind of problem with the default bandwidth throttling settings added to the client not handling this well is leading to a crash in the Ubuntu One client, which in turn leads to this crash.

If you think I should file a bug report against the Ubuntu One client, let me know.

Revision history for this message
MacRules (macrules) wrote :

I have this after an upgrade from 9.10 to 10.04 LTS beta via the web.
I can't find the versing, so i suppose it is beta 1.

I get the error by simply starting the program.
I am running inside VMWare Workstation 7 for Linux (on ubuntu 9.10)

Revision history for this message
iheartubuntu (iheartubuntu) wrote :

Agreed. I believe this is a U1 (ubuntuone) problem. None of my files sync at all with lucid and my contacts in evolution do not sync with ubuntu one which uses couchDB.

Revision history for this message
Raydawggg (raydawggg) wrote :

I have this same problem after an upgrade from 9.10 to 10.04 LTS beta.

Revision history for this message
iheartubuntu (iheartubuntu) wrote :

I do not think this is an "upgrade" problem, although i see many people here reporting the problem after the upgrade. I have this problem at home on 32 bit (which is an uprade to lucid) and i have this same problem here at work which is a fresh install of 64 bit lucid.

Revision history for this message
Ivan Brasil Fuzzer (ivanbrasil) wrote :

I have this problem in two 32 bit fresh install.

Revision history for this message
niroxx (niroxxos) wrote :

Me too, 32bit fresh install ...

Revision history for this message
Tom Imhof (tomimhof) wrote :

Same issues with gwibber and U1, running a fresh install 64-bit lucid on a white macbook 5.2.

Steve Langasek (vorlon)
Changed in desktopcouch (Ubuntu Lucid):
milestone: ubuntu-10.04-beta-2 → ubuntu-10.04
Revision history for this message
linusr (linusr) wrote :

have this problem in 32-bit upgrade from Karmic

Revision history for this message
VinDSL (perfect-pecker) wrote :

"Update:
I deleted my ~/.cache/desktop-couch/desktop-couchdb.pid file and it now works."

I just tried this and it worked for me, as well. Kudos!

Actually, I renamed the file (above) and it was regenerated during the next boot -- only, now it works, e.g. no desktopcouch-service crash/dialog box.

Perhaps this will help:

The content of the original file (that crashes) was simply '1837'

The content of the new file (that doesn't crash) is '1528'

Heh! These numbers don't mean jack to me, but it fixed the problem...

Revision history for this message
VinDSL (perfect-pecker) wrote :

> Perhaps this will help:
> The content of the original file (that crashes) was simply '1837'
> The content of the new file (that doesn't crash) is '1528'

Google'ing these numbers, they are evidently port numbers; thus using port 1837 (on my machine) is causing desktopcouch-service to crash. Using port 1528 always it to work.

BTW, this is an 9:10->10.04 install, via web update (like many others above).

Revision history for this message
iheartubuntu (iheartubuntu) wrote :

Did you test Ubuntu One out after rebooting? I deleted the pid file, rebooted and did not experience any couchdb problems until I tried to go into Ubuntu One. Then I got the same crashes as before. Problem not fixed on my system.

Revision history for this message
Ivan Brasil Fuzzer (ivanbrasil) wrote :

The ~/.cache/desktop-couch/desktop-couchdb.pid is the process identification file, not port number. The number inside file is only the number who identifies the process and is always diferent.

Revision history for this message
Tom Imhof (tomimhof) wrote :

Nope, deleting the pid file does not fix the problem for me either.

Revision history for this message
VinDSL (perfect-pecker) wrote :

>Did you test Ubuntu One out after rebooting? I deleted the pid file, rebooted and did
>not experience any couchdb problems until I tried to go into Ubuntu One. Then I got
>the same crashes as before. Problem not fixed on my system.

Yes, I tested Ubu One (last night) and it worked fine.

Here's the thing...

When I just rebooted my system (for probably the 5th time in approx 24 hr) I'm back to getting the desktopcouch-service can't be started warning.

However...

Ubu One is still working. Dittos for Gwibber, Pidgin, et cetera. Everything is working except, I'm back to getting the (supposed) desktopcouch-service cannot be started dialog.

Heh! This problem is a real corker, no?!?!?

Revision history for this message
VinDSL (perfect-pecker) wrote :

I don't know if this means anything to anybody, but...

I was just looking at my 'apport' logs and one of them says:

apport (pid 1588) Thu Apr 8 23:37:14 2010: called for pid 1386, signal 6
apport (pid 1588) Thu Apr 8 23:37:14 2010: script: /usr/lib/desktopcouch/desktopcouch-service, interpreted by /usr/bin/python2.6 (command line "/usr/bin/python /usr/lib/desktopcouch/desktopcouch-service")
apport (pid 1588) Thu Apr 8 23:37:14 2010: this executable already crashed 2 times, ignoring
apport (pid 1853) Fri Apr 9 21:57:51 2010: called for pid 1670, signal 6
apport (pid 1853) Fri Apr 9 21:57:51 2010: script: /usr/lib/desktopcouch/desktopcouch-service, interpreted by /usr/bin/python2.6 (command line "/usr/bin/python /usr/lib/desktopcouch/desktopcouch-service")
apport (pid 1853) Fri Apr 9 21:57:55 2010: wrote report /var/crash/_usr_lib_desktopcouch_desktopcouch-service.1000.crash
apport (pid 1544) Fri Apr 9 22:13:34 2010: called for pid 1358, signal 6
apport (pid 1544) Fri Apr 9 22:13:34 2010: script: /usr/lib/desktopcouch/desktopcouch-service, interpreted by /usr/bin/python2.6 (command line "/usr/bin/python /usr/lib/desktopcouch/desktopcouch-service")
apport (pid 1544) Fri Apr 9 22:13:34 2010: this executable already crashed 2 times, ignoring
apport (pid 1829) Sat Apr 10 00:20:05 2010: called for pid 1641, signal 6
apport (pid 1829) Sat Apr 10 00:20:06 2010: script: /usr/lib/desktopcouch/desktopcouch-service, interpreted by /usr/bin/python2.6 (command line "/usr/bin/python /usr/lib/desktopcouch/desktopcouch-service")
apport (pid 1829) Sat Apr 10 00:20:06 2010: this executable already crashed 2 times, ignoring

As you can see -- after deleting the pid file -- everything was okay for approx 24 hrs... then back to the same old/same old...

Revision history for this message
VinDSL (perfect-pecker) wrote :

Hrm...

If I'm reading the above correctly, desktopcouch-service is crashing twice (around midnight) then being ignored until (around midnight) the next day.

Sooooo, now I'm thinking that deleting the pid file was simply a coincidence, e.g. mimicking a fix.

Still, that doesn't answer why my Ubu One is working, regardless or whether (or not) desktopcouch-service is running.

Maybe it's a bogus warning.

I'll have to think about this for a while. LoL! I've (evidently) got 24 hours to come up with a solution...

Revision history for this message
VinDSL (perfect-pecker) wrote :

Epilog: I was going to go play a flash game on Facebook, while I mulled this situation over, but while I was logging in, I thought, "Duh! Why don't I follow the breadcrumbs???"

I just looked at my /var/crash/ folder, and I had 3 files in there.

One report was for a Plymouth crash (from when I first updated to 10.04 via the web)

One report was for Gwibber (from 4-April) ZZZZzzzzzzzz...

And, one report was for desktopcouch-service (see the path in the above text).

The CoreDump is Base64 and unintelligible (to me). I wonder why we cannot submit these reports to someone.

Okay, I'm going to go play Cafe World, and think about this some more. Carry on... :)

Revision history for this message
Rick Spencer (rick-rickspencer3) wrote :

Desktopcouch is working locally, but does not seem to be successfully syncing databases. So far my contacts database for U1 has successfully synced (there was but 1 contact in it), and several of my personal desktopcouch databases from various development projects have synced. My bindwood bookmarks and my gwibber accounts have not synced.

Revision history for this message
Nigel Atkinson (nigel-atkinson) wrote :

I've noticed , that IF the desktop couch server does not crash, it hogs the cpu. This is after logging in. I have the system monitor applet on my top panel, and its really obvious (using 'top' as well). If I want to do anything remotely cpu intensive, I have to kill the desktop couch process to get any sort of performance.

Revision history for this message
frizzle21 (frederik-nnaji) wrote :

@ VinDSL : hahaaah follow the white rabbit next time, breadcrumds will not still your hunger :D

yeah, there's something seriously not ok with the couch, we all see that.

modifying an encrypted file on a "cloud" server is obviously a very complicated thing nowadays...
even Mozilla Weave is tripping a lot on my machines..

the couch was meant to send PIM data into a cloud-residing data structure... what's whith that? ftp does that sort of thing, SAFT does it, ssh does it, any db via php, even jabber has options... what is it exactly with the couch?
how do we achieve the main goal of cloud synced PIM timely for lucid?

this is obviously big enough to receive some special attention..
i see close to 400 people marked affected, countless duplicates of the bug and 55 comments on this bug here alone..

Revision history for this message
frizzle21 (frederik-nnaji) wrote :

greatest problem concerning contacts in Ubuntu One / Gnome:
Gnome has no method to describe People in one single place.

Personal information about my contacts is scattered across the system.
*Empathy: IM contact, network and avatar
*Evolution: undynamic v-card data
*Gwibber: could pull information from facebook, identi.ca, google buzz, tumblr, or youtube profiles..

as an example, here how my phone does it:
1) pulls PIM data where it finds it (jabber, facebook, cloud PIM..)
2) links all available personal profile information on the people it finds in these contact lists
3) overlays, if field name and information are the same, appends if field name or information differ

this way i have more than 50% of my contacts in one pretty list, easily organized and merged.

who would do that in Gnome?
Evolution Contacts? Empathy's "Contact List" ?
wasn't there a project on launchpad called "People" ?

Chad Miller (cmiller)
Changed in desktopcouch:
status: New → Fix Committed
assignee: nobody → Chad Miller (cmiller)
importance: Undecided → Critical
Revision history for this message
Chad Miller (cmiller) wrote :

Sorry about my lack of feedback, folks; I've been away from work for several days.

I have a patch in upstream trunk that I think fixes the problem with using all CPU, at least. Perhaps more.

Would some of you who have crashes try the package in this PPA? ppa:cmiller/u1-lucid
I don't know that it will fix the varied problems listed here, but I need to know what is left.

$ sudo add-apt-repository ppa:cmiller/u1-lucid
$ sudo apt-get update
$ sudo apt-get upgrade .\*desktopcouch.\*

If you do, please report the version number of "desktopcouch" package along with your results! Report success as well as failure, please.

$ dpkg -l desktopcouch |cat

Revision history for this message
Willem Hobers (whobers) wrote :

Chad,
thanks for your fix.

Just tried to execute the commands you list.
The sudo apt-get update seems to not work:
...
Fout http://ppa.launchpad.net karmic/main Packages
  404 Not Found
....

W: Ophalen van http://ppa.launchpad.net/cmiller/u1-lucid/ubuntu/dists/karmic/main/binary-i386/Packages.gz 404 Not Found is mislukt

What am I doing wrong?

Thanks.

Revision history for this message
Chad Miller (cmiller) wrote :

Willem, sorry, this is for Lucid beta only. Are you running pure Ubuntu 9.10?

Revision history for this message
iheartubuntu (iheartubuntu) wrote :

Chad, thanks for your help. After rebooting, I still get the errors/crashes. Here is my output....

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=================================================-=================================================-============================================
ii desktopcouch 0.6.4-0ubuntu1~proposed1~chad0 A Desktop CouchDB instance

Revision history for this message
Phil Bayfield (philio) wrote :

Same issue, Lucid beta 2

Revision history for this message
Peter Kingsnorth (petejk) wrote :

Well last two re-boots I haven't had a couchdb crash.

Regards, Pete
Lucid 10.04

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=====================================================-===================================================================-============================================
ii desktopcouch 0.6.4-0ubuntu1~proposed1~chad0 A Desktop CouchDB instance

Revision history for this message
igi (igor-cali) wrote :

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Nome Versione Descrizione
+++-====================================-===============================================-============================================
ii desktopcouch 0.6.4-0ubuntu1~proposed1~chad0 A Desktop CouchDB instance

Chad Miller (cmiller)
Changed in desktopcouch:
status: Fix Committed → Fix Released
Revision history for this message
frizzle21 (frederik-nnaji) wrote : Re: [Bug 530541] Re: desktopcouch-service crashed with RuntimeError in run_couchdb()

>
> ~$ dpkg -l desktopcouch |cat
> Desired=Unknown/Install/Remove/Purge/Hold
> |
> Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name
> Version Description
>
> +++-=====================================-==================================================-============================================
> ii desktopcouch
> 0.6.4-0ubuntu1~proposed2~chad0 A Desktop CouchDB
> instance
>

hope it's of use.
doesn't include a restart between the apt commands and this one..

On Mon, Apr 12, 2010 at 18:36, Chad Miller <email address hidden>wrote:

> Sorry about my lack of feedback, folks; I've been away from work for
> several days.
>
> I have a patch in upstream trunk that I think fixes the problem with
> using all CPU, at least. Perhaps more.
>
> Would some of you who have crashes try the package in this PPA?
> ppa:cmiller/u1-lucid
> I don't know that it will fix the varied problems listed here, but I need
> to know what is left.
>
> $ sudo add-apt-repository ppa:cmiller/u1-lucid
> $ sudo apt-get update
> $ sudo apt-get upgrade .\*desktopcouch.\*
>
> If you do, please report the version number of "desktopcouch" package
> along with your results! Report success as well as failure, please.
>
> $ dpkg -l desktopcouch |cat
>
> --
> desktopcouch-service crashed with RuntimeError in run_couchdb()
> https://bugs.launchpad.net/bugs/530541
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in Desktop CouchDB: Fix Committed
> Status in “desktopcouch” package in Ubuntu: Triaged
> Status in “desktopcouch” source package in Lucid: Triaged
>
> Bug description:
> Binary package hint: desktopcouch
>
> Lucid alpha 3
> desktopcouch-0.6.2-0ubuntu1
>
> Trying to start Gwibber after update, I received this error.
>
> ProblemType: Crash
> Architecture: i386
> Date: Tue Mar 2 03:28:39 2010
> DistroRelease: Ubuntu 10.04
> ExecutablePath: /usr/lib/desktopcouch/desktopcouch-service
> InterpreterPath: /usr/bin/python2.6
> NonfreeKernelModules: nvidia
> Package: desktopcouch 0.6.2-0ubuntu1
> PackageArchitecture: all
> ProcCmdline: /usr/bin/python /usr/lib/desktopcouch/desktopcouch-service
> ProcEnviron:
> SHELL=/bin/bash
> LANG=en_US.UTF-8
> ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
> PythonArgs: ['/usr/lib/desktopcouch/desktopcouch-service']
> SourcePackage: desktopcouch
> Title: desktopcouch-service crashed with RuntimeError in run_couchdb()
> Uname: Linux 2.6.32-14-generic i686
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare video
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/desktopcouch/+bug/530541/+subscribe
>

Revision history for this message
igi (igor-cali) wrote :

Hello Chad,

I have upgrade the package with instructions you provided.

On restart I keep getting crash notifications (I can't send apport traces since it says this is not a genuine Ubuntu package).
I still have to perform my daily update of lucid beta2.

Chad Miller (cmiller)
Changed in desktopcouch:
status: Fix Released → Confirmed
tags: added: desktop+
Revision history for this message
Tomáš Honzák (thonzak) wrote :

Hi Chad,

with the most recent version of desktopcouch from your ppa and full today's update of beta2, the problem seems to be resolved for me.

tom@quork:~$ LC_ALL=C dpkg -l desktopcouch |cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=================================================-===============================================-============================================
ii desktopcouch 0.6.4-0ubuntu1~proposed2~chad0 A Desktop CouchDB instance
tom@quork:~$

Revision history for this message
Chad Miller (cmiller) wrote :

Thank you, Tomáš. Anyone else? Please, time is short on releasing this to the distro folks.

Revision history for this message
mikbini (mikbini) wrote :

The PPA fixed the crash for me.

Revision history for this message
Jono Bacon (jonobacon) wrote :

I installed the package, Chad. How can I test if it is working properly?

Revision history for this message
Jono Bacon (jonobacon) wrote :

Chad, I think this might be working for me. Gwibber and Contact Syncing in Evolution seems to work OK for me. I am running 0.6.4-0ubuntu1~proposed2~chad0

Revision history for this message
Chad Miller (cmiller) wrote :

Thanks, all.

Changed in desktopcouch:
status: Confirmed → Fix Released
Changed in desktopcouch (Ubuntu Lucid):
status: Triaged → In Progress
assignee: Chad Miller (cmiller) → Ken VanDine (ken-vandine)
Revision history for this message
Chad Miller (cmiller) wrote :

For everyone who added my PPA, you may (and should!) now remove it from your package list.

$ sudo rm /etc/apt/sources.list.d/cmiller-u1-lucid*

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package desktopcouch - 0.6.4-0ubuntu1

---------------
desktopcouch (0.6.4-0ubuntu1) lucid; urgency=low

  * Upstream release. Adds all patches that were previously in this packaging.
  * Split desktopcouch-service threads into to discrete processes, since they
    do not depend on each other, and because multithreading breaks with recent
    changes to libraries. (LP: #524566, #530605)
  * Made desktopcouch more robust when dealing with mergeable lists.
    (LP: #555908)
  * If the replication service gives a user_id, then include it in the
    query string, so the service can shard access.
  * Add bookmark records support.
  * Handle cancelled keyring dialogs. (LP: #527036)
  * Retry when starting couchdb fails. (LP: #530541)
  * debian/patches/0-items-should-expose-private-data-for-now.patch
    - Gwibber demands that some items that are private be exposed, namely
      keys _id and _rev. These should properly be accessed as attributes
      .record_id and .record_revision in some future release of gwibber.
 -- Chad MILLER <email address hidden> Mon, 12 Apr 2010 23:02:01 -0400

Changed in desktopcouch (Ubuntu Lucid):
status: In Progress → Fix Released
Revision history for this message
jvin248 (jvin248) wrote :

Got this crashed program after trying to launch gwibber from 10.04 Beta 2.

Revision history for this message
John Doe (jodo-deactivatedaccount) wrote :

Got this too, with desktopcouch 0.6.4-0ubuntu2 while trying to start gwibber.

Revision history for this message
J. Austin Rodriguez (jeanaustinr) wrote :

Same as jvin248. I was testing Lucid Beta 2 via Live CD and Gwibber crashed.

Revision history for this message
Tom Imhof (tomimhof) wrote :
Download full text (3.7 KiB)

I just tested this again with the latest Lucid update - desktopcouch 0.6.4.-0ubuntu3 - still no luck. I get the same errors as before :(

Command line output:

tom@MUMBLE:~$ gwibber

** (gwibber:15553): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'

** (gwibber:15553): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'

** (gwibber:15553): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
Apache CouchDB has started, time to relax.
WARNING:root:Pid file does not contain int: '\n\n'
WARNING:root:Pid file does not contain int: '\n\n'
WARNING:root:Pid file does not contain int: '\n\n'
WARNING:root:Pid file does not contain int: '\n\n'
WARNING:root:Pid file does not contain int: '\n\n'
WARNING:root:Pid file does not contain int: '\n\n'
ERROR:root:Starting couchdb failed on try 0
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/desktopcouch/start_local_couchdb.py", line 251, in start_couchdb
    pid, port = run_couchdb(ctx=ctx)
  File "/usr/lib/python2.6/dist-packages/desktopcouch/start_local_couchdb.py", line 132, in run_couchdb
    raise RuntimeError("Can not start couchdb.")
RuntimeError: Can not start couchdb.
WARNING:root:Pid file does not contain int: '\n\n'
Apache CouchDB has started, time to relax.
WARNING:root:Pid file does not contain int: '\n\n\n'
WARNING:root:Pid file does not contain int: '\n\n\n'
WARNING:root:Pid file does not contain int: '\n\n\n\n'
WARNING:root:Pid file does not contain int: '\n\n\n\n'
WARNING:root:Pid file does not contain int: '\n\n\n\n'
WARNING:root:Pid file does not contain int: '\n\n\n\n'
WARNING:root:Pid file does not contain int: '\n\n\n\n'
WARNING:root:Pid file does not contain int: '\n\n\n\n'
ERROR:root:Starting couchdb failed on try 1
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/desktopcouch/start_local_couchdb.py", line 251, in start_couchdb
    pid, port = run_couchdb(ctx=ctx)
  File "/usr/lib/python2.6/dist-packages/desktopcouch/start_local_couchdb.py", line 132, in run_couchdb
    raise RuntimeError("Can not start couchdb.")
RuntimeError: Can not start couchdb.
WARNING:root:Pid file does not contain int: '\n\n\n\n'
Apache CouchDB has started, time to relax.
WARNING:root:Pid file does not contain int: '\n\n\n\n\n'
WARNING:root:Pid file does not contain int: '\n\n\n\n\n'
WARNING:root:Pid file does not contain int: '\n\n\n\n\n\n'
WARNING:root:Pid file does not contain int: '\n\n\n\n\n\n'
WARNING:root:Pid file does not contain int: '\n\n\n\n\n\n'
WARNING:root:Pid file does not contain int: '\n\n\n\n\n\n'
WARNING:root:Pid file does not contain int: '\n\n\n\n\n\n'
WARNING:root:Pid file does not contain int: '\n\n\n\n\n\n\n'
ERROR:root:Starting couchdb failed on try 2
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/desktopcouch/start_local_couchdb.py", line 251, in start_couchdb
    pid, port = run_couchdb(ctx=ctx)
  File "/usr/lib/python2.6/dist-packages/desktopcouch/start_local_couchdb.py", line 132, in run_couchdb
    raise RuntimeError("Can not start couchdb.")
R...

Read more...

Revision history for this message
corrie (corrie-engelbrecht) wrote :

Just upgraded from Karmic to Lucid (distupgrade), with all the latest patches and packages.

I can report that I've experienced the same issue as in post #78, with the same output.

The advice in post #11 was to reduce the number of entries in /etc/hosts and this worked for me.

Unfortunately this means that ad blocking using the hosts file is not possible, so I will not be using gwibber, or any other app that requires couchdb :(

Sorry, this is just an unacceptable issue.

Revision history for this message
corrie (corrie-engelbrecht) wrote :

Re #79:

But if you want a work around, then:

1. Rename the large /etc/hosts file with all the adblock entries to something like /etc/hosts.normal
2. Make a small /etc/hosts file with only localhost and so on in it. I called mine /etc/hosts.minimal
3. Launch gwibber from a script that copies the minimal hosts file to /etc/hosts, runs gwibber in the background, then copies the normal hosts file back.

#!/bin/bash
sudo cp /etc/hosts.minimal /etc/hosts
nohup gwibber 1>/dev/null 2>/dev/null &
sudo cp /etc/hosts.normal /etc/hosts

Revision history for this message
Brian J. Murrell (brian-interlinx) wrote : Re: [Bug 530541] Re: desktopcouch-service crashed with RuntimeError in run_couchdb()

On Sat, 2010-05-01 at 12:10 +0000, corrie wrote:
> Re #79:
>
> But if you want a work around, then:
>
> 1. Rename the large /etc/hosts file with all the adblock entries to something like /etc/hosts.normal
> 2. Make a small /etc/hosts file with only localhost and so on in it. I called mine /etc/hosts.minimal
> 3. Launch gwibber from a script that copies the minimal hosts file to /etc/hosts, runs gwibber in the background, then copies the normal hosts file back.

And how praytell, is this done without root priviledges? Oh, yes, I
see, everyone on a machine should be able to sudo so that they can be
root and have all sorts of nasty accidents that the typical practise of
preventing users from being root keeps them safe from.

Bottom line, this is one of the uglier hacks I have ever seen. Full of
security issues as well as races.

It's really bad that this is what trying to run a functional system has
come to. Why is such buggy software being let into stable releases?

Revision history for this message
corrie (corrie-engelbrecht) wrote :

Hi Brian.

Apparently the script I put in was cut off.

There are no race conditions here.

You can also turn your sarcasm off, thanks.

See the attached script (which hopefully makes it through this time)

Revision history for this message
John Doe (jodo-deactivatedaccount) wrote :

The script is really not optimal, I could only use gwibber when using it. I mean: all other Apps like Browsers that I run when using this solution are using the same minimal /etc/hosts when gwibber is on. This means: no ad-blocking, even with your script.

Revision history for this message
Brian J. Murrell (brian-interlinx) wrote :

On Sat, 2010-05-01 at 12:34 +0000, corrie wrote:
> Hi Brian.

Hey,

> Apparently the script I put in was cut off.

No, it wasn't.

> There are no race conditions here.

Sure there is. What if another process wants to do a gethost* call for
a hosts that's only in the /etc/hosts.normal while you have
"temporarily" hijacked the /etc/hosts file for the sake of starting the
buggy application?

Revision history for this message
corrie (corrie-engelbrecht) wrote :

No, the script is not optimal, Thorsten, but to address your points:
1. You can modify it for other apps
2. Once any app that uses this script to launch, because said app depends on desktopcouch, then all other apps that also depends on desktopcouch can just be started directly, because the link between the desktopcouch and the couchdb service will have been established

This is just a workaround, and you would use it knowing that you:
a) need sudo privileges
b) run the small risk of an app asking for a host entry *that exists in your hosts file* and that you want to handle differently from DNS in the few seconds that it takes to run the scripe. Small risk, small impact even if it happens, so what?

Also Thorsten, I don't think you read the script properly.

It will launch a gwibber process *in the background*, and immediately replace the hosts file after the gwibber process is created.

Brian, you are very critical of the bugs in desktopcouch, but I'm sure that it will be fixed in due course. In the meantime, I will not be using gwibber or other affected apps, and you don't have to either.

This is a WORKAROUND, which will alleviate the problem until it's fixed.

For example, I am using this script as a workaround so I can play with gwibber.

Really guys, if you don't want to use the script, then don't use it. It works for me, and it provides a workaround to the issue which I am using, and I'm sure other people are as well.

Revision history for this message
John Doe (jodo-deactivatedaccount) wrote :

You're right, I didn't realize how the script works exactly. Thanks for your explaination. Badly, that didn't solved the problem for me, because gwibber doesn't start on my System at all, even with an unmodified /etc/hosts.

Revision history for this message
corrie (corrie-engelbrecht) wrote :

No problem. So which of the problems in this thread is breaking gwibber for you?

Can you post the console output if you start gwibber from a terminal, so that someone can help figure it out?

Revision history for this message
John Doe (jodo-deactivatedaccount) wrote :

Now it starts. I'm not able to create an account, but I've made a new report for that error. Thanks.

Revision history for this message
Chad Miller (cmiller) wrote :

For those using the system /etc/hosts file to block undesirable names, you might consider putting the undesirable names in a proper name resolver and trimming your hosts file down to what it should be. See 'dnsmasq' for a simple resolver.

Revision history for this message
corrie (corrie-engelbrecht) wrote :

Thanks, Chad.

This suggestion might work in some configurations. Unfortunately it won't work in mine.

I should point out that other software can handle large hosts files without issues. One example is squid, which loads the entire hosts file on startup.

Why any software should want to do this is a bit of a mystery though.

Revision history for this message
John Doe (jodo-deactivatedaccount) wrote :

Chad, had trouble again with starting gwibber. Tried again with your script and it works well.

Revision history for this message
Tom Imhof (tomimhof) wrote :

Hello,

I just had to set up my 64-bit and my 32-bit boxes again - and since I had to do this anyway, it gave me a chance to test this again both setups.

Results:

1. 32-bit system: gwibber starts fine both booting from the installation CD and after installing to the harddrive
2. 64-bit system: gwibber starts fine if booted from the installation CD, it fails with the exact same errors as above when running it after installation

Are we all on 64-bit systems here on the thread?

thanks,
Tom

Revision history for this message
Tom Imhof (tomimhof) wrote :

... oh and since I have nothing in my hosts file, I actually do not think this is really the core of the problem after all. At least not for my stubbornly unsocial 64-bit macbook;-)

Revision history for this message
Pablo Almeida (pabloalmeidaff9) wrote : Re: [Bug 530541] Re: desktopcouch-service crashed with RuntimeError in run_couchdb()

I'm on a 32-bit environment, but the bug seems fixed to me.

2010/5/31 Tom Imhof <email address hidden>

> ... oh and since I have nothing in my hosts file, I actually do not
> think this is really the core of the problem after all. At least not for
> my stubbornly unsocial 64-bit macbook;-)
>
> --
> desktopcouch-service crashed with RuntimeError in run_couchdb()
> https://bugs.launchpad.net/bugs/530541
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in Desktop CouchDB: Fix Released
> Status in “desktopcouch” package in Ubuntu: Fix Released
> Status in “desktopcouch” source package in Lucid: Fix Released
>
> Bug description:
> Binary package hint: desktopcouch
>
> Lucid alpha 3
> desktopcouch-0.6.2-0ubuntu1
>
> Trying to start Gwibber after update, I received this error.
>
> ProblemType: Crash
> Architecture: i386
> Date: Tue Mar 2 03:28:39 2010
> DistroRelease: Ubuntu 10.04
> ExecutablePath: /usr/lib/desktopcouch/desktopcouch-service
> InterpreterPath: /usr/bin/python2.6
> NonfreeKernelModules: nvidia
> Package: desktopcouch 0.6.2-0ubuntu1
> PackageArchitecture: all
> ProcCmdline: /usr/bin/python /usr/lib/desktopcouch/desktopcouch-service
> ProcEnviron:
> SHELL=/bin/bash
> LANG=en_US.UTF-8
> ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
> PythonArgs: ['/usr/lib/desktopcouch/desktopcouch-service']
> SourcePackage: desktopcouch
> Title: desktopcouch-service crashed with RuntimeError in run_couchdb()
> Uname: Linux 2.6.32-14-generic i686
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare video
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/desktopcouch/+bug/530541/+subscribe
>

--
Pablo Almeida
http://www.google.com/profiles/pabloalmeidaff9

Revision history for this message
Saravanan Thirumuruganathan (saravanan-thirumuruganathan) wrote :

I am in a 64 bit machine and I still have this issue

Revision history for this message
Richy (klemmster) wrote :

This bug is _not_ fixed on 64-Bit systems.
 Installed Lucid last weekend and gwibber worked fine until Thursday.

Since then I get these Error-Messages too.

Revision history for this message
Richy (klemmster) wrote :

PS:
That is for desktopcouch-0.6.3ubuntu3
What log or information is needed to get this fixed?

Revision history for this message
Adam (adam-jackman) wrote :

I have to agree that this is still present in 64bit. Every time I wake up my PC I have to reenable all chat accounts to go ready.

I have desktopcouch 0.6.4-0ubuntu3 installed.

Revision history for this message
Tobias Bradtke (webwurst) wrote :

This Bug just happend on Maverick Beta with all updates.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.