Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GUI v0.12 unable to connect to remote / local daemon (error std::bad_cast) #1261

Closed
dEBRUYNE-1 opened this issue Apr 4, 2018 · 93 comments
Closed

Comments

@dEBRUYNE-1
Copy link
Contributor

dEBRUYNE-1 commented Apr 4, 2018

Getting a few reports of people unable to connect to their own (local) node or remote node after upgrading to v0.12.0.0. Logs:

Case 1:

https://paste.fedoraproject.org/paste/QKowduN71M9OMENPNHX2Vg

https://paste.fedoraproject.org/paste/W3HZGq7O9~TTIfw3SSKJew

Reddit conversation: https://www.reddit.com/r/Monero/comments/89nn2p/monero_gui_v01200_lithium_luna_released/dws770b/


Case 2:

https://paste.fedoraproject.org/paste/dwXoiPEYE82lO5g7FB793Q

https://paste.fedoraproject.org/paste/pj3gZVLxvpcE5VWAvDsIXA

Reddit conversation: https://www.reddit.com/r/Monero/comments/89nn2p/monero_gui_v01200_lithium_luna_released/dwsh4fc/


EDIT: Three more Linux users affected here. The issue seems specific to Linux.

EDIT2: For anyone incurring this issue: As last resort you can always run GUI v0.11 with daemon (monerod) v0.12. Please see instructions below for using v0.11 and being sufficiently prepared for the upcoming scheduled network upgrade:

<dEBRUYNE> You mean v0.11?
<dEBRUYNE> If you're using a local node -> replace monerod v0.11 w/ monerod v0.12
<dEBRUYNE> remote node, just open v0.11 and you should be able to use it past the fork
<dEBRUYNE> However, the wallet cache may be incompatible, because (afaik) it's only forward compatible
<dEBRUYNE> So if you incur an issue opening the wallet, use -> <dEBRUYNE> Go to your wallet directory (Documents\Monero\<wallet-name> on Windows | ~/Monero/<wallet-name>) and rename <wallet-name> to <wallet-name>-old

After block 1546000 you should also ensure that your transaction uses ring size 7, otherwise it will be rejected by the network.

EDIT3: Better overview of workarounds:

https://monero.stackexchange.com/questions/7999/linux-gui-v0-12-does-not-connect-to-local-or-remote-node-stdbad-cast-error

EDIT4: GUI v0.12.2.0, which includes a fix for this particular issue, has been released:

https://www.reddit.com/r/Monero/comments/8vkx2g/gui_v01220_released/

@dEBRUYNE-1
Copy link
Contributor Author

+bug

@badfiles
Copy link

badfiles commented Apr 4, 2018

I run the daemon in my lan, the cli version successfully connects and syncs wallet with the blockchain.
The gui version does nothing when I push 'connect', nothing in logs, status disconnected. WTF?

@dEBRUYNE-1
Copy link
Contributor Author

@badfiles: Which operating system are you using?

@memorie62
Copy link

same problem on Win64. daemon fails. log shows

2018-04-05 00:33:03.194 8536 WARN net.http src/wallet/wallet_errors.h:794 C:/msys64/home/vagrant/slave/monero-gui-win64/build/monero/src/wallet/wallet2.cpp:5610:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = gettransactions

the local file does not exist. Also, monerod.exe is not included in the Win64 download.

@stevesbrain
Copy link

No issue here; running Arch linux version, connecting to version 0.12.0.0 node also running on Arch Linux.

@medusadigital
Copy link
Contributor

@memorie62 monerod.exe is definetely included, make sure no anti virus software removed it while unpacking

@CaptainPlanet77
Copy link

I'm also affected. Running Xubuntu 16.04.

@badfiles
Copy link

badfiles commented Apr 5, 2018

Ubuntu 17.10
No connection attempts on the pool side, nothing in client logs.

@mbay1971
Copy link

mbay1971 commented Apr 5, 2018

same on Ubuntu 16.04.4 LTS

@dEBRUYNE-1
Copy link
Contributor Author

dEBRUYNE-1 commented Apr 5, 2018

@CaptainPlanet77, @badfiles, @mbay1971: As last resort you can always run GUI v0.11 with daemon (monerod) v0.12. Please see instructions below for using v0.11 and being sufficiently prepared for the upcoming scheduled network upgrade:

<dEBRUYNE> You mean v0.11?
<dEBRUYNE> If you're using a local node -> replace monerod v0.11 w/ monerod v0.12
<dEBRUYNE> remote node, just open v0.11 and you should be able to use it past the fork
<dEBRUYNE> However, the wallet cache may be incompatible, because (afaik) it's only forward compatible
<dEBRUYNE> So if you incur an issue opening the wallet, use -> <dEBRUYNE> Go to your wallet directory (Documents\Monero\<wallet-name> on Windows | ~/Monero/<wallet-name>) and rename <wallet-name> to <wallet-name>-old

After block 1546000 you should also ensure that your transaction uses ring size 7, otherwise it will be rejected by the network.

@badfiles
Copy link

badfiles commented Apr 5, 2018

cli 0.12 works fine. and I don't need local daemon, I already have a running 0.12 daemon on another machine.

@M5M400
Copy link

M5M400 commented Apr 5, 2018

same here. Ubuntu 17.10, v0.12 release binaries.

2018-04-05 15:42:25.591	    7fa7dbfff700	WARN 	net.http	src/wallet/wallet_errors.h:794	/home/vagrant/slave/monero-gui-ubuntu-amd64/build/monero/src/wallet/wallet2.cpp:5610:N5tools5error23no_connection_to_daemonE: no connection to daemon, request = gettransactions
2018-04-05 15:42:25.591	    7fa7dbfff700	ERROR	wallet.wallet2	src/wallet/wallet2.cpp:3827	Failed to save rings, will try again next time
2018-04-05 15:42:25.593	    7fa7f9772840	ERROR	default	src/wallet/api/utils.cpp:46	error: std::bad_cast
2018-04-05 15:42:49.498	    7fa7f9772840	ERROR	default	src/wallet/api/utils.cpp:46	error: std::bad_cast

Same behavior for starting daemon in GUI or separately and for remote daemon.

@erols
Copy link

erols commented Apr 5, 2018

Same here on Ubuntu 17.10.

I noticed that I couldn't set Wallet Mode to Local Node in the gui

screenshot from 2018-04-05 21-33-35

@dEBRUYNE-1
Copy link
Contributor Author

@erols - If the Local Node button is grey it means that the wallet mode is set to local node.

@erols
Copy link

erols commented Apr 5, 2018

@dEBRUYNE-1 thanks.

@ghost
Copy link

ghost commented Apr 7, 2018

Unable to connect to daemon using monero-gui-v0.12.0.0 on Mint 18 confirmed

@notgiven688
Copy link

Same here. Ubuntu 17.10.

@gypzie
Copy link

gypzie commented Apr 7, 2018

@badfiles did you need to open and run the CLI on another machine to connect to daemon. I see that CLI works, it is also working for me. Were you able to use this to make the GUI work?

@badfiles
Copy link

badfiles commented Apr 7, 2018

CLI from GUI package syncs well with my remote daemon.
GUI version does not connect and also does not exit properly.
I am quite surprised you guys rolling out a release that does not connect and does not quit under most famous Linux distro.

@dEBRUYNE-1
Copy link
Contributor Author

I am quite surprised you guys rolling out a release that does not connect and does not quit under most famous Linux distro.

None of us did incur this bug whilst testing. Frankly, we were quite surprised too this bug was present.

For anyone that is affected, could you please test the buildbot binary from here?

https://build.getmonero.org/builders/monero-gui-ubuntu-amd64/builds/105

It should include a fix for this particular issue.

@notgiven688
Copy link

@dEBRUYNE-1 buildbot binary also does not work.

@dEBRUYNE-1
Copy link
Contributor Author

@notgiven688 - Same error in the log?

@notgiven688
Copy link

I only get this error:
ERROR default src/wallet/api/utils.cpp:46 error: std::bad_cast

@badfiles
Copy link

badfiles commented Apr 8, 2018

2018-04-08 10:43:36.934	    7f5af5d76840	ERROR	default	src/wallet/api/utils.cpp:46	error: std::bad_cast
2018-04-08 10:44:01.643	    7f5af5d76840	ERROR	default	src/wallet/api/utils.cpp:46	error: std::bad_cast

@dEBRUYNE-1
Copy link
Contributor Author

@notgiven688 & @badfiles - are you using a local node or a remote node?

@badfiles
Copy link

badfiles commented Apr 8, 2018

remote node. I have no space for the whole blockchain on my laptop.

@notgiven688
Copy link

@dEBRUYNE-1 local

@vitalisator
Copy link

@dEBRUYNE-1, same issue with the fix on Linux Mint x64
2018-04-08 16:42:56.522 7f70e8e447c0 ERROR default src/wallet/api/utils.cpp:46 error: std::bad_cast

