2014-07-04 19:19:13 |
UlfZibis |
bug |
|
|
added bug |
2014-07-04 19:21:31 |
UlfZibis |
bug task added |
|
gnome-power-manager (Ubuntu) |
|
2014-07-04 19:23:06 |
UlfZibis |
bug task added |
|
hibernated |
|
2014-07-04 19:24:46 |
UlfZibis |
bug task deleted |
software-center (Ubuntu) |
|
|
2014-07-04 19:25:47 |
UlfZibis |
description |
When I then suspend again to standby as workaround and then resume again the network connecting becomes again available.
Because the resume from hibernate takes 2..3 minutes to become finished from hard disk restore, I guess there is some timeout missed to establish the connection again.
Can have somebody have a look on that please? |
When I then suspend again to standby as workaround and then resume again the network connecting becomes again available.
Because the resume from hibernate takes 2..3 minutes to become finished from hard disk restore, I guess there is some timeout missed to establish the connection again.
Can have somebody have a look on that please?
Please excuse, when I have assigned the wrong projects. |
|
2014-07-04 19:26:33 |
UlfZibis |
description |
When I then suspend again to standby as workaround and then resume again the network connecting becomes again available.
Because the resume from hibernate takes 2..3 minutes to become finished from hard disk restore, I guess there is some timeout missed to establish the connection again.
Can have somebody have a look on that please?
Please excuse, when I have assigned the wrong projects. |
When I then suspend again to standby as workaround and then resume again the network connecting becomes again available.
Because the resume from hibernate takes 2..3 minutes to become finished from hard disk restore, I guess there is some timeout missed to establish the connection.
Can have somebody have a look on that please?
Please excuse, when I have assigned the wrong projects. |
|