Version-Release number of selected component: libmbim-utils-1.12.0-1.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/libexec/mbim-proxy crash_function: __strcmp_sse2_unaligned executable: /usr/libexec/mbim-proxy global_pid: 1168 kernel: 4.1.5-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (6 frames) #0 __strcmp_sse2_unaligned at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:30 #1 g_str_equal at ghash.c:1845 #2 peek_opening_device_info at mbim-proxy.c:440 #3 device_open_ready at mbim-proxy.c:473 #4 g_simple_async_result_complete at gsimpleasyncresult.c:763 #5 complete_in_idle_cb at gsimpleasyncresult.c:775
Created attachment 1065812 [details] File: backtrace
Created attachment 1065813 [details] File: cgroup
Created attachment 1065814 [details] File: core_backtrace
Created attachment 1065815 [details] File: dso_list
Created attachment 1065816 [details] File: environ
Created attachment 1065817 [details] File: limits
Created attachment 1065818 [details] File: maps
Created attachment 1065819 [details] File: mountinfo
Created attachment 1065820 [details] File: namespaces
Created attachment 1065821 [details] File: open_fds
Created attachment 1065822 [details] File: proc_pid_status
Created attachment 1065823 [details] File: var_log_messages
Seems to me that this was fixed by these: 688b094 mbim-proxy: block function error signals when checking if device is opened or not 9d8acbe mbim-proxy: upon new client, always check if device really open with a command