segfault at 18 ip 0000000000425ca4 sp 00007ffe07d73380 error 4 in gnome-calendar
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-calendar (Ubuntu) |
Invalid
|
High
|
Unassigned |
Bug Description
I found following error in dmesg after running and closing gonome-calendar:
segfault at 18 ip 0000000000425ca4 sp 00007ffe07d73380 error 4 in gnome-calendar
No other sign of failure except for this.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-calendar 3.20.1-1ubuntu1
ProcVersionSign
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Apr 23 12:02:54 2016
InstallationDate: Installed on 2013-04-24 (1095 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
SourcePackage: gnome-calendar
UpgradeStatus: Upgraded to xenial on 2016-03-23 (31 days ago)
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.
If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.
Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. _my_crash_ report. crash' where _my_crash_ report. crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/ _my_crash_ report. crash'.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/
I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.