Mudlet clear profile how to#
Mudlet clear profile 64 Bit#

Screenshots of the crash in the debugger (running Mudlet 4.4.0) are attached. Netflix will display a prompt informing you that deleting the profile will delete all its preferences and watch history. Select Delete Profile at the bottom of your screen. On a profile I have been using awhile it happens almost always immediately after the first RDP connection. Click your profile icon at the top-right, and select Manage Profiles. Using a vanilla profile it took me several iterations of the above to cause a crash.

Mudlet clear profile 64 Bit#

Updating the 64 bit windows branch to bring in changes from the devel.

SlySven added a commit that referenced this issue on Aug 3.

Signed-off by: Stephen Lyons <> Authored by: atari2600tim <29287358+>.

settings button will be available again before you connect to a profile. Return to Windows desktop and login at console Fix 2 typos in JSON map export Closes 5265. In Imperian, I have to type in all my commands and figure out Mudlet again to.one is provide some sort of interface because its pretty clear the direction. Open mudlet with run-mudlet.sh Click Connect, +New and create a botman profile with IP and Telnet port Click Connect and if you see 'Enter password', clode mudlet and save profile. While messing with mudlet earlier and a GUI, I managed to split my screen into.

Mudlet clear profile how to#

but decided to switch over), so I'm trying to figure out how to do different things. Connect to a game, open the triggers window, scroll up/down Were going to get straight into Mudlets history, its development and its. Okay, I'm a complete newbie when it comes to mudlet (I've been using Mushclient for years.This bug report is referring to the 'Mudlet' application ( ) which is based on Desktop Qt 5.13.2 MinGW 32-bit.Īfter repeatedly using various Microsoft Remote Desktop clients to connect to a Windows computer running the Qt application Mudlet, Mudlet crashes when opening or scrolling within the Triggers window (I believe the triggers window may involve widgets/dialog, see stack trace screenshot) Steps to reproduce the issue: