*** This bug is a duplicate of bug 1754202 ***
https://bugs.launchpad.net/bugs/1754202
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 #1754202, 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/1761309/+attachment/5101952/+files/CoreDump.gz
** Attachment removed: "Disassembly.txt"
https://bugs.launchpad.net/bugs/1761309/+attachment/5101954/+files/Disassembly.txt
** Attachment removed: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/1761309/+attachment/5101957/+files/ProcMaps.txt
** Attachment removed: "ProcStatus.txt"
https://bugs.launchpad.net/bugs/1761309/+attachment/5101958/+files/ProcStatus.txt
** Attachment removed: "Registers.txt"
https://bugs.launchpad.net/bugs/1761309/+attachment/5101959/+files/Registers.txt
** Attachment removed: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1761309/+attachment/5101960/+files/Stacktrace.txt
** Attachment removed: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1761309/+attachment/5101961/+files/ThreadStacktrace.txt
** This bug has been marked a duplicate of bug 1754202
gnome-calendar crashed with SIGSEGV in gtk_image_reset()
** 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/1761309
Title:
gnome-calendar crashed with SIGSEGV in gtk_image_clear()
Status in gnome-calendar package in Ubuntu:
New
Bug description:
hung when trying to add google
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-calendar 3.28.0-1
ProcVersionSignature: Ubuntu 4.15.0-14.15-generic 4.15.15
Uname: Linux 4.15.0-14-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 4 16:49:10 2018
ExecutablePath: /usr/bin/gnome-calendar
InstallationDate: Installed on 2018-04-01 (2 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64
(20180228)
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
ProcEnviron:
XDG_RUNTIME_DIR=<set>
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f363487c667 <gtk_image_clear+7>: mov
0x28(%rdi),%rbp
PC (0x7f363487c667) 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: Upgraded to bionic on 2018-04-04 (0 days ago)
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/1761309/+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
