log_error ignored in my.cnf file if log_basename set

With 10.8.3, "log_error" was working fine until the 29th June, and only now I noticed that since the restart on that day, the "log_error" property in "my.cnf" file is being ignored, and instead it's defaulting to "./mysql.err". There was no MariaDB update around that day.

I restarted MariaDB yesterday, and "log_error" continues to be ignored.

I confirm that the path (outside datadir) exists and is accessible by the user mysql (also set in user property).

I checked several of the other properties, and they seem to be OK (not ignored).

–

I added this recently:

log_basename = "mysql"

I suspect this might be the cause.

–

Does setting log_basename make log_error be ignored?

I added it to make any other files have that prefix instead of the hostname, but I was assuming I could still override the path of the logs separately, like for log_error.

–

I also get this warning:

[Warning] Although a path was specified for the --log-slow-queries option, log tables are used. To enable logging to files use the --log-output=file option.

Even though I don't specify any "log_show_queries" option.

Thank you.