hang if I type after starting a wireless network

RESOLVED EXPIRED

Status

SeaMonkey
General
RESOLVED EXPIRED
14 years ago
12 years ago

People

(Reporter: Scott Otterson, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040116
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040116

If I boot my laptop without the ethernet cable plugged in and then connect
to a wireless network, I see at least these problems:

- Mozilla freezes if I type anything when mozilla is in focus 
  (However, I can browse using the mouse until I hit the keyboard)
- Nautilus hangs forever on startup.  No error messages.
- The panel and the rest of gnome eventually freeze.  

The mozilla freeze does not happen if, before turning on the RF, I type
something into a text box (like the URL window).  I still have the other
problems, though.

Stranger yet, I don't have these problems if I boot with an ethernet cable
connected, unplug it, and then start the RF.

I was running stock Ximian XD2 with the latest redcarpet updates e.g. Mozilla
1.4.2 and Nautilus 2.2.4.  I've just updated to mozilla 1.6 and I see the same
problem.

I'm starting the RF like so:

sudo ifdown eth0
sudo iwconfig eth1 essid scottonet
sudo iwconfig eth1 mode managed
sudo iwconfig eth1 key KEY_VALUE
 
sudo dhclient

Reproducible: Always
Steps to Reproduce:

Comment 1

14 years ago
My build: 2004041918

Reporter, can you please download and use a newer uild.  Your build is a bit
old.  Download a nightly release to see if the problem reoccurs.

If it does, please post what type of wireless network you are using. E.g.
ad-hoc,access point and other details regarding the network.

Can you also check to see if it is not a driver problem of the network card by
updating your drivers.

Thanks
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.