Skip to content

fix: delay conky restart after network activation - #66

Merged
PC-FREEDOM merged 1 commit into
mainfrom
fix/conky-restart-network-activation-delay
Sep 22, 2026
Merged

PC-FREEDOM merged 1 commit into
mainfrom
fix/conky-restart-network-activation-delay

Conversation

@PC-FREEDOM

Copy link
Copy Markdown
Owner

Summary

  • add a 2-second delay before restarting Conky from the NetworkManager dispatcher
  • address a real-hardware race where Conky restarted before the Wi-Fi default route/interface state had fully settled
  • extend the Conky network restart tests to verify the delay and restart ordering

Reproduction / verification context

  • reproduced on Legacy BIOS hardware using a USB Wi-Fi adapter (wlx0090fee6a5f7)
  • networking itself was functional, but Conky stayed at Down: 0B / Up: 0B
  • manual dispatcher execution fixed the display
  • adding sleep 2 before Conky restart and then reconnecting Wi-Fi made the display update correctly

Tests

  • persistence: 298 PASS / 0 FAIL
  • edition-build: 185 PASS / 0 FAIL
  • desktop-polish: 751 PASS / 0 FAIL
  • usb-persistence-image: 94 PASS / 0 FAIL
  • test_conky_network_restart.sh: 53/53
  • git diff --check: clean

Scope

  • dispatcher script and related test only
  • no Conky display logic changes
  • no other NetworkManager configuration changes
  • no ISO/generated artifacts or reports/ai-review/ changes

実機Legacy BIOS環境・USB Wi-Fiアダプタ(wlx0090fee6a5f7)で、NetworkManager
dispatcherの"up"イベントが接続のactivated/default route確定より前に
発火し、Conky再起動時点で${gw_iface}が未確定のままDown/Upが0Bに固定
される不具合を修正した。

01-mypocketos-conky-restartで、既存Conkyプロセスをkillした後、
再起動直前に固定2秒のsleepを追加した。実機でWi-Fi切断→再接続を行い、
Down/Up表示が正常に更新されることを確認済み。

tests/desktop-polish/test_conky_network_restart.shに、sleepの存在・
配置順序(kill後・再起動前)の静的確認と、実際に約2秒の遅延が発生する
ことを計測するシナリオを追加した。

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@PC-FREEDOM
PC-FREEDOM merged commit 41cbb23 into main Sep 22, 2026
2 checks passed
PC-FREEDOM added a commit that referenced this pull request Sep 23, 2026
Reflect the final pre-release hardware validation results in the spec.

- UEFI + Secure Boot: on 2026-09-23, re-confirmed on the same physical
  UEFI machine, using the final candidate ISO (commit 41cbb23, which
  includes the Conky NetworkManager dispatcher fix) that the boot
  menu displays, the Standard Live desktop is reached, and Japanese
  display and basic UI have no major corruption (sections 3, 10.1.4,
  16.2, 17)
- Legacy BIOS, low-spec physical machine (Core 2 Duo T9550, 4GB RAM):
  confirmed Standard Live boot, USB Wi-Fi adapter recognition,
  NetworkManager connection, ping, and real Firefox communication
  (sections 16.2 and 17, new rows)
- Persistence on a UEFI-created USB: confirmed on a physical UEFI
  machine that creating a Persistence area via the GUI, rebooting into
  "MyPocketOS Live (Persistence)", Conky showing Persistence mode, and
  persistence-test.txt surviving reboot (i.e. /home persistence) all
  work (sections 3, 16.2, 17)
- Conky network display fix: added the technical background and the
  real-hardware confirmation that Down/Up now updates automatically
  after Wi-Fi connects, with no manual action, to section 5.3
- Minimum RAM: no new measurement was taken. The Calamares install
  requirement of "about 2 GiB or more" is kept, while the exact
  minimum RAM for the Live environment remains unmeasured; this is now
  explicitly treated as not a release-blocking gate (sections 16.2,
  17)
- Section 17 "GitHub CI PASS" row: replaced the stale HEAD reference
  (e5f5e16) with a statement that the two required status checks
  (mypocketos-tests, static-checks) both succeeded on 41cbb23 (PR #66,
  the last production-code change and the ISO build baseline), and
  that later doc-only PRs (e.g. #67) are not treated as the build
  baseline

All entries in the section 17 completion table are now checked; none
are left as an open box. Previously recorded confirmed dates and
values are unchanged. The ISO build baseline commit (41cbb23) is
unchanged.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant