4 ms·

As well, you do not describe the exact sequence of actions that leads you to the error. Without it, you cannot be helped. You also provide a list of bug report

As well, you do not describe the exact sequence of actions that leads you to the error. Without it, you cannot be helped. You also provide a list of bug reports that are just similar, but probably not related to your particular issue.

torstenvl 4y ago
> not related to your particular issue That's extremely unlikely and it's concerning that you think the exact same error at the exact same point starting after the exact same last-known good build is "not related." If that's a possible failure mode of your code base then your code base is pure shit.
- jeditobe 4y ago
  This problem is very rare. It is very hard to encounter it, unless you have some very specific conditions. You said nothing about the version and name of VM you are using. As well, you do not describe the exact sequence of actions that leads you to the error. Without it, you cannot be helped.
  - torstenvl 4y ago
    > you cannot be helped I'm not the one who needs help. Your software is. I linked to several detailed bug reports and told you very clearly that I had the "exact same" problem. It is not encouraging that you won't even read the bug reports, and certainly doesn't encourage anyone to further help you.
    - jeditobe 4y ago
      I really don't understand your childish behavior. You flaunt your unwillingness to cooperate, as revenge for the offense allegedly inflicted on you by someone. This is stupid and naive. There is nothing difficult about naming your version of the Virtual Machine. The error "Failed to open txtsetup.sif" can theoretically pop up for a million reasons\scenarios, and even fixing all of them may not help in your particular case, without providing information from you. However, this error is extremely rare. Developers can't fix a bug that they can't reproduce. Therefore, extra efforts are needed to catch, eliminate or bypass it. Hysterical insults on volunteer developers of a free open source project are not the best example of interaction.

torstenvl 4y ago

> not related to your particular issue That's extremely unlikely and it's concerning that you think the exact same error at the exact same point starting after the exact same last-known good build is "not related." If that's a possible failure mode of your code base then your code base is pure shit.

jeditobe 4y ago
This problem is very rare. It is very hard to encounter it, unless you have some very specific conditions. You said nothing about the version and name of VM you are using. As well, you do not describe the exact sequence of actions that leads you to the error. Without it, you cannot be helped.
- torstenvl 4y ago
  > you cannot be helped I'm not the one who needs help. Your software is. I linked to several detailed bug reports and told you very clearly that I had the "exact same" problem. It is not encouraging that you won't even read the bug reports, and certainly doesn't encourage anyone to further help you.
  - jeditobe 4y ago
    I really don't understand your childish behavior. You flaunt your unwillingness to cooperate, as revenge for the offense allegedly inflicted on you by someone. This is stupid and naive. There is nothing difficult about naming your version of the Virtual Machine. The error "Failed to open txtsetup.sif" can theoretically pop up for a million reasons\scenarios, and even fixing all of them may not help in your particular case, without providing information from you. However, this error is extremely rare. Developers can't fix a bug that they can't reproduce. Therefore, extra efforts are needed to catch, eliminate or bypass it. Hysterical insults on volunteer developers of a free open source project are not the best example of interaction.