(1) Pedro: running evolution now does not generate a new crash file in
/var/crash (which
may be a separate bug). The old crash from a day ago or so does not contain
debug
symbols. Do I have to invoke /usr/bin/evolution with a wrapper script or
something
to get it to generate a /var/crash log?
I know C/C++ and (non-debian) linux reasonably well, and if evolution
can be recompiled on my machine with a few apt-get's and make,
I'd be happy to do so if you can provide directions. If this is complex
to explain how to do, never mind.
The question is: how simple are the commands necessary to
*** This bug is a duplicate of bug 185588 ***
https://bugs.launchpad.net/bugs/185588
Public bug reported:
Binary package hint: evolution-data-server
/etc/lsb-release contains:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION=Ubuntu hardy (development
*** This bug is a duplicate of bug 185588 ***
https://bugs.launchpad.net/bugs/185588
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/12215114/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/12215115/Dependencies.txt
** Attachment added:
Public bug reported:
Binary package hint: evolution
cat /etc/lsb-release:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION=Ubuntu hardy (development branch)
dpkg -l evolution:
||/ Name VersionDescription
