Bug 74159 - SIGTRAP when connect more that 1 account (g_source_remove())
Summary: SIGTRAP when connect more that 1 account (g_source_remove())
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-glib (show other bugs)
Version: unspecified
Hardware: Other All
: high critical
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-28 20:15 UTC by Igor Gnatenko
Modified: 2014-01-29 13:05 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
backtrace (33.81 KB, text/plain)
2014-01-28 20:16 UTC, Igor Gnatenko 		Details
cgroup (180 bytes, text/plain)
2014-01-28 20:16 UTC, Igor Gnatenko 		Details
core_backtrace (12.29 KB, text/plain)
2014-01-28 20:17 UTC, Igor Gnatenko 		Details
dso_list (5.12 KB, text/plain)
2014-01-28 20:17 UTC, Igor Gnatenko 		Details
environ (945 bytes, text/plain)
2014-01-28 20:17 UTC, Igor Gnatenko 		Details
limits (1.31 KB, text/plain)
2014-01-28 20:18 UTC, Igor Gnatenko 		Details
maps (26.17 KB, text/plain)
2014-01-28 20:18 UTC, Igor Gnatenko 		Details
open_fds (441 bytes, text/plain)
2014-01-28 20:18 UTC, Igor Gnatenko 		Details
proc_pid_status (1.10 KB, text/plain)
2014-01-28 20:19 UTC, Igor Gnatenko 		Details
var_log_messages (212 bytes, text/plain)
2014-01-28 20:19 UTC, Igor Gnatenko 		Details
View All

Description Igor Gnatenko 2014-01-28 20:15:54 UTC 
Original report: https://bugzilla.redhat.com/show_bug.cgi?id=1055772

Description of problem:
Tried connect to google account

Version-Release number of selected component:
telepathy-gabble-0.18.1-2.fc21

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/libexec/telepathy-gabble
crash_function: g_source_remove
executable:     /usr/libexec/telepathy-gabble
kernel:         3.13.0-0.rc8.git4.1.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_source_remove at gmain.c:2211
 #3 ffi_call_unix64 at ../src/x86/unix64.S:76
 #4 ffi_call at ../src/x86/ffi64.c:522
 #5 g_cclosure_marshal_generic at gclosure.c:1454
 #10 tp_svc_connection_manager_emit_new_connection at _gen/tp-svc-connection-manager.c:129
 #11 tp_base_connection_manager_request_connection at base-connection-manager.c:1067
 #12 ffi_call_unix64 at ../src/x86/unix64.S:76
 #13 ffi_call at ../src/x86/ffi64.c:522
 #14 g_cclosure_marshal_generic at gclosure.c:1454
 #15 invoke_object_method at dbus-gobject.c:1899
Comment 1 Igor Gnatenko 2014-01-28 20:16:31 UTC 
Created attachment 92942 [details]
backtrace
Comment 2 Igor Gnatenko 2014-01-28 20:16:47 UTC 
Created attachment 92943 [details]
cgroup
Comment 3 Igor Gnatenko 2014-01-28 20:17:02 UTC 
Created attachment 92944 [details]
core_backtrace
Comment 4 Igor Gnatenko 2014-01-28 20:17:34 UTC 
Created attachment 92945 [details]
dso_list
Comment 5 Igor Gnatenko 2014-01-28 20:17:55 UTC 
Created attachment 92946 [details]
environ
Comment 6 Igor Gnatenko 2014-01-28 20:18:11 UTC 
Created attachment 92947 [details]
limits
Comment 7 Igor Gnatenko 2014-01-28 20:18:29 UTC 
Created attachment 92948 [details]
maps
Comment 8 Igor Gnatenko 2014-01-28 20:18:55 UTC 
Created attachment 92949 [details]
open_fds
Comment 9 Igor Gnatenko 2014-01-28 20:19:12 UTC 
Created attachment 92950 [details]
proc_pid_status
Comment 10 Igor Gnatenko 2014-01-28 20:19:30 UTC 
Created attachment 92951 [details]
var_log_messages
Comment 11 Simon McVittie 2014-01-29 11:13:51 UTC 
If you have GLib 2.39, then I think this is Bug #72303 (which is fixed in git, but not yet in a release).
Comment 12 Igor Gnatenko 2014-01-29 12:37:07 UTC 
(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
Comment 13 Igor Gnatenko 2014-01-29 12:48:30 UTC 
(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...
Comment 14 Simon McVittie 2014-01-29 13:01:25 UTC 
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.
Comment 15 Igor Gnatenko 2014-01-29 13:05:40 UTC 
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.