Ubuntu
linux package

USB devices not registering, and other: "device not accepting address" or "device descriptor read/64, error " issues on ubuntu, mint 4.0 and debian etch

Bug #178601 reported by Andronik on 2007-12-25

This bug affects 8 people

Affects		Status	Importance	Assigned to	Milestone
	NULL Project	Invalid	Undecided	Unassigned
	linux (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Short history:

There seems to be long history of usb devices behaving strangely under different kernel versions, and this seems not affect only ubuntu, but most major distros with kernel versions 2.6.18 -up do date.

Description of problem.

After plugin in usb device (there are issues with cameras, hdd-s, memorystiks, wifi adapters, scanners) device will not accept address or will disconnect shortly thereafter.) in dmesg there is often messages like:

usb 1-1: new full speed USB device using uhci_hcd and address 3
[ 33.564000] usb 1-1: device descriptor read/64, error -71
[ 33.788000] usb 1-1: device descriptor read/64, error -71
[ 34.004000] usb 1-1: new full speed USB device using uhci_hcd and address 4
[ 34.124000] usb 1-1: device descriptor read/64, error -71
[ 34.348000] usb 1-1: device descriptor read/64, error -71
[ 34.564000] usb 1-1: new full speed USB device using uhci_hcd and address 5
[ 34.904000] ppdev: user-space parallel port driver
[ 34.972000] usb 1-1: device not accepting address 5, error -71
[ 35.084000] usb 1-1: new full speed USB device using uhci_hcd and address 6

device disconnects shortly and will be lost in lspci

after pluging it again and loading driver ndiswrapper- dmesg will show
hub 1-0:1.0: over-current change on port 1
[ 8722.876000] usb 1-1: new full speed USB device using uhci_hcd and address 7
[ 8723.044000] usb 1-1: configuration #1 chosen from 1 choice
[ 8958.976000] ndiswrapper version 1.45 loaded (smp=yes)
[ 8959.100000] usbcore: registered new interface driver ndiswrapper

and lsusb

Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 007: ID 0bda:8189 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 15ca:00c3
Bus 001 Device 001: ID 0000:0000

all is ok, device is present and ndiswrapper shows it...

after few seconds, sometimes minutes it just disappears.

This also happens in debian etch 2.6.18-15 kernel.

It does not matter, is ndiswrapper, ndisdriver or wpa_assistant loaded or not. Device dissappears also if:

you will try workaround "modprobe -r ehci_hcd"
or if you plug it on different usb port.

or another workaround suggested on numerous linux forums:
"If you want to start the usbcore.ko each time with the old_scheme_first parameter create a rc.local file for debian system by doing the following:

Make a file /etc/init.d/local with the following lines:
#! /bin/sh
echo N > /sys/module/usbcore/parameters/old_scheme_first" does not help.

And those issues are not due to short, long otherwise ugly or unshielded cables, (as assumes Alan Cox), nor corrupted hardware or chipsets (same devices do work under windows) (and most people having such

DEVICE NOT registering issues, have had working configurations with older kernels, or claim that same hardware works under different operating systems.

I have not tried recompile kernel from source, because i am not sure, is it due to kernel options or source or usb module itself. Also because similar (maybe same problem) have been reported
here: Bug #54273 in linux-source-2.6.15 and there are another similar complaints suse, opensuse, mandriva, debian, fedora and ubuntu forums on different countries till kernel 2.6.22-46.

Questions i have:

1) Is that kernel bug or usb module bug?
2 is there patch available?
3) Is it fixed or when this will be fixed?
4) Any workaround will be nice, it helps.

Sorry about bad english.

Tags:

Daniel T Chen (crimsun) on 2008-11-20

Changed in linux:
status:	New → Confirmed

Revision history for this message

Jesse N. Richardson (richardson183) wrote on 2009-01-11:

I have the same problem.

Revision history for this message

NoahY (noahy) wrote on 2009-03-25:

Same here... my device is a Microtrack II recorder with CF card storage:

lsusb output (before the errors):

Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 010: ID 0763:2401 Midiman
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 1915:2236 Linksys
Bus 003 Device 002: ID 413c:3012 Dell Computer Corp.
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 004: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

dmesg output:

[ 111.532012] usb 4-3: new high speed USB device using ehci_hcd and address 5
[ 111.672733] usb 4-3: configuration #1 chosen from 1 choice
[ 111.734385] usbcore: registered new interface driver libusual
[ 111.744931] Initializing USB Mass Storage driver...
[ 111.745285] scsi4 : SCSI emulation for USB Mass Storage devices
[ 111.745660] usbcore: registered new interface driver usb-storage
[ 111.745663] USB Mass Storage support registered.
[ 111.749376] usb-storage: device found at 5
[ 111.749380] usb-storage: waiting for device to settle before scanning
[ 116.748174] usb-storage: device scan complete
[ 116.748744] scsi 4:0:0:0: Direct-Access M-Audio MicroTrack 24/96 PQ: 0 ANSI: 0
[ 116.759920] sd 4:0:0:0: [sdb] 1006993 512-byte hardware sectors (516 MB)
[ 116.766674] sd 4:0:0:0: [sdb] Write Protect is off
[ 116.766681] sd 4:0:0:0: [sdb] Mode Sense: 45 00 00 00
[ 116.766684] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 116.773878] sd 4:0:0:0: [sdb] 1006993 512-byte hardware sectors (516 MB)
[ 116.774628] sd 4:0:0:0: [sdb] Write Protect is off
[ 116.774633] sd 4:0:0:0: [sdb] Mode Sense: 45 00 00 00
[ 116.774636] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 116.775022] sdb:<6>usb 4-3: reset high speed USB device using ehci_hcd and address 5
[ 151.996014] usb 4-3: device descriptor read/64, error -71
[ 157.212013] usb 4-3: device descriptor read/64, error -71
[ 157.428018] usb 4-3: reset high speed USB device using ehci_hcd and address 5
[ 162.540015] usb 4-3: device descriptor read/64, error -71
ad infinitum...

** modprobe -r ehci_hcd doesn't work

** echo N > /sys/module/usbcore/parameters/old_scheme_first doesn't work

** changing cables or ports (front/back) doesn't work

I've heard that recompiling the kernel can help, changing the setting:

#define EHCI_TUNE_CERR 3 /* 0-3 qtd retries; 0 == don't stop */

#define EHCI_TUNE_CERR 0 /* 0-3 qtd retries; 0 == don't stop */

in drivers/usb/host/ehci-hcd.c, but this is beyond me. Also people saying that tweaking the kernel in other ways works, can't verify. Anybody out there who can help?

Same here... my device is a Microtrack II recorder with CF card storage:

lsusb output (before the errors):

Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 010: ID 0763:2401 Midiman 
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 1915:2236 Linksys 
Bus 003 Device 002: ID 413c:3012 Dell Computer Corp. 
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 004: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

dmesg output:

[  111.532012] usb 4-3: new high speed USB device using ehci_hcd and address 5
[  111.672733] usb 4-3: configuration #1 chosen from 1 choice
[  111.734385] usbcore: registered new interface driver libusual
[  111.744931] Initializing USB Mass Storage driver...
[  111.745285] scsi4 : SCSI emulation for USB Mass Storage devices
[  111.745660] usbcore: registered new interface driver usb-storage
[  111.745663] USB Mass Storage support registered.
[  111.749376] usb-storage: device found at 5
[  111.749380] usb-storage: waiting for device to settle before scanning
[  116.748174] usb-storage: device scan complete
[  116.748744] scsi 4:0:0:0: Direct-Access     M-Audio  MicroTrack 24/96      PQ: 0 ANSI: 0
[  116.759920] sd 4:0:0:0: [sdb] 1006993 512-byte hardware sectors (516 MB)
[  116.766674] sd 4:0:0:0: [sdb] Write Protect is off
[  116.766681] sd 4:0:0:0: [sdb] Mode Sense: 45 00 00 00
[  116.766684] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[  116.773878] sd 4:0:0:0: [sdb] 1006993 512-byte hardware sectors (516 MB)
[  116.774628] sd 4:0:0:0: [sdb] Write Protect is off
[  116.774633] sd 4:0:0:0: [sdb] Mode Sense: 45 00 00 00
[  116.774636] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[  116.775022]  sdb:<6>usb 4-3: reset high speed USB device using ehci_hcd and address 5
[  151.996014] usb 4-3: device descriptor read/64, error -71
[  157.212013] usb 4-3: device descriptor read/64, error -71
[  157.428018] usb 4-3: reset high speed USB device using ehci_hcd and address 5
[  162.540015] usb 4-3: device descriptor read/64, error -71
ad infinitum...

** modprobe -r ehci_hcd doesn't work

** echo N > /sys/module/usbcore/parameters/old_scheme_first doesn't work

** changing cables or ports (front/back) doesn't work

I've heard that recompiling the kernel can help, changing the setting:

#define	EHCI_TUNE_CERR		3	/* 0-3 qtd retries; 0 == don't stop */

#define	EHCI_TUNE_CERR		0	/* 0-3 qtd retries; 0 == don't stop */

in drivers/usb/host/ehci-hcd.c, but this is beyond me.  Also people saying that tweaking the kernel in other ways works, can't verify.  Anybody out there who can help?

Revision history for this message

NoahY (noahy) wrote on 2009-03-27:

Oh wait... in my case, replacing the CF card (a no-name 512MB card) with a newer (Kingston 4GB Elite Pro) card makes it work... I'll have to do a little more testing, because I formatted the original card using the Microtrack's internal formatter, which may have screwed things up... the new card I didn't format, just popped it in out of the box and voila, I get a drive on my desktop and am transferring 2.6 GB of mp3s as we speak. Will confirm soon which was the problem, the format of the CF or the CF itself, but the device was not the problem, it seems.

Revision history for this message

NoahY (noahy) wrote on 2009-03-27:

Okay, it was the CF card itself, not the format method. Formatting the new card in the Microtrack doesn't change anything, it still mounts fine. The old card, it seems, has a problem with Ubuntu, or maybe reformatting it will help? Right now I have data on it, but once I find a card reader to transfer it to my desktop I'll try that and see whether it was simply a bug in the formatting process (my guess is the card is just incompatible...)

Revision history for this message

Shea McCombs (shea241) wrote on 2009-12-19:

I have this problem as well, on all physical ports. The problem goes away on restart, and manifests itself after an unknown time. I have not been able to identify any factors which trigger this behavior.

Devices tried:
- Cellphone
- Bluetooth dongle
- Microsoft Mouse
- Dynex Keyboard

Plugging in the cellphone does not generate any output to dmesg, but plugging in the other devices does. Example (from plugging in the mouse):

[398551.537022] usb 5-1: new low speed USB device using uhci_hcd and address 18
[398551.660015] usb 5-1: device descriptor read/64, error -71
[398551.884019] usb 5-1: device descriptor read/64, error -71
[398552.100020] usb 5-1: new low speed USB device using uhci_hcd and address 19
[398552.220016] usb 5-1: device descriptor read/64, error -71
[398552.444026] usb 5-1: device descriptor read/64, error -71
[398552.660017] usb 5-1: new low speed USB device using uhci_hcd and address 20
[398553.068015] usb 5-1: device not accepting address 20, error -71
[398553.180018] usb 5-1: new low speed USB device using uhci_hcd and address 21
[398553.588017] usb 5-1: device not accepting address 21, error -71
[398553.588038] hub 5-0:1.0: unable to enumerate USB device on port 1

These devices also do not get power, or at least aren't drawing as much current as they need to 'turn on'. Mouse does not illuminate, phone does not charge, bluetooth dongle's power LED does not illuminate. Rebooting fixes this as well.

uname -a:
Linux phobos 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:01:29 UTC 2009 i686 GNU/Linux

lspci:
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
00:01.0 PCI bridge: Intel Corporation 82865G/PE/P PCI to AGP Controller (rev 02)
00:06.0 System peripheral: Intel Corporation 82865G/PE/P Processor to I/O Memory Interface (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce 7800 GS] (rev a2)
02:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
02:04.0 Multimedia audio controller: Creative Labs CA0106 Soundblaster

I have this problem as well, on all physical ports.  The problem goes away on restart, and manifests itself after an unknown time.  I have not been able to identify any factors which trigger this behavior.

Devices tried:
- Cellphone
- Bluetooth dongle
- Microsoft Mouse
- Dynex Keyboard

Plugging in the cellphone does not generate any output to dmesg, but plugging in the other devices does.  Example (from plugging in the mouse):

These devices also do not get power, or at least aren't drawing as much current as they need to 'turn on'.  Mouse does not illuminate, phone does not charge, bluetooth dongle's power LED does not illuminate.  Rebooting fixes this as well.

uname -a:
Linux phobos 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:01:29 UTC 2009 i686 GNU/Linux

Revision history for this message

Steve H (steven-h67) wrote on 2009-12-30:

In my case, this happened for the 1st time with Ubuntu version:
Linux Hostname 2.6.28-17-generic #58-Ubuntu SMP Tue Dec 1 21:27:25 UTC 2009 x86_64 GNU/Linux

The last functional time for the USB, was 29 Dec, between 11:00am-11:59am. I was using a digital camera, Olympus Stylus, transferring pictures. The device timed out after minutes of non-use, and the USB mount (in storage mode, not MTP) was removed.

The next time I tried to use the USB ports (4 of them on an HP Pavilion laptop) they failed to register.

Rebooting did nothing. Rebooting in recovery mode to the root shell did nothing. I booted the system with an Ubuntu 8.04 LiveCD image, and the results were the same.

Both the installed 9.04 and the 8.04 LiveCD log files, reflected the identical error.

Attempting to boot a prior kernel version, resulted in the same errors AND loss of wireless network activation.

Attached is a .zip file of all logs I could think to capture. The log file names should provide a sufficient description of the command used to capture the log. If any clarification is needed, please email me.

Revision history for this message

Steve H (steven-h67) wrote on 2009-12-30:

I should have mentioned, I've been using this same laptop and same USB devices starting with Ubuntu 8.10, then an update via Update Manager to 9.04. The system was installed Oct '08. This is the 1st time this problem has occurred.

Revision history for this message

rabidmonkey1 (rabidmonkey1) wrote on 2010-09-13:

I think I encountered the bug here - http://ubuntuforums.org/showthread.php?t=1572877 - real pain in the butt. Hope there is a way to resolve it soon.

Revision history for this message

penalvch (penalvch) wrote on 2012-06-15:

Andronik, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete
tags:	added: needs-upstream-testing

Revision history for this message

Andronik (andrusele) wrote on 2012-06-15: Re: [Bug 178601] Re: USB devices not registering, and other: "device not accepting address" or "device descriptor read/64, error " issues on ubuntu, mint 4.0 and debian etch

#10

*
*
*

Hi,*
*
*
*You are right ,this all happened long long time ago. Not using same
hardware nor software anymore. So for me it.s history.*
*
*
*Currently running on Mint debian ed +latest 10.04 and 12 LTS versions*
*Not using additional usb cards on old 1,1 usb ports.*
*So i cant help and you can safely close the bug if needed so.*
*
*
*Andrus
*
2012/6/15 Christopher M. Penalver <email address hidden>

> Andronik, this bug was reported a while ago and there hasn't been any
> activity in it recently. We were wondering if this is still an issue?
> Can you try with the latest development release of Ubuntu? ISO CD images
> are available from http://cdimage.ubuntu.com/releases/ .
>
> If it remains an issue, could you run the following command in the
> development release from a Terminal
> (Applications->Accessories->Terminal). It will automatically gather and
> attach updated debug information to this report.
>
> apport-collect -p linux <replace-with-bug-number>
>
> Also, if you could test the latest upstream kernel available that would
> be great. It will allow additional upstream developers to examine the
> issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once
> you've tested the upstream kernel, please remove the 'needs-upstream-
> testing' tag. This can be done by clicking on the yellow pencil icon
> next to the tag located at the bottom of the bug description and
> deleting the 'needs-upstream-testing' text.
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> If you are unable to test the mainline kernel, for example it will not
> boot, please add the tag: 'kernel-unable-to-test-upstream'.
>
> Please let us know your results. Thanks in advance.
>
> ** Attachment removed: "Archive zip file of various system log files"
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/178601/+attachment/1083635/+files/usb_init_fail.zip
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Tags added: needs-upstream-testing
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/178601
>
> Title:
> USB devices not registering, and other: "device not accepting address"
> or "device descriptor read/64, error " issues on ubuntu, mint 4.0 and
> debian etch
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/178601/+subscriptions
>

*
*
*

> Andronik, this bug was reported a while ago and there hasn't been any
> activity in it recently. We were wondering if this is still an issue?
> Can you try with the latest development release of Ubuntu? ISO CD images
> are available from http://cdimage.ubuntu.com/releases/ .
>
> If it remains an issue, could you run the following command in the
> development release from a Terminal
> (Applications->Accessories->Terminal). It will automatically gather and
> attach updated debug information to this report.
>
> apport-collect -p linux <replace-with-bug-number>
>
> Also, if you could test the latest upstream kernel available that would
> be great. It will allow additional upstream developers to examine the
> issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once
> you've tested the upstream kernel, please remove the 'needs-upstream-
> testing' tag. This can be done by clicking on the yellow pencil icon
> next to the tag located at the bottom of the bug description and
> deleting the 'needs-upstream-testing' text.
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> If you are unable to test the mainline kernel, for example it will not
> boot, please add the tag: 'kernel-unable-to-test-upstream'.
>
> Please let us know your results. Thanks in advance.
>
> ** Attachment removed: "Archive zip file of various system log files"
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/178601/+attachment/1083635/+files/usb_init_fail.zip
>
> ** Changed in: linux (Ubuntu)
>       Status: Confirmed => Incomplete
>
> ** Tags added: needs-upstream-testing
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/178601
>
> Title:
>   USB devices not registering, and other: "device not accepting address"
>  or "device descriptor read/64, error " issues on ubuntu, mint 4.0 and
>  debian etch
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/178601/+subscriptions
>

penalvch (penalvch) on 2012-06-15

Changed in linux (Ubuntu):
status:	Incomplete → Invalid
affects:	debian → null
Changed in null:
status:	New → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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

Ubuntulinux package

USB devices not registering, and other: "device not accepting address" or "device descriptor read/64, error " issues on ubuntu, mint 4.0 and debian etch

Bug Description

Other bug subscribers

Remote bug watches

Ubuntu
linux package