ndisgtk doesn't work with a file name with space (in the tree and/or in the filename)

Bug #133623 reported by Fabien Lusseau
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ndisgtk
Medium
Julian Andres Klode
ndisgtk (Ubuntu)
Undecided
Julian Andres Klode
ndiswrapper (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: ndisgtk

Step to reproduce:

Download a windows wireless driver, (wg311v2 for example) the directories structure have spaces (wg311v2/Drivers/Win XP/wg311v2.inf), if you choose it with the file chooser of ndisgtk, he ignore it because, if i rename the folder 'Win XP' to WinXP it work ...

Changed in ndisgtk:
assignee: nobody → juliank
importance: Undecided → Medium
status: New → In Progress
assignee: nobody → juliank
status: New → In Progress
Revision history for this message
Julian Andres Klode (juliank) wrote :

I'll fix this in the next version, which will also contain the new translations.

I'll release the version tomorrow.

Revision history for this message
Nicola Fagnani (nicfagn) wrote :

Simple patch to guard against spaces in the .inf file path and to reload the ndiswrapper module in case it was already loaded.

Revision history for this message
Julian Andres Klode (juliank) wrote :

This is already fixed in the development tree.
I just had no time to release the new version yet.
I hope I can release it Sunday.

Changed in ndisgtk:
status: In Progress → Fix Committed
Revision history for this message
Julian Andres Klode (juliank) wrote :

ndiswrapper does not handle spaces in the inf filename.

Changed in ndisgtk:
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ndisgtk - 0.8.1-1ubuntu1

---------------
ndisgtk (0.8.1-1ubuntu1) hardy; urgency=low

  * Merge from debian unstable (LP: #191848), remaining changes:
    - Use gksu/kdesu in .desktop files
    - Do not depend on menu
    - Adhere to DebianMaintainerField
  * Fix the kdesu call (LP: #174018)

ndisgtk (0.8.1-1) unstable; urgency=low

  * New upstream releases 0.8.0 and 0.8.1
    - Added many new translations
    - Add support for spaces in filename (LP: #133623)
    - Use ndiswrapper -ma instead of ndiswrapper -m (LP: #138852) and reload
      the module after installation
    - Use Special icon for invalid drivers
  * debian/menu: Fix menu file
  * debian/rules: Do not ignore make clean errors
  * debian/copyright:
    - Update the copyright years
    - Use proposed format: http://wiki.debian.org/Proposals/CopyrightFormat
  * debian/control:
    - Add Homepage, VCS and XS-DM-Upload-Allowed
    - Upgrade to policy 3.7.3

 -- Julian Andres Klode <email address hidden> Thu, 14 Feb 2008 15:53:06 +0100

Changed in ndisgtk:
status: In Progress → Fix Released
Revision history for this message
Daniel Holbach (dholbach) wrote :

Is a fix in ndiswrapper still necessary?

Changed in ndiswrapper:
status: New → Incomplete
Revision history for this message
Julian Andres Klode (juliank) wrote :

Yes. Run:
  sudo mkdir '/etc/ndiswrapper/test driver'
  sudo ndiswrapper -l
and you'll get:
  ls: /etc/ndiswrapper/test: No such file or directory
  ls: driver: No such file or directory
  test driver : invalid driver!

I recommend to change whitespace to _ if you call ndiswrapper -i to install a driver.
This would mean that 'test driver' would be 'test_driver'.

Revision history for this message
Przemek K. (azrael) wrote :

Did anyone report this bug upstream to the ndiswrapper project?
http://sourceforge.net/tracker/?group_id=93482&atid=604450

Changed in ndiswrapper (Ubuntu):
status: Incomplete → Confirmed
Changed in ndiswrapper (Ubuntu):
status: Confirmed → Fix Committed
assignee: nobody → michael (michael-maas011988)
Revision history for this message
Julian Andres Klode (juliank) wrote :

Resetting status and asignee, as no fix was committed anywhere.

Changed in ndiswrapper (Ubuntu):
assignee: michael (michael-maas011988) → nobody
status: Fix Committed → Confirmed
Revision history for this message
Julian Andres Klode (juliank) wrote :

This is most likely not going to get fixed, as upstream is (apparently) not active anymore.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers