| 2020-02-20 20:33:27 |
Clinton H |
description |
1) Ubuntu 19.10
2) GNOME Shell 3.34.1
3) no error.
4) error in log app.
Dec 25 2:57:16 PM gnome-shell-ext: The offending signal was destroy on Gjs_ExtensionRow 0x561b4774bee0.
Dec 25 2:57:16 PM gnome-shell-ext: The offending signal was destroy on Gjs_ExtensionRow 0x561b4774bee0.
Dec 25 2:57:16 PM gnome-shell-ext: 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.
Dec 25 2:57:16 PM gnome-shell-ext: The offending signal was destroy on Gjs_ExtensionRow 0x561b4774bbe0.
Dec 25 2:57:16 PM gnome-shell-ext: 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.
Dec 25 2:57:16 PM gnome-shell-ext: The offending signal was destroy on Gjs_ExtensionRow 0x561b4774b5e0.
Dec 25 2:57:16 PM gnome-shell-ext: 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.
Dec 25 2:57:16 PM gnome-shell-ext: The offending signal was destroy on Gjs_ExtensionRow 0x561b4774b2e0.
Dec 25 2:57:16 PM gnome-shell-ext: 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.
Dec 25 2:57:16 PM gnome-shell: == Stack trace for context 0x561b46fae1a0 ==
Dec 25 2:57:16 PM gnome-shell-ext: The offending signal was destroy on Gjs_ExtensionRow 0x561b4774b8e0. |
1) Ubuntu 19.10
2) GNOME Shell 3.34.1
3) no error.
4) error in log app.
Dec 25 2:57:16 PM gnome-shell-ext: The offending signal was destroy on Gjs_ExtensionRow 0x561b4774bee0.
Dec 25 2:57:16 PM gnome-shell-ext: The offending signal was destroy on Gjs_ExtensionRow 0x561b4774bee0.
Dec 25 2:57:16 PM gnome-shell-ext: 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.
Dec 25 2:57:16 PM gnome-shell-ext: The offending signal was destroy on Gjs_ExtensionRow 0x561b4774bbe0.
Dec 25 2:57:16 PM gnome-shell-ext: 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.
Dec 25 2:57:16 PM gnome-shell-ext: The offending signal was destroy on Gjs_ExtensionRow 0x561b4774b5e0.
Dec 25 2:57:16 PM gnome-shell-ext: 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.
Dec 25 2:57:16 PM gnome-shell-ext: The offending signal was destroy on Gjs_ExtensionRow 0x561b4774b2e0.
Dec 25 2:57:16 PM gnome-shell-ext: 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.
Dec 25 2:57:16 PM gnome-shell: == Stack trace for context 0x561b46fae1a0 ==
Dec 25 2:57:16 PM gnome-shell-ext: The offending signal was destroy on Gjs_ExtensionRow 0x561b4774b8e0.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2019-10-28 (115 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
Tags: wayland-session eoan
Uname: Linux 5.3.0-26-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True |
|
