Bug 670655

Summary: Can't dismiss error dialog when subscribing to personal subscriptions
Product: Red Hat Enterprise Linux 6 Reporter: Jeff Weiss <jweiss>
Component: subscription-managerAssignee: Chris Duryee <cduryee>
Status: CLOSED ERRATA QA Contact: J.C. Molet <jmolet>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: bkearney, cduryee, dajohnso, dgoodwin, jmolet
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
subscription-manager-gnome-0.94.0-1.git.29.5062eed.el6.x86_64
Last Closed: 2011-05-19 13:38:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 568421    

Description Jeff Weiss 2011-01-18 22:05:03 UTC
Description of problem:
See repeat steps

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


How reproducible:
always

Steps to Reproduce:
1.  Register to on-prem server as testuser1
2.  Search for subscriptions - uncheck "match my hardware", check "cover software not installed"
3.  Subscribe to all the products one by one, choosing the first contract, until all that's left is "RHEL Personal" and "IPA Client Pack (50)" - those can't be subscribed to, but try anyway and dismiss the error dialog by clicking OK.

  
Actual results:
By the time there are only 2 subscriptions left in the list, Can't dismiss the error dialog - stderr shows:
TypeError: object at 0x16cbd20 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 64, in _on_response_event
    self.emit('response', rc)

Expected results:
Error dialog can be dismissed

Additional info:

Comment 2 Adrian Likins 2011-01-24 21:26:35 UTC
commit 3609334d2e2dee04a524003917e97319d75a2e64
Author: Adrian Likins <alikins>
Date:   Fri Jan 21 13:35:08 2011 -0500

    670655: remove addFrame method. Fix traceback on sub error dialog
    
    Looks like this was causing self.dialog to get destroy. Remove
    it since I don't think we need it. It was the .remove() that
    I think was removing the last ref for self.dialog, causing the destroy.

Comment 4 J.C. Molet 2011-01-27 15:59:45 UTC
I'm able to reproduce this by just selecting the "IPA Client Pack (50)" subscription.

This is still broken as described as of build:
subscription-manager-gnome-0.93.15-1.git.4.5551b04.el6.x86_64

Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized
Traceback (most recent call last):
  File "/usr/share/rhsm/gui/messageWindow.py", line 63, in _on_response_event
    self.emit('response', rc)
TypeError: object at 0x7f76781d2e10 of type ErrorDialog is not initialized

Comment 5 Chris Duryee 2011-02-07 21:01:22 UTC
fixed in rhel6 branch and master

Comment 6 Chris Duryee 2011-02-07 21:27:17 UTC
master - 6eda843df0c79f52e5a63906397a2cd1da55bea7 0.96.2

RHEL6 - 0f6dcdcbb83ee12edf2aa1251bdce04590b9283a 0.95.2

Comment 8 J.C. Molet 2011-02-21 15:07:47 UTC
subscription-manager-gnome-0.95.1-1.git.15.c75e560.el6.x86_64

I was able to reproduce this by doing a search for products that did not match my hardware.  I then subscribed to a sub of a different type than my system (Multiplier Client product pack (50)).  I got the error dialog and was able to dismiss it easily without any warnings or tracebacks.

Comment 9 errata-xmlrpc 2011-05-19 13:38:58 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2011-0611.html