[Desktop-packages] [Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)
The fix in 44.1-1ubuntu1 works for me, at least on Lunar. Jonathan, please run: dconf dump /org/gnome/ > settingschanges.txt and then attach the resulting text file here. ** Changed in: mutter (Ubuntu Lunar) Status: In Progress => Incomplete ** Changed in: mutter (Ubuntu) Status: Fix Released => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2013216 Title: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Incomplete Status in mutter source package in Lunar: Incomplete Bug description: Impact -- Single clicking the title bar of windows without a complex title bar (namely a title bar with additional buttons besides the close/maximinze/minimize) does not transfer focus to them. Test Case - 1. Open gnome-terminal. 2. Run xedit. 3. Focus gnome-terminal. 4. Click Xedit's title bar. Expected: Xedit has focus. Observed: gnome-terminal retains focus. . 5. Focus Xedit. 6. Click gnome-terminal's title bar. Expected and observed: Xedit relinquishes focus and gnome-terminal gets focus. Other Info -- I can reproduce this in my main, up to date Lunar system in Xorg and also in a virtual machine with the 2023-03-24 09:02 iso (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop-amd64.iso). What Could Go Wrong --- This fix is included in the upstream mutter 44.1 release. See LP: #2020225 for more details. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 11:53:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-16 (316 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-2ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1974029] Re: [nvidia] vram memory leak under Wayland
** Tags added: lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1974029 Title: [nvidia] vram memory leak under Wayland Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: I use 3 monitors. When I turn two of then off and on, the "memory usage" shown by nvidia-smi grows by approximately 400 MB each cycle. When used video memory reaches maximum my card has (it ix GTX 970 with 4GB) the graphical system sort of crashes (desktop is not shown, one of the monitor does not show image at all). This occurs only under Wayland. Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 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 nvidia_modeset nvidia .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..0c.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 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 18 14:50:11 2022 DistUpgraded: 2022-03-19 09:03:59,252 INFO cache.commit() DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed nvidia/510.60.02, 5.15.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GM204 [GeForce GTX 970] [1458:367a] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=UUID=ca73c670-cd82-4bb7-9d49-1e036cf94a1a ro usbcore.autosuspend=-1 libata.force=1.00:noncq acpi_enforce_resources=lax libata.noacpi=1 amd_iommu=on iommu=pt SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-03-19 (60 days ago) dmi.bios.date: 08/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5861 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5861:bd08/10/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1974029/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017412] Re: Libreoffice Draw won't start, unless Impress is installed
** Changed in: libreoffice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2017412 Title: Libreoffice Draw won't start, unless Impress is installed Status in libreoffice package in Ubuntu: Fix Released Bug description: Draw fails to open, unless I install also libreoffice Impress. It only shows the splash screen for 1/2 second, and then dies. I tried to find a useful error message, but I couldn't find any. I randomly discovered that if I install libreoffice-impress, then Draw starts working too. Before, besides Draw, I only had writer, calc, and math installed. Libreoffice version: 7.5.2-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: libreoffice-draw 4:7.5.2-0ubuntu1 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: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 23 11:19:52 2023 InstallationDate: Installed on 2020-10-04 (930 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: libreoffice UpgradeStatus: Upgraded to lunar on 2023-04-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2017412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1974029] Re: [nvidia] vram memory leak under Wayland
Still present in Ubuntu 23.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1974029 Title: [nvidia] vram memory leak under Wayland Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: I use 3 monitors. When I turn two of then off and on, the "memory usage" shown by nvidia-smi grows by approximately 400 MB each cycle. When used video memory reaches maximum my card has (it ix GTX 970 with 4GB) the graphical system sort of crashes (desktop is not shown, one of the monitor does not show image at all). This occurs only under Wayland. Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 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 nvidia_modeset nvidia .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..0c.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 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 18 14:50:11 2022 DistUpgraded: 2022-03-19 09:03:59,252 INFO cache.commit() DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed nvidia/510.60.02, 5.15.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GM204 [GeForce GTX 970] [1458:367a] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=UUID=ca73c670-cd82-4bb7-9d49-1e036cf94a1a ro usbcore.autosuspend=-1 libata.force=1.00:noncq acpi_enforce_resources=lax libata.noacpi=1 amd_iommu=on iommu=pt SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-03-19 (60 days ago) dmi.bios.date: 08/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5861 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5861:bd08/10/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1974029/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Tags added: originate-from-2019935 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in Mutter: New Status in OEM Priority Project: Triaged Status in mutter package in Ubuntu: New Status in nautilus package in Ubuntu: Incomplete Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017097] Re: [raspi] GNOME Shell 44.0 runs at 30 FPS unless the CPU is being stressed
** Summary changed: - [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed + [raspi] GNOME Shell 44.0 runs at 30 FPS unless the CPU is being stressed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2017097 Title: [raspi] GNOME Shell 44.0 runs at 30 FPS unless the CPU is being stressed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: In Progress Bug description: [ Impact ] On a Raspberry Pi 400, GNOME Shell runs at 30 FPS unless the CPU is being stressed in which case it becomes a smooth 60 FPS. Seems like a frequency scaling issue. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always [ Test Plan ] 1. Log into the default (Wayland) session on a Raspberry Pi 4/400. 2. Set the display resolution to 1920x1080 60Hz. 3. Drag a window around and ensure it appears smooth (60Hz). [ Where problems could occur ] Triple buffering affects all frame scheduling so any mistakes can cause high CPU usage, screen freezes and stutter. Try not to make mistakes. [ Original bug ] ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Apr 20 15:13:51 2023 ImageMediaBuild: 20230417 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/2017097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017137] Re: GNOME 44.0 Xorg sessions on Intel GPUs stutter noticeably in 23.04
** Summary changed: - Xorg sessions on Intel GPUs stutter noticeably in 23.04 + GNOME 44.0 Xorg sessions on Intel GPUs stutter noticeably in 23.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2017137 Title: GNOME 44.0 Xorg sessions on Intel GPUs stutter noticeably in 23.04 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: In Progress Bug description: [ Impact ] Xorg sessions on Intel GPUs stutter noticeably in 23.04 Seems like a combination of: * over-aggressive latency optimizations in the latest version of triple buffering; and * gnome-shell 44 being slightly less efficient at some operations like scrolling the app grid. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always [ Test Plan ] 1. Find a machine with an Intel GPU. 2. Log into 'Ubuntu on Xorg'. 3. Press Super+A and scroll the icon right left/right. It should be perfectly smooth like in Wayland sessions. [ Where problems could occur ] Triple buffering affects all frame scheduling so any mistakes can cause high CPU usage, screen freezes and stutter. Try not to make mistakes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2017137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)
Jonathan already opened his own bug 2011251 before this. I'm reluctant to hide the reopening just in there because if it fails for one person then it can fail for another. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2013216 Title: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: In Progress Bug description: Impact -- Single clicking the title bar of windows without a complex title bar (namely a title bar with additional buttons besides the close/maximinze/minimize) does not transfer focus to them. Test Case - 1. Open gnome-terminal. 2. Run xedit. 3. Focus gnome-terminal. 4. Click Xedit's title bar. Expected: Xedit has focus. Observed: gnome-terminal retains focus. . 5. Focus Xedit. 6. Click gnome-terminal's title bar. Expected and observed: Xedit relinquishes focus and gnome-terminal gets focus. Other Info -- I can reproduce this in my main, up to date Lunar system in Xorg and also in a virtual machine with the 2023-03-24 09:02 iso (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop-amd64.iso). What Could Go Wrong --- This fix is included in the upstream mutter 44.1 release. See LP: #2020225 for more details. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 11:53:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-16 (316 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-2ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017976] Update Released
The verification of the Stable Release Update for libreoffice has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2017976 Title: [SRU] libreoffice 7.5.3 for lunar Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Lunar: Fix Released Status in libreoffice source package in Mantic: Fix Released Bug description: [Impact] * LibreOffice 7.5.3 is in its third bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.3_release * Version 7.5.2 is currently released in lunar. For a list of fixed bugs compared to 7.5.2 see the list of bugs fixed in the release candidates of 7.5.3 (that's a total of 119 bugs): https://wiki.documentfoundation.org/Releases/7.5.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.3/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1277/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/14726196/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230428_091914_c1745@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230428_145808_db4a8@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230428_112634_ff879@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230428_092959_ffca8@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230428_214513_ee240@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 119 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2017976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017976] Re: [SRU] libreoffice 7.5.3 for lunar
This bug was fixed in the package libreoffice - 4:7.5.3-0ubuntu0.23.04.1
---
libreoffice (4:7.5.3-0ubuntu0.23.04.1) lunar; urgency=medium
* New upstream release (LP: #2017976)
libreoffice (4:7.5.3~rc2-2) UNRELEASED; urgency=medium
* debian/rules, debian/control.in:
- move share/config/soffice.cfg/simpress/{layoutlist,objectlist,styles}.xml
and share/config/modules/soffice.cfg/simpress/ui/sidebarslidebackground.ui
from -impress to -draw since without them Draw doesn't start anymore
* debian/control.postgresql.in:
- depend on libreoffice-core-nogui | libreoffice-core (like the other
-sdbc-*) (closes: #1034792)
libreoffice (4:7.5.3~rc2-1) experimental; urgency=medium
* New upstream release candidate
libreoffice (4:7.5.3~rc1-1) experimental; urgency=medium
* New upstream release candidate
* debian/rules, debian/tests/*: don't fail if ulimit -c unlimited fails
(like in ci.d.n infrastructure after the bookworm upgrade...)
-- Rico Tzschichholz Mon, 01 May 2023 17:12:14
+0200
** Changed in: libreoffice (Ubuntu Lunar)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/2017976
Title:
[SRU] libreoffice 7.5.3 for lunar
Status in libreoffice package in Ubuntu:
Fix Released
Status in libreoffice source package in Lunar:
Fix Released
Status in libreoffice source package in Mantic:
Fix Released
Bug description:
[Impact]
* LibreOffice 7.5.3 is in its third bugfix release of the 7.5 line:
https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.3_release
* Version 7.5.2 is currently released in lunar. For a list of fixed bugs
compared to 7.5.2 see the list of bugs fixed in the release candidates of 7.5.3
(that's a total of 119 bugs):
https://wiki.documentfoundation.org/Releases/7.5.3/RC1#List_of_fixed_bugs
https://wiki.documentfoundation.org/Releases/7.5.3/RC2#List_of_fixed_bugs
* Given the nature of the project, the complexity of the codebase and
the high level of quality assurance upstream, it is preferable to SRU
a minor release rather than cherry-pick selected bug fixes.
[Testing]
* Upstream testing. Bugs fixed upstream typically include
unit/regression tests, and the release itself is extensively exercised
(both in an automated manner and manually).
* A recent set of upstream's automated jenkins testing can be found here:
https://ci.libreoffice.org/job/gerrit_75/1277/
* More information about the upstream QA testing can be found here:
* Automated tests
https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
* Automated UI tests
https://wiki.documentfoundation.org/Development/UITests
* Regression tests
https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
* Feature tests
https://wiki.documentfoundation.org/QA/Testing/Feature_Tests
* Launchpad testing. The libreoffice packages include autopkgtests that were
run and verified as passing.
Tested build can be found at
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/14726196/+listing-archive-extra
* [amd64]
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230428_091914_c1745@/log.gz
* [arm64]
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230428_145808_db4a8@/log.gz
* [armhf]
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230428_112634_ff879@/log.gz
* [ppc64el]
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230428_092959_ffca8@/log.gz
* [riscv64] not available
* [s390x]
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230428_214513_ee240@/log.gz
* General smoke testing of all the applications in the office suite were
carried out by going through the manual testplan as documented by:
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice
[Regression Potential]
* A minor release with a total of 119 bug fixes always carries the
potential for introducing regressions, even though it is a bugfix-only
release, meaning that no new features were added, and no existing
features were removed.
* A combination of autopkgtests and careful smoke testing as
described above should provide reasonable confidence that no
regressions sneaked in.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2017976/+subscriptions
--
Mailing list:
[Desktop-packages] [Bug 2017976] Re: [SRU] libreoffice 7.5.3 for lunar
7.5.4 is in mantic so setting that task to Fix Released. ** Changed in: libreoffice (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2017976 Title: [SRU] libreoffice 7.5.3 for lunar Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Lunar: Fix Released Status in libreoffice source package in Mantic: Fix Released Bug description: [Impact] * LibreOffice 7.5.3 is in its third bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.3_release * Version 7.5.2 is currently released in lunar. For a list of fixed bugs compared to 7.5.2 see the list of bugs fixed in the release candidates of 7.5.3 (that's a total of 119 bugs): https://wiki.documentfoundation.org/Releases/7.5.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.3/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1277/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/14726196/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230428_091914_c1745@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230428_145808_db4a8@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230428_112634_ff879@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230428_092959_ffca8@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230428_214513_ee240@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 119 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2017976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020277] Re: Update gnome-shell to 44.1
** Description changed: Impact -- + There is a new bugfix release in the stable 44 series. + + https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/44.1/NEWS + + Test Case + - + Complete all the test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell + + Other Info + -- + gnome-shell provides the GNOME version number for the Settings app About page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by gnome-desktop/gnome-desktop3) + + This update requires mutter 44.1 (LP: #2020225). This was done with + bumped dependencies in debian/control. gnome-shell 44.1 could be run + with mutter 44.1 but it led to build test failures. Also, mixing + different versions of mutter & gnome-shell is not supported upstream. + + What Could Go Wrong + --- + GNOME Shell is the heart of the Ubuntu desktop experience. + + A severe enough bug could mean that people are unable to use their + desktop version of Ubuntu. + + Smaller bugs could interrupt people's workflows. + + GNOME Shell is included in the GNOME micro release exception + + https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Changed in: gnome-shell (Ubuntu Lunar) Status: Triaged => In Progress ** Description changed: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/44.1/NEWS + + It is also believed to fix at least one crash issue reported as LP: + #2016007 but without a clear test case, that bug is not included in this + SRU verification. Test Case - Complete all the test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell Other Info -- gnome-shell provides the GNOME version number for the Settings app About page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by gnome-desktop/gnome-desktop3) This update requires mutter 44.1 (LP: #2020225). This was done with bumped dependencies in debian/control. gnome-shell 44.1 could be run with mutter 44.1 but it led to build test failures. Also, mixing different versions of mutter & gnome-shell is not supported upstream. What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2020277 Title: Update gnome-shell to 44.1 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Lunar: In Progress Status in gnome-shell source package in Mantic: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/44.1/NEWS It is also believed to fix at least one crash issue reported as LP: #2016007 but without a clear test case, that bug is not included in this SRU verification. Test Case - Complete all the test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell Other Info -- gnome-shell provides the GNOME version number for the Settings app About page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by gnome-desktop/gnome-desktop3) This update requires mutter 44.1 (LP: #2020225). This was done with bumped dependencies in debian/control. gnome-shell 44.1 could be run with mutter 44.1 but it led to build test failures. Also, mixing different versions of mutter & gnome-shell is not supported upstream. What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968383] Re: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by
** Description changed: - Ubuntu 22.04 development fully updated as of time of this report. + Impact + -- + On a fresh boot, as soon as you open some applications and do the up touchpad gesture to enter the application grid and then back down to return to the desktop, journal spits out js stacktrace. If you don't trigger the crash then try opening and closing an app and trying again. - On a fresh boot, as soon as you open some applications and do the up - touchpad gesture to enter the application grid and then back down to - return to the desktop, journal spits out js stacktrace. If you don't - trigger the crash then try opening and closing an app and trying again. + Test Case + - + 1. Install the update + 2. Open a terminal and run journalctl -f + 3. You may need to wait a few moments for some background tasks like NetworkManager or PackageKit to finish what they're doing. The journal should be fairly quiet before proceeding. + 3. Open another app + 4. Perform the 3 finger swipe up gesture until the app grid displays then swipe down to go back to the desktop. + 5. See journal for gnome-shell errors like seen below. + 6. If nothing happens try opening an app, closing it and try again. + What Could Go Wrong + --- + This is fixed in gnome-shell 44.1. See LP: #2020277 for more details. + + Sample stacktrace + - Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ** Also affects: gnome-shell (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Lunar) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. [windowPreview.js:566] Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Lunar: In Progress Bug description: Impact -- On a fresh boot, as soon as you open some applications and do the up touchpad gesture to enter the application grid and then back down to return to the desktop, journal spits out js stacktrace. If you don't trigger the crash then try opening and closing an app and trying again. Test Case - 1. Install the update 2. Open a terminal and run journalctl -f 3. You may need to wait a few moments for some background tasks like NetworkManager or PackageKit to finish what they're doing. The journal should be fairly quiet before proceeding. 3. Open another app 4. Perform the 3 finger swipe up gesture until the app grid displays then swipe down to go back to the desktop. 5. See journal for gnome-shell errors like seen below. 6. If nothing happens try opening an app, closing it and try again. What Could Go Wrong --- This is fixed in gnome-shell 44.1. See LP: #2020277 for more details. Sample stacktrace - Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be
[Desktop-packages] [Bug 1968390] Re: JS ERROR: TypeError: this.window_container is null
For simplicity, we are going to use bug 1968383 for tracking this bugfix for Ubuntu 23.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968390 Title: JS ERROR: TypeError: this.window_container is null Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: Ubuntu 22.04 Development A 3 finger touchpad swipe up/down gesture with 1 application open outputs a lot of JS errors and stacks to the journal. This issue may be the same or related to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383 but the output is somewhat different when you have more than 1 app open. This also happens with all extensions disabled, does not happen in Fedora 36. To reproduce 1. login and open terminal and watch the journal 2. perform the 3 finger swipe up gesture until the app grid displays then swipe down to go back to the desktop. 3. See journal 4. If nothing happens try opening an app, closing it and try again. Apr 08 21:18:49 x1c gnome-shell[21675]: JS ERROR: TypeError: this.window_container is null hideOverlay@resource:///org/gnome/shell/ui/windowPreview.js:373:9 vfunc_leave_event/this._idleHideOverlayId<@resource:///org/gnome/shell/ui/windowPreview.js:571:26 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968390/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1987976 Title: firefox black window on wayland Status in Mozilla Firefox: Unknown Status in Mutter: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: [ Impact ] On some systems, when you open the Firefox snap right after having logged in into an Ubuntu on Wayland session, you are met by a black window. This happens because the FF snap is run under Xwayland, and Xwayland may not be enabled early enough to handle the start of the application properly. You can easily reproduce the issue in a Wayland session: * Close Firefox * Run the command "killall Xwayland" in terminal * Open Firefox An upstream mutter change addresses this issue, and the proposed lunar change cherry picks that upstream change as a patch. [ Test Plan ] On an updated Ubuntu 23.04: * Install the mutter related binaries from lunar-proposed * Reboot and log in to an Ubuntu on Wayland session * Run the command "killall Xwayland" * Open the Firefox snap, and find that it starts normally [ Where problems could occur ] This is the upstream merge request in question: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970 The changes (except for the test related ones) are small, and specifically intended to address issues like the one reported in this bug. There are also reviews by a couple of experienced GNOME devs. So even if the proposed change is not well tested yet, it seems to me that the risk for adverse side effects is limited. The merge request was accepted upstream and will be included in mutter 44.2 which should be released approximately May 29. [ Original description ] nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976] Re: firefox black window on wayland
This bug was fixed in the package mutter - 44.0-2ubuntu4.23.04.1 --- mutter (44.0-2ubuntu4.23.04.1) lunar; urgency=medium [ Marco Trevisan (Treviño) ] * Fix issue with Firefox opening black window in wayland sessions - d/p/display-Set-compositor-selection-earlier-on-XWayland.patch (LP: #1987976) -- Gunnar Hjalmarsson Mon, 24 Apr 2023 19:59:49 +0200 ** Changed in: mutter (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1987976 Title: firefox black window on wayland Status in Mozilla Firefox: Unknown Status in Mutter: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: [ Impact ] On some systems, when you open the Firefox snap right after having logged in into an Ubuntu on Wayland session, you are met by a black window. This happens because the FF snap is run under Xwayland, and Xwayland may not be enabled early enough to handle the start of the application properly. You can easily reproduce the issue in a Wayland session: * Close Firefox * Run the command "killall Xwayland" in terminal * Open Firefox An upstream mutter change addresses this issue, and the proposed lunar change cherry picks that upstream change as a patch. [ Test Plan ] On an updated Ubuntu 23.04: * Install the mutter related binaries from lunar-proposed * Reboot and log in to an Ubuntu on Wayland session * Run the command "killall Xwayland" * Open the Firefox snap, and find that it starts normally [ Where problems could occur ] This is the upstream merge request in question: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970 The changes (except for the test related ones) are small, and specifically intended to address issues like the one reported in this bug. There are also reviews by a couple of experienced GNOME devs. So even if the proposed change is not well tested yet, it seems to me that the risk for adverse side effects is limited. The merge request was accepted upstream and will be included in mutter 44.2 which should be released approximately May 29. [ Original description ] nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015861] Re: cursor does not track window when dragging between monitors with different scaling factors
** Description changed: - I have two screens. My laptop is using 200% scaling and the other - external screen is using 100% scaling. When I drag windows between the - monitors the cursor moves to unexpected locations when it moves onto - another screen with a different scaling factor. + Impact + --- + I have two screens. My laptop is using 200% scaling and the other external screen is using 100% scaling. When I drag windows between the monitors the cursor moves to unexpected locations when it moves onto another screen with a different scaling factor. I would expect the cursor to stay in the relative location when I started dragging the window. Hopefully this is clear the the attached screencast. + + Test Case + - + 1. Install the update + 2. Log out + 3. Log back in + 4. If not already done, open the Settings app. Click one of the displays in the list and set it to 200%. Leave your other display at 100%. + 5. Drag a window from one screen to the other. + The cursor and window should smoothly transition from one displays to the other without the cursor jumping dramatically to a different location when it crosses between the displays. + + Other Info + -- + Setting different scaling for different displays requires Wayland. This will not work with the Ubuntu on Xorg session. + + What Could Go Wrong + --- + This fix is included in the upstream mutter 44.1 release. See LP: #2020225 for more details. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:04:51 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Also affects: mutter (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Lunar) Importance: Undecided => Low ** Changed in: mutter (Ubuntu Lunar) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2015861 Title: cursor does not track window when dragging between monitors with different scaling factors Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: In Progress Bug description: Impact --- I have two screens. My laptop is using 200% scaling and the other external screen is using 100% scaling. When I drag windows between the monitors the cursor moves to unexpected locations when it moves onto another screen with a different scaling factor. I would expect the cursor to stay in the relative location when I started dragging the window. Hopefully this is clear the the attached screencast. Test Case - 1. Install the update 2. Log out 3. Log back in 4. If not already done, open the Settings app. Click one of the displays in the list and set it to 200%. Leave your other display at 100%. 5. Drag a window from one screen to the other. The cursor and window should smoothly transition from one displays to the other without the cursor jumping dramatically to a different location when it crosses between the displays. Other Info -- Setting different scaling for different displays requires Wayland. This will not work with the Ubuntu on Xorg session. What Could Go Wrong --- This fix is included in the upstream mutter 44.1 release. See LP: #2020225 for more details. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:04:51 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2015861/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 2018600] Update Released
The verification of the Stable Release Update for libreoffice has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2018600 Title: [SRU] libreoffice 7.4.7 for kinetic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Kinetic: Fix Released Bug description: [Impact] * LibreOffice 7.4.7 is in its seventh bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.7_release * Version 7.4.6 is currently released in kinetic. For a list of fixed bugs compared to 7.4.6 see the list of bugs fixed in the release candidates of 7.4.7 (that's a total of 73 bugs): https://wiki.documentfoundation.org/Releases/7.4.7/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.4.7/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1827/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/14734942/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/amd64/libr/libreoffice/20230504_151518_a9360@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/arm64/libr/libreoffice/20230504_200542_1dfdd@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/armhf/libr/libreoffice/20230505_142551_a6b85@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/ppc64el/libr/libreoffice/20230504_161525_fdb04@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/s390x/libr/libreoffice/20230506_054745_25b3f@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 73 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2018600/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2018600] Re: [SRU] libreoffice 7.4.7 for kinetic
This bug was fixed in the package libreoffice - 1:7.4.7-0ubuntu0.22.10.1 --- libreoffice (1:7.4.7-0ubuntu0.22.10.1) kinetic; urgency=medium * New upstream release (LP: #2018600) [ Rico Tzschichholz ] * Install all yaru icon variants * Bump yaru source to "2023-03-31" [ Rene Engelhard ] * debian/rules, debian/tests/*: don't fail if ulimit -c unlimited fails (like in ci.d.n infrastructure after the bookworm upgrade...) * debian/control.postgresql.in: - depend on libreoffice-core-nogui | libreoffice-core (like the other -sdbc-*) -- Rico Tzschichholz Wed, 03 May 2023 19:17:57 +0200 ** Changed in: libreoffice (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2018600 Title: [SRU] libreoffice 7.4.7 for kinetic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Kinetic: Fix Released Bug description: [Impact] * LibreOffice 7.4.7 is in its seventh bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.7_release * Version 7.4.6 is currently released in kinetic. For a list of fixed bugs compared to 7.4.6 see the list of bugs fixed in the release candidates of 7.4.7 (that's a total of 73 bugs): https://wiki.documentfoundation.org/Releases/7.4.7/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.4.7/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1827/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/14734942/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/amd64/libr/libreoffice/20230504_151518_a9360@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/arm64/libr/libreoffice/20230504_200542_1dfdd@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/armhf/libr/libreoffice/20230505_142551_a6b85@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/ppc64el/libr/libreoffice/20230504_161525_fdb04@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/s390x/libr/libreoffice/20230506_054745_25b3f@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 73 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2018600/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020225] Re: Update mutter to 44.1
** Description changed: Impact -- + There is a new bugfix release in the stable 44 series. + https://gitlab.gnome.org/GNOME/mutter/-/blob/44.1/NEWS + + Test Case + - + Complete the test case from + + https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter + + What Could Go Wrong + --- + Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. + + A severe enough bug could mean that people are unable to use their + desktop version of Ubuntu. + + Smaller bugs could interrupt people's workflows. + + mutter is part of GNOME Core and is included in the GNOME micro release + exception + + https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Description changed: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/44.1/NEWS + + This is also a prerequisite to update gnome-shell to 44.1 (LP: #2020277) Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** No longer affects: mutter (Ubuntu Mantic) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020225 Title: Update mutter to 44.1 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: In Progress Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/44.1/NEWS This is also a prerequisite to update gnome-shell to 44.1 (LP: #2020277) Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976] Re: firefox black window on wayland
** Description changed: [ Impact ] On some systems, when you open the Firefox snap right after having logged in into an Ubuntu on Wayland session, you are met by a black window. This happens because the FF snap is run under Xwayland, and Xwayland may not be enabled early enough to handle the start of the application properly. You can easily reproduce the issue in a Wayland session: * Close Firefox * Run the command "killall Xwayland" in terminal * Open Firefox An upstream mutter change addresses this issue, and the proposed lunar change cherry picks that upstream change as a patch. [ Test Plan ] On an updated Ubuntu 23.04: * Install the mutter related binaries from lunar-proposed * Reboot and log in to an Ubuntu on Wayland session * Run the command "killall Xwayland" * Open the Firefox snap, and find that it starts normally [ Where problems could occur ] This is the upstream merge request in question: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970 The changes (except for the test related ones) are small, and specifically intended to address issues like the one reported in this bug. There are also reviews by a couple of experienced GNOME devs. So even if the proposed change is not well tested yet, it seems to me that the risk for adverse side effects is limited. + The merge request was accepted upstream and will be included in mutter + 44.2 which should be released approximately May 29. + [ Original description ] nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1987976 Title: firefox black window on wayland Status in Mozilla Firefox: Unknown Status in Mutter: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: [ Impact ] On some systems, when you open the Firefox snap right after having logged in into an Ubuntu on Wayland session, you are met by a black window. This happens because the FF snap is run under Xwayland, and Xwayland may not be enabled early enough to handle the start of the application properly. You can easily reproduce the issue in a Wayland session: * Close Firefox * Run the command "killall Xwayland" in terminal * Open Firefox An upstream mutter change addresses this issue, and the proposed lunar change cherry picks that upstream change as a patch. [ Test Plan ] On an updated Ubuntu 23.04: * Install the mutter related binaries from lunar-proposed * Reboot and log in to an Ubuntu on Wayland session * Run the command "killall Xwayland" * Open the Firefox snap, and find that it starts normally [ Where problems could occur ] This is the upstream merge request in question: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970 The changes (except for the test related ones) are small, and specifically intended to address issues like the one reported in this bug. There are also reviews by a couple of experienced GNOME devs. So even if the proposed change is not well tested yet, it seems to me that the risk for adverse side effects is limited. The merge request was accepted upstream and will be included in mutter 44.2 which should be released approximately May 29. [ Original description ] nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat :
[Desktop-packages] [Bug 2017097] Re: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed
** Also affects: mutter (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Lunar) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2017097 Title: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: In Progress Bug description: [ Impact ] On a Raspberry Pi 400, GNOME Shell runs at 30 FPS unless the CPU is being stressed in which case it becomes a smooth 60 FPS. Seems like a frequency scaling issue. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always [ Test Plan ] 1. Log into the default (Wayland) session on a Raspberry Pi 4/400. 2. Set the display resolution to 1920x1080 60Hz. 3. Drag a window around and ensure it appears smooth (60Hz). [ Where problems could occur ] Triple buffering affects all frame scheduling so any mistakes can cause high CPU usage, screen freezes and stutter. Try not to make mistakes. [ Original bug ] ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Apr 20 15:13:51 2023 ImageMediaBuild: 20230417 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/2017097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999308] Re: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox
There is technical reason why we need the transitional deb. You have options if you are set on not using the firefox version Ubuntu is officially supporting, apt pinning is one. Installing from the upstream tar instead of an official ppa is another one... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1999308 Title: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox Status in firefox package in Ubuntu: Invalid Bug description: I have looked on various forums including the search features of Launchpad, help.ubuntu..com, and Google for answers on this but not been able to. I have uninstalled the snap of firefox multiple times, installing the real Firefox from ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/, only for a few days later (once hours later) for snap to uninstall the real thing and install its snap version instead. I have tried a basic sudo snap remove firefox and when that didn't work sudo snap disable firefox sudo snap remove --purget firefox The former should be enough - that's a direct expression of my preferences, some thing like "You should have typed sudo snap remove --do-not-reinstall --disable-auto-ignore-preferences firefox" would not resolve this bug. When installing using apt-get, the correct version is being installed, and snap afterwards does not show the presence of firefox: Get:1 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 xul-ext-ubufox all 3.4-0ubuntu1.17.10.1 [3,320 B] Get:2 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 firefox-locale-en amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [831 kB] Get:3 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 firefox amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [64.9 MB] Name Version RevTracking Publisher Notes authy 2.2.2 12 latest/stable twilio-authy - bare 1.0 5 latest/stable canonical✓ base chromium 108.0.5359.94 2238 latest/stable canonical✓ - code 5235c6bb114latest/stable vscode✓classic core 16-2.57.6 14399 latest/stable canonical✓ core core18 202211032632 latest/stable canonical✓ base core20 202211231738 latest/stable canonical✓ base cups 2.4.2-4 836latest/stable openprinting✓ - gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 161latest/stable canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - onlyoffice-desktopeditors 7.2.1 133latest/stable onlyoffice✓- snap-store 41.3-66-gfe1e325638 latest/stable/… canonical✓ - snapd 2.57.6 17883 latest/stable canonical✓ snapd /var/lib/snapd/seed/snaps contains (once firefox is removed): core18_1880.snap gnome-3-34-1804_36.snap gtk-common-themes_1506.snap snapd_8542.snap snap-store_467.snap https://ubuntuhandbook.org/index.php/2021/10/prevent-installing-firefox-snap-ubuntu-mate-21-10/ claims that a similar issue affects Ubuntu MATE 21.04 and the solution was to type "sudo apt-mark manual firefox", which I have done, but that has not resolved the problem. I'm not here to explain why I wouldn't want the snap version, it is clearly a bug for snap to accept a command to uninstall something and then automatically reinstall it days later without the permission of the user, and especially galling that it removes the real version at the same time. I have lost data (passwords and history) because of this bug, because one of the many faults of the snap version is that it ignores the user's real ~/.mozilla profile and creates a shadow profile instead inside of the snap system. Please disable this behavior. It's obnoxious, it ignores EXPLICITY stated user preferences, and it causes the loss of data. I am unclear on what package is causing the behavior so for now marking it against Firefox, but it could be against some other piece of infrastructure related to snap: affects ubuntu/firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1999308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)
** Also affects: mutter (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Lunar) Status: New => In Progress ** Description changed: - Single clicking the title bar of windows without a complex title bar - (namely a title bar with additional buttons besides the - close/maximinze/minimize) does not transfer focus to them. + Impact + -- + Single clicking the title bar of windows without a complex title bar (namely a title bar with additional buttons besides the close/maximinze/minimize) does not transfer focus to them. - Reproduction recipe: - + Test Case + - 1. Open gnome-terminal. 2. Run xedit. 3. Focus gnome-terminal. 4. Click Xedit's title bar. Expected: Xedit has focus. Observed: gnome-terminal retains focus. . 5. Focus Xedit. 6. Click gnome-terminal's title bar. Expected and observed: Xedit relinquishes focus and gnome-terminal gets focus. - I can reproduce this in my main, up to date Lunar system in Xorg and - also in a virtual machine with the 2023-03-24 09:02 iso - (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop-amd64.iso). + Other Info + -- + I can reproduce this in my main, up to date Lunar system in Xorg and also in a virtual machine with the 2023-03-24 09:02 iso (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop-amd64.iso). + + What Could Go Wrong + --- + This fix is included in the upstream mutter 44.1 release. See LP: #2020225 for more details. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 11:53:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-16 (316 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-2ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2013216 Title: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: In Progress Bug description: Impact -- Single clicking the title bar of windows without a complex title bar (namely a title bar with additional buttons besides the close/maximinze/minimize) does not transfer focus to them. Test Case - 1. Open gnome-terminal. 2. Run xedit. 3. Focus gnome-terminal. 4. Click Xedit's title bar. Expected: Xedit has focus. Observed: gnome-terminal retains focus. . 5. Focus Xedit. 6. Click gnome-terminal's title bar. Expected and observed: Xedit relinquishes focus and gnome-terminal gets focus. Other Info -- I can reproduce this in my main, up to date Lunar system in Xorg and also in a virtual machine with the 2023-03-24 09:02 iso (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop-amd64.iso). What Could Go Wrong --- This fix is included in the upstream mutter 44.1 release. See LP: #2020225 for more details. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 11:53:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-16 (316 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-2ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012717] Re: GNOME 44 multi-monitor screen freeze when resuming from sleep
** Also affects: mutter (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Lunar) Status: New => In Progress ** Changed in: mutter (Ubuntu Lunar) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2012717 Title: GNOME 44 multi-monitor screen freeze when resuming from sleep Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: In Progress Bug description: [ Impact ] Using multiple monitors in a Wayland session, one or both may freeze when resuming from sleep. [ Test Plan ] 1. Log into a Wayland session. 2. Set up gnome-shell to span two monitors. 3. Wait for the monitors to sleep. 4. Wiggle the mouse to wake them. 5. Move the mouse between both monitors. 6. Verify that the mouse appears on both monitors and neither are frozen. [ Where problems could occur ] This fix affects frame scheduling so problems could always occur in the form of other screen freezes and frame rate issues. [ Original report ] Testing GNOME 44 I find it can't resume from sleep properly if two monitors are plugged in. Both monitors wake up, but one is completely frozen and the other is partially frozen (stops responding to anything but cursor movement). Using Intel graphics with two USB-C monitors. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2012717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020225] Re: Update mutter to 44.1
** Changed in: mutter (Ubuntu Lunar) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020225 Title: Update mutter to 44.1 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: In Progress Status in mutter source package in Mantic: Fix Released Bug description: Impact -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)
Jonathan, please open a new bug. You can run this command to include basic information about your system: ubuntu-bug libmutter-12-0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2013216 Title: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: Single clicking the title bar of windows without a complex title bar (namely a title bar with additional buttons besides the close/maximinze/minimize) does not transfer focus to them. Reproduction recipe: 1. Open gnome-terminal. 2. Run xedit. 3. Focus gnome-terminal. 4. Click Xedit's title bar. Expected: Xedit has focus. Observed: gnome-terminal retains focus. . 5. Focus Xedit. 6. Click gnome-terminal's title bar. Expected and observed: Xedit relinquishes focus and gnome-terminal gets focus. I can reproduce this in my main, up to date Lunar system in Xorg and also in a virtual machine with the 2023-03-24 09:02 iso (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop- amd64.iso). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 11:53:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-16 (316 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-2ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017137] Re: Xorg sessions on Intel GPUs stutter noticeably in 23.04
** Also affects: mutter (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Lunar) Status: New => In Progress ** Changed in: mutter (Ubuntu Lunar) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2017137 Title: Xorg sessions on Intel GPUs stutter noticeably in 23.04 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: In Progress Bug description: [ Impact ] Xorg sessions on Intel GPUs stutter noticeably in 23.04 Seems like a combination of: * over-aggressive latency optimizations in the latest version of triple buffering; and * gnome-shell 44 being slightly less efficient at some operations like scrolling the app grid. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always [ Test Plan ] 1. Find a machine with an Intel GPU. 2. Log into 'Ubuntu on Xorg'. 3. Press Super+A and scroll the icon right left/right. It should be perfectly smooth like in Wayland sessions. [ Where problems could occur ] Triple buffering affects all frame scheduling so any mistakes can cause high CPU usage, screen freezes and stutter. Try not to make mistakes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2017137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1700085] Re: Mouse cursor is tiny on HiDPI screens
I just noticed the same issue... I also nociced that if my laptop goes to sleep it's small when I'm using it again. But if I switch to xorg (and not wayland) I can restart it and it's working ok until my laptop goes to sleep again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1700085 Title: Mouse cursor is tiny on HiDPI screens Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I am on Artful and have switched to GNOME as GNOME is the default desktop now and Unity shows some instabilities. I am using a Lenovo Thinkpad X1 Carbon (2nd gen.) notebook with 14-inch QHD (2560x1440) display, so I am well over the good old 72-dpi CRT resolution. With some effort I have at least got a somewhat useful scaling of the GUI elements (esp. text size), mainly by getting into Unity7, getting into the Display Settings there, removing my ~1.5 scaling factor, returning to GNOME, installing the advanced settings manager (gnome- tweak-tool or so) and setting a scaling factor of ~2). Large text in accessibilty does not work for me as it makes the text huge. Now the mouse cursor does no bother on all these changes. It stays always in its 72-dpi hard-coded size which is really tiny under GNOME on my QHD screen. It gets easily totally invisible for me, especially on text fields where it gets a skinny vertical bar. Therefore there are two fixes needed: 1. Mouse cursor needs to scale with scale factor for the desktop, so that it is in a good size relation with the rest of the desktop. Please take this into account for fractional scaling efforts. 2. Even a standard-sized mouse cursor can be too small for people with vision problems, so the accessibility options need a possibility to apply a (fractional) adjustable scaling factor to the mouse cursor's standard size. Please take these changes into account ASAP, ideally on 17.10 at the latest. Please consider backporting upstream fixes for achieving this goal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1700085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019994] Re: Update gnome-calendar to 44.1
I installed gnome-calendar 44.1-0ubuntu1 and verified that the app continues to work well. I successfully completed the Test Case. ** Tags removed: verification-needed verification-needed-lunar ** Tags added: verification-done verification-done-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/2019994 Title: Update gnome-calendar to 44.1 Status in gnome-calendar package in Ubuntu: Fix Released Status in gnome-calendar source package in Lunar: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 44 series. https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/44.1/NEWS Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Calendar What Could Go Wrong --- GNOME Calendar is included by default in Ubuntu Desktop, Edubuntu, and Ubuntu Cinnamon. If there are bugs in GNOME Calendar, Evolution (not installed by default) could be used instead. GNOME Calendar can sync with Google or Microsoft online calendars. Therefore, bugs in editing calendar events can by synced to those services. GNOME Calendar is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/2019994/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904789] Re: [snap] Cannot confirm security exception for invalid certificate
Apologies if this isn't the right place to post. I'm new to Ubuntu, and couldn't find anything recent that addresses my problem via a search of help topics. As of this morning I can't access Thunderbird due to a box asking me to add a security exception as my mail server is attempting to identify itself with invalid information. The box to add an exception comes pre- ticked, but when I click on the 'Confirm Security Exception' button the box just remains. There are solutions available elsewhere, but they're all dependent on my being able to get into Thunderbird and change settings, and the presence of the box won't let me access the settings. Is there a way around this. Please bear in mind I'm new to Ubuntu and have little experience in coding. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1904789 Title: [snap] Cannot confirm security exception for invalid certificate Status in thunderbird package in Ubuntu: Confirmed Bug description: Note: This bug is specific to the Snap version of Thunderbird, I can't reproduce it with the Ubuntu-packaged version for example (which I have installed on Ubuntu, used for multiple years and stopped using recently to get the more recent versions of TB available with Snap). When a certificate problem arrises with a server from which Thunderbird tries to retrieve emails, the "Add Security Exception" window gives you the option to "Confirm Security Exception" (meaning that Thunderbird will overlook the invalid certificate). The problem is that nothing happens when I click the "Confirm Security Exception" button. I've tried the usual workarounds, including removing the email account and adding it again, to no avail. The peculiar thing here is that I have had certificate problems before, when using a non-snap version of Thunderbird, and clicking the "Confirm Security Exception" button has always worked. Not with the Snap version it seems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1904789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019200] Re: glmark2 fullscreen performance regression in mutter 44.0
** Changed in: mutter Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2019200 Title: glmark2 fullscreen performance regression in mutter 44.0 Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: Gnome broke fullscreen unredir in mutter 12 resulting in serious performance regressions shown in : https://www.phoronix.com/review/ubuntu-2304-laptops/2 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2019200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999308] Re: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox
If you intercept snap as described above by sudo snap disable firefox sudo snap remove firefox and add the Mozilla PPA for Firefox, then the Ubuntu deb package will remove the Mozilla Firefox version without being able to install the snap version because that was disabled. The result is no Firefox. This can be fixed by running apt upgrade twice but I would call this a bug with the package. This can be prevented by disabling the Ubuntu package by cat
[Desktop-packages] [Bug 1991022] Re: Service activation via Systemd socket
** Description changed: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Impact] It's relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. That can be done by implementing the action of the speech dispatcher service via a Systemd socket: > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The changes are already merged upstream[21][22][23], but still not released. I have built and installed the package in Mantic and verified that running spd-say from inside a snap causes the host's dispatcher to spawn and emit sound — see 'Test case' for more details. This has also been - verified in Jammy by Lissyx[3] and there is a merge proposal[4] for the - Firefox snap that assumes the incorporation of this delta in speech- + verified in Jammy by Lissyx[31][32] and there is a merge proposal[4] for + the Firefox snap that assumes the incorporation of this delta in speech- dispatcher. Note: Either the installed socket needs to be started manually to function correctly or the system needs to be rebooted. [Test case] Install the proposed speech-dispatcher and the snap[5] containing spd- say. Then, systemctl start --user speech-dispatcher.socket snap run --shell geheim $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi [Regression potential] If the socket communication were not working (e.g. connection refused), then this would result in text-to-speech failing, even for a not sandboxed program. Do note, however, that if the socket were not available for whatever - reason (e.g. the user didn't start it manually nor rebooted), then - thesd_listen_fds(0) >= 1 would be false and no regression would be + reason (e.g. the user didn't start it manually nor rebooted), then the + sd_listen_fds(0) >= 1 test would be false and no regression would be observed, as then the program would fallback to its usual operation. [1] https://github.com/brailcom/speechd/issues/335 [21] https://github.com/brailcom/speechd/pull/763 [22] https://github.com/brailcom/speechd/pull/776 [23] https://github.com/brailcom/speechd/pull/817 - [3] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html + [31] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html + [32] https://bugzilla.mozilla.org/show_bug.cgi?id=1729750#c23 [4] https://github.com/canonical/firefox-snap/pull/12 [5] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: Service activation via Systemd socket Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Focal: New Status in speech-dispatcher source package in Jammy: New Status in speech-dispatcher source package in Kinetic: New Status in speech-dispatcher source package in Lunar: New Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Impact] It's relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps
[Desktop-packages] [Bug 2012388] Re: X11 window at top-right of the screen is invisible and steals mouse clicks
Here is more information. This is without the gnome extension and anydesk: luis@xtreme:~$ xwininfo -all xwininfo: Please select the window about which you would like information by clicking the mouse in that window. xwininfo: Window id: 0x40093f (has no name) Root window id: 0x1ef (the root window) (has no name) Parent window id: 0x1ef (the root window) (has no name) 0 children. Absolute upper-left X: 2854 Absolute upper-left Y: 5 Relative upper-left X: 2854 Relative upper-left Y: 5 Width: 200 Height: 200 Depth: 24 Visual: 0x21 Visual Class: TrueColor Border width: 0 Class: InputOutput Colormap: 0x20 (installed) Bit Gravity State: ForgetGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: no Map State: IsViewable Override Redirect State: yes Corners: +2854+5 -386+5 -386-1235 +2854-1235 -geometry 200x200+2854+5 Bit gravity: ForgetGravity Window gravity: NorthWestGravity Backing-store hint: NotUseful Backing-planes to be preserved: 0x Backing pixel: 0 Save-unders: No Someone wants these events: StructureNotify PropertyChange Do not propagate these events: Override redirection?: Yes No window manager hints defined Window manager hints: Window state: Skip Pager Skip Taskbar Process id: (unknown) No normal window size hints defined No zoom window size hints defined No window shape defined No border shape defined -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2012388 Title: X11 window at top-right of the screen is invisible and steals mouse clicks Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: Hardware Model: Dell Inc. Inspiron 16 Plus 7620 Firmware version: 1.5.1 CPU i7-12700H x20 GPU: Nvidia RTX3060 / MaxQ GPU: Intel Alder Lake-P Release: Lunar Lobster Architecture: AMD64 Kernel: 6.1.0-16-generic GNOME version: 44.rc Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue with window focus when windows are placed under the top-right system tray. Since it is hard to explain, I am attaching a screenshot. I am unable to click or interact with anything in the area within green rectangle. Applications affected: - Firefox (snap) - Chromium (snap) - Vivaldi Browser (deb) - Mattermost (snap) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~rc-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 20:35:05 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-23 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44~rc-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991022] Re: Service activation via Systemd socket
** Description changed: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. - [Rationale] + [Impact] It's relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. - And then, + That can be done by implementing the action of the speech dispatcher + service via a Systemd socket: > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] - The changes are already merged upstream[2], but still not released. + The changes are already merged upstream[21][22][23], but still not + released. I have built and installed the package in Mantic and verified that running spd-say from inside a snap causes the host's dispatcher to spawn - and emit sound — see 'Reproduction case' for more details. + and emit sound — see 'Test case' for more details. This has also been + verified in Jammy by Lissyx[3] and there is a merge proposal[4] for the + Firefox snap that assumes the incorporation of this delta in speech- + dispatcher. - The installed socket needs to be started manually to function correctly, - or else the system needs to be rebooted. + Note: Either the installed socket needs to be started manually to + function correctly or the system needs to be rebooted. - [Reproduction case] + [Test case] - Install the proposed speech-dispatcher from the PPA[3] and the snap[4] - with spd-say. Then, + Install the proposed speech-dispatcher and the snap[5] containing spd- + say. Then, - systemctl start --user speech-dispatcher.socket - snap run --shell geheim - $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi + systemctl start --user speech-dispatcher.socket + snap run --shell geheim + $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi - [1] https://github.com/brailcom/speechd/issues/335 - [2] https://github.com/brailcom/speechd/pull/763 - [3] https://launchpad.net/~nteodosio/+archive/ubuntu/rebuilds/+build/26035882 - [4] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 + [Regression potential] + + If the socket communication were not working (e.g. connection refused), + then this would result in text-to-speech failing, even for a not + sandboxed program. + + Do note, however, that if the socket were not available for whatever + reason (e.g. the user didn't start it manually nor rebooted), then + thesd_listen_fds(0) >= 1 would be false and no regression would be + observed, as then the program would fallback to its usual operation. + + [1] https://github.com/brailcom/speechd/issues/335 + [21] https://github.com/brailcom/speechd/pull/763 + [22] https://github.com/brailcom/speechd/pull/776 + [23] https://github.com/brailcom/speechd/pull/817 + [3] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html + [4] https://github.com/canonical/firefox-snap/pull/12 + [5] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: Service activation via Systemd socket Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Focal: New Status in speech-dispatcher source package in Jammy: New Status in speech-dispatcher source package in Kinetic: New Status in speech-dispatcher source package in Lunar: New Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Impact] It's relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private"
[Desktop-packages] [Bug 38513] Re: autocomplete=off should yield a one-time informational dialog
** Changed in: firefox Importance: Wishlist => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/38513 Title: autocomplete=off should yield a one-time informational dialog Status in Mozilla Firefox: Won't Fix Status in firefox package in Ubuntu: Won't Fix Bug description: I am perfectly capable of telling how secure my computer is. Firefox honors site designer's requests to not allow autocomplete (password saving) on a given form field. This is a bug, not a feature. I read some rumors about banking sites threatening to block Firefox if it didn't honor autocomplete=off. Bowing to that pressure is unacceptable. At the very least, there should be an option (even if it's hidden in about:config) to disable this behavior. Also, if this behavior is going to be left, or there's going to be an option, it'd be nice if Firefox would pop-up a dialog the first time this happens: "This site has requested that browsers not save form data (e.g. usernames, passwords, etc.). [ ] Show this message when a site blocks autocompletion [OK]" Then, by default, users would see one warning about this. That way they'd know what the heck was going on instead of wondering (like I did) why Firefox isn't offering to save the password. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/38513/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012388] Re: X11 window at top-right of the screen is invisible and steals mouse clicks
Hi Daniel, well you are 100% right. We tested with a German friend the following: 1. Ubuntu 23.04 with gnome-shell-extension-appindicator ONLY 2. Ubuntu 23.04 with AnyDesk running only 3. Ubuntu 23.04 without both. Only by removing BOTH did it work correctly. There is however a weird behavior also where, when you click the system bars at the top of an app, they do not get selected. you need to drag the windows for them to get focused. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2012388 Title: X11 window at top-right of the screen is invisible and steals mouse clicks Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: Hardware Model: Dell Inc. Inspiron 16 Plus 7620 Firmware version: 1.5.1 CPU i7-12700H x20 GPU: Nvidia RTX3060 / MaxQ GPU: Intel Alder Lake-P Release: Lunar Lobster Architecture: AMD64 Kernel: 6.1.0-16-generic GNOME version: 44.rc Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue with window focus when windows are placed under the top-right system tray. Since it is hard to explain, I am attaching a screenshot. I am unable to click or interact with anything in the area within green rectangle. Applications affected: - Firefox (snap) - Chromium (snap) - Vivaldi Browser (deb) - Mattermost (snap) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~rc-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 20:35:05 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-23 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44~rc-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991022] Re: Service activation via Systemd socket
** Also affects: speech-dispatcher (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: speech-dispatcher (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: speech-dispatcher (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: speech-dispatcher (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: speech-dispatcher (Ubuntu Focal) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: speech-dispatcher (Ubuntu Jammy) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: speech-dispatcher (Ubuntu Kinetic) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: speech-dispatcher (Ubuntu Lunar) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: speech-dispatcher (Ubuntu Focal) Importance: Undecided => High ** Changed in: speech-dispatcher (Ubuntu Jammy) Importance: Undecided => High ** Changed in: speech-dispatcher (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: speech-dispatcher (Ubuntu Lunar) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: Service activation via Systemd socket Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Focal: New Status in speech-dispatcher source package in Jammy: New Status in speech-dispatcher source package in Kinetic: New Status in speech-dispatcher source package in Lunar: New Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Rationale] It's relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. And then, > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The changes are already merged upstream[2], but still not released. I have built and installed the package in Mantic and verified that running spd-say from inside a snap causes the host's dispatcher to spawn and emit sound — see 'Reproduction case' for more details. The installed socket needs to be started manually to function correctly, or else the system needs to be rebooted. [Reproduction case] Install the proposed speech-dispatcher from the PPA[3] and the snap[4] with spd-say. Then, systemctl start --user speech-dispatcher.socket snap run --shell geheim $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi [1] https://github.com/brailcom/speechd/issues/335 [2] https://github.com/brailcom/speechd/pull/763 [3] https://launchpad.net/~nteodosio/+archive/ubuntu/rebuilds/+build/26035882 [4] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999308] Re: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox
Ok, let's try to figure thing out. Please uninstall the snap, install
the deb and next time the snap is installed back please share the output
of
1.
$ snap info firefox
2. the corresponding journal log ('-b 0' is the current system log, if you
restarted since the snap refresh date from .1 then use '-b -' where is
the number of restart since)
$ journalctl -b 0
3.
$ grep firefox /var/log/dpkg.log
(try the .1 variant of the log if there is no mention in the current one)
My guess is that unattended-upgrade or something is replacing your
firefox version by the '1:snap' version because is no feature in snapd
to 'install firefox automatically'
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1999308
Title:
Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox
Status in firefox package in Ubuntu:
Invalid
Bug description:
I have looked on various forums including the search features of
Launchpad, help.ubuntu..com, and Google for answers on this but not been
able to.
I have uninstalled the snap of firefox multiple times, installing the real
Firefox from ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/, only for a
few days later (once hours later) for snap to uninstall the real thing and
install its snap version instead.
I have tried a basic
sudo snap remove firefox
and when that didn't work
sudo snap disable firefox
sudo snap remove --purget firefox
The former should be enough - that's a direct expression of my preferences,
some thing like "You should have typed sudo snap remove --do-not-reinstall
--disable-auto-ignore-preferences firefox" would not resolve this bug.
When installing using apt-get, the correct version is being installed, and
snap afterwards does not show the presence of firefox:
Get:1 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64
xul-ext-ubufox all 3.4-0ubuntu1.17.10.1 [3,320 B]
Get:2 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main
amd64 firefox-locale-en amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [831 kB]
Get:3 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main
amd64 firefox amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [64.9 MB]
Name Version RevTracking
Publisher Notes
authy 2.2.2 12 latest/stable
twilio-authy -
bare 1.0 5 latest/stable
canonical✓ base
chromium 108.0.5359.94 2238 latest/stable
canonical✓ -
code 5235c6bb114latest/stable
vscode✓classic
core 16-2.57.6 14399 latest/stable
canonical✓ core
core18 202211032632 latest/stable
canonical✓ base
core20 202211231738 latest/stable
canonical✓ base
cups 2.4.2-4 836latest/stable
openprinting✓ -
gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 161latest/stable
canonical✓ -
gnome-3-38-20040+git.6f39565 119latest/stable
canonical✓ -
gtk-common-themes 0.1-81-g442e511 1535
latest/stable/… canonical✓ -
onlyoffice-desktopeditors 7.2.1 133latest/stable
onlyoffice✓-
snap-store 41.3-66-gfe1e325638
latest/stable/… canonical✓ -
snapd 2.57.6 17883 latest/stable
canonical✓ snapd
/var/lib/snapd/seed/snaps contains (once firefox is removed):
core18_1880.snap gnome-3-34-1804_36.snap gtk-common-themes_1506.snap
snapd_8542.snap snap-store_467.snap
https://ubuntuhandbook.org/index.php/2021/10/prevent-installing-firefox-snap-ubuntu-mate-21-10/
claims that a similar issue affects Ubuntu MATE 21.04 and the solution was
to type "sudo apt-mark manual firefox", which I have done, but that has not
resolved the problem.
I'm not here to explain why I wouldn't want the snap version, it is clearly
a bug for snap to accept a command to uninstall something and then
automatically reinstall it days later without the permission of the user,
and especially galling that it removes the real version at the same time.
I have lost data (passwords and history) because of this bug, because one
of the many faults of the snap version is that it ignores the user's real
~/.mozilla profile and creates a shadow profile instead inside of the snap
system.
Please disable this behavior. It's obnoxious, it ignores EXPLICITY stated
user preferences, and it causes the loss of data.
I am unclear on what package is
[Desktop-packages] [Bug 1999308] Re: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox
I mean, I literally cut and pasted what apt-get does in my bug report, how the hell did you conclude from that it's not "snapd or the system" and that it's a version number issue from that? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1999308 Title: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox Status in firefox package in Ubuntu: Invalid Bug description: I have looked on various forums including the search features of Launchpad, help.ubuntu..com, and Google for answers on this but not been able to. I have uninstalled the snap of firefox multiple times, installing the real Firefox from ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/, only for a few days later (once hours later) for snap to uninstall the real thing and install its snap version instead. I have tried a basic sudo snap remove firefox and when that didn't work sudo snap disable firefox sudo snap remove --purget firefox The former should be enough - that's a direct expression of my preferences, some thing like "You should have typed sudo snap remove --do-not-reinstall --disable-auto-ignore-preferences firefox" would not resolve this bug. When installing using apt-get, the correct version is being installed, and snap afterwards does not show the presence of firefox: Get:1 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 xul-ext-ubufox all 3.4-0ubuntu1.17.10.1 [3,320 B] Get:2 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 firefox-locale-en amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [831 kB] Get:3 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 firefox amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [64.9 MB] Name Version RevTracking Publisher Notes authy 2.2.2 12 latest/stable twilio-authy - bare 1.0 5 latest/stable canonical✓ base chromium 108.0.5359.94 2238 latest/stable canonical✓ - code 5235c6bb114latest/stable vscode✓classic core 16-2.57.6 14399 latest/stable canonical✓ core core18 202211032632 latest/stable canonical✓ base core20 202211231738 latest/stable canonical✓ base cups 2.4.2-4 836latest/stable openprinting✓ - gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 161latest/stable canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - onlyoffice-desktopeditors 7.2.1 133latest/stable onlyoffice✓- snap-store 41.3-66-gfe1e325638 latest/stable/… canonical✓ - snapd 2.57.6 17883 latest/stable canonical✓ snapd /var/lib/snapd/seed/snaps contains (once firefox is removed): core18_1880.snap gnome-3-34-1804_36.snap gtk-common-themes_1506.snap snapd_8542.snap snap-store_467.snap https://ubuntuhandbook.org/index.php/2021/10/prevent-installing-firefox-snap-ubuntu-mate-21-10/ claims that a similar issue affects Ubuntu MATE 21.04 and the solution was to type "sudo apt-mark manual firefox", which I have done, but that has not resolved the problem. I'm not here to explain why I wouldn't want the snap version, it is clearly a bug for snap to accept a command to uninstall something and then automatically reinstall it days later without the permission of the user, and especially galling that it removes the real version at the same time. I have lost data (passwords and history) because of this bug, because one of the many faults of the snap version is that it ignores the user's real ~/.mozilla profile and creates a shadow profile instead inside of the snap system. Please disable this behavior. It's obnoxious, it ignores EXPLICITY stated user preferences, and it causes the loss of data. I am unclear on what package is causing the behavior so for now marking it against Firefox, but it could be against some other piece of infrastructure related to snap: affects ubuntu/firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1999308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More
[Desktop-packages] [Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)
Logged out, rebooted, made sure all packages are up-to-date, none of it made a difference. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2013216 Title: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: Single clicking the title bar of windows without a complex title bar (namely a title bar with additional buttons besides the close/maximinze/minimize) does not transfer focus to them. Reproduction recipe: 1. Open gnome-terminal. 2. Run xedit. 3. Focus gnome-terminal. 4. Click Xedit's title bar. Expected: Xedit has focus. Observed: gnome-terminal retains focus. . 5. Focus Xedit. 6. Click gnome-terminal's title bar. Expected and observed: Xedit relinquishes focus and gnome-terminal gets focus. I can reproduce this in my main, up to date Lunar system in Xorg and also in a virtual machine with the 2023-03-24 09:02 iso (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop- amd64.iso). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 11:53:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-16 (316 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-2ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)
> This bug is not fixed. Still happening for me in Xorg on Mantic. The fix works for me (mutter 44.1-1ubuntu1). Did you log out? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2013216 Title: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: Single clicking the title bar of windows without a complex title bar (namely a title bar with additional buttons besides the close/maximinze/minimize) does not transfer focus to them. Reproduction recipe: 1. Open gnome-terminal. 2. Run xedit. 3. Focus gnome-terminal. 4. Click Xedit's title bar. Expected: Xedit has focus. Observed: gnome-terminal retains focus. . 5. Focus Xedit. 6. Click gnome-terminal's title bar. Expected and observed: Xedit relinquishes focus and gnome-terminal gets focus. I can reproduce this in my main, up to date Lunar system in Xorg and also in a virtual machine with the 2023-03-24 09:02 iso (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop- amd64.iso). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 11:53:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-16 (316 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-2ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999308] Re: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox
> Indeed, the process for fixing this I should stress that by this I mean "the process for temporarily fixing this". The system will still install the unwanted Snap version in the background at a later date. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1999308 Title: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox Status in firefox package in Ubuntu: Invalid Bug description: I have looked on various forums including the search features of Launchpad, help.ubuntu..com, and Google for answers on this but not been able to. I have uninstalled the snap of firefox multiple times, installing the real Firefox from ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/, only for a few days later (once hours later) for snap to uninstall the real thing and install its snap version instead. I have tried a basic sudo snap remove firefox and when that didn't work sudo snap disable firefox sudo snap remove --purget firefox The former should be enough - that's a direct expression of my preferences, some thing like "You should have typed sudo snap remove --do-not-reinstall --disable-auto-ignore-preferences firefox" would not resolve this bug. When installing using apt-get, the correct version is being installed, and snap afterwards does not show the presence of firefox: Get:1 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 xul-ext-ubufox all 3.4-0ubuntu1.17.10.1 [3,320 B] Get:2 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 firefox-locale-en amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [831 kB] Get:3 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 firefox amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [64.9 MB] Name Version RevTracking Publisher Notes authy 2.2.2 12 latest/stable twilio-authy - bare 1.0 5 latest/stable canonical✓ base chromium 108.0.5359.94 2238 latest/stable canonical✓ - code 5235c6bb114latest/stable vscode✓classic core 16-2.57.6 14399 latest/stable canonical✓ core core18 202211032632 latest/stable canonical✓ base core20 202211231738 latest/stable canonical✓ base cups 2.4.2-4 836latest/stable openprinting✓ - gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 161latest/stable canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - onlyoffice-desktopeditors 7.2.1 133latest/stable onlyoffice✓- snap-store 41.3-66-gfe1e325638 latest/stable/… canonical✓ - snapd 2.57.6 17883 latest/stable canonical✓ snapd /var/lib/snapd/seed/snaps contains (once firefox is removed): core18_1880.snap gnome-3-34-1804_36.snap gtk-common-themes_1506.snap snapd_8542.snap snap-store_467.snap https://ubuntuhandbook.org/index.php/2021/10/prevent-installing-firefox-snap-ubuntu-mate-21-10/ claims that a similar issue affects Ubuntu MATE 21.04 and the solution was to type "sudo apt-mark manual firefox", which I have done, but that has not resolved the problem. I'm not here to explain why I wouldn't want the snap version, it is clearly a bug for snap to accept a command to uninstall something and then automatically reinstall it days later without the permission of the user, and especially galling that it removes the real version at the same time. I have lost data (passwords and history) because of this bug, because one of the many faults of the snap version is that it ignores the user's real ~/.mozilla profile and creates a shadow profile instead inside of the snap system. Please disable this behavior. It's obnoxious, it ignores EXPLICITY stated user preferences, and it causes the loss of data. I am unclear on what package is causing the behavior so for now marking it against Firefox, but it could be against some other piece of infrastructure related to snap: affects ubuntu/firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1999308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
Re: [Desktop-packages] [Bug 1999308] Re: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox
> if you remove the snap, it's not being installed back by snapd or the system This is clearly untrue. > - the issue there is that users do install a firefox deb version which is older than the 1:1snap version from the archive. Apt does what is the standard behavior next time you install available updates, it replaces an outdated version by a newer one. The newer version is the archive special package which install the snap, so you get back the snap If it were the case, then apt-get update / apt-get upgrade (or just the regular system update tool) would be installing the 1:1snap version. But that isn't true, the Snap is being reinstalled in the background at an unpredictable time. apt-get does not "update" the package to the bogus, removed, package. Indeed, the process for fixing this (minus the lost data) is apt-get remove firefox followed by apt-get install firefox. Also the "buggy deb" you're referring to is the one from the official Mozilla Team PPA, https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/ It sounds as if there's a misunderstanding here of exactly what's going on. Can this ticket be re-opened please? On Mon, May 22, 2023 at 8:51 AM Sebastien Bacher <1999...@bugs.launchpad.net> wrote: > Details of why that's not a bug > > - Ubuntu decided to default to firefox as a snap and turned the deb to > an 'utility' package providing some of the system gluing and installing > the snap. The package uses a '1:1snap' version version '1:' is an Debian > epoch (which means that version is going to be considered newer than any > other version not using it) > > - if you remove the snap, it's not being installed back by snapd or the > system > > - the issue there is that users do install a firefox deb version which > is older than the 1:1snap version from the archive. Apt does what is the > standard behavior next time you install available updates, it replaces > an outdated version by a newer one. The newer version is the archive > special package which install the snap, so you get back the snap > > > The problem there is that people install a deb with a 'buggy' version for > what they try to achieve, if you want that deb to stay you need to use a > version newer than the archive one. Or to use apt pinning as described in > previous comment to hold updates. Or install firefox from the upstream > tarball instead of using a deb... > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1999308 > > Title: > Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox > > Status in firefox package in Ubuntu: > Invalid > > Bug description: >I have looked on various forums including the search features of > Launchpad, help.ubuntu..com, and Google for answers on this but not been > able to. > > I have uninstalled the snap of firefox multiple times, installing the > real > Firefox from ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/, only for > a > few days later (once hours later) for snap to uninstall the real thing > and > install its snap version instead. > > I have tried a basic > sudo snap remove firefox > > and when that didn't work > sudo snap disable firefox > sudo snap remove --purget firefox > > The former should be enough - that's a direct expression of my > preferences, > some thing like "You should have typed sudo snap remove > --do-not-reinstall > --disable-auto-ignore-preferences firefox" would not resolve this bug. > > When installing using apt-get, the correct version is being installed, > and > snap afterwards does not show the presence of firefox: > > Get:1 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 > xul-ext-ubufox all 3.4-0ubuntu1.17.10.1 [3,320 B] > Get:2 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main > amd64 firefox-locale-en amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [831 kB] > Get:3 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main > amd64 firefox amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [64.9 MB] > > Name Version RevTracking > Publisher Notes > authy 2.2.2 12 > latest/stable > twilio-authy - > bare 1.0 5 > latest/stable > canonical✓ base > chromium 108.0.5359.94 2238 > latest/stable > canonical✓ - > code 5235c6bb114 > latest/stable > vscode✓classic > core 16-2.57.6 14399 > latest/stable > canonical✓ core > core18 202211032632 > latest/stable > canonical✓ base > core20 202211231738 > latest/stable > canonical✓ base > cups 2.4.2-4 836 >
[Desktop-packages] [Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)
This bug is not fixed. Still happening for me in Xorg on Mantic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2013216 Title: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: Single clicking the title bar of windows without a complex title bar (namely a title bar with additional buttons besides the close/maximinze/minimize) does not transfer focus to them. Reproduction recipe: 1. Open gnome-terminal. 2. Run xedit. 3. Focus gnome-terminal. 4. Click Xedit's title bar. Expected: Xedit has focus. Observed: gnome-terminal retains focus. . 5. Focus Xedit. 6. Click gnome-terminal's title bar. Expected and observed: Xedit relinquishes focus and gnome-terminal gets focus. I can reproduce this in my main, up to date Lunar system in Xorg and also in a virtual machine with the 2023-03-24 09:02 iso (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop- amd64.iso). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 11:53:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-16 (316 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-2ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)
What do I do about the fact that I am unable to edit the status of the bug to indicate that it is not fixed? File a new bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2013216 Title: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: Single clicking the title bar of windows without a complex title bar (namely a title bar with additional buttons besides the close/maximinze/minimize) does not transfer focus to them. Reproduction recipe: 1. Open gnome-terminal. 2. Run xedit. 3. Focus gnome-terminal. 4. Click Xedit's title bar. Expected: Xedit has focus. Observed: gnome-terminal retains focus. . 5. Focus Xedit. 6. Click gnome-terminal's title bar. Expected and observed: Xedit relinquishes focus and gnome-terminal gets focus. I can reproduce this in my main, up to date Lunar system in Xorg and also in a virtual machine with the 2023-03-24 09:02 iso (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop- amd64.iso). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 11:53:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-16 (316 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-2ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999308] Re: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox
Details of why that's not a bug - Ubuntu decided to default to firefox as a snap and turned the deb to an 'utility' package providing some of the system gluing and installing the snap. The package uses a '1:1snap' version version '1:' is an Debian epoch (which means that version is going to be considered newer than any other version not using it) - if you remove the snap, it's not being installed back by snapd or the system - the issue there is that users do install a firefox deb version which is older than the 1:1snap version from the archive. Apt does what is the standard behavior next time you install available updates, it replaces an outdated version by a newer one. The newer version is the archive special package which install the snap, so you get back the snap The problem there is that people install a deb with a 'buggy' version for what they try to achieve, if you want that deb to stay you need to use a version newer than the archive one. Or to use apt pinning as described in previous comment to hold updates. Or install firefox from the upstream tarball instead of using a deb... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1999308 Title: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox Status in firefox package in Ubuntu: Invalid Bug description: I have looked on various forums including the search features of Launchpad, help.ubuntu..com, and Google for answers on this but not been able to. I have uninstalled the snap of firefox multiple times, installing the real Firefox from ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/, only for a few days later (once hours later) for snap to uninstall the real thing and install its snap version instead. I have tried a basic sudo snap remove firefox and when that didn't work sudo snap disable firefox sudo snap remove --purget firefox The former should be enough - that's a direct expression of my preferences, some thing like "You should have typed sudo snap remove --do-not-reinstall --disable-auto-ignore-preferences firefox" would not resolve this bug. When installing using apt-get, the correct version is being installed, and snap afterwards does not show the presence of firefox: Get:1 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 xul-ext-ubufox all 3.4-0ubuntu1.17.10.1 [3,320 B] Get:2 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 firefox-locale-en amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [831 kB] Get:3 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 firefox amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [64.9 MB] Name Version RevTracking Publisher Notes authy 2.2.2 12 latest/stable twilio-authy - bare 1.0 5 latest/stable canonical✓ base chromium 108.0.5359.94 2238 latest/stable canonical✓ - code 5235c6bb114latest/stable vscode✓classic core 16-2.57.6 14399 latest/stable canonical✓ core core18 202211032632 latest/stable canonical✓ base core20 202211231738 latest/stable canonical✓ base cups 2.4.2-4 836latest/stable openprinting✓ - gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 161latest/stable canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - onlyoffice-desktopeditors 7.2.1 133latest/stable onlyoffice✓- snap-store 41.3-66-gfe1e325638 latest/stable/… canonical✓ - snapd 2.57.6 17883 latest/stable canonical✓ snapd /var/lib/snapd/seed/snaps contains (once firefox is removed): core18_1880.snap gnome-3-34-1804_36.snap gtk-common-themes_1506.snap snapd_8542.snap snap-store_467.snap https://ubuntuhandbook.org/index.php/2021/10/prevent-installing-firefox-snap-ubuntu-mate-21-10/ claims that a similar issue affects Ubuntu MATE 21.04 and the solution was to type "sudo apt-mark manual firefox", which I have done, but that has not resolved the problem. I'm not here to explain why I wouldn't want the snap version, it is clearly a bug for snap to accept a command to uninstall something and then automatically reinstall it days later without the permission of the user, and especially
[Desktop-packages] [Bug 2020362] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2020362/+attachment/5674702/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2020362 Title: Gnome notifies keyboard battery is low but actually mouse battery is low Status in gnome-settings-daemon package in Ubuntu: New Bug description: Gnome notifies keyboard battery is low but when I open energy settings dialogue it tells that is the mouse battery is low. The keyboard battery is full. Expected behaviour: Gnome notifies 'mouse' battery is low --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-12 (494 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-settings-daemon 44.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-27 (24 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2020362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020362] Re: Gnome notifies keyboard battery is low but actually mouse battery is low
** Attachment added: "Captura de tela de 2023-05-22 09-18-07.png" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2020362/+attachment/5674699/+files/Captura%20de%20tela%20de%202023-05-22%2009-18-07.png ** Tags added: apport-collected lunar wayland-session ** Description changed: Gnome notifies keyboard battery is low but when I open energy settings dialogue it tells that is the mouse battery is low. The keyboard battery is full. Expected behaviour: Gnome notifies 'mouse' battery is low + --- + ProblemType: Bug + ApportVersion: 2.26.1-0ubuntu2 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 23.04 + InstallationDate: Installed on 2022-01-12 (494 days ago) + InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) + Package: gnome-settings-daemon 44.0-1ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 + Tags: lunar wayland-session + Uname: Linux 6.2.0-20-generic x86_64 + UpgradeStatus: Upgraded to lunar on 2023-04-27 (24 days ago) + UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2020362 Title: Gnome notifies keyboard battery is low but actually mouse battery is low Status in gnome-settings-daemon package in Ubuntu: New Bug description: Gnome notifies keyboard battery is low but when I open energy settings dialogue it tells that is the mouse battery is low. The keyboard battery is full. Expected behaviour: Gnome notifies 'mouse' battery is low --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-12 (494 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-settings-daemon 44.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-27 (24 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2020362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020362] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2020362/+attachment/5674700/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2020362 Title: Gnome notifies keyboard battery is low but actually mouse battery is low Status in gnome-settings-daemon package in Ubuntu: New Bug description: Gnome notifies keyboard battery is low but when I open energy settings dialogue it tells that is the mouse battery is low. The keyboard battery is full. Expected behaviour: Gnome notifies 'mouse' battery is low --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-12 (494 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-settings-daemon 44.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-27 (24 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2020362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020362] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2020362/+attachment/5674701/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2020362 Title: Gnome notifies keyboard battery is low but actually mouse battery is low Status in gnome-settings-daemon package in Ubuntu: New Bug description: Gnome notifies keyboard battery is low but when I open energy settings dialogue it tells that is the mouse battery is low. The keyboard battery is full. Expected behaviour: Gnome notifies 'mouse' battery is low --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-12 (494 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-settings-daemon 44.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-27 (24 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2020362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020362] [NEW] Gnome notifies keyboard battery is low but actually mouse battery is low
Public bug reported: Gnome notifies keyboard battery is low but when I open energy settings dialogue it tells that is the mouse battery is low. The keyboard battery is full. Expected behaviour: Gnome notifies 'mouse' battery is low --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-12 (494 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-settings-daemon 44.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-27 (24 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2020362 Title: Gnome notifies keyboard battery is low but actually mouse battery is low Status in gnome-settings-daemon package in Ubuntu: New Bug description: Gnome notifies keyboard battery is low but when I open energy settings dialogue it tells that is the mouse battery is low. The keyboard battery is full. Expected behaviour: Gnome notifies 'mouse' battery is low --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-01-12 (494 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-settings-daemon 44.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-27 (24 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2020362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017976] Re: [SRU] libreoffice 7.5.3 for lunar
Upgraded libreoffice from 4:7.5.2-0ubuntu1 to 4:7.5.3-0ubuntu0.23.04.1 from lunar-proposed in a clean and up-to-date lunar amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice. ** Tags removed: verification-needed verification-needed-lunar ** Tags added: verification-done verification-done-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2017976 Title: [SRU] libreoffice 7.5.3 for lunar Status in libreoffice package in Ubuntu: Fix Committed Status in libreoffice source package in Lunar: Fix Committed Status in libreoffice source package in Mantic: Fix Committed Bug description: [Impact] * LibreOffice 7.5.3 is in its third bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.3_release * Version 7.5.2 is currently released in lunar. For a list of fixed bugs compared to 7.5.2 see the list of bugs fixed in the release candidates of 7.5.3 (that's a total of 119 bugs): https://wiki.documentfoundation.org/Releases/7.5.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.3/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1277/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/14726196/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230428_091914_c1745@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230428_145808_db4a8@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230428_112634_ff879@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230428_092959_ffca8@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230428_214513_ee240@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 119 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2017976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2018600] Re: [SRU] libreoffice 7.4.7 for kinetic
Upgraded libreoffice from 1:7.4.6-0ubuntu0.22.10.1 to 1:7.4.7-0ubuntu0.22.10.1 from kinetic-proposed in a clean and up-to-date kinetic amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice. ** Tags removed: verification-needed verification-needed-kinetic ** Tags added: verification-done verification-done-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2018600 Title: [SRU] libreoffice 7.4.7 for kinetic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Kinetic: Fix Committed Bug description: [Impact] * LibreOffice 7.4.7 is in its seventh bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.7_release * Version 7.4.6 is currently released in kinetic. For a list of fixed bugs compared to 7.4.6 see the list of bugs fixed in the release candidates of 7.4.7 (that's a total of 73 bugs): https://wiki.documentfoundation.org/Releases/7.4.7/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.4.7/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1827/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/14734942/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/amd64/libr/libreoffice/20230504_151518_a9360@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/arm64/libr/libreoffice/20230504_200542_1dfdd@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/armhf/libr/libreoffice/20230505_142551_a6b85@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/ppc64el/libr/libreoffice/20230504_161525_fdb04@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic-ricotz-ppa/kinetic/s390x/libr/libreoffice/20230506_054745_25b3f@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 73 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2018600/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973470] Re: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic
This bug was fixed in the package apport - 2.20.11-0ubuntu82.5 --- apport (2.20.11-0ubuntu82.5) jammy; urgency=medium * apport-gtk: Exclude trailing dot from URL links (LP: #1978301) * apport-bug: Add /snap/bin to PATH for Firefox snap on Lubuntu (LP: #1973470) * test: - Clear environment for test_run_as_real_user_no_sudo - Fix GTK UI tests if whoopsie.path is disabled - tests: Fix GTK UI race condition and reduce timeout again, saving five minutes test execution time (LP: #1780767) - tests: Fix race in tests for run_report_bug() -- Benjamin Drung Fri, 14 Apr 2023 01:08:26 +0200 ** Changed in: apport (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1973470 Title: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in xdg-utils package in Ubuntu: Invalid Status in apport source package in Jammy: Fix Released Status in xdg-utils source package in Jammy: New Bug description: Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD. While reporting Bug #1973469, I discovered that ubuntu-bug was unable to open Firefox at the very end of the process. Sadly, I closed the terminal window that contained the initial error, but I was able to easily reproduce it reporting this bug. The full console output of "ubuntu-bug apport" on Lubuntu Kinetic is: *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (5.1 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 94% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?' I am unsure if this problem is in Apport or Lubuntu. ubuntu-bug works just fine for me on Ubuntu Kinetic, but not on Lubuntu. I suspect this is due to the Snap version of Firefox, but I don't know for sure. Since ubuntu-bug is what gave me the error, I'm filing this against Apport. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport 2.20.11-0ubuntu82 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: LXQt Date: Sun May 15 11:41:07 2022 LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1973470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973470] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1973470 Title: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in xdg-utils package in Ubuntu: Invalid Status in apport source package in Jammy: Fix Released Status in xdg-utils source package in Jammy: New Bug description: Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD. While reporting Bug #1973469, I discovered that ubuntu-bug was unable to open Firefox at the very end of the process. Sadly, I closed the terminal window that contained the initial error, but I was able to easily reproduce it reporting this bug. The full console output of "ubuntu-bug apport" on Lubuntu Kinetic is: *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (5.1 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 94% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?' I am unsure if this problem is in Apport or Lubuntu. ubuntu-bug works just fine for me on Ubuntu Kinetic, but not on Lubuntu. I suspect this is due to the Snap version of Firefox, but I don't know for sure. Since ubuntu-bug is what gave me the error, I'm filing this against Apport. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport 2.20.11-0ubuntu82 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: LXQt Date: Sun May 15 11:41:07 2022 LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1973470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019940] Re: Directly manipulating NetworkManager keyfiles
Thank you @seth-arnold! I've updated the affected packages of this bug and (bug #2019939) accordingly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2019940 Title: Directly manipulating NetworkManager keyfiles Status in augeas package in Ubuntu: New Status in calamares package in Ubuntu: New Status in cloud-init package in Ubuntu: Invalid Status in cruft package in Ubuntu: Won't Fix Status in cruft-ng package in Ubuntu: New Status in dracut package in Ubuntu: New Status in forensic-artifacts package in Ubuntu: New Status in guestfs-tools package in Ubuntu: New Status in guix package in Ubuntu: New Status in ltsp package in Ubuntu: Invalid Status in netcfg package in Ubuntu: Won't Fix Status in netplan.io package in Ubuntu: Invalid Status in network-manager package in Ubuntu: New Status in refpolicy package in Ubuntu: New Status in sosreport package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in uhd package in Ubuntu: New Status in vagrant package in Ubuntu: New Bug description: The affected packages can manipulate NetworkManager keyfiles directly on disk, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019939] Re: Outdated documentation about NetworkManager keyfiles
** Also affects: scap-security-guide (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/2019939 Title: Outdated documentation about NetworkManager keyfiles Status in debian-handbook package in Ubuntu: New Status in dhcpcanon package in Ubuntu: New Status in fai package in Ubuntu: New Status in gnome-user-docs package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in network-manager-l2tp package in Ubuntu: New Status in scap-security-guide package in Ubuntu: New Status in wifi-qr package in Ubuntu: New Bug description: The affected packages contain documentation or examples about NetworkManager keyfiles, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-handbook/+bug/2019939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019940] Re: Directly manipulating NetworkManager keyfiles
cruft is not part of Ubuntu anymore (got dropped post Kinetic) ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Also affects: cruft (Ubuntu) Importance: Undecided Status: New ** Changed in: cruft (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2019940 Title: Directly manipulating NetworkManager keyfiles Status in augeas package in Ubuntu: New Status in calamares package in Ubuntu: New Status in cloud-init package in Ubuntu: Invalid Status in cruft package in Ubuntu: Won't Fix Status in cruft-ng package in Ubuntu: New Status in dracut package in Ubuntu: New Status in forensic-artifacts package in Ubuntu: New Status in guestfs-tools package in Ubuntu: New Status in guix package in Ubuntu: New Status in ltsp package in Ubuntu: Invalid Status in netcfg package in Ubuntu: Won't Fix Status in netplan.io package in Ubuntu: Invalid Status in network-manager package in Ubuntu: New Status in refpolicy package in Ubuntu: New Status in sosreport package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in uhd package in Ubuntu: New Status in vagrant package in Ubuntu: New Bug description: The affected packages can manipulate NetworkManager keyfiles directly on disk, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019940] Re: Directly manipulating NetworkManager keyfiles
** Changed in: netplan.io (Ubuntu) Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2019940 Title: Directly manipulating NetworkManager keyfiles Status in augeas package in Ubuntu: New Status in calamares package in Ubuntu: New Status in cloud-init package in Ubuntu: Invalid Status in cruft-ng package in Ubuntu: New Status in dracut package in Ubuntu: New Status in forensic-artifacts package in Ubuntu: New Status in guestfs-tools package in Ubuntu: New Status in guix package in Ubuntu: New Status in ltsp package in Ubuntu: Invalid Status in netcfg package in Ubuntu: Won't Fix Status in netplan.io package in Ubuntu: Invalid Status in network-manager package in Ubuntu: New Status in refpolicy package in Ubuntu: New Status in sosreport package in Ubuntu: New Status in uhd package in Ubuntu: New Status in vagrant package in Ubuntu: New Bug description: The affected packages can manipulate NetworkManager keyfiles directly on disk, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2018455] Re: gnome-shell exits after screen lock / unlock & login segfault libmutter-12.so.0.0.0 in Ubuntu 23.04 on Lenovo X1 Carbon Gen10
The above crash was unreportable because at least one package was out of date. Please open a Terminal and run: sudo apt update sudo apt full-upgrade Then reboot and reproduce the crash again. ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Bug watch removed: gitlab.gnome.org/GNOME/mutter/-/issues #2398 https://gitlab.gnome.org/GNOME/mutter/-/issues/2398 ** Tags added: lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2018455 Title: gnome-shell exits after screen lock / unlock & login segfault libmutter-12.so.0.0.0 in Ubuntu 23.04 on Lenovo X1 Carbon Gen10 Status in mutter package in Ubuntu: Incomplete Bug description: The issue is happening 9 out of 10 times. It is hard to get a crash dump in /var/crash during this error though, but I found one from few days ago. Looks like should be relevant. I've reported it, see OOPS ID: b68253a2-ea4c-11ed-af33-fa163e55efd0 Laptop: Lenovo ThinkPad X1 Carbon Gen 10, model 21CB007WCK root@x1:~# uname -a Linux x1 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux To reproduce: 1. Win+L to lock the session 2. Screen turns black as expected 3. Login back to your session 4. Welcome to the new & clean session... all unsaved work is lost! 5. see gnome-shell segfault in libmutter-12.so in dmesg root@x1:~# dmesg -T |grep segf [Thu May 4 17:45:04 2023] gnome-shell[2554]: segfault at ff78 ip 7f3d10961115 sp 7ffd72b85f78 error 5 in libmutter-12.so.0.0.0[7f3d1084a000+13d000] likely on CPU 0 (core 0, socket 0) [Fri May 5 14:09:43 2023] gnome-shell[24568]: segfault at 11 ip 7f4c14161119 sp 7ffd4590de28 error 4 in libmutter-12.so.0.0.0[7f4c1404a000+13d000] likely on CPU 9 (core 17, socket 0) Logs from "ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash" command May 04 09:24:31 x1 systemd[1]: Started whoopsie.service - crash report submission. May 04 09:24:31 x1 whoopsie[54307]: [09:24:31] Using lock path: /var/lock/whoopsie/lock May 04 09:24:31 x1 whoopsie[54307]: [09:24:31] Parsing /var/crash/_usr_bin_gnome-shell.1000.crash. May 04 09:24:31 x1 whoopsie[54307]: [09:24:31] Uploading /var/crash/_usr_bin_gnome-shell.1000.crash. May 04 09:24:32 x1 whoopsie[54307]: [09:24:32] Sent; server replied with: No error May 04 09:24:32 x1 whoopsie[54307]: [09:24:32] Response code: 200 May 04 09:24:32 x1 whoopsie[54307]: [09:24:32] Reported OOPS ID b68253a2-ea4c-11ed-af33-fa163e55efd0 It was difficult to figure how to send the report in Ubuntu 23.04, previously it was just working... but with Ubuntu 23.04 there was this error: May 04 09:21:33 x1 systemd[1]: Starting apport-autoreport.service - Process error reports when automatic reporting is enabled... May 04 09:21:33 x1 systemd[1]: Started whoopsie.service - crash report submission. May 04 09:21:33 x1 whoopsie[53709]: [09:21:33] Using lock path: /var/lock/whoopsie/lock May 04 09:21:33 x1 systemd[1]: whoopsie.service: Deactivated successfully. May 04 09:21:33 x1 whoopsie-upload-all[53708]: ERROR: whoopsie.path is not enabled May 04 09:21:33 x1 systemd[1]: apport-autoreport.service: Main process exited, code=exited, status=1/FAILURE May 04 09:21:33 x1 systemd[1]: apport-autoreport.service: Failed with result 'exit-code'. May 04 09:21:33 x1 systemd[1]: Failed to start apport-autoreport.service - Process error reports when automatic reporting is enabled. Fixed by changing "Send error reports to Canonical" (in gnome control panel -> "Privacy" -> "Diagnostics") from "Automatic" to "Never" and re-running the `ubuntu-bug` command again. gnome-shell 44.0-2ubuntu3 intel-media-va-driver:amd64 23.1.2+dfsg1-1 root@x1:~# lshw -class display *-display description: VGA compatible controller product: Alder Lake-P Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 logical name: /dev/fb0 version: 0c width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb configuration: depth=32 driver=i915 latency=0 mode=1920x1200 resolution=1920,1200 visual=truecolor xres=1920 yres=1200 resources: iomemory:600-5ff iomemory:400-3ff irq:199 memory:603d00-603dff memory:40-400fff ioport:2000(size=64) memory:c-d memory:401000-4016ff memory:402000-40 root@x1:~# lshw -class multimedia *-multimedia:0 UNCLAIMED description: Multimedia controller product: Intel Corporation vendor: Intel Corporation physical id: 5 bus info: pci@:00:05.0 version: 02 width: 64 bits clock: 33MHz
[Desktop-packages] [Bug 2018525] Re: [nvidia] Intermittent loss of display
** No longer affects: xorg-server (Ubuntu) ** Package changed: nvidia-graphics-drivers-525 (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2018525 Title: [nvidia] Intermittent loss of display Status in Ubuntu: Incomplete Bug description: Screen freezes, then goes to black during a few seconds then returns to working state. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-1008.8-oem 6.1.14 Uname: Linux 6.1.0-1008-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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..07.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 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 12.1.0 (Ubuntu 12.1.0-2ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 4 17:21:47 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 5.19.0-41-generic, x86_64: installed nvidia/525.105.17, 6.1.0-1008-oem, x86_64: installed ExtraDebuggingInterest: No GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3070 Mobile / Max-Q] [10de:249d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GA104M [GeForce RTX 3070 Mobile / Max-Q] [1558:50f4] InstallationDate: Installed on 2023-01-27 (96 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Notebook NH5xVR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1008-oem root=UUID=c6e942e5-1878-4e2a-8d85-81abebd32761 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2021 dmi.bios.release: 7.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH5xVR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.3 dmi.modalias: dmi:bvnInsydeCorp.:bvr1.07.06:bd02/18/2021:br7.6:efr7.3:svnNotebook:pnNH5xVR:pvrNotApplicable:rvnNotebook:rnNH5xVR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NH5xVR dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 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:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2018525/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020127] Re: x apps fail to launch from terminal shell
I don't see any evidence of the offending line in Ubuntu 22.04 so 22.10 is also unlikely. Particularly since we've supported Wayland for quite some time now, and it works. It does sound like a manual change you made. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2020127 Title: x apps fail to launch from terminal shell Status in Ubuntu: Invalid Bug description: New upgrade to 23.04 In terminal typing xeyes, idle or other X app including ubuntu-bug fails to launch with error Invalid MIT-MAGIC-COOKIE-1 keyError: cannot open display: :0 Desktop and remote access from another machine to a shell on this host with ssh -X work correctly echo $XAUTHORITY is /home/dave/.Xauthority File exists and contains 2 cookies Clue: export XAUTHORITY=$(ls /run/user/1000/.mutter-Xwayland*) ubuntu-bug links to a working per session cookie, and I'm able to type this. Expected behaviour: display just works when an X application is started from a shell. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 18 18:44:46 2023 DistUpgraded: 2023-05-16 20:52:31,229 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: virtualbox/7.0.6, 5.19.0-42-generic, x86_64: installed virtualbox/7.0.6, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn XT [Radeon HD 7870 GHz Edition] [1002:6818] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Pitcairn XT [Radeon HD 7870 GHz Edition] [1787:2321] InstallationDate: Installed on 2021-03-06 (802 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Gigabyte Technology Co., Ltd. Z490 AORUS ELITE AC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=c3300897-9f55-4525-91f6-ac8cfbe405f3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-05-16 (1 days ago) dmi.bios.date: 08/28/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: Z490 AORUS ELITE AC dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd08/28/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnZ490AORUSELITEAC:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ490AORUSELITEAC:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Z490 MB dmi.product.name: Z490 AORUS ELITE AC dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2020127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020281] Re: unable to update
What error do you see when trying to update? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2020281 Title: unable to update Status in Ubuntu: Incomplete Bug description: won't update to jammy ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-125.141-generic 5.4.195 Uname: Linux 5.4.0-125-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None Date: Sun May 21 16:17:33 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 6000 [8086:1626] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation HD Graphics 6000 [8086:2057] InstallationDate: Installed on 2015-12-30 (2699 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-125-generic root=UUID=4040334c-a39e-4351-861e-0a64070772ca ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2015 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0352.2015.1130.1011 dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-504 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0352.2015.1130.1011:bd11/30/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr: version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3 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: Sat Jul 18 19:41:08 2020 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2020281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020286] Re: shuttering screen especely yootube with nvidia rtx 20260 super
Thanks for the bug report. Please explain in more detail what you mean by "shuttering". Perhaps by attaching a photo or video of the problem. ** Package changed: gnome-shell (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2020286 Title: shuttering screen especely yootube with nvidia rtx 20260 super Status in Ubuntu: Incomplete Bug description: after i went to free ubuntu subscription and update, using nvidia server driver metapackage from nvidia-driver-525-server (propietary) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell (not installed) ProcVersionSignature: Ubuntu 5.15.0-72.79-generic 5.15.98 Uname: Linux 5.15.0-72-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon May 22 05:22:07 2023 InstallationDate: Installed on 2020-03-22 (1155 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2020286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020277] Re: Update gnome-shell to 44.1
Series-assigned bugs should also have people assigned to them to avoid the list of release bugs growing without anyone to contact. ** Also affects: gnome-shell (Ubuntu Mantic) Importance: High Status: Fix Released ** Changed in: gnome-shell (Ubuntu Mantic) Assignee: (unassigned) => Jeremy Bícha (jbicha) ** Changed in: gnome-shell (Ubuntu Lunar) Assignee: (unassigned) => Jeremy Bícha (jbicha) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2020277 Title: Update gnome-shell to 44.1 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Lunar: Triaged Status in gnome-shell source package in Mantic: Fix Released Bug description: Impact -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020249] Re: Missing Wayland login option on NVIDIA systems - still broken
You can safely comment out those udev rules. They're only there to stop regular users from hitting these issues while Nvidia Wayland support is not production-ready: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-wayland It's likely some people will only recently have lost the Wayland login option because it was sometimes displayed by mistake until this update: https://launchpad.net/ubuntu/+source/gdm3/42.0-1ubuntu7.22.04.2 So this bug is the design we intended in April 2022, but for some only a recent change that appeared on their machine in April 2023 (after bug 2006059 was fixed). ** Changed in: gdm3 (Ubuntu) Status: New => Opinion ** Summary changed: - Missing Wayland login option on NVIDIA systems - still broken + Missing Wayland login option on NVIDIA desktops -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2020249 Title: Missing Wayland login option on NVIDIA desktops Status in gdm3 package in Ubuntu: Opinion Bug description: Ref: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968929 The symptom is that there is no Wayland option with the gear icon of the login screen. This is a reopening of the tracking bug (https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968929) for the followup from the previous attempt to fix the problem (https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/comments/37). It's a continuation of the ongoing problem of getting NVidia and Wayland to play well together. It may be that this fix didn't make it into Ubuntu 22.04.2 LTS. System: $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020249/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020183] Re: Xorg crash
Sounds like this isn't a crash (unless you find files in /var/crash). Can you provide a better summary of the problem than "Xorg crash"? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2020183 Title: Xorg crash Status in Ubuntu: Incomplete Bug description: I'm using a Docking station with two displays (1 HDMI + 1 DP) and one HDMI to the machine's port. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-72.79~20.04.1-generic 5.15.98 Uname: Linux 5.15.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip Date: Thu May 18 15:11:56 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8846] InstallationDate: Installed on 2022-08-05 (286 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: HP HP EliteBook 850 G8 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-72-generic root=/dev/mapper/elx_vg-root ro mem_sleep_default=deep noaudit noquiet nosplash sysrq_always_enabled i915.enable_guc=1 intel_idle.max_cstate=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2021 dmi.bios.release: 6.2 dmi.bios.vendor: HP dmi.bios.version: T76 Ver. 01.06.02 dmi.board.name: 8846 dmi.board.vendor: HP dmi.board.version: KBC Version 30.33.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 48.51 dmi.modalias: dmi:bvnHP:bvrT76Ver.01.06.02:bd08/12/2021:br6.2:efr48.51:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.33.00:cvnHP:ct10:cvr:sku4T9G0EC#ABB: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G8 Notebook PC dmi.product.sku: 4T9G0EC#ABB dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-08-05T12:33:01.637811 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.8 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 N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2020183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2018525] Re: [nvidia] Intermittent loss of display
Please check to see if the loss of display is: * gnome-shell crashing and being restarted (while Xorg and the apps keep running); or * A faulty monitor cable/connection. If it's just a laptop display then most likely gnome-shell is crashing so please follow https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Changed in: nvidia-graphics-drivers-525 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2018525 Title: [nvidia] Intermittent loss of display Status in nvidia-graphics-drivers-525 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Screen freezes, then goes to black during a few seconds then returns to working state. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-1008.8-oem 6.1.14 Uname: Linux 6.1.0-1008-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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..07.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 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 12.1.0 (Ubuntu 12.1.0-2ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 4 17:21:47 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 5.19.0-41-generic, x86_64: installed nvidia/525.105.17, 6.1.0-1008-oem, x86_64: installed ExtraDebuggingInterest: No GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3070 Mobile / Max-Q] [10de:249d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GA104M [GeForce RTX 3070 Mobile / Max-Q] [1558:50f4] InstallationDate: Installed on 2023-01-27 (96 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Notebook NH5xVR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1008-oem root=UUID=c6e942e5-1878-4e2a-8d85-81abebd32761 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2021 dmi.bios.release: 7.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH5xVR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.3 dmi.modalias: dmi:bvnInsydeCorp.:bvr1.07.06:bd02/18/2021:br7.6:efr7.3:svnNotebook:pnNH5xVR:pvrNotApplicable:rvnNotebook:rnNH5xVR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NH5xVR dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 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:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2018525/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()
** Changed in: gjs (Ubuntu Jammy) Assignee: Jeremy Bícha (jbicha) => Ghadi Rahme (ghadi-rahme) ** Changed in: gjs (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1974293 Title: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl() Status in gjs: Fix Released Status in OEM Priority Project: Confirmed Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: In Progress Status in gjs source package in Kinetic: Triaged Status in gjs source package in Lunar: Fix Released Status in gnome-shell package in Fedora: Confirmed Bug description: [ Impact ] gnome-shell often crashes on logout causing annoyance to the user as an error report dialog is displayed at the next login. [ Test Plan ] 1. Log into gnome-shell 2. Use gnome-shell for long enough to trigger a garbage collection cycle: Scroll the app grid and repeatedly open the calendar from the top bar for 30 seconds. 3. Log out. 4. Verify no new gnome-shell crash files appear in /var/crash/ [ Where problems could occur ] Only gnome-shell shutdown/logout is affected. [ Other Info ] https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4 https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7 Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Crash 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 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 16:06:35 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1649813447 InstallationDate: Installed on 2022-05-05 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1974293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2014136] Re: gnome-shell[957]: message repeated 2 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native
Fixed in mutter 44.1 which is now in Ubuntu 23.10 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2014136 Title: gnome-shell[957]: message repeated 2 times: [ (../src/backends/native/meta-onscreen- native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb)] Status in mutter package in Ubuntu: Fix Released Bug description: [ Impact ] Occasional messages in the system log: (../src/backends/native/meta-onscreen- native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native->gbm.next_fb) [ Test Plan ] TODO - can't remember the conditions right now. [ Where problems could occur ] Triple buffering affects all frame scheduling so any mistakes can cause high CPU usage, screen freezes and stutter. Try not to make mistakes. [ Original report ] Just got on inactivity ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 Uname: Linux 6.2.0-18-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 22:13:08 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1679944760 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/sem33 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2014136/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017137] Re: Xorg sessions on Intel GPUs stutter noticeably in 23.04
Fixed in mutter 44.1 which is now in Ubuntu 23.10 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2017137 Title: Xorg sessions on Intel GPUs stutter noticeably in 23.04 Status in mutter package in Ubuntu: Fix Released Bug description: [ Impact ] Xorg sessions on Intel GPUs stutter noticeably in 23.04 Seems like a combination of: * over-aggressive latency optimizations in the latest version of triple buffering; and * gnome-shell 44 being slightly less efficient at some operations like scrolling the app grid. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always [ Test Plan ] 1. Find a machine with an Intel GPU. 2. Log into 'Ubuntu on Xorg'. 3. Press Super+A and scroll the icon right left/right. It should be perfectly smooth like in Wayland sessions. [ Where problems could occur ] Triple buffering affects all frame scheduling so any mistakes can cause high CPU usage, screen freezes and stutter. Try not to make mistakes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2017137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017097] Re: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed
Fixed in mutter 44.1 which is now in Ubuntu 23.10 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2017097 Title: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed Status in mutter package in Ubuntu: Fix Released Bug description: [ Impact ] On a Raspberry Pi 400, GNOME Shell runs at 30 FPS unless the CPU is being stressed in which case it becomes a smooth 60 FPS. Seems like a frequency scaling issue. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always [ Test Plan ] 1. Log into the default (Wayland) session on a Raspberry Pi 4/400. 2. Set the display resolution to 1920x1080 60Hz. 3. Drag a window around and ensure it appears smooth (60Hz). [ Where problems could occur ] Triple buffering affects all frame scheduling so any mistakes can cause high CPU usage, screen freezes and stutter. Try not to make mistakes. [ Original bug ] ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Apr 20 15:13:51 2023 ImageMediaBuild: 20230417 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/2017097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012717] Re: GNOME 44 multi-monitor screen freeze when resuming from sleep
** Description changed: + [ Impact ] + + Using multiple monitors in a Wayland session, one or both may freeze + when resuming from sleep. + + [ Test Plan ] + + 1. Log into a Wayland session. + 2. Set up gnome-shell to span two monitors. + 3. Wait for the monitors to sleep. + 4. Wiggle the mouse to wake them. + 5. Move the mouse between both monitors. + 6. Verify that the mouse appears on both monitors and neither are frozen. + + [ Where problems could occur ] + + This fix affects frame scheduling so problems could always occur in the + form of other screen freezes and frame rate issues. + + [ Original report ] + Testing GNOME 44 I find it can't resume from sleep properly if two monitors are plugged in. Both monitors wake up, but one is completely frozen and the other is partially frozen (stops responding to anything but cursor movement). Using Intel graphics with two USB-C monitors. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2012717 Title: GNOME 44 multi-monitor screen freeze when resuming from sleep Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: [ Impact ] Using multiple monitors in a Wayland session, one or both may freeze when resuming from sleep. [ Test Plan ] 1. Log into a Wayland session. 2. Set up gnome-shell to span two monitors. 3. Wait for the monitors to sleep. 4. Wiggle the mouse to wake them. 5. Move the mouse between both monitors. 6. Verify that the mouse appears on both monitors and neither are frozen. [ Where problems could occur ] This fix affects frame scheduling so problems could always occur in the form of other screen freezes and frame rate issues. [ Original report ] Testing GNOME 44 I find it can't resume from sleep properly if two monitors are plugged in. Both monitors wake up, but one is completely frozen and the other is partially frozen (stops responding to anything but cursor movement). Using Intel graphics with two USB-C monitors. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2012717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1698083] Re: Maximize vertically/horizontally doesn't work (in some apps) if configured via middle-click
** Changed in: gtk+3.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1698083 Title: Maximize vertically/horizontally doesn't work (in some apps) if configured via middle-click Status in GTK+: Fix Released Status in gnome-control-center package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Triaged Bug description: Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539 In Gnome Tweak Tool you can configure vertical maximizing for: Windows > Titlebar Actions > Middle-Click However this feature seems to get ignored in Wayland sessions (it just maximizes fully instead). It only works correctly in Xorg Gnome sessions. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Thu Jun 15 14:46:04 2017 DisplayManager: lightdm InstallationDate: Installed on 2017-05-03 (43 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011251] Re: gnome-shell gets into state where clicking on window title bars doesn't raise them
*** This bug is a duplicate of bug 2013216 *** https://bugs.launchpad.net/bugs/2013216 While this was the first bug logged, we failed to notice when duplicate bug 2013216 was reported and most of the discussion has now occurred there. So we should use bug 2013216 as the primary bug. Feel free to reopen that too if you're confident that it's not fixed in Ubuntu 23.10. ** This bug has been marked a duplicate of bug 2013216 Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2011251 Title: gnome-shell gets into state where clicking on window title bars doesn't raise them Status in Mutter: Fix Released Status in mutter package in Ubuntu: New Bug description: After the most recent Lunar updates (i.e., with the newest GNOME) my gnome-shell got into a state where clicking on the title bar of a window wouldn't raise the window (or do anything else), while clicking inside the window raised it as expected. The problem went away after I rebooted. I think this may have occurred after some other aberrant behavior, specifically the shell hanging for about 30 seconds (I will file a separate bug about that), so it's possible that things were in some sort of broken state because of that and this bug isn't actually specifically about the title bar, but I thought I should file a bug report about it just in case it's something other people start seeing so we can see how frequently it's happening. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 10 16:16:22 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (1302 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 44~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2022-11-24 (106 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2011251/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2018234] Re: Window not focusing when title bar is clicked.
*** This bug is a duplicate of bug 2013216 *** https://bugs.launchpad.net/bugs/2013216 ** This bug is no longer a duplicate of bug 2011251 gnome-shell gets into state where clicking on window title bars doesn't raise them ** This bug has been marked a duplicate of bug 2013216 Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2018234 Title: Window not focusing when title bar is clicked. Status in mutter package in Ubuntu: New Bug description: When a window is partially behind another and I click on the title bar, the window I clicked on does not come forward to get focus. I have to click in the body of the window for this to happen. This only started happening when I upgraded to Ubuntu Budgie 23.04. I am running Ubuntu Budgie 23.04, Budgie desktop version 10.7.1 Running an Nvidia GP108 [GeForce GT 1030] using the nvidia-driver-525. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2018234/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807276] Re: Cannot open Onscreen Keyboard in Xorg
"Won't Fix": The upstream bug has been closed because the reporter deleted their account. And this launchpad bug has gone unanswered when more information was requested 3 years ago. If anyone continues to experience a similar issue then please report a new bug by running: ubuntu-bug gnome-shell ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1807276 Title: Cannot open Onscreen Keyboard in Xorg Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Ubuntu 18.10 / GNOME Shell 3.30.1 ALSO Ubuntu 18.04 LTS / GNOME Shell 3.28.1 Steps to reproduce on our end: - Login (Xorg as default) - Attempt to swipe up with finger from below screen RESULT: It draws a thin vertical (desktop) selection box, but no OSK - Logout - Log back in, after first hitting 'gear' button to select 'Ubuntu on Wayland' - ps -e | grep Xwayland #shows 'Xwayland' process is running - Repeat swipe up with finger from below screen RESULT: OSK shows up as expected This has been verified both in 1920x1080 as well as 3840x2160 resolutions (also with various scaling options selected) Issue is also logged upstream: https://gitlab.gnome.org/GNOME/gnome- shell/issues/839 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1807276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020225] Re: Update mutter to 44.1
** Package changed: ubuntu => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released ** Also affects: mutter (Ubuntu Mantic) Importance: Medium Status: Fix Released ** Also affects: mutter (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Lunar) Status: New => Triaged ** Changed in: mutter (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Lunar) Assignee: (unassigned) => Jeremy Bícha (jbicha) ** Changed in: mutter (Ubuntu Mantic) Assignee: (unassigned) => Jeremy Bícha (jbicha) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020225 Title: Update mutter to 44.1 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Triaged Status in mutter source package in Mantic: Fix Released Bug description: Impact -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
