Skip to content
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

ssb-patchwork 3.17.7 crashing when clicking on icon "Chose profile image..." #93246

Closed
alciono opened this issue Jul 16, 2020 · 4 comments
Closed

Comments

@alciono
Copy link

alciono commented Jul 16, 2020

The bug
ssb-patchwork crashing when clicking on icon "Chose profile image"

To Reproduce

  1. After starting the app click on "Profile".
  2. Click on "Edit Your Profile".
  3. Click on icon "Chose Profile Image...".
  4. The app crashes and disappears all together...

Expected behavior

Expecting to be able to add an Image and keep editing the profile.

Notify maintainers

Metadata

  • system: "x86_64-linux"
  • host os: Linux 5.4.51, NixOS, 20.09pre234242.c71518e75bf (Nightingale)
  • multi-user?: yes
  • sandbox: yes
  • version: nix-env (Nix) 2.3.7
  • channels(root): "nixos-20.09pre234242.c71518e75bf"
  • channels(k): ""
  • nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos
@mkf
Copy link
Contributor

mkf commented Nov 23, 2020

It fails with

(ssb-patchwork:2): GLib-GIO-ERROR **: 13:07:02.956: Settings schema 'org.gtk.Settings.FileChooser' is not installed

Which appears to be fixable just the way it was fixed in #84449 in commit d89ed04, that is, by adding wrapGAppsHook in the arguments and in the nativeBuildInputs

I would like to add that I see all kinds of programs that use image/file choosers crash upon attempting to open such, one other example being, iirc, Zim (the local desktop wiki software). Clearly we have a repetitive issue there, that should probably be adressed in a more abstract way.

@mkf
Copy link
Contributor

mkf commented Nov 23, 2020

Mentioning maintainers: @asymmetric @NinjaTrappeur

@picnoir
Copy link
Member

picnoir commented Nov 23, 2020

Thanks for pointing this out. This issue is however a duplicate of #76743

Potential fix:

I currently work around that by lauching ssb-patchwork from a terminal. It seems to inject the appropriate gsettings schema.

Help welcome :)

@mkf
Copy link
Contributor

mkf commented Nov 23, 2020

I currently work around that by lauching ssb-patchwork from a terminal. It seems to inject the appropriate gsettings schema.

@NinjaTrappeur The way I obtained the error message was by launching it from a terminal. It clearly doesn't do that for me. I use awesomewm and xterm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants