-
Notifications
You must be signed in to change notification settings - Fork 96
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
seg fault #600
Comments
Yea, any logs would be useful. I've been seeing segfaults occasionally on some people (I have yet to get one) with no rhyme or reason as to why. |
Where would I find any hyprpanel logs? |
Two ways, you can either:
|
Ah in that case it's unfortunately not super useful. The only thing output is the standard |
You don't happen to have other notifications daemons running right? dunst, mako sway-nc, etc? |
Also is there anything else surrounding the segmentation fault? Could you also share your |
No other notification daemons running. I'll grab the journal logs when I can and post them. |
And no, nothing else output prior to the crash 😕 |
BTW, could you share with me your hyprland version please? |
Here's the stack trace from journalctl.
And here's the output of hyprland --version (I did also just update before reproducing this again)
|
Same problem here, this is the first time I'm trying hyprpanel.
|
@EduuG That null error is because of an incorrect type in Astal. Not related to Hyprpanel. These segfaults are interesting. I had someone else running into the same issue and their status update is:
What I'm curious about it
Looks like some Astal hyprland workspace issue? Another user had the same origin (Astal Hyprland) for the segfault. |
@EduuG Could you please share your segfault core dump as well from your journalctl? I'm wonder if it's related to hyprland service. |
Sure, here it is:
|
Yeah, Astal Hyprland in all the instances of a segfault. Other people had an issue with this on the Astal github, so I'm pushing a fix that hopefully fixes it for now until an upstream fix is added. |
@evogelsa @EduuG Could you please update all your Astal service in additional to hyprpanel via:
And let me know if you're still running into this issue. I have opened an issue on Astal for this: Aylur/astal#213 Will keep you posted. |
Updated everything again this morning and still hit the seg fault. This one looks unrelated to the hyprland service in the previous ones.
|
Reproduced while running hyprpanel interactively and again there's nothing else useful logged other than the seg fault itself and g-icon being deprecated. |
This seems to fix the problem for me, haven't encountered any issues since. Thank you! |
@EduuG's comment made me go double check everything. It turns out that had I forgotten I built and installed hyprpanel from source, so the binary in |
Closing for now. We can reopen if this is an issue again but I think we've found that upgrading libastal fixes these issues. |
Describe the bug
Running hyprpanel results in a segmentation fault
To Reproduce
Run hyprpanel
Expected behavior
No seg fault
Screenshots
N/A
Desktop (please complete the following information):
Additional context
Hyprpanel will run for a bit (up to a couple minutes) before seg faulting, but it's not consistent, sometimes it happens right away, sometimes it's longer. This started occurring after I made the upgrade from agsv1 to astal/agsv2. There are no other errors seen when running hyprpanel from the command line. I was able to reproduce with the default config as well as my customized config.
If there are logs or other bits of useful information I can provide let me know.
The text was updated successfully, but these errors were encountered: