Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#41229 - [pam_mount] Cannot mount because segfault

Attached to Project: Community Packages
Opened by Jorge Araya Navarro (shackra) - Thursday, 17 July 2014, 02:02 GMT
Last edited by Sergej Pupykin (sergej) - Friday, 13 March 2015, 14:14 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: I updated my machine, and after rebooting, I wasn't able to login into my account throught SLiM. This was the output of dmesg:

[ +10,062662] slim[1051]: segfault at 0 ip 00007fd5d1066409 sp 00007fffe63abaa0 error 4 in libxcb.so.1.1.0[7fd5d1059000+21000]
[ +8,981338] mount.crypt[1329]: segfault at 11 ip 00007f6f85df3676 sp 00007fffb7c3de00 error 4 in libc-2.19.so[7f6f85dab000+1a4000]
[ +0,031412] mount.crypt[1333]: segfault at 11 ip 00007f7c8c570676 sp 00007ffff4e79120 error 4 in libc-2.19.so[7f7c8c528000+1a4000]

I tried then to mount my encrypted partition with:

`cryptsetup luksOpen /home/jorge.img jorge`

and doing `mount /dev/mapper/jorge /home/jorge` worked well, I then logged in through SLiM.

I notice that trying to login to my account through a TTy doesn't work, the same error message appears:

[jul16 19:34] mount.crypt[2001]: segfault at 11 ip 00007fe115d13676 sp 00007fffac7c7bd0 error 4 in libc-2.19.so[7fe115ccb000+1a4000]
[ +0,025401] mount.crypt[2006]: segfault at 11 ip 00007f3e40b1d676 sp 00007fff61a5a240 error 4 in libc-2.19.so[7f3e40ad5000+1a4000]

Additional info:
* glibc 2.19-5
* libxcb 1.10-3
* cryptsetup 1.6.4-1

This task depends upon

Closed by  Sergej Pupykin (sergej)
Friday, 13 March 2015, 14:14 GMT
Reason for closing:  No response
Additional comments about closing:  hopefully fixed
Comment by Sergej Pupykin (sergej) - Wednesday, 04 March 2015, 12:43 GMT
can it be reproduced with pam_mount 2.15 ?

Loading...