While hardware not detected is troublesome.. documentation on getting the
wireless chip to work is documented.
Ubuntu and linux often need modification to work or function as the end user
would like( this is a known learning curve)
The solution can be found easily because it is not just on
Hi Daniel, indeed the CL is how i solved my problem, but that is completely
beside the point. We're talking about the User Experience bug on Jockey.
Jockey is often ineffective in installing wifi, there's a bug written
against it. end of story
On Wed, Oct 6, 2010 at 7:28 AM, Daniel Stone
** Changed in: new-user-experience-team
Importance: Undecided = Wishlist
--
Jockey user experience nightmare for installation of Ubuntu on machines
requiring b43 and b43-legacy wireless driver
https://bugs.launchpad.net/bugs/578970
You received this bug notification because you are a member
@Alberto Milone wrote: Also you mention 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. I would be glad if you could describe the exact steps that you
followed to get your
You said that Jockey fails in various ways. Can you explain how,
please?
Also you mention 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. I would be glad
if you could
@nUboon2Age: Hi , I would argue that this is a bug and not a usability issue
per-se .
Yes it is troubling for a new user when stuff doesnt work out of the box. I
dont disagree with that.
But if this bug a usability bug , wouldn't that mean any hardware not being
detected is a usability issue?
@nUboon2Age: Also to note that we would be shortly announcing a few tags which
are relevant to usability issues.
You can follow this blueprint regarding the tags
https://blueprints.launchpad.net/ubuntu/+spec/design-m-heuristics-and-bugs
--
Jockey user experience nightmare for installation of
@Vish, thank you for your response, but none of that info explains how
we should address an Ubuntu User Experience bug, which we both know is
different than writing a regular technical bug. It sounds like you are
on the hundredpapercuts project, so it seems like you or someone you
know would be
http://brainstorm.ubuntu.com/item/12370/
Idea #12370: Developers with focus on user experience
* Description
* Report duplicate
* Help promote this idea!
Written by Madsrh the 20 Aug 08 at 10:54. Category: Look and Feel. Status: New
Rationale
As a desktop OS Ubuntu needs
http://brainstorm.ubuntu.com/idea/24481/
Idea #24481: Proprietary drivers hard to install
* Description
* Report duplicate
* Help promote this idea!
Written by MasterNetra the 18 Apr 10 at 15:01. Category: System. Related
project: Nothing/Others. Status: New
Rationale
My
Solution posted to the above
#4
Solution #6: Just fix the bugs in Hardware Drivers (jockey-gtk)
Written by aysiu the 27 Apr 10 at 17:18.
This already happens in theory. It just has to be implemented better.
--
Jockey user experience nightmare for installation of Ubuntu on machines
requiring
As Mark Shuttleworth wrote in
Design, user experience and development at Canonical
Wednesday, September 10th, 2008
There’s also recognition for the scale of the challenge that faces us.
When I laid out the goal of “delivering a user experience that can
compete with Apple in two years” at OSCON,
** Summary changed:
- 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
** Description changed:
- The user
Architecture: i386
CurrentDmesg:
[ 41.588441] ndiswrapper (iw_set_auth:1602): invalid cmd 12
[ 42.059314] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 52.256033] wlan0: no IPv6 routers present
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release
Thank you for bringing this bug to our attention. However, a paper cut
should be a small usability issue, in the default Ubuntu install, that
affects many people and is quick and easy to fix. So this bug can't be
addressed as part of this project.
- This is a hardware specific issue , Not a
@NUboon2Age : Seems like you are new to launchpad , the branch linking
and tagging other usability projects for a bug report is not the right
way to do it.
You may find it helpful to read How to report bugs effectively
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.
You can learn more
16 matches
Mail list logo
