View Single Post
Posts: 462 | Thanked: 550 times | Joined on Sep 2008 @ Moscow
#249
Originally Posted by peterleinchen View Post
avoiding that stop worked
yep, because of stability issues. power users can always remove that sudo, because they know, what they are doing

Originally Posted by Estel View Post
I testes it ~40 times in row (sic! [including lockdown timer]) and it never rebooted. cssu-thumb and kernel-power here (kernel isn't related, probably).

The most I was able to reproduce, were "spawning too fast" or something like that, which deny starting wlancond again, until certain time passes. Highly unlikely to happen in real-life situations, though - to get it, one need to *really* spam stopping and starting wlancond.

/Estel
my scenario's steps are:
1. turn wlan off
2. open modest with autoupdates turned on
3. turn wlan on, connect to network
4. update modest manually
5. turn wlan off
6. lock device (additional step, which is not always necessary)
7. kaboom

the alternative scenarion is using im accounts:
0. availability is turned on, wlan is off
1. turn wlan on, connect to network
2. accounts started connecting/all connected
3. turn wlan off
4. lock device (additional step, which is not always necessary)
5. kaboom

it happens with different kernels (kp mostly), cssu (-testing and -thumb).
 

The Following 2 Users Say Thank You to 412b For This Useful Post: