After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 557861 - Evolution Mail and Calendar: Switching to the calenda...
Evolution Mail and Calendar: Switching to the calenda...
Status: RESOLVED DUPLICATE of bug 560329
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.24.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-10-25 13:58 UTC by mike
Modified: 2008-11-13 08:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description mike 2008-10-25 13:58:50 UTC
Switching to the calendar crashes the application


Distribution: Ubuntu 8.10 (intrepid)
Gnome Release: 2.24.1 2008-10-24 (Ubuntu)
BugBuddy Version: 2.24.1
Comment 1 mike 2008-10-25 21:29:47 UTC
Oct 25 17:17:38 desktop kernel: [  284.173681] evolution[6216]: segfault at 8508458b ip b6187eb5 sp bf869fc0 error 4 in libatk-bridge.so[b6184000+6000]
Comment 2 André Klapper 2008-10-26 22:34:54 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 3 mike 2008-10-27 02:20:20 UTC
I installed the -dbg packages, and clicked on the calendar which promptly caused evolution to disappear, however no bug buddy appeared, I tried a number of times.
Comment 4 mike 2008-10-27 02:28:29 UTC
I do have the debug for libatk-bridge.so installed, so I would expect this to start bug buddy up

[ 3542.520351] evolution[7033]: segfault at 8508458b ip b62f1eb5 sp bf8d3a80 error 4 in libatk-bridge.so[b62ee000+6000]
[ 3565.126624] evolution[7237]: segfault at 8508458b ip b62a0eb5 sp bf882d50 error 4 in libatk-bridge.so[b629d000+6000]
[ 3892.924561] evolution[7538]: segfault at 8508458b ip b62b9eb5 sp bf89bd60 error 4 in libatk-bridge.so[b62b6000+6000]
[ 4074.156945] firefox[7726]: segfault at b7a1da9e ip b7d57571 sp bfdf4f34 error 4 in libc-2.8.90.so[b7d29000+158000]
[ 4131.400473] evolution[7682]: segfault at 8508458b ip b61c7eb5 sp bfda7a70 error 4 in libatk-bridge.so[b61c4000+6000]
Comment 5 mike 2008-10-27 02:36:23 UTC
sorry for all the posts, I just kept trying things, and normaly at work I woudl start with gdb :-)

mike@desktop:~$ gdb evolution
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(gdb) run
Starting program: /usr/bin/evolution 
[Thread debugging using libthread_db enabled]
[New Thread 0xb6467940 (LWP 8078)]
** (evolution:8078): DEBUG: mailto URL command: evolution %s
** (evolution:8078): DEBUG: mailto URL program: evolution
[New Thread 0xb5ac1b90 (LWP 8085)]
[New Thread 0xb52c0b90 (LWP 8086)]
[Thread 0xb52c0b90 (LWP 8086) exited]
[Thread 0xb5ac1b90 (LWP 8085) exited]
[New Thread 0xb52c0b90 (LWP 8087)]
[New Thread 0xb480ab90 (LWP 8089)]
[New Thread 0xb5ac1b90 (LWP 8092)]
[New Thread 0xb47c9b90 (LWP 8093)]
[Thread 0xb47c9b90 (LWP 8093) exited]
[Thread 0xb52c0b90 (LWP 8087) exited]
[New Thread 0xb52c0b90 (LWP 8094)]
[New Thread 0xb47c9b90 (LWP 8095)]
[New Thread 0xb3dffb90 (LWP 8096)]
[Thread 0xb47c9b90 (LWP 8095) exited]
[Thread 0xb3dffb90 (LWP 8096) exited]
[New Thread 0xb3dffb90 (LWP 8097)]
[New Thread 0xb47c9b90 (LWP 8098)]
[Thread 0xb47c9b90 (LWP 8098) exited]
[Thread 0xb3dffb90 (LWP 8097) exited]
[Thread 0xb5ac1b90 (LWP 8092) exited]
[New Thread 0xb5ac1b90 (LWP 8100)]
[New Thread 0xb3dffb90 (LWP 8103)]
[New Thread 0xb47c9b90 (LWP 8104)]
Changing the queries (contains? "summary" "") 
[New Thread 0xb3411b90 (LWP 8105)]
[New Thread 0xb2c10b90 (LWP 8106)]

(evolution:8078): camel-imap-provider-WARNING **: Unable to load summary no such table: Friends


(evolution:8078): camel-imap-provider-WARNING **: Unable to load summary no such table: [Gmail]


(evolution:8078): camel-imap-provider-WARNING **: Unable to load summary no such table: login


(evolution:8078): camel-imap-provider-WARNING **: Unable to load summary no such table: receipt


(evolution:8078): camel-imap-provider-WARNING **: Unable to load summary no such table: wine

[Thread 0xb52c0b90 (LWP 8094) exited]
[Thread 0xb3dffb90 (LWP 8103) exited]
[Thread 0xb5ac1b90 (LWP 8100) exited]
[Thread 0xb2c10b90 (LWP 8106) exited]
[Thread 0xb3411b90 (LWP 8105) exited]
[New Thread 0xb3411b90 (LWP 8111)]
[New Thread 0xb2c10b90 (LWP 8112)]
[Thread 0xb3411b90 (LWP 8111) exited]
[Thread 0xb47c9b90 (LWP 8104) exited]
[Thread 0xb2c10b90 (LWP 8112) exited]
[New Thread 0xb2c10b90 (LWP 8113)]
[Thread 0xb2c10b90 (LWP 8113) exited]

Program exited normally
Comment 6 André Klapper 2008-10-27 09:50:21 UTC
gdb is a good approach (see the link I posted), however "Program exited normally".
Comment 7 mike 2008-10-27 11:28:47 UTC
The evolution application disappears instantly when not in gdb. My reading of it is that it must decide to exit, its not a segfault, but it is a crash from the users perspective. I was hoping the camel-imap-provider-WARNING  messages might mean something to you, its the only abnormal status indication other than the whole thing closing.
Comment 8 Akhil Laddha 2008-10-28 06:02:35 UTC
(evolution:8078): camel-imap-provider-WARNING **: Unable to load summary no
such table: login

This warning comes when you are loading summary first time and haven't visited the folder yet. It will go away once you visit the folder. It doesn't indicate more than that.  
Comment 9 mike 2008-10-28 16:41:21 UTC
I can't really take this much further, I have no experience with gnome and evolution. The calendar is unusable as the whole applications disappears if used.
The -dbg symbols have not fired the bug buddy and gdb allows it to run. I do get the attached segfaults when not in gdb.
In my experience this dual behavior in the debugger is often because debug builds have values inserted to normally un-initialized variables.

Let me know if I can run anything else for anyone.
Comment 10 Kandepu Prasad 2008-11-13 08:33:19 UTC
This is accessibility bug. Dup.Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 560329 ***