| 2010-05-11 20:29:24 |
beej |
bug |
|
|
added bug |
| 2010-05-16 09:55:48 |
nUboon2Age |
ubuntu: status |
New |
Confirmed |
|
| 2010-05-16 17:33:54 |
nUboon2Age |
bug task added |
|
jockey |
|
| 2010-05-16 18:00:03 |
nUboon2Age |
branch linked |
|
lp:ubuntu/jockey |
|
| 2010-05-16 18:04:30 |
nUboon2Age |
branch linked |
|
lp:ubuntu/lucid/jockey |
|
| 2010-05-16 18:45:15 |
nUboon2Age |
bug task added |
|
hundredpapercuts |
|
| 2010-05-16 19:17:09 |
nUboon2Age |
bug task added |
|
new-user-experience-team |
|
| 2010-05-16 19:24:37 |
nUboon2Age |
summary |
user experience for installation of Ubuntu on machines requiring b43 and b43-legacy wireless driver needs work |
user experience nightmare for installation of Ubuntu on machines requiring b43 and b43-legacy wireless driver |
|
| 2010-05-16 19:31:42 |
nUboon2Age |
description |
when Ubuntu is installed on a machine with a wi-fi interface that requires either the b43 or b43-legacy driver, the user experience is currently (10.04) pretty bad. no information is provided to the user about the need to connect to the internet some other way and run the script from the b43-fwcutter package. |
when Ubuntu is installed on a machine with a wi-fi interface that requires either the b43 or b43-legacy driver, the user experience is awful currently (10.04). Jockey should automatically find, provide, correctly install and activate the b43 or b43-legacy wireless drivers. Instead not only does it fail in various ways, no troubleshooting information is provided to the user about how to apply workarounds for the Jockey bug, such as the need to connect to the Internet some other way and run the script to work b43-fwcutter package or ndiswrapper or bmcwl sources.
|
|
| 2010-05-16 19:33:55 |
nUboon2Age |
description |
when Ubuntu is installed on a machine with a wi-fi interface that requires either the b43 or b43-legacy driver, the user experience is awful currently (10.04). Jockey should automatically find, provide, correctly install and activate the b43 or b43-legacy wireless drivers. Instead not only does it fail in various ways, no troubleshooting information is provided to the user about how to apply workarounds for the Jockey bug, such as the need to connect to the Internet some other way and run the script to work b43-fwcutter package or ndiswrapper or bmcwl sources.
|
When Ubuntu is installed on a machine with a wi-fi interface that requires either the b43 or b43-legacy driver, the user experience is awful currently (10.04). Jockey should automatically find, provide, correctly install and activate the proprietary b43 or b43-legacy wireless drivers. Instead not only does it fail in various ways, no troubleshooting information is provided to the user about how to apply workarounds for the Jockey bug, such as the need to connect to the Internet some other way and run the script to work b43-fwcutter package or ndiswrapper or bmcwl sources.
|
|
| 2010-05-16 19:38:26 |
nUboon2Age |
description |
When Ubuntu is installed on a machine with a wi-fi interface that requires either the b43 or b43-legacy driver, the user experience is awful currently (10.04). Jockey should automatically find, provide, correctly install and activate the proprietary b43 or b43-legacy wireless drivers. Instead not only does it fail in various ways, no troubleshooting information is provided to the user about how to apply workarounds for the Jockey bug, such as the need to connect to the Internet some other way and run the script to work b43-fwcutter package or ndiswrapper or bmcwl sources.
|
The user experience is awful currently (10.04) when Ubuntu is installed on a machine with a wi-fi interface that requires either the b43 or b43-legacy driver. Jockey should automatically find, provide, correctly install and activate the proprietary b43 or b43-legacy wireless drivers. Instead not only does it fail in various ways, no troubleshooting information is provided to the user about how to apply workarounds for the Jockey bug(s), such as the need to connect to the Internet some other way and run the script to work b43-fwcutter package or ndiswrapper or bmcwl sources.
|
|
| 2010-05-16 21:26:46 |
nUboon2Age |
summary |
user experience nightmare for installation of Ubuntu on machines requiring b43 and b43-legacy wireless driver |
Jockey user experience nightmare for installation of Ubuntu on machines requiring b43 and b43-legacy wireless driver |
|
| 2010-05-16 21:27:20 |
nUboon2Age |
description |
The user experience is awful currently (10.04) when Ubuntu is installed on a machine with a wi-fi interface that requires either the b43 or b43-legacy driver. Jockey should automatically find, provide, correctly install and activate the proprietary b43 or b43-legacy wireless drivers. Instead not only does it fail in various ways, no troubleshooting information is provided to the user about how to apply workarounds for the Jockey bug(s), such as the need to connect to the Internet some other way and run the script to work b43-fwcutter package or ndiswrapper or bmcwl sources.
|
The Jockey user experience is awful currently (10.04) when Ubuntu is installed on a machine with a wi-fi interface that requires either the b43 or b43-legacy driver. Jockey should automatically find, provide, correctly install and activate the proprietary b43 or b43-legacy wireless drivers. Instead not only does it fail in various ways, no troubleshooting information is provided to the user about how to apply workarounds for the Jockey bug(s), such as the need to connect to the Internet some other way and run the script to work b43-fwcutter package or ndiswrapper or bmcwl sources.
|
|
| 2010-05-16 21:32:42 |
nUboon2Age |
tags |
|
apport-collected |
|
| 2010-05-16 21:32:55 |
nUboon2Age |
attachment added |
|
.var.log.jockey.log.txt http://launchpadlibrarian.net/48573547/.var.log.jockey.log.txt |
|
| 2010-05-16 21:33:02 |
nUboon2Age |
attachment added |
|
BootDmesg.txt http://launchpadlibrarian.net/48573548/BootDmesg.txt |
|
| 2010-05-16 21:33:06 |
nUboon2Age |
attachment added |
|
Dependencies.txt http://launchpadlibrarian.net/48573550/Dependencies.txt |
|
| 2010-05-16 21:33:11 |
nUboon2Age |
attachment added |
|
Devices.txt http://launchpadlibrarian.net/48573553/Devices.txt |
|
| 2010-05-16 21:33:15 |
nUboon2Age |
attachment added |
|
Lspci.txt http://launchpadlibrarian.net/48573554/Lspci.txt |
|
| 2010-05-16 21:33:19 |
nUboon2Age |
attachment added |
|
Lsusb.txt http://launchpadlibrarian.net/48573587/Lsusb.txt |
|
| 2010-05-16 21:33:25 |
nUboon2Age |
attachment added |
|
ProcCpuinfo.txt http://launchpadlibrarian.net/48573593/ProcCpuinfo.txt |
|
| 2010-05-16 21:33:29 |
nUboon2Age |
attachment added |
|
ProcInterrupts.txt http://launchpadlibrarian.net/48573594/ProcInterrupts.txt |
|
| 2010-05-16 21:33:33 |
nUboon2Age |
attachment added |
|
ProcModules.txt http://launchpadlibrarian.net/48573597/ProcModules.txt |
|
| 2010-05-16 21:33:38 |
nUboon2Age |
attachment added |
|
UdevDb.txt http://launchpadlibrarian.net/48573599/UdevDb.txt |
|
| 2010-05-16 21:33:46 |
nUboon2Age |
attachment added |
|
UdevLog.txt http://launchpadlibrarian.net/48573605/UdevLog.txt |
|
| 2010-05-16 21:38:16 |
nUboon2Age |
description |
The Jockey user experience is awful currently (10.04) when Ubuntu is installed on a machine with a wi-fi interface that requires either the b43 or b43-legacy driver. Jockey should automatically find, provide, correctly install and activate the proprietary b43 or b43-legacy wireless drivers. Instead not only does it fail in various ways, no troubleshooting information is provided to the user about how to apply workarounds for the Jockey bug(s), such as the need to connect to the Internet some other way and run the script to work b43-fwcutter package or ndiswrapper or bmcwl sources.
|
The Jockey user experience is awful when Ubuntu (currently 10.04) is installed on a machine with a wi-fi interface that requires either the b43 or b43-legacy driver. Jockey should automatically find, provide, correctly install and activate the proprietary b43 or b43-legacy wireless drivers. Instead not only does it fail in various ways, no troubleshooting information is provided to the user about how to apply workarounds for the Jockey bug(s), such as the need to connect to the Internet some other way and run the script to work b43-fwcutter package or ndiswrapper or bmcwl sources.
|
|
| 2010-05-17 05:41:02 |
Vish |
branch unlinked |
lp:ubuntu/jockey |
|
|
| 2010-05-17 05:41:21 |
Vish |
branch unlinked |
lp:ubuntu/lucid/jockey |
|
|
| 2010-05-17 05:42:47 |
Vish |
hundredpapercuts: status |
New |
Invalid |
|
| 2010-05-17 05:46:19 |
Vish |
affects |
hundredpapercuts |
null |
|
| 2010-05-17 05:46:58 |
Vish |
affects |
ubuntu |
jockey (Ubuntu) |
|
| 2010-10-06 14:29:15 |
Daniel Stone |
new-user-experience-team: status |
New |
Invalid |
|
| 2010-10-06 14:29:23 |
Daniel Stone |
jockey (Ubuntu): status |
Confirmed |
Opinion |
|
| 2010-10-06 15:00:40 |
Daniel Stone |
new-user-experience-team: importance |
Undecided |
Wishlist |
|
