[Desktop-packages] [Bug 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
Hi, should gnome-shell-extension-ubuntu-dock 87ubuntu2 have already migrated from mantic-proposed? I'm assuming this process is automatic. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-tiling-assistant source package in Mantic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Committed Bug description: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] Introspected types are not defined and so extensions may try to use undefined code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+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
[Desktop-packages] [Bug 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
Thanks Pablo, I must've done something wrong. Installed it now and issue solved for me on mantic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-tiling-assistant source package in Mantic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Committed Bug description: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] Introspected types are not defined and so extensions may try to use undefined code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+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
[Desktop-packages] [Bug 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
how can I install gnome-shell-extension-ubuntu-dock (87ubuntu2) for mantic? I don't see it in proposed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-tiling-assistant source package in Mantic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Committed Bug description: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] Introspected types are not defined and so extensions may try to use undefined code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+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
[Desktop-packages] [Bug 2037655] [NEW] dbuss apparmor="DENIED" interface="org.gnome.Mutter.IdleMonitor" spamming logs
Public bug reported: On the latest 23.10 Mantic beta using firefox 118.0 spams the log with message: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gnome/Mutter/IdleMonitor/Core" interface="org.gnome.Mutter.IdleMonitor" member="GetIdletime" mask="send" name=":1.34" pid=6444 label="snap.firefox.firefox" peer_pid=3234 peer_label="unconfined" ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Description changed: - On the latest Mantic beta using firefox spams the log with message: + On the latest 23.10 Mantic beta using firefox 118.0 spams the log with + message: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gnome/Mutter/IdleMonitor/Core" interface="org.gnome.Mutter.IdleMonitor" member="GetIdletime" mask="send" name=":1.34" pid=6444 label="snap.firefox.firefox" peer_pid=3234 peer_label="unconfined" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2037655 Title: dbuss apparmor="DENIED" interface="org.gnome.Mutter.IdleMonitor" spamming logs Status in firefox package in Ubuntu: New Bug description: On the latest 23.10 Mantic beta using firefox 118.0 spams the log with message: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gnome/Mutter/IdleMonitor/Core" interface="org.gnome.Mutter.IdleMonitor" member="GetIdletime" mask="send" name=":1.34" pid=6444 label="snap.firefox.firefox" peer_pid=3234 peer_label="unconfined" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2037655/+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
[Desktop-packages] [Bug 2037345] Re: error saving a new vpn
Same here, and to add even though the VPN was apparently not created, after rebooting or restarting NetworkManager the VPN is now there and now I'm not able to delete it without it coming back on next reboot. I've also tried deleting it using Advanced Network Configuration but it does not stick. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037345 Title: error saving a new vpn Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I tried adding a new openvpn. I filled in all the information, but after I click the save button, it returns me to the network settings list, but that vpn is not present. Release: 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037345/+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
[Desktop-packages] [Bug 2037256] Re: 23.10 maximize window shortcut missing on fresh install
*** This bug is a duplicate of bug 2034998 *** https://bugs.launchpad.net/bugs/2034998 ** Tags added: mantic -- 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/2037256 Title: 23.10 maximize window shortcut missing on fresh install Status in gnome-shell package in Ubuntu: New Bug description: Sorry not sure what package to file this bug. On a fresh 23.10 Beta install the usual default shortcut for maximizing the current window (Meta + Up) is disabled by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037256/+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
[Desktop-packages] [Bug 2037256] [NEW] 23.10 maximize window shortcut missing on fresh install
Public bug reported: Sorry not sure what package to file this bug. On a fresh 23.10 Beta install the usual default shortcut for maximizing the current window (Meta + Up) is disabled by default. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/2037256 Title: 23.10 maximize window shortcut missing on fresh install Status in gnome-shell package in Ubuntu: New Bug description: Sorry not sure what package to file this bug. On a fresh 23.10 Beta install the usual default shortcut for maximizing the current window (Meta + Up) is disabled by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037256/+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
[Desktop-packages] [Bug 2037115] [NEW] Focus is not given when a new window is launched from overview
Public bug reported: Ubuntu 23.04 Lunar Mutter 44.3 upstream bug https://gitlab.gnome.org/GNOME/mutter/-/issues/2690 >From the upstream bug: "When opening a new app window from the overview, the window focus is not properly given to the new window and the user input still go to the old focused window. Both windows appear to be in focus, however, the old window has the proper focus." This may cause data loss or security issues due to input still going to another application if the user is not aware. This appears to be fixed in the latest mutter release 44.5, any chance we can get this in Lunar? Thanks. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Description changed: + Ubuntu 23.04 Lunar + Mutter 44.3 + upstream bug https://gitlab.gnome.org/GNOME/mutter/-/issues/2690 From the upstream bug: "When opening a new app window from the overview, the window focus is not properly given to the new window and the user input still go to the old focused window. Both windows appear to be in focus, however, the old window has the proper focus." This may cause data loss or security issues due to input still going to another application if the user is not aware. This appears to be fixed in the latest mutter release 44.5, any chance we can get this in Lunar? Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2037115 Title: Focus is not given when a new window is launched from overview Status in mutter package in Ubuntu: New Bug description: Ubuntu 23.04 Lunar Mutter 44.3 upstream bug https://gitlab.gnome.org/GNOME/mutter/-/issues/2690 From the upstream bug: "When opening a new app window from the overview, the window focus is not properly given to the new window and the user input still go to the old focused window. Both windows appear to be in focus, however, the old window has the proper focus." This may cause data loss or security issues due to input still going to another application if the user is not aware. This appears to be fixed in the latest mutter release 44.5, any chance we can get this in Lunar? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2037115/+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
[Desktop-packages] [Bug 2017907] Re: cups-browsed high CPU usage
*** This bug is a duplicate of bug 2018504 *** https://bugs.launchpad.net/bugs/2018504 I have again experienced this after the update that was intended to address this. Just today I found cups-browsed using 100% CPU. This is on 23.04 Lunar with 2.0~rc1-0ubuntu1.1 cups-browsed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/2017907 Title: cups-browsed high CPU usage Status in cups-filters package in Ubuntu: Confirmed Bug description: Hi, Using Lunar wifi connected to an enterprise network. cups-browsed uses a lot of CPU %, I need to kill it to save my battery. 2.0rc1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2017907/+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
[Desktop-packages] [Bug 1987976] Re: firefox black window on wayland
that was it, appears to be fixed on my end. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1987976 Title: firefox black window on wayland Status in Mozilla Firefox: Unknown Status in Mutter: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: [ Impact ] On some systems, when you open the Firefox snap right after having logged in into an Ubuntu on Wayland session, you are met by a black window. This happens because the FF snap is run under Xwayland, and Xwayland may not be enabled early enough to handle the start of the application properly. You can easily reproduce the issue in a Wayland session: * Close Firefox * Run the command "killall Xwayland" in terminal * Open Firefox An upstream mutter change addresses this issue, and the proposed lunar change cherry picks that upstream change as a patch. [ Test Plan ] On an updated Ubuntu 23.04: * Install the mutter related binaries from lunar-proposed * Reboot and log in to an Ubuntu on Wayland session * Run the command "killall Xwayland" * Open the Firefox snap, and find that it starts normally [ Where problems could occur ] This is the upstream merge request in question: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970 The changes (except for the test related ones) are small, and specifically intended to address issues like the one reported in this bug. There are also reviews by a couple of experienced GNOME devs. So even if the proposed change is not well tested yet, it seems to me that the risk for adverse side effects is limited. [ Original description ] nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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
[Desktop-packages] [Bug 1987976] Re: firefox black window on wayland
On 23.04 I still get a black window on first firefox start with the proposed mutter update. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1987976 Title: firefox black window on wayland Status in Mozilla Firefox: Unknown Status in Mutter: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: [ Impact ] On some systems, when you open the Firefox snap right after having logged in into an Ubuntu on Wayland session, you are met by a black window. This happens because the FF snap is run under Xwayland, and Xwayland may not be enabled early enough to handle the start of the application properly. You can easily reproduce the issue in a Wayland session: * Close Firefox * Run the command "killall Xwayland" in terminal * Open Firefox An upstream mutter change addresses this issue, and the proposed lunar change cherry picks that upstream change as a patch. [ Test Plan ] On an updated Ubuntu 23.04: * Install the mutter related binaries from lunar-proposed * Reboot and log in to an Ubuntu on Wayland session * Run the command "killall Xwayland" * Open the Firefox snap, and find that it starts normally [ Where problems could occur ] This is the upstream merge request in question: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970 The changes (except for the test related ones) are small, and specifically intended to address issues like the one reported in this bug. There are also reviews by a couple of experienced GNOME devs. So even if the proposed change is not well tested yet, it seems to me that the risk for adverse side effects is limited. [ Original description ] nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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
[Desktop-packages] [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 Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gtk+3.0 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+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
[Desktop-packages] [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 Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gtk+3.0 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+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
[Desktop-packages] [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
** 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 Desktop Packages, which is subscribed to gnome-shell in 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. Status in gnome-shell package in Ubuntu: New Bug description: 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. 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383/+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
[Desktop-packages] [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
[Desktop-packages] [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
** 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 Desktop Packages, which is subscribed to gnome-shell in 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. Status in gnome-shell package in Ubuntu: New Bug description: 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. 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383/+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
[Desktop-packages] [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
[Desktop-packages] [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
** 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 Desktop Packages, which is subscribed to gnome-shell in 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. Status in gnome-shell package in Ubuntu: New Bug description: 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. 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. To manage notifications about this bug go to:
[Desktop-packages] [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 Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gtk+3.0 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+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
[Desktop-packages] [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 t
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 Desktop Packages, which is subscribed to gnome-shell in 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. Status in gnome-shell package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383/+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
[Desktop-packages] [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 Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1870597 Title: libinput says "your system is too slow" Status in GNOME Shell: Unknown Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm- x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Inspiron 5570 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed quiet splash --- ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870597/+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
[Desktop-packages] [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 Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in mutter package in Ubuntu: Confirmed Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1951878/+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
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gnome-terminal package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1951878/+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
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gnome-terminal package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1951878/+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
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1951786 Title: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: 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
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1951786 Title: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated Status in gnome-shell
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in 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] Status in gnome-shell package in Ubuntu: Confirmed Bug description: In disco, when policykit prompted me for a password in order for update-manager to dispatch instructions to aptdaemon to perform package updates, the password dialog remained on the screen after I clicked 'authenticate'. The window is not clickable, it appears not to even be a window - mouse presses are received by the window underneath. The exception is that the 'cancel' button is active and receives mouse events - but clicking it does nothing. This may be a gnome-shell issue rather than policykit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: policykit-1 0.105-25 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 13:14:33 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: policykit-1 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/+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
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in 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] Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Eoan: Won't Fix Status in mutter source package in Eoan: Fix Committed Status in gnome-shell source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Released Status in gnome-shell package in Fedora: Confirmed Bug description: [ Impact ] Gnome shell fills the journal with errors as soon as a view is closed from the overview Ubuntu 19.10 on Xorg gnome-shell 3.34.1-1ubuntu1 [ Test case ] 1) Open terminal and watch journalct -f /usr/bin/gnome-shell 2) Open a window (i.e Files) 3) Close Files in the activities overview 4) gnome-shell spanws errors in the journal. 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) [ Regression potential ] Key focus might not work properly in some shell elements, in particular the focus be owned by multiple actors or by none of them. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1848119/+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
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1848119 Title: gnome-shell infinite error loop when closing app in activities overview Status in gnome-shell package in Ubuntu: Incomplete Bug description: 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 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848119/+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
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1848119 Title: gnome-shell infinite error loop when closing app in activities overview Status in gnome-shell package in Ubuntu: Incomplete Bug description: 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 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848119/+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
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1848119 Title: gnome-shell infinite crash loop when closing app in activities overview Status in gnome-shell package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848119/+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
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1764417 Title: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: I've had this happen a couple of times now since upgrading to 18.04: soon (perhaps within a minute) after logging in, Gnome session ends abruptly and I'm thrown back to the login screen. IIRC, in both instances this occurred on the first login after boot, so it does not reoccur on the subsequent re-login, and not on every login (very rarely in fact), and for now I have no better steps to reproduce this other than "boot, log in". Bug #1663839 (reported against 17.04) seems similar, as does bug #1731428 (reported against 17.10). journalctl output during the issue: Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Apr 16 07:00:30 saegusa gnome-session-binary[4342]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Apr 16 07:00:30 saegusa gnome-session-binary[4342]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 16 07:00:30 saegusa gnome-session-binary[4342]: CRITICAL: We failed, but the fail whale is dead. Sorry ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 16 17:07:14 2018 InstallationDate: Installed on 2016-10-13 (550 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+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
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1734095 Title: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed] Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software and Updates app and attempt to change anything it does not popup the authorization dialog and will not let changes through. In sylog I see Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 3 identities that can be used for authentication. Only considering one. Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of begin_modal failed Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed to show modal dialog. Dismissing authentication request for action-id com.ubuntu.softwareproperties.applychanges cookie 1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740 Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: ERROR:root:Authentication canceled, changes have not been saved Before the upgrade it was ok. Other apps that require authorisation function as expected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Nov 23 10:07:44 2017 DisplayManager: lightdm InstallationDate: Installed on 2014-10-21 (1128 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1734095/+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
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1825623 Title: [AppIndicatorSupport-FATAL] unable to update overlay icon Status in gnome-shell-extension-appindicator package in Ubuntu: Incomplete Bug description: After startup or login, An error occurs that just states cancel or report... but does not open a detail dialog Error messages in the syslog: ... Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem:1.95/org/ayatana/NotificationItem/software_update_available Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable to update overlay icon Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable to update overlay icon ... It seems that the update notifier cannot register its icon in the top bar. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 10:49:27 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-30 (354 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1825623/+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
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in 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) Status in gnome-shell package in Ubuntu: Confirmed Bug description: I'm seeing a several gigs (more than 70GB) a day of the following entries on syslog: May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90), has been already finalized. Impossible to set any property to it. May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) gnome-shell: Installed: 3.28.1-0ubuntu2 Candidate: 3.28.1-0ubuntu2 Version table: *** 3.28.1-0ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic There's similar bug that should be related to this one https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747566 but that fix didn't work
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in 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) Status in gnome-shell package in Ubuntu: Incomplete Bug description: I'm seeing a several gigs (more than 70GB) a day of the following entries on syslog: May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90), has been already finalized. Impossible to set any property to it. May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) gnome-shell: Installed: 3.28.1-0ubuntu2 Candidate: 3.28.1-0ubuntu2 Version table: *** 3.28.1-0ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic There's similar bug that should be related to this one https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747566 but that fix didn't work for me. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 DisplayManager: gdm3 DistroRelease:
Re: [Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in 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) Status in gnome-shell package in Ubuntu: Confirmed Bug description: I'm seeing a several gigs (more than 70GB) a day of the following entries on syslog: May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90), has been already finalized. Impossible to set any property to it. May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) gnome-shell: Installed: 3.28.1-0ubuntu2 Candidate: 3.28.1-0ubuntu2 Version table: ***
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in 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." Status in gnome-shell package in Ubuntu: Incomplete Bug description: My Ubuntu 18.04 installation is killing my disk space. It is filling /var/log/syslog with about 5gb of messages per day. I did a tail on it: PS: already upgraded to the latest packages lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 apt-cache policy gnome-shell gnome-shell: Installed: 3.28.3-0ubuntu0.18.04.2 Candidate: 3.28.3-0ubuntu0.18.04.2 Version table: *** 3.28.3-0ubuntu0.18.04.2 500 500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages tail of /var/log/syslog: Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493ee54c50), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e3717c0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e00d150), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e2f7ef0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493f4a1ac0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e428090), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e466470), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e401fc0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e2086c0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e2a8dc0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493f9d8e00), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e349860), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e1f57f0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e3d5e90), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e417050), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493fa7f490), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493fa81550), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493fbf3370), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493f8f8640), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493ed5fc90), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e264330), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493fcab090), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e2e9830), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493fce7880), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493fcf4190), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493ffa3890), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in 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." Status in gnome-shell package in Ubuntu: Incomplete Bug description: My Ubuntu 18.04 installation is killing my disk space. It is filling /var/log/syslog with about 5gb of messages per day. I did a tail on it: PS: already upgraded to the latest packages lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 apt-cache policy gnome-shell gnome-shell: Installed: 3.28.3-0ubuntu0.18.04.2 Candidate: 3.28.3-0ubuntu0.18.04.2 Version table: *** 3.28.3-0ubuntu0.18.04.2 500 500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages tail of /var/log/syslog: Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493ee54c50), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e3717c0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e00d150), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e2f7ef0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493f4a1ac0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e428090), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e466470), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e401fc0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e2086c0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e2a8dc0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493f9d8e00), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e349860), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e1f57f0), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493e3d5e90), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e417050), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493fa7f490), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493fa81550), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493fbf3370), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493f8f8640), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493ed5fc90), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e264330), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493fcab090), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493e2e9830), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493fce7880), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.BoxLayout (0x56493fcf4190), has been already finalized. Impossible to set any property to it. Sep 15 10:07:52 marte gnome-shell[1104]: Object St.Icon (0x56493ffa3890), has been already finalized. Impossible to set any property to it.
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1739468 Title: Repeated [AppIndicatorSupport-WARN] Item :1.51/org/ayatana/NotificationItem/multiload is already registered Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Status in indicator-multiload package in Ubuntu: Confirmed Bug description: The following message is continuously logged to /var/log/syslog (every few seconds): Dec 20 10:29:26 lxjima gnome-shell[13730]: [AppIndicatorSupport-WARN] Attempting to re-register :1.51/org/ayatana/NotificationItem/multiload; resetting instead Dec 20 10:29:26 lxjima gnome-shell[13730]: [AppIndicatorSupport-WARN] Item :1.51/org/ayatana/NotificationItem/multiload is already registered It's hard to find anything in syslog because thousands of these messages intermingle with everything else ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 20 10:28:49 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-12-13 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1739468/+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
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/987220 Title: System does not power off reliably when Shut Down chosen from GUI Status in The Session Menu: Incomplete Status in “gnome-session” package in Ubuntu: Invalid Status in “indicator-session” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: Invalid Status in “gnome-session” source package in Precise: Invalid Status in “indicator-session” source package in Precise: Invalid Status in “linux” source package in Precise: Confirmed Status in “upstart” source package in Precise: Invalid Bug description: Shutting down the computer using the menue does not work always correct. It often does not complete turn off the computer. The power LED and the LED of the bluetooth unit remain on. Also the fan is still running and won't stop. Shutting down the computer with sudo shutdown -h now using the terminal works fine. I am using a Dell Inspiron 1720. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: indicator-session 0.3.96-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu5 Architecture: i386 Date: Mon Apr 23 12:26:10 2012 ExecutablePath: /usr/lib/indicator-session/gtk-logout-helper InstallationMedia: Kubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=de_DE.UTF-8 SourcePackage: indicator-session UpgradeStatus: Upgraded to precise on 2012-04-21 (1 days ago) --- ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) NonfreeKernelModules: nvidia Package: upstart PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 Tags: precise Uname: Linux 3.2.0-24-generic-pae i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/987220/+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