Bug 14603 - tp-glib should not force our fatal-criticals policy on all CMs
Summary: tp-glib should not force our fatal-criticals policy on all CMs
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-glib (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-21 05:01 UTC by Simon McVittie
Modified: 2009-12-18 09:29 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Simon McVittie 2008-02-21 05:01:05 UTC 
tp_run_connection_manager() makes critical warnings fatal. Perhaps it shouldn't, since this is global state.

*Our* connection managers should of course continue to set fatal criticals, because we want to write non-buggy code...
Comment 1 Dafydd Harries 2008-02-21 05:36:35 UTC 
I advocate leaving fatal-criticals on until somebody complains. I'm surprised that criticals aren't fatal by default given their name.

fatal-errors is perhaps more contentious.
Comment 2 Sjoerd Simons 2009-12-18 09:29:49 UTC 
people complained (haze is unhappy by this), fixed in git

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.