[SOLVED] Bitcoin Core GUI not showing wallet functions

[btc123thatthere]

Problem solved! I was looking at the wrong bitcoin.conf file.
I used the 'Debug log file -> Open' button in Bitcoin Core's Information tab to see what bitcoin.conf file it was using.

-----------
I'm running 0.20.1 Bitcoin Core on Raspbian.
It's up to date.
I can use it as a node to keep an up to date copy of the blockchain on hand, but it's not showing any of the wallet features like Overview, Send, Receive and Transactions up the top.
Under the File menu, the only option is Exit.
The top tabs include Information, Console, Network Traffic and Peers.

How do I use this as a GUI'd wallet?

Thanks

[btc123thatthere]

It should be enabled by default, did you run Bitcoin Core with parameter -disablewallet or add these lines to bitcoin.conf file?

Code:

# [wallet]
disablewallet=1

No, there's no line in Bitcoin-Qt.conf setting disablewallet to anything.

I'm using https://bitcoin.org/bin/bitcoin-core-0.20.1/bitcoin-0.20.1-arm-linux-gnueabihf.tar.gz

[btc123thatthere]

Also, it looks like there's no wallet functions in the console.
When I type help, I get:


== Blockchain ==
getbestblockhash
getblock "blockhash" ( verbosity )
getblockchaininfo
getblockcount
getblockfilter "blockhash" ( "filtertype" )
getblockhash height
getblockheader "blockhash" ( verbose )
getblockstats hash_or_height ( stats )
getchaintips
getchaintxstats ( nblocks "blockhash" )
getdifficulty
getmempoolancestors "txid" ( verbose )
getmempooldescendants "txid" ( verbose )
getmempoolentry "txid"
getmempoolinfo
getrawmempool ( verbose )
gettxout "txid" n ( include_mempool )
gettxoutproof ["txid",...] ( "blockhash" )
gettxoutsetinfo
preciousblock "blockhash"
pruneblockchain height
savemempool
scantxoutset "action" ( [scanobjects,...] )
verifychain ( checklevel nblocks )
verifytxoutproof "proof"

== Control ==
getmemoryinfo ( "mode" )
getrpcinfo
help ( "command" )
logging ( ["include_category",...] ["exclude_category",...] )
stop
uptime

== Generating ==
generatetoaddress nblocks "address" ( maxtries )
generatetodescriptor num_blocks "descriptor" ( maxtries )

== Mining ==
getblocktemplate ( "template_request" )
getmininginfo
getnetworkhashps ( nblocks height )
prioritisetransaction "txid" ( dummy ) fee_delta
submitblock "hexdata" ( "dummy" )
submitheader "hexdata"

== Network ==
addnode "node" "command"
clearbanned
disconnectnode ( "address" nodeid )
getaddednodeinfo ( "node" )
getconnectioncount
getnettotals
getnetworkinfo
getnodeaddresses ( count )
getpeerinfo
listbanned
ping
setban "subnet" "command" ( bantime absolute )
setnetworkactive state

== Rawtransactions ==
analyzepsbt "psbt"
combinepsbt ["psbt",...]
combinerawtransaction ["hexstring",...]
converttopsbt "hexstring" ( permitsigdata iswitness )
createpsbt [{"txid":"hex","vout":n,"sequence":n},...] [{"address":amount},{"data":"hex"},...] ( locktime replaceable )
createrawtransaction [{"txid":"hex","vout":n,"sequence":n},...] [{"address":amount},{"data":"hex"},...] ( locktime replaceable )
decodepsbt "psbt"
decoderawtransaction "hexstring" ( iswitness )
decodescript "hexstring"
finalizepsbt "psbt" ( extract )
getrawtransaction "txid" ( verbose "blockhash" )
joinpsbts ["psbt",...]
sendrawtransaction "hexstring" ( maxfeerate )
signrawtransactionwithkey "hexstring" ["privatekey",...] ( [{"txid":"hex","vout":n,"scriptPubKey":"hex","redeemScript":"hex","witnessScript":"hex","amount":amount},...] "sighashtype" )
testmempoolaccept ["rawtx",...] ( maxfeerate )
utxoupdatepsbt "psbt" ( ["",{"desc":"str","range":n or [n,n]},...] )

== Util ==
createmultisig nrequired ["key",...] ( "address_type" )
deriveaddresses "descriptor" ( range )
estimatesmartfee conf_target ( "estimate_mode" )
getdescriptorinfo "descriptor"
signmessagewithprivkey "privkey" "message"
validateaddress "address"
verifymessage "address" "signature" "message"

== Zmq ==
getzmqnotifications

[btc123thatthere]

Bitcoin.conf doesn't exist.

Debug.log:

2020-11-01T08:03:15Z Bitcoin Core version v0.20.1 (release build)
2020-11-01T08:03:15Z Assuming ancestors of block 0000000000000000000f2adce67e49b0b6bdeb9de8b7c3d7e93b21e7fc1e819d have valid signatures.
2020-11-01T08:03:15Z Setting nMinimumChainWork=00000000000000000000000000000000000000000e1ab5ec9348e9f4b8eb8154
2020-11-01T08:03:15Z Using the 'standard' SHA256 implementation
2020-11-01T08:03:15Z Default data directory /home/pi/.bitcoin
2020-11-01T08:03:15Z Using data directory /home/pi/.bitcoin
2020-11-01T08:03:15Z Config file: /home/pi/.bitcoin/bitcoin.conf (not found, skipping)
2020-11-01T08:03:15Z Using at most 125 automatic connections (1024 file descriptors available)
2020-11-01T08:03:15Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2020-11-01T08:03:15Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2020-11-01T08:03:15Z Script verification uses 3 additional threads
2020-11-01T08:03:15Z scheduler thread start
2020-11-01T08:03:15Z Binding RPC on address ::1 port 8332 failed.
2020-11-01T08:03:15Z Binding RPC on address 127.0.0.1 port 8332 failed.
2020-11-01T08:03:15Z Unable to bind any endpoint for RPC server
2020-11-01T08:03:15Z Error: Unable to start HTTP server. See debug log for details.
2020-11-01T08:03:15Z Shutdown: In progress...
2020-11-01T08:03:15Z scheduler thread exit
2020-11-01T08:03:15Z Shutdown: done

[nc50lc]

Try to launch Bitcoin-qt with -wallet='directory' argument.
That will instruct it to use the wallet.dat in that directory (although it should create one in the data dir by default).

If it didn't work, tell us how bitcoin core was installed in your RPi.

[achow101]

In the Info tab, do you see a line that says "Using BerkeleyDB Version"? If you don't this means that you have a version compiled without wallet support. If you do, then you do have wallet support, but have a configuration option somewhere that disables it.

[btc123thatthere]

Problem found - I was looking at the wrong bitcoin.conf file.
It looks like a new bitcoin.conf file was created when bitcoin core was installed on its first run, and then when I told it to use the external drive for the blocks, it also used the bitcoin.conf file from the external drive as well.

I'm glad the new bitcoin core has a button to open the Debug log file, as that's the same directory that the relevant bitcoin.conf file is in.

Thanks