[Desktop-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
** Attachment added: "lunar without fonts-droid-fallback" https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+attachment/5683311/+files/Screenshot%20from%202023-07-02%2013-33-22.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/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 2017076] Re: default Chinese font in snap apps is ugly
@Gunnar Thanks for the advice. I removed fonts-droid-fallback and tried it, and now Japanese glyphs are displayed. However, I am concerned that it only affects the snap package, while the non-snap package seems to select the correct glyphs. I will first check if this also happens in Mantic and then report the problem to language-selector. -- 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 2017426] Re: Can't connect with RDP from/to LTS22.04
[Expired for gnome-remote-desktop (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-remote-desktop (Ubuntu) Status: Incomplete => Expired -- 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/2017426 Title: Can't connect with RDP from/to LTS22.04 Status in gnome-remote-desktop package in Ubuntu: Expired Bug description: I use on both side the default apps and desktop environment: gnome-control-center, remmina & wayland. I tried with all three possible server side session locked/unlocked/closed. lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 apt-cache policy gnome-remote-desktop gnome-remote-desktop: Installé : 42.7-0ubuntu1 Candidat : 42.7-0ubuntu1 Table de version : *** 42.7-0ubuntu1 500 (phased 0%) 500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-4ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages I tried also with ssh tunnel disabled (and port 3389 opened for remote access) Chain INPUT (policy DROP 4 packets, 240 bytes) pkts bytes target prot opt in out source destination 140 15693 ACCEPT tcp -- * * 192.168.22.290.0.0.0/0 tcp dpt:3389 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2014-07-26 (3201 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: gnome-remote-desktop 42.7-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-71.78-generic 5.15.92 Tags: jammy Uname: Linux 5.15.0-71-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-04-07 (23 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2017426/+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 2018160] Re: gnome-shell crashes when top right panel touched on touchscreen
[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/2018160 Title: gnome-shell crashes when top right panel touched on touchscreen Status in gnome-shell package in Ubuntu: Expired Bug description: Version: ubuntu 23.04 Package: gnome-shell: Installed: 44.0-2ubuntu3 Candidate: 44.0-2ubuntu3 Version table: *** 44.0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status What I expected: I expected the wifi/bluetooth/dark... menu (in the upper right hand corner) to popup when I touched it on my touchscreen (clicking with a mouse or touchpad works fine, touchscreen press does not). This works as intended on Ubuntu 22.04.2 LTS. What happened: The menu popped up as intended, but 2 seconds later it disappeared, along with the top gnome shell panel (presumably it crashed). A few seconds later the gnome panel restores but without the menu. Running applications (such as firefox) don't seem to be affected. Running on an Asus Vivobook 14 (touchscreen). Tried using both safe mode and proprietary graphic mode with same result. Earlier versions of gnome seem to work fine. Same problem happens in Fedora too. Willing to do additional testing. Really wanna get this working. Thanks ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.480 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 18:06:49 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:13d2] LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP470EA_TP470EA ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset layerfs-path=minimal.standard.live.squashfs --- quiet splash SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: TP470EA.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP470EA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrTP470EA.311:bd07/22/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP470EA_TP470EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP470EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: VivoBook Flip dmi.product.name: VivoBook_ASUSLaptop TP470EA_TP470EA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018160/+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
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 Google chrome is a Google product, and not a Ubuntu package. Bug reports on google products are not managed on Launchpad (a Ubuntu bug tracker). Refer https://support.google.com/chrome/answer/95315 FYI: This bug report can be converted into a question, which is geared at support. ** 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/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 1748895] Re: LO unable to find a working email configuration
** Changed in: df-libreoffice Status: New => Confirmed -- 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/1748895 Title: LO unable to find a working email configuration Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Installed from PPA: ppa:libreoffice/ppa $ lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial $ apt-cache policy libreoffice libreoffice: Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Version table: *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 1:5.1.6~rc2-0ubuntu1~xenial2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 1:5.1.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages WHAT YOU EXPECT TO HAPPEN: Should spawn an new Evolution eMAIL with attached ODF document WHAT HAPPENED INSTEAD: Error Dialogue: LibreOffice is unable to find a working email configuration. Please save your document locally and attached from within your eMAIL client. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1748895/+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 1803604] Re: [upstream] "Send -> Document as e-mail" in Writer / Calc does not work
** Changed in: df-libreoffice Status: New => Confirmed -- 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/1803604 Title: [upstream] "Send -> Document as e-mail" in Writer / Calc does not work Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Description: Linux Mint 18.3 Sylvia Release: 18.3 LO: Version: 6.1.3.2 Build-ID: 1:6.1.3~rc2-0ubuntu0.16.04.1 In writer I have an open document. If I then want to send it: "File - send - document as e-mail" **Nothing happens** Same with send e-mail as open-document and word document. Only send with pdf opens at least the pdf dialogue. But then nothing happens. Path to thunderbird: /usr/bin/thunderbird Thunderbird opens if I use this path so the path seems correct. No error message received. Expect: Mail is opened and document attached. (which worked before) Update: Just checked in Ubuntu 18.04 and LO 6.06.2 There it works as expected. Will check my other system again. Maybe it just does not work on my other system. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803604/+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 1748895]
*** Bug 154479 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/1748895 Title: LO unable to find a working email configuration Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Installed from PPA: ppa:libreoffice/ppa $ lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial $ apt-cache policy libreoffice libreoffice: Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Version table: *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 1:5.1.6~rc2-0ubuntu1~xenial2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 1:5.1.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages WHAT YOU EXPECT TO HAPPEN: Should spawn an new Evolution eMAIL with attached ODF document WHAT HAPPENED INSTEAD: Error Dialogue: LibreOffice is unable to find a working email configuration. Please save your document locally and attached from within your eMAIL client. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1748895/+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 1803604]
Clearly issues to solve, including in link to Thunderbird as in duplicate but 154479. Thanks Bernard for continuously looking into it, and please don't hesitate submitting a patch on gerrit if you think it can improve the situation. -- 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/1803604 Title: [upstream] "Send -> Document as e-mail" in Writer / Calc does not work Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Description: Linux Mint 18.3 Sylvia Release: 18.3 LO: Version: 6.1.3.2 Build-ID: 1:6.1.3~rc2-0ubuntu0.16.04.1 In writer I have an open document. If I then want to send it: "File - send - document as e-mail" **Nothing happens** Same with send e-mail as open-document and word document. Only send with pdf opens at least the pdf dialogue. But then nothing happens. Path to thunderbird: /usr/bin/thunderbird Thunderbird opens if I use this path so the path seems correct. No error message received. Expect: Mail is opened and document attached. (which worked before) Update: Just checked in Ubuntu 18.04 and LO 6.06.2 There it works as expected. Will check my other system again. Maybe it just does not work on my other system. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803604/+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 1748895]
Clearly issues to solve, including in link to Thunderbird as in duplicate but 154479. Thanks Bernard for continuously looking into it, and please don't hesitate submitting a patch on gerrit if you think it can improve the situation. -- 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/1748895 Title: LO unable to find a working email configuration Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Installed from PPA: ppa:libreoffice/ppa $ lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial $ apt-cache policy libreoffice libreoffice: Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Version table: *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 1:5.1.6~rc2-0ubuntu1~xenial2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 1:5.1.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages WHAT YOU EXPECT TO HAPPEN: Should spawn an new Evolution eMAIL with attached ODF document WHAT HAPPENED INSTEAD: Error Dialogue: LibreOffice is unable to find a working email configuration. Please save your document locally and attached from within your eMAIL client. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1748895/+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 1803604]
*** Bug 154479 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/1803604 Title: [upstream] "Send -> Document as e-mail" in Writer / Calc does not work Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Description: Linux Mint 18.3 Sylvia Release: 18.3 LO: Version: 6.1.3.2 Build-ID: 1:6.1.3~rc2-0ubuntu0.16.04.1 In writer I have an open document. If I then want to send it: "File - send - document as e-mail" **Nothing happens** Same with send e-mail as open-document and word document. Only send with pdf opens at least the pdf dialogue. But then nothing happens. Path to thunderbird: /usr/bin/thunderbird Thunderbird opens if I use this path so the path seems correct. No error message received. Expect: Mail is opened and document attached. (which worked before) Update: Just checked in Ubuntu 18.04 and LO 6.06.2 There it works as expected. Will check my other system again. Maybe it just does not work on my other system. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803604/+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 2020049] Re: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finis
This bug was fixed in the package mutter - 44.2-3ubuntu1 --- mutter (44.2-3ubuntu1) mantic; urgency=medium * Merge with Debian. Remaining changes: - Add x11-Add-support-for-fractional-scaling-using-Randr.patch - Add window-Add-ability-to-override-the-edge-constraints.patch + Make possible for extensions (such as Tiling Assistant) to override window constraints mutter (44.2-3) experimental; urgency=medium * Cherry-pick patch to fix build test with mesa 23.1 (LP: #2025287) mutter (44.2-2ubuntu1) mantic; urgency=medium * Merge with Debian. Remaining changes: - Add x11-Add-support-for-fractional-scaling-using-Randr.patch - Add window-Add-ability-to-override-the-edge-constraints.patch + Make possible for extensions (such as Tiling Assistant) to override window constraints mutter (44.2-2) experimental; urgency=medium [ Daniel van Vugt ] * Cherry-pick 2 patches for stuttering fixes * Avoid cursor stuttering over some windows (LP: #2023766). This will also improve best-case input latency by roughly half a frame. * Avoid render stuttering in some fullscreen games (LP: #2016990). * Update Support-Dynamic-triple-double-buffering.patch * Fix a failure to resume from sleep (frozen black screen), which seems to be an old bug but only became likely in 44.1. * Fix a crash on resume from sleep (LP: #2020049). -- Jeremy Bícha Wed, 28 Jun 2023 15:31:07 -0400 ** Changed in: mutter (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020049 Title: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finish_frame() from try_post_latest_swap() Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Triaged Status in mutter source package in Mantic: Fix Released Bug description: 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/c675f1d61cef940571272d7e655162f1b1cddab1 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020049/+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 2016990] Re: Irregular frame rate in some fullscreen games
This bug was fixed in the package mutter - 44.2-3ubuntu1 --- mutter (44.2-3ubuntu1) mantic; urgency=medium * Merge with Debian. Remaining changes: - Add x11-Add-support-for-fractional-scaling-using-Randr.patch - Add window-Add-ability-to-override-the-edge-constraints.patch + Make possible for extensions (such as Tiling Assistant) to override window constraints mutter (44.2-3) experimental; urgency=medium * Cherry-pick patch to fix build test with mesa 23.1 (LP: #2025287) mutter (44.2-2ubuntu1) mantic; urgency=medium * Merge with Debian. Remaining changes: - Add x11-Add-support-for-fractional-scaling-using-Randr.patch - Add window-Add-ability-to-override-the-edge-constraints.patch + Make possible for extensions (such as Tiling Assistant) to override window constraints mutter (44.2-2) experimental; urgency=medium [ Daniel van Vugt ] * Cherry-pick 2 patches for stuttering fixes * Avoid cursor stuttering over some windows (LP: #2023766). This will also improve best-case input latency by roughly half a frame. * Avoid render stuttering in some fullscreen games (LP: #2016990). * Update Support-Dynamic-triple-double-buffering.patch * Fix a failure to resume from sleep (frozen black screen), which seems to be an old bug but only became likely in 44.1. * Fix a crash on resume from sleep (LP: #2020049). -- Jeremy Bícha Wed, 28 Jun 2023 15:31:07 -0400 ** Changed in: mutter (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2016990 Title: Irregular frame rate in some fullscreen games Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Won't Fix Status in mutter source package in Lunar: Triaged Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] I'm having a strange issue with the game Path of Exile (free). With Ubuntu Wayland session, vsync on, I get very irregular frame rates, it jumps around 40 fps. If I switch to Plasma Wayland the game is very smooth 60 fps. I'm running the game from Steam with Proton. I've tried Proton Experimental and Proton 8.0 so far, no difference. The game uses Vulkan so I guess it's being allowed to set up all the swap and presentation stuff pretty much itself... ? MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1 doesn't help Mutter so it's not strictly related to triple buffering, which makes sense since it's a full screen game anyway. [ Test Plan ] None known, other than the OP to run the game. [ Where problems could occur ] In rendering performance of fullscreen apps/games. [ Workaround ] Add this to /etc/environment: CLUTTER_PAINT=disable-dynamic-max-render-time [ Other Info ] Kernel: 6.2.0-1003-lowlatency GPU: Radeon 6800 XT CPU: Ryzen 9 5900X To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2016990/+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 but only over GUI elements that are animated
This bug was fixed in the package mutter - 44.2-3ubuntu1 --- mutter (44.2-3ubuntu1) mantic; urgency=medium * Merge with Debian. Remaining changes: - Add x11-Add-support-for-fractional-scaling-using-Randr.patch - Add window-Add-ability-to-override-the-edge-constraints.patch + Make possible for extensions (such as Tiling Assistant) to override window constraints mutter (44.2-3) experimental; urgency=medium * Cherry-pick patch to fix build test with mesa 23.1 (LP: #2025287) mutter (44.2-2ubuntu1) mantic; urgency=medium * Merge with Debian. Remaining changes: - Add x11-Add-support-for-fractional-scaling-using-Randr.patch - Add window-Add-ability-to-override-the-edge-constraints.patch + Make possible for extensions (such as Tiling Assistant) to override window constraints mutter (44.2-2) experimental; urgency=medium [ Daniel van Vugt ] * Cherry-pick 2 patches for stuttering fixes * Avoid cursor stuttering over some windows (LP: #2023766). This will also improve best-case input latency by roughly half a frame. * Avoid render stuttering in some fullscreen games (LP: #2016990). * Update Support-Dynamic-triple-double-buffering.patch * Fix a failure to resume from sleep (frozen black screen), which seems to be an old bug but only became likely in 44.1. * Fix a crash on resume from sleep (LP: #2020049). -- Jeremy Bícha Wed, 28 Jun 2023 15:31:07 -0400 ** Changed in: mutter (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2023766 Title: Mouse cursor stutters but only 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 but only over GUI elements that are animated. [ 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 2025287] Re: mutter cogl-test-framebuffer-get-bits-gl3 failure
This bug was fixed in the package mutter - 44.2-3ubuntu1 --- mutter (44.2-3ubuntu1) mantic; urgency=medium * Merge with Debian. Remaining changes: - Add x11-Add-support-for-fractional-scaling-using-Randr.patch - Add window-Add-ability-to-override-the-edge-constraints.patch + Make possible for extensions (such as Tiling Assistant) to override window constraints mutter (44.2-3) experimental; urgency=medium * Cherry-pick patch to fix build test with mesa 23.1 (LP: #2025287) mutter (44.2-2ubuntu1) mantic; urgency=medium * Merge with Debian. Remaining changes: - Add x11-Add-support-for-fractional-scaling-using-Randr.patch - Add window-Add-ability-to-override-the-edge-constraints.patch + Make possible for extensions (such as Tiling Assistant) to override window constraints mutter (44.2-2) experimental; urgency=medium [ Daniel van Vugt ] * Cherry-pick 2 patches for stuttering fixes * Avoid cursor stuttering over some windows (LP: #2023766). This will also improve best-case input latency by roughly half a frame. * Avoid render stuttering in some fullscreen games (LP: #2016990). * Update Support-Dynamic-triple-double-buffering.patch * Fix a failure to resume from sleep (frozen black screen), which seems to be an old bug but only became likely in 44.1. * Fix a crash on resume from sleep (LP: #2020049). -- Jeremy Bícha Wed, 28 Jun 2023 15:31:07 -0400 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2025287 Title: mutter cogl-test-framebuffer-get-bits-gl3 failure Status in mutter package in Ubuntu: Fix Released Bug description: mutter has one failing build test in Mantic. Debian Experimental has the same build test failure but Ubuntu 23.04 (Lunar) does not. This is reproducible with mutter 44.2-1 from earlier in June so this appears to be triggered by a change in one of the dependencies. https://launchpad.net/ubuntu/+source/mutter/44.2-2ubuntu1 Build log excerpt = 67/179 mutter:cogl+cogl/conform / cogl-test-framebuffer-get-bits-gl3 RUNNING >>> LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/cogl/cogl:/<>/obj-x86_64-linux-gnu/src:/<>/obj-x86_64-linux-gnu/cogl/cogl-pango:/<>/obj-x86_64-linux-gnu/src/tests:/<>/obj-x86_64-linux-gnu/clutter/clutter G_ENABLE_DIAGNOSTIC=0 G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/src/tests/cogl/conform G_TEST_SRCDIR=/<>/src/tests/cogl/conform COGL_DRIVER=gl3 MALLOC_PERTURB_=209 MUTTER_TEST_PLUGIN_PATH=/<>/obj-x86_64-linux-gnu/src/compositor/plugins/libdefault.so /<>/src/tests/meta-dbus-runner.py -- /<>/obj-x86_64-linux-gnu/src/tests/cogl/conform/cogl-test-framebuffer-get-bits ― ✀ ― Starting D-Bus daemons (session & system)... Launching required services... Starting mocked services... Running test case... TAP version 13 # random seed: R02Scf195b999d71877c99f7f10a5670c4cb # GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation memory (GMemorySettingsBackend) for ‘gsettings-backend’ # libmutter-MESSAGE: Running Mutter Test (using mutter 44.2) as a Wayland display server # libmutter-MESSAGE: Created surfaceless renderer without GPU # GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’ # libmutter-MESSAGE: Disabling DMA buffer screen sharing (not hardware accelerated) # libmutter-MESSAGE: Disabling DMA buffer screen sharing (implicit modifiers not supported) # libmutter-DEBUG: WL: loaded libnvidia-egl-wayland.so.1:wl_eglstream_controller. # libmutter-MESSAGE: Using Wayland display name 'mutter-test-display' Window manager warning: Failed to set environment variable WAYLAND_DISPLAY for gnome-session: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.SessionManager" does not exist 1..1 # Start of framebuffer tests ** ERROR:../src/tests/cogl/conform/test-framebuffer-get-bits.c:39:test_framebuffer_get_bits: assertion failed (cogl_framebuffer_get_alpha_bits (fb_a) >= 1): (0 >= 1) not ok /framebuffer/get-bits - ERROR:../src/tests/cogl/conform/test-framebuffer-get-bits.c:39:test_framebuffer_get_bits: assertion failed (cogl_framebuffer_get_alpha_bits (fb_a) >= 1): (0 >= 1) Bail out! ―― 67/179 mutter:cogl+cogl/conform / cogl-test-framebuffer-get-bits-gl3 FAIL 1.09s (exit status 250 or signal 122 SIGinvalid) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2025287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
@Mitsuya Shibata: Well, yes it *affects* Japanese fonts too, but it makes no sense that *this change* would increase the risk of picking Chinese glyphs under a Japanese locale. OTOH, if I start Firefox with: env LC_CTYPE=ja_JP.UTF-8 firefox the default sans-serif font for me according to FF Settings is Droid Sans Fallback!! That might have something to do with it. I see now that the fonts-droid-fallback package is shipped on the ISO (did we simply forget to drop it?). So as a test, can you please uninstall that package: sudo apt purge fonts-droid-fallback and let us know if it makes a difference. In any case I think there is a need to reconsider the default font configuation for Japanese. The /usr/share/fontconfig/conf.avail/70-fonts-noto-cjk.conf file includes: ja sans-serif Noto Sans CJK JP while the Chinese equivalents have: So, Mitsuya Shibata, it would be great if you could submit a new bug where we can focus on the Japanese font configuration. The reconsideration would probably affect multiple packages, but language- selector may be a proper affected package to start with. -- 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 2025537] Re: chrome Check failed
Were you using the generic kernel stack ? If yes, check your kernel release number (uname -r) to confirm it’s still the generic kernel (should end with “-generic”). If your kernel stack suddenly changed, you’re not alone. People have reported the updates going fancy and installing unwanted kernel stacks. I hope this won’t get unnoticed by Canonical for too long, as it could have severe availability consequences for some people. -- 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: New 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)
Same issue here as well, after an update yesterday. Running it with --no-sandbox works, but not ideal. Every other fix I've tried so far doesn't seem to work... -- 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 chromium-browser package in Ubuntu: Confirmed 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/chromium-browser/+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 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
Chrome bug report: https://bugs.chromium.org/p/chromium/issues/detail?id=1459821 -- 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 chromium-browser package in Ubuntu: Confirmed 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/chromium-browser/+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 2024887] Re: Bad image quality when saving JPEG or PDF scans
I have just discovered a few good PDF image documents scanned with simple-scan 42.00 on January 22. So the regression was not introduced by the upgrade from 20.04LTS to 22.04LTS, but after that. I will have a deeper look at the changes in /var/log/dpkg.log.* later... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/2024887 Title: Bad image quality when saving JPEG or PDF scans Status in simple-scan package in Ubuntu: New Bug description: Description: Ubuntu 22.04.2 LTS Release: 22.04 simple-scan: Installed: 42.0-1 Candidate: 42.0-1 Version table: *** 42.0-1 500 500 http://be.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When saving a document scanned using "Image" settings to JPEG or PDF format, the resulting quality is really bad. The image shown in the scan window looks fine, so this is not a scanner issue. When saving to (lossless) PNG, the quality is also fine. This is also reflected in the file sizes, e.g. for a 600 dpi scan of a 19x13 cm photo: - PNG: 12575069 bytes (OK) - JPEG: 227595 bytes (BAD) - PDF: 229414 bytes (BAD) It looks like the compression rate for (embedded) JPEG files is way too large. When scanning using "Text" settings, the resulting quality is fine (I rescanned an old document and compared the results). The difference with a scan using the "Image" settings is very clear, even for text documents. Version 3.36.3-0ubuntu0.20.04.0 did not have this problem. I downloaded and installed 42.5-1 from kinetic, but that did not fix the issue. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/2024887/+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)
Related (but not duplicate) is bug https://bugs.launchpad.net/ubuntu/+source/linux-signed- nvidia-5.19/+bug/2025538 -- 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 chromium-browser package in Ubuntu: Confirmed 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/chromium-browser/+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 1676810] Re: Network Manager needs restarting from sleep
Noticing the same on Ubuntu 22.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1676810 Title: Network Manager needs restarting from sleep Status in network-manager package in Ubuntu: Confirmed Bug description: Each time my laptop is suspended and resumed, Network Manager seems unable to bring up Wifi. Calling... sudo service network-manager restart ...resolves the problem. I therefore placed the attached file at... /lib/systemd/system-sleep/network-manager ...which provides a workaround for the problem. However, there must be some kind of underlying bug in network-manager which requires it to be restarted after every suspend/resume cycle. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: LXDE Date: Tue Mar 28 10:21:35 2017 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp1s0 proto static metric 600 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.203 metric 600 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/1 docker0 ac7e4d66-b979-41de-b4b2-6f7c5dffc232 /org/freedesktop/NetworkManager/ActiveConnection/0 wlp1s0 wifi connected /org/freedesktop/NetworkManager/Devices/0 Kitchen 2 937ae07a-fb47-46ac-91a4-0fe200203a95 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676810/+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] [NEW] chrome Check failed
Public bug reported: 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... ** Affects: chromium-browser (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/2025537 Title: chrome Check failed Status in chromium-browser package in Ubuntu: New 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 2025527] Re: nautilus segfault
upgraded ubuntu to 23.04 . got a lot more bugs but this one seems fixed. -- 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: New 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 2024887] Re: Bad image quality when saving JPEG or PDF scans
"journalctl -f" does show some messages, but there is not really any difference depending on the selected file format. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/2024887 Title: Bad image quality when saving JPEG or PDF scans Status in simple-scan package in Ubuntu: New Bug description: Description: Ubuntu 22.04.2 LTS Release: 22.04 simple-scan: Installed: 42.0-1 Candidate: 42.0-1 Version table: *** 42.0-1 500 500 http://be.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When saving a document scanned using "Image" settings to JPEG or PDF format, the resulting quality is really bad. The image shown in the scan window looks fine, so this is not a scanner issue. When saving to (lossless) PNG, the quality is also fine. This is also reflected in the file sizes, e.g. for a 600 dpi scan of a 19x13 cm photo: - PNG: 12575069 bytes (OK) - JPEG: 227595 bytes (BAD) - PDF: 229414 bytes (BAD) It looks like the compression rate for (embedded) JPEG files is way too large. When scanning using "Text" settings, the resulting quality is fine (I rescanned an old document and compared the results). The difference with a scan using the "Image" settings is very clear, even for text documents. Version 3.36.3-0ubuntu0.20.04.0 did not have this problem. I downloaded and installed 42.5-1 from kinetic, but that did not fix the issue. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/2024887/+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 2024887] Re: Bad image quality when saving JPEG or PDF scans
** Attachment added: "Bad JPEG document" https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/2024887/+attachment/5683264/+files/Scanned%20Document.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/2024887 Title: Bad image quality when saving JPEG or PDF scans Status in simple-scan package in Ubuntu: New Bug description: Description: Ubuntu 22.04.2 LTS Release: 22.04 simple-scan: Installed: 42.0-1 Candidate: 42.0-1 Version table: *** 42.0-1 500 500 http://be.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When saving a document scanned using "Image" settings to JPEG or PDF format, the resulting quality is really bad. The image shown in the scan window looks fine, so this is not a scanner issue. When saving to (lossless) PNG, the quality is also fine. This is also reflected in the file sizes, e.g. for a 600 dpi scan of a 19x13 cm photo: - PNG: 12575069 bytes (OK) - JPEG: 227595 bytes (BAD) - PDF: 229414 bytes (BAD) It looks like the compression rate for (embedded) JPEG files is way too large. When scanning using "Text" settings, the resulting quality is fine (I rescanned an old document and compared the results). The difference with a scan using the "Image" settings is very clear, even for text documents. Version 3.36.3-0ubuntu0.20.04.0 did not have this problem. I downloaded and installed 42.5-1 from kinetic, but that did not fix the issue. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/2024887/+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 2024887] Re: Bad image quality when saving JPEG or PDF scans
** Attachment added: "Good PNG document" https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/2024887/+attachment/5683265/+files/Scanned%20Document.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/2024887 Title: Bad image quality when saving JPEG or PDF scans Status in simple-scan package in Ubuntu: New Bug description: Description: Ubuntu 22.04.2 LTS Release: 22.04 simple-scan: Installed: 42.0-1 Candidate: 42.0-1 Version table: *** 42.0-1 500 500 http://be.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When saving a document scanned using "Image" settings to JPEG or PDF format, the resulting quality is really bad. The image shown in the scan window looks fine, so this is not a scanner issue. When saving to (lossless) PNG, the quality is also fine. This is also reflected in the file sizes, e.g. for a 600 dpi scan of a 19x13 cm photo: - PNG: 12575069 bytes (OK) - JPEG: 227595 bytes (BAD) - PDF: 229414 bytes (BAD) It looks like the compression rate for (embedded) JPEG files is way too large. When scanning using "Text" settings, the resulting quality is fine (I rescanned an old document and compared the results). The difference with a scan using the "Image" settings is very clear, even for text documents. Version 3.36.3-0ubuntu0.20.04.0 did not have this problem. I downloaded and installed 42.5-1 from kinetic, but that did not fix the issue. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/2024887/+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 2024887] Re: Bad image quality when saving JPEG or PDF scans
** Attachment added: "Bad PDF document" https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/2024887/+attachment/5683263/+files/Scanned%20Document.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/2024887 Title: Bad image quality when saving JPEG or PDF scans Status in simple-scan package in Ubuntu: New Bug description: Description: Ubuntu 22.04.2 LTS Release: 22.04 simple-scan: Installed: 42.0-1 Candidate: 42.0-1 Version table: *** 42.0-1 500 500 http://be.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When saving a document scanned using "Image" settings to JPEG or PDF format, the resulting quality is really bad. The image shown in the scan window looks fine, so this is not a scanner issue. When saving to (lossless) PNG, the quality is also fine. This is also reflected in the file sizes, e.g. for a 600 dpi scan of a 19x13 cm photo: - PNG: 12575069 bytes (OK) - JPEG: 227595 bytes (BAD) - PDF: 229414 bytes (BAD) It looks like the compression rate for (embedded) JPEG files is way too large. When scanning using "Text" settings, the resulting quality is fine (I rescanned an old document and compared the results). The difference with a scan using the "Image" settings is very clear, even for text documents. Version 3.36.3-0ubuntu0.20.04.0 did not have this problem. I downloaded and installed 42.5-1 from kinetic, but that did not fix the issue. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/2024887/+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 1995781] Re: Excessive libinput pointer motion even idle
Section "InputClass" Identifier "devops" MatchDevicePath "/dev/nvram" MatchDriver "usbhid" EndSection Section "InputClass" Identifier "libinput" Driver "libinput" EndSectio Thats my class No pointer motion fuzzy :/ Thx -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1995781 Title: Excessive libinput pointer motion even idle Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: Hi, I have a notebook avell c65 mob model and a razer mouse model abyssus essential. What is happening: I installed the package libinput-tools and ran the command; $ sudo libinput debug-events After that i see lots of pointer motion event "logs" even with the mouse idle and gnome-settings acceleration medium/low configs. Tested workaround: Edit file file /usr/share/X11/xorg.conf.d/40-libinput.conf , like this: Section "InputClass" Identifier "libinput pointer catchall" MatchIsPointer "on" MatchDevicePath "/dev/input/event*" NoMatchDriver "libinput" # maybe this line optional Driver "stdin" EndSection Now if i set in gnome-control-center, menu mouse, mouse speed/acceleration at full speed; and run again: $ sudo libinput debug-events ; with mouse pointer idle i got no pointer motion ;) Thank you! Luiz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1995781/+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
** Attachment added: "jammy glyph" https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+attachment/5683253/+files/Screenshot%20from%202023-07-01%2021-52-33.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/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 2017076] Re: default Chinese font in snap apps is ugly
Hi all, Does this fix affect Japanese fonts? I installed Ubuntu 23.04 today and encountered a problem where the Japanese in the snap package is incorrectly displayed with Chinese font glyphs. Specifically, the problem occurs in Firefox and Snap Store, but not in gnome-terminal or Text Editor. I have attached a screenshot that shows the difference between Ubuntu 22.04 LTS and Ubuntu 23.04. The letters circled in red should originally look the same in 22.04 and 23.04. ** Attachment added: "lunar glyph" https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+attachment/5683252/+files/Screenshot%20from%202023-07-01%2021-51-17.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/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 1987928] Re: gnome-control-center closes with Gtk Gio Error when trying to access keyboard shortcut details
** Changed in: gnome-control-center (Ubuntu) Status: Expired => New -- 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/1987928 Title: gnome-control-center closes with Gtk Gio Error when trying to access keyboard shortcut details Status in gnome-control-center package in Ubuntu: New Bug description: Hello, I report this issue on behalf of someone else, I can't use the bug reporter on the Ubuntu machine. The same issue has been reported by other people on other places: Bug report for GNOME: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1728 Bug report for Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008493 --- lsb_release -rd --- Description: Ubuntu 22.04.1 LTS Release: 22.04 --- end lsb_release -rd --- --- apt-cache policy gnome-control-center --- gnome-control-center: Installé : 1:41.7-0ubuntu0.22.04.4 Candidat : 1:41.7-0ubuntu0.22.04.4 Table de version : *** 1:41.7-0ubuntu0.22.04.4 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:41.4-1ubuntu13.2 500 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages 1:41.4-1ubuntu12 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages --- end apt-cache policy gnome-control-center --- Issue started after update of gnome-control-center on 24 August 2022 (1:41.7-0ubuntu0.22.04.1 → 1:41.7-0ubuntu0.22.04.4) --- Snippet from /var/log/apt/history.log --- Start-Date: 2022-08-24 16:56:32 Commandline: /usr/sbin/synaptic Requested-By: michel (1003) Upgrade: gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubun tu0.22.04.4), thunderbird:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 1:91.13. 0+build1-0ubuntu0.22.04.1), libpam-fprintd:amd64 (1.94.2-1, 1.94.2-1ubuntu0.22.0 4.1), isc-dhcp-common:amd64 (4.4.1-2.3ubuntu2.1, 4.4.1-2.3ubuntu2.2), thunderbir d-locale-en:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 1:91.13.0+build1-0ubun tu0.22.04.1), thunderbird-locale-fr:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1 , 1:91.13.0+build1-0ubuntu0.22.04.1), isc-dhcp-client:amd64 (4.4.1-2.3ubuntu2.1, 4.4.1-2.3ubuntu2.2), fprintd:amd64 (1.94.2-1, 1.94.2-1ubuntu0.22.04.1), gnome-c ontrol-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.4), gno me-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.4), thun derbird-locale-en-gb:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 1:91.13.0+bui ld1-0ubuntu0.22.04.1), thunderbird-locale-en-us:amd64 (1:91.12.0+build1-0ubuntu0 .22.04.1~mt1, 1:91.13.0+build1-0ubuntu0.22.04.1), thunderbird-gnome-support:amd6 4 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 1:91.13.0+build1-0ubuntu0.22.04.1) End-Date: 2022-08-24 16:57:15 --- end /var/log/apt/history.log --- The user opens gnome-control-center, the main window appears. The user selects the keyboard tab and click on the arrow to open the keyboard shortcut binding interface. The user expects the interface for binding keyboard shortcuts to open. Instead, the main gnome-control-center window closes and outputs the following error in the terminal: --- output of gnome-control-center --- (gnome-control-center: 647357): GLib-GIO-ERROR **: 00:31:19.451: Settings schema 'org.gnome.settin gs-daemon.plugins.media-keys' does not contain a key named 'screenshot' Trappe pour point d'arrêt et de trace (core dumped) --- end output of gnome-control-center --- It was working some time before the update to 1:41.7-0ubuntu0.22.04.4. Downgrading the package to 1:41.4-1ubuntu13.2 doesn't fix the issue. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987928/+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 1987928] Re: gnome-control-center closes with Gtk Gio Error when trying to access keyboard shortcut details
Hello, Issue is still present. Regards. -- 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/1987928 Title: gnome-control-center closes with Gtk Gio Error when trying to access keyboard shortcut details Status in gnome-control-center package in Ubuntu: Expired Bug description: Hello, I report this issue on behalf of someone else, I can't use the bug reporter on the Ubuntu machine. The same issue has been reported by other people on other places: Bug report for GNOME: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1728 Bug report for Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008493 --- lsb_release -rd --- Description: Ubuntu 22.04.1 LTS Release: 22.04 --- end lsb_release -rd --- --- apt-cache policy gnome-control-center --- gnome-control-center: Installé : 1:41.7-0ubuntu0.22.04.4 Candidat : 1:41.7-0ubuntu0.22.04.4 Table de version : *** 1:41.7-0ubuntu0.22.04.4 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:41.4-1ubuntu13.2 500 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages 1:41.4-1ubuntu12 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages --- end apt-cache policy gnome-control-center --- Issue started after update of gnome-control-center on 24 August 2022 (1:41.7-0ubuntu0.22.04.1 → 1:41.7-0ubuntu0.22.04.4) --- Snippet from /var/log/apt/history.log --- Start-Date: 2022-08-24 16:56:32 Commandline: /usr/sbin/synaptic Requested-By: michel (1003) Upgrade: gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubun tu0.22.04.4), thunderbird:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 1:91.13. 0+build1-0ubuntu0.22.04.1), libpam-fprintd:amd64 (1.94.2-1, 1.94.2-1ubuntu0.22.0 4.1), isc-dhcp-common:amd64 (4.4.1-2.3ubuntu2.1, 4.4.1-2.3ubuntu2.2), thunderbir d-locale-en:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 1:91.13.0+build1-0ubun tu0.22.04.1), thunderbird-locale-fr:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1 , 1:91.13.0+build1-0ubuntu0.22.04.1), isc-dhcp-client:amd64 (4.4.1-2.3ubuntu2.1, 4.4.1-2.3ubuntu2.2), fprintd:amd64 (1.94.2-1, 1.94.2-1ubuntu0.22.04.1), gnome-c ontrol-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.4), gno me-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.4), thun derbird-locale-en-gb:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 1:91.13.0+bui ld1-0ubuntu0.22.04.1), thunderbird-locale-en-us:amd64 (1:91.12.0+build1-0ubuntu0 .22.04.1~mt1, 1:91.13.0+build1-0ubuntu0.22.04.1), thunderbird-gnome-support:amd6 4 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 1:91.13.0+build1-0ubuntu0.22.04.1) End-Date: 2022-08-24 16:57:15 --- end /var/log/apt/history.log --- The user opens gnome-control-center, the main window appears. The user selects the keyboard tab and click on the arrow to open the keyboard shortcut binding interface. The user expects the interface for binding keyboard shortcuts to open. Instead, the main gnome-control-center window closes and outputs the following error in the terminal: --- output of gnome-control-center --- (gnome-control-center: 647357): GLib-GIO-ERROR **: 00:31:19.451: Settings schema 'org.gnome.settin gs-daemon.plugins.media-keys' does not contain a key named 'screenshot' Trappe pour point d'arrêt et de trace (core dumped) --- end output of gnome-control-center --- It was working some time before the update to 1:41.7-0ubuntu0.22.04.4. Downgrading the package to 1:41.4-1ubuntu13.2 doesn't fix the issue. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987928/+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)
** Also affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Confirmed ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- 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 chromium-browser package in Ubuntu: Confirmed 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/chromium-browser/+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 2025527] Re: nautilus segfault
seems clone of https://gitlab.gnome.org/GNOME/pango/-/issues/715 -- 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: New 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 2025527] Re: nautilus segfault
looking in /var/log/syslog kernel: [ 1272.348057] nautilus[10457]: segfault at 0 ip 7fcbf4e57ea6 sp 7ffcb4373be0 error 4 in libpango-1.0.so.0.5000.10[7fcbf4e4+37000] kernel: [ 1272.348095] Code: 55 89 f5 53 48 83 ec 70 64 48 8b 04 25 28 00 00 00 48 89 44 24 68 31 c0 49 89 e4 4c 89 e6 e8 a1 b0 00 00 48 8b 5c 24 10 31 c0 <48> 83 3b 00 75 43 e9 df 00 00 00 0f 1f 80 00 00 00 00 4c 89 ea 31 ** Bug watch added: gitlab.gnome.org/GNOME/pango/-/issues #715 https://gitlab.gnome.org/GNOME/pango/-/issues/715 -- 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: New 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 2025527] Re: nautilus segfault
I tried to debug. using > G_DEBUG="all" NAUTILUS_DEBUG="All" nautilus . lead to instant crash Using > NAUTILUS_DEBUG="All" nautilus . nothing of value was visible, same bug Using > G_MESSAGES_DEBUG=all nautilus . >> ~/Desktop/trace_nautilus.log I had a bit more information but nothing related to the crash -- 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: New 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 2025527] Re: nautilus segfault
description : 1. I created a new file named .txt in my templates. Created it with contextual menu okay. This leads to file ".txt" created . 2. I right click this file, rename ; then I press "leftarrow" three times and nautilus crashed. 3. open nautilus in console with "nautilus ." goto 2. got a Segmentation fault (core dumped) -- 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: New 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 2025527] [NEW] nautilus segfault
Public bug reported: 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 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages -- 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: New 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 2025526] [NEW] Printer is not available in chromium snap
Public bug reported: 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 ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: printing -- 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 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 2025523] [NEW] tracker3 taking 100% CPU for a long time
Public bug reported: /usr/libexec/tracker-extract-3 and /usr/libexec/tracker-miner-fs-3 are constantly taking 100% CPU, causing the machine to overheat and the fans to work overtime. This should not happen. What doesn't help: • Ubuntu Settings > Search > turn off search. • Restart the machine. The problem is that on the next boot, tracker3 restarts and again takes 100% of CPU. What does help: • kill -9 for both processes (until the next boot). • Disable tracker3 according to: https://www.linuxuprising.com/2019/07/how-to-completely-disable-tracker.html Description:Ubuntu 22.04.2 LTS Release:22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: tracker-extract 3.3.0-1 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 Date: Sat Jul 1 07:06:47 2023 ExecutablePath: /usr/libexec/tracker-extract-3 InstallationDate: Installed on 2022-08-28 (306 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: tracker-miners UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tracker-miners (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 tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/2025523 Title: tracker3 taking 100% CPU for a long time Status in tracker-miners package in Ubuntu: New Bug description: /usr/libexec/tracker-extract-3 and /usr/libexec/tracker-miner-fs-3 are constantly taking 100% CPU, causing the machine to overheat and the fans to work overtime. This should not happen. What doesn't help: • Ubuntu Settings > Search > turn off search. • Restart the machine. The problem is that on the next boot, tracker3 restarts and again takes 100% of CPU. What does help: • kill -9 for both processes (until the next boot). • Disable tracker3 according to: https://www.linuxuprising.com/2019/07/how-to-completely-disable-tracker.html Description: Ubuntu 22.04.2 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: tracker-extract 3.3.0-1 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 Date: Sat Jul 1 07:06:47 2023 ExecutablePath: /usr/libexec/tracker-extract-3 InstallationDate: Installed on 2022-08-28 (306 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: tracker-miners UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/2025523/+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 1971242] Re: printing PDF appears always grey, no color
Hello dm, or anyone else affected,
Accepted cups into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/cups/2.4.1op1-1ubuntu4.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: cups (Ubuntu Jammy)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Fix Released
Status in okular package in Ubuntu:
Confirmed
Status in cups source package in Jammy:
Fix Committed
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
and start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
editor. Check whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints
about color printing. So the regression potential is very low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+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
