Public bug reported:
Working on a dell xps13 running Ubuntu 20.04, having a second display
connected to my laptop.
When disconnecting the 2nd display, first the application windows move
the built-in laptop display, but after one or two seconds the screen
went gray, telling me that an error has occured and that you need to log
in again.
I went through the journalctl, and noticed lots of messages as below:
Attempting to call back into JSAPI during the sweeping phase of GC. This
is most likely caused by not destroying a Clutter actor or Gtk+ widget
with ::destroy signals connected, but can also be caused by using the
destroy(), dispose(), or remove() vfuncs. Because it would crash the
application, it has been blocked and the JS callback not invoked.
Not sure if this is the actual cause though. After some googling I found bug
report #1857660 in which it was suggested to uninstall a few gnome extensions.
One of the mentioned extensions was indeed installed, but I removed (in the
end) all of them, rebooted but still problem occurs. And is reproducable in a
very simple way:
- Reboot & Login (with 2nd monitor attached)
- Open an app (not sure this is really needed to reproduce though)
- Disconnect the 2nd display and wait a second.
- Boom!
Useful to mention that the problem does not occur on Wayland, even with
the extensions installed (but with Wayland I can't share my full screen,
which I need for Slack :-( ).
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "journal.txt"
https://bugs.launchpad.net/bugs/1876802/+attachment/5366447/+files/journal.txt
--
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/1876802
Title:
Gnome (on Xorg) crashes when disconnecting external monitor
Status in gnome-shell package in Ubuntu:
New
Bug description:
Working on a dell xps13 running Ubuntu 20.04, having a second display
connected to my laptop.
When disconnecting the 2nd display, first the application windows move
the built-in laptop display, but after one or two seconds the screen
went gray, telling me that an error has occured and that you need to
log in again.
I went through the journalctl, and noticed lots of messages as below:
Attempting to call back into JSAPI during the sweeping phase of GC.
This is most likely caused by not destroying a Clutter actor or Gtk+
widget with ::destroy signals connected, but can also be caused by
using the destroy(), dispose(), or remove() vfuncs. Because it would
crash the application, it has been blocked and the JS callback not
invoked.
Not sure if this is the actual cause though. After some googling I found bug
report #1857660 in which it was suggested to uninstall a few gnome extensions.
One of the mentioned extensions was indeed installed, but I removed (in the
end) all of them, rebooted but still problem occurs. And is reproducable in a
very simple way:
- Reboot & Login (with 2nd monitor attached)
- Open an app (not sure this is really needed to reproduce though)
- Disconnect the 2nd display and wait a second.
- Boom!
Useful to mention that the problem does not occur on Wayland, even
with the extensions installed (but with Wayland I can't share my full
screen, which I need for Slack :-( ).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876802/+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
