Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - davidpbrown

Pages: 1 ... 33 34 35 36 37 38 39 [40] 41 42 43 44 45 46
586
General Discussion / Re: Get 2$ Easily by Helping BitShares! Support our Thunderclap Campaign!!
« on: August 28, 2014, 09:49:10 pm »
Ok.. so, I couldn't resist the idea of getting my first 2 bitUSD, though it's less clear how that is sent to those signed up. So, I'll suggest here throw your assets at BitShareX://davidpbrown

587
General Discussion / Re: Register account issue
« on: August 28, 2014, 07:30:22 pm »
That could open up a spamming option for those without BitShares best interests at heart. Delegates want their payment and it's nice to be nice and to have users engage with the community too.

588
General Discussion / Re: HEY, BM ,this is btc38's announcement ,what's the ploblem with 0.4.9a ?
« on: August 28, 2014, 07:19:44 pm »
Google translator add-on makes it one right click away.

Quote
"Dear user, our server ongoing btsx hard forked version upgrade, but we found a little problem the latest 0.4.9 version, temporarily unable to open elution, and btsx official feedback we have this problem is solved them, please Wait"

No surprises then.

589
Technical Support / Re: bitshareX client 0.4.8 crashes on mac osx 10.9.4
« on: August 27, 2014, 08:07:06 pm »
Quote from: xeroc on August 27, 2014, 07:20:21 pm
try this for downloading the blockchain:
https://github.com/BitShares/bitshares_toolkit/wiki/Using-Chain-Servers#using-a-chain-server-to-sync-with-bitshares-x

also at least "OPEN" a wallet .. (not necessarily unlock it, .. just open it)

That help?

Just to suggest for now that adding the chain servers as suggested and the opting for refresh database, had the splash screen for 10mins before that disappeared; the client appeared about 10mins after that; and 10mins laters I'm looking at the wallet open without my doing anything about that but not yet connected - harddrive is grinding away as if it's making some sort of progress and I hope to come back in a while and see it's reconnected to the usual p2p and updating. So far, so good..

590
Technical Support / Re: bitshareX client 0.4.8 crashes on mac osx 10.9.4
« on: August 27, 2014, 06:47:10 pm »
Relatively clean Linux Mint 17 old laptop but it complied ok. 0.4.7 worked fine. It's just 0.4.8 that falls over within ~10mins of downloading the blockchain, regardless of whether it's a clean new wallet or the old one.

I've got log files which are peppered with Bad file descriptors and alsorts.. but not sure what to make of those. Sample of the end of p2p.log below from line 17523. I don't know, if the last line is useful..

Code: [Select]
20140827T180823.861167  bitshares      execute_markets ] execute markets [] chain_database.cpp:766
20140827T180824.052536  bitshares on_closing_connectio ] Peer 95.85.52.135:49550 is disconnecting us because: I rejected your connection request (hello message) so I'm disconnecting node.cpp:2296
20140827T180824.453273  bitshares terminate_inactive_c ] Forcibly disconnecting from handshaking peer 23.239.5.30:1776 due to inactivity of at least 5 seconds node.cpp:1089
20140827T180824.453407  bitshares terminate_inactive_c ] Peer's negotiating status: hello_sent, bytes sent: 0, bytes received: 0 node.cpp:1093
20140827T180824.453485  bitshares terminate_inactive_c ] Forcibly disconnecting from handshaking peer 121.40.126.75:46136 due to inactivity of at least 5 seconds node.cpp:1089
20140827T180824.453533  bitshares terminate_inactive_c ] Peer's negotiating status: connecting, bytes sent: 0, bytes received: 0 node.cpp:1093
20140827T180824.453606  bitshares terminate_inactive_c ] Forcibly disconnecting from handshaking peer 95.85.33.16:8764 due to inactivity of at least 5 seconds node.cpp:1089
20140827T180824.453653  bitshares terminate_inactive_c ] Peer's negotiating status: connecting, bytes sent: 0, bytes received: 0 node.cpp:1093
20140827T180824.453726  bitshares terminate_inactive_c ] Forcibly disconnecting from handshaking peer 106.185.26.162:1776 due to inactivity of at least 5 seconds node.cpp:1089
20140827T180824.453772  bitshares terminate_inactive_c ] Peer's negotiating status: connecting, bytes sent: 0, bytes received: 0 node.cpp:1093
20140827T180824.453843  bitshares terminate_inactive_c ] Forcibly disconnecting from handshaking peer 178.79.148.143:1776 due to inactivity of at least 5 seconds node.cpp:1089
20140827T180824.453890  bitshares terminate_inactive_c ] Peer's negotiating status: connecting, bytes sent: 0, bytes received: 0 node.cpp:1093
20140827T180824.459469  bitshares rebroadcast_pending_ ] skip rebroadcast_pending while syncing client.cpp:1028
20140827T180824.745374  bitshares            read_loop ] disconnected 0 exception: unspecified
Bad file descriptor
    {"message":"Bad file descriptor"}
    asio  asio.cpp:28 read_write_handler

    {"len":16}
    bitshares  stcp_socket.cpp:72 readsome message_oriented_connection.cpp:195
