After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 667493 - empathy-accounts crashed with SIGSEGV in handle_property_changed()
empathy-accounts crashed with SIGSEGV in handle_property_changed()
Status: RESOLVED INCOMPLETE
Product: NetworkManager
Classification: Platform
Component: API
unspecified
Other Linux
: High critical
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2012-01-08 14:21 UTC by Bilal Shahid
Modified: 2012-04-12 15:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
stacktrace (16.73 KB, text/plain)
2012-01-20 17:19 UTC, Bilal Shahid
  Details
stacktrace (1.76 KB, patch)
2012-01-21 14:33 UTC, Bilal Shahid
none Details | Review
stacktrace (2.04 KB, text/plain)
2012-01-22 18:27 UTC, Bilal Shahid
  Details
vg.log (20.00 KB, text/plain)
2012-01-30 13:50 UTC, Bilal Shahid
  Details

Description Bilal Shahid 2012-01-08 14:21:37 UTC
Originally reported at:
  https://bugs.launchpad.net/bugs/908348

emphaty accounts crashes when i finish adding a new yahoo account but it works if i enable the account from emphaty acounts in the menu.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: empathy 3.3.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-6.12-generic 3.2.0-rc6
Uname: Linux 3.2.0-6-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Sat Dec 24 10:26:39 2011
ExecutablePath: /usr/bin/empathy-accounts
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111223)
ProcCmdline: /usr/bin/empathy-accounts --if-needed
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc75fad34f1:	mov    (%rax),%rdi
 PC (0x7fc75fad34f1) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? () from /usr/lib/libnm-glib.so.4
 g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/libnm-glib.so.4
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: empathy-accounts crashed with SIGSEGV in g_hash_table_foreach()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Comment 1 André Klapper 2012-01-08 20:08:19 UTC
Thanks for taking the time to report this bug.
Without a complete (better) stack trace from the crash it's very hard to determine what caused it. Can you get us a complete stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Guillaume Desmottes 2012-01-16 14:58:34 UTC
Trace is on https://launchpadlibrarian.net/88913888/ThreadStacktrace.txt

  • #0 handle_property_changed
    at nm-object.c line 346
  • #1 g_hash_table_foreach
    at /build/buildd/glib2.0-2.31.4.tested/./glib/ghash.c line 1459
  • #2 get_all_cb
    at nm-device.c line 366
  • #3 complete_pending_call_and_unlock
    at ../../dbus/dbus-connection.c line 2303
  • #4 dbus_connection_dispatch
    at ../../dbus/dbus-connection.c line 4552
  • #5 message_queue_dispatch
    at dbus-gmain.c line 90
  • #6 g_main_dispatch
    at /build/buildd/glib2.0-2.31.4.tested/./glib/gmain.c line 2513
  • #7 g_main_context_dispatch
    at /build/buildd/glib2.0-2.31.4.tested/./glib/gmain.c line 3050
  • #8 g_main_context_iterate
    at /build/buildd/glib2.0-2.31.4.tested/./glib/gmain.c line 3121
  • #9 g_main_context_iterate
    at /build/buildd/glib2.0-2.31.4.tested/./glib/gmain.c line 3058
  • #10 g_main_context_iteration
    at /build/buildd/glib2.0-2.31.4.tested/./glib/gmain.c line 3182
  • #11 g_application_run
    at /build/buildd/glib2.0-2.31.4.tested/./gio/gapplication.c line 1548
  • #12 main
    at empathy-accounts.c line 253

Comment 3 Guillaume Desmottes 2012-01-16 15:04:52 UTC
What are the exact steps to reproduce this crash? Which "menu" are you refering to?
Comment 4 Bilal Shahid 2012-01-16 15:10:10 UTC
emphaty accounts crashes when i finish adding a new yahoo or msn account but it works if i enable the account from emphaty acounts in the menu(reporter) i guess accounts option in edit menu.
Comment 5 Guillaume Desmottes 2012-01-16 15:13:56 UTC
Which menu? Does it happen with, say, gtalk accounts?
Comment 6 Bilal Shahid 2012-01-20 17:19:50 UTC
Created attachment 205709 [details]
stacktrace

