It is amazing how much time can be consumed with little devilish details! After searching Microsoft’s website, Canon’s website, etc., I found the key ingredient that was missing. Was it a device driver? Did I need the Media Feature Pack for Windows 10 N and KN versions? NO! I just needed this:
Simple fix: Disable WiFi in the camera settings, turn off camera, and turn it back on!
(Sheepish Grin)
I have experienced this issue several times through the years with my current hardware… each time I have to re-learn how to get around it. Here is the simplest one yet, thanks to “Leppie” at ubuntuforums:
sudo chmod a-x /etc/grub.d/30_os-prober
This disables the os-prober that Debian based OS’s run when updating the system.
I just experienced a substantial boost to my geek-ego… for the first time ever I succeeded in compiling a software program from source!
After upgrading my laptop to Linux Mint 15 over the last couple of days, I discovered that Bibletime 2.9.1 presented me with blank pages instead of Bible text, commentaries, etc. My first thought was “hmmm… maybe I’m looking at white text on white background?” No such luck. If that were the case, you could still click and drag over the text and copy/paste, etc. The window was actually empty where there should have been text, no matter which Bible, commentary, etc. was opened. I tried downloading a new copy of the KJV Bible using the Bookshelf Manager… still the same issue.
Well, let’s see what the newest version is at Sourceforge… Bibletime 2.9.2.
So… here is what I had to do to get it going… (please understand that this was MY wandering pathway, in MY installation… not all of these steps may actually be necessary, but the end result for me was good):
First, install some preliminary software that will allow you to compile it on Linux Mint/Ubuntu. The following commands (in italics) are to be typed or copy/pasted into a terminal such as Konsole:
sudo apt-get install build-essential checkinstall cmake
…and to satisfy dependencies for Bibletime (not certain that every package listed here is absolutely needed, but there were several that silenced some build errors…)
sudo apt-get install qt4-designer qt4-demos qt4-doc qt4-dev-tools libqt4-dev libclucene-dev libsword-dev libsword-utils libqt4webkit-dev curl zlibc libqt5clucene5 libqt5core5
Then, download the tarball from sourceforge
Then, make sure your /usr/local/src folder belongs to you and is writable:
sudo chown $USER /usr/local/src
sudo chmod u+rwx /usr/local/src
Then, move the downloaded bibletime tarball into /usr/local/src
Extract it with the following command (change the filename if you are using a different version of bibletime!)
tar -xjvf bibletime-2.9.2.tar.bz2
navigate into the new bibletime directory created in /usr/local/src:
cd /usr/local/src/bibletime-2.9.2
and finally, type the following command
make
(close eyes… hold breath… push Enter!)…
[please note: the following screenshot is a “re-creation” for illustrative purposes only! Contrary to what the picture shows, I did not install Bibletime in a folder on my Desktop!]
And now is when the terminal goes crazy with a mind-boggling array of things it has to do to compile human-readable source code into machine-readable binary code! If all goes well, in the end it will give you the path to the newly created binary:
/usr/local/src/bibletime-2.9.2/build/install/bin/bibletime
Now, you can use that line to create a shortcut in your menu system or on your desktop. For me, using KDE:
-right-click on the “Start button” (using Windows-Speak) or, more correctly in KDE… the “Application Launcher Menu” button.
-click “Edit Applications”
-select “Education” (or wherever you would like it to appear in your menu structure)
-click the “New Item” button and enter “Bibletime” in the window that pops up, and click OK
-select the new Bibletime entry in the menu editor tree, and type “Bible study tool” or whatever you like in the description line on the right.
-copy and paste the path to the new binary in the “Command” field. For me this was “/usr/local/src/bibletime-2.9.2/build/install/bin/bibletime” (do not type the quotation marks!)
And finally, before closing the menu editor, click on the blank square in the upper right of the menu editor window. This will bring up a window where you can select an icon for the Bibletime entry in the menu. Click on “Other icons:”, and browse to /usr/local/src/bibltime-2.9.2/pics/icons/bibltime.svg
-click on the “Save” button on the menu editor window
Hopefully, when you click on Bibletime in your menu, it should fire right up! Enjoy!
(This pic was created in Sketchup.)
This is what our existing jailhouse food tray racks look like inside our mobile food carts. The food carts are loaded up in the kitchen, and wheeled down to the jailhouse dorms by a couple of trusties. The current carts are barely more than 3 years old, and already have been welded and repaired numerous times. They are literally coming apart at the seams. I think the manufacturer had no idea how to build for the kind of abuse these things get.
My intention is to use the existing racks, and build a far superior cart around them… at least digitally. Whether or not it ever gets built in reality is subject to budgets, chain of command, etc.
I’ve been enjoying Linux Mint 14 KDE version for some months now, but decided this morning to update to KDE 4.10 using Ubuntu’s KDE-Backports PPA (Personal Package Archive). Here is a screenshot:
It seems to be working very nicely. I haven’t noticed any of their many changes yet… which is probably a good thing. One minor issue from recent versions does not seem to be fixed yet: whenever I try to place plasma widgets any closer to the top of the screen than you see in the screenshot, they automatically move back down (about 1/2 inch from the top). Strange. Perhaps it’s a “feature,” not a bug!
To add the Kubuntu Backports repository, press Ctrl-T (to open a terminal), and type the following:
sudo add-apt-repository ppa:kubuntu-ppa/backports
You will have to type your root password, then you will be asked to confirm that you really want to do this. Press Enter.
When it completes, you will need to type the following command:
sudo apt-get update
followed by this command:
sudo apt-get dist-upgrade
This will begin the download and installation of all the new KDE 4.10 packages. A reboot will be necessary after it completes. Enjoy!
Someone tried to make some purchases today using my Wells-Fargo/Visa check-card info at Walmart.com. Site-to-Store… to Merrilville, IN. Thankfully, Walmart.com recognized this somehow as a fraudulent transaction, and refunded the 276.06 within minutes, while I was still on the phone with Wells-Fargo! Bravo to Wal-Mart, and to the quick work of the Wells-Fargo customer service rep. Another attempt for over $400 was made after the card had been blocked. Thank you, Lord, for my guardian “angels” at Wal-Mart and Wells-Fargo! 
My old Compaq desktop recently decided that Microsoft Vista was no longer welcome. I mean, Vista just wouldn’t boot. Linux booted fine, but no amount of reinstalls, tweaks, etc. would get Vista going. I needed Vista only for the purpose of running a Microsoft Access database. So, I decided that this was as good of an excuse as I was going to get for buying myself a decent laptop.
I thought I would try to get something with Intel based cpu and graphics, since everything I currently used had older Nvidia graphics, and AMD processors. I just wanted to see how Linux and Intel get along. I should have studied up on things a bit more before buying!
I purchased a used Gateway NV79 from Ebay, with Intel i5 cpu, and ATI Mobility Radeon HD graphics. Windows 7 works beautifully, Linux, not so much…
I tried the following Linux distributions…
Linux Mint 14 64bit Cinnamon: no backlight on monitor after bootup
Siduction 12.2.0 -rc2 64 bit: no backlight on monitor after bootup
OpenSuse 12.2 rc 64 bit: no backlight on monitor after bootup
Antix 12: monitor backlight worked, but wireless network wouldn’t.
Rosa 2012 64 bit: no backlight on monitor after bootup
Kubuntu 13.04 alpha 1 64 bit: no backlight on monitor after bootup
Fedora 18 beta 64 bit: no backlight on monitor after bootup
Chakra 2012.12 64 bit: don’t remember for sure, but I think the monitor worked, but the wireless didn’t.
And FINALLY… I discovered the download for the upcoming Linux Mint 14 KDE version, and… everything works, once it is fully installed. The laptop monitor backlight did NOT work while running from the live-dvd, meaning that I had to shine a flashlight on the monitor to see what was going on during installation. That’s a little tricky… because it’s easy to lose track of your cursor… but once installation was complete, and I rebooted from the hard drive, everything works beautifully. Well… as long as I don’t close the laptop lid. Then the backlight goes off, and I have to get the flashlight and log out of the desktop and log in again, and the backlight comes back on. (Edit, 2/28/13: I’ve since discovered that Ctrl>Alt>backspace, which logs out of KDE, will bring the backlight back on, and allow me to log in and get to work. I am still using this installation, and am quite happy with it, and with the new laptop!)
I came home from my first cross-country Amtrak experience with a whole bushel-basket full of pictures. Much to my consternation, I discovered that the camera’s date and time settings were almost 5 days behind. After much investigation, I decided that jhead was the best way to fix the problem. So, here is the jhead command I used:
jhead -da2012:11:09/13:52:04-2012:11:04/19:59:04 *.jpg
This translates to: “jhead -da(correct date/correct time)-(wrong date/wrong time) fix anything with a .jpg filename in the current folder” (I probably could have just used * without the .jpg, because in most of my picture folders, only the jpegs have metadata.)
I determined the correct time from a photo that included my Tom-Tom GPS, which was stuck on the train window. I brought it for the entertainment value of knowing how fast we were moving, and where we were. By the way, from Florida to Washington, D.C., the max speed was usually right around 80 mph. From D.C. to Philly, on improved tracks and with electric engine, the max speed was more like 110 mph.
Jhead calculates the difference between the two date/time entries, and adjusts every date/time entry in the exif metadata by the calculated difference!
Then, because I rename my pictures by the exif date/time, I used the following jhead command to fix the filenames:
jhead -nf%Y-%02m-%02d_%02H-%02M-%02S *
Next time I have a metadata issue with jpegs, I’ll look carefully at jhead’s documentation page FIRST!
I very much enjoyed sharing this talk earlier this evening with our Wednesday night Bible study group. Promises, Promises: Hebrews 10, 11, 12
Lin-u-Type 