QT wallet on Ubuntu is so buggy it is unusable

Started by gabes, January 18, 2015, 12:06:18 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Thom

Quote from: btcxyzzz on February 16, 2015, 02:48:37 PM
Seems like the restart of system was required... Now it seems QT client is working, so I may confirm United Kindom in is required setting in Locale>Country in Kubuntu 14.04.

BTW, seems like newest client does not have access to Bitshares console like it used to?

The console is found under the account / advanced menu now.
Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: [url="https://bitsharestalk.org/index.php/topic,23902.0.html"]https://bitsharestalk.org/index.php/topic,23902.0.html[/url]

btcxyzzz

No... It's not starting again (don't know how it started that one time after reset). Even deleting config.json file does not help like it used to

btcxyzzz

Quote from: gabes on February 16, 2015, 01:21:12 PM
Quote from: btcxyzzz on February 16, 2015, 11:52:59 AM
Tried United Kingdom setting - doesn't work. Really don't know what to try next...

Try to describe your problem first. ;)
How it behaves?
Which version you are using?
Does it start correctly at least?

Seems like the restart of system was required... Now it seems QT client is working, so I may confirm United Kindom in is required setting in Locale>Country in Kubuntu 14.04.

BTW, seems like newest client does not have access to Bitshares console like it used to?

maqifrnswa

FYI, ubuntu fixed the bug that put the bitshares app icon in the top left of the screen. It won't be fixed until the next release (april), however:
https://bugs.launchpad.net/sni-qt/+bug/1209106
maintains an Ubuntu PPA: [url="https://launchpad.net/~showard314/+archive/ubuntu/bitshares"]https://launchpad.net/~showard314/+archive/ubuntu/bitshares[/url] [15% delegate] wallet_account_set_approval maqifrnswa true [50% delegate] wallet_account_set_approval delegate1.maqifrnswa true

gabes

Quote from: btcxyzzz on February 16, 2015, 11:52:59 AM
Tried United Kingdom setting - doesn't work. Really don't know what to try next...

Try to describe your problem first. ;)
How it behaves?
Which version you are using?
Does it start correctly at least?

btcxyzzz

Tried United Kingdom setting - doesn't work. Really don't know what to try next...

gabes

Quote from: btcxyzzz on February 15, 2015, 05:07:18 PM
Using Kubuntu 14.04, my Country: setting is "System Country (United States Of America)", I guess this needs to be changed, but to what?

If you do not encounter any problems you should be fine with your settings. Also Kubuntu has QT based frontend (KDE). I think QT based apps could be integrated better compared to Ubuntu.

btcxyzzz

Using Kubuntu 14.04, my Country: setting is "System Country (United States Of America)", I guess this needs to be changed, but to what?

gabes

I just tested the newest 0.6.1 client on Ubuntu. It still doesn't work correctly on a non-english systems.
Quick workaround is to switch regional settings to english, but it is rather unconvenient and causes input problems in other localized applications.
I was told by vikram there is no technical support for QT related bugs on linux. Anyway I leave here this bug report if someone from the community willing to inspect this.

Bitshares on Ubuntu

regional settings - slovak
(bottom bar, json parsing errors, empty market)
http://pastebin.com/J050FauJ
http://pastebin.com/f2xE0Spd
http://imgur.com/a/EDmQY

regional settings - english
(works perfect)
http://pastebin.com/KMg4MtiM
http://pastebin.com/5kh3ALx8
http://imgur.com/a/Pc03T

gabes

#6
So after tinkering a bit with Bitshares on Ubuntu I finally found out what causes the "corrupted config.json" bug.
It is the "Regional formats" in System settings -> Language support.
Some languages uses comma instead of period as a decimal point.
And this breaks the json parsing after running the app. (GUI only, command line versioin not affected)
This is supposed to affect many foreign users, so I hope the devs will treat this somehow.

Edit: After this, the app runs really good as I can tell.  :)

gabes

#5
Never mind! I just found the "web_wallet" option.
Actually it works pretty well, including the market and also the network status bar.

xeroc

are you sure you are running the correct binary? what's the "last modify date" of the binary/executable?
have you tried removing the "chains" folder in "~/.BitShares" ?

vikram

Quote from: gabes on January 18, 2015, 12:06:18 PM

I hope you guys will ironing out these glitches and will make the Qt client usable on linux.
I will follow the progress and will check the updates on a regular basis from an end user perspective.

Currently we do not provide support for Linux QT client.

deprdoo

Interesting. I have no problems in Ubuntu at all.

gabes

Hi I am new to bitshares, and wanna share my experience. I just tried the latest client 0.5 on Ubuntu 14.04 amd64.
First I downloaded the binaries from Scotts PPA. Later a built the client from sources on github. In both cases everything looks identical including bugs.
* I have to say the command line version works perfectly, without any glitch.

The GUI (Qt) version is unusable. I try to describe how it functions.
* After running the app, tens of JSON parse errors appears in notification and counting. The "show details" link doesn't work.
* There is a "Not connected" network status in the footer.
* There is a big red warning on the asset page: "Cannot get market status. Probably no orders have been placed." and the app doesn't show my asset balance.
(I didn't figured out how to check assets balance in cmd client)

* And now the interesting part:
After quiting the app it fails to run again. It also deletes the downloaded blockchain! I did a quick inspect and find out this:
Right after first run, the app immediately corrupts the config.json file. Notice the period replaced by comma at the end of file.

Normal config.json

"wallet_callback_url": "",
  "client_debug_name": "",
  "growl_notify_endpoint": null,
  "growl_password": null,
  "growl_bitshares_client_identifier": null,
  "relay_fee": 0.10000000000000001,
  "light_relay_fee": 0.10000000000000001,
  "relay_account_name": "",
  "faucet_account_name": "",
  "track_statistics": true
}


Corrupted config.json

"wallet_callback_url": "",
  "client_debug_name": "",
  "growl_notify_endpoint": null,
  "growl_password": null,
  "growl_bitshares_client_identifier": null,
  "relay_fee": 0,
  10000000000000001,
  "light_relay_fee": 0,
  10000000000000001,
  "relay_account_name": "",
  "faucet_account_name": "",
  "track_statistics": true
}


I hope you guys will ironing out these glitches and will make the Qt client usable on linux.
I will follow the progress and will check the updates on a regular basis from an end user perspective.