Bug 184422 - Bad: probeHW() got an unexpected keyword argument 'forceVesa'
Bad: probeHW() got an unexpected keyword argument 'forceVesa'
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-03-08 12:22 EST by Chitlesh GOORAH
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-03-08 13:03:08 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Chitlesh GOORAH 2006-03-08 12:22:34 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060306 Fedora/1.5.0.1-7 Firefox/1.5.0.1

Description of problem:
on executing kadischi, anaconda fails.
anaconda-runtime-11.0.1-1
busybox-anaconda-1.01-3
anaconda-11.0.1-1

Version-Release number of selected component (if applicable):
anaconda-runtime-11.0.1-1
busybox-anaconda-1.01-3
anaconda-11.0.1-1

How reproducible:
Always

Steps to Reproduce:
1. su -
2. kadischi /tmp/FC5T3/ /tmp/t.iso
3.  

Actual Results:  Loadnig config file options

  ***  running anaconda  ***

Traceback (most recent call last):
  File "/usr/sbin/anaconda", line 892, in ?
    forceVesa=forcevesa)
TypeError: probeHW() got an unexpected keyword argument 'forceVesa'

  ***  Fatal error: anaconda returned non zero (256) exit code. Aborting execution.

Cleaning up temporary files...
Done.


Expected Results:  launch graphical interface

Additional info:
Comment 1 Jeremy Katz 2006-03-08 13:03:08 EST
If you're going to follow rawhide anaconda, you need to follow rawhide
everything else too.

You need a newer rhpxl. 
Comment 2 Chitlesh GOORAH 2006-03-08 17:27:19 EST
Thanks,
shouldn't it be pulled as dependency ?
Comment 3 Chitlesh GOORAH 2006-03-08 17:42:08 EST
Yet Im falling on:

23:41:31 INFO    : Display mode = g
23:41:31 INFO    : Method = nfs://tmp/FC5T3
23:41:31 INFO    : _Fedora is only installclass, using it
23:41:35 INFO    : Starting graphical installation...
23:41:37 WARNING : no floppy devices found but we'll try fd0 anyway
23:41:37 INFO    : Detected 512M of memory
23:41:37 INFO    : Swap attempt of 512M to 1024M
23:41:37 WARNING : step partitionmethod does not exist
23:41:37 WARNING : step partitionmethodsetup does not exist
23:41:37 WARNING : step autopartition does not exist
23:41:37 WARNING : step readcomps does not exist
23:41:37 WARNING : step selectlangpackages does not exist
23:41:37 WARNING : step handleX11pkgs does not exist
23:41:37 WARNING : step handlemiscpkgs does not exist
23:41:37 WARNING : step fixupconditionals does not exist
23:41:39 INFO    : moving (1) to step welcome
23:41:41 INFO    : moving (1) to step language
23:41:43 INFO    : moving (1) to step keyboard
23:41:50 INFO    : moving (1) to step findrootparts
23:41:50 INFO    : moving (1) to step networkdevicecheck
23:41:50 INFO    : moving (1) to step network
23:41:51 INFO    : moving (1) to step timezone
23:41:53 INFO    : moving (-1) to step network
23:42:02 INFO    : moving (1) to step timezone
23:42:15 INFO    : moving (1) to step accounts
23:42:20 INFO    : moving (1) to step reposetup
23:42:20 INFO    : anaconda                                                    
        [1/1]
23:42:22 INFO    : moving (1) to step basepkgsel
23:42:23 INFO    : moving (1) to step tasksel
23:42:28 INFO    : moving (1) to step group-selection
23:42:28 WARNING : /usr/lib/python2.4/site-packages/pirut/GroupSelector.py:329:
GtkWarning: gtk_tree_view_scroll_to_point: assertion `GTK_WIDGET_REALIZED
(tree_view)' failed
  tree.scroll_to_point(0, 0)

23:42:30 INFO    : moving (1) to step postselection
23:42:30 INFO    : selected kernel package for kernel
23:42:37 DEBUG   : ignoring libtermcap>bash in whiteout
23:42:38 DEBUG   : ignoring initscripts>kernel in whiteout
23:42:42 DEBUG   : ignoring aspell>aspell-en in whiteout
23:42:44 DEBUG   : ignoring ghostscript-fonts>ghostscript in whiteout
23:42:53 DEBUG   : ignoring dbus>dbus-glib in whiteout
23:42:53 DEBUG   : ignoring dbus>dbus-glib in whiteout
23:42:56 DEBUG   : ignoring coreutils>pam in whiteout
23:43:02 DEBUG   : ignoring ghostscript>gimp-print in whiteout
23:43:03 DEBUG   : ignoring gstreamer-tools>gstreamer in whiteout
23:43:03 DEBUG   : ignoring ypbind>yp-tools in whiteout
23:43:04 DEBUG   : ignoring nautilus>nautilus-cd-burner in whiteout
23:43:12 DEBUG   : ignoring openjade>docbook-dtds in whiteout
23:43:13 DEBUG   : ignoring gnome-python2>gnome-python2-bonobo in whiteout
23:43:18 DEBUG   : ignoring gtk+>gdk-pixbuf in whiteout
23:43:18 DEBUG   : ignoring gtk+>gdk-pixbuf in whiteout
23:43:19 DEBUG   : ignoring ghostscript>gimp-print in whiteout
23:43:21 DEBUG   : ignoring gstreamer-tools>gstreamer in whiteout
23:43:21 DEBUG   : ignoring ypbind>yp-tools in whiteout
23:43:21 DEBUG   : ignoring gtk+>gdk-pixbuf in whiteout
23:43:21 DEBUG   : ignoring gtk+>gdk-pixbuf in whiteout
23:43:21 DEBUG   : ignoring dbus>dbus-glib in whiteout
23:43:21 DEBUG   : ignoring dbus>dbus-glib in whiteout
23:43:24 DEBUG   : ignoring libtermcap>bash in whiteout
23:43:24 DEBUG   : ignoring gnome-python2>gnome-python2-bonobo in whiteout
23:43:24 DEBUG   : ignoring initscripts>kernel in whiteout
23:43:24 DEBUG   : ignoring openjade>docbook-dtds in whiteout
23:43:28 DEBUG   : ignoring nautilus>nautilus-cd-burner in whiteout
23:43:28 DEBUG   : ignoring coreutils>pam in whiteout
23:43:28 DEBUG   : ignoring ghostscript-fonts>ghostscript in whiteout
23:43:30 DEBUG   : ignoring aspell>aspell-en in whiteout

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