Saturday, January 19, 2008

Where To Buy Fur Wallpaper

Bug in xorg: Azureus non parte più in Ubuntu

Two days ago I installed Azureus (bittorrent client platform written in java) on my laptop with Ubuntu Gutsy Gibbon 7.10.
Alright, got the program from the official repositories and immediately went to work ..

Yesterday morning (1/18/2008) from the update manager for my distro I was offered the opportunity to upgrade the X server in its core: "xorg-core." Everything ok, normal administration ..

the evening I try to log back to Azureus and not part .. after some 'speed to understand what goes wrong I get the error:

 The program' SWT 'Received an X Window System error. This 
Probably Reflects a bug in the program.
The error Was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 343 error_code 11 request_code 146 minor_code 5)
(Note to programmers: Normally, X errors are reported figures 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 backtrace from your debugger Meaningful
if you break on the gdk_x_error () function.)


try the Ubuntu forums and I find be a common problem after upgrading xorg-core component .

So if you have had the same problem (which seems to afflict even eclipse) and do not understand why the solution is to downgrade the version of xorg that before the update.

1-Open "Synaptic Package Manager" 2-
Search for "xorg-core" and select "xserver-xorg-core"
3-Go to the top of the menu "Package-> Force Version ..."
4-Set earlier version of the " xorg-core 2:1.3.0.0. dfsg-12ubuntu8.1 ( buggy), that" xorg-core 2:1.3.0.0. dfsg-12ubuntu8 (gutsy) "(working )
5-Reboot

To avoid downgrade xorg-core, was also offered a fix but although they appear to affect significantly the operating system performance.

UPDATE-It seems to have been issued in record time two later than bugata xorg-core. The advice is to let a few days before leaving for a working version of a new (since this mistake) in any case be aware that with the above procedure You can redo the downgrade.