novatel_3g_suspend does not check device type

Bug #1219333 reported by peter swain
12
This bug affects 2 people
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/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

peter swain (swine)
affects: linux (Ubuntu) → toshset (Ubuntu)
Revision history for this message
In , peter swain (swine) wrote :

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)
https://bugs.launchpad.net/ubuntu/+source/toshset/+bug/1219333

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*,
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

Changed in pm-utils:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in toshset (Ubuntu):
status: New → Confirmed
Revision history for this message
In , Ajax-a (ajax-a) wrote :

pm-utils hasn't been touched in eight years, none of this is likely to get addressed. Closing bugs and disabling the bz product.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.