Description of problem: I don't remember doing anything special, in general I just use yum from the cmdline, so this most likely happened while package kit was checking for updates in the background. Version-Release number of selected component: PackageKit-0.9.1-0.5.20140217.fc21 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: strlen executable: /usr/libexec/packagekitd kernel: 3.14.0-0.rc2.git1.1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 strlen at ../sysdeps/x86_64/strlen.S:106 #1 __strdup at strdup.c:41 #2 setstropt at url.c:291 #3 Curl_dupset at url.c:355 #4 curl_easy_duphandle at easy.c:880 #5 prepare_next_transfer at /usr/src/debug/librepo/py3/librepo/downloader.c:529 #6 prepare_next_transfers at /usr/src/debug/librepo/py3/librepo/downloader.c:714 #7 check_transfer_statuses at /usr/src/debug/librepo/py3/librepo/downloader.c:1029 #8 lr_perform at /usr/src/debug/librepo/py3/librepo/downloader.c:1116 #9 lr_download at /usr/src/debug/librepo/py3/librepo/downloader.c:1231
Created attachment 865966 [details] File: backtrace
Created attachment 865967 [details] File: cgroup
Created attachment 865968 [details] File: core_backtrace
Created attachment 865969 [details] File: dso_list
Created attachment 865970 [details] File: environ
Created attachment 865971 [details] File: exploitable
Created attachment 865972 [details] File: limits
Created attachment 865973 [details] File: maps
Created attachment 865974 [details] File: open_fds
Created attachment 865975 [details] File: proc_pid_status
Created attachment 865976 [details] File: var_log_messages
Another user experienced a similar problem: Opened gnome-software reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: strlen executable: /usr/libexec/packagekitd kernel: 3.13.3-201.fc20.x86_64 package: PackageKit-0.9.1-0.5.20140217.fc21 reason: packagekitd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
Looks like a librepo crash. Reassigning.
Cannot reproduce with current version of Librepo (should be fixed). Feel free to reopen if reappears.