After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 726735 - gdm-session-worker crash in strlen()
gdm-session-worker crash in strlen()
Status: RESOLVED NOTGNOME
Product: gdm
Classification: Core
Component: general
3.10.x
Other Linux
: Normal critical
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2014-03-19 18:19 UTC by Milan Bouchet-Valat
Modified: 2014-03-19 19:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Bouchet-Valat 2014-03-19 18:19:10 UTC 
I'm seeing this crash on Fedora 20 with gdm-3.10.0.1-1.fc20, but it also happened with 3.8.

https://bugzilla.redhat.com/show_bug.cgi?id=989653

Core was generated by `gdm-session-worker [pam/gdm-fingerprint]'.
Program terminated with signal SIGSEGV, Segmentation fault.

+ Trace 233369

Thread 1 (Thread 0x7f3d9eef5880 (LWP 2422))

  • #0 strlen
    at ../sysdeps/x86_64/strlen.S line 106
  • #1 __GI___strdup
    at strdup.c line 41
  • #2 pam_sm_authenticate
    at pam_ecryptfs.c line 161
  • #3 _pam_dispatch_aux
    at pam_dispatch.c line 110
  • #4 _pam_dispatch
    at pam_dispatch.c line 407
  • #5 pam_authenticate
    at pam_auth.c line 34
  • #6 gdm_session_worker_authenticate_user
    at gdm-session-worker.c line 1196
  • #7 do_authenticate
    at gdm-session-worker.c line 2217
  • #8 state_change_idle
    at gdm-session-worker.c line 2430
  • #9 g_main_dispatch
    at gmain.c line 3066
  • #10 g_main_context_dispatch
    at gmain.c line 3642
  • #11 g_main_context_iterate
    at gmain.c line 3713
  • #12 g_main_loop_run
    at gmain.c line 3907
  • #13 main
    at session-worker-main.c line 138 






Comment 1


Ray Strode [halfline]





          2014-03-19 19:12:15 UTC
        



this looks like some sort of bug in pam_ecryptfs not a bug in gdm.  My guess is ecryptfs uses the typed in password to decrypt the fs, but with fingerprint login, there's not password to decrypt with.  you probably need to disable the fingerprint login and/or take pam_ecryptfs out of your fingerprint authentication stack.