Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Changed in: gnome-calendar (Ubuntu)
       Status: New => Invalid

-- 
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/1872805

Title:
  gnome-calendar crashes on launch

Status in gnome-calendar package in Ubuntu:
  Invalid

Bug description:
  On start, crashes with the following errors:

  
  (gnome-calendar:518114): GcalEvent-CRITICAL **: 21:09:58.835: 
gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed

  (gnome-calendar:518114): GcalEvent-CRITICAL **: 21:09:58.835:
  gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed

  (gnome-calendar:518114): GLib-GObject-CRITICAL **: 21:09:58.835:
  g_object_new_valist: invalid object type '

  (gnome-calendar:518114): GcalContext-CRITICAL **: 21:09:58.835:
  gcal_context_get_clock: assertion 'GCAL_IS_CONTEXT (self)' failed

  (gnome-calendar:518114): GLib-GObject-WARNING **: 21:09:58.835:
  invalid (NULL) pointer instance

  (gnome-calendar:518114): GLib-GObject-CRITICAL **: 21:09:58.835:
  g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)'
  failed

  (gnome-calendar:518114): GcalEvent-CRITICAL **: 21:09:58.835:
  gcal_event_get_date_start: assertion 'GCAL_IS_EVENT (self)' failed

  (gnome-calendar:518114): GcalEvent-CRITICAL **: 21:09:58.835:
  gcal_event_get_date_end: assertion 'GCAL_IS_EVENT (self)' failed

  (gnome-calendar:518114): GcalEvent-CRITICAL **: 21:09:58.835:
  gcal_event_get_color: assertion 'GCAL_IS_EVENT (self)' failed

  (gnome-calendar:518114): GLib-CRITICAL **: 21:09:58.835: 
g_date_time_difference: assertion 'end != NULL' failed
  Segmentation fault (core dumped)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-calendar 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue Apr 14 21:08:48 2020
  InstallationDate: Installed on 2020-03-17 (28 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1872805/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to