Hi! I am a bug triager trying to make sure that this bug have enough info to be fixed.
If you have a fast Internet and a CD burner, you could download Gutsy Tribe-2 and report how it worked with it.
See http://www.ubuntu.com/testing/tribe2
I don't suggest you install it, just to run it.
After the bug (after you replugged the mouse and keyboard in 2 new USB ports) please open a console and type:
cd [that will make you go to your home directory]
sudo lshw > lshw_jb68321.txt
sudo lsusb -v > lsusb_jb68321.txt
uname -a > uname-a.log
cat /proc/version > version.log
dmesg > dmesg.log
sudo lspci -vvnn > lspci-vvnn.log
Then attach each of the following files to this bug (attach not paste!):
uname-a.log
version.log
dmesg.log
lspci-vvnn.log
lshw_jb68321.txt
lsusb_jb68321.txt
Thanks, I realize that it request a quite an amount of effort, but this is really needed to progress on that kind of bugs.
Hi! I am a bug triager trying to make sure that this bug have enough info to be fixed.
If you have a fast Internet and a CD burner, you could download Gutsy Tribe-2 and report how it worked with it. www.ubuntu. com/testing/ tribe2
See http://
I don't suggest you install it, just to run it.
After the bug (after you replugged the mouse and keyboard in 2 new USB ports) please open a console and type:
cd [that will make you go to your home directory]
sudo lshw > lshw_jb68321.txt
sudo lsusb -v > lsusb_jb68321.txt
uname -a > uname-a.log
cat /proc/version > version.log
dmesg > dmesg.log
sudo lspci -vvnn > lspci-vvnn.log
Then attach each of the following files to this bug (attach not paste!):
uname-a.log
version.log
dmesg.log
lspci-vvnn.log
lshw_jb68321.txt
lsusb_jb68321.txt
Thanks, I realize that it request a quite an amount of effort, but this is really needed to progress on that kind of bugs.