2008-10-24 22:03:08 |
takeda64 |
bug |
|
|
added bug |
2008-10-25 05:30:33 |
FredBezies |
None: bugtargetdisplayname |
Ubuntu |
network-manager (Ubuntu) |
|
2008-10-25 05:30:33 |
FredBezies |
None: bugtargetname |
ubuntu |
network-manager (Ubuntu) |
|
2008-10-25 05:30:33 |
FredBezies |
None: statusexplanation |
|
Moving to right component in order to get it triaged. But it smells like a duplicate of a known bug.
Can you provide more technical info : just type in a terminal :
lspci -vvnn > lspci.log
Thanks. |
|
2008-10-25 05:30:33 |
FredBezies |
None: title |
Bug #288922 in Ubuntu: "Network Manager sometimes needs to be restarted when coming back from Standby/Hibernation" |
Bug #288922 in network-manager (Ubuntu): "Network Manager sometimes needs to be restarted when coming back from Standby/Hibernation" |
|
2008-10-25 06:08:20 |
takeda64 |
bug |
|
|
added attachment 'lspci.log' (lspci.log) |
2008-10-25 06:10:01 |
takeda64 |
bug |
|
|
added attachment 'lspci.log' (lspci.log) |
2008-10-27 00:51:01 |
Alexander Sack |
network-manager: status |
New |
Incomplete |
|
2008-10-27 00:51:01 |
Alexander Sack |
network-manager: statusexplanation |
Moving to right component in order to get it triaged. But it smells like a duplicate of a known bug.
Can you provide more technical info : just type in a terminal :
lspci -vvnn > lspci.log
Thanks. |
when this happens, could you check whether NetworkManager and nm-applet process is still running?
|
|
2008-12-15 15:18:31 |
Alexander Sack |
bug |
|
|
assigned to wpasupplicant (Ubuntu) |
2008-12-15 15:18:31 |
Alexander Sack |
bug |
|
|
assigned to linux (Ubuntu) |
2008-12-31 18:48:52 |
Alexander Sack |
network-manager: status |
Incomplete |
Triaged |
|
2008-12-31 18:48:52 |
Alexander Sack |
network-manager: importance |
Undecided |
Medium |
|
2008-12-31 18:48:52 |
Alexander Sack |
network-manager: statusexplanation |
when this happens, could you check whether NetworkManager and nm-applet process is still running?
|
so far i understand that killing wpa_supplicant after restart helps. So for now I assume that NM sends a dbus signal for scan before wpasupplicant is ready. Will set NM and wpasupp to triaged until we found where to fix this best.
Maybe you could also try the latest intrepid bits in the network manager PPA? (https://edge.launchpad.net/~network-manager/+archive). Thanks. |
|
2008-12-31 18:49:10 |
Alexander Sack |
wpasupplicant: status |
New |
Triaged |
|
2008-12-31 18:49:10 |
Alexander Sack |
wpasupplicant: importance |
Undecided |
Medium |
|
2008-12-31 18:49:10 |
Alexander Sack |
wpasupplicant: statusexplanation |
|
|
|
2009-08-16 11:44:31 |
Henrik |
nominated for series |
|
Ubuntu Karmic |
|
2009-08-27 00:02:47 |
Leann Ogasawara |
linux (Ubuntu): status |
New |
Incomplete |
|
2010-08-15 10:28:02 |
leo.sutton |
bug |
|
|
added subscriber leo.sutton |
2010-11-16 01:25:46 |
kenden |
bug |
|
|
added subscriber kenden |
2011-02-24 23:39:39 |
Julian Wiedmann |
removed subscriber Julian Wiedmann |
|
|
|
2012-03-09 17:29:26 |
papukaija |
bug |
|
|
added subscriber papukaija |
2012-03-09 17:29:34 |
papukaija |
removed subscriber papukaija |
|
|
|
2012-03-09 17:29:57 |
papukaija |
marked as duplicate |
|
524454 |
|
2012-03-09 17:30:02 |
papukaija |
bug |
|
|
added subscriber papukaija |