Hi Daniel,
The logic of the test is as follows:
If checks if you *have* a wireless connection at the point of running
the test with 'nmcli -f SSID,ACTIVE dev wifi list'
For you this should be 'wiberg.nu'
It then uses this to get the connection from the list of existing ones,
and here's the
I'll test this as soon as I get home from work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/877752
Title:
wireless_before_suspend failed
To manage notifications about this bug go to:
After a little modification your solution seams to work, type must also be
included:
conn=$(nmcli -t -f UUID,TYPE,NAME con list | grep wireless | grep -e $ap$ |
awk -F\: '{print $1}')
I'll see if the result shows up on friendly.ubuntu.com soon.
I think this would be a good fix as it's not too
The attachment Patch to only look for wireless connection. of this bug
report has been identified as being a patch. The ubuntu-reviewers team
has been subscribed to the bug report so that they can review the patch.
In the event that this is in fact not a patch you can resolve this
situation by
Results are up on friendly.ubuntu.com now, I think it works,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/877752
Title:
wireless_before_suspend failed
To manage notifications about this bug go
Hi Daniel,
Yes, thanks for catching the missing TYPE. We'll schedule this fix for
an SRU and it will also be included in Precise.
** Changed in: checkbox (Ubuntu)
Status: New = Confirmed
** Changed in: checkbox (Ubuntu)
Assignee: (unassigned) = Brendan Donegan (brendan-donegan)
**
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/877752
Title:
wireless_before_suspend failed
To manage notifications about this bug go to:
Based on discussion with the original reporter, it seems eth0 was
mentioned by the wireless_before_suspend test, this leads me to believe
that at the time of running the test, eth0 was connected and maybe the
wireless interface wasn't. Another possibility was that some other
wireless connections
[danne@danne-fnuttbook] ~/Downloads nmcli con
NAME UUID TYPE
TIMESTAMP-REAL
Auto Dannes Nalle 232a0551-6baf-400f-ae87-016f1fddb87c
802-11-wireless Fri 23 Sep 2011 08:07:26 AM CEST
Auto
I tried removing all but the active wireless connection, but it didn't
help. But I noticed that the test before and after suspend seems to
disconnect the wireless, so I think the problem is that the test script
disconnects the wireless and then reports it as not functioning. I will
do the same
10 matches
Mail list logo
