[Desktop-packages] [Bug 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
It looks like the nvidia kernel has been reverted. However, I am still seeing the same error with Slack, and the second monitor is still not working -- 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 2025552] Re: Some of the screen doesnt interact
Is it the top right area of the screen? (bug 2012388) ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2025552 Title: Some of the screen doesnt interact Status in Ubuntu: Incomplete Bug description: I am using browsers and code editors. in some part of the screen i cant click buttons or vscode doesnt detect the typing, etc ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 2 13:32:01 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: rtl8188fu/1.0, 5.19.0-40-generic, x86_64: installed rtl8814au/4.3.21: added GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2022-09-05 (300 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ECS H61H2-M4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=253580b7-029c-45d3-99ea-5e0bd016dda4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-M4 dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/13/2013:br4.6:svnECS:pnH61H2-M4:pvr1.0:rvnECS:rnH61H2-M4:rvr1.0:cvnECS:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H61H2-M4 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: ECS modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-10-23T16:06:36.178537 version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu3 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/+bug/2025552/+subscriptions -- Mailing list: https://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 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Update changelog to document the apt_pkg.DepCache in
_is_runtimepm_supported. Related discussion is at
https://github.com/tseliot/ubuntu-drivers-
common/pull/71/commits/025cce328b9909f3f421376be35cb34511b9ea2e#r884846872
[ Jeremy Szu ]
* README, README.md,
UbuntuDrivers/detect.py,
tests/test_ubuntu_drivers.py:
- Let OEM image can locally extending the NVIDIA driver
supported PCI IDs for cutting edge silicons by specifying
related information in /etc/custom_supported_gpus.json file.
(lp: #1990341)
- Fix pkg.candidate.record retired from apt_pkg library
- Support autopkgtest for force install Nvidia and update
related section in README.
** Patch added: "jammy-0.9.6.2~22.04.4__0.9.6.2~22.04.5_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5683469/+files/jammy-0.9.6.2~22.04.4__0.9.6.2~22.04.5_v2.debdiff
** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Confirmed
Status in ubuntu-drivers-common source package in Lunar:
Fix Released
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions
--
Mailing list: https://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 1082110]
*** Bug 156086 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/1082110 Title: [Upstream] Endnote placed at end of document is unmovable Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.6.2~rc2-0ubuntu4 Candidate: 1:3.6.2~rc2-0ubuntu4 Version table: *** 1:3.6.2~rc2-0ubuntu4 0 900 http://archive.ubuntu.com/ubuntu/ quantal-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.6.2~rc2-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 3) What is expected to happen in Calc is open a blank document -> type example -> click Insert -> Footnote/Endnote... -> under Numbering click radio button Automatic -> under Type click radio button Endnote -> click button OK and an Endnote is inserted one line down from example, which one may click Enter on the keyboard, moving the Endnote one line down, as it does in Microsoft Office Professional Plus 2010 Word Version 14.0.6023.1000 (32-bit). 4) What happens instead is the Endnote is placed all the way at the bottom of the document, and is not movable via clicking Del on the keyboard. WORKAROUND: Use AbiWord. apt-cache policy abiword abiword: Installed: 2.9.2+svn20120603-8 Candidate: 2.9.2+svn20120603-8 Version table: *** 2.9.2+svn20120603-8 0 500 http://archive.ubuntu.com/ubuntu/ quantal/universe i386 Packages 100 /var/lib/dpkg/status Open a blank document -> type example -> click References -> Insert Endnote and an Endnote is inserted one line down from example, which one may click Enter on the keyboard, moving the Endnote one line down. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice-writer 1:3.5.4-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu15 Architecture: i386 Date: Thu Nov 22 09:03:21 2012 InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1082110/+subscriptions -- Mailing list: https://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 2022369] Re: 200% scaling on wayland touchpad feels laggy on X1 Carbon 9th
Fix Released in unknown package :) ** No longer affects: mutter (Ubuntu) ** Package changed: libinput (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/2022369 Title: 200% scaling on wayland touchpad feels laggy on X1 Carbon 9th Status in libinput: Fix Released Status in Ubuntu: Fix Released Bug description: I have an X1 carbon 9th gen with a 4k screen where I use 200% scaling. Unfortunately, the touchpad feels laggy and imprecise when trying to hit click targets. Switching to X11 helps as well as the flat acceleration profile in gnome tweaks. I feel like this is related to how gnome or libinput upscale mouse movement. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 16:57:16 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-15 (18 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/2022369/+subscriptions -- Mailing list: https://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 2025574] Re: ayatana-indicator-messages-service crashed with SIGSEGV in g_closure_invoke()
*** This bug is a duplicate of bug 2025467 *** https://bugs.launchpad.net/bugs/2025467 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2025467, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2025574/+attachment/5683453/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/2025574/+attachment/5683455/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2025574/+attachment/5683458/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2025574/+attachment/5683459/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/2025574/+attachment/5683460/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2025574/+attachment/5683461/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2025574/+attachment/5683462/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 2025467 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ayatana-indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/2025574 Title: ayatana-indicator-messages-service crashed with SIGSEGV in g_closure_invoke() Status in ayatana-indicator-messages package in Ubuntu: New Bug description: happened on launch of software updater ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: ayatana-indicator-messages 22.9.0-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: MATE Date: Fri Jun 30 08:32:20 2023 ExecutablePath: /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service InstallationDate: Installed on 2023-05-07 (56 days ago) InstallationMedia: Ubuntu-MATE 23.10 "Mantic Minotaur" - Daily amd64 (20230507) ProcCmdline: /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f4e5e24e022:mov0x90(%rbp),%rdi PC (0x7f4e5e24e022) ok source "0x90(%rbp)" (0x557d0712ec20) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: ayatana-indicator-messages StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ayatana-indicator-messages-service crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-messages/+bug/2025574/+subscriptions -- Mailing list: https://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)
yes i tried that. but even with the old kernel, the second monitor did not work. but chrome was running. -- 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)
When booting just select an older kernel - and hope that the maintainers are quickly cleaning the mess -- 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)
the same. The second monitor does not work, chrome does not start. what do you advise to do? wait or reinstall the system? -- 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 2025537] Re: chrome Check failed
@slboss222 OK, so this is a confirmed kernel stack change. While this is likely a bug, it’s probably not a Chromium bug, but rater related to the ubuntu-drivers-common package. Can you post the output of “LC_ALL=C apt list --installed 'linux-*'” (without the “”) ? This will help confirm the origin of the bug, as well as determine the steps to solve the problem. The possible cause is the Ubuntu third-party driver logic choosing an Nvidia driver for another kernel stack, which then triggers installation of those kernels, to satisfy dependencies. The solution would be to uninstall those non-generic kernels and associated drivers (provided there’s at least one generic kernel installed) and then rebooting. It’s also possible that the Nvidia driver version is too old, and that may be what triggered the bug. Running “ubuntu-drivers install” should bring it up to date. -- 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 2017076] Re: default Chinese font in snap apps is ugly
I think the reason why fonts-droid-fallback is installed by default is this dependency chain: ubuntu-desktop -> ghostscript-x -> ghostscript -> libgs10 -> libgs10-common -> (recommends) fonts-droid-fallback A fragile workaround might be to somehow stop fonts-droid-fallback from being pulled (change libgs10-common so it Suggests instead of Recommends fonts-droid-fallback). Or maybe we could drop the font configuration file from the fonts-droid-fallback package. OTOH, neither would address the root cause — why do the snaps behave as they do with respect to font configuration? -- 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 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
I'm seeing the same thing running Slack. --- [** ~]$ /bin/slack [64844:0702/180844.731816:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped) --- This started after the latest 'apt update/upgrade' The 2nd monitor connected to the laptop this is running is also no longer working. From previous posts, they appear related -- 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)
-- 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 2017076] Re: default Chinese font in snap apps is ugly
> I am concerned that it only affects the snap package, while > the non-snap package seems to select the correct glyphs. Yes, that's what it looks like. $ lsb_release -c No LSB modules are available. Codename: mantic $ dpkg-query -W fonts-droid-fallback fonts-droid-fallback1:6.0.1r16-1.1build1 $ snap run --shell firefox To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. /home/gunnar$ LC_CTYPE=ja_JP.UTF-8 fc-match sans-serif DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular" /home/gunnar$ exit exit $ LC_CTYPE=ja_JP.UTF-8 fc-match sans-serif NotoSansCJK-Regular.ttc: "Noto Sans CJK JP" "Regular" So the font configuration of the snaps prioritizes differently compared to the font configuration of the system. Reason unclear to me ATM. I also checked in Debian testing, where Firefox is conventionally packaged. Starting FF there with the Japanese locale results in the default sans-serif font "VL Gothic". But that's what's expected from the system font configuration: $ LC_CTYPE=ja_JP.UTF-8 fc-match sans-serif VL-Gothic-Regular.ttf: "VL ゴシック" "regular" (Debian with GNOME has a lot of fonts installed.) -- 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 2024887] Re: Bad image quality when saving JPEG or PDF scans
Further investigation of my backups shows that I never had a "jpeg-quality"
setting in GNOME settings on this machine before
("HOME=/path/to/restored/homedir dconf dump /org/gnome/simple-scan/").
I do have jpeg-quality=75 on the old machine that was connected to the scanner
until 5 years ago...
So it looks like there is a problem with the default value if the "jpeg-
quality" setting does not exist (i.e. has never been changed and
saved?).
src/app-window.vala: quality_adjustment.value = settings.get_int
("jpeg-quality");
However, data/org.gnome.SimpleScan.gschema.xml does show a suitable
default:
75
Quality value to use for JPEG compression
Quality value to use for JPEG compression.
--
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
TL;DR: Apparently the compression setting was set to the minimum value. Changing that fixed the problem. --- Investigation log: 1. Pointing LD_LIBRARY_PATH to a restored backup of /usr/lib/x86_64-linux-gnu does not help. 2. "strace -f" shows no external programs are called to handle compression/saving. 3. Looking at the simple-scan sources, there must be a quality setting somewhere in the GUI? But it's not in Preferences, where I believe there used to be such an option? 4. Found it: when the file format at the bottom of the save dialog is set to JPEG or PDF, a small "Compression" slider is shown next to it, which I had never noticed before (I always change file format by editing the file name + extension at the top). This was set to its minimum value. 5. Moving the slider to the right fixes the issue for me. -- 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 2025537] Re: chrome Check failed
@novhak 5.19.0-1010-nvidia-lowlatency -- 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 2025557] [NEW] Documents cannot be opened in desktop UI on storage device
Public bug reported: I have LibreCalc files on a WD MyCloudEX2Ultra NAS. When I try to open these files, It claims the document is in use. It offers to open it in read-only mode. I've tried several Calc files, same issue. I used GNU Paint to paste the screenshot in. Tried to show as much as I could. Attached is a PNG screen capture. lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 apt-cache policy gvfs gvfs: Installed: 1.48.2-0ubuntu1 Candidate: 1.48.2-0ubuntu1 Version table: *** 1.48.2-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.48.1-4 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages I expected it to open in r/w mode, just like my Linux Mint and KDE Neon machines. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gvfs 1.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./scripts/chroot-scripts/os-post/70_fix-apt-installed.sh CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Sun Jul 2 04:57:20 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33 InstallationDate: Installed on 2023-03-07 (116 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs Symptom: storage Title: Documents cannot be opened in desktop UI on storage device UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "PNG screen capture" https://bugs.launchpad.net/bugs/2025557/+attachment/5683395/+files/ubuntu-bug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/2025557 Title: Documents cannot be opened in desktop UI on storage device Status in gvfs package in Ubuntu: New Bug description: I have LibreCalc files on a WD MyCloudEX2Ultra NAS. When I try to open these files, It claims the document is in use. It offers to open it in read-only mode. I've tried several Calc files, same issue. I used GNU Paint to paste the screenshot in. Tried to show as much as I could. Attached is a PNG screen capture. lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 apt-cache policy gvfs gvfs: Installed: 1.48.2-0ubuntu1 Candidate: 1.48.2-0ubuntu1 Version table: *** 1.48.2-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.48.1-4 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages I expected it to open in r/w mode, just like my Linux Mint and KDE Neon machines. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gvfs 1.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./scripts/chroot-scripts/os-post/70_fix-apt-installed.sh CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Sun Jul 2 04:57:20 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33 InstallationDate: Installed on 2023-03-07 (116 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs Symptom: storage Title: Documents cannot be opened in desktop UI on storage device UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2025557/+subscriptions -- Mailing list: https://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)
Coming back to this report here: as expected but now confirmed: when I boot the old kernel everything is working normally. So the cause is *confirmed* to be the different/upgraded kernel that was installed without my request (as described in 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 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
I just checked the chromium bug tracker: the link is valid, but it is flagged as "Only users with EditIssue permission or issue reporter may view.". I guess it's caused by being created from an uploaded crash report. Probably due to privacy considerations as the crash dump might contain private information. There's also no way that I can change the permissions. -- 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 2025552] [NEW] Some of the screen doesnt interact
Public bug reported: I am using browsers and code editors. in some part of the screen i cant click buttons or vscode doesnt detect the typing, etc ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 2 13:32:01 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: rtl8188fu/1.0, 5.19.0-40-generic, x86_64: installed rtl8814au/4.3.21: added GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2022-09-05 (300 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ECS H61H2-M4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=253580b7-029c-45d3-99ea-5e0bd016dda4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-M4 dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/13/2013:br4.6:svnECS:pnH61H2-M4:pvr1.0:rvnECS:rnH61H2-M4:rvr1.0:cvnECS:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H61H2-M4 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: ECS modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-10-23T16:06:36.178537 version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu3 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2025552 Title: Some of the screen doesnt interact Status in xorg package in Ubuntu: New Bug description: I am using browsers and code editors. in some part of the screen i cant click buttons or vscode doesnt detect the typing, etc ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 2 13:32:01 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: rtl8188fu/1.0, 5.19.0-40-generic, x86_64: installed rtl8814au/4.3.21: added GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2022-09-05 (300 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ECS H61H2-M4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=253580b7-029c-45d3-99ea-5e0bd016dda4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-M4 dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/13/2013:br4.6:svnECS:pnH61H2-M4:pvr1.0:rvnECS:rnH61H2-M4:rvr1.0:cvnECS:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M.
[Desktop-packages] [Bug 2025550] [NEW] External display is not detecting
Public bug reported: After an update my external display switched off and is not being detected. I connected my external display to windows laptop to test and it worked. Some additional information: lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 xrandr --listmonitors Monitors: 1 0: +*XWAYLAND0 1920/340x1080/190+0+0 XWAYLAND0 dpkg -l | grep -i nvidia ii libnvidia-cfg1-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA binary OpenGL/GLX configuration library ii libnvidia-common-535 535.54.03-0ubuntu0.23.04.2 all Shared files used by the NVIDIA libraries rc libnvidia-compute-525:amd64525.116.04-0ubuntu0.23.04.1 amd64NVIDIA libcompute package ii libnvidia-compute-535:amd64535.54.03-0ubuntu0.23.04.2 amd64NVIDIA libcompute package ii libnvidia-decode-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA Video Decoding runtime libraries ii libnvidia-encode-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64NVENC Video Encoding runtime library ii libnvidia-extra-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64Extra libraries for the NVIDIA driver ii libnvidia-fbc1-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA OpenGL-based Framebuffer Capture runtime library ii libnvidia-gl-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD rc linux-modules-nvidia-525-6.2.0-20-generic 6.2.0-20.20+2 amd64Linux kernel nvidia modules for version 6.2.0-20 rc linux-modules-nvidia-525-6.2.0-23-generic 6.2.0-23.23 amd64Linux kernel nvidia modules for version 6.2.0-23 rc linux-modules-nvidia-525-6.2.0-24-generic 6.2.0-24.24 amd64Linux kernel nvidia modules for version 6.2.0-24 ii linux-objects-nvidia-525-6.2.0-1005-oracle 6.2.0-1005.5+3 amd64Linux kernel nvidia modules for version 6.2.0-1005 (objects) ii linux-objects-nvidia-525-6.2.0-1007-lowlatency 6.2.0-1007.7+3 amd64Linux kernel nvidia modules for version 6.2.0-1007 (objects) rc linux-objects-nvidia-525-6.2.0-20-generic 6.2.0-20.20+2 amd64Linux kernel nvidia modules for version 6.2.0-20 (objects) rc linux-objects-nvidia-525-6.2.0-23-generic 6.2.0-23.23 amd64Linux kernel nvidia modules for version 6.2.0-23 (objects) rc linux-objects-nvidia-525-6.2.0-24-generic 6.2.0-24.24 amd64Linux kernel nvidia modules for version 6.2.0-24 (objects) ii linux-signatures-nvidia-6.2.0-1005-oracle 6.2.0-1005.5+3 amd64Linux kernel signatures for nvidia modules for version 6.2.0-1005-oracle ii linux-signatures-nvidia-6.2.0-1007-lowlatency 6.2.0-1007.7+3 amd64Linux kernel signatures for nvidia modules for version 6.2.0-1007-lowlatency rc nvidia-compute-utils-525 525.116.04-0ubuntu0.23.04.1 amd64NVIDIA compute utilities ii nvidia-compute-utils-535 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA compute utilities ii nvidia-dkms-535535.54.03-0ubuntu0.23.04.2 amd64NVIDIA DKMS package ii nvidia-driver-535 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA driver metapackage ii nvidia-firmware-535-535.54.03 535.54.03-0ubuntu0.23.04.2 amd64Firmware files used by the kernel module rc nvidia-kernel-common-525 525.116.04-0ubuntu0.23.04.1 amd64Shared files used with the kernel module ii nvidia-kernel-common-535 535.54.03-0ubuntu0.23.04.2 amd64Shared files used with the kernel module ii nvidia-kernel-source-535 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA kernel source package ii nvidia-prime 0.8.17.1 all Tools to enable NVIDIA's Prime ii nvidia-settings510.47.03-0ubuntu1 amd64Tool for configuring the NVIDIA graphics driver ii nvidia-utils-535 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA driver support binaries ii screen-resolution-extra0.18.3 all
[Desktop-packages] [Bug 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
I get "permission denied" on the chrome bug link https://bugs.chromium.org/p/chromium/issues/detail?id=1459821. Is there a public link for that bug? -- 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
