| Summary: | empathy and gnome-contacts crash immediately after startup with folks[zeitgeist] | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Mehmet Giritli <mehmet> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | desktop-misc, graaff, jlec, pva, rodolphe.rocca |
| Priority: | Normal | Keywords: | InVCS |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=505252 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
0001-Fix-unit-tests.patch
0001-WhereClause-Fix-array-length-to-work-with-string.joi.patch |
||
|
Description
Mehmet Giritli
2014-07-26 14:08:41 UTC
You will need to provide a backtrace: https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces And also "emerge -pv gnome-contacts empathy folks bluez" output [ebuild R ] net-wireless/bluez-5.21-r1:0/3 USE="cups obex readline systemd udev -debug (-selinux) {-test}" ABI_X86="(64) (-32) (-x32)" 0 kB
[ebuild R ] dev-libs/folks-0.9.7.1:0/25 USE="bluetooth eds socialweb telepathy tracker -debug {-test} -utils -zeitgeist" 0 kB
[ebuild R ] gnome-extra/gnome-contacts-3.12.0 USE="v4l" 0 kB
[ebuild R ] net-im/empathy-3.12.4 USE="geoloc gnome gnome-online-accounts map spell v4l -debug {-test}" 0 kB
gdb empathy GNU gdb (Gentoo 7.6.2 p1) 7.6.2 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". For bug reporting instructions, please see: <http://bugs.gentoo.org/>... Reading symbols from /usr/bin/empathy...Reading symbols from /usr/lib64/debug/usr/bin/empathy.debug...done. done. (gdb) run Starting program: /usr/bin/empathy warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffde554700 (LWP 14399)] [New Thread 0x7fffdd72f700 (LWP 14402)] [New Thread 0x7fffdcf2e700 (LWP 14403)] [New Thread 0x7fffcadad700 (LWP 14408)] [New Thread 0x7fffca5ac700 (LWP 14409)] [New Thread 0x7fffc9dab700 (LWP 14410)] [New Thread 0x7fffc95aa700 (LWP 14411)] [New Thread 0x7fffbb7c8700 (LWP 14425)] [New Thread 0x7fffbafc7700 (LWP 14426)] [Thread 0x7fffc95aa700 (LWP 14411) exited] [Thread 0x7fffcadad700 (LWP 14408) exited] [New Thread 0x7fffcadad700 (LWP 14460)] [New Thread 0x7fffc95aa700 (LWP 14461)] [New Thread 0x7fffba7c6700 (LWP 14463)] [New Thread 0x7fffb9fc5700 (LWP 14464)] [New Thread 0x7fffb97c4700 (LWP 14465)] [New Thread 0x7fffb8fc3700 (LWP 14466)] [New Thread 0x7fff9ffff700 (LWP 14467)] [New Thread 0x7fff9f7fe700 (LWP 14469)] ** bluez:ERROR:bluez-persona-store.c:2645:_folks_backends_blue_z_persona_store_perform_obex_transfer_co: code should not be reached Program received signal SIGABRT, Aborted. 0x00007ffff5012955 in raise () from /lib64/libc.so.6 (gdb) bt #0 0x00007ffff5012955 in raise () from /lib64/libc.so.6 #1 0x00007ffff5013dc7 in abort () from /lib64/libc.so.6 #2 0x00007ffff5615845 in g_assertion_message () from /usr/lib64/libglib-2.0.so.0 #3 0x00007ffff5615eca in g_assertion_message_expr () from /usr/lib64/libglib-2.0.so.0 #4 0x00007fffcc6cc96b in _folks_backends_blue_z_persona_store_perform_obex_transfer_co () from /usr/lib64/folks/42/backends/bluez/bluez.so #5 0x00007ffff6091067 in g_simple_async_result_complete () from /usr/lib64/libgio-2.0.so.0 #6 0x00007ffff6091149 in complete_in_idle_cb () from /usr/lib64/libgio-2.0.so.0 #7 0x00007ffff55f2c2b in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #8 0x00007ffff55f2f84 in g_main_context_iterate.isra.23 () from /usr/lib64/libglib-2.0.so.0 #9 0x00007ffff55f304c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #10 0x00007ffff60c44e4 in g_application_run () from /usr/lib64/libgio-2.0.so.0 #11 0x00000000004195f9 in main (argc=1, argv=0x7fffffffda68) at empathy.c:842 Are you able to reproduce on a new created user account with a fresh home directory? (In reply to Pacho Ramos from comment #5) > Are you able to reproduce on a new created user account with a fresh home > directory? PAcho, I havent yet tried that but I found out that if I turn off bluetooth of my phone, everything works ok. I think folks have this backend which retrieves the phone contacts and the problem is bluetooth infrastructure related? Can you test this by pairing your phone to your computer and see if the bt backend of folks works? I am unsure, I guess bluez is failing for some reason in your case, but haven't found any similar backtrace un upstream. I would report to bugzilla.gnome.org (component: folks) providing tha backtrace as a comment there. Maybe they will know what is occurring :/ I'm seeing this also: $ empathy (empathy:19219): GLib-CRITICAL **: g_variant_ref: assertion 'value->ref_count > 0' failed (empathy:19219): GLib-CRITICAL **: g_variant_unref: assertion 'value->ref_count > 0' failed (empathy:19219): GLib-CRITICAL **: g_variant_unref: assertion 'value->ref_count > 0' failed (empathy:19219): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed (empathy:19219): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed (empathy:19219): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Terminated And in /var/log/messages: Jul 30 09:16:53 localhost dbus[2424]: [system] Activating service name='org.freedesktop.GeoClue2' (using servicehelper) Jul 30 09:16:53 localhost dbus[2424]: [system] Successfully activated service 'org.freedesktop.GeoClue2' Jul 30 09:16:53 localhost dbus[2424]: [system] Activating service name='org.bluez' (using servicehelper) Jul 30 09:16:53 localhost dbus[2424]: [system] Activated service 'org.bluez' failed: Launch helper exited with unknown return code 1 Jul 30 09:16:57 localhost dbus[2424]: [system] Activating service name='org.bluez' (using servicehelper) Jul 30 09:16:57 localhost dbus[2424]: [system] Activated service 'org.bluez' failed: Launch helper exited with unknown return code 1 Jul 30 09:16:57 localhost kernel: [ 3300.255505] empathy-chat[19254]: segfault at 7fff595e3ff8 ip 00007f3b76eeae13 sp 00007fff595e4000 error 6 in libgio-2.0.so.0.4000.0[7f3b76e13000+16a000] Hans, do you have zeitgeist use flag for folks? If so try turning it off and recompile folks. If this fixes your problem, then it is a separate bug, which again I opened a while back. It is an upstream bug which is reported here: https://bugzilla.gnome.org/show_bug.cgi?id=726248 (In reply to Mehmet Giritli from comment #9) > Hans, do you have zeitgeist use flag for folks? If so try turning it off and > recompile folks. If this fixes your problem, then it is a separate bug, > which again I opened a while back. It is an upstream bug which is reported > here: > > https://bugzilla.gnome.org/show_bug.cgi?id=726248 Thanks! Recompiling folks without zeitgeist fixed my crash. (In reply to Mehmet Giritli from comment #9) > Hans, do you have zeitgeist use flag for folks? If so try turning it off and > recompile folks. If this fixes your problem, then it is a separate bug, > which again I opened a while back. It is an upstream bug which is reported > here: > > https://bugzilla.gnome.org/show_bug.cgi?id=726248 It should be reported to folks upstream I think: https://bugzilla.gnome.org/enter_bug.cgi?product=folks (I don't have permissions to reassign the already reported bug to proper component and maintainers :( ) Similar bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752482 It mentions upstream patch, but for some reason upstream git is inaccessible at the moment, so I loosely stole fix from debian. Following two patches fix an issue for me. Please, apply or give me ok to commit :) Created attachment 388324 [details, diff]
0001-Fix-unit-tests.patch
Created attachment 388326 [details, diff]
0001-WhereClause-Fix-array-length-to-work-with-string.joi.patch
(In reply to Peter Volkov from comment #14) > Created attachment 388326 [details, diff] [details, diff] > 0001-WhereClause-Fix-array-length-to-work-with-string.joi.patch I am a bit unsure about this check for 0.24... wouldn't be better to check for older versions instead? (assuming the way it's handled in 0.24 is the way that will be needed for newer versions too) (In reply to Pacho Ramos from comment #15) > (In reply to Peter Volkov from comment #14) > > Created attachment 388326 [details, diff] [details, diff] [details, diff] > > 0001-WhereClause-Fix-array-length-to-work-with-string.joi.patch > > I am a bit unsure about this check for 0.24... wouldn't be better to check > for older versions instead? (assuming the way it's handled in 0.24 is the > way that will be needed for newer versions too) CCing zeitgeist maintainers to check them as they will know better than me for sure :) Maybe related is totem crashing and being mostly unusable with USE=zeitgeist enabled as well. I will have a try at this patch asap. zeitgeist-0.9.15 should fix the issue. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752482#12 I was looking up the source tarball and it seems that the launchpad project is dead, so it got partly moved to freedesktop infrastructure but there is no release tarball there. The only tar I could find, that is being used by everyone it seems, is the one generated by github on release tags :-/ I'll work on reporting the problem upstream and generating a proper tarball for us asap. So this packages appears to have multiple autoconf/automake issues. Current ebuild tries to do and out-of-tree build but it does seem actually supported. I forked the github repository and will try to fix the situation there before bumping. (In reply to Gilles Dartiguelongue from comment #20) > So this packages appears to have multiple autoconf/automake issues. Current > ebuild tries to do and out-of-tree build but it does seem actually > supported. I forked the github repository and will try to fix the situation > there before bumping. Are you taking care of it? +*zeitgeist-0.9.15 (03 Mar 2015) + + 03 Mar 2015; Gilles Dartiguelongue <eva@gentoo.org> +zeitgeist-0.9.15.ebuild, + +files/zeitgeist-0.9.15-fix-array-length-string-join.patch, + +files/zeitgeist-0.9.15-python-detection.patch: + Version bump, fix bug #518174. Move vala_src_prepare call after potential + eautoreconf, fix configure to properly detect/use python, make unittest run + within a dbus session, do not install docs in multiple paths. + I haven't included fixes to make it compatible with python3 as I feel this needs review from upstream but things should be a lot cleaner now. For some reason the patch for vala 0.24 makes the tests work for both vala 0.24 and 0.26. All tests are passing now so I guess we are good now. |
