Quote from: fullzero on July 22, 2017, 06:07:49 PM

Quote from: ijduncan on July 22, 2017, 05:55:14 PM

Quote from: fullzero on July 22, 2017, 05:28:09 PM

Quote from: WoolF911 on July 22, 2017, 03:54:17 PM

Quote from: ijduncan on July 22, 2017, 03:43:08 PM

I am seeing a new error i have not seen before.
There is no screen to be resumed matching miner.
In the terminal window right before the miner of choice starts. And the mining still does seem to start in the background.

Yes, same problem.

Quote from: newmz on July 22, 2017, 04:53:49 PM

Quote from: ijduncan on July 22, 2017, 03:43:08 PM

I am seeing a new error i have not seen before.

There is no screen to be resumed matching miner.

In the terminal window right before the miner of choice starts. And the mining still does seem to start in the background.

Could it have something to do with a high resolution screen being present?

I have tried another image and the same thing occurred.

go to the quake terminal window and type "screen -r miner" and you should see your miner running

Have you set:

Code:

LOCALorREMOTE="REMOTE"

if so then this is expected

as newmz indicated:

open a terminal and enter

Code:

screen -r miner

to attach the mining process

The code is LOCAL. I have not adjusted the default.

If this is occurring it is because there is already a mining process going on before 1bash has been launched. Thus when the code attempts to attach the new process to the gnome-terminal it finds multiple screens; and cannot attach without you specifying which (which is not done by the code in 1bash).

The bugfix files + newest 1bash should prevent this from happening. I highly suspect many members are using the newest 1bash without updating the other files or using the new files without updating their 1bash. The next version will incorporate a method that should do away with this kind of problem.

I realize all of these changes are a pain to deal with; and it doesn't help that v0018 wasn't properly tested beforehand. I think I have a solution to accommodate users who prefer a known stable build and users who want the newest unverified beta; I will implement this in v0019 as well.

If you are using the newest 1bash and newest files and this problem is still occurring; I would reboot and not change any settings on startup. The initial boot should attach the mining process to a screen in the gnome-terminal.

I got this message sometime to, but only when i try some OC setting and the miner crash chain ... I simply hard reset and work again.