[Bug 541501] Re: [RV515] [LENOVO T60] external screen display shows "shivering", horizontal refresh offset
I've been annoyed by this same bug and can confirm that the modeset=0 option for the radeon resolved the problem for me. I'm a little surprised that this fix as well as the one from bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/543045 were not fixed for the official 10.04 release. Fortunately with two radeon options it could be fixed, but I guess usual people who do not often handle module options are going to be lost and much more annoyed than I have been. You just need to add the line: options radeon new_pll=0 modeset=0 in a (for instance) /etc/modprobe.d/radeon.conf file (or any /etc/modprobe.d/ file). -- [RV515] [LENOVO T60] external screen display shows "shivering", horizontal refresh offset https://bugs.launchpad.net/bugs/541501 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 543045] Re: [RV530] screen flickers in lucid lynx [Needs pll quirk]
Hum, my problem for the external screen is not related to this bug (so the radeon option solved my problem for LVDS flickering). The external screen problem is this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/541501 -- [RV530] screen flickers in lucid lynx [Needs pll quirk] https://bugs.launchpad.net/bugs/543045 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 543045] Re: [RV530] screen flickers in lucid lynx [Needs pll quirk]
Adding the new_pll=0 to the radeon driver solved the problem for my LVDS monitor on my T60p. However, when I try to hook an external monitor, the output on the second monitor also has a flickering issue that did not disappear with this option. -- [RV530] screen flickers in lucid lynx [Needs pll quirk] https://bugs.launchpad.net/bugs/543045 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 130437] Re: udev rule can fail to run ifdown, break reinserting device
I can confirm that this is fixed with jaunty, usb networking now works fine with ifupdown udev script in jaunty. -- udev rule can fail to run ifdown, break reinserting device https://bugs.launchpad.net/bugs/130437 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 368109] Re: rfcomm nodes should be created with dialout group
** Attachment added: "Direct solution with new udev rule." http://launchpadlibrarian.net/26038777/49-rfcomm-rights.rules -- rfcomm nodes should be created with dialout group https://bugs.launchpad.net/bugs/368109 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 368109] [NEW] rfcomm nodes should be created with dialout group
Public bug reported: Binary package hint: udev When I register a rfcomm device on my system, it is created as a root:root device node. The correct behaviour should be root:dialout, as for instance /dev/ttyUSB*. I have written a direct solution by adding a new udev rule to /etc/udev/rules.d/ attached to this bug. A patch would be to change this line in /lib/udev/rules.d/50-udev- default.rules: # serial KERNEL=="tty[A-Z]*[0-9]|pppox[0-9]*|ircomm[0-9]*|noz[0-9]*", GROUP="dialout" to: # serial KERNEL=="tty[A-Z]*[0-9]|pppox[0-9]*|ircomm[0-9]*|noz[0-9]*|rfcomm[0-9]*", GROUP="dialout" ** Affects: udev (Ubuntu) Importance: Undecided Status: New -- rfcomm nodes should be created with dialout group https://bugs.launchpad.net/bugs/368109 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 277619] Re: kded4 crashed at update
I solved it by removing the .kde4/share/config/kglobalshortcutsrc file, log out and then reapply default global shortcuts after login. -- kded4 crashed at update https://bugs.launchpad.net/bugs/277619 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde4libs in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 277619] Re: kded4 crashed at update
Same happens here for Hardy with this ppa (deb http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu hardy main ) that I guess give the same kde4 packages that for Intrepid. This bug is really annoying, not being able to use keyboard shortcuts is a killer for me. Here is the error message I get: kded(29721) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: "NetworkManager" ASSERT: "d->keyToAction.value(key) == ad" in file /build/buildd/kde4libs-4.1.2/kdeui/shortcuts/kdedglobalaccel.cpp, line 412 [EMAIL PROTECTED]:~$ KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kded4 path = pid = 29721 sock_file=/home/valentin/.kde4/socket-thinkpad/kdeinit4__0 kded(29748) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: "NetworkManager" ASSERT: "d->keyToAction.value(key) == ad" in file /build/buildd/kde4libs-4.1.2/kdeui/shortcuts/kdedglobalaccel.cpp, line 412 -- kded4 crashed at update https://bugs.launchpad.net/bugs/277619 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 226279] Re: Kernel 2.6.24-17 - broken resume from suspend to RAM
I just want to add a "me too" post on my Thinkpad T60p. Suspend/resume (by the way, that's resume that hangs, being VERY long) has stopped working since -17 and does not work with -18. It looks like -19 proposed by Tim has corrected the bug, but since this laptop is my work computer and I need it rather stable, I don't feel like installing something from PPA (or don't have time to do it). When can we expect the -19 to be released on the official package sources ? -- Kernel 2.6.24-17 - broken resume from suspend to RAM https://bugs.launchpad.net/bugs/226279 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 207089] Re: USB devices are not always detected on 2.6.24
After the Hardy release, this still happens to me. I can confirm that when I have no USB device plugged to my laptop when I suspend, they all work well when I replug them after the resume. However, when they are plugged during the suspend/resume, all USB devices are not detected (and not powered) afterwards. -- USB devices are not always detected on 2.6.24 https://bugs.launchpad.net/bugs/207089 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 207089] Re: USB devices are not always detected on 2.6.24
I have run into the exact same problem. Just in case it could play a role, my laptop is a Thinkpad t60p running the amd64 version of ubuntu. The suspend log is attached to this message However, for me this has worked prior to 2.6.24-15 (I have noticed problem after the upgrade from -14 to -15). ** Attachment added: "suspend log" http://launchpadlibrarian.net/13212790/suspend.log -- USB devices are not always detected on 2.6.24 https://bugs.launchpad.net/bugs/207089 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 185131] Re: [GUTSY KDE4] Suspend and hibernate don't work
I am experiencing exactly the same problem here with Gutsy. Hibernate works under KDE3 (configured thanks to guidance-power-manager). Under KDE4, it does not work automatically, however when I make a "echo mem > /sys/power/state", it works perfectly fine. I am also unable to configure the processor frequency. All these kind of things are handled under KDE3 by guidance-power-manager and I think it does not behave well with KDE4. How could I produce a log of this tool ? Is it planned to have a new version of this tool for Hardy that is better integrated with KDE4 (maybe in the Battery Monitor Plasmoid ?) These annoyances are showstoppers for me to use KDE4 on my laptop, although I would love to. I would love to be able to do so for Hardy ... -- [GUTSY KDE4] Suspend and hibernate don't work https://bugs.launchpad.net/bugs/185131 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 163353] Re: Unable to install Ubuntu with a m2n-mx motherboard
He needs to give the kernel the noapic option because the asus bios is far from perfect and the kernel hangs if it tries to handle the apic -- Unable to install Ubuntu with a m2n-mx motherboard https://bugs.launchpad.net/bugs/163353 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121653] Re: [gutsy] Suspend to Ram does not work on Z61m
Just want to add another comment, to confirm that this issue really affects a lot of people and is a real regression. I have had the same issue on my Thinkpad T60p. Since suspend is for me much more important than 3D support, I prevent the fglrx kernel module from being loaded and I can suspend again. Hum ... when is the open-source ati driver based on ati specification going to be released ? I badly want an open-source driver for my video card (01:00.0 VGA compatible controller: ATI Technologies Inc M56GL [Mobility FireGL V5250]) -- [gutsy] Suspend to Ram does not work on Z61m https://bugs.launchpad.net/bugs/121653 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133810] Re: package guidance-backends 0.8.0svn20070727-0ubuntu2 failed to install/upgrade: trying to overwrite `/usr/share/apps/guidance/vesamodes', which is also in package kde-guidance
I am experiencing exactly the same here and it blocks me to achieve my upgrade to gutsy. I also did the a dist-upgrade to gutsy. -- package guidance-backends 0.8.0svn20070727-0ubuntu2 failed to install/upgrade: trying to overwrite `/usr/share/apps/guidance/vesamodes', which is also in package kde-guidance https://bugs.launchpad.net/bugs/133810 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kde-guidance in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 81915] Re: adds/removes same device many times a second causing high loads and extremally slow performance
No it has absolutely nothing to do with KDE or KDM because I'm using it too and the problem is also here. This is definitely kernel related. I'm currently running 2.6.20-8.4 -- adds/removes same device many times a second causing high loads and extremally slow performance https://launchpad.net/bugs/81915 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 81915] Re: adds/removes same device many times a second causing high loads and extremally slow performance
You're right Martin, the problem comes from the kernel, which goes on detecting USB connections although my USB device is disconnnected. (and furthermore, it cannot handle the USB device). Here is /var/log/kernel.log: tail -f /var/log/kern.log Feb 15 11:29:48 lsro1pc307 kernel: [79503.404000] usb 1-1: new full speed USB device using uhci_hcd and address 2 Feb 15 11:29:48 lsro1pc307 kernel: [79503.596000] usb 1-1: configuration #1 chosen from 1 choice Feb 15 11:29:48 lsro1pc307 kernel: [79503.992000] usbcore: registered new interface driver usbserial Feb 15 11:29:48 lsro1pc307 kernel: [79503.992000] drivers/usb/serial/usb-serial.c: USB Serial support registered for generic Feb 15 11:29:49 lsro1pc307 kernel: [79504.084000] usbcore: registered new interface driver usbserial_generic Feb 15 11:29:49 lsro1pc307 kernel: [79504.084000] drivers/usb/serial/usb-serial.c: USB Serial Driver core Feb 15 11:29:49 lsro1pc307 kernel: [79504.096000] drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Serial Device Feb 15 11:29:49 lsro1pc307 kernel: [79504.096000] ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected Feb 15 11:29:49 lsro1pc307 kernel: [79504.096000] drivers/usb/serial/ftdi_sio.c: Detected FT232BM Feb 15 11:29:49 lsro1pc307 kernel: [79504.096000] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0 Feb 15 11:29:49 lsro1pc307 kernel: [79504.096000] usbcore: registered new interface driver ftdi_sio Feb 15 11:29:49 lsro1pc307 kernel: [79504.096000] drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver Feb 15 11:29:49 lsro1pc307 kernel: [79504.30] usb 1-1: usbfs: interface 0 claimed by ftdi_sio while 'brltty' sets config #1 Feb 15 11:29:49 lsro1pc307 kernel: [79504.304000] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 Feb 15 11:29:49 lsro1pc307 kernel: [79504.304000] ftdi_sio 1-1:1.0: device disconnected Feb 15 11:30:00 lsro1pc307 kernel: [79515.572000] usb 1-1: USB disconnect, address 2 Feb 15 11:30:00 lsro1pc307 kernel: [79515.684000] usb 1-1: new full speed USB device using uhci_hcd and address 3 Feb 15 11:30:00 lsro1pc307 kernel: [79515.876000] usb 1-1: configuration #1 chosen from 1 choice Feb 15 11:30:00 lsro1pc307 kernel: [79515.88] ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected Feb 15 11:30:00 lsro1pc307 kernel: [79515.88] drivers/usb/serial/ftdi_sio.c: Detected FT232BM Feb 15 11:30:00 lsro1pc307 kernel: [79515.88] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0 Feb 15 11:30:06 lsro1pc307 kernel: [79521.032000] usb 1-1: usbfs: interface 0 claimed by ftdi_sio while 'brltty' sets config #1 Feb 15 11:30:06 lsro1pc307 kernel: [79521.036000] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 Feb 15 11:30:06 lsro1pc307 kernel: [79521.036000] ftdi_sio 1-1:1.0: device disconnected Feb 15 11:30:11 lsro1pc307 kernel: [79526.516000] usb 4-2: USB disconnect, address 4 Feb 15 11:30:11 lsro1pc307 kernel: [79526.628000] usb 4-2: new full speed USB device using uhci_hcd and address 5 Feb 15 11:30:11 lsro1pc307 kernel: [79526.86] usb 4-2: configuration #1 chosen from 1 choice Feb 15 11:30:12 lsro1pc307 kernel: [79526.972000] usb 1-1: USB disconnect, address 3 Feb 15 11:30:12 lsro1pc307 kernel: [79527.084000] usb 1-1: new full speed USB device using uhci_hcd and address 4 Feb 15 11:30:12 lsro1pc307 kernel: [79527.276000] usb 1-1: configuration #1 chosen from 1 choice Feb 15 11:30:12 lsro1pc307 kernel: [79527.28] ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected Feb 15 11:30:12 lsro1pc307 kernel: [79527.28] drivers/usb/serial/ftdi_sio.c: Detected FT232BM Feb 15 11:30:12 lsro1pc307 kernel: [79527.28] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0 Feb 15 11:30:17 lsro1pc307 kernel: [79532.432000] usb 1-1: usbfs: interface 0 claimed by ftdi_sio while 'brltty' sets config #1 Feb 15 11:30:17 lsro1pc307 kernel: [79532.436000] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 Feb 15 11:30:17 lsro1pc307 kernel: [79532.436000] ftdi_sio 1-1:1.0: device disconnected Feb 15 11:30:28 lsro1pc307 kernel: [79543.668000] usb 1-1: USB disconnect, address 4 Feb 15 11:30:28 lsro1pc307 kernel: [79543.78] usb 1-1: new full speed USB device using uhci_hcd and address 5 Feb 15 11:30:29 lsro1pc307 kernel: [79543.972000] usb 1-1: configuration #1 chosen from 1 choice Feb 15 11:30:29 lsro1pc307 kernel: [79543.976000] ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected Feb 15 11:30:29 lsro1pc307 kernel: [79543.976000] drivers/usb/serial/ftdi_sio.c: Detected FT232BM Feb 15 11:30:29 lsro1pc307 kernel: [79543.976000] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0 Feb 15 11:30:34 lsro1pc307 kernel: [79549.128000] usb 1-1: usbfs: interface 0 claimed by ftdi_sio while 'brltty' sets config #1 Feb 15 11:30:34 lsro1pc307 kernel: [79549.132
[Bug 81915] Re: [feisty] hald adds/removes same device many times a second causing high loads and extremally slow performance
I have the same kind of problem. However I have been able to install Feisty rather cleanly and can use it in rather good conditions. Feb 14 08:12:53 lsro1pc307 NetworkManager: ^I[1171437173.079769] nm_hal_device_removed (): Device removed (hal udi is '/org/freedesktop/Hal/d evices/usb_device_483_2016_noserial_usbraw'). Feb 14 08:12:53 lsro1pc307 NetworkManager: ^I[1171437173.082146] nm_hal_device_removed (): Device removed (hal udi is '/org/freedesktop/Hal/d evices/usb_device_483_2016_noserial_if0'). Feb 14 08:12:53 lsro1pc307 NetworkManager: ^I[1171437173.082750] nm_hal_device_removed (): Device removed (hal udi is '/org/freedesktop/Hal/d evices/usb_device_483_2016_noserial'). Feb 14 08:12:53 lsro1pc307 NetworkManager: ^I[1171437173.391037] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/d evices/usb_device_483_2016_noserial'). Feb 14 08:12:53 lsro1pc307 NetworkManager: ^I[1171437173.475606] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/d evices/usb_device_483_2016_noserial_if0'). Feb 14 08:12:53 lsro1pc307 NetworkManager: ^I[1171437173.494472] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/d evices/usb_device_483_2016_noserial_usbraw'). Feb 14 08:13:45 lsro1pc307 NetworkManager: ^I[1171437225.414194] nm_hal_device_removed (): Device removed (hal udi is '/org/freedesktop/Hal/d evices/usb_device_483_2016_noserial_usbraw'). Feb 14 08:13:45 lsro1pc307 NetworkManager: ^I[1171437225.414788] nm_hal_device_removed (): Device removed (hal udi is '/org/freedesktop/Hal/d evices/usb_device_483_2016_noserial_if0'). Feb 14 08:13:45 lsro1pc307 NetworkManager: ^I[1171437225.416037] nm_hal_device_removed (): Device removed (hal udi is '/org/freedesktop/Hal/d evices/usb_device_483_2016_noserial'). Feb 14 08:13:45 lsro1pc307 NetworkManager: ^I[1171437225.727227] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/d evices/usb_device_483_2016_noserial'). Feb 14 08:13:45 lsro1pc307 NetworkManager: ^I[1171437225.809810] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/d evices/usb_device_483_2016_noserial_if0'). Feb 14 08:13:45 lsro1pc307 NetworkManager: ^I[1171437225.829630] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/d evices/usb_device_483_2016_noserial_usbraw'). And this also seems to be related: when I plug in an USB device (FTDI- based USB-serial converter, using ftd_sio module), here are the various log files: UDEVMONITOR: UEVENT[1171437717.856855] add@/devices/pci:00/:00:1d.3/usb5/5-2 UEVENT[1171437717.856894] add@/class/usb_endpoint/usbdev5.7_ep00 UDEV [1171437717.857448] add@/devices/pci:00/:00:1d.3/usb5/5-2 UEVENT[1171437717.858739] add@/devices/pci:00/:00:1d.3/usb5/5-2/5-2:1.0 UEVENT[1171437717.860501] add@/class/usb_endpoint/usbdev5.7_ep81 UEVENT[1171437717.860527] add@/class/usb_endpoint/usbdev5.7_ep02 UEVENT[1171437717.860540] add@/class/usb_endpoint/usbdev5.7_ep83 UEVENT[1171437717.860552] add@/class/usb_device/usbdev5.7 UDEV [1171437717.877150] add@/class/usb_endpoint/usbdev5.7_ep81 UDEV [1171437717.68] add@/class/usb_endpoint/usbdev5.7_ep02 UDEV [1171437717.897248] add@/class/usb_endpoint/usbdev5.7_ep00 UDEV [1171437717.971358] add@/class/usb_endpoint/usbdev5.7_ep83 UDEV [1171437717.994808] add@/devices/pci:00/:00:1d.3/usb5/5-2/5-2:1.0 UDEV [1171437718.021570] add@/class/usb_device/usbdev5.7 UEVENT[1171437724.335900] add@/devices/pci:00/:00:1d.0/usb2/2-1 UEVENT[1171437724.335935] add@/class/usb_endpoint/usbdev2.9_ep00 UEVENT[1171437724.341608] add@/devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0 UDEV [1171437724.341608] add@/devices/pci:00/:00:1d.0/usb2/2-1 UEVENT[1171437724.341654] add@/devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/ttyUSB0 UEVENT[1171437724.341668] add@/class/tty/ttyUSB0 UEVENT[1171437724.357684] add@/class/usb_endpoint/usbdev2.9_ep81 UDEV [1171437724.357684] add@/class/tty/ttyUSB0 UEVENT[1171437724.357720] add@/class/usb_endpoint/usbdev2.9_ep02 UEVENT[1171437724.357733] add@/class/usb_device/usbdev2.9 UDEV [1171437724.359261] add@/class/usb_endpoint/usbdev2.9_ep81 UDEV [1171437724.370653] add@/class/usb_endpoint/usbdev2.9_ep02 UDEV [1171437724.439815] add@/devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0 UDEV [1171437724.440975] add@/devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/ttyUSB0 UDEV [1171437724.460055] add@/class/usb_device/usbdev2.9 UDEV [1171437724.502372] add@/class/usb_endpoint/usbdev2.9_ep00 UEVENT[1171437728.315357] remove@/class/tty/ttyUSB0 UDEV [1171437728.315357] remove@/class/tty/ttyUSB0 UEVENT[1171437728.315400] remove@/devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/ttyUSB0 UDEV [1171437728.315400] remove@/class/usb_endpoint/usbdev2.9_ep02 UEVENT[1171437728.315419] remove@/class/usb_endpoint/usbdev2.9_ep81 UDEV [1171437728.315419] remove@/devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/ttyUSB0 UEVENT[1171437728
