Bug 526856 - firstboot crashing at startup
Summary: firstboot crashing at startup
Keywords:
Status: CLOSED DUPLICATE of bug 527299
Alias: None
Product: Fedora
Classification: Fedora
Component: firstboot
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F12Blocker, F12FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2009-10-02 06:17 UTC by Jens Petersen
Modified: 2009-10-06 02:50 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-10-02 14:08:32 UTC


Attachments (Terms of Use)

Description Jens Petersen 2009-10-02 06:17:12 UTC
Description of problem:
firstboot seems to be crashing at startup consistently
with current rawhide

Version-Release number of selected component (if applicable):
firstboot-1.109-1.fc12
plymouth-0.8.0-0.2009.29.09.1.fc12 (version date!)

How reproducible:
every time

Steps to Reproduce:
1. install and boot rawhide
  
Actual results:
console shows (cleanup output):

firstboot ERROR: X server failed to start
Traceback (most recent call last):
File "/usr/sbin/firstboot", line 167, in <module> config.frontend.start()
File "/usr/lib64/python2.6/site-packages/firstboot/xfrontend.py", line 87, in start
  raise RuntimeError, "X server failed to start"
  RuntimeError: X server failed to start
  plymouthd: ply-keyboard.c:447: ply_keyboard_add_input_handler: Assertion `keyboard != ((void *)0)' failed.
  error: unexpectedly disconnected from boot status daemon
[FAILED]

Expected results:
no backtrace

Additional info:
firstboot starts ok as root on desktop.

Comment 1 Chris Lumens 2009-10-02 14:08:32 UTC

*** This bug has been marked as a duplicate of bug 526842 ***

Comment 2 Jens Petersen 2009-10-06 02:47:50 UTC
This wasn't ATI but the plymouth bit:
anyway it is fixed now in recent rawhide since yesterday
at least.

Comment 3 Jens Petersen 2009-10-06 02:50:51 UTC

*** This bug has been marked as a duplicate of bug 527299 ***


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