[Bug 2042993] [NEW] overview sometimes stuck after pressing super
Public bug reported: I press super a lot to see progress of other applications or the system time from activities overview when in a fullscreen application, such as a steam game. Occasionally the activities overview will not show any applications nor the desktop, but only the gray background and the search bar (although applications on the dock will still be visible and selectable, just not interactable other than audio). The clock and quick settings are the only things that work normally in this state as not even the activities search bar is responsive. The only way I've been able to exit is by restarting the computer. I'm going to try using Xorg to restart gnome next time but I've not tested that yet. This issue hasn't seemed to occur in any situations other than running full screen applications. Although, given that I don't often use activities overview outside of fullscreen apps, that may not be required for the bug to occur. This bug started after upgrading to Ubuntu 23.10. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 23:01:44 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-03 (553 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-17 (22 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic ** Attachment added: "Screenshot from 2023-10-25 21-06-03.png" https://bugs.launchpad.net/bugs/2042993/+attachment/5717103/+files/Screenshot%20from%202023-10-25%2021-06-03.png -- 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/2042993 Title: overview sometimes stuck after pressing super To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1893693] Re: Unable to scroll gnome app list
-- 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/1893693 Title: Unable to scroll gnome app list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1893693] [NEW] Unable to scroll gnome app list
Public bug reported: I'm unable to scroll from page 1 to 2 in all apps under the gnome app list. Changing the dock from left side to bottom or right side solves the issue. Ubuntu 20.04 fresh install. See here for same issue: https://askubuntu.com/questions/1241165/should-i-report-show- applications-not-scrolling-as-a-bug ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 31 22:37:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-22 (39 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1893693 Title: Unable to scroll gnome app list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866974] [NEW] The Diffie-Hellman prime sent by the server is not acceptable
Public bug reported: I can no longer connect to my ISP mail server. Works in previous version 19.10 "The reported error was “Failed to get capabilities: Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough).”." I've tried finding a workaround but so far no luck. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evolution 3.35.92-1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 11:07:01 2020 InstallationDate: Installed on 2020-03-03 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1866974 Title: The Diffie-Hellman prime sent by the server is not acceptable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866416] Re: Ubuntu 18.04 system freezes when attempting to switch user
I've come to a pseudo-resolution by disabling Wayland usage in gdm3. - Edit /etc/gdm3/custom.conf and simply uncomment: #WaylandEnable=false - restart everything and Switch Users works fine. I included this comment as "NOTE 3" in the bug report. ** Description changed: Ubuntu 18.04 freezes and must be manually powered down and rebooted when attempting to "Switch User". Prerequisites: - Use Ubuntu 18.04 - You need at least 2 users (e.g. user1 and user2) Expected behavior: - While logged in as any user, choose "Switch User" from top power drop down. - Click "Log in as another user" - - Enter another user's credentials and login + - Enter another user's credentials and login Bug behavior and steps to reproduce: - Start your computer - At the graphical login prompt, log in with user1: user1 is able to log in, its desktop is shown - While logged into the desktop of user1, choose "Switch user" - Returns to login screen, with prompt to enter user1 password - Click "Log in as another user" - RESULT: the screen freezes with no ability to type or move the mouse. It is never possible to login in as either user1 or user2 and the system must be manually powered down and restarted. NOTE 1: the same happens when user2 was the first to log in after a reboot of the system. "Switch User" ends up with the same freeze issue. NOTE 2: I've been getting crash reports at login that say "System program problem detected / Do you want to report the problem now?". I am unsure whether or not this is related, but the cat _usr_lib_gnome- session_gnome-session-check-accelerated.121.crash file in /var/crash provides the following information at the top of the report: ProblemType: Crash Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Mar 6 11:28:30 2020 DistroRelease: Ubuntu 18.04 ExecutablePath: /usr/lib/gnome-session/gnome-session-check-accelerated ExecutableTimestamp: 1525246842 ProcCmdline: /usr/lib/gnome-session/gnome-session-check-accelerated ProcCwd: /var/lib/gdm3 ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/false + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/false ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 11:49:25 2020 InstallationDate: Installed on 2020-03-03 (2 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) + + NOTE 3: I've come to a pseudo-resolution by disabling Wayland usage in + gdm3. + + - Edit /etc/gdm3/custom.conf and simply uncomment: + #WaylandEnable=false + + - restart everything and Switch Users works fine. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1866416 Title: Ubuntu 18.04 system freezes when attempting to switch user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1866416/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866416] [NEW] Ubuntu 18.04 system freezes when attempting to switch user
Public bug reported: Ubuntu 18.04 freezes and must be manually powered down and rebooted when attempting to "Switch User". Prerequisites: - Use Ubuntu 18.04 - You need at least 2 users (e.g. user1 and user2) Expected behavior: - While logged in as any user, choose "Switch User" from top power drop down. - Click "Log in as another user" - Enter another user's credentials and login Bug behavior and steps to reproduce: - Start your computer - At the graphical login prompt, log in with user1: user1 is able to log in, its desktop is shown - While logged into the desktop of user1, choose "Switch user" - Returns to login screen, with prompt to enter user1 password - Click "Log in as another user" - RESULT: the screen freezes with no ability to type or move the mouse. It is never possible to login in as either user1 or user2 and the system must be manually powered down and restarted. NOTE 1: the same happens when user2 was the first to log in after a reboot of the system. "Switch User" ends up with the same freeze issue. NOTE 2: I've been getting crash reports at login that say "System program problem detected / Do you want to report the problem now?". I am unsure whether or not this is related, but the cat _usr_lib_gnome- session_gnome-session-check-accelerated.121.crash file in /var/crash provides the following information at the top of the report: ProblemType: Crash Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Mar 6 11:28:30 2020 DistroRelease: Ubuntu 18.04 ExecutablePath: /usr/lib/gnome-session/gnome-session-check-accelerated ExecutableTimestamp: 1525246842 ProcCmdline: /usr/lib/gnome-session/gnome-session-check-accelerated ProcCwd: /var/lib/gdm3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 11:49:25 2020 InstallationDate: Installed on 2020-03-03 (2 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1866416 Title: Ubuntu 18.04 system freezes when attempting to switch user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1866416/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847551] [NEW] Mutter 3.34.1 broke Night Light, screen color profiles
Public bug reported: Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen color profile switching. The commit at fault is 104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes when processing update” (which was intended to fix LP bug 1847044). Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851 ** Affects: mutter Importance: Unknown Status: Unknown ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #851 https://gitlab.gnome.org/GNOME/mutter/issues/851 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/851 Importance: Unknown Status: Unknown -- 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/1847551 Title: Mutter 3.34.1 broke Night Light, screen color profiles To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1847551/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844445] Re: gnome-session-binary crashed with SIGSEGV in tcache_thread_shutdown()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/185 Title: gnome-session-binary crashed with SIGSEGV in tcache_thread_shutdown() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/185/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843107] Re: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)
This is fixed by https://gitlab.gnome.org/GNOME/mutter/merge_requests/792 (I tested 850ef518795dcc20d3b9a4f661f70ff8d0ddacb2). -- 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/1843107 Title: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1843107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843107] Re: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/1843107 Title: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1843107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843107] Re: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #771 https://gitlab.gnome.org/GNOME/mutter/issues/771 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/771 Importance: Unknown Status: Unknown -- 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/1843107 Title: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1843107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843107] Re: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)
By adding some debugging output to mutter and gnome-shell I verified that mutter emits the x11-display-opened signal before gnome-shell is able to connect a handler for it, and the handler never runs. (Possibly things would be different in the experimental autostart- xwayland mode, but the whole system froze when I tried to log in with that enabled.) -- 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/1843107 Title: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1843107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843107] Re: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)
Hmm, I upgraded mutter from eoan-proposed and gnome-shell from eoan-
proposed plus those three commits
(https://launchpad.net/~andersk/+archive/ubuntu/ppa, if you want to
check my work), but it didn’t resolve the problem. Even after a reboot,
gsd-xsettings doesn’t start and X11 applications don’t get themed.
$ dpkg-query -W gir1.2-mutter-5 libmutter-5-0 mutter mutter-common gnome-shell
gnome-shell-common
gir1.2-mutter-5:amd64 3.33.92-1ubuntu1
gnome-shell 3.33.92-1ubuntu1andersk1
gnome-shell-common 3.33.92-1ubuntu1andersk1
libmutter-5-0:amd64 3.33.92-1ubuntu1
mutter 3.33.92-1ubuntu1
mutter-common 3.33.92-1ubuntu1
$ strings /usr/lib/gnome-shell/libgnome-shell.so | grep x11-display
global.display.connect('x11-display-opened', () => {
global.display.connect('x11-display-closing', () => {
$ systemctl --user status gnome-session-x11-services.target
gsd-xsettings.target gsd-xsettings.service
● gnome-session-x11-services.target - GNOME session X11 services
Loaded: loaded (/usr/lib/systemd/user/gnome-session-x11-services.target;
static; vendor preset: enabled)
Active: inactive (dead)
● gsd-xsettings.target - GNOME XSettings
Loaded: loaded (/usr/lib/systemd/user/gsd-xsettings.target; static; vendor
preset: enabled)
Active: inactive (dead)
● gsd-xsettings.service - GNOME XSettings
Loaded: loaded (/usr/lib/systemd/user/gsd-xsettings.service; static; vendor
preset: enabled)
Active: inactive (dead)
--
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/1843107
Title:
Themes and font settings don’t apply to X apps running in Wayland
(g-s-d 3.33.90 → 3.33.92 regression)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1843107/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843107] [NEW] Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)
Public bug reported: After upgrading gnome-settings-daemon from 3.33.90-1ubuntu2 to 3.33.92-1ubuntu1, my GTK theme and font settings selected with gnome- tweaks are no longer applied to X11 applications when running in a Wayland session (I tried Firefox and Emacs). This seems to be because gsd-xsettings is not running. Known workarounds: • downgrade gnome-settings-daemon to 3.33.90-1ubuntu2 and reboot; or • use Xorg instead of Wayland; or • manually start /usr/lib/gnome-settings-daemon/gsd-xsettings. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-settings-daemon 3.33.92-1ubuntu1 Uname: Linux 5.2.11-050211-lowlatency x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Fri Sep 6 17:24:02 2019 InstallationDate: Installed on 2016-02-19 (1295 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to eoan on 2019-06-23 (75 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1843107 Title: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1843107/+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
@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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
The situation with apache2 is what I documented in https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1792544/comments/9: “But since we’re apparently gathering information here: although Apache 2.4.x does not support PCRE2, Apache trunk does support PCRE2 as of r1773454. (As you can see, this support was added by creating separate conditionally compiled code paths for PCRE and PCRE2.) https://github.com/apache/httpd/commit/b1a3338e011a17ad190fb7f66cf5ca9acf353570” trunk is the 2.5.x branch, not 2.4.x. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820331] Re: gnome-shell crashed with SIGABRT. Assertion failure in meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode == META_POWER_SAVE_ON"
I hope 3.32.1 will get into Disco, but in case this can’t happen and a more minimal set of patches is required, these are the nine upstream patches I added to my mutter package to get it to stop crashing on wakeup: fe86694dd renderer/native: Make EGLStream page flip errors non-fatal 1eabaf12d renderer/native: Make the EGLStreams operate in mailbox mode 4cae9b5b1 monitor-manager: Clean up DPMS state tracking 40e7e5d35 renderer-native: Fix page flip retry timeout calculation 53b59d8bf renderer-native: Fake page flipped if power saving when retrying 3cc3b7526 renderer-native: Fake page flipping slower when power saving 88e4ff740 backend: Add API to freeze/thaw frame clock 808a75b23 renderer-native: Add helper to get backend from renderer b2d0184c6 renderer-native: Freeze frames while retrying to page flip Note that they were accepted into master nonconsecutively, with other commits between 1eabaf12d and 4cae9b5b1. -- 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/1820331 Title: gnome-shell crashed with SIGABRT. Assertion failure in meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode == META_POWER_SAVE_ON" To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1820331/+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 1820331] Re: gnome-shell crashed with SIGABRT
** Information type changed from Private to Public -- 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/1820331 Title: gnome-shell crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820331/+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 185928] Re: Pressing Space key should toggle play/pause (pause when playing; play when paused)
This is a standard for music players. Follow the standard!!! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/185928 Title: Pressing Space key should toggle play/pause (pause when playing; play when paused) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/185928/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
This happens on a clean installation of 18.10 here as well, and I'd like to point out that the window miniature previews are clearly visible and in some cases even readable from the lock screen by right clicking the application icons and selecting "All Windows". -- 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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+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 1795556] Re: mutter 3.30.0-4 FTBFS
As long as you're working on this package would you mind including the one-line upstream patch for bug 1788483, if you haven't already? -- 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/1795556 Title: mutter 3.30.0-4 FTBFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795556] Re: mutter 3.30.0-4 FTBFS
That was a local build. I also saw it on Launchpad with an unrelated patch (bug 1788483): https://launchpadlibrarian.net/391298478/buildlog_ubuntu- cosmic-i386.mutter_3.30.0-4andersk1_BUILDING.txt.gz However, the failure seems to have disappeared with today’s updates of other packages, or maybe the tests are just flaky. I’ll reopen this if I see the failure again. ** Changed in: mutter (Ubuntu) Status: New => Invalid -- 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/1795556 Title: mutter 3.30.0-4 FTBFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795556/+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 1788483] Re: gnome-shell crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr("assertion failed: (trap->end_sequence == 0)") from gdk_x11_display_error_trap_pop_internal()
(Still waiting on sponsorship, but apparently “In Progress” is the right
status for that.)
** Tags added: patch-accepted-upstream
--
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/1788483
Title:
gnome-shell crashed with SIGABRT in g_assertion_message() from
g_assertion_message_expr("assertion failed: (trap->end_sequence ==
0)") from gdk_x11_display_error_trap_pop_internal() from
meta_input_settings_x11_set_tablet_keep_aspect()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788483/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795556] [NEW] mutter 3.30.0-4 FTBFS
Public bug reported: mutter 3.30.0-4 fails to build from source (regression from 3.30.0-1). A full build log is attached. The relevant part is these test failures. == clutter 1.26.1: tests/conform/test-suite.log == # TOTAL: 83 # PASS: 81 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 2 .. contents:: :depth: 2 ERROR: actor-offscreen-redirect === # random seed: R02Sb2875ff7949f70873efba32072c693a6 1..1 # Start of actor tests ** Clutter-Conform:ERROR:actor-offscreen-redirect.c:147:verify_results: assertion failed (ABS ((int) expected_color_green - (int) pixel[1]) <= 2): (255 <= 2) # Start of offscreen tests Aborted (core dumped) Bail out! Clutter-Conform:ERROR:actor-offscreen-redirect.c:147:verify_results: assertion failed (ABS ((int) expected_color_green - (int) pixel[1]) <= 2): (255 <= 2) ERROR: actor-offscreen-redirect - Bail out! Clutter-Conform:ERROR:actor-offscreen-redirect.c:147:verify_results: assertion failed (ABS ((int) expected_color_green - (int) pixel[1]) <= 2): (255 <= 2) ERROR: actor-shader-effect == # random seed: R02S35d2b55cc4cd821aa7b19454f0028a03 1..1 ** Clutter-Conform:ERROR:actor-shader-effect.c:233:paint_cb: assertion failed (get_pixel (50, 50) == 0xff): (0 == 16711680) # Start of actor tests Aborted (core dumped) Bail out! Clutter-Conform:ERROR:actor-shader-effect.c:233:paint_cb: assertion failed (get_pixel (50, 50) == 0xff): (0 == 16711680) ERROR: actor-shader-effect - Bail out! Clutter-Conform:ERROR:actor-shader-effect.c:233:paint_cb: assertion failed (get_pixel (50, 50) == 0xff): (0 == 16711680) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic ** Attachment added: "mutter_3.30.0-4_amd64.build" https://bugs.launchpad.net/bugs/1795556/+attachment/5195672/+files/mutter_3.30.0-4_amd64.build -- 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/1795556 Title: mutter 3.30.0-4 FTBFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1788483] Re: gnome-shell crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr("assertion failed: (trap->end_sequence == 0)") from gdk_x11_display_error_trap_pop_internal()
(Is it really correct to mark this as “In Progress” and assigned to me
when there’s nothing else I can do to move this forward except wait for
a sponsor to pay attention?)
** Patch added: "debdiff adding upstream patch, rebased"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1788483/+attachment/5195604/+files/mutter_3.30.0-4_lp1788483.debdiff
--
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/1788483
Title:
gnome-shell crashed with SIGABRT in g_assertion_message() from
g_assertion_message_expr("assertion failed: (trap->end_sequence ==
0)") from gdk_x11_display_error_trap_pop_internal() from
meta_input_settings_x11_set_tablet_keep_aspect()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788483/+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 1788483] Re: gnome-shell crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr("assertion failed: (trap->end_sequence == 0)") from gdk_x11_display_error_trap_pop_internal()
** Patch added: "debdiff adding upstream patch"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788483/+attachment/5195090/+files/mutter_3.30.0-1_lp1788483.debdiff
--
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/1788483
Title:
gnome-shell crashed with SIGABRT in g_assertion_message() from
g_assertion_message_expr("assertion failed: (trap->end_sequence ==
0)") from gdk_x11_display_error_trap_pop_internal() from
meta_input_settings_x11_set_tablet_keep_aspect()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788483/+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 1792544] Re: demotion of pcre3 in favor of pcre2
Likewise, nginx does not support PCRE2: https://trac.nginx.org/nginx/ticket/720 ** Bug watch added: trac.nginx.org/nginx/ #720 http://trac.nginx.org/nginx/ticket/720 ** Changed in: nginx (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
I think that completes the analysis of the current state of things. Although it seems infeasible to demote PCRE at this time, there’s no reason that should block the promotion of PCRE2, especially seeing as a bundled copy of PCRE2 is already in main (18.04 and 18.10) via libqt5core5a. ** Changed in: sssd (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
Note to those filing upstream bugs: probably don’t call the old library “pcre3” since that’s not a thing outside Debian/Ubuntu. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
• Quagga: no PCRE2 support • Rasqal: no PCRE2 support • S-Lang: no PCRE2 support ** Changed in: quagga (Ubuntu) Status: New => Incomplete ** Changed in: rasqal (Ubuntu) Status: New => Incomplete ** Changed in: slang2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
• pam_mount: no PCRE2 support • nmap: no PCRE2 support • postfix: no PCRE2 support, http://postfix.1071664.n5.nabble.com/Plans-for-using-PCRE-v2-in-Postfix-td83200.html • pyScss: no PCRE2 support ** Changed in: libpam-mount (Ubuntu) Status: New => Incomplete ** Changed in: nmap (Ubuntu) Status: New => Incomplete ** Changed in: postfix (Ubuntu) Status: New => Incomplete ** Changed in: python-pyscss (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
• Aide: no PCRE2 support • Exim: no PCRE2 support, upstream bug: https://bugs.exim.org/show_bug.cgi?id=1878 • FreeRADIUS: no PCRE2 support, mentioned in passing: https://github.com/FreeRADIUS/freeradius-server/issues/1865 • GLib: no PCRE2 support • grep: no PCRE2 support ** Bug watch added: bugs.exim.org/ #1878 http://bugs.exim.org/show_bug.cgi?id=1878 ** Bug watch added: github.com/FreeRADIUS/freeradius-server/issues #1865 https://github.com/FreeRADIUS/freeradius-server/issues/1865 ** Changed in: aide (Ubuntu) Status: New => Incomplete ** Changed in: exim4 (Ubuntu) Status: New => Incomplete ** Changed in: freeradius (Ubuntu) Status: New => Incomplete ** Changed in: glib2.0 (Ubuntu) Status: New => Incomplete ** Changed in: grep (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
Copying from https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/163/comments/20, HAProxy and SELinux upstream support PCRE2. https://git.haproxy.org/?p=haproxy.git;a=commitdiff;h=f2592b29f13907ddf2bba42d00bc41cb8ee5b69b https://github.com/SELinuxProject/selinux/commit/50f0910cf05bdc1d10710c7c3fb748a178473387 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
apr-util has a false Build-Depends on libpcre3-dev; it should simply be dropped. A corresponding Depends was already dropped in https://bugs.debian.org/757140. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
Andreas: No, it’s not a bug. PCRE2 is a new project that’s not intended to be compatible with the older PCRE (i.e. what Debian misnamed “pcre3”). The API is completely different and this is expected. See bug 163 for context, and specifically the PCRE2 release announcement linked in the bug description: https://lists.exim.org/lurker/message/20150105.162835.0666407a.en.html That’s why getting rid of PCRE “in favor of” PCRE2 is a pointless way to frame the issue. PCRE2 neither replaces nor conflicts with PCRE, as was pointed out many times in bug 163. But since we’re apparently gathering information here: although Apache 2.4.x does not support PCRE2, Apache trunk does support PCRE2 as of r1773454. (As you can see, this support was added by creating separate conditionally compiled code paths for PCRE and PCRE2.) https://github.com/apache/httpd/commit/b1a3338e011a17ad190fb7f66cf5ca9acf353570 ** Bug watch added: Debian Bug tracker #757140 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757140 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790992] Re: gnome-shell crashes with SIGABRT when touching stylus to screen, "assertion failed: (trap->end_sequence == 0)" in in gdk_x11_display_error_trap_pop_internal() from gdk_x11_display_er
GNOME on Wayland works around the crash. Based on the apport-retrace results, this is possibly a duplicate of bug 1788483. -- 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/1790992 Title: gnome-shell crashes with SIGABRT when touching stylus to screen, "assertion failed: (trap->end_sequence == 0)" in in gdk_x11_display_error_trap_pop_internal() from gdk_x11_display_error_trap_pop() from meta_x11_error_trap_pop_with_return() from meta_input_settings_x11_set_stylus_button_map() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1790992/+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
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 1701289] Re: gnome-shell crashed with signal 5 in XIGetClientPointer() from gdk_x11_display_get_default_seat()
This may have been fixed by mutter 3.26.1-2 (bug 1722510). At least I can no longer reproduce it using the recipe in my duplicate bug 1722709. -- 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/1701289 Title: gnome-shell crashed with signal 5 in XIGetClientPointer() from gdk_x11_display_get_default_seat() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1701289/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722687] [NEW] ‘env GTK_IM_MODULE=uim gedit’ crashes with SIGSEGV in Wayland
Public bug reported: Running ‘env GTK_IM_MODULE=uim gedit’ in a Wayland session results in this crash. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gedit 3.22.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 10 20:50:10 2017 Disassembly: => 0x2:Cannot access memory at address 0x2 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2016-02-19 (599 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) ProcCmdline: gedit ProcEnviron: LANG=en_US.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x2: Cannot access memory at address 0x2 PC (0x0002) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: () XGetModifierMapping () at /usr/lib/x86_64-linux-gnu/libX11.so.6 im_uim_init_modifier_keys () at /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-uim.so im_module_init () at /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-uim.so () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gedit crashed with SIGSEGV UpgradeStatus: Upgraded to artful on 2017-05-02 (161 days ago) UserGroups: ** Affects: gedit (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash artful ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1722687 Title: ‘env GTK_IM_MODULE=uim gedit’ crashes with SIGSEGV in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1722687/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721681] Re: gnome-terminal-server crashed with SIGSEGV in XGetModifierMapping()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1721681 Title: gnome-terminal-server crashed with SIGSEGV in XGetModifierMapping() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1721681/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714745] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R()
I’m not sure. Since it’s been a week without any sign of an upload to artful-proposed, I’m changing this back to Confirmed. I have a patched build of gnome-shell in my PPA if you need it now: https://launchpad.net/~andersk/+archive/ubuntu/ppa/+packages https://launchpadlibrarian.net/339202115/gnome-shell_3.26.0-0ubuntu2_3.26.0-0ubuntu2andersk1.diff.gz ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Confirmed ** Tags removed: wayland-session ** Tags added: patch patch-accepted-upstream -- 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/1714745 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1714745/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714745] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R()
It seems to be the TopIcons Plus extension that triggers this so often. I think that’s roughly consistent with the upstream bug report. -- 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/1714745 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1714745/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714745] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R()
This might be triggered by a shell extension. I haven’t seen any crashes after turning them all off. I’ll see if I can bisect which one it is. -- 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/1714745 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1714745/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714745] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R()
This is happening to me very frequently (several times a day) on both Wayland and Xorg. On Wayland, it brings down the entire session. -- 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/1714745 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714745/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714745] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
** Information type changed from Private to Public -- 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/1714745 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714745/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1449001] Re: systemd-resolved: please do not use Google public DNS by default
** Also affects: systemd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658 Importance: Unknown Status: Unknown ** Changed in: systemd Importance: Unknown => Undecided ** Changed in: systemd Status: Fix Released => New ** Changed in: systemd Remote watch: Debian Bug tracker #761658 => None -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1449001 Title: systemd-resolved: please do not use Google public DNS by default To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1449001/+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 1689555] [NEW] Scrolling + "Terminal bell" crashes pulseaudio
Public bug reported: If "Terminal bell" is enabled (in "Profile Preferences" > "General"), and I scroll fast in the output of e.g less to cause the "alert sound" to be played repeatably very fast, pulseaudio crashes. >From /var/log/syslog: May 9 15:05:13 ubuntu-laptop indicator-sound[2948]: volume-control-pulse.vala:735: unable to get pulse unix socket: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 was not provided by any .service files May 9 15:05:15 ubuntu-laptop indicator-sound[2948]: volume-control-pulse.vala:735: unable to get pulse unix socket: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 was not provided by any .service files May 9 15:05:16 ubuntu-laptop unity-settings-[2940]: Unable to get default sink May 9 15:05:16 ubuntu-laptop unity-settings-[2940]: Unable to get default source May 9 15:05:16 ubuntu-laptop unity-settings-[2940]: Failed to connect context: Connection refused May 9 15:05:16 ubuntu-laptop unity-control-c[5557]: Failed to connect context: Connection refused May 9 15:05:16 ubuntu-laptop unity-control-c[5557]: Unable to find stream for bar '(null)' May 9 15:05:17 ubuntu-laptop indicator-sound[2948]: volume-control-pulse.vala:735: unable to get pulse unix socket: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 was not provided by any .service files May 9 15:06:01 ubuntu-laptop indicator-sound[2948]: message repeated 22 times: [ volume-control-pulse.vala:735: unable to get pulse unix socket: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 was not provided by any .service files] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Tue May 9 14:58:51 2017 InstallationDate: Installed on 2017-05-01 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1689555 Title: Scrolling + "Terminal bell" crashes pulseaudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1689555/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1676115] [NEW] systemd-resolved spams the system log with useless “Processing query...” messages
Public bug reported: If you are running ‘journalctl -f’ to try to debug some other problem, you are constantly interrupted by zillions of these messages from systemd-resolved: Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... This was fixed upstream in v233 by downgrading this message from log_info to log_debug: https://github.com/systemd/systemd/pull/5233 ** Affects: systemd Importance: Unknown Status: Unknown ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/systemd/systemd/issues #5233 https://github.com/systemd/systemd/issues/5233 ** Also affects: systemd via https://github.com/systemd/systemd/issues/5233 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676115 Title: systemd-resolved spams the system log with useless “Processing query...” messages To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1676115/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 897302] Re: Screen dims even automatic dimming is turned OFF (when on battery)
** Also affects: gnome-settings-daemon via https://bugzilla.gnome.org/show_bug.cgi?id=665073 Importance: Unknown Status: Unknown -- 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/897302 Title: Screen dims even automatic dimming is turned OFF (when on battery) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/897302/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1661020] [NEW] package gimp (not installed) failed to install/upgrade: försöker skriva över "/usr/lib/gimp/2.0/plug-ins/wavelet-decompose" som också finns i paketet gimp-plugin-registry 7.2014060
Public bug reported: ... ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gimp (not installed) ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu1 AptOrdering: gimp:amd64: Install libgimp2.0:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Jan 31 17:09:40 2017 DpkgTerminalLog: Förbereder att packa upp .../gimp_2.9.5~79-0z21~ppa~5170980_amd64.deb ... Packar upp gimp (2.9.5~79-0z21~ppa~5170980) över (2.9.5~71-0z0~ppa~00faf17) ... [1mdpkg:[0m fel vid hantering av arkivet /var/cache/apt/archives/gimp_2.9.5~79-0z21~ppa~5170980_amd64.deb (--unpack): försöker skriva över "/usr/lib/gimp/2.0/plug-ins/wavelet-decompose" som också finns i paketet gimp-plugin-registry 7.20140602ubuntu3 ErrorMessage: försöker skriva över "/usr/lib/gimp/2.0/plug-ins/wavelet-decompose" som också finns i paketet gimp-plugin-registry 7.20140602ubuntu3 InstallationDate: Installed on 2016-02-22 (345 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4~beta4ubuntu1 SourcePackage: gimp Title: package gimp (not installed) failed to install/upgrade: försöker skriva över "/usr/lib/gimp/2.0/plug-ins/wavelet-decompose" som också finns i paketet gimp-plugin-registry 7.20140602ubuntu3 UpgradeStatus: Upgraded to zesty on 2017-01-13 (18 days ago) ** Affects: gimp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1661020 Title: package gimp (not installed) failed to install/upgrade: försöker skriva över "/usr/lib/gimp/2.0/plug-ins/wavelet-decompose" som också finns i paketet gimp-plugin-registry 7.20140602ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1661020/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1649370] [NEW] libnss-{resolve,myhostname} don’t install correctly if previously removed without being purged
Public bug reported:
# grep hosts /etc/nsswitch.conf
hosts: files myhostname dns
# apt install libnss-resolve
# grep hosts /etc/nsswitch.conf
hosts: files myhostname resolve [!UNAVAIL=return] dns
# apt remove libnss-resolve
# grep hosts /etc/nsswitch.conf
hosts: files myhostname dns
# apt install libnss-resolve
# grep hosts /etc/nsswitch.conf
hosts: files myhostname dns
libnss-resolve.postinst and libnss-myhostname.postinst only update
/etc/nsswitch.conf if [ "$1" = configure ] && [ -z "$2" ]. If the
package was previously removed but not purged (it is in the Config-Files
state), dpkg passes the previous version as $2, so this fails.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: zesty
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1649370
Title:
libnss-{resolve,myhostname} don’t install correctly if previously
removed without being purged
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1649370/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1647031] [NEW] systemd-resolved’s 127.0.0.53 server does not follow CNAME records
Public bug reported:
$ systemd-resolve www.freedesktop.org
www.freedesktop.org: 131.252.210.176
2610:10:20:722:a800:ff:feda:470f
(annarchy.freedesktop.org)
-- Information acquired via protocol DNS in 673.6ms.
-- Data is authenticated: no
$ ping www.freedesktop.org
ping: www.freedesktop.org: Name or service not known
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53
$ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
;www.freedesktop.org. IN A
www.freedesktop.org.7146IN CNAME annarchy.freedesktop.org.
$ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
;www.freedesktop.org. IN A
www.freedesktop.org.14399 IN CNAME annarchy.freedesktop.org.
annarchy.freedesktop.org. 14399 IN A 131.252.210.176
I trust it needn’t be explained why this makes the internet almost
completely useless in zesty.
** Affects: systemd
Importance: Unknown
Status: Unknown
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: github.com/systemd/systemd/issues #3826
https://github.com/systemd/systemd/issues/3826
** Also affects: systemd via
https://github.com/systemd/systemd/issues/3826
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1647031
Title:
systemd-resolved’s 127.0.0.53 server does not follow CNAME records
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1647031/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1628778] [NEW] systemd-resolved: after network reconnection, DNSSEC unsigned zones treated as bogus, stop resolving
Public bug reported: On the MIT network (which runs some ancient version of BIND 9), systemd- resolved stops resolving anything that isn’t DNSSEC-signed after I disconnect and reconnect the network. Signed zones continue to resolve. This happens with either DNSSEC=yes or the default DNSSEC=allow- downgrade. $ systemd-resolve github.com github.com: 192.30.253.113 -- Information acquired via protocol DNS in 15.6ms. -- Data is authenticated: no $ # (disconnect and reconnect wifi) $ systemd-resolve github.com github.com: resolve call failed: DNSSEC validation failed: no-signature More debug information is available in my upstream report (https://github.com/systemd/systemd/issues/4175), which has gotten no response in the last week and a half. I’m refiling this here because I believe that this regression and others (bug 1588230, bug 1624071, bug 1624317, bug 1449001) indicate that systemd-resolved is not ready for production, and with final freeze just a week away, leaving systemd-resolved enabled for the yakkety release would be reckless. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: regression-release yakkety -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1628778 Title: systemd-resolved: after network reconnection, DNSSEC unsigned zones treated as bogus, stop resolving To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1628778/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624320] [NEW] systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
Public bug reported: systemd-resolved, or more precisely the hook script /lib/systemd/system /systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624320 Title: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624317] [NEW] systemd-resolved breaks VPN with split-horizon DNS
Public bug reported: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624317/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624071] [NEW] libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation
Public bug reported: The libnss-resolve postinst script inserts ‘resolve’ before ‘dns’ in the hosts line of /etc/nsswitch.conf. This makes DNSSEC validation impossible, even with DNSSEC=yes in /etc/systemd/resolved.conf, because if libnss_resolve returns a validation failure, glibc will simply fall back to libnss_dns. It also makes NXDOMAIN lookups twice as slow. The following syntax would preserve the fallback in the case that systemd-resolved is not running at all, but allow systemd-resolved to fail lookups that should fail when it is running: hosts: files resolve [!TRYAGAIN=return] dns ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624071 Title: libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624071/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1591868] Re: fwupd consuming 100% CPU
The infinite loop is not in libyaml (yaml_parser_parse), but rather in its caller in appstream-glib (as_node_yaml_process_layer), which is ignoring the error code returned by yaml_parser_parse and blindly going around the loop again. This patch fixes it. ** Patch added: "appstream-glib_0.5.17-0ubuntu1_lp1591868.debdiff" https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1591868/+attachment/4722986/+files/appstream-glib_0.5.17-0ubuntu1_lp1591868.debdiff ** Changed in: libyaml (Ubuntu Xenial) Status: New => Invalid ** Changed in: libyaml (Ubuntu Yakkety) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1591868 Title: fwupd consuming 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1591868/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1592515] [NEW] Snap Packages shows up in Disk collumn
Public bug reported: Xenial 16.04 gnome-disk-utility 3.18.3.1 http://pix.toile-libre.org/upload/original/1465929217.png ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1592515 Title: Snap Packages shows up in Disk collumn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1592515/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1583862] Re: apt-get update hangs after hit/get
*** This bug is a duplicate of bug 1579712 *** https://bugs.launchpad.net/bugs/1579712 ** This bug has been marked a duplicate of bug 1579712 Refresh hangs indefinitely, appstreamcli using 100% CPU -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1583862 Title: apt-get update hangs after hit/get To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1583862/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1573206] Re: GNOME Software does not install third-party .deb packages
It seems like if a third party package has been (attempted) installed, automated updates are disabled. / (#17) However, even after you get the deb package installed, it breaks your ability to sudo apt-get update. / --- "Hi, this has been fixed upstream. If you still have issues, please fully update with: sudo apt-get update sudo apt-get upgrade" Does the upstream fix for everyone affected (who has attempted to install a third party package such as Google Chrome) entail to start a terminal session and run these commands, while adding "sudo apt-get -f install"? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1573206 Title: GNOME Software does not install third-party .deb packages To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1573206/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1541807] [NEW] package udev 228-5ubuntu1 failed to install/upgrade: underprocessen installerade post-installation-skript gav felkod 1
Public bug reported: ... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 228-5ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Thu Feb 4 03:32:43 2016 ErrorMessage: underprocessen installerade post-installation-skript gav felkod 1 InstallationDate: Installed on 2016-01-29 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160127) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=afe7feaf-b274-43a5-b3a7-a6166ca11362 ro quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: systemd Title: package udev 228-5ubuntu1 failed to install/upgrade: underprocessen installerade post-installation-skript gav felkod 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1541807 Title: package udev 228-5ubuntu1 failed to install/upgrade: underprocessen installerade post-installation-skript gav felkod 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1541807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1541985] [NEW] package udev 228-5ubuntu2 failed to install/upgrade: underprocessen installerade post-installation-skript gav felkod 1
Public bug reported: ... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 228-5ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Thu Feb 4 19:45:28 2016 ErrorMessage: underprocessen installerade post-installation-skript gav felkod 1 InstallationDate: Installed on 2016-01-29 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160127) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=afe7feaf-b274-43a5-b3a7-a6166ca11362 ro quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: systemd Title: package udev 228-5ubuntu2 failed to install/upgrade: underprocessen installerade post-installation-skript gav felkod 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1541985 Title: package udev 228-5ubuntu2 failed to install/upgrade: underprocessen installerade post-installation-skript gav felkod 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1541985/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1528728] Re: gnome-terminal starts up at 79×23 instead of 80×24
** Patch added: "vte2.91_0.42.1-1ubuntu1_lp1528728.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1528728/+attachment/4539301/+files/vte2.91_0.42.1-1ubuntu1_lp1528728.debdiff ** Tags added: patch ** Bug watch added: Debian Bug tracker #787104 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787104 ** Also affects: vte2.91 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787104 Importance: Unknown Status: Unknown ** Package changed: gnome-terminal (Ubuntu) => vte2.91 (Ubuntu) ** Bug watch added: GNOME Bug Tracker #750559 https://bugzilla.gnome.org/show_bug.cgi?id=750559 ** Also affects: vte via https://bugzilla.gnome.org/show_bug.cgi?id=750559 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1528728 Title: gnome-terminal starts up at 79×23 instead of 80×24 To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/1528728/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1528728] [NEW] gnome-terminal starts up at 79×23 instead of 80×24
Public bug reported: Starting gnome-terminal results in a 79×23 window instead of the standard 80×24, at least in Ubuntu Gnome with the default Adwaita theme on a high-DPI laptop. This makes it irritating to use some applications designed for an 80-column terminal. According to an upstream bug report (https://bugzilla.gnome.org/show_bug.cgi?id=750559), the problem is caused by the Ubuntu patch debian/patches/0001-Add-the-style-context- provider-with-FALLBACK-priorit.patch, which was reverted upstream (https://bugzilla.gnome.org/show_bug.cgi?id=740123#c6) and in Debian (https://bugs.debian.org/787104) for this reason. A new version of this patch (https://bugzilla.gnome.org/show_bug.cgi?id=740123#c9) fixes the problem for me. ** Affects: vte Importance: Unknown Status: Unknown ** Affects: vte2.91 (Ubuntu) Importance: Undecided Status: New ** Affects: vte2.91 (Debian) Importance: Unknown Status: Unknown ** Tags: patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1528728 Title: gnome-terminal starts up at 79×23 instead of 80×24 To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/1528728/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1512209] Re: update-manager crashed with SyntaxError in find_cookie(): invalid or missing encoding declaration for '/usr/bin/sys'
** Bug watch added: Python Roundup #25493 http://bugs.python.org/issue25493 ** Also affects: python via http://bugs.python.org/issue25493 Importance: Unknown Status: Unknown ** Bug watch added: GNOME Bug Tracker #757184 https://bugzilla.gnome.org/show_bug.cgi?id=757184 ** Also affects: pygobject via https://bugzilla.gnome.org/show_bug.cgi?id=757184 Importance: Unknown Status: Unknown ** Attachment removed: "CurrentDmesg.txt.txt" https://bugs.launchpad.net/pygobject/+bug/1512209/+attachment/4510908/+files/CurrentDmesg.txt.txt ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/pygobject/+bug/1512209/+attachment/4510912/+files/JournalErrors.txt ** Information type changed from Private to Public ** Also affects: pygobject (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1512209 Title: update-manager crashed with SyntaxError in find_cookie(): invalid or missing encoding declaration for '/usr/bin/sys' To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/1512209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1512209] Re: update-manager crashed with SyntaxError in find_cookie(): invalid or missing encoding declaration for '/usr/bin/sys'
This is a combination of two problems. One is that starting update-
manager results in these warnings:
/usr/bin/update-manager:28: PyGIWarning: Gtk was imported without specifying a
version first. Use gi.require_version('Gtk', '3.0') before import to ensure
that the right version gets loaded.
from gi.repository import Gtk
/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py:26: PyGIWarning:
GdkX11 was imported without specifying a version first. Use
gi.require_version('GdkX11', '3.0') before import to ensure that the right
version gets loaded.
from gi.repository import Gdk, GdkX11
/usr/lib/python3/dist-packages/UpdateManager/UnitySupport.py:29: PyGIWarning:
Dbusmenu was imported without specifying a version first. Use
gi.require_version('Dbusmenu', '0.4') before import to ensure that the right
version gets loaded.
from gi.repository import Dbusmenu, Unity
/usr/lib/python3/dist-packages/UpdateManager/UnitySupport.py:29: PyGIWarning:
Unity was imported without specifying a version first. Use
gi.require_version('Unity', '7.0') before import to ensure that the right
version gets loaded.
from gi.repository import Dbusmenu, Unity
The other is that when openafs-client is installed, the presence of
/usr/bin/sys causes Python to crash while displaying these warnings (see
linked bugs).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1512209
Title:
update-manager crashed with SyntaxError in find_cookie(): invalid or
missing encoding declaration for '/usr/bin/sys'
To manage notifications about this bug go to:
https://bugs.launchpad.net/pygobject/+bug/1512209/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1314556] Re: Unable to mount Android MTP device
+1 on the last comment. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1314556 Title: Unable to mount Android MTP device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1419856] Re: Long Delay When Pressing Volume Up/Down Keys
fixed in 15.04 ** Changed in: gnome-power-manager (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1419856 Title: Long Delay When Pressing Volume Up/Down Keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1419856/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1427877] Re: Media, brightness and volume keys don't work with GNOME 3.15.90
Every time I press one of these keys, I get the message
(gnome-settings-daemon:7822): GLib-GIO-WARNING **: Dropping signal
AcceleratorActivated of type (ua{sv}) since the type from the expected
interface is (uuu)
This is probably the same thing that happened in LP: #1217196 and LP:
#1376471.
--
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/1427877
Title:
Media, brightness and volume keys don't work with GNOME 3.15.90
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1427877/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
