<p>There is no way to have them run at the same time. <code>bitcoin-qt</code> is an entirely separate binary that contains the entire contents of <code>bitcoind</code> in addition all of the GUI things. It cannot operate on an existing one since that is not how it communicates with the node part of the software.</p>
<p>However the issue that you are describing could be considered a bug and I would encourage you to open an issue in the <a href="https://github.com/bitcoin-core/gui/issues" rel="nofollow noreferrer">GUI issue tracker</a> so that someone more familiar with the GUI can take a look at it and possibly fix it.</p>

CC BY-SA 4.0
2023-08-13T19:43:35.737Z
The problem with that is that every single time I create a Github account, for many years now (since MS bought it), it has either been rejected or shadowbanned instantly. I'm unable to file any bugs or make any issue on any project at all. Doesn't matter how many different PAID proxies I try. None of them work.
V B
CC BY-SA 4.0
2023-08-13T19:50:57.443Z
I have created an issue for you: https://github.com/bitcoin-core/gui/issues/748
Ava Chow
CC BY-SA 4.0
2023-08-13T19:03:45.680Z
2023-08-13T19:03:45.680Z
Ava Chow
<blockquote>
<p>I will open [the GUI] <strong>only when I actively need to do a Bitcoin transfer.</strong></p>
</blockquote>
<p>I would consider one of</p>
<ul>
<li><a href="https://chainquery.com/bitcoin-cli/sendtoaddress" rel="nofollow noreferrer"><code>$ bitcoin-cli sendtoaddress &quot;[address]&quot; [amount]</code></a></li>
<li>Something like <a href="https://sparrowwallet.com/" rel="nofollow noreferrer">sparrow</a> which supports
<blockquote>
<p>A range of connection options: Public servers, <strong>Bitcoin Core</strong> and private Electrum servers</p>
</blockquote>
</li>
</ul>

CC BY-SA 4.0
2023-08-13T15:35:15.510Z
2023-08-13T15:35:15.510Z
RedGrittyBrick
<p>As others have written, you cannot use <code>bitcoin-qt</code> and <code>bitcoind</code> with the same directory at the same time, because both require exclusive access.</p>
<p>While the situation certainly is imperfect, you could make a small tweak to make it more bearable. As you already do, run <code>bitcoind</code> at startup so that your blockchain will be synchronized at all times. Then make yourself a shell command alias that calls <code>bitcoin-cli stop &amp;&amp; sleep 120 &amp;&amp; bitcoin-qt</code>. When you want to make some payments, call your alias and go get a cup of coffee, touch the grass, or browse the internet for a couple minutes. When you get back, your Bitcoin wallet will have popped up.</p>
<p>Finally, add a <code>cron</code> job to your system that attempts to start <code>bitcoind</code> every 15 minutes. If it’s already running, it will simply error out with <code>Error: Cannot obtain a lock on data directory /home/user/.bitcoin. Bitcoin Core is probably already running.</code> Otherwise, your computer will automatically restart <code>bitcoind</code> a few minutes after you close <code>bitcoin-qt</code>.</p>
<p>This would turn the enervating process of “stopping one program, starting a second, using the second program, stopping the second program and restarting the first program” into one command to kick off starting the GUI, making your transfer, and then simply quitting the GUI when you’re done.</p>

CC BY-SA 4.0
2023-08-14T15:34:34.083Z
2023-08-14T15:34:34.083Z
Murch
<p>I know this post is old but if you run bitcoin-qt -min -splash=0</p>
<p>the loading wallets dialog box will appear for just a split second and disappear</p>

CC BY-SA 4.0
2024-02-11T03:49:28.670Z
2024-02-11T03:49:28.670Z
callmejoe
<p>Is it possible to run Bitcoin Core (GUI) at the same time as bitcoind?</p>
<p><strong>Nope</strong>. Both pieces of software will use a LOCK on databases (levelDB for example). So it <em>will not</em> be possible to run <em>at the same time</em> GUI / Daemon. You should know there would be plenty of bugs if this could be possible...</p>
<p>Like @RedGrittyBrick wrote, using bitcoin-cli can be a solution in order to communicate to your RPC. But a GUI one is easier. Sparrow is nice. However it is an advanced software which displays a lot of technical elements.</p>

CC BY-SA 4.0
2023-08-13T16:30:16.977Z
2023-08-13T16:30:16.977Z
Loopite
<p>I'm in a very frustrating situation. I used to run Bitcoin Core on Windows, without these problems, but ever since I switched to Linux (XFCE), and I of course have Bitcoin Core (GUI) starting automatically, I'm interrupted after like five minutes while typing/working by an indescribably annoying GUI box saying &quot;Loading wallets...&quot;. That's in spite of running it with <code>-min</code> to start minimized and not bother me. But it does anyway.</p>
<p>This has become so annoying that I've been forced to remove Bitcoin Core from starting automatically. Instead, I will open it only when I actively need to do a Bitcoin transfer. But then a new problem arises: the blockchain will be many months outdated when I finally open it up, and then it has to sit around for a long time and sync the blockchain before I can do anything with it. Also, I can't use its RPC API if nothing is running.</p>
<p>So instead I'm now starting <code>bitcoind</code> at boot, so that it will run in the background without a GUI and keep the blockchain up to date.</p>
<p>But now, there's a new problem: if I start Bitcoin Core (GUI) while bitcoind is running in the background, I get an error saying that it can't obtain a lock of the blocks dir or something along those lines. Obviously, this is because bitcoind is already working on the block dir.</p>
<p>I can &quot;solve&quot; this by first running a script which calls the RPC API with the &quot;stop&quot; command, so that bitcoind shuts down safely (killing the process is not safe). Then I'm able to open Bitcoin Core (GUI) and start using it.</p>
<p>But, as you can imagine, this is anything but an ideal situation. I now have to both remember to not just start the Bitcoin Core (GUI) program when I need it, but also to first dig up and run that script to first shut down bitcoind. And then, after I'm done in Bitcoin Core (GUI), I need to shut it down and again start bitcoind to go back to the same state as before. It just makes my skin crawl.</p>
<p>Is there some hidden option I can send when opening Bitcoin Core (GUI) so that instead of trying to run its own stuff, it just &quot;hooks into&quot; the existing bitcoind?</p>

<bitcoin-core><bitcoind><linux><command-line-options><automation>
Is it possible to run Bitcoin Core (GUI) at the same time as bitcoind?
V B
# Is it possible to run Bitcoin Core (GUI) at the same time as bitcoind?

(Asked by: username_0 on 2023-08-13)

I'm in a very frustrating situation. I used to run Bitcoin Core on Windows, without these problems, but ever since I switched to Linux (XFCE), and I of course have Bitcoin Core (GUI) starting automatically, I'm interrupted after like five minutes while typing/working by an indescribably annoying GUI box saying "Loading wallets...". That's in spite of running it with `-min` to start minimized and not bother me. But it does anyway.

This has become so annoying that I've been forced to remove Bitcoin Core from starting automatically. Instead, I will open it only when I actively need to do a Bitcoin transfer. But then a new problem arises: the blockchain will be many months outdated when I finally open it up, and then it has to sit around for a long time and sync the blockchain before I can do anything with it. Also, I can't use its RPC API if nothing is running.

So instead I'm now starting `bitcoind` at boot, so that it will run in the background without a GUI and keep the blockchain up to date.

But now, there's a new problem: if I start Bitcoin Core (GUI) while bitcoind is running in the background, I get an error saying that it can't obtain a lock of the blocks dir or something along those lines. Obviously, this is because bitcoind is already working on the block dir.

I can "solve" this by first running a script which calls the RPC API with the "stop" command, so that bitcoind shuts down safely (killing the process is not safe). Then I'm able to open Bitcoin Core (GUI) and start using it.

