Via dup: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1886672

Adding some additional testing to my above comments.

*When second monitor is not removed*, i.e. remains connected, lock
screen/suspend resume all restore display as expected after latest
updates as suggested by Daniel in above linked dup.

Plugging display out, gnome adjusts to single screen settings as
expected. But plugging back the second monitor in does nothing.
Restarting gnome-shell resets displays as expected. I.e. working.

Also note not working in #26 regarding resuming laptop after plugging in
screen.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1877774

Title:
  gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  from st_theme_node_paint_equal() from st_widget_recompute_style() from
  st_widget_style_changed() [when locking the screen] [usually due to
  dash-to-panel]

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  GNOME shell crashes on extensions loading / updates

  [ Test case ]
   - No clear test case, normally may happen during screen locking/unlocking
   - But crashes should be monitored at
     https://errors.ubuntu.com/problem/4127e7e714fd28c090da0220de2ff06e71274eda

  [ Regression potential ]

  Stylesheet memory could be leaked

  ---

  Seems to be reproducible
  Suspend the computer
  Start the computer from suspend
  Start chrome gmail.
  Has happened two times

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.36.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu33
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  9 20:00:47 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-16 (23 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fe1b40c4252 <_st_theme_node_ensure_background+226>: 
mov    (%rax),%r12
   PC (0x7fe1b40c4252) ok
   source "(%rax)" (0x00000000) not located in a known VMA region (needed 
readable region)!
   destination "%r12" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   _st_theme_node_ensure_background () from /usr/lib/gnome-shell/libst-1.0.so
   st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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