Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
+++ This bug was initially created as a clone of Bug #580756 +++
The following was filed automatically by anaconda:
anaconda 13.37.2 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/iw/task_gui.py", line 203, in createDialog
self.usernameEntry.set_text(self.repo.proxy_username)
File "/usr/lib/anaconda/iw/task_gui.py", line 527, in _editRepo
dialog.createDialog()
TypeError: Gtk.Entry.set_text() argument 1 must be string, not None
--- Additional comment from bcl on 2010-04-08 19:52:17 EDT ---
Created an attachment (id=405429)
Attached traceback automatically from anaconda.
--- Additional comment from bcl on 2010-04-08 19:56:09 EDT ---
While testing clumens' patch for bug 580226 I hit this bug in the repo edit dialog. It doesn't like having an empty user passed to it.
Triggered by rebuilding loader with Chris' patch and passing proxy=http://proxy.home:3128 to the kernel while doing a PXE boot of the new build.
--- Additional comment from bcl on 2010-04-08 20:15:52 EDT ---
The same error happens on the password entry when I pass proxy=http://bcl@proxy.home:3128
--- Additional comment from bcl on 2010-04-09 02:13:11 EDT ---
Yum doesn't like it when empty username and password fields are "" instead of None. Submitted a patch that converts to "" on entry to the repo edit dialog and converts "" back to None on exit.
--- Additional comment from rvykydal on 2010-04-09 04:44:52 EDT ---
*** This bug has been marked as a duplicate of bug 572460 ***
--- Additional comment from bcl on 2010-06-25 20:29:14 EDT ---
Created an attachment (id=427017)
Attached traceback automatically from anaconda.
Radek's patch 870dff4fdbbf7e88cfdf46d672ba0b3846aa7d50 will fix this.
Comment 3RHEL Program Management
2010-06-26 01:02:53 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
inclusion.
Comment 6Alexander Todorov
2010-07-14 11:50:05 UTC
With snapshot #7 (0707.4 tree) booted with proxy=http://hostname:port. In anaconda UI selecting a repository and then clicking the Modify button shows the repo config dialog. Pressing OK/Cancel closes the dialog. There's no traceback and no username/password is specified. Moving to VERIFIED.
Comment 7releng-rhel@redhat.com
2010-11-10 19:49:14 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.