From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <eg@gaute.vetsj.com>
Received: from localhost (c0A64BF51.dhcp.bluecom.no [81.191.100.10])
        by mx.google.com with ESMTPS id u9sm831454eeh.17.2010.08.24.14.21.12
        (version=TLSv1/SSLv3 cipher=RC4-MD5);
        Tue, 24 Aug 2010 14:21:12 -0700 (PDT)
Content-Type: text/plain; charset=UTF-8
From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [issue64] Crash on sup start
In-reply-to: <1265688194.03.0.035958787068.issue64@masanjin.net>
References: <1265688194.03.0.035958787068.issue64@masanjin.net>
Date: Tue, 24 Aug 2010 23:21:10 +0200
Message-Id: <1282684816-sup-340@dolk>
User-Agent: Sup/git
Content-Transfer-Encoding: 8bit

Excerpts from anonymous's message of 2010-02-09 05:03:14 +0100:
> 
> New submission from anonymous:
> 
> sup crashed after I sent an email, and won't start anymore.
> 
> This is with the latest git version. Ubuntu/Karmic.
> 
> [Tue Feb 09 14:59:30 +1100 2010] ERROR: oh crap, an exception
> ----------------------------------------------------------------
> I'm very sorry. It seems that an error occurred in Sup. Please
> accept my sincere apologies. Please submit the contents of
> /home/brian/.sup/exception-log.txt and a brief report of the
> circumstances to http://masanjin.net/sup-bugs/ so that I might
> address this problem. Thank you!
> 
> Sincerely,
> William
> ----------------------------------------------------------------
> --- RuntimeError from thread: load threads for thread-index-mode
> 
> /home/brian/tree/sup/lib/sup/xapian_index.rb:348:in `find_docid'
> /home/brian/tree/sup/lib/sup/xapian_index.rb:353:in `find_doc'
> /home/brian/tree/sup/lib/sup/xapian_index.rb:363:in `get_entry'
> /home/brian/tree/sup/lib/sup/xapian_index.rb:77:in `build_message'
> /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
> /home/brian/tree/sup/lib/sup/xapian_index.rb:372:in `synchronize'
> /home/brian/tree/sup/lib/sup/xapian_index.rb:77:in `build_message'
> /home/brian/tree/sup/lib/sup/xapian_index.rb:121:in `each_id_by_date'
> /home/brian/tree/sup/lib/sup/thread.rb:332:in `call'
> /home/brian/tree/sup/lib/sup/thread.rb:332:in `load_n_threads'
> /home/brian/tree/sup/lib/sup/xapian_index.rb:121:in `each_id_by_date'
> /home/brian/tree/sup/lib/sup/xapian_index.rb:114:in `each_id'
> /home/brian/tree/sup/lib/sup/xapian_index.rb:114:in `each'
> /home/brian/tree/sup/lib/sup/xapian_index.rb:114:in `each_id'
> /home/brian/tree/sup/lib/sup/xapian_index.rb:121:in `each_id_by_date'
> /home/brian/tree/sup/lib/sup/thread.rb:328:in `load_n_threads'
> /home/brian/tree/sup/lib/sup/modes/thread-index-mode.rb:630:in 
> `__unprotected_load_n_threads'
> (eval):12:in `load_n_threads'
> /home/brian/tree/sup/lib/sup/modes/thread-index-mode.rb:614:in 
> `load_n_threads_background'
> /home/brian/tree/sup/lib/sup.rb:77:in `reporting_thread'
> /home/brian/tree/sup/lib/sup.rb:75:in `initialize'
> /home/brian/tree/sup/lib/sup.rb:75:in `new'
> /home/brian/tree/sup/lib/sup.rb:75:in `reporting_thread'
> /home/brian/tree/sup/lib/sup/modes/thread-index-mode.rb:613:in 
> `load_n_threads_background'
> /home/brian/tree/sup/lib/sup/modes/thread-index-mode.rb:684:in 
> `__unprotected_load_threads'
> (eval):12:in `load_threads'
> /home/brian/tree/sup/bin/sup:226
> 
> Brian May
> 
> ----------
> messages: 155
> nosy: anonymous
> priority: bug
> ruby_version: 4.2
> status: unread
> sup_version: git
> title: Crash on sup start
> 

This just happened to me as well. Commenting out the fail lets me start up.

- gaute