Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Ubuntu 26.04: the per-user message broker does not start (AppArmor profile for mosquitto)

未關閉
#646 1 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

@ohlincha 已經在處理了。

開始於 2026年10月28日。

評估

這個 Issue 還沒有評估資料。

描述

On Ubuntu 26.04 the mosquitto package (2.0.22) installs an AppArmor profile, /etc/apparmor.d/mosquitto, attached to /usr/sbin/mosquitto. It allows only the system service's files (/etc/mosquitto, /var/lib/mosquitto, /var/log/mosquitto, inet sockets). ECCE starts a per-user broker with its configuration, log and Unix socket under ~/.ECCE (or $XDG_RUNTIME_DIR/ecce-* for long paths), so it cannot read its configuration or create its socket, and ecce-gateway-start ends with "broker did not come up within 10s". Every ECCE app then refuses to start ("no messaging relay for this session").

Found on CI: GitHub's ubuntu-latest moved from 24.04 to 26.04 and the GUI-app suite failed on all apps. CI is pinned to ubuntu-24.04 for now (ea955db5); 9.4.2's Ubuntu package is built on 24.04, as the release notes say. Debian 13 (mosquitto 2.0.21) has no such profile.

Proposed fix: the profile ends with include if exists <local/mosquitto>, the place meant for site additions. The ecce-client package for Ubuntu installs /etc/apparmor.d/local/mosquitto with, roughly,

owner @{HOME}/.ECCE/** rwk,
owner @{run}/user/*/ecce-*/** rwk,
owner /tmp/ecce-*/** rwk,
network unix stream,

and reloads the profile in postinst (apparmor_parser -r /etc/apparmor.d/mosquitto when AppArmor is active). The shared system broker (ecce-broker.service, #191) needs checking against the same profile.

Workaround until then (not yet tested on 26.04; as root): put the lines above into /etc/apparmor.d/local/mosquitto and run apparmor_parser -r /etc/apparmor.d/mosquitto.

Test: the GUI-app suite on an ubuntu-26.04 runner.

主要語言
C
星號
10
分支
8
平均合併
1 小時 58 分鐘
30 天內合併 PR
8

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

FriendsofECCE/ECCE 的其他 Issue

查看 FriendsofECCE/ECCE 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。