20140827T180824.765168  bitshares send_queued_messages ] Error sending message: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":28,"method":"read_write_handler","hostname":"","thread_name":"asio","timestamp":"20140827T180824.764855"},"format":"${message} ","data":{"message":"Bad file descriptor"}},{"context":{"level":"warn","file":"stcp_socket.cpp","line":95,"method":"writesome","hostname":"","thread_name":"bitshares","timestamp":"20140827T180824.764922"},"format":"","data":{"len":400}},{"context":{"level":"warn","file":"message_oriented_connection.cpp","line":235,"method":"send_message","hostname":"","thread_name":"bitshares","timestamp":"20140827T180824.764967"},"format":"unable to send message","data":{}}]}.  Closing connection. peer_connection.cpp:199
20140827T180824.804430  bitshares           connect_to ] fatal: error connecting to peer 178.79.148.143:1776: 9 canceled_exception: Canceled
Operation cancelled
    {"message":"Operation cancelled"}
    asio  asio.cpp:17 read_write_handler peer_connection.cpp:169
20140827T180824.804814  bitshares           connect_to ] fatal: error connecting to peer 121.40.126.75:46136: 9 canceled_exception: Canceled
Operation cancelled
    {"message":"Operation cancelled"}
    asio  asio.cpp:17 read_write_handler peer_connection.cpp:169
20140827T180824.805509  bitshares            read_loop ] disconnected 0 exception: unspecified
Bad file descriptor
    {"message":"Bad file descriptor"}
    asio  asio.cpp:28 read_write_handler

    {"len":16}
    bitshares  stcp_socket.cpp:72 readsome message_oriented_connection.cpp:195
20140827T180824.808809  bitshares           connect_to ] fatal: error connecting to peer 106.185.26.162:1776: 0 exception: unspecified
Bad file descriptor
    {"message":"Bad file descriptor"}
    asio  asio.cpp:28 read_write_handler peer_connection.cpp:169
20140827T180824.809665  bitshares            read_loop ] disconnected 0 exception: unspecified
Bad file descriptor
    {"message":"Bad file descriptor"}
    asio  asio.cpp:28 read_write_handler

    {"len":16}
    bitshares  stcp_socket.cpp:72 readsome message_oriented_connection.cpp:195
20140827T180825.156033  bitshares            read_loop ] disconnected 11 eof_exception: End Of File
End of file
    {"message":"End of file"}
    asio  asio.cpp:22 read_write_handler

    {"len":16}
    bitshares  stcp_socket.cpp:72 readsome message_oriented_connection.cpp:190
20140827T180825.794035  bitshares on_closing_connectio ] Peer 207.12.89.119:1700 is disconnecting us because: I rejected your connection request (hello message) so I'm disconnecting node.cpp:2296
20140827T180825.794419  bitshares            read_loop ] disconnected 0 exception: unspecified
Bad file descriptor
    {"message":"Bad file descriptor"}
    asio  asio.cpp:28 read_write_handler

    {"len":16}
    bitshares  stcp_socket.cpp:72 readsome message_oriented_connection.cpp:195
20140827T180825.838812  bitshares send_queued_messages ] Error sending message: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":28,"method":"read_write_handler","hostname":"","thread_name":"asio","timestamp":"20140827T180825.838464"},"format":"${message} ","data":{"message":"Bad file descriptor"}},{"context":{"level":"warn","file":"stcp_socket.cpp","line":95,"method":"writesome","hostname":"","thread_name":"bitshares","timestamp":"20140827T180825.838547"},"format":"","data":{"len":96}},{"context":{"level":"warn","file":"message_oriented_connection.cpp","line":235,"method":"send_message","hostname":"","thread_name":"bitshares","timestamp":"20140827T180825.838588"},"format":"unable to send message","data":{}}]}.  Closing connection. peer_connection.cpp:199
20140827T180825.997473  bitshares ~message_oriented_co ] Exception thrown while canceling message_oriented_connection's read_loop, ignoring: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"error","file":"asio.cpp","line":28,"method":"read_write_handler","hostname":"","thread_name":"asio","timestamp":"20140827T180818.745864"},"format":"${message} ","data":{"message":"Bad file descriptor"}},{"context":{"level":"warn","file":"stcp_socket.cpp","line":72,"method":"readsome","hostname":"","thread_name":"bitshares","timestamp":"20140827T180818.745956"},"format":"","data":{"len":16}},{"context":{"level":"warn","file":"message_oriented_connection.cpp","line":198,"method":"read_loop","hostname":"","thread_name":"bitshares","timestamp":"20140827T180818.746171"},"format":"disconnected ${e}","data":{"e":"0 exception: unspecified\nBad file descriptor \n    {\"message\":\"Bad file descriptor\"}\n    asio  asio.cpp:28 read_write_handler\n\n    {\"len\":16}\n    bitshares  stcp_socket.cpp:72 readsome"}}]}

