[Bug 1945008] Re: Logs in with Wayland although Xorg looks selected in session menu. Need to reselect
So you're going to abandon even worrying about it just because the original bug reporter -- who could have given up, gone to another distro or even another OS at this point -- hasn't replied? And people wonder why I don't report bugs. -- 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/1945008 Title: Logs in with Wayland although Xorg looks selected in session menu. Need to reselect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1891429] Re: Unable to use any application or return to homescreen after opening application menu
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1891429 Title: Unable to use any application or return to homescreen after opening application menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1891429/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1937090] Re: Opening a very wide window crashes the entire system
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- 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/1937090 Title: Opening a very wide window crashes the entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1937090/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946411] Re: Glitchy/freezing desktop caused by opening app launcher group
*** This bug is a duplicate of bug 1872268 *** https://bugs.launchpad.net/bugs/1872268 Thanks, it's a duplicate then. I'm attaching the video again, let's see if it works now. ** Attachment removed: "Reproducing the bug in video" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946411/+attachment/5531404/+files/Grava%C3%A7%C3%A3o%20de%20tela%20de%2007-10-2021%2023%3A08%3A21.webm ** Attachment added: "Reproducing the bug in video" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946411/+attachment/5531405/+files/gnome-shell-bug.webm -- 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/1946411 Title: Glitchy/freezing desktop caused by opening app launcher group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946411/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946410] Re: freezing
Please run: gsettings set org.gnome.desktop.a11y always-show-universal-access-status true and then use the new menu in the top panel to check you don't have any of those options enabled that would affect keyboard behaviour. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Summary changed: - freezing + when "/" or "?" the system hangs for 5 seconds -- 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/1946410 Title: when "/" or "?" the system hangs for 5 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1946410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946411] Re: Glitchy/freezing desktop caused by opening app launcher group
*** This bug is a duplicate of bug 1872268 *** https://bugs.launchpad.net/bugs/1872268 The link in comment #2 is not working, but I can already tell you are describing bug 1889102 and bug 1872268. ** This bug has been marked a duplicate of bug 1872268 Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded) -- 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/1946411 Title: Glitchy/freezing desktop caused by opening app launcher group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946411/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946367] Re: DisplayPort MST Hub only recognizes one of two displays using Wayland (NVIDIA)
Please report the bug upstream at: https://gitlab.gnome.org/GNOME/mutter/issues and then tell us the new issue ID. ** Package changed: wayland (Ubuntu) => mutter (Ubuntu) ** Tags added: nvidia ** Tags added: multimonitor -- 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/1946367 Title: DisplayPort MST Hub only recognizes one of two displays using Wayland (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1946367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946410] [NEW] freezing
You have been subscribed to a public bug: when "/" or "?" the system hangs for 5 seconds ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 7 22:49:32 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] [1002:683f] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] [1682:3248] InstallationDate: Installed on 2021-09-29 (8 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=e4266656-ad3e-418c-ad5b-feb2f61ea165 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0330 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0330:bd05/29/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:skuAll:rvnASUSTeKCOMPUTERINC.:rnZ97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: mutter (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal performance ubuntu -- freezing https://bugs.launchpad.net/bugs/1946410 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945992] Re: Onscreen keyboard is to big in 200% scale
That still looks different to the Ubuntu 20.04 OSK due to your theme. Try changing back to the Ubuntu "Yaru" theme. -- 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/1945992 Title: Onscreen keyboard is to big in 200% scale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945992/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945008] Re: Logs in with Wayland although Xorg looks selected in session menu. Need to reselect
Since this is Mario's bug, we're still incomplete waiting on comment #2. -- 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/1945008 Title: Logs in with Wayland although Xorg looks selected in session menu. Need to reselect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945008] Re: Logs in with Wayland although Xorg looks selected in session menu. Need to reselect
I've noticed this in lots of impish bug reports. Not sure if it indicates a bug but sure looks suspicious: Oct 07 19:13:03 sdcpc systemd[1363]: Starting GNOME Shell on Wayland... Oct 07 19:13:03 sdcpc systemd[1363]: Starting GNOME Shell on X11... Oct 07 19:13:03 sdcpc systemd[1363]: app-gnome-gnome\x2dkeyring\x2dpkcs11-1484.scope: Deactivated successfully. Oct 07 19:13:03 sdcpc systemd[1363]: org.gnome.Shell@x11.service: Control process exited, code=exited, status=2/INVALIDARGUMENT Oct 07 19:13:03 sdcpc systemd[1363]: org.gnome.Shell@x11.service: Skipped due to 'exec-condition'. Oct 07 19:13:03 sdcpc systemd[1363]: Condition check resulted in GNOME Shell on X11 being skipped. Oct 07 19:13:03 sdcpc systemd[1363]: app-gnome-gnome\x2dkeyring\x2dsecrets-1488.scope: Deactivated successfully. Oct 07 19:13:03 sdcpc systemd[1363]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 1. Oct 07 19:13:03 sdcpc systemd[1363]: Stopped GNOME Shell on X11. ... -- 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/1945008 Title: Logs in with Wayland although Xorg looks selected in session menu. Need to reselect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946367] [NEW] DisplayPort MST Hub only recognizes one of two displays using Wayland (NVIDIA)
You have been subscribed to a public bug: I have two 4K Monitors connected to a single DisplayPort 1.4 Output via a DisplayPort 1.4 MST Hub working flawlessly under X.org. I have enabled nvidia-drm.modeset=1 in the GRUB CMDLINE Settings and switched to Wayland in the GDM Greeter. But it seems like Wayland is unable to drive multiple displays via a DisplayPort 1.4 MST Hub, because only one of them shows a display output. However they are both correctly recognized under the display settings. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..2a.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 7 15:05:07 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: zfs, 2.0.6, 5.13.0-16-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA102 [GeForce RTX 3080 Ti] [10de:2208] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GA102 [GeForce RTX 3080 Ti] [10de:1535] InstallationDate: Installed on 2021-10-07 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211006) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_10kpab@/vmlinuz-5.13.0-16-generic root=ZFS=rpool/ROOT/ubuntu_10kpab ro quiet splash nvidia-drm.modeset=1 vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.20 dmi.board.name: X570 Phantom Gaming-ITX/TB3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.20:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming-ITX/TB3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu wayland-session -- DisplayPort MST Hub only recognizes one of two displays using Wayland (NVIDIA) https://bugs.launchpad.net/bugs/1946367 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946411] Re: Glitchy/freezing desktop caused by opening app launcher group
** Attachment added: "Reproducing the bug in video" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946411/+attachment/5531404/+files/Grava%C3%A7%C3%A3o%20de%20tela%20de%2007-10-2021%2023%3A08%3A21.webm -- 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/1946411 Title: Glitchy/freezing desktop caused by opening app launcher group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946411/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946411] [NEW] Glitchy/freezing desktop caused by opening app launcher group
Public bug reported: # Steps to reproduce: 1. Press "Super + A" to see all apps. 2. Find an app launcher group (many launchers grouped in one item) and open it 3. Close the group # What happens: The pagination indicators become duplicated, followed by glitchy animations. This can be temporarily fixed by pressing ALT + F2 and running "r" to restart the desktop. If you don't do that soon, the desktop will become frozen, unresponsive. # Workaround (for the frozen desktop): Switch to another TTY and restart the 'gdm' service. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 7 22:53:34 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-10-07 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) 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 -- 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/1946411 Title: Glitchy/freezing desktop caused by opening app launcher group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946411/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945008] Re: Logs in with Wayland although Xorg looks selected in session menu. Need to reselect
Also seeing this issue. No crashes shown. Boot session is three (3) logins, all three with the selector set to Xorg -- the first one logs in with Gnome Wayland session, the second with Xorg, and the third with Wayland again. This is a fresh Impish (Ubuntu 21.10) install, not an upgrade with no custom core components, updated to latest packages. ** Attachment added: "journalctl -b0 > journal.txt with three desktop logins" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945008/+attachment/5531371/+files/journal.txt -- 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/1945008 Title: Logs in with Wayland although Xorg looks selected in session menu. Need to reselect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1891270] Re: Iranian calendar shows in Azerbaijani language
Related Question: https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/697919 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1891270 Title: Iranian calendar shows in Azerbaijani language To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1891270/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946209] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1946209/+attachment/5531339/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1946209/+attachment/5531020/+files/CoreDump.gz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1946209 Title: evolution-alarm-notify crashed with signal 5 in _XEventsQueued() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1946209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946209] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1946209/+attachment/5531338/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1946209 Title: evolution-alarm-notify crashed with signal 5 in _XEventsQueued() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1946209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946209] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1946209/+attachment/5531337/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1946209 Title: evolution-alarm-notify crashed with signal 5 in _XEventsQueued() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1946209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946209] evolution-alarm-notify crashed with signal 5 in _XEventsQueued()
StacktraceTop: XPending (dpy=0x560aba38aef0) at ../../src/Pending.c:55 gdk_check_xpending (display=0x560aba3a10e0) at x11/../../../../../gdk/x11/gdkeventsource.c:269 gdk_event_source_check (source=source@entry=0x560aba3e2cb0) at x11/../../../../../gdk/x11/gdkeventsource.c:306 g_main_context_check (context=0x560aba3e2da0, max_priority=2147483647, fds=, n_fds=-728157272) at ../../../glib/gmain.c:3955 g_main_context_iterate.constprop.0 (context=context@entry=0x560aba3e2da0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4128 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1946209 Title: evolution-alarm-notify crashed with signal 5 in _XEventsQueued() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1946209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946204] Re: Animations stutter constantly on Nvidia in GNOME 40
Fix uploaded to the impish unapproved queue. -- 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/1946204 Title: Animations stutter constantly on Nvidia in GNOME 40 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1946204/+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
** Changed in: evince (Ubuntu) Assignee: (unassigned) => Georgia Garcia (georgiag) -- 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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Olivier, yes, I shouldn't be assigned. Ian, you're right the profile is
suboptimal (it's also old so likely needs updating).
Do note that this is a separate named profile and evince (and if this is
put in an abstraction, anything that uses the abstraction) only has the
`/{,snap/core/[0-9]*/}usr/bin/snap mrCx -> snap_browser,` rule which
means that it is able to run the 'snap' command (needed since everything
in /snap/bin points to /usr/bin/snap) which at the time I wrote the
profile meant that access to this socket was needed as part of snap run.
IIRC, snapd should be protecting certain actions by uid connecting to it
(eg, you are root or not), but it has been a while since I've looked at
that. Evince is not a snap though so if snapd does any checks on 'is the
client a snap' then those would fail and evince would be able to do
whatever a non-root user could do with the 'snap' command via the
socket.
For snap run, we can see that the snap_browser profile limits what can
be used with 'run' since (at the time I wrote the comment) 'snap run'
required being able to look at the meta/snap.yaml of the specific snap.
This 'works' (worked?) but is brittle since if snap run changed to lift
this requirement (eg, 'snap run' just passed the name of the unresolved
symlink to snapd over the socket and let snapd start the snap, perhaps
via userd, etc) then this falls apart.
The profile was put up as an example as what could be done at the time without
any help from snapd. I never particularly cared for it cause it was brittle and
not designed. I'm not sure how to fix this, but here are some thoughts:
* evince is just executing stuff from /snap/bin (probably via the system's
xdg-open). Assuming xdg-open, the system's xdg-open (or whatever evince is
using to decide and launch the default browser) could itself be fixed in Ubuntu
to launch a different command that behaved better. This wouldn't necessarily
fix other distros (though this is the evince profile in Debian and Ubuntu, so
*technically*, if you got this change (to presumably xdg-open) into them, you
could update the evince profile in them accordingly)
* In lieu of that, if the profile still worked as intended, snapd could be
hardened to look to check more than if the connecting process is root or a
snap; it could also see if it is running under a non-snap profile, then limit
access to the socket API accordingly. This has drawbacks and could break people
who have written custom profiles similar to what I presented.
* I suppose an alternative approach would be to have symlinks in /snap/bin for
things that are registered as browsers (or just the default browser) point to a
designed snap command. Eg:
/snap/bin/firefox -> /usr/bin/snap # keep the
existing one too
/snap/bin/default-browser-is-a-snap -> /usr/bin/snap-browser # name is
illustrative, TBD
Now firefox, chromium, opera, brave, etc snaps registers themselves as
being capable of being a default browser with snapd, then snapd
registers with the system that /snap/bin/default-browser-is-a-snap is
the default browser (so system utilities like xdg-open don't need to
change) and /usr/bin/snap-browser is written to be safe (eg, only able
to 'snap run' the configured default browser, nothing else) and apparmor
profiles are adjusted to have `/{,snap/core/[0-9]*/}usr/bin/snap-browser
Uxr,` (or similar). The /snap/bin/default-browser-is-a-snap path is
illustrative and there isn't really a need for it at all. Could simply
perhaps have snapd register /usr/bin/snap-browser as the default browser
on the system (it now needs to know what snapd configured as the default
browser snap though) and forego the symlink.
--
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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Changed in: evince (Ubuntu) Assignee: Jamie Strandboge (jdstrand) => (unassigned) -- 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 1946307] Re: Loss of focus when an application goes full screen
** No longer affects: mutter (Ubuntu) -- 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/1946307 Title: Loss of focus when an application goes full screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1946307/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945992] Re: Onscreen keyboard is to big in 200% scale
Hi, Daniel, There must be something more than "Extensions" app or improvedosk issue. I removed both and the propblem with scalling is still present. Enclosed screenshot. ** Attachment added: "Zrzut ekranu z 2021-10-07 11-38-29.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945992/+attachment/5531270/+files/Zrzut%20ekranu%20z%202021-10-07%2011-38-29.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/1945992 Title: Onscreen keyboard is to big in 200% scale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945992/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946258] Re: Panels unclickable after screen area capture
No problem in latest version of Remmina (latest/edge v1.4.20+git208.d7b580d50) from https://snapcraft.io/remmina -- 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/1946258 Title: Panels unclickable after screen area capture To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screenshot/+bug/1946258/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946307] Re: Loss of focus when an application goes full screen
** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: New => In Progress ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Status: New => In Progress -- 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/1946307 Title: Loss of focus when an application goes full screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1946307/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946258] Re: Panels unclickable after screen area capture
** Also affects: gnome-screenshot via https://gitlab.gnome.org/GNOME/gnome-screenshot/-/issues/178 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/1946258 Title: Panels unclickable after screen area capture To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screenshot/+bug/1946258/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946258] Re: Panels unclickable after screen area capture
Done https://gitlab.gnome.org/GNOME/gnome-screenshot/-/issues/178 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-screenshot/-/issues #178 https://gitlab.gnome.org/GNOME/gnome-screenshot/-/issues/178 -- 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/1946258 Title: Panels unclickable after screen area capture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1946258/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946258] Re: Panels unclickable after screen area capture
** Also 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/1946258 Title: Panels unclickable after screen area capture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1946258/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946258] Re: Panels unclickable after screen area capture
Please report the issue to the developers at https://gitlab.gnome.org/GNOME/gnome-screenshot/-/issues ** Package changed: gnome-shell (Ubuntu) => gnome-screenshot (Ubuntu) -- 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/1946258 Title: Panels unclickable after screen area capture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1946258/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946258] Re: Panels unclickable after screen area capture
** Attachment added: "IMG_20211007_110544.jpg" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946258/+attachment/5531213/+files/IMG_20211007_110544.jpg -- 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/1946258 Title: Panels unclickable after screen area capture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1946258/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946258] Re: Panels unclickable after screen area capture
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => 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/1946258 Title: Panels unclickable after screen area capture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1946258/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946258] Re: Panels unclickable after screen area capture
Here is the video - https://photos.app.goo.gl/hQ5nAQgNWEQsuyDBA -- 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/1946258 Title: Panels unclickable after screen area capture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1946258/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946258] Re: Panels unclickable after screen area capture
I managed to reproduce it constantly. Problem appears only when Remmina is active and "Grab all keyboad events" pressed. When you try to capture area of Remmina window, Gnome shell freezes after pressing "Take Screenshot" button, window just reappears and no image captured. ** Attachment added: "Screenshot from 2021-10-07 10-43-27.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946258/+attachment/5531212/+files/Screenshot%20from%202021-10-07%2010-43-27.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/1946258 Title: Panels unclickable after screen area capture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946258/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946258] Re: Panels unclickable after screen area capture
Thanks. It sounds like your gnome-shell process has crashed or frozen. When that happens you might be able to interact with apps still as those run through Xorg which has probably not crashed... Next time it happens, please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. 5. Also check for any crashes using these steps: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment -- 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/1946258 Title: Panels unclickable after screen area capture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946258/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1943 https://gitlab.gnome.org/GNOME/mutter/-/issues/1943 ** Project changed: gnome-shell => mutter ** Changed in: mutter Remote watch: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2912 => gitlab.gnome.org/GNOME/mutter/-/issues #1943 ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Invalid ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Fix Committed ** Changed in: mutter (Ubuntu) Importance: Undecided => Low ** Tags added: fixed-in-41.1 fixed-upstream -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1882291/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946204] Re: Animations stutter constantly on Nvidia in GNOME 40
** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-40.6 fixed-upstream -- 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/1946204 Title: Animations stutter constantly on Nvidia in GNOME 40 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1946204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946258] Re: Panels unclickable after screen area capture
Results of execution gsettings list-recursively org.gnome.shell > settings.txt ** Attachment added: "settings.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946258/+attachment/5531205/+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/1946258 Title: Panels unclickable after screen area capture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946258/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
