Hi there,
I suppose that the people interested in this problem may have missed my
last correspondence. Would it be possible for someone to tell me how I can
inform the driver maintainers of this issue? Like I said, I never
experienced this problem using Gutsy or Hardy, so I think it may have been a
recent regression, and I am very interested in helping with the resolution.
I am a computer science student, so I know more than the average user, but I
don't think I would even begin to understand how the driver works enough to
resolve the problem on my own.
Could someone give me some suggestions for who to contact?
Thanks so much
-Mike
On Sun, Nov 2, 2008 at 7:08 PM, Mike Jones <[EMAIL PROTECTED]> wrote:
> Right.
>
> So what do I do about this?
>
> This problem never used to occur before I began using the Ibex beta, it
> worked fine under gutsy, and hardy. Is there somewhere else I should report
> the bug to?
>
> Thanks
>
> -Mike
>
>
> On Sun, Nov 2, 2008 at 5:05 PM, Alexander Sack <[EMAIL PROTECTED]> wrote:
>
>> lockups are driver issues.
>>
>> ** Changed in: linux (Ubuntu)
>> Sourcepackagename: network-manager => linux
>>
>> ** Summary changed:
>>
>> - Network-manager causes system lockup when connecting to specific
>> encrypted network
>> + [bcm...] Network-manager causes system lockup when connecting to
>> specific encrypted network
>>
>> --
>> [bcm...] Network-manager causes system lockup when connecting to specific
>> encrypted network
>> https://bugs.launchpad.net/bugs/289898
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>> Status in "linux" source package in Ubuntu: Incomplete
>>
>> Bug description:
>> Binary package hint: network-manager
>>
>> When connecting to my campus wireless network, the entire system will lock
>> up.
>>
>> the settings currently set in network-manager for this network are
>>
>> name: Auto RHIT-1X
>> Connect automatically
>> ssid: *blank*
>> mode: infastructure
>> bssid *blank*
>> mac address *blank*
>> mtu : automatic
>>
>> secutiry: WPA and WPA2 enterprise
>> authentication: PEAR
>> anonymous id: *blank*
>> ca certificate: none
>> peap version: version 0
>> inner authentication: MSCHAPv2
>> user and pass are my school login's.
>>
>> ipv4 settings: automatic DHCP.
>>
>> i tested this with a freshly updated package as of 10 am central time,
>> Monday, October 27th. THe network manager applet is version
>> 0.7~~svn20081018t105859-0ubuntu1 (intrepid)
>> I am running the Intrepid Ibex beta since around October first, as said
>> before, my most recent update was 10 am central time, Monday, October 27th.
>>
>
>
--
[bcm...] Network-manager causes system lockup when connecting to specific
encrypted network
https://bugs.launchpad.net/bugs/289898
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
