Public bug reported:

ubuntu bionic. in beta. I think the issue might be location service on

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-calendar 3.28.0-1
Uname: Linux 4.15.14-041514-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Apr  4 20:45:25 2018
ExecutablePath: /usr/bin/gnome-calendar
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7f4b0be1c667 <gtk_image_clear+7>:      mov    
0x28(%rdi),%rbp
 PC (0x7f4b0be1c667) ok
 source "0x28(%rdi)" (0x00000028) not located in a known VMA region (needed 
readable region)!
 destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
 gtk_image_clear () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ()
 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-calendar crashed with SIGSEGV in gtk_image_clear()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo

** Affects: gnome-calendar (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-crash bionic need-amd64-retrace third-party-packages

** Information type changed from Private to Public

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

Title:
  gnome-calendar crashed with SIGSEGV in gtk_image_clear()

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  ubuntu bionic. in beta. I think the issue might be location service on

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.28.0-1
  Uname: Linux 4.15.14-041514-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Apr  4 20:45:25 2018
  ExecutablePath: /usr/bin/gnome-calendar
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f4b0be1c667 <gtk_image_clear+7>:    mov    
0x28(%rdi),%rbp
   PC (0x7f4b0be1c667) ok
   source "0x28(%rdi)" (0x00000028) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-calendar
  StacktraceTop:
   gtk_image_clear () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-calendar crashed with SIGSEGV in gtk_image_clear()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1761224/+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