novatel_3g_suspend does not check device type
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pm-utils |
Won't Fix
|
Medium
|
|||
toshset (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Package: toshset-1.76-4
Environment: Ubuntu Saucy Salamander (development branch) Release: 13.10
I found /etc/pm/
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-
[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: | linux (Ubuntu) → toshset (Ubuntu) |
Changed in pm-utils: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
Changed in pm-utils: | |
status: | Confirmed → Won't Fix |
This is not a pm-utils bug as such, but a possible failure of policy/toolset in acpi-support ....
I'm re-reporting it in pm-utils, because resume-failure is the expected symptom.
From main report (ubuntu toshset - novatel_3g_suspend does not check device type) /bugs.launchpad .net/ubuntu/ +source/ toshset/ +bug/1219333
https:/
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 usb 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*, to-non- toshiba by some dpkg Suggests/ Recommends/ Requires tag.
but it was probably mistakenly added as harmless-
[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