its also in empathy 3.3.4
Comment 7 Bilal Shahid 2012-01-20 22:05:35 UTC
@ cassidy
as you said this bug must be fixed in 3.3.4 but not i have attached the stacktrace hope this helps yes this also with the google mail accounts.
Comment 8 André Klapper 2012-01-20 22:07:36 UTC
(In reply to comment #6)
> Created an attachment (id=205709) [details]
> stacktrace

That's not a stacktrace. Please see https://live.gnome.org/GettingTraces/Details#learn-about-stacktraces what a stacktrace is, and what isn't.
Comment 9 Bilal Shahid 2012-01-20 22:16:16 UTC
but i have seen this page and follow its instructions..
sorry about that i will get another and attach with it thanks for mentioning.
Comment 10 Bilal Shahid 2012-01-20 23:19:11 UTC
stack trace is on 
https://launchpadlibrarian.net/90579267/stacktrace%20empathy
Comment 11 André Klapper 2012-01-21 12:21:14 UTC
That stack trace is missing basically all elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. 
Please always provide a stack trace with debugging symbols by installing debug packages for empathy, gtk3, glib2. Thanks in advance!

Also note that the stacktrace that you provided does not have ANY function call from Empathy included, just very generic ones.
Comment 12 Bilal Shahid 2012-01-21 12:32:56 UTC
i tried so much i removed my account to reproduce it tell me the good way to get the stacktrace..like we get more and more information in that.
i have used the "Obtaining a stack trace using GDB" method to get this..can you tell me any other way that will give us the exact information that will help?
like which way you more prefer and you experienced that give max info?
Comment 13 André Klapper 2012-01-21 12:40:40 UTC
(In reply to comment #12)
> i have used the "Obtaining a stack trace using GDB" method to get this

That's good. If you go to https://live.gnome.org/GettingTraces/Details the first item is "Installing debugging information packages"
Comment 14 Bilal Shahid 2012-01-21 14:33:22 UTC
Created attachment 205762 [details] [review]
stacktrace
Comment 15 Bilal Shahid 2012-01-21 14:41:15 UTC
i have got this and one more thing i have got and i am attaching it to downstream
https://launchpadlibrarian.net/90626628/_usr_bin_empathy-accounts.1000.crash
this is found me as name empathy-accounts crash with the last day dated on it..mean i was on 20.1.2012
and one more thing i tell you how to reproduce it
first remove all accounts.
remove the id and password also by searching keys and password.
and than restart than again enter the account..than after inserting the data when  you press enter to proceed than the crash happen...hope this helps
Comment 16 André Klapper 2012-01-21 15:30:36 UTC
Stacktraces in comment 14 and comment 15 still miss any debug symbols and are not useful. Please provide stacktraces with debug symbols.
Comment 17 Bilal Shahid 2012-01-22 18:27:49 UTC
Created attachment 205826 [details]
stacktrace

hope this will help you.
Comment 18 André Klapper 2012-01-22 21:17:55 UTC
Looks definitely better, nice! Symbols for libglib-2.0 would also be great but I'll let the developers decide.
For future reference, please choose type "plain text" when attaching text files. Thanks!
Comment 19 Guillaume Desmottes 2012-01-24 10:02:31 UTC
Looks like it's crashing in libnm. Which version of this lib are you using? 

According to its source code, you may be raising this warning:

		g_warning ("%s: property '%s' changed but wasn't defined by object type %s.",
		           __func__,
		           prop_name,
		           G_OBJECT_TYPE_NAME (self));


Do you have any kind of warning displayed before the crash?
Comment 20 Bilal Shahid 2012-01-24 21:03:22 UTC
no there is no warning before the crash,,just a hang of few sec and than crash window appear and than every thing is normal.and libnm version is

Version: 0.9.2.0+git201201101813.0b30200-0ubuntu2
Comment 21 Guillaume Desmottes 2012-01-30 10:04:27 UTC
Humm weird, it could be a memory corruption then. A valgrind log would be perfect. Could you please:
- script /tmp/vg.log
- G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind --tool=memcheck --leak-check=full --leak-resolution=high --num-callers=20 /usr/bin/empathy-accounts

The accounts dialog should be loaded but it will be much slower than usual. Then try to reproduce the crash and attach /tmp/vg.log
Comment 22 Bilal Shahid 2012-01-30 13:50:53 UTC
Created attachment 206431 [details]
vg.log

hey and here is the output that we have already discussed at irc channel so http://pastebin.com/5SpuJLcA
Comment 23 Guillaume Desmottes 2012-01-30 14:08:56 UTC
Pasting the trace.

GLib-GObject-WARNING **: invalid uninstantiatable type `<invalid>' in cast to `NMObject'

Program received signal SIGTRAP, Trace/breakpoint trap.
0x010080ad in g_logv () from /lib/i386-linux-gnu/libglib-2.0.so.0
(gdb) ^CQuit
(gdb) thread apply all bt

Thread 1 (Thread 0xb7fd8870 (LWP 2082))

  • #0 g_logv
    from /lib/i386-linux-gnu/libglib-2.0.so.0
  • #1 g_log
    from /lib/i386-linux-gnu/libglib-2.0.so.0
  • #2 g_type_check_instance_cast
    from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  • #3 get_all_cb
    at nm-device.c line 342
  • #4 d_pending_call_notify
    at dbus-gproxy.c line 1835
  • #5 ??
    from /lib/i386-linux-gnu/libdbus-1.so.3
  • #6 ??
    from /lib/i386-linux-gnu/libdbus-1.so.3
  • #7 dbus_connection_dispatch
    from /lib/i386-linux-gnu/libdbus-1.so.3
  • #8 message_queue_dispatch
    at dbus-gmain.c line 90
  • #9 g_main_context_dispatch
    from /lib/i386-linux-gnu/libglib-2.0.so.0
  • #10 ??
    from /lib/i386-linux-gnu/libglib-2.0.so.0
  • #11 g_main_context_iteration
    from /lib/i386-linux-gnu/libglib-2.0.so.0
  • #12 g_application_run
    from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
  • #13 main
    at empathy-accounts.c line 253

Comment 24 Guillaume Desmottes 2012-01-30 14:14:42 UTC
Looks like get_all_cb in nm-device is called after some data have been disposed.
Re-assigning to NetworkManager.
Comment 25 Jiri Klimes 2012-02-07 17:16:25 UTC
We need steps to reproduce, otherwise we are not able to find the problem.

Moreover, libnm-glib code has recently changed upstream.
Comment 26 Bilal Shahid 2012-02-07 18:21:25 UTC
remove all the accounts from empathy.
also remove its passwords from "keys and password"
than restart 
start empathy and add the account detail
as you have added the id and password and press enter than the crash occur.
Comment 27 Jiri Klimes 2012-02-15 16:04:25 UTC
I'm sorry, but I can't reproduce. My packages are
jklimes@gromit ~$ rpm -q NetworkManager-glib
NetworkManager-glib-0.9.2-1.fc16.x86_64
jklimes@gromit ~$ rpm -q empathy
empathy-3.2.2-1.fc16.x86_64

Would you install devel packages for Empathy and NetworkManager and then run it
again in gdb and get the backtrace with 'bt full' command.
Comment 28 Bilal Shahid 2012-02-19 13:55:42 UTC
sorry 
now  i am on empathy 3.3.5 it was reproduce able on 3.3.3 i don't know how to get back to 3.3.3 if i can  go back to 3.3.3.i can reproduce it.
Comment 29 Bilal Shahid 2012-02-24 16:39:46 UTC
i tried so much to go back to empathy 3.3.3 or 3.3.4 from 3.3.5 but not be able to install that one..a developer has also told me some commands but no result..and i also download a deb file and open it in the software center,,it opens but can not shows the install button instead of that there is a error sign there..sorry  but if a can install 3.3.3  or 3.3.4 i can reproduce it  very well.
any body else know a way after all this to install that in ubuntu so i can try that one
thanks
Comment 30 André Klapper 2012-02-25 16:59:43 UTC
We cannot handle distribution-specific issues here - please ask in a forum of your distribution. If you cannot reproduce, feel free to close as RESOLVED INCOMPLETE.
Comment 31 Bilal Shahid 2012-02-25 20:45:15 UTC
wait i will talk with some responcible persons for that and than tell you waht to do with this crash..leave it as for 2,3 days
Comment 32 Bilal Shahid 2012-03-02 03:49:01 UTC
so in the end one person  has reproduce it and i am very thankfull to him. 
 this is the stacktrace with these symbols which you have mentioned
 "Jiri Klimes "
 https://launchpadlibrarian.net/94916957/Stacktrace.txt
 and this one was in a duplicate bug i found 
https://launchpadlibrarian.net/94893528/Stacktrace.txt
see if they can help
Comment 33 Bilal Shahid 2012-04-12 15:44:53 UTC
not be able to reproduce working fine now