Bug 470203 - system-control-network crashes at start-up when a wireless device is configured
Summary: system-control-network crashes at start-up when a wireless device is configured
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-network
Version: 10
Hardware: noarch
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 477823 518780 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-06 09:17 UTC by Joachim Frieben
Modified: 2009-08-25 22:35 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-14 00:49:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Backtrace of system-control-network when a wireless device has been configured (1.40 KB, text/plain)
2008-11-06 09:17 UTC, Joachim Frieben
no flags Details
Section of /var/log/messages related to creation of connection wlan0 (2.05 KB, text/plain)
2008-11-06 11:52 UTC, Joachim Frieben
no flags Details

Description Joachim Frieben 2008-11-06 09:17:36 UTC
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):
system-config-network-1.5.94-1.fc10.noarch

How reproducible:
Always.

Steps to Reproduce:
1. Launch system-control-network from the shell.
  
Actual results:
Application crashes immediately.

Expected results:
Application starts as expected.

Additional info:
- 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.

Comment 1 Jiri Moskovcak 2008-11-06 09:56:31 UTC
Hm, that's weird, aren't there any selinux denials?
Can you send me output of ls -l /etc/sysconfig/networking/devices/ifcfg-wlan0.

Thanks,
Jirka

Comment 2 Joachim Frieben 2008-11-06 11:52:54 UTC
Created attachment 322698 [details]
Section of /var/log/messages related to creation of connection wlan0

Comment 3 Joachim Frieben 2008-11-06 11:56:32 UTC
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.

Comment 4 Joachim Frieben 2008-11-06 11:58:48 UTC
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.

Comment 5 Harald Hoyer 2008-11-06 12:57:20 UTC
it needs the checkbox 
[x] Allow all users to enable and disable the device

otherwise only root can activate it

in the config file:
USERCTL=yes

Comment 6 Joachim Frieben 2008-11-06 15:30:36 UTC
(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:
> USERCTL=yes

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.

Comment 7 Harald Hoyer 2008-11-06 16:04:25 UTC
hmpf, yes, it should not crash.

ifcfg-wlan0 is supposed to be readable. key-wlan0 only for root.

Comment 8 Bug Zapper 2008-11-26 04:51:33 UTC
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:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Jiri Moskovcak 2008-11-28 12:52:23 UTC
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 ?

Thanks,
Jirka

Comment 10 Joachim Frieben 2008-11-29 07:17:46 UTC
No change for system-config-network-1.5.94-2.fc10.

Comment 11 Joachim Frieben 2008-11-29 07:19:50 UTC
(In reply to comment #9)
$ getfacl ifcfg-wlan0
# file: ifcfg-wlan0
# owner: root
# group: root
user::rw-
group::r--
other::r--

Comment 12 Nicola Soranzo 2008-12-02 21:23:55 UTC
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.

Comment 13 Jiri Moskovcak 2008-12-08 15:18:41 UTC
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.

Thanks,
Jirka

Comment 14 Nicola Soranzo 2008-12-12 12:08:34 UTC
I'd like to test the fix, which version should I try?

Thanks!

Comment 17 Nicola Soranzo 2008-12-14 11:38:57 UTC
Can you please release official updated packages?
Thanks again

Comment 18 Fedora Update System 2008-12-17 12:58:03 UTC
system-config-network-1.5.95-1.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/system-config-network-1.5.95-1.fc10

Comment 19 Jiri Moskovcak 2008-12-24 10:57:56 UTC
*** Bug 477823 has been marked as a duplicate of this bug. ***

Comment 20 Fedora Update System 2009-01-07 09:06:21 UTC
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.

Comment 21 Christoph Wickert 2009-08-25 22:35:35 UTC
*** Bug 518780 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.