How to fix a package that is broken or not fully installed?

After running apt update && apt upgrade -y on an virtual machine, I am getting the following error for libssl1.1:amd64.

dpkg --configure -a Setting up libssl1.1:amd64 (1.1.1-1ubuntu2.1~18.04.2) ... Checking for services that may need to be restarted...done. Checking for services that may need to be restarted...done. Checking init scripts... dpkg: error processing package libssl1.1:amd64 (--configure):  installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 Processing triggers for libc-bin (2.27-3ubuntu1) ... Errors were encountered while processing:  libssl1.1:amd64  dpkg-reconfigure libssl1.1:amd64 /usr/sbin/dpkg-reconfigure: libssl1.1:amd64 is broken or not fully installed 

Here is my server information,

uname -a Linux remote 4.15.0-1040-aws #42-Ubuntu SMP Fri May 17 13:47:10 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux  cat /etc/os-release NAME="Ubuntu" VERSION="18.04.2 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.2 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic 

This is a vital package to any Linux distribution, I cannot simply uninstall it and then reinstall it.

Recovering Files from Broken Screen Nexus 5x

I have a Nexus 5x that has an unresponsive and broken display (screen displays colored lines and doesn’t respond to any touches) that I am trying to get files off of. I can’t seem to get my computer to recognize it, presumably because you need the phone to be unlocked, but i cant get through the lock screen without touching the display. Is there any way to unlock my screen through recovery mode or something without wiping it? Thanks!

Fixing broken update-motd.d folder and files on headless ubuntu ssh server

Short story I was trying to fix the
motd .d files so that they would display when booting up ssh on my android device and I used an online tutorial to try to fix them.

Now I am unable to test them by typing in run-parts /etc/update-motd.d because I keep on getting the following errors. run-parts: failed to exec /etc/update-motd.d/00-header:Exec format error

run-parts: /etc/update-motd.d/00-header exited with return code 1

run-parts: failed to exec /etc/update-motd.d/10-sysinfo: Exec format error

run-parts: /etc/update-motd.d/10-sysinfo exited with return code 1

run-parts: failed to exec /etc/update-motd.d/90-footer: Exec format error

run-parts: /etc/update-motd.d/90-footer exited with return code 1 .

Typing in systemctl status motd I get this on my screen

motd.service   Loaded: masked (/dev/null; bad)   Active: inactive (dead)   

Magento 2 getting error “Broken reference: The element with the “customer” ID wasn’t found. Verify the ID and try again. [] []” in system.log

I am getting lots of

Broken reference: The element with the "customer" ID wasn't found. Verify the ID and try again. [] [] 

errors in the error.log. I’ve googled around and tried to trace it with NetBeans but I can’t track down what’s causing it. Everything seems to be working perfectly except this error is getting written repeatedly.

Has anyone any idea what’s causing it or how I might track it down?

As some background, I migrated my site from 1.8.1 to 2.3 (and have since upgraded to 2.3.1 but the error started in 2.3). I wonder if something hasn’t migrated correctly. Note it occurs in both developer and production mode.

How to fix broken dependency: software-properties-common : WD MyCloud

While installing software-properties-common in my Western Digital MyCloud NAS server, I came up with the following issue. I would like to revert the installation but I am facing following issue. Can anyone suggest a workable solution to remove this.

Reading package lists... Building dependency tree... Reading state information... You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies:  libc-bin : Depends: libc6 (< 2.18) but 2.19-18+deb8u10 is installed  libstdc++6 : Depends: gcc-4.7-base (= 4.7.2-5) but it is not installable  libtirpc1 : Breaks: nfs-common (< 1:1.2.8-7) but 1:1.2.6-4 is installed              Breaks: nfs-kernel-server (< 1:1.2.8-7) but 1:1.2.6-4 is installed 

My sources list are as follows:

cat /etc/apt/sources.list deb http://ftp.us.debian.org/debian/ jessie main ## Note, wheezy is not 64K page aligned. ##deb http://ftp.us.debian.org/debian/ wheezy main #deb http://ftp.us.debian.org/debian/ sid main #deb http://ftp.us.debian.org/debian/ experimental main 

I tried some typical answers that I browsed online. sudo apt-get -f install gives following error.

... (Reading database ... 26996 files and directories currently installed.) Preparing to unpack .../libc-bin_2.19-18+deb8u10_armhf.deb ... Unpacking libc-bin (2.19-18+deb8u10) over (2.17-93) ... dpkg: error processing archive /var/cache/apt/archives/libc-bin_2.19-18+deb8u10_armhf.deb (--unpack):  trying to overwrite '/etc/ld.so.conf.d/libc.conf', which is also in package wd-lib 01.05.02-7ee92da Errors were encountered while processing:  /var/cache/apt/archives/libc-bin_2.19-18+deb8u10_armhf.deb E: Sub-process /usr/bin/dpkg returned an error code (1) 

Any pointers to get this fixed?

How to bypass/authorize ADB RSA key with broken touch AND screen?

First of all, I tried a lot of hours with everything I could find on the internet and mostly on StackOverflow.

Something I’ve already tried with no avail:

https://stackoverflow.com/questions/51082608/is-it-possible-to-authorize-adb-on-my-android-phone-with-a-broken-screen

https://stackoverflow.com/questions/26213954/how-to-solve-adb-device-unauthorized-in-android-adb-host-device

https://stackoverflow.com/questions/25236960/running-adb-devices-showing-unauthorized-device

Both screen AND touch are broken so I can’t see nor touch a thing. (So the OTG mouse option can’t be used in my case.)

Device is a Huawei Ascend P7 L10, Lollipop 5.1.1.

It’s rooted.

It has TWRP recovery.

USB Debugging is enabled.

I’m using the latest ADB version, updated from Android Studio.

I entered recovery mode, done adb push adbkey.pub /data/misc/adb/adb_keys and rebooted, after reboot adb keeps saying devices isn’t authorized. I rentered recovery checked if file copied on device was still the same as the one in .android folder, and it was, same key.

If anybody has any idea I’m all ears. Thanks in advance.