Ubuntu
linux-backports-modules-2.6.27 package

prepare-compat-wireless.sh - incorrect shell variable

Bug #332576 reported by TJ
8
Affects Status Importance Assigned to Milestone
linux-backports-modules-2.6.27 (Ubuntu)
Fix Released
Low
Stefan Bader
Intrepid
Fix Released
Low
Stefan Bader

Bug Description

SRU justificaton:

Impact: The script contains a single missing character. No other code will be affected

Fix: Add missing $ to variable.

prepare-compat-wireless.sh has a typing error in the usage of the variable ${WT} - the leading $ is missing.

See original description
Revision history for this message
TJ (tj) wrote :
Stefan Bader (smb)
Changed in linux-backports-modules-2.6.27:
assignee: nobody → stefan-bader-canonical
importance: Undecided → Low
status: New → In Progress
Stefan Bader (smb)
Changed in linux-backports-modules-2.6.27:
assignee: nobody → stefan-bader-canonical
importance: Undecided → Low
status: New → Fix Committed
status: In Progress → Fix Committed
description: updated
Revision history for this message
James Usmar (james-usmar) wrote :

Hello,

Would this bug explain why since 22/2/09 I am now seeing my wireless USB based connection timing out and resetting every 2-4 minutes?

My install of Intrepid was doing just fine until yesterday when I assume some update started to causes this fault.

Best wishes,
James Usmar

Revision history for this message
Stefan Bader (smb) wrote : Re: [Bug 332576] Re: prepare-compat-wireless.sh - incorrect shell variable

> Would this bug explain why since 22/2/09 I am now seeing my wireless USB
> based connection timing out and resetting every 2-4 minutes?
>
No, I don't think so. First this does not affect the build. Second, you would
have to have linux-backports-modules installed. So it sounds unlikely. The
question would be whether you have -proposed enabled in your installation
sources. That might relate to the date you mention. In that case you should be
running 2.6.27-12.28 but also should be able to boot the older 2.6.27-11.27 to
compare against that.

Revision history for this message
Martin Pitt (pitti) wrote :

Accepted into intrepid-proposed; please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-backports-modules-2.6.27 - 2.6.27-14.16

---------------
linux-backports-modules-2.6.27 (2.6.27-14.16) intrepid-proposed; urgency=low

  [Upstream Kernel Changes]

  * wiphy_update_regulatory: avoid beacons and notifiers if no
    regulatory_domain
    - LP: #337929

linux-backports-modules-2.6.27 (2.6.27-14.15) intrepid-proposed; urgency=low

  [Stefan Bader]

  * scripts: Fix type in prepare-compat-wireless.sh
    - LP: #332576
  * ABI bump by proposed update

  [Tim Gardner]

  * Update MUNGE script for latest wireless-testing/compat-wireless
    - LP: #293217
  * Update to master-2009-03-04
    - LP: #293217

linux-backports-modules-2.6.27 (2.6.27-13.14) intrepid-proposed; urgency=low

  [Stefan Bader]

  * ABI bump by proposed update

linux-backports-modules-2.6.27 (2.6.27-12.13) intrepid-proposed; urgency=low

  * ABI bump by proposed update

 -- Stefan Bader <email address hidden> Wed, 08 Apr 2009 10:54:13 +0200

Changed in linux-backports-modules-2.6.27 (Ubuntu Intrepid):
status: Fix Committed → Fix Released
Stefan Bader (smb)
Changed in linux-backports-modules-2.6.27 (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.