Ticket #36 (defect)

Opened 4 years ago

Last modified 4 years ago

Uninitting and re-initting after a GalagoService was created causes D-BUS issues

Status: closed (fixed)

Reported by: chipx86 Assigned to: chipx86
Priority: high Milestone: Glib Rewrite
Component: libgalago Version: 0.5.0
Severity: critical Keywords:
Cc: D-BUS Version:
Patch Included: OS/Distro Version:

This is an odd bug, but if you init a feed, create a service, uninit galago, and then init galago as either a feed or a a client, D-BUS will complain with "Not enough memory" errors, or other errors. This does not happen with any other object, it seems.

This will trigger the problem: 

galago_init("test", TRUE);
galago_create_service("dummy-service", "Dummy Service", 0);
galago_uninit();

/* This will fail. */
galago_init("test", FALSE);

Change History

04/04/06 15:55:35: Modified by chipx86

  • version set to 0.5.0.
  • severity changed from blocker to critical.

Worked around this for now by just not uninitting the D-BUS connection. This isn't a good solution, but it works for now. It's likely that this is actually a D-BUS problem. More investigation will have to be done.

04/19/06 18:00:10: Modified by chipx86

  • status changed from new to closed.
  • resolution set to fixed.

Actually, maybe this is fine. We don't want to get rid of an existing D-BUS connection anyway. Let's just call it fixed, since we now work around it fine.