Bug 904644 - Firstboot after fedup hangs after "Started Authorization Manager
Summary: Firstboot after fedup hangs after "Started Authorization Manager
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: fedup
Version: 18
Hardware: Unspecified
OS: Other
unspecified
unspecified
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-26 18:57 UTC by taa
Modified: 2013-05-20 19:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-20 19:41:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screen capture of first boot (14.92 KB, image/png)
2013-01-26 18:57 UTC, taa
no flags Details

Description taa 2013-01-26 18:57:55 UTC
Created attachment 688108 [details]
screen capture of first boot

Description of problem:
Using fedup to upgrade Fedora 17 64-bit to Fedora 18. Running under Virtualbox 4.2.6, host OS is Win 7 Pro 64-bit.

Attached screen capture shows boot hangs after successfully starting authorization manager.

Version-Release number of selected component (if applicable):
I installed whatever version of fedup was available as of 01/22/2013.

How reproducible:
Fedora 18 now hangs at this same spot whenever I try to boot.

Steps to Reproduce:
unknown
  
Actual results:
Fedora 18 hangs.

Expected results:
Fedora 18 expected to boot.

Additional info:

Comment 1 warnesj 2013-02-05 05:26:38 UTC
I had the exact same problem.  I found that if I SSH'ed to the VM, reinstalled the Linux Additions and rebooted that the boot sequence completed just fine.

Comment 2 taa 2013-02-06 06:35:07 UTC
Thanks -- that was a great tip! I decided to see if I could switch to a different virtual (character) console instead of doing ssh and I could by doing ctrl-alt-F2. 

I made sure I booted the VM with guest additions attached to the virtual CDROM drive, waited until the boot froze, did ctrl-alt-f2 and then:

sudo mount /dev/cdrom /media
cd /media
sudo ./VBoxLinuxAdditions.run

I did the manual step because the autorun.sh could not find an active Gnome display.

The install completed, I rebooted and voila!

Comment 3 David Shea 2013-05-20 19:41:19 UTC
Glad you got it working. Do note that the VirtualBox guest additions need to be re-installed any time you update the kernel.

Closing the bug since this the hang was due to VirtualBox.


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