The problem

This is a reopen of issue 10462 using git from the command line
I am seeing the same problem. git commit worked before for me. It used to bring up my editor (kate) and wait for me to type in a commit message, save it, and exit the editor, and then do the commit. Now git brings up my editor (kate) but does not wait. Instead git responds
Aborting commit due to empty commit message.
and exits. I tried
git config --global core.editor "kate -w"
as suggested in an old stackoverflow posting, but then git commit emits the error message without even starting kate. git commit -m <message> works. I'm running git version 2.43.0, which the latest version supported by my (linux) OS openSUSE Leap 15.6.

Release version

git version 2.43.0

Operating system

openSUSE Leap 15.6

Steps to reproduce the behavior

Run git commit from command line.
Previous behaviour:-
My editor (kate) pops up with a list of changed files which will be committed and another list of untracked files with a field at the top for typing in a commit message. When I type in a commit message, save it, and close the editor, git does the commit and reports what it has done.
New incorrect behaviour:-
My editor (kate) pops up with a list of changed files which will be committed and another list of untracked files with a field at the top for typing in a commit, but git prints
Aborting commit due to empty commit message.
and exits without waiting for the editor.

Log files

No response

Screenshots

No response

Additional context

No response