-
Notifications
You must be signed in to change notification settings - Fork 75
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
TimeApp prevents to lock screen under gnome-shell 3.30 #75
Comments
Should be fixed now. Let me know whether it works. |
@ludenticus Any news? |
After installation of the git version, it worked... However it has a critical bug: this new version prevents to lock screen. It took me a while to realize this was the culprit. It happens under GDM with Wayland and Xorg. Whenever you lock the screen (manual or automatic), gnome-shell crashes and sends you to the GDM login screen. It doesn't let you blank the screen |
Ahh. Not good.. Could you debug it with journalctl? |
I have similar problem. Here are my logs with only timeapp extension active Log:
|
@mgrabowski84 @ludenticus Could you check in the latest github version? I think I might have fixed it. |
@zagortenay333 Checked really fast and I still have same issues. |
Can I see a log? |
@mgrabowski84 Srry for bothering you, but I fixed another thing that might be very related to you specific crash. Would you mind downloading the github version again? |
Log:
|
I tried your latest git, and the problem is still there... However, it seems to be related with tracker. Maybe Nextcloud Client? Log:
|
Same behavior without Nextcloud Client or Wi-Fi, or even with the |
No, that can't have anything to do with timepp. The issues is that here: https://gitlab.gnome.org/GNOME/gnome-shell/blob/master/js/ui/popupMenu.js#L887 ..the boxpointer.actor is referenced when you lock the screen and doesn't exist. I am not exactly sure why; haven't looked into it yet. Btw, please post the logs on sites like pastebin and link it here, or wrap it into a dropdown like I did above; pasting the full log here clutters the comments. |
Here we go again. Could you guys try it now? I tweaked something again which might be related. |
Sadly, same thing |
@mgrabowski84 Could you get rid of these lines and try again: and line 60: https://github.com/zagortenay333/timepp__gnome/blob/2ee1257cbfb29dd5ed6844ad7f138b82993dcf40/extension.js#L60 |
Nope. No luck |
@ludenticus No luck with what? Did you comment out the lines above? |
I'm sorry. I was in a hurry after trying the latest version, but anyway I wanted to report back. I downloaded the git version and commented out lines 60 and 71-107 of |
Hmm, that error report can't cause the crash; it's just a warning.. No idea what's going on here. So to recap, the error happens when you lock the screen? Have you tried disabling the extension via tweak tool and seeing whether it crashes or shows any errors? Also try disabling various sections (alarms, timer, todo..) to see if any one in particular is the culprit. |
As a matter of fact, I only have the Todo section enabled... Error happens whenever screen tries to go blank: it doesn't matter if you do it manually (Meta + L) or gnome-shell triggers it automatically (after X minutes). |
Try disabling the todo section and enabling another one. See if you still get the error. |
Even with all sections disabled, TimeApp prevents the screen to go blank. One thing I haven't mentioned: once I enable TimeApp, it isn't enough to disable the extension or even log out. Instead, I need to disable and reboot. |
@ludenticus I didn't quite understand what you said there. Does it crash when you disable timepp from the gnome-tweaks tool or only when you lock the screen? |
TimeApp prevents the screen to go blank. That's the bug I face enabling the extension. To successfully disable the TimeApp extension it isn't enough to disable it from gnome-tweaks or via extensions.gnome.org. It isn't enough either to log out and log in, because gnome-shell continues to crash whenever the screen tries to go blank, even though TimeApp extension is supposed to be already disabled. That's why, after enabling TimeApp and facing crashes due to the bug, I need to
|
Do this:
|
What you asked @zagortenay333 After that, I disabled all extensions but TimeApp and reboot... It doesn't work anymore: |
How frustrating.. I still can't tell what's wrong. OK, try this:
|
As a matter of fact, after the latest reboot TimeApp in Tweaks and Chromium displays the same error message: |
Do what I said above. The errors you're showing are symptoms I'm afraid; I need to figure out what the cause is. |
OK, finally got a chance to install 3.30. I think this should be fixed now. Please let know if it works @ludenticus @mgrabowski84 |
Latest git works as intended. Bug seems to be solved |
Good to hear. |
Extension is broken.
lg
displays the following message:The text was updated successfully, but these errors were encountered: