gnome-calendar crashed with SIGSEGV in e_cal_data_model_subscribe()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-calendar (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Also, wen I've tried to add some new events the size of the windows gets oversized
ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: gnome-calendar 3.24.0-0ubuntu1
ProcVersionSign
Uname: Linux 4.10.0-15-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Wed Mar 29 19:38:30 2017
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-03-22 (6 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
ProcCmdline: /usr/bin/
ProcEnviron:
XDG_RUNTIME_
SHELL=/bin/bash
LANGUAGE=es_AR:es
PATH=(custom, no user)
LANG=es_AR.UTF-8
SegvAnalysis:
Segfault happened at: 0x555579e32a3b: mov (%rdx),%ecx
PC (0x555579e32a3b) ok
source "(%rdx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
e_cal_
Title: gnome-calendar crashed with SIGSEGV in e_cal_data_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #1666709, 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.