Well, about a year ago, I purchased a System76 Oryx 10 Pro Linux laptop. Outstanding decision. It’s a killer laptop with incredible performance. It’s my daily driver, so I needed speed, lots of storage, a 4K display and the ability to run a second 4K display. The Oryx 10 delivers! Moving from a desktop box to a high-performance laptop proved incredibly providential as we’ve been pretty mobile this year.

System 76 uses their own PopOS! with their Gnome-based desktop. I put OpenSUSE KDE on the laptop, which I ran on my desktop, when I received it, but the system is clearly optimized for the Gnome-based desktop. So, I went back to the Gnome-based desktop and migrated from KMail to Thunderbird. Thunderbird 115 is finally everything I wished it to be and am now very happy with it. I keep the mail, calendar, and task tabs handy to swap between. Setting up the DAV calendars was simple and reliable.

System76 is moving to their rust-based COSMIC desktop in the next year, and I’m looking forward to it. In the meantime, I’m enjoying Thunderbird 115.5 on my Oryx 10 Pro.

I wrote in my previous post that I had reached Nirvana with Kontact and my Google accounts. Well, not so fast. I had to re-add my Google calendars and that triggered Google’s persistent security permission alerts again – every three hours! This time I couldn’t get them to stop. I tried everything I did before, rechecked everything, and exhausted Google’s online help system. I’m a Google One customer, so I chatted with their tech support. A very patient young lady worked the issue for almost an hour, but in the end had no answer. I filed a comment with the Google engineers, but remained frustrated by the persistent alerts. The email accounts still work fine, but not the calendars.

That was it for me. I only use two calendars – my personal one and a shared one with my wife for joint operations. They are both Google accounts. I determined to free myself from Google’s arrogant labeling of non-Google programs as “less secure apps.” The good news is that I already had the resources required.

I moved to a new website/email host, Hostway, earlier this year because of their superior inbound and outbound spam filtering. They also use Open-Xchange (OX) Suite for online access, which is pretty slick. I simply had to upgrade two of my email accounts to Collaboration level to get CalDav capability for their associated calendars.

For KDE and Kontact, I added my CalDav account to the Online Accounts. To obtain the CalDav link, I simply looked in the Properties on the OX web app. I then added my calendar to Kontact. I created the joint email account and shared that calendar with my email account. When Kontact put the primary account in the Calandar Management window, it included the shared calendar as well. So far, so good.

I then exported the contents of both Google calendars to .ics files, then imported them to their respective new homes in OX Suite online. It took a few minutes to import my larger calendar, but then all was golden. I disabled the two Google calendars in Kontact, and no more permission security alerts! After ensuring proper operation with the new setup, I deleted the Google calendars from Kontact.

That left the Android phones. Following the Hostway help page here, I added both my primary and the joint account as Exchange accounts. In the calendar app, I simply deselected the Google calendars and selected mine. Bingo! Piece of cake.

Now I have control of my calendars and associated security. We have full function access in Kontact on my desktop, web access on my Chromebook, and in the calendar app on our Androids. It isn’t free, but it’s not much and well worth it. I’m in control now.

We still use the Google accounts for some email, and they work fine for now. If that ever goes south, I can drop them in favor of my own email accounts on Hostway.

As the Who sang, “I’m free, and freedom tastes of reality.”

I’ve been using Mozilla Thunderbird for well over a decade. I started with it during my final Windows days, then stayed with it when I moved to Kubuntu Linux. My goal was to get the family on one email client, browser, and eventually operating system (OS). That wound up being Thunderbird, Firefox, and some flavor of Ubuntu Linux. And all was well. Sorta…

I wanted a non-browser calendar program, and Thunderbird very occasionally provided that with the Lightning extension. The problem has always been that Lightning was usually behind Thunderbird changes, and therefore didn’t work much of the time. Also, to access Google calendars, it required Google Calendar Provider extension – another level of complexity that was often behind keeping up with Lightening and Google changes. The bottom line was that the calendar feature rarely work uni-directionally much less bi-directionally.

Thunderbird 78 incorporated the calendar function natively, which was supposed to fix all the calendar issues. However, it remained unable to sync with Google calendars without the Provider extension, which again was behind. Plus, the jump from versions 68 to 78 somehow broke calendar profiles. The recommendation was to start with a clean profile, then copy the email data over. I had 15 email accounts for various purposes, so recreating all that from scratch was a non-starter. If I was going to start over, it wouldn’t be on Thunderbird.

The Linux KDE desktop comes with a powerful Personal Information Manager (PIM) called Kontact. It includes KMail, KOrganizer (calendar & todo), KAddressbook, a journal, Akregator (RSS feeds), and KNotes all in one window, with Akonadi as the underlying/unifying framework. All of it works with Google accounts natively, as well as a lot of other formats. It also imports from a number of programs, including Thunderbird. KMail had issues with IMAP accounts a few years ago when I first tried it, but those were supposedly fixed. I decided to give it a shot.

The import could have been better designed in that with so many accounts, it was tough to see what folder I was mapping with which account. That’s because the dialog windows often didn’t have the folder or account name embedded. I could have taken longer and written the required information for each step down, but I didn’t. I was later able to clean up and remap the folders that I mis-aligned with no problem. That’s the price of being impatient.

The other caution that I’d offer concerns filters. I apparently had filters in Thunderbird from years ago which were long forgotten. I left the filter import box checked without thinking about it, and KMail imported and reenabled them all during the migration. It took me a while to figure out why the occasional email was going to strange places, but I figured it out eventually and deleted all the filters.

The real headaches and heartburn came from Google, not Kontact. My non-Google accounts worked like a charm. However, Google’s arrogant insistence in treating any program that they didn’t write as “less secure” and therefore locked out by default drove me crazy. It took days and countless Google pop-ups asking for passwords and permissions until I sorted it all out, but I finally reached nirvana through trial, error, and web searches.

First, one has to enable “less secure apps” in Google security for every single Google account that you want to sync with Kontact. I knew this, but had missed a few accounts. Go to the Google account settings, then Security. Be prepared to endure warnings about the end of the world as you know it.

It turned out that for the calendars, I also had to add my Google accounts to KDE Setup’s Online Accounts. Google produced the usual security inquiries, but the calendar synced bidirectionally after that. Thank you, KDE developers.

After “winning” the battles with Google, I am up and running with Kontact. All IMAP email accounts work and the calendar and todos sync bi-directionally with Google. It’s great to have everything in one window and for all the components to talk to each other (emails -> appointments, etc.) Life is good!

As you may notice, like I just did, whatever changes WordPress made to its software basically messed up the site’s formatting. Almost all images now exceed the page width. They worked fine when I wrote the posts, going back years. Wow. Perhaps time to find another platform.

In this post, I talked about how switching to the open source nouveau and mesa video drivers and VirtualBox insulated me from Linux kernel changes and made OpenSUSE Tumbleweed a viable option for me. Well…not so fast. With the Linux kernel 5.8.x memory allocation changes, VirtualBox would no longer load. But, as Mr. Spock used to say, there are always alternatives.

KVM is the native Linux hypervisor. QEMU provides an interface to it. Back in 2007, when I first moved to Linux, I looked at QEMU but decided then that it was too complex. No longer. OpenSUSE makes the KVM/QEMU installation and operation easy. 

Important safety tip – Before burning down VirtualBox, write down the hardware characteristics of your VMs – memory, CPUs, network, USB setup, etc., as well as the location of your virtual hard drives. You’ll need to match the key hardware characteristics when you recreate your VMs in QEMU/KVM. If your virtual disks are one file each, you can skip the next paragraph.

If you have your virtual drives in multiple 2GB files and/or have snapshots, you’ll need to combine them into one file. QEMU doesn’t recognize the multiple file formats. I used the Virtual Media Manager in VirtualBox to convert the multiple files and snapshots into one .vmdk file. You’ll find the instructions here. Be sure to select the most recent snapshot for the conversion. Works like a charm. If you are using VMWare Workstation, they also have a utility to combine virtual disk files. Consult the VMWare docs.

Once you’ve recorded your VM physical characteristics and combined your multiple virtual disk files (if needed), uninstall VirtualBox (or whatever virtual solution that you use) completely, but retain your virtual drives. I created a new directory in my /home folder for the virtual drives that wanted for KVM and copied them over. 

After uninstalling VirtualBox (or whatever you use), restart your computer. Then open YaST and Click on Virtualization -> Install Hypervisor and Tools. (This assumes that you have installed all the YaST modules. If not, you’ll need to go into YaST Software and install the additional YaST modules.)

A new window will pop up:

Check KVM server and KVM Tools under KVM Hypervisor. Those boxes are grayed out in the above image because I already have them installed. Click Accept and OpenSUSE will install all the necessary files and kernel modules. Once the installation competes, restart the computer. 

You now have a running KVM hypervisor, but you need to recreate your virtual machines in the Virtual Machine Manager. Open YaST again as above and click on Virtualization -> Create Virtual Machines.

Select Import existing disk image. I clicked on Architecture options to show that you can select the VM’s architecture up front. Click forward.

Click Browse on this window.

Here’s the tricky part. Note that the default location is on your system drive. I want my VMs on my /home drive, which is a much larger SDD. Ignore what’s in the window and click Browse Local at the bottom. When you get to your virtual disk, click Open. That will bring you back to the previous screen. Simply start typing in the operating system in the bottom box, then pick the correct one as they are offered and click Forward.

Select the memory and CPU setup that you had in your VirtualBox virtual machine. Click Forward.

This takes you to the last screen, which summarizes your system. You can also select your network type, with NAT being the recommended default. You also should click the Customize configuration box. Click Finish and KVM will create the virtual machine, then display a window to customize the VM. It’s critical that you go through the settings and ensure that they match your VirtualBox setup.

That’s it. You now have a new virtual machine in QEMU/KVM that should be almost identical to the one that you had in VirtualBox. If you click the “Play” icon at the top, your VM will start. For future VM startups, use Virtual Machine Manager from the OpenSUSE menu.

Note, if your VM is a Windows installation, its authentication will likely be lost. You can regain it several ways. Consult your Windows documentation or Microsoft’s site.

I’ve found QEMU/KVM’s performance equivalent to VirtualBox, but without all the kernel compatibility issues. So far, it does everything that I need.

Like any other system, there’s a lot more to QEMU/KVM. The OpenSUSE virtualization forums and, of course, the online manual.  QEMU/KVM possesses a host of helpful capabilities and a rich command-line utility capabilities, including converting .vmdk virtual disks to the native .qcow2 format. Happy exploring!

 

I talked about my reasons for going back to openSUSE Tumbleweed in my previous post. That migration did not go smoothly, but it wasn’t an openSUSE’s issue.

I revisited GeckoLinux, which is a kind of wrapper on openSUSE. Gecko claims to improve the default fonts, install non-open source libraries and drivers by default, and overall provide a smoother openSUSE installation experience with a result closer to what many users prefer involving non-open source software (OSS). That’s the promise. So, I downloaded the GeckoLinux iso image and copied it to a USB flash stick.

I use two SSDs in my system – a small one for the root and associated system files, and a 2 TB one for /home. This enables me to freely change Linux distributions while preserving my data and most setup files (e.g., Thunderbird mail, browser setups, KDE desktop appearance). Because I’m paranoid, I also use LuckyBackup to keep my /home directory safe in case of a disaster or stupid installation mistake.

Bottom line up front: the GeckoLinux installation displayed serious issues across no less than five installation attempts. One was my fault for not realizing that the manual partition option requires scrolling to get my desired layout. I don’t recall another distribution that requires scrolling for the partitioning because of the importance of the partition layouts. The rest of the problems were various setup or file conflicts. For example, installing Krusader, my favorite KDE file manager, prompted Gecko to want to uninstall a lot of required KDE software. Worse, trying to install the Vivaldi browser trashed the entire system, requiring a reinstallation. That blew my mind. I also didn’t see any font differences from openSUSE. After almost a day of work and five installation attempts, I finally gave up and abandoned GeckoLinux. On the good side, my /home partition remained intact.

