YMMV, but this is what worked for me on Kubuntu 20.04 with Radeon Graphics.
Make sure you have told Steam to run all Windows games in Proton 5.
Install the prerequisites:
sudo apt install git cabextract python2 libudev1
Download and install media foundation workaround
mkdir ~/Downloads/bl3-mf/ cd ~/Downloads/bl3-mf/ git clone https://github.com/z0z0z/mf-install.git cd mf-install/ WINEPREFIX=”$HOME/.steam/steam/steamapps/compatdata/397540/pfx” PROTON=”$HOME/.steam/steam/steamapps/common/Proton 5.0″ ./mf-install.sh -proton cd ..
Download and install the media foundation cab workaround
At the time of this post, the installer seems to be pointing to a file on Microsoft’s website that doesn’t exist anymore. These steps will download a working file manually and rename it to what the script expects. If you see a 404 error, you can ignore. If not, then the script has been fixed to point to a good location now.
On the left hand side of the screen, choose Design & Deploy
You’ll see two tabs: Custom Modules and Policies.
The Policies tab has the custom settings used by the client (such as whitelisting, auto-starting, and auto-adding to groups).
Each custom module can only use one “Policy,” but each policy can have all possible settings. If you need to create a new policy, use the “Add policy” button at the top of the screen.
To change a policy, click the edit button next to the one of the policies. (The “enforce” checkbox for each setting prevents the end-user from being able to change that setting). These policies are checked by the client during installation.
Once the policy is setup, go to the Custom Modules tab. Create a new module with the Add Custom Module button or click the edit button on a existing module.
Customize the look of the TeamViewer app however you’d like.
Make sure the TeamViewer policy selected is the correct one from the Policies tab and you’ve selected the group you would like the devices added to under the “Automatically add computers to a group in your Computers list.”
Copy the API token and the Configuration ID. You will need these when creating the app in Intune.
Click the “Download MSI” link as well. Without any options, this MSI will just do a basic TeamViewer Host installation. Only when passed your configuration ID and API token during installation will it give you the customized client and add itself to your TeamViewer groups.
Package the Installer
The MSI file will come in a zip file; unzip it. Inside you will find two more folders: Full and Host. Go into the Host folder and copy the TeamViewer_host.msi file into another folder. I named mine “teamviewer-host”. Make sure there is nothing else in that folder.
Under Detection Rules choose “Manually configure detection rules”
Click + Add
Choose MSI for rule type. Intune will automatically enter the correct MSI Product code. Keep “MSI Product version check” as “no” so that the app won’t re-install if upgrades are done on the client side.
No Dependencies are needed.
Finally, assign it to whatever device groups you need. Devices in those groups will automatically download the TeamViewer Host app as well as place an icon called TeamViewer on the desktop.
That’s it! Your custom TeamViewer host should install on the selected devices and be ready for remote management.
I recently fired up Konsole and tried using tmux when I suddenly realized that Control-B wasn’t working.
Plasma, in one of their recent updates, seems to have added an “Add Bookmark” global shortcut to all Plasma apps mapped to Control-B. While it’s active, Control-B in Konsole won’t get sent to tmux, but will instead keep adding bookmarks to the Konsole Bookmarks menu.
Open System Settings Under “Workspace” choose “Shortcuts” Select “Standard Shortcuts” Find “Add Bookmark” in the list Change the Shortcut to Custom, then don’t assign a key sequence. This will set it to none.
Once changed, tmux should immediately start working again
I wish I could re-find the Unity Community article where I found this solution so I could credit the original source. If I find it I’ll link here.
Anyway, if you’re here you might be getting error 0x0000142 trying to run Unity Editor 2019.2.x in a virtual machine in KVM (or another hypervisor).
The culprit is openimagedenoise.dll
The fix is simple: Install any version of Unity Editor 2019.3.x (either directly or from the Unity Hub) and copy openimagedenoise.dll from the Unity Editor 2019.3.x folder to the Unity Editor 2019.2.x folder. Overwrite the existing file.
If you’re using Unity Hub that’s: From: C:\Program Files\Unity\Hub\Editor\2019.3.0b4\Editor\openimagedenoise.dll (Replace 2019.3.0b4 with whatever 2019.3 version you installed) To: C:\Program Files\Unity\Hub\Editor\2019.2.18f1\Editor (Again, replace 2019.2.18f1 with whatever 2019.2 version you’re using)
That’s it! Run Unity 2019.2 and everything should just work.
Or, can a man fall in love with KDE, 20 years later
KDE has never been able to capture my heart. I remember trying KDE 1.1 or so on Madrake Linux 6 in the late 90s. It just never clicked for me. I opted instead for Enlightenment. Ever since then, I’ve tried it every year or so to see if I could understand peoples’ love for it. I didn’t fall for KDE 3.5 that so many people remember fondly, or KDE 4, which people recall much less fondly. I’ve peeked in on KDE Plamsa 5 during it’s development, but it never was able to bring me in. But here I am, in 2019, about 20 years since I started using Linux, and I’ve giving KDE Plasma 5.16.4 a go!
So, why now? Well, as I said, I try KDE every now and then. Something about it always draws me in, before turning me off again. I recently ended up down an internet rabbit hole following articles on Plasma mobile, Qt Python bindings and even Qt C# bindings for .Net Core (and I love me some C#). I wondered: “Could Plasma, Plasma Mobile, Qt, and C# be the epic combo of my dreams?” Let’s find out!
I’m running KDE Plasma 5.16.4 on KDE Neon Linux. Neon is based on Ubuntu 18.04 LTS using KDE’s own, and constantly updated, repos for Plasma itself. I figured as long as I’m giving a fair shake, I ought to go right to the source. (As I’ve written this article, I’ve upgraded across a few versions of 5.x Plasma)
I’m running it on my trusty desktop with a Core i7 920, AMD Radeon RX 560, 12 GB RAM, a 512 GB SSD, and a HiDPI monitor at 3840×2160. It’s my daily driver at home for general computing, gaming, and game development.
I’m also running the X11 version of Plasma, rather than Wayland. I did some testing and Wayland seems to be particularly fluky with AMD graphics, though remarkably stable on the Intel-graphics based laptop I tested on. Your mileage may vary.
At work I use a Mac, so having the close, minimize and maximize icons on the left just keeps my flow going. I really thought this was going to be one of those “sorry, can’t do with Plasma” things. Oh, how wrong I was! In face, Plasma lets you customize all the icons on title bar.
I was able to connect a Bluetooth Microsoft Arc Mouse and my Apple AirPods without any difficulty whatsoever. Major bonus in my book!
One of things I love about Plasma is the decimal-based resolution scaling. Wheres the GTK-based desktops I’ve used require scaling at 1x, 2x, 3x, etc., Plasma allows you too choose, for example, 1.5x. This is a huge improvement for HiDPI displays.
The caveat is, you’re probably not going to be running all Qt apps. Invariably, you’ll also run some GTK apps as well. These will ignore your scaling. This was the case for me with Unity Editor.
Luckily, there’s an easy fix!
Find the app you need to scale
Prefix the command with: GDK_SCALE=2
While this isn’t an issue for me on my main computer, I did want to see how Plasma handled multiple monitors in case I’m able to get a 2nd display at home someday. Using a test laptop with Intel-based graphics I had no problem at all running Plasma with two 4K monitors daisy chained with DisplayPort.
One of the things that drives me crazy about Nautilus is that it doesn’t support the preview of PSD files out of the box. Perhaps there’s a plugin or setting somewhere, but not that I could find. I was thrilled to open a folder with a whole slew of PSD files and see previews of them working by default.
If you’re a lover of docks like I am, I can’t recommend Latte Dock highly enough! Latte Dock is integrated beautifully into the Plasma ecosystem, with all the fun stuff like pinning and app actions. For example, the Spotify app will give you playback options right from the dock icon.
Media over SMB
Dolphin (KDE’s file manager) does fantastic job of browsing SMB shares. It’s handy to be able to view shares without actually mounting them, but there’s quite a few drawbacks. Most frustrating was getting media to play when double clicking the file. I was eventually able to get it to work with VLC by using the snap version and dragging/dropping the file into the VLC window, but this still required me putting in my username and password for each video. My recommendation: mount the share, and everything works fine. I found smb4k recommended in a forum for this, and it does a fantastic job. Just make sure to exclude it’s default mount point, ~/smb4k, from your backup jobs.
Discover is Plasma’s app installation and system update tool. It’s gotten much better over the years (and even since I began writing this article), but can still be finicky. For example: if I search for ‘kmenu,’ I get nothing. It’s not until I search for ‘kmenuedit’ that I get a search result. I just seems by now that I should be able to do a partial search and good results.
I will say this about Discovery though, it’s ability to handle both apt and snap versions of packages is very convenient!
KRDC is a Qt-based remote desktop app for Plasma. It works great on a regular-resolution displays, but has some strange scaling issues for me on a HiDPI display and AMD graphics. I like to have a bunch of remote desktop sessions open at once, so I’ll typically have the remote desktop display be the current size of the client window. This works great in Remmina (the GTK equivalent of KRDC), but with KRDC I can never get it working quite right. (See below)
I’m sold! I started this article about four months ago wondering when I’d switch from Plasma back to Budgie. Now, I can say without a doubt that Plasma will remain my desktop of choice for the foreseeable future. Great job Plasma team!
I chose to install Linux on my 1st drive (sda). I’ll be using sdb for the ZIL, sdc for L2ARC, and sdd, sde, sdf, sdg, and sdh to for the data pool.
First, I’ll setup the data pool. This is where SSH is handy, since you can copy/paste your paths from above.
In my example below, I’m naming my pool “data.” You can use a different name if you’d like. If your setup is like mine, you’ll create one pool with many volumes in it.
I’m using drives with 4k physical sectors, so I’m adding the option: -o ashift=12 This should increase performance, but at the cost of total storage space. You an remove this option if you don’t think it’s a good fit for you.
For anyone who’s installed Ubuntu Server before, there’s not much here for you. I’m putting this here for anyone starting out with Ubuntu and for the sake of completeness.
Also, my 1st warning: this is the setup I think will serve me best for my particular situation. It may not be the best for you, and, while it’s somewhat redundant, it certainly isn’t “enterprise-grade.” You were warned 😉
In the steps below, anytime you see something in brackets, replace it with the correct value for your system, without the brackets. For example, if you see: ssh [username]@[ip address] You should really enter something like: ssh firstname.lastname@example.org
All the major Linux distros are awesome. You really can’t go wrong! For servers, I’ve typically gone with Centos in the past (and on this Ubuntu server will be many Centos virtual machines). However, there is one reason I’ve decided to go with Ubuntu in this instance: ZFS. Ubuntu has ZFS baked in, whereas Centos and Fedora require recompilation of kernel modules after major OS upgrades. Since I want this box to be as turnkey as possible (if it goes down, my internet will go down as well), Ubuntu it is!
First, download the Ubuntu Server iso from Ubuntu. I’ll be using the 18.04 LTS release, since I prefer to stick to LTS releases for critical infrastructure.
Next, either burn the iso to a DVD or image it to a flash drive. If you use the flash drive method, I recommend Fedora Media Writer. It’s available for Windows, MacOS, and Linux, and will image pretty much any Linux distro to USB.
Once you’ve got a bootable DVD or flash drive, boot from it. Most servers and workstations will tell you which key to press on the keyboard to get to your BIOS/UEFI boot menu.
After booting, choose *Install Ubuntu Server.
Choose your language.
Choose your keyboard layout.
Choose Install Ubuntu.
I’m going to use DHCP for now and set static IP later when I configure the virtualization networks for KVM. If you need to configure a static IP, you can do so here.
If you use an internet proxy, set it here.
Choose the default Ubuntu mirror.
I prefer to use LVM in case I need to resize partitions in the future.
I’ll be using one SSD as a boot volume. Choose whichever drive you’ll be booting from. I’ll be using all of the rest of the drives for ZFS, so I’ll leave them as they are for now.
By default, Ubuntu will only use 4GB of your drive for the root partition. Since all of my other data will live my ZFS volumes, I’ll expand the volume to use the whole 1TB.
To change the size of the root volume, use the down arrow to chose “ubuntu-lv,” press Enter, then choose “Edit.”
Ubuntu will helpfully tell you the max size you can set the partition to. Enter that number and choose “Save.”
Let Ubuntu know your name, your computer’s name, the username you’d like to use, and the password you’d like to use.
You now have the option of installing a secure shell server. This will allow you to log in remotely. I’ll be installing this.
You also have the option of installing some other services. You can always install these later. I’ll be skipping them and just choosing “Done.”
When the installation has finished, choose “Reboot Now.”
Remove the bootable DVD or flash drive and press Enter.
Once the server has rebooted, you can log in to the server itself or via SSH (if you installed SSH).
If you need to find out your server’s IP address for SSH, log in via the console and run the following:
Then on the computer you are using to SSH into the server run:
ssh [username]@[ip address]
Before anything else, let’s make sure everything is up-to-date.
sudo apt upgrade
Once that has completed, you may need to reboot.
KDE On a Server?
Let’s get right to it: it’s not considered security-wise to install a GUI on a server. However, I’ll be using things like Handbrake and Virtual Machine Manager, so I’ll be putting on KDE. To add a bit of security and save memory, I’ll manually start KDE when I need it.
To install just the very minimum of KDE (you can always add the other bits later), run:
I’m also going to install a couple other KDE apps to make my life easier. KDE’s Konsole terminal and the dolphin file manager:
sudo apt install konsole dolphin
If you want all of KDE, and have it start be default, you can simply run this instead:
sudo apt install kubuntu-desktop
If GNOME is more your thing, you can install it with:
sudo apt install ubuntu-gnome-desktop
If you install just the minimum KDE, your server will still boot in console mode. To start KDE, simply log in and run:
Since I’ll often want to use the UI remotely, I’m also going to install a package called xrdp. This will serve a desktop over the RDP protocol so I can get a desktop remotely:
sudo apt install xrdp
This will install xrdp, configure the service to start automatically, and start the service. Once it’s finished, you can connect to your server’s IP address via any remote desktop app and use the same username and password you use to log in locally.
Since my previous article Upgrading to PostgreSQL 10 on Centos 7 was so popular, I though I’d do a follow-up for anyone looking to upgrade a very simply configured PostgreSQL 10 server to PostgreSQL 11 on Centos 7.
First, and this goes without saying, backup your server!