restore DWC 3.5.2

Tinchus

Hi. I just installed some days ago version 3.5.2, I used the 64 bits version on a duet 3 + SBC (raspi 3 B+)

Once installation finished (still had a problem about rotation of the touch screen) I changed the default name of the printer. After reboot the DWC did not start (it happened to me in the past but usually by manually starting the link on the pi desktiop, solved the problem) and this time trying to lauch it from the link on the pi desktop doesnt work.
Tips on how I can start DWC on the touchscreen again?

Thanbks in advance

Phaedrux

@Tinchus said in restore DWC 3.5.2:

this time trying to lauch it from the link on the pi desktop doesnt work.

Do you mean DWC doesn't launch at all, or it's not auto-launching at startup?

Tinchus

@Phaedrux It doesnt launch in the touch panel I have cnnected. I can access it through the network.
In the touch panel screen I can see the direct access to it, clicking on it doesnt work. I cant find were logs are to see what the problem is either

Phaedrux

@Tinchus said in restore DWC 3.5.2:

I can see the direct access to it, clicking on it doesnt work.

What exactly does this mean?

Tinchus

@Phaedrux when the printer boots, the touuch screen at the end ends up showing the pi GUI desktop. There I can see direct access icon named DUET WEb CONTROL.

Phaedrux

@Tinchus said in restore DWC 3.5.2:

There I can see direct access icon named DUET WEb CONTROL.

And that icon doesn't work at all to start the browser and open DWC?

Can you manually open a browser and open the local address for DWC?

Tinchus

@Phaedrux that link doesnt work at all.
From my computer connected to the wifi netwark, I can access the printer using its fantasy name or its IP with no problem

Phaedrux

Perhaps @chrishamm can suggest some log files to check to see what is failing.

Tinchus

@Phaedrux Problem solved. Dont know why, seems chromium got bloques as usual when changing the printers fantasy name. Usually when this hapenned in the past, using this link on desktop asked you about a lock being present and giving you the chance to reset this lok. This time that never happened.

Manually removing the lock solved the problem:

rm .config/chromium/SingletonLock

Thaks