I agree 100% with Paul;
I preffer a slower rate on new releases than this mess of unsolved bugs on LTS
editions...
how can we serioulsy consider an LTS edition if bugs are only solved on
new releases forcing us to upgrade when what we really want is
stability???
--
wpasupplicant doesn't start w
Thanks to everyone who figured this bug out. I installed backported
versions of ifupdown and netbase from Intrepid and this specific problem
seems to be solved for me.
However, after having to hunt down the apparent cause of the problem
(useless wlan0 interface being brought up at boot which does
Thanks, Kel and Reinhard. Sorry I didn't reply or send the patch
earlier; the Easter holidays slowed me down somewhat (I was in a tearing
hurry on Thursday to get everything done). Thanks a lot for the merge -
I appreciate the work.
Good catch regarding the D-Bus service. I've uploaded the attache
On Friday 10 April 2009 22:50:44 Reinhard Tartler wrote:
> kelmo writes:
>
> >> https://launchpad.net/~cjwatson/+archive/ppa
> >>
> >> ... to install the wpasupplicant package from there, and report whether
> >> it fixes this bug? This test is only valid if you're already running up-
> >> to-d
kelmo writes:
>> https://launchpad.net/~cjwatson/+archive/ppa
>>
>> ... to install the wpasupplicant package from there, and report whether
>> it fixes this bug? This test is only valid if you're already running up-
>> to-date Jaunty.
>>
>
> Any chance I could see a diff so that divergence be
On Thursday 09 April 2009 02:37:37 Colin Watson wrote:
> Could people affected by this bug who are running up-to-date Jaunty
> systems please follow the directions at:
>
> https://launchpad.net/~cjwatson/+archive/ppa
>
> ... to install the wpasupplicant package from there, and report whether
>
I confirm that the bug is fixed in jaunty with wpasupplicant
0.6.6-2ubuntu1 . Extreme thanks to Colin Watson, Steve Langasek and all
other people that helped this bug to get fixed.
--
wpasupplicant doesn't start when the network start
https://bugs.launchpad.net/bugs/44194
You received this bug no
This bug was fixed in the package wpasupplicant - 0.6.6-2ubuntu1
---
wpasupplicant (0.6.6-2ubuntu1) jaunty; urgency=low
* Operate reasonably when /var is not yet mounted read-write (LP: #44194):
- 07_syslog.patch: Backport syslog logging support from upstream.
- 08_syslog_su
With Steve Langasek's agreement as release manager, I'm going to go
ahead and upload my changes to Jaunty even though we haven't yet
confirmed that they fix the original bug. Lars Wirzenius reported that
my package at least doesn't break his use of WPA, so I don't think I've
gone too badly wrong. I
** Changed in: wpasupplicant (Ubuntu Jaunty)
Status: Triaged => In Progress
** Changed in: wpasupplicant (Ubuntu Jaunty)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
wpasupplicant doesn't start when the network start
https://bugs.launchpad.net/bugs/44194
You received this bug
Could people affected by this bug who are running up-to-date Jaunty
systems please follow the directions at:
https://launchpad.net/~cjwatson/+archive/ppa
... to install the wpasupplicant package from there, and report whether
it fixes this bug? This test is only valid if you're already running
Colin: I agree. A smart card is generally used to identify a user. So it
is a good idea to use it to mount a home directory. But mounting /usr or
/ would using a smart card is a very strange configuration and very
uncommon.
--
wpasupplicant doesn't start when the network start
https://bugs.launch
Stephen: Yes, I think so. I'd be pretty worried about stability of the
LTS release if we did this.
Ludovic: Thanks for the note. What would you recommend? My personal
inclination would be to say that smartcard auth for mounting /usr is
sufficiently niche that we should just not support that, but y
This bug was fixed in the package openssl - 0.9.8g-15ubuntu2
---
openssl (0.9.8g-15ubuntu2) jaunty; urgency=low
* Move runtime libraries to /lib, for the benefit of wpasupplicant
(LP: #44194). Leave symlinks behind in /usr/lib (except on the Hurd)
since we used to set an rpa
Regarding the patch for pcsc-lite (moving libpcsclite.so.1 from /usr/lib
to /usr) it is only a half fix. The smart card support will not be
available since the daemon is still in /usr/sbin/pcscd and will only be
started later (when /usr is available)
You should also:
- move pcscd in /sbin
- move a
Is this fix too involved to be backported to Hardy as well? Hardy is the
current LTS release...
--
wpasupplicant doesn't start when the network start
https://bugs.launchpad.net/bugs/44194
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
** Changed in: openssl (Ubuntu Jaunty)
Status: Triaged => Fix Committed
** Changed in: ifupdown (Ubuntu Hardy)
Status: New => Won't Fix
** Changed in: netbase (Ubuntu Hardy)
Status: New => Won't Fix
** Changed in: openssl (Ubuntu Hardy)
Status: New => Won't Fix
** Ch
** Changed in: openssl (Ubuntu Jaunty)
Importance: Undecided => High
Status: New => Triaged
--
wpasupplicant doesn't start when the network start
https://bugs.launchpad.net/bugs/44194
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscribe
This bug was fixed in the package pcsc-lite - 1.4.102-1ubuntu2
---
pcsc-lite (1.4.102-1ubuntu2) jaunty; urgency=low
* Move runtime libraries to /lib, for the benefit of wpasupplicant
(LP: #44194).
-- Colin WatsonWed, 18 Mar 2009 16:34:28 +
** Changed in: pcsc-lite (Ub
zlib (1:1.2.3.3.dfsg-12ubuntu2) jaunty; urgency=low
* Move zlib.so.* to /lib (LP: #44194).
-- Colin Watson Wed, 18 Mar 2009 16:28:00 +
** Also affects: zlib (Ubuntu)
Importance: Undecided
Status: New
** Also affects: openssl (Ubuntu)
Importance: Undecided
Status: Ne
On Friday 27 February 2009 20:51:41 Colin Watson wrote:
> Having reviewed the whole bug, I have to say that this all seems like an
> order of magnitude more work than is really required. The suggested
> approaches involve lots of complex interface definition, strict ordering
> constraints, and the
Having reviewed the whole bug, I have to say that this all seems like an
order of magnitude more work than is really required. The suggested
approaches involve lots of complex interface definition, strict ordering
constraints, and the need to warn users when they violate constraints.
Why not make i
Drat, I thought I'd corrected it, but probably undid once too far later
in editing. it should read: "Late would run after root is mounted RW
(very likely with all other filesystems being mounted first at this
point)." not RO.
--
wpasupplicant doesn't start when the network start
https://bugs.lau
I think this can probably be decomposed in to a series of problems that
result in this bug:
1) Networking in specific, but all devices in general, should have a way
of specifying if it's an 'initrd', 'early', 'late' or 'later/optional'
type of event. initrd items would be rolled in to the initrd
** Changed in: wpasupplicant (Ubuntu Jaunty)
Assignee: Mathias Gug (mathiaz) => (unassigned)
Target: jaunty-alpha-4 => None
--
wpasupplicant doesn't start when the network start
https://bugs.launchpad.net/bugs/44194
You received this bug notification because you are a member of Ubuntu
** Changed in: wpasupplicant (Ubuntu Jaunty)
Target: jaunty-alpha-2 => jaunty-alpha-4
--
wpasupplicant doesn't start when the network start
https://bugs.launchpad.net/bugs/44194
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
u
** Tags added: regression
--
wpasupplicant doesn't start when the network start
https://bugs.launchpad.net/bugs/44194
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.
On Friday 05 December 2008 05:13:10 Soren Hansen wrote:
> kelmo, you wouldn't read about this bug on Debian's BTS, because it's an
> Ubuntu specific bug. Last I checked Debian hasn't changed its boot
> process to do all this stuff dynamically, i.e. attempt configuration of
> everything you possibly
On Thursday 04 December 2008 20:29:26 Soren Hansen wrote:
> > I disagree to an extent, the problem doesn't sound specific to
> > wpa_supplicant's shell glue at all,
>
> If wpasupplicant tells ifupdown that it's done configuring the
> interface, and that everything went fine, but it that's not actu
By the way, kelmo: Sorry if you felt "I jumped all over your casual
remark". I was simply genuinely surprised why you'd suggest what you
did. ifupdown is a framework (as you say yourself) for doing network
configuration. It leaves everything but the very simple things to a sort
of "modules" in the
kelmo, you wouldn't read about this bug on Debian's BTS, because it's an
Ubuntu specific bug. Last I checked Debian hasn't changed its boot
process to do all this stuff dynamically, i.e. attempt configuration of
everything you possibly can when it's discovered.
--
wpasupplicant doesn't start when
> Glancing at its pre-up script, I'm guessing your problem is this:
>
>> # quit if executables are not installed
>> if [ ! -x "$WPA_SUP_BIN" ] || [ ! -x "$WPA_CLI_BIN" ]; then
>> exit 0
>> fi
> This is a perfectly valid use case when the wpasupplicant package is
> removed but not purged.
I know wh
>>> but rather, the inflexibility of the statically maintained ifupdown
>>> software on an ever evolving Debian/Ubuntu software ecosystem.
>> What exactly do you mean by "statically maintained"?
> WPA keys written to /etc/network/interfaces as outlined in
> /usr/share/doc/wpasupplicant/README.Debia
On Friday 05 December 2008 00:25:02 Reinhard Tartler wrote:
> Soren Hansen <[EMAIL PROTECTED]> writes:
>
> > Glancing at its pre-up script, I'm guessing your problem is this:
> >
> > # quit if executables are not installed
> > if [ ! -x "$WPA_SUP_BIN" ] || [ ! -x "$WPA_CLI_BIN" ]; then
> >
Soren Hansen <[EMAIL PROTECTED]> writes:
> Glancing at its pre-up script, I'm guessing your problem is this:
>
> # quit if executables are not installed
> if [ ! -x "$WPA_SUP_BIN" ] || [ ! -x "$WPA_CLI_BIN" ]; then
> exit 0
> fi
This is a perfectly valid use case when the wpasupplicant pa
Soren Hansen <[EMAIL PROTECTED]> writes:
>> but rather, the inflexibility of the statically maintained ifupdown
>> software on an ever evolving Debian/Ubuntu software ecosystem.
>
> What exactly do you mean by "statically maintained"?
WPA keys written to /etc/network/interfaces as outlined in
/us
> I disagree to an extent, the problem doesn't sound specific to
> wpa_supplicant's shell glue at all,
If wpasupplicant tells ifupdown that it's done configuring the
interface, and that everything went fine, but it that's not actually the
case... That's wrong. No matter how you look at it.
> but
>> Waiting until S40networking is run brings up an issue with iscsi
>> devices. The current way of handling iscsi devices is to treat them
>> as local devices by making sure that all iscsi devices are created
>> before local filesystems are mounted (S35mountall.sh and
>> S30checkfs.sh). That requir
On Tuesday 02 December 2008 16:52:21 Reinhard Tartler wrote:
> Mathias Gug <[EMAIL PROTECTED]> writes:
>
> > Waiting until S40networking is run brings up an issue with iscsi
> > devices. The current way of handling iscsi devices is to treat them as
> > local devices by making sure that all iscsi d
Mathias Gug <[EMAIL PROTECTED]> writes:
> Waiting until S40networking is run brings up an issue with iscsi
> devices. The current way of handling iscsi devices is to treat them as
> local devices by making sure that all iscsi devices are created before
> local filesystems are mounted (S35mountall.
Hi Reinhard,
On Mon, Dec 01, 2008 at 10:49:52PM +0100, Reinhard Tartler wrote:
> Reporters claim this bug to be fixed. What symptoms did recently arise?
>
On the wpa_supplicant front, none. However it raises issue with iscsi
devices as outlined below.
> > It seems that the issue is with the ifup
Just to reiterate my request from earlier: once you've all decided what
exactly this fix should be, can we please have it back-ported to Hardy?
It is supposed to be the LTS release and Wifi is next to unusable
without it.
--
wpasupplicant doesn't start when the network start
https://bugs.launchpa
Mathias Gug <[EMAIL PROTECTED]> writes:
> Reopening this bug in wpa_supplicant.
Reporters claim this bug to be fixed. What symptoms did recently arise?
> It seems that the issue is with the ifupdown script from
> wpa_supplicant.
What is the issue?
> If the script cannot be run early in the boo
Reopening this bug in wpa_supplicant. It seems that the issue is with
the ifupdown script from wpa_supplicant. If the script cannot be run
early in the boot process it should fail gracefully and leave the
interface unconfigured until the networking init script is run. Could
the wpa_supplicant ifupd
I can also confirm Reinhard's fix works on 8.04 if you manually copy in
just the ifupdown.rules and networking files from the patch. Many thanks
Reinhard!
Can we please have this officially backported as an update to 8.04?
--
wpasupplicant doesn't start when the network start
https://bugs.launch
Ditto Ole Jon. On a fresh install of 8.04 using ipw2200. Using pre-up
sleep 10 before any wpa information in /etc/network/interfaces resolved
issue, but what a sloppy workaround.
--
wpasupplicant doesn't start when the network start
https://bugs.launchpad.net/bugs/44194
You received this bug no
Bug confirmed with ipw2200. Installed Wicd (http://wicd.sourceforge.net)
and the Ubuntu-version works like a charm. Wicd uninstalls network-
manager, and do not use /etc/network/interfaces.
--
wpasupplicant doesn't start when the network start
https://bugs.launchpad.net/bugs/44194
You received th
Confirming proper udev behavior after installing updated netbase & ifupdown
over Ubuntu 8.04 system.
Thanks for the fix!
--
wpasupplicant doesn't start when the network start
https://bugs.launchpad.net/bugs/44194
You received this bug notification because you are a member of Ubuntu
Bugs, which i
okay, I've uploaded a very similar patch to what Roman has proposed to
intrepid. I tested the packages in a kvm instance, obviously without
wpasupplicant.
My current guess what's going wrong here:
The udev rules gets activated too early in the boot sequence, most
probably with S10udev, where udev
nothing to do in this bug for wpasupplicant
** Changed in: wpasupplicant (Ubuntu)
Status: Confirmed => Invalid
--
wpasupplicant doesn't start when the network start
https://bugs.launchpad.net/bugs/44194
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
This bug was fixed in the package netbase - 4.30ubuntu2
---
netbase (4.30ubuntu2) intrepid; urgency=low
* introduce flag file for indicating the network has been
configured. This is needed so that ifupdown udev rules does not 'ifup'
the interface too early. Related to LP: #4
This bug was fixed in the package ifupdown - 0.6.8ubuntu9
---
ifupdown (0.6.8ubuntu9) intrepid; urgency=low
* debian/ifupdown.rules: (the udev rule) ensure that the init script
/etc/network/networking has been started to ensure that the udev
script does not start too early i
https://bugs.edge.launchpad.net/ubuntu/+source/wpasupplicant/+bug/44194/comments/10
has the right idea.
** Changed in: ifupdown (Ubuntu)
Assignee: (unassigned) => Reinhard Tartler (siretart)
Status: New => Triaged
--
wpasupplicant doesn't start when the network start
https://bugs.lau
https://bugs.edge.launchpad.net/ubuntu/+source/wpasupplicant/+bug/44194/comments/10
has the righjt idea. I'm going to work on integrating this patch
** Changed in: netbase (Ubuntu)
Assignee: (unassigned) => Reinhard Tartler (siretart)
Status: New => Triaged
--
wpasupplicant doesn't s
** Also affects: netbase (Ubuntu)
Importance: Undecided
Status: New
--
wpasupplicant doesn't start when the network start
https://bugs.launchpad.net/bugs/44194
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mail
captain haddock <[EMAIL PROTECTED]> writes:
> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/40763
> is a (partial) duplicate and confirms the problem for a current Hardy
> Heron install.
It does not. bug #40763 is about an issue in ipw2200. Later in the
bugtrail some user see
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/40763
is a (partial) duplicate and confirms the problem for a current Hardy
Heron install.
--
wpasupplicant doesn't start when the network start
https://bugs.launchpad.net/bugs/44194
You received this bug notification because you
I would like to confirm this bug. I have only started to have problems
with automatic wifi connection since running the Hardy beta. Doing sudo
/etc/init.d/networking restart seems the most convenient way of
overcoming it until there is a proper fix.
--
wpasupplicant doesn't start when the network
I would like to confirm this bug. I have only started to have problems
with automatic wifi connection since running the Hardy beta. Doing sudo
/etc/init.d/networking restart seems the most convenient way of
overcoming it until there is a proper fix.
--
wpasupplicant doesn't start when the network
Yes, apologies guys. This bug got mixed up in a list of other bugs I was
working on. Launchpad appears to have set it to "invalid". Not sure why. I
didn't direct it to do that. I'll be more careful in future.
Again, sorry for causing a bother.
--
wpasupplicant doesn't start when the network sta
Gareth Fitzworthington wrote on 2008-04-05: (permalink)
>This is a Network Manager bug.
>Fix released for Hardy.
This is definitely not a Network Manager bug. I (and others who have
commented on this bug and its duplicates) do not use Network Manager at
all. It is an ifupdown bug that occurs beca
Setting back to confirmed.
Gareth Fitzworthington : This bug exist in latest Hardy beta with all
updates. This is not a duplicate. This bug happens when the wireless
network is configured manually (ex. with a static IP) with WPA/WPA2.
Hardy won't connect to the network at boot, but it will always
Sorry. holding off on duplicate. Anyone trying to use Hidden AP then see Bug
#50214
Also, anything other than "Roaming Mode" pre-Hardy see this comment:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/110187/comments/7
Thanks.
--
wpasupplicant doesn't start when the network start
This is a Network Manager bug.
Fix released for Hardy.
Marking as duplicate.
Any backport requests should be first examined against:
https://help.ubuntu.com/community/UbuntuBackports
Then filed against the main bug stream. Unless this duplicate message is viewed
as errant. In which case please
Some questions and some considerations.
I was wondering what happens if 85-ifupdown.rules is removed. I believe
/etc/init.d/networking would still do its job and networking would work fine.
If a card is removed (or added) udev wouldn't care (dinamically) about the
removal (or addiction), am I wr
Confirmed. Bug also exists with me, patch works. Patch should be
included in Ubuntu 8.04.
--
wpasupplicant doesn't start when the network start
https://bugs.launchpad.net/bugs/44194
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubun
To: Roman Yepishev
Thanks a lot. Your patch works.
--
wpasupplicant doesn't start when the network start
https://bugs.launchpad.net/bugs/44194
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
Dear all,
Today I managed to make it run on boot while maintaining udev support
(i.e. the interface goes down with the card removal and is brought up
when my PCMCIA card is inserted).
First of all (for those who come from earlier releases), looks like udev is
confused a bit with DRIVERS=="?*" te
#45842 seems to be related to this.
--
wpasupplicant doesn't start when the network start
https://bugs.launchpad.net/bugs/44194
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
I can confirm the udev "critical race": removing
/etc/udev/rules.d/85-ifupdown.rules and setting the wireless interface as auto
everything works as intended (interface correctly brought up at boot time by
/etc/init.d/networking).
I can't explane why udev cannot work correctly even if it uses ifu
Alessio Gaeta <[EMAIL PROTECTED]> writes:
> maybe there is some odd interaction with udev rule ifupdown.rules?
> Udev is started before than Networking in the init process and (as far
> as I understood) tries to configure the interfaces it found. So, when
> Networking starts, interfaces are already
I have the same problem too: wpasupplicant doesn't start automatically
at boot and to get a working interface I have to:
$ ifdown eth1 [<--]
$ ifup eth1
So it seems that the network is actually started and configured, only
wpasupplicant refuses to start.
I have only one suspect: maybe there is
since wpasupplicant starts fine when called manually, I hardly think
this is a bug with the package itself but some obscure race condition
with the interaction with ifupdown. I'm therfore reassigning this bug.
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: Unconfirmed
I see the same problem and both workarounds work for me.
But there is another (related?) problem remaining: once connected
(either without workaround and having networking restarted or with one
of the workarounds) it is not possible to restart networking again. The
connection cannot be reestablish
I have the same problem, which I believe is also the one reported here:
http://ubuntuforums.org/showthread.php?p=1307027
Moving the wpa config out into a separate configuration file, as
detailed there, resolved the problem for me.
--
wpasupplicant doesn't start when the network start
https://l
75 matches
Mail list logo
