[Bug 2069361] [NEW] Chrome does not tile correctly after disabling enhanced tiling
Public bug reported: Not sure under what package to file this under but I've disabled enhanced tiling due to issues I was having with it but now with it disabled for some reason Google Chrome does not tile correctly. When tiled using super+left/right, parts of the app end up behind the top panel and outside of the edge of the screen or the ubuntu dock. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4 Uname: Linux 6.8.0-35-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 13 17:00:17 2024 InstallationDate: Installed on 2024-06-04 (9 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Description changed: Not sure under what package to file this under but I've disabled enhanced tiling due to issues I was having with it but now with it disabled for some reason Google Chrome does not tile correctly. When tiled using super+left/right, parts of the app end up behind the top - panel and if tiled to where the ubuntu dock is, a part of the app is - behind the dock. + panel and outside of the edge of the screen or the ubuntu dock. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4 Uname: Linux 6.8.0-35-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 13 17:00:17 2024 InstallationDate: Installed on 2024-06-04 (9 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069361 Title: Chrome does not tile correctly after disabling enhanced tiling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2069361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051595] Re: Reapplying a layout with mapped applications makes the app unresponsive
I can reproduce this much more easily and consistently when tiling chrome and vscode both running under xwayland. e.g. 1. Tile vscode to the right (super+right) 2. Tile chrome to the left (super+left) 3. both apps are unresponsive to input, chrome can be seen flickering as in OPs video with gnome-text. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051595 Title: Reapplying a layout with mapped applications makes the app unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2051595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
Updated and now I can't reproduce. Looks like some update made it go away. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
fwiw I've checked Ubuntu 21.10/22.04, Fedora 35/36 and Arch. This only happens in Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968383] Re: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having b
** Description changed: Ubuntu 22.04 development fully updated as of time of this report. On a fresh boot, as soon as you open some applications and do the up touchpad gesture to enter the application grid and then back down to - return to the desktop, journal spits out js stacktrace and animations - become choppy. + return to the desktop, journal spits out js stacktrace. If you don't + trigger the crash then try opening and closing an app and trying again. Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968390] Re: JS ERROR: TypeError: this.window_container is null
** Description changed: Ubuntu 22.04 Development - - A 3 finger touchpad swipe up/down gesture with 1 application open outputs a lot of JS errors and stacks to the journal. This issue may be the same or related to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383 but the output is somewhat different when you have more than 1 app open. + A 3 finger touchpad swipe up/down gesture with 1 application open + outputs a lot of JS errors and stacks to the journal. This issue may be + the same or related to https://bugs.launchpad.net/ubuntu/+source/gnome- + shell/+bug/1968383 but the output is somewhat different when you have + more than 1 app open. This also happens with all extensions disabled, does not happen in Fedora 36. To reproduce 1. login and open terminal and watch the journal 2. perform the 3 finger swipe up gesture until the app grid displays then swipe down to go back to the desktop. 3. See journal + 4. If nothing happens try opening an app, closing it and try again. Apr 08 21:18:49 x1c gnome-shell[21675]: Object St.Button (0x56219f5b8060), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:566 (4ce0bb0ac40 @ 10) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:567 (4ce0bb0ac40 @ 36) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:570 (4ce0bb0ac40 @ 77) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:638 (4ce0bb0ae20 @ 23) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:353 (4ce0bb0a5b0 @ 62) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:357 (4ce0bb0a5b0 @ 87) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:364 (4ce0bb0a600 @ 8) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0aa640 I self-hosted:205 (330c4e3bed80 @ 272) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222) Apr 08 21:18:49 x1c gnome-shell[21675]: #3 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 7ffc4c0a99a0 b resource:///org/gnome/shell/ui/environment.js:160 (330c4e3cc560 @ 43) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0a9a70 b resource:///org/gnome/shell/ui/environment.js:369 (330c4e3ccd30 @ 23) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:365 (4ce0bb0a600 @ 109) Apr 08 21:18:49 x1c gnome-shell[21675]: #3 7ffc4c0aa640 I self-hosted:205 (330c4e3bed80 @ 272) Apr 08 21:18:49 x1c gnome-shell[21675]: #4 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222) Apr 08 21:18:49 x1c gnome-shell[21675]: #5 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: Object St.Label (0x56219f5a8440), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 21:18:49 x1c gnome-shell[21675]: #0 7ffc4c0a98b0 b resource:///org/gnome/shell/ui/environment.js:361 (330c4e3ccc90 @ 43) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0a99a0 b resource:///org/gnome/shell/ui/environment.js:163 (330c4e3cc560 @ 91) Apr 08 21:18:49 x1c
[Bug 1968383] Re: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having b
** Description changed: Ubuntu 22.04 development fully updated as of time of this report. On a fresh boot, as soon as you open some applications and do the up touchpad gesture to enter the application grid and then back down to - return to the desktop, journal spits out js stacktrace. + return to the desktop, journal spits out js stacktrace and animations + become choppy. Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968390] [NEW] JS ERROR: TypeError: this.window_container is null
Public bug reported: Ubuntu 22.04 Development A 3 finger touchpad swipe up/down gesture with 1 application open outputs a lot of JS errors and stacks to the journal. This issue may be the same or related to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383 but the output is somewhat different when you have more than 1 app open. This also happens with all extensions disabled, does not happen in Fedora 36. To reproduce 1. login and open terminal and watch the journal 2. perform the 3 finger swipe up gesture until the app grid displays then swipe down to go back to the desktop. 3. See journal Apr 08 21:18:49 x1c gnome-shell[21675]: Object St.Button (0x56219f5b8060), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:566 (4ce0bb0ac40 @ 10) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:567 (4ce0bb0ac40 @ 36) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:570 (4ce0bb0ac40 @ 77) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:638 (4ce0bb0ae20 @ 23) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:353 (4ce0bb0a5b0 @ 62) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:357 (4ce0bb0a5b0 @ 87) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:364 (4ce0bb0a600 @ 8) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0aa640 I self-hosted:205 (330c4e3bed80 @ 272) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222) Apr 08 21:18:49 x1c gnome-shell[21675]: #3 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: #0 7ffc4c0a99a0 b resource:///org/gnome/shell/ui/environment.js:160 (330c4e3cc560 @ 43) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0a9a70 b resource:///org/gnome/shell/ui/environment.js:369 (330c4e3ccd30 @ 23) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:365 (4ce0bb0a600 @ 109) Apr 08 21:18:49 x1c gnome-shell[21675]: #3 7ffc4c0aa640 I self-hosted:205 (330c4e3bed80 @ 272) Apr 08 21:18:49 x1c gnome-shell[21675]: #4 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222) Apr 08 21:18:49 x1c gnome-shell[21675]: #5 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == Apr 08 21:18:49 x1c gnome-shell[21675]: Object St.Label (0x56219f5a8440), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 21:18:49 x1c gnome-shell[21675]: #0 7ffc4c0a98b0 b resource:///org/gnome/shell/ui/environment.js:361 (330c4e3ccc90 @ 43) Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0a99a0 b resource:///org/gnome/shell/ui/environment.js:163 (330c4e3cc560 @ 91) Apr 08 21:18:49 x1c gnome-shell[21675]: #2 7ffc4c0a9a70 b resource:///org/gnome/shell/ui/environment.js:369 (330c4e3ccd30 @ 23) Apr 08 21:18:49 x1c gnome-shell[21675]: #3 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:365 (4ce0bb0a600 @ 109) Apr 08 21:18:49 x1c gnome-shell[21675]: #4 7ffc4c0aa640 I self-hosted:205 (330c4e3bed80 @ 272) Apr 08 21:18:49 x1c gnome-shell[21675]: #5 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222) Apr 08
[Bug 1968383] Re: Touch gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been
** Description changed: Ubuntu 22.04 development fully updated as of time of this report. On a fresh boot, as soon as you open some applications and do the up - touch gesture to enter the application grid and then back down to return - to the desktop, journal spits out js stacktrace. + touchpad gesture to enter the application grid and then back down to + return to the desktop, journal spits out js stacktrace. Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ** Summary changed: - Touch gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. + Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
I am seeing this in 22.04 and an easy way for me to reproduce is on a fresh login, open a terminal and watch the log, open Brave/Chrome, for some reason the first time you open the browser it has a GTK title bar which goes away on closing/reopening the app, now right clicking in the terminal window or opening the hamburger menu and bringing up the menu triggers this message in the logs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968383] [NEW] Touch gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having be
Public bug reported: Ubuntu 22.04 development fully updated as of time of this report. On a fresh boot, as soon as you open some applications and do the up touch gesture to enter the application grid and then back down to return to the desktop, journal spits out js stacktrace. Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968383 Title: Touch gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949352] Re: Removable drives are not auto-mounted after screen lock/unlock
Fixed here as well, tested same steps as #17. Just wanted to add tested version is 70~ubuntu3.21.10.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949352 Title: Removable drives are not auto-mounted after screen lock/unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1949352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
Hi Daniel, sorry for the late reply, it does look very similar to bug 1863416, the only difference is it's happening in wayland for me. Contrary to what I said above I can't consistently reproduce the problem but I do still see these messages in the journal, but no idea how to reproduce them. I ran that apport command but got this message: Package gtk+3.0 not installed and no hook available, ignoring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870597] Re: libinput says "your system is too slow"
I'm getting spammed by libinput messages about the system being slow. A couple of patches in libinput were merged to master about month ago that rate limits some messages that previously were not, and should at least stop the spamming of messages, if you use a wireless mouse for example the journal gets flooded if you're doing a lot of mouse movements. Please consider backporting these. https://gitlab.freedesktop.org/libinput/libinput/-/commit/a1e9150210abda0d3dd41127330cd7985d29957d https://gitlab.freedesktop.org/libinput/libinput/-/commit/64a49d18b948a5b8ac88da9207689af356a081cf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870597 Title: libinput says "your system is too slow" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
** Package changed: gnome-terminal (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1951878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
* I found out how to repro. Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 If I leave any gtk apps open e.g. gnome-terminal, evince, Files open, and then open Google Chrome with the flags to enable wayland support --enable-features=UseOzonePlatform --ozone-platform=wayland Then any gtk app that was open outputs the following message to journal after any UI interaction, like switching tabs, opening context menu, etc. gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window This persists until each individual app is restarted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1951878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951878] [NEW] "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
Public bug reported: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1951878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951786] Re: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated
Can confirm, does not happen with dock disabled. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951786 Title: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1951786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951786] [NEW] Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated
Public bug reported: on Ubuntu 21.10 gnome-shell 40.5-1ubuntu2 Locking desktop and then unlocking it makes gnome-shell spit out a stack trace. v 22 02:00:49 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated — impossible to access it. This might be caused by the> Nov 22 02:00:49 saturn gnome-shell[33781]: == Stack trace for context 0x5572c18e3130 == Nov 22 02:00:49 saturn gnome-shell[33781]: #0 7ffcbc579470 b resource:///org/gnome/gjs/modules/core/overrides/GObject.js:567 (22c5be1b1d80 @ 25) Nov 22 02:00:49 saturn gnome-shell[33781]: #1 5572c8ea2dc0 i resource:///org/gnome/shell/ui/components/autorunManager.js:159 (374b9f3380 @ 31) Nov 22 02:00:49 saturn gnome-shell[33781]: #2 7ffcbc57a1d0 b resource:///org/gnome/shell/ui/components/__init__.js:56 (374b9d7650 @ 66) Nov 22 02:00:49 saturn gnome-shell[33781]: #3 7ffcbc57a960 b resource:///org/gnome/shell/ui/components/__init__.js:22 (374b9d7790 @ 15) Nov 22 02:00:49 saturn gnome-shell[33781]: #4 7ffcbc57b030 b self-hosted:225 (374b92ab50 @ 273) Nov 22 02:00:49 saturn gnome-shell[33781]: #5 5572c8ea2d30 i resource:///org/gnome/shell/ui/components/__init__.js:22 (374b9d78d0 @ 110) ...skipping... Nov 22 02:04:21 saturn gnome-shell[33781]: #7 7ffcbc578a80 b resource:///org/gnome/shell/ui/sessionMode.js:200 (25da4d8e6d30 @ 284) Nov 22 02:04:21 saturn gnome-shell[33781]: #8 7ffcbc579630 b resource:///org/gnome/shell/ui/sessionMode.js:168 (25da4d8e6e20 @ 116) Nov 22 02:04:21 saturn gnome-shell[33781]: #9 7ffcbc579dc0 b resource:///org/gnome/shell/ui/screenShield.js:574 (25da4d8d4a60 @ 79) Nov 22 02:04:21 saturn gnome-shell[33781]: #10 7ffcbc57a550 b resource:///org/gnome/shell/ui/screenShield.js:565 (25da4d8d4ab0 @ 17) Nov 22 02:04:21 saturn gnome-shell[33781]: #11 7ffcbc57acd0 b resource:///org/gnome/shell/gdm/authPrompt.js:604 (25da4d8f24c0 @ 65) Nov 22 02:04:21 saturn gnome-shell[33781]: #12 7ffcbc57b460 b resource:///org/gnome/shell/ui/unlockDialog.js:871 (374b9053d0 @ 40) Nov 22 02:04:21 saturn gnome-shell[33781]: #13 7ffcbc57bbf0 b resource:///org/gnome/shell/ui/screenShield.js:565 (25da4d8d4b00 @ 50) Nov 22 02:04:21 saturn gnome-shell[33781]: #14 7ffcbc57c380 b resource:///org/gnome/shell/ui/screenShield.js:116 (25da4d8dc6f0 @ 13) Nov 22 02:04:21 saturn gnome-shell[33781]: #15 7ffcbc57ca50 b resource:///org/gnome/gjs/modules/core/_signals.js:114 (22c5be1b1330 @ 439) Nov 22 02:04:21 saturn gnome-shell[33781]: #16 5572c39ba218 i resource:///org/gnome/gjs/modules/core/overrides/Gio.js:152 (22c5be1a5b50 @ 39) Nov 22 02:04:21 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated — impossible to connect to any signal on it. This migh> Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Nov 22 02:04:21 saturn dbus-daemon[33727]: [session uid=1000 pid=33727] Activating service name='org.freedesktop.FileManager1' requested by ':1.20' (uid=1000 pid=33781 comm> Nov 22 02:04:21 saturn gnome-shell[33781]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Nov 22 02:04:21 saturn gnome-shell[33781]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Nov 22 02:04:21 saturn gnome-shell[33781]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Nov 22 02:04:21 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated — impossible to access it. This might be caused by the> Nov 22 02:04:21 saturn gnome-shell[33781]: g_volume_monitor_get_volumes: assertion 'G_IS_VOLUME_MONITOR (volume_monitor)' failed Nov 22 02:04:21 saturn gnome-shell[33781]: == Stack trace for context 0x5572c18e3130 == Nov 22 02:04:21 saturn gnome-shell[33781]: #0 5572c39ba218 i resource:///org/gnome/shell/ui/components/automountManager.js:66 (374b9f3e20 @ 30) Nov 22 02:04:21 saturn gnome-shell[33781]: #1 7ffcbc57d550 b self-hosted:850 (374b92a650 @ 398) Nov 22 02:04:21 saturn NetworkManager[1054]: [1637564661.8704] agent-manager: agent[70e63220a742bb64,:1.631/org.gnome.Shell.NetworkAgent/1000]: agent registered Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Nov 22 02:04:21 saturn gnome-shell[33781]: cr_declaration_parse_list_from_buf: assertion 'parser' failed ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951786 Title: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated To manage notifications about this bug go
[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
I get this all the time after resuming from sleep, unfortunately with wayland it's not possible to reload gnome-shell so I have to log out/in to get rid of it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848119] Re: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695]
3.34.1+git20191107-1ubuntu1~19.10.1 Confirmed fixed here too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848119 Title: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1848119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848119] Re: gnome-shell infinite error loop when closing app in activities overview
I also reported this upstream https://gitlab.gnome.org/GNOME/gnome- shell/issues/1791 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848119 Title: gnome-shell infinite error loop when closing app in activities overview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848119] Re: gnome-shell infinite error loop when closing app in activities overview
There's nothing in /var/crash related to this. I guess I associated stack traces with crashes, perhaps error is the appropriate description here. I've edited the title and description to reflect this. ** Summary changed: - gnome-shell infinite crash loop when closing app in activities overview + gnome-shell infinite error loop when closing app in activities overview ** Description changed: Ubuntu 19.10 on Xorg gnome-shell 3.34.1-1ubuntu1 How to reproduce: 1) Open terminal and watch journalct -f 2) Open Files 3) Close Files in the activities overview - 4) gnome-shell loop crashes non stop. - + 4) gnome-shell errors in journal non stop. Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 0x55aead0b5360 == Oct 14 23:25:38 titan gnome-shell[9919]: #0 55aeae6f3910 i resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15) Oct 14 23:25:38 titan gnome-shell[9919]: #1 7ffd96c5e360 b self-hosted:975 (7f438c12dee0 @ 392) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1791 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1791 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848119 Title: gnome-shell infinite error loop when closing app in activities overview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848119] [NEW] gnome-shell infinite crash loop when closing app in activities overview
Public bug reported: Ubuntu 19.10 on Xorg gnome-shell 3.34.1-1ubuntu1 How to reproduce: 1) Open terminal and watch journalct -f 2) Open Files 3) Close Files in the activities overview 4) gnome-shell loop crashes non stop. Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 0x55aead0b5360 == Oct 14 23:25:38 titan gnome-shell[9919]: #0 55aeae6f3910 i resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15) Oct 14 23:25:38 titan gnome-shell[9919]: #1 7ffd96c5e360 b self-hosted:975 (7f438c12dee0 @ 392) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848119 Title: gnome-shell infinite crash loop when closing app in activities overview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
Getting this on 19.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764417 Title: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734095] Re: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]
I can also reproduce this reliably in Disco. I tried to enable Canonical Partner packages so I think it's easy to trigger. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734095 Title: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1734095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825623] Re: [AppIndicatorSupport-FATAL] unable to update overlay icon
I see this error in the logs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825623 Title: [AppIndicatorSupport-FATAL] unable to update overlay icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1825623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
I'm sorry, I no longer use Ubuntu on my machines. But I can confirm this happened to me when the lockscreen is active. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772677 Title: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)
Apologies, this is indeed still happening in 18.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772677 Title: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)
It's been removed from 18.10. On Thu, Oct 11, 2018 at 9:51 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Is anyone seeing this bug in Ubuntu 18.10 or is it already fixed there? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1772677 > > Title: > gnome-shell filling up syslog with thousands of entries (stack traces > ending in osdWindow.js:206/207) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772677/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772677 Title: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792702] Re: gnome-shell filling /var/log/syslog with "Object St.Icon|BoxLayout (...), has been already finalized. Impossible to set any property to it."
Same behavior in Gnome 3.30.1 in 18.10 Beta. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792702 Title: gnome-shell filling /var/log/syslog with "Object St.Icon|BoxLayout (...), has been already finalized. Impossible to set any property to it." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792702] Re: gnome-shell filling /var/log/syslog with "Object St.Icon|BoxLayout (...), has been already finalized. Impossible to set any property to it."
Same behavior, happens when screen is locked, log grew close to 1 GB in less then 1 hour locked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792702 Title: gnome-shell filling /var/log/syslog with "Object St.Icon|BoxLayout (...), has been already finalized. Impossible to set any property to it." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579580] Re: ureadahead reports relative path errors in journalctl output
I would just remove ureadahead using apt. It's just another canonical project that nobody has looked at in years and not a priority. I see no difference whatsoever without it and maybe you won't either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739468] Re: Repeated [AppIndicatorSupport-WARN] Item :1.51/org/ayatana/NotificationItem/multiload is already registered
This problem is compounded by the fact that rsyslog is duplicating journal logging. Getting huge log files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739468 Title: Repeated [AppIndicatorSupport-WARN] Item :1.51/org/ayatana/NotificationItem/multiload is already registered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1739468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 987933] Re: 10de:0407 Ubuntu 12.04 shutdown hangs with proprietary nVidia driver
This problem seems to affect 32 bit version of Ubuntu. I just realized my working xubuntu install was 64 bit as opposed to the 32 bit I was using for Ubuntu. So I decided to try out 64 bit Ubuntu and guess what? Shuts down and reboots as expected every single time and I've been using for a couple of days and have not experienced any hangs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/987933 Title: 10de:0407 Ubuntu 12.04 shutdown hangs with proprietary nVidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 987933] Re: 10de:0407 Ubuntu 12.04 shutdown hangs with proprietary nVidia driver
I have tried with both default nouveau and nvidia-current without problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/987933 Title: 10de:0407 Ubuntu 12.04 shutdown hangs with proprietary nVidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 987933] Re: Ubuntu 12.04 shutdown hangs
This has been driving me crazy. I tried everything recommended and could not get rid of the problem. I too could shutdown or reboot if I did it immediately following booting into the login screen, but once I logged on and used the machine for a bit of time it would hang always if I tried shutting down or rebooting. I have a Dell Inspiron 1420 with nvidia card, I tried the nouveau drivers and nothing, same thing. Then I installed xubuntu 12.04 on the same machine with nvidia-current and low and behold! It shuts down and reboots like a champ every single time no matter what I do. Something is definitely wrong in something that is unique to Ubuntu that does not affect xubuntu and maybe other variants. I have also installed Fedora 17 Gnome 3 in the same computer and did not have this problem. Could be related to Unity. Sorry I don't have more but for anybody who cannot get rid of this you can try either going for Xubuntu from scratch or try to installed xfce on top of regular ubuntu and see if the problem persists. For me I went for a fresh install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/987933 Title: Ubuntu 12.04 shutdown hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 987220] Re: System does not power off reliably when Shut Down chosen from GUI
I was sufferring from this, eventually installed Xubuntu 12.04 and all was well See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987933/comments/8 If anybody else goes this route please let us know if you are still affected. In my case I can shutdown and reboot without problem and using any driver, nvidia-current and nouveau. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/987220 Title: System does not power off reliably when Shut Down chosen from GUI To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/987220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 364232] Re: HP Pavilion dv9000 hangs on boot if power is not plugged in
I had the same problem, adding pci=noacpi to the kernel parameters worked for me. Suspend to ram doesn't work though. -- HP Pavilion dv9000 hangs on boot if power is not plugged in https://bugs.launchpad.net/bugs/364232 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs