Description of problem: Try to connect to XMPP server (ejabberd) using empathy Version-Release number of selected component: telepathy-gabble-0.17.3-2.fc19 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/telepathy-gabble crash_function: do_lookup_records executable: /usr/libexec/telepathy-gabble kernel: 3.9.0-0.rc7.git3.1.fc19.x86_64 runlevel: N 5 uid: 1000 ureports_counter: 1 Truncated backtrace: Thread no. 1 (3 frames) #2 do_lookup_records at gthreadedresolver.c:696 #3 g_task_thread_pool_thread at gtask.c:1242 #5 g_thread_proxy at gthread.c:798
Created attachment 739522 [details] File: backtrace
Created attachment 739523 [details] File: cgroup
Created attachment 739524 [details] File: core_backtrace
Created attachment 739525 [details] File: dso_list
Created attachment 739526 [details] File: environ
Created attachment 739527 [details] File: limits
Created attachment 739528 [details] File: maps
Created attachment 739529 [details] File: open_fds
Created attachment 739530 [details] File: proc_pid_status
Created attachment 739531 [details] File: var_log_messages
I did nothing to trigger the crash, but it is likely caused by suspending the laptop and changing the wifi network when the laptop woke up, and likely going either on a different network, or a captive portal backtrace_rating: 4 cmdline: /usr/libexec/telepathy-gabble crash_function: do_lookup_records executable: /usr/libexec/telepathy-gabble kernel: 3.9.0-301.fc19.x86_64 package: telepathy-gabble-0.17.3-2.fc19 reason: Process /usr/libexec/telepathy-gabble was killed by signal 5 (SIGTRAP) runlevel: N 5 uid: 500 ureports_counter: 9
I think this might actually be a bug in glib's resolver, although I haven't tested/verified. If I'm right though, it looks like it's been fixed upstream: https://git.gnome.org/browse/glib/commit/gio/gthreadedresolver.c?id=3456152f23a9507f10c868ff4bc1cca91a486b21 Feel free to reassign.
Patch is already commited in unstable glib2-2.37. Could you backport it to 2.36 and build updated package?
I have one account that triggers this bug on every connection, taking down all my other XMPP accounts with it. Backporting the patch and rebuilding glib2 fixes it.
glib2-2.36.3-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/glib2-2.36.3-1.fc19
Package glib2-2.36.3-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing glib2-2.36.3-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-10464/glib2-2.36.3-1.fc19 then log in and leave karma (feedback).
glib2-2.36.3-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.