debconf-kde-helper warns "//.config/debconf-kde-helperrc not writable" on every update — please backport upstream fix 4c97ea7 to the 1.2.8 package
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 2/5
- Geschätzter Aufwand
- 1-3 Stunden
- Anfängerfreundlichkeit
- 45/100
Rechercherichtung
The environment for the debconf helper is built in pk_client_create_helper_argv_envp() in lib/packagekit-glib2/pk-client.c. Start with upstream commit 4c97ea7, which adds the extra env vars, and check whether it applies cleanly to the 1.2.8 source tree. Done means the patched 1.2.8 package sets XDG_CONFIG_HOME for the helper and the KDialog warning no longer appears on a Mint 22.x update. Packaging the patch for the Mint release is maintainer work and may need a reviewer.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Affected
- Linux Mint 22.3 "Zena" (Ubuntu 24.04 base), KDE Plasma 5.27
packagekit 1.2.8+mint3+wilma
Symptom
On every MintUpdate run, debconf-kde-helper pops up a KDialog:
Configuration file "//.config/debconf-kde-helperrc" not writable.
Please contact your system administrator.
The update itself completes normally — this is a warning, not a failure.
Root cause
PackageKit builds a minimal environment for the debconf helper in pk_client_create_helper_argv_envp() (lib/packagekit-glib2/pk-client.c). It does not pass HOME or XDG_CONFIG_HOME, so the Qt-based debconf-kde-helper resolves its KConfig path as //.config/debconf-kde-helperrc, i.e. /.config/... at the filesystem root. That directory does not exist and is not writable, so KConfig emits the warning.
Same issue as Launchpad #1851573.
Upstream status
Fixed upstream in PackageKit commit 4c97ea734dc60c4edbdd98da37cd496fd5af35ca — "client: Pass a few more env vars to the debconf helper to fix Qt helpers". It sets XDG_CONFIG_HOME=$XDG_RUNTIME_DIR/config and forwards XDG_SESSION_DESKTOP, LANG and LANGUAGE.
I verified the commit is contained in the v1.3.4, v1.3.6 and v1.4.0 tags, so any 1.3.x build already has it. It is not in 1.2.8.
Why a backport is needed for Mint 22.x
1.3.x cannot simply be dropped into zena: packagekit 1.3.6 depends on libapt-pkg7.0 (apt 2.9+), while zena ships apt 2.8.4 / libapt-pkg6.0t64, and libapt-pkg7.0 is not present in the noble or Mint repositories. The fix itself is a few lines in pk_client_create_helper_argv_envp() and is self-contained, so it should be straightforward to carry in the 1.2.8 package.
Mint 22.x is supported until April 2029, so KDE users will keep seeing this dialog on every update until then.
Workaround used locally
Created /.config and /.config/debconf-kde-helperrc owned by the user, which gives the helper a writable path. That is a per-machine hack, not a fix.
Request
Please backport commit 4c97ea7 to the 1.2.8 package for Mint 22.x. Mint 27 (1.3.4) should already be covered by the upstream fix.
- Vorherrschende Sprache
- C
- Sterne
- 1
- Forks
- 2
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus linuxmint/packagekit
-
Merge upstreamOffen
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 25/100
linuxmint/packagekit#2 · 4 Kommentare ·
Alle Issues in linuxmint/packagekit
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
Maintainer antworten meist innerhalb von 1 Tag
-
isolation2 lockmodes fails on cassert builds: extra AccessShareLock on partition rootEvtl. vergeben @tuhaihe hat das heute übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
apache/cloudberry#2356 ·
Maintainer antworten meist innerhalb von 2 Tagen
-
windows-artifacts: the win-arm64 job uses a Visual Studio generator missing from windows-11-armOffen
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 86/100
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
wasm-micro-runtime/wasm-micro-runtime#5217 ·
Maintainer antworten meist innerhalb von 3 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
Maintainer antworten meist innerhalb von 1 Tag