search

BuddiesOfBudgie / budgie-screensaver

Budgie Screensaver is a fork of old gnome screensaver for purposes of providing an authentication prompt on wake.
GNU General Public License v2.0
15 stars 2 forks source link

Changing language on lock screen not possible #6

Closed mike-ua closed 2 years ago

mike-ua commented 2 years ago

My comment added to the Solus forums, but user 'Nolan' says it's a Budgie issue, not Solus.

Hi, I have the same issue (Solus/Budgie) - when coming back from 'Suspend', and the language was left in another that was not English (my 'unlock' password' is in English) there is no longer the option to switch languages. It was there before, used it many times.

The only way to resolve the issue is to hold the power button down and kill the computer, a fairly substantial regression that significantly affects usability.

Here is the link to the issue reported in the Solus forums - https://discuss.getsol.us/d/8187-changing-language-on-lock-screen

Thanks Mike

fossfreedom commented 2 years ago

The input sources stuff and its display is in and around this area https://github.com/BuddiesOfBudgie/budgie-screensaver/blob/master/src/gs-lock-plug.c#L1457

@mike-ua what is the value of the following under solus?

gsettings get org.gnome.desktop.input-sources sources
gsettings get org.gnome.desktop.input-sources current

For example my GB and Greek layouts returns the following values:

[('xkb', 'gb'), ('xkb', 'gr')]
uint32 0
mike-ua commented 2 years ago

gsettings get org.gnome.desktop.input-sources sources returns: [('xkb', 'us'), ('xkb', 'ua')]

gsettings get org.gnome.desktop.input-sources current returns: uint32 0

fossfreedom commented 2 years ago

Thx. So the inputs look OK.

To resolve this will need a series of debug statements in the area of the code i pointed to to find out what is going on. This will need to be done on Solus ... I can't do this since debian and budgie doesn't use budgie-screensaver.

mike-ua commented 2 years ago

unfortunately, I do not know how to do this, is it difficult to produce a 'debug statement'? Maybe you can give me some instructions and I can try.

EbonJaeger commented 2 years ago

If @fossfreedom can tell me where/what the prints need to be, I can make a quick testing package for you to try.

Solarunit commented 2 years ago

The only way to resolve the issue is to hold the power button down and kill the computer,

There is another "workaround". Left button (Switch user iirc) will take you to the Login screen where you can reboot system. (You can bypass the Login screen but will stuck at lock-screen again, so reboot is only option)

mike-ua commented 2 years ago

The only way to resolve the issue is to hold the power button down and kill the computer,

There is another "workaround". Left button (Switch user iirc) will take you to the Login screen where you can reboot system. (You can bypass the Login screen but will stuck at lock-screen again, so reboot is only option)

That's basically the same as holding the power button down, less abrupt, but still a disruption to work flow. Strange part is that I know the option to switch languages was there before, so at some point this (necessary) feature was eliminated for whatever reasons.