desktop-packages team mailing list archive

[Launchpad Bug Tracker <589829@xxxxxxxxxxxxxxxxxx>]

[Expired for gconf (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gconf (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/589829

Title:
  Disabling network after ORBIIOPUSock=0 causes virtual session-freeze.

Status in “gconf” package in Ubuntu:
  Expired

Bug description:
  Binary package hint: gconf

  After I put this into my ~/.orbitrc for some local development work:

  ORBIIOPUSock=0
  ORBIIOPIPv4=1
  ORBIIOPIPv6=0
  ORBNetID=ipaddr

  ... all hell broke lose when I disabled networking through the panel.

  Obviously everything depending on gconf stopped working, terminals
  froze and it was only after a while a GUI application properly
  reported the COMM_FAILURE dialog and I realized what was happening.

  I had to switch to a tty to re-enable networking so the programs could
  reach gconfd again (gnome-panel was frozen too).

  Well. This definitively sucks. Let's not talk about whether or not one
  should disable ORBIIOPUSock - there are valid reasons.

  In my case I'm developing an application talking to an ORB which
  prefers not to receive IOR profiles it doesn't understand.

  What exactly the solution is I don't know (which is why I am not yet
  reporting this upstream).

  One possibility would be for libgconf to enfore ORBIIOPUSock.

  Or it could set ORBNoUserRC (or better ORBNoSystemRC).

  Or all applications could pass it along using argv/argc to libgconf
  (if the API allows that).

  I don't know if upstream would care about this - this is more a
  configuration issue really... but AFAIK there currently is no way to
  configure it, while still allowing system- and user-specific
  orbitrcs...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/589829/+subscriptions