kernel-packages team mailing list archive

[peter swain <swine@xxxxxxxxx>]

Public bug reported:

Package: toshset-1.76-4
Environment: Ubuntu Saucy Salamander (development branch) Release:	13.10

I found /etc/pm/sleep.d/novatel_3g_suspend on my non-toshiba laptop.
It takes action on suspend/resume, meddling with bus=2 device=2 as if this is definitely a novatel-3G thingy.
But nowhere in the script, nor in the pre-install script, does it check that, or even check dmidecode to see if this is a target laptop.

How I installed toshset-1.76-4 I don't know - it's lost in the pre-history of /var/log/dpkg*,
but it was probably mistakenly added as harmless-to-non-toshiba by some dpkg Suggests/Recommends/Requires tag.
[looks, finds it's a dependency of acpi-support]

Is there some traditional way for scanning usb/pci for affected devices in such scripts?
In my case usb/2-2 was unoccupied, but this could mangle hibernate/resume for someone with a critical device there

** Affects: toshset (Ubuntu)
     Importance: Undecided
         Status: New

** Package changed: linux (Ubuntu) => toshset (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1219333

Title:
  novatel_3g_suspend does not check device type

Status in “toshset” package in Ubuntu:
  New

Bug description:
  Package: toshset-1.76-4
  Environment: Ubuntu Saucy Salamander (development branch) Release:	13.10

  I found /etc/pm/sleep.d/novatel_3g_suspend on my non-toshiba laptop.
  It takes action on suspend/resume, meddling with bus=2 device=2 as if this is definitely a novatel-3G thingy.
  But nowhere in the script, nor in the pre-install script, does it check that, or even check dmidecode to see if this is a target laptop.

  How I installed toshset-1.76-4 I don't know - it's lost in the pre-history of /var/log/dpkg*,
  but it was probably mistakenly added as harmless-to-non-toshiba by some dpkg Suggests/Recommends/Requires tag.
  [looks, finds it's a dependency of acpi-support]

  Is there some traditional way for scanning usb/pci for affected devices in such scripts?
  In my case usb/2-2 was unoccupied, but this could mangle hibernate/resume for someone with a critical device there

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/toshset/+bug/1219333/+subscriptions