*** This bug is a duplicate of bug 1759474 *** https://bugs.launchpad.net/bugs/1759474
** Information type changed from Private to Public ** This bug has been marked a duplicate of bug 1759474 gnome-calendar (11) g_date_time_to_instant → g_date_time_to_timezone → g_date_time_to_local → split_event_widget_at_column → apply_overflow_at_weekday -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1759387 Title: gnome-calendar crashed with SIGSEGV in g_date_time_to_instant() Status in gnome-calendar package in Ubuntu: New Bug description: It crashed when I have clicked on the next month button in the toolbar. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 27 22:45:15 2018 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2018-03-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) JournalErrors: -- Logs begin at Tue 2018-03-27 10:24:33 CEST, end at Tue 2018-03-27 22:48:44 CEST. -- mar 27 11:04:14 hostname kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later) mar 27 11:04:17 hostname spice-vdagent[952]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 mar 27 11:04:23 hostname spice-vdagent[1407]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 mar 27 11:04:41 hostname pulseaudio[1280]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service ProcEnviron: XDG_RUNTIME_DIR=<set> SHELL=/bin/bash PATH=(custom, user) LANG=it_IT.UTF-8 SegvAnalysis: Segfault happened at: 0x7f0ed2bac3cc <g_date_time_to_timezone+12>: mov 0x10(%rdi),%esi PC (0x7f0ed2bac3cc) ok source "0x10(%rdi)" (0x00000010) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: g_date_time_to_timezone () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_date_time_to_local () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 gcal_week_header_add_event () gcal_week_header_set_date () ?? () Title: gnome-calendar crashed with SIGSEGV in g_date_time_to_timezone() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1759387/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp