Bug 869083 - [abrt] gnome-bluetooth-3.6.0-1.fc18: strstr: Process /usr/bin/bluetooth-wizard was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-bluetooth-3.6.0-1.fc18: strstr: Process /usr/bin/bluetooth-wizar...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-bluetooth
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:89677b228c9cf872b3481c6f2cf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-23 01:20 UTC by Gerard Ryan
Modified: 2012-10-29 17:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-29 17:24:51 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: core_backtrace (3.87 KB, text/plain)
2012-10-23 01:21 UTC, Gerard Ryan 		no flags Details
File: environ (1.46 KB, text/plain)
2012-10-23 01:21 UTC, Gerard Ryan 		no flags Details
File: backtrace (42.03 KB, text/plain)
2012-10-23 01:21 UTC, Gerard Ryan 		no flags Details
File: limits (1.29 KB, text/plain)
2012-10-23 01:21 UTC, Gerard Ryan 		no flags Details
File: cgroup (129 bytes, text/plain)
2012-10-23 01:21 UTC, Gerard Ryan 		no flags Details
File: maps (52.00 KB, text/plain)
2012-10-23 01:21 UTC, Gerard Ryan 		no flags Details
File: dso_list (10.76 KB, text/plain)
2012-10-23 01:21 UTC, Gerard Ryan 		no flags Details
File: proc_pid_status (934 bytes, text/plain)
2012-10-23 01:21 UTC, Gerard Ryan 		no flags Details
File: var_log_messages (159 bytes, text/plain)
2012-10-23 01:21 UTC, Gerard Ryan 		no flags Details
File: open_fds (609 bytes, text/plain)
2012-10-23 01:21 UTC, Gerard Ryan 		no flags Details
View All

Description Gerard Ryan 2012-10-23 01:20:59 UTC 
Version-Release number of selected component:
gnome-bluetooth-3.6.0-1.fc18

Additional info:
libreport version: 2.0.16
abrt_version:   2.0.16
backtrace_rating: 4
cmdline:        bluetooth-wizard
crash_function: strstr
kernel:         3.6.2-2.fc18.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 strstr at ../string/strstr.c:62
: #1 pin_db_parse_start_tag at pin.c:95
: #3 emit_start_element at gmarkup.c:983
: #4 g_markup_parse_context_parse at gmarkup.c:1320
: #5 get_pincode_for_device at pin.c:148
: #6 select_device_changed at main.c:754
: #7 g_cclosure_marshal_VOID__STRINGv at gmarshal.c:1004
: #8 _g_closure_invoke_va at gclosure.c:840
: #11 select_browse_device_callback at bluetooth-chooser.c:469
: #12 _g_closure_invoke_va at gclosure.c:840
Comment 1 Gerard Ryan 2012-10-23 01:21:01 UTC 
Created attachment 631798 [details]
File: core_backtrace
Comment 2 Gerard Ryan 2012-10-23 01:21:04 UTC 
Created attachment 631799 [details]
File: environ
Comment 3 Gerard Ryan 2012-10-23 01:21:06 UTC 
Created attachment 631800 [details]
File: backtrace
Comment 4 Gerard Ryan 2012-10-23 01:21:08 UTC 
Created attachment 631801 [details]
File: limits
Comment 5 Gerard Ryan 2012-10-23 01:21:10 UTC 
Created attachment 631802 [details]
File: cgroup
Comment 6 Gerard Ryan 2012-10-23 01:21:12 UTC 
Created attachment 631803 [details]
File: maps
Comment 7 Gerard Ryan 2012-10-23 01:21:15 UTC 
Created attachment 631804 [details]
File: dso_list
Comment 8 Gerard Ryan 2012-10-23 01:21:17 UTC 
Created attachment 631805 [details]
File: proc_pid_status
Comment 9 Gerard Ryan 2012-10-23 01:21:20 UTC 
Created attachment 631806 [details]
File: var_log_messages
Comment 10 Gerard Ryan 2012-10-23 01:21:23 UTC 
Created attachment 631807 [details]
File: open_fds
Comment 11 Bastien Nocera 2012-10-29 17:24:51 UTC 
Fixed upstream.

You just need to wait for the search to have completed (and the device's name to be available) to work around the problem.

commit f1ede20e18c9b731d21e7ea8869c9a80933c11b2
Author: Bastien Nocera <hadess>
Date:   Mon Oct 29 18:20:02 2012 +0100

    wizard: Fix crash when doing substring-matching
    
    Regression caused by aabaada7ac0d24cf67590f7403156c68bc8f98d4
    
    https://bugzilla.redhat.com/show_bug.cgi?id=869083
Note You need to log in before you can comment on or make changes to this bug.