fixed: https://github.com/cyphermox/urfkill/pull/6
** Changed in: urfkill (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1325578
Title:
One suggestion I would make it adding a script to the urfkill that
allows the killswitches to be enumerated? We also could add a switch to
the existing 'enumerate' script to allow it to dump the killswitch
states.
Also a monitor-rfkill script would be helpful too.
--
You received this bug
OK, just as an demonstration how to reproduce the urfkill problem:
1. flash a device
2. check that flightmode is off and wifi is on
3. enable flightmode
after this rfkill list shows as expected:
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
1: hci0: Bluetooth
Will try to some logs today.
But please note that this bug is about URfkill.Killswitch objects, not Devices.
So the thing to verify and test is that the Killswitch states match what
urfkill list is telling:
dbus-send --system --print-reply --dest=org.freedesktop.URfkill
@Antii
I assume you meant verify that urfkill's Killswitch states match what
rfkill list outputs?
I will try and re-test today as well.
That said, as we previously discussed, you need to provide a scenario
that's reproducible using the UI. I tried testing your proposed flight
mode changes in
there was a breakage with libstdc++ on our repository earlier today, so
I could not do more testing. I will get back to this later todayy and
provide more data.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Does the indicator still read the state of WiFi from NM, or does it now
use urfkill?
I flash/wiped u81 on my mako this morning, installed all of the packages
from the silo ( except for system-settings which has a newer version
available ), and ran some tests.
The first problem I encountered was
As for the initial description, when I manually block WLAN using rfkill
block wlan, I do in fact see a DeviceChanged signal for the WiFi
device, and if I run urfkill's enumerate script urfkill does have the
correct state. Note, I edited the output from enumerate below to only
show the WiFi
** Changed in: urfkill (Ubuntu)
Status: New = Incomplete
** Changed in: urfkill (Ubuntu)
Assignee: (unassigned) = Antti Kaijanmäki (kaijanmaki)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
there is a silo now that adds flightmode toggles to indicator-network and
system-settigns that eases the debugging of this:
https://launchpad.net/~ci-train-ppa-service/+archive/landing-002/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
when testing, make sure you have swiped the greeter away before trying
to use the indicator.
Couple of things to try:
1) enable flight mode
2) enable wifi
3) disable flight mode
and repeat.
At some point the Killswitch objects states get out of sync between what
rfkill list reports.
You can
+ you can also request the states from killswitches by doing:
dbus-send --system --print-reply --dest=org.freedesktop.URfkill
/org/freedesktop/URfkill/WLAN org.freedesktop.DBus.Properties.Get
string:org.freedesktop.URfkill.Killswitch string:state
--
You received this bug notification because
12 matches
Mail list logo
