Noah Kirschmann

> (edit: ...and, finally, another thing that might be worth trying: if you send me your binary, I can try and see what happens if I run it locally. It...

> The only difference seems to be that I'm on 3.24 for gtkmm, but I thought I tested it on 3.22 systems before as well... it might be worth asking:...

> I just pushed a commit that should remove all valgrind memcheck errors that notekit throws, if the build is correct. Could you merge that into your repository and see...

> Could the problems when running the binary directly be caused by the version mismatch? After all, if I understand correctly, we haven't managed to run the snap itself with...

> Oh, you mean you built it directly with cmake . and make against the containing system's libraries? I assumed from one of your earlier posts that you just unpacked...

> (though it's odd that it would wind up using the same path as both the default notes path and the resource path; I might need to revisit the logic...

> I'm really at a loss as to what to do about the issue with text not being displayed, though, since I can't reproduce it on any system I have...

> . The overlay can probably be disabled safely by finding, in notebook.cpp, the line that says add_child_in_window(overlay,Gtk::TEXT_WINDOW_WIDGET,0,0); and commenting it out. This might be worth a try either way....

The current snap build has one problem. Every time a new document is opened or created, the whole program crashes with a segmentation fault. Edit: Despite this I published the...

> I probably should've spotted this when merging Glad you found the issue and fixed it again. However the program now crashes with a segmentation fault when I try to...