*** This bug is a duplicate of bug 446889 ***
https://bugs.launchpad.net/bugs/446889
Ok, this is becoming way more complicated than it needs to be. You don't need
to worry about filing another bug anymore, as it appears that this problem was
already reported in bug 446889. I will mark this
I don't see that you filed any other bugs. However, it looks like this
has already been filed as bug 446889 - do you agree? If so, you can
mark this bug as a duplicate of that one and confirm that bug. It
already has a Canonical developer assigned to it.
--
Linksys WUSB54GC with Ralink chip RT
OK, I went back to the Ubuntu system and tried to file the report again and
this ia what happened:
jaspm...@kbeta:~$ su
r...@kbeta:/home/jaspmatt# ubuntu-bug linux
GConf Error: Failed to contact configuration server; some possible causes
are that you need to enable TCP/IP networking for ORBit, or
I couldn't use ubuntu-bug linux (apport) on the Mint system so I just filed
a regular new bug report on Mint via launchpad. The first time I hit submit
it bitched at me because it said the module name was incorrect. The second
time it seemed to take it ok, the screen blanked out and it said "done
I don't see your bug report - apport should have shown its screen
collecting information, then prompted you to file the report. If you
accept, then it should take you to the Launchpad bug filing page where
you say you want to file a new report. You type out your description,
and then submit. Did
I filed a new bug report a few minutes ago and it seemed to take it but so
far has not sent any confirmation.
On Sun, Dec 13, 2009 at 11:10 AM, Connor Imes
wrote:
> Jimbob, you should file the report from the Ubuntu system that has the
> wireless card, not from your Mint box. Even though you go
Jimbob, you should file the report from the Ubuntu system that has the
wireless card, not from your Mint box. Even though you got it to work
by manually adding the driver, the report is still valid. You can't do
it from your Mint box because apport-collect gets data direct from the
computer, so i
I tried to report the bug this AM and this is what came up:
*M8 jaspmatt # ubuntu-bug linux
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
...
*** Problem in linux-image-2.6.31-14-generic
The
That is still acceptable, Jimbob, you can just say in your report that
you were able to get it to work by doing that.
--
Linksys WUSB54GC with Ralink chip RT3070
https://bugs.launchpad.net/bugs/351699
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The only system I can do this on right now is a new Mint installation using
kernel 2.6.31-14-generic. The Ubuntu system I have already fixed by
compiling and make, make install the latest driver from the Ralink website.
Is this acceptable?
On Thu, Dec 10, 2009 at 8:55 PM, Connor Imes wrote:
>
Jimbob, it is easier if you use apport to file a new bug so it will
automatically attach some necessary information to the report. On the machine
that has the problem, connect to the internet in whatever way you can and run
ubuntu-bug linux
to file a bug report against the kernel for hardware
No, it does not work out of the box with Karmic. It attempts to use driver
rt2800usb which is incorrect for the RT3070 chip so it fails.. Do you want
me to file a new bug or continue the old one?
J.
On Tue, Dec 8, 2009 at 10:20 PM, Connor Imes
wrote:
> Jimbob, thank you for taking the time to
Jimbob, thank you for taking the time to report this. Does your
WUSB54GC with the RT3070 chipset work out of the box now in Karmic? If
not, have you filed a separate bug for it?
** Changed in: ubuntu-docs (Ubuntu)
Status: New => Incomplete
--
Linksys WUSB54GC with Ralink chip RT3070
htt
WUSB54GC-EU v2 works in Karmic
--
Linksys WUSB54GC with Ralink chip RT3070
https://bugs.launchpad.net/bugs/351699
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.ubu
Same goes for WUSB54GC-EU v2 - it has USB ID 1737:0073 and is not
detected by Jaunty. The Windows driver shows that it has the RTL8187B
chipset.
--
Linksys WUSB54GC with Ralink chip RT3070
https://bugs.launchpad.net/bugs/351699
You received this bug notification because you are a member of Ubuntu
15 matches
Mail list logo
