touch-packages team mailing list archive

[Eric Koegel <1347272@xxxxxxxxxxxxxxxxxx>]

Created attachment 5567
Fork before gtk/dbus init

Hey, found another fork bug report. This should fix it in xfsettingsd.

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

Title:
  Several XFCE applications appear irresponsible after communicating
  with a daemon

Status in pixbuf library for gtk+:
  New
Status in One Hundred Papercuts:
  Triaged
Status in System policy:
  Confirmed
Status in Thunar file manager:
  Confirmed
Status in xfce4-appfinder:
  Confirmed
Status in Xfce4 Power Manager:
  Confirmed
Status in xfce4-settings:
  Fix Released
Status in Volume management daemon for XFCE 4:
  Invalid
Status in Volume management daemon for Xfce:
  Confirmed
Status in “gdk-pixbuf” package in Ubuntu:
  Triaged
Status in “policykit-1” package in Ubuntu:
  Triaged
Status in “thunar” package in Ubuntu:
  Triaged
Status in “xfce4-appfinder” package in Ubuntu:
  Triaged
Status in “xfce4-power-manager” package in Ubuntu:
  Triaged
Status in “xfce4-settings” package in Ubuntu:
  Triaged
Status in “xfce4-volumed” package in Ubuntu:
  Triaged

Bug description:
  Several programs in Xfce have a daemon mode call gtk_init() before
  fork()ing.

  This is unsafe, and when it goes wrong this will typically manifest as
  the daemon hanging shortly after forking, and appearing to simply do
  nothing at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+subscriptions