Bug#740979: feedback on your nautilus search crash bug report

Emilio Pozuelo Monfort pochu at debian.org
Fri Mar 7 15:14:04 UTC 2014


Hi!

On 07/03/14 15:47, Andreas Henriksson wrote:
> Hello Martin Dosch.
> 
> Thanks for your bug report and the backtrace to go with it!
> 
> While it included some very nice details, I'd like to ask for
> some more that might help figure out the exact reason for your crash.
>
> You gathered a backtrace from SIGTRAP which happened when a
> error log message about a missing schema was detected.
> This might, or might not, be the cause of the actual crash.
> To make sure, could you reproduce the problem same way as before
> and after you gather the backtrace of the SIGTRAP, type "c"
> to continue execution.... gather a backtrace every time
> gdb stops at a signal until the process is no longer running
> at all (and you can't "c(ontinue)" anymore).

Missing schemas cause a g_error() (hence the G_LOG_LEVEL_ERROR) which aborts the
execution, so this should indeed be the cause of the crash.

Unfortunately the g_error() should print a message which isn't in the original
report. That'd help determine what schema is needed. The problem seems to come
from libtracker.

#6  0x00007ffff510d614 in g_object_new (object_type=13409568,
first_property_name=0x7ffff3b73502 "schema")
    at /tmp/buildd/glib2.0-2.38.2/./gobject/gobject.c:1559
#7  0x00007ffff3b68a29 in ?? () from /usr/lib/tracker-0.16/libtracker-data.so.0

Perhaps grep'ing for "schema" in the libtracker-data sources would find where
this is happening.

HTH.

Regards,
Emilio




More information about the pkg-gnome-maintainers mailing list