[Bug 1745666] Re: gsd-housekeeping leaks file descriptors
@snabb (Janne) #7 or @ljh48332 (Luke) just detected this again in latest release and will present a workaround that solves it even with continuous Ubuntu/Debian/Gnome updates. Could you give some insight into why this service is kept and not removed completely? Even the Gnome threads state it should be removed. Most people probably are not aware of the problem but it is a severe bug from a performance, data integrity and hardware perspective. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1745666 Title: gsd-housekeeping leaks file descriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1745666] Re: gsd-housekeeping leaks file descriptors
This bug came back again in latest ubuntu, this time a new symptom occurred. Gnome extensions are also regularly disabled for some reason. Removing gsd-housekeepin still works. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1745666 Title: gsd-housekeeping leaks file descriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1745666] Re: gsd-housekeeping leaks file descriptors
This bug came back in recent updated after using workaround #5 by Janne. Didn't notice at first, then severe system slowdowns and odd power behaviour started to occur. 100% Fan on etc. Killing my disk long term as well. I detected it when the gsd-housekeepin service crashed and Ubuntu notified this. Why is no one fixing this? Just remove the whole service permanently, it has no real value as stated upstream. Linux computer 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:04:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1745666 Title: gsd-housekeeping leaks file descriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799430] Re: Icon dock visible on lock screen
@Plurto your workaround was successful for my case as well. Thanks. Weird bug, transparency affecting clicks and interaction through a lock screen. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1799430 Title: Icon dock visible on lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1799430/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799430] Re: Icon dock visible on lock screen
Hi @Plurto. Where is this setting and is it a default ubuntu setting? Thanks. Note: Just using the default installation (had no active extensions before upgrade besides Ubuntu system defaults). I.e., have not installed dash to dock. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1799430 Title: Icon dock visible on lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1799430/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799430] Re: Icon dock visible on lock screen
Same problem after upgrade from 18.04 to 18.10. However, the whole screen is visible when manually locking the screen (ctrl + alt + L in my case). All programs are minimized when locking manually/or resuming from suspend and the screen goes slightly blurry, but not enough to distort text for instance. I.e., i can see everything. The exact same thing happens after suspend (lid closing/opening). Also I can actually close programs by right clicking icons and access the dock menu as well as the top bar menu (e.g., se wifi info, click on settings panel etc). Noticed that if i do ctrl + alt + L followed by a second ctrl + alt + L after a short wait period - then the correct lock screen appears. I have lock enabled after 5 minutes and suspend. No auto login and no extensions at all enabled. gnome-shell --version GNOME Shell 3.30.1 uname -a Linux computer 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux (same problem as this guy is having: https://askubuntu.com/questions/1085426/desktop-is-visible-after- suspend). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1799430 Title: Icon dock visible on lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1799430/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799430] Re: Icon dock visible on lock screen
Btw, for me this happens 100% of all suspend/manual lock cases. Gnome has crashed once completely as well since upgrade due to this issue. In 18.04 the whole screen was visible sometimes for a very short period of time after lock, this is worse. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1799430 Title: Icon dock visible on lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1799430/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1745666] Re: gsd-housekeeping leaks file descriptors
Problem exist in 18.10 as well after upgrade. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1745666 Title: gsd-housekeeping leaks file descriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)
Same issue, not as severe regarding disk space. No extensions active. # NOTE: will only grep first line of stacktracce journalctl -m | grep osdWindow.js | wc -l 3597 gnome-shell --version GNOME Shell 3.28.3 Oct 8 11:15:02 computer gnome-shell[2515]: Object St.Icon (0x55a64961dc90), has been already finalized. Impossible to set any property to it. Oct 8 11:15:02 computer gnome-shell[2515]: Object St.BoxLayout (0x55a647bf04e0), has been already finalized. Impossible to set any property to it. Oct 8 11:15:02 computer gnome-shell[2515]: Object St.Icon (0x55a645fdf090), has been already finalized. Impossible to set any property to it. Oct 8 11:15:02 computer gnome-shell[2515]: Object St.BoxLayout (0x55a649204c40), has been already finalized. Impossible to set any property to it. Oct 8 11:15:02 computer gnome-shell[2515]: Object St.Icon (0x55a644e107e0), has been already finalized. Impossible to set any property to it. Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: == Stack trace for context 0x55a6441b7330 == Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #0 0x7ffd21e60e00 b resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f8f286c7780 @ 231) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #1 0x7ffd21e60e60 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f8f3c2b5de0 @ 71) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #2 0x7ffd21e60f20 b self-hosted:916 (0x7f8f3c2f12b8 @ 367) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #3 0x7ffd21e61010 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f8f3c2d2230 @ 386) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #4 0x55a644565880 i resource:///org/gnome/shell/ui/layout.js:531 (0x7f8f286042b8 @ 127) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #5 0x7ffd21e61c60 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f8f3c2b5de0 @ 71) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #6 0x7ffd21e61d20 b self-hosted:916 (0x7f8f3c2f12b8 @ 367) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: == Stack trace for context 0x55a6441b7330 == Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #0 0x7ffd21e60e00 b resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f8f286c7780 @ 273) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #1 0x7ffd21e60e60 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f8f3c2b5de0 @ 71) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #2 0x7ffd21e60f20 b self-hosted:916 (0x7f8f3c2f12b8 @ 367) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #3 0x7ffd21e61010 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f8f3c2d2230 @ 386) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #4 0x55a644565880 i resource:///org/gnome/shell/ui/layout.js:531 (0x7f8f286042b8 @ 127) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #5 0x7ffd21e61c60 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f8f3c2b5de0 @ 71) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #6 0x7ffd21e61d20 b self-hosted:916 (0x7f8f3c2f12b8 @ 367) Oct 8 11:15:02 computer gnome-shell[2515]: Object St.BoxLayout (0x55a644e10d80), has been already finalized. Impossible to set any property to it. Oct 8 11:15:02 computer gnome-shell[2515]: Object St.Icon (0x55a646d64620), has been already finalized. Impossible to set any property to it. Oct 8 11:15:02 computer gnome-shell[2515]: Object St.BoxLayout (0x55a645ed92d0), has been already finalized. Impossible to set any property to it. Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: == Stack trace for context 0x55a6441b7330 == Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #0 0x7ffd21e60e00 b resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f8f286c7780 @ 231) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #1 0x7ffd21e60e60 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f8f3c2b5de0 @ 71) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #2 0x7ffd21e60f20 b self-hosted:916 (0x7f8f3c2f12b8 @ 367) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #3 0x7ffd21e61010 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f8f3c2d2230 @ 386) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #4 0x55a644565880 i resource:///org/gnome/shell/ui/layout.js:531 (0x7f8f286042b8 @ 127) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #5 0x7ffd21e61c60 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f8f3c2b5de0 @ 71) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #6 0x7ffd21e61d20 b self-hosted:916 (0x7f8f3c2f12b8 @ 367) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: == Stack trace for context 0x55a6441b7330 == Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #0 0x7ffd21e60e00 b resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f8f286c7780 @ 273) Oct 8 11:15:02 computer org.gnome.Shell.desktop[2515]: #1 0x7ffd21e60e60
[Bug 1745666] Re: gsd-housekeeping leaks file descriptors
#journalctl -b | grep gsd-housekeepin | wc -l 100067 Going for #5 by Janne since nothing else works (annoying task to keep performing). It is also the suggestion by Fedora maintainers as systemd does the same task of cleaning tmp (https://bugzilla.redhat.com/show_bug.cgi?id=1563445) Upstream reports: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/26 ** Bug watch added: Red Hat Bugzilla #1563445 https://bugzilla.redhat.com/show_bug.cgi?id=1563445 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1745666 Title: gsd-housekeeping leaks file descriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1745666] Re: gsd-housekeeping leaks file descriptors
In 15 hours 6000 new messages occur. #journalctl -b | grep gsd-housekeepin | wc -l 12000 The permission on /var/tmp drwxrwxrwt 45 root root 56K okt 1 14:53 tmp/ The permissions on mkinitramfs stuff in /var/tmp drwxr-xr-x 12 root root 4,0K jan 21 2017 mkinitramfs_NNARsN/ -rw--- 1 root root0 jan 12 2017 mkinitramfs-OL_3YeMt7 The permissions on systemd stuff in /var/tmp ll /var/tmp/systemd-private-b45aa528188d4cb180453f35adbfd14c-systemd-resolved.service-ceueNy/ total 68K drwx-- 3 root root 4,0K okt 1 14:52 ./ drwxrwxrwt 45 root root 56K okt 1 14:53 ../ drwxrwxrwt 2 root root 4,0K okt 1 14:52 tmp/ Will try changing permissions next. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1745666 Title: gsd-housekeeping leaks file descriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1745666] Re: gsd-housekeeping leaks file descriptors
Nope, the message persists even with fs.inotify.max_user_watches=524288 Total nr messages: # journalctl -m | grep gsd-housekeepin | wc -l 1947297 Previous nr boot messages (no reboot after workaround was applied, could be weeks): #journalctl -b | grep gsd-housekeepin | wc -l 51500 Current nr boot messages (about 1 day after the workaround was applied and a reboot was performed): #journalctl -b | grep gsd-housekeepin | wc -l 6000 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1745666 Title: gsd-housekeeping leaks file descriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1745666] Re: gsd-housekeeping leaks file descriptors
I'm fairly sure this is related to changes in fs.inotify.max_user_watches ("Too
many open files"). I recently got a bunch of warnings in misc code editors
about low values. Took me a while to understand the max_user_watches had
reverted back to the default value of about 8000. I.e., some update probably
changed my setting, which was much higher before, without permission. I haven't
touched that setting for years.
This could perhaps also affect large dropbox folders.
Pro/Cons of a higher value:
https://unix.stackexchange.com/questions/13751/kernel-inotify-watch-limit-reached
Currently testing this workaround:
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo
sysctl -p
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1745666
Title:
gsd-housekeeping leaks file descriptors
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795109] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1795109/+attachment/5194411/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1795109 Title: gnome-software spams syslog with assertion errors for != NULL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1795109/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795109] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1795109/+attachment/5194409/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1795109 Title: gnome-software spams syslog with assertion errors for != NULL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1795109/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795109] Re: gnome-software spams syslog with assertion errors for != NULL
apport information ** Tags added: apport-collected bionic third-party-packages ** Description changed: The fan and cpu is very active during this event, thousands of assertions reported. Syslog case attached. lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 apt-cache policy gnome-software gnome-software: Installed: 3.28.1-0ubuntu4.18.04.3 Candidate: 3.28.1-0ubuntu4.18.04.3 Version table: *** 3.28.1-0ubuntu4.18.04.3 500 500 http://ftp.acc.umu.se/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu4 500 500 http://ftp.acc.umu.se/ubuntu bionic/main amd64 Package 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://ftp.acc.umu.se/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu2 500 500 http://ftp.acc.umu.se/ubuntu bionic/main amd64 Packages uname -a Linux computer 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux gnome-shell --version GNOME Shell 3.28.3 Sep 29 06:58:01 computer gnome-software[2694]: json_object_has_member: assertion 'member_name != NULL' failed Sep 29 06:58:01 computer gnome-software[2694]: g_strsplit: assertion 'string != NULL' failed Sep 29 06:58:01 computer gnome-software[2694]: g_strv_length: assertion 'str_array != NULL' failed Sep 29 06:58:01 computer gnome-software[2694]: json_object_has_member: assertion 'member_name != NULL' failed Sep 29 06:58:01 computer gnome-software[2694]: g_strsplit: assertion 'string != NULL' failed Sep 29 06:58:01 computer gnome-software[2694]: g_strv_length: assertion 'str_array != NULL' failed Sep 29 06:58:01 computer gnome-software[2694]: json_object_has_member: assertion 'member_name != NULL' failed Sep 29 06:58:01 computer gnome-software[2694]: g_strsplit: assertion 'string != NULL' failed + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.4 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2015-07-18 (1168 days ago) + InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) + Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 + Tags: bionic third-party-packages + Uname: Linux 4.15.0-34-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1795109/+attachment/5194408/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1795109 Title: gnome-software spams syslog with assertion errors for != NULL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1795109/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795109] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1795109/+attachment/5194410/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1795109 Title: gnome-software spams syslog with assertion errors for != NULL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1795109/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795108] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1795108/+attachment/5194406/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1795108 Title: Using the super key spams the syslog with St.Bin has been already deallocated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1795108/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795108] Re: Using the super key spams the syslog with St.Bin has been already deallocated
apport information ** Tags added: apport-collected bionic third-party-packages ** Description changed: All extensions are disabled. All gnome-shell extensions, if enabled, do severe spamming of the syslog. Most errors are related to "st.bin" and/or "st.whatever" has been already deallocated. I.e., at least six popular extensions experience similar crashes after software updates in gnome. 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://ftp.acc.umu.se/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu2 500 500 http://ftp.acc.umu.se/ubuntu bionic/main amd64 Packages uname -a Linux computer 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux gnome-shell --version GNOME Shell 3.28.3 Sep 29 06:32:20 computer gnome-shell[2491]: Object St.Bin (0x563811418000), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: == Stack trace for context 0x56380fde1330 == Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #0 0x7ffc8c0b3dd0 b resource:///org/gnome/shell/ui/workspaceThumbnail.js:974 (0x7f8003cf6560 @ 439) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #1 0x7ffc8c0b4ad0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #2 0x56381018ec28 i resource:///org/gnome/shell/ui/workspaceThumbnail.js:884 (0x7f8003cf62b8 @ 390) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #3 0x7ffc8c0b56c0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #4 0x7ffc8c0b5780 b self-hosted:916 (0x7f80200f12b8 @ 367) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #5 0x7ffc8c0b5870 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f80200d2230 @ 386) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #6 0x56381018eb90 i resource:///org/gnome/shell/ui/overview.js:568 (0x7f8003ecf890 @ 324) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #7 0x7ffc8c0b64c0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #8 0x56381018eb10 i resource:///org/gnome/shell/ui/overview.js:540 (0x7f8003ecf808 @ 109) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #9 0x7ffc8c0b70a0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #10 0x56381018ea90 i resource:///org/gnome/shell/ui/overview.js:670 (0x7f8003ecfb38 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #11 0x7ffc8c0b7c80 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #12 0x56381018ea10 i resource:///org/gnome/shell/ui/main.js:197 (0x7f80200da3c8 @ 39) Sep 29 06:32:20 computer gnome-shell[2491]: Object St.Bin (0x563811418000), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: == Stack trace for context 0x56380fde1330 == Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #0 0x56381018eb70 i resource:///org/gnome/shell/ui/workspaceThumbnail.js:1231 (0x7f8003cf8120 @ 739) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #1 0x7ffc8c0b11a0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #2 0x7ffc8c0b1280 b self-hosted:920 (0x7f80200f12b8 @ 428) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #3 0x56381018eaa8 i resource:///org/gnome/shell/ui/overviewControls.js:76 (0x7f8003ecfe68 @ 521) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #4 0x7ffc8c0b3430 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #5 0x7ffc8c0b57a0 b resource:///org/gnome/gjs/modules/_legacy.js:39 (0x7f80200b5b38 @ 215) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #6 0x56381018ea10 i resource:///org/gnome/shell/ui/overviewControls.js:394 (0x7f8003ed52b8 @ 26) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #7 0x7ffc8c0b6410 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20
[Bug 1795108] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1795108/+attachment/5194407/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1795108 Title: Using the super key spams the syslog with St.Bin has been already deallocated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1795108/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795108] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1795108/+attachment/5194405/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1795108 Title: Using the super key spams the syslog with St.Bin has been already deallocated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1795108/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795111] Re: gsd-housekeepin spams syslog with Failed to enumerate children of /tmp/systemd-private.. Error opening directory '/tmp/systemd-private..
*** This bug is a duplicate of bug 1745666 *** https://bugs.launchpad.net/bugs/1745666 ** This bug has been marked a duplicate of bug 1745666 gsd-housekeeping leaks file descriptors -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1795111 Title: gsd-housekeepin spams syslog with Failed to enumerate children of /tmp /systemd-private.. Error opening directory '/tmp/systemd-private.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1795111/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795111] [NEW] gsd-housekeepin spams syslog with Failed to enumerate children of /tmp/systemd-private.. Error opening directory '/tmp/systemd-private..
Public bug reported: The fan and cpu is very active during this event, thousands of errors reported. Syslog case attached. The desktop becomes unresponsive during this event (for instance cant close windows). 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://ftp.acc.umu.se/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu2 500 500 http://ftp.acc.umu.se/ubuntu bionic/main amd64 Packages uname -a Linux computer 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux gnome-shell --version GNOME Shell 3.28.3 NOTE: syslog package name is incorrect it seems apt-cache policy gsd-housekeepin N: Unable to locate package gsd-housekeepin apt-cache policy gsd-housekeeping N: Unable to locate package gsd-housekeeping Sample: Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children of /tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-rtkit-daemon.service-HcUyZY: Error opening directory '/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-rtkit-daemon.service-HcUyZY': Permission denied Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children of /tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-fwupd.service-iinX30: Error opening directory '/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-fwupd.service-iinX30': Permission denied Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children of /tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-systemd-resolved.service-wgHcsA: Error opening directory '/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-systemd-resolved.service-wgHcsA': Permission denied Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children of /tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-systemd-timesyncd.service-1vLCpk: Error opening directory '/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-systemd-timesyncd.service-1vLCpk': Permission denied Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children of /tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-colord.service-M2su41: Error opening directory '/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-colord.service-M2su41': Permission denied Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children of /var/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-colord.service-zPlm2z: Error opening directory '/var/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-colord.service-zPlm2z': Permission denied Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children of /var/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-rtkit-daemon.service-nn8vHs: Error opening directory '/var/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-rtkit-daemon.service-nn8vHs': Permission denied Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children of /var/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-fwupd.service-4y9y5r: Error opening directory '/var/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-fwupd.service-4y9y5r': Permission denied Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children of /var/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-systemd-timesyncd.service-gW3soH: Error opening directory '/var/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-systemd-timesyncd.service-gW3soH': Permission denied Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children of /var/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-systemd-resolved.service-ZGaNqX: Error opening directory '/var/tmp/systemd-private-bdf344a9b3b14e43a062622847c9d2ee-systemd-resolved.service-ZGaNqX': Permission denied Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children of /var/tmp/mkinitramfs_FJNyyu/var/cache/ldconfig: Error opening directory '/var/tmp/mkinitramfs_FJNyyu/var/cache/ldconfig': Permission denied Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children of /var/tmp/mkinitramfs_6DHTrf/var/cache/ldconfig: Error opening directory '/var/tmp/mkinitramfs_6DHTrf/var/cache/ldconfig': Permission denied Sep 29 06:56:57 computer gsd-housekeepin[2637]: Failed to enumerate children of /var/tmp/mkinitramfs_WgThBv/var/cache/ldconfig: Error opening directory '/var/tmp/mkinitramfs_WgThBv/var/cache/ldconfig': Permission denie ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Package changed: gnome-shell (Ubuntu) => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
[Bug 1745666] Re: gsd-housekeeping leaks file descriptors
I think this bug i filed might be a duplicate of this: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/1795111 In my case i could detect that the desktop became unresponsive as well. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1745666 Title: gsd-housekeeping leaks file descriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795108] Re: Using the super key spams the syslog with St.Bin has been already deallocated
** Description changed: All extensions are disabled. All gnome-shell extensions, if enabled, do severe spamming of the syslog. Most errors are related to "st.bin" and/or "st.whatever" has been already deallocated. I.e., at least six popular extensions experience similar crashes after software updates in gnome. + + 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://ftp.acc.umu.se/ubuntu bionic-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 3.28.1-0ubuntu2 500 + 500 http://ftp.acc.umu.se/ubuntu bionic/main amd64 Packages uname -a Linux computer 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux gnome-shell --version GNOME Shell 3.28.3 - Sep 29 06:32:20 computer gnome-shell[2491]: Object St.Bin (0x563811418000), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: == Stack trace for context 0x56380fde1330 == - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #0 0x7ffc8c0b3dd0 b resource:///org/gnome/shell/ui/workspaceThumbnail.js:974 (0x7f8003cf6560 @ 439) - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #1 0x7ffc8c0b4ad0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #2 0x56381018ec28 i resource:///org/gnome/shell/ui/workspaceThumbnail.js:884 (0x7f8003cf62b8 @ 390) - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #3 0x7ffc8c0b56c0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #4 0x7ffc8c0b5780 b self-hosted:916 (0x7f80200f12b8 @ 367) - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #5 0x7ffc8c0b5870 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f80200d2230 @ 386) - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #6 0x56381018eb90 i resource:///org/gnome/shell/ui/overview.js:568 (0x7f8003ecf890 @ 324) - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #7 0x7ffc8c0b64c0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #8 0x56381018eb10 i resource:///org/gnome/shell/ui/overview.js:540 (0x7f8003ecf808 @ 109) - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #9 0x7ffc8c0b70a0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #10 0x56381018ea90 i resource:///org/gnome/shell/ui/overview.js:670 (0x7f8003ecfb38 @ 71) - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #11 0x7ffc8c0b7c80 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #12 0x56381018ea10 i resource:///org/gnome/shell/ui/main.js:197 (0x7f80200da3c8 @ 39) - Sep 29 06:32:20 computer gnome-shell[2491]: Object St.Bin (0x563811418000), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: == Stack trace for context 0x56380fde1330 == - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #0 0x56381018eb70 i resource:///org/gnome/shell/ui/workspaceThumbnail.js:1231 (0x7f8003cf8120 @ 739) - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #1 0x7ffc8c0b11a0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #2 0x7ffc8c0b1280 b self-hosted:920 (0x7f80200f12b8 @ 428) - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #3 0x56381018eaa8 i resource:///org/gnome/shell/ui/overviewControls.js:76 (0x7f8003ecfe68 @ 521) - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #4 0x7ffc8c0b3430 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #5 0x7ffc8c0b57a0 b resource:///org/gnome/gjs/modules/_legacy.js:39 (0x7f80200b5b38 @ 215) - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #6 0x56381018ea10 i resource:///org/gnome/shell/ui/overviewControls.js:394 (0x7f8003ed52b8 @ 26) - Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #7 0x7ffc8c0b6410 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) + Sep 29 06:32:20 computer gnome-shell[2491]: Object St.Bin
[Bug 1795109] [NEW] gnome-software spams syslog with assertion errors for != NULL
Public bug reported: The fan and cpu is very active during this event, thousands of assertions reported. Syslog case attached. lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 apt-cache policy gnome-software gnome-software: Installed: 3.28.1-0ubuntu4.18.04.3 Candidate: 3.28.1-0ubuntu4.18.04.3 Version table: *** 3.28.1-0ubuntu4.18.04.3 500 500 http://ftp.acc.umu.se/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu4 500 500 http://ftp.acc.umu.se/ubuntu bionic/main amd64 Package 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://ftp.acc.umu.se/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu2 500 500 http://ftp.acc.umu.se/ubuntu bionic/main amd64 Packages uname -a Linux computer 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux gnome-shell --version GNOME Shell 3.28.3 Sep 29 06:58:01 computer gnome-software[2694]: json_object_has_member: assertion 'member_name != NULL' failed Sep 29 06:58:01 computer gnome-software[2694]: g_strsplit: assertion 'string != NULL' failed Sep 29 06:58:01 computer gnome-software[2694]: g_strv_length: assertion 'str_array != NULL' failed Sep 29 06:58:01 computer gnome-software[2694]: json_object_has_member: assertion 'member_name != NULL' failed Sep 29 06:58:01 computer gnome-software[2694]: g_strsplit: assertion 'string != NULL' failed Sep 29 06:58:01 computer gnome-software[2694]: g_strv_length: assertion 'str_array != NULL' failed Sep 29 06:58:01 computer gnome-software[2694]: json_object_has_member: assertion 'member_name != NULL' failed Sep 29 06:58:01 computer gnome-software[2694]: g_strsplit: assertion 'string != NULL' failed ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "syslog-gnome-software-error" https://bugs.launchpad.net/bugs/1795109/+attachment/5194329/+files/syslog-gnome-software.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1795109 Title: gnome-software spams syslog with assertion errors for != NULL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1795109/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795108] [NEW] Using the super key spams the syslog with St.Bin has been already deallocated
Public bug reported: All extensions are disabled. All gnome-shell extensions, if enabled, do severe spamming of the syslog. Most errors are related to "st.bin" and/or "st.whatever" has been already deallocated. I.e., at least six popular extensions experience similar crashes after software updates in gnome. uname -a Linux computer 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux gnome-shell --version GNOME Shell 3.28.3 Sep 29 06:32:20 computer gnome-shell[2491]: Object St.Bin (0x563811418000), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: == Stack trace for context 0x56380fde1330 == Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #0 0x7ffc8c0b3dd0 b resource:///org/gnome/shell/ui/workspaceThumbnail.js:974 (0x7f8003cf6560 @ 439) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #1 0x7ffc8c0b4ad0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #2 0x56381018ec28 i resource:///org/gnome/shell/ui/workspaceThumbnail.js:884 (0x7f8003cf62b8 @ 390) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #3 0x7ffc8c0b56c0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #4 0x7ffc8c0b5780 b self-hosted:916 (0x7f80200f12b8 @ 367) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #5 0x7ffc8c0b5870 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f80200d2230 @ 386) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #6 0x56381018eb90 i resource:///org/gnome/shell/ui/overview.js:568 (0x7f8003ecf890 @ 324) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #7 0x7ffc8c0b64c0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #8 0x56381018eb10 i resource:///org/gnome/shell/ui/overview.js:540 (0x7f8003ecf808 @ 109) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #9 0x7ffc8c0b70a0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #10 0x56381018ea90 i resource:///org/gnome/shell/ui/overview.js:670 (0x7f8003ecfb38 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #11 0x7ffc8c0b7c80 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #12 0x56381018ea10 i resource:///org/gnome/shell/ui/main.js:197 (0x7f80200da3c8 @ 39) Sep 29 06:32:20 computer gnome-shell[2491]: Object St.Bin (0x563811418000), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: == Stack trace for context 0x56380fde1330 == Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #0 0x56381018eb70 i resource:///org/gnome/shell/ui/workspaceThumbnail.js:1231 (0x7f8003cf8120 @ 739) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #1 0x7ffc8c0b11a0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #2 0x7ffc8c0b1280 b self-hosted:920 (0x7f80200f12b8 @ 428) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #3 0x56381018eaa8 i resource:///org/gnome/shell/ui/overviewControls.js:76 (0x7f8003ecfe68 @ 521) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #4 0x7ffc8c0b3430 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #5 0x7ffc8c0b57a0 b resource:///org/gnome/gjs/modules/_legacy.js:39 (0x7f80200b5b38 @ 215) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #6 0x56381018ea10 i resource:///org/gnome/shell/ui/overviewControls.js:394 (0x7f8003ed52b8 @ 26) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #7 0x7ffc8c0b6410 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f80200b5de0 @ 71) Sep 29 06:32:20 computer org.gnome.Shell.desktop[2491]: #8 0x7ffc8c0b7e40 b resource:///org/gnome/shell/ui/layout.js:209 (0x7f8003e01780 @ 62) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "syslog-st.bin-error" https://bugs.launchpad.net/bugs/1795108/+attachment/5194327/+files/syslog.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1795108 Title: Using the super key spams the syslog with St.Bin has been already deallocated
[Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
Confirm (Super - L) not working on Ubuntu 18.04, switching keyboard language does not work either most of the time (Super + Space). Those I use the most. Extremely annoying after some time, especially when using dual screens (since the Gnome top bar is only on one monitor which is even more annoying: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1682542). Worked fine in Ubuntu 17.10 with Gnome and previous versions with Unity. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
Sorry, small adjustment. I use wayland as default since 17.10 with gdm (works well in general for me): loginctl show-session c1 -p Type Type=wayland -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1437502] Re: nautilus lacking 'new document' in context menu on GNOME
For anyone ending up here, i lost this feature in 17.04 and need it: quick fix found at https://askubuntu.com/questions/11/create-new- document-right-click-option-missing-in-ubuntu-gnome/791946 " 1. See if you have ~/Templates folder. Create one if it is missing using command: mkdir ~/Templates 2. Now create an empty file from command prompt: touch ~/Templates/Text\ File.txt1 "Create Document" option is back again and you can create a new text file or a new document. 1the backslash is used to tell the shell that the space following it is part of the filename. Since the shell recognizes spaces are delimiters between commands/options/arguments, unless you "quote it" 'quote it' or quote\ it, the shell will treat whatever comes after the space as a separate argument. " -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1437502 Title: nautilus lacking 'new document' in context menu on GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1437502/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1576685] Re: Disable touchpad while typing is not active nor can it be enabled
FYI: got a better experience in gnome when opening a terminal and running syndaemon -d in gnome. However, that seem to freeze the mouse slightly too long after I have stopped typing. The unity version works better (not sure what differs yet). https://askubuntu.com/questions/505007/ubuntu-gnome-14-04-disable- touchpad-while-typing-not-working -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1576685 Title: Disable touchpad while typing is not active nor can it be enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1576685/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1576685] Re: Disable touchpad while typing is not active nor can it be enabled
Related and probably duplicate of: https://bugs.launchpad.net/ubuntu/+source/unity-settings- daemon/+bug/1351772 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1576685 Title: Disable touchpad while typing is not active nor can it be enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1576685/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1576685] Re: Disable touchpad while typing is not active nor can it be enabled
Hi, the synaptics (libinput also installed) package work well for me in 16.04 (and previous version to 12.04 at least) up to 17.04 on thinkpads (x2XX to carbon X1). Currently using carbon x1 5th gen. There is however some form of instability with settings that affects many users including me. Sometimes the disable while typing feature stops working and reinstall of libinput and synaptics drivers help. I.e, reinstall xserver-xorg- input-synaptics and -libinput as well as running: gconftool-2 --set --type boolean /desktop/gnome/peripherals/touchpad/touchpad_enabled true https://help.ubuntu.com/community/SynapticsTouchpad#Touchpad_not_working_after_login However, what perplexes me is that the gnome desktop (gnome default) does not work with synaptics disable while typing when it clearly works in unity at the same time. I'm testing gnome before 18.04 and login in/out between both desktops, with the exact same settings (gconf, drivers etc). Currently I'm writing this in gnome and the cursor skips with random artefacts that make the keyboard defunct. In unity it works perfectly (two finger scroll, trackpoint etc works). Related: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1687191 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1576685 Title: Disable touchpad while typing is not active nor can it be enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1576685/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Comment 19 worked for me after reboot on 14.04. The error happened in relation to manual a password reset I did (replaced shadow and passwd with a backup). https://bugs.launchpad.net/ubuntu/+source/policykit-desktop- privileges/+bug/1240336/comments/19 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: Not authorized to perform operation / Unable to determine the session we are in: No session for pid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1240336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
My key-combo (left ctrl + caps-lock) can know be training/activating it in settings. However, the key-combo doesn't work all the time and seems to get confused when switching between terminal, gnome screen saver and regular desktop activity. So 1) after upgrade to 13.10 my key-combo stopped working completely. 2) then after some update my old key-combo started to work in gnome screen saver, terminal and all programs. Yet the indicator never changed state/appearance. 3) then tested using system settings and after that it works partially. ... why bugs like this slip through is beyond me. Canonical has a work force from many countries. Let half of the work-force upgrade continuously over several releases and half install fresh builds. Also add more testing. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1218322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
This bug has been partially fixed for me. I used left shift + caps lock to change language in 13.04 and it know works in 13.10. I haven’t used the control panel application to set those keys, they are kept from the upgrade to 13.10. However, the indicator (US, SV etc) never changes between languages unless I mouse click, even when the keyboard layout changes. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1218322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
This new great languge indicator looks almost exactly as the old one. However, Super + space (default) does not work for me OR changing the key combination. Super + space opens the left menu. Wiz posted workaround it is then. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-keyboard/+bug/1218322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 882893] Re: gnome-screensaver 3.2.0-0ubuntu1 failed to exit
Another workaround for this issue is to be very patient and hit enter a few times while the screen is frozen. After a while (minutes) the password screen appears. I've seen this happen to another guy in the office and he makes a hard reboot every time (figures it is a complete freeze) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/882893 Title: gnome-screensaver 3.2.0-0ubuntu1 failed to exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/882893/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 882893] Re: gnome-screensaver 3.2.0-0ubuntu1 failed to exit
Can confirm this exact behavior on lenovo x201 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/882893 Title: gnome-screensaver 3.2.0-0ubuntu1 failed to exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/882893/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 290476] [NEW] Nautilus failed to suppress new empty disk message when burning image with right click action
Public bug reported: On Intrepid RC1: Nautilus failed to suppress new empty disk message when burning image with right click action. 1. Download the Ubuntu image to your desktop. 2. Right click on that image and choose to burn it. 3. Insert empty disk before you write the image. If I have chosen the burn alternative then nautilus should not pop-up a question asking what to do with my empty disk - i.e., on top of my burn settings dialogue. ** Affects: nautilus-cd-burner (Ubuntu) Importance: Undecided Status: New -- Nautilus failed to suppress new empty disk message when burning image with right click action https://bugs.launchpad.net/bugs/290476 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus-cd-burner in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
