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#32221 - [nodejs] nodejs-0.8.12-2 and v8, npm install results in segmentation fault

Attached to Project: Community Packages
Opened by mojo (mojo) - Thursday, 25 October 2012, 16:46 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Thursday, 15 November 2012, 05:39 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Bartłomiej Piotrowski (Barthalion)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
Straight up update via pacman -Syu

Installing any node module with npm results in a segmentation fault. eg:

$ npm install buffet
npm http GET https://registry.npmjs.org/buffet
npm http 304 https://registry.npmjs.org/buffet
npm http GET https://registry.npmjs.org/buffet/-/buffet-0.4.6.tgz
Segmentation fault

Workaround is to downgrade to previous version (without v8 dependency)
nodejs-0.8.12-1

Additional info:
architecture: x86_64
nodejs-0.8.12-2-x86_64.pkg.tar.xz
v8-3.14.0-1-x86_64.pkg.tar.xz


Steps to reproduce:

npm install <node module>
or
npm install -g <node module>
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Thursday, 15 November 2012, 05:39 GMT
Reason for closing:  Works for me
Comment by Bartłomiej Piotrowski (Barthalion) - Thursday, 25 October 2012, 17:35 GMT
I'll try to debug it first, to the end of the week I'll fix the problem or revert latest changes.
Comment by Thomas Bächler (brain0) - Friday, 26 October 2012, 15:52 GMT
I don't know much about nodejs, but it segfaults when I run etherpad-lite and try to access a pad. Downgrading to -1 fixes the problem.
Comment by mojo (mojo) - Friday, 26 October 2012, 20:54 GMT
@Barthalion: Before you spend time debugging it, perhaps it was fixed in the latest version of node? Current Version: v0.8.14. Then try npm install something :)
Comment by Tom (reztho) - Saturday, 27 October 2012, 12:00 GMT
https://projects.archlinux.org/svntogit/community.git/commit/trunk?h=packages/nodejs&id=b51b8b9166e03b07e031141f6c3b6c62012d4c13

I managed to fixed it here. Just change the find/sed lines related with fixing the python2 name to the previous ones and it will work. If you don't do that, it won't work, even with the new version of node. Some of the new sed lines should be wrong or missing.


Comment by Bartłomiej Piotrowski (Barthalion) - Saturday, 27 October 2012, 12:51 GMT
@mojo: It wasn't, npm still throws a segfault.

@Tom: Reverting find-related lines doesn't change a thing, at least for me.
Comment by James Cleveland (antihero) - Wednesday, 14 November 2012, 23:54 GMT
  • Field changed: Percent Complete (100% → 0%)
It still segfaults when using r.js?
Comment by Bartłomiej Piotrowski (Barthalion) - Thursday, 15 November 2012, 05:14 GMT
That's very cool but 1) works for me 2) it doesn't segfault on any of my machines. Provide logs next time.

Loading...