Home · ProLoser/AnythingSlider Wiki.

This is a great solution to help friends (or maybe also customers) watching directly the remote screen.

It’s safe and easy (it uses JAVA to do the trick – so the sharing screen system must [...]]]> This web app can share your screen (it’s a view only application, not like VNC/remote desktop) to who you want.

This is a great solution to help friends (or maybe also customers) watching directly the remote screen.

It’s safe and easy (it uses JAVA to do the trick – so the sharing screen system must have JAVA installed) and after few steps you can share the screen sending a URL or giving a share code (a nine digit numeric code, easy to tell, maybe on the phone…)

Instant Screen Sharing | Screenleap.

This is a well know bug, but until it will be fixed, you can fix it by yourself.

Run from the terminal your favorite text editor (gedit, kate, [...]]]> Today, trying to slice an image with Gimp, with my Kubuntu Oneiric I have found this strange error message: “TypeError in slice(): integer argument expected, got float”.

This is a well know bug, but until it will be fixed, you can fix it by yourself.

Run from the terminal your favorite text editor (gedit, kate, vim, nano, pico, etc…) and replace the bad line with the good one.

sudo kate /usr/lib/gimp/2.0/plug-ins/py-slice.py

replace at line 172 (ymmv)

temp_image.crop(int(right – left), int(bottom – top), int(left), int(top))

with

temp_image.crop(int(right - left), int(bottom - top), int(left), int(top))

Save and close. Happy slicing!

The last Ubuntu version, Oneiric Ocelot, contains a bug preventing SBackup from running from a system wide cron-job and storing the backup data on remote drive.

If you have this problem, from the logs, you can [...]]]> I’m a huge fan of Simple Backup for many reasons (simple personal backup configuration, settings profile, etc…).

The last Ubuntu version, Oneiric Ocelot, contains a bug preventing SBackup from running from a system wide cron-job and storing the backup data on remote drive.

If you have this problem, from the logs, you can find something like this:

ERROR: Traceback (most recent call last):
File "/usr/share/sbackup/sbackup/fs_backend/_gio_utils.py", line 372, in _mount_done_cb
self.__mount_finish_callback(error)
File "/usr/share/sbackup/sbackup/fs_backend/_gio_fam.py", line 157, in _mount_cb
raise exceptions.FileAccessException("Unable to mount: %s" % error)
FileAccessException: Unable to mount: volume doesn't implement mount

I have fixed this (well… it’s a workaround…) adding the SBackup executable to sudoers and running the backup task from my personal cron-job.

To do this you have to:

1. run “sudo visudo“
2. add to the bottom of the file this:
   Cmnd_Alias SBACKUP_CMDS = /usr/bin/sbackup
   USERNAME ALL=NOPASSWD: SBACKUP_CMDS
3. replace USERNAME with your actual username (eg John)
4. save and quit the editor with CTRL-X
5. run “crontab -e“
6. add to the bottom of the file this:
   00      */3     *       *       *       /usr/bin/sudo /usr/bin/sbackup
7. take a cup of coffee

Now, every 3 hours your backup is running with root privileges and over the network. Feel free to change the cron-job as you wish!

- pigz – Parallel gzip

- pbzip2 – Parallel bzip2

I’m using gzip and bzip2 from ages, and also multiple processors and multiple cores, so why don’t use multi-threading compression utilities? They are (obviously) binary compatible with the old counterparts and they [...]]]> Recently I have discovered two new (at least for me) utilities:

- pigz – Parallel gzip

- pbzip2 – Parallel bzip2

I’m using gzip and bzip2 from ages, and also multiple processors and multiple cores, so why don’t use multi-threading compression utilities? They are (obviously) binary compatible with the old counterparts and they have also the same command line flags.

It’s time to take advantage of new technologies. Happy multi-threading folks!

I can’t wait!

FAQs | Raspberry Pi.