Bug 111979
Summary: | redhat config network segfault | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | randy smyth <ssj4goko4> |
Component: | kudzu | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED DUPLICATE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1 | CC: | eddie.kuns, rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 19:00:23 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
randy smyth
2003-12-12 08:20:35 UTC
is there a python traceback you could attach? Or does it segfault completly? I recently upgraded from RedHat 8 to Fedora Core 1. I've been running FC1 on my laptop (upgraded from RH9) for a couple months. Everything is fine on the laptop. However, on my desktop, redhat-config-network segfaults with no python traceback at all. All I see is a pop-up window: Application "redhat-config-network" (process 4287) has crashed due to a fatal error. (Segmentation fault) and a link to the Gnome error reporting page. I just run redhat-config-network and the first and only thing I see is that error pop-up. I don't know if this is the same issue as above, but it sounds like it. Since the upgrade, this tool has segfaulted 100% of the time. If I run (as root) redhat-config-network-tui, it gets as far as showing the first ethernet device. (if I click on Ethernet) As soon as I *OK* that one, it segfaults. All I see in the window is "Segmentation fault" and a command prompt. The other redhat-config-* programs that I have run all work without a problem. this is mostly the kudzu python module... reassigning *** This bug has been marked as a duplicate of 114071 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |