Error message

I was trying to install Epic Games on my Lutris installation on my old laptop and ran into the following error message:

Exit with return code 256

(This appears to be a common issue and is not necessarily limited to Epic Games.)

I actually removed my default Ubuntu package which was a few minor versions behind the official packages. I then installed the latest version of Lutris directly using a .deb file from their website.

An ASUS ROGSTRIX B450-F gaming motherboard that I have had been working perfectly fine for a year. Suddenly though, booting up the system resulted in the following message on the POST boot screen:

USB Device over current status detected !! System will shut down after 15 seconds

The system would shutdown and restarting would result in the same message. I couldn't get into the BIOS either as the del and F2 keys did nothing.

So I tried playing a video on Netflix in Firefox and while everything worked including the previews while hovering over a title, the actual movie/TV episode failed to play and resulted in the following error:

Playback Error Code: F7701-1003

The main thing that needs to be done is to enabled DRM support in Firefox's preferences section. (Look for a checkbox titled "Play DRM-controlled content".)

I ran into this error today while running a python program in Kubuntu 18.04 (upgraded from 17.10):

qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method

followed by a bunch of other similar SSL-related errors. When I checked apt, I found that my openSSL install was fine. A generous guy on IRC informed me that I was very likely missing libraries that the app was looking for. S/he asked me to try installing libssl1.0-dev and voila, it worked.

IOW, run sudo apt-get install libssl1.0-dev to fix the issue.

So, when I got home yesterday, I found that my Samsung microwave was beeping frequently for no apparent reason. Switching it off and back on did fuck all and occasionally I'd see the clock display read "5E" or "SE". This issue didn't go away even after a few hours and I'd resigned myself to having to go through the rigmarole of calling a service center and getting this fixed which would undoubtedly involve charges amounting to a good chunk of the microwave's original price. Of course, that wasn't what I did.

I just ran into the following error while trying to commit (a previously working project) in Eclipse Neon:

svn: E200007: Commit failed (details follow):
svn: E200007: Commit failed (details follow):
svn: E200007: CHECKOUT can only be performed on a version resource [at this time].
svn: E175002: CHECKOUT request failed on '/svn/foo/!svn/rvr/1337/trunk/site/bar.example'
svn: E200007: Commit failed (details follow):

If you encounter,

Could not back up sites directory for drupal

when trying to back up a site using Aegir, then this is because there are some permission issues with some of the files in the sites directory.

In my case, these files were in the private/temp/ directory. Listing all offending files can be done by the following command:

find . | grep private/temp/

If anything other than the usual .htaccess file is found, then that is probably a likely culprit. Checking file permissions should confirm this.

Edit: Skip this and scroll down for a proper fix!

Just tried installing MongoDB support for PHP on Kubuntu 15.10 via pecl and ran into the following error message which caused the installation to fail:

configure: error: Cannot find OpenSSL's libraries

While this can probably be fixed using some magickery, in my case, I did not want SSL support on a dev server. I just wanted to get the fucker up and running. To this end, I discovered that the issue was that I was using:

pecl install mongodb

If you run into the following error while adding a project into Eclipse from existing source using the New Project dialog,

Cannot create project content in workspace.

then you are very likely trying to create a new Eclipse project that contains Eclipse metadata files from a previous Eclipse project created at the same location. The fix for this is to import this pre-existing project into your workspace using the Import, General, Existing Projects into Workspace option.