Github projects

I’ve been slowly adding some of my sysadmin creations to Github. Most of them will be scripts, many for Active Directory. You can find the section in the sidebar linking to each project, or use my profile page here:

ErikLentz
12 repositories, 7 followers.

Error Upgrading Fedora 27 to Fedora 28 with Cinnamon desktop

When attempting to upgrade my Fedora 27 to Fedora 28 running the Cinnamon desktop, I received the following error:

dnf system-upgrade download --releasever=28
Before you continue ensure that your system is fully upgraded by running "dnf --refresh upgrade". Do you want to continue [y/N]: y
Last metadata expiration check: 0:00:00 ago on Wed 02 May 2018 11:19:35 PM CDT.
Error:
Problem: package gstreamer1-plugins-bad-1:1.12.4-3.fc27.x86_64 requires libchromaprint.so.0()(64bit), but none of the providers can be installed
- libchromaprint-1.2-8.fc27.x86_64 does not belong to a distupgrade repository
- problem with installed package gstreamer1-plugins-bad-1:1.12.4-3.fc27.x86_64

It turns out the name for this gstreamer plugins package has changed names, and it’s goofing up the dependencies path for libchromaprint. Minor issue, but it stops my upgrade cold.

I came up with this workaround: upgrade libchromaprint and gstreamer1-plugins-bad-free before trying to update the entire distro. So:

sudo dnf install libchromaprint-1.4.2-2.fc28.x86_64 gstreamer1-plugins-bad-free --releasever=28 --allowerasing

You can now proceed with your regular upgrade process.

VLC missing title bar and window decorations on Fedora 27

Recently, VLC Media Player on my Fedora 27 installation running the Cinnamon desktop has been missing the title bar and window decorations, resulting in VLC not being a proper window and only a full-screen application. For me, this behavior is undesirable.

VLC without title bar

To restore normal functionality it’s easiest to simply delete the VLC configuration:

rm -r ~/.config/vlc

Now, VLC will function normally. Preferences will have to be recreated, but if you’re like me, you don’t need much more than the ability to play media.

x11vnc – stack smashing detected

My x11vnc on Fedora has recently started crashing with the following error:

*** stack smashing detected ***: terminated

This issue seems to come and go for a lot of people with x11vnc. Bugs have been reported, but nobody seems to be able to pin it down. One workaround is to recompile it from source with some memory protections disabled, but that is a lot of work .

This workaround takes care of it: launch x11vnc with  -noxrecord on the end. That’s it!

Android cannot delete emails from IMAP server

I’ve been having an odd problem with being unable to delete emails from the Inbox of my self-hosted email account from my Android phone, using the Gmail app, using IMAP. When I would delete a message, a copy would be created in the Trash folder, but the original would remain in the inbox – when viewed from webmail. When I refreshed the inbox, the original would reappear on my phone.

At first, I thought the problem was permissions on /var/mail – so I did various changes such as chmod 1775, but to no avail.

I then remembered that I had recently re-setup my mail account on my phone, and realized that maybe it wasn’t using IMAP previously. So, I deleted the account, set it up again as POP3, and enabled server-side deletion. It worked!

It turns out that most mobile IMAP clients do not support the ability to achieve true server-side deletion. Using POP3 is an easy alternative and there is no harm. Yes, POP3 is an outdated and cruddy protocol, but in the end, it works.

Cannot run xiwi applications in Crouton

Recently on my Chromebook running Crouton, I’ve had trouble running applications using xiwi after entering my chroot. I would receive the following error repeatedly:

write_image: Cannot find shm, moving on…
find_shm: Cannot connect to findnacl daemon. (Connection refused)

I tried re-updating my chroot, checking drivers, reinstalling the crouton integration extension, and none of those worked, but this did:

  1. Enter the chroot
  2. Run the following command: chown -R 1000:1000 “$HOME”

Apparently, permissions can get messed up and stop xiwi from functioning properly.

Re-enable the certificate detail window in Google Chrome

Web Developers, Sysadmins, and their ilk lamented the day when Google decided to remove the detailed certificate window from Google Chrome. Now, it’s back. Here’s how:

  1. Put the following in the address bar: chrome://flags/#show-cert-link
  2. Click Enable
    Google Chrome - Click Enable

Crouton and Steam on a Chromebook Setup Guide

Update: I recently updated this walkthrough for Ubuntu Xenial instead of Trusty because that’s what I’m using now.

Update #2: A Chrome security update necessitates running a command on the Crouton script before running it the first time.

You might think that ChromeOS cannot run games that aren’t browser-based, and by itself you would not be wrong. But, with Developer Mode, a script called Crouton developed by a Google employee in his off-time, and a bit of effort, you can have a low-end laptop that runs both ChromeOS and an Ubuntu Linux desktop at the same time – without dual-booting. The way this works is that your device is always using ChromeOS’s Linux kernel, but you’re running a chroot (essentially a fake root file system) that contains everything needed to run software from Ubuntu.

This should be possible on any Intel-based Chromebook. On my Acer R11 CB5-132T-C1LK with an Intel Celeron N3150, 4GB RAM, 32GB Flash storage, I can smoothly play:

  •  Crusader Kings II
  •  Gemini Rue
  •  Papers, Please
  •  Pillars of Eternity
  •  Tyranny
    I haven’t tried anything twitchy, but I would assume only older titles will perform well. The newer (and cheaper) model of the Acer R11 has an Intel Celeron N3160 with Intel HD Graphics 400, making for a cheap, fast, long battery, netbook-like device that can still play games on the lower end of the spectrum.

Getting Started: Developer Mode

Note that Developer Mode completely wipes your Chromebook, so back up any files to Google Drive or elsewhere before getting started.

  1. Power your Chromebook off. Then press and hold ESC+Refresh+Power until you get a screen that says ChromeOS is missing.
  2. Press CTRL+D. Then press Enter. This turns OS verification off.
  3. The next screen will say that OS verification is off. You will see this screen every time you boot your Chromebook in Developer Mode. If you are concerned that another person will press the Spacebar and then Enter and destroy your little experiment, press the left arrow key a few times to change the language on this screen to something like Korean – this change will be saved for future boot-ups. Now only you will know how to boot your Chromebook and there won’t be instructions on the screen. To restore your Chromebook, all you need to do is press Spacebar then Enter on this screen.

Setting up Crouton

  1. Install the Crouton chrome extension. This lets you share a clipboard between ChromeOS/Linux and open URLs in Chrome.
  2. Go to this page and click the goo.gl link toward the top to download Crouton. Do not ever delete this file from your Chromebook’s Downloads directory and do not overwrite it. I’ll show you how to update it below.
  3. Press CTRL+ALT+T to open a terminal window. Type shell and press Enter.
  4. Type this command to bypass ChromeOS’s security lockdown on the Crouton file:

    sudo install -Dt /usr/local/bin -m 755 ~/Downloads/crouton

  5. Type in the following command to install Ubuntu Xenial with some Crouton targets (sort of like parameters):

    sudo crouton -r xenial -t xfce,keyboard,touch,extension

This will install the XFCE desktop environment, which is very lightweight. The ‘touch’ target is for if your Chromebook has a touchscreen – if yours doesn’t, omit this target. The ‘extension’ targets allows Ubuntu to talk to that Chrome extension you installed in step 1. The ‘keyboard’ target lets you use the Chromebook’s function keys – you will have to press the Search key before pressing VolUp/VolDown/BrightUp/BrightDown keys. I had some trouble getting audio while in the chroot, so I added the ‘audio’ target after the fact in my setup.

If you have a beefier Chromebook, you could use Gnome or Unity instead of XFCE, but because you’re wanting to game, the desktop environment with the lowest memory overhead would be best, and that’s XFCE.

Here is a Cheat Sheet of Crouton commands, which includes adding targets to existing chroots, backing up your chroot, and updating Crouton. Bookmark this!

Linux aficionados might ask why I recommend Ubuntu – because it’s the most commonly used and widely supported in the Crouton community, and because game developers primarily seem to target Ubuntu for Linux game development. Personally, I prefer Fedora on my Thinkpad, but I use Ubuntu on my Chromebook. You might also wonder why I don’t recommend xiwi (X in a Window) instead of having the full overhead of a XFCE environment: game performance in xiwi is absolute crap. Only Papers, Please and Gemini Rue were playable in xiwi.

The Ubuntu installation can take a long time, depending on your Internet connection.

Starting Crouton and installing Steam

  1. Once your chroot is set up, from the terminal tab type in: sudo startxfce4
    You will need to type this into a terminal tab each time you want to enter Ubuntu!!!!
  2. Congratulations, you’re in Ubuntu! To switch back to ChromeOS, press CTRL+ALT+Forward on your keyboard. You can use this to switch back and forth from Ubuntu to ChromeOS.
  3. Disable the screensaver in XFCE. It can cause graphical glitches and resume problems.
  4. Download TrueType fonts by entering into Xterm: sudo apt-get install ttf-ubuntu-font-family
  5. Update Ubuntu’s software: sudo apt-get update && sudo apt-get upgrade
  6. Install some basic tools (text editor, archive manager): sudo apt-get install file-roller gedit
  7. (Optional) Install VLC media player: sudo apt-get install vlc browser-plugin-vlc
  8. And Finally, install Steam:

 wget http://media.steampowered.com/client/installer/steam.deb

sudo apt-get install gdebi-core

sudo gdebi steam.deb

If you’re a Linux regular, you can also install games from .deb files, compile from source, or install Wine and run Windows executables, but I won’t cover that here because other guides on how to do this in Linux will cover it better.

Updating Crouton

You should update Crouton after each ChromeOS update. Since I’ve been using it, I’ve never had a ChromeOS update actually cause a problem with running Crouton, but it might and it’s best to keep it up to date. Because the developer essentially builds this on his free time, it might take a couple of days for an update to come out after a ChromeOS update with major changes. To update both Crouton and your chroot:

 sudo crouton -u -n chrootname

Adding Additional Storage

Most other guides don’t cover this, but I find it critical to running Steam games on a Chromebook. Your chroot environment is taking up a fair amount of space on your Chromebook’s internal storage, so you’re probably going to want to install your Steam games to an SD card. I’m using a 64GB SDXC UHS Speed Class-1 card and it performs fairly well, and was only about $25. Before you can add the SD card as a Library Folder in Steam, however, there are some hoops to jump through because ChromeOS does not mount SD cards in executable mode – so you can’t run games off of them.

  1. Insert your SD card and make sure it’s a format that ChromeOS can write files to. Format it if necessary.
    2. Eject the SD card from ChromeOS, but leave it in the slot. Enter Crouton.
    3. On the desktop, find the see-through icon for your SD card (they should be listed by size), double-click it to mount it. Open the SD card and make note of the mount location in the address bar. It should be something like: /media/[linuxusername]/[letters and numbers]
    4. Open an Xterm window and type: mount
    5. Find your SD card in the listing there by looking for the Device ID and where it mounts. The line looks like something like this:
    “/dev/mmcblk1p1 on /media/[your username]/[sequence of letters-and-numbers]”
    You want both the /dev/ information and the /media text!
    6. Back on the desktop, right-click it and Dismount
    7. Back in the Xterm window, type: vi mountsdcard
    8. Press the letter ‘i’ on your keyboard, modify the following to match your variables from above, and write it into the file:

sudo mkdir /media/[linuxusername]/[letters and numbers]

sudo mount -o rw,nosuid,nodev,relatime,seclabel,data=ordered,uhelper=udisks2 /dev/[deviceid] /media/[linuxusername]/[letters and numbers]

  1. Press Esc. Press : and enter: wq
  2. Enter into the terminal window: chmod +x mountsdcard
  3. To mount your SD card, enter: sudo ./mountsdcard

So, to recap, the process you need to follow every time –  before launching Steam needs to be:

  • Dismount the SD card from ChromeOS
  • Press CTRL+ALT+T to open a terminal tab.
  • Enter: shell
  • Enter: sudo startxfce4
  • Open Xterm and enter: sudo ./mountsdcard
  • Open Steam.

From this point, you can create a Steam Library Folder on the SD card and install your games. Once you’re done playing your game, log out of Crouton and physically eject and re-insert your SD card to see it again in ChromeOS. If your Chromebook goes to sleep, it will dismount your card, so do not allow your Chromebook to go to sleep while Steam is running or otherwise you will have to close Steam, Dismount, run mountsdcard, and possibly re-add your Library Folders.

Please refer to the Crouton Command Cheat Sheet to learn how to backup your chroot. Backing up from time to time can save you if an update breaks something, but I’ve been running my chroot since December without a backup and haven’t had any trouble.

If you want help with your specific situation and setup, you can ask me here and I can try to help you, or you can ask the collective minds at the Crouton subreddit – they will probably be able to help with more complex questions than just me.

WordPress ‘HTTP Error’ image upload workaround

On a couple of my WordPress sites, I’ve encountered an HTTP Error when trying to upload media. I tried many solutions: increasing PHP’s memory allocation, changing file permissions, using GD instead of Imagick, adding lines to my functions.php, etc. None of them worked.

But I found a workaround. A simple plugin called Add From Server allows you to add media to that is already uploaded to your website’s server. So, all I need to do is upload the files to my server, add the media from there, and go about my business.

It’s not a true solution, only a workaround, but it’s a more-than-adequate workaround until WordPress can find a singular solution to this elusive error.

Update: Moving from a Debian 7 to Debian 9 VPS seems to have eliminated this problem.

Postfix: TLS is required, but our TLS engine is unavailable

Recently, emails sent from my Postfix mail server to my Gmail account were getting tagged as ‘insecure’. Come to find out, they were no longer sending with TLS. They were defaulting back to open SMTP over port 25. Why? Because Debian’s ca-certificates.crt had updated and that removed the CA needed to make my site’s certificate valid – and I use that same certificate to encrypt my TLS SMTP traffic.

First, to diagnose the problem, I forced TLS in my main.cf and turned on TLS logging with the following settings:

smtp_enforce_tls=yes
smtp_tls_loglevel=1

I then restarted Postfix with:

sudo service postfix restart

After restarting, Postfix provides the following error in its logs when attempting to send email:

TLS is required, but our TLS engine is unavailable

Earlier in the log file, it indicates a failure to load the CA file that validates the cert and key files. So, here’s the solution:

  1. Make sure your cert and CA files are located in /etc/ssl/certs
  2. Run the following command: sudo update-ca-certificates –fresh
  3. Then go to your Postfix main.cf and verify the following lines are there (and comment out any conflicting lines):
     smtpd_use_tls=yes
     smtp_use_tls=yes
     smtpd_tls_CAfile=/etc/ssl/certs/ca-certificates.crt
     smtpd_tls_cert_file=/etc/ssl/certs/YOUR_CERT.crt
     smtpd_tls_key_file=/etc/ssl/YOUR_PRIVATE_KEY.key
     smtp_tls_CAfile=/etc/ssl/certs/ca-certificates.crt
     smtp_tls_key_file=/etc/ssl/YOUR_PRIVATE_KEY.key
     smtp_tls_cert_file=/etc/ssl/certs/YOUR_CERT.crt
     smtpd_tls_security_level=encrypt
     smtp_tls_security_level=encrypt
  4. Restart the Postfix service again.
  5. Send an email to an @gmail.com address – you should no longer see the unlocked icon under the sender information.