The future of KDE: Wayland, Qt 5, uniform Plasma shell – The H Open: News and Features

English: Logo of the KDE Project "KDE, K ...

English: Logo of the KDE Project “KDE, K Desktop Environment and the KDE Logo are trademarks of KDE e.V” (Photo credit: Wikipedia)

See on Scoop.itopenSUSE Desktop

The road to Plasma Workspaces 2 has been laid out as the Plasma developers recently met in Nuremberg, Germany, to discuss their open issues around future developments – it will be based on version 5 of the KDE platform and Qt…

Mike McCallister‘s insight:

Key points I take away from this: KDE 5 Plasma Workspaces will be designed to function exactly as the current KDE 4 does.

To do that, it will take at least a year of development. Thus we should see a production-worthy release in late 2014.

See on www.h-online.com

So, That's It For Thunderbird

Reblogged from TechCrunch:

Mozilla is not "stopping" Thunderbird development, it has just decided that: "continued innovation on Thunderbird is not the best use of our resources given our ambitious organizational goals." And it's pulling people off the project. But it's not stopping? Right.

This, according to a letter shared with "Mozillians" ahead of the official announcement to be revealed on Monday. Recipients were asked not to share the letter, blog or tweet about the news until then, but obviously someone out there didn't agree with that plan.

Read more… 665 more words

