Public bug reported:

I can consistently crash gnome-calendar by dragging it from one monitor
over to the other monitor at the top of the screen so that it moves into
full screen. It seems to move to that screen with the window resized but
the contents not redrawn.

Focal with all updates as of 25-mar. Reproducible multiple times.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-calendar 3.36.0-1
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 25 15:56:02 2020
ExecutablePath: /usr/bin/gnome-calendar
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
 PATH=(custom, no user)
 Segfault happened at: 0x7f3696bd795d <gdk_rgba_to_string+13>:  movsd  
 PC (0x7f3696bd795d) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed 
readable region)!
 destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-calendar
 gdk_rgba_to_string () at /usr/lib/x86_64-linux-gnu/
 () at /usr/lib/x86_64-linux-gnu/
 g_object_new_valist () at /usr/lib/x86_64-linux-gnu/
Title: gnome-calendar crashed with SIGSEGV in gdk_rgba_to_string()
UpgradeStatus: Upgraded to focal on 2019-07-08 (261 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sbuild 
sudo wireshark

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

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

** Information type changed from Private to Public

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  [focal] gnome-calendar crashes when moving it full screen to another
  screen (SIGSEGV in gdk_rgba_to_string())

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to