Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#77856 - [code] 1.76.1-2 unable to launch
Attached to Project:
Community Packages
Opened by Hanabishi (Hanabishi) - Tuesday, 14 March 2023, 21:54 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Wednesday, 15 March 2023, 08:52 GMT
Opened by Hanabishi (Hanabishi) - Tuesday, 14 March 2023, 21:54 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Wednesday, 15 March 2023, 08:52 GMT
|
DetailsDescription:
code 1.76.1-2 is broken and unable to launch. /usr/bin/code: line 35: /usr/lib/electron/electron: No such file or directory Obviously something went wrong with this update and there should be electron19 instead. Additional info: * package version(s) code 1.76.1-2 |
This task depends upon
Closed by Massimiliano Torromeo (mtorromeo)
Wednesday, 15 March 2023, 08:52 GMT
Reason for closing: Fixed
Additional comments about closing: code-1.76.1-3
Wednesday, 15 March 2023, 08:52 GMT
Reason for closing: Fixed
Additional comments about closing: code-1.76.1-3
Whitespace breaks the sed script here. It should be:
sed -i "s|name=electron|name=$_electron|" ../code.sh
Sadly, I am now having trouble rebuilding code due to open-vsx.org being down: https://github.com/EclipseFdn/open-vsx.org/issues/1684
Executing `sed 's/^name=electron$/name=electron19/' -i /usr/bin/code` can be used to manually fix the issue other than downgrading to code-1.76.1-1