Getting XMind 8 to work on openSUSE Leap 15

openSUSE Leap 15 was officially launched on 25th May 2018.  More at https://en.opensuse.org/Portal:15.0

XMind is my go-to mind mapping software for a few years now.  More at https://www.xmind.net/

Challenge:

Using the XMind 8 Linux package (zip file) and following the, albeit brief, instructions at http://support.xmind.net/customer/en/portal/articles/2639667-begin-to-use-xmind-8-on-linux, you will see XMind launch with the GUI Splash screen but the program will fail and exit.

Root-cause:

XMind is a Java-based application and it is sensitive to the version of Java.  The default Java runtime in openSUSE Leap 15 is OpenJDK version 10.0.1 (dated 2018-04-17).

Resolution:

Install the older OpenJDK version 1.8.0.  Instead of removing the default version 10.0.1, I elected to install the older version 1.8.0 alongside and switch the default path for Java to 1.8.0.

Here are my steps:

zypper in java-1_8_0-openjdk

update-alternatives --config java

(followed by picking the newly installed jre-1.8.0)

Validate:  java -version

That's it.  Now, when we execute the XMind program, it will work and launched successfully.  

Keep Calm & Carry On loving Linux!

openSUSE Leap 42.3 on Google Cloud Platform (GCP)

Blogging... I'm glad I started in 2008, it is like having a diary that you can never misplace... and reading some old entries can bring back wonderful memories, as I recall and review the course of my life from this, albeit narrow, technology perspective.

Anyway, its been a good 4+ years since my last entry and the longest hiatus... glad and grateful to say that I am now working for Google.  My personal Linux passion is still very much alive and personal bias towards all things SUSE (more openSUSE since 2011).

Problem Statement:

So, it is May 2018 and I am little disappointed that openSUSE Leap did not make it to the out-of-the-box public images on Google Cloud Platform (GCP).  However, it is listed in the "Community supported images" category.

PS:  I'm placing my vain hope that Leap 15 will make it though...

This blog entry describes the steps to create a vanilla openSUSE Leap 42.3 VM on GCP and thereafter, create a custom image from this said VM so you can easily/quickly create openSUSE Leap 42.3 VMs for other workloads in the future through the GCP Web Console.

From this point on, I will assume you have a GCP account and therefore access to GCP consoles etc.  It is not difficult to start with Google Cloud Platform, just go to https://cloud.google.com/free/ to get a Free Tier account.

Create an openSUSE Leap 42.3 VM on GCP:

1. Login to your GCP console and your project (default or otherwise).
2. From Menu (top-left),  Compute Engine -> VM instances
3. Note that openSUSE is not listed as an Operating System image when you try to create a new VM.  This is well documented at the Images section of the Compute Engine topic.
   
4. Launch the Cloud Shell within the console, on the top-right.
   
5. Find the available community supported openSUSE Leap image with the following command input to the Cloud Shell. 
• gcloud compute images list --project opensuse-cloud --no-standard-images 
6. Create a VM with the openSUSE Leap 42.3 image in the Singapore datacenter (or any Zones that is closest to you)


•  gcloud compute instances create osleap423 --image-family opensuse-leap --image-project opensuse-cloud --zone asia-southeast1-a
• For Reference, the available parameters for gcloud compute instances create at this link - https://cloud.google.com/sdk/gcloud/reference/compute/instances/create
• Verify that the VM has been created in the console 
  
7. SSH into your newly created openSUSE Leap 42.3 VM to download and apply the latest updates/patches.  Click the SSH button (see screenshot above).
• Once you SSH into your VM,  zypper up.
  
  
8. Reboot the VM to test all updates are working.
• Reboot:  sudo reboot.  You will lose SSH connection, naturally.
• Sign back in via SSH button... it may take a few tries as the VM is rebooting.
• Sign out of SSH:  exit
9. Shutdown the VM.  Select the VM (checkbox) from the Console and Click STOP.

Create a custom image in your GCP Project for Re-use later:

1. From the GCP console, navigate to Compute Engine -> Images
2. Click [+] CREATE IMAGE 
   
3. Put in the name of your new image (eg. my-opensuse-leap-423) and select Source as Disk and Source disk as the boot disk from the right VM (eg. osleap423).
   
• (Optional) You can click the command line link at the bottom to note the equivalent Cloud Shell command.  This is useful if you want to script actions for future re-use and not use the web-console.
4. Once your custom image is created, you will be able to select it for the next VM you wish to create.

Enjoy! :-)

My openSUSE 13 Journal 1: Getting IBM Notes 9.0.1 to work!

Its a new year (belated) and 13.1 has been out for quite a while now.  I had it running in a VM as an evaluation and did not really move my desktop setup from 12.3 up to 13.1 until last weekend.

In the meantime, a few readers has corresponded with me via comments in my previous post about getting IBM Lotus Notes 9 Social Edition to work on 13.1.  My initial favourable responses were based purely on a very quick install and startup tests (it all looked good).  Unfortunately, there appears to be a little bug with the combination of openSUSE 13.1 and IBM Notes 9.0.1 but it is a very small one and the resolution is ridiculously simple (but not immediately apparent).

I hope to blog more on 13.1 at a later date but will only focus on getting IBM Notes 9.0.1 working on 13.1 in this entry.  I have been having some difficulties in my personal health lately and that only takes time away from pursuing my hobbies (blogging here being one of them).

First, I would like to acknowledge Craig for bringing to my attention the challenge and so proactively providing the links to his discussions in the Lotus forum (here).  I would also like to Thank Ashu for his encouraging comments left on my previous blog entry and hope this entry will be just as useful to those out there who share the same fascination of using openSUSE and IBM Notes.

Installation - Easy as pie

As documented in previous blog entries, installation of IBM Notes 9.0.1 is really a piece of cake.  You download the binaries (NOTES_9.0.1_LINUX_RPM_EN.tar), untar it into an empty directory and you will find 5 RPMs (i586 - 32-bit) and a few other files.

As root, execute the following in the same directory:

zypper in *.rpm

Done!  You will find the IBM Notes icon in the Recently Installed Apps folder in KDE4.  Alternatively, the launch icon can also be found in the KDE::Applications::Office::More Programs::IBM Notes.  Right-click and Add to Favourites to easily find it the next time.

First sign of trouble

First sign of trouble, at least for me, only occurred after successfully launching IBM Notes and when I get into my mailbox, view calendar or log into SameTime.  The GUI would freeze and then IBM Notes would terminate and NSD runs.

My IBM Worklight Studio Software Appliance via SUSE Studio

Its been quite a while since I've created any software appliance via SUSE Studio.  This blog entry describes the motivation behind and the details of my IBM Worklight Studio Developer Edition software appliance created via SUSE Studio.

Background

IBM Worklight is the mobile application platform that is part of the IBM MobileFirst solution.

IBM Worklight Studio is the development tool for creating web, hybrid or native mobile apps that runs on the IBM Worklight platform.  IBM developerWorks also host resources on working with IBM Worklight, here and here.

IBM Worklight Studio Developer Edition V6, release in June 2013, is freely available as a plugin on top of Eclipse Juno V4.2.2.  Also freely available, is the Rational Test Workbench plugin that provides functional testing of mobile applications created by Worklight Studio.  Both plugins can be found on the Eclipse Marketplace.

* From this point forward, I will use "IBM Worklight Studio" to mean the IBM Worklight Studio Developer Edition for the rest of this blog entry *

Motivation

The installation and configuration of IBM Worklight Studio and the Android SDK will take at least an hour or two. This is very much dependent on your network download speed and readiness of your OS/machine (or virtual machine).  

By the time your IBM Worklight Studio and the Android SDK is ready for action, you will probably opt to go for a coffee break first.  :)

Therefore, to shorten the time to evaluation and also improve productivity of fellow developers out there who wants to focus on evaluating the tool from a development perspective, I thought a software appliance with everything pre-installed and configured would be helpful.  

Since I cannot give out Windows or Mac OS virtual images without running into license infringement issues, I chose to use SUSE Studio to construct a openSUSE based virtual machine with all the required IBM Worklight Studio components installed and ready to go.

Link to my Appliances

I have created two editions of my software appliance:

RTR - Ready to Rock edition (Link)

ARTR - Almost Ready to Rock edition (Link)

The RTR edition is a complete and ready to go stack with all software installed and configured.  I have also included a library of tutorials downloaded from IBM developerWorks on the subject.  You can start developing your first mobile app straight away and can deploy that onto the Android Emulator.  If you have an Android phone connected via USB to the VM, you can also deploy your mobile app onto your Android phone for testing.  However, the size of the appliance download is 2.4Gb (compressed).

The ARTR edition has a smaller footprint of only 1.5Gb (compressed).  However, you only have Eclipse Juno V4.2.2 installed and you will need to install the IBM Worklight Studio plugins on your own.  The effort is not strenuous for the operator but you'll need good Internet download speed to install the plugins via the Eclipse Marketplace.  All tutorials on installation are included in the Tutorials folder to help guide you through the process.

PS:  For those who are new to SUSE Studio, you do not need to sit around and wait for the download to complete before you can see the appliance in action.  Use the Testdrive option to have it provisioned in the Cloud for an hour and you can interact with it remotely from your web browser.  

That's all for now.  Please let me know what you think by leaving a comment on the SUSE Studio Marketplace or here on my blog.  

Have Fun!

PS:  Happy Father's Day to Australians who celebrate it on this day.

My openSUSE 12 Journal 14: IBM Notes 9 on 12.3

Syed Tassawur Hussain, this is for you.  Thank you for prodding and giving me the motivation to complete this blog entry on how to install the GA version of IBM Notes 9 Social Edition.

Back in the days of using 12.2, IBM Notes 9 was in Beta and I have blogged about how I installed and configured this combination here.

With my move to 12.3, I was going to install the now GA version of IBM Notes 9.  Given how impressed I was with 12.3, and all the additional software and customizations applied in 12.2 seems to transfer seemlessly to 12.3, I was naturally mildly surprised (and annoyed) that installation of IBM Notes 9 did not go quite as smoothly as Notes 9 Beta on 12.2.

Let me jump to the crux of the matter, one particular library (libjpeg62) has been removed from the media and default online repositories of 12.3.  This libjpeg62 was previously in 12.2 and earlier versions of openSUSE.  As such, IBM Notes 9 installer and even zypper were not able to install execute successfully.

Here's how I arrive at this conclusion and was able to successfully install IBM Notes 9 on openSUSE 12.3.  While I have not tried this on the enterprise flavour of openSUSE (ie SUSE Linux Enterprise Desktop 11), should you encounter the same challenges, the steps below may be of help.

My openSUSE 12 Journal 13: NetworkManager Config for Cisco LEAP Wireless

This is my 100th blog entry!  

In short, I wasted a few days and a weekend to get my shiny new 12.3 to connect with my company's Cisco LEAP (henceforth referred to as just LEAP) wireless network.

For those who do not have a requirement to connect to wifi via LEAP but are curious anyways, please see this link for LEAP.

To save you the same grief, here is the answer (see screenshot below) on how to configure NetworkManager:

The one on the Left WORKED; the one on the Right did NOT work for me

Disclaimer: Your mileage may vary (YMMV) because I did not test this against another LEAP wifi network outside of my company's implementation.

My openSUSE 12 Journal 12: Hello 12.3!

Hello openSUSE 12.3!  You were released into the big bad world on 13 March 2013 and you are fantastic!


Two weeks back, I installed 12.3 onto a new partition on my primary workstation/laptop in one hour.  By the hour thereafter, and I do need to install quite a handful of additional software, I was working on my day job without skipping a beat.  One of the software that is critical to my job is IBM Notes 9 Social Edition. As covered in my previous blog entry on the beta, IBM Notes 9 has been officially released on 2 March 2013.  Look out for my next blog entry on installing the Generally Available(GA) version of IBM Notes 9 Social Edition on openSUSE 12.3.

Hand on my heart, 12.3 is a very worthy successor to 12.2.  I am very happy with it, and if you know me, that says alot... BUT... there is one little usage/design point with the GUI of NetworkManager that got me confused and I was unable to get onto my office's Cisco LEAP wireless network.  This was resolved eventually (after 3 days and a weekend) and it turns out to be a non-issue... or a usage issue... or... anyway, look out for this in my next entry.

Installation and Partitioning

My openSUSE 12 Journal 11: VirtualBox

This should be an interesting entry in light of the recent developments in the roadmap of both Fedora & openSUSE where MySQL is being ditched for MariaDB.  This will affect new enterprise deployments in the next 18-24 months when the changes cascades into the next major release of RHEL & SLES.

At the heart of these changes is the perceived lack of openness & transparency of commercial juggernauts shepherding open source projects.  Another example is LibreOffice, being a fork of OpenOffice a few years back, and is now the default in openSUSE distributions.

VirtualBox was originally from Innotek GmbH and they were acquired by  Sun Microsystems Inc. in February 2008 which in turn got acquired by  Oracle Corporation in January 2010.  Virtualbox is not shipped as a default on openSUSE but you can install it very easily because the binaries are available in the default online repositories.

Personally, I think VirtualBox is the 'BEST' virtualization software for the desktop. I would go with KVM or even Xen for enterprise server virtualization. However, for virtualizing Windows or Linux on a desktop for quick testing purposes,  I'll pick Virtualbox anytime for its ease of use & free of cost attributes.

Easy Install Method

My openSUSE 12 Journal - 10: Chinese text input (fcitx)

I need Simplified Chinese text input capability for my desktop.  Back in openSUSE 12.1 and prior versions, it was SCIM that provided that functionality.  In openSUSE 12.2, FCITX replaces SCIM.

How do you add secondary language input capabilities?

This section applies to all openSUSE and SUSE Linux Enterprise versions.  Thanks to YaST, the way to enable this functionality has remained consistent over the years.

In YaST, find and select Language (under System).

In the Secondary Languages section, select and put a check mark next to Simplified Chinese... and any other language of your choice.
Click Ok button and YaST will install the proper software and language package to enable this functionality.

(Optional):  You might want to log out and log back in to your account, just to be sure there is a new language input icon in your System Tray.  In my experience, the icon shows up without a need to log out and back in again.


Frustration #1:  Where is the configuration panel?

My openSUSE 12 Journal - 9: Upgrading to Stable Kernel 3.7.4

I took every step and every precaution, with fear and trembling, but I finally took the plunge to upgraded my default kernel (3.4.11) in openSUSE 12.2 to the latest stable kernel (3.7.4).

You know what?  This is the best thing I could have ever done for my laptop!!!

Special Thanks to Mike Veltman, appreciate your guidance and encouragement.

What made me do it?
I have been using openSUSE 12.2 for over 3+ weeks and have noticed some performance issues from a desktop productivity perspective.  This was confirmed when speaking with Mike and also confirmed by a comment from Jack Bauer on my previous blog entry.

