apport information
** Tags added: apport-collected third-party-packages
** Description changed:
My system is up-to-date on:
$ lsb_release -rd
Description: Ubuntu 18.10
Release: 18.10
$ apt-cache policy gnome-shell
gnome-shell:
Installed: 3.30.2-0ubuntu1.18.10.1
Candidate: 3.30.2-0ubuntu1.18.10.1
To provide you with an idea of the motivation for the origin in gnome-
shell; I've included the lines in syslog that are displayed for many
more occasions than presented below.
At the times that these messages are displayed in my logs I can still
move my mouse, but mouse clicks are unresponsive and typing is frozen
(but text does appear after freeze).
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: 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.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was
g-signal on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: 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.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was
g-signal on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: 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.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was
g-signal on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: 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.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was
g-signal on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: 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.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was
g-signal on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: 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.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was
g-signal on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: 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.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was
g-signal on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: 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.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was
g-signal on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: 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.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was
g-signal on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: 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.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for
context 0x55f9f7a3f220 ==
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu13.2
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 18.10
+ InstallationDate: Installed on 2019-03-07 (41 days ago)
+ InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
+ Package: gnome-shell 3.30.2-0ubuntu1.18.10.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
+ Tags: cosmic third-party-packages
+ Uname: Linux 4.18.0-17-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1825197/+attachment/5256635/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825197
Title:
system unresponse for several seconds a couple of times per hour
[Attempting to call back into JSAPI during the sweeping phase of
GC...]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825197/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
