> I checked it out and it was because that my WPA-key was 64 chars long,
> not 63.
Ah, if you are using 64 characters long passphrase it means that it's
the actual key and hashing is not used. So this is either a bug in
indicator-network or in connman, that needs to be investigated.
> Changed it and now it works like a charm.
Nice to know.
> Although you might make these errors visible for the user. I did not
> get any kind of notification at all regarding the connection.
This is bad and needs to be fixed as well.
> ** Changed in: indicator-network (Ubuntu) Status: New => Invalid
Actually I'm going to reopen the bug because I think this is a valid
bug.
Daniel Holm <email address hidden> writes:
> I checked it out and it was because that my WPA-key was 64 chars long,
> not 63.
Ah, if you are using 64 characters long passphrase it means that it's
the actual key and hashing is not used. So this is either a bug in
indicator-network or in connman, that needs to be investigated.
> Changed it and now it works like a charm.
Nice to know.
> Although you might make these errors visible for the user. I did not
> get any kind of notification at all regarding the connection.
This is bad and needs to be fixed as well.
> ** Changed in: indicator-network (Ubuntu) Status: New => Invalid
Actually I'm going to reopen the bug because I think this is a valid
bug.
Daniel, thank you for your efforts.
--
Kalle Valo