Scenario:  Try copying a large amount of files (total file size of say over 1Gb) from your hard disk to an external USB drive.  During the file transfer (doesn't matter if you initiate the transfer via commandline or GUI), the rest of the desktop (except the mouse pointer) is practically dead and unresponsive.  At best, a simple task of opening a new tab on Firefox to surf will take over 10 seconds.  If you want to open LibreOffice to read a doc/spreadsheet, you can forget-about-it.

This was initially tolerated because I would schedule large file backups in the evening after work.  However, it is starting to get to me because I don't recall earlier openSUSE 11.3, 11.4 and 12.1 ever giving me such issues.  The final straw came this week and its my Windows VM... it was running well but I have to put PGP whole disk encryption on the VM.  As expected the Windows VM slowed down but I also noticed its slowing my host as well.

How I did it?

My openSUSE 12 Journal - 8: IBM Notes 9.0 public beta

I was going to install Lotus Notes 8.5.3 on openSUSE 12.2... but a good friend of mine (Lotus geek) informed me that the next great version IBM Notes 9.0 is ready as an open beta.  He challenged me to live life on the edge again and, I accepted!

Link to download IBM Notes/Domino 9.0 public beta
Link to the public beta forum.

I would like to draw your attention to the fact that IBM has dropped the Lotus brand and name this new major version IBM Notes 9.0 Social Edition.  This is a great statement of intent and direction for this product/solution.

Installation:

Pre-requisite:  You will need to uninstall previous versions of Lotus Notes (if any).  Note that installing both 8.5.x and 9.0b is not supported (officially).

After you have downloaded the tarball for Notes 9.0b, untar it.  You will notice a bunch of RPMs and a smartupgrade.sh script.  Run/execute the script as root.  Its really that simple.

[Update on 23 Jan 2013]:  If running smartupgrade.sh script did not work for you, don't fret.  In the same directory where all the ibm_* rpms reside.  Execute, as root, zypper in ibm_*.rpm and let zypper figure out all the dependencies for you.  All good. 

The Notes 9.0b icon can be found via Application Launcher -> Applications -> Office -> More Programs -> IBM Notes.  You can right-click and select Add to Favourites so that you don't have to navigate that much just to start it later.

Note that in your very first startup, it will launch a text console for you to accept the license... just in case you miss it and wonder why you are stuck at the splash screen and nothing happens.

My openSUSE 12 Journal - 7: Printing to PDF

One more thing... that I forgot to mention in my previous entry is the topic of printing to PDF.

I'm quite surprised this capability is not included in the base openSUSE 12.2 install since we have OSS version of the Adobe PDF reader (Okular).

Scenario/Use Case:
You need to print out a document directly into a PDF format file, instead of killing trees.  Some examples are:

• Printing online receipts directly into a PDF for your electronic filing
• Converting some page or document into PDF format using the Print function

Do note that if your document can be opened and edited in LibreOffice (comes with 12.2), and you want to convert that document into a PDF, you can do that by clicking the PDF button within LibreOffice.

Solution:

My openSUSE 12 Journal - 6: Hello 12.2!

More than a year (12+ months) since my last entry... obviously lots have happened... BUT

Its a new year (2013), a new job, a new Laptop and a new openSUSE 12.2!  I'll stop right there before I go off on a tangent, seeing & proclaiming trends where none existed previously.

Details:

• openSUSE 12.2 x86_64 (64-bit) - KDE desktop (default)
• Toshiba Tecra R840 (Intel i5, 4Gb RAM, 320Gb Hdd, Intel HD integrated graphics)
• Dual-boot with Windows 7 (/dev/sda1) and openSUSE (/dev/sda2)

Installation:
Smooth as silk is all I can say and something that has come to be expected.

Given the dual-boot setup, I created my own disk partitioning scheme.  So this step deviated from the otherwise straight-forward install (ie click next till the end).

Disk partition scheme:

• /dev/sda1 - 100Gb - original factory installed Windows 7 (size shrunk to 100Gb)
• /dev/sda2 - 100Gb - root partition of openSUSE 12.2 ('/') formatted to ext4
• /dev/sda3 - 98Gb - extended partition
• /dev/sda5 - 6Gb - SWAP partition
• /dev/sda6 - 92Gb - common data partition formatted to NTFS (read/write for both Win7 & openSUSE 12.2)

At install time, I did not format the common data partition.  Instead, I left it blank (unformatted) and used Windows 7 to format it much later.  Once formatted, this common data partition will be known as D:\ drive on Windows 7.

Reboot into openSUSE 12.2 and use YaST Partitioner to set a mount point.  I usually mount this under /mnt/common.  Now, openSUSE 12.2 will automatically mount the common data partition in /mnt/common on boot.

The only outstanding part is that /mnt/common is accessible by root (super-user) but normal users access is troublesome.  To make /mnt/common read-writeable by normal user, I edit the mount options of /mnt/common in the /etc/fstab file.  Example, changed the options in bold from original (first line below) to the second:

/dev/disk/by-id/ata-xxxxxx-part6 /mnt/common          ntfs-3g    user,users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0

/dev/disk/by-id/ata-xxxxxx-part6 /mnt/common          ntfs-3g    uid=han,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0

where han in uid=han is my normal user account on openSUSE 12.2.

There might be a more user-friendly way to do this but I did not explore since I'm comfortable editing the /etc/fstab. Readers who knows how this can be done, please feel free to leave a comment.  Thanks.


Grub vs Grub2:
I chose to stick with Grub instead of the newer Grub2 boot loader.  The reason is simple, I could easily edit the boot options via /boot/grub/menu.lst because its a text file.  In Grub2, this is non-trivial and until they have an easier editing interface, I'll stick with Grub.


Additional Software

My openSUSE 12 Journal - 5: Desktop Bits & Bytes

This is week 3 of using 12.1 and still lovin' it.  This journal entry covers a few disparate topics, from wifi to graphics cards, as I go about my daily routine in the office (stuff I actually get paid doing) with openSUSE 12.1 on my Lenovo Thinkpad.


Can't locate your hidden Wifi access point?
Here is a neat command (as root) that you can execute to help NetworkManager connect to a hidden wireless access point OR when NetworkManager is unable to detect your desired wireless point fast enough in a wifi-saturated environment.

iwlist wlan0 scanning essid MyWifi

where wlan0 is usually your default wifi device, if you are unsure, execute ip add to verify.
MyWifi is the name of your desired/hidden wireless access point.  For ease of use, you could wrap this into a nice little script.

My openSUSE 12 Journal - 4: Minor Frustrations

This is my fourth journal entry for openSUSE 12.1 and it has been two weeks of operational use on both my Thinkpad and home PC.  Here are some additional minor frustrations and some workarounds... and yes, I have posted on the openSUSE forums (just in case you'd ask).

Boot 12.1 using the old System V init
In my first journal entry, I complained the lack of "chattiness" during boot since the adoption of Systemd.  You can easily switch to the old System V init on boot.  At the grub boot loader screen (usual 8 seconds delay) and before you hit Enter to boot, press the F5 button to switch from default to System V.  Now, press Enter to boot and press the Esc key during the splash screen to see the familiar System V init messages.

[Update on 6 Dec 2011]: Tired of pressing F5 every time on boot? Append the following to the end of the line:
init=/sbin/sysvinit
For example, in /boot/grub/menu.lst, at the end of the line starting with "kernel /boot/vmlinuz-3.1.0-1.2-desktop...", append the line above and save the file.  On the next boot, you can verify the change in the Boot Options field.  Press Enter and you will boot up 12.1 under the old System V init.

Air Video Server on openSUSE 12.1

In short, Air Video is a client-server product that streams, via live conversion, videos of many formats to any iOS device (eg iPhone, iPad etc).  The server software is free-of-charge but only runs on Mac OSX and Windows.  The client is also free-of-charge for iOS devices but "crippled".  If you like the solution, you pay for the client.

Since the Air Video Server is written in Java and uses a customized version of FFMPEG, it would be possible to run it on Linux.  The folks behind Air Video though supportive but are NOT offering official support for Linux. 

I have been successful in making Air Video Server (AVS) work on openSUSE 11.3, 11.4 and 12.1.  Here are the steps:

On the road again: MYGOSSCON 2011

Going on the road again... after a year of life's transitions and pursuing other interests, I am privileged to have the opportunity to speak at MYGOSSCON 2011 next week. 

The title of my paper is "Key Trends: Challenges, Opportunities and Leverage for Linux/OSS Ecosystem".  I look forward to the discussions it will generate.  :)

Personally, I am looking forward to this with excitement as I have been granted the latitude in content creation.  I will be approaching the topic from another angle and with, what I hope to be, a fresh perspective.

My openSUSE 12 Journal - 3: Lotus Notes 8.5.3

Lotus Notes is what I use at work and the latest v8.5.3 works well on openSUSE 11.4.  Although it installed without a hitch on 12.1, things goes awry when I start using it.  Here are my observations and how I managed to get it working again.  :)

For starters, Lotus Notes 8.5.3 only managed to render about half of its interface.  For example, I could see my inbox but email preview pane is blank.  Integrated SameTime worked but workspaces and replication tabs were blank too.  I suspect it could be some incompatibility or confusion with the GTK libs and I was right...  Google is my friend and I discovered a brilliant soul who had the same challenge, created a bug report against openSUSE and even created a workaround/fix.

[Update on 27 Nov 2011]: Oops, it occurred to me that Lotus Notes 8.5.3 is actually 32-bit running on 64-bit openSUSE 12.1.  That means the RPM created by Stefan Lijewski should have worked.  I cannot recall why I came to the previous conclusion.  I have just tried the 32-bit RPM and it worked for me.  Therefore, I am correcting my entry below. 

Unfortunately for me, I could not use his nicely packaged RPM and online repository because I am using 64-bit openSUSE 12.1. 

The easy way is to use a 1-click install via Stefan Lijewski's online repository.

The easy but manual way is to download the RPM before you manually execute a zypper in lotus-notes-gnome3-1-1.1.i586.rpm

In both cases, you will need to verify that your Lotus Notes launch icon has been updated to use the new notes-wrapper script instead of the original notes script in /opt/ibm/lotus/notes/ directory.

Finally, the hard way (if you're so inclined to experience compiling your own code) is the original method I used below.

Below is how I got Lotus Notes 8.5.3 working on openSUSE 12.1 (64-bit).

1.  Download the workaround fix from https://github.com/sgh/lotus-notes_gtk2.23.3/downloads

2.  Un-tar the fix, tar zxvf sgh-lotus-notes_gtk2.23.3-2028e8e.tar.gz

3.  You will need to install additional packages before you can compile the fix.  As root, zypper in make gcc gtk2-devel glibc-devel-32bit gcc-32bit

4.  In the sgh-lotus-notes_gtk2.23.3-2028e8e subdirectory, compile the fix with make

5.  If make completed with success, you should have a new file libnotesgtkfix.so in the directory.  Copy it and notes-wrapper to installed Lotus Notes directory /opt/ibm/lotus/notes/.

6.  Last and final step, edit your Lotus Notes icons (kmenuedit if using KDE4) and change the default launch script to execute notes-wrapper instead.

That's it.  Lotus Notes 8.5.3 should function normally... and its all good for the last 3 days for me.

I hear this would not be a challenge with the newer Lotus Notes 8.5.4 (yet to be officially released).  We shall see when we get there.  :)

openSUSE 12.1 gets positive review on LAS

Nice and positive review of openSUSE 12.1 on the Linux Action Show on 20th Nov 2011.  The YouTube video is embedded below... you may fast-forward to 30:10 where they finally got down to the review of openSUSE 12.1.

Most interesting (the best) comment on that YouTube page was from Jos Poortvliet (our openSUSE Community Manager), "VERY nice review guys! Fun to see how opinions on openSUSE have changed in the last year - from 'meh, yeah, is that distro still alive?' to the awesomeness now :D

If you ever wanna talk about it with me - I'd be happy to be on the show..."

As with most things in life, its all about perception and goodwill.  openSUSE 12.1 is polished and enjoyable but a number of the great features mentioned, including SUSE Studio and openSUSE Build Service, have been around for a while... anyway, I'm just happy & enjoying the goodwill towards openSUSE.  :)

My openSUSE 12 Journal - 2

Installed openSUSE 12.1 (64-bit) on both my home PC and my Thinkpad W520. The best part was I did not have to burn any installation DVDs and speed of installation was at Gigabit speed on my home local network.

Here is what I did in a nutshell:

1. Download openSUSE 12.1 64-bit ISO and verified integrity with md5sum
2. Configured my Thinkpad, running openSUSE 11.4, as the network installation server.
3. Boot up my home PC in PXE-boot mode and installed openSUSE 12.1 from my Thinkpad.
4. Once my PC is installed and running openSUSE 12.1, I configured it as the network installation server and boot up my Thinkpad in PXE-boot mode and installed openSUSE 12.1 onto it.

Simple and sweet!

For more details, please refer to my older posts:

1. Network Installation of openSUSE [Link]
2. Using Apache2 to deploy and maintain SUSE [Link]
3. Install and configure TFTP server for PXE boot environment [Link]
4. Install and configure DHCP Server [Link]
   

Happy to report the steps I documented in the posts above worked for openSUSE 12.1. There were some minor differences, mainly to do with Systemd and how it changes the console output a little. The previously observed SuSEFirewall bug for TFTP server is still present, so remember to add port 69 to UDP as previously documented.