Session is discarded when updating shortcut

[bagage]

What steps will reproduce the problem?

1. Download some OSM data, add some imagery layers…
2. Open settings, change a shortcut, and quit the settings dialog with OK button
3. A popup open "JOSM must be restarted so that new shortcut takes effect"
4. Click OK

What is the expected result?

1. JOSM is restarted
2. the new shortcut works as expected.
3. I can continue my work from there.

What happens instead?

Ideally, I'd love to have shortcuts taking effect immediately. But if that's not possible that's OK and instead:

Points 1&2 work as intended.
However JOSM starts a fresh session and all the previous layers are lost. JOSM didn't ask what to do about these (it only does when there are some modifications not saved yet). Ideally reopening the session would be great, otherwise at least modifying the alert text so that it is clear that open layers will be closed?

Thanks!

Please provide any additional information below. Attach a screenshot if possible.

URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2019-06-01 23:08:04 +0200 (Sat, 01 Jun 2019)
Build-Date:2019-06-01 21:56:04
Revision:15150
Relative:URL: ^/trunk

Identification: JOSM/1.5 (15150 fr) Linux Debian GNU/Linux 10 (buster)
Memory Usage: 1029 MB / 4436 MB (697 MB allocated, but free)
Java version: 1.8.0_212-8u212-b03-2-b03, Oracle Corporation, OpenJDK 64-Bit Server VM
Screen: :0.0 1920x1080
Maximum Screen Size: 1920x1080
Java package: openjdk-8-jre:amd64-8u212-b03-2
Java ATK Wrapper package: libatk-wrapper-java:all-0.33.3-22
Dataset consistency test: No problems found

Plugins:
+ AddrInterpolation (34908)
+ HouseNumberTaggingTool (34977)
+ OpeningHoursEditor (34977)
+ PicLayer (34908)
+ buildings_tools (34982)
+ conflation (0.6.3)
+ jts (34908)
+ poly (34991)
+ reverter (34999)
+ scripting (30794)
+ terracer (34977)
+ todo (30306)
+ utilsplugin2 (34977)

Last errors/warnings:
- E: Handled by bug report queue: java.lang.IllegalArgumentException: Invalid number of points in LinearRing (found 3 - must be 0 or >= 4)
- E: Handled by bug report queue: java.lang.IllegalArgumentException: Invalid number of points in LinearRing (found 3 - must be 0 or >= 4)
- E: Handled by bug report queue: java.lang.IllegalArgumentException: Invalid number of points in LinearRing (found 3 - must be 0 or >= 4)
- E: Handled by bug report queue: java.lang.IllegalArgumentException: Invalid number of points in LinearRing (found 3 - must be 0 or >= 4)
- E: Handled by bug report queue: java.lang.IllegalArgumentException: Invalid number of points in LinearRing (found 3 - must be 0 or >= 4)
- E: Handled by bug report queue: java.lang.IllegalArgumentException: Invalid number of points in LinearRing (found 3 - must be 0 or >= 4)
- E: Handled by bug report queue: java.lang.IllegalArgumentException: Invalid number of points in LinearRing (found 3 - must be 0 or >= 4)
- E: Handled by bug report queue: java.lang.IllegalArgumentException: Invalid number of points in LinearRing (found 3 - must be 0 or >= 4)
- E: Handled by bug report queue: java.lang.IllegalArgumentException: Invalid number of points in LinearRing (found 3 - must be 0 or >= 4)
- E: Handled by bug report queue: java.lang.IllegalArgumentException: Invalid number of points in LinearRing (found 3 - must be 0 or >= 4)