Public bug reported:
crashed on log out with weather
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-calendar 3.28.0-1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME-Classic:GNOME
Date: Fri Mar 30 16:37:42 2018
ExecutablePath: /usr/bin/gnome-calendar
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
ProcEnviron:
XDG_RUNTIME_DIR=<set>
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7fe7941d2667 <gtk_image_clear+7>: mov
0x28(%rdi),%rbp
PC (0x7fe7941d2667) 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: Upgraded to bionic on 2018-03-20 (10 days ago)
UserGroups: 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/1760230
Title:
gnome-calendar crashed with SIGSEGV in gtk_image_clear()
Status in gnome-calendar package in Ubuntu:
New
Bug description:
crashed on log out with weather
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-calendar 3.28.0-1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME-Classic:GNOME
Date: Fri Mar 30 16:37:42 2018
ExecutablePath: /usr/bin/gnome-calendar
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
ProcEnviron:
XDG_RUNTIME_DIR=<set>
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7fe7941d2667 <gtk_image_clear+7>: mov
0x28(%rdi),%rbp
PC (0x7fe7941d2667) 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: Upgraded to bionic on 2018-03-20 (10 days ago)
UserGroups: sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1760230/+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
