Summary: | SIGTRAP when connect more that 1 account (g_source_remove()) | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Igor Gnatenko <i.gnatenko.brain> |
Component: | tp-glib | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | critical | ||
Priority: | high | CC: | i.gnatenko.brain |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
See Also: | https://bugzilla.redhat.com/show_bug.cgi?id=1055772 | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
backtrace
cgroup core_backtrace dso_list environ limits maps open_fds proc_pid_status var_log_messages |
Description
Igor Gnatenko
2014-01-28 20:15:54 UTC
Created attachment 92942 [details]
backtrace
Created attachment 92943 [details]
cgroup
Created attachment 92944 [details]
core_backtrace
Created attachment 92945 [details]
dso_list
Created attachment 92946 [details]
environ
Created attachment 92947 [details]
limits
Created attachment 92948 [details]
maps
Created attachment 92949 [details]
open_fds
Created attachment 92950 [details]
proc_pid_status
Created attachment 92951 [details]
var_log_messages
If you have GLib 2.39, then I think this is Bug #72303 (which is fixed in git, but not yet in a release). (In reply to comment #11) > If you have GLib 2.39, then I think this is Bug #72303 (which is fixed in > git, but not yet in a release). $ rpm -q glib2 glib2-2.39.3-1.fc21.x86_64 (In reply to comment #11) > If you have GLib 2.39, then I think this is Bug #72303 (which is fixed in > git, but not yet in a release). testing that patch... Believed to be fixed in telepathy-glib 0.22.1, which I just released. Please reopen if not. If you're tracking development versions of telepathy-glib, it'll be fixed in 0.23.1 (which I haven't released yet); the necessary patch is commit 3c1c43cc2. Yes. That patch fixes my bug. |
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.