Finally it's completely synced!
Thanks for your help.
When is the new GUI is to be expected?

And why does it show "Not connected"?

On the Linux machine, there are obviously multiple problems:
> When starting the client appears again and again: "Crash Detected".
> If you select "Reset Database" the system freezes (remains frozen for hours).
> If you select "Continue Normally" the account shows unter "balance" false (old) values.
> At the bottom right is permanently displayed: "Not Connected".
> Always 100% CPU load.
> Top right following alert is permanently displayed: "JSON - Prase error: Property name must be a string literal [show details]"(This link does not work.)

Here comes the actual info result:
>> info

{
   "blockchain_head_block_num": 2150328,
   "blockchain_head_block_age": "19 weeks old",
   "blockchain_head_block_timestamp": "2015-03-29T19:28:40",
   "blockchain_head_block_id": "6b4ec2a3730e800f7554f356b8004b8873bc0148",
   "blockchain_average_delegate_participation": "0.01 %",
   "blockchain_share_supply": "2,505,332,930.65325 BTS",
   "blockchain_blocks_left_in_round": 63,
   "blockchain_next_round_time": "at least 10 minutes in the future",
   "blockchain_next_round_timestamp": "2015-08-08T05:12:30",
   "blockchain_random_seed": "5f969b30b7b00e9a438b9c97e2c1b4eb7b508217",
   "client_data_dir": "/home/armin/.BitShares",
   "client_version": "0.9.2",
   "network_num_connections": 11,
   "network_num_connections_max": 200,
   "network_chain_downloader_running": false,
   "network_chain_downloader_blocks_remaining": null,
   "ntp_time": "2015-08-08T05:02:03",
   "ntp_time_error": -0,
   040773999999999998,
   "wallet_open": true,
   "wallet_unlocked": true,
   "wallet_unlocked_until": "12 days in the future",
   "wallet_unlocked_until_timestamp": "2015-08-19T18:45:13",
   "wallet_last_scanned_block_timestamp": "2015-01-20T18:57:10",
   "wallet_scan_progress": "100.00 %",
   "wallet_block_production_enabled": false,
   "wallet_next_block_production_time": null,
   "wallet_next_block_production_timestamp": null }

No, no firewall on this linux-machine.

Here is the info result:

>> info

{
   "blockchain_head_block_num": 398872,
   "blockchain_head_block_age": "48 weeks old",
   "blockchain_head_block_timestamp": "2014-09-04T15:32:10",
   "blockchain_head_block_id": "0d9ebf2fcc1f8fd66b174796ee9ce93902533738",
   "blockchain_average_delegate_participation": "0.00 %",
   "blockchain_share_supply": "2,498,911,649.25664 BTS",
   "blockchain_blocks_left_in_round": 78,
   "blockchain_next_round_time": "at least 13 minutes in the future",
   "blockchain_next_round_timestamp": "2015-08-07T13:20:50",
   "blockchain_random_seed": "ae6a0dd9a4c06dd26e3f7b32bef7ebc300a66c1a",
   "client_data_dir": "/home/armin/.BitShares",
   "client_version": "0.9.2",
   "network_num_connections": 19,
   "network_num_connections_max": 200,
   "network_chain_downloader_running": false,
   "network_chain_downloader_blocks_remaining": null,
   "ntp_time": "2015-08-07T13:07:53",
   "ntp_time_error": 0,
   276283,
   "wallet_open": true,
   "wallet_unlocked": true,
   "wallet_unlocked_until": "12 days in the future",
   "wallet_unlocked_until_timestamp": "2015-08-19T02:40:00",
   "wallet_last_scanned_block_timestamp": null,
   "wallet_scan_progress": "100.00 %",
   "wallet_block_production_enabled": false,
   "wallet_next_block_production_time": null,
   "wallet_next_block_production_timestamp": null }

Sorry, but on a Linux-Machine (MInt 17.1) I have still (even with BitShares 0.9.2) the same problem: It's not connecting.
What can I do, to solve this problem too?

Thanks for your help! Sync does work again.

My client shows under >File >Check for Updates:
"No new updates available."
Where can I download the new version?
Uninstall 0.8.0 before installing the new version?

> bitshare client 0.8.0 doesn't sync anymore
> shows always "Not connected", even when firewall is deactivated
> doesn't shoe my BitGOLD.BTS and BitSILVER.BTS (only my BTS)
> before, sync process stoped always at 2379149 blocs
What can I do? Pls help!

As I have now found the problem is quite different:
After starting a new installation, the CPU usage (sync process) is so high (too high!), that after entering the password, the client window can not be opened (for hours!).
This occurs reproducibly on Windows and Linux.
This behavior of the client is not acceptable for the time after the beta version.

Quote

How can I import .json without starting the client?

Okay Guys, whatever the reasons for the current poor GUI/usability may be, the fact is, who wants to enter the mass market, needs an excellent interface! Hurry up!

GUI design and usability are very poor!
For beta testing perhaps sufficient; absolutely not for the mass market.
A few top people for GUI design should lend a hand!
Take a look at https://bitreserve.org/dashboard to see the difference.
When can we expect a GUI 2.0 for Bitshare?

Client 0.8.0 does not start.
After entering the password, the program locks up.
Reproducible.
Deinstallation/Reinstallation did not help.
Windows 8.1 up-to-date, Firewall switch off.
What can I do in order to see my account?

Hello,

I think this might be of interest for you:

Yesterday afternoon (CET) we have made a test transfer of 0.1 BTC via BlockTrades*) for exchange in BTS and to credit our account "armin39" at BitShares. It took over 20 hours until that amount was credited to the account.

A similar test transfer via Metaexchange was done in less than half an hour.

*) The email address '[email protected]' shown on the BlockTrades website does not work!

Best regards,
armilo

This was the answer from bter.com:
"Dear armilo,
Please try to send it to the account, not theaccount key.
For example, if you have a registered account lily with the key 123455.
Please try to send asset to lily rather than the account key 12345.
When you are trying to send BTS to bter, please also send to the account btercom instead of BTSX567mPAbaXvB932Ky2c7tNkswP92dyFDkf8s2cfRFbzC2VfgMzf
Best Regards
Bter.com"
This sounds strange, but it works!
No idea why the public key for transfers from bter.com to bitshares.org does not work ...