Bug 209124 - bluez-utils segfaults on shutdown
Summary: bluez-utils segfaults on shutdown
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: bluez-utils
Version: rawhide
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Woodhouse
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-10-03 12:59 UTC by Alan Cox
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-11-14 16:05:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Alan Cox 2006-10-03 12:59:01 UTC
Description of problem:
On shutdown bluez-utils segfaults which is logged to console as a NULL pointer
dereference in the user space app by the x86-64 kernel. This oddly doesn;t occur
if I do
service stop/start  only at shutdown.

How reproducible:
100%

Steps to Reproduce:
1. Boot
2. Shutdown

Happens with no bluetooth devices are attached to the system

Comment 1 David Woodhouse 2006-10-03 13:01:54 UTC
Please update to bluez-utils-3.7 (in the repo at http://david.woodhou.se/bluez/)
and retest.

Failing that, find some way to debug it and show me what happened :)

Comment 2 David Woodhouse 2006-10-03 13:03:57 UTC
does it also SEGV if you stop messagebus before stopping it?

Comment 3 Alan Cox 2006-10-03 13:51:33 UTC
It did the once but no pattern

The fault repeatably is segv for address 0x30, rip: 0x00002aaaaacebfe8

I'll try your repository in a bit and update the bug then see what I can do to
debug it more


Comment 4 David Woodhouse 2006-10-03 21:42:28 UTC
The bluez-utils-3.7 package should fix this. Unfortunately, it has been decreed
that we will not ship the fixed package in FC6.

I'll do an erratum after the FC6 release.

Comment 5 Alan Cox 2006-10-03 21:50:27 UTC
Fair enough, its not exactly anything but an ugly glitch on shutdown

Will verify 3.7 once I have a moment


Comment 6 Fedora Update System 2006-10-26 16:20:00 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.


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