[gutsy] the wifi « died » after a few minutes

Bug #147596 reported by Olivier Guéry
4
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Low
Brian Murray

Bug Description

Fresh installation on a dell inspiron 1520

No problem with wired network.
No problem to connect to wifi.
But after a few minutes, the network died :
* can’t go back to wired
* can’t use « network » from System > Administration to connect
* /etc/init.d/network start gave me nothing
* « network-manager » in a console give me an : can’t find /usr/bin/esd

So, I install esound ! « esound-common » was installed but not « esound »

It seem’s to work…

Hope it can help.

Revision history for this message
Alexander Sack (asac) wrote :

please post your /var/log/syslog (that contains the incident)

Changed in network-manager:
status: New → Incomplete
Revision history for this message
Olivier Guéry (nemolivier) wrote :

Here is the syslog.

Today the wifi run well (I don’t use it much).
But when I plugged back the cable it failed to found it.
I had to « forced » it in network-manager applet.
When I unplugged it, it can’t log to the wifi again.

Revision history for this message
Alexander Sack (asac) wrote :

that syslog doesn't contain a connection attempt to your wifi network. Please do that, wait till it dies and then attach your syslog again.

 - Alexander

Revision history for this message
Olivier Guéry (nemolivier) wrote :

Maybe this one is better.
It was on sunday (the 30th), around 17:00 / 18:00 I think.
My wireless is eth1 and my local network : uranie (WPA key)
Now everything seems to work well (but I don’t use this computer a lot : it’s my girlfriend one).
Since I install « esound »
Do you want me to remove this package for test ?

Sorry If this information are not very usefull…

Olivier.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Now that the final version of Gutsy Gibbon is available we were wondering if this issue still exists. Thanks in advance.

Changed in network-manager:
importance: Undecided → Low
Revision history for this message
Brian Murray (brian-murray) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.

Changed in network-manager:
assignee: nobody → brian-murray
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.