It's just a few minutes after my previous post about a broken Google Earth 6.0.3 on Slackware and now i have found the solution for that kind of problem, so here's the solution to install the latest Google Earth on Linux (tested here on Slackware Linux):

./GoogleEarthLinux.bin --target /tmp/ge --noexec
cd /tmp/ge/setup.data/bin/Linux/x86/
cd /tmp/ge/setup.data/bin/Linux/x86_64/ (64-bit)
mv setup.gtk setup.gtk2
cd /tmp/ge
./setup.sh (it can be installed using root or normal account)

If for some reason you failed to launch the Google Earth, make sure you have created a symlink to comply with LSB that Google requires by running this as root:

ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3

Here's a screenshot to a working Google Earth installation on my desktop:

There's a new Google Earth release and it's now 6.2. Unfortunately, the same version is not available in Linux and the latest one in Linux is at 6.0.3.2197. I once covered on how to install Google Earth on Slackware and it's working fine up to Version 6.0.2.2074.

Today, i downloaded the latest version and i saw an update there : 6.0.3.2197. I tried to reproduce the same steps i have been using to perform the installation of Google Earth in Linux, but this time, it failed me.

/GoogleEarthLinux.bin --target /tmp/ge
Creating directory /tmp/ge
Verifying archive integrity... All good.
Uncompressing Google Earth for GNU/Linux 6.0.3.2197.............................................................................................
This version of Google Earth requires LSB 4.0 support which you
do not seem to have.
./setup.sh: line 285: [: missing `]'
Unknown id: yum install redhat-lsb
I/O error : No such file or directory
setup.data/setup.xml:1: parser error : Document is empty

^
setup.data/setup.xml:1: parser error : Start tag expected, '<' not found

^
./setup.sh: line 158: 28089 Segmentation fault      "$setup" "$@"

I'm really sure that it was working in the previous version, but unfortunately, it's likely that Google changed it's requirement to have LSB 4.0 as the base

digiKam is one of my favorite application in KDE since i can use it to export my photos to Facebook directly and it has a lot of interesting features. Unfortunately, this package is not yet part of Slackware default packages, but it's still available on SlackBuilds project.

Another problem is that the maintainer hasn't updated the SlackBuild script to the latest version (2.5.0) and stuck at 1.9.0 up to now.

For those who wanted to try the new digiKam, you can download the original SlackBuild for digiKam from SBo package and replace the .SlackBuild script with the modified SlackBuild from my Box.net account and also a patch file to make it compilable. Put them in the digikam directory and start your engine to compile.

Please read the requirements for the new digiKam package as it adds more dependencies in the process.

Jérôme posted a comment on my post about VMWare and Linux Kernel patch, saying that the patch i mentioned is not working with VMWare Workstation 8.0.2, the latest VMWare released by the vendor. When a stable kernel is released, normally, the patch should work normally, but in this case, i was wrong (at least my assumption), since the changes in the kernel affected the patch.

So i started a discussion at the patcher's blog and finally the author of the patch confirmed that there's a change in kernel source code which applies to his patch. He fixed the patch and submit it again into his blog post.

Unfortunately, the script still failed on me if i tried to use his script, but Ted, another people confirmed that it's working on his system but instead of using the bash script to do the job, he patched it manually, so i tried and it worked.

So here's the solution:

1. Get the patch from the author's blog or from my Box account
2. Extract it (assume in /home/willysr)
3. Go to /usr/lib/vmware/modules/source
4. Extract the source file (tar xvf vmnet.tar)
5. Patch the source file (patch -p1 < /home/willysr/vmware3.2.0.patch)
6. Create a new source file (tar cvf vmnet.tar vmnet-only/)
7. Recompile VMWare again (vmware-modconfig --console --install-all)
8. Voila.... everything works normally again

This patch should also be working for future Linux Kernel 3.3, so you probably don't need to search for more patch when Linux Kernel 3.3 released by Linus.

I didn't remember when i started to have this problem, but it's very annoying bug. Amarok will stop playing after it completed playing one track even though there are still a lot of files in the playlist. I assume it's another bug due to transition from previous release of Amarok that might caused this problem to surface.

Thanks to UbuntuForums, i found the solution and i tried it on my desktop and yes, it worked like charm. It seems my predictions was right and the solution is very simple, which is to remove the old configuration of Amarok by doing this steps (you might loose all your Amarok configuration):

mkdir ~/.kde/share/config/backup
mv ~/.kde/share/config/amarok* ~/.kde/share/config/backup/

Restart your Amarok and voila.... it will start playing all the playlist tracks

For those who have been playing with KDE 4.8.0 that was released yesterday, you might noticed that your KDE will not ring any sound when you logged in anymore. I noticed this earlier, but i thought that there was some backend problem and i haven't had time to find the solutions for this.

AJ Field commented on Eric's blog post about KDE 4.8.0 and pointed a thread at ArchLinux Forum which should solve the problem. I tried to use the solution written there and it really work like a charm.

The problem only lies in the directory reading on Notification settings (System Settings -> Applications and System Notifications). Previously, you mentioned only the filename, but in KDE 4.8.0, i guess it should have been a complete path, so the solution is simple, just browse the file and pick the same file and it will give you the full path.

I'll show you before and after i changed the path using these two screenshots below. The first screenshot is the original condition:

This is what i got after i browse the file and pick the same filename.

I only need to save the changes and it will be back to normal again once you logged out and logged in again.

BismilLahirrohmanirohim.

Ini tulisan "agak serius" dan "non slackware", yang lahir dari keprihatinan diri selaku putra negeri ini. Baiklah ... jelang peringatan Maulid Nabi Muhammad shollalLohu 'alayhi wa sallam, sebenarnya ada kesempatan kita -selaku muslim- untuk bercermin diri. Tentu saja yang akan ana bicarakan adalah sisi Sistem Operasi (SO) di komputer kita, bukan hari kemarin yang telah berlalu... tapi hari ini dan hari esok. Ya, mencoba meneropongnya lebih dalam dengan kejujuran seorang muslim.

Dan jujur saja, tulisan di bawah ini akan menyarankan Anda selaku pembaca untuk menggunakan SO dan aplikasi GNU/Linux yang merdeka, dan meninggalkan SO yang tidak pernah kita -satu kali pun- membeli lisensi penggunaannya. Jadi kalau Anda "membenci" tema seperti ini, berhentilah membaca dan berpindahlah ke judul lainnya, oke?

(more)

I have just finished upgrading my desktop to use KDE 4.8.0, which was just released by KDE team few hours ago while i was sleeping. Thanks to Eric Hameleers, i could get the early release of KDE packages and downloaded this packages as i slept last night. When i woke up this morning, all i have to do is to make sure everything is already up to date by running the rsync script once again.

Next on, performed the command written on the README and performed the upgrade. Don't forget to have a complete look on the README as there has been a renamed packages. After i rebooted my machine, KDE started to be loaded and there was a new splash screen called Air and Ariya Splash Screen which is very minimalistic, but it does look more professionals.

If you have been using KDE 4.7, you won't get too much drastic changes, as it's based on previous releases. According to the announcement, there are a lot of areas which has been improved on this release:

• KDE Plasma Workspaces 4.8 Gain Adaptive Power Management  
• KDE Applications 4.8 Offer Faster, More Scalable File Management 
• KDE Platform 4.8 Enhances Interoperability, Introduces Touch-Friendly Components

I do feel that KDE 4.8.0 is faster than previous release, probably due to updated Qt which is now bumped to 4.8.0 to sync with KDE release version. You can also have better performance when you enabled desktop effects as there has been a lot of improvements on this area as well.

I used Kate a lot and on this release, Kate also got several new features and one of the new feature i like a lot is the new Line Modification Indicators. It really helps for developers to work in collaboration.

Another nice improvement from KDE is the Power Management System Settings which has been redesigned for simplification. It really helps for users carrying portable devices, such as laptop or netbooks.

KSecretService is taking it's debut on this release to provide new framework for sharing saved passwords and other credentials between a wider range of applications.

So far, i have no problems with this release, but even if there is a problem, it will soon be sorted out in the next monthly release which should be out in February and months following.

For now, i'll enjoy Slackware and KDE 4.8.0

KDE has been proven to be stable enough ever since they released the controversial 4.0 version few years ago. Since then, KDE has matured and i can say it's stable enough to be used in production machines (i used it on my desktop, laptop, and workstation). The previous current version was 4.7.4 and it was released on December 2011. This version was meant to be the last version of KDE 4.7.x series according to KDE

KDE communities never stop improving KDE and as the results, we could see KDE 4.8.0 by now and it's spreading to mirror sites around the world and most distribution vendors has started up to update KDE to the latest version to be included to the distribution packages.

Slackware at this point is still on hibernate status and there hasn't been any big changes on the public repository (-Current tree). Many people has feared that Pat will stop maintaining Slackware, but that's not true. We all know that Pat is very proud of Slackware and i'm sure he will try to maintain it as long as he can, but for now, he need to focus on other things besides Slackware and that results in the lack of updates in -Current. Hopefully that will change in the near future.

Meanwhile, Eric has continued to keep maintaining KDE packages for Slackware. He has done it for several releases back from KDE 4.0 up to 4.7.4 and now, he continues his tradition to provide KDE packages and this time, it's KDE 4.8.0, the latest version from KDE.

This new version of KDE has more packages then the previous version, thanks to the modularization made by the KDE release team. In total, Eric counted there are 90 tarball sources for this release, exploded from 71 sources from KDE 4.7. This gives more burden to the packagers, but it gives more flexibility to the users as they can pick which packages should be installed on their systems.

As always, KDE has been known to work without HAL and that will also likely to happen in Slackware, so try to stop depending to HAL for the time being until it's removed completely from Slackware which will be likely to be in the next release of Slackware since KDE and XFCE will be HAL-free for their next major release (KDE 4.8.0 and XFCE 4.8.0).

Eric mentioned that newer KDE needs mesa-7.10 or newer, and his KDE packages are built for -Current users, not for Slackware 13.37. The reason is simple. There has been a toolchain upgrade in -Current which affects the KDE packages shipped by Eric being incompatible with Slackware-13.37.

Due to a lot of changes in the package naming, it's suggested that you do exactly what's written on the README to perform this upgrade:

On Slackware 32-bit:
  # upgradepkg --reinstall --install-new x86/deps/*.t?z
  # upgradepkg --reinstall --install-new x86/kde/*.t?z
  # removepkg polkit-kde-1
  # removepkg kdeaccessibility
  # removepkg kdebase
  # removepkg kdebase-runtime
  # removepkg kdebase-workspace
  # removepkg kdebindings
  # removepkg kdeedu

# removepkg kdegraphics
  # removepkg kdeutils
  # removepkg konq-plugins

  On Slackware 64-bit:
  # upgradepkg --reinstall --install-new x86_64/deps/*.t?z
  # upgradepkg --reinstall --install-new x86_64/kde/*.t?z
  # removepkg polkit-kde-1
  # removepkg kdeaccessibility
  # removepkg kdebase
  # removepkg kdebase-runtime
  # removepkg kdebase-workspace
  # removepkg kdebindings
  # removepkg kdeedu

# removepkg kdegraphics
  # removepkg kdeutils
  # removepkg konq-plugins

You can remove the unneeded packages later on once it's proven to be running well.

If you upgrade from his previous packages (KDE 4.6 or 4.7), then please the end of the note about a change in the package's name:
* oxygen-gtk was renamed to oxygen-gtk2
* mobipocket was renamed to kdegraphics-mobipocket

In the end, credit should all go to Eric for his hard work of maintaining KDE packages for Slackware. I am only helping to distribute his work to Indonesian areas and for those who reads this blog.

If you need to keep KDE 4.7.4 on your system, please use the main repository (http://alien.slackbook.org/ktown/) or put an "exclude" command on your rsync script to prevent them to be deleted since in other mirror sites, KDE 4.7.4 has been deleted.

This set of KDE 4.8.0 packages is now available at UKDW Repository as well. Enjoy KDE 4.8.0 for Slackware.

ternyata tidak diperlukan perjuangan yang payah untuk memasang Gnome 3.2 pada Slackware 13.37. ini diakibatkan adanya dokumentasi pada blog pak Widya Walesa. setelah installasi berhasil, saya memasang libffi yang tidak ditemukan. kemudian membangun ulang gjs. lalu mengcompile ulang mesa untuk mengaktifkan gallium. saya iseng memanfaatkan mesa 7.10.2 yang tersedia pada directory testing. kompilasi berjalan lancar jaya tanpa mengganti libdrm versi 2.3.23. berikut konfigurasi yang saya kutip :

 gjs.SlackBuild
..
sed -i 's/mozilla-js/seamonkey-js/g' configure.ac
autoconf -i -f
..

 Mesa.SlackBuild
..
  --enable-gallium-i915 \
  --enable-gallium-i965 \
  --enable-gallium-radeon \
  --enable-gallium-r600 \
  --enable-gles1 \
  --enable-gles2 \
  --enable-shared-dricore \
  --with-driver=dri \
  --with-state-trackers=dri,glx,egl
..

hasilnya, lumayan

referensi :
http://www.walecha.net/content/gallium-berhasil-tundukkan-gnome-shell-di-ati-radeon
http://www.walecha.net/content/mencoba-gsb-32-di-slackware-current

• 
• 
• 
• 

LibreOffice 3.4.5 has been released by The Document Foundation. It's a maintenance release, so no new features added, but you can expect bug fixes on this release. If you have a bug reported on previous release, you might want to check the first and second changelogs.

Eric has compiled LibreOffice 3.4.5 for Slackware users and upload it to his repository. Please enjoy this release as this might be the latest release for 3.4.x series as the developer are now working on the 3.5.x series and they even started the second bug hunting for LibreOffice 3.5 that will commence on January 21 and 22, 2012. The decided to put a second session after a successfull first session that generates 70 bug reports from over 150 volunteers.

The next major release of LibreOffice, 3.5.0 is scheduled to be released on February, meaning it's less than 3 weeks from now.

If you use LibreOffice and you are having problem to print in landscape mode, then you are not alone. Some people reported this on LQ and i myself also experienced this problem.

Some members reported a fix for this problem, but requires a lot of changes in the printer behaviour settings. Other member suggested that upgrading CUPS to 1.5.0 should fix this problem and this is what i choose.

Of course, it's not that smooth to upgrade to the latest cups. I had some problem building it and it was discussed on LQ, but finally i'm able to build cups by removing the old patches on Slackware-Current's SlackBuild script.

Now i'm able to build CUPS and fix the problem on LibreOffice. Hopefully this helps for those having same problems with me and with other Slackware users.

• 
• 
• 
• 

• 
• 
• 
• 

Kutipan dari wikipedia:

Hypertext Transfer Protocol (HTTP) adalah sebuah protokol jaringan lapisan aplikasi yang digunakan untuk sistem informasi terdistribusi, kolaboratif, dan menggunakan hipermedia. Penggunaannya banyak pada pengambilan sumber daya yang saling terhubung dengan tautan, yang disebut dengan dokumen hiperteks, yang kemudian membentuk World Wide Web pada tahun 1990 oleh fisikawan Inggris, Tim Berners-Lee. Hingga kini, ada dua versi mayor dari protokol HTTP, yakni HTTP/1.0 yang menggunakan koneksi terpisah untuk setiap dokumen, dan HTTP/1.1 yang dapat menggunakan koneksi yang sama untuk melakukan transaksi. Dengan demikian, HTTP/1.1 bisa lebih cepat karena memang tidak perlu membuang waktu untuk pembuatan koneksi berulang-ulang.

Secure Socket Layer (SSL) dan Transport Layer Security (TLS), merupakan kelanjutan dari protokol kriptografi yang menyediakan komunikasi yang aman di Internet. Protocol SSL dan TLS berjalan pada layer dibawah application protocol seperti HTTP, SMTP and NNTP dan di atas layer TCP transport protocol, yang juga merupakan bagian dari TCP/IP protocol. Selama SSL dan TLS dapat menambahkan keamanan ke protocol apa saja yang menggunakan TCP, keduanya terdapat paling sering pada metode akses HTTPS. HTTPS menyediakan keamanan web-pages untuk aplikasi seperti pada Electronic commerce. Protocol SSL dan TLS menggunakan cryptography public-key dan sertifikat publik key untuk memastikan identitas dari pihak yang dimaksud. Sejalan dengan peningkatan jumlah client dan server yang dapat mendukung TLS atau SSL alami, dan beberapa masih belum mendukung. Dalam hal ini, pengguna dari server atau client dapat menggunakan produk standalone-SSL seperti halnya Stunnel untuk menyediakan enkripsi SSL.

Protokol transfer hiperteks adalah versi aman dari HTTP, protokol komunikasi dari World Wide Web. Ditemukan oleh Netscape Communications Corporation untuk menyediakan autentikasi dan komunikasi tersandi dan penggunaan dalam komersi elektris. Selain menggunakan komunikasi plain text, HTTPS menyandikan data sesi menggunakan protokol SSL (Secure Socket layer) atau protokol TLS (Transport Layer Security). Kedua protokol tersebut memberikan perlindungan yang memadai dari serangan eavesdroppers, dan man in the middle attacks. Pada umumnya port HTTPS adalah 443. Tingkat keamanan tergantung pada ketepatan dalam mengimplementasikan pada browser web dan perangkat lunak server dan didukung oleh algorithma penyandian yang aktual.

Menggabungkan protocol http dengan ssl pada slackware sehingga menjadi https  dengan langkah sebagai berikut :

 

1.  editlah file httpd.conf

# nano /etc/httpd/httpd.conf

 

2. hapuslah tanda pagar “#” didepan kata LoadModule ssl_module lib

LoadModule ssl_module lib/httpd/modules/mod_ssl.so

 

3. kemudian aktifkan dengan menghapus tanda pagar “# ” didepan kata Include

 # Various default settings
Include /etc/httpd/extra/httpd-default.conf

 

4. hapus juga tanda pagar “#” didepan kata Include

# Secure (SSL/TLS) connections
Include /etc/httpd/extra/httpd-ssl.conf

 

5. masuke kedalam direktori /etc/httpd

# cd   /etc/httpd

Setelah mengetikkan perintah dibawah ini akan diminta isikan apa saja yang diminta

# openssl genrsa -des3 -out server.key 1024

# openssl req -new -key server.key -out server.csr

# openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt

 

6. Berikutnya adalah

# cp server.key server.key.orig

# openssl rsa -in server.key.orig -out server.key

 

7. Untuk melindungi key file , ketikkan permission seperti dibawah ini :

# chmod 400 server.*

 

8. Masuk ke direktory extra :

# cd  /etc/httpd/extra

# nano /etc/httpd/extra/httpd-default.conf

ubahlah seperti berikut :

ServerTokens Prod 

ServerSignature Off

 

9. Kemudian edit file :

# nano httpd-ssl.conf

ServerName www.domain.tld:443 

SSLCertificateFile "/etc/ssl/apache/server.crt"

SSLCertificateKeyFile "/etc/ssl/apache/server.key"

 

10. Pada file httpd-ssl.conf perhatikan parameter dibawah ini

#   General setup for the virtual host
DocumentRoot “/lelaki-sejati”                ( jika tidak ada perubahan pada path DocumenRoot biarkan saja seperti default)
ServerName www.palembang-slackers.org:443
ServerAdmin molaviarman@gmail.com

 

11. Kemudian restart httpd dengan perintah :

# /etc/rc.d/rc.httpd  restart

 

12. Pastikan port 80 dan 443  dalam kondisi listening

# netstat -pln | grep 80

# netstat -pln | grep 443

 

Pesan Slackers : Jangan mudah menyerah untuk menjadi lelaki sejati, hahahah

Incoming search terms for the article:

• https adalah (2)
• internet gak konek di slackware (2)
• protokol http (2)
• server key (1)

Oke kali ini saya akan membahas bagaimana cara install chrome di slackware 13.37. Soalnya kemaren ane sempet install, tapi pas di klik kok gak mau-mau buka ya tu si chromenya, eh ternyata da sedikit trik agar si chrome tu bisa berjalan dan ini juga tau karena dapet dari postingan orang luar n bahasa inggris, maklum karena gak ngarti, cari-cari yang bahasa indonesia gak ketemu, yaudah coba artiin dah tu yang b.inggris tadi.Hehe

• 
• 
• 
• 

Screenfetch is a bash script that shows your system information on the terminal as it's executed and also display your Linux distribution logos. Since it's a bash script, the only thing you need to do is to give it an execute permission and then put it on your PATH variables. In my case, i put it on my /usr/bin, but you can put it anywhere.

If you wanted to be displayed everytime you opened up your terminal, then put this line into the bottom part of your .bashrc (if you are using bash):

. /usr/bin/screenfetch

Notice the dot in front and there's a space gap between the dot and the executable script. Test it by close your terminal and fire up another one.

You can try to have a look on other distro's logo by using -D parameter, for example:

screenfetch -D 'ArchLinux'
screenfetch -D 'Mint'
screenfetch -D 'Ubuntu'

BismilLahirrohmanirrohim.

AlhamdulilLah rancang-bangun Comal-Linux-0233 bisa ana selesaikan hari ini, 18 Shofar 1433H. Sekaligus malam ini pula selesai ana unggah di server dan siap untuk di-unduh. Inilah versi "Qubbatush-Shokhroh" final, menyempurnakan versi sebelumnya 0932, keduanya dibangun berbasiskan Slackware 13.37.

Versi 0233 ini tetap disuguhkan dengan konsep KISS. Sesederhana apa yang ana bayangkan. Seringan apa yang bisa ana racik. Selengkap apa yang ana butuhkan. Tentu saja menghadirkannya tidak semudah yang ana bayangkan. Dan ...  belum tentu sesuai untuk Anda, tapi ya mari dinikmati saja apa adanya

(more)