#2008 [abrt] sssd-ipa-1.10.0-12.fc19.beta2: pac_lookup_sids_done: Process /usr/libexec/sssd/sssd_pac was killed by signal 11 (SIGSEGV)
Closed: Duplicate None Opened 10 years ago by lslebodn.

Ticket was cloned from Red Hat Bugzilla (product Fedora): Bug 981091

Description of problem:
I upgraded to Fedora 19 from Fedora 18 using fedup. I tried to login with my AD
credentials which had been set up using "realm join" in F18. I could not
authenticate so logged in as a local user, did "realm leave" and then a new
"realm join". Can now authenticate.

However, when using sudo to run a command, I get a crash in sssd_pac.

/var/log/sssd/sssd_pac.log is 0 byte.

Version-Release number of selected component:
sssd-ipa-1.10.0-12.fc19.beta2

Additional info:
reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        /usr/libexec/sssd/sssd_pac --debug-to-files
crash_function: pac_lookup_sids_done
executable:     /usr/libexec/sssd/sssd_pac
kernel:         3.9.8-300.fc19.x86_64
runlevel:       N 5
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 pac_lookup_sids_done at src/responder/pac/pacsrv_cmd.c:309
 #1 pac_lookup_sids_next_done at src/responder/pac/pacsrv_cmd.c:1070
 #2 sss_dp_internal_get_done at src/responder/common/responder_dp.c:779
 #3 complete_pending_call_and_unlock at dbus-connection.c:2314
 #5 sbus_dispatch at src/sbus/sssd_dbus_connection.c:104
 #6 tevent_common_loop_timer_delay at ../tevent_timed.c:341
 #7 epoll_event_loop_once at ../tevent_epoll.c:916
 #8 std_event_loop_once at ../tevent_standard.c:112
 #9 _tevent_loop_once at ../tevent.c:530
 #10 tevent_common_loop_wait at ../tevent.c:634

It is a duplicate of ticket https://fedorahosted.org/sssd/ticket/1989

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
review: True => 0
selected: =>
testsupdated: => 0

Closing as this is a duplicate of (already closed) bug.

resolution: => duplicate
status: new => closed

Metadata Update from @lslebodn:
- Issue set to the milestone: NEEDS_TRIAGE

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/3050

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata