Looking for a nice, somewhat fancy sans serif font?

Today as I was catching up with the Linux Mint Forums I saw a thread about the Mint Spirit fonts. I’m always on the lookout for a new font to use, and when I looked at the preview PDF (which is in French but that shouldn’t be a problem regardless of which languages you speak) I found a very nice font. The font is available in both the standard TrueType Collection (TTC) and  Opentype PS outlines (OTF) formats and they’re both in the single ZIP file you can download. One of the best parts? All of the fonts from Arkandis Digital Foundry (ADF) are free.

As soon as I saw how Mint Spirit font looks I thought I might have a new default font style to use on my system but after changing all of the font settings to use Mint Spirit I realize it may not be perfect for everything, but I love it for my window titlebars. I’ll just have to take some time and decide how many other classes of fonts on my Linux Mint Debian Edition + KDE system the font works for.

You can download Mint Spirit, as well as all of the  ADF fonts and preview PDF files, on the ADF Fonts page. Please note: The Mint Spirit font is a personal project of the designer and is neither supported nor sponsored by the Linux Mint team.

Debian Linux infographic

This morning I was catching up with new posts on the Linux Mint Forums and saw that user Vincent Vermeulen posted a comment in the LMDE FAQ thread about an infographic  someone created to show the history of Debian Linux, the basis for Ubuntu Linux, Linux Mint (actually the main Mint is built on Ubuntu) and Linux Mint Debian Edition (LMDE). Claudio F. Filho created what could be the best visual overview of Debian Linux available anywhere. It shows the different versions of Debian Linux, along with the Toy Story characters they were named after. It also shows the difference between Wheezy, the current testing version that’s the basis of LMDE, and Sid, the bleeding edge version some of us like to use to test the absolute latest versions of apps.

Even if you’re not a direct user of Debian Linux, or even a Linux user at all, you should check out Claudio’s infographic. And if you can help with translations (the main version is in English) please get his translation sheet so he can create a version of the infographic in more languages. Yooouge thanks to Vincent Vermeulen for mentioning it on the Linux Mint Forums. I owe both of you a brew.

Update: After I published this post I checked out more of Claudio’s blog and realized it’s a gold mine of great information. His latest post is a Migration Guide for Open Source and has another infographic, but it’s not available in English yet. The good news is that while he writes in Português if you use Google Chrome (or Chromium, of course) you can use the built-in translation tool to get an English translation of anything on his blog other than his graphics.

[HOWTO] Fixing Samba sharing in LMDE

With all the goodness in Linux Mint Debian Edition (LMDE) there are some problems, like the fact that sharing files and folders with Samba doesn’t work. Had I checked the Linux Mint Forums sooner I would have seen the fix for the problem in the Tutorials section, and since I’ve finally found it I wanted to share it here to help everyone else find it. The tutorial is written with GNOME’s Nautilus file manager in mind but it works just as well for KDE users like myself. I’m going to give both the GNOME and KDE versions of the first step but the rest of the steps work beautifully regardless which desktop environment you prefer. Please note that if you use Xfce as your DE I have no idea if the steps need to be changed to work with it.

1. Enable “Guest Access” in Samba
For some reason this is disabled by default in LMDE but it’s an easy fix for it. Open the Samba configuration file as root in your preferred text editor. If you use GNOME run this command in your terminal

gksu gedit /etc/samba/smb.conf

If you’re a KDE user like me run this command in either your terminal or in the Run Command Interface

kdesudo kate /etc/samba/smb.conf

Once the file is open in your text editor add these two lines to the [global] section

usershare allow guests = yes
map to guest = Bad user

It doesn’t matter where within [global] you put those two lines. I put them at the bottom of the Misc. section (line 231) but you can put them right below the [global] section header around line 34. Once you have put the lines into the file save it and close it, then restart Samba by running this command in your terminal

sudo service samba restart

2. Add yourself to the correct usergroup
As things stand you won’t be able to create shared files and folders because you don’t have the right permissions. This is an easy fix by running this command in your terminal

sudo gpasswd -a your_user_name sambashare

Replace your_user_name with the name you use when logging into LMDE. Keep the terminal open because you’re not finished with it.

3. Install samba client packages
There are four packages you will need to install  on your system before you can set Samba to share files on your system. Run each line one line at a time in your terminal

sudo apt-get install gvfs-fuse
sudo apt-get install libsmbclient
sudo apt-get install smbclient
sudo apt-get install python-smbc

Now add yourself to the fuse group to make sure you have the permissions needed for actually using these packages

sudo gpasswd -a your_user_name fuse

again replacing your_user_name with your user name on the system.

4. Log out and back in for the group changes to take effect
That’s right, it’s that simple. If you’re running GNOME you may find that the “Create Share” button in Nautilus abruptly closes and your desktop will disappear but there’s no need to fear because it will return. There’s probably a bug filed with Debian about it but I haven’t seen it or a workaround for it yet. If you’re running KDE you don’t need to even worry about it because I didn’t see the glitch on my laptop.

Thanks to Linux Mint Forums user altair4 for writing the tutorial I found. You can find it, and other posts on the matter in the thread How To – Simple File Sharing in Mint on the Mint Forums.

[HOWTO] QuickTip: Do you use the OxyXmas icons but can’t change the icon for Chromium on LMDE with KDE SC 4.7.2?

Earlier this week I installed the OxyXmas icons as part of my holiday decorations, but no matter what I did I couldn’t get the icon for Chromium to change. I finally looked at the settings in the Chromium desktop file (/usr/share/applications/chromium.desktop) and found the problem. There’s an icon for chromium-browser but not for chromium, which is how the browser is identified in LMDE. It turns out the fix is very simple.

  • Download the OxyXmas tarball from KDE-Look.org if you don’t have it on your hard drive. Extract the tarball.
  • Before creating the various icon sizes drill down to the OxyXmas/128x128/apps directory
  • Copy the chromium-browser icon by manually copying it in Dolphin or by running cp chromium-browser.png chromium.png in the terminal
  • Go back to the main OxyXmas directory
  • In a terminal window working in the main oxyXmas directory run ./iconvert
  • Install the icon theme via systemsettings or by copying the oxyXmas directory to /usr/share/icons/ or ~/.kde/share/icons (I prefer the latter)
  • Open the System Settings dialog and go to Application Appearance > Icons and select the OxyXmas – OxySeasons Xmas-Theme and click Apply.

Voilà! You can now use the OxyXmas theme and show the Chromium icon sporting a jolly Santa hat.

How does my desktop look for the season? Here’s a clean shot:

And here’s a dirty shot:

Thanks to spacepenguin for creating this fun set of icons.

[HOWTO] Fixing Chromium on Linux Mint Debian Edition with KDE SC 4.7.2

Yesterday I wrote about updating to KDE SC 4.7.2 and the fact that Chromium broke thanks to a long known issue in Debian testing repos. My original fix was to install Google Chrome, but that wasn’t that great of a fix because I really want to run Chromium, not Chrome. Although running Chrome seems to fix the problem of missing the first character of Facebook status updates, which is a royal PITA. Today wayne128 shared a fix he uses to get past the “Aw snap!” messages.

NOTE: Please note that this fix uses an unusual source for getting the updated Chromium packages. If you add this source to your sources.list please disable it once you get Chromium installed to prevent other breakages.

The fix is to use a repository for aptosid. Before we add the repo let’s make a backup of your sources.list.

kdesudo cp /etc/apt/sources.list /etc/apt/sources.list.backup

Now open sources.list by running this command in your terminal

sudo kate /etc/apt/sources.list

Here’s the repo to add at the bottom of the list:

deb http://oscar.aptosid.com/debian/ sid main fix.main
#deb-src http://oscar.aptosid.com/debian/ sid main fix.main

You can leave the source code entry commented out or you can enable it by removing the “#” at the start of the line. Save and close the file and let’s get your package list updated.

sudo apt-get update

Let’s check to make sure your system can see the right version by running apt-cache policy chromium in your terminal. No sudo is needed for this command. You can ignore the version listed for Installed but the Candidate version should match this

~$ apt-cache policy chromium
chromium:
Installed: 15.0.874.106~r107270-1+c0.aptosid.1
Candidate: 15.0.874.106~r107270-1+c0.aptosid.1
Version table:
*** 15.0.874.106~r107270-1+c0.aptosid.1 0
500 http://oscar.aptosid.com/debian/ sid/fix.main amd64 Packages
500 ftp://ftp.spline.de/pub/aptosid/debian/ sid/fix.main amd64 Packages
100 /var/lib/dpkg/status
15.0.874.106~r107270-1 0
500 http://http.us.debian.org/debian/ unstable/main amd64 Packages
14.0.835.202~r103287-1 0
500 http://ftp.debian.org/debian/ testing/main amd64 Packages
~$

If the candidate version matches you’re ready to take the next step. If you already have Chromium (the browser) installed run sudo apt-get upgrade and make sure chromium is available to be upgraded.  Otherwise run sudo pat-get install chromium in your terminal. Either way you get Chromium 15.0.874.106~r107270-1+c0.aptosid.1 you can now launch it and be able to use the browser instead of being greeted with “Aw snap!” on every tab you open.

You’re almost done with the task. Before you go back to your web surfing open sources.list again and comment the lines you’ve added out by putting “#” at the start of each line. That way you won’t have to worry about getting prompted about updates you don’t need.  When Chromium gets fixed in Debian it should make the aptosid repos unnecessary, and if Debian updates it and you end up with the error messages again it will be an easy process of uncommenting the lines, getting aptosid’s newest packages and commenting them out again.

You can see wayne1287′s post itself on the Linux Mint Forums.

On a side note, you’ll see a number of packages being held back, and I wouldn’t worry about it. I’m not sure why the packages are being held back but I haven’t missed any held back package since I’ve done these updates. (If someone knows why they’re held back please leave it in the comments so we can get the info.) Updating and upgrading in the terminal will keep some packages held back but if you select all the updates in Synaptic they’ll be installed so I wouldn’t update with Synaptic if you’re running KDE SC 4.7.2 on Linux Mint.

[HOWTO] Get KDE SC 4.7.2 on Linux Mint Debian Edition, and a fix to the LMDE Chromium issue

[Updated 5 December to include an additional pair of apps  the broke with the upgrade. - Peng]

I love being able to run KDE on Linux Mint Debian Edition (LMDE), even if it is just KDE 4.6.5. I was able to install it without jumping through any hoops or using any repositories not counted among in the default Linux Mint software repos. Boo had been working on getting Linux Mint 11 KDE ready for release, but before we could get to a release candidate The Powers That Be realized that a ton of work would be needed to get Mint 11 KDE, based on Kubuntu, ready for release, and that rather than fix the problems they’d move Mint KDE to the LMDE base. Before that could start clem, the founder of Linux Mint, had to get LMDE Update Pack 3 released to the user base, and he needed to get Mint 12 out. Unfortunately before Mint 12 was released boo found that he couldn’t continue being the lead maintainer of Mint KDE any longer, so now all the work of getting LMDE KDE ready falls on clem’s plate, along with everything else he has to do.

But back in August I noticed a thread on the Linux Mint Forums called “KDE SC 4.7.2 enters Debian (only amd64).” Since Kathryn runs the amd64 version LMDE I was eager to get KDE 4.7.2, and all I needed to do first was get some other work out of the way and have some time to make sure the updates I would get wouldn’t break my system. This is especially important since the first step is to upgrade to the Debian Testing repos rather than using the Linux Mint Incoming repos and I was already seeing posts in a thread about broken apps in Testing upgrades. This wasn’t that big of a problem to me because I’ve run nightly and testing builds of software before and knew how to be careful. But there was a huge issue in the fact that I couldn’t find the information I needed to switch to the testing repos, the first step in getting ready to get KDE 4.7.2. Luckily GeneC gave me the information I was looking for, and since it was so hard to find I’m going to list the steps you need if you want to get KDE 4.7.2, or even just get packages from Debian Testing rather than even LMDE incoming.

Important: Please read the entire post and make sure you understand what you’ll be doing and have backed up your system before performing any of the steps I lay out. I’d hate to get you partway to the new KDE and have you stuck with something you don’t understand. Also, the KDE 4.7.2 update is a semi-official Debian-kde build so you’ll be using different repositories to get it. All the information on this release of KDE 4.7.2 is available on the qt-kde Debian site.

Disclaimer: These steps are not to be taken lightly. There is a very good chance that you may get an upgrade that breaks your system, leaving you to hunt for a fix (if there is one) or even having to reinstall LMDE all over again. If you’re not not comfortable with the risk of completely wrecking your computer don’t perform these steps. And even if you are willing to take that very real risk, check the latest posts in this thread on the Linux Mint Forums to see what problems are cropping up lately. Even if the coast looks clear think long and hard about taking these steps on the computer you use on a daily basis. And of course don’t forget the most important step: Back up your system before doing any of this.

You’re still here? You must be a glutton for punishment, and I’m not even going to make too many puns. (Sorry, I couldn’t resist.) After you’ve backed up your system (I’m not kidding about that step), start by making sure your system is up to date by running this in your terminal:

sudo apt-get update && sudo apt-get dist-upgrade

When you have made sure your system is up to date you need to back up your sources.list file before you start changing anything there. An easy way to backup the file is by running this command in a terminal

kdesudo cp /etc/apt/sources.list /etc/apt/sources.list.backup

Now open sources.list by running this command in your terminal

sudo kate /etc/apt/sources.list

Your current sources.list should contain entries very close to this:

deb http://packages.linuxmint.com/ debian main upstream import
deb http://debian.linuxmint.com/incoming testing main contrib non-free
deb http://debian.linuxmint.com/incoming/security testing/updates main contrib non-free
deb http://debian.linuxmint.com/incoming/multimedia testing main non-free

Comment out those lines, except for the very first line, by putting “#” as the very first character in each line (except the one for packages.linuxmint.com). Before you can snag the new KDE 4.7.2 packages you need to upgrade your system to use the Linux Mint Sid (testing) repos. First let’s get you updated to the Linux Mint Incoming repos. To do that add these lines at the bottom of your sources.list.

deb http://debian.linuxmint.com/incoming testing main contrib non-free
deb-src http://debian.linuxmint.com/incoming testing main contrib non-free

Save the file and update your package list and software again, and let’s apply the first batch of updates if you don’t have them already. Run this command in your terminal

sudo apt-get update && sudo apt-get dist-upgrade

The upgrade could take some time, so have some coffee or a soda, and a smoke if you are part of the wonderful group of folks on the planet that smoke. Don’t go too far though because the process will have some questions about the upgrades for you to answer. When it’s done you will probably need to apply more updates after rebooting your system. Why reboot your system? You may be getting updates that can only be applied with a system reboot, the only kind of updates and installs in Linux that require a reboot, unlike Windows’ insistence on reboots after installing anything. You may also have other updates waiting for you after the reboot, and apply them with

sudo apt-get update && sudo apt-get upgrade

Make sure you’re happy with your system after the updates, and don’t apply any more updates from this post until you’re happy with how your system is operating. Did something break already? It’s time to hunt down what got broken and how to fix it. Once you are completely up to date with incoming and happy with your system you need to update your system to Mint Sid (unstable testing). Here’s where you can really hose your system, so don’t do the steps below unless you’re willing to risk making your system completely unusable. Ready to take the risk? Comment out the lines for the Testing repo and add these lines at the bottom of your sources.list

deb http://packages.linuxmint.com/ debian main upstream import backport
deb http://security.debian.org/ testing/updates main contrib non-free
deb http://www.debian-multimedia.org sid main non-free
deb http://http.us.debian.org/debian/ unstable main contrib non-free

Update and upgrade again, and again this could take some time and it could have some questions for you to answer again. Reboot your system after it’s done because once again you’ve got updates that can’t be applied and used until you reboot your system. Again, make sure you’re happy with how your system operates, and if you’re not bookmark this page and come back to it after you’ve resolved the problems you’ve discovered.

/me fires up the David Wax Museum and enjoys their tunes while you take care of your new issues

Welcome back. Everything copacetic now? Cool. Let’s get you KDE 4.7.2. Backup your sources list again, and if you’ve done other things since you got Sid installed backup your system again, just to be on the safe side. Like I said at the top of the post, this update isn’t coming from the standard Debian repos, so you’ll need to add the appropriate repos to your sources.list file. Open the file and see if you have the following lines, and if so remove them.

deb http://qt-kde.debian.net/debian experimental-snapshots main
deb-src http://qt-kde.debian.net/debian experimental-snapshots main

