Community Packages

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!
Tasklist

FS#62207 - [code] stopped working after upgrading electron from 3.1.6 to 4.1.1

Attached to Project: Community Packages
Opened by Igor (igvalor) - Monday, 01 April 2019, 15:20 GMT
Last edited by Filipe Laíns (FFY00) - Saturday, 06 April 2019, 16:05 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Filipe Laíns (FFY00)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description: VS Code launches but shows blank window.

Additional info:
* package version: 1.32.3-1

Steps to reproduce:
Updgrade electron from 3.1.6 to 4.1.1.
Try to launch code.

Workaround: downgrade electron back to 3.1.6
This task depends upon

Closed by  Filipe Laíns (FFY00)
Saturday, 06 April 2019, 16:05 GMT
Reason for closing:  Fixed
Additional comments about closing:  code 1.33.0-1
Comment by Rémi Bourgeon (remicmacs) - Tuesday, 02 April 2019, 07:05 GMT
I had the same problem and came to the same workaround.

If someone needs it I can provide two startup logs : one with the new electron and another after downgrade.

The logs are generated with `code --verbose > stacktrace 2&>1`

With `diff` I could see immediately the errors that had gone away with the downgrade. But they're weird node stacktraces and I don't know anything about Electron so I don't understand anything about that.
Comment by Yaohan Chen (hagabaka) - Friday, 05 April 2019, 10:15 GMT
I built the package locally, and that fixed the problem. I think the cause of the problem is that electron was updated to 4.x in [testing], but code has not been updated in [community-testing], so the code package in the repo is built with the wrong version of libraries for [testing] users.

While building, I needed to install nodejs-lts-dubnium and replace nodejs with it as `makepkg --syncdeps` asked.

Also I needed to quit VSCode before testing the new package, because otherwise it would simply ask the current running process to open a new window.

Loading...