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 562145 - Evolution Mail and Calendar: When trying to access th...
Evolution Mail and Calendar: When trying to access th...
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-11-24 16:54 UTC by jp.boyer
Modified: 2008-11-26 11:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description jp.boyer 2008-11-24 16:54:41 UTC 
When trying to access the Calendar, either via the button or the menu item, Evolution simply closes. 
I am running Ubuntu 8.10 with latest updates, and Evolution is up-to-date 2.4.1.1


Distribution: Ubuntu 8.10 (intrepid)
Gnome Release: 2.24.1 2008-10-24 (Ubuntu)
BugBuddy Version: 2.24.1
Comment 1 André Klapper 2008-11-24 17:33:47 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 2 jp.boyer 2008-11-24 20:48:00 UTC 
(In reply to comment #1)
> 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!
> 
I got the following trace. But this time, for whatever reason, I was able to switch to Calendar, but then Evolution froze and I had to force it to quit:
(gdb) cont
Continuing.
[New Thread 0xb48e6b90 (LWP 15611)]
[New Thread 0xb5a90b90 (LWP 15614)]
[New Thread 0xb528fb90 (LWP 15615)]
[Thread 0xb528fb90 (LWP 15615) exited]
[New Thread 0xb528fb90 (LWP 15616)]
[New Thread 0xb3ddab90 (LWP 15618)]
[New Thread 0xb29ffb90 (LWP 15619)]
[Thread 0xb29ffb90 (LWP 15619) exited]
[Thread 0xb3ddab90 (LWP 15618) exited]
[New Thread 0xb3ddab90 (LWP 15620)]
[New Thread 0xb29ffb90 (LWP 15621)]
[Thread 0xb29ffb90 (LWP 15621) exited]
[Thread 0xb3ddab90 (LWP 15620) exited]
[New Thread 0xb3ddab90 (LWP 15622)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6431940 (LWP 15516)]
0xb62a2ec5 in ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so
(gdb) thread apply all bt

+ Trace 210193

Thread 1 (Thread 0xb6431940 (LWP 15516))

  • #0 ??
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #1 ??
    from /usr/lib/libgobject-2.0.so.0
  • #2 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #3 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #4 idle_dates_changed
    at ea-cal-view.c line 280
  • #5 ??
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #9 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #10 main
    at main.c line 689 
I'll try to get a trace when Evolution quits after clicking on the calendar button.
Thank you!
Comment 3 jp.boyer 2008-11-24 20:58:44 UTC 
(In reply to comment #1)
> 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!
> 

I tried several times:
- when I have the trace on (using gdb), I cannot get Evolution to terminate by clicking the 'calendar' button. When I click the button, the calendar opens bu Evolution freezes.
- when I have no tracing on, if I click the 'calendar' button, then Evolution terminates suddenly before opening the calendar.

I hope that helps.
Comment 4 jp.boyer 2008-11-24 21:03:25 UTC 
(In reply to comment #3)
> (In reply to comment #1)
> > 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!
> > 
> 
> I tried several times:
> - when I have the trace on (using gdb), I cannot get Evolution to terminate by
> clicking the 'calendar' button. When I click the button, the calendar opens bu
> Evolution freezes.
> - when I have no tracing on, if I click the 'calendar' button, then Evolution
> terminates suddenly before opening the calendar.
> 
> I hope that helps.
> 
Correction... When Evolution terminates it does open the calendar before shuting down, so briefly that I did not notice before.
Comment 5 Akhil Laddha 2008-11-25 03:58:27 UTC 
For time being, disable accessibility.

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but
we are happy to tell you that the problem has already been fixed. It should be
solved in the next software version. You may want to check for a software
upgrade.
Comment 6 jp.boyer 2008-11-26 09:31:36 UTC 
(In reply to comment #5)
> For time being, disable accessibility.
> 
> Thanks for taking the time to report this bug.
> This particular bug has already been reported into our bug tracking system, but
> we are happy to tell you that the problem has already been fixed. It should be
> solved in the next software version. You may want to check for a software
> upgrade.
> 

Thank you very much! 
I'll wait for the update then.
Comment 7 Akhil Laddha 2008-11-26 11:09:14 UTC 

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