However, by this point I was reduced to booting the GeckoLinux live CD to create a bootable USB stick for openSUSE Tumbleweed. Once complete, I booted to the USB stick for full installation.

The openSUSE Tumbleweed installation went very smoothing and provided a great deal more granularity than the Gecko installer. The partitioning selections were both visible and straight-forward. After requesting permission, Tumbleweed updated itself during the installation. In short, I had no issues successfully installing openSUSE Tumbleweed in one shot.

After the basic installation, I started installing all my usual applications. This, too, went very smoothly. Installing GIMP resulted in over 1 GB of other files being installed. Several other program resulted in a host of other libraries being installed. I’m not sure how many of those were really required, especially for GIMP, but I have plenty of room on the boot disk.

Before I forget, Tumbleweed also picked up my existing KDE desktop setup, including Plasmoids and my icon-only task bar. When I installed programs, those previously pinned to the task bar reconnected to their place on the bar. Both Thunderbird and Firefox tried to start with blank profiles, but I was able to easily redirect them to my existing ones. In short order, I had basically duplicated my Kubuntu app setup and was fully functional. Very impressive.

Tumbleweed installed with the 5.7.x kernel, but everything works fine with that version. I’m also on KDE Plasma 5.19.1 and loving it. I’m still occasionally discovering non-OSS libraries that I need but didn’t install by default. I use the packman repositories for all the “extra” stuff, which occasionally requires me to switch sources for some libraries to get the latest non-OSS versions.

One last cool thing is that Tumbleweed picked up my Republic of Gamers (ROG) motherboard logo and displays it while starting the Linux loading. Slick.

Overall, I’m thrilled with openSUSE Tumbleweed with the OSS nouveau & mesa video drivers, plus VirtualBox. Here’s my current desktop.

Should look familiar. 🙂

In future posts, I’ll talk about the Wayland display controller and other goodies.

I tried openSUSE Tumbleweed several years ago, but had to abandon it because key software I used didn’t keep up with the Linux kernel updates in openSUSE. In particular, VMWare Workstation and the Nvidia video drivers provided regular challenges with kernel updates.

Times have changed. I switched from VMWare Workstation to VirtualBox some time ago. VirtualBox has grown to provide all the capability that I need/use, it’s more flexible with kernel changes, and it stays up to date with necessary kernel changes. In addition, since the NVidia video drivers now have serious issues with display tearing and memory leaks, I moved to the open source nouveau and mesa drivers. The open source drivers provide ample performance for my uses. Therefore, my two primary reasons for leaving openSUSE no longer apply.

In addition, I installed newer kernels in an attempt to fix the NVidia driver issues. Kubuntu 20.04 uses the Linux kernel 5.4.x versions, but I was already running version 5.6.14, though that’s not officially supported. The nouveau and mesa drivers, as well as VirtualBox, worked fine. Running openSUSE Tumbleweed in a VirtualBox virtual machine (VM) revealed that used the 5.6.14 kernel as well.

So, I ran openSUSE in a VM and wrung it out with my usage, including edge cases. For example, I loaded VirtualBox inside the VM and created a VM in that VM. That worked really well. I couldn’t really test the nouveau and mesa video drivers in the VM, but they were working fine with the same kernel on the host. After extensive testing in a VM, I grew confident that openSUSE Tumbleweed could be my production Linux distribution.

But why change from Kubuntu? I like to keep up to date with both the KDE Plasma desktop along with its underpinings, as well as the underlying kernel. The Kubuntu team decided to stick with the 5.4.x kernel, but we’re up to 5.7.1 as I write this. I use the Kubuntu Backports to stay up with the KDE Plasma desktop and applications, but they often lag releases depending on the backport team’s workload. My recent, trouble-free experience with running updated kernel versions convinced me that I could live closer to the bleeding edge now.

Hence my decision to revisit openSUSE Tumbleweed, who’s underlying purpose is to run at a stable leading edge of Linux and desktop software. The KDE desktop implementation is also one of the best that I’ve tested over the years. Time to roll up my sleeves!

I detailed my issues and troubleshooting a serious memory leak and screen tearing issue in this post. After running through every NVidia configuration setting that might bear on the issue and also testing a number of new Ubuntu mainline kernels over the course of a week, I ran out of ideas…and patience with NVidia drivers.

That left only the open source Nouveau drivers. From their Wiki page:

“Nouveau” [nuvo] is the French word for “new”. Nouveau is composed of a Linux kernel KMS driver (nouveau), Gallium3D drivers in Mesa, and the Xorg DDX (xf86-video-nouveau).

I’d used them before in OpenSUSE with good results, so it was worth a shot. Note that if you don’t install any proprietary drivers in a clean installation of Kubuntu with an NVidia card installed, the Nouveau drivers will be installed by default. Easy-peasy. However, there’s a bit more to returning to Nouveau once you are running on the NVidia drivers.

When NVidia installs its drivers, it also blacklists the Nouveau driver in a few places to prevent conflicts. That’s cool if you stay with the proprietary drivers, but a bit of a pain if you don’t. Kubuntu makes changing the drivers themselves easy. Just open Discover, go to Settings, then click on Software Sources at the top right of the main repository list:

Kubuntu will ask for your password, then take you to the Software Sources window. Click on the Additional Drivers tab. Going into System Settings -> Driver Manager will take you to the same place.

You can see that I already have the Nouveau display driver in use. If you have an NVidia driver selected, select the Nouveau driver and click Apply Changes. It will take a minute or so – be patient. Once that’s done, you still have more work to do.

Using whatever text editor you like, Kate for instance, Navigate Dolphin or Krusader to /etc/modprobe.d/. It will have a number of files, most of which Linux uses to black-list drivers that may cause issues. Edit the file nvidia-graphics-drivers.conf and comment out all the Nouveau lines by putting a # character (and a space for neatness) in from of them:

Save the file. If there are any nvidia-*.conf files, edit them as well and duplicate what you just did above. Save the files.

One last thing. The old wisdom was to edit /etc/X11/xorg.conf file to match your setup. Apparently, this file isn’t needed anymore and can actually do more harm than good. I had a solid evening of xorg.conf editing and rebooting to lockups before I finally deleted the version that I was editing and presto! Booted with no problem. If you have one there, rename to something like xorg.conf.old or something like that so that Linux won’t find it on boot up.

That should do it. Simply reboot and you should have the Nouveau drivers running your NVidia card for the display. Be patient on the first boot. Pretty much all your 3D effects should work as before. It may be a tad slower, but I don’t really notice a difference. You won’t have as much control of or information for your graphics card, but then you won’t have memory leaking either.

The only thing that I lost from the interface was using the scroll wheel to change desktops. It’s still set in kwin, but it doesn’t work. I simply remapped the mouse right-click on the desktop to change desktops and clicking the scroll wheel to bring up the context menu. Close enough.

I also got a scroll-like bar on the right side of my screen which I believe means that the NVidia card is in On Demand mode rather than Performance Mode. I’m going to explore this next to see if there’s a way to activate the Performance mode for PRIME in Nouveau. I’ll take any hints.

I’ve been having an occasional issue with overnight lock ups for about a year. The SSD access light is on constantly and the system requires a hard reset to recover. I never could find a reason, until now.

The update to Kubuntu 20.04 displayed bad screen tearing after playing videos or conducting Zoom calls with the NVidia 440 driver, and sometimes without. The rate varies with the number of participant video links, but the leak is much worse in Kubuntu 20.04 than 19.10. After doing considerable research, I found a major change in the NVidia drivers starting with driver 3.70, but in full force in version 3.90. That was the introduction of PRIME and PRIME synchronization.

PRIME provides the capability for multiple-GPU cards to share the load amongst those GPUs. It’s a nifty capability, especially for gamers. General performance is impressive. However, somewhere in the process it introduced a memory leak that remains to this day.

The issue manifested in the NVidia driver through the kwin_x11 module that handles screen effect and calls the NVidia engine. The module continuously gathers more memory to itself at a pretty constant rate. It will do that until one of two things happens. One, you run out of physical and swap memory, locking the system. I believe that’s what happened with I found a locked up computer with the SDD access light on. Or two, one could open a window, either one that was minimized or a new one, which causes the driver to shed the extra memory. However, that shedding took a time proportional to the amount of memory to be shed, resulting in either a temporary screen freeze or bad screen tearing. Not good.

I tried a number of remedies. This situation seemed to be much worse with the 5.4 Linux kernel in Kubuntu 20.04. I tried various NVidia setting changes suggested at various places on the Net, including doing whole-page syncs, trying to turn on VSync manually, et al. Nothing had very much effect. So, I went to to a more drastic approach – the updated Ubuntu mainline kernels.

WARNING: The mainline kernels are not supported and not recommended for production systems! If your dog gets warts, your lawn spawns grubs, or your pickup truck runs away with a Yugo, it’s totally on you.

So, I downloaded the four necessary files from the mainline kernel repository as indicated on the mainline kernel page into a temp folder by themselves, change into that folder, and install them in mass. For example, for Ubuntu kernel 5.6.11, download

linux-headers-5.6.11-050611_5.6.11-050611.202005061022_all.deb
linux-headers-5.6.11-050611-generic_5.6.11-050611.202005061022_amd64.deb
linux-image-unsigned-5.6.11-050611-generic_5.6.11-050611.202005061022_amd64.deb
linux-modules-5.6.11-050611-generic_5.6.11-050611.202005061022_amd64.deb

into a temp directory by themselves, then open a terminal and type

sudo dpkg -i *.deb

Worked like a charm! The system even compiled the kernel modules for the NVidia driver and VirtualBox during the installation. Sweet! I started with the 5.6.0 kernel, then went to 5.6.7, 5.6.10, and finally 5.6.11 as they were released. Don’t forget to move the downloaded kernel files to another folder before moving the next version. Although the leak slowed with the newer kernels, it never went away. Through all the testing, the NVidia and VirtualBox drivers compiled and loaded fine with the newest kernels. Never had a hiccup with VirtualBox operations, either. That was impressive. I ran 5.6.11 for several days with no glitches other than the NVidia memory leak, which clearly originated in the NVidia video driver.

Bottom line is that the leak remained. I finally did solve the problem, but that’s a topic for the next post.

Linux continues to grow and improve. I haven’t written in a while, but hope to get a bunch of stuff published now. This is just a quick update.

Kubuntu has been great. I use the backports to keep the KDE desktop up to date. Everything works. Here’s my current Plasma desktop:

I just updated to Kubuntu 20.04 this past week. The update went flawlessly.

There’s one outstanding issue, but it isn’t a Kubuntu-specific issue. In retrospect, there’s been an issue with the NVidia video drivers that’s been there for over a year. More on that in the next post.

The FBI leadership has been about as corrupt as possible, and that legacy lives on in Mueller’s corrupt investigation of Russian-created myths. Innocent lives are ruined in the process.

The Philadelphia Eagles are the Super Bowl LII Champions!!!

As Coach Peterson, Quarterback Nick Foles, and Tight End Zack Ertz all proclaimed, all glory goes to God!

I don’t understand it, but even free Texas prohibits carrying firearms in a church:

(b) A license holder commits an offense if the license holder intentionally, knowingly, or recklessly carries a handgun regardless of whether the handgun is concealed or carried in a shoulder or belt holster, on or about the license holder’s person:

(6) on the premises of a church, synagogue, or other established place of religious worship.

Yep, today’s killing followed the usual pattern for gun-free zones. Providentially, one gun owner eventually showed up with his own rifle to stop the killing. Again, the “first responder” is an armed citizen, as is often the case. But imagine if several of the church members were armed. The cowardly killer would have turned and run, just like he did when finally challenged by an armed citizen.

Of course, the Democrats are calling for gun control. They should be repealing every existing gun-free, victim-rich zone so that the evil, deranged predators will face a hail of return fire when they attack. Arm up and be ready!

This is great! Independent Journal Review is publishing the mugshots of cowardly antifa terrorists who like to hide behind masks. You can see the wall of shame here. Looks like most of them live in their parents’ basement and the rest look like professional hoodlums. This is apparently the best that the communists can do. Be sure to do thorough web searches on names and criminal record checks before you hire anyone these days, as you might wind up employing these worthless clowns to your inevitable deficit.

As if that wasn’t enough, the antifa and other communist thugs are backing the dictatorship in North Korea over the U.S. This is my shocked face. Being uniformly ignorant, the communist terrorists have obviously not read Nothing to Envy. Ignorance is not only bliss, it carries signs advertising itself.

Of course, you won’t read any of this in the fake news outlets.

The lefties are all up in arms over the fact that Congress has before it laws that allow Americans to do what the Constitution already says that they can do – keep and bear arms as they travel across the country. One stupid argument is that only police and the military should be able to carry arms. Well, back in 2012, the Illinois Tactical Blog did a great article compiling the data for police shootings vs. citizen shootings of criminals. Bottom line: depending on how you do the calculations, police are 11 times more likely to shoot an innocent individual than an armed civilian. We won’t even consider the hypocrisy of folks that hate the police are generally the same folks who say only police should have guns.

Let me be clear that I am pro-police, and the  police have a very tough job. They have to enter uncertain situations at great personal risk and make split-second decisions. That doesn’t excuse the murders innocents like Justine Damond or Philando Castile, but those are rare occurrences. The offending cops should be punished to the maximum extent of the law, but the do not represent law enforcement at large.

National concealed carry is a Constitutional right and should be recognized across the country. Imagine if you had to get a permit to speak in every state of the nation before you could espouse your views?

Here’s an older set of graphs showing the long-term trends that show no real effect of man on the climate. Australia recently got caught with its hands in the cookie jar. As Fox Mulder used to say, the truth is out there. But first, we need to peel back the lies of governments and NGOs who have power and money invested in the lies of global warming.

The amazing Colion Noir answers the subject question in definitive style:

Yep, the liberals hate liberty and personal responsibility, and want to keep law abiding Blacks unarmed on the Democrat plantations. Democrats are so upset over President Trump trying to free folks from dependency under the Democrat thumb that:

Yeah, let’s not forget that the Democrats are political party of the Confederacy, Jim Crow, segregation, and the KKK. It was the party of Lincoln, the Republicans, that fought against all those abominations. This video is instructive:

Don’t be fooled by the Democrat switcheroo. They only want Black subjugation to keep their power bases on the Democrat plantations in the cities. All the Democrat lies come down to that core point. An armed Black populace could fight back in crime-ridden neighborhoods, could take a stand against government overreach, would not be dependent on the benevolence of the Democrats with other people’s money. Hence the 2nd Amendment. Hence the NRA to empower all, including Blacks. Know who your real friends are, not the false ones with their handouts to keep you on the plantations.

My hero, Colin Noir, nails the democrat plantation owners for their lies and hypocrisy:

Oh, and he has great taste in pistols as well. The best of all worlds!

This is precious. Don’t forget, Nazism wasn’t a movement of the right, it was a movement of the far left. Nazi party was the National Socialist Party. The games start at 0:35 or so into the video. Watch and be utterly amazed…or maybe not.

If you look up “moron” in the dictionary, these people’s pictures would be there en mass as exemplars.

This is how it started in 1920’s Germany, and how it’s starting in 2017 America. Be ready when the real American fascists come for your business and/or family. Which makes the following video about these so-called anti-fascists of the left all the more relevant:

And don’t forget that the video sequences in the background of the NRA video are actual footage of the leftist fascist in action right here in America. Nor will we apologize to the violent fascists of the left:

Keep your powder dry, America.

And if that’s not bad enough:

Quite the scam, eh? An OBYW, you cannot keep your doctor.