Bug 467757 - bluetooth-wizard dies with segmentation fault after selecting a device to pair
Summary: bluetooth-wizard dies with segmentation fault after selecting a device to pair
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: bluez-gnome
Version: rawhide
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-20 18:57 UTC by Dominik 'Rathann' Mierzejewski
Modified: 2008-10-20 21:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-20 21:57:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
gdb backtrace (17.11 KB, text/plain)
2008-10-20 18:57 UTC, Dominik 'Rathann' Mierzejewski
no flags Details

Description Dominik 'Rathann' Mierzejewski 2008-10-20 18:57:35 UTC
Created attachment 320900 [details]
gdb backtrace

Description of problem:
bluetooth-wizard dies with segmentation fault after selecting a device to pair and clicking "Forward".

Version-Release number of selected component (if applicable):
bluez-gnome-1.8-3.fc10.i386

How reproducible:
Always

Steps to Reproduce:
1. run bluetooth-wizard
2. select a device from the list
3. click "Forward"
  
Actual results:
segmentation fault

Expected results:
It should work.

Additional info:
gdb backtrace attached

Comment 1 Bastien Nocera 2008-10-20 19:09:03 UTC
Should already be fixed in 1.8-5.

* Thu Oct 16 2008 - Bastien Nocera <bnocera> - 1.8-5
- Fix potential crasher in the wizard

Comment 2 Dominik 'Rathann' Mierzejewski 2008-10-20 19:25:20 UTC
No such build in koji yet.

Comment 3 Bastien Nocera 2008-10-20 20:03:53 UTC
My mistake, forgot to run the build. See:
http://koji.fedoraproject.org/koji/taskinfo?taskID=891437

Comment 4 Bastien Nocera 2008-10-20 20:08:26 UTC
Make that:
http://koji.fedoraproject.org/koji/taskinfo?taskID=891458

Comment 5 Dominik 'Rathann' Mierzejewski 2008-10-20 21:25:15 UTC
Confirmed fixed, thanks.


Note You need to log in before you can comment on or make changes to this bug.