[Desktop-packages] [Bug 1866926] Re: Device validation failing when connected to an usb hub

2020-07-07 Thread Sebastien Bacher
@Josua, agreed and as mentioned on comment #13 the package has been made
to use tcl again now, in an ideal world we would prefer to have one less
interpreter on the default installation to maintain but in practice the
cost is low so it will do

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1866926

Title:
  Device validation failing when connected to an usb hub

Status in usb-modeswitch package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to Ubuntu focal fossa development branch the usb_modeswitch 
does not seem to work any more on a Toshiba laptop.
  Two modems I have D-Link DWM-156 and Huawei E3372 show up as drives and stay 
like that until I use "Eject" in Gnome or explicitly use usb_modeswitch from 
the terminal.
  I have a strong feeling that it may either be related to Gnome or hardware.
  On another Dell laptop with Kubuntu focal fossa development, both modems 
connect automatically.

  /var/log/usb_modeswitch.log ends with:
  Warning: SCSI attribute "ref" not readable.
  Check class of first interface ...
  Device is in istall mode.
  No access to interface 8. Exit

  Up until and including the "ref" not readable is exactly the same as on 
Kubuntu @ Dell.
  Yet on Kubuntu I get plenty of successful config logs after that and on 
Ubuntu @ Toshiba I don't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1866926/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1866926] Re: Device validation failing when connected to an usb hub

2020-07-06 Thread Josua Dietze
Sebastien, I understand your concerns with regard to jimtcl. However,
the tcl package seems to be well maintained, with very few bugs (2) in
the current version, one of low urgency and one undecided.

Anyway, it's not my decision to make obviously. I trust that you know
what's best for Ubuntu.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1866926

Title:
  Device validation failing when connected to an usb hub

Status in usb-modeswitch package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to Ubuntu focal fossa development branch the usb_modeswitch 
does not seem to work any more on a Toshiba laptop.
  Two modems I have D-Link DWM-156 and Huawei E3372 show up as drives and stay 
like that until I use "Eject" in Gnome or explicitly use usb_modeswitch from 
the terminal.
  I have a strong feeling that it may either be related to Gnome or hardware.
  On another Dell laptop with Kubuntu focal fossa development, both modems 
connect automatically.

  /var/log/usb_modeswitch.log ends with:
  Warning: SCSI attribute "ref" not readable.
  Check class of first interface ...
  Device is in istall mode.
  No access to interface 8. Exit

  Up until and including the "ref" not readable is exactly the same as on 
Kubuntu @ Dell.
  Yet on Kubuntu I get plenty of successful config logs after that and on 
Ubuntu @ Toshiba I don't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1866926/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1866926] Re: Device validation failing when connected to an usb hub

2020-07-06 Thread Sebastien Bacher
@Jakub, pulling it an extra interpreter in a stable update is probably
not something we want to do so we are going to either fix the issue in
the C code or let <= focal versions have issues in some cases. I do
agree that starting doing changes to the logic might be something we
want to avoid, there is probably an easier way to restore the previous
behaviour but in a way that avoid the segfault right?

Also not that Jim is currently in Universe and not something Canonical
has commited to maintain, which is why we are using tcl (which is in
Ubuntu main)

@Josua, the problem there isn't the language or startup performance but
having to maintain one extra language/interpreter for us
(Canonical/Ubuntu), it means we have to keep someone on team familiar
with tcl and to commit to fix any security problem find in the tclsh (or
jimtcl if we decide to promote this one) which is adding maintenance
load of a small team already having lot to do

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1866926

Title:
  Device validation failing when connected to an usb hub

Status in usb-modeswitch package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to Ubuntu focal fossa development branch the usb_modeswitch 
does not seem to work any more on a Toshiba laptop.
  Two modems I have D-Link DWM-156 and Huawei E3372 show up as drives and stay 
like that until I use "Eject" in Gnome or explicitly use usb_modeswitch from 
the terminal.
  I have a strong feeling that it may either be related to Gnome or hardware.
  On another Dell laptop with Kubuntu focal fossa development, both modems 
connect automatically.

  /var/log/usb_modeswitch.log ends with:
  Warning: SCSI attribute "ref" not readable.
  Check class of first interface ...
  Device is in istall mode.
  No access to interface 8. Exit

  Up until and including the "ref" not readable is exactly the same as on 
Kubuntu @ Dell.
  Yet on Kubuntu I get plenty of successful config logs after that and on 
Ubuntu @ Toshiba I don't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1866926/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1866926] Re: Device validation failing when connected to an usb hub

2020-07-04 Thread Josua Dietze
Let me just explain shortly why I'm sticking with Tcl for the
dispatcher.

That script language is perfectly fitted for string and file parsing. At
the same time, it's much better human-readable than a Bash or Perl
script. I had people adding fixes to the wrapper script who weren't even
familiar with the language.

Execution time is not really relevant regarding the mode-switching
process, because its duration predominantly depends on the device's
internal workings until it 'reappears' in the new mode.

Both the bare interpreter tclsh *and* the 'pocket version' (jimtcl) have
everything on board for the task. No loading of additional extensions or
modules required.

Besides, I somehow can't warm up to Python but that's my personal issue
:-)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1866926

Title:
  Device validation failing when connected to an usb hub

