Bug 186101

Summary:	hcid[1744] causes an segmentation fault at shutdwon
Product:	[Fedora] Fedora	Reporter:	Armin Mohring <mohringarmin>
Component:	bluez-utils	Assignee:	David Woodhouse <dwmw2>
Status:	CLOSED ERRATA	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	5	CC:	matbayer.web, thomas
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-07-21 09:36:47 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Armin Mohring 2006-03-21 17:27:23 UTC

Description of problem:
hcid[1744] causes an segmentation fault at shutdwon.

Version-Release number of selected component (if applicable):
?

How reproducible:

During every shutdwon
Steps to Reproduce:
1.logout from Fedora Core
2.Reboot or shutdwon Computer
3.hcid[1744] causes an exception.
  
Actual results:
exception: segmentation fault

Expected results:
no exception

Additional info:

Comment 1 Armin Mohring 2006-03-25 21:14:43 UTC

How reproducible:
during every shurdown or reboot

Comment 2 David Woodhouse 2006-09-10 09:40:49 UTC

I've not been able to reproduce this -- can you provide a core dump or catch in
gdb? Is it still happening?

Comment 3 David Woodhouse 2006-09-10 09:52:24 UTC

*** Bug 189464 has been marked as a duplicate of this bug. ***

Comment 4 Fedora Update System 2006-10-26 16:19:33 UTC

bluez-utils-3.7-2 bluez-gnome-0.6-1.fc6 has been pushed for fc6, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.

Comment 5 Armin Mohring 2006-10-26 20:07:49 UTC

I have tested FC6 x86_64 and the problem still present.

Segfault of hcid at shutdown.

Comment 6 David Woodhouse 2006-10-26 21:52:06 UTC

Please confirm: You have bluez-gnome-3.7-2 installed from today updates (and the
mirrors have synced already, etc.) and you're _still_ seeing it?