ubuntustudio-bugs team mailing list archive

[Tim Starling <1851573@xxxxxxxxxxxxxxxxxx>]

By replacing debconf-kde-helper with a shell script, I logged its
environment, which contains only:

DEBCONF_DB_REPLACE=configdb
DEBCONF_DB_OVERRIDE=Pipe{infd:none outfd:none}
DISPLAY=:0
DEBIAN_FRONTEND=kde

This small environment is apparently set up by
pk_client_create_helper_argv_envp() in packagekit. You can reproduce the
error dialog by just running

 env -i DISPLAY=:0 /usr/bin/debconf-kde-helper

With strace you can see a lot of attempted access to //.config,
//.local, etc. I collected a backtrace for the access to
//.config/debconf-kde-helperrc. It comes from the KSharedConfig
constructor. The error dialog is shown by KConfig::isConfigWritable().

The HOME environment variable is read by QFileSystemEngine::homePath().
There is no easy way for an application to prevent it from being read.
So it seems like the simplest solution is to patch packagekit.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to kde-runtime in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1851573

Title:
  configuration file //.config/debconf-kde-helperrc not writable

Status in KDE Base Runtime:
  New
Status in kde-runtime package in Ubuntu:
  Confirmed

Bug description:
  Running ubuntu 19.10 with plasma 5.17 backport. When I run Configure -
  system settings module from bluetooth icon on icon tray it displays
  the error:

  debconf-kde-helper - KDialog
  Configuration file "//.config/debconf-kde-helperrc" not writable.
  Please contact your system administrator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-runtime/+bug/1851573/+subscriptions