The crash seems to be in the monitor numbering displayed while the
Settings app is open:
[ 749.493355] decuman gnome-shell[6575]: GNOME Shell crashed with signal 11
[ 749.493355] decuman gnome-shell[6575]: == Stack trace for context
0x6044d87c2ac0 ==
[ 749.493709] decuman gnome-shell[6575]: #0 6044d888f0c0 i
resource:///org/gnome/shell/ui/osdMonitorLabeler.js:104 (db8b9a7ad80 @ 119)
[ 749.493709] decuman gnome-shell[6575]: #1 6044d888f000 i
resource:///org/gnome/shell/ui/shellDBus.js:354 (3db34bd71ce0 @ 349)
[ 749.493709] decuman gnome-shell[6575]: #2 6044d888ef58 i
self-hosted:1461 (3db34bd2a0b0 @ 30)
[ 749.493709] decuman gnome-shell[6575]: #3 7fffdf22a8e0 b self-hosted:852
(2491ea6c40 @ 15)
[ 749.493709] decuman gnome-shell[6575]: #4 6044d888eec8 i
resource:///org/gnome/shell/ui/init.js:21 (1ab9ad470bf0 @ 48)
That could have the same root cause as a lost display config if the
detected display specs are changing during wakeup.
** Summary changed:
- On high resolution modes, after screen resume from power saving, the display
configuration gets lost, and sometimes Gnome crashes
+ [nvidia] On high resolution modes, after screen resume from power saving, the
display configuration gets lost, and sometimes Gnome crashes
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081199
Title:
[nvidia] On high resolution modes, after screen resume from power
saving, the display configuration gets lost, and sometimes Gnome
crashes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2081199/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
