Minha versão do Ubuntu MX4 não está mais sendo bloqueada automaticamente. Ele acorda para notificações e deixa a tela ativada. Este é um dreno de bateria importante. Isso tem sido desde que eu atualizei para ubuntu-touch / stable / meizu.en r2, ou desde que eu definir o tempo de bloqueio de tela para nunca e de volta para 1 minuto. (Eu notei o comportamento apenas quando eu definir o tempo de bloqueio de volta para 1 minuto, e eu tinha atualizado até então)
Agora as perguntas são: Qual processo monitora isso? Por que está ficando acordado? Qual arquivo contém as configurações reais de tempo limite? Como posso investigar o que está acontecendo?
EDITAR
Então eu também arquivei um bug no launchpad para isso, mas até agora ninguém mais parece ser afetado. É realmente só eu? Eu adicionei algumas informações para powerd, mas não tenho certeza se esse é o serviço que gerencia isso.
Quando eu corri powerd-cli test
todos passaram, exceto o primeiro:
Test: checkForDbusName(test_dbusname, 0, requests, TRUE)
result: FAILED
Test: checkForDbusName(powerd_cli_bus_name, 1, requests, TRUE)
result: PASSED
Test: clearSysState(main_cookie) == TRUE
result: PASSED
Test: checkForDbusName(powerd_cli_bus_name, 0, requests, TRUE)
result: PASSED
Test: requestSysState(name, POWERD_SYS_STATE_ACTIVE, &cookies[i]) == TRUE
result: PASSED
Test: requestSysState(name, POWERD_SYS_STATE_ACTIVE, &cookies[i]) == TRUE
result: PASSED
Test: requestSysState(name, POWERD_SYS_STATE_ACTIVE, &cookies[i]) == TRUE
result: PASSED
Test: requestSysState(name, POWERD_SYS_STATE_ACTIVE, &cookies[i]) == TRUE
result: PASSED
Test: requestSysState(name, POWERD_SYS_STATE_ACTIVE, &cookies[i]) == TRUE
result: PASSED
Test: requests->len >= TEST_NUM_SYS_REQUESTS+1
result: PASSED
Test: checkForDbusName(powerd_cli_bus_name, TEST_NUM_SYS_REQUESTS+1, requests, TRUE)
result: PASSED
Test: clearSysState(cookies[i]) == TRUE
result: PASSED
Test: clearSysState(cookies[i]) == TRUE
result: PASSED
Test: clearSysState(cookies[i]) == TRUE
result: PASSED
Test: clearSysState(cookies[i]) == TRUE
result: PASSED
Test: clearSysState(cookies[i]) == TRUE
result: PASSED
Test: requests->len >= 1
result: PASSED
Test: checkForDbusName(powerd_cli_bus_name, 1, requests, TRUE)
result: PASSED
Test: clearSysState(cookies[i]) == FALSE
result: PASSED
Test: clearSysState(cookies[i]) == FALSE
result: PASSED
Test: clearSysState(cookies[i]) == FALSE
result: PASSED
Test: clearSysState(cookies[i]) == FALSE
result: PASSED
Test: clearSysState(cookies[i]) == FALSE
result: PASSED
Test: clearSysState("bad cookie") == FALSE
result: PASSED
Test: requests->len >= 1
result: PASSED
Test: checkForDbusName(powerd_cli_bus_name, 1, requests, TRUE)
result: PASSED
Test: requestSysState("test-cookie", POWERD_SYS_STATE_SUSPEND, &cookie) == FALSE
result: PASSED
Test: requestSysState("test-cookie", -1, &cookie) == FALSE
result: PASSED
Test: requestSysState("test-cookie", POWERD_NUM_POWER_STATES, &cookie) == FALSE
result: PASSED
Test: requestSysState("test-cookie", POWERD_NUM_POWER_STATES+1, &cookie) == FALSE
result: PASSED
Test: clearSysState(main_cookie) == TRUE
result: PASSED
Test: checkForDbusName(powerd_cli_bus_name, 0, requests, TRUE)
result: PASSED
Abaixo está a saída completa e as entradas do syslog por um período em que eu
- Comece com um telefone bloqueado
- virar na tela pressionando o botão
- Aguarde 2 minutos e desligue-o novamente. (o tempo de bloqueio é de 1 minuto. Também não desliga após 1 hora)
Jul 5 22:12:08 ubuntu-phablet powerd[3893]: handle_requestSysState from :1.13 (com.canonical.Unity.Screen) - ACTIVE (1)
Jul 5 22:12:08 ubuntu-phablet powerd[3893]: name_watch_add: looking for :1.13
Jul 5 22:12:08 ubuntu-phablet powerd[3893]: watching :1.13 to see when it disappears on dbus
Jul 5 22:12:08 ubuntu-phablet powerd[3893]: libsuspend: acquire_wake_lock: powerd_power_request
Jul 5 22:12:08 ubuntu-phablet powerd[3893]: handle_requestSysState - SUCCESS
Jul 5 22:12:08 ubuntu-phablet powerd[3893]: Enqueue state change to ACTIVE
Jul 5 22:12:08 ubuntu-phablet powerd[3893]: exiting suspend
Jul 5 22:12:08 ubuntu-phablet powerd[3893]: libsuspend: calling exit_suspend
Jul 5 22:12:08 ubuntu-phablet powerd[3893]: libsuspend: exit_suspend succeeded
Jul 5 22:12:08 ubuntu-phablet powerd[3893]: Emitting signal for transition to state ACTIVE (1)
Jul 5 22:12:08 ubuntu-phablet powerd[3893]: Transition to ACTIVE complete
Jul 5 22:12:08 ubuntu-phablet powerd[3893]: libsuspend: release_wake_lock: powerd_power_request
Jul 5 22:12:08 ubuntu-phablet powerd[3893]: light_dev: setting brightness to 78
Jul 5 22:12:08 ubuntu-phablet powerd[3893]: we get signal from :1.14: DisplayPowerStateChange
Jul 5 22:12:08 ubuntu-phablet powerd[3893]: Received DisplayPowerStateChange: state=1 flags=2
Jul 5 22:12:12 ubuntu-phablet powerd[3893]: handle_requestSysState from :1.22 (usensord) - ACTIVE (1)
Jul 5 22:12:12 ubuntu-phablet powerd[3893]: name_watch_add: looking for :1.22
Jul 5 22:12:12 ubuntu-phablet powerd[3893]: watching :1.22 to see when it disappears on dbus
Jul 5 22:12:12 ubuntu-phablet powerd[3893]: libsuspend: acquire_wake_lock: powerd_power_request
Jul 5 22:12:12 ubuntu-phablet powerd[3893]: handle_requestSysState - SUCCESS
Jul 5 22:12:12 ubuntu-phablet powerd[3893]: Enqueue state change to ACTIVE
Jul 5 22:12:12 ubuntu-phablet powerd[3893]: queue empty && state == current, discarding
Jul 5 22:12:12 ubuntu-phablet powerd[3893]: libsuspend: release_wake_lock: powerd_power_request
Jul 5 22:12:15 ubuntu-phablet powerd[3893]: handle_clearSysState from :1.22, cookie: 8096ad4e-6c90-4852-97e2-dac9866d21e0
Jul 5 22:12:15 ubuntu-phablet powerd[3893]: clear_sys_request: usensord - :1.22
Jul 5 22:12:15 ubuntu-phablet powerd[3893]: name_watch_remove: looking for :1.22
Jul 5 22:12:15 ubuntu-phablet powerd[3893]: name_watch: ref_count for :1.22 is now 0
Jul 5 22:12:15 ubuntu-phablet powerd[3893]: no longer watching :1.22, there are no more requests
Jul 5 22:12:15 ubuntu-phablet powerd[3893]: libsuspend: acquire_wake_lock: powerd_power_request
Jul 5 22:12:15 ubuntu-phablet powerd[3893]: Enqueue state change to ACTIVE
Jul 5 22:12:15 ubuntu-phablet powerd[3893]: queue empty && state == current, discarding
Jul 5 22:12:15 ubuntu-phablet powerd[3893]: libsuspend: release_wake_lock: powerd_power_request
Jul 5 22:14:27 ubuntu-phablet powerd[3893]: light_dev: setting brightness to 0
Jul 5 22:14:27 ubuntu-phablet powerd[3893]: we get signal from :1.14: DisplayPowerStateChange
Jul 5 22:14:27 ubuntu-phablet powerd[3893]: Received DisplayPowerStateChange: state=0 flags=2
Jul 5 22:14:27 ubuntu-phablet powerd[3893]: handle_clearSysState from :1.13, cookie: 28dfac1e-72a2-4e07-81c2-eb50380d620d
Jul 5 22:14:27 ubuntu-phablet powerd[3893]: clear_sys_request: com.canonical.Unity.Screen - :1.13
Jul 5 22:14:27 ubuntu-phablet powerd[3893]: name_watch_remove: looking for :1.13
Jul 5 22:14:27 ubuntu-phablet powerd[3893]: name_watch: ref_count for :1.13 is now 0
Jul 5 22:14:27 ubuntu-phablet powerd[3893]: no longer watching :1.13, there are no more requests
Jul 5 22:14:27 ubuntu-phablet powerd[3893]: libsuspend: acquire_wake_lock: powerd_power_request
Jul 5 22:14:27 ubuntu-phablet powerd[3893]: Enqueue state change to SUSPEND
Jul 5 22:14:27 ubuntu-phablet powerd[3893]: libsuspend: prepare_suspend.
Jul 5 22:14:27 ubuntu-phablet powerd[3893]: Emitting signal for transition to state SUSPEND (0)
Jul 5 22:14:27 ubuntu-phablet powerd[3893]: entering suspend
Jul 5 22:14:27 ubuntu-phablet powerd[3893]: libsuspend: calling enter_suspend
Jul 5 22:14:27 ubuntu-phablet powerd[3893]: libsuspend: enter_suspend succeeded
Jul 5 22:14:27 ubuntu-phablet powerd[3893]: Transition to SUSPEND complete
Jul 5 22:14:27 ubuntu-phablet powerd[3893]: libsuspend: release_wake_lock: powerd_power_request
O que significa que testdbus_name
está falhando? O que deve acontecer quando os autolocks de tela? Alguém poderia executar algum teste semelhante e postar o arquivo de log aqui?