[Desktop-packages] [Bug 2018433] Re: display resolution stuck on 93Hz
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2018433 Title: display resolution stuck on 93Hz Status in gnome-shell package in Ubuntu: Expired Bug description: The display settings are stuck at 2560x1440 x 93Hz xrandr says: xrandr: Failed to get size of gamma for output default Screen 0: minimum 2560 x 1440, current 2560 x 1440, maximum 2560 x 1440 default connected primary 2560x1440+0+0 0mm x 0mm 2560x1440 93.00* ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 3 16:09:38 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-09 (298 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.5-0ubuntu1 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/2018433/+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 819796] Re: [Upstream] overline automatic color incorrect in pdf
** Changed in: df-libreoffice Status: Confirmed => Fix Released ** Changed in: df-libreoffice Importance: Low => Medium -- 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/819796 Title: [Upstream] overline automatic color incorrect in pdf Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages apt-cache policy acroread acroread: Installed: 9.4.2-0natty1 Candidate: 9.4.2-0natty1 Version table: *** 9.4.2-0natty1 0 500 http://archive.canonical.com/ubuntu/ natty/partner i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/819796/+attachment/2251624/+files/overline%20color%20test.odt -O test.odt && lowriter -nologo test.odt File -> Export as PDF -> Export button and open in Adobe Reader is the overline above B remains red. 4) What happens is it is black. WORKAROUND: Highlight B -> Secondary click -> click character... -> Font Effects tab -> change Overline color from Automatic to Light red -> OK button ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.2-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic-pae 2.6.39-rc5 Uname: Linux 2.6.39-0-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Tue Aug 2 08:34:40 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to natty on 2011-05-30 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/819796/+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 819796]
Khaled Hosny committed a patch related to this issue. It has been pushed to "libreoffice-7-6": https://git.libreoffice.org/core/commit/02243bc209f70a52214e15268ff02c6209c71146 tdf#48707: Explicitly set overline color in PDF export It will be available in 7.6.0.0.beta2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- 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/819796 Title: [Upstream] overline automatic color incorrect in pdf Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages apt-cache policy acroread acroread: Installed: 9.4.2-0natty1 Candidate: 9.4.2-0natty1 Version table: *** 9.4.2-0natty1 0 500 http://archive.canonical.com/ubuntu/ natty/partner i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/819796/+attachment/2251624/+files/overline%20color%20test.odt -O test.odt && lowriter -nologo test.odt File -> Export as PDF -> Export button and open in Adobe Reader is the overline above B remains red. 4) What happens is it is black. WORKAROUND: Highlight B -> Secondary click -> click character... -> Font Effects tab -> change Overline color from Automatic to Light red -> OK button ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.2-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic-pae 2.6.39-rc5 Uname: Linux 2.6.39-0-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Tue Aug 2 08:34:40 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to natty on 2011-05-30 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/819796/+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 819796]
*** Bug 154395 has been marked as a duplicate of this bug. *** -- 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/819796 Title: [Upstream] overline automatic color incorrect in pdf Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages apt-cache policy acroread acroread: Installed: 9.4.2-0natty1 Candidate: 9.4.2-0natty1 Version table: *** 9.4.2-0natty1 0 500 http://archive.canonical.com/ubuntu/ natty/partner i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/819796/+attachment/2251624/+files/overline%20color%20test.odt -O test.odt && lowriter -nologo test.odt File -> Export as PDF -> Export button and open in Adobe Reader is the overline above B remains red. 4) What happens is it is black. WORKAROUND: Highlight B -> Secondary click -> click character... -> Font Effects tab -> change Overline color from Automatic to Light red -> OK button ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.2-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic-pae 2.6.39-rc5 Uname: Linux 2.6.39-0-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Tue Aug 2 08:34:40 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to natty on 2011-05-30 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/819796/+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 819796]
Khaled Hosny committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/13c4456ca382a92b93395db367ef8edb27a349fa tdf#48707: Explicitly set overline color in PDF export It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- 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/819796 Title: [Upstream] overline automatic color incorrect in pdf Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages apt-cache policy acroread acroread: Installed: 9.4.2-0natty1 Candidate: 9.4.2-0natty1 Version table: *** 9.4.2-0natty1 0 500 http://archive.canonical.com/ubuntu/ natty/partner i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/819796/+attachment/2251624/+files/overline%20color%20test.odt -O test.odt && lowriter -nologo test.odt File -> Export as PDF -> Export button and open in Adobe Reader is the overline above B remains red. 4) What happens is it is black. WORKAROUND: Highlight B -> Secondary click -> click character... -> Font Effects tab -> change Overline color from Automatic to Light red -> OK button ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.2-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic-pae 2.6.39-rc5 Uname: Linux 2.6.39-0-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Tue Aug 2 08:34:40 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to natty on 2011-05-30 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/819796/+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 1944113]
Very impressive article. I really like the topic you talk about and the information you share is very interesting. https://slitherio.online -- 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/1944113 Title: Many UI elements (list box, drop down) don't work at all in kf5 environment Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: Many UI elements (list box, drop down) don't work at all in kf5 environment. This makes LO unusable. For example, try to insert a table from standard toolbar in LO Writer – nothing inserted. Same happens with other drop down elements (styles, font family, font size, font color, font highlight, etc). Bug reports at LO's bug tracker: https://bugs.documentfoundation.org/show_bug.cgi?id=144037 https://bugs.documentfoundation.org/show_bug.cgi?id=144562 https://gerrit.libreoffice.org/c/core/+/122116 Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.11.0-34-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz Memory: 7,7 GiB Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3 Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+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 2025687] [NEW] URL Links in Document Viewer Does not Open in Firefox
Public bug reported: 1. Description: Ubuntu 22.04.2 LTS Release:22.04 2. evince: Installed: 42.3-0ubuntu3 Candidate: 42.3-0ubuntu3 Version table: *** 42.3-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.1-3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3. I expect the URL link in the PDF to open in my Firefox web browser when I click on it. I have to manually copy the link from the PDF document and paste it to the Firefox web browser. 4. Nothing ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 3 21:27:55 2023 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2022-11-03 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (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 evince in Ubuntu. https://bugs.launchpad.net/bugs/2025687 Title: URL Links in Document Viewer Does not Open in Firefox Status in evince package in Ubuntu: New Bug description: 1. Description: Ubuntu 22.04.2 LTS Release: 22.04 2. evince: Installed: 42.3-0ubuntu3 Candidate: 42.3-0ubuntu3 Version table: *** 42.3-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.1-3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3. I expect the URL link in the PDF to open in my Firefox web browser when I click on it. I have to manually copy the link from the PDF document and paste it to the Firefox web browser. 4. Nothing ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 3 21:27:55 2023 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2022-11-03 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2025687/+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 1959525] Re: Occasional no display output on 6900XT or if been idle for too long
My problems only occur when running a KDE Wayland session, not with KDE X11 sessions. -- 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/1959525 Title: Occasional no display output on 6900XT or if been idle for too long Status in libdrm package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: ## No output at boot The dmesg I attached is from when nothing showed at boot. Journal output: $ journalctl -r --grep amdgpu -- Journal begins at Thu 2022-01-27 05:36:17 EST, ends at Sun 2022-01-30 15:58:40 EST. -- Jan 30 15:50:24 Y4M1-II kernel: amdgpu: probe of :0c:00.0 failed with error -110 Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: ttm finalized Jan 30 15:50:24 Y4M1-II kernel: amdgpu_init+0x77/0x1000 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_pci_probe+0x12a/0x1b0 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_driver_load_kms.cold+0x46/0x83 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_driver_unload_kms+0x43/0x70 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_device_fini+0xc5/0x1e5 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_device_ip_fini.isra.0+0x206/0x2cd [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: gmc_v10_0_sw_fini+0x33/0x40 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_bo_fini+0x12/0x50 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_ttm_fini+0xab/0x100 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_vram_mgr_fini+0xe8/0x160 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: Modules linked in: hid_generic usbhid hid amdgpu(+) iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul sysfillrect ghash_clmulni_intel sysimgblt fb_sys_fops cec aesni_intel rc_core crypto_simd cryptd drm nvme ahci xhci_pci i2c_piix4 nvme_core igc libahci xhci_pci_renesas wmi Jan 30 15:50:24 Y4M1-II kernel: [drm:psp_v11_0_ring_destroy [amdgpu]] *ERROR* Fail to stop psp ring Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: amdgpu: finishing device. Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Fatal error during GPU init Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: amdgpu_device_ip_init failed Jan 30 15:50:24 Y4M1-II kernel: [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* hw_init of IP block failed -110 Jan 30 15:50:24 Y4M1-II kernel: [drm:amdgpu_gfx_enable_kcq.cold [amdgpu]] *ERROR* KCQ enable failed Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SMU is initialized successfully! Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: use vbios provided pptable Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SMU driver if version not matched Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: smu driver if version = 0x003d, smu fw if version = 0x0040, smu fw version = 0x003a4700 (58.71.0) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Will use PSP to load VCN firmware Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: 16368M of GTT memory ready. Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: 16368M of VRAM memory ready Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: AGP: 267894784M 0x0084 - 0x Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: GART: 512M 0x - 0x1FFF Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: VRAM: 16368M 0x0080 - 0x0083FEFF (16368M used) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SRAM ECC is not presented. Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: MEM ECC is not presented. Jan 30 15:50:24 Y4M1-II kernel: amdgpu: ATOM BIOS: 113-EXT800216-L05 Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Fetched VBIOS from VFCT Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: enabling device (0006 -> 0007) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: vgaarb: deactivate vga console Jan 30 15:50:24 Y4M1-II kernel: fb0: switching to amdgpudrmfb from EFI VGA Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Topology: Add CPU node Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Virtual CRAT table created for CPU Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Ignoring ACPI CRAT on non-APU system Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu kernel modesetting enabled. Jan 30 15:50:24 Y4M1-II kernel: Kernel
[Desktop-packages] [Bug 2025651] Re: default Japanese font in snap apps is ugly
That FC_DEBUG variable was useful. :) I dropped the line: /etc/fonts/conf.d from: ~/snap/firefox/current/.config/fontconfig/fonts.conf and that fixed it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: New Status in language-selector package in Ubuntu: New Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
I did an check and can confirm that the chromium-browser as installed by the usual 22.04 package is *NOT* affected. But Google chrome well as google-chrome-beta installed by the PPA deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main do show the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+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 2025674] Re: ruby-cairo test failure with cairo 1.17.8
** Changed in: cairo (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/2025674 Title: ruby-cairo test failure with cairo 1.17.8 Status in cairo package in Ubuntu: Fix Released Status in ruby-cairo package in Ubuntu: Fix Committed Status in ruby-cairo package in Debian: Unknown Bug description: We need to update ruby-cairo to version 1.17.7 or higher to fix its test suite to pass with cairo 1.17.8 in mantic-proposed. https://github.com/rcairo/rcairo/blob/master/NEWS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/2025674/+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 2025651] Re: default Japanese font in snap apps is ugly
On 2023-07-03 23:05, Sebastien Bacher wrote: > Ignore my previous comment, I keep forgetting how fonts in snaps > work. The snap doesn't have access to the /etc configuration and > /snap/gnome-42-2204/current/etc/fonts/conf.d is used instead Yes, unfortunately... > did the configuration change since jammy? I upgraded fontconfig in lunar. But I'm not aware of any changes which might explain this issue. Well, I tested a theory in comment #11, but that change seems not related either. > Is the problem describing here existing on 22.04 for deb software? No. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: New Status in language-selector package in Ubuntu: New Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 2025651] Re: default Japanese font in snap apps is ugly
Ok, doing $ FC_DEBUG=1024 LC_CTYPE=ja_JP.UTF-8 fc-match -s sans-serif | less gives a clue, it seems to read first the /snap/gnome-42-2204/current/etc/fonts/conf.d configurations but then the /etc/fonts/conf.d ones. Confirmed by moving /etc/fonts/conf.avail/65-droid-sans-fallback.conf away on the system which makes the snap use NotoSansCJK-Regular.ttc it manages to read /etc/fonts/65-droid-sans-fallback.conf (which points to /etc/fonts/conf.avail/) but not /etc/fonts/conf.d/70-fonts-noto- cjk.conf (which points to /usr/share/fontconfig/conf.avail) so the first one end up winning. The fix is probably to make fontconfig use /snap/gnome-42-2204/current/etc/fonts/ only in the snap In the firefox case the desktop wrapper sets FONTCONFIG_FILE=/var/snap/firefox/common/fontconfig/fonts.conf which has /etc/fonts/fonts.conf but without that line it still seems to read configs from /etc... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: New Status in language-selector package in Ubuntu: New Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 2025651] Re: default Japanese font in snap apps is ugly
Ignore my previous comment, I keep forgetting how fonts in snaps work. The snap doesn't have access to the /etc configuration and /snap/gnome-42-2204/current/etc/fonts/conf.d is used instead You are right that the snap is built from jammy, did the configuration change since jammy? Is the problem describing here existing on 22.04 for deb software? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: New Status in language-selector package in Ubuntu: New Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 2025651] Re: default Japanese font in snap apps is ugly
Ignore my previous comment, I keep forgetting how fonts in snaps work. The snap doesn't have access to the /etc configuration and /snap/gnome-42-2204/current/etc/fonts/conf.d is used instead You are right that the snap is built from jammy, did the configuration change since jammy? Is the problem describing here existing on 22.04 for deb software? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: New Status in language-selector package in Ubuntu: New Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 2025651] Re: default Japanese font in snap apps is ugly
It struck me that fontconfig prefers Noto Sans by default in lunar and mantic, but not in the snaps if I understand it correctly since the fonts related packages are grabbed from jammy. As a test I made this change in mantic: --- /usr/share/fontconfig/conf.avail/60-latin.conf.orig +++ /usr/share/fontconfig/conf.avail/60-latin.conf @@ -18,7 +18,7 @@ sans-serif - Noto Sans + DejaVu Sans Verdana Arial But I still can't reproduce the issue on the host system: $ LC_CTYPE=ja_JP.UTF-8 fc-match -s sans-serif | grep -E 'Noto|Droid' | head -3 NotoSansCJK-Regular.ttc: "Noto Sans CJK JP" "Regular" NotoSansSinhala-Regular.ttf: "Noto Sans Sinhala" "Regular" DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: New Status in language-selector package in Ubuntu: New Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 2025651] Re: default Japanese font in snap apps is ugly
This works for me: $ snap run --shell firefox To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. /home/gunnar$ cat /snap/firefox/current/gnome-platform/etc/fonts/conf.d/70-fonts-noto-cjk.conf ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: New Status in language-selector package in Ubuntu: New Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 2025651] Re: default Japanese font in snap apps is ugly
The issue is probably that in the snap environment $ cat /etc/fonts/conf.d/70-fonts-noto-cjk.conf cat: /etc/fonts/conf.d/70-fonts-noto-cjk.conf: No such file or directory the target /usr/share/fontconfig/conf.avail/70-fonts-noto-cjk.conf seems to not be available -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: New Status in language-selector package in Ubuntu: New Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 2025651] Re: default Japanese font in snap apps is ugly
64-language-selector-prefer.conf prefers Noto Sans CJK JP for sans- serif. 65-droid-sans-fallback.conf prefers Droid Sans Fallback for sans-serif. 64 is lower than 65, so Noto is preferred over Droid. And on top of that we have 70-fonts-noto-cjk.conf which prepends Noto Sans CJK JP in case of a Japanese locale. Do the snaps not parse the config files in the right order? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: New Status in language-selector package in Ubuntu: New Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 2025674] Re: ruby-cairo test failure with cairo 1.17.8
** Changed in: ruby-cairo (Ubuntu) Status: Triaged => Fix Committed ** Description changed: - We need to update ruby-cairo to version 1.17.9 or higher to fix its test + We need to update ruby-cairo to version 1.17.7 or higher to fix its test suite to pass with cairo 1.17.8 in mantic-proposed. https://github.com/rcairo/rcairo/blob/master/NEWS -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/2025674 Title: ruby-cairo test failure with cairo 1.17.8 Status in cairo package in Ubuntu: Triaged Status in ruby-cairo package in Ubuntu: Fix Committed Status in ruby-cairo package in Debian: Unknown Bug description: We need to update ruby-cairo to version 1.17.7 or higher to fix its test suite to pass with cairo 1.17.8 in mantic-proposed. https://github.com/rcairo/rcairo/blob/master/NEWS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/2025674/+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 2025538] Re: Unrequested kernel update
Today apt want's to update my nvidia driver from 510.108.03-0ubuntu0.22.04.1 to 525.125.06-0ubuntu0.22.04.1 Based on the bad experience of the unwanted kernel update I'm not sure whether I should take the risk. Hopefully one of the maintainers reacts to this bug soon and gives more advice about how to solve the issue and clean up the system -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-nvidia-5.19/+bug/2025538/+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 2025651] Re: default Japanese font in snap apps is ugly
I don't know. The behavior for deb software is expected, the behavior for lunar and mantic snaps is unexpected. But we do know that uninstalling fonts-droid-fallback from the host system makes a difference wrt the snap behavior as regards Japanese font rendering. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: New Status in language-selector package in Ubuntu: New Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 2025651] Re: default Japanese font in snap apps is ugly
But fonts-droid-fallback is installed by default on mantic so why isn't it creating the same problems for deb software? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: New Status in language-selector package in Ubuntu: New Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 2025651] Re: default Japanese font in snap apps is ugly
Maybe it would make a difference to simply drop fonts-droid-fallback from this list: https://github.com/ubuntu/gnome- sdk/blob/gnome-42-2204/snapcraft.yaml#L245 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: New Status in language-selector package in Ubuntu: New Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 1997560] Re: [MIR] libcamera
Override component to main libcamera 0.0.5-1ubuntu1 in mantic: universe/misc -> main libcamera-dev 0.0.5-1ubuntu1 in mantic amd64: universe/libdevel/optional/100% -> main libcamera-dev 0.0.5-1ubuntu1 in mantic arm64: universe/libdevel/optional/100% -> main libcamera-dev 0.0.5-1ubuntu1 in mantic armhf: universe/libdevel/optional/100% -> main libcamera-dev 0.0.5-1ubuntu1 in mantic i386: universe/libdevel/optional/100% -> main libcamera-dev 0.0.5-1ubuntu1 in mantic ppc64el: universe/libdevel/optional/100% -> main libcamera-dev 0.0.5-1ubuntu1 in mantic riscv64: universe/libdevel/optional/100% -> main libcamera-dev 0.0.5-1ubuntu1 in mantic s390x: universe/libdevel/optional/100% -> main libcamera-doc 0.0.5-1ubuntu1 in mantic amd64: universe/doc/optional/100% -> main libcamera-doc 0.0.5-1ubuntu1 in mantic arm64: universe/doc/optional/100% -> main libcamera-doc 0.0.5-1ubuntu1 in mantic armhf: universe/doc/optional/100% -> main libcamera-doc 0.0.5-1ubuntu1 in mantic i386: universe/doc/optional/100% -> main libcamera-doc 0.0.5-1ubuntu1 in mantic ppc64el: universe/doc/optional/100% -> main libcamera-doc 0.0.5-1ubuntu1 in mantic riscv64: universe/doc/optional/100% -> main libcamera-doc 0.0.5-1ubuntu1 in mantic s390x: universe/doc/optional/100% -> main libcamera0.0.5 0.0.5-1ubuntu1 in mantic amd64: universe/libs/optional/100% -> main libcamera0.0.5 0.0.5-1ubuntu1 in mantic arm64: universe/libs/optional/100% -> main libcamera0.0.5 0.0.5-1ubuntu1 in mantic armhf: universe/libs/optional/100% -> main libcamera0.0.5 0.0.5-1ubuntu1 in mantic i386: universe/libs/optional/100% -> main libcamera0.0.5 0.0.5-1ubuntu1 in mantic ppc64el: universe/libs/optional/100% -> main libcamera0.0.5 0.0.5-1ubuntu1 in mantic riscv64: universe/libs/optional/100% -> main libcamera0.0.5 0.0.5-1ubuntu1 in mantic s390x: universe/libs/optional/100% -> main Override [y|N]? y ** Changed in: libcamera (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcamera in Ubuntu. https://bugs.launchpad.net/bugs/1997560 Title: [MIR] libcamera Status in libcamera package in Ubuntu: Fix Released Bug description: [Availability] The package libcamera is already in Ubuntu universe. The package libcamera build for the architectures it is designed to work on. It currently builds and works for architectures: amd64 arm64 armhf ppc64el riscv64 s390x Link to package https://launchpad.net/ubuntu/+source/libcamera [Rationale] - The package libcamera is required in Ubuntu main as it aims at becoming the standard solution to handle modern cameras on linux (https://blogs.gnome.org/uraeus/2021/10/01/pipewire-and-fixing-the-linux-video-capture-stack/). It's also an optional depends of pipewire which we want to enable. - The package libcamera is required in Ubuntu main no later than feb 23 due to feature freeze [Security] - No CVEs/security issues in this software in the past - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024) - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu and has only minor bug reports - Ubuntu https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libcamera - The package does deal with a range of webcam devices and newer drivers are likely to be added in the futur. We will test on a selection of that hardware: https://wiki.ubuntu.com/DesktopTeam/TestPlans/Libcamera [Quality assurance - testing] - The package runs a test suite on build time, if it fails it makes the build fail, link to build log https://launchpad.net/ubuntu/+source/libcamera/0.0.1-4ubuntu1/+build/24869057 - The package runs an autopkgtest, and is currently passing on this list of architectures, link to test logs https://autopkgtest.ubuntu.com/packages/libc/libcamera [Quality assurance - packaging] - debian/watch is present and works - the debian/control Maintainer has been generated by update- maintainer - The lintian warnings listed are about missing manpages and length of some of the sourcecode lines (details in #3) which we believe are minor and shouldn't be a blocker - Please link to a recent build log of the package https://launchpadlibrarian.net/628408476/buildlog_ubuntu-kinetic- amd64.libcamera_0~git20211108+1b30992b623e-5_BUILDING.txt.gz - Lintian overrides > libcamera-dev: repeated-path-segment libcamera [usr/include/libcamera/libcamera/] the path is what is defined by upstream and not a bug > libcamera0: lacks-unversioned-link-to-shared-library example:
[Desktop-packages] [Bug 2025677] [NEW] Pulseaudio does not connect to snd_hda_intel
Public bug reported: Since approximately version 20.04 pulseaudio has failed to include the analog sound options in its configuration settings for the series 6 c200 chipset. Meaning that it is impossible to use either built in or external speakers without using either bluetooth (which has its own problems) or USB (which uses up USB sockets). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1565 F wireplumber /dev/snd/seq:mark 1564 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Jul 3 19:55:46 2023 InstallationDate: Installed on 2023-06-30 (3 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2023-06-30 (3 days ago) dmi.bios.date: 03/12/2015 dmi.bios.release: 15.96 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.60 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.78 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.60:bd03/12/2015:br15.96:efr151.78:svnHewlett-Packard:pn:pvrA0001C02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:sku: dmi.product.family: 103C_5336AN dmi.product.version: A0001C02 dmi.sys.vendor: Hewlett-Packard ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2025677 Title: Pulseaudio does not connect to snd_hda_intel Status in pulseaudio package in Ubuntu: New Bug description: Since approximately version 20.04 pulseaudio has failed to include the analog sound options in its configuration settings for the series 6 c200 chipset. Meaning that it is impossible to use either built in or external speakers without using either bluetooth (which has its own problems) or USB (which uses up USB sockets). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1565 F wireplumber /dev/snd/seq:mark 1564 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Jul 3 19:55:46 2023 InstallationDate: Installed on 2023-06-30 (3 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2023-06-30 (3 days ago) dmi.bios.date: 03/12/2015 dmi.bios.release: 15.96 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.60 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.78 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.60:bd03/12/2015:br15.96:efr151.78:svnHewlett-Packard:pn:pvrA0001C02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:sku: dmi.product.family: 103C_5336AN dmi.product.version: A0001C02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2025677/+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 2025674] [NEW] ruby-cairo test failure with cairo 1.17.8
Public bug reported: We need to update ruby-cairo to version 1.17.9 or higher to fix its test suite to pass with cairo 1.17.8 in mantic-proposed. https://github.com/rcairo/rcairo/blob/master/NEWS ** Affects: cairo (Ubuntu) Importance: High Status: Triaged ** Affects: ruby-cairo (Ubuntu) Importance: High Status: Triaged ** Affects: ruby-cairo (Debian) Importance: Unknown Status: Unknown ** Tags: mantic update-excuse ** Also affects: ruby-cairo (Ubuntu) Importance: Undecided Status: New ** Changed in: ruby-cairo (Ubuntu) Status: New => Triaged ** Changed in: ruby-cairo (Ubuntu) Importance: Undecided => High ** Bug watch added: Debian Bug tracker #1040230 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040230 ** Also affects: ruby-cairo (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040230 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/2025674 Title: ruby-cairo test failure with cairo 1.17.8 Status in cairo package in Ubuntu: Triaged Status in ruby-cairo package in Ubuntu: Triaged Status in ruby-cairo package in Debian: Unknown Bug description: We need to update ruby-cairo to version 1.17.9 or higher to fix its test suite to pass with cairo 1.17.8 in mantic-proposed. https://github.com/rcairo/rcairo/blob/master/NEWS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/2025674/+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 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+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 2025526] Re: Printer is not available in chromium snap
Heiko, even that you have found a workaround, could you continue help us what was going on? Could you follow the instructions of comment #4? -- 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/2025526 Title: Printer is not available in chromium snap Status in chromium-browser package in Ubuntu: Incomplete Status in cups package in Ubuntu: Incomplete Bug description: My printer is not available in chromium. I had the same problem in firefox but fixed it with the following command: sudo snap connect firefox:cups-control However this did not work with the chromium snap. I got the following error: snap "chromium" has no plug named "cups-control" My printer is a network printer and is automatically detected by my Kubuntu install. It works out of the box with all native apps and flatpaks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025526/+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 2025538] Re: Unrequested kernel update
** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-nvidia-5.19/+bug/2025538/+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 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: New Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+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 2017076] Re: default Chinese font in snap apps is ugly
On 2023-07-03 12:59, Gunnar Hjalmarsson wrote: > (But I notice another weird issue: In the FF Settings it shows Ubuntu > as the default serif font irrespective of locale. How come?) Pls disregard that. User error. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Fix Released Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+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 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths
Hi Matthew, thank you for the debdiffs! Things look good overall, I'd just like to add attribution for the upstream patches (for Didier Roche). This is something one can easily add when uploading, so don't worry about supplying a new debdiff just for this change. We've discussed this offline, but I'm going to mention it here as well, so we can track it later: There's an upload for adsys 0.12 sitting in the Jammy queue, and we'd have to either trample over that or wait for it to release in order to get the fix for this bug. There's some discussion going on over at the ubuntu-release mailing lists about granting adsys an SRU exception [0]. I'm going to reach out to the ones in charge of LP bug 2020682 to see if we can release this bug fix first, as the SRU exception discussion might take some time, still. [0] https://lists.ubuntu.com/archives/ubuntu- release/2023-June/005650.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020834 Title: Properly convert DNS names with '-' characters to valid dbus object paths Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: In Progress Status in adsys source package in Jammy: In Progress Status in adsys source package in Kinetic: In Progress Bug description: [Impact] It is common that domain names contain the '-' character, as in "test- example.com", and adsys versions 0.9.2 and below cannot parse these correctly, leading to the error: ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name when attempting to run adsys on a system attached to "test- example.com" Active Directory. Currently, 0.9.2 only changes '.' into '_2e', and this would change all special characters to use their hexadecimal representations, notably '-' becomes '_2d'. There is plans from Foundations + Desktop to SRU 0.12.0 back to at least Jammy, documented in bug 2020682 which depends on golang 1.20 to be included in the jammy archive, documented in bug 2020658. However, this fixup is required with high priority while the 0.12.0 release is being prepared, and the SRU will hopefully bridge a few weeks between SRU release to release of 0.12.0. [Testcase] Start a Windows Server VM, 2022 will be fine, and create an Active Directory with the domain "test-example.com". Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the domain. Try to enable adsys: $ sudo apt install adsys $ adsysctl update ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name There are test packages in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test If you install the test package and retry to join the domain, it will succeed. [Where problems could occur] We are changing how domain names are being parsed and converted to valid dbus object path names. Domain names can only contain [0-9], [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its hexadecimal representation of '_2d', there should be limited scope of regressions. However, if a regression were to occur, then users may not be able to use adsys to apply group policy restrictions, and could run into issues accessing files, shares and networks. As mentioned in the impact section, this will be a temporary fix to 0.9.2 while 0.12.0 is being prepared to be released into the archive, which contains the full fix and testsuite coverage. This SRU should hopefully be short lived. [Other Info] The upstream merge request is: https://github.com/ubuntu/adsys/pull/498 This was fixed in 0.10.0 by the commit: commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Author: Didier Roche Date: Tue Nov 15 11:10:51 2022 +0100 Subject: Fix special characters in domain conversion to dbus object path Link: https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Now, there were some additional commits that added testsuite coverage: commit cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 Author: Didier Roche Date: Tue Nov 15 11:13:03 2022 +0100 Subject: Refresh golden file now that we properly handle the path. Link: https://github.com/ubuntu/adsys/commit/cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 commit 4571e39cd724a973270a586d2b18f653f0007de9 Author: Didier Roche Date: Tue Nov 15 11:14:35 2022 +0100 Subject: Use a better case to assert on ServerURL() failure being ignored. Link:
[Desktop-packages] [Bug 2024197] Re: Update gnome-remote-desktop to 44.2
I completed the Basic RDP Test Case from the wiki (the only test case that applied). I installed gnome-remote-desktop 44.2-0ubuntu1 on my host Ubuntu 23.04 computer. I was able to successfully connect using a second Ubuntu 23.04 computer as guest using the Remmina apt package. ** Tags removed: verification-needed verification-needed-lunar ** Tags added: verification-done verification-done-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024197 Title: Update gnome-remote-desktop to 44.2 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Lunar: Fix Committed Bug description: Impact -- This is a new stable release in the GNOME 44 series It fixes some crashes reported to errors.ubuntu.com Changes since the current Ubuntu 23.04 release, 44.0: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/44.0...44.2 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024197/+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 2025662] [NEW] mutter pauses for multiple seconds at random times
Public bug reported:
Hi, I have this weird bug in mutter (44.2-0ubuntu1) which seems to
correlate with uptime - if I kill mutter the problem seems to go away
for a few days, although killing mutter is very inconvenient because all
applications are also killed even with session persistence.
Upon strace analysis it can be seen that when the pauses are happening
there is a specific trace involving GEM operations happening immediately
after a ~1 second epoll expires.
During this state the entire UI is paused - video does not update, mouse
cursor does not move, keypresses have no response. However, input
events are "queued" so that when the pause ends, the mouse instantly
warps across the screen, and if a key was down at the time the pause
began, the key is repeated hundreds of times since it seems that the
key-up event is only processed when the "pause" ends.
The system is up to date 23.04 and mutter is using the Intel HD 530
integrated graphics. I do not believe this issue happened before 23.04
was released, although it has been intermittent and persistent since
that time.
Attached a strace with timestamps which provides an example of a multi-
second pause. Using grep -A1 epoll_wait you can see the instances of
the GEM operations during the pause. Eventually at around 09:40:57
local time in the trace the "pause" ended.
Example of an instance of the GEM operation trace after a ~1 second
epoll timeout:
[pid 686436] 09:40:54.750468 poll([{fd=3, events=POLLOUT}], 1, 5) = 1 ([{fd=3,
revents=POLLOUT}])
[pid 686436] 09:40:54.750719 epoll_wait(8, [], 256, 671) = 0
[pid 686436] 09:40:55.422886 ioctl(11, DRM_IOCTL_SYNCOBJ_DESTROY,
0x7ffce0975140) = 0
[pid 686436] 09:40:55.423213 ioctl(11, DRM_IOCTL_I915_GEM_EXECBUFFER2,
0x7ffce09751d0) = 0
[pid 686436] 09:40:55.423525 ioctl(11, DRM_IOCTL_I915_GEM_MADVISE,
0x7ffce0975098) = 0
[pid 686436] 09:40:55.423642 ioctl(11, DRM_IOCTL_SYNCOBJ_WAIT, 0x7ffce0974ef0)
= 0
[pid 686436] 09:40:55.423876 ioctl(11, DRM_IOCTL_I915_GEM_MADVISE,
0x7ffce0974fec) = 0
[pid 686436] 09:40:55.423971 ioctl(11, DRM_IOCTL_SYNCOBJ_CREATE,
0x7ffce0975100) = 0
[pid 686436] 09:40:55.424218 writev(45,
[{iov_base="#\221\360s\0\0\0\0\2\0\0\0\204\v \4\3\0\200\3s\213\0\0\243\v
\4\244\v \4", iov_len=32}], 1) = 32
[pid 686436] 09:40:55.424471 writev(45,
[{iov_base="#\221\360s\2\0\0\0\1\0\0\2\204\v
\4\3\0\200\3r\213\0\0\376S\340\252\37\2\0\0\311uf\0\0\0\0\0", iov_len=40}], 1)
= 40
[pid 686436] 09:40:55.424810 poll([{fd=3, events=POLLOUT}], 1, 5) = 1 ([{fd=3,
revents=POLLOUT}])
[pid 686436] 09:40:55.425150 epoll_wait(8, [], 256, 0) = 0
These pauses are often 10-15 seconds in length but can also be much
longer. I have observed it happening even with the screen locked
(screen lock unresponsive until pause ends).
FD 8 in the trace is anon_inode:[eventpoll] and FD 11 is
/dev/dri/renderD129, the Intel HD 530 DRI device.
Kernel is 6.2.0-24-generic from the distribution.
** Affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "strace.txt"
https://bugs.launchpad.net/bugs/2025662/+attachment/5683579/+files/strace.txt
** Description changed:
Hi, I have this weird bug in mutter which seems to correlate with uptime
- if I kill mutter the problem seems to go away for a few days, although
killing mutter is very inconvenient because all applications are also
killed even with session persistence.
Upon strace analysis it can be seen that when the pauses are happening
there is a specific trace involving GEM operations happening immediately
- after a 1 second epoll expires.
+ after a ~1 second epoll expires.
During this state the entire UI is paused - video does not update, mouse
cursor does not move, keypresses have no response. However, input
events are "queued" so that when the pause ends, the mouse instantly
warps across the screen, and if a key was down at the time the pause
began, the key is repeated hundreds of times since it seems that the
key-up event is only processed when the "pause" ends.
The system is up to date 23.04 and mutter is using the Intel HD 530
integrated graphics. I do not believe this issue happened before 23.04
was released, although it has been intermittent and persistent since
that time.
Attached a strace with timestamps which provides an example of a multi-
second pause. Using grep -A1 epoll_wait you can see the instances of
the GEM operations during the pause. Eventually at around 09:40:57
local time in the trace the "pause" ended.
- Example of an instance of the GEM operation trace after a 1 second epoll
- timeout:
+ Example of an instance of the GEM operation trace after a ~1 second
+ epoll timeout:
[pid 686436] 09:40:54.750468 poll([{fd=3, events=POLLOUT}], 1, 5) = 1
([{fd=3, revents=POLLOUT}])
[pid 686436] 09:40:54.750719 epoll_wait(8, [], 256, 671) = 0
[pid 686436] 09:40:55.422886 ioctl(11, DRM_IOCTL_SYNCOBJ_DESTROY,
0x7ffce0975140) = 0
[pid 686436]
[Desktop-packages] [Bug 2025651] Re: default Japanese font in snap apps is ugly
** Tags added: lunar mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: New Status in language-selector package in Ubuntu: New Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 2025651] Re: default Japanese font in snap apps is ugly
I hope we will figure out the reason for this snap behavior. Otherwise there are workarounds. Not pulling fonts-droid-fallback was mentioned above. Or this change would probably do it: --- /usr/share/fontconfig/conf.avail/70-fonts-noto-cjk.conf.orig +++ /usr/share/fontconfig/conf.avail/70-fonts-noto-cjk.conf @@ -68,7 +68,7 @@ sans-serif - + Noto Sans CJK JP Or maybe do the equivalent in language-selector-common instead, to not add an Ubuntu delta to fonts-noto-cjk. But I don't know how to test these things for snaps (read-only). @Sebastien: Is there an easy way? (It was much better when the snaps honored the system's /etc/fonts/conf.d .) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: New Status in language-selector package in Ubuntu: New Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 1869042] Re: [nvidia] fractional monitor scaling fails due to overlapping monitors
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1869042 Title: [nvidia] fractional monitor scaling fails due to overlapping monitors Status in mutter package in Ubuntu: Confirmed Bug description: After an upgrade with focal-proposed this morning, I am unable to set any scaling for any of my monitors without the monitor turning blank for 15 seconds and reverting to 100% scaling. I am using X11 with gnome and proprietary nvidia drivers on Focal. I have 3 monitors attached, all 4K, and my usual setup is to enable fractional scaling, and set all 3 monitors to 150% scaling. Now however, I cannot change the monitors to use any scaling, and even if I disconnect 2 of the monitors to only have a single monitor I still cannot use scaling. Finally note I am just using the Settings window, I haven't fiddled with xrandr at all manually. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Uname: Linux 5.4.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 11:24:05 2020 InstallationDate: Installed on 2019-07-05 (264 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+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 1983117] Re: "Focus Follow Mouse" auto-raises windows when it shouldn't
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1983117 Title: "Focus Follow Mouse" auto-raises windows when it shouldn't Status in mutter package in Ubuntu: Confirmed Bug description: Steps to reproduce on Jammy LTS: 1. Create a new empty user and login under Wayland 2. Using gnome-tweaks select "Windows" -> "Window Focus" -> "Focus on Hover" 3. Notice that "Raise Windows When Focused" is disabled Windows auto-raise when changing workspaces: 1. Open two terminal windows and partially overlap them 2. Place the mouse over the lower terminal window so that it remains lowered 3. Do not move the mouse: Press Super-End to change to another workspace, then Super-Begin to go back 4. Observe that the terminal window the mouse is over has been raised The expected behaviour is that windows are not auto-raised when changing workspaces Windows auto-raise when closing windows: 1. Open three terminal windows such that parts of all windows are visible but all windows overlap. 2. Place the mouse inside the topmost terminal so that it is within the visible lowest terminal 3. Without moving the mouse Ctrl-D the terminal to close it 4. Observe that the lowest terminal window the mouse is over has been raised to the top. The expected behaviour is that windows are not auto-raised when closing windows Logout/Login using X and repeat these actions. Notice that window ordering remains fixed in order. This has been the expected behaviour of gnome for the last 10 years or so. This is a behaviour regression for Ubuntu users upgrading from the last LTS (using X). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 12:11:27 2022 InstallationDate: Installed on 2022-06-25 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1983117/+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 2025526] Re: Printer is not available in chromium snap
I fixed the problem myself by setting the printer up with a cupsdriver. Since my printer is connected to my LAN as a networkprinter it is using the default "driverless" setup that works out of the box after i install Kubuntu. It works for native apps and flatpaks as well. Applications installed as snap seem to be unable to detect the printer. This happens on three different systems. -- 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/2025526 Title: Printer is not available in chromium snap Status in chromium-browser package in Ubuntu: Incomplete Status in cups package in Ubuntu: Incomplete Bug description: My printer is not available in chromium. I had the same problem in firefox but fixed it with the following command: sudo snap connect firefox:cups-control However this did not work with the chromium snap. I got the following error: snap "chromium" has no plug named "cups-control" My printer is a network printer and is automatically detected by my Kubuntu install. It works out of the box with all native apps and flatpaks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025526/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012388] Re: X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks
Good morning Daniel, just updating you that I have tested for 7 days already. Your suggestion works beautifully. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2012388 Title: X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: Hardware Model: Dell Inc. Inspiron 16 Plus 7620 Firmware version: 1.5.1 CPU i7-12700H x20 GPU: Nvidia RTX3060 / MaxQ GPU: Intel Alder Lake-P Release: Lunar Lobster Architecture: AMD64 Kernel: 6.1.0-16-generic GNOME version: 44.rc Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue with window focus when windows are placed under the top-right system tray. Since it is hard to explain, I am attaching a screenshot. I am unable to click or interact with anything in the area within green rectangle. Applications affected: - Firefox (snap) - Chromium (snap) - Vivaldi Browser (deb) - Mattermost (snap) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~rc-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 20:35:05 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-23 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44~rc-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025654] Re: package gnome-menus 3.36.0-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
OK, seems I may have had a broken Python setup. Works after fixing it with sudo apt install --reinstall python3 python python3-minimal --fix-broken ** Changed in: gnome-menus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/2025654 Title: package gnome-menus 3.36.0-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gnome-menus package in Ubuntu: Invalid Bug description: This happened after running: sudo apt install eid-mw eid-viewer Which I did after installing the following deb manually: https://eid.belgium.be/sites/default/files/software/eid-archive_2023.2_all.deb ProblemType: Package DistroRelease: Ubuntu 22.04 Package: gnome-menus 3.36.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jul 3 15:56:42 2023 Dependencies: ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2023-06-05 (28 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: gnome-menus Title: package gnome-menus 3.36.0-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/2025654/+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 2025654] [NEW] package gnome-menus 3.36.0-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: This happened after running: sudo apt install eid-mw eid-viewer Which I did after installing the following deb manually: https://eid.belgium.be/sites/default/files/software/eid-archive_2023.2_all.deb ProblemType: Package DistroRelease: Ubuntu 22.04 Package: gnome-menus 3.36.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jul 3 15:56:42 2023 Dependencies: ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2023-06-05 (28 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: gnome-menus Title: package gnome-menus 3.36.0-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-menus (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/2025654 Title: package gnome-menus 3.36.0-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gnome-menus package in Ubuntu: Invalid Bug description: This happened after running: sudo apt install eid-mw eid-viewer Which I did after installing the following deb manually: https://eid.belgium.be/sites/default/files/software/eid-archive_2023.2_all.deb ProblemType: Package DistroRelease: Ubuntu 22.04 Package: gnome-menus 3.36.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jul 3 15:56:42 2023 Dependencies: ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2023-06-05 (28 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: gnome-menus Title: package gnome-menus 3.36.0-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/2025654/+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 2025526] Re: Printer is not available in chromium snap
Heiko, please run the following commands and post their output here: lpstat -v lpstat -p cups.lpstat -v cups.lpstat -p snap list | grep cups snap connections cups -- 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/2025526 Title: Printer is not available in chromium snap Status in chromium-browser package in Ubuntu: Incomplete Status in cups package in Ubuntu: Incomplete Bug description: My printer is not available in chromium. I had the same problem in firefox but fixed it with the following command: sudo snap connect firefox:cups-control However this did not work with the chromium snap. I got the following error: snap "chromium" has no plug named "cups-control" My printer is a network printer and is automatically detected by my Kubuntu install. It works out of the box with all native apps and flatpaks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025526/+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 2025526] Re: Printer is not available in chromium snap
** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete ** Changed in: cups (Ubuntu) Status: New => Incomplete -- 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/2025526 Title: Printer is not available in chromium snap Status in chromium-browser package in Ubuntu: Incomplete Status in cups package in Ubuntu: Incomplete Bug description: My printer is not available in chromium. I had the same problem in firefox but fixed it with the following command: sudo snap connect firefox:cups-control However this did not work with the chromium snap. I got the following error: snap "chromium" has no plug named "cups-control" My printer is a network printer and is automatically detected by my Kubuntu install. It works out of the box with all native apps and flatpaks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025526/+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 2025651] Re: default Japanese font in snap apps is ugly
Inspired by https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/comments/35 Mantic: $ snap run --shell firefox $ LC_CTYPE=ja_JP.UTF-8 fc-match -s sans-serif | head DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular" DejaVuSans.ttf: "DejaVu Sans" "Book" DejaVuSans-Bold.ttf: "DejaVu Sans" "Bold" KhmerOS.ttf: "Khmer OS" "Regular" NimbusSans-Regular.otf: "Nimbus Sans" "Regular" Loma.ttf: "Loma" "Regular" Waree.ttf: "Waree" "Regular" Umpush-Bold.ttf: "Umpush" "Bold" Laksaman.ttf: "Laksaman" "Regular" NotoSansCJK-Regular.ttc: "Noto Sans CJK JP" "Regular" Jammy: $ snap run --shell firefox $ LC_CTYPE=ja_JP.UTF-8 fc-match -s sans-serif | head NotoSansCJK-Regular.ttc: "Noto Sans CJK JP" "Regular" DejaVuSans.ttf: "DejaVu Sans" "Book" DejaVuSans-Bold.ttf: "DejaVu Sans" "Bold" NimbusSans-Regular.otf: "Nimbus Sans" "Regular" Lohit-Devanagari.ttf: "Lohit Devanagari" "Regular" DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular" KhmerOS.ttf: "Khmer OS" "Regular" Waree.ttf: "Waree" "Regular" Umpush-Bold.ttf: "Umpush" "Bold" padmaa-Medium-0.5.ttf: "padmaa" "regular" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: New Status in language-selector package in Ubuntu: New Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 2025526] Re: Printer is not available in chromium snap
It could be a problem in Chromium or Cups then. If you start Chromium from the command line with chromium --enable-logging=stderr |& tee chromium.log and work from there, do you see anything relevant in the output? If yes, please attach the generated log file to this bug report. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => New ** Description changed: - My printer is not available in chromium. I had the same problem in - firefox but fixed it with the following command: sudo snap connect - firefox:cups-control + My printer is not available in chromium. I had the same problem in firefox but fixed it with the following command: + + sudo snap connect firefox:cups-control - However this did not work with the chromium snap i got the following error: - snap "chromium" has no plug named "cups-control" + However this did not work with the chromium snap. I got the following + error: + + snap "chromium" has no plug named "cups-control" My printer is a network printer and is automatically detected by my Kubuntu install. It works out of the box with all native apps and - flatpaks + flatpaks. ** Also affects: cups (Ubuntu) Importance: Undecided Status: 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/2025526 Title: Printer is not available in chromium snap Status in chromium-browser package in Ubuntu: New Status in cups package in Ubuntu: New Bug description: My printer is not available in chromium. I had the same problem in firefox but fixed it with the following command: sudo snap connect firefox:cups-control However this did not work with the chromium snap. I got the following error: snap "chromium" has no plug named "cups-control" My printer is a network printer and is automatically detected by my Kubuntu install. It works out of the box with all native apps and flatpaks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025526/+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 2025651] Re: default Japanese font in snap apps is ugly
lunar result: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/comments/27 jammy result: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/comments/28 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: New Status in language-selector package in Ubuntu: New Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 1840908] Re: Stick to 1.16 for hirsute
This bug was fixed in the package cairo - 1.17.8-2 --- cairo (1.17.8-2) experimental; urgency=medium * Add 2 patches to update check-def test for ARM & MIPS -- Jeremy Bícha Sun, 02 Jul 2023 10:02:22 -0400 cairo (1.17.8-1) experimental; urgency=medium * New upstream release (Closes: #958487) - CVE-2019-6462 Fix infinite loop in cairo-arc.c (Closes: #929945) * Build with meson * Stop building cairo-perf-utils (Closes: #715709) * Drop all patches except for the Hurd patch * Cherry-pick patch to fix tee build * debian/control.in: Build-Depend on libspectre-dev * debian/control.in: Drop ancient Breaks & obsolete version restraints * debian/control.in: Build-Depend on ghostscript, libpoppler-glib-dev & librsvg2-dev for build tests * debian/docs: README → README.md * debian/libcairo2.symbols: Add new symbols * Don't disable png support for the udeb * Enable some build tests * Temporarily disable docs test * Update standards version to 4.6.2, no changes needed -- Jeremy Bícha Fri, 30 Jun 2023 19:29:07 -0400 ** Changed in: cairo (Ubuntu) Status: Triaged => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-6462 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1840908 Title: Stick to 1.16 for hirsute Status in cairo package in Ubuntu: Fix Released Bug description: There is no stable 1.18 planned for before hirsute and nothing we really need in 1.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1840908/+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 2025651] Re: default Japanese font in snap apps is ugly
** Also affects: snappy Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: New Status in language-selector package in Ubuntu: New Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 2017076] Re: default Chinese font in snap apps is ugly
Sorry for late response. I filed bug #2025651. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Fix Released Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+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 2025526] Re: Printer is not available in chromium snap
This is the output: snap connections chromium Schnittstelle PlugSlot Notizen audio-playbackchromium:audio-playback :audio-playback - audio-record chromium:audio-record :audio-record - bluez chromium:bluez :bluez - browser-support chromium:browser-sandbox :browser-support - camerachromium:camera :camera - content chromium:foo-install-cups - - content[gnome-3-38-2004] chromium:gnome-3-38-2004 gnome-3-38-2004:gnome-3-38-2004 - content[gtk-3-themes] chromium:gtk-3-themes gtk-common-themes:gtk-3-themes - content[icon-themes] chromium:icon-themes gtk-common-themes:icon-themes- content[sound-themes] chromium:sound-themes gtk-common-themes:sound-themes - cups chromium:cups cups:cups - desktop chromium:desktop:desktop - desktop-legacychromium:desktop-legacy :desktop-legacy - gsettings chromium:gsettings :gsettings - home chromium:home :home - joystick chromium:joystick :joystick - mount-observe chromium:mount-observe - - mpris - chromium:mpris - network chromium:network:network - network-bind chromium:network-bind :network-bind - network-manager chromium:network-manager- - openglchromium:opengl :opengl - password-manager-service chromium:password-manager-service - - personal-fileschromium:chromium-config :personal-files - raw-usb chromium:raw-usb- - removable-media chromium:removable-media :removable-media - screen-inhibit-controlchromium:screen-inhibit-control :screen-inhibit-control - system-files chromium:etc-chromium-browser-policies :system-files - system-packages-doc chromium:system-packages-doc :system-packages-doc - u2f-devices chromium:u2f-devices:u2f-devices - unity7chromium:unity7 :unity7 - upower-observechromium:upower-observe :upower-observe - wayland chromium:wayland:wayland - x11 chromium:x11:x11 - -- 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/2025526 Title: Printer is not available in chromium snap Status in chromium-browser package in Ubuntu: Incomplete Bug description: My printer is not available in chromium. I had the same problem in firefox but fixed it with the following command: sudo snap connect firefox:cups-control However this did not work with the chromium snap i got the following error: snap "chromium" has no plug named "cups-control" My printer is a network printer and is automatically detected by my Kubuntu install. It works out of the box with all native apps and flatpaks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025526/+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 2025651] [NEW] default Japanese font in snap apps is ugly
Public bug reported: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. ** Affects: snappy Importance: Undecided Status: New ** Affects: language-selector (Ubuntu) Importance: Undecided Status: New ** Attachment added: "mantic result" https://bugs.launchpad.net/bugs/2025651/+attachment/5683556/+files/Screenshot%20from%202023-07-03%2021-23-41.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: New Status in language-selector package in Ubuntu: New Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 1993356] Re: udisks doesn't make sense from cdrom
No progress in the upstream bug so far. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1993356 Title: udisks doesn't make sense from cdrom Status in udisks: Unknown Status in qemu package in Ubuntu: Triaged Status in udisks2 package in Ubuntu: Triaged Bug description: udisks doesn't make sense from cdrom there are journal errors from sending ATA command IDENTIFY, maybe incomplete kernel or qemu support? To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1993356/+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 2023913] Re: Release gnome-shell 42.9 to Jammy
Because of an apt phasing issue (LP: #2025462), gnome-shell 42.9 must NOT be released to updates until mutter 42.9 has been released to jammy- updates and has fully phased. ** Description changed: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.9/NEWS The overall GNOME project considers GNOME 42 to be end of life now and there are no more scheduled releases for GNOME Shell 42 after 42.9 The current version of GNOME Shell in Jammy is 42.5. Test Case - Complete all the non-optional test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This update requires mutter 42.9 (LP: #1998286). This was done with bumped dependencies in debian/control. gnome-shell 42.9 could be run with mutter 42.5, but mixing different versions of mutter & gnome-shell is not supported upstream. + + WARNING + --- + Because of an apt phasing issue (LP: #2025462), gnome-shell 42.9 must NOT be released to updates until mutter 42.9 has been released to jammy-updates and has fully phased. -- 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/2023913 Title: Release gnome-shell 42.9 to Jammy Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.9/NEWS The overall GNOME project considers GNOME 42 to be end of life now and there are no more scheduled releases for GNOME Shell 42 after 42.9 The current version of GNOME Shell in Jammy is 42.5. Test Case - Complete all the non-optional test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This update requires mutter 42.9 (LP: #1998286). This was done with bumped dependencies in debian/control. gnome-shell 42.9 could be run with mutter 42.5, but mixing different versions of mutter & gnome-shell is not supported upstream. WARNING --- Because of an apt phasing issue (LP: #2025462), gnome-shell 42.9 must NOT be released to updates until mutter 42.9 has been released to jammy-updates and has fully phased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2023913/+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 2025290] Re: user-accounts: GFileInfo created without standard::symlink-target
** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2025290 Title: user-accounts: GFileInfo created without standard::symlink-target Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: If I open g-c-c from terminal on an updated mantic install and switch to the Users panel, I see some warning messages (see attachment). I don't know the significance of it, but it does not look right... ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 28 20:55:07 2023 InstallationDate: Installed on 2022-05-07 (416 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-06-20 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2025290/+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 2025290] Re: user-accounts: GFileInfo created without standard::symlink-target
Fixed upstream. https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/701f7c6c -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2025290 Title: user-accounts: GFileInfo created without standard::symlink-target Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: If I open g-c-c from terminal on an updated mantic install and switch to the Users panel, I see some warning messages (see attachment). I don't know the significance of it, but it does not look right... ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 28 20:55:07 2023 InstallationDate: Installed on 2022-05-07 (416 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-06-20 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2025290/+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 2017076] Re: default Chinese font in snap apps is ugly
On 2023-07-03 11:08, Sebastien Bacher wrote: > Could you use a new bug to discuss the japanese issue? Yes, Mitsuya plans to submit a new bug once he has checked mantic. (I have used this one in the meantime to share a couple of thoughts.) > It could help also to know if you are using the core20 or core22 > version of firefox and they have the same issue. Mitsuya doesn't see it in jammy, and neither do I: $ snap run --shell firefox To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. /home/gunnar$ LC_CTYPE=ja_JP.UTF-8 fc-match sans-serif NotoSansCJK-Regular.ttc: "Noto Sans CJK JP" "Regular" Even if fonts-droid-fallback is present there too. (But I notice another weird issue: In the FF Settings it shows Ubuntu as the default serif font irrespective of locale. How come?) > Is the configuration in the snap environment matching the real > system one? It is not per se, is it? At least not in lunar and mantic, where we use an upgraded fontconfig in the system. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Fix Released Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+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 2023766] Re: Mouse cursor stutters over GUI elements that are animated
Jammy fix proposed: https://salsa.debian.org/gnome- team/mutter/-/merge_requests/99 -- 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/2023766 Title: Mouse cursor stutters over GUI elements that are animated Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Status in mutter source package in Lunar: Triaged Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] Mouse cursor stutters over GUI elements that are animated, such as GTK apps, web pages and shell elements. [ Test Plan ] 1. Open Settings. 2. Move the cursor up/down over an empty area of the desktop. 3. Move the cursor up/down over the list pane on the left side of the Settings window. Expect: No difference in cursor smoothness whether the window below is animating in response to movement or not. [ Where problems could occur ] In frame scheduling, so the risk is more stuttering or screen freezes. [ Workaround ] Add this to /etc/environment: CLUTTER_PAINT=disable-dynamic-max-render-time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/+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 2024135] Re: Default right click method on touchpads should be with two fingers
Discussing this over chat there is a concern that changing the default will break corner clicking which might feel a regression to some users -- 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/2024135 Title: Default right click method on touchpads should be with two fingers Status in gnome-control-center: Fix Released Status in ubuntu-settings package in Ubuntu: New Bug description: The default right click method on touchpads should be with two fingers so you can right click without having to look at the touchpad. Modern laptops have supported this for a decade, modern OSes like macOS and ChromeOS default to it, and upstream GNOME has defaulted to it since version 3.28 in 2018. This issue was fixed at the start of 2018 in bug 1699033, but then reverted again in: https://launchpad.net/ubuntu/+source/ubuntu- settings/18.10.8 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2024135/+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 2017076] Re: default Chinese font in snap apps is ugly
Could you use a new bug to discuss the japanese issue? It could help also to know if you are using the core20 or core22 version of firefox and they have the same issue. Is the configuration in the snap environment matching the real system one? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Fix Released Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+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 2025527] Re: nautilus segfault
Thanks, closing then if it's fixed in the current version ** Changed in: nautilus (Ubuntu) Importance: Undecided => High ** Changed in: nautilus (Ubuntu) Status: New => Fix Released -- 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/2025527 Title: nautilus segfault Status in nautilus package in Ubuntu: Fix Released Bug description: Later ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-47.49-generic 5.19.17 Uname: Linux 5.19.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 1 10:20:46 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-12-22 (190 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-dropbox 2019.02.14-1.2 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2025527/+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 2023766] Re: Mouse cursor stutters over GUI elements that are animated
** Changed in: mutter (Ubuntu Lunar) Assignee: Daniel van Vugt (vanvugt) => Jeremy Bícha (jbicha) ** Changed in: mutter (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2023766 Title: Mouse cursor stutters over GUI elements that are animated Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Status in mutter source package in Lunar: Triaged Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] Mouse cursor stutters over GUI elements that are animated, such as GTK apps, web pages and shell elements. [ Test Plan ] 1. Open Settings. 2. Move the cursor up/down over an empty area of the desktop. 3. Move the cursor up/down over the list pane on the left side of the Settings window. Expect: No difference in cursor smoothness whether the window below is animating in response to movement or not. [ Where problems could occur ] In frame scheduling, so the risk is more stuttering or screen freezes. [ Workaround ] Add this to /etc/environment: CLUTTER_PAINT=disable-dynamic-max-render-time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/+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 2025531] Re: file-roller crashed with signal 5 in g_object_new_valist()
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: file-roller (Ubuntu) Importance: Undecided => Low ** Changed in: file-roller (Ubuntu) Status: New => Incomplete ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2025531/+attachment/5683242/+files/CoreDump.gz ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/2025531 Title: file-roller crashed with signal 5 in g_object_new_valist() Status in file-roller package in Ubuntu: Incomplete Bug description: While edubuntu-mantic parallel installing kubuntu kde-desktop ubuntucinnamon-desktop: E: /tmp/apt-dpkg-install-iBrOhl/518-kubuntu-settings- desktop_1%3a23.04.5_all.deb: »/etc/skel/.face« tried to override because of desktop-base 12.0.6ubuntu1 ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: file-roller 43.0-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 1 14:35:45 2023 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2023-07-01 (0 days ago) InstallationMedia: Edubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230629) ProcCmdline: /usr/bin/file-roller --service ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 5 SourcePackage: file-roller StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: file-roller crashed with signal 5 in g_object_new_valist() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: My solution in synaptic was: uninstall kubuntu-desktop and kubuntu-settings-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2025531/+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 2023766] Re: Mouse cursor stutters over GUI elements that are animated
** Summary changed: - Mouse cursor stutters but only over GUI elements that are animated + Mouse cursor stutters over GUI elements that are animated ** Description changed: [ Impact ] - Mouse cursor stutters but only over GUI elements that are animated. + Mouse cursor stutters over GUI elements that are animated, such as GTK + apps, web pages and shell elements. [ Test Plan ] 1. Open Settings. 2. Move the cursor up/down over an empty area of the desktop. 3. Move the cursor up/down over the list pane on the left side of the Settings window. Expect: No difference in cursor smoothness whether the window below is animating in response to movement or not. [ Where problems could occur ] In frame scheduling, so the risk is more stuttering or screen freezes. [ Workaround ] Add this to /etc/environment: CLUTTER_PAINT=disable-dynamic-max-render-time -- 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/2023766 Title: Mouse cursor stutters over GUI elements that are animated Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Triaged Status in mutter source package in Lunar: Triaged Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] Mouse cursor stutters over GUI elements that are animated, such as GTK apps, web pages and shell elements. [ Test Plan ] 1. Open Settings. 2. Move the cursor up/down over an empty area of the desktop. 3. Move the cursor up/down over the list pane on the left side of the Settings window. Expect: No difference in cursor smoothness whether the window below is animating in response to movement or not. [ Where problems could occur ] In frame scheduling, so the risk is more stuttering or screen freezes. [ Workaround ] Add this to /etc/environment: CLUTTER_PAINT=disable-dynamic-max-render-time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/+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 2016217] Re: gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer() from GjsAutoPointer()
Bumped to High, just because this is the top gnome-shell crasher for
lunar.
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
appindicator (Ubuntu)
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: gnome-shell-extension-appindicator (Ubuntu)
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Importance: Undecided => High
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: New => Confirmed
--
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/2016217
Title:
gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from
st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer()
from GjsAutoPointer()
Status in GNOME Shell:
New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
Confirmed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
44.0-2ubuntu3, the problem page at
https://errors.ubuntu.com/problem/677a794c2788cd0244c8fc6d7d34780a85127bc9
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
#0 0x7f3aa429dd82 in clutter_actor_remove_effect
(self=self@entry=0x55d60fa59e90, effect=0x55d6101c48a0) at
../clutter/clutter/clutter-actor.c:14830
__inst = 0x55d6101c48a0
__t = 94377826055744
__r =
_g_boolean_var_274 =
__func__ = "clutter_actor_remove_effect"
#1 0x7f3aa3f9d27f in st_scroll_view_dispose (object=0x55d60fa59e90) at
../src/st/st-scroll-view.c:246
priv = 0x55d60fa59a00
#2 0x7f3aa4aeada0 in g_object_unref (_object=0x55d60fa59e90) at
../../../gobject/gobject.c:3891
_pp =
gaig_temp =
gaig_temp =
weak_locations =
nqueue = 0x55d60fa6da60
_ptr =
object = 0x55d60fa59e90
old_ref =
retry_atomic_decrement1 =
__func__ = "g_object_unref"
#3 0x7f3aa43b4b2c in GjsAutoPointer<_GObject, void, _object_unref,
_object_ref>::reset (ptr=0x0, this=) at ../gjs/jsapi-util.h:229
old_ptr =
#4 GjsAutoPointer<_GObject, void, _object_unref,
_object_ref>::~GjsAutoPointer (this=, this=) at
../gjs/jsapi-util.h:172
No locals.
#5 GjsSmartPointer<_GObject>::~GjsSmartPointer (this=,
this=) at ../gjs/jsapi-util.h:349
No locals.
#6 ObjectInstance::release_native_object (this=0x55d60fa0ce80) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1524
No locals.
#7 ObjectInstance::release_native_object (this=0x55d60fa0ce80) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1500
No locals.
#8 0x7f3aa43c9ec0 in ObjectInstance::~ObjectInstance (this=, this=) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1945
was_using_toggle_refs = false
had_toggle_up = false
had_toggle_down =
had_toggle_up =
had_toggle_down =
was_using_toggle_refs =
#9 GIWrapperInstance::finalize_impl (this=0x55d60fa0ce80) at ../gi/wrapperutils.h:1113
No locals.
#10 ObjectInstance::finalize_impl (gcx=, obj=0x35b1abd24820,
this=0x55d60fa0ce80) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1912
query = {type = 94377830362416, type_name = 0x7f3aa3fdcda6
"StScrollView", class_size = 664, instance_size = 48}
query =
_g_boolean_var_74 =
#11 GIWrapperBase::finalize
(gcx=, obj=0x35b1abd24820) at ../gi/wrapperutils.h:411
priv = 0x55d60fa0ce80
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2016217/+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 2025599] [NEW] BlueZ release 5.68
Public bug reported: BlueZ release 5.68 is now available: https://mirrors.edge.kernel.org/pub/linux/bluetooth/ ** Affects: bluez (Ubuntu) Importance: Wishlist Assignee: Daniel van Vugt (vanvugt) Status: Triaged ** Tags: mantic udeng-894 ** Tags added: udeng-894 ** Changed in: bluez (Ubuntu) Importance: Undecided => Wishlist ** Changed in: bluez (Ubuntu) Status: New => Triaged ** Changed in: bluez (Ubuntu) Milestone: None => ubuntu-23.10-feature-freeze -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2025599 Title: BlueZ release 5.68 Status in bluez package in Ubuntu: Triaged Bug description: BlueZ release 5.68 is now available: https://mirrors.edge.kernel.org/pub/linux/bluetooth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2025599/+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 1970389] Re: [nvidia] Janky text entry and frames appear out of order in Xwayland apps
A potential fix is in progress: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1120 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1970389 Title: [nvidia] Janky text entry and frames appear out of order in Xwayland apps Status in X.Org X server: New Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in xwayland package in Ubuntu: Confirmed Bug description: When writing into text fields in some applications (Firefox, VS Code) on Jammy in a GNOME / Wayland session, I can see an effect best described as the glyphs appearing / disappearing sometimes repeatedly. I have attached a recording from my phone (since attempting to record a screencast fails). This doesn't happen always, and it appear somehow sensitive to some environmental condition (load?) since for example when I'm on a video call, the effect seems to not be happening so often. I have also experienced a few instances of a currently not-focused window disappearing (seeing through to a window that is below that window), but cannot reproduce that reliably. I have the NVIDIA driver 510 in use, RTX3090-only 16-core Zen1 Threadripper system with no integrated GPU. No similar effects visible when in a GNOME / Xorg session. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 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 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 12:17:02 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-11-08 (168 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-22 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1970389/+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 1970389] Re: [nvidia] Janky text entry and frames appear out of order in Xwayland apps
Sounds like: > Xwayland does not provide a suitable mechanism for our driver to synchronize > application > rendering with presentation, which can cause visual corruption in some > circumstances. from http://us.download.nvidia.com/XFree86/Linux-x86_64/535.54.03/README/wayland- issues.html ** Also affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1970389 Title: [nvidia] Janky text entry and frames appear out of order in Xwayland apps Status in X.Org X server: New Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in xwayland package in Ubuntu: Confirmed Bug description: When writing into text fields in some applications (Firefox, VS Code) on Jammy in a GNOME / Wayland session, I can see an effect best described as the glyphs appearing / disappearing sometimes repeatedly. I have attached a recording from my phone (since attempting to record a screencast fails). This doesn't happen always, and it appear somehow sensitive to some environmental condition (load?) since for example when I'm on a video call, the effect seems to not be happening so often. I have also experienced a few instances of a currently not-focused window disappearing (seeing through to a window that is below that window), but cannot reproduce that reliably. I have the NVIDIA driver 510 in use, RTX3090-only 16-core Zen1 Threadripper system with no integrated GPU. No similar effects visible when in a GNOME / Xorg session. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 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 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 12:17:02 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-11-08 (168 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-22 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1970389/+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 2025526] Re: Printer is not available in chromium snap
Thanks for the bug report, Heiko. We do not have cups-control in Chromium. What is the output of 'snap connections chromium'? Is the cups one connected? ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/2025526 Title: Printer is not available in chromium snap Status in chromium-browser package in Ubuntu: Incomplete Bug description: My printer is not available in chromium. I had the same problem in firefox but fixed it with the following command: sudo snap connect firefox:cups-control However this did not work with the chromium snap i got the following error: snap "chromium" has no plug named "cups-control" My printer is a network printer and is automatically detected by my Kubuntu install. It works out of the box with all native apps and flatpaks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025526/+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 2025460] Re: night light stopped working
Thanks for the bug report. Please run: lspci -k > lspci.txt journalctl -b0 > journal.txt and attach the resulting text files here. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Package changed: gnome-shell (Ubuntu) => linux-hwe-5.15 (Ubuntu) -- 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/2025460 Title: night light stopped working Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Same as #1752680 but happening from cold boot and won't work again after disabling/re-enabling night light. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-76.83~20.04.1-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 30 10:25:21 2023 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-24 (978 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 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/linux-hwe-5.15/+bug/2025460/+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 2025537] Re: chrome Check failed
*** This bug is a duplicate of bug 2017980 *** https://bugs.launchpad.net/bugs/2017980 ** This bug has been marked a duplicate of bug 2017980 Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) -- 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/2025537 Title: chrome Check failed Status in chromium-browser package in Ubuntu: Incomplete Bug description: local_slava@worksystem:~$ google-chrome [19394:19394:0701/201749.072306:FATAL:credentials.cc(127)] Check failed: . : Отказано в доступе (13) Trace/breakpoint trap (core dumped) How fix this? After update ubuntu... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025537/+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 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
Removing chromium-browser as affected package because this wasn't actually verified on Chromium. If it is verified on Chromium, please revert that. ** No longer affects: chromium-browser (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/2017980 Title: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+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 2025460] Re: night light stopped working
** Tags added: gamma -- 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/2025460 Title: night light stopped working Status in gnome-shell package in Ubuntu: New Bug description: Same as #1752680 but happening from cold boot and won't work again after disabling/re-enabling night light. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-76.83~20.04.1-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 30 10:25:21 2023 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-24 (978 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 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/2025460/+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 2025550] Re: External display is not detecting
Thanks for the bug report. It appears you have no nvidia kernel module loaded. And the attached logs aren't enough to explain why. Please run: journalctl -b0 > journal.txt find /var/lib/dkms/nvidia -name make.log and then attach both journal.txt and make.log here. ** Summary changed: - External display is not detecting + nvidia 535 kernel module is not loaded ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-535 (Ubuntu) ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2025550 Title: nvidia 535 kernel module is not loaded Status in nvidia-graphics-drivers-535 package in Ubuntu: Incomplete Bug description: After an update my external display switched off and is not being detected. I connected my external display to windows laptop to test and it worked. Some additional information: lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 xrandr --listmonitors Monitors: 1 0: +*XWAYLAND0 1920/340x1080/190+0+0 XWAYLAND0 dpkg -l | grep -i nvidia ii libnvidia-cfg1-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA binary OpenGL/GLX configuration library ii libnvidia-common-535 535.54.03-0ubuntu0.23.04.2 all Shared files used by the NVIDIA libraries rc libnvidia-compute-525:amd64 525.116.04-0ubuntu0.23.04.1 amd64NVIDIA libcompute package ii libnvidia-compute-535:amd64535.54.03-0ubuntu0.23.04.2 amd64NVIDIA libcompute package ii libnvidia-decode-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA Video Decoding runtime libraries ii libnvidia-encode-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64NVENC Video Encoding runtime library ii libnvidia-extra-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64Extra libraries for the NVIDIA driver ii libnvidia-fbc1-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA OpenGL-based Framebuffer Capture runtime library ii libnvidia-gl-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD rc linux-modules-nvidia-525-6.2.0-20-generic 6.2.0-20.20+2 amd64Linux kernel nvidia modules for version 6.2.0-20 rc linux-modules-nvidia-525-6.2.0-23-generic 6.2.0-23.23 amd64Linux kernel nvidia modules for version 6.2.0-23 rc linux-modules-nvidia-525-6.2.0-24-generic 6.2.0-24.24 amd64Linux kernel nvidia modules for version 6.2.0-24 ii linux-objects-nvidia-525-6.2.0-1005-oracle 6.2.0-1005.5+3 amd64Linux kernel nvidia modules for version 6.2.0-1005 (objects) ii linux-objects-nvidia-525-6.2.0-1007-lowlatency 6.2.0-1007.7+3 amd64Linux kernel nvidia modules for version 6.2.0-1007 (objects) rc linux-objects-nvidia-525-6.2.0-20-generic 6.2.0-20.20+2 amd64Linux kernel nvidia modules for version 6.2.0-20 (objects) rc linux-objects-nvidia-525-6.2.0-23-generic 6.2.0-23.23 amd64Linux kernel nvidia modules for version 6.2.0-23 (objects) rc linux-objects-nvidia-525-6.2.0-24-generic 6.2.0-24.24 amd64Linux kernel nvidia modules for version 6.2.0-24 (objects) ii linux-signatures-nvidia-6.2.0-1005-oracle 6.2.0-1005.5+3 amd64Linux kernel signatures for nvidia modules for version 6.2.0-1005-oracle ii linux-signatures-nvidia-6.2.0-1007-lowlatency 6.2.0-1007.7+3 amd64Linux kernel signatures for nvidia modules for version 6.2.0-1007-lowlatency rc nvidia-compute-utils-525 525.116.04-0ubuntu0.23.04.1 amd64NVIDIA compute utilities ii nvidia-compute-utils-535 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA compute utilities ii nvidia-dkms-535535.54.03-0ubuntu0.23.04.2 amd64NVIDIA DKMS package ii nvidia-driver-535 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA driver metapackage ii nvidia-firmware-535-535.54.03 535.54.03-0ubuntu0.23.04.2 amd64Firmware files used by the kernel module rc nvidia-kernel-common-525
[Desktop-packages] [Bug 2024135] Re: Default right click method on touchpads should be with two fingers
Seb, would it be OK with you to remove the Ubuntu setting override? https://launchpad.net/ubuntu/+source/ubuntu-settings/18.10.8 -- 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/2024135 Title: Default right click method on touchpads should be with two fingers Status in gnome-control-center: Fix Released Status in ubuntu-settings package in Ubuntu: New Bug description: The default right click method on touchpads should be with two fingers so you can right click without having to look at the touchpad. Modern laptops have supported this for a decade, modern OSes like macOS and ChromeOS default to it, and upstream GNOME has defaulted to it since version 3.28 in 2018. This issue was fixed at the start of 2018 in bug 1699033, but then reverted again in: https://launchpad.net/ubuntu/+source/ubuntu- settings/18.10.8 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2024135/+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 1982483]
options snd-hda-intel model=alc295-hp-x360 didn't help either. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1982483 Title: No sound from built-in speakers HP Pavilion All-in-One Desktop 27-ca1xxx (ALC274) Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: I have tried: options snd-hda-intel model=alc285-hp-amp-init options snd-hda-intel model=alc274-dell-aio and newer kernels up to 5.19-rc6. 21: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.2CriaNVEdN5 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Device Name: "Onboard - Sound" Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x7ad0 SubVendor: pci 0x103c "Hewlett-Packard Company" SubDevice: pci 0x89e9 Revision: 0x11 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x6105238000-0x610523bfff (rw,non-prefetchable) Memory Range: 0x610500-0x61050f (rw,non-prefetchable) IRQ: 161 (1098 events) Module Alias: "pci:v8086d7AD0sv103Csd89E9bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_sof_pci_intel_tgl is active Driver Activation Cmd: "modprobe snd_sof_pci_intel_tgl" Config Status: cfg=new, avail=yes, need=no, active=unknown <6>[3.582352] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC274: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker <6>[3.582359] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) <6>[3.582362] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) <6>[3.582364] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 <6>[3.582366] snd_hda_codec_realtek hdaudioC0D0:inputs: <6>[3.582367] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 <6>[3.582369] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 Alsa-info: https://alsa- project.org/db/?f=ed6190cfc9d9eb1c758c6c3106dd236b150f5b31 Here is a kernel bug report: https://bugzilla.kernel.org/show_bug.cgi?id=216139 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ernst 1560 F pulseaudio /dev/snd/controlC0: ernst 1560 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (143 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP Pavilion All-in-One Desktop 27-ca1xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1006-oem root=UUID=72ea78e1-7744-4fcc-b63c-3aa577c86a80 ro quiet splash ibt=off mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1006.6-oem 6.0.0 RelatedPackageVersions: linux-restricted-modules-6.0.0-1006-oem N/A linux-backports-modules-6.0.0-1006-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy wayland-session Uname: Linux 6.0.0-1006-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/09/2022 dmi.bios.release: 15.2 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.name: 89E9 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnAMI:bvrF.02:bd02/09/2022:br15.2:efr1.16:svnHP:pnHPPavilionAll-in-OneDesktop27-ca1xxx:pvr:rvnHP:rn89E9:rvr0100:cvnHP:ct13:cvr:sku661Q7EA#UUW: dmi.product.family: 103C_53311M HP Pavilion dmi.product.name: HP Pavilion All-in-One Desktop 27-ca1xxx dmi.product.sku: 661Q7EA#UUW dmi.sys.vendor: HP modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-06-15T22:28:44.879144 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1982483/+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
