-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
xournalpp / xournal++ crashes at startup #63715
Comments
Do you have an icon theme installed? |
I don't know, so maybe not.. |
Installing |
I'd be happy to take a fix to xournalpp here, but I'm not quite sure what the best approach is. My understanding is that GTK+ itself is what's crashing if the "image-missing" icon isn't found - see here. As I understand it, we have the following options:
|
I haven't had the chance to test it, but if anyone else wants to: here's an example of a Nix derivation for an icon theme that only contains the |
Why isn't
The obvious solution? It is still possible to set another icon theme locally (if using |
I guess it's mostly a question of icons are large (ish) and we don't want to install unnecessary icons. I am pro the image-missing solution, provided we also document it somewhere (not sure if NixOS manual is the best place, could apply to non-NixOS nix installations, so the Nix manual). Also, the |
This is indeed the primary reason, see the discussion in #43150.
Customization is still possible (the theme used will be still the one set in profile, defaulting to Adwaita), the closure is the main concern.
I talked with GTK devs on IRC a few days ago and they also said that GTK should use the image-missing from GTK and the source code looks like that is what should be happening but to no avail. Actually, it seems to somewhat work – try running
Brilliant idea. This would be an acceptable compromise, I think, until it is fixed in GTK. We should probably use
We might still want something like this to let users know they should install an icon theme. But we can worry about that once we prevent the crash. |
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use Git blame or GitHub's web interface on the relevant files to find them. Lastly, you can always ask for help at our Discourse Forum or at #nixos' IRC channel. |
This is still an issue. |
Just in case, the same problem with MyPaint (#54677), it crashes at startup. |
I marked this as stale due to inactivity. → More info |
I really cannot reproduce the crash neither at startup, nor with |
Seems to work for me now. I don't know what has changed. Should I close this or is it still an issue for someone? |
I still have this problem. |
Try #159902, maybe it helps. |
@sikmir I cannot reproduce the problem anymore. Good catch! |
Hello, this is still an issue for me! On a NixOS unstable 23.11 install with KDE Plasma. Same error as original post:
|
installing the |
Thanks. I can confirm that it solves the issues. But if it is a known requirement/dependency for so long already shouldn't the xournalpp package install it in the first place? |
Issue description
Xournalpp crashes immediately.
Steps to reproduce'
I don't have KDE nor GNOME installed in case that matters.
Technical details
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste theresults.
The text was updated successfully, but these errors were encountered: