Monero-gui refuses to build

[lulighttec]

Beating my head against the wall trying to get the gui to install on Ubuntu 20.04 for Arm7. Following these instructions: https://github.com/monero-project/monero-gui"
./build.sh" can't find 3 files that should be there. -lwallet_merged -lepee -leasylogging (even though I installed the easylogging package separately to make sure it was there) Read a few threads similar to mine, but no avail. Here's a paste of the log output: PrivateBin I tried installing the regular monero first, then the gui; regular monerod installs and runs ok. Guibuild still produced this error. Noticed there's also a monero directory inside monero-gui, so tried "make" in that directory first, then "./build.sh" in monero-gui, but still no joy.

[lulighttec]

It seems this way, I'm exiting root before I create the wallet and really make sure, but it got past the part where it crashed the first time

[lulighttec]

There's probably a quick and easy CLI command to write the contents of monero-gui2 over the original monero-gui, right? And will that break anything? like, mv monero-gui2/* monero-gui/ or would

cd monero-gui2
find -exec mv {} ../monero-gui/ +

be better?

[selsta]

You should be able to move around the binaries, not sure about changing the whole folder. Might reduce in weird issues if you want to rebuild.

[lulighttec]

It is running, and currently downloading the blockchain. :-) Also, I opted for fixing a broken shortcut instead of moving anything around; seemed like a safer solution. Thank you so much for your help!

One question: is there a way to change the transparency of the interface? When it's in Dark mode, it almost blends in with the background (which is orange) with white floating text, but if I reverse it, the text becomes transparent on a white background, which is even harder to read. If it means rebuilding, I probably won't bother, but if there's an easy fix...

Also, was serious about lattes.

[selsta]

One question: is there a way to change the transparency of the interface? When it's in Dark mode, it almost blends in with the background (which is orange) with white floating text, but if I reverse it, the text becomes transparent on a white background, which is even harder to read. If it means rebuilding, I probably won't bother, but if there's an easy fix...

Can you make a screenshot? Not sure what you mean with transparency.

Also, was serious about lattes.

:))

[lulighttec]

Took a while, but yes. lol Top photo is Dark theme, Bottom photo is Light Theme.

[selsta]

That’s definitely a bug, it should not look like that.. hmm

Which Qt version did you use to compile? Can you update your graphics drivers?

Alternatively you can start the GUI with the QMLSCENE_DEVICE=softwarecontext env var, but this will use the low quality renderer..

[lulighttec]

Qt Creator 4.11.0

Based on Qt 5.12.8 (GCC 9.3.0, 32 bit)

Anytime I tried to search for 5, I kept getting pointed here... TBH, at first I thought it was just extra fancy, because when the wallet is locked, everything behind the password field is blurred and looks pretty cool LOL

Oh, and I should probably mention that that's the way the interface has looked (after it built) for me from day 1, so this looks the same as crashing binary did.

[lulighttec]

oooo, it really didn't like when I turned off custom decorations... Luckily the hotspots still work for the checkboxes and I was able to set it back... the first time. the second time it crashed the whole shell :-o I know now not to fiddle with that setting (since it's only for the titlebar).

[lulighttec]

