-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
[BUG]: "Type of Bar: Trilands" crash after logout #63
Comments
Hello, Oh no, the weird shell crash issue! These can be hard to crack. I am also using 'Trilands' and have tested on Ubuntu 24.04 and Fedora WS 40 with Gnome 46 Wayland and Open Bar 38 but haven't faced this issue. While Ubuntu is on Gnome 46.0, Fedora is on 46.4, same as you, but the kernel versions are ahead with 6.8 and 6.10. Are you using Panel blur with Blur My Shell?
I believe Super+L locks the screen which leads to a crash, so Gnome shell will restart (but not a logout as such, right?)
What do you mean by options? Like regular login vs recovery mode or regular vs previous version of the kernel?
That could be the case since such issues do exist but something seems to be triggering the scenario since it only happens with 'Trilands' for you and yes similar case is also reported for 'Candybar'. That's the weird part that it is OK otherwise.
Command to apply the patch: Let me know if this helps or not. Also, could you please try to get a stack trace for the crash with the Logs app (if present) or journalctl, so we can see if it matches the shell/mutter issue? Thank you for reporting! |
No, I have this option disabled.
I just tried logging out without using the short cut (no locking screen) and it caused a crash... So it's most probably something with Gnome crashing (option in OpenBar was Islands, so it's not a problem with the extenstion it seems)
I mean the GRUB boot options, the second option is "Advanced options for Arch Linux" and then I choose "Arch Linux with linux-lts" or something like that and I can log in. It doesn't seem to be connected to OpenBar issue.
I've tried out Candybar and it also caused a crash.
After installing the fix the extension becomes unusable for me. The command to apply the patch made the extension unusable for me, it blocked the extension with info "An error occured when loading this extension" or something like that (I'm not using english in the system). I deleted the package from extensions directory and reinstalled it again and it works, so it seems that this fix actually causes some interference with my current state of the app. journalctl logs of the last few boots, latest one with and Trilands turned on, errors only:
|
So, it seems the issue is same as the Candybar one, at least the same cause. The stack trace is similar to the shell/mutter issue being tracked here. There is a MR but for some reason it is still open.
This is unexpected. Maybe the command didn't finish well. I wanted to try skipping some steps on disable in an attempt to bypass the crash scenario. Can you instead try this -
Let's see how that goes. Thank you! |
I just tried using Trilands as the Type of Bar and it worked! I don't see any error messages from the journal, only some warnings which aren't connected to the extension. it seems to have fixed it <3 What was the reason for the problem then? |
That's great news! Can you please also try with Candybar to check if that doesn't crash as well?
Well, the main reason is still shell/mutter issue associated with stylesheet unload. But it was specifically getting triggered for Trilands and Candybar. Those are special styles so I have to add additional style classes to each panel button. When we do screen lock, Gnome disables the extensions. On disable we need to clean up anything that extensions has touched. So I remove these style classes. This isn't really necessary since the entire stylesheet is unloaded anyway. So I commented this part. And that's it. Now the fun part: As I was typing the above explanation, one more thing struck me, in terms of why it maybe a problem. When we lock the screen, the Panel is also changed by Gnome. Without digging deep, it seems the left and center boxes are removed and only the Quick Settings is kept in the right box. This may create that scenario of trying to remove something from memory that doesn't exist. This should not cause a crash, given it is only style class, but with some combination of upstream issue and the timing of events (since it does not happen for me for e.g.) it might happen. Thanks for trying out! |
Ok, just letting you know. I'm still playing around with my environment and Arch is being more and more of a pain, but now that I've tried the fix it's not working anymore, which is really surprising for me. Both Type of Bar: Trilands and Candybar. I think I'd need to just do a clean install and check it out again, just having the OpenBar extension installed. I don't have time for deeper digging today, therefore I'll try to give an update in upcoming days. Edit: I think it would be a good idea to just setup a VM instance of Arch with same config, just going straight into installing OpenBar, and then adding up the things that I've installed (it's not a lot, but small things can make a big mess). With that I'll be able to conclude whether this is the extension affecting the basic setup (like an upstream issue you mentioned or something else) or it's an incompatibility between some packages. I'll try to keep this environment as is to be able to further troubleshoot the issue. |
Oh, that's unfortunate. It would be great if we have a way to dodge the crash till upstream is fixed. Yeh, that's a good idea to try in a fresh setup in VM and then add other packages/extensions. Do replace the Feel free to update here when you have some results. |
Update: I have changed the way Trilands is implemented in an attempt to avoid the crash scenario. This might solve it. Let me know if that works for you. |
I'm also having this issue with triland, where it crashes after suspending, on fedora 41, gnome 47 and I'm on 41 of the extension. |
I'm facing a similar problem as in #35, but with different circumstances. What I've found is that when using "Type of Bar: Trilands", whenever I lock my screen using Super + L (which causes a logout as well), it crashes my system, and all I see is blackscreen with console cursor blinking. However, when changing "Type of Bar" to "Islands", the issue seems to be solved.
I expect that it might be related to Gnome/mutter issue, as I've faced something similar previously, but now it seems to be a problem with that particular function (other Bar types don't cause a crash). It also doesn't allow me to boot using standard "Arch Linux" option, and I need to go through with second boot option (it looks to be a GRUB issue). But after changing to "Type of Bar: Islands" I can boot normally, so I believe it also may be a matter of compatibility with OpenBar, therefore creation of this issue.
Versions/Specs:
Reproduce:
I don't have an error trace. If you want me to run some command to troubleshoot, let me know. I'll try to respond and be of help!
The text was updated successfully, but these errors were encountered: