Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 466207 - Crash when using Calendar
Summary: Crash when using Calendar
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 10
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F10Target
TreeView+ depends on / blocked
 
Reported: 2008-10-09 07:46 UTC by Denis Leroy
Modified: 2009-06-29 01:59 UTC (History)
3 users (show)

Fixed In Version: evolution-2.26.2-1.fc11
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-29 01:59:01 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
GDB session during crash (7.34 KB, text/plain)
2008-10-09 07:46 UTC, Denis Leroy 		no flags Details
GDB session, all debuginfo installed. (7.85 KB, text/plain)
2008-10-09 14:29 UTC, Denis Leroy 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 560329 0 None None None Never

Description Denis Leroy 2008-10-09 07:46:34 UTC 
Created attachment 319833 [details]
GDB session during crash

Somebody on #fedora-qa reported evolution instability with a Google calendar conencted. I was quickly able to reproduce. Stack trace attached. Seems to come from ea-cal-view.c, line 280:

g_signal_emit_by_name (ea_cal_view, "children_changed", NULL);


I've reproduced the crash several times pretty easily, typically by just "playing around" with the calendar stuff, changing the view, enabling/disabling, etc... Crash always comes from line above.

I would recommend to mark this a F10 blocker.
Comment 1 Matthew Barnes 2008-10-09 12:58:23 UTC 
Thanks for the backtrace.

Looks like this is accessibility-related, and I see some atk symbols missing from the trace.  Would you mind installing atk-debuginfo and attempting to reproduce the crash again?
Comment 2 Denis Leroy 2008-10-09 14:29:25 UTC 
Created attachment 319864 [details]
GDB session, all debuginfo installed.

I also recompiled at-spi with '-g3 -O0' for extra info. This bug is easily reproducible.
Comment 3 Matthew Barnes 2008-10-09 14:37:27 UTC 
Great!  Thanks for the extra info.
Comment 4 Denis Leroy 2008-10-09 14:46:46 UTC 
"valgrind -q evolution"

shows invalid reads in the same at-spi code section.
Comment 5 Denis Leroy 2008-10-11 08:39:26 UTC 
Changing subject, as it doesn't appear to be strictly related to the Google feature.
Comment 6 Jerry Amundson 2008-10-12 05:21:58 UTC 
Possible connection upstream?
Comment 7 Milan Crha 2008-11-05 13:03:20 UTC 
This [1] is more accurate upstream bug, than the old one (357608). Close this as upstream? There is some patch already, done by Matt, awaiting the review.

[1] http://bugzilla.gnome.org/show_bug.cgi?id=530776
Comment 8 Bug Zapper 2008-11-26 03:41:20 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 9 Matthew Barnes 2009-06-29 01:59:01 UTC 
According to [1] this bug should be fixed now in Fedora 11.
Please reopen if this is not the case.

[1] http://bugzilla.gnome.org/show_bug.cgi?id=560329
Note You need to log in before you can comment on or make changes to this bug.