Bug 322601 - System hangs on firstboot while starting bluetooth.
System hangs on firstboot while starting bluetooth.
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
x86_64 Linux
low Severity high
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-10-07 20:47 EDT by Eric Hyatt
Modified: 2008-08-02 19:40 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-06-16 22:35:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Eric Hyatt 2007-10-07 20:47:42 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727)

Description of problem:
I installed Fedora 7 from an x86_64 DVD.  I have customized some things, but the installation is pretty much plain vanilla.  During firstboot, the system gets to a point where it prints "Starting Bluetooth services:  [OK]", and then
the system hangs.  The system makes no further progress.  To get past this brick wall, I reinstalled the system, making the same customization choices, except I must uncheck the boxes next to bluez-utils-3.9-2.fc7.x86_64 and gnome-bluetooth-0.8.0-4.fc7.x86_64.  After omitting these 2 packages, I can install Fedora 7, and the firstboot runs to completion without hanging.

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

How reproducible:

Steps to Reproduce:
1.Install Fedora 7 from DVD.
2.Some customization of hard disk layout.
3.Minor customization of package choices.

Actual Results:
The system hangs during first boot immediately after the message "Starting Bluetooth services:  [OK]" appears on screen.

Expected Results:
The system should have continued to print messages on the blackscreen, until firstboot was completed.

Additional info:
Comment 1 Bug Zapper 2008-05-14 10:39:17 EDT
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 2 Bastien Nocera 2008-05-20 20:02:15 EDT
a kernel problem if that's actually the case. I'd boot up the machine without
rhgb to see whether this is actually the problem.
Comment 3 Bug Zapper 2008-06-16 22:35:56 EDT
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 is no longer maintained, which means that it will not 
receive any further security or bug fix updates. As a result we 
are closing this bug. 

If you can reproduce this bug against a currently maintained version 
of Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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