pand won't execute the dev-up script

Bug #116075 reported by kuni
8
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: bluez-utils

When a new bnepN interface becomes available, pand should execute the /etc/bluetooth/pan/dev-up script. That obviously won't happen; even specifying the file explicitly by --devup option doesn't help.

Revision history for this message
kuni (zdenekkunicky) wrote :

Sorry I forgot - my system runs Ubuntu Feisty

Revision history for this message
ken (kenrobinsonster) wrote :

I also get the same problem. Is there progress on this bug? I use 7.0.4

Revision history for this message
ken (kenrobinsonster) wrote :

I found a bug report about the pand utility
Debian Bug report logs - #398190
pand: undocumented change regarding dev-up script
which states you use --devup.
I have 3.9. Will try --devup option tomorrow to see if it works.

Revision history for this message
ken (kenrobinsonster) wrote :

The --devup option works. What do I do to get this fixed?
ken.

Revision history for this message
Jimmy Wennlund (jimmy-wennlund) wrote :

I can confirm this bug, devup is never called, and never have on Feisty+, Dapper worked.

Revision history for this message
Jerzy Luszawski (dr-agon) wrote :

I also confirm this problem on Feisty, but for me adding --devup and full path to script helped.
I checked the debian bug report mentioned by Ken - it says this feature is back as default in newer versions of bluez. Unfortunately I have not found them in any Ubuntu repository, but I'm gonna compile and test them.
Good luck.

Revision history for this message
Maxim Kuleshov (maximk) wrote :

Confirming this problem on Gutsy. Nor default script (/etc/bluetooth/pan/dev-up), neither custom specified via --devup option, is run.

Revision history for this message
kuni (zdenekkunicky) wrote : Re: [Bug 116075] Re: pand won't execute the dev-up script

Hello Maxim!
   I found the next work-around: it's just enough to copy the dev-up script in your home directory, then it should work. Please tell me if that works for you too.. Kind regards, Zdenek

> pand won't execute the dev-up script
> https://bugs.launchpad.net/bugs/116075
> You received this bug notification because you are a direct subscriber
> of the bug.
>
>
>

Revision history for this message
ken (kenrobinsonster) wrote :

I can't do this workaround at the moment. Will be able to do it in a
few weeks and will post my results then
regards,
ken.

On Nov 28, 2007 6:48 AM, kuni <email address hidden> wrote:
> Hello Maxim!
> I found the next work-around: it's just enough to copy the dev-up script in your home directory, then it should work. Please tell me if that works for you too.. Kind regards, Zdenek
>
>
>
> > pand won't execute the dev-up script
> > https://bugs.launchpad.net/bugs/116075
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
> >
> >
>
> --
> pand won't execute the dev-up script
> https://bugs.launchpad.net/bugs/116075
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Maxim Kuleshov (maximk) wrote :

> I found the next work-around: it's just enough to copy the dev-up script in your home directory, then it should work.

Unfortunately, I'm unable to reproduce it. Does it matter where to place dev-up script in home directory? I copied it to ~/pan/dev-up and made corresponding changes to pand arguments, but with no success...

Full argument list to pand:
--listen --role NAP --devup /home/kme/pan/dev-up --devdown /home/kme/pan/dev-down

Revision history for this message
kuni (zdenekkunicky) wrote :

Hello Maxim,
   it's already some time I played with pand, I shall try it when I have time and revive my bluetooth device. Also don't forget to make the script executable and add the #!/bin/bash header as the first line of course..otherwise I don't see a rescue :( Kind regards, Zdenek

> > I found the next work-around: it's just enough to copy the dev-up
> script in your home directory, then it should work.
>
> Unfortunately, I'm unable to reproduce it. Does it matter where to place
> dev-up script in home directory? I copied it to ~/pan/dev-up and made
> corresponding changes to pand arguments, but with no success...
>
> Full argument list to pand:
> --listen --role NAP --devup /home/kme/pan/dev-up --devdown
> /home/kme/pan/dev-down
>
> --
> pand won't execute the dev-up script
> https://bugs.launchpad.net/bugs/116075
> You received this bug notification because you are a direct subscriber
> of the bug.
>
>
>

Revision history for this message
Mario Limonciello (superm1) wrote :

pand isn't supported starting with intrepid and later on the 4.x stack.

bluez (4.12-0ubuntu1) intrepid; urgency=low

  * Initial Release. (LP: #274950)
    - This package replaces bluez-utils and bluez-libs source packages.
    - It was generated by merging the contents of bluez-utils and bluez-libs
      and updating content.
    - Legacy functionality for hidd, dund, and pand are not present, and
      have been removed from all configuration files.
  * This release introduces encryption (LP: #182191)
  * debian/patches:
    - bluez-utils-oui-usage.patch was borrowed from the Fedora 10 packaging.
    - sco-connect-git.patch was taken from bluez git shortly after 4.12 release.
      It should "help" with some sco headset issues.
  * debian/control:
    - Update different packages per upstream's recommendations.
    - Update conflicts/replaces for earlier packages.
    - Add a transitional bluez-utils package to help with the transition.

 -- Mario Limonciello < <email address hidden>> Tue, 07 Oct 2008 12:10:29 -0500

Changed in bluez-utils:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers