etcher
etcher copied to clipboard
balena-io
Debian Testing has removed gconf2 packages.
- Etcher version: 1.18.12
- Operating system and architecture: Debian Gnu/Linux Testing
- Image flashed: N/A
- What happened: Install filed because dependency is not satisfiable: gconf-service
gconf2 is used for gtk2 application and is an archived project. https://gitlab.gnome.org/Archive/gconf
modern application like gtk3 and gtk4 use dconf. https://gitlab.gnome.org/GNOME/dconf
https://github.com/balena-io/etcher/issues/2019#issuecomment-363366530
And here we are in 2023
Ubuntu 23.10 is no longer packaging gconf2, gconf-service and this is breaking the .deb
Looks like this is related to https://github.com/electron/electron/issues/2727 so maybe this problem will be "automatically" fixed when Etcher moves to a newer version of Electron?
Looks like this is related to electron/electron#2727 so maybe this problem will be "automatically" fixed when Etcher moves to a newer version of Electron?
I wonder version if Electron is being used now. Electron removed gconf 4 years ago; the change happened in Electron v7.0.0-beta.1.
As of today, the latest non-beta of Electron is v25. Unless I'm making incorrect assumptions, hard to imagine Etcher is using Electron older than v7.
Edit: @lurch According to CHANGELOG.md:9 Electron is already at version 25.
> # v1.18.13
> ## (2023-10-16)
>
> * patch: upgrade to electron 25 [Edwin Joassart]
> * patch: refactor scanner, loader and flasher out of gui + upgrade to electron 25 [Edwin Joassart]
@aethernet with the highest amount of respect for your time and resources, is the removal of gconf2 as a listed dependency something you are able to look into or point directions for?
@XrayBravoGolf Ahh, good sleuthing! :detective: In that case, I don't know why Etcher still needs gconf2 - I was only providing my best guess as an "outside observer" :slightly_smiling_face:
Its a shame that etcher continues to be unmaintained. it took 1 year and 4 months for this bug https://github.com/balena-io/etcher/issues/3647#issuecomment-1249473908 to be resolved so that etcher could launch on modern disros
looks like after approaching 6 months this current issue is still unfixed that prevents etcher from even being installed on modern disros. guess we will have another year to wait until maintainers fix this one too. not sure why the developers don't archive this repository if they don't have interest in maintaining it, at least then it would clearly signal that users should move onto other software or someone should fork.
This is still happening with 1.19.4 ... The compilation process shoulda failed altogether, so why this is even possible I don't think I wanna know.
Also affected by this issue.
+1
Had to go back to 1.7.9 which still works
The Balena Etcher package definitions state to include gconf - see here where these're defined:
https://github.com/balena-io/etcher/blob/37618ce2fd7cdbc8c26d0fdb4e91f393acfacbab/package.json#L109:L110
If lines 109 and 110 were removed or replaced with dconf-specific packages instead, this would fix the .deb files. This requires, however, that the Balena Etcher team determines if there are any hard dependencies on the now deprecated gconf components.
This is independent from Electron upstream changes, and something Balena has to change in the code.
the now deprecated
gconfcomponents.
correction. it is not "now" deprecated. It was deprecated in 2014 (10 years ago). https://wiki.gnome.org/Initiatives/GnomeGoals/GSettingsMigration It is now finally being removed after 10 years of deprecation by OSs since this has given ample time for developers to remove this dependency from their applications. Etcher has not acted on the 10 years of deprecation notice.
