From: Wladimir <laanwj@gmail.com>
To: Kristov Atlas <author@anonymousbitcoinbook.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Compatibility Bitcoin-Qt with Tails
Date: Sun, 27 Apr 2014 08:52:38 +0200 [thread overview]
Message-ID: <CA+s+GJBgBiB8LESvy2-3GX_gsdqrTLF9LeQVvR7gTgRrAxq4DQ@mail.gmail.com> (raw)
In-Reply-To: <535BECDC.9070804@anonymousbitcoinbook.com>
> Sample terminal output for latest Tails (0.23):
>
> amnesia@amnesia:~/linux-4765b8c-gitian-2d48b96/32$ ./bitcoin-qt
> Bus::open: Can not get ibus-daemon's address.
> IBusInputContext::createInputContext: no connection to ibus-daemon
> sendto: Operation not permitted
> Segmentation fault
> amnesia@amnesia:~/linux-4765b8c-gitian-2d48b96/32$ ./bitcoin-qt
> Segmentation fault
> amnesia@amnesia:~/linux-4765b8c-gitian-2d48b96/32$ ./bitcoin-qt -proxy=127.0.0.1:9050
> Segmentation fault
Can you get a traceback?
Wladimir
next prev parent reply other threads:[~2014-04-27 6:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 20:27 [Bitcoin-development] Compatibility Bitcoin-Qt with Tails Wladimir
2014-04-26 17:29 ` Kristov Atlas
2014-04-27 6:52 ` Wladimir [this message]
2014-04-30 7:02 ` Wladimir
2014-05-02 17:46 ` Kristov Atlas
2014-05-02 18:28 ` Wladimir
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+s+GJBgBiB8LESvy2-3GX_gsdqrTLF9LeQVvR7gTgRrAxq4DQ@mail.gmail.com \
--to=laanwj@gmail.com \
--cc=author@anonymousbitcoinbook.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox