Bug 81121 - Redhat-config-packages crashes with unknown error on launch
Redhat-config-packages crashes with unknown error on launch
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-05 00:50 EST by Ken Schar
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:50:56 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 Ken Schar 2003-01-05 00:50:38 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030104

Description of problem:
When trying to launch redhat-config-packages it crashes and pops up a small
window that says "Unknown error."

When program is run manually from the cmdline under root the following
additional error info is provided - [root@localhost root]# redhat-config-packages
(MainWindow.py:4591): GLib-GObject-WARNING **: invalid uninstantiatable type
`gint' in cast to `GtkObject'
(MainWindow.py:4591): GLib-GObject-WARNING **: instance of invalid
non-instantiatable type `gint'
(MainWindow.py:4591): 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. Run redhat-config-packages
2. Error pops up everytime on launch

Actual Results:  Program errors out and won't run.

Expected Results:  Program should work.

Additional info:
Comment 1 Jeremy Katz 2003-01-05 01:08:27 EST

*** This bug has been marked as a duplicate of 80283 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:50:56 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.