public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Kristov Atlas <author@anonymousbitcoinbook.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Compatibility Bitcoin-Qt with Tails
Date: Sat, 26 Apr 2014 13:29:00 -0400	[thread overview]
Message-ID: <535BECDC.9070804@anonymousbitcoinbook.com> (raw)
In-Reply-To: <CA+s+GJARfPhMo8ucE7E40bE890NsuzuWPq1DQuK6ZVMvps0LVQ@mail.gmail.com>

On 04/25/2014 04:27 PM, Wladimir wrote:
> Kristov,
> I've modified the gitian build so that it builds against Qt 4.6
> instead of Qt 4.8 in this pull request:
> https://github.com/bitcoin/bitcoin/pull/4094
>
> A test build of master with that pulls gitian descriptor is available:
>
> https://download.visucore.com/bitcoin/linux-4765b8c-gitian-2d48b96.tar.gz
> https://download.visucore.com/bitcoin/linux-4765b8c-gitian-2d48b96.tar.gz.sig
>
> These bitcoin-qt executables *should* work on Debian Squeeze / Tails
> Linux. Let me know if it is the case.
>
>
Hey Wladimir,

Thanks for building this binary. The initial problem with Qt was 
resolved, and I was able to load the GUI that chooses my datadir. After 
choosing the default datadir, however, it segfaulted.

The segfault came after the usual message that I get when running 
Bitcoin Core in Tails, which is the "sendto: Operation not permitted" 
message since Core will not be able to connect to the internet without 
going through Tails' Tor SOCKS proxy. When I specify the SOCKS proxy 
through the command-line, I get a brief flash of the GUI before it 
segfaults again.

The "Bus::open" and "IBusInputContext::createInputContext" messages are 
atypical and might be related to the segfault.

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


-Kristov



  reply	other threads:[~2014-04-26 17:55 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 [this message]
2014-04-27  6:52   ` Wladimir
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=535BECDC.9070804@anonymousbitcoinbook.com \
    --to=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