Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I'm running Ubuntu 7.04 (Feisty) and just got a bunch of new updates with the Update Manager (18 Jan). Some had to do with the xorg server.
NEW EDIT: VLC Player is also broken ... same error messages as aMule.
Anyway, aMule won't start. Hitting the icon yields nothing. Typing "aMule" in terminal brings:
----------------------------------------------------------------------------------------------------------------------
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
(amule:5846): Gtk-WARNING **: Unable to locate theme engine in module_path: "lighthouseblue",
The program 'amule' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 397 error_code 11 request_code 143 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.)
---------------------------------------------------------------------------------------------------------------------
I don't understand this exactly.
Does anyone know how to fix this (precise commands)?
It's fixed! The devs caught it. There's a new update for the xorg server. The system doesn't call for a reboot, but you need it after updating.
After the update, VLC worked. aMule didn't, but that is fixed by killing any running instance of aMule OR, as in my case, by deleting the file called mulelock from the /home/.amule folder.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.