bazecor: init at 1.3.6

[amesgen]

Description of changes

Adapted from the chrysalis derivation.

Things done

• Built on platform(s)
  • x86_64-linux
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• Fits CONTRIBUTING.md.

[dotlambda]

Please squash.

[dotlambda]

Did you try building from source? There are already a few electron apps using yarn in nixpkgs. You could copy from those expressions.

[amesgen]

Did you try building from source? There are already a few electron apps using yarn in nixpkgs. You could copy from those expressions.

No, I just adapted the chrysalis derivation and thought it would be nice to upstream it; I might look into building it from source in the future when I have time.

[gvolpe]

@dotlambda I did try to build from source a while ago, got stuck with some Electron dependency: Dygmalab/Bazecor#370

[nixos-discourse]

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/prs-ready-for-review/3032/2733

[gvolpe]

@amesgen does this work for you on NixOS? I'm just trying it out and get this error:

Electron's autoUpdater does not support the 'linux' platform
CHECKING BACKUP FOLDER VALUE /home/gvolpe/Dygma/Backups
[4302:1009/151524.287338:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.portal.Desktop was not provided by any .service files

Not sure if this is relevant or not, but the Update Firmware option just gives me a blank screen and it seems stuck there. Also, I can't access the configured layers on my Defy either...

[amesgen]

@amesgen does this work for you on NixOS?

Yes, it works well for my Raise, but I have to reboot after installing it for the first time before it works; otherwise, I get behavior similar to what you describe. Maybe it is enough to restart some udev-related services (but just restarting systemd-udevd.service does not do it) in order to get away without rebooting.

[gvolpe]

@amesgen thanks, I'm still looking at it, might need to raise an issue with them directly. It doesn't work at all with my Dygma Defy (just arrived today), even after restarting my OS 😭

EDIT: I've raised Dygmalab/Bazecor#525, might be helpful to other Defy owners on Linux...

[gvolpe]

@amesgen FWIW I managed to fix my connection issues (details on the issue linked above). TL;DR I needed different udev rules.

[gvolpe]

@amesgen if interested, I came up with a workaround to remove the annoying udev rules check on startup 😄

EDIT: This PR should make it easier if accepted: #261190

[amesgen]

@amesgen if interested, I came up with a workaround to remove the annoying udev rules check on startup 😄

EDIT: This PR should make it easier if accepted: #261190

Thanks, integrated 👍

[gvolpe]

@Artturin I've already approved this two months ago, would be nice to get it merged, thanks 🙏🏽

[azuline]

thank you!!