Initial reaction is disappointment, but I do wonder (a) who besides me still uses a desktop email client, and (b) if email itself is (as I've heard) "something for old people" and "how I reach grandma." What do y'all think about this development? Do you use Thunderbird? KMail? Evolution? Or just read your mail on the web? Oh, don't overlook the link to Mitchell Baker's blog post at the bottom of this story!

More good news on the Kubuntu front

As has been reported at numerous outlets, the project currently known as Kubuntu has a new sponsor, a German company called Blue Systems.

It was just a couple months ago that Canonical announced it was withdrawing direct support to Kubuntu, and reassigning Jonathan Riddell to other projects.

kubuntu

kubuntu (Photo credit: arellis49)

Not much is known about Blue Systems, though what is known is expressed well on the Kubuntu page on Google+:

Did you know. #kubuntu is back with a new family. A brother +Netrunner, and a sister +Linux Mint KDE. “But who’s your daddy?”
http://blue-systems.com !

The good news is that Blue Systems has been sponsoring a variety of KDE projects and distributions in the last few months. They’ve pledged to keep Jonathan Riddell on its payroll working on Kubuntu (or whatever it may be called in the future), and is offering marketing support too. But it’s hard to know from this distance how much money they actually have to back those pledges up. A WhoIs search on the Blue-Systems.com site pointed to a German reseller, http://itwu.de/, as the owner. That’s pretty much all outsiders know.

In some ways, the news is not that different from when Attachmate surfaced last year as the company to buy the SUSE brands from Novell. People rightly questioned what the company had planned for the distribution. So far, it appears that Attachmate has largely left the community alone to make its own plans. Plus openSUSE enthusiasts in the Americas now have their own conference to attend this fall. So I think we can say that up to now, that deal has worked out pretty well.

As I said before, best wishes to Riddell and the Kubuntu community. I’m confident this is good news for my favorite desktop environment, and Linux overall.

If you know anything more about Blue Systems and their work with the community, please let me know. Whatever you think about Kubuntu, KDE and its future, feel free to comment too!

Kubuntu and the “Sinking Ship” of KDE: Really?

English: Logo of the KDE Project "KDE, K ...

Image via Wikipedia

You may have heard that Canonical is formally dropping support of the KDE-based version of the Ubuntu desktop come October. This is kinda old news now, but it seems that at least some folks want to make a big deal of it. So I’m feeling the need to talk about it too.

Tracking the Story

The news came in the form of a February 6 post from Kubuntu developer Jonathan Riddell to the Kubuntu developers list:

Today I bring the disappointing news that Canonical will no longer be funding my work on Kubuntu after 12.04. Canonical wants to treat Kubuntu in the same way as the other community flavors such as Edubuntu, Lubuntu, and Xubuntu, and support the projects with infrastructure. This is a big challenge to Kubuntu of course and KDE as well.

A few days later, Riddell’s counterpart at openSUSE, Will Stephenson responded to the situation on the KDE Contributor’s Blog in a way that may seem a little cynical, but struck me as a completely valid response.

After a week had passed, TechRepublic’s open source pundit Jack Wallen said he read Riddell’s announcement “with a heavy heart.” The money quote here:

try to find a major Linux distribution that ships with KDE as the default desktop. You’re going to be hard pressed to do so.

He said the best way for KDE to survive this blow was to develop its own distribution, which he named KOS. In the poll accompanying the story, 51% of his readers agreed with that strategy.

Bruce Byfield at Datamation (a fine writer for a variety of Linux publications) may have overhyped Wallen’s article just a little, and turned it into part of a wave of “KDE Death Watch” commentary. The story does effectively dispute the idea of KDE disappearing, but does again raise the question of “Just what is a major KDE distribution.”

openSUSE: Can’t get no respect

Younger folks in the audience may not remember Rodney Dangerfield, the comic who built his entire career on the theme that he “got no respect at all” (Check out the films Caddyshack or Back to School to learn more about the Dangerfield persona). One of the most striking things about all these stories is how Kubuntu is (allegedly) the last major Linux distribution with a KDE desktop. Perhaps I’m biased, but when did openSUSE cease being a major distribution? While it has never been dominant in terms of mindshare or installations (admittedly both hard to quantify), the little green Geeko with the outstanding system administration tool just chugs along.

The SUSE distro has been famously associated with KDE throughout its life. Some historical notes:

  • Novell bought the original German company that produced the distribution around the same time that they bought one of the main development teams for the GNOME desktop. When openSUSE planned to make GNOME the default desktop on installation, a massive uproar from the user base left the desktop choice to the person doing the installation.
  • openSUSE was the first distribution to switch to KDE 4. That was certainly a bad idea or miscalculation, but certainly a commitment to the KDE desktop.

openSUSE is not going away, and will continue to be a “KDE-first” distribution for a long time to come. I’m looking forward to seeing how big our community is at the openSUSE Summit this fall.

KDE’s Future

Byfield certainly makes an excellent case for why KDE is not dead, and certainly won’t be on life support anytime soon. Even Wallen (who doesn’t really use KDE anymore) concedes that “KDE is one of the most polished, professional desktops available for the Linux operating system and deserves to be made available through some official channel.”

I disagree that KDE needs to put out its own distro to succeed long-term. The world probably does not need many more Linux distributions. Linux users should always have a choice of desktop environments and associated applications. I love that I can run apps designed for GNOME on my KDE desktop, and want to continue to do that.

KDE certainly needs to attract more developers, volunteer or otherwise. More users and platforms will follow. As I noted last week, the Spark tablet is a great way to build pathways to the future.

Things may not be entirely rosy for KDE today, but I can heartily raise both hands when Wallen says “Linux without KDE is simply not the Linux I’ve known and loved since the mid-90s.” May that continue to be true.

The Problem with Tablets and the Spark Solution

It’s real: Tablet PCs have arrived. According to a recent DePaul University study, one in every dozen airline passengers is using a tablet PC or e-book reader at any given moment.

Like many of you, I got a tablet (a Nook, if you’re interested) as a gift this last December (thanks Jeanette!). It’s pretty nice. I read Wired on it now, check news, post tweets occasionally. But it’s moderately frustrating that I can’t really do anything worthwhile on this machine.

The problem with tablets is that they are designed for consumption: of movies, books, websites and the like. People want to be productive while on the go. The size and weight of the average tablet is perfect for productivity almost anywhere. But the software isn’t there to support a productive worker.

What if there was a tablet with a real operating system and a collection of software that lived in the tablet (not in the cloud)? What if you could work on a presentation without worrying whether your carrier had an affordable wi-fi connection today? What if you could then use a USB port to plug your tablet into a projector when the time came to deliver that presentation? At under $300, that’s a purchase even a cash-strapped employer could justify. This machine is the Spark.Spark tablet

Due for delivery in May 2012, the Spark is being developed by the KDE Project, the open source development team behind the KDE Software Collection, the longstanding and popular Linux desktop environment. It runs the Plasma Active mobile desktop on top of the Mer operating system, the successor to MeeGo.

Project developers are working on building an app store, but you’ll also be able to use the Open Build Service (OBS) from the openSUSE Project to obtain apps for your Spark. This is the “productive” part of this tablet, as you could run most (if not all) applications that could run on desktop KDE.

The main initial problem with Spark is that it’s not an especially powerful machine. The 7-inch Zenithink C71 tablet has just a 1GHz processor, 512MB of memory, and 4GB storage space. The display is 800 x 480 pixels. One hopes that future models will have a little more muscle. The good news here is that it has two USB ports and a microSD slot to help you get work done!

This is where I should be telling you how you can get this marvelous device, but I’m late. Thousands of pre-orders at MakePlayLive.com last week reached the capacity of machines able to be built by the May release. You can (and should!) still put your name on the waiting list, though.

For more complete information on this device, and the philosophy behind it, reading through lead developer Aaron Seigo’s blog posts on the Spark is really exciting.

The Spark is a beginning. The prairie fire will hit when more people realize that a tablet doesn’t have to be a toy.

What do you think about the Spark, and open tablets generally? What tools would you like to see in the Spark? What problems are you seeing in the tablets you use? Leave a comment!

Installing openSUSE 12.1

openSUSE Logo on TuxLast weekend, I got my system ready to install the latest and greatest from the openSUSE community. After I wrote that post, I thought I was going right into the installation, but life intervened (as it so often does). Between tending to other priorities (some of us are still working while the economic crisis continues) and wanting to reserve a large block of time for the install, just in case anything went wrong, I didn’t get to install openSUSE 12.1 until Wednesday.

The good news is that it went pretty smoothly. Let me tell you about it…

The last item of preparation last week was to burn the KDE LiveCD to use for the installation. I kept the Transmission BitTorrent client going 24×7 throughout this period, sharing the 32-bit DVD, KDE and GNOME ISO files (in case you’re wondering, the share ratio indicating the demand for each file wound up at over 5 for the DVD, and both live CDs around 2, with GNOME slightly ahead) for roughly a week.

Before I shut down the laptop, I popped the burned CD-RW into the holder, without sliding it in. I powered down the machine, and the CD drive pulled in the disc. After a couple of deep breaths, I fired up the laptop, and the CD loaded and displayed the KDE desktop, as expected. Two things made me happy to begin with:

  • The desktop displayed in both the laptop and my attached second monitor. They were identical images, so I couldn’t (yet) use the big monitor as an extension of the desktop, but it was a good start for the open-source Nouveau driver.
  • KDE also found my Ethernet cable, attached to the DSL router. I was slightly disappointed it did not immediately locate the wireless card, but I was pretty hopeful that the networking piece of the install would go smoothly.

In the KDE folder view that presented itself on the LiveCD was a lovely Install button. The adventure was about to begin. Clicking the button generated a warning box, telling me I didn’t have enough memory (less than 1GB) to complete the install and run anything else. While thinking “Wow, you mean with a newer system I would have been able to get screen shots? Or even tweet the whole process?”, I resigned myself to reality and started the install. Sorry folks!

The openSUSE installation process has changed a bit since the v10.3 install I documented in openSUSE Linux Unleashed back in 2007, but similar to more recent versions. On the first screen, the installer identifies the language and keyboard you use, with drop-down menus in case it guesses wrong. It also displays the GNU General Public License v2 text, which you do not have to “sign,” but have the option to read.

Clicking Next takes you to the gorgeous full-color world map that allows you to define your time zone, either by clicking your spot on the map, using the drop-down menus or some combination of both. Because this is YaST, you get the option to use the Network Time Protocol (NTP) to set your clock with the help of time servers associated with ultra-accurate atomic clocks. As I had yet to set up my Internet connection, this didn’t work—but I got it working (set to the us.pool.ntp server) later. Click Next.

The third screen offered a suggestion for partitioning the hard drive. YaST reproduced the existing partition table exactly as I had it written down last week, and recommended only reformatting the root (/) partition. For a truly clean install, I could have reformatted /home too, but I was getting anxious and lazy, so I let it slide.

After the suggested partition table, you get three check boxes to select from:

  • Create an LVM-based proposal; this Logical Volume Method would start over and create new partitions across physical hard drives. Choosing this option also allows you to encrypt certain volumes.
  • Propose a separate home partition, selected by default (though I don’t know whether that was because I already had that setup). This is an excellent idea, by the way, for the simple reason that you can store and backup all your data in one place. Then you can choose whether to continue using that data when you change computers or operating systems.
  • Use btrfs as the default filesystem. This new filesystem type (pronounced “Butter-FS”) is intended to be faster and better organized than ext4, the dominant filesystem for UNIX/Linux. But it’s new, and relatively untested.This is not checked by default, and I seriously considered selecting this option, but chickened out on my main production system.

When I clicked Next, I ran into the first glitch of the install, based on the fact that the LiveCD was still running. While the install program (YaST) was trying to identify an initial set of software packages, PackageKit was using the same YaST Software Management module to check for new software, generating an error message from the install program. I had to press Ctrl+Esc to get the System Activity module up to kill PackageKit to continue. that’s Tip #1 for a first-time installer!

Once the software conflict was resolved, the fourth screen of the install appeared, where I created my first user. YaST asks for your Full Name, and offers your first name as your user name. You can change this manually if you prefer something else. You are then asked to type a password twice for that user.

Here you also get three check boxes for this user:

  • Use password for system administrator. This is how Ubuntu does things, but critics (like me) suggest that this is a bad convenience-vs-security tradeoff. I prefer to have a separate admin password, so I clear this box.
  • Receive system mail. Because I am the main user of this system, I do check this box, so when the system wants to tell me something it found in its logs, it will tell me (not the Root account that I never log into directly).
  • Autologin. This box is checked, and is OK to my mind if you’re the only user of your computer (or at least the Linux side). OTOH, if you like to choose your desktop from the login screen, you might not ever see the login screen.

Also on this screen, you can select an authentication method (how the system is to know that you are really you). By default, openSUSE will use the classic UNIX method of a passwd file in /etc. If you have one, you can also select a digital certificate stored on a Lightweight Directory Access Protocol (LDAP) server, a Network File Server (NFS) or a Windows share. Your password will be encrypted using a SHA-512 key, the most secure protocol available, by default. You could choose a lesser cipher (DES, MD5 or SHA-256), but I don’t know why you’d do such a thing.

If you opted to create a different Root/admin password, clicking Next lets you set that password, otherwise you will see the Summary page of all the decisions you’ve made up to this point, with a final opportunity to make changes. You can also select what happens at boot time on this machine. openSUSE presumes you want to start at runlevel 5, with a graphical desktop, but if you just want to run a server of some type, with just command-line access, you can choose that here.

Click Next, and you’ll get the last warning to turn back. The installer then formats the partition(s) it’s slated to and starts “copying the root filesystem.” You can walk away or read a magazine article while it works. On my laptop, the install took 27 minutes. You will be asked to reboot the system.

After the reboot, the automatic hardware configuration kicks in, and two minutes later, your shiny new KDE desktop appears on your screen! From starting the LiveCD to a new working system took less than an hour, and would have been even faster had I not been taking copious notes.

Of course, I wasn’t quite done yet. You remember the problem I had with PackageKit earlier in the process? Well, I still hadn’t done my network setup, so the newly installed PackageKit replacement, called Apper, tried to find updates and promptly crashed.

I opened YaST, and set up my DSL connection with AT&T. After some poking around, I finally found KNetworkManager in the KDE “Configure Desktop” settings application and set up the wireless connection too. Finally, I set up my software repositories in YaST without a hitch. The KDE Crash Reporter was then able to get a proper backtrace, which was sent off to the KDE team.

Over the course of the holiday weekend, I’ve had to fix a few settings, and install a bunch more software, but overall I’m a happy guy! Yes, I’ve successfully booted to Windows and booted back to openSUSE again. I hope your install/upgrade goes as well as mine. If you’re still on the fence about installing, here are some of the other new features. Don’t forget: Have a lot of fun!

Preparing to Install openSUSE 12.1 from Scratch

You may already know, but openSUSE released v12.1 of the community distribution this week. With a new number before the decimal point, I thought it would be a good time for a fresh, clean install on my aging laptop. I could just upgrade my existing v11.4 installation, but I like to see what the new install looks like from time to time. Doing a clean install also means I can share the process with you too.

Clean installs do require a bit of preparation, though. You will be wiping your partitions, so you want to preserve your existing data, and a bit of your configurations before embarking on a new install. In this post, I’ll share what I did.

1. Review Existing Repositories in YaST

While you can find software to do just about anything with just the default repositories in openSUSE, sometimes you need something that isn’t in there, or even in the community repositories that you get access to with every installation. Fortunately, the openSUSE Build Service (OBS) allows anyone to create packages to distribute with openSUSE, or any major Linux distribution.

When you use the 1-Click Install option, the packager adds his/her  repository to your system so you get all the updates. Checking what packages come from what repositories can save you some time later.

As I write this, it occurs to me that the repo list is probably stored in /etc somewhere, but you will still want to write down the repo names and the relevant packages that to install on 12.1.

2. Full Backup

Speaking of packages I got from a non-standard repository, I use BackInTime to handle regular backups of my /home drive to my ever-trusty Seagate FreeAgent external drive. It backs up that info weekly, and is a no-brainer to set up. Nonetheless, I wanted to ensure that everything got backed up before the uninstall/reinstall, so I wanted to make my own archived /home drive, and also the /etc space (where system configuration files tend to be kept).

I thought that would be a simple task with KDE‘s handy Ark tool, but I ran into a permissions issue. Apparently the place I wanted to back up to was restricted to Root! So using the Krusader file manager in Root mode, I was able to change the permissions for the backup folder, and perform the backup; shrinking the 25GB on my /home path to just 9GB. Data is safe!

3. Understand Your Partition Table

Now some people might get angry with me, but I still have the occasional need for that Microsoft operating system. Lots of folks still use it, and the appropriate screen shot is still helpful for my readers (thanks, all of you!). So I’ve been running a dual-boot system for pretty much this entire millennium. Maybe you don’t have to, so you can skip this step. Otherwise, I highly recommend knowing what your system currently looks like. the openSUSE install program should recognize everything that’s there already, but in the off-chance that something goes wrong, if you know how Linux already sees your drive, chances are better it will stay that way.

Again, YaST helps in this regard with the Expert Partitioner module. This tool will reorganize your drive if you need it to, but I’m just going to look at the table now. I wrote down the current partition table, noting that the physical drive was split up into eight pieces (including an extended partition that holds just about everything). I made careful notes of the file system on each partition (so I know where Windows sits) and the size of each. After I wrote it down by hand, I took a screen shot  for additional peace of mind. I should be able to recreate that during the install.

4. Release Day Arrives: Let’s Pull Down Torrents!

As I awoke on the morning of November 16, openSUSE v12.1 was released. I went straight to the download site, and downloaded the torrent files for the full 32-bit DVD release, and LiveCDs containing the GNOME 3.2 desktop and KDE 4.7.2. I can’t make DVDs with this laptop, but I suspected that I could be of help to others if I got all the stuff. The Transmission torrent client went to work as I did the same. When I got home from work, all three files were downloaded to the FreeAgent drive and seeding other people’s downloads.

I guessed right, as my share ratios indicate the DVD is by far the most popular form of download. Interestingly, the GNOME LiveCD has maintained a slight edge over KDE every time I’ve checked the ratios.

BTW, If all this talk of torrents and share ratios have you scratching your head, please let me know. This post has gone on too long already, but I’m happy to take up the topic later.

5. Burn the KDE LiveCD

So let’s see: Data’s backed up; we know where to find random packages, we know where to install the new version and got the installation program. All that’s left is to put the install program on CD. For that task, I use K3B, the excellent CD/DVD burning tool that comes with KDE. Throw a CD-RW into the drive, go to Tools > Burn Image, and point to the openSUSE-12.1-KDE-LiveCD-i686.iso file. Another dialog comes up, where I ask K3B to confirm the data is valid on the CD after writing it, and 10 minutes later, I have a CD ready to go.

In the next post, I’ll tell you how the install went. In the meantime, let me know how you prepare for a new install. Fewer steps? Always just a dist-upgrade?

If you’ve already upgraded to openSUSE 12.1, I’d love to hear how it went, and what you think. Of course, if anything went badly, please file bug reports!

Another Transition: Linux Journal Goes All-Digital

Linux Journal logo.svg

Image via Wikipedia

The word went out Friday: the 208th monthly edition of Linux Journal would be the last of its kind in print. Starting immediately, the magazine would no longer be printed and delivered to newsstands and subscribers. Instead, a plain PDF or enhanced PDF from a company called Texterity will be delivered to subscribers.

Doc Searls described the reasons for the switch thusly in the article linked above:

Just this month, ABC reported that newsstand magazine sales fell 9% in the first six months of this year. The Wall Street Journal reported a drop of 9.2% for consumer magazines, with double-digit drops for celebrity weeklies like People andStar. Women’s Wear Daily reported similar drops for all but one fashion magazine: Vogue, thanks to one Lady Gaga cover.

The big computer-industry trade magazines from the ’90s have either disappeared or gone digital. Of the big three publishers, only IDG is still intact, but relatively few of its old magazines are still in print.

We survived while others failed by getting lean and staying focused. But the costs of printing and distributing continue to go up. We could keep publishing in print if we could raise the number of advertiser pages, but we don’t see that happening.

So, after a fashion, you can see the writing on the wall. The backlash against the decision can be seen in the comment stream. These ranged from the likes of (not actual quotes) “Well, duh, this was inevitable. You gotta get used to it” to pleas for the ability to read the magazine while camping.

One of the more thoughtful critics wondered whether historians and archaeologists of the future might believe humans of our age lost the ability to write, given the lack of tangible artifacts. I suspect there’s a good sci-fi story in that idea; wish I had the imagination to write it.

Now I’ll admit that I lean more toward the side that says “isn’t a printed computer magazine something of an anachronism these days?” But I’ll also admit that I don’t really make time to read all the electronic publications I subscribe to. I find it a little hard to make time for the print publications I subscribe to as well.

I do think that we will eventually everyone will be going all-digital, and probably sooner rather than later. As some folks in the LJ comment thread noted, it’s important to do it right, though. I hope that as this transition proceeds, we can all find the right form(s) for our information.

As a writer, I also hope that LJ remains a paying market for the people who provide the content we all read. To that end, I intend to keep my subscription for as long as possible, and recommend you do that too. I’d give ‘em a raise too, but that’s just me. Disclaimer: I sold a story to the website (not the print version) a few years ago, and hope to do so again one day.

Do you read Linux Journal? Other Linux-oriented print publications? Do you read electronic magazines of any kind? Are print magazines on the way out, and is that a good thing? Just a few of the many questions raised by this decision; feel free to comment here on any or all of them.

Some Quick Hits: openSUSE Strategy, WordPress Upgrades, and Some Pointers

It’s summer in Milwaukee, and I haven’t been spending too much time in front of a keyboard lately. You’re surprised?

Anyway, I do have a lot of things on my mind, and here are some of them:

  • openSUSE Strategy Vote: This is directed at the 267 formal Members of the openSUSE Community who have not yet voted on the proposed strategy document: As I write this, you’ve got less than 24 hours to cast your ballot.  The proposal has a 90% approval rating right now (and I voted Yes, if you care what I think); but unless at least 35 more members vote, bumping turnout over 50%, the strategy won’t be adopted! The statement doesn’t take long to read, you can vote No, or even abstain if you like, but please make your voice heard!
  • WordPress v3.2: In the offhand chance you haven’t heard: WordPress released v3.2 (aka Gershwin) over a week ago! There’s even been an update already! Much more to say about this soon, but goodness knows if you haven’t upgraded yet, what are you waiting for?
  • Some Personal History: If you’ve read my About page, or checked out my main website, you know that I’m a technical writer by profession. I wrote a brief account of my “Adventures in Publishing: Finding a Gig as a Computer-Book Author” for the webzine associated with the venerable Technical Writing mailing list (TechWr-L). You may find it interesting.
  • Getting Yet More Social: You may have heard about this new little social network called Google+. It’s really been flying under the radar, don’t you think? I’ve been playing around there this week. If you’re there, connect with me here. If you’re not there, and are anxious to learn more, my Invite button is still showing. Drop a line with your name and email address to gplus-at-michaelmccallister.com. I’ll see what I can do.
That’s all for now. Expect to be hearing more from me on these and other riveting topics as the summer presses onward.