A new version Deluge is out. Version 0.5.8.2 promises to fix the crash issues faced by many users. Changelog, Deluge 0.5.8.2 (24 January 2008) Fix column width saving Option to download new blocklist after certain number of days - Patch from Mark Stahler Fix ui-locking when tracker responded in non-utf8 encoding Remove Extra Stats plugin Prevent Scheduler plugin from setting an invalid ‘max_active_torrents’ Download Deluge 0.5.8.2 here. Source: Deluge
Stand a chance to win a HP Kensington Wireless Mouse by writing a short story about Delirium. To qualify, Write a story no longer then 30 words about Delirium and the contest. Keywords “Delirium”, “Blog”, “Your Name” must be included in the story. Contest starts 21st Jan 2008 and ends on 31st Jan 2008. source: Delirium Short Story Contest
RedHat is coming to town with Intel to roll out a new seminar next week, The Redhat Choice Seminar. What’s will be covered, Why FOSS? Entreprise on Intel Integrated Virtualization When and where, Date: 29th January 2008 Venue: Sheraton Imperial Hotel, Jalan Sultan Ismail Kuala Lumpur 50250 Malaysia Time: 1.30pm - 5.00 pm If you are interested to attend the seminar then Source:
I’ve been hit by bug #345131 since updating to the latest xorg-server [7.2-143.9] security update on my openSUSE 10.3 installation. xorg-server version 7.2-143.6 to 7.2-143.9. VLC, Filezilla and a few other applications stopped working. The bug has something to do with the X Window shared memory (MIT-SHM) overflowing. My error, The program ‘Filezilla’ received an X Window System error. This probably reflects a bug in the program. The error was ‘BadAlloc (insufficient resources for operation)’. (Details: serial 1072 error_code 11 request_code 147 minor_code 5) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the -sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Few hours of Googling and experimenting later I found my fix. 3 actually. ...
I develop quite a few bash scripts to automated backups and dropbox operation in my office. One of the usual requirements is to tar (tar.gz) the files locally and later untar them on the destination server when needed. I have a few simple scripts with interactive menus which help the data center operations team with their daily backup tasks. One of the challenges during development was the ability to untar files on the backup server over SSH. The command by default will untar to the home directory instead of the target folder output always returned success but the files were nowhere to be found. This apparently is a limitation on the tar command, it did not know where to untar the files to when being executed over SSH. Fortunately the fix was really simple. Original command, ssh 127.0.0.1 'tar zxvf ~/test/files.tzr.gz' The simple fix, ssh 127.0.0.1 'cd ~/test/ ; tar zxvf files.tar.gz' or, (thanks Aik) ssh 127.0.0.1 'tar zxvf files.tar.gz -C ~/test/' Here’s a video I put together to demonstrate the above. Hopefully I got it right. ...