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 691284 - [abrt] Crash on alarm discard
[abrt] Crash on alarm discard
Status: RESOLVED OBSOLETE
Product: evolution-ews
Classification: Other
Component: Calendar
3.4.x
Other Linux
: Normal critical
: ---
Assigned To: Evolution EWS maintainer(s)
Evolution EWS maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-01-07 11:47 UTC by Milan Crha
Modified: 2013-01-11 10:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Crha 2013-01-07 11:47:22 UTC 
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=890448

Description of problem:
I just dismissed some calendar notifications when the crash occurred.

Version-Release number of selected component:
evolution-data-server-3.4.4-4.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        /usr/libexec/evolution-calendar-factory
crash_function: e_ews_connection_update_items_start
kernel:         3.6.10-2.fc17.x86_64

Core was generated by `/usr/libexec/evolution-calendar-factory'.
Program terminated with signal 11, Segmentation fault.

+ Trace 231347

Thread 1 (Thread 0x7fd685ffb700 (LWP 4476))

  • #0 e_ews_connection_update_items_start
    at e-ews-connection.c line 3217
  • #1 e_cal_backend_ews_discard_alarm
    at e-cal-backend-ews.c line 361
  • #2 operation_thread
    at e-data-cal.c line 247
  • #3 g_thread_pool_thread_proxy
    at gthreadpool.c line 309
  • #4 g_thread_proxy
    at gthread.c line 801
  • #5 start_thread
    at pthread_create.c line 309
  • #6 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 115 






Comment 1


Milan Crha





          2013-01-07 11:48:18 UTC
        



I know the 3.4.x is old, and 3.6.x will not crash, but claim a runtime warning, still it'll be good to investigate whether the 3.4.x crash uncovered anything or not.






Comment 2


Milan Crha





          2013-01-11 10:39:10 UTC
        



It seems it's about "when in offline", because otherwise it works as expected. When in offline, no connection object is available, thus one ends with NULL being used here, but the 3.6+ doesn't listen for evolution's offline state, and doesn't open EWS calendars when in offline (bug #678466), thus I'm currently unable to reproduce this, thus I'm closing this for now.