[Desktop-packages] [Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM

2016-11-03 Thread Alec Leamas
Now, suspend-resume is about the kernel, the extra modules secion. But which iof them? Just don't know. ** Package changed: lirc (Ubuntu) => linux-lts-xenial (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https:

[Desktop-packages] [Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM

2016-11-03 Thread Alec Leamas
Re-assigning to kernel - this is teh way to clarify whether it's a bug or just documented behaviour. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to d

[Desktop-packages] [Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM

2016-07-06 Thread Alec Leamas
I don't know if changing the device after a kernel suspend/resume could be a kernel bug. Basically, I don't think the kernel guarantees much more than that device names should be unique(?) The proper solution to handle situation is to install a udev rule which sets up a stable device name for the

[Desktop-packages] [Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM

2014-09-01 Thread Bob Mroczka
Although not a fix by no means I have used a workaround by modifying /etc/lirc/hardware.conf and changing the line from REMOTE_LIRCD_ARGS="-d /dev/ttyUSB0" to REMOTE_LIRCD_ARGS="-d /dev/ttyUSB*" If you have more than one ttyUSB device this will not work but I have not had this issue. -- You rec