--- Comment #27 from Matthias Seidel <matthias.sei...@hamburg.de> ---
(In reply to hanya from comment #26)
> If it would be part of 4.1.3, it's better. I thought next release would be
> 4.2 when I found the fix.
Well, at that time there was no 4.1.3 planned... ;-)
Can anyone change the target milestone? I have no rights.
Interesting that issue 126980 occurs for you in en-US (OK, I only tested with
en-GB). But I have at least 2 other reproducible crashes which may be caused by
the same problem.
One is issue 125762.
You are receiving this mail because:
You are the assignee for the issue.