[Bug 2066352] [NEW] Desktop session crashes randomly
Public bug reported: On a test laptop running Ubuntu 24.04, I am occasionally seeing my desktop session crash and return to the login screen. I haven't identified a pattern for these crashes yet but seems to occur randomly regardless of which app i have open or if I'm interacting with the system or it's idle. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5.1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 22 10:38:31 2024 DisplayManager: gdm3 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/usr/local/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Attachment added: "This journalctl log contains logs for the most recent crash. Crash occurred at around 10:05AM" https://bugs.launchpad.net/bugs/2066352/+attachment/5781146/+files/journal.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/2066352 Title: Desktop session crashes randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2066352/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
Thanks for the info. Very excited to know that 24.04 will get this automatically as part of 46.1. I'm curious if 46.1 is something that's days, weeks, or months away from being released on 24.04? I ask because we've got several folks internally running into this and I'm trying to decide if it's better to wait for the fix to hit 24.04 or for us to build a deb with the fix and have folks use that for now. If the fix is likely to reach 24.04 soon, then we'll wait. If not, then we'll likely do some work to get the fix to folks sooner. Thanks again. -- 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/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2063818] [NEW] libzmq5 : Depends: libpgm-5.3-0 (>= 5.1.116~dfsg) but only libpgm-5.3-0t64 is available
Public bug reported: Uuntu 24.04 Noble I see this when trying to install libzmq5 libzmq5 is in Ubuntu Universe, but the bug reporter does not think libzmq5 existing in ubuntu, so I put zeromq3 instead. the "I don't know" option does not let you select it when you go to submit bug. The following packages have unmet dependencies: libzmq5 : Depends: libpgm-5.3-0 (>= 5.1.116~dfsg) E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. It appears to be looking for libpgm-5.3-0 but only libpgm-5.3-0t64 is available ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libzmq5 4.3.5-1build2 Uname: Linux 6.8.7-jcd x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 11:02:52 2024 InstallationDate: Installed on 2022-11-27 (516 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: zeromq3 UpgradeStatus: Upgraded to noble on 2024-04-25 (1 days ago) ** Affects: zeromq3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/2063818 Title: libzmq5 : Depends: libpgm-5.3-0 (>= 5.1.116~dfsg) but only libpgm-5.3-0t64 is available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/2063818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2058923] [NEW] Clicking 'App Details' from the Apps tab does not work
Public bug reported: This was tested on Ubuntu 24.04 with all current updates applied. To reproduce the issue: - Open gnome-control-centre - Navigate to the 'Apps' section - Click on any app - Click the 'App Details' button The system will open the snap-store front-page, but won't show the given apps details. This seems to be the same for both .deb and Snap packages. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:46~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 25 11:05:37 2024 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/usr/local/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2058923 Title: Clicking 'App Details' from the Apps tab does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2058923/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2052784] Re: Settings not responding
Same issue for me. It looks like this only occurs on the first login with a given user. After logging-out and back in again, I can't reproduce the issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2052784 Title: Settings not responding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2052784/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724037] Re: Allow GNOME fractional scaling below 100%
@darkdragon-001 by way of an update, I re-tried this on 24.04 (development) as of this date, using Gnome 45.3, on Wayland and it worked. It's quite uncanny to see 2400x1600 rendered on a 2160x1440 screen, but it worked with the exception of a couple of apps that were blew up spectacularly, including OBS, and Slack... otherwise... everything else worked fine, and at the scaling factor above (90%), things seemed quite usable... it looked a little like an old CRT that was being pushed a little hard, but for certain applications this could be awesome. I wish the UI in gnome would offer the ability to be more granular than just 25% increments, and also go below 100%, perhaps with a warning, or from within Gnome Tweaks. -- 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/1724037 Title: Allow GNOME fractional scaling below 100% To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724037/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046992] Re: ubuntu 22.04 fwupd apt package seems broken (library / daemon version mismatch)
** Description changed: - System version: + On Ubuntu 22.04.03, the fwupd package fails to perform a clean apt install. + The error given upon service startup is the following: + + Dec 19 21:36:46 jwlandon-ThinkPad-E14-Gen-2 fwupd[9985]: Failed to load + engine: libfwupd version 1.9.4 does not match daemon 1.7.9 + + + More info below: + + System version: root@jwlandon-ThinkPad-E14-Gen-2:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy - No fwupd related packages installed: + No fwupd related packages installed: root@jwlandon-ThinkPad-E14-Gen-2:~# apt list --installed 2> /dev/null |grep fwupd - Now I install fwupd: + Now I install fwupd: root@jwlandon-ThinkPad-E14-Gen-2:~# apt install fwupd Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: - fwupd-signed libfwupd2 libfwupdplugin5 + fwupd-signed libfwupd2 libfwupdplugin5 Suggested packages: - gir1.2-fwupd-2.0 + gir1.2-fwupd-2.0 The following NEW packages will be installed: - fwupd fwupd-signed libfwupd2 libfwupdplugin5 + fwupd fwupd-signed libfwupd2 libfwupdplugin5 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/2,889 kB of archives. After this operation, 7,989 kB of additional disk space will be used. - Do you want to continue? [Y/n] + Do you want to continue? [Y/n] Selecting previously unselected package libfwupd2:amd64. (Reading database ... 329400 files and directories currently installed.) Preparing to unpack .../libfwupd2_1.7.9-1~22.04.3_amd64.deb ... Unpacking libfwupd2:amd64 (1.7.9-1~22.04.3) ... Selecting previously unselected package libfwupdplugin5:amd64. Preparing to unpack .../libfwupdplugin5_1.7.9-1~22.04.3_amd64.deb ... Unpacking libfwupdplugin5:amd64 (1.7.9-1~22.04.3) ... Selecting previously unselected package fwupd. Preparing to unpack .../fwupd_1.7.9-1~22.04.3_amd64.deb ... Unpacking fwupd (1.7.9-1~22.04.3) ... Selecting previously unselected package fwupd-signed. Preparing to unpack .../fwupd-signed_1.51.1~22.04.1+1.4-0ubuntu0.1_amd64.deb ... Unpacking fwupd-signed (1.51.1~22.04.1+1.4-0ubuntu0.1) ... Setting up libfwupd2:amd64 (1.7.9-1~22.04.3) ... Setting up fwupd-signed (1.51.1~22.04.1+1.4-0ubuntu0.1) ... Setting up libfwupdplugin5:amd64 (1.7.9-1~22.04.3) ... Setting up fwupd (1.7.9-1~22.04.3) ... fwupd-offline-update.service is a disabled or a static unit, not starting it. fwupd-refresh.service is a disabled or a static unit, not starting it. fwupd-refresh.timer is a disabled or a static unit, not starting it. fwupd.service is a disabled or a static unit, not starting it. Processing triggers for libc-bin (2.35-0ubuntu3.5) ... Processing triggers for man-db (2.10.2-1) ... Processing triggers for dbus (1.12.20-2ubuntu4.1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... fwupd packages are now installed: root@jwlandon-ThinkPad-E14-Gen-2:~# apt list --installed 2> /dev/null |grep fwupd fwupd-signed/jammy-updates,now 1.51.1~22.04.1+1.4-0ubuntu0.1 amd64 [installed,automatic] fwupd/jammy-updates,now 1.7.9-1~22.04.3 amd64 [installed] libfwupd2/jammy-updates,now 1.7.9-1~22.04.3 amd64 [installed,automatic] libfwupdplugin5/jammy-updates,now 1.7.9-1~22.04.3 amd64 [installed,automatic] Service is unable to start: root@jwlandon-ThinkPad-E14-Gen-2:~# systemctl start fwupd Job for fwupd.service failed because the control process exited with error code. See "systemctl status fwupd.service" and "journalctl -xeu fwupd.service" for details. Service complains about a library to daemon sw version mismatch: root@jwlandon-ThinkPad-E14-Gen-2:~# systemctl status fwupd × fwupd.service - Firmware update daemon - Loaded: loaded (/lib/systemd/system/fwupd.service; static) - Active: failed (Result: exit-code) since Tue 2023-12-19 21:36:46 PST; 20s ago -Docs: https://fwupd.org/ - Process: 9985 ExecStart=/usr/libexec/fwupd/fwupd (code=exited, status=1/FAILURE) -Main PID: 9985 (code=exited, status=1/FAILURE) - CPU: 59ms + Loaded: loaded (/lib/systemd/system/fwupd.service; static) + Active: failed (Result: exit-code) since Tue 2023-12-19 21:36:46 PST; 20s ago + Docs: https://fwupd.org/ + Process: 9985 ExecStart=/usr/libexec/fwupd/fwupd (code=exited, status=1/FAILURE) + Main PID: 9985 (code=exited, status=1/FAILURE) + CPU: 59ms Dec 19 21:36:46 jwlandon-ThinkPad-E14-Gen-2 systemd[1]: Starting Firmware update daemon... Dec 19 21:36:46 jwlandon-ThinkPad-E14-Gen-2 fwupd[9985]: Failed to load engine: libfwupd version 1.9.4 does not match daemon 1.7.9 Dec 19 21:36:46 jwlandon-ThinkPad-E14-Gen-2 systemd[1]: fwupd.service: Main process exited, code=exited, status=1/FAILURE Dec 19 21:36:46
[Bug 2046992] [NEW] ubuntu 22.04 fwupd apt package seems broken (library / daemon version mismatch)
Public bug reported: System version: root@jwlandon-ThinkPad-E14-Gen-2:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy No fwupd related packages installed: root@jwlandon-ThinkPad-E14-Gen-2:~# apt list --installed 2> /dev/null |grep fwupd Now I install fwupd: root@jwlandon-ThinkPad-E14-Gen-2:~# apt install fwupd Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: fwupd-signed libfwupd2 libfwupdplugin5 Suggested packages: gir1.2-fwupd-2.0 The following NEW packages will be installed: fwupd fwupd-signed libfwupd2 libfwupdplugin5 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/2,889 kB of archives. After this operation, 7,989 kB of additional disk space will be used. Do you want to continue? [Y/n] Selecting previously unselected package libfwupd2:amd64. (Reading database ... 329400 files and directories currently installed.) Preparing to unpack .../libfwupd2_1.7.9-1~22.04.3_amd64.deb ... Unpacking libfwupd2:amd64 (1.7.9-1~22.04.3) ... Selecting previously unselected package libfwupdplugin5:amd64. Preparing to unpack .../libfwupdplugin5_1.7.9-1~22.04.3_amd64.deb ... Unpacking libfwupdplugin5:amd64 (1.7.9-1~22.04.3) ... Selecting previously unselected package fwupd. Preparing to unpack .../fwupd_1.7.9-1~22.04.3_amd64.deb ... Unpacking fwupd (1.7.9-1~22.04.3) ... Selecting previously unselected package fwupd-signed. Preparing to unpack .../fwupd-signed_1.51.1~22.04.1+1.4-0ubuntu0.1_amd64.deb ... Unpacking fwupd-signed (1.51.1~22.04.1+1.4-0ubuntu0.1) ... Setting up libfwupd2:amd64 (1.7.9-1~22.04.3) ... Setting up fwupd-signed (1.51.1~22.04.1+1.4-0ubuntu0.1) ... Setting up libfwupdplugin5:amd64 (1.7.9-1~22.04.3) ... Setting up fwupd (1.7.9-1~22.04.3) ... fwupd-offline-update.service is a disabled or a static unit, not starting it. fwupd-refresh.service is a disabled or a static unit, not starting it. fwupd-refresh.timer is a disabled or a static unit, not starting it. fwupd.service is a disabled or a static unit, not starting it. Processing triggers for libc-bin (2.35-0ubuntu3.5) ... Processing triggers for man-db (2.10.2-1) ... Processing triggers for dbus (1.12.20-2ubuntu4.1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... fwupd packages are now installed: root@jwlandon-ThinkPad-E14-Gen-2:~# apt list --installed 2> /dev/null |grep fwupd fwupd-signed/jammy-updates,now 1.51.1~22.04.1+1.4-0ubuntu0.1 amd64 [installed,automatic] fwupd/jammy-updates,now 1.7.9-1~22.04.3 amd64 [installed] libfwupd2/jammy-updates,now 1.7.9-1~22.04.3 amd64 [installed,automatic] libfwupdplugin5/jammy-updates,now 1.7.9-1~22.04.3 amd64 [installed,automatic] Service is unable to start: root@jwlandon-ThinkPad-E14-Gen-2:~# systemctl start fwupd Job for fwupd.service failed because the control process exited with error code. See "systemctl status fwupd.service" and "journalctl -xeu fwupd.service" for details. Service complains about a library to daemon sw version mismatch: root@jwlandon-ThinkPad-E14-Gen-2:~# systemctl status fwupd × fwupd.service - Firmware update daemon Loaded: loaded (/lib/systemd/system/fwupd.service; static) Active: failed (Result: exit-code) since Tue 2023-12-19 21:36:46 PST; 20s ago Docs: https://fwupd.org/ Process: 9985 ExecStart=/usr/libexec/fwupd/fwupd (code=exited, status=1/FAILURE) Main PID: 9985 (code=exited, status=1/FAILURE) CPU: 59ms Dec 19 21:36:46 jwlandon-ThinkPad-E14-Gen-2 systemd[1]: Starting Firmware update daemon... Dec 19 21:36:46 jwlandon-ThinkPad-E14-Gen-2 fwupd[9985]: Failed to load engine: libfwupd version 1.9.4 does not match daemon 1.7.9 Dec 19 21:36:46 jwlandon-ThinkPad-E14-Gen-2 systemd[1]: fwupd.service: Main process exited, code=exited, status=1/FAILURE Dec 19 21:36:46 jwlandon-ThinkPad-E14-Gen-2 systemd[1]: fwupd.service: Failed with result 'exit-code'. Dec 19 21:36:46 jwlandon-ThinkPad-E14-Gen-2 systemd[1]: Failed to start Firmware update daemon. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Summary changed: - ubuntu 22.04 fwupd apt package seems broken + ubuntu 22.04 fwupd apt package seems broken (library / daemon version mismatch) -- 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/2046992 Title: ubuntu 22.04 fwupd apt package seems broken (library / daemon version mismatch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2046992/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011806] Re: [lunar] Snaps don't launch due to cgroup issue
@Jonas: If KDE is launching apps in the same way gnome-shell was, it is inherently racy. It needs to make sure the child process is in the new cgroup before executing the application. Doing the cgroup move after the app is already running causes problems if the application itself wants to configure cgroups, and could let child processes of the app itself escape the cgroup if they are created before the launcher tries to move the app. -- 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/2011806 Title: [lunar] Snaps don't launch due to cgroup issue To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2011806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2041853] Re: screen goes blank, audio cuts out
Thanks for looking at this. I have worked around the issue by reverting my kernel to 5.15 There is no doubt an issue somewhere with the hardware/software stack I was using but I couldn't figure out what it was. For the record : - AMD Ryzen 7 PRO 6850U - Kernel 6.2.0-26 - Ubuntu 22.04.3 You can close/delete this 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/2041853 Title: screen goes blank, audio cuts out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041853/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2042724] [NEW] locking screen results in exit of session
Public bug reported: system installed with 22.04, upgraded to 23.04 and then to 23.10 today; whenever I lock the screen or the laptop suspends, I'm presented with the login screen to re-authenticate but my session is not maintained and all apps have been killed. Issue was not present on Lunar. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gdm3 45~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 4 14:13:53 2023 InstallationDate: Installed on 2023-09-12 (53 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: gdm3 UpgradeStatus: Upgraded to mantic on 2023-11-04 (0 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2042724 Title: locking screen results in exit of session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2042724/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2041853] [NEW] screen goes blank, audio cuts out, cause Window manager warning: Overwriting existing binding of keysym messages
Public bug reported: I'm tracking down the multiple causes of screen flashes and audio interruption on my ubuntu 22.04 laptop. Issue open with Lenovo : https://forums.lenovo.com/t5/Ubuntu/ThinkPad-T14s-Gen-3-AMD-Ryzen-Screen-flickers-randomly-and-becomes-black-for-4-5-seconds/m-p/525298 This bug is one of the causes (log reversed : journalctl -r) oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac8bfbc10] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acd416dc0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac996b860] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac878ac50] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acb009cc0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac878a610] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac9f6a480] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acd404df0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac878a2f0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acb16d9a0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558aca446320] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acdf86f70] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac996a4e0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558aca9a6fd0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac9e94de0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558aca9a6350] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acb121e80] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac996ab60] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558aca9a6670] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acd3dada0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion
[Bug 2037497]
(In reply to Adam Williamson from comment #14) > Can reporters please test downgrading packages to figure out what actually > fixes this? I'd suggest this order: > > 1. Downgrade mesa to > https://koji.fedoraproject.org/koji/buildinfo?buildID=2274339 > 2. If that doesn't fix it, downgrade mutter and gnome-shell to > https://koji.fedoraproject.org/koji/buildinfo?buildID=2284675 and > https://koji.fedoraproject.org/koji/buildinfo?buildID=2284676 > > if that doesn't fix it, report back and we'll try something else, I guess. :D > > Instructions for downgrading: `dnf -y install koji`, then make a scratch dir > somewhere (in your home dir or /var/tmp or something), and do `koji > download-build --arch=x86_64 --arch=noarch (buildid)` , where (buildid) is > the build ID from the URL, so 2274339 for mesa. Then do `dnf downgrade > *.rpm`. None of this worked, nor mesa-23.2.0~rc2-1.fc39. I was able to get it working again by downgrading to mesa-23.1.5-1.fc39 (build 2268808). Will try to bisect. -- 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/2037497 Title: gnome-shell crashed with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2029216] [NEW] Generating an escrow-packet fails
Public bug reported: https://access.redhat.com/documentation/en- us/red_hat_enterprise_linux/6/html/storage_administration_guide/ch- volumekey Attempting to generate an escrow-packet as documented at the above link fails with the following error: ``` sudo volume_key --save ./luks.img --output ./escrow-packet volume_key: Error opening `./luks.img': Error getting information about volume `./luks.img': Invalid argument ``` The exact same command works on Fedora Workstation 38. To replicate the issue, do the following: - On Ubuntu 22.04 (haven't tested other releases) - Install `volume-key` package - Generate a LUKS encrypted volume ``` # Pre-allocate a 1GB volume sudo fallocate -l 1GB ./luks.img sudo cryptsetup luksFormat ./luks.img # Follow prompts to setup the volume with a passphrase ``` - Try to generate the escrow-packet ``` sudo volume_key --save ./luks.img --output ./escrow-packet ``` ** Affects: volume-key (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to volume-key in Ubuntu. https://bugs.launchpad.net/bugs/2029216 Title: Generating an escrow-packet fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/volume-key/+bug/2029216/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983112] Re: Appstream does not install config file
Had some time to test this more. I'm almost certain this is caused by the server autoinstall method. After doing another manual server install (interactive), and installing ubuntu-desktop-minimal, I just need to do a `snap refresh snapd` to fix the issue with the software store. /etc/apt/apt.conf.d/50appstream is present without any extra steps. If I do an autoinstall, and list appstream as the only package to install, /etc/apt/apt.conf.d/50appstream is missing. The command run by the installer is below: ``` /usr/bin/apt-get --quiet --assume-yes --option=Dpkg::options::=--force-unsafe-io --option=Dpkg::Options::=--force-confold install appstream ``` But if I run this manually on a clean system, /etc/apt/apt.conf.d/50appstream is present. So the issue must be something else related to the autoinstall. I can only replicate this issue if using the Ubuntu Autoinstall method. Should I open a separate issue for this? I've already added subiquity package to the affected packages list. -- 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/1983112 Title: Appstream does not install config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983112] Re: Appstream does not install config file
** Also affects: subiquity (Ubuntu) Importance: Undecided Status: New -- 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/1983112 Title: Appstream does not install config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2022155] [NEW] File selection dialog does not allow selecting multiple files using Ctrl
Public bug reported: I have no idea if I have filed this against the right package. It happens in both Firefox and Chrome, whatever provides their file selection dialog for uploads is apparently the problem, I don't know if that's gnome shell or something else. When I want to upload multiple files in a web browser, I can do that if I hit shift, and then click another file. But, that selects not just the two files that I clicked on, but every file in between them in the dialog (which is the expected behaviour when shift clicking in a file selection dialog). When I just want to select two files that are not displayed next to each other, I expect to be able to Ctrl+click on the files, and for them and only them to be selected. But, this doesn't happen, the second file does not get selected when I do that. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 10:08:32 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-08-04 (301 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (41 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- 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/2022155 Title: File selection dialog does not allow selecting multiple files using Ctrl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2022155/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011806] Re: [lunar] Snaps don't launch due to cgroup issue
I did a search through the KDE bug tracker, and it looks like someone reported the same root problem back in 2020: https://bugs.kde.org/show_bug.cgi?id=423756 ** Bug watch added: KDE Bug Tracking System #423756 https://bugs.kde.org/show_bug.cgi?id=423756 -- 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/2011806 Title: [lunar] Snaps don't launch due to cgroup issue To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2011806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011806] Re: [lunar] Snaps don't launch due to cgroup issue
I've filed https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6565 upstream to cover the gnome-shell problem. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6565 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6565 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6565 Importance: Unknown Status: Unknown -- 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/2011806 Title: [lunar] Snaps don't launch due to cgroup issue To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2011806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011806] Re: [lunar] Snaps don't launch due to cgroup issue
> So, I feel snapd tracker should somewhat be able to track that an app > changed its cgroup and move it back to what it belongs, but as discussed > in https://github.com/systemd/systemd/issues/26925 there's nothing > telling us that right now. There is no "snapd tracker". It's the "snap run" code that moves itself to a new cgroup before setting up the sandbox, dropping privileges, and executing the confined application. At that point, it has no permission to talk to systemd. It's basically working like "systemd-run --scope" would: it sets up the environment appropriately and then lets the app take over. -- 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/2011806 Title: [lunar] Snaps don't launch due to cgroup issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011806] Re: [lunar] Snaps don't launch due to cgroup issue
Another idea for how to synchronise the StartTransientUnit call without resorting to passing pipe file descriptors to the child: we could simply have the child_setup_func call kill(getpid(), SIGSTOP). The parent process can now do the cgroup move at its leisure, and then send a SIGCONT to the child to let it continue to the exec() call. -- 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/2011806 Title: [lunar] Snaps don't launch due to cgroup issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011806] Re: [lunar] Snaps don't launch due to cgroup issue
@Batuhan: it's different code, but looks to be the same type of problem: https://github.com/KDE/kio/blob/5bda428992cbd168fc1898661d80a089a8217449/src/gui/systemd/scopedprocessrunner.cpp#L13-L41 It's moving the process to a new cgroup after the application has started executing (so happens without any synchronisation with what the application is doing). -- 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/2011806 Title: [lunar] Snaps don't launch due to cgroup issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
I've created https://github.com/snapcore/snapd/pull/12627 as a proposed fix for the issue. -- 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/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
Okay. In a clean Lunar VM with glib 2.75.3 installed and ibus enabled as
described in the bug description, I could reproduce the input problems
in Firefox. I saw the following AppArmor denial in the dmesg logs:
[ +0.343553] audit: type=1400 audit(1678248386.012:62):
apparmor="DENIED" operation="connect" profile="snap.firefox.firefox"
name="/home/james/.cache/ibus/dbus-THbBfRNt" pid=2398 comm="pool-
firefox" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
I edited /var/lib/snapd/apparmor/profiles/snap.firefox.firefox and added
the following rule:
@{HOME}/.cache/ibus/dbus-* rw,
After reloading the policy with "apparmor_parser -r
.../snap.firefox.firefox", keyboard input worked again. So that confirms
my guess about the cause of the problem. This is something we can fix
via a snapd update.
Longer term, we should get these snaps using ibus's portal interface,
which is both more secure (i.e. suitable to allow in the desktop
interface) and should be immune to future changes of this type.
--
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/2008279
Title:
glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if
IBus is turned on
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
This seems like the most likely culprit: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3005 This basically means that code that would have created an abstract namespace socket in glib 2.74.x now creates a regular unix domain socket in 2.75.x. We have AppArmor rules in snapd's desktop-legacy interface granting access to the abstract namespace socket in $XDG_CACHE_HOME, but nothing for the equivalent regular socket: https://github.com/snapcore/snapd/blob/d5f47ca71fcd8a884072e75391a7e55d9ec9d145/interfaces/builtin/desktop_legacy.go#L142-L149 I still need to verify this is the actual cause, but if so it should be relatively simple to update snapd's AppArmor rules to allow access to this socket. -- 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/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
I think last time we had problems like this it was due to changes in the location of the socket for ibus's private D-Bus bus. Looking into the glib diffs for clues. -- 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/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987631] Re: Screencast only records one second
If gstreamer is fixed then any pipewire combination should work I think. -- 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/1987631 Title: Screencast only records one second To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987631] Re: Screencast only records one second
To clarify the gstreamer fix should be sufficient. The pipewire always- copy change I made allows for working around the bug but isn't required as long as you have the gstreamer fix. Fixes the bug in gstreamer: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/1c8244a19dbb4ebdf972a703b55d719f2b968056 Makes it possible to work around the gstreamer bug without updating gstreamer: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525c1ac946a915599c6bee813e88e8cee12 Note that gnome-shell applies the always-copy pipewire workaround based on gstreamer/pipewire version detection so this logic may need tweaking due to backports: https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/43.2/js/dbusServices/screencast/screencastService.js#L233-235 -- 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/1987631 Title: Screencast only records one second To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1578736] Re: /usr/lib/gvfs/gvfsd-smb-browse:6:raise:abort:talloc_abort:talloc_abort_unknown_value:talloc_chunk_from_ptr
i have also facing the same issue on my client's site: https://apkintl.com/tekken-5-apk/ -- 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/1578736 Title: /usr/lib/gvfs/gvfsd-smb- browse:6:raise:abort:talloc_abort:talloc_abort_unknown_value:talloc_chunk_from_ptr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1578736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724037] Re: Allow GNOME fractional scaling below 100%
I tried the suggestion in #13 to manually edit .config/monitors.xml without success, I do hope this can eventually be realised. -- 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/1724037 Title: Allow GNOME fractional scaling below 100% To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724037/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724037] Re: Allow GNOME fractional scaling below 100%
I am not certain why fractional scaling below 100% would cause any different performance issues than fractional scaling above 100%, but it is certainly something that I have wanted for a long time sometimes the fact that it would cause some blurring as the image would be scaled to contain more pixels than the display... is not a problem. Please do consider allowing this if it is possible, even if it is not directly exposed to the user on most distros, accessing it through gnome-tweaks or dconf would be fine. -- 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/1724037 Title: Allow GNOME fractional scaling below 100% To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724037/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983112] Re: Appstream does not install config file
** Attachment added: "scenario_3_installer.zip" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607336/+files/scenario_3_installer.zip -- 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/1983112 Title: Appstream does not install config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983112] Re: Appstream does not install config file
** Attachment added: "scenario_2_appstream.txt" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607337/+files/scenario_2_appstream.txt -- 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/1983112 Title: Appstream does not install config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983112] Re: Appstream does not install config file
** Attachment added: "scenario_2_installer.zip" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607335/+files/scenario_2_installer.zip -- 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/1983112 Title: Appstream does not install config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983112] Re: Appstream does not install config file
** Attachment added: "scenario_1_installer.zip" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607334/+files/scenario_1_installer.zip -- 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/1983112 Title: Appstream does not install config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983112] Re: Appstream does not install config file
Reuploading previous attachments after redacting sensitive information. Original comment copied below: Okay, I've gone down the rabbit hole with this one. It's possible this is 2 separate issues. I tested 3 scenarios: Scenario 1 - Performed a clean Ubuntu Server install (interactive), and installed ubuntu-desktop-minimal post-deployment. After rebooting, the 50appstream config is present, and I installed snap-store and gnome-software. Neither snap-store nor gnome-software showed any .deb packages. Only snaps. I tried re-installing appstream and forcing a refresh of the cache, but still no .deb packages shown. Nothing I have tried in this install has been able to fix the issue. Scenario 2 - I performed a clean install using our automated install image (/var/log/installer contents attached) WITHOUT our appstream config reinstall script that I shared previously. After deployment, ubuntu-desktop-minimal is already installed, and 50appstream config is MISSING (see attachment). Both snap-store and gnome-software only show snaps. No .deb packages. Next, I ran the appstream re-install script I shared previously and rebooted the machine. After the reboot, gnome-software correctly shows .deb packages. However, snap-store is still only showing snaps!!! Scenario 3 - I performed a clean install using our automated install image (/var/log/installer contents attached), this time including our appstream config reinstall script. After the deployment, 50appstream config is PRESENT. Both snap-store and gnome-software work correctly and show both snaps and .deb packages. The varying behaviour between all 3 has completely blown my mind. I really don't know what is the cause of the issue, and potentially this is even 2 separate issues, since in Scenario 1, neither snap-store nor gnome-software work correctly. -- 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/1983112 Title: Appstream does not install config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983112] Re: Appstream does not install config file
** Attachment removed: "installer logs for Scenario 1" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607134/+files/scenario_1_installer.zip ** Attachment removed: "scenario_2_installer.zip" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607135/+files/scenario_2_installer.zip ** Attachment removed: "scenario_2_appstream.txt" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607136/+files/scenario_2_appstream.txt ** Attachment removed: "scenario_3_installer.zip" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607137/+files/scenario_3_installer.zip -- 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/1983112 Title: Appstream does not install config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983112] Re: Appstream does not install config file
** Attachment added: "scenario_2_appstream.txt" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607136/+files/scenario_2_appstream.txt -- 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/1983112 Title: Appstream does not install config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983112] Re: Appstream does not install config file
** Attachment added: "scenario_3_installer.zip" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607137/+files/scenario_3_installer.zip -- 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/1983112 Title: Appstream does not install config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983112] Re: Appstream does not install config file
** Attachment added: "scenario_2_installer.zip" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607135/+files/scenario_2_installer.zip -- 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/1983112 Title: Appstream does not install config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983112] Re: Appstream does not install config file
Okay, I've gone down the rabbit hole with this one. It's possible this is 2 separate issues. I tested 3 scenarios: Scenario 1 - Performed a clean Ubuntu Server install (interactive), and installed ubuntu-desktop-minimal post-deployment. After rebooting, the 50appstream config is present, and I installed snap-store and gnome-software. Neither snap-store nor gnome-software showed any .deb packages. Only snaps. I tried re-installing appstream and forcing a refresh of the cache, but still no .deb packages shown. Nothing I have tried in this install has been able to fix the issue. Scenario 2 - I performed a clean install using our automated install image (/var/log/installer contents attached) WITHOUT our appstream config reinstall script that I shared previously. After deployment, ubuntu-desktop-minimal is already installed, and 50appstream config is MISSING (see attachment). Both snap-store and gnome-software only show snaps. No .deb packages. Next, I ran the appstream re-install script I shared previously and rebooted the machine. After the reboot, gnome-software correctly shows .deb packages. However, snap-store is still only showing snaps!!! Scenario 3 - I performed a clean install using our automated install image (/var/log/installer contents attached), this time including our appstream config reinstall script. After the deployment, 50appstream config is PRESENT. Both snap-store and gnome-software work correctly and show both snaps and .deb packages. The varying behaviour between all 3 has completely blown my mind. I really don't know what is the cause of the issue, and potentially this is even 2 separate issues, since in Scenario 1, neither snap-store nor gnome-software work correctly. ** Attachment added: "installer logs for Scenario 1" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5607134/+files/scenario_1_installer.zip -- 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/1983112 Title: Appstream does not install config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1983112] Re: Appstream does not install config file
As far as I can tell, this only happens during deployment when installing the ubuntu-desktop-minimal (haven't tried with the full-fat ubuntu-desktop package) via the new Ubuntu automated server install method. So probably is an Ubuntu-specific issue. I will try to do more testing and narrow down the exact combination of events causing this. On 01/08/2022 10:23, Matthias Klumpp wrote: > Very odd... There is nothing special about this config file (it's installed > like every other) and this works absolutely fine on Debian and even my Ubuntu > VM. > So, something very odd and possibly uBUNTU-SPECIFIC is going on here... > -- James Paton-Smith Linux Support Officer EBI Systems Application Group, South Building, Studio 12 European Bioinformatics Institute (EMBL-EBI) Wellcome Trust Genome Campus Hinxton Cambridge CB10 1SD +44 (0)1223 494308 -- 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/1983112 Title: Appstream does not install config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983112] Re: Appstream does not install config file
No, I did not remove the config file manually. We're actually using the attached bash script as a late-command in the autoinstall as a workaround to fix the issue. Without this script, the snap-store simply refuses to show .deb packages from the repos. ** Attachment added: "appstream_config_reinstall" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+attachment/5606252/+files/appstream_fix.sh -- 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/1983112 Title: Appstream does not install config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983112] [NEW] Appstream does not install config file
Public bug reported: After performing an Ubuntu automated server install, and installing the ubuntu-desktop-minimal package (which includes appstream as a dependency) then the snap-store, the snap-store will fail to display search results for .deb packages in the Ubuntu apt repositories. This is due to a missing config file (/etc/apt/apt.conf.d/50appstream) which is supposed to be installed as part of the appstream package. The issue can be fixed by re-installing appstream with the following command-line: apt-get -y install --reinstall -o Dpkg::Options::="--force-confmiss" appstream ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 15:25:44 2022 InstallationDate: Installed on 2022-07-27 (1 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: appstream (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images wayland-session -- 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/1983112 Title: Appstream does not install config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1983112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969140] Re: Window minimize animation flickers and appears in the wrong place in Xorg sessions
My findings so far, system configuration attached: - Occurs with any number of windows open. - The minimise animation seems more broken than the restore animation. - DING enabled/disabled does not affect the animation behaviour. - I agree with the findings of comment #10, as the minimise animation shows multiple flickering frames where a thumbnail of the minimising window can be seen shrinking and moving to the top right hand corner of the screen. The expected minimising animation, where the window shrinks down into the dock icon (set to the bottom of the screen on my machine) still occurs while this is happening. - The restore animation sometimes (but not always) displays a frame where the errant window thumbnail can be seen above and to the left of the window position, presumably the reverse of the errant 'shrink to top left' minimise animation, but for some reason with less visible errant frames and occurs less consistently. ** Attachment added: "configuration" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1969140/+attachment/5601046/+files/Screenshot%20from%202022-07-03%2016-59-46.png -- 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/1969140 Title: Window minimize animation flickers and appears in the wrong place in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1969140/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1974212] [NEW] memory leak in gnome-shell
Public bug reported: Gnome-shell slowly grows in memory over time. The mouse will start to stutter and keyboard input repeats the same character many times. After a day or two, I have to reboot or my desktop environment crashes. I have disabled all extensions except for the Ubuntu default ones. I'm willing to help debug if needed. Heaptrack from a recent session: https://paste.ubuntu.com/p/Gj4nVPG3zx/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 19 10:37:46 2022 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-21 (727 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2021-11-19 (181 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy wayland-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/1974212 Title: memory leak in gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1974212/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
> Is there any option to do this via portals - ie can evince use > org.freedesktop.portal.OpenURI to open the URI? Would then this > allow to avoid going via xdg-open? Evince is using g_app_info_launch_default_for_uri(), which can use the portal interface: https://gitlab.gnome.org/GNOME/evince/-/blob/main/shell/ev- window.c#L6775-6778 However, it only does this as a fallback if no desktop file supports the URI. This is intended to allow a confined app to handle some file types within the sandbox before falling back to portals for everything else. In the case of Evince running on the host system and seeing all the desktop files in /usr/share/applications and other locations, it likely won't ever call the portal API. It'd be possible to code in explicit portal API calls, but it isn't something that Evince packaged as a flatpak or snap would need. So it might end up as a distro patch we'd be on the hook to maintain forever. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960972] Re: All snap applications missing from gnome-search after update
Downgrading snapd to the previous version 2.53+21.10ubuntu1 resolves the issue. As such this may actually be a snapd issue, or something involving both communications between the two applications. Neither version of snapd logs any errors. -- 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/1960972 Title: All snap applications missing from gnome-search after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960972/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960972] [NEW] All snap applications missing from gnome-search after update
Public bug reported: After this "upgrade", snapd:amd64 2.53+21.10ubuntu1 2.54.2+21.10ubuntu1 (Some video drivers were upgraded at the same time, but this doesn't seem relevant.) ...all snap applications have disappeared from gnome-shell search. All snaps are still installed and can be executed with "snap run app". All applications work correctly when launched this way, except that they will be missing their dock icons showing the "gears"/missing icon indicator. Application icons are also missing in the Ubuntu Software Center. Reinstalling the snap applications affected does not help, including "snap remove --purge && snap install". Non-snap applications are unaffected. To reproduce, press super key and type the name of any installed in /snap. No snap applications appear but normal applications and files will be listed as usual. Tried to uninstall shell extensions removed and reboot. Nothing improved. --- gnome-shell logs complain of the following: Feb 15 15:26:56 gnome-shell[3135]: GNOME Shell started at Tue Feb 15 2022 15:26:53 GMT-0800 (PST) Feb 15 15:26:56 gnome-shell[3135]: Registering session with GDM Feb 15 15:27:03 ubuntu-appindicat...@ubuntu.com[3135]: Slack1, Impossible to lookup icon for 'Slack1_2-panel' in path /run/user/1000/.org.chromium.Chromium.cgr> Feb 15 15:27:03 ubuntu-appindicat...@ubuntu.com[3135]: unable to update icon for Slack1 Feb 15 15:27:09 gnome-shell[3135]: Failed to set the markup of the actor 'ClutterText': Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity — escape ampersand as Feb 15 15:27:09 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:27:09 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:27:10 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:27:10 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:27:13 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Feb 15 15:27:13 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:29:06 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:29:06 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:29:33 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:29:33 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:29:34 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:29:34 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:29:34 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:29:34 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:35:17 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:35:22 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:35:22 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:35:25 gnome-shell[3135]: Timelines with detached actors are not supported --- Description:Ubuntu 21.10 Release:21.10 gnome-shell: Installed:
[Bug 1908429] Re: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal conn
For info. The bug also means that the systemd journal is growing at an extremely fast rate. Double whammy. All these files by default reside in the root file system. Which is usually created quite small. -- 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/1908429 Title: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. The offending callback was SourceFunc(). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908429/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1698083] Re: Maximize vertically/horizontally doesn't work (in some apps)
Since this bug was logged 5 years ago, and is still present... in fact it is now on a shortlist of 2 bugs that will stop my adoption of Wayland, I thought I would confirm that it is still present in Ubuntu 22.04 (development branch), at the time of writing, with Gnome 41.1. -- 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/1698083 Title: Maximize vertically/horizontally doesn't work (in some apps) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698083/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1931989] [NEW] Day of week not displaying on drop-down calendar from top bar.
Public bug reported: This is not caused by the custom theme, as this still occurs with a dconf reset to the default theme. I am not sure if this issue is present with Wayland enabled as well. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 15 11:30:14 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-13 (2 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2021-06-15 11-35-44.png" https://bugs.launchpad.net/bugs/1931989/+attachment/5504734/+files/Screenshot%20from%202021-06-15%2011-35-44.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/1931989 Title: Day of week not displaying on drop-down calendar from top bar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1931989/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
Another user affected on 20.04. Happened to me after resuming from sleep. Alt+F2: R made it go away for me as well. -- 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/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1824874/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1913453] Re: gnome-shell freeze
There was indeed a directory named extensions, which I have deleted. I have attached the last crash, which took a long time to trigger. I did not deliberately suspend and the laptop was charging so it should not have slept in the 3 days it has been running. The crash occurred shortly after detaching the laptop from a dock. judging by it's behaviour it thought that it was still using multiple displays (monitors) despite being detached. Unfortunately this time I forgot to put top running in the foreground of the screen when i detached the computer, so I cannot confirm any process usage values at the time of the crash, I will try and get this. ** Attachment added: "cleanprevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913453/+attachment/5470592/+files/cleanprevboot.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/1913453 Title: gnome-shell freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913453/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1913453] Re: gnome-shell freeze
Not sure if it's helpful but here's another crash from today. Pretty sure network-manager crashed which has happened before, as i lost connection to my SSH'd devices and could not connect back to my AP. Complete freeze happened promptly after. This happened after using a usb-hub switch. ** Attachment added: "prevboot3.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913453/+attachment/5466761/+files/prevboot3.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/1913453 Title: gnome-shell freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913453/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1913453] Re: gnome-shell freeze
settings.txt ** Attachment added: "settings.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913453/+attachment/5466688/+files/settings.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/1913453 Title: gnome-shell freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913453/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1913453] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1913453/+attachment/5466687/+files/monitors.xml.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/1913453 Title: gnome-shell freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913453/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1913453] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1913453/+attachment/5466685/+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/1913453 Title: gnome-shell freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913453/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1913453] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1913453/+attachment/5466686/+files/ShellJournal.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/1913453 Title: gnome-shell freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913453/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1913453] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1913453/+attachment/5466683/+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/1913453 Title: gnome-shell freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913453/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1913453] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1913453/+attachment/5466684/+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/1913453 Title: gnome-shell freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913453/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1913453] Re: gnome-shell freeze
apport information ** Tags added: apport-collected ** Description changed: System Description: Ubuntu 20.04.1 LTS Release: 20.04 Description: Plugging in USB hub with peripherals while system is running causes gradual lag of a visual response, until freezing. usually takes < 1 min. Only work around is to sleep system between plugging in hub. I thought I fixed it by change DM but the issue has persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 14:27:12 2021 DistUpgraded: 2020-04-28 14:42:33,856 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2018-12-25 (763 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 2324AS7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=957184f1-8feb-4ca9-ac97-3fb70937b4ac ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-28 (274 days ago) dmi.bios.date: 04/11/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324AS7 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB2WW(2.72):bd04/11/2018:svnLENOVO:pn2324AS7:pvrThinkPadX230:rvnLENOVO:rn2324AS7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324AS7 dmi.product.sku: LENOVO_MT_2324 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~ppa1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue Nov 24 16:32:27 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2018-12-25 (792 days ago) + InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) + Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 + RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 + Tags: third-party-packages focal wayland-session + Uname: Linux 5.4.0-65-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-04-28 (302 days ago) + UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo wireshark + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1913453/+attachment/5466682/+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/1913453 Title: gnome-shell freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913453/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1915993] [NEW] Window close button appears botched
Public bug reported: I'm using the gedit snap, version 3.36.2+git3.8c9da67ab, rev 605 on Ubuntu MATE 20.04. The window control for closing the window looks botched, almost as though it were smudged. See attached picture. ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot at 2021-02-17 22-38-53.png" https://bugs.launchpad.net/bugs/1915993/+attachment/5464695/+files/Screenshot%20at%202021-02-17%2022-38-53.png ** Description changed: - I'm using the gedit snap, version 3.36.2+git3.8c9da67ab, rev 603 on + I'm using the gedit snap, version 3.36.2+git3.8c9da67ab, rev 605 on Ubuntu MATE 20.04. The window control for closing the window looks botched, almost as though it were smudged. See attached picture. -- 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/1915993 Title: Window close button appears botched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1915993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1903777] Re: Screen resolution falls back to default (low res) under Ubuntu Budgie 20.10 (Intel/Nvidia)
Thanks, I will do ASAP. My computer is currently in a shipping container pending delivery Jan 2021 :/ On Wed, 11 Nov 2020, at 2:58 AM, Daniel van Vugt wrote: > Please run the following commands: > > xrandr --verbose > xrandr.txt > lspci -kv > lspci.txt > journalctl -b0 > journal.txt > grep . /sys/class/drm/*/modes > drmmodes.txt > > and then attach the resulting text files here. > > > ** Changed in: mutter (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1903777 > > Title: > Screen resolution falls back to default (low res) under Ubuntu Budgie > 20.10 (Intel/Nvidia) > > Status in mutter package in Ubuntu: > Incomplete > > Bug description: > Fresh install of Budgie 20.10. Things work normally, but after a reboot the > screen resolution goes down to something like 1024x768 (from 1440p) and won't > go back. Can't be selected in GUI, grayed out. Issuing a "sudo systemctl > restart display-manager" will get things back to 1440p, but kills all my > windows etc. > > Using the latest NVIDIA driver, although this also happened under the > previous one. > > Description: Ubuntu 20.10 > Release: 20.10 > > > x@x:~$ apt-cache policy libmutter-7-0 > libmutter-7-0: > Installed: 3.38.1-1ubuntu1 > Candidate: 3.38.1-1ubuntu1 > Version table: >*** 3.38.1-1ubuntu1 500 > 500 http://gb.archive.ubuntu.com/ubuntu groovy/main amd64 Packages > 100 /var/lib/dpkg/status > > ProblemType: Bug > DistroRelease: Ubuntu 20.10 > Package: libmutter-7-0 3.38.1-1ubuntu1 > ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 > Uname: Linux 5.8.0-26-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.11-0ubuntu50 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: Budgie:GNOME > Date: Tue Nov 10 21:53:32 2020 > InstallationDate: Installed on 2020-10-23 (18 days ago) > InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Release amd64 > (20201022) > SourcePackage: mutter > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903777/+subscriptions > -- 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/1903777 Title: Screen resolution falls back to default (low res) under Ubuntu Budgie 20.10 (Intel/Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903777/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903910] Re: Mouse settings ignored when plugging in a new mouse
*** This bug is a duplicate of bug 1899509 *** https://bugs.launchpad.net/bugs/1899509 > @Ben: Can you please install the mutter packages from this PPA I can confirm that the suggested package works - I've tried with multiple mice and all keep adopt the expected settings when I unplug and plug them in again. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1903910 Title: Mouse settings ignored when plugging in a new mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1903910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903910] Re: Primary mouse button setting reverts to default
*** This bug is a duplicate of bug 1899509 *** https://bugs.launchpad.net/bugs/1899509 I can also confirm that gsettings shows the correct value when disconnecting the mouse, but when the mouse is reconnected, the setting is reverted silently (gsettings and gnome-control-center show the wrong value). gsettings and gnome-control-center are in sync, but both wrong. Steps to reproduce: 1) Plug in two USB mice. 2) Set Primary Button: Right. 3) Confirm - both buttons work as expected on both mice, gsettings shows "left-handed true" 4) Unplug one mouse. 5) The remaining mouse works fine, gsettings and gnome-control-center both show the right setting. 6) Plug the second mouse in again. 7) gsettings and gnome-control-center still show the same setting, however the two mice have different behaviour. Summary: Mouse settings are not applied to a new mouse. ** Summary changed: - Primary mouse button setting reverts to default + Mouse settings ignored when plugging in a new mouse -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1903910 Title: Mouse settings ignored when plugging in a new mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1903910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903910] Re: Primary mouse button setting reverts to default
*** This bug is a duplicate of bug 1899509 *** https://bugs.launchpad.net/bugs/1899509 After a bit more debug, it appears the problem occurs when any external mouse is disconnected and reconnected (ruling out the USB hub and switch as a factor). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1903910 Title: Primary mouse button setting reverts to default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1903910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903910] [NEW] Primary mouse button setting reverts to default
Public bug reported: I'm running Ubuntu 20.04 LTS on a Dell XPS 13 laptop with an external mouse and keyboard connected via a USB switch.* I've set the mouse to left-handed operation (i.e. primary mouse button = right) using gnome-control-center; this works fine for a while and shows the expected setting on the command line: > gsettings get org.gnome.desktop.peripherals.mouse left-handed true ...however if I leave the laptop for a while and come back to it, the mouse has reverted back to right-handed operation. The really curious thing is that gnome-control-center still shows the expected setting (primary mouse button = right). To set the mouse as desired, I have to change the primary mouse button to left and then back to right in gnome-control-center. It's almost as if gsettings is reverting the mouse configuration and becoming out of sync with gnome-control-center. *The laptop is connected to a monitor using a single USB-C cable; the monitor acts as a USB hub and is connected to a USB switch such that I can use a single keyboard and mouse with two machines. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 19:51:39 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-08-04 (99 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-09-22 (50 days ago) ** Affects: gnome-control-center (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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1903910 Title: Primary mouse button setting reverts to default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1903910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1903777] [NEW] Screen resolution falls back to default (low res) under Ubuntu Budgie 20.10 (Intel/Nvidia)
Public bug reported: Fresh install of Budgie 20.10. Things work normally, but after a reboot the screen resolution goes down to something like 1024x768 (from 1440p) and won't go back. Can't be selected in GUI, grayed out. Issuing a "sudo systemctl restart display-manager" will get things back to 1440p, but kills all my windows etc. Using the latest NVIDIA driver, although this also happened under the previous one. Description:Ubuntu 20.10 Release:20.10 x@x:~$ apt-cache policy libmutter-7-0 libmutter-7-0: Installed: 3.38.1-1ubuntu1 Candidate: 3.38.1-1ubuntu1 Version table: *** 3.38.1-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libmutter-7-0 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Nov 10 21:53:32 2020 InstallationDate: Installed on 2020-10-23 (18 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1903777 Title: Screen resolution falls back to default (low res) under Ubuntu Budgie 20.10 (Intel/Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903777/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1901965] [NEW] Natural scroll setting not honoured when mouse is plugged in
Public bug reported: If I go into the mouse settings and enable natural scrolling for my mouses scroll wheel, this works. If I unplug the mouse, and then plug it back in, the natural scroll stops working, however, in the mouse settings dialog, it still appears to be on. To actually turn it back on, I have to turn the setting off, and then back on again. This happens every time I unplug the mouse, and plug it back in. I first noticed this about a month ago on Ubuntu 20.04 after doing a software update. When I upgraded to Ubuntu 20.10, the bug was still present. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1901965 Title: Natural scroll setting not honoured when mouse is plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1901965/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
I've updated the description with the SRU bug template. I think this includes all the relevant info? ** Description changed: - I'm trying to run chromium installed via snap in Ubuntu 20.10 when - running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: + [Impact] - > chromium + * Users who select the Wayland session on Ubuntu 20.10 cannot run snap +confined X11 applications, due to gnome-shell no longer listening on an +abstract socket for connections. + + * The fix, which has been accepted into upstream's gnome-3-38 branch +reverts the change removing the abstract socket, and fixes the bug that +prompted it's removal. + + [Test Case] + + * Start with a stock Ubuntu 20.10 desktop install. + + * At the GDM login screen, after selecting your user account use the gear +icon to select the "Ubuntu on Wayland" session, and log in. + + * Ensure Chromium is installed by running "sudo snap install chromium". + + * Try to run "chromium" from the terminal. Without the fix, it will fail +with the error "Unable to open X display". With the fix applied, it +will launch as normal. + + [Regression Potential] + + * The patch modifies the logic gnome-shell uses to launch Xwayland. So +there is a potential that the change could break X11 application +support on the Wayland session. + + * The default configuration for gnome-shell is to launch Xwayland on +session start, so it should be immediately obvious if there are +problems. + + * In addition to checking snapped X11 apps like Chromium, verify that a +few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc). + + [Other Info] + + * Running "ss -xlp | grep Xwayland" should show that it is listening on +both "/tmp/.X11-unix/X0" (the regular unix domain socket) and +"@/tmp/.X11-unix/X0" (the abstract socket). + + --- + I'm trying to run chromium installed via snap in Ubuntu 20.10 when running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: + + > chromium [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to open X display. I am able to run Firefox just fine (assuming that Firefox still runs on xwayland) and also Intellij snap works fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:45:16 2020 InstallationDate: Installed on 2016-09-05 (1480 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Snap: chromium 85.0.4183.121 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: [Impact] - * Users who select the Wayland session on Ubuntu 20.10 cannot run snap -confined X11 applications, due to gnome-shell no longer listening on an -abstract socket for connections. + * Users who select the Wayland session on Ubuntu 20.10 cannot run snap + confined X11 applications, due to gnome-shell no longer listening on an + abstract socket for connections. - * The fix, which has been accepted into upstream's gnome-3-38 branch -reverts the change removing the abstract socket, and fixes the bug that -prompted it's removal. + * The fix, which has been accepted into upstream's gnome-3-38 branch + reverts the change removing the abstract socket, and fixes the bug that + prompted it's removal: + +https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 [Test Case] - * Start with a stock Ubuntu 20.10 desktop install. + * Start with a stock Ubuntu 20.10 desktop install. - * At the GDM login screen, after selecting your user account use the gear -icon to select the "Ubuntu on Wayland" session, and log in. + * At the GDM login screen, after selecting your user account use the gear + icon to select the "Ubuntu on Wayland" session, and log in. - * Ensure Chromium is installed by running "sudo snap install chromium". + * Ensure Chromium is installed by running "sudo snap install chromium". - * Try to run "chromium" from the terminal. Without the fix, it will fail -with the error "Unable to open X display". With the fix applied, it -will launch as normal. + * Try to run "chromium" from the terminal. Without the fix, it will fail + with the error "Unable to open X display". With the fix applied, it + will launch as normal. [Regression Potential] - * The patch modifies the logic gnome-shell uses to launch Xwayland. So -there is a potential that the change could break X11 application -support on the Wayland session. + * The patch modifies the logic gnome-shell uses to launch Xwayland. So + there is a potential that the change could break X11
[Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
I had a go at fixing this in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 -- taking the patches from that MR and applying them to the Groovy mutter source package gave me a Wayland session that supported X11 snaps again. It is probably worth waiting for a review from upstream before going further. I've done the testing they asked for with the "autostart- xwayland" feature enabled, so hopefully that will come soon. -- 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/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872159] Re: Boot animation never finishes when external monitors (or just more than one) are connected
I ran into this problem with a new install of 20.04 on a Dell Optiplex 5060. This system has integrated Display Ports.Hangs at boot with Ubuntu spinning for hours. My configuration has a single monitor attached via Display port/HDMI cable and DVI adapter to monitor DVI input. Two workarounds mentioned here worked for me: 1) boot with monitor cable unplugged and then plug cable in to see login screen 2) remove "splash quiet" in /etc/default/grub, then boot to login screen -- 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/1872159 Title: Boot animation never finishes when external monitors (or just more than one) are connected To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1872159/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897224] Re: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display
I've filed https://gitlab.gnome.org/GNOME/mutter/-/issues/1454 upstream about this regression. ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1454 https://gitlab.gnome.org/GNOME/mutter/-/issues/1454 -- 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/1897224 Title: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897224] Re: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display
Looking at the reasoning behind that change, Mutter introduced lazy initialisation of Xwayland: binding the two sockets, and starting Xwayland when someone connected to the abstract namespace socket. Flatpak apps apparently can't speak to the abstract namespace socket, so would hang forever when started since the connection to the non-abstract /tmp/.X11-unix socket was never accepted. Rather than fixing the initialisation logic to start Xwayland on connect to either socket, they dropped the abstract namespace socket. I'll talk to the snapd folks about it, but this sounds like it should be dealt with on the Mutter side. ** Changed in: mutter (Ubuntu) Status: Invalid => Confirmed -- 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/1897224 Title: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1897224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897224] Re: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1424 is definitely the culprit here. Snaps depend on access to the abstract namespace socket to function correctly. Inside the sandboxes, snaps see a private /tmp that is under their complete control. So there is no /tmp/.X11-unix directory there. They can see the abstract namespace socket though, which the client libraries will use automatically. -- 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/1897224 Title: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1897224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1894234] Re: Bluetooth not working with Gnome in Groovy (20.10)
Sorry, I should have mentioned, this is while testing Groovy, as of the 4th September. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1894234 Title: Bluetooth not working with Gnome in Groovy (20.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1894234/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1894234] [NEW] Bluetooth not working with Gnome in Groovy (20.10)
Public bug reported: Having plugged in a USB bluetooth dongle, the gnome-bluetooth settiogs report that I have no bluetooth adapter, and I should plug one in. At the same time, I can see the bluetooth adapter with hciconfig, and in fact, I can pair with remote bluetooth devices using a 3rd party bluetooth manager (blueman). Obviously this is not ideal, as it is not fully integrated with gnome, sound devices are not fully available etc.. I'm not sure what else I can provide, but:- # hciconfig -a hci0: Type: Primary Bus: USB BD Address: 24:4B:FE:3A:21:65 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:1117 acl:0 sco:0 events:72 errors:0 TX bytes:4973 acl:0 sco:0 commands:72 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'morpheous' Class: 0x1c0104 Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0xb LMP Version: 5.1 (0xa) Subversion: 0x8761 Manufacturer: Realtek Semiconductor Corporation (93) root@morpheous:~# When I got to settings, it tells me I have no bluetooth devices plugged in! ** Affects: gnome-bluetooth (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth gnome groovy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1894234 Title: Bluetooth not working with Gnome in Groovy (20.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1894234/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1839380] Re: Nautilus freezes when restoring files and a copy already exists
When I opened my laptop today the delete key stuck. Since the active window was displaying the directory of my home folder EVERY SINGLE FILE AND DIRECTORY was deleted. Now they are all in the trash but whenever I try to recover from trash it hangs and the only way out is to power off the laptop. I would appreciate some idea of how I can recover all of my files from trash. -- 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/1839380 Title: Nautilus freezes when restoring files and a copy already exists To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1839380/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1889295] Re: [GM965] dual monitor display not working after login
Daniel, As requested, I enabled Wayland and logged in with 'Ubuntu on Wayland'. The second monitor is now working. Thank you. I am very impressed with the quick turn around and support. Jim Battis On 7/30/20 10:11 PM, Daniel van Vugt wrote: > Thanks. It looks like Xorg is the cause of this problem and Wayland > (used on the login screen) works better. Please try selecting 'Ubuntu on > Wayland' on the login screen (button at the bottom right) before > entering your password and tell us if that improves the situation. > > > ** Summary changed: > > - dual monitor display not working after login > + [GM965] dual monitor display not working after login > -- 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/1889295 Title: [GM965] dual monitor display not working after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889295/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1889295] Re: dual monitor display not working after login
** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889295/+attachment/5397190/+files/lspcik.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/1889295 Title: dual monitor display not working after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889295/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1889295] Re: dual monitor display not working after login
** Attachment added: "xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889295/+attachment/5397189/+files/xrandr.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/1889295 Title: dual monitor display not working after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889295/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1889295] Re: dual monitor display not working after login
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889295/+attachment/5397188/+files/journal.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/1889295 Title: dual monitor display not working after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889295/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1889295] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1889295/+attachment/5396952/+files/monitors.xml.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/1889295 Title: dual monitor display not working after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889295/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1889295] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1889295/+attachment/5396950/+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/1889295 Title: dual monitor display not working after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889295/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1889295] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1889295/+attachment/5396949/+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/1889295 Title: dual monitor display not working after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889295/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1889295] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1889295/+attachment/5396951/+files/ShellJournal.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/1889295 Title: dual monitor display not working after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889295/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1889295] Re: dual monitor display not working after login
apport information ** Tags added: apport-collected ** Description changed: Results from a clean install of 20.04 with a forced update. When my system boots, the system comes up in dual monitor status (separated monitors). Once I log into my account the system reverts to a single monitor mode and the second monitor goes blank. If I attempt to change the display to dual monitors, both monitors are shown and defined correctly in the setup window (Built-in Laptop Monitor and HP 24"). However, once I click on apply, the system tries to reset to dual monitor, I would say several times, but fails and second monitor says that no signal is detected and to check the connection or cable. However, if I run Ubuntu (older version) from a thumb drive I have no problem with the dual monitor. I believe I am running the default video driver. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.4 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-07-25 (3 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + Package: gnome-shell 3.36.1-5ubuntu1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 + RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 + Tags: focal + Uname: Linux 5.4.0-42-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1889295/+attachment/5396948/+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/1889295 Title: dual monitor display not working after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889295/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1889295] [NEW] dual monitor display not working after login
Public bug reported: Results from a clean install of 20.04 with a forced update. When my system boots, the system comes up in dual monitor status (separated monitors). Once I log into my account the system reverts to a single monitor mode and the second monitor goes blank. If I attempt to change the display to dual monitors, both monitors are shown and defined correctly in the setup window (Built-in Laptop Monitor and HP 24"). However, once I click on apply, the system tries to reset to dual monitor, I would say several times, but fails and second monitor says that no signal is detected and to check the connection or cable. However, if I run Ubuntu (older version) from a thumb drive I have no problem with the dual monitor. I believe I am running the default video driver. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1889295 Title: dual monitor display not working after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1889295/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1884049] Re: gnome-shell is taking more and more CPU over time, UI becomes slowly unusable
*** This bug is a duplicate of bug 1880405 *** https://bugs.launchpad.net/bugs/1880405 Daniel, how does one produce the shell journal log? I'm afraid the problem resurfaced even after I removed all the extensions. -- 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/1884049 Title: gnome-shell is taking more and more CPU over time, UI becomes slowly unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1884049/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
@Rod Thanx again for your outstanding bug fix. I didn't try Bestweb via the cli. I used software updater. And the problem with the Bestweb ISP was on my end. My setup got mangled and was trying to connect to yahoo. I got it sorted out and it works perfectly, although the first time I connected, evolution reported that the SSL cert was not trusted. I've never seen that before. I have accepted it temporarily and when I feel comfortable with it, I'll accept it permanently. Oh, and thanx for posting the wiki regarding enabling the proposed updates. There is a lot of good info there. @Joe Buc, you might want to try using tamille1's instructions. It worked for me. Just remember to disable the proposed updates when you are done. -- 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/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1884049] Re: gnome-shell is taking more and more CPU over time, UI becomes slowly unusable
*** This bug is a duplicate of bug 1880405 *** https://bugs.launchpad.net/bugs/1880405 Agreed, on both :) I'll submit a suggestion there. Thank you Daniel -- 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/1884049 Title: gnome-shell is taking more and more CPU over time, UI becomes slowly unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1884049/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1884049] Re: gnome-shell is taking more and more CPU over time, UI becomes slowly unusable
*** This bug is a duplicate of bug 1880405 *** https://bugs.launchpad.net/bugs/1880405 This seems to have been the case. So far so good. If it changes I'll act accordingly. How about gnome-shell issuing an alert to the user that something nasty is happening in the background without them knowing about it? -- 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/1884049 Title: gnome-shell is taking more and more CPU over time, UI becomes slowly unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1884049/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
Thankyou tamille1 I followed you instructions and added the repository to 16.04lts. Evolution now downloads email from yahoo:993. I had to deselect 'Pre-released updates' from the developer options in update manager to get rid of the extra updates, but it worked. I couldn't find the repository in my list to remove it. I know that I added it, but it just wasn't showing. I am still having trouble downloading email from one of my ISP's: Bestweb.net. It might be a transient issue on their end. I'll give it a few days. -- 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/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled
Daniel, I apologise. We have been talking about different apps. I have been referring to the browser plugin that talks to https://extensions.gnome.org/. This is because it was the first thing I spotted when I searched on the net. I realise that what you have been talking about the is a standalone app that is accessible via the applications panel or the activities search box. Yes, the standalone app works perfectly and is packaged with the shell. The browser plugin does not. I have only tested the Firefox version though. The Chrome one might be better. Thank you for being patient Roger -- 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/1872796 Title: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872796/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled
I am running Ubuntu Focal 20.04. The gnome-shell version is 3.36.2-1ubuntu1-20.04.1. The desktop icons version is 20.04.0-2-1ubuntu1-20.04.1. The app does not work. I believe the app is designed to work on per user extensions only. The desktop icon extension is installed as a system extension in /usr/share/gnome-shell/extensions. See the review by akram87 on the page https://extensions.gnome.org/extension/1465/desktop-icons/ But that is not the point. All I am trying to achieve is to gather information about the impact the ubuntu version of the extension has on the desktop rendering. The easiest way for the user to do this is by issuing one simple command. sudo mv /usr/share/gnome-shell/extensions/desktop-icons@csoriano something-else If I am missing something here please accept my apologies. -- 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/1872796 Title: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872796/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled
The Extensions app does not appear to work fro the csoriano version of desktop icons. It thinks that it is the rastersoft fork. -- 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/1872796 Title: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872796/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery
If you are experiencing this bug. Try the following. if the directory "/usr/share/gnome-shell/extensions/desktop- icons@csoriano" rename it to something else. Then restart the desktop (logout then login). Please report the results of this test back here. I am trying to correlate information on the part this extension is playing in various desktop rendering glitches. -- 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/1832812 Title: Locking and unlocking the screen is slow and stuttery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832812/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled
If you are experiencing this bug. Try the following. if the directory "/usr/share/gnome-shell/extensions/desktop- icons@csoriano" rename it to something else. Then restart the desktop (logout then login). Please report the results of this test back here. I am trying to correlate information on the part this extension is playing in various desktop rendering glitches. -- 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/1872796 Title: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872796/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1867585] Re: CPU spikes caused by saving PDF to Desktop
If you are experiencing this bug. Try the following. if the directory "/usr/share/gnome-shell/extensions/desktop- icons@csoriano" rename it to something else. Then restart the desktop (logout then login). Please report the results of this test back here. I am trying to correlate information on the part this extension is playing in various desktop rendering glitches. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1867585 Title: CPU spikes caused by saving PDF to Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1867585/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
