Open Icy-Thought opened 3 years ago
Hi, can you pleas elaborate a bit more? What is the exact behavior of "I find myself unable to access my account after reboot"? Maybe a short gif would help?
Hi, can you pleas elaborate a bit more? What is the exact behavior of "I find myself unable to access my account after reboot"? Maybe a short gif would help?
It prevents me from logging in completely and thus I cannot record this behavior to showcase it.
Visual explanation: After entering my password I would've normally seen my splash screen load, but when the plugin is enabled my screen would attempt to load the splash screen (go black for a a short period of time) and later return to the login page as if I had just started the laptop.
Hello.
I have the same issue with different computers on Ubuntu 20.04, 20.10 PopOS 20.04, 20.10 and Fedora 33.
In the syslog I see this error:
gnome-shell[7352]: segfault at c6fb33ffff0 ip 00007f0420a140fc sp 00007ffef6ead130 error 4 in libmozjs-78.so.0.0.0[7f042060e000+a06000]
So what happens looks like the gnome-shell crashes in a wayland session after logging in. Then a new gnome-shell is launchend and you see the login again.
For me this looks like this: System starts up to login screen. I enter my credentials. I hit "enter" key. I get the Gray background with the mouse cursor in the lower right corner of the screen. Mouse curser freezes and the screen stays at this stage for about 2 Minutes. Login screen reappears.
I then switched to Xorg Session and disabled TouchpadIndicator. Logged out and switched to wayland session again. Problem dissapears.
@user501254 I can provide you the crash data from Fedora if that might help. There is a backtrace and a lot of other info in there.
@jhit Thank you, that would definitely help. However, to be honest, it is unlikely that I would get a chance to look at it before mid December.
Describe the issue
When this extension has been enabled on GNOME 3.36 I find myself unable to access my account after reboot.
Expected behavior
Signing in like usual.
Steps to reproduce the behavior
Mandatory system details (please complete/update the following information)
Additional context
touchpad-indicator.log
Journalctl logs from the time-out instance: