[Desktop-packages] [Bug 1989844] [NEW] Quick settings changes spacing when toggling Dark Mode
Public bug reported: Quick settings changes spacing when toggling Dark Mode ** Affects: yaru-theme (Ubuntu) Importance: Low Status: New ** Tags: kinetic visual-quality ** Attachment added: "Screencast from 2022-09-16 11-55-23.webm" https://bugs.launchpad.net/bugs/1989844/+attachment/5616280/+files/Screencast%20from%202022-09-16%2011-55-23.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1989844 Title: Quick settings changes spacing when toggling Dark Mode Status in yaru-theme package in Ubuntu: New Bug description: Quick settings changes spacing when toggling Dark Mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1989844/+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 1979037] Re: Monitor numbers are almost invisible in an Ubuntu/Yaru session
** Changed in: yaru-theme (Ubuntu) Status: In Progress => Fix Released -- 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/1979037 Title: Monitor numbers are almost invisible in an Ubuntu/Yaru session Status in Yaru Theme: New Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in yaru-theme source package in Jammy: Triaged Bug description: Monitor numbers (displayed in the top left corner of each screen while in the Screen Display settings) are almost invisible in an Ubuntu/Yaru session. But they are big and bold in a GNOME (Adwaita) session. Both using Wayland. It looks like you need to have two monitors connected to test the feature. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1979037/+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 1989826] Re: cannot start lightdm gui
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1989826 Title: cannot start lightdm gui Status in lightdm package in Ubuntu: New Bug description: i installed lightdm but cannot start it manually using ubuntu 22.04.1 LTS release 22.04 codename: jammy ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lightdm 1.30.0-0ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 Date: Fri Sep 16 01:27:20 2022 InstallationDate: Installed on 2022-08-28 (18 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1989826/+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 1984167] Re: Some Yaru icons have bulging shadows
** Changed in: yaru-theme (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1984167 Title: Some Yaru icons have bulging shadows Status in Yaru Theme: Unknown Status in yaru-theme package in Ubuntu: Fix Released Bug description: Some Yaru icons have weird bulging shadows in their bottom right corners, including: terminal-app filemanager-app system-monitor-app Mostly the problem is invisible but if you add an extra drop shadow (like in the GNOME overview) or analyse the icon image in GIMP then the issue becomes visible. See screenshots attached. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1984167/+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 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)
this error still occurs in Lubuntu kinetic (daily) using snapd: Installed: 2.57.1+22.10.1 daily 20220915 (though it's working on my primary box running kinetic using the same procedures... my primary box though is heavily modified/bloated) -- 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/1951210 Title: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html) Status in libreoffice package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Committed Status in libreoffice source package in Jammy: Fix Released Status in snapd source package in Jammy: Confirmed Bug description: Ubuntu jammy live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) Opened LibreOffice Writer as random apps in QA-test. Hit F1 to call help, and all I get is an error URL: file:///tmp/lu417531j7po.tmp/NewHelp0.html --- File not found Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- Firefox opens as a snap; but it isn't accessing the data from LibreOffice. Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks- libreoffice-deb/27537 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 04:46:33 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+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 1989590] Re: Can't click on dock items if status drop-down is shown
** Summary changed: - Can't click on Dash items if status drop-down is shown + Can't click on dock items if status drop-down is shown ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- ubuntu-dock (Ubuntu) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Confirmed ** Description changed: Steps: 1. open any of the system status drop-downs - 2. click on any Dash item + 2. click on any app icon in the Ubuntu Dock Expected: 1. the system status drop-down goes away - 2. the clicked item is activated Current: 1. nothing happens ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 16:49:59 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (13 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: - TERM=screen-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=pl_PL.UTF-8 - SHELL=/bin/zsh + TERM=screen-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=pl_PL.UTF-8 + SHELL=/bin/zsh RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Triaged -- 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/1989590 Title: Can't click on dock items if status drop-down is shown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: Steps: 1. open any of the system status drop-downs 2. click on any app icon in the Ubuntu Dock Expected: 1. the system status drop-down goes away Current: 1. nothing happens ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 16:49:59 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (13 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1989590/+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 1870597] Re: libinput says "your system is too slow"
Please try Ubuntu 22.04 when you can because it is much faster: https://ubuntu.com/download/desktop -- 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/1870597 Title: libinput says "your system is too slow" Status in GNOME Shell: Unknown Status in libinput: Fix Released Status in Linux: Confirmed Status in libinput package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm- x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870597/+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 1965123] Re: Active launchers area pixels (corners) missing
It looks like we're caching an incomplete rendering (missing the corner textures), but only sometimes. From what I recall this code is entirely in gnome-shell (I think I touched it last) but I don't know why only ubuntu-dock would have the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1965123 Title: Active launchers area pixels (corners) missing Status in Dash to dock: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 development branch @ 16/03/2022 after yesterdays updates to gnome 42 beta the docks area around the active launcher is missing 4 pixels in the corners when hovering mouse over them switching to another active launchers can be reproduced non-active area around launchers does not suffer this bug ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 12:55:20 2022 PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1965123/+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 1898395] Re: [nvidia] [amdgpu] Problem with external monitor
** Tags removed: multi-gpu ** Tags added: multigpu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1898395 Title: [nvidia] [amdgpu] Problem with external monitor Status in nvidia-graphics-drivers-450 package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: So, I installed Ubuntu 20.04 on my laptop with Ryzen 7 4800h processor and Nvidia gtx 1650 graphic card.. But i wasn't able to make my external monitor work.. At first it wasn't even recognized, but after I updated kernel to version 5.7.1 and with(only with latest) nvidia drivers 450 it recognized external monitor and I get options when I press SUPER KEY + P that I can switch screens.. But even though I pick external monitor and I see that it switch to it, monitor is turned on, but I have only black screen and can't do anything.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.7.1-050701-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .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 450.66 Wed Aug 12 19:42:48 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 3 22:59:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 5.7.1-050701-generic, x86_64: installed nvidia, 450.66, 5.7.1-050701-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1f99] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3a43] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:3a3f] InstallationDate: Installed on 2020-09-15 (18 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 82B5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.7.1-050701-generic root=UUID=29bfdbd7-583f-4a6e-8e15-9bf5e33c383d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.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:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1898395/+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 1893217] Re: [nvidia] Chrome window is corrupt - has a hole in it showing the desktop
** Tags removed: multi-gpu ** Tags added: multigpu -- 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/1893217 Title: [nvidia] Chrome window is corrupt - has a hole in it showing the desktop Status in chromium-browser package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: my display doesnt work properly.it mostly gets clubbed with previous window i used in system. Even now while i m reporting the bug,i face the same issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .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 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 27 18:10:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-42-generic, x86_64: built rtl8821ce, v5.5.2_34066.20200325, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:84a7] Subsystem: Hewlett-Packard Company GM108M [GeForce MX110] [103c:84a7] InstallationDate: Installed on 2020-08-26 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 003: ID 04f2:b65d Chicony Electronics Co., Ltd HP TrueVision HD Camera Bus 001 Device 011: ID 04e8:6864 Samsung Electronics Co., Ltd GT-I9070 (network tethering, USB debugging enabled) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15g-dr0xxx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=4cac576c-f749-447e-9180-b78666e12db6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A7 dmi.board.vendor: HP dmi.board.version: 80.31 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.07:bd11/21/2018:svnHP:pnHPLaptop15g-dr0xxx:pvrType1ProductConfigId:rvnHP:rn84A7:rvr80.31:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15g-dr0xxx dmi.product.sku: 4ZD61PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.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:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1893217/+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 1989744] Re: KB/Mouse use causing short system freezes. Happens after resume
Thanks for the bug report. Please try removing any custom extensions that might be installed: cd ~/.local/share/gnome-shell/ rm -rf extensions and then log in again. If the problem still happens, then while it is happening please run: ps auxw | grep gnome-shell > psoutput.txt and attach the resulting text file here. ** Tags added: hybrid i915 multigpu nvidia ** Tags added: resume suspend-resume ** Changed in: xorg-server (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/1989744 Title: KB/Mouse use causing short system freezes. Happens after resume Status in xorg-server package in Ubuntu: Incomplete Bug description: Summary: My laptop gets into a an odd state after resuming from sleep where, depending on user activity, the entire system freezes every 20 seconds for about 1/2 second. This does not happen after every resume. After upgrading to 22.04 was much less frequent than it was with 21.10. It seems that after some recent update it is happening more frequently again. Maybe one every 4 suspend/resume cycles. Normal operation can be restored by rebooting or sometimes suspending and waking. The triggering event is complex: * The pointer or pointer and keyboard must be actively used * Just typing with no mouse use will not cause it to happen. * Just moving the mouse pointer around but keeping it inside the same GUI element(a textarea for example) will not cause it * Typing for more than 20 seconds and then moving the mouse one pixel will cause it. * Moving the mouse around constantly for over 20 seconds will cause it to happen only if: a key on the keyboard was hit OR the pointer moved over a new GUI element(window border, button, even frames in a web page) * It is not application specific. The following is usually logged(not always though) when the freeze happens: ==> ~/.local/share/xorg/Xorg.1.log <== [1214998.964] (II) event5 - TPPS/2 Elan TrackPoint: SYN_DROPPED event - some input events have been lost. ==> /var/log/syslog <== Sep 15 08:23:51 krug /usr/libexec/gdm-x-session[3264]: (II) event5 - TPPS/2 Elan TrackPoint: SYN_DROPPED event - some input events have been lost. Sep 15 08:50:34 krug /usr/libexec/gdm-x-session[3264]: (II) event5 - TPPS/2 Elan TrackPoint: SYN_DROPPED event - some input events have been lost. Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer event4 trackpoint: scheduled expiry is in the past (-317ms), your system is too slow Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer event4 trackpoint: scheduled expiry is in the past (-301ms), your system is too slow Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer event4 trackpoint: scheduled expiry is in the past (-288ms), your system is too slow Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer event4 trackpoint: scheduled expiry is in the past (-278ms), your system is too slow Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) WARNING: log rate limit exceeded (5 msgs per 360ms). Discarding future messages. System Information: Lenovo Thinkpad P15 Model: 20YQ-003WUS OS: Ubuntu 22.04.1 LTS Kernel: 5.15.0-46-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-core 2:21.1.3-2ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic 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..01.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 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 15 10:13:26 2022 DistUpgraded: 2022-06-30 16:37:37,968 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.34, 5.15.0-43-generic, x86_64: installed virtualbox/6.1.34, 5.15.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-H GT1 [UHD Graphics] [17aa:22d8] NVIDIA Corporation GA107GLM [RTX A2000
[Desktop-packages] [Bug 1989304] Re: gnome-shell 43.rc SIGSEGV in g_str_hash() via on_directory_profile_ready() [meta-color-store.c:94]
** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-43.0 fixed-upstream -- 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/1989304 Title: gnome-shell 43.rc SIGSEGV in g_str_hash() via on_directory_profile_ready() [meta-color-store.c:94] Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: Unable to login to gnome session(bug#1989240). ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~rc-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 12 10:51:32 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1662686872 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/thelastline RelatedPackageVersions: mutter-common 43~rc-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_steal () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-11.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: Upgraded to kinetic on 2022-09-07 (5 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1989304/+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 1989582] Re: gnome-shell 43 (and mutter) Xorg sessions stutter and freeze
** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-43.0 fixed-upstream -- 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/1989582 Title: gnome-shell 43 (and mutter) Xorg sessions stutter and freeze Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: gnome-shell 43 (and mutter) Xorg sessions stutter and freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1989582/+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 1989830] [NEW] vmwgfx_dri.so not built on aarch64
Public bug reported: Ubuntu currently isn't building the vmwgfx_dri.so driver on aarch64 which makes graphics acceleration not work on VMware hypervisors running aarch64. Any Mesa3D version 22.1.4 or higher has full 3D support for the svga device, unfortunately only in: https://gitlab.freedesktop.org/mesa/mesa/-/commit/6e311dd7229b2afb478e65afe2f17d7fb422d01e we've added it to the default/auto compile options, before then it had to be manually enabled. It would be great if mesa packages for 22.10 could build the vmwgfx_dri.so by enabling the svga device in mesa packages. That would make accelerated GL work on aarch64 with VMware products. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1989830 Title: vmwgfx_dri.so not built on aarch64 Status in mesa package in Ubuntu: New Bug description: Ubuntu currently isn't building the vmwgfx_dri.so driver on aarch64 which makes graphics acceleration not work on VMware hypervisors running aarch64. Any Mesa3D version 22.1.4 or higher has full 3D support for the svga device, unfortunately only in: https://gitlab.freedesktop.org/mesa/mesa/-/commit/6e311dd7229b2afb478e65afe2f17d7fb422d01e we've added it to the default/auto compile options, before then it had to be manually enabled. It would be great if mesa packages for 22.10 could build the vmwgfx_dri.so by enabling the svga device in mesa packages. That would make accelerated GL work on aarch64 with VMware products. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1989830/+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 1989822] Re: Accent color foreground elements (such as links) may have lower contrast ratio
This bug was fixed in the package libadwaita-1 - 1.2.0-1ubuntu2 --- libadwaita-1 (1.2.0-1ubuntu2) kinetic; urgency=medium * debian/patches: Compute the fg accent color taking care of contrast with bg (LP: #1989822) -- Marco Trevisan (Treviño) Fri, 16 Sep 2022 01:51:02 +0200 ** Changed in: libadwaita-1 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libadwaita-1 in Ubuntu. https://bugs.launchpad.net/bugs/1989822 Title: Accent color foreground elements (such as links) may have lower contrast ratio Status in libadwaita-1 package in Ubuntu: Fix Released Bug description: Libadwaita expose to apps the "accent_color" color that is meant to be used as a foreground accent color, in contrast to the defined accent color. We may provide colors that are not fully conform to the W4C specs for fg/bg contrast ratio. Can see more details at https://twitter.com/alexm_gnome/status/1526531918166212608 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug/1989822/+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 1989826] [NEW] cannot start lightdm gui
Public bug reported: i installed lightdm but cannot start it manually using ubuntu 22.04.1 LTS release 22.04 codename: jammy ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lightdm 1.30.0-0ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 Date: Fri Sep 16 01:27:20 2022 InstallationDate: Installed on 2022-08-28 (18 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1989826 Title: cannot start lightdm gui Status in lightdm package in Ubuntu: New Bug description: i installed lightdm but cannot start it manually using ubuntu 22.04.1 LTS release 22.04 codename: jammy ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lightdm 1.30.0-0ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 Date: Fri Sep 16 01:27:20 2022 InstallationDate: Installed on 2022-08-28 (18 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1989826/+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 1989822] [NEW] Accent color foreground elements (such as links) may have lower contrast ratio
Public bug reported: Libadwaita expose to apps the "accent_color" color that is meant to be used as a foreground accent color, in contrast to the defined accent color. We may provide colors that are not fully conform to the W4C specs for fg/bg contrast ratio. Can see more details at https://twitter.com/alexm_gnome/status/1526531918166212608 ** Affects: libadwaita-1 (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libadwaita-1 in Ubuntu. https://bugs.launchpad.net/bugs/1989822 Title: Accent color foreground elements (such as links) may have lower contrast ratio Status in libadwaita-1 package in Ubuntu: In Progress Bug description: Libadwaita expose to apps the "accent_color" color that is meant to be used as a foreground accent color, in contrast to the defined accent color. We may provide colors that are not fully conform to the W4C specs for fg/bg contrast ratio. Can see more details at https://twitter.com/alexm_gnome/status/1526531918166212608 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug/1989822/+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 1989821] [NEW] Firefox hangs, unable to reload tabs for up to 2min after switching to session that was idle for several hours
Public bug reported: I am not sure when exactly this started. I feel like it was around FF v99. System is always on. 2 user accounts (mine, wife's). We keep the desktop sessions logged-in, just switch between accounts whenever needed. Firefox stays open since it's heavily used. When an active session is unlocked or switched to after being unused for several hours (not rigorously measured but I'd say more than 6-8 hours), we observe the following behavior in Firefox: * Gmail tab will show a message at the top of the page along the lines of "encountered a problem, retrying in 3:00" with the timer counting down * For the first 10-20s, clicking on another tab will have no effect - FF doesn't switch to the tab * From 20s to between 1-2 minutes: - Switching tabs will work albeit slowly. - Reloading an existing tab does nothing except cause the side-to-side loading indicator on the tab to cycle - I am able to open a new tab via ctrl-T - I can enter a URL into a new tab, but the site doesn't load. The loading indicator cycles in the tab title. - I cannot open about:performance to troubleshoot After some period of time, as short as 30-40s and as long as 2 minutes, FF becomes usable again. Sites can be loaded/reloaded, etc. What I have tried, but has not resolved the issue: * Restart FF in troubleshooting mode * Upgrade to new releases as they are available in the package manager * Run in non-troubleshooting mode but with all extensions removed * Refresh the browser * Set browser.tabs.unloadOnLowMemory = false * rm -rf ~/.mozilla and start with a fresh profile Workaround: killall -9 firefox, then relaunch firefox Again, this seems to have started suddenly at some point possibly around the v99 timeframe. Prior to that, I did not observe this problem. Hardware, and to the best of my knowledge the usage habits of the 2 users, have not changed in quite some time. I've attached the output of a "vmstat 1" command that I launched when I unlocked a session that was idle for approximately 40h, before interacting with the existing firefox session. The firefox issue manifested for about 1min 20s. Once firefox became usable, I stopped the vmstat command. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 104.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195 Uname: Linux 5.4.0-124-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tyr 743015 F pulseaudio /dev/snd/controlC1: tyr 743015 F pulseaudio BuildID: 20220818191623 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: XFCE Date: Thu Sep 15 18:38:25 2022 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-01-05 (2444 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 100 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.100 metric 100 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:302 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=104.0/20220818191623 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2021-02-04 (588 days ago) dmi.bios.date: 11/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "firefox-vmstat.out" https://bugs.launchpad.net/bugs/1989821/+attachment/5616215/+files/firefox-vmstat.out ** Summary changed: - Firefox hangs, unable to reload tabs after switching to session that was idle for several hours + Firefox hangs, unable to reload tabs for up to 2min after switching to session that was idle for several hours ** Description changed: I am not sure when exactly this started. I feel like it
[Desktop-packages] [Bug 1989807] Re: Move raspi cloud-init configuration to ubuntu-settings
** Also affects: ubuntu-settings (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1989807 Title: Move raspi cloud-init configuration to ubuntu-settings Status in Ubuntu Seeds: New Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-settings source package in Jammy: New Status in ubuntu-settings source package in Kinetic: New Bug description: Currently /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg (which exists to disable "real" cloud sources on the raspi images) is hacked into the images from livecd-rootfs. It would be preferable to have this in a server-specific variant of the ubuntu-raspi-settings package. To avoid dpkg conflicts, the file should be differently named (99-fake-cloud.cfg would be sufficient) with a maintscript tweak to remove the old name. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1989807/+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 1989807] Re: Move raspi cloud-init configuration to ubuntu-settings
Apparently rm_conffile is considerably more stubborn than I'd given it credit for, when it comes to removing files previously unowned by packages (i.e. /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg). The only successful method is to rm it in a postinst script unfortunately. The attached patch remedies this (along with the aforementioned fixes for LP: #1977764). ** Patch added: "2-1989807.debdiff" https://bugs.launchpad.net/ubuntu-seeds/+bug/1989807/+attachment/5616205/+files/2-1989807.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1989807 Title: Move raspi cloud-init configuration to ubuntu-settings Status in Ubuntu Seeds: New Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-settings source package in Kinetic: New Bug description: Currently /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg (which exists to disable "real" cloud sources on the raspi images) is hacked into the images from livecd-rootfs. It would be preferable to have this in a server-specific variant of the ubuntu-raspi-settings package. To avoid dpkg conflicts, the file should be differently named (99-fake-cloud.cfg would be sufficient) with a maintscript tweak to remove the old name. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1989807/+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 1870597] Re: libinput says "your system is too slow"
The problem come back again after recent updates in ubuntu 20.04. System is stuttering when moving mouse and typing on keyboard: mutter3.36.9-0ubuntu0.20.04.2 xserver-xorg-input-libinput 0.29.0-1 libinput10:amd64 1.15.5-1ubuntu0.3 GNOME Shell 3.36.9 xorg-server 2:1.20.13-1ubuntu1~20.04.3 5.15.0-46-generic Lot of errors like following in journald: ``` /usr/lib/gdm3/gdm-x-session[4273]: (EE) client bug: timer event16 debounce short: scheduled expiry is in the past (-2ms), your system is too slow /usr/lib/gdm3/gdm-x-session[4273]: (EE) client bug: timer event16 debounce: scheduled expiry is in the past (-1ms), your system is too slow ``` Other DE does not have this issue. -- 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/1870597 Title: libinput says "your system is too slow" Status in GNOME Shell: Unknown Status in libinput: Fix Released Status in Linux: Confirmed Status in libinput package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm- x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870597/+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 381017] Re: Cannot drag attachment from mail attachment pane to desktop
** Changed in: seamonkey Status: Fix Released => Confirmed ** Changed in: thunderbird Status: Fix Released => Confirmed -- 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/381017 Title: Cannot drag attachment from mail attachment pane to desktop Status in One Hundred Papercuts: Triaged Status in SeaMonkey: Confirmed Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Ubuntu 9.04 Gnome Desktop 2.26.1 Thunderbird 2.0.0.21 This is regression introduced in Jaunty as it works in Intrepid. Dragging an attachment from the attachment pane to the desktop give the following error: == Error while copying There was an error getting information about "fetch>UID>.voicemail>1784". The specified location is not supported == Mail account is IMAP. This error was shown to seb128 and asac. The expected behavior is that the file is copied to the destination onto which it is dragged. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/381017/+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 381017]
> I have Manjaro Linux with TB 102, and the problem is still here. >... > Not work. Location specified is not compatible. Bugs fixed long ago is not a great place to be reporting current issues. If it reproduces under Help > Troubleshooting Mode then please file a new bug report -- 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/381017 Title: Cannot drag attachment from mail attachment pane to desktop Status in One Hundred Papercuts: Triaged Status in SeaMonkey: Confirmed Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Ubuntu 9.04 Gnome Desktop 2.26.1 Thunderbird 2.0.0.21 This is regression introduced in Jaunty as it works in Intrepid. Dragging an attachment from the attachment pane to the desktop give the following error: == Error while copying There was an error getting information about "fetch>UID>.voicemail>1784". The specified location is not supported == Mail account is IMAP. This error was shown to seb128 and asac. The expected behavior is that the file is copied to the destination onto which it is dragged. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/381017/+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 381017]
Will look at it - still reproducible on TB 102. -- 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/381017 Title: Cannot drag attachment from mail attachment pane to desktop Status in One Hundred Papercuts: Triaged Status in SeaMonkey: Confirmed Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Ubuntu 9.04 Gnome Desktop 2.26.1 Thunderbird 2.0.0.21 This is regression introduced in Jaunty as it works in Intrepid. Dragging an attachment from the attachment pane to the desktop give the following error: == Error while copying There was an error getting information about "fetch>UID>.voicemail>1784". The specified location is not supported == Mail account is IMAP. This error was shown to seb128 and asac. The expected behavior is that the file is copied to the destination onto which it is dragged. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/381017/+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 381017]
Ubuntu 20.04 Thunderbird 102.2.2 Thunar 4.16.10 Not work. Location specified is not compatible. -- 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/381017 Title: Cannot drag attachment from mail attachment pane to desktop Status in One Hundred Papercuts: Triaged Status in SeaMonkey: Confirmed Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Ubuntu 9.04 Gnome Desktop 2.26.1 Thunderbird 2.0.0.21 This is regression introduced in Jaunty as it works in Intrepid. Dragging an attachment from the attachment pane to the desktop give the following error: == Error while copying There was an error getting information about "fetch>UID>.voicemail>1784". The specified location is not supported == Mail account is IMAP. This error was shown to seb128 and asac. The expected behavior is that the file is copied to the destination onto which it is dragged. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/381017/+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 381017]
I have Manjaro Linux with TB 102, and the problem is still here. When I do drag-and-drop to a Nemo folder I got the icon copied, and when going to Nautilus I still have "Drag and drop not supported", "an invalid drag type was used". -- 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/381017 Title: Cannot drag attachment from mail attachment pane to desktop Status in One Hundred Papercuts: Triaged Status in SeaMonkey: Confirmed Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Ubuntu 9.04 Gnome Desktop 2.26.1 Thunderbird 2.0.0.21 This is regression introduced in Jaunty as it works in Intrepid. Dragging an attachment from the attachment pane to the desktop give the following error: == Error while copying There was an error getting information about "fetch>UID>.voicemail>1784". The specified location is not supported == Mail account is IMAP. This error was shown to seb128 and asac. The expected behavior is that the file is copied to the destination onto which it is dragged. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/381017/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
ok, I was not aware of : « Wayland sessions (which might include the login screen) ». -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 1989807] Re: Move raspi cloud-init configuration to ubuntu-settings
** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1989807 Title: Move raspi cloud-init configuration to ubuntu-settings Status in Ubuntu Seeds: New Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-settings source package in Kinetic: New Bug description: Currently /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg (which exists to disable "real" cloud sources on the raspi images) is hacked into the images from livecd-rootfs. It would be preferable to have this in a server-specific variant of the ubuntu-raspi-settings package. To avoid dpkg conflicts, the file should be differently named (99-fake-cloud.cfg would be sufficient) with a maintscript tweak to remove the old name. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1989807/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
Seth, pcscd.socket is already enabled. You should not have to run "sudo systemctl enable pcscd.socket" again. In your output I see that pcscd is already running. I would like to get the results of the following commands when you *have* the problem and before you try to fix it. systemctl status pcscd.socket systemctl status pcscd.service ls -l /run/pcscd/ journalctl --no-pager --unit=pcscd.socket journalctl --no-pager --unit=pcscd.service -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1989626] Re: UIFe: fonts-noto-color-emoji & other updates for Unicode 15
** Description changed: Justification - Unicode 15 was release September 13. This is an annual release. It's expected that the latest Ubuntu will support the latest stable Unicode release. This is required for compatibility with Internet communications with other platforms that will be quickly adopting the new emoji characters. The release happened too late for related upstream releases to happen by Ubuntu's User Interface Freeze on September 15 and be packaged. Therefore, I request a UIFe for Ubuntu 22.10 for Unicode 15 packages. More details Google will be releasing a new version of fonts-noto-color-emoji "later this week" but it looks like it won't be released in time for Ubuntu's User Interface Freeze. - We also need to update glib and pango for the new release so that new + We also need to update glib and harfbuzz for the new release so that new composite emoji like "pink heart" display correctly. https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2877 - There isn't an upstream pango merge request or issue but I think it will - be needed. + https://github.com/harfbuzz/harfbuzz/pull/3797 There are probably some other minor universe packages that we should sync from Debian if we see they are related to Unicode 15. I don't have packaging ready for these changes yet but I'm requesting the UIFe early. Likely affected packages fonts-noto-color-emoji nototools (current version was updated for Unicode 15 in August so may already be new enough) glib2.0 - pango1.0 + harfbuzz node-unicode-data maybe more universe packages 22.04 LTS - We have done SRUs of new fonts-noto-color-emoji releases to older LTSes before. We may do it again but that will be one or more separate bugs. References -- https://blog.emojipedia.org/whats-new-in-unicode-15-0/ https://developers.googleblog.com/2022/09/updates-to-emoji-new- characters-animation-colors-and-more.html https://unicode.org/versions/Unicode15.0.0/ Email to Docs List: https://lists.ubuntu.com/archives/ubuntu-doc/2022-September/020889.html I don't believe translators need to be notified about this UIFe but let me know if I should email them anyway. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1989626 Title: UIFe: fonts-noto-color-emoji & other updates for Unicode 15 Status in fonts-noto-color-emoji package in Ubuntu: New Bug description: Justification - Unicode 15 was release September 13. This is an annual release. It's expected that the latest Ubuntu will support the latest stable Unicode release. This is required for compatibility with Internet communications with other platforms that will be quickly adopting the new emoji characters. The release happened too late for related upstream releases to happen by Ubuntu's User Interface Freeze on September 15 and be packaged. Therefore, I request a UIFe for Ubuntu 22.10 for Unicode 15 packages. More details Google will be releasing a new version of fonts-noto-color-emoji "later this week" but it looks like it won't be released in time for Ubuntu's User Interface Freeze. We also need to update glib and harfbuzz for the new release so that new composite emoji like "pink heart" display correctly. https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2877 https://github.com/harfbuzz/harfbuzz/pull/3797 There are probably some other minor universe packages that we should sync from Debian if we see they are related to Unicode 15. I don't have packaging ready for these changes yet but I'm requesting the UIFe early. Likely affected packages fonts-noto-color-emoji nototools (current version was updated for Unicode 15 in August so may already be new enough) glib2.0 harfbuzz node-unicode-data maybe more universe packages 22.04 LTS - We have done SRUs of new fonts-noto-color-emoji releases to older LTSes before. We may do it again but that will be one or more separate bugs. References -- https://blog.emojipedia.org/whats-new-in-unicode-15-0/ https://developers.googleblog.com/2022/09/updates-to-emoji-new- characters-animation-colors-and-more.html https://unicode.org/versions/Unicode15.0.0/ Email to Docs List: https://lists.ubuntu.com/archives/ubuntu-doc/2022-September/020889.html I don't believe translators need to be notified about this UIFe but let me know if I should email them anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1989626/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1989807] Re: Move raspi cloud-init configuration to ubuntu-settings
Attaching debdiff for ubuntu-settings. This incorporates the diff for this bug as well as the earlier (and vaguely related) LP: #1977764. In addition to this, I've extended the merge proposal for the aforementioned bug to update the necessary seed to include this package in the Ubuntu Pi server image(s). ** Patch added: "1-1989807.debdiff" https://bugs.launchpad.net/ubuntu-seeds/+bug/1989807/+attachment/5616189/+files/1-1989807.debdiff ** Tags added: raspi-image -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1989807 Title: Move raspi cloud-init configuration to ubuntu-settings Status in Ubuntu Seeds: New Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-settings source package in Kinetic: New Bug description: Currently /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg (which exists to disable "real" cloud sources on the raspi images) is hacked into the images from livecd-rootfs. It would be preferable to have this in a server-specific variant of the ubuntu-raspi-settings package. To avoid dpkg conflicts, the file should be differently named (99-fake-cloud.cfg would be sufficient) with a maintscript tweak to remove the old name. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1989807/+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 1989807] Re: Move raspi cloud-init configuration to ubuntu-settings
** Also affects: ubuntu-settings (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: ubuntu-seeds Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1989807 Title: Move raspi cloud-init configuration to ubuntu-settings Status in Ubuntu Seeds: New Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-settings source package in Kinetic: New Bug description: Currently /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg (which exists to disable "real" cloud sources on the raspi images) is hacked into the images from livecd-rootfs. It would be preferable to have this in a server-specific variant of the ubuntu-raspi-settings package. To avoid dpkg conflicts, the file should be differently named (99-fake-cloud.cfg would be sufficient) with a maintscript tweak to remove the old name. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1989807/+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 1989807] [NEW] Move raspi cloud-init configuration to ubuntu-settings
Public bug reported: Currently /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg (which exists to disable "real" cloud sources on the raspi images) is hacked into the images from livecd-rootfs. It would be preferable to have this in a server-specific variant of the ubuntu-raspi-settings package. To avoid dpkg conflicts, the file should be differently named (99-fake- cloud.cfg would be sufficient) with a maintscript tweak to remove the old name. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-settings (Ubuntu Kinetic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1989807 Title: Move raspi cloud-init configuration to ubuntu-settings Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-settings source package in Kinetic: New Bug description: Currently /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg (which exists to disable "real" cloud sources on the raspi images) is hacked into the images from livecd-rootfs. It would be preferable to have this in a server-specific variant of the ubuntu-raspi-settings package. To avoid dpkg conflicts, the file should be differently named (99-fake-cloud.cfg would be sufficient) with a maintscript tweak to remove the old name. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1989807/+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 1741074]
(In reply to William Woodruff from comment #10) > Chiming in as a maintainer of an extension > ([ff2mpv](https://github.com/woodruffw/ff2mpv)) that uses native messaging: > users have already reported challenges getting the extension to function > correctly with the `snap`-ified Firefox distribution in the upcoming Ubuntu > LTS release. > > Downstream tracking: https://github.com/woodruffw/ff2mpv/issues/80 Following up on this: I'm able to confirm that the extension I maintain works correctly on the "beta" channel of the Firefox snap. However, to get it working, I had to run a manual `flatpak` command on the terminal: ``` flatpak permission-set webextensions ff2mpv snap.firefox yes ``` Is this documented somewhere? I had to dig through others' bug reports to figure out that this is what I needed, and I can imagine that a lot of other native extension users (and developers) are in a similar position. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: In Progress Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: In Progress Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Status in plasma-browser-integration package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. [Workaround] If you're using Ubuntu 22.04 LTS, you can install GNOME Shell extensions with this app. sudo apt install gnome-shell-extension-manager To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+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 1989733] Re: [FFE] build ubuntu-desktop package for riscv64
This bug was fixed in the package ubuntu-meta - 1.494 --- ubuntu-meta (1.494) kinetic; urgency=medium * Provide ubuntu-desktop for riscv64 (LP: #1989733) -- Heinrich Schuchardt Thu, 15 Sep 2022 11:11:32 +0200 ** Changed in: ubuntu-meta (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1989733 Title: [FFE] build ubuntu-desktop package for riscv64 Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Currently the ubuntu-desktop and the ubuntu-desktop-minimal package are missing for riscv64. This makes it difficult for users to upgrade from a server image to a full desktop. Ubuntu-destkop and Ubuntu-desktop-minimal are just meta packages. So the only problems that could arise for a user are: * the package is not installable if a dependency is missing * the numerous dependent packages may exceed the disk space. As the riscv64 packages have not existed before and are not included in any images there is no regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1989733/+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 1988686] Re: Read failure Photo SD Memory Card in USB
there is a merge request with a fix upstream now ** Changed in: nautilus (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1988686 Title: Read failure Photo SD Memory Card in USB Status in Nautilus: New Status in nautilus package in Ubuntu: In Progress Bug description: Tried to read my SD memory card in the USB slot. Nautilus responded with message box "Force Close" or "Wait". Nautilus is outputting the following messages to Syslog when trying to display the device. Sep 4 14:41:42 Desktopps nautilus[31175]: specified class size for type 'NautilusXContentBar' is smaller than the parent type's 'GtkInfoBar' class size Sep 4 14:41:42 Desktopps nautilus[31175]: g_once_init_leave: assertion 'result != 0' failed Sep 4 14:41:42 Desktopps nautilus[31175]: g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed Sep 4 14:41:42 Desktopps nautilus[31175]: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed Sep 4 14:41:42 Desktopps nautilus[31175]: gtk_box_append: assertion 'GTK_IS_WIDGET (child)' failed Able to read this memory card in a Ubuntu 22.04 system. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~beta.1-2ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Sep 4 15:08:36 2022 InstallationDate: Installed on 2022-09-03 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1988686/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
Ludovic, Please find the output you requested below. systemctl status pcscd.socket ● pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; enabled; vendor preset: enabled) Active: active (running) since Thu 2022-09-15 10:58:12 PDT; 1min 26s ago Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) CGroup: /system.slice/pcscd.socket systemctl status pcscd.service ● pcscd.service - PC/SC Smart Card Daemon Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor preset: enabled) Active: active (running) since Thu 2022-09-15 10:58:16 PDT; 1min 31s ago TriggeredBy: ● pcscd.socket Docs: man:pcscd(8) Main PID: 2544 (pcscd) Tasks: 7 (limit: 38174) Memory: 1.5M CPU: 73ms CGroup: /system.slice/pcscd.service └─2544 /usr/sbin/pcscd --foreground --auto-exit Let me provide additional information on the behavior that we are seeing If we use sudo systemctl enable pcscd.socket then we must issue either sudo systemctl restart pcscd.socket sudo systemctl stop pcscd.socket; sudo systemctl start pcscd.socket almost every time we want to use smartcard authentication at gnome login screen We have observed this behavior after the following events: reboot lock screen (seems to respond better to a stop and start of the socket rather than a restart, e.g. we can get multiple locks where we are able to log back in, if we stop and start the socket, whereas a restart just lets us get logged back in once) log out output from /var/log/auth.log Sep 15 11:29:10 test-jammy gdm-password]: pam_sss(gdm-password:auth): received for user test.user: 7 (Authentication failure) Sep 15 11:29:10 test-jammy gdm-password]: pam_pkcs11(gdm-password:auth): no suitable token available Sep 15 11:29:10 test-jammy gdm-password]: pam_sss(gdm-password:auth): authentication failure; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=test.user Sep 15 11:29:10 test-jammy gdm-password]: pam_sss(gdm-password:auth): received for user test.user: 7 (Authentication failure) Sep 15 11:29:19 test-jammy gdm-smartcard]: pam_sss(gdm-smartcard:auth): User info message: Please insert smart card Commandline tools on the other hand seem to work as expected once the socket has been enabled, no additional socket restarts are needed opensc-tool --list-readers pkcs11-tool --list-token-slots pkcs11_listcerts debug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1877038]
Just read a news about even iOS 16 will ship better webauthn function. I guess this issue should be taken care of sooner. -- 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/1877038 Title: [upstream] Firefox lacks FIDO2 support with Yubikeys Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: Ubuntu LTS versions affected. "Passwordless" authentications with Yubikeys using Firefox don't work with FIDO2. Tested both with the yubikey software packages from the bionic/universe repo and those from the vendor https://www.yubico.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1877038/+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 1877038]
My company is considering enforcing the use of FIDO2 devices. It would be a blow for our Mac and Linux employees to have to switch from Firefox to Chrome because of this. -- 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/1877038 Title: [upstream] Firefox lacks FIDO2 support with Yubikeys Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: Ubuntu LTS versions affected. "Passwordless" authentications with Yubikeys using Firefox don't work with FIDO2. Tested both with the yubikey software packages from the bionic/universe repo and those from the vendor https://www.yubico.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1877038/+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 1989733] Re: [FFE] build ubuntu-desktop package for riscv64
I've uploaded and unsubscribed ubuntu-sponsors. Thanks! ** Changed in: ubuntu-meta (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1989733 Title: [FFE] build ubuntu-desktop package for riscv64 Status in ubuntu-meta package in Ubuntu: Fix Committed Bug description: Currently the ubuntu-desktop and the ubuntu-desktop-minimal package are missing for riscv64. This makes it difficult for users to upgrade from a server image to a full desktop. Ubuntu-destkop and Ubuntu-desktop-minimal are just meta packages. So the only problems that could arise for a user are: * the package is not installable if a dependency is missing * the numerous dependent packages may exceed the disk space. As the riscv64 packages have not existed before and are not included in any images there is no regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1989733/+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 1987875] Re: Cmore streaming service not working well after recent updates
Launchpad has imported 2 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1790389. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2022-09-12T13:28:44+00:00 Jørn Melchior Nielsen wrote: User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:104.0) Gecko/20100101 Firefox/104.0 Steps to reproduce: Streaming from cmore.dk is interrupting after Ubuntu/Firefox update. Actual results: I think the problem is Widevine Content Decryption Module provided by Google Inc. Streaming from dr.dk and youtube.com is ok It happens with Ubuntu 18.04 and 20.04 and HP Elitebook and HP Pavillion Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987875/comments/9 On 2022-09-12T13:31:45+00:00 Release-mgmt-account-bot wrote: The [Bugbug](https://github.com/mozilla/bugbug/) bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987875/comments/11 ** Changed in: firefox Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1987875 Title: Cmore streaming service not working well after recent updates Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Incomplete Status in firefox package in Ubuntu: New Bug description: I have tried with several computers and version 18.04 20.04 and 22.04 after last update Cmore is not playing well. The picture and sound is interrupting, so the streaming is not good. I think it is the last version of widevine decryption is doing it, because youtube and dr.dk works fine. The laptop is also getting very very hot, and in the end it just stop. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987875/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
See the four year old bug mentioned here: https://github.com/flatpak/xdg-desktop-portal-gtk/issues/137 ** Bug watch added: github.com/flatpak/xdg-desktop-portal-gtk/issues #137 https://github.com/flatpak/xdg-desktop-portal-gtk/issues/137 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 1971763] Re: www-browser is not satisfied by the default Firefox snap
** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Changed in: firefox (Ubuntu) Status: New => Confirmed ** Changed in: firefox (Ubuntu) Importance: Undecided => High -- 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/1971763 Title: www-browser is not satisfied by the default Firefox snap Status in firefox package in Ubuntu: Confirmed Status in gimp-help package in Ubuntu: Confirmed Bug description: When installing a package that has the virtual-package www-browser as a dependency, the Firefox snap is not taken into account. This leads to wslu being installed on Ubuntu 22.04 Desktop (notably when installing the GIMP translation packages), which breaks the ding desktop behaviour: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1971757 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1971763/+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 1989744] [NEW] KB/Mouse use causing short system freezes. Happens after resume
Public bug reported: Summary: My laptop gets into a an odd state after resuming from sleep where, depending on user activity, the entire system freezes every 20 seconds for about 1/2 second. This does not happen after every resume. After upgrading to 22.04 was much less frequent than it was with 21.10. It seems that after some recent update it is happening more frequently again. Maybe one every 4 suspend/resume cycles. Normal operation can be restored by rebooting or sometimes suspending and waking. The triggering event is complex: * The pointer or pointer and keyboard must be actively used * Just typing with no mouse use will not cause it to happen. * Just moving the mouse pointer around but keeping it inside the same GUI element(a textarea for example) will not cause it * Typing for more than 20 seconds and then moving the mouse one pixel will cause it. * Moving the mouse around constantly for over 20 seconds will cause it to happen only if: a key on the keyboard was hit OR the pointer moved over a new GUI element(window border, button, even frames in a web page) * It is not application specific. The following is usually logged(not always though) when the freeze happens: ==> ~/.local/share/xorg/Xorg.1.log <== [1214998.964] (II) event5 - TPPS/2 Elan TrackPoint: SYN_DROPPED event - some input events have been lost. ==> /var/log/syslog <== Sep 15 08:23:51 krug /usr/libexec/gdm-x-session[3264]: (II) event5 - TPPS/2 Elan TrackPoint: SYN_DROPPED event - some input events have been lost. Sep 15 08:50:34 krug /usr/libexec/gdm-x-session[3264]: (II) event5 - TPPS/2 Elan TrackPoint: SYN_DROPPED event - some input events have been lost. Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer event4 trackpoint: scheduled expiry is in the past (-317ms), your system is too slow Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer event4 trackpoint: scheduled expiry is in the past (-301ms), your system is too slow Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer event4 trackpoint: scheduled expiry is in the past (-288ms), your system is too slow Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer event4 trackpoint: scheduled expiry is in the past (-278ms), your system is too slow Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) WARNING: log rate limit exceeded (5 msgs per 360ms). Discarding future messages. System Information: Lenovo Thinkpad P15 Model: 20YQ-003WUS OS: Ubuntu 22.04.1 LTS Kernel: 5.15.0-46-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-core 2:21.1.3-2ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic 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..01.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 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 15 10:13:26 2022 DistUpgraded: 2022-06-30 16:37:37,968 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.34, 5.15.0-43-generic, x86_64: installed virtualbox/6.1.34, 5.15.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-H GT1 [UHD Graphics] [17aa:22d8] NVIDIA Corporation GA107GLM [RTX A2000 Mobile] [10de:25b8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA107GLM [RTX A2000 Mobile] [17aa:22d8] InstallationDate: Installed on 2022-03-03 (195 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: LENOVO 20YQ003WUS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntuRAID-rootRAID ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to jammy on 2022-06-30 (77 days ago) dmi.bios.date: 12/24/2021 dmi.bios.release: 1.18 dmi.bios.vendor: LENOVO dmi.bios.version: N37ET37W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20YQ003WUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10
[Desktop-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?
Current status: $ grep hda /etc/modprobe.d/blacklist.conf blacklist snd_hda_codec_realtek Seems to stop the problems. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1988658 Title: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize? Status in pulseaudio package in Ubuntu: New Bug description: $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal 3 to 5 of 10 boot occasions stops prematurely. dmesg (included here, I assume) indicates a pulseaudio failure stopping the booting. I have NOT investigated further (knowledge limit). This very latest bootup seemed to indicate that there is something waiting on the keyboard, as I got all the way "up" after beating repeatedly - alternating - on ESC and ENTER --- dmesg tail on this boot --- 4 sec pause from previous line (at 9 secs) [ 13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 13.444031] usb usb3: root hub lost power or was reset [ 13.444032] usb usb4: root hub lost power or was reset [ 13.557170] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61) [ 17.001076] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 17.105681] rfkill: input handler disabled [ 28.694324] Bluetooth: RFCOMM TTY layer initialized [ 28.694328] Bluetooth: RFCOMM socket layer initialized [ 28.694331] Bluetooth: RFCOMM ver 1.11 [ 28.922797] rfkill: input handler enabled [ 29.043050] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 31.669031] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 31.907300] rfkill: input handler disabled [ 41.959736] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 78.940840] usb usb3: root hub lost power or was reset [ 78.940841] usb usb4: root hub lost power or was reset [ 929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 929.174669] usb usb3: root hub lost power or was reset [ 929.174671] usb usb4: root hub lost power or was reset -- end --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sun Sep 4 08:19:01 2022 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G731GU.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G731GU dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G731GU_G731GU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1988658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
Seth, what is the output of the command: systemctl status pcscd.socket -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1989737] Re: Package option (for xcolor) is not being properly used in beamer
** Description changed: There is a bug in beamer v3.65 which is fixed in beamer v3.66. A full description along with the workaround you currently have to use is given at https://tex.stackexchange.com/questions/641909/package-option-for- xcolor-is-not-being-properly-used-in-beamer . It would be great if an updated version of texlive with the newer - version of jammy could be packaged up for jammy. + version of beamer could be packaged up for jammy. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: texlive-full 2021.20220204-1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 15 15:59:03 2022 InstallationDate: Installed on 2020-08-03 (773 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: texlive-base 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 texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1989737 Title: Package option (for xcolor) is not being properly used in beamer Status in texlive-base package in Ubuntu: New Bug description: There is a bug in beamer v3.65 which is fixed in beamer v3.66. A full description along with the workaround you currently have to use is given at https://tex.stackexchange.com/questions/641909/package- option-for-xcolor-is-not-being-properly-used-in-beamer . It would be great if an updated version of texlive with the newer version of beamer could be packaged up for jammy. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: texlive-full 2021.20220204-1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 15 15:59:03 2022 InstallationDate: Installed on 2020-08-03 (773 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: texlive-base UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1989737/+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 1989733] Re: [FFE] build ubuntu-desktop package for riscv64
Tricky. It's a bit sad that we're doing this now, as this might potentially spawn some bug reports from RISC-V users that will now try to install ubuntu-desktop and run into problems. That being said, I suppose the userbase is still small and I know Heinrich is actively looking into this right now. In this case, let's proceed! Will still need a sponsor (not sure if I'll be able to get to it today). ** Changed in: ubuntu-meta (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1989733 Title: [FFE] build ubuntu-desktop package for riscv64 Status in ubuntu-meta package in Ubuntu: Triaged Bug description: Currently the ubuntu-desktop and the ubuntu-desktop-minimal package are missing for riscv64. This makes it difficult for users to upgrade from a server image to a full desktop. Ubuntu-destkop and Ubuntu-desktop-minimal are just meta packages. So the only problems that could arise for a user are: * the package is not installable if a dependency is missing * the numerous dependent packages may exceed the disk space. As the riscv64 packages have not existed before and are not included in any images there is no regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1989733/+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 1989418] Re: [BPO] libreoffice 7.3.6 for focal
OK just doing due diligence. Approved for backports pocket, it'll need to build and publish then should be available afterwards. ** Changed in: libreoffice (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1989418 Title: [BPO] libreoffice 7.3.6 for focal Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Fix Committed Bug description: [Impact] * LibreOffice 7.3.6 is in its sixth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.6_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988744 and its backport is currently provided by the LibreOffice Fresh PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages * Previous backport of 7.3.5 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1987045 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.3.5 is currently released in focal-backports. * 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. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.6-0ubuntu0.22.04.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [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_73/1900/ * 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. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/amd64/libr/libreoffice/20220904_103401_f46f5@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/arm64/libr/libreoffice/20220904_144020_84b5b@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/armhf/libr/libreoffice/20220904_113245_95845@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/ppc64el/libr/libreoffice/20220904_100953_3af7d@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/s390x/libr/libreoffice/20220904_095636_d0c69@/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 50 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/1989418/+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 1989733] Re: [FFE] build ubuntu-desktop package for riscv64
The Ubuntu Desktop Team is ok with this change. We'll continue to only produce Ubuntu Desktop ISOs for just amd64 and arm64 and those are the only architectures we officially support for desktop use cases. But we don't have a problem with making the metapackages available on other architectures. Thank you for proposing this! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1989733 Title: [FFE] build ubuntu-desktop package for riscv64 Status in ubuntu-meta package in Ubuntu: Triaged Bug description: Currently the ubuntu-desktop and the ubuntu-desktop-minimal package are missing for riscv64. This makes it difficult for users to upgrade from a server image to a full desktop. Ubuntu-destkop and Ubuntu-desktop-minimal are just meta packages. So the only problems that could arise for a user are: * the package is not installable if a dependency is missing * the numerous dependent packages may exceed the disk space. As the riscv64 packages have not existed before and are not included in any images there is no regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1989733/+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 1989418] Re: [BPO] libreoffice 7.3.6 for focal
@teward It is a backport as it was done at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1987045. It basically got the same testing as the corresponding SRU for jammy. The package is already uploaded and sitting int the focal/unapproved queue. https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=libreoffice -- 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/1989418 Title: [BPO] libreoffice 7.3.6 for focal Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: In Progress Bug description: [Impact] * LibreOffice 7.3.6 is in its sixth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.6_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988744 and its backport is currently provided by the LibreOffice Fresh PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages * Previous backport of 7.3.5 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1987045 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.3.5 is currently released in focal-backports. * 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. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.6-0ubuntu0.22.04.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [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_73/1900/ * 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. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/amd64/libr/libreoffice/20220904_103401_f46f5@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/arm64/libr/libreoffice/20220904_144020_84b5b@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/armhf/libr/libreoffice/20220904_113245_95845@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/ppc64el/libr/libreoffice/20220904_100953_3af7d@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/s390x/libr/libreoffice/20220904_095636_d0c69@/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 50 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/1989418/+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 1989737] [NEW] Package option (for xcolor) is not being properly used in beamer
Public bug reported: There is a bug in beamer v3.65 which is fixed in beamer v3.66. A full description along with the workaround you currently have to use is given at https://tex.stackexchange.com/questions/641909/package-option-for- xcolor-is-not-being-properly-used-in-beamer . It would be great if an updated version of texlive with the newer version of jammy could be packaged up for jammy. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: texlive-full 2021.20220204-1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 15 15:59:03 2022 InstallationDate: Installed on 2020-08-03 (773 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: texlive-base UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: texlive-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1989737 Title: Package option (for xcolor) is not being properly used in beamer Status in texlive-base package in Ubuntu: New Bug description: There is a bug in beamer v3.65 which is fixed in beamer v3.66. A full description along with the workaround you currently have to use is given at https://tex.stackexchange.com/questions/641909/package- option-for-xcolor-is-not-being-properly-used-in-beamer . It would be great if an updated version of texlive with the newer version of jammy could be packaged up for jammy. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: texlive-full 2021.20220204-1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 15 15:59:03 2022 InstallationDate: Installed on 2020-08-03 (773 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: texlive-base UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1989737/+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 1969910] Re: Firefox lost passwords, saved tabs, settings after upgrading to Ubuntu 22.04
I just updated to Ubuntu 22.04.1 LTS on 9/13/22 and I lost my profile in the new FireFox snap world. So, I drilled down to where the profiles are in my /home directory (~, in Linux speak, it's /home/[username]/[path_to_firefox_directory]) and edited the profiles.ini file. My old profile was in that directory as *.default and for some reason FF didn't find it and created a new one. I had two *.default files. It's just some letters and numbers made up randomly by FF and looks something like 9sQt7fr2.default (as an example). So I had two profiles with the extension 'default' and FF used the new one it created after the update. The one FF uses is specified in the file called 'profiles.ini'. So in 'profiles.ini' I changed it to my other original *.default and it worked. I got my world back! Simple as that! So in more detail: In the FF url bar I typed in 'about:profiles' and FF showed the new, empty profile that comes with the new install under the new snap. To edit 'profiles.ini' the path you need to use in terminal is shown there in 'about:profiles'. In my case I found my profiles in /home/[username]/snap/firefox/common/.mozilla/firefox In 'about:profiles' use the one labeled 'Root Directory' I copied that path and then... In terminal, change directories, type: cd [copied_path] and then list the directory using ls and MAYBE, hopefully you will find two *.default files. The one not shown in about:profiles is probably your old profile. It was in my case. Of course, there, you will also find the 'profiles.ini' file. So, I just added the old profile to the profiles.ini file. In my case profiles.ini from the update looked like this: (in terminal type in cat profile.ini) [Profile0] Name=default IsRelative=1 Path=6wcfqbmw.default <---this is the new one FF created after the update. Default=1 [General] StartWithLastProfile=1 Version=2 - After I edited 'profiles.ini' my new 'profiles.ini' looks like this: [Profile1] Name=MyLinuxWorld IsRelative=1 Path=6wcfqbmw.MyLinuxWorld <---this is the new one FF created after the update the extension altered by me. [Profile0] Name=default IsRelative=1 Path=76qngg3y.default <---this is my original profile that I typed in Default=1 [General] StartWithLastProfile=1 Version=2 - NOTE: [Profile0] is the first profile, [Profile1] is the second profile, and so on... -Now restart FF. Go to about:profiles and voila, there are now two profiles the way I did it. I kept the profile FF made after the update because I opened a bunch of tabs as I searched this problem out and wanted to keep that world. (I'd love to put those tabs into my original profile, but I haven't figured that out yet other than to copy every url into my editor then go to my original profile and type them in again. That sounds like work to me!) In 'about:profiles', if your old profile is not the default, then choose 'Set as default profile'. Restart FF again and then your old profile will become the default, in my case all my passwords and bookmarks were there. Tabs you had opened will probably be gone, but that's more of an inconvenience than a really life altering problem like losing your profile could be. In my case, Ubuntu warned me that snap was being updated and so I bookmarked all my open tabs first before I let software updater install the new system. Now all I had to do was reopen the bookmarks and I got my world back. I only did that just because I was nervous about things, bookmarking my open tabs. Obviously, after the fact you lose the tabs you had opened if they weren't bookmarked, but like I say everything else was there, passwords, history, themes, etc. >From your history you can probably figure out what tabs you had opened if you can get your old profile back. NOTE: Since I kept that 'new' profile [Profile1], I had to change the file extension of the "new" *.default that FF created after the update, which in this example is "MyLinuxWorld". You can use the 'profiles.ini' created by FF and simply make up your own extension for your username. Look closely at the examples above and you will see the 'name=' line in [Profile0] is "default" per FF's install and [Profile1] 'name=' is the one I made up 'MyLinuxWorld'. Two lines to change in profiles.ini: path= :the filename.ext of the 'profile' file usually *.default name= :the extension you choose for your new profile name just the ext, 'default' in [Profile0]. If you want to use the profile FF made after the update, make a new profile [Profile1]. Look at my examples above. Of course, before you go making these changes, make a backup, in my case I have the original as profile.ini.bak1 Use the command cp profile.ini profile.ini.bak1 at the command line. Then copy the path from the command line in terminal (or from 'about:profiles' in FF) into the editor in Ubuntu and open profiles.ini and make the suggested changes. When editing profiles.ini of course use your own username and get the correct
[Desktop-packages] [Bug 1989418] Re: [BPO] libreoffice 7.3.6 for focal
I'm confused, are you asking for a backport to the backports pocket or an SRU? The bug refers to SRU in multiple places. Backports in the backports pocket are NOT SRUs so its critical to identify which process and goal you have in mind - SRU or backport. -- 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/1989418 Title: [BPO] libreoffice 7.3.6 for focal Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: In Progress Bug description: [Impact] * LibreOffice 7.3.6 is in its sixth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.6_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988744 and its backport is currently provided by the LibreOffice Fresh PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages * Previous backport of 7.3.5 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1987045 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.3.5 is currently released in focal-backports. * 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. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.6-0ubuntu0.22.04.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [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_73/1900/ * 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. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/amd64/libr/libreoffice/20220904_103401_f46f5@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/arm64/libr/libreoffice/20220904_144020_84b5b@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/armhf/libr/libreoffice/20220904_113245_95845@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/ppc64el/libr/libreoffice/20220904_100953_3af7d@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/s390x/libr/libreoffice/20220904_095636_d0c69@/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 50 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/1989418/+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 1989733] Re: [FFE] build ubuntu-desktop package for riscv64
** Patch added: "ubuntu-meta-1.493..1.494.debdiff" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1989733/+attachment/5616101/+files/ubuntu-meta-1.493..1.494.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1989733 Title: [FFE] build ubuntu-desktop package for riscv64 Status in ubuntu-meta package in Ubuntu: New Bug description: Currently the ubuntu-desktop and the ubuntu-desktop-minimal package are missing for riscv64. This makes it difficult for users to upgrade from a server image to a full desktop. Ubuntu-destkop and Ubuntu-desktop-minimal are just meta packages. So the only problems that could arise for a user are: * the package is not installable if a dependency is missing * the numerous dependent packages may exceed the disk space. As the riscv64 packages have not existed before and are not included in any images there is no regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1989733/+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 1989615] Re: gnome-shell crashed with SIGABRT in assertion [libmutter:ERROR:../src/backends/meta-monitor-manager.c:1690:get_connector_type_name: code should not be reached]
** Information type changed from Private to Public -- 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/1989615 Title: gnome-shell crashed with SIGABRT in assertion [libmutter:ERROR:../src/backends/meta-monitor- manager.c:1690:get_connector_type_name: code should not be reached] Status in mutter package in Ubuntu: Fix Committed Bug description: Started Ubuntu Kinetic (22.10) Desktop for Raspberry Pi on a Pi 4 with 4GB of RAM. One notable thing about this particular setup is that the display is the Pimoroni Hyperpixel which has an unusual resolution of 480x800 (portrait by default) or 800x480 landscape, which seems to be too low for the vast majority of GNOME applications unfortunately. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-1001.3-raspi 5.19.0-rc8 Uname: Linux 5.19.0-1001-raspi aarch64 ApportVersion: 2.23.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Greeter:GNOME Date: Wed Sep 14 20:40:05 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: ImageMediaBuild: 20220829 ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/false RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 Signal: 6 SourcePackage: gnome-shell StacktraceTop: g_assertion_message () from /lib/aarch64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/aarch64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/aarch64-linux-gnu/libmutter-11.so.0 ?? () from /lib/aarch64-linux-gnu/libffi.so.8 ?? () from /lib/aarch64-linux-gnu/libffi.so.8 Title: gnome-shell crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1989615/+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 1989733] [NEW] [FFE] build ubuntu-desktop package for riscv64
Public bug reported: Currently the ubuntu-desktop and the ubuntu-desktop-minimal package are missing for riscv64. This makes it difficult for users to upgrade from a server image to a full desktop. Ubuntu-destkop and Ubuntu-desktop-minimal are just meta packages. So the only problems that could arise for a user are: * the package is not installable if a dependency is missing * the numerous dependent packages may exceed the disk space. As the riscv64 packages have not existed before and are not included in any images there is no regression risk. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1989733 Title: [FFE] build ubuntu-desktop package for riscv64 Status in ubuntu-meta package in Ubuntu: New Bug description: Currently the ubuntu-desktop and the ubuntu-desktop-minimal package are missing for riscv64. This makes it difficult for users to upgrade from a server image to a full desktop. Ubuntu-destkop and Ubuntu-desktop-minimal are just meta packages. So the only problems that could arise for a user are: * the package is not installable if a dependency is missing * the numerous dependent packages may exceed the disk space. As the riscv64 packages have not existed before and are not included in any images there is no regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1989733/+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 1989582] Re: gnome-shell 43 (and mutter) Xorg sessions stutter and freeze
** Changed in: gnome-shell Status: New => 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/1989582 Title: gnome-shell 43 (and mutter) Xorg sessions stutter and freeze Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: In Progress Bug description: gnome-shell 43 (and mutter) Xorg sessions stutter and freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1989582/+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 1989572] Re: libglib2.0-0-dbgsym dependency mismatch with libglib2.0-0
Thanks for the report, that should be fixed now ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => High ** Changed in: glib2.0 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1989572 Title: libglib2.0-0-dbgsym dependency mismatch with libglib2.0-0 Status in glib2.0 package in Ubuntu: Fix Released Bug description: This maybe has to be reassigned to affect 'ddeb-retriever', but the web form doesn't allow setting it as package for reporting. 'libglib2.0-0' was updated in the bionic-updates repository, but 'libglib2.0-0-dbgsym' was not correspondingly updated in the ddebs repository: # apt-cache policy libglib2.0-0 libglib2.0-0: Installed: 2.56.4-0ubuntu0.18.04.9 Candidate: 2.56.4-0ubuntu0.18.04.9 Version table: *** 2.56.4-0ubuntu0.18.04.9 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.56.1-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages # apt-cache policy libglib2.0-0-dbgsym libglib2.0-0-dbgsym: Installed: (none) Candidate: 2.56.1-2ubuntu1 Version table: 2.56.1-2ubuntu1 500 500 http://ddebs.ubuntu.com bionic/main amd64 Packages Due to this, the package 'libglib2.0-0-dbgsym' is not installable with apt-get: # apt-get update && apt-get install libglib2.0-0-dbgsym [...] The following packages have unmet dependencies: libglib2.0-0-dbgsym : Depends: libglib2.0-0 (= 2.56.1-2ubuntu1) but 2.56.4-0ubuntu0.18.04.9 is to be installed E: Unable to correct problems, you have held broken packages. Using `--force-yes` or `--allow-downgrades` does not make any difference. These are the ddebs repositories in use: # cat /etc/apt/sources.list.d/ddebs.list deb http://ddebs.ubuntu.com bionic main restricted universe multiverse deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse deb http://ddebs.ubuntu.com bionic-proposed main restricted universe multiverse System is Ubuntu 18.04 Bionic: # lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1989572/+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 1989515] Re: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic
Thank you for the quick response! I'll do a test today or tomorrow and let you know the result. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1989515 Title: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic Status in poppler package in Ubuntu: Fix Released Bug description: Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic but "goo/gmem.h" still has the statement `#include "GooCheckedOps.h"`. As a result, a compile error will happen when compiling code that uses poppler: /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h: No such file or directory I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the previous version) installed. I confirmed that "goo/gmem.h" doesn't have the `#include "GooCheckedOps.h"` statement. I found this issue when I was compiling gdal on my Docker container. The Docker container was installed the problematic version 0.62.0-2ubuntu2.13 and I ran into the "No such file or directory" error. I compiled on both Amd64 and AArch64 and I ran into the same error on both platforms. By reading the diff between 2.12 and 2.13 (https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz), the patch looks quite right. But when I examined the contents of the built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h". Kind of weird, because the problem seems to be caused by applying "CVE-2022-38784-pre.patch" in half: the first part that creates "goo/GooCheckedOps.h" was not applied during the build process and the second part that modifies "goo/gmem.h" was applied. Any thoughts? Ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1989515/+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 1703377] Re: Gnome online account login prevents paste or autotype
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1703377 Title: Gnome online account login prevents paste or autotype Status in gnome-online-accounts: New Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: On entering Login data to an online account such as google. Using keepass as password manager I now can not enter my password via paste nor via autotype. Trying any of them results in an invalid password. Ubuntu 16.10 - GNOME Shell 3.20.4 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1703377/+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 1988292] Re: Voices aren't listed
** Tags removed: verification-needed ** Tags added: verification-done -- 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/1988292 Title: Voices aren't listed Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Jammy: Fix Committed Bug description: * Impact In the default speech-dispatcher configuration no voices are listed while some are installed. Voices are needed for speechsynthesis to work in webbrowser as described on bug #1987979 * Test case $ spd-say -L should list voices the fix is also part of making speech-dispatcher work with firefox but more fixes are needed for the feature to work in the snap * Regression potential The wrong voices could be selected, check that spd-say respects the selected voice and language. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1988292/+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 1988292] Re: Voices aren't listed
As much as I can say: - I had the bug (hence sebastian filing this) - I am on proposed - 0.11.1-1ubuntu2 is installed (I apt purge'd it and reinstalled) - I cannot reproduce anymore, neither in `spd-say -L` nor in Firefox. Looks like the backport works. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/1988292 Title: Voices aren't listed Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Jammy: Fix Committed Bug description: * Impact In the default speech-dispatcher configuration no voices are listed while some are installed. Voices are needed for speechsynthesis to work in webbrowser as described on bug #1987979 * Test case $ spd-say -L should list voices the fix is also part of making speech-dispatcher work with firefox but more fixes are needed for the feature to work in the snap * Regression potential The wrong voices could be selected, check that spd-say respects the selected voice and language. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1988292/+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 1989304] Re: gnome-shell 43.rc SIGSEGV in g_str_hash() via on_directory_profile_ready() [meta-color-store.c:94]
** Changed in: mutter Status: New => 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/1989304 Title: gnome-shell 43.rc SIGSEGV in g_str_hash() via on_directory_profile_ready() [meta-color-store.c:94] Status in Mutter: Fix Released Status in mutter package in Ubuntu: In Progress Bug description: Unable to login to gnome session(bug#1989240). ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~rc-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 12 10:51:32 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1662686872 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/thelastline RelatedPackageVersions: mutter-common 43~rc-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_steal () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-11.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: Upgraded to kinetic on 2022-09-07 (5 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1989304/+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 1989714] Re: FFE: Switch dependencies from webkitgtk 4.0 to 4.1
** Changed in: webkit2gtk (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1989714 Title: FFE: Switch dependencies from webkitgtk 4.0 to 4.1 Status in webkit2gtk package in Ubuntu: New Bug description: Impact -- The webkit2gtk source package provides 3 different API builds: - 4.0 for GTK3 using libsoup2 - 4.1 for GTK3 using libsoup3 (otherwise same as 4.0) - 5.0 for GTK4 using libsoup3 I am requesting a Feature Freeze Exception to be able to switch dependencies from 4.0 to 4.1 for Ubuntu 22.10 The Desktop Team has an outstanding todo item to stop using libsoup2 in main. We got more than halfway done for Ubuntu 22.10 but still won't finish for 22.10, even with this Feature Freeze Exception but it gets us closer. https://people.canonical.com/~ubuntu-archive/transitions/html/libsoup3-main.html It's bad for security updates that we need to do so many builds as part of the webkit2gtk source package. We still won't be able to drop the 4.0 build for 22.10 but this gets us closer for 23.04. Affected Packages - https://people.canonical.com/~ubuntu-archive/transitions/html/webkit2gtk-4.0.html Example --- https://salsa.debian.org/gnome-team/gnome-feeds/-/commit/32183b4 https://salsa.debian.org/gnome-team/gnome-feeds/-/commit/fc58345 Many packages will also need their meson.build/configure.ac/CMakeLists.txt patches to look for 4.1 instead of 4.0 Future Goals Stop building the webkitgtk 4.0 API for Ubuntu 23.04 Stop using libsoup2 in main for Ubuntu 23.04 Stop building libsoup2 for Ubuntu 23.10 Debian will begin freezing in early January and will be frozen for several months while they prepare for the Debian 12 release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1989714/+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 1989714] [NEW] FFE: Switch dependencies from webkitgtk 4.0 to 4.1
Public bug reported: Impact -- The webkit2gtk source package provides 3 different API builds: - 4.0 for GTK3 using libsoup2 - 4.1 for GTK3 using libsoup3 (otherwise same as 4.0) - 5.0 for GTK4 using libsoup3 I am requesting a Feature Freeze Exception to be able to switch dependencies from 4.0 to 4.1 for Ubuntu 22.10 The Desktop Team has an outstanding todo item to stop using libsoup2 in main. We got more than halfway done for Ubuntu 22.10 but still won't finish for 22.10, even with this Feature Freeze Exception but it gets us closer. https://people.canonical.com/~ubuntu-archive/transitions/html/libsoup3-main.html It's bad for security updates that we need to do so many builds as part of the webkit2gtk source package. We still won't be able to drop the 4.0 build for 22.10 but this gets us closer for 23.04. Affected Packages - https://people.canonical.com/~ubuntu-archive/transitions/html/webkit2gtk-4.0.html Example --- https://salsa.debian.org/gnome-team/gnome-feeds/-/commit/32183b4 https://salsa.debian.org/gnome-team/gnome-feeds/-/commit/fc58345 Many packages will also need their meson.build/configure.ac/CMakeLists.txt patches to look for 4.1 instead of 4.0 Future Goals Stop building the webkitgtk 4.0 API for Ubuntu 23.04 Stop using libsoup2 in main for Ubuntu 23.04 Stop building libsoup2 for Ubuntu 23.10 Debian will begin freezing in early January and will be frozen for several months while they prepare for the Debian 12 release. ** Affects: webkit2gtk (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: kinetic ** Changed in: webkit2gtk (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1989714 Title: FFE: Switch dependencies from webkitgtk 4.0 to 4.1 Status in webkit2gtk package in Ubuntu: Incomplete Bug description: Impact -- The webkit2gtk source package provides 3 different API builds: - 4.0 for GTK3 using libsoup2 - 4.1 for GTK3 using libsoup3 (otherwise same as 4.0) - 5.0 for GTK4 using libsoup3 I am requesting a Feature Freeze Exception to be able to switch dependencies from 4.0 to 4.1 for Ubuntu 22.10 The Desktop Team has an outstanding todo item to stop using libsoup2 in main. We got more than halfway done for Ubuntu 22.10 but still won't finish for 22.10, even with this Feature Freeze Exception but it gets us closer. https://people.canonical.com/~ubuntu-archive/transitions/html/libsoup3-main.html It's bad for security updates that we need to do so many builds as part of the webkit2gtk source package. We still won't be able to drop the 4.0 build for 22.10 but this gets us closer for 23.04. Affected Packages - https://people.canonical.com/~ubuntu-archive/transitions/html/webkit2gtk-4.0.html Example --- https://salsa.debian.org/gnome-team/gnome-feeds/-/commit/32183b4 https://salsa.debian.org/gnome-team/gnome-feeds/-/commit/fc58345 Many packages will also need their meson.build/configure.ac/CMakeLists.txt patches to look for 4.1 instead of 4.0 Future Goals Stop building the webkitgtk 4.0 API for Ubuntu 23.04 Stop using libsoup2 in main for Ubuntu 23.04 Stop building libsoup2 for Ubuntu 23.10 Debian will begin freezing in early January and will be frozen for several months while they prepare for the Debian 12 release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1989714/+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 1970921] Re: Drag and drop does not work
I have the same problem, drag and drop fails in many forms on Wayland (not on X11). If you repeatedly drag and drop from Nautilus to Chrome (for example), it works like 10% of the time. - sometimes it works - sometimes it pastes a text path instead of the file - sometimes it does nothing When opening a Chrome tab by dropping a file, often I see a wrong path like this: file:///home/thisuser/Downloads/some_document.docx-34:-56:63:64 It seems like the random addendum -34:-56:63:64 is causing the fail. I'm using up to date Ubuntu 22.04, Gnome 42.4 on Wayland. Drag and drop is failing for me since Ubuntu 22.04 release, when I switched to Wayland. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1970921 Title: Drag and drop does not work Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Triaged Bug description: After upgrading Ubuntu to 22.04 drag and dropping files from nautilus to web browser (chromium, google chrome / apps like seafile, etc.) do not work. Also drag & drop from nautilus to slack desktop app does not work. If making several attempts, it might suddenly work with nth attempt. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 13:32:48 2022 InstallationDate: Installed on 2016-11-22 (1983 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-04-29 (0 days ago) usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1970921/+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 1750199] Re: Blurry Icons on HighDPI
Launchpad has imported 16 comments from the remote bug at https://bugs.documentfoundation.org/show_bug.cgi?id=144583. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2021-09-18T08:44:30+00:00 Pmenzel+bugs-documentfoundation-org wrote: Description: Using Debian sid/unstable with LibreOffice 7.2.1-1 (and GNOME), the icons are blurry on a HiDPI screen. This is *not* a regression. A similar bug is in Ubuntu’s bug tracker [1]. [1]: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1750199 Steps to Reproduce: 1. Start LibreOffice on a HiDPI screen Actual Results: Notice blurry icons. Expected Results: Sharp icons. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.14; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: de-DE Debian package version: 1:7.2.1-1 Calc: threaded Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1750199/comments/2 On 2021-09-19T08:19:33+00:00 Heiko-tietze-g wrote: Tools > Options > View let you pick different themes and icon sizes. Guess you use Elementary and Automatic but please try the SVG variant. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1750199/comments/3 On 2021-09-21T16:08:54+00:00 Pmenzel+bugs-documentfoundation-org wrote: (In reply to Heiko Tietze from comment #1) > Tools > Options > View let you pick different themes and icon sizes. Guess > you use Elementary and Automatic but please try the SVG variant. *Elementary (SVG)* is selected. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1750199/comments/4 On 2022-04-05T04:00:39+00:00 Jay Chu wrote: I can reproduce this on Arch Linux and Gnome 41 Wayland with my 13-inch 2K laptop: Version: 7.3.2.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 16; OS: Linux 5.17; UI render: default; VCL: gtk3 Locale: ja-JP (ja_JP.UTF-8); UI: en-US 7.3.2-1 Calc: threaded The non-SVG version is a bit blurry as expected, but the SVG version blurry even more, which is annoying. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1750199/comments/6 On 2022-09-13T12:15:26+00:00 Hossein-7 wrote: Created attachment 182408 Blurry toolbar icons I can reproduce this issue, as I use HiDPI display with 2x scaling on Ubuntu 22.04. I use this icon theme: Breeze (SVG + Dark) Toolbar icons look blurry in 7.4: Version: 7.4.0.3 / LibreOffice Community Build ID: f85e47c08ddd19c015c0114a68350214f7066f5a CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: fa-IR (en_US.UTF-8); UI: en-US Calc: threaded And also in the latest dev master 7.5: Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: c0d09eb46665a0b2ab86f263cc95662f406d83d2 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1750199/comments/7 On 2022-09-13T13:19:49+00:00 Hossein-7 wrote: @Caolan I think this is related to the way icons are rasterized and get rendered. If someone uses a 2x scaling, the underlying rasterizer does the rasterization for a smaller size, and the result becomes blurry. Do you have any idea how to draw vectors better in vcl/gtk? Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1750199/comments/8 On 2022-09-13T17:31:56+00:00 Vstuart-foote wrote: (In reply to Hossein from comment #5) > @Caolan > I think this is related to the way icons are rasterized and get rendered. If > someone uses a 2x scaling, the underlying rasterizer does the rasterization > for a smaller size, and the result becomes blurry. > Do you have any idea how to draw vectors better in vcl/gtk? @Hossein, * So please check the cache in your user profile. With a 200% scaling you should see a breeze_svg directory and sub-directory "200" that should contain the entire Breeze icon theme resampled to PNG icons at ~64x64px. If used those should be very crisp. If not there then the icons are not being rebuilt and some lower resolution 32px icons are simply being scaled 200% with other UI graphics. See also bug 115439 Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1750199/comments/9
[Desktop-packages] [Bug 1965123] Re: Active launchers area pixels (corners) missing
It seems to be something when loading the session, because after locking and unlocking the screen, it goes back to normal. ** Attachment added: "Captura de tela de 2022-09-14 13-04-59.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965123/+attachment/5616056/+files/Captura%20de%20tela%20de%202022-09-14%2013-04-59.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1965123 Title: Active launchers area pixels (corners) missing Status in Dash to dock: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 development branch @ 16/03/2022 after yesterdays updates to gnome 42 beta the docks area around the active launcher is missing 4 pixels in the corners when hovering mouse over them switching to another active launchers can be reproduced non-active area around launchers does not suffer this bug ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 12:55:20 2022 PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1965123/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
Re comment #27 It's NOT only snap. This also happens to me with: • The flatpak version of Firefox • The Appimage version of Firefox • Chrome installed from the official Chrome PPA I have seen confirmation of this from others. Thus Snap, Flatpak, Appimage and PPA are all affected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 1979891] Re: Firefox becomes unusable when adjusting window size
Launchpad has imported 2 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1790527. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2022-09-13T03:01:49+00:00 Christopher Beland wrote: Created attachment 9294363 about:support.json User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:104.0) Gecko/20100101 Firefox/104.0 Steps to reproduce: Upgraded to snap version of Firefox on Ubuntu, used browser normally. Actual results: After a while, scroll bars stop sliding smoothly. I can click on the slider, hold, and move to the desired part of the page, but while doing that there is no animation showing what I'm doing. Hovering over a hyperlink no longer causes the URL to show up at the bottom of the screen. Then when I adjust window size, sometimes the window fails to render inside its boundaries properly. In particular, if I unplug my external monitor (which is in portrait orientation and connected to my laptop via a USB-C port that's converted to HDMI) this forces Firefox windows to redraw on my built-in monitor (which is in landscape orientation) and I immediately experience problems with windows not rendering in their boundaries properly. When a window is in this maladjusted state, the contents don't fill the window, not all the controls are visible, and clicks are offset, so if I click on one spot, the window behaves as if I clicked on a different spot (so it's impossible to use Firefox in that window anymore). Not all windows are broken, so I can fix this problem for a given window by moving all its tabs to a new window, one by one. Restarting Firefox cures this problem for all windows. Expected results: No rendering problems. FTR, originally reported here, and I was asked to re-report to mozilla.org: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1979891 Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1979891/comments/8 On 2022-09-13T03:31:52+00:00 Release-mgmt-account-bot wrote: The [Bugbug](https://github.com/mozilla/bugbug/) bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1979891/comments/10 ** Changed in: firefox Status: Unknown => New -- 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/1979891 Title: Firefox becomes unusable when adjusting window size Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: OS version: Ubuntu 22.04 LTS Firefox version: 1:1snap1-0ubuntu2 - 101.0.1 (64-bit) Sometimes when I adjust the size of a Firefox window, that window becomes messed up: the contents don't fill the window, not all the controls are visible, and clicks are offset, so if I click on one spot, the window behaves as if I clicked on a different spot (so it's impossible to use Firefox in that window anymore). I seem to remember being able to fix this by dragging and dropping the window onto a different monitor or workspace in the GNOME Activities view, but I'm currently experiencing the problem and that is not helping. I took a screenshot of what's currently going on (attached) which happened when I tried to maximize the window. This is on a laptop with an external monitor that I'm using in portrait mode, via a USB-C connection that's converted to HDMI. I had plugged in to the external monitor a few minutes before this happens, and plugging in or possibly unplugging seems to make this bug more likely. This is a relatively new problem, starting within the last few weeks. (Maybe after I switched to the snap version of Firefox? I guess that was when I upgraded from the previous LTS version of Ubuntu.) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 25 15:23:13 2022 DistUpgraded: 2022-05-27 14:03:05,108 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-39-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes,
[Desktop-packages] [Bug 1989590] Re: Can't click on Dash items if status drop-down is shown
Managed to record with OBS Studio. You can hear the mouse clicks through the microphone ;) ** Attachment added: "recording of the problem" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989590/+attachment/5616045/+files/2022-09-15%2012-44-59.mkv -- 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/1989590 Title: Can't click on Dash items if status drop-down is shown Status in gnome-shell package in Ubuntu: Incomplete Bug description: Steps: 1. open any of the system status drop-downs 2. click on any Dash item Expected: 1. the system status drop-down goes away 2. the clicked item is activated Current: 1. nothing happens ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 16:49:59 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (13 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989590/+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 1989590] Re: Can't click on Dash items if status drop-down is shown
Screen capture isn't working very well… but you'd see exactly that. As long as the drop-down is open, the dash doesn't show hover highlights and no actions are performed. Note I use dual screens, and the external screen is set as the primary one - maybe that has bearing on the problem? -- 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/1989590 Title: Can't click on Dash items if status drop-down is shown Status in gnome-shell package in Ubuntu: Incomplete Bug description: Steps: 1. open any of the system status drop-downs 2. click on any Dash item Expected: 1. the system status drop-down goes away 2. the clicked item is activated Current: 1. nothing happens ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 16:49:59 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (13 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989590/+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 1989626] Re: UIFe: fonts-noto-color-emoji & other updates for Unicode 15
** Description changed: Justification - Unicode 15 was release September 13. This is an annual release. It's expected that the latest Ubuntu will support the latest stable Unicode release. This is required for compatibility with Internet communications with other platforms that will be quickly adopting the new emoji characters. The release happened too late for related upstream releases to happen by Ubuntu's User Interface Freeze on September 15 and be packaged. Therefore, I request a UIFe for Ubuntu 22.10 for Unicode 15 packages. More details Google will be releasing a new version of fonts-noto-color-emoji "later this week" but it looks like it won't be released in time for Ubuntu's User Interface Freeze. We also need to update glib and pango for the new release so that new composite emoji like "pink heart" display correctly. https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2877 There isn't an upstream pango merge request or issue but I think it will be needed. - We also need new versions of unicode-data, node-unicode, and gucharmap. - There are probably some other minor universe packages that we should sync from Debian if we see they are related to Unicode 15. I don't have packaging ready for these changes yet but I'm requesting the UIFe early. + + Likely affected packages + + fonts-noto-color-emoji + nototools + glib2.0 + pango1.0 + node-unicode + maybe more universe packages 22.04 LTS - We have done SRUs of new fonts-noto-color-emoji releases to older LTSes before. We may do it again but that will be one or more separate bugs. References -- https://blog.emojipedia.org/whats-new-in-unicode-15-0/ https://developers.googleblog.com/2022/09/updates-to-emoji-new- characters-animation-colors-and-more.html https://unicode.org/versions/Unicode15.0.0/ Email to Docs List: https://lists.ubuntu.com/archives/ubuntu-doc/2022-September/020889.html I don't believe translators need to be notified about this UIFe but let me know if I should email them anyway. ** Description changed: Justification - Unicode 15 was release September 13. This is an annual release. It's expected that the latest Ubuntu will support the latest stable Unicode release. This is required for compatibility with Internet communications with other platforms that will be quickly adopting the new emoji characters. The release happened too late for related upstream releases to happen by Ubuntu's User Interface Freeze on September 15 and be packaged. Therefore, I request a UIFe for Ubuntu 22.10 for Unicode 15 packages. More details Google will be releasing a new version of fonts-noto-color-emoji "later this week" but it looks like it won't be released in time for Ubuntu's User Interface Freeze. We also need to update glib and pango for the new release so that new composite emoji like "pink heart" display correctly. https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2877 There isn't an upstream pango merge request or issue but I think it will be needed. There are probably some other minor universe packages that we should sync from Debian if we see they are related to Unicode 15. I don't have packaging ready for these changes yet but I'm requesting the UIFe early. Likely affected packages fonts-noto-color-emoji nototools glib2.0 pango1.0 - node-unicode + node-unicode-data maybe more universe packages 22.04 LTS - We have done SRUs of new fonts-noto-color-emoji releases to older LTSes before. We may do it again but that will be one or more separate bugs. References -- https://blog.emojipedia.org/whats-new-in-unicode-15-0/ https://developers.googleblog.com/2022/09/updates-to-emoji-new- characters-animation-colors-and-more.html https://unicode.org/versions/Unicode15.0.0/ Email to Docs List: https://lists.ubuntu.com/archives/ubuntu-doc/2022-September/020889.html I don't believe translators need to be notified about this UIFe but let me know if I should email them anyway. ** Description changed: Justification - Unicode 15 was release September 13. This is an annual release. It's expected that the latest Ubuntu will support the latest stable Unicode release. This is required for compatibility with Internet communications with other platforms that will be quickly adopting the new emoji characters. The release happened too late for related upstream releases to happen by Ubuntu's User Interface Freeze on September 15 and be packaged. Therefore, I request a UIFe for Ubuntu 22.10 for Unicode 15 packages. More details Google will be releasing a new version of fonts-noto-color-emoji "later this week" but it looks like it won't be released
[Desktop-packages] [Bug 1790608] Re: [snap] Libreoffice/Firefox do not open files from thunderbird (more general: from /tmp)
Is there a way to grant Snap access to the /tmp/ directory? I googled for this, but only found a workaround (suggestion to create ~/tmp and symlink that as /tmp) which defies the idea of having a /tmp/ (which clears on reboot). This issue is still around in 22.04, and is quite inconvenient as many applications (like firefox/jammy,now 1:1snap1-0ubuntu2 amd64) lean on there being an accessible /tmp/ dir. https://forum.snapcraft.io/t/firefox-snap-no-access-to-gvfs-and- tmp/27253/5 has more details on this, but no solution. -- 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/1790608 Title: [snap] Libreoffice/Firefox do not open files from thunderbird (more general: from /tmp) Status in firefox package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: I received a document via e-mail in Thunderbird. I have the Libreoffice snap package installed. When I want to open the document from Thunderbird, I see the Libreoffice splash screen, and then a dialog stating "/tmp/mozilla_0/.docx does not exist." The same dialog appears when I navigate to the folder in Files and want to open it. When I copy the file to my desktop, however, I can open it without problems. I guess the source of the issue is confinement, that the Libreoffice snap can only access files from $HOME. But this breaks the case where thunderbird creates a temporary copy in /tmp. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1790608/+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 1980839] Re: thunderbird -compose returns error since the 102 snap update?
You get the same error message simply running "thunderbird -compose" (while a thuderbird snap window is alread yopen). This is the log from journald: sept. 15 10:33:42 paulision systemd[978]: Started snap.thunderbird.thunderbird.fd02926d-30bb-4c8b-8f25-525c118b1819.scope. sept. 15 10:33:47 paulision dbus-daemon[1040]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/a11y/bus" interface="org.freedesktop.DBus.Properties" member="Get" mask="send" name="org.a11y.Bus" pid=127887 label="snap.thunderbird.thunderbird" peer_pid=1879 peer_label="unconfined" sept. 15 10:33:47 paulision audit[127887]: SECCOMP auid=1000 uid=1000 gid=1000 ses=2 pid=127887 comm="thunderbird-bin" exe="/snap/thunderbird/249/thunderbird-bin" sig=0 arch=c03e syscall=314 compat=0 ip=0x7f353321c73d code=0x5 sept. 15 10:33:47 paulision kernel: audit: type=1326 audit(1663230827.748:420): auid=1000 uid=1000 gid=1000 ses=2 pid=127887 comm="thunderbird-bin" exe="/snap/thunderbird/249/thunderbird-bin" sig=0 arch=c03e syscall=314 compat=0 ip=0x7f353321c73d code=0x5 p.s. sorry for the unreadable log. -- 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/1980839 Title: thunderbird -compose returns error since the 102 snap update? Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to the latest thunderbird 102.0.1 snap on Ubuntu 20.04, it is no longer possible to open mailto links from the firefox snap in thunderbird. When clicking a mailto link in the firefox 102.0.1 snap, thunderbird returns the following error message: "Thunderbird is already running, but is not responding. To use Thunderbird, you must first close the existing Thunderbird process, restart your device, or use a different profile." The issue appears related to the thunderbird update as there was no issue opening links in the previous 91 version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1980839/+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 1988301] Re: Does not implement data-ciphers, only cipher which OpenVPN 2.5+ ignores, hence can fail to connect
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager-openvpn (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1988301 Title: Does not implement data-ciphers, only cipher which OpenVPN 2.5+ ignores, hence can fail to connect Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: It's no longer possible to use the cipher option in NetworkManager as it's ignored by OpenVPN; and the default list of data-ciphers is applied, making it impossible to connect to an AES-128-CBC endpoint from NetworkManager. There does not appear any way to forward the data-ciphers config, even if I hand edited the nmconnection file to add a data-ciphers line it is ignored. More insight is available to Canonical folks in https://rt.admin.canonical.com/Ticket/Display.html?id=153000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1988301/+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 1981966] Re: [SRU] libreoffice 7.3.5 for jammy
-- 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/1981966 Title: [SRU] libreoffice 7.3.5 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Released Bug description: [Impact] * LibreOffice 7.3.5 is in its fifth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.5_release * Version 7.3.4 is currently released in jammy. For a list of fixed bugs compared to 7.3.4 see the list of bugs fixed in the release candidates of 7.3.5 (that's a total of 83 bugs): https://wiki.documentfoundation.org/Releases/7.3.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.3.5/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_73/1797/ * 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. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20220719_091411_74233@/log.gz * [arm64] ... * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20220719_110142_388ca@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20220719_082728_0b9aa@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20220719_080609_7c067@/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 83 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/1981966/+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 1988744] Re: [SRU] libreoffice 7.3.6 for jammy
Upgraded libreoffice from 1:7.3.5-0ubuntu0.22.04.1 to 1:7.3.6-0ubuntu0.22.04.1 from jammy-proposed in a clean and up-to-date jammy amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/1988744 Title: [SRU] libreoffice 7.3.6 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Committed Bug description: [Impact] * LibreOffice 7.3.6 is in its sixth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.6_release * Version 7.3.5 is currently released in jammy. For a list of fixed bugs compared to 7.3.5 see the list of bugs fixed in the release candidates of 7.3.6 (that's a total of 50 bugs): https://wiki.documentfoundation.org/Releases/7.3.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.3.6/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_73/1900/ * 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. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20220903_204748_cb772@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/arm64/libr/libreoffice/20220903_234903_5c5f9@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20220903_221954_4437b@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20220903_203030_f897a@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20220903_202914_32e82@/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 50 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/1988744/+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 1989418] Re: [BPO] libreoffice 7.3.6 for focal
-- 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/1989418 Title: [BPO] libreoffice 7.3.6 for focal Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: In Progress Bug description: [Impact] * LibreOffice 7.3.6 is in its sixth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.6_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988744 and its backport is currently provided by the LibreOffice Fresh PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages * Previous backport of 7.3.5 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1987045 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.3.5 is currently released in focal-backports. * 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. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.6-0ubuntu0.22.04.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [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_73/1900/ * 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. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/amd64/libr/libreoffice/20220904_103401_f46f5@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/arm64/libr/libreoffice/20220904_144020_84b5b@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/armhf/libr/libreoffice/20220904_113245_95845@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/ppc64el/libr/libreoffice/20220904_100953_3af7d@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/s390x/libr/libreoffice/20220904_095636_d0c69@/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 50 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/1989418/+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 1989582] Re: gnome-shell 43 (and mutter) Xorg sessions stutter and freeze
Fix proposed: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2625 -- 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/1989582 Title: gnome-shell 43 (and mutter) Xorg sessions stutter and freeze Status in GNOME Shell: New Status in mutter package in Ubuntu: In Progress Bug description: gnome-shell 43 (and mutter) Xorg sessions stutter and freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1989582/+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 1843392] Re: [snap] smart card reader no longer works
Whoops, sorry, I didn't mean to do that :) Basically though, this is causing issues for users in, e.g., Belgium, who want to do their tax declaration using Ubuntu and their electronic ID card. We are currently guiding users to use a non-snap browser (see https://eid.belgium.be/en/faq/why-it-not-possible-use-eid-software-snap- andor-flatpak#7636), and that's just sad. Comment #1 mentions a proposal to possibly resolve this. Since it explicitly asks for feedback, here is some (belated) feedback: First, PKCS#11 is about more than just smartcards. While allowing access to the pcscd socket from within the confined environment might allow some PKCS#11 modules to work, using this as a solution assumes all PKCS#11 modules use PC/SC as a backend API, and that's a wild assumption which is probably not true for everything. PKCS#11 is a generic cryptographic plug-in API, which allows hardware crypto modules of any kind (e.g., USB tokens, Networked HSMs, PCI(e) crypto accelerator boards, TPM modules, etc etc) to be plugged into anything. libnss uses it mostly for smartcards, and all browsers on Linux do so as well, but it can also be used by libreoffice and evolution to sign documents, it is extensively used by OpenDNSSEC for its crypto operations (going so far as providing a "SoftHSM" pkcs#11 module and not having native crypto), OpenSSH has had PKCS#11 code for a while to read and use certificates, and there are ways to hook PKCS#11 up to OpenSSL allowing for a large number of other applications to use HSMs. PKCS#11 modules could possibly access the hardware that they're written for using PC/SC (which this proposal could possibly work for, as long as the libpcsclite.so inside the snap and the pcscd outside the snap are sufficiently in sync), but this would not help PKCS#11 modules for USB tokens, TPM modules, PCI crypto accelerators, or possibly networked systems (depending on how the host application is confined). Apart from hardware, PKCS#11 modules may sometimes need to do other things as well. E.g., the Belgian eID middleware needs to occasionally show certain messages to the user, for which it uses the GnuPG pinentry framework to show a dialog box that integrates with the user's UI. Unless this is explicitly allowed by the snap, this won't work. There might be other similar issues with other PKCS#11 modules, which means that running them in a confined environment might just not work. So while this may be a solution for some PKCS#11 modules, it will not be a solution for all. Additionally, the PKCS#11 modules need to be installed and registered in host applications. For NSS-based applications, this means they need to be installed using "modutil". Chrome doesn't even *have* any UI to install PKCS#11 modules; Firefox does, but it's so basic and confusing to users that I developed a "browser.pkcs11" add-on API for Firefox to allow modules to be registered using an add-on. These work with native manifests (intentionally similar to native messaging manifests) and expect the PKCS#11 module to be in the location as specified by the manifest. Libreoffice just gave up and looks for a Firefox, Thunderbird, or Chromium configuration directory and reuses that. As such, just allowing access to a PKCS#11 module is not going to be sufficient if the user has no easy way to register the PKCS#11 modules. An alternate method (that I suggested at https://github.com/flatpak/xdg- desktop-portal/issues/662) is to use p11-kit-proxy to provide a bridge between the confined system and PKCS#11 modules. p11-kit-proxy could then communicate with the unconfined world using a dbus service. A proof-of-concept implementation of this exists (see the github link), and the only reason why it's not in common use right now is that p11-kit-proxy is not commonly added to, and enabled in, snaps. ** Bug watch added: github.com/flatpak/xdg-desktop-portal/issues #662 https://github.com/flatpak/xdg-desktop-portal/issues/662 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1843392 Title: [snap] smart card reader no longer works Status in chromium-browser package in Ubuntu: Confirmed Bug description: chromium uses the Netscape Cryptographic Module to access smartcards for authentication purposes. This stopped working when switching to the snap version. Chromium would normally access the setup in ~/.pki/nssdb/pkcs11.txt That file would refer to a library used to access the smart card. I.e /usr/lib/x86_64-linux-gnu/pkcs11/opensc- pkcs11.so The problem can be bypassed by manually launching chromium via: /snap/chromium/current/usr/lib/chromium-browser/chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1843392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1989325] Re: gnome-shell crashes on Lenovo Thinkpad P50 after upgrade to 22.04.1
Another common cause of crashes like this is the "nouveau" graphics driver. It's not very reliable so we recommend opening the "Additional Drivers" app and using it to install the NVIDIA driver instead. -- 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/1989325 Title: gnome-shell crashes on Lenovo Thinkpad P50 after upgrade to 22.04.1 Status in gnome-shell package in Ubuntu: Incomplete Bug description: I upgrade to Ubuntu 22.04 recently, and while upgrading and updating I also got a new bios version (1.69) for my Lenovo Thinkpad P50 laptop. Since then gnome-shell has been very unstable, crashing regularly on minor changes, like plugging in a monitor or going to suspend mode. Update: I just found out that the bug is not reproducable when logged in with Xorg instead of Wayland (https://askubuntu.com/questions/1428898/lenovo-p50-crashes-gnome- shell-regularly-after-upgrade-to-ubuntu-22-04-1-using) So we got a workaround and a culprit: Wayland ... in conjunction with something quite typical for my hardware maybe(?), Lenovo Thinkpad P50 (20ENCTO1WW) with Quadro M2000M discrete graphics ... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 12 09:49:57 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-09 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-09 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989325/+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 1989325] Re: gnome-shell crashes on Lenovo Thinkpad P50 after upgrade to 22.04.1
The most likely cause of this crash is locally installed extensions and you seem to have a few. Please start by deleting them: cd ~/.local/share/gnome-shell/ rm -rf extensions and then log in 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/1989325 Title: gnome-shell crashes on Lenovo Thinkpad P50 after upgrade to 22.04.1 Status in gnome-shell package in Ubuntu: Incomplete Bug description: I upgrade to Ubuntu 22.04 recently, and while upgrading and updating I also got a new bios version (1.69) for my Lenovo Thinkpad P50 laptop. Since then gnome-shell has been very unstable, crashing regularly on minor changes, like plugging in a monitor or going to suspend mode. Update: I just found out that the bug is not reproducable when logged in with Xorg instead of Wayland (https://askubuntu.com/questions/1428898/lenovo-p50-crashes-gnome- shell-regularly-after-upgrade-to-ubuntu-22-04-1-using) So we got a workaround and a culprit: Wayland ... in conjunction with something quite typical for my hardware maybe(?), Lenovo Thinkpad P50 (20ENCTO1WW) with Quadro M2000M discrete graphics ... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 12 09:49:57 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-09 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-09 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989325/+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 1917941] Re: System-config-printer keeps asking for network printer credentials
Storing the password from printer system dialog was running well for me with ubuntu 20.04 lts. Now, with ubuntu 22.04 lts the dialog is looking the same: with the 'remember password' checkbox. But, the password will be not stored any more. The dialog appears every time you print, regardless of whether you save the password. I have tested the behavior with a newly installed ubuntu 20.04 and 22.04. I printed from firefox with the printer system dialog. Any ideas how to make this work again? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1917941 Title: System-config-printer keeps asking for network printer credentials Status in system-config-printer package in Ubuntu: Confirmed Bug description: Hello. I think I found a small bug in the printing process of Xubuntu 20.04.02 LTS. I have a networked laser printer (Xerox Phaser 3250) that requires username/password credentials to print. The device is present in the CUPS page (see the Printers page in http://localhost:631) and uses the IPP protocol set to "ipp://192.168.1.10:631/ipp" URI. It is also visible in the system- config-printer window (XFCE Start button => Settings => Printers) and is set as default printer. The printer username/password are different than my PC username/password. Anyway, I noticed that the OS will sometimes pester me to enter the same credentials each time I try to print something. I recall the printing authorization window does have a "Remember password" checkbox that seemingly does nothing. Now why I am mentioning that this happens only sometimes? It's because I noticed that different programs will use different authorization windows to get printer credentials. For example, Mousepad will try to get credentials by using a CUPS popup dialog (I think). LibreOffice seems to popup its own small password entry window. This bug only applies to the cases where the printing is done via system-config-printer that uses its own authorization dialog. The printing works fine after credentials are entered though. So, after a short debug session I managed to narrow down the problem to this file: /usr/share/system-config-printer/jobviewer.py. I ran the applet.py and scp-dbus-service.py with the --debug option from command line to get some extra debug messages. Printing from Mousepad did not trigger any debug messages, but it did bring up the printing authorization dialog regardless. Like I've previously stated, Mousepad seems to use a different auth dialog, and I've verified (via seahorse) that this dialog works properly because it correctly stores the credentials into the keyring, and, if the Remember password checkbox is ticked, remembers them next time I try to print something. The problem only applies to the auth dialog triggered from jobviewer.py of system-config-printer. I managed to trigger the jobviewer auth dialog by trying to print something in LibreOffice Writer and then hitting Cancel in the small window that pops up. This will then trigger the *proper* jobviewer.py auth window to show up. It also triggers upon boot when there is something queued to be printed. It can also be reliably triggered queueing a print job, killing scp-dbus-service.py and applet.py and re-running them in this order: 1) /usr/share/system-config-printer/scp-dbus-service.py --debug 2) /usr/share/system-config-printer/applet.py --debug Though this jobviewer.py auth dialog will successfully save the printer credentials to the keyring, if the checkbox is ticked (verified with Seahorse), it will fail to read them next time, assume the credentials are missing, and ask the user to enter them. The error appears to happen in jobviewer.py: Line 1056: search_obj = ItemSearch(service, attrs) This line causes the following error to appear in the terminal: GLib-GIO-CRITICAL **: 19:28:31.663: g_dbus_connection_call_internal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed The call fails to fetch any credentials and instead returns an empty result. I've written a short python script (see test.py) that reproduces the issue and triggers the same error. Related libsecret documentation: https://developer.gnome.org/libsecret/0.20/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: system-config-printer 1.5.12-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: CurrentDesktop: XFCE Date: Fri Mar 5 19:34:54 2021 InstallationDate: Installed on 2020-01-20 (409 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for Phaser-3250: ipp://192.168.1.10:631/ipp
[Desktop-packages] [Bug 1897562] Re: gedit snap fails to save or open files in miscellaneous directories including dot-folders, ~/bin, and system folders.
** Description changed: The snap version of gedit prevents viewing and editing files outside a strictly limited set of folders. For example, it cannot change files in - standard folders ~/bin or ~/.local or ~/.config, or standard files such - as ~/.bashrc or ~/.profile. Even "sudo -H gedit /etc/fstab" doesn't + standard folders ~/bin, ~/.local, ~/.config, ~/.ssh, or standard files + such as ~/.bashrc or ~/.profile. Even "sudo -H gedit /etc/fstab" doesn't work. Using sudoedit doesn't work, as access to /var/tmp is rejected. EDIT: ~/bin is now available to gedit. As there is a bug in the non-snap versions [1], the snap version is important, but sadly it is unusable for a certain number of cases. I understand that the only solution is to make gedit available in classic confinement. Please would you do this. Thank you [1] https://gitlab.gnome.org/GNOME/gedit/-/issues/361 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1897562 Title: gedit snap fails to save or open files in miscellaneous directories including dot-folders, ~/bin, and system folders. Status in gedit package in Ubuntu: Triaged Bug description: The snap version of gedit prevents viewing and editing files outside a strictly limited set of folders. For example, it cannot change files in standard folders ~/bin, ~/.local, ~/.config, ~/.ssh, or standard files such as ~/.bashrc or ~/.profile. Even "sudo -H gedit /etc/fstab" doesn't work. Using sudoedit doesn't work, as access to /var/tmp is rejected. EDIT: ~/bin is now available to gedit. As there is a bug in the non-snap versions [1], the snap version is important, but sadly it is unusable for a certain number of cases. I understand that the only solution is to make gedit available in classic confinement. Please would you do this. Thank you [1] https://gitlab.gnome.org/GNOME/gedit/-/issues/361 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1897562/+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 1917941] Re: System-config-printer keeps asking for network printer credentials
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: system-config-printer (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1917941 Title: System-config-printer keeps asking for network printer credentials Status in system-config-printer package in Ubuntu: Confirmed Bug description: Hello. I think I found a small bug in the printing process of Xubuntu 20.04.02 LTS. I have a networked laser printer (Xerox Phaser 3250) that requires username/password credentials to print. The device is present in the CUPS page (see the Printers page in http://localhost:631) and uses the IPP protocol set to "ipp://192.168.1.10:631/ipp" URI. It is also visible in the system- config-printer window (XFCE Start button => Settings => Printers) and is set as default printer. The printer username/password are different than my PC username/password. Anyway, I noticed that the OS will sometimes pester me to enter the same credentials each time I try to print something. I recall the printing authorization window does have a "Remember password" checkbox that seemingly does nothing. Now why I am mentioning that this happens only sometimes? It's because I noticed that different programs will use different authorization windows to get printer credentials. For example, Mousepad will try to get credentials by using a CUPS popup dialog (I think). LibreOffice seems to popup its own small password entry window. This bug only applies to the cases where the printing is done via system-config-printer that uses its own authorization dialog. The printing works fine after credentials are entered though. So, after a short debug session I managed to narrow down the problem to this file: /usr/share/system-config-printer/jobviewer.py. I ran the applet.py and scp-dbus-service.py with the --debug option from command line to get some extra debug messages. Printing from Mousepad did not trigger any debug messages, but it did bring up the printing authorization dialog regardless. Like I've previously stated, Mousepad seems to use a different auth dialog, and I've verified (via seahorse) that this dialog works properly because it correctly stores the credentials into the keyring, and, if the Remember password checkbox is ticked, remembers them next time I try to print something. The problem only applies to the auth dialog triggered from jobviewer.py of system-config-printer. I managed to trigger the jobviewer auth dialog by trying to print something in LibreOffice Writer and then hitting Cancel in the small window that pops up. This will then trigger the *proper* jobviewer.py auth window to show up. It also triggers upon boot when there is something queued to be printed. It can also be reliably triggered queueing a print job, killing scp-dbus-service.py and applet.py and re-running them in this order: 1) /usr/share/system-config-printer/scp-dbus-service.py --debug 2) /usr/share/system-config-printer/applet.py --debug Though this jobviewer.py auth dialog will successfully save the printer credentials to the keyring, if the checkbox is ticked (verified with Seahorse), it will fail to read them next time, assume the credentials are missing, and ask the user to enter them. The error appears to happen in jobviewer.py: Line 1056: search_obj = ItemSearch(service, attrs) This line causes the following error to appear in the terminal: GLib-GIO-CRITICAL **: 19:28:31.663: g_dbus_connection_call_internal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed The call fails to fetch any credentials and instead returns an empty result. I've written a short python script (see test.py) that reproduces the issue and triggers the same error. Related libsecret documentation: https://developer.gnome.org/libsecret/0.20/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: system-config-printer 1.5.12-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: CurrentDesktop: XFCE Date: Fri Mar 5 19:34:54 2021 InstallationDate: Installed on 2020-01-20 (409 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for Phaser-3250: ipp://192.168.1.10:631/ipp Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500] Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M
[Desktop-packages] [Bug 1989325] Re: gnome-shell crashes on Lenovo Thinkpad P50 after upgrade to 22.04.1
Still haven't got time to reproduce, but I do think as long as this hardware combination doesn't work out of the box with wayland it should be disabled automatically for this hardware after installation or upgrade. This script is already disabling Wayland for lots of hardware configurations: /usr/lib/udev/rules.d/61-gdm.rules First step would be to find the most relevant values for my hardware that is proven not to work. More will follow. Would be so nice if I could make sure more Ubuntu users have a smooth experience with an out- of-the-box installation -- 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/1989325 Title: gnome-shell crashes on Lenovo Thinkpad P50 after upgrade to 22.04.1 Status in gnome-shell package in Ubuntu: Incomplete Bug description: I upgrade to Ubuntu 22.04 recently, and while upgrading and updating I also got a new bios version (1.69) for my Lenovo Thinkpad P50 laptop. Since then gnome-shell has been very unstable, crashing regularly on minor changes, like plugging in a monitor or going to suspend mode. Update: I just found out that the bug is not reproducable when logged in with Xorg instead of Wayland (https://askubuntu.com/questions/1428898/lenovo-p50-crashes-gnome- shell-regularly-after-upgrade-to-ubuntu-22-04-1-using) So we got a workaround and a culprit: Wayland ... in conjunction with something quite typical for my hardware maybe(?), Lenovo Thinkpad P50 (20ENCTO1WW) with Quadro M2000M discrete graphics ... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 12 09:49:57 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-09 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-09 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989325/+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 1989676] [NEW] Save As dialog cannot receive focus
Public bug reported: How to reproduce: 1. Open firefox 2. Ctrl+s Expected behavior: The "Save As" dialog opens. I can edit the file name, click on the left-side menu to change directory, click on the save button, close the dialog. Bug: The "Save As" dialog box is open. The "on mouse over" events work (elements are highlighted when the mouse is over) but clicking on any element has no effect. I cannot edit the filename, save the document, close the dialog box, ... I can click on the "+" button of the main window and open a new tab, but the dialog box stays on top. When I have a tab open that plays a video or some music, the playing doesn't stop. Firefox doesn't seem to freeze, it just keeps this dialog box open on top. I have to pkill firefox. Additional information: `wmctrl -l` lists multiple "Save as" windows. My computer: Dell XPS 15 My system: $ lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 $ firefox --version Mozilla Firefox 104.0.2 $ apt-cache policy firefox firefox: Installed: (none) Candidate: 1:1snap1-0ubuntu2 Version table: 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages $ snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stablecanonical✓ base chromium 105.0.5195.52 2076 latest/stablecanonical✓ - code e7f30e38 107latest/stablevscode✓ classic core 16-2.57.1 13741 latest/stablecanonical✓ core core18 20220831 2566 latest/stablecanonical✓ base core20 20220826 1623 latest/stablecanonical✓ base firefox104.0.2-1 1810 latest/stable/… mozilla✓ - gnome-3-38-20040+git.891e5bc 115latest/stable/… canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - helm 3.7.0 353latest/stable snapcrafters classic snap-store 41.3-63-gbd822db 592latest/stable/… canonical✓ - snapd 2.57.116778 latest/stablecanonical✓ snapd snapd-desktop-integration 0.1 14 latest/stable/… canonical✓ - $ snap info firefox name: firefox summary: Mozilla Firefox web browser publisher: Mozilla✓ store-url: https://snapcraft.io/firefox contact: https://support.mozilla.org/kb/file-bug-report-or-feature-request-mozilla license: unset description: | Firefox is a powerful, extensible web browser with support for modern web application technologies. commands: - firefox - firefox.geckodriver snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk tracking: latest/stable/ubuntu-22.04 refresh-date: 8 days ago, at 00:27 CEST channels: latest/stable:104.0.2-12022-09-06 (1810) 185MB - latest/candidate: 105.0-1 2022-09-13 (1842) 187MB - latest/beta: 105.0b9-12022-09-12 (1836) 187MB - latest/edge: 106.0a1 2022-09-14 (1845) 192MB - esr/stable: 91.13.0esr-1 2022-09-02 (1791) 161MB - esr/candidate:102.3.0esr-1 2022-09-12 (1839) 183MB - esr/beta: ↑ esr/edge: 102.2.0esr-2 2022-09-02 (1793) 182MB - installed: 104.0.2-1 (1810) 185MB - ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 15 09:16:40 2022 InstallationDate: Installed on 2022-06-30 (76 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Screen recording of the bug" https://bugs.launchpad.net/bugs/1989676/+attachment/5615981/+files/2022-09-15%2009-01-21.mkv -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1989676 Title: Save As dialog cannot receive focus Status in evince package in Ubuntu: New Bug description: How to reproduce: 1. Open firefox 2. Ctrl+s Expected behavior: The "Save As" dialog opens. I can edit the file name, click on the left-side menu to change directory, click on the save button, close the dialog. Bug: The "Save As" dialog box is open. The "on mouse over" events work (elements are highlighted when the mouse is over) but clicking on any element has no
[Desktop-packages] [Bug 1843392] Re: [snap] smart card reader no longer works
** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** No longer affects: firefox (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1843392 Title: [snap] smart card reader no longer works Status in chromium-browser package in Ubuntu: Confirmed Bug description: chromium uses the Netscape Cryptographic Module to access smartcards for authentication purposes. This stopped working when switching to the snap version. Chromium would normally access the setup in ~/.pki/nssdb/pkcs11.txt That file would refer to a library used to access the smart card. I.e /usr/lib/x86_64-linux-gnu/pkcs11/opensc- pkcs11.so The problem can be bypassed by manually launching chromium via: /snap/chromium/current/usr/lib/chromium-browser/chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1843392/+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 1989626] Re: UIFe: fonts-noto-color-emoji & other updates for Unicode 15
This is fine, but I'd like to have an exact list of packages that need changes (or rebuilds), either as an 'affects as' or a list in the description. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1989626 Title: UIFe: fonts-noto-color-emoji & other updates for Unicode 15 Status in fonts-noto-color-emoji package in Ubuntu: New Bug description: Justification - Unicode 15 was release September 13. This is an annual release. It's expected that the latest Ubuntu will support the latest stable Unicode release. This is required for compatibility with Internet communications with other platforms that will be quickly adopting the new emoji characters. The release happened too late for related upstream releases to happen by Ubuntu's User Interface Freeze on September 15 and be packaged. Therefore, I request a UIFe for Ubuntu 22.10 for Unicode 15 packages. More details Google will be releasing a new version of fonts-noto-color-emoji "later this week" but it looks like it won't be released in time for Ubuntu's User Interface Freeze. We also need to update glib and pango for the new release so that new composite emoji like "pink heart" display correctly. https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2877 There isn't an upstream pango merge request or issue but I think it will be needed. We also need new versions of unicode-data, node-unicode, and gucharmap. There are probably some other minor universe packages that we should sync from Debian if we see they are related to Unicode 15. I don't have packaging ready for these changes yet but I'm requesting the UIFe early. 22.04 LTS - We have done SRUs of new fonts-noto-color-emoji releases to older LTSes before. We may do it again but that will be one or more separate bugs. References -- https://blog.emojipedia.org/whats-new-in-unicode-15-0/ https://developers.googleblog.com/2022/09/updates-to-emoji-new- characters-animation-colors-and-more.html https://unicode.org/versions/Unicode15.0.0/ Email to Docs List: https://lists.ubuntu.com/archives/ubuntu-doc/2022-September/020889.html I don't believe translators need to be notified about this UIFe but let me know if I should email them anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1989626/+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 1989508] Re: hp-plugin unable to load plugin.conf
** Also affects: hplip (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1989508 Title: hp-plugin unable to load plugin.conf Status in HPLIP: New Status in hplip package in Ubuntu: New Bug description: Linux hp-plugin fails on Fedora 35 with the error: error: Plugin download failed with error code = 8 error: file does not match its checksum. File may have been corrupted or altered When running "hp-plugin -l debug" the reason turns out to be that http://hplip.sourceforge.net/plugin.conf does not exist: hp-plugin[540794]: debug: wget returned: 0 hp-plugin[540794]: debug: --2022-09-13 23:23:02-- http://hplip.sf.net/plugin.conf Resolving hplip.sf.net (hplip.sf.net)... 204.68.111.100 Connecting to hplip.sf.net (hplip.sf.net)|204.68.111.100|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: http://hplip.sourceforge.net/plugin.conf [following] --2022-09-13 23:23:02-- http://hplip.sourceforge.net/plugin.conf Resolving hplip.sourceforge.net (hplip.sourceforge.net)... 204.68.111.100 Reusing existing connection to hplip.sf.net:80. HTTP request sent, awaiting response... 404 Not Found 2022-09-13 23:23:02 ERROR 404: Not Found. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1989508/+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