deb http://qt-kde2.debian.net/debian experimental-snapshots main
deb-src http://qt-kde2.debian.net/debian experimental-snapshots main

Update your system again with

sudo apt-get update

and let’s tell your system that the packages from those repos are trusted. Run this line in your terminal

sudo apt-get install pkg-kde-archive-keyring

Once it’s installed update your package list and make sure your system is updated one more time with

sudo apt-get update && sudo apt-get dist-upgrade

Everything green? Let’s get you upgraded to KDE 4.7.2. This update is different from most upgrades you run, including dist-upgrades. This time you want to run

sudo apt-get -t experimental-snapshots dist-upgrade

This upgrade could be the longest of the bunch, and you’ll definitely need to stay close by to answer some questions the upgrade process will ask you. When it’s all done go ahead and do one more reboot to apply the last set of upgrades. When you log back in your desktop may not look all that different, but checking About KDE in System Settings will have a new version number for you to see. Here are a pair of screenshots of my system after the upgrade.

Clean

Dirty

Updated 5 December: It turns out two other apps died with this upgrade. Electric Sheep broke because I had to reinstall xscreensaver. The wallpaper finder and changer app Webilder also broke, but this is due to the fact that python-appindicator is not available in my current repos. Unfortunately I don’t see a way to fix it

What the hell happened to my Chromium???

There’s one big casualty in the upgrade process to KDE 4.7.2, and that’s the fact that the Chromium browser is borked. Every time you launch chromium-browser all your pages show the “Snap!” error, even the preferences page. It’s a known issue and to fix it you’ll have to install Google Chrome instead. The Google Linux repos are borked so you’ll have to install the it manually. Go to the Google Chrome website and download the package. Open the directory you downloaded it into and run this command in Terminal

sudo dpkg-i google-chrome-stable_current_amd64.deb

You can also install the package from Dolphin by double-clicking it, but if it opens in Ark you need to install a package.

sudo apt-get install gdebi-kde

That package will let you install packages with a graphical installer. Many Linux hate using graphical package installers like this, but it’s a matter of personal preference. I love being able to use Gdebi and had to do some searching to find it when I installed KDE on top of LMDE.

There’s one more thing to to before you launch Chrome for the first time. You’ll want to import your Chromium settings into Chrome, but there’s no settings import option that I was able to find. Luckily it’s easy to do. Just copy everything from ~/.config/chromium/ into ~/.config/google-chrome and all of your settings from Chromium will be available in Chrome, including your passwords, cookies, extensions and search engine settings.

[RESOLVED] Can someone help diagnose my Plymouth bootsplash issue?

Update 27 Nov 9:40a ET: I found a solution to my issue on the Linux Mint Forums. It turns out the instructions I read on the KDE-Looks page for Kmint seem to be missing some important steps. I’ve added them at the bottom of this post.

Update 28 Apr 2012: Stupid me just realized I had used a placeholder for the name of the file you need for Kmint but never actually went back and replaced it with the file name. Sorry about the confusion.

I got tired of the scrolling text boot on my LMDE laptop and installed Plymouth, but it’s looking pretty funky to me. I had been using the Kmint Plymouth bootsplash theme but it’s showing up as blank except for the progress bar on the bottom left of the screen and distro information (that isn’t even completely accurate) on the lower right. I switched to the solar theme from the package plymouth-themes-all but the same thing happened. I shot this video to show what I’m getting.

Sorry about the video quality and the lack of audio, but that’s what I got on my Samsung Restore (on Virgin Mobile). As the video shows I get the progress bar at the lower left corner, and other than the progressing bar I get the Debian version info on the lower right but nothing else until my Ksplash kicks in. Does anyone know what I may be doing wrong? If anyone needs more info just ask in the comments and I’ll add it to the post.

Oops! After posting this I remembered I took some screenshots that may help show the issue.  These two pics show the Kmint Plymouth theme.

I got it resolved, and here are the steps I hadn’t known about:

Install instructions

1) Install plymouth

sudo apt-get install plymouth plymouth-drm

2) Download and untar file for LifeInTheGrey’s Plymouth theme from  his original post on this Linux Mint Forums thread.

Download the attached zip file and expand it to /usr/share/plymouth/themes/

