[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to different ttyUSB after resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/359356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to different ttyUSB after resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/359356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
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 device. This should certainly work also after suspend resume. Anyway, this is not a lirc bug and this issue should IMHO be closed (or possibly re-assigned to the kernel if there is some guarantee that device names should be stable during suspend/resume). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to different ttyUSB after resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/359356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to different ttyUSB after resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/359356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
Okay, if its multiple machines, I put the blame squarely on the ftdi_sio and dib0700 drivers for apparently not implementing any suspend/resume support. I've actually dug out my usb-uirt hardware, which has some usb- serial ftdi driver as well, iirc., and will see if I can reproduce the issue and try to better understand it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to different ttyUSB after resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/359356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
As for resume taking so long time, it seems it is an issue with the dvb device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to different ttyUSB after resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/359356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
And the computer is NC10. But that is not the only computer that this bug occurs in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to different ttyUSB after resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/359356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
As for BIOS, I have updated it long time ago, and I suppose it is still latest version. $ lshal | grep firmware system.firmware.release_date = '09/08/2009' (string) system.firmware.vendor = 'Phoenix Technologies Ltd.' (string) system.firmware.version = '11CA.M015.20090908.RHU' (string) storage.firmware_version = 'HH100-60' (string) (If I remember right, I used the DOS version of BIOS update software.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to different ttyUSB after resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/359356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
Choice excerpts from dmesg: [0.00] Atom PSE erratum detected, BIOS microcode update recommended [0.00] ACPI: BIOS bug: multiple APIC/MADT found, using 0 [0.00] ACPI: If "acpi_apic_instance=2" works better, notify linux-a...@vger.kernel.org [0.180781] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored I'd suggest seeing if there's a BIOS update available for your system, which may or may not improve suspend/resume functionality a bit. Especially if its taking more than a minute to resume. However, that aside, looking at both the dib0700 driver and the ftdi_sio driver, I noticed they lack suspend or resume functions entirely. The ftdi_sio driver may have the default usb-serial suspend routine wired up to it somehow though. But anyway, I'm not sure if the usb core is possibly behaving as expected, disconnecting the devices, rather than suspending them, or if its the usb chipset not suspending properly. The incremented ttyUSBx device makes some degree of sense though. If lircd has an active client (such as irxevent) at suspend time, then the IR device (/dev/ttyUSB0) will be open, in which case, it can't be fully removed. Thus, when the device is reconnected, it gets ttyUSB1, as there's still a lingering reference to ttyUSB0. No clients, 0 gets fully freed up, and can be allocated again. I'll have to see about getting some ftdi usb IR hardware one of these days to get a better understanding of what's going on. I do stand by the assertion that lirc isn't actually doing anything wrong here though. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to different ttyUSB after resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/359356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
Here's the data. Probably not relevant, but resume took more than a minute. ** Attachment added: "dmesg after fresh boot, suspend and resume" https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/359356/+attachment/2181690/+files/dmesg2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to different ttyUSB after resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/359356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
Still sounds like a kernel-level issue underneath. Can you provide dmesg output from after a fresh boot, suspend and resume? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to different ttyUSB after resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/359356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
Tested this in ubuntu 11.04. The device name is not changed, and lirc works after resume, if neither irexec nor irxevent is running. If either one is running, device is changed in resume. A workaround is to unplug and re-plug the USB device. Then /dev/ttyUSB0 exists again and lirc works. The remote control in question is "VLSystem MPlay Blast". ** Description changed: - Update: As for Xubuntu 10.04 at least, please read comment #5 + Update: As for Xubuntu 11.04 at least, please read comment #13 OS: 8.10 USB device is attached to /dev/ttyUSB0 when I plug it in USB port. But when I suspend to RAM and resume, it gets attached to /dev/ttyUSB1. Consequently, the daemon configured using /dev/ttyUSB0 does not work after resume. I would expect the device to be attached to the same ttyUSB before and after. Details of the device (from output of lsusb -v): Bus 003 Device 010: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0403 Future Technology Devices International, Ltd idProduct 0x6001 FT232 USB-Serial (UART) IC bcdDevice6.00 iManufacturer 1 FTDI iProduct2 FT232R USB UART iSerial 3 A5001qxI bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 90mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 2 FT232R USB UART Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Device Status: 0x (Bus Powered) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to different ttyUSB after resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/359356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
99% certain this is not an lirc bug, it is a kernel bug. Devices disconnecting and reconnecting on suspend/resume is indicative of buggy support for the usb chipset on the system(s) in question. The isn't anything in lirc that assigns ttyUSB devices, that is purely the kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/359356 Title: USB device attached to different ttyUSB after resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/359356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
Confirming due to above comment. ** Changed in: lirc (Ubuntu) Status: New => Confirmed -- USB device attached to different ttyUSB after resume from suspend to RAM https://bugs.launchpad.net/bugs/359356 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
This happens to me in Lucid while using a Streamzap PC Remote. -- USB device attached to different ttyUSB after resume from suspend to RAM https://bugs.launchpad.net/bugs/359356 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
And the workaround does not work in 10.04 so I don't know how to make 10.04 work as well as 9.04. -- USB device attached to different ttyUSB after resume from suspend to RAM https://bugs.launchpad.net/bugs/359356 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
To be more specific, also irxevent and irexec worked after resume in 9.04, when applying comment #7. -- USB device attached to different ttyUSB after resume from suspend to RAM https://bugs.launchpad.net/bugs/359356 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
As for comment #2, the following workaround worked in Xubuntu 9.04; replace "jarno" by your username; it has not been tested, when more than one user is logged in. ** Attachment added: "/etc/pm/sleep.d/00lirc" http://launchpadlibrarian.net/49014660/00lirc -- USB device attached to different ttyUSB after resume from suspend to RAM https://bugs.launchpad.net/bugs/359356 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
** Description changed: + Update: As for Xubuntu 10.04 at least, please read comment #5 + OS: 8.10 USB device is attached to /dev/ttyUSB0 when I plug it in USB port. But when I suspend to RAM and resume, it gets attached to /dev/ttyUSB1. Consequently, the daemon configured using /dev/ttyUSB0 does not work after resume. I would expect the device to be attached to the same ttyUSB before and after. Details of the device (from output of lsusb -v): Bus 003 Device 010: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Device Descriptor: - bLength18 - bDescriptorType 1 - bcdUSB 2.00 - bDeviceClass0 (Defined at Interface level) - bDeviceSubClass 0 - bDeviceProtocol 0 - bMaxPacketSize0 8 - idVendor 0x0403 Future Technology Devices International, Ltd - idProduct 0x6001 FT232 USB-Serial (UART) IC - bcdDevice6.00 - iManufacturer 1 FTDI - iProduct2 FT232R USB UART - iSerial 3 A5001qxI - bNumConfigurations 1 - Configuration Descriptor: - bLength 9 - bDescriptorType 2 - wTotalLength 32 - bNumInterfaces 1 - bConfigurationValue 1 - iConfiguration 0 - bmAttributes 0xa0 - (Bus Powered) - Remote Wakeup - MaxPower 90mA - Interface Descriptor: - bLength 9 - bDescriptorType 4 - bInterfaceNumber0 - bAlternateSetting 0 - bNumEndpoints 2 - bInterfaceClass 255 Vendor Specific Class - bInterfaceSubClass255 Vendor Specific Subclass - bInterfaceProtocol255 Vendor Specific Protocol - iInterface 2 FT232R USB UART - Endpoint Descriptor: - bLength 7 - bDescriptorType 5 - bEndpointAddress 0x81 EP 1 IN - bmAttributes2 - Transfer TypeBulk - Synch Type None - Usage Type Data - wMaxPacketSize 0x0040 1x 64 bytes - bInterval 0 - Endpoint Descriptor: - bLength 7 - bDescriptorType 5 - bEndpointAddress 0x02 EP 2 OUT - bmAttributes2 - Transfer TypeBulk - Synch Type None - Usage Type Data - wMaxPacketSize 0x0040 1x 64 bytes - bInterval 0 + bLength18 + bDescriptorType 1 + bcdUSB 2.00 + bDeviceClass0 (Defined at Interface level) + bDeviceSubClass 0 + bDeviceProtocol 0 + bMaxPacketSize0 8 + idVendor 0x0403 Future Technology Devices International, Ltd + idProduct 0x6001 FT232 USB-Serial (UART) IC + bcdDevice6.00 + iManufacturer 1 FTDI + iProduct2 FT232R USB UART + iSerial 3 A5001qxI + bNumConfigurations 1 + Configuration Descriptor: + bLength 9 + bDescriptorType 2 + wTotalLength 32 + bNumInterfaces 1 + bConfigurationValue 1 + iConfiguration 0 + bmAttributes 0xa0 + (Bus Powered) + Remote Wakeup + MaxPower 90mA + Interface Descriptor: + bLength 9 + bDescriptorType 4 + bInterfaceNumber0 + bAlternateSetting 0 + bNumEndpoints 2 + bInterfaceClass 255 Vendor Specific Class + bInterfaceSubClass255 Vendor Specific Subclass + bInterfaceProtocol255 Vendor Specific Protocol + iInterface 2 FT232R USB UART + Endpoint Descriptor: + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x81 EP 1 IN + bmAttributes2 + Transfer TypeBulk + Synch Type None + Usage Type Data + wMaxPacketSize 0x0040 1x 64 bytes + bInterval 0 + Endpoint Descriptor: + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x02 EP 2 OUT + bmAttributes2 + Transfer TypeBulk + Synch Type None + Usage Type Data + wMaxPacketSize 0x0040 1x 64 bytes + bInterval 0 Device Status: 0x - (Bus Powered) + (Bus Powered) -- USB device attached to different ttyUSB after resume from suspend to RAM https://bugs.launchpad.net/bugs/359356 You received this bug notific
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
OK, thanks. Changing back to New so that the lirc guys will look at it. ** Changed in: lirc (Ubuntu) Status: Incomplete => New -- USB device attached to different ttyUSB after resume from suspend to RAM https://bugs.launchpad.net/bugs/359356 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
Oh, I can reproduce it: I just have to have irxevent running. Note: If I have irexec running, but no irxevent, the device is not changed in resume, but lirc does not work anyway. -- USB device attached to different ttyUSB after resume from suspend to RAM https://bugs.launchpad.net/bugs/359356 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
I can not reproduce this in 10.04. -- USB device attached to different ttyUSB after resume from suspend to RAM https://bugs.launchpad.net/bugs/359356 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in lirc. When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Can you reproduce this bug in 10.04? Thanks. ** Package changed: ubuntu => lirc (Ubuntu) ** Changed in: lirc (Ubuntu) Status: New => Incomplete -- USB device attached to different ttyUSB after resume from suspend to RAM https://bugs.launchpad.net/bugs/359356 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
Workaround is to run "/etc/init.d/lirc stop" before suspend and "/etc/init.d/lirc start" after resume; both as superuser. These can even be automated; see http://en.opensuse.org/Pm-utils -- USB device attached to different ttyUSB after resume from suspend to RAM https://bugs.launchpad.net/bugs/359356 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 359356] Re: USB device attached to different ttyUSB after resume from suspend to RAM
** Attachment added: "dmesg listing of messages" http://launchpadlibrarian.net/25226424/dmesg.list -- USB device attached to different ttyUSB after resume from suspend to RAM https://bugs.launchpad.net/bugs/359356 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
