[Tracker] DBus calls _exit() !!!??? [WAS: miner-fs: Could not process file (timeout by message bus)]



On 09/02/2010 04:35 PM, Mildred Ki'Lya wrote:
Hi again :)


Sorry to bother you with my problem but it seems I can't get
tracker-miner-fs to index my mbox files. tracker-info cannot find
anything about the file whereas tracker-miner-fs tells me that the file
should be monitored. And when I manually run tracker-extract on that
file, it print a lot of SPARQL queries and don't fail.

I found the problem ... is in DBus

When I ask tracker-extract to extract medatadata from a file, if I wait
for the DBus request (dbus-send --print-reply),  tracker-extract exist,
if I don't wait for the DBus answer, tracker-extract continues its life.

When I run tracker-extract in gdb and put a breakpoint on _exit, and
send the following dbus request:

dbus-send --session --print-reply \
    --dest=org.freedesktop.Tracker1.Extract \
    /org/freedesktop/Tracker1/Extract \
    org.freedesktop.Tracker1.Extract.GetMetadata \
    string:"file:///.../comments.mbox" string:"application/mbox"

I get the following stack trace:

Breakpoint 2, 0x0000003b8e8ade10 in _exit () from /lib64/libc.so.6
(gdb) bt
#0  0x0000003b8e8ade10 in _exit () from /lib64/libc.so.6
#1  0x0000003b93c2bec9 in ?? () from /lib64/libdbus-1.so.3
#2  0x0000003b93c0df20 in ?? () from /lib64/libdbus-1.so.3
#3  0x0000003b93c0f167 in ?? () from /lib64/libdbus-1.so.3
#4  0x0000003b93c0c0af in dbus_bus_remove_match () from
/lib64/libdbus-1.so.3
#5  0x00000032ab012da5 in ?? () from /usr/lib64/libdbus-glib-1.so.2
#6  0x00000032ab01307c in ?? () from /usr/lib64/libdbus-glib-1.so.2
#7  0x00000032a8411540 in g_object_run_dispose () from
/lib64/libgobject-2.0.so.0
#8  0x00000032ab00fecb in ?? () from /usr/lib64/libdbus-glib-1.so.2
#9  0x0000003b93c0fb4c in dbus_connection_dispatch () from
/lib64/libdbus-1.so.3
#10 0x00000032ab0099d5 in ?? () from /usr/lib64/libdbus-glib-1.so.2
#11 0x00000032a7c43233 in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#12 0x00000032a7c43a10 in ?? () from /lib64/libglib-2.0.so.0
#13 0x00000032a7c44082 in g_main_loop_run () from /lib64/libglib-2.0.so.0
#14 0x000000000040917e in main ()
(gdb)


is there a way to avoid this behaviour?

Mildred

-- 
Mildred Ki'Lya
ââââââââââ ïïïïïïïïïïïïïïïïïïïï ââââââââââ
â Jabber, GoogleTalk: <mildred jabber fr>
â Website: <http://ki.lya.online.fr>           GPG ID: 9A7D 2E2B
â Fingerprint: 197C A7E6 645B 4299 6D37 684B 6F9D A8D6 9A7D 2E2B

Attachment: 0x9A7D2E2B.asc
Description: application/pgp-keys

Attachment: signature.asc
Description: OpenPGP digital signature



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]