I don't sure that it is exactly corresponds to the bug #21034.
I can't reproduce it with USB mouse, only with USB keyboard.
Please try reproduce this with thunar-volman-plugin-0.6.0-alt3.M60P.1 and
xfce4-settings-4.8.3-alt0.M60P.2.

(In reply to comment #1)
> I can't reproduce it with USB mouse, only with USB keyboard.

Yes, now I can reproduce it only with USB keyboard, and not with a USB mouse, but I'm quite sure it happened with mouse, too, perhaps on Simply Linux 6.0beta or some other distro...

> Please try reproduce this with thunar-volman-plugin-0.6.0-alt3.M60P.1 and
> xfce4-settings-4.8.3-alt0.M60P.2.

Ok, I'll try; now I have older releases:

thunar-volman-plugin-0.6.0-alt2.M60P.1
xfce4-settings-4.8.3-alt0.M60P.1

from Simply Linux 6.0.1RC2.

Yes, with these new packages switching the layouts after unplugging and plugging a USB keyboard works. (Although it looks like a hack -- the fix is not on the appropriate, window-manager-independent level.)

Are they included in a published Simply Linux distro? (Then this bug could be closed.)

(В ответ на комментарий №3)
> Yes, with these new packages switching the layouts after unplugging and
> plugging a USB keyboard works. (Although it looks like a hack -- the fix is not
> on the appropriate, window-manager-independent level.)

Yes, it is a workaround. I don't know how do it in another way.

> Are they included in a published Simply Linux distro? (Then this bug could be
> closed.)

It will be in the next RC, of course.

https://bugzilla.altlinux.org/show_bug.cgi?id=21034#c24

В p7 на Simply Linux проблема проявляется так:

у меня запущен Xfce на 7-ой консоли (втыкание USB-наушников не портит заметно
раскладку).

Теперь заходит пользователь (в моём случае -- другой, но это вряд ли важно) на
первой консоли, делает startx, работает Xfce на 8-ой консоли.

Когда мы на 8-ой консоли, втыкаем USB-наушники. В Xfce на 8-ой консоли
раскладка заметно не портится.

Но переключаемся на 7-ую консоль с Xfce, там русская раскладка слетела!

Нужно более чистое исправление.

(В ответ на комментарий №4)

> Yes, it is a workaround. I don't know how do it in another way.

> It will be in the next RC, of course.

Thank you! It worked, until now when the case described above was discovered.