mango-lassi segs at startup

[Dave Gilbert]

Binary package hint: mango-lassi

I have two machines on a local network.
I ran mango-lassi on the 1st machine (major) - it is apparently running.

I run it on the 2nd machine (davros) and it segs.
Both machines are running up to date maverick in 64bit.

Davros (on which I'm running this ubuntu-bug instance) is most recently upgraded - just an hour ago.

I've included a backtrace from bug-buddy.

Dave

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: mango-lassi 001+dfsg-1
ProcVersionSignature: Ubuntu 2.6.35-10.15-generic 2.6.35-rc5
Uname: Linux 2.6.35-10-generic x86_64
Architecture: amd64
Date: Sat Jul 24 20:27:09 2010
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
SourcePackage: mango-lassi

[Dave Gilbert (ubuntu-treblig)]

OK,
  1) This is fixed in the debian mango-lassi_001+dfsg-2 that debian has.
  2) It's an interaction with bug-buddy and likely a bug in it (which explains why it only triggers on one of my machines - since it had bug-buddy on from a long time ago)
  3) http://github.com/herzi/mango-lassi/issues/#issue/1 has the workaround which is adding:

   /* workaround bug-buddy using our logging handler in an unsave way
     * http://github.com/herzi/mango-lassi/issues/#issue/1
     * and
     * http://bugs.gnome.org/622068 */
    g_setenv ("GNOME_DISABLE_CRASH_DIALOG", "1", TRUE);

in src/lassi-server.c in main( right after the GError *error = NULL;

Dave

[Charlie Kravetz (cjkgeek)]

 Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here.

Thank you for the upstream bug reports.

Thanks for taking the time to make Ubuntu better!