first, sorry that it took so long to respond. I almost forgot that issue and due to a misconfiguration of evolution (me is at fault here too) it filtered the bugreport mails "out of my eyes" and I acually forgot the issue, other more important things took my attention. I was just re-remembered as I saw yesterday nautilus-sendto was upgraded and found the mails again, sorry for that.
So I did what you suggested (even now with the new version) and it did crash again: $ LC_ALL=C nautilus-sendto /dev/null Init evolution plugin Init gaim plugin Init sylpheed-claws plugin Init gajim plugin ** (nautilus-sendto:6357): WARNING **: Unable to open addressbook: EBookStatus returned 3 (nautilus-sendto:6357): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: e_book_new: no factories available for uri `scalix://[EMAIL PROTECTED]/Kontakte' Speicherzugriffsfehler I don't know why the last word was not affected by LC_ALL but... it just means segmentation fault. As I once had tested scalix (groupware foo) with Evolution but purged it already months ago, there were some "things" left in my ~/.evolution/ directory: [EMAIL PROTECTED]:~$ mv .evolution/scalix/ .evolution/scalix.bak [EMAIL PROTECTED]:~$ evolution --force-shutdown Evolution restart and no crash with nautilus-sendto. As it was so easily to understand what may have caused the bug even without the debugging package, I did not try the debugging version you kindly shiped with in your last mail. Even if it is clear what "caused" the bug, I'd still call it a bug somehow. But as the scalix thingy was not debian-official packaged... no idea what to think there. Anyhow, finally solved, just almost a month past due :) Thanks for your input! greets Michael Am Dienstag, den 20.03.2007, 23:45 +0100 schrieb Øystein Gisnås: > tags 415491 unreproducible > quit > > I do not experience the crash you're describing here, so I have to ask > for your help to identify the problem cause. > > Can you start nautilus-sendto from a terminal with the command: > "LANG=C nautilus-sendto /dev/null" and paste the textual output here? > > The stacktrace you pasted will be much more valuable if it's collected > from binaries with debug symbols. If you install the attached .deb, > recreate the crash and paste the stacktrace, I might be able to track > down the exact code line. > > Thanks in advance! > > Cheers, > Øystein
