To celebrate the LibreOffice Bug Hunting Session yesterday and today I wanted to make notes of some desktop issues I’ve had lately, and have mostly overcome.
To preface, there have been times in the last year where I have been very close to pitching my Linux desktop operating system over issues that seem to reveal that it just does not have the stability, reliability or “usability” that an average person needs. Like when a home computer is malfunctioning, or I’m trying to support a family member’s new system and issues keep coming up I have been tempted to toss the system and move back to Windows, primarily to simplify things and create an environment where the variables are less dependent upon me.
I’ll add a couple of caveats to the paragraph above. Linux is very customizable, which is a great strength of it, but also is dangerous. It is easy to delve into configurations that are open which should be left alone; in a Microsoft or Apple environment those doors are sealed shut for the most part. Another issue is that I update a lot. Almost everyday. I should be more patient– it’s a bad habit.
Overall the last six months has actually strengthened my resolve to stick with the OSS community, and especially their operating system. My OS of choice is OpenSUSE, and I have found that the forum members have been sincere, jovial and compassionate. It is worth sticking with the Linux system if for nothing else than the community.
Here is a log of some issues I’ve allowed to build up in my system, and how I went about solving them.
Hibernation Mode broken
My hibernate splash screen has been “command line” instead of a graphical splash screen. So I began following this bug and this page. Eventually by adding a development build of splashy and adding some custom code I got a fix.
I found you could adjust settings here /etc/suspend.conf to:
## use splash picture? (default y) splash = y
Since then the standard repositories have updated, and I think for the most part this is fixed. I have also found some splashy configuration files here: /etc/splashy/ and usr/share/splashy/themes/.
LibreOffice won’t load because of Java issue
I began having an issue whenever I would try to launch LibreOffice. The error would state: javaldx failed! Warning: failed to read path from javaldx.
I knew this had something to do with Java, and thought perhaps it was a Java 1.6 vs 1.7 issue. Earlier this year I was finding that LibreOffice would have issues when I installed the new Java application on Windows computers, I think this is fixed now. But no Java upgrades or downgrades would help. Currently I use Java 1.6 OpenJDK which I’m happy with, except for the occational propritary webap which requires Oracle’s version, rather than the opensource OpenJDK version– see here for the news of the removal of Oracle pulling back their free licence earlier this year.
Finally this was a very basic fix. I simply changed the permissions of my ~/.libreoffice directory to 766 in Terminal and LibreOffice worked! Then I realized that I had recreated my user profile, and this is when I began having trouble.
Next time I create, copy or attempt to duplicate a username I need to make sure I adjust all the directory permissions.
Private XMPP server on kde?
I would like to use a kde client with a private xmpp server like OpenFire, but I haven’t had luck with kopete or telepathy, spark and pidgin work for me though. I used to use Kopete entirely on my KDE desktop, but now have reverted to using Pidgin which I haven’t used for a long time.
There is a KDE Bug out there which seems to be getting no love. I would love to see a patch for this… but fix in sight yet.
Discombobulated Font Rendering
After installing quite a few updates on a system my font rendering was entirely messed up. This was at a point when the unstable kde-telepathy presence module really messed up my system, and I had to delete and restart my ~/.kde4 directory. I reinstalled fonts, and the freetype2-devel package (which is REALLY, REALLY great), and fetchmsttfonts (or msttcorefonts in some systems). Still no help.
I then realized I had not readjusted my KDE Font Settings. So then I went in and enable anti-aliasing, and then configured the rest of it. I still had issues. I rebooted, tried different profiles, still no fix. But my other Linux computers were fine, and the issue was especially related to Google Fonts on a particular website which now looked really ugly.
Finally today I found the issue. I had not configured my anti-alias font setting correctly, or I had gone overboard. I had selected an “excluded range.” Taking this off, and keeping sub-pixel rendering to RGB, and hinting style to Medium I had a beautiful desktop once again!
By the way, if you have not taken advantage of freetype 2.4, please do, it makes for a shiny, clear looking graphical interface. Also, upgrading graphics cards and adding DVI cables where ever possible lately has also made a huge difference!







