From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] evolution segfaults
Date: Tue, 21 Apr 2009 06:48:09 -0700 [thread overview]
Message-ID: <5bdc1c8b0904210648x377eaed9i1b47712b50be7c1d@mail.gmail.com> (raw)
In-Reply-To: <1240320571.8730.106.camel@camille.espersunited.com>
On Tue, Apr 21, 2009 at 6:29 AM, Michael Sullivan <msulli1355@gmail.com> wrote:
<SNIP>
> amy@catherine ~ $ evolution
> ** (evolution:19607): DEBUG: mailto URL command: evolution %s
> ** (evolution:19607): DEBUG: mailto URL program: evolution
> Segmentation fault
>
> Nothing shows up in ~/.xsession-errors. Not much shows up
> in /var/log/messages:
>
> catherine X11 # grep evolution /var/log/messages
> Apr 17 22:25:56 catherine [133453.338825] evolution[24366]: segfault at
> 36303632 ip b6def622 sp bff36500 error 4 in
> libcamel-provider-1.2.so.14.0.0[b6dcf000+59000]
<SNIP>
emerge -1pv libcamel-provider ???
revdep-rebuild -p ???
>
> catherine X11 # emerge -pv evolution
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild R ] mail-client/evolution-2.24.5 USE="crypt dbus hal nntp
> ssl -debug -kerberos -krb4 -ldap -mono -networkmanager -pda -profile" 0
> kB
>
Why hal?
Did you look in the gdm logs? (In /var/log/gdm)
Note that I've had trouble on my wife's machine with segfaults since
the xorg-server upgrade. I just downgraded my compiler and rebuilt the
machine. Waste of time so far. Segfaults are still there.
- Mark
next prev parent reply other threads:[~2009-04-21 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 13:29 [gentoo-user] evolution segfaults Michael Sullivan
2009-04-21 13:48 ` Mark Knecht [this message]
2009-04-21 15:18 ` Michael Sullivan
2009-04-21 15:26 ` Xavier Parizet
2009-04-21 17:55 ` Michael Sullivan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5bdc1c8b0904210648x377eaed9i1b47712b50be7c1d@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox