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

1754202 does not seem to exist so I cannot confirm it's the same bug

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

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

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  shortly after the virtual machine started. host arch linux. gues
  ubuntu budgie 18.04

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.27.90-1build1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sat Mar 10 20:02:54 2018
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2018-03-09 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
  JournalErrors:
   -- Logs begin at Fri 2018-03-09 19:52:42 CET, end at Sun 2018-03-11 10:22:52 
CET. --
   mar 11 10:21:03 username-VirtualBox systemd[1]: Failed to start 
vboxadd-service.service.
   mar 11 10:21:15 username-VirtualBox spice-vdagent[1638]: Cannot access 
vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
   mar 11 10:21:16 username-VirtualBox pulseaudio[1727]: [pulseaudio] pid.c: 
Daemon already running.
   mar 11 10:21:41 username-VirtualBox pulseaudio[1662]: [pulseaudio] 
bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: 
Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f6472db4517 <gtk_image_clear+7>:    mov    
0x28(%rdi),%rbp
   PC (0x7f6472db4517) 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 () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /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 lpadmin plugdev sambashare sudo

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

Reply via email to