monero-gui@0.17.3.2 is unable to use p2pool miner due to it's binaries instalaltion to read-only filesystem

  • Done
  • quality assurance status badge
Details
2 participants
  • Guillaume Le Vaillant
  • Jacob Hrbek
Owner
unassigned
Submitted by
Jacob Hrbek
Severity
normal
J
J
Jacob Hrbek wrote on 19 May 2022 00:11
(address . bug-guix@gnu.org)
0aca16c8-5969-4119-ea72-8a2529ee6983@rixotstudio.cz
it's trying to use the read-only filesystem and failing as a result of
it (should probably use the `~/.guix-profile/bin/p2pool`):
Steps to reproduce:
1. Invoke `guix shell monero-gui@0.17.3.2 -- monero-wallet-gui`
2. Create a new wallet (user-friendly GUI)
3. Set the wallet to use a local node and wait for it to compute the
blockchain until fully synced (Settings->Node->Local node and Start the
daemon)
 * Optionally consider adding `--prune-blockchain` for daemon startup
flags for significantly reduced blockchain (~40 GB) to avoid computing
the ~120 GB node or using Bootstrap Address to download the blockchain
already computed
4. Try to launch the miner using p2pool pool and expect failure above
(Advanced->Mining->Mining mode=P2Pool and Start mining)
--
-- Jacob Hrbek #StandWithUkraine
Attachment: file
Attachment: signature.asc
G
G
Guillaume Le Vaillant wrote on 12 Aug 2022 17:49
(address . 55512-done@debbugs.gnu.org)
87pmh5tq1p.fsf@kitej
Hi,

I fixed the path to the p2pool binary in commit
eecb5efad92b8f7cb5bbea0be66c4707a749512c.
I checked that p2pool starts when clicking the "Start Mining" button,
but I have not tested if all its functionalities are working correctly.
Please open a new bug report if you find issues.
-----BEGIN PGP SIGNATURE-----

iIUEAREKAC0WIQTLxZxm7Ce5cXlAaz5r6CCK3yH+PwUCYvZ34g8cZ2x2QHBvc3Rl
by5uZXQACgkQa+ggit8h/j+qNgEAmzN4MhjaYAhYxgfjK/5a3PJbtK0khh2e4PR7
fTtOmt4A/0iZRhqhJ5IVOYG3k+ZiYoC72m8BarPW9Jzoku6LicTJ
=QS0L
-----END PGP SIGNATURE-----

Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 55512@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 55512
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch