Bug#553213: balsa: Balsa crashes when opening a window as mail arrives
Peter Bloomfield
peterbloomfield at bellsouth.net
Fri Nov 6 23:57:51 UTC 2009
On 11/06/2009 06:27:55 PM Fri, Karl O. Pinc wrote:
>
> ** (balsa:13747): CRITICAL **: lbmss_stream_reset: assertion
> `lbmss_thread_has_lock(stream)' failed
>
> could be a false lead. I have occasionally started balsa
> twice by accident.
>
> Is there any way to get timestamps in ~/.xsession-errors?
>
> Karl <kop at meme.com>
> Free Software: "You don't pay back, you pay forward."
> -- Robert A. Heinlein
>
>
That's probably not caused by two instances of Balsa--it's an internal
check on the code. If it's reproducible, could you run Balsa under gdb
with --g-fatal-warnings and get a back-trace? That would be really
helpful.
Balsa tries to avoid starting multiple instances, in the past using
BonoboActivation, and more recently using LibUnique. If you can start
more than one instance, I guess neither mechanism is working!
Peter
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20091106/bed89e97/attachment.pgp>
More information about the pkg-gnome-maintainers
mailing list