Red Hat Bugzilla – Bug 470203
system-control-network crashes at start-up when a wireless device is configured
Last modified: 2009-08-25 18:35:35 EDT
Created attachment 322677 [details]
Backtrace of system-control-network when a wireless device has been configured
Description of problem:
After installing F10 PR x86_64 on a new system, system-control-network does not start up when launched from the menu. After executing the command from the shell, it crashes instantaneously returning the attached backtrace.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Launch system-control-network from the shell.
Application crashes immediately.
Application starts as expected.
- After removing all wlan0 entries in etc/sysconfig/.. created by anaconda,
system-control-network behaves correctly.
- Interestingly, the wireless device cannot be removed from within
system-config-network: it is greyed out.
Hm, that's weird, aren't there any selinux denials?
Can you send me output of ls -l /etc/sysconfig/networking/devices/ifcfg-wlan0.
Created attachment 322698 [details]
Section of /var/log/messages related to creation of connection wlan0
When system-control-network is executed a root, then the GUI will actually come up. However, the wlan0 connection is missing now, whereas it is shown by system-config-network.
The output of 'ls -l /etc/sysconfig/networking/devices/ifcfg-wlan0' reads:
-rw-r--r-- 3 root root 300 2008-11-06 12:54 /etc/sysconfig/networking/devices/ifcfg-wlan0
The issue is not related to SELinux since I have set SELINUX=permissive.
it needs the checkbox
[x] Allow all users to enable and disable the device
otherwise only root can activate it
in the config file:
(In reply to comment #5)
> it needs the checkbox
> [x] Allow all users to enable and disable the device
> otherwise only root can activate it
> in the config file:
Sure, but that does not explain why system-control-network would crash when there is a configured wlan0 connection. Only ppp0 is allowed to be enabled and disabled by ordinary users here, but not so eth0 or eth1. Likewise wlan0 is not supposed to be controlled by a non-root user on my system.
Moreover, I had actually launched system-control-network as root when the wlan0 connection did still not show up, although the necessary rights where granted. An ordinary would never see the GUI because the applications crashes before.
hmpf, yes, it should not crash.
ifcfg-wlan0 is supposed to be readable. key-wlan0 only for root.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
Hm, I could reproduce this, but once I wrote smth to ifcfg-wlan0 it suddenly started to work - maybe there is smth wrong with ACLs of the file, can you send me output of $ getfacl ifcfg-wlan0 ?
No change for system-config-network-1.5.94-2.fc10.
(In reply to comment #9)
$ getfacl ifcfg-wlan0
# file: ifcfg-wlan0
# owner: root
# group: root
This is a regression from F9.
I have exactly the same problem, but with wireless device eth1.
From the backtrace it looks like that system-control-network is trying to open the file /etc/sysconfig/networking/devices/ifcfg-eth1 in write mode, that's why it works only if started by root.
Yes, you're right, it tries to write to the file. I've removed this unnecessary write and this should be fixed with the next version.
I'd like to test the fix, which version should I try?
Care for beta test?
(In reply to comment #15)
> Care for beta test?
Work for me, thanks!
Can you please release official updated packages?
system-config-network-1.5.95-1.fc10 has been submitted as an update for Fedora 10.
*** Bug 477823 has been marked as a duplicate of this bug. ***
system-config-network-1.5.95-1.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 518780 has been marked as a duplicate of this bug. ***