** Tags added: oem-priority originate-from-1967530 somerville
** Changed in: oem-priority
Status: New => Confirmed
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Assignee: (unassigned) => Andy Chi (andch)
--
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/1976204
Title:
system freeze and gnome-shell reports multiple stack trace
Status in OEM Priority Project:
Confirmed
Status in gnome-shell package in Ubuntu:
New
Bug description:
[Summary]
The system will run into freeze if I connect the external monitor through
DP/HDMI with dongle DA310 or Docking WD19TB
[Steps to reproduce]
1. Attact DA310 or WD19TB to DUT
2. Cold Boot into OS
3. Plug the DP/HDMI cable to DA310 or WD19TB
4. Check the external monitor has signal
5. Click keyboard or move mouse to check system can work well
[Expected result]
System won't be freeze with external monitor.
[Actual result]
System will be freeze.
It can be recovered after unplug the external monitor sometime.
[gnome-shell stack trace]
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning:
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning:
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning:
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]:
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0'
failed
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ;
PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session
opened for user root(uid=0) by ubuntu(uid=1001)
五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session
closed for user root
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: 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.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context
0x56156f8f04a0 ==
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context
0x56156f8f04a0 ==
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was
window-added on MetaWorkspace 0x56156f916640.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: 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.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was
window-added on MetaWorkspace 0x56156f916640.
五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: 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.
This system is using OLED (3456x2160) panel, and I can't reproduce
this issue on FHD panel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1976204/+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
