[Bug 1965323] Re: Wayland: overview hotspot is not recognised if cursor slides to it along top of screen on RTL
** Tags removed: lunar ** Tags added: plucky -- 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/1965323 Title: Wayland: overview hotspot is not recognised if cursor slides to it along top of screen on RTL To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1965323/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965323] Re: Wayland: overview hotspot is not recognised if cursor slides to it along top of screen on RTL
This bug still exists on current Gnome in ubuntu 25.04. Any news regarding this bug? The issue seems small, but it blocks me from moving to wayland as the hotspot interaction is very common and important. -- 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/1965323 Title: Wayland: overview hotspot is not recognised if cursor slides to it along top of screen on RTL To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1965323/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 428884] Re: gnome-screensaver-command --poke no longer inhibits screensaver
** Changed in: gnome-screensaver (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/428884 Title: gnome-screensaver-command --poke no longer inhibits screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/428884/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2097232] [NEW] Wireguard enabled without internet access
Public bug reported: When enabling Wireguard VPN created through the new Import from file... in Network Settings, the config seems complete but no internet access is available. My settings work on the Wireguard Android app (i.e. I can access the remote network) from the same network on which I am trying to set up the client. I have checked that the firewall on my client does not block the port. Other members of the community have experienced the same issue: https://www.reddit.com/r/Ubiquiti/comments/1ewan95/wireguard_vpn_setup_on_ubuntu_2404/ https://askubuntu.com/questions/1520182/how-to-configure-the-pre- installed-wireguard-client-on-ubuntu-24-04-via-network ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:46.5-0ubuntu0.24.04.1 ProcVersionSignature: Ubuntu 6.8.0-51.52-generic 6.8.12 Uname: Linux 6.8.0-51-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Feb 2 22:20:46 2025 InstallationDate: Installed on 2024-09-07 (148 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) 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 ** Description changed: When enabling Wireguard VPN created through the new Import from file... in Network Settings, the config seems complete but no internet access is available. My settings work on the Wireguard Android app (i.e. I can access the remote network) from the same network on which I am trying to - set up the client. + set up the client. I have checked that the firewall on my client does + not block the port. Other members of the community have experienced the same issue: https://www.reddit.com/r/Ubiquiti/comments/1ewan95/wireguard_vpn_setup_on_ubuntu_2404/ https://askubuntu.com/questions/1520182/how-to-configure-the-pre- installed-wireguard-client-on-ubuntu-24-04-via-network ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:46.5-0ubuntu0.24.04.1 ProcVersionSignature: Ubuntu 6.8.0-51.52-generic 6.8.12 Uname: Linux 6.8.0-51-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Feb 2 22:20:46 2025 InstallationDate: Installed on 2024-09-07 (148 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- 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/2097232 Title: Wireguard enabled without internet access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2097232/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2097230] [NEW] File explorer stops responding on multi file rename
Public bug reported: I am generally experiencing lots of File Explorer crashes in the past months, and I never understood why it kept happening. But today I realized that when I select two or more files(by accident in my case) and then right-click "Rename", file explorer stops responding. Renaming of multi files should either be not allowed or handled better(with some additional interface in which you can rename multiple files at once)... PS I am using 22.04.. If this is fixed in 24, forget about this :) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.6-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-52.53~22.04.1-generic 6.8.12 Uname: Linux 6.8.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Feb 2 23:11:34 2025 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1091, 643)' b'org.gnome.nautilus.window-state' b'sidebar-width' b'262' InstallationDate: Installed on 2022-10-09 (847 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu3.1 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "This is a recording of the bug..." https://bugs.launchpad.net/bugs/2097230/+attachment/5854723/+files/Screencast%20from%2002.02.2025%2023%3A16%3A26.webm ** Summary changed: - File explorer stops reporting on multi file rename + File explorer stops responding on multi file rename -- 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/2097230 Title: File explorer stops responding on multi file rename To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2097230/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011350] Re: ERROR:../src/nautilus-gtk4-helpers.c:116:gtk_widget_get_first_child: assertion failed: (GTK_IS_CONTAINER (widget))
I don't think 43+ needs the same fix. Instead it switched to GTK4 which already has gtk_widget_get_first_child. Hence no bug. See comment #18. -- 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/2011350 Title: ERROR:../src/nautilus-gtk4-helpers.c:116:gtk_widget_get_first_child: assertion failed: (GTK_IS_CONTAINER (widget)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011350/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2088572] Re: Wrong window resolution when using external monitors
Windows being too tall for a monitor are usually the fault of the application or toolkit. It's not like any of your monitors are low resolution, they're definitely not. So I suggest listing all the affected apps in case there's any commonality between them. As a workaround, you can manipulate a window size and position without being able to reach its edges. Just use: * Super+left mouse button to move the window * Super+middle mouse button to resize the window (it will move whichever edge/corner is nearest). -- 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/2088572 Title: Wrong window resolution when using external monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2088572/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2097003] Re: gnome-shell crashed with SIGABRT [libmutter:ERROR:../src/core/window.c:5937:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)]
-- 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/2097003 Title: gnome-shell crashed with SIGABRT [libmutter:ERROR:../src/core/window.c:5937:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2097003/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2089709] Re: Ubuntu 24.04 (X11) sometimes logs in to a black screen with only an X cursor
I can't see anything that would explain this bug in those logs, other than an unsupported extension 'system-monitor-next'. If any extension is buggy then it does have the potential to break the whole shell, so please run: cd ~/.local/share/gnome-shell rm -rf extensions and log in again. Does the bug still occur after that? -- 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/2089709 Title: Ubuntu 24.04 (X11) sometimes logs in to a black screen with only an X cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2089709/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2097003] Re: gnome-shell crashed with SIGABRT [libmutter:ERROR:../src/core/window.c:5937:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)]
Yes, and unfortunately having Nvidia triggers a bug in errors.ubuntu.com which prevents it from providing a proper stack trace. Only this: gnome-shell (6) /usr/lib/x86_64-linux-gnu/libc.so.6+1d26e → /usr/bin/gnome-shell+1c46 → /usr/lib/x86_64-linux-gnu/libc.so.6+1d26e → /usr/lib/x86_64-linux-gnu/libc.so.6+8ff → /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.8000.0+1f5b → /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.8000.0+6aa97 → /usr/lib/x86_64-linux-gnu/libmutter-14.so.0.0.0+9b84b → /usr/lib/x86_64-linux-gnu/libmutter-14.so.0.0.0+a2cc5 → /usr/lib/x86_64-linux-gnu/libmutter-14.so.0.0.0+c13fe → /usr/lib/x86_64-linux-gnu/libmutter-14.so.0.0.0+c343f → /usr/lib/x86_64-linux-gnu/libmutter-14.so.0.0.0+c6885 → /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.8000.0+3f48e → /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.8000.0+9e717 → /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.8000.0+3ff77 → /usr/lib/x86_64-linux-gnu/libmutter-14.so.0.0.0+850fa There are however some unusual errors in the log around the time of the crash. Do you have any other extensions enabled? Please check: gnome-extensions list --enabled -- 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/2097003 Title: gnome-shell crashed with SIGABRT [libmutter:ERROR:../src/core/window.c:5937:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2097003/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2097003] Re: gnome-shell crashed with SIGABRT [libmutter:ERROR:../src/core/window.c:5937:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)]
Decoding it by hand on Noble without debug symbols /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.8000.0+6aa97 → /usr/lib/x86_64-linux-gnu/libmutter-14.so.0.0.0+9b84b → meta_monitor_manager_lid_is_closed_changed? /usr/lib/x86_64-linux-gnu/libmutter-14.so.0.0.0+a2cc5 → meta_monitor_manager_get_laptop_panel? /usr/lib/x86_64-linux-gnu/libmutter-14.so.0.0.0+c13fe → meta_rectangle_find_nonintersected_monitor_edges? /usr/lib/x86_64-linux-gnu/libmutter-14.so.0.0.0+c343f → ? /usr/lib/x86_64-linux-gnu/libmutter-14.so.0.0.0+c6885 → meta_window_delete? and with debug symbols: /usr/lib/x86_64-linux-gnu/libmutter-14.so.0.0.0+9b84b: meta-monitor-manager.c:1426: update_panel_orientation_managed? I don't know what to believe there, but can you disable automatic screen rotation? -- 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/2097003 Title: gnome-shell crashed with SIGABRT [libmutter:ERROR:../src/core/window.c:5937:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2097003/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2097003] Re: gnome-shell crashed with SIGABRT [libmutter:ERROR:../src/core/window.c:5937:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)]
The list is d...@rastersoft.com ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com should I try to disable all of them and try to trigger the crash again? -- 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/2097003 Title: gnome-shell crashed with SIGABRT [libmutter:ERROR:../src/core/window.c:5937:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2097003/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
