iotaledger / legacy-wallet-use-trinity-wallet-instead

IOTA Wallet

IOTA App

WARNING: This wallet is now deprecated. Please use https://github.com/iotaledger/trinity-wallet instead.

Prerequisites

1. Download NodeJS

2. Install Electron:

npm install -g electron

3. Install Bower:

npm install -g bower

Windows Users Only

Run the following command as Administrator:

npm install -g --production windows-build-tools

Compiling

If you wish to compile the app, install the following also:

1. Install Electron Builder

Electron Builder is used behind the scenes. Read their instructions on how to set up your system.

2. Install Docker

Instructions

1. Clone this repository:

git clone https://github.com/iotaledger/wallet

2. Go to the wallet directory:

cd wallet

3. Clone iri:

git clone https://github.com/iotaledger/iri

Note: make sure compiled iri.jar is in the iri folder.

4. Install components

npm install

5. Run the app:

npm start

6. If you wish to compile the app:

npm run compile

If you'd like to create a package only for a specific OS, you can do so like this:

npm run compile:win
npm run compile:mac
npm run compile:lin

Compiled binaries are found in the out directory.

Testnet

To build testnet binaries, rename package.testnet.json to package.json and follow instructions as above. Make sure the jar is named iri-testnet.jar.

legacy-wallet-use-trinity-wallet-instead's Issues

Issue While SettingUp Project

Hi,

I have followed each and every step in Wallet and IRI project.

After all the node setups and maven setups,finally I am able to run the program.

While I run it in browser (localhost:14265://), I got one JSON with "{Duration : Randomno(1) }".

Can you please guide how to use this program.In CMD screen it shows some null pointer exception,too. ?

If you can let me know that what should be desired output then it would be really helpful
Thanks
Parth Kansara

Bug display!!

sometime when i sent iota (confirmed) or generate adress (confirmed) statut not change i have statut "pending", i need restart iota for look my statut change!!

Error when stopping Spamming. Wallet version 2.2.1

$.fn.loadingReset: Spam the Network
ui.spam.js:27 OK loading reset was called
iota.js:3895 Uncaught TypeError: callback is not a function
at makeRequest.prepareResult (iota.js:3895)
at exports.XMLHttpRequest.request.onreadystatechange (iota.js:3767)
at exports.XMLHttpRequest.dispatchEvent (iota.js:17602)
at setState (iota.js:17621)
at exports.IncomingMessage. (iota.js:17458)
at exports.IncomingMessage.EventEmitter.emit (iota.js:12084)
at endReadableNT (iota.js:14445)
at afterTickTwo (iota.js:12494)
at Item.run (iota.js:12666)
at drainQueue (iota.js:12636)
ui.spam.js:66 Stopped spamming

Only minor as spamming does stop and the wallet remains functional.

Status Bar improvment

Maybe it is possible to let the gui have acess to botbox values.. So everbody nows the latest milestone and we can write in status bar myActuelMilestone / coordinatorMilestone or as option as precent..

minWeightMagnitude input from user

GUI Spammer 1948 Bug

Not really a wallet issue, but related to atypical's GUI, but I think we can consider it under this scope :-)

The Network Spammer function always stops working when it hits 1948 tx
This as happen every time I run the spammer, with either version 1.0.4 or 1.0.5 (can't remember if it happened in the previous version)
It simply stays stuck in getting tips, no matter how much time goes by.

Tested and verified in Windows Server 2012 R2, Java 64 bit 1.8 build 101, running in a VM with an Hyper-V environment

claiming gives error

I am trying to claim IOTAs which I never had a chance to claim (missed first process). When I enter old and new seed (twice) after a while I have Invalid Input error message.

General FAQ-related (not a wallet issue per se): is there a plan to integrate Google Doc FAQs into iota.readme.io?

Main FAQ:
https://docs.google.com/document/d/1IVhPOpgS-UbX3T9iPYWjhPFBKZpOzYKwBBAE8ROBpxo

Additionaly there are:
https://docs.google.com/document/d/18wdKGHVUWvA84uEsvJ9pMnwFo7L84L8BnJlLT0Ye9o4
https://docs.google.com/document/d/1Hazmuv9P_9c_Vj7HLc1aBkPhvm5JGHKSgMY2LWuZJds

General FAQ-related (not a wallet issue per se): every address has a timestamp (by looking at JSON on tangle.guru), are those timestamps somehow validated?

interrruptAttachingTangle

If i wait while address attachedToTangle and you call interruptAttachingToTangle the wallet show that the address ist successful attached but it isn't.

Wallet v2.2.0 is unuseable

Mac OSx Sierra.

ccurl-interface.js:67 Uncaught TypeError: Cannot read property 'isHash' of undefined
    at Object.ccurlHashing (/Applications/IOTA Wallet.app/Contents/Resources/app.asar/app/js/ccurl-interface.js:67:20)
    at api.iota.api.attachToTangle (eval at globalEval (file:///Applications/IOTA%20Wallet.app/Contents/Resources/ui/bower_components/jquery/dist/jquery.min.js:1:1), <anonymous>:4:11)
    at file:///Applications/IOTA%20Wallet.app/Contents/Resources/ui/bower_components/iota.lib.js/dist/iota.js:679:14
    at file:///Applications/IOTA%20Wallet.app/Contents/Resources/ui/bower_components/iota.lib.js/dist/iota.js:434:20
    at file:///Applications/IOTA%20Wallet.app/Contents/Resources/ui/bower_components/iota.lib.js/dist/iota.js:38:20
    at makeRequest.prepareResult (file:///Applications/IOTA%20Wallet.app/Contents/Resources/ui/bower_components/iota.lib.js/dist/iota.js:3679:10)
    at exports.XMLHttpRequest.request.onreadystatechange (file:///Applications/IOTA%20Wallet.app/Contents/Resources/ui/bower_components/iota.lib.js/dist/iota.js:3636:23)
    at exports.XMLHttpRequest.dispatchEvent (file:///Applications/IOTA%20Wallet.app/Contents/Resources/ui/bower_components/iota.lib.js/dist/iota.js:17038:25)
    at setState (file:///Applications/IOTA%20Wallet.app/Contents/Resources/ui/bower_components/iota.lib.js/dist/iota.js:17057:14)
    at exports.IncomingMessage.<anonymous> (file:///Applications/IOTA%20Wallet.app/Contents/Resources/ui/bower_components/iota.lib.js/dist/iota.js:16894:13)
@ ccurl-interface.js:67iota.api.attachToTangle 
@ VM124:4(anonymous function) 
@ iota.js:679(anonymous function) 
@ iota.js:434(anonymous function) 
@ iota.js:38makeRequest.prepareResult 
@ iota.js:3679request.onreadystatechange 
@ iota.js:3636dispatchEvent 
@ iota.js:17038setState 
@ iota.js:17057(anonymous function) 
@ iota.js:16894EventEmitter.emit 
@ iota.js:11593endReadableNT 
@ iota.js:13933afterTickTwo 
@ iota.js:11986Item.run 
@ iota.js:12158drainQueue 
@ iota.js:12128

Windows 7 64Bit Java Loop

I have a brand new install of Windows 7 Ultimate 64 bit.

When i downloaded the official GUI install.exe it found that i dont have java installed.

I clicked next to download java.

Java pops up, i click install but that is the end of the java prompts.

After a while iota prompts to say that i dont have java installed. Then i go through the same process without ever fully installing java.

I installed the java manually and that corrected the issue.

Adding of Neighbors doesn't require restart

When a user adds a new neighbor, instead of restarting the GUI, it should use the addNeighbors (https://iota.readme.io/docs/addneighors) API call and store the new neighbors information in settings.json (as it did previously).

This way we don't need to restart the GUI, the connection to the neighbor still gets established and on the next restart the neighbor will be automatically loaded as a startup parameter to IRI.

Bug Hours and Balance

when i sent IOTA, my balance et not correct and Hours also, i have logout, login and restart IOTA and i have same problem!!

IOTA Wallet.dmg Connection Refused

When I start the wallet v.2.0.0 on my mac, I can generate a seed, however cannot login. It displays "connection refused".

possibility to choose database location

The possibility to choose the database location would be useful. e.g. for people whose $HOME is on a SSD disk and wants the database to be elsewhere in order to avoid lot of writing operations on the SSD.

Feature Req: Stop Spam button

500 internal server error

I got this error while spamming with v2.2.1-testnet release on WIndows 10.

Failed to load resource: the server responded with a status of 500 (Internal Server Error)

General FAQ-related questions (not a wallet issue per se)

Every address has a timestamp (by looking at JSON on tangle.guru), are those timestamps somehow validated?

What are the limits in sending and receiving IOTA?
(Here we can mention stuff like capped number of IOTAs per address, guidelines regarding maximum amount of sends from a given address, etc.)

What actions are unsafe to do while unsynced?

How do I know I'm synced?

What does a coordinator do?

Why does my 1.0.3. client generate a 90-character address while tangle.guru shows 81-character truncated version of this same address?

Is there a plan to integrate Google Doc FAQs into iota.readme.io?
(Main FAQ:
https://docs.google.com/document/d/1IVhPOpgS-UbX3T9iPYWjhPFBKZpOzYKwBBAE8ROBpxo
Additionaly there are:
https://docs.google.com/document/d/18wdKGHVUWvA84uEsvJ9pMnwFo7L84L8BnJlLT0Ye9o4
https://docs.google.com/document/d/1Hazmuv9P_9c_Vj7HLc1aBkPhvm5JGHKSgMY2LWuZJds)

Verify downloads

Where can I find the hashes and signatures to verify the download?

Unable to scan qr code unknown / unsupported format

Either it did not contain a qr code, or did not contain one in a supported format, or the software was simply unable to find it.

General FAQ-related (not a wallet issue per se): what actions are unsafe to do while unsynced?

Displaying the balance after the post-snapshot or coin claim

I wonder if the GUI client can automatically display the balance after users first open the post-snapshot wallet or claim their coins. For instance, the wallet can automatically re-generate the necessary addresses to display the total balance for the users when the users are doing those two actions.

For now, after users claim, they don't see the balance in their wallet before manually generating some addresses. Same for using the post-snapshot wallet. For instance, if a user has 100 addresses in his account, after the snapshot, he has to manually re-create these 100 addresses to let his balance show up.

Another potential confusion is that if a user has many addresses in his account and he did not write down all the addresses, when he is creating the addresses in his post-snapshot wallet, he won't know which ones are the old and used addresses and which ones are the brand new addresses.

Windows system dependency: Could not load light wallet functionality

On some windows system, the GUI wallet can't work well due to system dependency. The wallet shows " Could not load light wallet functionality". So the user need to download Visual C++ Redistributable Packages(https://www.microsoft.com/en-nz/download/details.aspx?id=48145). After that and restart the GUI wallet, it works fine.

So please prepackage the above package in the GUI package and do auto downloading and installation, or add some hints for users to download and install that package manually.

wallet don't start - wallet 2.0.0 IRI 1.1.1.1- ubuntu 16.04

I don't know if it's just for ubuntu 16.04:
I post the fix someone answer me on slack. Or for the second, the solution I found on Internet.
On npm start, I was stopping at :
[ '-XX:+DisableAttachMechanism',
'-jar',
'/home/user/folder/iri/iri.jar',
14265 ]
IRI 1.1.1.1

Solution : open wallet/app/js/main.js with any text editor

change at line 1262 data.match(/Welcome to IRI (Testnet)?\s*([0-9.]+)/i);
by data.match(/IRI (Testnet)?\s*([0-9.]+)/i);

The following one is not specific for the iota wallet but more for bower. Will be nice to add it on the tutorial for those who doesn't know :
bower install
If you see :
Error: EACCES: permission denied, open '/home/username/.config/configstore/bower-github.json'

One of the bower installation folder is owning by root(or other) :
sudo chown username:group directory

while sending a tx/attaching a new address, should disable functions for spammer until other action is complete.

wallet 2.0.2

while spamming on gui wallet, and i went and clicked>tools>claim process
this cancels out my spamming and may have corrupted my db. as i try to spam again, spams shoot out like 10 spams every second

another thing while sending a tx or attaching a receive address and then before it finishes go to the spammer, they both seem to run in conjunction with each other but as i hit cancel spam after running it a few seconds, it then immediately shows as "attach address complete/sending tx complete" but in reality it did not.

General FAQ-related (not a wallet issue per se): what does a coordinator do?

Seed longer than 81 trytes generates incorrect addresses

If the user's seed is longer than 81 trytes, it appears that the wallet will truncate the seed before using it to generate addresses.

Example seed (82 trytes):

TESTVALUE9DONTUSEINPRODUCTION99999VBQBZCEAGHJENC99YGBEDDLHYGLFYESGHCOGQAVEFEECVCNA

Output from JS lib:

> var IOTA = require('./lib/iota.js');
> var iota = new IOTA();

// 82-tryte seed
> iota.api.getNewAddress('TESTVALUE9DONTUSEINPRODUCTION99999VBQBZCEAGHJENC99YGBEDDLHYGLFYESGHCOGQAVEFEECVCNA', {index: 0, total: 1}, function (error, addy) { if(error) { console.log(error); } else { console.log(addy); }});
[ 'DOODVYDEAKYRCOOLHYGWGEABRZEGYRYSFKNNUJJKJEGUFXW9CLOAOITTIFCLEKIRFNHGRJCHRWTEKMLYW' ]

// 81-tryte seed
> iota.api.getNewAddress('TESTVALUE9DONTUSEINPRODUCTION99999VBQBZCEAGHJENC99YGBEDDLHYGLFYESGHCOGQAVEFEECVCN', {index: 0, total: 1}, function (error, addy) { if(error) { console.log(error); } else { console.log(addy); }});
[ 'VOMHWBGRLFSDPVLWUHUQSGU9VC9RUCZYNZQUZWGDXZMADBSMCQOQRMYLXQVFTBDDREULDX9XHQIYHZNLE' ]

When logging into the wallet with the 82-tryte seed, the Receive tab shows the same address as the 81-tryte seed (see screenshot).

Things not clear on doc ( confused with relation between doc and code wallet )

Hi ,I am impress with your DAG based concept , but i am confused as i have tried your code
on my linux server ( ubuntu desktop still struggling to install ).

1. should my neighbor execute same code of wallet in his ubuntu server or i should distribute my executable to all.
2. how can i find my 100 iota
3. if(seed == wallet) or seeds are server and wallet is executable.
4. how to convert my server to seed.

Missing opportunity to create new seed

Issue: When the seed got lost, you can not use the wallet to create a new one.
System: Windows 7, 64bit

Uninstalling the wallet and reinstalling it leads to the wallet's seed box does not appear when you start it again.
Note 1: After uninstalling also the folders C:\Users\username\AppData\Roaming\IOTA Wallet and C:\Users\username\AppData\Local\Programs\iota have been cleaned (removed the whole folders).
Note 2: After reinstalling the wallet then always starts in 'Full Mode' without the opportunity to first select Light or Full Mode (maybe minor issue).
Note 3: No errors are logged in the console.

The whole issue was discussed with several tries to solve (using different host addresses, cleanup old MS C++ Redist packages) in the forum: https://forum.iotatoken.com/t/lost-seed-how-to-re-login-to-wallet/1186/20

IOTA GUI wallet can not be opened

IOTA Wallet 2.0.0-IRI 1.1.1.1 can't be opened with error "The iota server process has exited", even I restarted my computer, detail is as below:

GUI version: IOTA Wallet 2.0.0-IRI 1.1.1.1
OS: Windows Server 2012 R2 Standard(AWS EC2
VM)
Java version(64-bit):
java version "1.8.0_111"
Java(TM) SE Runtime Environment (build 1.8.0_111-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.111-b14, mixed mode)

Cannot send things in decimals

When trying to send 0.3Ti, the GUI will not allow it. You have to send it in 300Gi.

How do i know wallet is installed on headless server

How do i know wallet is installed on headless server ..........
How can i see my wallet in it.

I have tried this code is working in windows desktop but when i switch it to my linux server without GUI that too remotely.I am not able to find out wallet working.

Bug: minWeightMagnitude is ignored

OS: Mac OSx Sierra
Wallet version: 2.2.0
Wallet mode: Light wallet

This is the hash with minWeightMagnitude 36:

GQTNNALMLANIKQEHUVPHQCURFXLEEZGXDFS9HHKL9FCNTOVZYTUVJFUFOZXOPPUPUUWZSHAVOZJ999999

but should be 12 trailing 9s at the end.

Invalid transaction hash

with GUI lightwallet client during spamming or sending a value tx

05/23 16:52:21.779 [XNIO-1 task-31] ERROR com.iota.iri.service.API - API Exception:
java.lang.RuntimeException: Invalid transaction hash
at com.iota.iri.TransactionValidator.runValidation(TransactionValidator.java:79) ~[iri-1.1.3.10.jar:na]
at com.iota.iri.TransactionValidator.validate(TransactionValidator.java:85) ~[iri-1.1.3.10.jar:na]
at com.iota.iri.service.API.broadcastTransactionStatement(API.java:621) [iri-1.1.3.10.jar:na]
at com.iota.iri.service.API.process(API.java:218) [iri-1.1.3.10.jar:na]
at com.iota.iri.service.API.processRequest(API.java:147) [iri-1.1.3.10.jar:na]
at com.iota.iri.service.API.access$000(API.java:81) [iri-1.1.3.10.jar:na]
at com.iota.iri.service.API$1.handleRequest(API.java:135) [iri-1.1.3.10.jar:na]
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:208) [iri-1.1.3.10.jar:na]
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:809) [iri-1.1.3.10.jar:na]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_131]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_131]

addNeighbor and removeNeighbor doesn't work in GUI

When removing a neighbor in the GUI (Tools > Edit Node Configuration), the message "removed 0 neighbor" appears. If you look at neighbor (Tools > View Neighbors) you see that indeed the neighbor isn't removed.
It seems this broke addNeighbor too: When you have tried to delete a neighbor and then you try to add another one, you have the message "added 0 neighbor" and indeed no new neighbor appears in the neighbor list.
Note that addNeighbor works when you do it first.

Minimize / close to tray instead of taskbar

Hi, it would be great to have an option to minimize / close to tray area instead of the taskbar. This would make it easier to run the app in the background.

IOTA Concept problem

How the nodes will get interacted between the DAG , so I want to know when a wallet A send the money to Wallet B , how does it get decided it reach to Wallet B only , Please help ? And if it transact between number of nodesthen why other node will participiate into it ?

IOTA Concept problem

And if it transact between number of nodesthen why other node will participiate into it ?

Cannot get any neighbour txt and so stuck at 6000

I am using the same laptop as wallet 1.0 and i have open firewall to ioto wallet and the port. I am using noip and i can confirm my neighbors are seeing my correct ip.

I have 17 neighbors and yet cannot get any connection. I have about ten or more others with the same problem.

I a running the spammer to encourage connection but still on 6000 and cannot proceed.

please check the ioto slack in testing as we have been discussing this issue.

server log

IRI 1.1.1.1
Confirmed transactions = 1
24 tails need to be analyzed
23 extra transactions approved
Confirmed transactions = 24
0 tails need to be analyzed
0 extra transactions approved
Transactions to request = 0 / 24 (46 ms / 0%)
Transactions to request = 0 / 24 (28 ms / 0%)
Transactions to request = 0 / 24 (29 ms / 0%)
Transactions to request = 0 / 24 (29 ms / 0%)
Transactions to request = 0 / 24 (32 ms / 0%)
Transactions to request = 0 / 24 (30 ms / 0%)
Transactions to request = 0 / 24 (29 ms / 0%)
Transactions to request = 0 / 24 (29 ms / 0%)
Transactions to request = 0 / 24 (28 ms / 0%)
Transactions to request = 0 / 24 (29 ms / 0%)
Transactions to request = 0 / 24 (29 ms / 0%)
Transactions to request = 0 / 24 (29 ms / 0%)
Transactions to request = 0 / 24 (28 ms / 0%)
Transactions to request = 0 / 24 (28 ms / 0%)
Transactions to request = 0 / 24 (28 ms / 0%)
Transactions to request = 0 / 24 (28 ms / 0%)
Transactions to request = 0 / 24 (29 ms / 0%)
Confirmed transactions = 1
25 tails need to be analyzed
24 extra transactions approved
Confirmed transactions = 25
0 tails need to be analyzed
0 extra transactions approved
Transactions to request = 0 / 25 (45 ms / 0%)
Transactions to request = 0 / 25 (35 ms / 0%)
Transactions to request = 0 / 25 (32 ms / 0%)
Transactions to request = 0 / 25 (34 ms / 0%)
Transactions to request = 0 / 25 (34 ms / 0%)
Transactions to request = 0 / 25 (32 ms / 0%)
Transactions to request = 0 / 25 (35 ms / 0%)
Transactions to request = 0 / 25 (35 ms / 0%)
Transactions to request = 0 / 25 (33 ms / 0%)
Transactions to request = 0 / 25 (33 ms / 0%)
Transactions to request = 0 / 25 (34 ms / 0%)
Transactions to request = 0 / 25 (32 ms / 0%)
Transactions to request = 0 / 25 (34 ms / 0%)
Transactions to request = 0 / 25 (33 ms / 0%)
Transactions to request = 0 / 25 (32 ms / 0%)
Transactions to request = 0 / 25 (36 ms / 0%)
Transactions to request = 0 / 25 (33 ms / 0%)
Confirmed transactions = 1
26 tails need to be analyzed
25 extra transactions approved
Confirmed transactions = 26
0 tails need to be analyzed
0 extra transactions approved
Transactions to request = 0 / 26 (33 ms / 0%)
Transactions to request = 0 / 26 (28 ms / 0%)
Transactions to request = 0 / 26 (29 ms / 0%)
Transactions to request = 0 / 26 (29 ms / 0%)
Transactions to request = 0 / 26 (28 ms / 0%)
Transactions to request = 0 / 26 (28 ms / 0%)
Transactions to request = 0 / 26 (31 ms / 0%)
Transactions to request = 0 / 26 (27 ms / 0%)
Transactions to request = 0 / 26 (27 ms / 0%)
Transactions to request = 0 / 26 (27 ms / 0%)
Transactions to request = 0 / 26 (28 ms / 0%)
Transactions to request = 0 / 26 (29 ms / 0%)
Transactions to request = 0 / 26 (28 ms / 0%)
Transactions to request = 0 / 26 (28 ms / 0%)
Transactions to request = 0 / 26 (29 ms / 0%)
Transactions to request = 0 / 26 (27 ms / 0%)
Transactions to request = 0 / 26 (28 ms / 0%)
Confirmed transactions = 1
27 tails need to be analyzed
26 extra transactions approved
Confirmed transactions = 27
0 tails need to be analyzed
0 extra transactions approved

General FAQ-related (not a wallet issue per se): how do I know I'm synced?

Feature: Show checksum as user types their seed

To prevent issues caused by a user mistyping their seed, what do you think about computing a checksum as the user types their seed (same idea as address checksum: run the value through curl and take the first 9 trytes)?

When generating a new seed, present the user with both the seed and the corresponding checksum value.

This would give users an easy way to verify that they typed in their seed correctly, and the checksum cannot be reverse-engineered to gain information about the seed.

GUI Request:Add alias next to neighbors ip for easier contacts

pretty self-explanatory
Add alias box next to neighbors ip for easier remember who owns it so can be contacted when there's problems, so we don't need to open our precious notepads = ]

might as well create textboxes per ip, and limit wallet to 9-12textboxes so people won't just add loads of ips.
next to each ip textbox has corresponding alias textbox

Not working on Centos server

I have tried to check your code in linux server , I think its not working as electron prebuilt

/usr/local/lib/node_modules/electron-prebuilt/dist/electron: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory

Can you please enlighten me . ... how should i install or where i am wrong ??

General FAQ-related (not a wallet issue per se): why does my 1.0.3. client generate 90-character address while tangle.guru shows 81-character truncated version of this same address?

Errors / Grammar Mistakes in the Help/FAQ Section

Little things, but we are on a bug hunt...

In the Help/FAQ section of the Wallet:

Tangle Not Solid

In the status bar, you'll see: xx / yyyy (zz)

This is not longer the case - we now have xxxxx / yyyyy / CPU %

How long and complex should my seed be?

In order to ensure that only you got access...

Replace with: "In order to ensure that only you have access..."

GUI Wallet says "sending..." but Proof of Work doesn't start

When attempting to send a transaction, the wallet says "sending..." as expected, but the proof of work does not kick in and the CPU usage stays low. Generating addresses works as expected.

Three users can confirm that this issue is isolated to a single seed and when sending from other seeds the problem does not exist.

General FAQ-related (not a wallet issue per se): what are the limits in sending and receiving IOTA?

Here we can mention stuff like capped number of IOTAs per address, guidelines regarding maximum amount of sends from a given address, etc.

Install Flow is not Correct

I am using a new Win 7 64 bit VM. When i use the installer, it says Java is not installed so gives me the option to Install Java or Start light mode.

Clicking start light mode without Java should not be allowed, so the option should not be given at that point.

Black screen following an attempted replay

Steps:

1. Create transaction.
2. Spam network
3. Wait one hour from original transaction and choose to replay
4. Wait 20 mins

Expected Result:
See message confirming Replay completed

Actual Result:
Application Window goes black and no functionality apart from closing is available

Other notes:

I'm seeing the wallet go black around 20 minutes after a starting replay. No menu items work at all and I need to exit and reopen. I think the replay is done successfully, as I can see it in the history, but no confirmation is given.

I think that the wallet fails when attempting to display the confirmation message.

This happened three times in a row last night. Over a period of 5 hours.

Using v2.1.1 on Windows Dell i5

I've replayed successfully in the past about a month ago, so unusual to see this happening consistently yesterday.

Today I've done another replay and this has completed successfully.

One possible related consideration, but needs further investigation: When a TX is replayed, and you want to do a second replay, the user has the choice to replay the original bundle, or the new bundle created as a result of a recent replay. The recent successful replay was done against a new bundle, whereas the previous black screens were done against the original bundle. Please note black screen appears intermittently, and may be entirely unrelated to this.