pam mount crashes with libcrypto and gdm3 or sddm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libpam-mount (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
From kern.log crash only in gdm and sddm pam_mount works in console :
Apr 29 21:11:53 dellUbuntuPW kernel: [ 16.904989] gdm-session-
ult at 1d3 ip 00007fcec1f7fa1c sp 00007ffd0f4a17a0 error 4 in libcrypto.so.1.1[7
fcec1f53000+1a3000]
Apr 29 21:11:53 dellUbuntuPW kernel: [ 16.905002] Code: 54 24 08 49 89 14 24 4
1 89 6c 24 0c e9 d6 fe ff ff 31 c0 e9 70 ff ff ff 66 0f 1f 44 00 00 f3 0f 1e fa
41 56 41 55 41 54 55 53 <8b> 47 34 48 89 fb 85 c0 75 07 8b 57 38 85 d2 74 13 83
c0 01 89 43
Apr 29 21:11:56 dellUbuntuPW kernel: [ 20.015493] gdm-session-
ult at 1d3 ip 00007f5255942a1c sp 00007fff2c682f80 error 4 in libcrypto.
Apr 29 21:11:56 dellUbuntuPW kernel: [ 20.015511] Code: 54 24 08 49 89 14 24 41 89 6c 24 0c e9 d6 fe ff ff 31 c0 e9 70 ff ff ff 66 0f 1f 44 00 00 f3 0f 1e fa 41 56 41 55 41 54 55 53 <8b> 47 34 48 89 fb 85 c0 75 07 8b 57 38 85 d2 74 13 83 c0 01 89 43
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libpam-mount 2.18-2build2
Uname: Linux 5.15.20-
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 29 21:31:50 2022
InstallationDate: Installed on 2020-06-01 (696 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=pl_PL.UTF-8
SHELL=/bin/sh
SourcePackage: libpam-mount
UpgradeStatus: Upgraded to jammy on 2022-04-29 (0 days ago)
mtime.conffile.
Thank you for taking the time to file a bug report.
I'm afraid we will need more information in order to investigate this. Could you please provide steps to reproduce the problem? Can you reliably reproduce it? Is there any coredump file available after the crash?
Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".
For local configuration issues, you can find assistance here: www.ubuntu. com/support/ community
http://