Date: Wed, 3 Apr 2013 07:46:22 -0500 From: Jeremy Messenger <mezz.freebsd@gmail.com> To: Carlos Jacobo Puga Medina <cjpugmed@gmail.com> Cc: FreeBSD GNOME Users <gnome@freebsd.org>, Jeremy Messenger <mezz@freebsd.org> Subject: Re: mate-settings-daemon-1.5.7 uid 1001: exited on signal 11 (core dumped) Message-ID: <CADLFttdrbm8P06MWv_dWsMjMTKPfRtqsWC6-FBJ%2BMF0Nd1oc%2BQ@mail.gmail.com> In-Reply-To: <CAHHLbRNDfMzHw%2BFktJyCLsRmd6_-rhTO%2ByzmmuZAbTtZAekkhQ@mail.gmail.com> References: <CAHHLbRP7SrxpiQ%2BByWAf_Q5jJ7fTFSNNs8g68T4tFMU1Dtwzew@mail.gmail.com> <CADLFttexpO1AAzHzRC6-dygSiOowj%2BAhfTGjB9N6A85c%2BAXaAw@mail.gmail.com> <CAHHLbRNDfMzHw%2BFktJyCLsRmd6_-rhTO%2ByzmmuZAbTtZAekkhQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 1, 2013 at 7:29 AM, Carlos Jacobo Puga Medina <cjpugmed@gmail.com> wrote: > [charly@freebsd:/home/charly]% gdb /usr/local/libexec/mate-settings-daemon > mate-settings-daemo.core I don't know and I can't reproduce it. I am not very good with read backtraces. Reinstall glib, dbus-glib, and gtk with the debug too. When you ran 'bt'. Do the 'bt full' after that. If it looks better then one of us will need to submit a bug report over at MATE GitHub. Can you also show me your 'pkg_info'? How did you start MATE? Did you custom anything else like CFLAGS or other options? <snip> > #0 0x2b806c90 in ?? () > [New Thread 2ac05e00 (LWP 100796/mate-settings-daemo)] > [New Thread 2aed3700 (LWP 100780/mate-settings-daemo)] > [New Thread 2ac04c00 (LWP 100779/mate-settings-daemo)] > [New Thread 2ac04300 (LWP 100255/mate-settings-daemo)] > (gdb) bt > #0 0x2b806c90 in ?? () > #1 0x2ba7763f in msd_media_keys_manager_stop (manager=0x2aca8e38) > at msd-media-keys-manager.c:1210 > #2 0x2ba75471 in impl_deactivate (plugin=0x2aeac468) > at msd-media-keys-plugin.c:89 > #3 0x0804cb0b in mate_settings_plugin_deactivate (plugin=0x2aeac468) > at mate-settings-plugin.c:60 > #4 0x0804d487 in _deactivate_plugin (info=0x2ac4b230) > at mate-settings-plugin-info.c:324 > #5 0x0804d568 in mate_settings_plugin_info_deactivate (info=0x2ac4b230) > at mate-settings-plugin-info.c:337 > #6 0x0804c2d0 in _unload_plugin (info=0x2ac4b230, user_data=0x0) > at mate-settings-manager.c:276 > #7 0x28c40721 in g_slist_foreach () from /usr/local/lib/libglib-2.0.so.0 > #8 0x0804c308 in _unload_all (manager=0x2ad4cc48) > at mate-settings-manager.c:284 > #9 0x0804c4ed in mate_settings_manager_stop (manager=0x2ad4cc48) > at mate-settings-manager.c:368 > #10 0x0804b333 in on_session_end (proxy=0x2ac2bd90, flags=0, > manager=0x2ad4cc48) at main.c:257 > #11 0x28ba2f3a in g_cclosure_marshal_VOID () > from /usr/local/lib/libgobject-2.0.so.0 > #12 0x28a07717 in dbus_g_proxy_set_interface () > ---Type <return> to continue, or q <return> to quit--- > from /usr/local/lib/libdbus-glib-1.so.2 > #13 0x28ba0ef5 in g_closure_invoke () from > /usr/local/lib/libgobject-2.0.so.0 > #14 0x28bb6624 in g_signal_handler_find () > from /usr/local/lib/libgobject-2.0.so.0 > #15 0x28bb8976 in g_signal_emit_valist () > from /usr/local/lib/libgobject-2.0.so.0 > #16 0x28bb8c65 in g_signal_emit () from /usr/local/lib/libgobject-2.0.so.0 > #17 0x28a0820d in dbus_g_proxy_set_interface () > from /usr/local/lib/libdbus-glib-1.so.2 > #18 0x28b64ffe in dbus_connection_dispatch () > from /usr/local/lib/libdbus-1.so.3 > #19 0x289fe27d in dbus_server_setup_with_g_main () > from /usr/local/lib/libdbus-glib-1.so.2 > #20 0x28c23374 in g_main_context_dispatch () > from /usr/local/lib/libglib-2.0.so.0 > #21 0x28c25069 in g_main_context_acquire () > from /usr/local/lib/libglib-2.0.so.0 > #22 0x28c262fc in g_main_loop_run () from /usr/local/lib/libglib-2.0.so.0 > #23 0x281ac884 in gtk_main () from /usr/local/lib/libgtk-x11-2.0.so.0 > #24 0x0804ba9e in main (argc=1, argv=0xbfbfea1c) at main.c:512 > (gdb) > > > > 2013/4/1 Jeremy Messenger <mezz.freebsd@gmail.com> >> >> On Sun, Mar 31, 2013 at 6:28 PM, Carlos Jacobo Puga Medina >> <cjpugmed@gmail.com> wrote: >> > Hi, >> > >> > I recently upgraded to MATE 1.5.x and I have an issue with >> > mate-settings-daemon on FreBSD 9.1-RELEASE (i386). >> > >> > Here is the gdb backtrace: >> <snip> >> >> You will need to reinstall your mate-settings-daemon with debug by >> using WITH_DEBUG=yes. After that, remove core and let >> mate-settings-daemon to crash then redo the backtraces. It should >> gives a better backtraces. >> >> >> -- >> mezz.freebsd@gmail.com - mezz@FreeBSD.org >> FreeBSD GNOME Team >> http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org > > -- mezz.freebsd@gmail.com - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLFttdrbm8P06MWv_dWsMjMTKPfRtqsWC6-FBJ%2BMF0Nd1oc%2BQ>