question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Issue with libicu on Ubuntu

See original GitHub issue

Ubuntu 19.04 npm@6.10.2 node@v12.8.1

Error when running npm start:

eli@ubuntu:~/react-nodegui-starter$ npm start

> react-nodegui-starter@1.0.0 start /home/eli/react-nodegui-starter
> tsc && qode ./dist/index.js

/home/eli/react-nodegui-starter/node_modules/@nodegui/qode/dist/1.0.0/qode: error while loading shared libraries: libicui18n.so.60: cannot open shared object file: No such file or directory
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! react-nodegui-starter@1.0.0 start: `tsc && qode ./dist/index.js`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the react-nodegui-starter@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/eli/.npm/_logs/2019-08-15T19_53_15_146Z-debug.log

Full log:

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/home/eli/.nvm/versions/node/v12.8.1/bin/node',
1 verbose cli   '/home/eli/.nvm/versions/node/v12.8.1/bin/npm',
1 verbose cli   'run',
1 verbose cli   'start'
1 verbose cli ]
2 info using npm@6.10.2
3 info using node@v12.8.1
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle react-nodegui-starter@1.0.0~prestart: react-nodegui-starter@1.0.0
6 info lifecycle react-nodegui-starter@1.0.0~start: react-nodegui-starter@1.0.0
7 verbose lifecycle react-nodegui-starter@1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle react-nodegui-starter@1.0.0~start: PATH: /home/eli/.nvm/versions/node/v12.8.1/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/eli/react-nodegui-starter/node_modules/.bin:/home/eli/.nvm/versions/node/v12.8.1/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/local/go/bin:/home/eli/go/bin:/usr/local/go/bin:/home/eli/go/bin
9 verbose lifecycle react-nodegui-starter@1.0.0~start: CWD: /home/eli/react-nodegui-starter
10 silly lifecycle react-nodegui-starter@1.0.0~start: Args: [ '-c', 'tsc && qode ./dist/index.js' ]
11 info lifecycle react-nodegui-starter@1.0.0~start: Failed to exec start script
12 verbose stack Error: react-nodegui-starter@1.0.0 start: `tsc && qode ./dist/index.js`
12 verbose stack spawn ENOENT
12 verbose stack     at ChildProcess.<anonymous> (/home/eli/.nvm/versions/node/v12.8.1/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
12 verbose stack     at ChildProcess.emit (events.js:203:13)
12 verbose stack     at maybeClose (internal/child_process.js:1021:16)
12 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
13 verbose pkgid react-nodegui-starter@1.0.0
14 verbose cwd /home/eli/react-nodegui-starter
15 verbose Linux 5.0.0-25-generic
16 verbose argv "/home/eli/.nvm/versions/node/v12.8.1/bin/node" "/home/eli/.nvm/versions/node/v12.8.1/bin/npm" "run" "start"
17 verbose node v12.8.1
18 verbose npm  v6.10.2
19 error file sh
20 error code ELIFECYCLE
21 error errno ENOENT
22 error syscall spawn
23 error react-nodegui-starter@1.0.0 start: `tsc && qode ./dist/index.js`
23 error spawn ENOENT
24 error Failed at the react-nodegui-starter@1.0.0 start script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:1
  • Comments:10

github_iconTop GitHub Comments

1reaction
a7ulcommented, Aug 16, 2019

Alright! Latest version of NodeGUI nodegui@0.1.3 has the fix for linux environment. I had missed few dynamic libraries. Just take a pull of this repo do npm install and npm start

and it should work! @elilambnz, @Bo-Duke, @gustavsl

0reactions
a7ulcommented, Aug 16, 2019

Closing this issue. Please re open if the issue persists.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to install libicu-dev on Ubuntu - Stack Overflow
You have to re-install this libicu, I solved this problem on ubuntu 22: apt purge libicu-dev libicu; apt update; apt install libicu-dev libicu....
Read more >
Ubuntu – Package Search Results -- libicu
You have searched for packages that names contain libicu in all suites, all sections, and all architectures. Found 13 matching packages.
Read more >
apt - install libicu-dev libicu-dev:i386 at the same time produce ...
It is normal behaviour. If you compare the filelists of both packages obtained from https://packages.ubuntu.com/bionic/libicu-dev you will ...
Read more >
Cannot install amd64 and i386 versions of libicu-dev in ...
On an x86-64 machine with Ubuntu 18.04, I've tried to install both 64 ... logs: $ cat /etc/issue.net Ubuntu 18.04.1 LTS $ uname...
Read more >
libicu-dev_66.1-2ubuntu2_arm64.deb
Download libicu-dev_66.1-2ubuntu2_arm64.deb for Ubuntu 20.04 LTS from Ubuntu Main ... Issue Tracker, https://bugs.launchpad.net/ubuntu/+source/icu ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found