*** This bug is a duplicate of bug 1761466 ***
    https://bugs.launchpad.net/bugs/1761466

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1761466, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1813174/+attachment/5232219/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1813174/+attachment/5232221/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1813174/+attachment/5232225/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1813174/+attachment/5232226/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1813174/+attachment/5232227/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1813174/+attachment/5232228/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1813174/+attachment/5232229/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1761466

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  gnome-calendar crashes from time to time, I have not yet been able to
  find out what action is triggering this behaviour

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.28.2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 24 11:21:08 2019
  ExecutablePath: /usr/bin/gnome-calendar
  ExecutableTimestamp: 1527247751
  InstallationDate: Installed on 2016-04-29 (999 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  ProcCwd: /home/kstoilov
  SegvAnalysis:
   Segfault happened at: 0x55b7aff55041 <gcal_manager_is_client_writable+1>:    
mov    0x18(%rdi),%rdi
   PC (0x55b7aff55041) ok
   source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-calendar
  StacktraceTop:
   gcal_manager_is_client_writable ()
   ()
   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 
gcal_manager_is_client_writable()
  UpgradeStatus: Upgraded to bionic on 2018-08-04 (172 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin plugdev 
sambashare sudo

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