Bug 420995

(In reply to comment #0 from Joop Beris)
> It is possible to configure the network manually using KNetworkmanager.

Could you please elaborate?
Does KNM show networks if you create a new connection?

No unfortunately, KNM doesn't show new networks or any networks for that matter. When creating a new wireless connection, the list of available networks is completely empty. Scanning with the "iwlist" command does show several available networks in the area, with above 50% signal strength.

When no network cable is plugged in, KNM will report there is no carrier for eth0. But when a cable is plugged in, nothing happens. KNM just sits in the tray and makes no attempt to configure the network.
I can use KNM to manually set up the wired network (enter static IP, etc.), at which point it saves the configuration correctly, and I can reuse that configuration later, when a cable is plugged in.

I also have one wireless network configuration saved. However, that doesn't connect when I select it, even when I know the network is in range, online, available and the pass phrase is correct.

Hope that answers your question. If not, feel free to ask more. If I can help/test anything, also please let me know.

Could you please attach the output of "nm-tool" when KNM does not show any networks?

What happens if you restart KNetworkManager?

Is NetworkManager running (ps aux | grep NetworkManager)?

Did you install all online update (just attach the output of "rpm -qa --changelog NetworkManager-kde")?

> I can use KNM to manually set up the wired network (enter static IP, etc.), at
> which point it saves the configuration correctly, and I can reuse that
> configuration later, when a cable is plugged in.

Did you check the checkbox "Auto connect"?

Created attachment 236722 [details]
Output of nm-tool

Created attachment 236723 [details]
NetworkManager-kde changelog as per rpm -qa --changelog NetworkManager-kde

> Could you please attach the output of "nm-tool" when KNM does not show any
> networks?

Done, see comment #4

> What happens if you restart KNetworkManager?

No change.

> Is NetworkManager running (ps aux | grep NetworkManager)?

Yes, it is running.

> Did you install all online update (just attach the output of "rpm -qa
> --changelog NetworkManager-kde")?

Done, see comment #5

> > I can use KNM to manually set up the wired network (enter static IP, etc.), at
> > which point it saves the configuration correctly, and I can reuse that
> > configuration later, when a cable is plugged in.
> 
> Did you check the checkbox "Auto connect"?

No, I didn't. I have done so now, and will tell you if it makes a difference. 

(In reply to comment #6 from Joop Beris)
> > Could you please attach the output of "nm-tool" when KNM does not show any
> > networks?
>
> Done, see comment #4

Well, NetworkManager does not see any access points too.
Not sure why. Tambet, any idea?

NM can't start wpa_supplicant for some reason. Try to run the Exec= line from 
/usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service file as root. If this works, it's a DBus activation error. If not, it's some sort of wpa_supplicant issue (wrong command line, missing libs, ...).

(In reply to comment #8 from Tambet Ingo)
> NM can't start wpa_supplicant for some reason. Try to run the Exec= line from 
> /usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service file
> as root. If this works, it's a DBus activation error. If not, it's some sort of
> wpa_supplicant issue (wrong command line, missing libs, ...).
> 

Okay, the Exec= line and it's output:

# Exec=/usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log
bash: -c: command not found

I guess that means that I have a wrong command line in that file. Any input as to what I should change it to?

> # Exec=/usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u
> -f /var/log/wpa_supplicant.log
> bash: -c: command not found

Please retry that without "Exec=" (that's not needed for manual execution), just "/usr/sbin/wpa_supplicant ...".

(In reply to comment #10 from Helmut Schaa)
 
> Please retry that without "Exec=" (that's not needed for manual execution),
> just "/usr/sbin/wpa_supplicant ...".
 
Of course! Sorry, shouldn't be doing two things at the same time. 
Okay, here is what happens with the CORRECT command:

# /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: No such file or directory
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable

Then it seems to hang. Nothing else happens.
So I stop with CTRL+C and I get one most line of output:

WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported

Created attachment 236766 [details]
wpa_supplicant.log after running the command specified

Figured you'd want to see this, so here is the wpa_supplicant.log

Could you please attach /var/log/NetworkManager?

Created attachment 237758 [details]
Networkmanager logfile (edited slightly for protection of certain networks)

I replaced some text and IP numbers with asterisk (*) characters, to protect a certain network. This should not be a problem, I think.

(In reply to comment #14 from Joop Beris)
> Created an attachment (id=237758) [details]
> Networkmanager logfile (edited slightly for protection of certain networks)
> 
> I replaced some text and IP numbers with asterisk (*) characters, to protect a
> certain network. This should not be a problem, I think.
> 

Forgot to remove "NEEDINFO"

Ok, it really seems like NM cannot start wpa_supplicant for some reason.
Could you please try the following:

Stop NM and wpa_supplicant:
$ rcnetwork stop
$ killall wpa_supplicant 

Try to start wpa_supplicant using system-bus-activation:
$ dbus-send --system --dest=fi.epitest.hostap.WPASupplicant  /fi/epitest/hostap/WPASupplicant fi.epitest.hostap.WPASupplicant.getInterface

Check if wpa_supplicant is active now:
$ ps aux | grep wpa_supplicant

If it is not running the system-bus-activation somehow failed.

(In reply to comment #16 from Helmut Schaa)

I tried the suggestions you mentioned above, however, after doing so, "ps aux | grep wpa_supplicant" results in zero processes being listed. So even through dbus, it's not possible to start wpa_supplicant.

> If it is not running the system-bus-activation somehow failed.

If you say so... :-)

Please let me know what else I can try.

Please run the test again but add "--print-reply" to the dbus-send call and attach the output here.

$ dbus-send --print-reply --system --dest=fi.epitest.hostap.WPASupplicant 
/fi/epitest/hostap/WPASupplicant fi.epitest.hostap.WPASupplicant.getInterface

Here it is:

# dbus-send --print-reply --system --dest=fi.epitest.hostap.WPASupplicant /fi/epitest/hostap/WPASupplicant fi.epitest.hostap.WPASupplicant.getInterface
Error org.freedesktop.DBus.Error.Spawn.PermissionsInvalid: The permission of the setuid helper is not correct

Interesting, it says permissions for the setuid helper are not correct...

Thanks. Seems like a dup of bug #375155 to me. Could you please verify that?

(In reply to comment #20 from Helmut Schaa)
> Thanks. Seems like a dup of bug #375155 to me. Could you please verify that?

Reading that bug, I agree it looks quite similar. I have tried the following from the thread about that bug:

# ls -al `rpm -ql dbus-1|grep launch`
-rwxr-x--- 1 root messagebus 47356 2008-06-06 23:20 /lib/dbus-1/dbus-daemon-launch-helper

I have my permission set according to /etc/permissions.secure as supplied by openSUSE. The only thing I have set in /etc/permissions.local is:

# Checking and installing patches should work for mere mortals
/usr/sbin/zypp-checkpatches-wrapper     root:root       4755
/usr/sbin/zypp-refresh-wrapper          root:root       4755

Permissions in the openSUSE security setting files are as follows:
# grep dbus-1 /etc/permission*
/etc/permissions.easy:# dbus-1 (#333361)
/etc/permissions.easy:/lib/dbus-1/dbus-daemon-launch-helper                   root:messagebus   4750
/etc/permissions.easy:/lib64/dbus-1/dbus-daemon-launch-helper                 root:messagebus   4750
/etc/permissions.paranoid:# dbus-1 (#333361)
/etc/permissions.paranoid:/lib/dbus-1/dbus-daemon-launch-helper                   root:messagebus   0750
/etc/permissions.paranoid:/lib64/dbus-1/dbus-daemon-launch-helper                 root:messagebus   0750
/etc/permissions.secure:# dbus-1 (#333361)
/etc/permissions.secure:/lib/dbus-1/dbus-daemon-launch-helper                   root:messagebus   0750
/etc/permissions.secure:/lib64/dbus-1/dbus-daemon-launch-helper                 root:messagebus   0750

Doing: 
# chmod u+s /lib/dbus-1/dbus-daemon-launch-helper
enables me to scan for networks and allows me to connect.
So far so good...until the next time the security settings are updated...

And indeed, when setting permission, it goes:

Executing /sbin/conf.d/SuSEconfig.permissions...
Checking permissions and ownerships - using the permissions files
        /etc/permissions
        /etc/permissions.secure
        /etc/permissions.d/mail-server
        /etc/permissions.d/postfix
        /etc/permissions.local
setting /lib/dbus-1/dbus-daemon-launch-helper to root:messagebus 0750. (wrong permissions 4750)

So the permissions as supplied by openSUSE disable the scanning for networks.

Looks like a duplicate bug to me.

(In reply to comment #21 from Joop Beris)
> Looks like a duplicate bug to me.

Ok, I'll close this one as a duplicate of #373654 now although that one is already marked as FIXED.

*** This bug has been marked as a duplicate of bug 373654 ***

(In reply to comment #22 from Helmut Schaa)
> (In reply to comment #21 from Joop Beris)
> > Looks like a duplicate bug to me.
> 
> Ok, I'll close this one as a duplicate of #373654 now although that one is
> already marked as FIXED.
> 
> *** This bug has been marked as a duplicate of bug 373654 ***
> 

That's fine by me, I can set the needed permissions through /etc/permissions.local.

Thanks for the help!