gnome-calendar crashed with SIGSEGV in GCAL_IS_MANAGER()

Bug #1723569 reported by Soungjin Park
30
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gnome-calendar (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

It crashes after some minutes after start gnome-calendar with no window appearing.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-calendar 3.26.2-1
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Sat Oct 14 12:34:23 2017
ExecutablePath: /usr/bin/gnome-calendar
InstallationDate: Installed on 2017-09-27 (16 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 (20170912)
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=ko_KR
 PATH=(custom, no user)
 LANG=ko_KR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x559b69098046 <gcal_manager_get_source+22>: mov (%rbx),%rdx
 PC (0x559b69098046) ok
 source "(%rbx)" (0x00000450) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
 gcal_manager_get_source ()
 ()
 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-calendar crashed with SIGSEGV in gcal_manager_get_source()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Soungjin Park (xcomart) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 GCAL_IS_MANAGER (ptr=0x450) at ../src/gcal-manager.h:34
 gcal_manager_get_source (self=0x450, uid=0x7f7c6c080aa0 "975163d4094bbee92398e15f414f6afde4f718a3") at ../src/gcal-manager.c:1149
 add_source (manager=<optimized out>, source=0x7f7c6c078300, enabled=<optimized out>, user_data=0x559b69a80230) at ../src/gcal-source-dialog.c:321
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7ffe2d7d8290, fn=fn@entry=0x559b690a0a30 <add_source>, rvalue=<optimized out>, avalue=avalue@entry=0x7ffe2d7d81a0) at ../src/x86/ffi64.c:525

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-calendar (Ubuntu):
importance: Undecided → Medium
summary: - gnome-calendar crashed with SIGSEGV in gcal_manager_get_source()
+ gnome-calendar crashed with SIGSEGV in GCAL_IS_MANAGER()
tags: removed: need-amd64-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

information type: Private → Public
tags: added: bionic
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-calendar (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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