Public bug reported:

After recent changes to scope settings handling in shell plugin (the
switch from QSettings to glib-based settings) we now get empty
settings.ini and settings dir created for absolutely every scope in the
system, even if it doesn't offer any settings. This doesn't pose any
issues as far as I can tell (other than polluting fs), but it would be
nice not to do that if not needed.

** Affects: canonical-devices-system-image
     Importance: Undecided
         Status: New

** Affects: unity-scopes-shell (Ubuntu)
     Importance: Undecided
         Status: Confirmed

** Changed in: unity-scopes-shell (Ubuntu)
       Status: New => Confirmed

** Also affects: canonical-devices-system-image
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1583055

Title:
  Empty settings.ini created for every scope even if it doesn't have
  settings

Status in Canonical System Image:
  New
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  After recent changes to scope settings handling in shell plugin (the
  switch from QSettings to glib-based settings) we now get empty
  settings.ini and settings dir created for absolutely every scope in
  the system, even if it doesn't offer any settings. This doesn't pose
  any issues as far as I can tell (other than polluting fs), but it
  would be nice not to do that if not needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583055/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to