Bug 81766 - redhat-config-packages fails to start
redhat-config-packages fails to start
Status: CLOSED DUPLICATE of bug 80283
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-packages (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Jeremy Katz
Depends On:
  Show dependency treegraph
Reported: 2003-01-13 15:59 EST by Don Welch
Modified: 2008-05-01 11:38 EDT (History)
0 users

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

Attachments (Terms of Use)

  None (edit)
Description Don Welch 2003-01-13 15:59:28 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130

Description of problem:
Launching '/usr/bin/redhat-config-packages' produces the following error:

(MainWindow.py:2010): GLib-GObject-WARNING **: invalid uninstantiable type
'gint' in cast to 'GtkObject'

(MainWindow.py:2010): GLib-GObject-WARNING **: instance of invalid
non-instantiable type 'gint'

(MainWindow.py:2010): GLib-GObject-CRITICAL **: file gsignal.c: line 2056
(g_signal_handlers_destroy): assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

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

How reproducible:

Steps to Reproduce:
1. Install Phoebe with Workstation option
2. Logon as root or any other user
3. Choose RH | System Settings | Packages or run /usr/bin/redhat-config-packages
from terminal window


Actual Results:  If launched from RH menu, error dialog "Unknown error"
If launched from terminal, error message as shown in description

Expected Results:  Package Manager should run

Additional info:
Comment 1 Jeremy Katz 2003-01-13 16:05:21 EST

*** This bug has been marked as a duplicate of 80283 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:51:10 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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