-
-
Notifications
You must be signed in to change notification settings - Fork 267
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
Recurrent segmentation fault #1131
Comments
Does it segfault as soon as the Given that gnome 46.2 is pretty new it may be a new gtk-related bug. There's another broken accounting issue (#1093) but it did not create segfaults. Can you long press on the canvas with your finger to check if the right click menu appears (or broken accounting messages appear) ? I'll test on my side if I can reproduce things on the latest gtk version (I think it'd be 4.14.4-2) |
I don't have time to give bug reports. I don't have a keyboard for my tablet, so it would be extremely tedious. But I think I might be having this issue. When I am using the latest Fedora Workstation with GNOME DE on wayland, the app crashes after several seconds of drawing. I didn't see anything about segfault in the debug log. |
Can you check again on 0.11 ? Might be a gtk issue that's fixed in 4.14 |
I have the same problem with my Wacom tablet on Hyprland with For me, the problem only occurs in the "Artist Mode" of the |
I haven't really used the app all that much recently as I'm on vacation now, but I did try it a couple times and I haven't found this issue again. I can confirm it properly once my classes come back next month, but as of right now it seems fixed. |
Well, my classes are back now and I've been using the app again for a little over 2 weeks now. What I can say for sure: the app is still crashing and giving the same segmentation fault. I haven't had the time to investigate the issue properly, but from my usage I noticed some things: 1. It seems to be somehow related to the palm rejection.I noticed in some of the crashes that the following sequence of events is very common:
2. Saving the file manually before it fully crashes can prevent itWell, this is where it gets weird to me. After a couple of these crashes, I started to notice the freezing before it fully crashed and closed the window. So, during one of my classes the following happened:
After that, every time I noticed the app stopped responding, I clicked the save button manically and it somehow saved it every single time! So, from this I learned that it wasn't the entire window that was freezing (hence my use of "" on the times I mentioned it before). Instead, only the canvas stopped responding, the rest of the window was still fine. I don know if any of this information helps at all and I could even be mistaken (specially on the palm rejection thing, that's honestly more of a feeling I have), but I hope it helps. I will try to investigate it a little more if I have he time, but for now that's all I have. |
Does it immediately fail when using the pressure level ? It may be an issue somewhere in the chain that triggers a segfault at that line : rnote/crates/rnote-ui/src/canvas/input.rs Line 393 in fbd056c
If it's the case this means that gtk4 never populates the field (probably a null pointer ...) Does |
Can you check whether this happens on 0.11 (and with the same symptom and workaround as #1131 (comment)) ? |
@lucas-yotsui From what you're describing, my guess is that it does not matter which button you click that isn't the canvas itself. Now I'm not sure which one. At least that can be tested (disable some or all of them, test, and go from there) |
The program keeps crashing due to a segmentation fault. It was previously crashing due to the rendered issue described in #1061, however I began to set
GSK_RENDERER=gl
whenever I opened the app and it solved this problem. However, I am now getting a recurrent segmentation fault, as can be seen in the screenshot below.To Reproduce
Steps to reproduce the behavior:
GSK_RENDERER=gl rnote
Expected behavior
Run without issues (and preferably without having to set
GSK_RENDERER
manually, like Doublonmousse/rnote@215a68e).Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: