[Bug 82503] Re: [apport] trackerd crashed with SIGSEGV in start_thread()

2007-07-30 Thread Sebastien Bacher
tracker (0.6.0-1) unstable; urgency=low . * New upstream release. - Uses XDG directories to store the settings, cache, database and log files. Closes: #414860 - Fixes the crash of the deskbar applet at session start. Closes: #434078 - Does not fall back to polling when

[Bug 82503] Re: [apport] trackerd crashed with SIGSEGV in start_thread()

2007-06-18 Thread Apport retracing service
** Attachment removed: "CoreDump.gz" http://launchpadlibrarian.net/6014803/CoreDump.gz -- [apport] trackerd crashed with SIGSEGV in start_thread() https://bugs.launchpad.net/bugs/82503 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubu

[Bug 82503] Re: [apport] trackerd crashed with SIGSEGV in start_thread()

2007-05-09 Thread Jamie McCracken
this bug is fixed upstream (assuming last thread stack trace is accurate) ** Changed in: tracker (Ubuntu) Status: Confirmed => Fix Committed -- [apport] trackerd crashed with SIGSEGV in start_thread() https://bugs.launchpad.net/bugs/82503 You received this bug notification because you are

[Bug 82503] Re: [apport] trackerd crashed with SIGSEGV in start_thread()

2007-03-23 Thread Emilio Pozuelo Monfort
** Changed in: tracker (Ubuntu) Status: Needs Info => Confirmed -- [apport] trackerd crashed with SIGSEGV in start_thread() https://launchpad.net/bugs/82503 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 82503] Re: [apport] trackerd crashed with SIGSEGV in start_thread()

2007-03-23 Thread Apport retracing service
StacktraceTop:tracker_get_mime_type (uri=0x76c650 "/home/frafra/Desktop/netsukuku-0.0.9b/conftest.er1") at tracker-utils.c:1320 tracker_db_index_file (db_con=0x698110, info=0x771640, is_attachment=0) at tracker-db.c:950 process_files_thread () at trackerd.c:1353 IA__g_thread_join (thread=0x6d539

[Bug 82503] Re: [apport] trackerd crashed with SIGSEGV in start_thread()

2007-03-23 Thread Emilio Pozuelo Monfort
** Tags added: need-amd64-retrace -- [apport] trackerd crashed with SIGSEGV in start_thread() https://launchpad.net/bugs/82503 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 82503] Re: [apport] trackerd crashed with SIGSEGV in start_thread()

2007-03-08 Thread Emilio Pozuelo Monfort
** Changed in: tracker (Ubuntu) Importance: Undecided => Medium -- [apport] trackerd crashed with SIGSEGV in start_thread() https://launchpad.net/bugs/82503 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 82503] Re: [apport] trackerd crashed with SIGSEGV in start_thread()

2007-02-11 Thread Francesco Frassinelli
This is my tracker.log ** Attachment added: "tracker.log" http://librarian.launchpad.net/6390351/tracker.log -- [apport] trackerd crashed with SIGSEGV in start_thread() https://launchpad.net/bugs/82503 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman

[Bug 82503] Re: [apport] trackerd crashed with SIGSEGV in start_thread()

2007-02-10 Thread Scott Zawalski
** Changed in: tracker (Ubuntu) Status: Unconfirmed => Needs Info -- [apport] trackerd crashed with SIGSEGV in start_thread() https://launchpad.net/bugs/82503 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 82503] Re: [apport] trackerd crashed with SIGSEGV in start_thread()

2007-02-01 Thread Jamie McCracken
Could you also forward the tracker log file ( $HOME/.Tracker/tracker.log) ? -- [apport] trackerd crashed with SIGSEGV in start_thread() https://launchpad.net/bugs/82503 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 82503] Re: [apport] trackerd crashed with SIGSEGV in start_thread()

2007-02-01 Thread Jamie McCracken
bug confined to X86_64 and libpthread we never treat integer as pointers (and v ice versa) in tracker so this is not likely to be 64-bit specific problem as such. more investigation is needed (outside fo tracker) in glib and glibc to see if random errors occur when using threads on X86_64 (in 64