lzma_stream_encoder_mt_memusage missing from dpkg-deb - dpkg

Recently, after an interrupted dist-upgrade, I've been experiencing some issues with dpkg-deb.
Most frequently, I get one specific issue:
dpkg-deb: relocation error: dpkg-deb: symbol lzma_stream_encoder_mt_memusage, version XZ_5.2 not defined in file liblzma.so.5 with link time reference
The message is very clear, but it's not clear to me how this should be fixed.
I've tried reinstalling liblzma5 from the default 17.10 PPAs, with no dice.
I've also tried to apt install --reinstall dpkg, also to no effect.
I've tried installing liblzma5 from source and updating my $LDPATH to reflect the new build's path, but I'm not sure which flags to use to export the missing symbol; a plain ./configure && make && make install doesn't seem to.
How can I fix this issue?

I was able to fix this by copying the file /lib/x86_64-linux-gnu/liblzma.so.5.2.2
from a machine already upgraded to bionic.

Related

Gnome “settings” not working on Fedora 34

Since I upgraded to Fedora 34, I noticed I’m not been able to open Gnome settings.
Right-clicking on wallpaper and selecting “Settings”, “Display Settings” or “Change background” have no effect either. The mouse pointer changes to a loading alike icon and returns to arrow icon after a while.
I searched web looking for this error, but i wasn’t able to find a solution. Thinking it may be some kind of conflict, I ran:
sudo su
dnf clean all
dnf -y distro-sync
dnf remove --duplicates
dnf update
This removed duplicated packages and updated them, but had no effect on the problem.
I managed to resolve it this way: I tryed to run gnome-control-center and got the following error message.
gnome-control-center: error while loading shared libraries: /lib64/libwebpdemux.so.2: file too short
Since this error usually indicates a broken .so file, I reinstalled the thing it belongs to, in this case that's libwebp.
sudo dnf reinstall libwebp
That resolved the problem.

warn Package undefined has been ignored because it contains invalid configuration. Reason: Cannot find module 'undefined/package.json'

In my app.json folder, I have everything bundled nicely, but I have one undefined package at the bottom of the install list:
"undefined": "react-navigation/bottom-tabs"
I tried running an "npm install react-navigation/bottom-tabs" but it threw this error:
warn Package undefined has been ignored because it contains invalid configuration. Reason: Cannot find module 'undefined/package.json'
Has anyone encountered an issue like this before? I am running React-Native Version 5 on top of Expo.
EDIT: It turns out that it was supposed to be #react-navigation/bottom-tabs, so I installed that and made an adjustment; but now I am still stuck with the original undefined package in my app.json folder, and cannot get rid of it.
So, I forgot this post existed and I actually figured this out months ago. When you're dealing with:
A bad bundle,
the wrong version,
or there's just something wrong with your 'package.json' file, (the file that contains the list of your packages)
These steps should fix it:
Perform "npm uninstall 'package-name' " or "yarn remove 'package-name'"
Note: You do this instead of 'expo-uninstall' because 'expo-uninstall' does not exist. We use 'expo-install' instead of 'npm' or 'yarn' install to make sure you download the proper npm or yarn version associated with your version of expo.
Open the package.json file and see if the bad package you uninstalled is still present.
If the bad package is still there, select and delete it from the file, then save.
Run an "expo" "npm" or "yarn" install on the correct package name
This should fix it. This is best fixed when step 4 is executed with an 'expo install' as you likely have an incompatible version of the package, so this will prevent that from happening again.
In my case, I couldn't figure out why my terminal was telling me a specific package didn't exist, so I did a "sud" command to force download the package. This package didn't exist, because I had actually spelled it wrong.
try deleting your node modules and install them again and make sure your metro is closed
clear cache and you are good to go by the way it worked for me
npm install or yarn add
npm start --reset-cache

Resolving Homebrew warnings without causing adverse effects

I am having issues installing mysql with Homebrew and have ran brew doctor to try and get to the bottom of it.
The advice given is always to resolve the warnings/errors presented by Homebrew, however I do not want to cause adverse side-effects on my system by doing so.
As I understand it, the node errors are likely caused by installing Node manually and not with Homebrew. I'm not sure what the git unlinked keg is about.
What is the safest way to resolve these errors?
CRMPiccos-MacBook:~ crmpicco$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!
Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.
Unexpected header files:
/usr/local/include/node/node_internals.h
/usr/local/include/node/smalloc.h
/usr/local/include/node/v8stdint.h
Warning: You have unlinked kegs in your Cellar
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
git
As I understand it, the node errors are likely caused by installing Node manually and not with Homebrew.
I don’t know where these files come from but if you’re afraid of removing them you could just move them somewhere then move them back if they’re needed.
I'm not sure what the git unlinked keg is about.
git is installed but not symlinked into standard locations like /usr/local/bin and friends. Programs that depend on that specific git installation thus can’t find it. You should either run brew link git or brew rm git if you don’t have any formula that depend on it.

Error while installing Octave

I am trying to install Octave on OS X. When executing brew install octave I get the following error:
octave: A LaTeX distribution is required to install.
You can install MacTeX distribution from:
http://www.tug.org/mactex/
Make sure that "/usr/texbin", or the location you installed it to, is in
your PATH before proceeding.
I downloaded and installed MacTeX but it is still not working :(
How can I fix this?
If you want to avoid the MacTeX dependency you can install Octave with brew as follows:
brew install octave --without-docs
"Make sure that "/usr/texbin", or the location you installed it to, is in
your PATH before proceeding."
This message may be the hint of the answer for you.
You need to set the PATH so that the Tex could be called from anywhere in your system.
Adding the following line in the .bash_profile may fix it.
export PATH=$PATH:/usr/texbin/
The reason why the texlive command does not work have also same cause on this.

PhpStorm is not starting up

I just downloaded PhpStorm 5 on my quite fresh ubuntu.
During the first start I installed a couple of plug-ins.
Now - after the installation of those plug-ins - PhpStorm is not starting up anymore.
No splash screen is showing up. No error gets written on the terminal:
gue#ubuntu:~$ phpstorm
Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
gue#ubuntu:~$
What shall I do with that drunken sailor?
I can't find any logfiles, no configuration file/directory in my home directory.
Since I'm used to Eclipse I've no clue where to look for a trace in this IntelliJ derivate...
If you're on Windows deleting the following directory helped me:
C:\Users\<user>\AppData\Roaming\JetBrains\
Some plug-ins can cause problems and prevent IDE from starting, if it happens, you should delete the directory containing plug-in manually. Location of this directory depends on the system and product, details are available in the FAQ.
For PhpStorm on Linux it would be ~/.WebIde50/config/plugins.
This happend to me too, I had created a custom vmoptions file, and entered incorrect values. I fixed it by deleting it in ~/.WebIde50/phpstorm.vmoptions
i had the same problem , i fixed it just with removing the file C:\Users\.PhpStorm2016.2
In linux, I fixed it by deleting vmoptions file of PhpStorm and then launching it again:
mv ~/.config/JetBrains/PhpStorm*/phpstorm64.vmoptions ~/.config/JetBrains/PhpStorm*/__phpstorm64.vmoptions
It might be possible if openjdk is installed then phpstorm not opened.
So remove first then follow steps that given in below link.
I solve the problem same way.
wiki.jetbrains.net/intellij/Installing_and_running_PHPStorm_on_Ubuntu
Here is how you fix this: Rename C:\Users\USERNAME.PhpStorm2016.3 to something else (anything, like PhpStorm2016.whatever) , it will start the program if you click on the phpStorm icon, then choose to import settings, and you're good to go ;)
I am using PhpStorm2020.2.1. I referred to Configuration directory. I accessed the folder %AppData%\JetBrains\PhpStorm2020.2, renamed it just in case I may need some files in future.
Voila! I can start my PhpStorm2020.2.1 again!
I had this problem yesterday and my OS is windows 10. phpStorm suddenly did not work and when I click on it nothing happened. I just downloaded JDK from this link (https://www.oracle.com/java/technologies/javase-downloads.html) and after installation, I set the environment value in the system setting for my java directory. You can use this link to set the environment (https://javatutorial.net/set-java-home-windows-10)
For me I had to remove all cache for the IDE located in:
~/.cache/JetBrains/
I have changed the VMOptions under the Help menu on MacOS and it just would not start up again. It just silently failed every time. I found the file at /Applications/PhpStorm.app/Contents/MacOS/phpstorm and ran it in the terminal, which gave me an output with the following error:
Invalid ReservedCodeCacheSize=3072M. Must be at most 2048M.
Luckily, it also gave me the path to the VMOptions file in one of the rows of the output, parseVMOptions: /Users/barnabas/Library/Application Support/JetBrains/PhpStorm2022.3/phpstorm.vmoptions in my case, so I could change it back to a valid configuration. Crisis averted.
Simple
Go to your task manager
end any task on php-storm
and restart the ide again
it will work
Open Terminal Linux Ubuntu 20.10
YOU#USER:~$ cd ~/.config
YOU#USER:~/.config$ ls
Obs: Locate the >>> JetBrains <<< folder, after that delete it your default app settings will disappear more it will open again
YOU#USER:~/.config$ sudo rm -rf JetBrains/
Open PHPSTORM