@rysade
Copy link

rysade commented Apr 20, 2018

@rysade (and anyone else affected by this particular issue) - Could you test these binaries?

https://build.getmonero.org/builders/monero-gui-ubuntu-amd64/builds/201

That appears to have worked.
stdout:
app startd available width: 1871 available height: 1047 devicePixelRatio: 1 screen height: 1920 screen width: 1080 screen logical dpi: 96 screen Physical dpi: 102.598 screen calculated ratio: 0.801544 qml: check next false qml: Checking seed qml: check next false qml: Checking seed qml: check next false qml: check next false 2018-04-20 00:50:06.285 7f750424a7c0 WARN net.http src/common/util.cpp:627 Failed to determine whether address '' is local, assuming not libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile qml: transfer page loaded qml: PrivacyLevel changed:0 qml: mixin count: 6 qml: qrScannerEnabled disabled qrc:/qt-project.org/imports/QtQuick/Controls/ApplicationWindow.qml:241:9: QML ContentItem: Binding loop detected for property "implicitWidth" Checking for updates qml: languages availible: 29 qml: initializing.. setLanguage "en" qml: transfer page loaded qml: PrivacyLevel changed:0 qml: mixin count: 6 qml: opening wallet at: /home/rysade/.local/monero/default-wallet.keys , network type: mainnet Wallet* WalletManager::openWallet(const QString&, const QString&, NetworkType::Type): opening wallet at /home/rysade/.local/monero/default-wallet.keys, nettype = 0 2018-04-20 00:50:25.166 7f74e4d09700 WARN wallet.wallet2 src/wallet/wallet2.cpp:3718 Loaded wallet keys file, with public address: 44ZBNkbTqsdTW4b5r6grVFRCShhPEeeTBS9vNxz6WJSbYm9jRC5nyzuH9DhGu29irXLF16oJ2JGDzJ4NCLRmXvxwK8h3nrh Wallet* WalletManager::openWallet(const QString&, const QString&, NetworkType::Type): opened wallet: 44ZBNkbTqsdTW4b5r6grVFRCShhPEeeTBS9vNxz6WJSbYm9jRC5nyzuH9DhGu29irXLF16oJ2JGDzJ4NCLRmXvxwK8h3nrh, status: 0 AddressBook getAll Subaddress getAll qml: check next false qml: >>> wallet opened: Wallet(0x7f74d02db2c0) qml: Recovering from seed: false qml: restore Height 0 qml: initializing with daemon address: localhost:18081 "initAsync: localhost:18081" init non async init async finished - starting refresh Checking connection status NEW STATUS Wallet::ConnectionStatus(ConnectionStatus_Disconnected) qml: Wallet connection status changed 0 refreshed sending external cmd: ("status") "Error: Couldn't connect to daemon: 127.0.0.1:18081\n" qml: >>> wallet refreshed qml: >>> wallet updated refreshed qml: >>> wallet refreshed Checking connection status qml: >>> wallet updated qml: Displaying processing splash " [] " "starting monerod /home/rysade/.local/monero/monerod" With command line arguments ("--detach", "--check-updates", "disabled") 2018-04-20 00:50:37.974 7f74e5d0b700 WARN net.dns src/common/dns_utils.cpp:508 WARNING: no two valid MoneroPulse DNS checkpoint records were received Checking for updates - done 2018-04-20 00:50:38.424 7fe1c522a740 INFO global src/daemon/main.cpp:280 Monero 'Lithium Luna' (v0.12.0.0-master-release) Forking to background... sending external cmd: ("status") "Error: Couldn't connect to daemon: 127.0.0.1:18081\n" daemon not running. checking again in 2 seconds. sending external cmd: ("status") "Height: 1554976/1554976 (100.0%) on mainnet, not mining, net hash 459.02 MH/s, v7, up to date, 0(out)+0(in) connections, uptime 0d 0h 0m 27s\n" daemon is started. Waiting 5 seconds to let daemon catch up qml: daemon started qml: Hiding processing splash Checking connection status NEW STATUS Wallet::ConnectionStatus(ConnectionStatus_Connected) qml: Wallet connection status changed 1 refreshed qml: >>> wallet refreshed qml: >>> wallet updated refreshed qml: >>> wallet refreshed Checking connection status qml: >>> wallet updated
GUI is showing 'Wallet is synchronized' and 'Daemon is synchronized (1554978)' and my balance is correct.

What was the issue? I am guessing it wasn't RPC if there was some kind of compiler snafu.

The last batch of binaries I may have neglected to fully test. I assumed we were only testing the GUI, and so swapped it out. This time, I copy-pasted the entire folder into my monero directory, replacing everything including monerod.

I'll try whatever you like if you're interested. I've always wanted to help out with an open source project, and Monero is one of my favorites.

@vitalisator
Copy link

@dEBRUYNE-1 , that works for me too now. Good work!

some debug output with private data Xed:
./start-gui.sh
app startd
available width: 1920
available height: 1048
devicePixelRatio: 1
screen height: 1920
screen width: 1080
screen logical dpi: 96.1263
screen Physical dpi: 141.951
screen calculated ratio: 1.10899
qml: check next false
qml: Checking seed
qml: check next false
qml: Checking seed
qml: check next false
qml: check next false
2018-04-20 06:05:05.783 7fe77fffd7c0 WARN net.http src/common/util.cpp:627 Failed to determine whether address '' is local, assuming not
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
qml: transfer page loaded
qml: PrivacyLevel changed:0
qml: mixin count: 6
qml: qrScannerEnabled disabled
qrc:/qt-project.org/imports/QtQuick/Controls/ApplicationWindow.qml:241:9: QML ContentItem: Binding loop detected for property "implicitWidth"
Checking for updates
qml: languages availible: 29
Checking for updates - done
qml: initializing..
setLanguage "de"
setLanguage: loading translation file 'monero-core_de' from '/home/me/Downloads/build (2)/release/bin/translations
setLanguage: translation for language 'de' loaded successfully
qml: transfer page loaded
qml: PrivacyLevel changed:0
qml: mixin count: 6
qml: opening wallet at: /home/me/Monero/wallets/wallet/wallet.keys , network type: mainnet
Wallet* WalletManager::openWallet(const QString&, const QString&, NetworkType::Type): opening wallet at /home/me/Monero/wallets/wallet/wallet.keys, nettype = 0
2018-04-20 06:05:23.725 7fe76ad51700 DEBUG device.ledger src/device/device_ledger.cpp:199 Device 0 Created
2018-04-20 06:05:23.725 7fe76ad51700 INFO wallet.wallet2 src/wallet/wallet2.cpp:5482 ringdb path set to /home/me/.shared-ringdb
2018-04-20 06:05:23.804 7fe76ad51700 WARN wallet.wallet2 src/wallet/wallet2.cpp:3718 Loaded wallet keys file, with public address: XXX
2018-04-20 06:05:23.811 7fe76ad51700 INFO wallet.wallet2 src/wallet/wallet2.cpp:3737 Trying to decrypt cache data
2018-04-20 06:05:23.900 7fe76ad51700 DEBUG wallet.wallet2 src/wallet/api/address_book.cpp:98 Refreshing addressbook
Wallet* WalletManager::openWallet(const QString&, const QString&, NetworkType::Type): opened wallet: XXX, status: 0
AddressBook
getAll
Subaddress
getAll
qml: check next false
qml: >>> wallet opened: Wallet(0x7fe75c529af0)
qml: Recovering from seed: false
qml: restore Height 0
2018-04-20 06:05:23.905 7fe77fffd7c0 DEBUG net.http src/common/util.cpp:641 Address 'localhost:18081' is local
qml: initializing with daemon address: localhost:18081
"initAsync: localhost:18081"
init non async
2018-04-20 06:05:23.905 7fe76ad51700 DEBUG net.http src/common/util.cpp:641 Address 'localhost:18081' is local
init async finished - starting refresh
Checking connection status
2018-04-20 06:05:23.920 7fe77fffd7c0 DEBUG WalletAPI src/wallet/api/wallet.cpp:1807 startRefresh: refresh started/resumed...
2018-04-20 06:05:23.921 7fe76ad51700 WARN net contrib/epee/include/net/net_helper.h:188 Some problems at connect, message: Verbindungsaufbau abgelehnt
NEW STATUS Wallet::ConnectionStatus(ConnectionStatus_Disconnected)
qml: Wallet connection status changed 0
2018-04-20 06:05:23.921 7fe768d4d700 WARN net contrib/epee/include/net/net_helper.h:188 Some problems at connect, message: Verbindungsaufbau abgelehnt
refreshed
2018-04-20 06:05:23.921 7fe77fffd7c0 DEBUG net.http src/common/util.cpp:647 Address 'xxx.xxx.xxx.xxx:18081' is not local
qml: >>> wallet refreshed
qml: >>> wallet updated
2018-04-20 06:05:33.922 7fe768d4d700 WARN net contrib/epee/include/net/net_helper.h:188 Some problems at connect, message: Verbindungsaufbau abgelehnt
refreshed
qml: >>> wallet refreshed
Checking connection status
2018-04-20 06:05:33.924 7fe76ad51700 WARN net contrib/epee/include/net/net_helper.h:188 Some problems at connect, message: Verbindungsaufbau abgelehnt
qml: >>> wallet updated
2018-04-20 06:05:43.923 7fe768d4d700 WARN net contrib/epee/include/net/net_helper.h:188 Some problems at connect, message: Verbindungsaufbau abgelehnt
refreshed
qml: >>> wallet refreshed
Checking connection status
2018-04-20 06:05:43.924 7fe76ad51700 WARN net contrib/epee/include/net/net_helper.h:188 Some problems at connect, message: Verbindungsaufbau abgelehnt
qml: >>> wallet updated
2018-04-20 06:05:53.924 7fe768d4d700 WARN net contrib/epee/include/net/net_helper.h:188 Some problems at connect, message: Verbindungsaufbau abgelehnt
refreshed
qml: >>> wallet refreshed
Checking connection status
2018-04-20 06:05:53.925 7fe76ad51700 WARN net contrib/epee/include/net/net_helper.h:188 Some problems at connect, message: Verbindungsaufbau abgelehnt
qml: >>> wallet updated
2018-04-20 06:06:03.925 7fe768d4d700 WARN net contrib/epee/include/net/net_helper.h:188 Some problems at connect, message: Verbindungsaufbau abgelehnt
refreshed
qml: >>> wallet refreshed
Checking connection status
2018-04-20 06:06:03.926 7fe76ad51700 WARN net contrib/epee/include/net/net_helper.h:188 Some problems at connect, message: Verbindungsaufbau abgelehnt
qml: >>> wallet updated
2018-04-20 06:06:09.975 7fe77fffd7c0 DEBUG WalletAPI src/wallet/api/wallet.cpp:1827 pauseRefresh: refresh paused...
qml: Displaying processing splash
" [] "
"starting monerod /home/me/Downloads/build (2)/release/bin/monerod"
With command line arguments ("--detach", "--check-updates", "disabled")
2018-04-20 06:06:11.014 7fc3d6f6c740 INFO global src/daemon/main.cpp:280 Monero 'Lithium Luna' (v0.12.0.0-master-release)
Forking to background...
sending external cmd: ("status")
"Height: 1547392/1547392 (100.0%) on mainnet, not mining, net hash 387.12 MH/s, v7, up to date, 0(out)+0(in) connections, uptime 0d 0h 0m 1s\n"
daemon is started. Waiting 5 seconds to let daemon catch up
qml: daemon started
qml: Hiding processing splash
Checking connection status
2018-04-20 06:06:18.270 7fe77fffd7c0 DEBUG WalletAPI src/wallet/api/wallet.cpp:1807 startRefresh: refresh started/resumed...
NEW STATUS Wallet::ConnectionStatus(ConnectionStatus_Connected)
qml: Wallet connection status changed 1
2018-04-20 06:06:18.285 7fe77fffd7c0 DEBUG cn src/cryptonote_basic/cryptonote_basic_impl.cpp:220 Invalid address format
2018-04-20 06:06:18.285 7fe77fffd7c0 DEBUG cn src/cryptonote_basic/cryptonote_basic_impl.cpp:220 Invalid address format
2018-04-20 06:06:18.290 7fe77fffd7c0 DEBUG net.http src/common/util.cpp:647 Address '192.168.77.15:18081' is not local
2018-04-20 06:06:33.446 7fe768d4d700 DEBUG net contrib/epee/include/net/net_helper.h:398 Problems at read: Vorgang abgebrochen
2018-04-20 06:06:33.446 7fe768d4d700 ERROR net.http contrib/epee/include/net/http_client.h:456 Unexpected recv fail
2018-04-20 06:06:33.447 7fe768d4d700 INFO net.http contrib/epee/include/storages/http_abstract_invoke.h:53 Failed to invoke http request to /json_rpc
2018-04-20 06:06:33.447 7fe768d4d700 ERROR WalletAPI src/wallet/api/wallet.cpp:893 daemonBlockChainTargetHeight: possibly lost connection to daemon
2018-04-20 06:06:33.447 7fe768d4d700 DEBUG net.http contrib/epee/include/net/http_client.h:365 Reconnecting...

