Corbo

Point is, the "Please touch the device" prompt does not even show until you successfully authenticated. At least here on Ubuntu disco. That msg is useles as is.

> > Point is, the "Please touch the device" prompt does not even show until you successfully authenticated. At least here on Ubuntu disco. That msg is useles as is....

Here, it is an authentication failure even with the device already plugged in. Until I hit the button, that's when I'm going to get logged in nevertheless.

Is this workaround still the way to go? And will it be so for the rest of the days? I'd kinda like to announce a slight preferrence on the bright...

Hi @magicmonty Thank you for your feedback and, yes, basically, I feel the same way you do. Before I started what became this PR in the end, I tried to...

@magicmonty: looking at the PR, I realize the guard is already in place. If there is no `$__GIT_PROMPT_DIR/git_user_cmds.sh` file nothing will get parsed, everything is hunky-dory. One could add an...

@magicmonty: about sourcing "a file everytime the prompt is generated", granted, it's far from being an elegant solution. As for now, it's rather a "works for me" situation. Where exactly...

@cp2004, chiming in upon your comment https://github.com/OctoPrint/OctoPrint/issues/3212#issuecomment-678743165 . I do not use plain serial to connect to RAMPS, using serial over USB instead (standard way IIMSS). Also, a raspberry pi...

> > @cp2004, chiming in upon your comment [OctoPrint/OctoPrint#3212 (comment)](https://github.com/OctoPrint/OctoPrint/issues/3212#issuecomment-678743165) . > > I do not use plain serial to connect to RAMPS, using serial over USB instead (standard way...

@cp2004 I just had had the `WS281x LED Status` plugin installed, not yet configured. That was when I noticed this connection issue and I immediately uninstalled the plugin again. No...