Description of problem: Not sure... Version-Release number of selected component: bluez-5.29-2.fc22 Additional info: reporter: libreport-2.5.0 backtrace_rating: 4 cmdline: /usr/libexec/bluetooth/obexd crash_function: __strcmp_sse2_unaligned executable: /usr/libexec/bluetooth/obexd global_pid: 3251 kernel: 4.0.0-0.rc5.git4.1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1975 Truncated backtrace: Thread no. 1 (6 frames) #0 __strcmp_sse2_unaligned at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:29 #1 find_session at obexd/client/manager.c:161 #2 remove_session at obexd/client/manager.c:230 #3 process_message at gdbus/object.c:259 #4 _dbus_object_tree_dispatch_and_unlock at dbus-object-tree.c:1018 #6 message_dispatch at gdbus/mainloop.c:72
Created attachment 1014319 [details] File: backtrace
Created attachment 1014320 [details] File: build_ids
Created attachment 1014321 [details] File: cgroup
Created attachment 1014322 [details] File: core_backtrace
Created attachment 1014323 [details] File: dso_list
Created attachment 1014324 [details] File: environ
Created attachment 1014325 [details] File: limits
Created attachment 1014326 [details] File: maps
Created attachment 1014327 [details] File: mountinfo
Created attachment 1014328 [details] File: namespaces
Created attachment 1014329 [details] File: open_fds
Created attachment 1014330 [details] File: proc_pid_status
Created attachment 1014331 [details] File: var_log_messages
Another user experienced a similar problem: Coming back from suspend reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/libexec/bluetooth/obexd crash_function: __strcmp_sse2_unaligned executable: /usr/libexec/bluetooth/obexd global_pid: 7439 kernel: 4.0.8-300.fc22.x86_64 package: bluez-5.29-2.fc22 reason: obexd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.