Bug 175817 - firstboot date module traces back
Summary: firstboot date module traces back
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: firstboot
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Chris Lumens
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-12-15 12:46 UTC by Paul Nasrat
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-12-15 17:08:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Paul Nasrat 2005-12-15 12:46:58 UTC
Description of problem:

Install rawhide 20051215 (see my commits to get it to install)

Traceback (most recent call last):
  File "/usr/share/firstboot/firstbootWindow.py", line 494, in loadModules
    vbox, pix, title = module.launch()
  File "/usr/share/firstboot/modules/date.py", line 77, in launch
    self.setupScreen()
  File "/usr/share/firstboot/modules/date.py", line 55, in setupScreen
    self.dateWindow = mainWindow.mainWindow (firstboot = True, showPages =
["datetime", "ntp"])
TypeError: __init__() got an unexpected keyword argument 'showPages'


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

firstboot-1.3.55-1.1
system-config-date-1.7.99.10-

How reproducible:

Always

Steps to Reproduce:
1.Install
2.reboot into firstboot
  
Actual results:

TRACEBACK

Expected results:

Shiny,fluffy date screen. 

Additional info:

Comment 1 Nils Philippsen 2005-12-15 13:25:29 UTC
Hmm, this is from s-c-date-1.7.99.10/mainWindow.py:

[...]
class mainWindow:
    [...]
    def __init__(self, page=None, firstboot=False, showPages=None):
    [...]

Is it picking up the wrong (an old) mainWindow.py file?

Comment 2 Paul Nasrat 2005-12-15 13:44:22 UTC
quite possibly due to the way firstboot modules/python path works.

Comment 3 Chris Lumens 2005-12-15 17:08:38 UTC
I've seen this within the past couple days but am unable to reproduce.


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