Summary: | A quick call to check if the TpDebugSender is enabled | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Mikhail Zabaluev <mikhail.zabaluev> |
Component: | tp-glib | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED INVALID | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | enhancement | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 26388 |
Description
Mikhail Zabaluev
2010-02-02 09:11:28 UTC
I'm not sure whether this is useful? Part of the idea of the Debug interface is that messages go onto a ring-buffer even if broadcasting them over D-Bus is currently disabled, so that after something breaks (other than a CM crash), you can go Help->Debug in Empathy. Empathy will start listening for messages, but also fetch the current contents of the ring-buffer, and hopefully the messages related to the failure won't have scrolled off the top yet. Conditionalizing on whether the debug-sender is enabled would break that. I agree with comment #1. This is not the change I'm looking for. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.