gnome-calendar crashed with SIGSEGV in gcal_manager_refresh()

Bug #1680691 reported by jc00ke
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-calendar (Ubuntu)
New
Undecided
Unassigned

Bug Description

All I did was try to add and remove online accounts, specifically for Exchange.

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: gnome-calendar 3.24.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
Uname: Linux 4.10.0-15-generic x86_64
ApportVersion: 2.20.4-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Apr 6 21:34:39 2017
ExecutablePath: /usr/bin/gnome-calendar
InstallationDate: Installed on 2017-03-25 (12 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
ProcEnviron:
 SHELL=/usr/bin/fish
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x55b41bba6b08 <gcal_manager_refresh+24>: mov 0x18(%rdi),%rdi
 PC (0x55b41bba6b08) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
 gcal_manager_refresh ()
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-calendar crashed with SIGSEGV in gcal_manager_refresh()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
jc00ke (jesse-jc00ke) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1505077, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.