<!-- This issue tracker is only for technical issues related to Bitcoin Core. General bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange at https://bitcoin.stackexchange.com. For reporting security issues, please read instructions at https://bitcoincore.org/en/contact/. If the node is "stuck" during sync or giving "block checksum mismatch" errors, please ensure your hardware is stable by running memtest and observe CPU temperature with a load-test tool such as linpack before creating an issue! -->
<!-- Describe the issue -->
flatpak run org.bitcoincore.bitcoin-qt -choosedatadir
<!--- What behavior did you expect? -->
The -choosedatadir Should allow me to choose the datadir. But it is not. It immediately starts downloading headers from the peers. The chooses a predefined datadir in
~/.var/app/org.bitcoincore.bitcoin-qt$ ls
cache config data
- I am unable to modify the datadir location when I run the client using flatpak (on PopOS).
To reproduce
- Install flatpak client
- try the command
flatpak run org.bitcoincore.bitcoin-qt -choosedatadir
<!--- How reliably can you reproduce the issue, what are the steps to do so? -->
Everytime.
System information
<!-- What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)? -->
- PopOS, Flatpak version. Client information
$ flatpak run org.bitcoincore.bitcoin-qt -version
Bitcoin Core version v22.0.0
Copyright (C) 2009-2021 The Bitcoin Core developers
Please contribute if you find Bitcoin Core useful. Visit
<https://bitcoincore.org/> for further information about the software.
The source code is available from <https://github.com/bitcoin/bitcoin>.
This is experimental software.
Distributed under the MIT software license, see the accompanying file COPYING
or <https://opensource.org/licenses/MIT>
<!-- What type of machine are you observing the error on (OS/CPU and disk type)? -->
<!-- GUI-related issue? What is your operating system and its version? If Linux, what is your desktop environment and graphical shell? -->
<!-- Any extra information that might be useful in the debugging process. -->
<!--- This is normally the contents of a `debug.log` or `config.log` file. Raw text or a link to a pastebin type site are preferred. -->