591
Technical Support / Re: bitshareX client 0.4.8 crashes on mac osx 10.9.4
« on: August 27, 2014, 05:30:27 pm »
I get Segmentation Fault on Linux.. without any of the detailed error above.

Happy to provide logs or whatever other detail might be useful.. unclear atm which log is useful for fixing this.

592
General Discussion / Re: client opened without password
« on: August 26, 2014, 03:17:36 pm »
It's either meant to do one approach or the other. If it's BTC like and open until action, then do that; otherwise ensure that client is locked and doesn't just appear to be most of the time. I don't mind either approach, although I think there's advantage having confirmation of password at the moment of action rather than having it open and with risk for a preferred amount of time. If it's open and available to action, then the user needs to use other screenlocks to secure the client's capability, which perhaps is odd.

593
General Discussion / Re: client opened without password
« on: August 26, 2014, 11:38:20 am »
I had that in the previous version too but if you try to do anything it does jump to the unlock screen. Still it shouldn't happen, as there might be detail visible that properly should be locked from view.

594
General Discussion / Re: Register account issue
« on: August 25, 2014, 08:17:15 pm »
I expect that if it's not registered and on the blockchain, then it's not visible. So, you can send to an unregistered account by putting the account key to a new contact in your address book and sending to the contact name.

595
General Discussion / Re: Register account issue
« on: August 25, 2014, 08:01:22 pm »
Could you not just send him 1 BTSX?.. add their account key as a contact and send to whatever name you gave it.

596
Technical Support / Re: is everyone syncing ok?
« on: August 25, 2014, 09:17:36 am »
I had it seem to stall on three or four occasions but wasn't clear if that was my old hardware struggling to keep up. Restarting the client without any refresh of the database, seemed to help kick the sync back to life.

The subject here has me reminded of the Berlitz German Coastguard :)

597
LottoShares / Importing keys/wallet -> signed statement?
« on: August 24, 2014, 05:53:19 pm »
Just trying to get my head around LottoShares and it seems odd to suggest we all must create new wallets and addresses and transfer existing balance then import the wallet.. just to prove that we are the address owner in claiming Lottoshares and others?.. Would it not be easier to use a signed confirmation and not disrupt everyones existing addresses? I recognise that might be complex but it's surely within the bounds of what is possible from the user side.. unless those wallets are more limited that ye olde BTC wallets.

I don't know, if this is an option for AGS holders even, rather than trusting thirdparty code.

598
General Discussion / Re: Status of BTSX?
« on: August 24, 2014, 12:09:17 pm »
Quote from: xeroc on August 24, 2014, 08:56:07 am
Maybe you can help out? Interessted in setting a ppa up? Is it difficult?

A quick look suggests it's a relatively simple two step process but is beyond my experience and resources here; if I had another PC spare, I'd be tempted to try. Also, it's important that any PPA is from a trusted source rather than a random user, as any user could tweak the source before upload creating a bad version.

1. create a .deb package
- Build .deb package http://packaging.ubuntu.com/html/packaging-new-software.html

2. upload it to Launchpad; Launchpad then will build the binaries.
Create a ppa repository http://developer.ubuntu.com/publish/apps/other-forms-of-submitting-apps/ppa/

Once the ppa exists it's just a case of advertising it. I expect there is another step to have it in the usual third party indexes but the PPA is all that's needed initially for people to add to their software sources.

599
General Discussion / Re: Status of BTSX?
« on: August 24, 2014, 07:36:12 am »
Thanks xeroc.

Those instructions work but have a few corrections:

:Downloading the Sources
Should suggest
> cd bitsharesx
NOT cd bitshares_toolkit

:GUI:: Configuration and Compilation
error suggesting a folder that doesn't exist: cd bitshares-toolkit
just ignore that cd and continue on in the bitsharesx folder


Also, although I didn't do it:
System-wide Installation (optional)
> sudo cp programs/qt_wallet/BitSharesX /usr/local/bin/
should be
> sudo cp programs/qt_wallet/bin/BitSharesX /usr/local/bin/

To help readability, it would useful to include an #anchor jump from the end of what is Debian/Ubuntu and ArchLinux over the OSX instructions as the subheading might appear to also be needed for Linux.

The Debian/Ubuntu dependancies suggested are likely correct but I note that on the previous attempt installing just the toolkit I also did this following puppies suggestion:
> sudo apt-get install qt5-default libqt5webkit5-dev npm nodejs-legacy

With only 0.5GB RAM the Core takes ~11hrs and the GUI ~1hr to compile. Having an official BitShares ppa:: repository would be a great next step.

600
General Discussion / Re: If you need BTSX to finish the registration, Just post your account key here
« on: August 24, 2014, 07:32:51 am »
BTSX5dEQn3G94zUPMfYDe9veJhtKGXrNK2Ph2AfiXwLhQb5MtwQLCc
Thanks

Pages: 1 ... 33 34 35 36 37 38 39 [40] 41 42 43 44 45 46

Page created in 0.025 seconds with 23 queries.