oem-qa team mailing list archive

[Brandon Williams <opensource@xxxxxxxxxxxxx>]

I am not confident that aircraft-manager-5 actually works to disable the
radios, which is the important part where battery use and aircraft
restriction compliance is concerned. That's why the author switched to
the other method in later version, and why the belmont11 version is the
one shipped on the mini.

I updated the packaging of the belmont11 version so that it can be
installed in Jaunty. The only changes that I made were to the
debian/control and debian/rules files. No code changes were required.
You can install it from my PPA: https://launchpad.net/~opensource-
subakutty/+archive/ppa/.

Hopefully, the maintainer will adopt my packaging changes.

Please note that the Jaunty version will only enable and disable the
radios. It will not disable wireless in network-manager. The dbus method
that aircraft-manager uses for enabling and disabling wireless in
network-manager does not appear to work in Jaunty. I would be happy to
update the utility if someone can tell me an alternate command to run.

-- 
Failure using Aircraft-Manager with Jaunty UNR
https://bugs.launchpad.net/bugs/357412
You received this bug notification because you are a member of OEM
Services QA, which is subscribed to The Dell Mini Project.

Status in Dell Inspiron Mini with Custom Dell UI: Invalid
Status in Ubuntu Netbook Remix: New

Bug description:
I am not sure if this should be bug or a wishlist. BUT aircraft-manager crashes miserably when I add the package to a Jaunty Ubuntu-Netbook-Remix. I wanted that aircraft manager installed to turn off and on my bluetooth support mostly.

I did dig into the code of aircraft manager and discovered two incompatibilities with the UNR live image for Jaunty. First the kernel is missing a module called hci_usb which may explain why bluetooth notification icon does not appear. I know this cause I ran the command that this app ran directly in a terminal. 

Second the d-bus messages for network manager appear to have changed which does explain why it crashes in the first place. I know this cause it spews "dbus.exceptions.DBus Exceptions: org.freedesktop.DBus.Error.UnknownMethod: Method "getWirelessEnabled" with signature "" on interface ("null") doesn't exist. This method is called with getWifiState() on line 300 of aircraft-manager.

As I said I am unsure how this should be handled :/ but I think that aircraft-manager should be usuable in Jaunty even if the entire mini9 package set stays with Hardy. It seems only common sense to keep those brave mini9 users happy.