The LS660ZV6_01.zip update has been dogging me for about a month on my Virgin Mobile LG Tribute phone. I couldn't install it. No matter what I did, there was "insufficient space" to do so. I finally got the update installed, and I will share my not-so-secret discovery with you.

tl;dr: You need 550 MB of free space to install the ZV6 update on the LG Tribute. Start deleting app data and full apps until you get there. Then try to install the update that has been dogging you and eating up your data for at least a month if not longer. It should work.

Even though the LS660ZV6_01.zip update is supposed to be "only" 73 MB in size, the most internal memory I've been able to free up by clearing out app data and cache was 300 MB. And the update still won't install. There is still "insufficient space" to cram this supposedly 73 MB update on my LG Tribute's 4 GB of internal memory.

Read the rest of this post

I just removed the social-sharing buttons for Google Plus and Twitter from this site.

Even though almost every http request for content on this Ode-powered blog is done via Perl CGI on shared hosting, the site is extremely quick.

And these two social-sharing buttons, which appear on every entry, were really slowing things down. (Instead of a third-party social-button service, I used embed code provided by Google and Twitter, respectively).

The question/dilemma I face: Is the reduced "performance"/speed of the site a fair tradeoff for what the social buttons have to offer?

Read the rest of this post

Even though I have a working Citrix installation in Fedora 22, my recent failure to replicate it in Debian Jessie has me worried.

To that end (and so I will have a place to go when I need to do this again and again), here is a list of Citrix-on-Linux how-tos:

Overall Linux

Citrix: Receiver 13.1 for Linux

Fedora

Install Citrix Receiver 13.1 on Fedora 21 x64 by Chris Savage

Installing Citrix on Fedora 21 by Ken Fallon

Citrix Receiver on Fedora 19 64 bits from Ask Fedora

CITRIX ICA (RECEIVER) 13.1 UNTER FEDORA 20 (64BIT) from iSticktoit.net (in German, but understandable from a Linux perspective)

CITRIX RECEIVER 13.2 (ICA) ON FEDORA 22 (KDE) from iSticktoit.net (in English)

Ubuntu

Ubuntu Community Help Wiki: CitrixICAClientHowTo

Installing Citrix Reciver on Ubuntu 14.04 LTS (Trusty Tahr) by Ken Fallon

How to install Citrix Receiver icaclient in Ubuntu 14.04 LTS 64-bit – tested and working using Mozilla Firefox by Mark911

Quora: How do I run the Citrix ICA Client on Ubuntu? by Cesar Augusto Nogueira

Debian

Superuser.com: How do I install Citrix ICA Client (Receiver) 13 on Debian 64-bit Linux?

Arch Linux

(Often the Arch Linux Wiki can help users of any Linux system, regardless of distribution)

Arch Linux Wiki: Citrix

RHEL (and CentOS)

UC Berkeley Knowledge Base: How to install the Citrix Receiver using Red Hat Enterprise Linux (RHEL) 6.5

Update on Nov. 18, 2015: I finally did succeed in getting Citrix ICA installed and running on Debian Jessie.

I can't find the exact web page I used for help, but the "core" of my successful method was adding the i386 architecture, updating my sources and then installing Citrix from the .deb package:

# dpkg --add-architecture i386
# apt-get update
# apt-get upgrade
# dpkg -i icaclient(bunch of other stuff).deb

So I now have Citrix ICA working in Debian. I use it through Chromium, so I don't have to go through any machinations to get CACerts into Firefox/Iceweasel.

Now that I have Citrix working on Debian, the stable Jessie release is a viable alternative for me. But since I've grown very accustomed to having the much-newer packages of Fedora (and I'm not as willing to run Debian Sid), I am looking at Xubuntu, staying with Fedora, or the Korora spin of Fedora.

The original post:

I've been having networking issues on the Fedora 22 installation I've been using and upgrading since it started out with Fedora 18 in early 2012.

