Tested to work with dhclient in edgy-proposed. Does not cause
regressions in wlassistant functionality from Edgy.
Ready to go into -updates after the seven day waiting period.
--
wireless assistant does not connect in edgy
https://launchpad.net/bugs/64841
--
ubuntu-bugs mailing list
Steve,
As we discussed on IRC, it looks like that usleep() is actually
superfluous. dhclient goes into the background only after it's done the
right thing.
Please update the status of this bug report to Fix Committed when the
appropriate package lands in -proposed. You may opt to keep that
** Changed in: wlassistant (Ubuntu)
Status: In Progress = Fix Committed
--
wireless assisant does not connect in edgy
https://launchpad.net/bugs/64841
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Simon,
I'm opting to keep the usleep() for the moment, just to save the hassle
of preparing another upload. I have set the bug report to Fix Commited,
as 0.5.5-0ubuntu3.1 has landed in edgy-proposed.
--
wireless assisant does not connect in edgy
https://launchpad.net/bugs/64841
--
ubuntu-bugs
Steve,
I'm a little concerned about that usleep() in the patch, as there could
be a race in there. A slow machine could fail.
Is there some better way you could ensure that dhclient has done the
Right Thing? Like wait for it to exit properly?
--
wireless assisant does not connect in edgy
Simon,
Unfortunately, you can't check if dhclient has done the Right Thing,
since it daemonizes, and stays put in the background. The value of 150ms
was picked since there was a call to usleep in the code that specified
it, and I shifted it to be called just after dhclient. I see your point,
Accepted into edgy-proposed. Steve, please notify the QA team via Simon
Law to verify that this bug has been fixed and that there are no
regressions.
Please also upload a similar fix with a newer version number to Feisty.
At some point, I would prefer that the messy textual check for
dhclient's
I was planning on fixing this issue by changing the patch to dhclient to
not complain about stale PID files. However, after I did that, it became
apparent that wlassistant had further problems, and I made the decision
that it would be easier to make wlassistant just cope with dhclient
complaining,
wlassistant 0.5.5-0ubuntu4 has been uploaded to Feisty, and has built on
all arches.
--
wireless assisant does not connect in edgy
https://launchpad.net/bugs/64841
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
So for us newbie users, what does this mean? Is there a patch uploaded?
How do I fix the wireless problem?
Thanks.
EB
--
wireless assisant does not connect in edgy
https://launchpad.net/bugs/64841
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
In the Adept Package Manager, navigate to 'Manage Repositories' and add
'deb http://archive.ubuntu.com/ubuntu edgy-proposed main restricted' and
then update your sources. That should show updates to among other
things, wlassistant. If you could please comment here on whether or not
it solves the
Added the repository and updated wlassistant.
* Booting the system with dhcp and a network defined lasts long and does not
connect (static works)
* Deactivating the module and reinserting does not connect
* Using wlassistant not works perfectly
In my opinion the patch is ok but there is another
Disconnected active connection.
Reconnected repeatedly and successfully to access point with MANUAL SETTINGS.
Attempts to reconnect to a different access point (set to automatic)
repeatedly failed.
Manual works, automatic (DHCP) most likely not.
Furthermore: Upon manual reconnection the
Thanks for sorting out the patch, but I think this says that there are
problems with the Kubuntu QA process.
Personally I would consider this bug a release blocker.
In the modern world, internet connectivity is probably the most
important function of a laptop.
--
wireless assisant does not
Patch looks excellent, testing among Kubuntu developers is successful,
subscribing ubuntu-sru to review. (Patch and description in comment
from Steve Kowalik at 2006-11-13 12:16:40GMT.)
--
wireless assisant does not connect in edgy
https://launchpad.net/bugs/64841
--
ubuntu-bugs mailing list
Finally some very good news indeed.
Now a question from a non-programmer and Linux -Wannabe:
How does one apply this patch to an existing 6.10 installation?
I know the very basics of Unix/Linux but my 'Unix for Dummies' says
nothing about applying a patch and debdiffs!
--
wireless assisant
I have also worked on this, and have a patch that somewhat encompasses
Ryan's changes, but also makes wlassistant work for me. There is in fact
more than one problem, and I'm sure that the second and third problems
would have come up during testing.
The problems:
1. wlassistant fires off
Let me ask a naive question that sounds pushy but is not intended as
such. This bug is listed as 'High' in importance and was first reported
10/9/06, over a month ago. However, I see that no one has been assigned
to fix the bug. Is that typical or normal under these circumstances?
Is there work
Changes from Medium to High has been made a few days/weeks ago... ;-)
My ugly workaround was to use wpa_supplicant for network I know (home,
professional, etc) so that I do not need wlanassistant except when I'm
out of home/office ;-)
--
wireless assisant does not connect in edgy
This bothers me too, so I sat down this morning and made an ugly hack
that causes wlassistant to ignore the message about pid files. Anyway,
afterwards I was able to connect to networks. I'm not really sure how to
make patches, so if I did it wrong, oops.
** Attachment added: patch to
After upgrading to Edgy I've started experiencing unusually long boot
times. I suspect that is is caused by the failure of the network
initialization. Is it possible to just ignore that init step and still
be able to connect throught iwconfig dhclient? If so, how can I do
that?
--
wireless
None of the 'fixes' and workarounds work reliably, including mine.
On booting the connection is established and works for a while but then decides
to quit.
Once that happens, I can restore it sometimes using one or the other of the
suggested solution.
Simply re-booting appears to be the best of
** Changed in: wlassistant (Ubuntu)
Importance: Undecided = High
--
wireless assisant does not connect in edgy
https://launchpad.net/bugs/64841
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Jozo in #ubuntu-devel pointed out this in Debian, which could be
related:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375551 wlassistant:
Wrong call to dhclient
--
wireless assisant does not connect in edgy
https://launchpad.net/bugs/64841
--
ubuntu-bugs mailing list
From #ubuntu-devel:
StevenK I know what is going on.
[06:16] StevenK wlassistant fires off dhclient, which complains about a zero
length PID file on stderr. wlassistant takes any output on stderr as being a
problem, and so kills dhclient.
[06:17] StevenK The bug can be worked around in
Further to the comment of M. Torres and pursuant to my remarks: I should have
kept my mouth shut.
Everything worked fine until I posted my last confirmation of the workaround.
Trouble started thereafter.
I still get connected over 95% of the time on booting up. However, if I
work too many
Confirmed here. I must add that it eventually works :
Just fire up WLAssistant and connect. It will say connection error. Just
let it be. After a while you'll be connected. Weird.
I'm also concerned that this bug doesn't have a priority assigned yet.
It is a MAJOR bug for laptop people!
--
I can now confirm that my workaround posted on 11/01/06 does indeed work
for my installation of Kubuntu 6.10. I have been using the modified
'interfaces' file since then and performed a great number of cold boots
as well as regular boot sequences.
The computer boots with the wireless connection
Confirmed here. sudo ifup eth1 works perfectly, with the appropriate
iwconfig setup for my network. Disappointing, since this worked
perfectly last week with Dapper...
--
wireless assisant does not connect in edgy
https://launchpad.net/bugs/64841
--
ubuntu-bugs mailing list
Kubuntu 6.10 has wireless work flawlessly after initial installation.
It gets lost after several boot sequences.
The workarounds suggested above did not work in my case.
I have Kubuntu 6.06 installed on the same computer. I therefore copied
the contents of /etc/networks/interfaces from Kubuntu
I think I may have found the cause of the wlassistant not working in
Edgy. I have noticed the same problem as well, but I didn't use
wlassistant to configure my connection. I just edited the
/etc/network/interfaces file so the wifi part reads:
auto wlan0
iface wlan0 inet dhcp
wireless-essid
Strange as my bug (65153 - bundle with knot3) was set as Medium for
importance...
I'm a little upset/disappointed with edgy flavour as it looks it's not
as reliable as dapper... :-/
--
wireless assisant does not connect in edgy
https://launchpad.net/bugs/64841
--
ubuntu-bugs mailing list
*sigh* Now Edgy has been released with this bug. It wasn't a bug a
month ago around Knot3 or so. Could we at least get an importance
assigned to this? (In Debian we can do that ourselves...)
--
wireless assisant does not connect in edgy
https://launchpad.net/bugs/64841
--
ubuntu-bugs
** Bug 65153 has been marked a duplicate of this bug
--
wireless assisant does not connect in edgy
https://launchpad.net/bugs/64841
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Ditto. However, when I first upgraded from Dapper to Edgy a few weeks
ago, this problem did not occur.
Attached is the console output that shows that while wlassistant fails
to run dhclient properly, running dhclient manually works fine.
--
wireless assisant does not connect in edgy
...oops...forgot to check that little box, even though the file got
uploaded...
** Attachment added: console output
http://librarian.launchpad.net/4808783/console%20log
--
wireless assisant does not connect in edgy
https://launchpad.net/bugs/64841
--
ubuntu-bugs mailing list
The dupe was confirmed, so this should be too. I can confirm it
personally, anyway. :)
** Changed in: wlassistant (Ubuntu)
Status: Unconfirmed = Confirmed
--
wireless assisant does not connect in edgy
https://launchpad.net/bugs/64841
--
ubuntu-bugs mailing list
In my case, I just need to do sudo dhclient eth3,
See https://launchpad.net/bugs/65153
--
wireless assisant does not connect in edgy
https://launchpad.net/bugs/64841
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
38 matches
Mail list logo
