Red Hat Bugzilla – Bug 137617
kwireless reports no network when session is resumed or network restarted
Last modified: 2008-08-02 19:40:33 EDT
Description of problem:
Kwireless reports no connection when there actually is one. This
happens when a session is started where kwireless was in use in the
previous session or when kwrireless is in the system tray.
I'm using ndiswrapper version 0.11. It has worked well for me with no
Version-Release number of selected component (if applicable):
How reproducible: Every time.
Steps to Reproduce:
1. Install kwireless in the tray. Log out. Log in. Will show no
3. /etc/init.d/network restart.
kwireless goes black with a red x through it even though wlan0 is work
ing fine. By working fine I mean that the restart script reported
success and you can surf the internet.
kwrireless should report a good connection and it strength, etc.
It worked fine in FC3T3. I was happy to see it as a standard
component. It kicks the Windows equivalent ! I can't wait to use it
with the sound feedback for finding good signals.
I should add some more information to this report:
a) I am running KDE, not gnome.
b) If I right click quit the kwireless appl. in the tray and start a
new one, it shows the network working like it should. kwireless
works, it just doesn't find the network at the start of a session.
c) kwireless is trying to find the connection, ie it flickers about
once every 2 seconds and refreshes the no network found text.
This appears to work properly with kernel 2.6.9-1.649.
This is still an isse with 2.6.9-1.649
The issue described occurs with smp kernels. I am testing FC3rc3
with a HP ZD7000 laptop which has a dual core P4 processor. When I
boot a smp kernel, info center shows 2 processors running. Kwireless
works fine with a non smp kernel.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
This issue seems to be resolved. It can be closed as far as I am concerned.