Status in usb-modeswitch package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to Ubuntu focal fossa development branch the usb_modeswitch 
does not seem to work any more on a Toshiba laptop.
  Two modems I have D-Link DWM-156 and Huawei E3372 show up as drives and stay 
like that until I use "Eject" in Gnome or explicitly use usb_modeswitch from 
the terminal.
  I have a strong feeling that it may either be related to Gnome or hardware.
  On another Dell laptop with Kubuntu focal fossa development, both modems 
connect automatically.

  /var/log/usb_modeswitch.log ends with:
  Warning: SCSI attribute "ref" not readable.
  Check class of first interface ...
  Device is in istall mode.
  No access to interface 8. Exit

  Up until and including the "ref" not readable is exactly the same as on 
Kubuntu @ Dell.
  Yet on Kubuntu I get plenty of successful config logs after that and on 
Ubuntu @ Toshiba I don't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1866926/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1866926] Re: Device validation failing when connected to an usb hub

2020-07-04 Thread Jakub Vaněk
Hmmm, the Ubuntu version does depend on Tcl. I think a better solution
would be to go with Jim (as Debian does:
https://packages.debian.org/buster/usb-modeswitch) for both Focal and
Groovy.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1866926

Title:
  Device validation failing when connected to an usb hub

Status in usb-modeswitch package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to Ubuntu focal fossa development branch the usb_modeswitch 
does not seem to work any more on a Toshiba laptop.
  Two modems I have D-Link DWM-156 and Huawei E3372 show up as drives and stay 
like that until I use "Eject" in Gnome or explicitly use usb_modeswitch from 
the terminal.
  I have a strong feeling that it may either be related to Gnome or hardware.
  On another Dell laptop with Kubuntu focal fossa development, both modems 
connect automatically.

  /var/log/usb_modeswitch.log ends with:
  Warning: SCSI attribute "ref" not readable.
  Check class of first interface ...
  Device is in istall mode.
  No access to interface 8. Exit

  Up until and including the "ref" not readable is exactly the same as on 
Kubuntu @ Dell.
  Yet on Kubuntu I get plenty of successful config logs after that and on 
Ubuntu @ Toshiba I don't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1866926/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1866926] Re: Device validation failing when connected to an usb hub

2020-07-04 Thread Jakub Vaněk
I'm starting to feel that trying to fix the C rewrite is futile.

On line 392 of usb_modeswitch_dispatcher.c, the iface variable is
overwritten. Unfortunately the value being assigned is not an interface
number, it is rather a USB class number. Fixing this might help with
some part of this, but it also might break something else. I was also
trying to map between the C rewrite and the 2.2.5 version of the tcl
script (as stated in the header of the C version), but it seems that
there are functional differences (for example the if_chk mode seems to
trigger on different ocassions).

I'd vote for going with the Tcl version for Focal as well (I'm ignoring
any existing SRU rules through). The dependency isn't a full Tcl
interpreter, only a small library-based variant of it called Jim
(http://jim.tcl.tk/index.html/doc/www/www/index.html). According to the
package description, the library size is only 100-200 kB, which seems
negligible compared to the current ISO sizes.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1866926

Title:
  Device validation failing when connected to an usb hub

Status in usb-modeswitch package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to Ubuntu focal fossa development branch the usb_modeswitch 
does not seem to work any more on a Toshiba laptop.
  Two modems I have D-Link DWM-156 and Huawei E3372 show up as drives and stay 
like that until I use "Eject" in Gnome or explicitly use usb_modeswitch from 
the terminal.
  I have a strong feeling that it may either be related to Gnome or hardware.
  On another Dell laptop with Kubuntu focal fossa development, both modems 
connect automatically.

  /var/log/usb_modeswitch.log ends with:
  Warning: SCSI attribute "ref" not readable.
  Check class of first interface ...
  Device is in istall mode.
  No access to interface 8. Exit

  Up until and including the "ref" not readable is exactly the same as on 
Kubuntu @ Dell.
  Yet on Kubuntu I get plenty of successful config logs after that and on 
Ubuntu @ Toshiba I don't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1866926/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1866926] Re: Device validation failing when connected to an usb hub

2020-07-04 Thread Jakub Vaněk
Hi all,

I'm the one who accidentally introduced the bug when fixing
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1676763.
I'm sorry for causing the problem, I will try to find a fix that will
work in both scenarios.

Best regards,

Jakub

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1866926

Title:
  Device validation failing when connected to an usb hub

Status in usb-modeswitch package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to Ubuntu focal fossa development branch the usb_modeswitch 
does not seem to work any more on a Toshiba laptop.
  Two modems I have D-Link DWM-156 and Huawei E3372 show up as drives and stay 
like that until I use "Eject" in Gnome or explicitly use usb_modeswitch from 
the terminal.
  I have a strong feeling that it may either be related to Gnome or hardware.
  On another Dell laptop with Kubuntu focal fossa development, both modems 
connect automatically.

  /var/log/usb_modeswitch.log ends with:
  Warning: SCSI attribute "ref" not readable.
  Check class of first interface ...
  Device is in istall mode.
  No access to interface 8. Exit

  Up until and including the "ref" not readable is exactly the same as on 
Kubuntu @ Dell.
  Yet on Kubuntu I get plenty of successful config logs after that and on 
Ubuntu @ Toshiba I don't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1866926/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp