Language Selection

English French German Italian Portuguese Spanish

Why I hate Ubuntu (even though it's awesome)

Ubuntu pisses me off.

A new release of Ubuntu means another attempt for me to come to terms with Debian's Celebrity Wild Child. I have installed every Ubuntu release since Warty. Each time, I start out being impressed and enthusiastic, become angry when something ridiculous happens, uninstall it in a fit of pique, and then post something on the internet about why I hate it. This time, I am resolved not to uninstall it. I have a second computer, so that living with Ubuntu doesn't mean living with all the time. I want to come to terms with Ubuntu, which is now the most popular Linux distro that ever was, and for good reasons. It's also the most despised distro among the established Linux community... also with good reason. In the past few days, I've read blogposts mocking Ubuntu users as "sheeple" and accusing Ubuntu haters of pettiness and jealousy.

My vague ambivalence toward the Ubuntu Humanity Juggernaut sharpened into dislike when I spent a good part of a frustrating afternoon trying to find KDE in the Butnut repositories. I repeated the experiment last night, with my latest install, and this problem still hasn't been fixed. There is no "kde-desktop" in the Ubuntu repositories. An apt-cache search finds a whole gaggle of KDE applications, but not the desktop itself.

The reason? Because Ubuntu has renamed KDE "Kubuntu-desktop".

Now, at first I was annoyed by the rechristening. I thought it was a pointless inconvenience, but I came to see that this kubuntu-fluxbuntu-xbuntu thing is a great idea for making the major desktop environments comprehensible to new converts to Linux. Looking back to my early days, it was a long time, more than a year, before I understood that Knoppix looked one way because it ran with KDE,and the reason why Red Hat 9 looked so different was because it used Gnome as a default, and that Red Hat 9 could easily be made to run KDE and look more like knoppix. Ubuntu's approach will make this a lot easier for a new user to take in.

This is why Ubuntu deserves its success, because it takes Debian-- one of the most reliable distros, and certainly the one with the richest arsenal of software applications, and makes it available to the Windows-afflicted with some very slick engineeering, engineering that is beyond intuitive. It's actually empathetic. Ubuntu is designed with some real insight into the thought processing of the beginning user.

So why am I pissed off? Because of a lack of empathy for me, the experienced linux user. In reeenginnering Debian, Ubuntu creates detours in the familiar highway of GNU-Linux administration, and then doesn't bother to put up a sign. And so, before I know it, I'm off the road.

The description of "kubuntu-desktop" in the repositories goes like this:

kubuntu-desktop - Kubuntu desktop system.

Redundant, isn't it? The desktop so nice, they named it twice.

Now, here's the thing that bugs me. Suppose they had put it in the repositories like this.

kubuntu-desktop - The KDE desktop for Ubuntu.

That's actually a better explanation, and I also believe that it would have put "kde" and "desktop" where apt-cache my apt-cache search would have found them. That's all that it would have taken for me not to spend an afternoon trying to find the KDE desktop, trying to visually scan all of the hundreds of listing generated by "apt-cache search kde", trying to find something that wasn't there.

I'd love for somebody to explain to me why I shouldn't be angry about this. A huge amount of time, effort, ingenuity and money has gone into adding very slick and intuitive interfaces and features so that the "everyday (i.e., Windows) users" can easily use Ubuntu. But it really looks like not one thought was wasted on me, the demographically insignificant Linux user, trying to find KDE the way he always has, after they've made their changes. It would have taken no time,no money, no ingenuity, to anticipate and solve this problem, and it wouldn't have interfered one iota with their grand design. All it would have required is for them to care. But why should they care about us? We're just the ones who gave them the software.

This is one particularly blatant example of how Ubuntu seems to punish me again and again for being a Debian user. You can grumble about Ubuntu being a mediocre product, but it's not. It's the most important Linux distro in years. In many ways, and, it's the breakthrough we're all waiting for, but I feel like those of us who have worked so hard for so long for Linux to succeed are not being considered at all. I'd just like to be invited to the party, that's all.

Another example, somewhat less blatant, and more geeky: I've often complained about the fact that Ubuntu has no /etc/inittab file, which I am used to editing to change the runlevel (to disable the X server and run from the plain console), and sometimes to add additional console screens. For a number of reasons, I prefer to run X from the console, rather than a desktop manager like kdm or gdm. For the first time in any Linux distro in my experience, the file isn't there in Ubuntu. So how about a text file, telling me what the hell is going on? It could be called "inittab-removed.READ_ME or something. Just a little sign post? Maybe some suggestions of what to look for, so I'm not just left standing in the middle of nowhere with my dick in my hand? If the runlevel can be changed, tell me how. If the runlevel can't be changed, tell me so I'm not wasting any more time on it. What would it cost for you to to show us that much respect for the veteran Linux user, since you've gone so far out of your way to do everything for the Windows user short of wiping his nose for him?

The Ubuntu Code of Conduct says that when there are disputes, consult the community... and that's what I have done here. If anybody has another point of view, I'd like to hear it.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

I'm posting this tonight.

Because if I leave it in my browser window all night, I'll lose it... but I'll edit it tomorrow. You might want to wait until the final version before you post your flames about how I'm a paid troll for Microsoft.

Okay, it's essentially complete... FLAME ON!

IIRC it works the other way, too

If you install Kubuntu, and later want to install GNOME, you have to install the "ubuntu-desktop" meta-package, instead of firing up Synaptic and choosing the individual GNOME components you want.

If you don't, you might reboot to find that (even though you can still choose it, instead of gdm, with the "dpkg-reconfigure xdm" command) kdm no longer works. If you prefer kdm over gdm, this is very frustrating. I don't know if that's been fixed in v7.10 or not.

Personally, as a user of Debian, my problem with Ubuntu and its siblings ("hate" is too strong a word; it's just an OS, after all) was said much better than I ever could by Martin Krafft, the guy who wrote The Debian System, in a blog post he made in July, 2006. It's still relevant today.

It's a love-hate thing.

I never thought about it before, but "hate" is a word that is defined by its context with an amazing degree of precision. If I say that I hate oatmeal, or Windows Vista, or "Seinfeld", or Dick Cheney, or my parents, or Catholics, the word means something dramatically different in each case. (None of these statements are true, by the way. Okay, maybe the one about Dick Cheney.)

More in Tux Machines

Leftovers: BSD

Security Leftovers

  • Stop using SHA1 encryption: It’s now completely unsafe, Google proves
    Security researchers have achieved the first real-world collision attack against the SHA-1 hash function, producing two different PDF files with the same SHA-1 signature. This shows that the algorithm's use for security-sensitive functions should be discontinued as soon as possible. SHA-1 (Secure Hash Algorithm 1) dates back to 1995 and has been known to be vulnerable to theoretical attacks since 2005. The U.S. National Institute of Standards and Technology has banned the use of SHA-1 by U.S. federal agencies since 2010, and digital certificate authorities have not been allowed to issue SHA-1-signed certificates since Jan. 1, 2016, although some exemptions have been made. However, despite these efforts to phase out the use of SHA-1 in some areas, the algorithm is still fairly widely used to validate credit card transactions, electronic documents, email PGP/GPG signatures, open-source software repositories, backups and software updates.
  • on pgp
    First and foremost I have to pay respect to PGP, it was an important weapon in the first cryptowar. It has helped many whistleblowers and dissidents. It is software with quite interesting history, if all the cryptograms could tell... PGP is also deeply misunderstood, it is a highly successful political tool. It was essential in getting crypto out to the people. In my view PGP is not dead, it's just old and misunderstood and needs to be retired in honor. However the world has changed from the internet happy times of the '90s, from a passive adversary to many active ones - with cheap commercially available malware as turn-key-solutions, intrusive apps, malware, NSLs, gag orders, etc.
  • Cloudflare’s Cloudbleed is the worst privacy leak in recent Internet history
    Cloudflare revealed today that, for months, all of its protected websites were potentially leaking private information across the Internet. Specifically, Cloudflare’s reverse proxies were dumping uninitialized memory; that is to say, bleeding private data. The issue, termed Cloudbleed by some (but not its discoverer Tavis Ormandy of Google Project Zero), is the greatest privacy leak of 2017 and the year has just started. For months, since 2016-09-22 by their own admission, CloudFlare has been leaking private information through Cloudbleed. Basically, random data from random sites (again, it’s worth mentioning that every site that used CloudFlare in the last half year should be considered to having fallen victim to this) would be randomly distributed across the open Internet, and then indefinitely cached along the way.
  • Serious Cloudflare bug exposed a potpourri of secret customer data
    Cloudflare, a service that helps optimize the security and performance of more than 5.5 million websites, warned customers today that a recently fixed software bug exposed a range of sensitive information that could have included passwords and cookies and tokens used to authenticate users. A combination of factors made the bug particularly severe. First, the leakage may have been active since September 22, nearly five months before it was discovered, although the greatest period of impact was from February 13 and February 18. Second, some of the highly sensitive data that was leaked was cached by Google and other search engines. The result was that for the entire time the bug was active, hackers had the ability to access the data in real-time by making Web requests to affected websites and to access some of the leaked data later by crafting queries on search engines. "The bug was serious because the leaked memory could contain private information and because it had been cached by search engines," Cloudflare CTO John Graham-Cumming wrote in a blog post published Thursday. "We are disclosing this problem now as we are satisfied that search engine caches have now been cleared of sensitive information. We have also not discovered any evidence of malicious exploits of the bug or other reports of its existence."

Security Leftovers

  • Change all the passwords (again)
    Looks like it is time to change all the passwords again. There’s a tiny little flaw in a CDN used … everywhere, it seems.
  • Today's leading causes of DDoS attacks [Ed: The so-called 'Internet of things' (crappy devices with identical passwords) is a mess; programmers to blame, not Linux]
    Of the most recent mega 100Gbps attacks in the last quarter, most of them were directly attributed to the Mirai botnet. The Mirai botnet works by exploiting the weak security on many Internet of Things (IoT) devices. The program finds its victims by constantly scanning the internet for IoT devices, which use factory default or hard-coded usernames and passwords.
  • How to Set Up An SSL Certificate on Your Website [via "Steps To Secure Your Website With An SSL Certificate"]
  • SHA-1 is dead, long live SHA-1!
    Unless you’ve been living under a rock, you heard that some researchers managed to create a SHA-1 collision. The short story as to why this matters is the whole purpose of a hashing algorithm is to make it impossible to generate collisions on purpose. Unfortunately though impossible things are usually also impossible so in reality we just make sure it’s really really hard to generate a collision. Thanks to Moore’s Law, hard things don’t stay hard forever. This is why MD5 had to go live on a farm out in the country, and we’re not allowed to see it anymore … because it’s having too much fun. SHA-1 will get to join it soon.
  • SHA1 collision via ASCII art
    Happy SHA1 collision day everybody! If you extract the differences between the good.pdf and bad.pdf attached to the paper, you'll find it all comes down to a small ~128 byte chunk of random-looking binary data that varies between the files.
  • PayThink Knowledge is power in fighting new Android attack bot
    Android users and apps have become a major part of payments and financial services, carrying an increased risk for web crime. It is estimated that there are 107.7 million Android Smartphone users in the U.S. who have downloaded more than 65 million apps from the Google App Store, and each one of them represents a smorgasbord of opportunity for hackers to steal user credentials and other information.
  • Red Hat: 'use after free' vulnerability found in Linux kernel's DCCP protocol IPV6 implementation
    Red Hat Product Security has published details of an "important" security vulnerability in the Linux kernel. The IPv6 implementation of the DCCP protocol means that it is possible for a local, unprivileged user to alter kernel memory and escalate their privileges. Known as the "use-after-free" flaw, CVE-2017-6074 affects a number of Red Hat products including Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7 and Red Hat Openshift Online v2. Mitigating factors include the requirement for a potential attacker to have access to a local account on a machine, and for IPV6 to be enabled, but it is still something that will be of concern to Linux users. Describing the vulnerability, Red Hat says: "This flaw allows an attacker with an account on the local system to potentially elevate privileges. This class of flaw is commonly referred to as UAF (Use After Free.) Flaws of this nature are generally exploited by exercising a code path that accesses memory via a pointer that no longer references an in use allocation due to an earlier free() operation. In this specific issue, the flaw exists in the DCCP networking code and can be reached by a malicious actor with sufficient access to initiate a DCCP network connection on any local interface. Successful exploitation may result in crashing of the host kernel, potential execution of code in the context of the host kernel or other escalation of privilege by modifying kernel memory structures."

Android Leftovers