Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removing keyboard layout logs you out and disables ability to log back in #740

Closed
NigelGreenway opened this issue Nov 23, 2016 · 24 comments
Closed

Comments

@NigelGreenway
Copy link

Operating System: Solus 1.2.1 (Ran within a VirtualBox machine)
Budgie version: 10.2.8

The issue encountered

Removing the English(US) keyboard layout ends the session and returns back to the login screen. When logging back in it will crash and return back to the login screen.

Steps to reproduce the issue

  • Install OS
  • Remove second keyboard layout
    • Try to log back in
@ikeydoherty
Copy link
Member

Do you have the keyboard layout indicator present..?

@ikeydoherty
Copy link
Member

Rather, did you..

@NigelGreenway
Copy link
Author

@ikeydoherty present in the system tray?

@NigelGreenway
Copy link
Author

I can recreate tomorrow with a fresh install if that helps? Could also log in and export a log too? Just not sure which log would help?

@NigelGreenway
Copy link
Author

@ikeydoherty I noticed this commit, a65303a, would it be worth me building budgie on my install? Would like to help but not sure where to start?

@ikeydoherty
Copy link
Member

That is in the Solus package already

@NigelGreenway
Copy link
Author

So, from a fresh install and without updates I have removed the English (US) keyboard layout and it has done the same. The indicator was not showing in the panel.

Is there are log I can look at?

@Robotmike1966
Copy link

If helpful:

  • I created a fresh Solus in a VirtualBox
  • updated everything in original language
  • rebooted
  • settings dialog: added German, removed English
  • Crash, loginscreen reappeared
  • did one login try
  • had crash again
    -waited for login screen
  • ctrl alt f1, login on terminal
  • journalctl -b -o export > journal.txt

Append this file here. (408 kB)
journal.txt

@arslan
Copy link

arslan commented Dec 6, 2016

I have a related problem, I guess.

When I add Russian keyboard layout, switch to it (use it, etc.) and log out of the system, or when the system locks due to the inactivity, I am introduced with a login screen that doesn't accept the password. Note that I use English letters for my password.

I suppose that login screen doesn't support language switching. I had to go back to Windows, after clean installing Solus 2 times, due to this bug. It is really annoying.

Prompt action on this matter would be highly appreciated.

@niyasc
Copy link
Contributor

niyasc commented Dec 6, 2016

I have a related problem, I guess.

When I add Russian keyboard layout, switch to it (use it, etc.) and log out of the system, or when the system locks due to the inactivity, I am introduced with a login screen that doesn't accept the password. Note that I use English letters for my password.

I suppose that login screen doesn't support language switching. I had to go back to Windows, after clean installing Solus 2 times, due to this bug. It is really annoying.

Prompt action on this matter would be highly appreciated.

@rcx
This appears like a problem having roots on gnome-screensaver and that issue is known for more than 3 years. You can find related discussions here

@arslan
Copy link

arslan commented Dec 6, 2016

@ikeydoherty It seems that this is a long-lived bug, any prospects of fixing it? Maybe adding a language pick menu in the lock screen would be a good temporary fix?

@niyasc
Copy link
Contributor

niyasc commented Dec 6, 2016

Well. The lock screen does not support language switch shortcut. Though you can see language code on right side of password field and it can be changed by mouse click. ( have n't checked in Solus, but that is the case on budgie-remix 16.40)

@arslan
Copy link

arslan commented Dec 7, 2016

Weird. Nothing happens, when I click on the language code on the right side. Let me check in VM.

@NigelGreenway
Copy link
Author

When I have used budgie-remix, I was unable to reproduce this error, only producible on Solus, if that helps?

@arslan
Copy link

arslan commented Dec 8, 2016

I have installed Solus on my laptop again and now I realized that when I log out I can see the menu to change the language. But when the system locks due to inactivity then there is no way to switch languages and log in using my English password.

Also the option to "Allow different sources for each window doesn't work". And the option to change the language using only modifier keys doesn't work.

languages
login screen after inactivity lock
login screen after log out
btw this feature doesnt work

@RDR8
Copy link

RDR8 commented Feb 5, 2017

As a workaround for the OP, try gsettings set org.gnome.desktop.input-sources current 0 at a shell prompt, i.e, Ctrl-Alt-F2. This resets the keyboard layout to the default.

@NigelGreenway
Copy link
Author

Will try that this weekend. Thank you @RDR8 👍

@RDR8
Copy link

RDR8 commented Feb 9, 2017

In #741 , @CarlosZaldivar mentions restarting budgie-wm. I think one could do that with systemctl from the same terminal where gsettings was run so that no reboot is needed but I didn't test that. I shamelessly rebooted.

@fu-sen
Copy link

fu-sen commented Feb 22, 2017

I confirmed this problem with Ubuntu Budgie 17.04 Daily Build. I am shooting that movie:
https://www.youtube.com/watch?v=cSMkgH_ei0U
Playback from 21:30

@fu-sen
Copy link

fu-sen commented Feb 22, 2017

I confirmed it with Solus. Currently Solus seems to have improved this problem.
I will test again after getting desktop updates with Ubuntu Budgie 17.04.

@valentin-fischer
Copy link

This should be reopen as it is still causing issues ...

@fossfreedom
Copy link
Contributor

@valentinul what distro are you using?

@ikeydoherty
Copy link
Member

I'm gonna guess a distro without that patch (like stable Solus)

@ikeydoherty
Copy link
Member

Confirmed this is resolved in git and will be part of 10.3 (in an hour or so)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants