Version-Release number of selected component: xscreensaver-base-5.19-3.fc17 Additional info: libreport version: 2.0.16 abrt_version: 2.0.16 backtrace_rating: 4 cmdline: xscreensaver -nosplash kernel: 3.6.2-4.fc17.x86_64 truncated backtrace: :Thread no. 1 (8 frames) : #2 pam_sm_authenticate at ../nsswitch/pam_winbind.c:2735 : #3 _pam_dispatch_aux at pam_dispatch.c:110 : #4 _pam_dispatch at pam_dispatch.c:407 : #5 pam_authenticate at pam_auth.c:34 : #6 pam_try_unlock at ../../driver/passwd-pam.c:246 : #7 xss_authenticate at ../../driver/passwd.c:263 : #8 unlock_p at ../../driver/lock.c:2230 : #9 main_loop at ../../driver/xscreensaver.c:1338
Created attachment 633959 [details] File: core_backtrace
Created attachment 633960 [details] File: environ
Created attachment 633961 [details] File: limits
Created attachment 633962 [details] File: backtrace
Created attachment 633963 [details] File: cgroup
Created attachment 633964 [details] File: smolt_data
Created attachment 633965 [details] File: maps
Created attachment 633966 [details] File: dso_list
Created attachment 633967 [details] File: proc_pid_status
Created attachment 633968 [details] File: var_log_messages
Created attachment 633969 [details] File: open_fds
Once asking samba maintainer for help. Looks like this is https://bugzilla.samba.org/show_bug.cgi?id=8564
If you can reproduce this bug, can you try if applying the following patch to current Fedora 17 samba srpm helps or not? https://attachments.samba.org/attachment.cgi?id=7054 (Looks like the above patch is not applied to samba-3.6.8-94.fc17.1.src yet)
(In reply to comment #13) > If you can reproduce this bug, can you try if applying the following patch > to current Fedora 17 samba srpm helps or not? > > https://attachments.samba.org/attachment.cgi?id=7054 > > (Looks like the above patch is not applied to samba-3.6.8-94.fc17.1.src yet) Yes, I can reproduce this bug; however, I do not know how to apply a patch in this form. Can you point me to the proper instructions?
Yes, this looks like bso #8564. I will provide an update.
@Andreas: Thank you. @Harold: Okay, then please try samba update when available.
samba-3.6.8-95.fc17.1 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/samba-3.6.8-95.fc17.1
Package samba-3.6.8-95.fc17.1: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing samba-3.6.8-95.fc17.1' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-17015/samba-3.6.8-95.fc17.1 then log in and leave karma (feedback).
(In reply to comment #18) > Package samba-3.6.8-95.fc17.1: > * should fix your issue, > * was pushed to the Fedora 17 testing repository, > * should be available at your local mirror within two days. > Update it with: > # su -c 'yum update --enablerepo=updates-testing samba-3.6.8-95.fc17.1' > as soon as you are able to. > Please go to the following url: > https://admin.fedoraproject.org/updates/FEDORA-2012-17015/samba-3.6.8-95. > fc17.1 > then log in and leave karma (feedback). After applying this patch, the reported bug no longer occurs.
samba-3.6.8-95.fc17.1 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.