From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.6) Gecko/20040422 Description of problem: i'm using a custom kernel (vanilla form kernel.org), because i had problems with acpi on my laptop. first i named this kernel 2.6.5-my-1, after booting this kernel i was not able to run system-config-network (see the dump file). after renaming the kernel version to 2.6.5-my.1 it started again without problems. Version-Release number of selected component (if applicable): system-config-network-1.3.16-1 How reproducible: Always Steps to Reproduce: 1. boot a kernel with a version string like 2.6.5-my-1 2. run system-config-network Actual Results: system-config-network crashed on starting Expected Results: it should start without a crash
Created attachment 99873 [details] dump-file of the crash
Created attachment 100114 [details] kernel version patch to /usr/share/system-config-network/netconfpkg/NC_functions.py
I guess it is quite benign to apply the following patch in order to extract only the first part (by passing the 'maxsplit' parameter to 'split()') of the kernel version string such as : "2.6.5" => "2.6.5" "2.6.0-test8" => "2.6.0", "test8" "2.6.6-rc1-mm1" => "2.6.6", "rc1-mm1" and so on.
*** Bug 124047 has been marked as a duplicate of this bug. ***
*** Bug 123930 has been marked as a duplicate of this bug. ***
*** Bug 125077 has been marked as a duplicate of this bug. ***
*** Bug 127985 has been marked as a duplicate of this bug. ***
[This is a mass update sent to many bugs that missed earlier such messages due to having their version set to a test version.] This bug was originally filed against a version of Fedora Core which is no longer supported, even for security updates. Many changes have occured since then. Please retest this bug against a still supported version. Note that FC3 and FC4 are supported by Fedora Legacy for security fixes only. If it still occurs on FC5 or FC6, please assign to the correct version. Otherwise, if this a security issue, please change the product to Fedora Legacy. Thanks, and we are sorry that we did not get to this bug earlier. This bug will be closed after a few weeks if no information is given indicating that the bug is still present in a supported release.
Closing per lack of response to previous request for information. This bug was originally filed against a much earlier version of Fedora Core, and significant changes have taken place since the last version for which this bug is confirmed. Note that FC3 and FC4 are supported by Fedora Legacy for security fixes only. Please install a still supported version and retest. If it still occurs on FC5 or FC6, please reopen and assign to the correct version. Otherwise, if this a security issue, please change the product to Fedora Legacy. Thanks, and we are sorry that we did not get to this bug earlier.