But, as you can imagine, this is anything but an ideal situation. I now have to both remember to not just start the Bitcoin Core (GUI) program when I need it, but also to first dig up and run that script to first shut down bitcoind. And then, after I'm done in Bitcoin Core (GUI), I need to shut it down and again start bitcoind to go back to the same state as before. It just makes my skin crawl.

Is there some hidden option I can send when opening Bitcoin Core (GUI) so that instead of trying to run its own stuff, it just "hooks into" the existing bitcoind?

**Tags:** bitcoin-core, bitcoind, linux, command-line-options, automation


---

## 5 answers

### Answer by username_1 on 2023-08-13. Score: 4

There is no way to have them run at the same time. `bitcoin-qt` is an entirely separate binary that contains the entire contents of `bitcoind` in addition all of the GUI things. It cannot operate on an existing one since that is not how it communicates with the node part of the software.

However the issue that you are describing could be considered a bug and I would encourage you to open an issue in the [GUI issue tracker](https://github.com/bitcoin-core/gui/issues) so that someone more familiar with the GUI can take a look at it and possibly fix it.

> **Comments:**
> **username_0**: The problem with that is that every single time I create a Github account, for many years now (since MS bought it), it has either been rejected or shadowbanned instantly. I'm unable to file any bugs or make any issue on any project at all. Doesn't matter how many different PAID proxies I try. None of them work.  
> **username_1**: I have created an issue for you: https://github.com/bitcoin-core/gui/issues/748  

---

### Answer by username_2 on 2023-08-13. Score: 1

> I will open [the GUI] **only when I actively need to do a Bitcoin transfer.**

I would consider one of

* [`$ bitcoin-cli sendtoaddress "[address]" [amount]`](https://chainquery.com/bitcoin-cli/sendtoaddress)
* Something like [sparrow](https://sparrowwallet.com/) which supports
  > A range of connection options: Public servers, **Bitcoin Core** and private Electrum servers


---

### Answer by username_3 on 2023-08-14. Score: 1

As others have written, you cannot use `bitcoin-qt` and `bitcoind` with the same directory at the same time, because both require exclusive access.

While the situation certainly is imperfect, you could make a small tweak to make it more bearable. As you already do, run `bitcoind` at startup so that your blockchain will be synchronized at all times. Then make yourself a shell command alias that calls `bitcoin-cli stop && sleep 120 && bitcoin-qt`. When you want to make some payments, call your alias and go get a cup of coffee, touch the grass, or browse the internet for a couple minutes. When you get back, your Bitcoin wallet will have popped up.

Finally, add a `cron` job to your system that attempts to start `bitcoind` every 15 minutes. If it’s already running, it will simply error out with `Error: Cannot obtain a lock on data directory /home/user/.bitcoin. Bitcoin Core is probably already running.` Otherwise, your computer will automatically restart `bitcoind` a few minutes after you close `bitcoin-qt`.

This would turn the enervating process of “stopping one program, starting a second, using the second program, stopping the second program and restarting the first program” into one command to kick off starting the GUI, making your transfer, and then simply quitting the GUI when you’re done.


---

### Answer by username_4 on 2024-02-11. Score: 0

I know this post is old but if you run bitcoin-qt -min -splash=0

the loading wallets dialog box will appear for just a split second and disappear


---

### Answer by username_5 on 2023-08-13. Score: 0

Is it possible to run Bitcoin Core (GUI) at the same time as bitcoind?

**Nope**. Both pieces of software will use a LOCK on databases (levelDB for example). So it *will not* be possible to run *at the same time* GUI / Daemon. You should know there would be plenty of bugs if this could be possible...

Like @username_2 wrote, using bitcoin-cli can be a solution in order to communicate to your RPC. But a GUI one is easier. Sparrow is nice. However it is an advanced software which displays a lot of technical elements.


---

