[BUG] GUI installed dependicies problem
See original GitHub issueDescribe the bug
./install-gui.sh
apt-get is /usr/bin/apt-get
Reading package lists... Done
Building dependency tree
Reading state information... Done
libxss1 is already the newest version (1:1.2.3-1).
libxss1 set to manually installed.
nodejs is already the newest version (15.14.0-deb-1nodesource1).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
nodejs : Conflicts: npm
npm : Depends: node-gyp (>= 3.6.2~) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
To Reproduce Should install
Expected behavior Installation should work
Desktop (please complete the following information): Additional context Add any other context about the problem here.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Trouble installing GUI dependencies with Zsh [SOLVED] #325
Hi, I ran into a small problem with install this morning and wanted to mention it ... so installing the gui dependencies with...
Read more >How to Prevent and Fix Package Dependency Errors in Ubuntu
It is possible to have broken packages and unmet dependencies, especially when you are installing multiple packages at once. The command below will...
Read more >dependency problem - PINE64 Forum
Hello All, I just got the new Pinebook Pro and probably somehow screwed the dependencies on first software install attempt (vi, mutt, ...
Read more >apt - How do I resolve unmet dependencies after adding a PPA?
One of the most basic fixes to resolve dependencies problems is to run: sudo apt-get -f install. The -f here stands for “fix...
Read more >Unable to resolve dependency tree error when installing npm ...
You have dependency conflict (incorrect and potentially broken dependency) as it says, so try to run the command with --force , or --legacy-peer ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve had the same issue. Ubuntu 20. I’ve tried multiple methods to fix this and nothing seems to work. Thus far I’ve tried reinstalling Node and NPM as well as downgrading libxssl. Which is not a good idea, but I was just trying to get the error to go away.
Any suggestions? How can I help? Here’s the complete error:
Using NVM and commenting out that line did not work for me. Says it can’t find NPM now
I’ve reinstalled Node, NPM, NVM. Removed NVM completely. Still no luck. Very frustrating because this was working before I updated Node with NVM