Re: [Evolution] Checking for new mail ...
- From: Bart Steanes <bart steanes gmail com>
- To: Milan Crha <mcrha redhat com>
- Cc: evolution-list gnome org
- Subject: Re: [Evolution] Checking for new mail ...
- Date: Fri, 4 Mar 2011 01:25:56 +1100
On 2 March 2011 18:05, Milan Crha
<mcrha redhat com> wrote:
On Wed, 2011-03-02 at 03:29 +1100, Bart Steanes wrote:
> And as if scanning the whole inbox wasn't bad enough, the scanning
> process (otherwise known as "Checking for new mail") usually fails.
Hi,
any error message given or just stuck? The error message can ba also on
console, thus please run evo from console. If stuck, could you install
debug-info packages for all evolution-related packages you use and get a
backtrace of running evolution to see where it is stuck, please?
Well, it keeps running, but the gui is "mostly stuck"?
The console messages I get from invoking evolution are -
[bart falcon5 /]$ evolution --force-shutdown
No response from Evolution -- killing the process
[bart falcon5 /]$ evolution
e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results)
e-data-server-ui-Message: Key file does not have group 'Passwords-Exchange'
e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results)
e-data-server-ui-Message: Key file does not have group 'Passwords-Exchange'
(evolution:6360): camel-exchange-provider-WARNING **: got_new_smtp_messages: 7
(evolution:6360): camel-exchange-provider-WARNING **: got_new_smtp_messages: 7
<no further output, and evolution appears to be working normally atm>
For packages I meant evolution-data-server, evolution,
evolution-exchange/evolution-mapi (if you use either), and gtkhtml3.
I already have all the debug packages loaded from when I used to make daily crash reports.
To get a backtrace it's usually enough to get PID of running evolution
and invoke this:
$ gdb --batch --ex "t a a bt" -pid=PID &>bt.txt
then the bt.txt should have contain the backtrace.
Bye,
Milan\
So I have a backtrace from during a sync (bt.txt), then another from the start of the next sync attempt (bt2.txt).
I hope they help.
--
ta
Bart
@ home - mailto:
bart steanes gmail com+61 4 2687 2712
Attachment:
bt2.txt
Description: Text document
Attachment:
bt.txt
Description: Text document
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]