@pedroaugustomontes
Copy link

I'm very frustrated with this wallet, I need my money but I can not access it, only get badcast issue :(

@sanderfoobar
Copy link
Contributor

@MrPMontes Try the CLI or wait for updates.

@badfiles
Copy link

It finally works, thank you.

@gagarin55
Copy link

same issue for me
Ubuntu 17.04

@el00ruobuob
Copy link
Contributor

@dEBRUYNE-1 https://build.getmonero.org/builders/monero-gui-ubuntu-amd64/builds/201 works perfectly!

@RemiMorin
Copy link

Works perfectly, Ubuntu 16 upgraded a while back, I look through the commit and can't figure out what's change? Is it only a change in the build environment?

@dEBRUYNE-1
Copy link
Contributor Author

@RemiMorin - It's merely a change in the build environment. If I recall correctly, upgrading boost from 1.58 to 1.59 resolved the bad_cast issue.

@PanderMusubi
Copy link

Build 201 fixes it for Ubuntu 17.10. If a new public release can be made, please. Also less tech-savvy users would like to use it.

@RemiMorin
Copy link

RemiMorin commented Apr 27, 2018

I agree that a new public build improve confidence and normalize the situation but you don't need to be tech-savvy.

Just go on the the 201 build page you will see a link directly to the build archive:
monero-gui-db5e71c-linux-amd64.tar.gz
https://build.getmonero.org/downloads/monero-gui-db5e71c-linux-amd64.tar.gz

inside this archive you will find the release folder. This folder content is the same as an official public release. Just allow execution of the start-gui script and you are done.

@DreadfulCode
Copy link

It's still an issue in 64 bit Linux. Just did a fresh install and this month-old bug is still happening. I can work around this but it takes a software guy like me to figure it out. Why is this still a problem?

@pmatulis
Copy link

The latest client is fatally broken even though the cause has been known for weeks. Why there has been no update is beyond me.

@grigio
Copy link
Contributor

grigio commented May 11, 2018

Please

@stoffu
Copy link
Contributor

stoffu commented May 12, 2018

This is a build-related problem which will be fixed in the next point release. Meanwhile, you can use an unofficial binary built by buildbot https://build.getmonero.org/builders/monero-gui-ubuntu-amd64/builds/201 as suggested above #1261 (comment).

@bananajamma
Copy link

bananajamma commented May 12, 2018

build 201 did not work for me... using the cli work-around

edit: build 201 did resolve the bad_cast issue for me, but the application appeared frozen due to window behavior, #1431

@sanderfoobar
Copy link
Contributor

@bananajamma Did you experience the bad_cast error on build 201? If it was something else, please open a new issue. If you did, please post OS details here.

@panupan
Copy link

panupan commented May 15, 2018

+1 happening on Ubuntu 16.04 LTS. Broken even after clean wipe of data dir and wallet. imo XMR is probably the most underrated coin out here... but it's issues like this that have caused its lackluster performance as of late.

@laudai
Copy link

laudai commented May 16, 2018

same problem on Ubuntu 16.04 +1

@Jaggfab
Copy link

Jaggfab commented Jun 5, 2018

Same problem here, Ubuntu 16.04.

@augustynr
Copy link

This still does not work, official website has old binary and the link from this thread is dead

@el00ruobuob
Copy link
Contributor

el00ruobuob commented Jun 8, 2018

This link? https://build.getmonero.org/builders/monero-gui-ubuntu-amd64/builds/201 looks ok IMO edit: no such resource on build file, it's indeed broken.

@augustynr
Copy link

augustynr commented Jun 8, 2018

Yep, Can I download it from anywhere?

@stoffu
Copy link
Contributor

stoffu commented Jun 8, 2018

This is the most recent build for the master which works for me: https://build.getmonero.org/builders/monero-gui-ubuntu-amd64/builds/472

@el00ruobuob
Copy link
Contributor

Thanks @stoffu!

@sanderfoobar
Copy link
Contributor

Alright, this one seems fixed now.

Unofficial release of 0.12.2: https://www.reddit.com/r/Monero/comments/8rkwyt/unofficial_release_of_gui_wallet_version_0122/

If you want the official releases, wait a bit.

+resolved

@dEBRUYNE-1
Copy link
Contributor Author

GUI v0.12.2.0, which includes a fix for this particular issue, has been released:

https://www.reddit.com/r/Monero/comments/8vkx2g/gui_v01220_released/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests