RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 722451 - Anaconda UI crashes (early on) when installing from live iso
Summary: Anaconda UI crashes (early on) when installing from live iso
Keywords:
Status: CLOSED DUPLICATE of bug 698282
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 6.1
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-15 11:53 UTC by Vitezslav Humpa
Modified: 2011-07-18 13:55 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-18 13:55:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Error log produced in place by anaconda (80.53 KB, text/xml)
2011-07-15 11:53 UTC, Vitezslav Humpa
no flags Details
Per request, same log plaintext version (79.13 KB, text/plain)
2011-07-15 12:27 UTC, Vitezslav Humpa
no flags Details

Description Vitezslav Humpa 2011-07-15 11:53:45 UTC
Created attachment 513366 [details]
Error log produced in place by anaconda

Description of problem:
When installing from life iso, Anaconda produces unhandled exception on the type root password screen, when a custom hostname was used.

Version-Release number of selected component (if applicable):
anaconda-13.21.117-1.el6

How reproducible:
Always
iso used: RHEL6.1-20110510.1-Workstation-x86_64-Live.iso (from globalsync/rhel/released/RHEL-6/6.1/Live/)

Steps to Reproduce:
1. Boot from the life image (kvm used in my case)
2. Start the installer.
3. Leave all the options default, except in place of "localhost.localdomain" type in e.g."rhel61"
4. When you get to the root passwd screen, installer crashes
  
Actual results:
Installer produces an unhalted exception. The backtrace goes: 
Traceback (most recent call first):
  File "/usr/lib/anaconda/iw/account_gui.py", line 91, in setCapsLockLabel
    if _isys.isCapsLockEnabled():
  File "/usr/lib/anaconda/iw/account_gui.py", line 72, in getScreen
    self.setCapsLockLabel()
  File "/usr/lib/anaconda/gui.py", line 1469, in setScreen
    new_screen = self.currentWindow.getScreen(anaconda)
  File "/usr/lib/anaconda/gui.py", line 1390, in nextClicked
    self.setScreen ()
SystemError: error return without exception set

Entire log is attached.

Expected results:
No crash

Additional info:

Comment 2 Vitezslav Humpa 2011-07-15 12:27:31 UTC
Created attachment 513370 [details]
Per request, same log plaintext version

Comment 3 Chris Lumens 2011-07-18 13:55:15 UTC

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


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