3) Set the theme

sudo plymouth-set-default-theme lmde

4) Modify grub to see the splash

gksudo gedit /etc/default/grub

Change:
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

5) Update initramfs and grub

sudo update-initramfs -u && sudo update-grub

Bam, you’re good to go! :D

You may need to restart a couple of times to get the changes registered. It took me two reboots to see the bootsplash. I’m changing my Plymouth theme one more time to get the Kmint theme enabled and I’ll snag a screenshot to show how it looks for me.  Here’s my Plymouth with a modified Kmint. I added a background while trying to get the issue resolved so it will look different from what’s on your system.

I’m not sure why I can’t get the statusbar, so I’ll have to dig some more. Here’s the lmde Plymouth theme, complete with the statusbar. I’ll be using it as my reference as I try to ID my last issues with the Kmint them. I will be passing my findings along to hellokitten, the dev of the Kmint theme.

Yoooouge thanks to LifeInTheGrey for the missing info.

[HOWTO] QuickTip: Install packages graphically on LMDE running KDE

Just a quick post to pass something along I just discovered. When I got my laptop with LMDE on it I had no problem double-clicking on Debian packages I had snagged and having Gdebi launch so I could install them, but the moment I installed KDE I lost that ability and couldn’t figure out how to get it back. Yes, I know I could install packages from the command line with a simple sudo dpkg -i [package name], but that’s a bit of a pain in the rear for someone who prefers to use GUIs for things whenever he can.

This morning I was checking out the latest post on Linux Mint 12 on the Mint blog and I noticed that “packages now open with gdebi” and just on a whim I fired up the Software manager and did a search for “gdebi.” Sure enough, I found gdebi-kde, and installed it, then I checked my theory by double clicking on a package I had installed. As I hoped, Gdebi opened in a window and asked me if I wanted to install the packge.

I’m a happy penguinista.

Posted in GNU/Linux, KDE, Linux Mint, LMDE. Tags: , , , , , , , , . Comments Off

[HOWTO] How to fix the broken spellchecker in LMDE’s LibreOffice

I’m using LibreOffice’s word processor to work on some translations for an open source project and I noticed that the spelling and grammar checker checker tool didn’t seem to work. I looked through all of the LibreOffice packages available for Linux Mint Debian Edition (LMDE) and couldn’t see what package I was missing so I did a Google search and saw mentions on several sites (sorry, I can’t find the sites in my history) about separate spell checkers not being installed.

This seemed odd, because I am able to check the spelling in other apps, from Chromium to even Dolphin, KDE’s file manager. I fired up my software manager again and saw that neither aspell nor hunspell were installed so I installed aspell and sure enough, the spelling and grammar checker in LibreOffice was finally working.

It turns out this is a frequent issue, and I suspect it shows up on other distros as well. I definitely saw it reported on Ubuntu and the Ubuntu-based flavors of Linux Mint. I was finally able to find Bug #836475: Spell checking does not work in LibreOffice and I posted a comment about the apparent missing dependency.

Need some computer case stickers for Linux Mint? I just found some for you.

One of the unfortunate things about using Linux is that you have to hunt to find a case sticker to cover the Windows case sticker on your computer or laptop. Granted a Google search will show up a number of folks who have stickers available that you can buy or download and print yourself, but if you run one of the flavors of Linux Mint you could only find stickers for the standard GNOME-based Mint.

I said “could” for a reason. I was running a search this morning and found a set of Linux Mint stickers on LinuxMint-Art.org. Sam Riggs was nice enough to include stickers for KDE, LMDE, Fluxbox, XFCE and even LXDE. There are two sizes for each sticker, the normal case sticker size and a larger image for other uses. Being from a good open source developer, Sam includes both PNG images and Gimp XCF files for each image. You have to supply your own sticker stock, and I’m seeing a comment about a problem with printing at 300dpi so you’ll want top print them at 1200dpi, but each image is a separate file so you can print as many images as your heart desires on a single page. I definitely want to print some Mint KDE stickers for my phone and cane, and when I can get a new computer I’ll print stickers for it, too.

Yooouge thanks to LinuxMint-Art.org user samriggs for creating the images. I owe you a brew.

Follow

Get every new post delivered to your Inbox.

Join 158 other followers