None of my attempts at fixes seem to bring the network (principally the wired network, whether I'm using it or not) back after suspend/resume, though I have a quick-and-dirty script that I can run from my application panel when I need it.

So that means it's time to audition new distros. I love Debian, and I tend to end up with it when my hardware starts to age. And yes, a 3 1/2-year-old laptop is aging as these things go.

So I'm auditioning distros. I continue to like Xubuntu, and reinstalling Fedora is always an option, especially since the networking problem is not present in the live environment.

But I wanted to try Debian Jessie. I'd love to be running Debian Stable.

Read the rest of this post

I'm getting tired of the constancy of keeping a Fedora Linux system up to date.

I've got plenty of bandwidth, and I often do appreciate all the newness that Fedora constantly brings to the table, even within releases.

But while there isn't much breakage, there is breakage. It usually gets fixed within two weeks to a month. And I know that "stable" distros can suffer with breakage for the entire period of the release.

But I'm weary of the sheer number of update in Fedora.

There is a way to make it ... less:

Just update less often. I tend to update daily. I could definitely get away with doing it weekly. And in the absence of major security issues I might even be able do it monthly.

Just not daily.

Briefly, for no good reason, my networking on the HP Pavilion g6 2210-us is broken after suspend/resume in Fedora 22.

It's not broken on live Fedora 22 and Xubuntu 15.04 images. It wasn't broken a week ago in the Fedora 22 system I've been upgrading since I started it with F18 in 2012.

I should probably just reinstall. And I probably will. Xubuntu on a new drive. Soon.

But until then, I need networking to return after a suspend/resume.

I've tried lots of things. Nothing has really worked. Closest is Wake-On-Lan issue with Realtek r8169: immediate resume after suspend from the Ubuntu Forums.

That script doesn't work.

But it did give me the idea to just run the modprobe lines:

$ sudo modprobe -r r8169
$ sudo modprobe r8169

That works. The network comes back (both wired and wireless, even though this only addresses the wired Ethernet network).

The script in /etc/pm/sleep.d seems to do nothing.

But running this script, which I titled jump_start, does work:

#! /bin/bash

modprobe -r r8169
modprobe r8169

exit 0

As a workaround, I created a launcher in Xfce, hooked it up to this two-line Bash script, and made an exception for it with visudo so I could run it from the launcher.

Now I resume the laptop, click my "jumpstart the network" icon in the panel, and I'm ready to go.

It's less than automatic, but for now it works.

I have no idea why this happened, but since every new live system I try suspends and resumes with no problems at all, this hack will keep me going until I build my new Linux system on a new hard drive. (This is a "production" laptop, and I want to avoid the anxiety of having to rebuild and configure it under pressure, so I'm opting for a new hard drive that will be a single-boot Linux system.)

Update: I may be putting my scripts in the wrong place for automatic execution in a Systemd environment. Fedora users suggest /usr/lib/systemd/system-sleep/

This is the script I put in /usr/lib/systemd/system-sleep/:

#!/bin/sh

case "$1" in
    hibernate|suspend)
   systemctl stop NetworkManager.service
        modprobe -r r8169
        ;;
    thaw|resume) 
        modprobe r8169
  systemctl start NetworkManager.service

        ;;
esac

I'm not convinced that any of this (other than running my jump_start script with the two modprobe lines) is working.

Further update: A day later, I've been using WiFi only, and the network has been available after suspend/resume with no trouble. Not sure why.

Further further update: It's spotty. I'm taking the script out of /usr/lib/systemd/system-sleep/ -- I don't think it's doing a damn thing. I still need my local script sometimes to jump-start the network.

Oct. 10 update: Things seem a lot better. I'm not 100 percent sure the problem has been solved. Maybe 80 percent.

I'm surprised that the Fedora documentation for working with GRUB 2 doesn't address rebuilding GRUB 2 entries for EFI booting.

They do address it, but they get it wrong.

The grub2-mkconfig instructions for both BIOS and UEFI systems are the same. The problem is that this instruction will only build the BIOS entries. The UEFI entries won't be rebuilt.

Once you have your changes set in /etc/default/grub, here is how to rebuild the GRUB 2 entries for BIOS and UEFI systems?

BIOS systems

# grub2-mkconfig -o /boot/grub2/grub.cfg

UEFI systems

# grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

It is perfectly OK to do both of these commands (using root, hence the # prompt, or with sudo), but you do need the one that matches your booting method (BIOS for older systems, optionally UEFI for newer systems).

The only reason I figured this out is because I poked around quite a bit when having dual-booting issues. Someone should fix the Fedora GRUB page. I'm a Fedora member and could probably make the fix myself, but I'm not 100 percent sure what I'm doing here is the absolute best method because my GRUB bootlines after doing this look different then they do when the system (either yum or dnf) does a kernel update.

I needed to use LibreOffice today. It's not something that happens very often. I almost always write or edit in a text editor, web form or Google Docs. But today I opened up LibreOffice.

I wanted to use "automatic" spell-checking in LibreOffice, which you invoke with shift-F7. But it didn't work.

I looked at my default "language," which was U.S. English. There was no little blue check next to it that indicated it had a dictionary. I checked my packages. I wasn't missing English.

It turns out there's a hack that gets spell-checking working and gives me the red squiggly lines under my misspelled words (that's the way I like to do it.

I found the answer in LibreOffice's "Ask LibreOffice" forum (which uses the same software as Ask Fedora).

Here is the fix from that helpful post:

Under Tools -> Options -> Language Settings: Writing Aids, the list of available language modules showed almost everything set. I unchecked and then re-checked "Hunspell SpellChecker" and "Libhyphen Hyphenator" and hit OK. (I strongly suspect that the hunspell was the significant checkbox). Then, when I go back to Language and look at the default language settings, the "English (USA)" entry has the ABC✔ by it, and now spell checking is working.

Best guess is that some results of invoking something from hunspell is saved by libreoffice and that with updating versions, the cached output is no longer valid. Re-invoking (when re-checking the checkbox) refreshes the cached data and now everything is all better.

It sure worked for me.

I like to learn by doing. I'm reading and typing in code and futzing around with it. But I had an idea, and I'm betting I can learn what I need to make it happen.

The idea is a "What is this acronym?" app, where there's a web page, the user types in an acronym (or partial acronym) and gets in return a list of possible full names for that acronym.

Nothing too crazy, and I'm going to keep it as simple as I can.

I want to do it as a single-page JavaScript app. Call it "just a web page with some interactive JavaScripty elements." Is that an "app"? (Don't know, don't care).

I'm choosing JavaScript for this project because I want to keep it simple. And I want to learn JavaScript.

Read the rest of this post

Today I started playing with Java arrays.

I'm also trying to figure out JavaScript objects at the same time.

(The Javascript is for a project I'm cooking up. I'll focus when I'm ready to focus.)