I did a clean clone into (a fresh) /monero-gui (not the current monero-gui2) and applied patches with git pull (though 3094 wouldn't, so I had to manually remove "AND STATIC" from line 398). I decided to stop the daemon and go ahead and build it.

it's building faster now...

[lulighttec]

Well, no errors anywhere that I could see this time; though something is still not quite right. Still had the crash when trying to check/uncheck the special decorations box. This is not a crucial component, right? Probably ok to load my wallet and continue downloading blockchain?

[selsta]

This is not a crucial component, right?

No, not crucial.

My only suggestion to fix these weird visual issues:

• Try to build with Qt 5.15 instead of 5.12
• update your graphics drivers (not sure if that is possible)

[lulighttec]

I'm not sure if that's possible either, (updating graphics drivers) but I'll try. Might be worth trying that first.

[lulighttec]

OMG, updated firmware and now it won't boot. This is a problem for a different chunk of github, but seriously? ready to cry

[selsta]

Does anything described here help? https://wiki.odroid.com/troubleshooting/odroid_flashing_tools

[lulighttec]

Well, that's what I was currently looking at. I was able to rescue the wallet file, and i can probably rescue the partially downloaded blockchain too, should i need to re-etch my card. I found a spare microSD and I'm flashing with the image. I'm hoping that will bring it back, and then I can go from there.

[lulighttec]

well, it boots again. in the process of putting things back together. Since I essentially had to start over, I'm taking the opportunity to build Qt 5.15 first.

[lulighttec]

It gets all the way to the end of the build and fails. I have a different error, though. [errors.txt](https://github.com/monero-project/monero-gui/files/5289439/errors.txt)

[selsta]

Anything different with this setup?

[lulighttec]

I built qt 5.15.1, built qt creator, otherwise no, I tried to do it exactly the same.

Sent from my iPhone

On Sep 27, 2020, at 9:28 PM, selsta notifications@github.com wrote:



Anything different with this setup?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/monero-project/monero-gui/issues/3093#issuecomment-699722169, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB4VXZ25SGRMEMPWCSRSAILSH7RCRANCNFSM4RTEL5IA.

[selsta]

You have to set CMAKE_PREFIX_PATH to your Qt 5.15.1 path in your cmake command, else 5.12 from your package manager gets picked up. On my system it is -D CMAKE_PREFIX_PATH=~/dev/Qt/5.15.1/clang_64/, on your system it won’t be called clang_64 but something else.

[lulighttec]

Ok. I’ll try that. I put the path in the environment, but I guess it didn’t pick it up.

Sent from my iPhone

On Sep 27, 2020, at 9:34 PM, selsta notifications@github.com wrote:



You have to set CMAKE_PREFIX_PATH to your Qt 5.15.1 path in your cmake command, else 5.12 gets picked up. On my system it is -D CMAKE_PREFIX_PATH=~/dev/Qt/5.15.1/clang_64/, on your system it won’t be called clang_64 but something else.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/monero-project/monero-gui/issues/3093#issuecomment-699723395, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB4VXZ35XSJ6M4NTFJQTGDTSH7RZ5ANCNFSM4RTEL5IA.

[lulighttec]

CMAKE_PREFIX_PATH=/usr/local/Qt-5.15.1/bin/?

[selsta]

I think it should be without bin, just /usr/local/Qt-5.15.1/

Anyway if you want to try Qt 5.12.1 again make sure to remove 5.15 out of your path, I can imagine this producing weird issues.

[lulighttec]

I did make sure to clean out 5.12 to avoid weird issues before I started building again. At one point, if I was non-root, I had access to 5.15.1 in the path, but if I was root, only had access to 5.12. I fixed that.

It built last night, again with one error at the very end, but I used /bin/ on the end of the path. I do wish it didn't take 8 hours to get to the error at the end. I just set it to "make" again, this time without /bin/. I guess in about 7 hours I'll let you know what happens.

[lulighttec]

It got all the way through both cmake and make without any errors. However, when I try to run it:

errors.txt

Which application is it suggesting I reinstall?

[lulighttec]

Holdup... I ran from /usr/local/bin.... and... I think it's running... is this it?

[selsta]

Looks good without graphics glitches :)

[selsta]

By the way, you can install ccache with your package manager it it will greatly speed up subsequent builds, but looks like you managed to build the GUI now anyway.

[lulighttec]

I wish I had known about ccache at the beginning... oh well, next time I'll know. Hopefully there won't be a next time. :-) Right now, it's syncing, and the interface doesn't seem to be doing any glitching or crashing, so I'm going to leave it be until it finishes and go to bed. I think we're there, though.

I may have spoken too soon. Doesn't appear to be syncing...

E Unexpected recv fail
I Failed to invoke http request to /json_rpc
D Wallet connection status changed 0
D checking connection status
D Wallet connection status changed 3
D Problems at read: Operation canceled

Just keeps looping this over and over

[xiphon]

Make sure you have monerod process running. You can start it from the GUI, see Settings -> Node tab.

[lulighttec]

I have tried, but monerod keeps failing when I start it, saying:

I SYNCHRONIZATION started
I [batch] DB resize needed
W Failed to set new mapsize: Cannot allocate memory
E Error in handle_invoke_map: Failed to set new mapsize: Cannot allocate memory

It won't go past this point, and if I type "exit" to try to stop the daemon, it will 'Stop signal sent', but the process never stops. Same thing with "stop_daemon". (I typed "help" at one point, and learned some commands.)

I should also add that I have tried rebooting to start fresh, and have tried starting the daemon from inside the gui, but it fails to start, so the gui suggests trying to start manually. When I start manually (from the terminal) I get what you see above.

[lulighttec]

Not only this, but once monerod is started, I can't get it to stop and free up the IPv4 binding so I can try again. It just keeps running and running, not doing anything. I even tried closing the terminal to kill the running process, and that didn't work. Edit: learned how to properly use the kill command in terminal. Still, this is kind of a problem, yes?

[xiphon]

Cannot allocate memory

The device ran out of memory. Nothing we can do about it on the Monero GUI side.

[lulighttec]

That can't be the case. I'm looking at htop and it's definitely not, and it worked at least once right after I built it, and besides that, other things keep running, so how can this be?

[xiphon]

Do you have enough free space on the disk?

[lulighttec]

I have 92 of 128GB available, and I could probably dump some things and get a bit more if i needed to, though last I read the blockchain was only 75GB, so that should be enough, shouldn't it?

Edit: I have increased free space to 105GB. Same result.

[xiphon]

Could you try official monero ARMV7 cli binary? https://downloads.getmonero.org/cli/linuxarm7

[lulighttec]

^^^^This daemon works, and works with the gui, so it must be a build problem. I think my solution will be to replace what I built with what I just downloaded, and that should fix things, yes?

[xiphon]

Right.