Bug 81761 - redhat-config-packages segfaults
redhat-config-packages segfaults
Status: CLOSED DUPLICATE of bug 80283
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-packages (Show other bugs)
9
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-01-13 15:22 EST by Pam Huntley
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:
Environment:
Last Closed: 2006-02-21 13:51:10 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Pam Huntley 2003-01-13 15:22:18 EST
Description of problem:
When I click on Red Hat->System Settings->Packages, I see a flash of a screen
for a minute, then I get a messagebox with "Unknown Error".

When I run it from the command line, I see this:
(MainWindow.py:3609): GLib-GObject-WARNING **: invalid uninstantiatable type
`gulong' in cast to `GtkObject'
 
(MainWindow.py:3609): GLib-GObject-WARNING **: instance of invalid
non-instantiatable type `gulong'
 
(MainWindow.py:3609): GLib-GObject-CRITICAL **: file gsignal.c: line 2056
(g_signal_handlers_destroy): assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Segmentation fault



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


How reproducible:
always

Steps to Reproduce:
1.  run redhat-config-packages
2.
3.
    
Actual results:
segfault

Expected results:
app to run

Additional info:
Comment 1 Jeremy Katz 2003-01-13 15:33:34 EST

*** This bug has been marked as a duplicate of 80283 ***
Comment 2 Pam Huntley 2003-01-13 17:14:39 EST
so how come none of these duplicates showed up when I searched for any bugs on
redhat-config-packages?  I'm just asking 'cause I hate wasting peoples time  :-)
Comment 3 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.