Ubuntu
gnome-calendar package

gnome-calendar crashed with SIGSEGV in g_type_check_instance_cast()

Bug #1662354 reported by Paulo Novais
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-calendar (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Ubuntu Zesty Zapus (development branch) 64-bit
Intel® Core™ i5-3210M CPU @ 2.50GHz × 4 RAM 6 MB

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: gnome-calendar 3.22.2-1
ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
Uname: Linux 4.9.0-15-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Budgie:GNOME
Date: Mon Feb 6 22:34:56 2017
ExecutablePath: /usr/bin/gnome-calendar
ExecutableTimestamp: 1482199562
InstallationDate: Installed on 2017-01-07 (30 days ago)
InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Alpha amd64 (20170107)
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
ProcCwd: /home/paulo
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=pt:pt_BR:en
 PATH=(custom, no user)
 LANG=pt_PT.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f331528593a <g_type_check_instance_cast+26>: mov (%rdi),%r9
 PC (0x7f331528593a) ok
 source "(%rdi)" (0x000000ff) not located in a known VMA region (needed readable region)!
 destination "%r9" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-calendar crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Paulo Novais (apvnovais) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_cast () from /tmp/apport_sandbox_s19CfB/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 on_source_added (manager=<optimized out>, source=0x56340e3c9460, enabled=<optimized out>, self=0x56340e5424f0) at gcal-quick-add-popover.c:298
 ffi_call_unix64 () from /tmp/apport_sandbox_s19CfB/usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /tmp/apport_sandbox_s19CfB/usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /tmp/apport_sandbox_s19CfB/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0

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
tags: removed: need-amd64-retrace
Jean-Baptiste Lallement (jibel)
information type: Private → Public
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.
Subscribing...

Other bug subscribers

Remote bug watches

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