Can you give us a new backtrace? On Tue, 2009-11-03 at 14:01 +0200, Tshepang Lekhonkhobe wrote: > On Tue, Nov 3, 2009 at 13:03, Tshepang Lekhonkhobe<tshep...@gmail.com> wrote: > > On Tue, Nov 3, 2009 at 12:50, Philip Van Hoof<s...@pvanhoof.be> wrote: > >> On Tue, 2009-11-03 at 11:48 +0100, Philip Van Hoof wrote: > >>> On Tue, 2009-11-03 at 12:46 +0200, Tshepang Lekhonkhobe wrote: > >>> > On Tue, Nov 3, 2009 at 12:04, Philip Van Hoof<s...@pvanhoof.be> wrote: > >>> > > We can't reproduce this problem. It would be useful if you guys could > >>> > > try to reproduce it after applying this patch: > >>> > > >>> > same crash; I'll do "tracker-control -r" and check again > >>> > >>> No, no need. Keep your situation if you can easily reproduce this way. > >>> We'll need it in a few moments to test against. > > > > silly me. I was too quick. > > > >> Can you try to reproduce against current master? We committed a fix for > >> this, but as we can't reproduce this ourselves you'll have to verify it. > > > > let's see if I can reproduce before I install the update; it's going > > to take a while; unless Laurent still got old DB around and checks > > this update > > I managed to reproduce even after a re-index, and even after > installing the update from master. > >
-- Philip Van Hoof, freelance software developer home: me at pvanhoof dot be gnome: pvanhoof at gnome dot org http://pvanhoof.be/blog http://codeminded.be _______________________________________________ tracker-list mailing list tracker-list@gnome.org http://mail.gnome.org/mailman/listinfo/tracker-list
