Micro tries to create log.txt on working directory every time it is opened

Status changed to 'Confirmed' because the bug affects multiple users.

It's really irritating having to clean up after using micro, and not being able to launch it from a directory that I don't have write access to. I've tried to set debug to false in the config file, but that doesn't work. Any ideas on how to fix this would be greatly appreciated.

@Sean: I used this way to reinstall micro and bypass the bug in repo:

$ sudo apt remove micro
$ sudo apt install curl
$ curl https://getmic.ro | bash
$ sudo mv micro /usr/bin/micro

Had the same problem under Linux mint 20 cinnamon (uses Ubuntu repositories) my fix was to remove the repository version and install the .deb from GitHub. https://github.com/zyedidia/micro/releases

I was asked to test this

Recent Lubuntu 20.04.2 QA-test install, thus clean system.
`sudo apt install micro`

I started micro, played with editor entering & changing text.
On exit (without save) I did have a `micro.txt` in my $HOME, it contained "2020/11/30 20:47:25 Micro started" as contents.

I `cd /etc` as per original poster and obtained the identical error message the OP reported, as I don't have write access to that directory.

I can confirm issue.

Changing the status to fix released. As the bug is rectified in versions of micro in groovy and in hirshute devel branch. Considering a SRU for focal.

Thank you! Although piping getmic.ro is interesting, update for focal would be great.

Not sure how it can be set to fix released if it's still an issue in LTS versions of Ubuntu?

Can we please backport this to all LTS releases?

Hello,

I am the maintainer of micro in Debian and thus here. I'll try to get this fixed in sometime. Thanks!