Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Technically it isn't really a process anymore, just a listing of one. In order to get rid of a defunct or zombie process you'll have to kill it's host process.
You can find that out by using the command ps axjf. Once you find the host process just type kill -9 <process number>
If there is no host process you'll either have to reboot the system or wait for the system to clean it up, however a few zombie processes generally aren't anything to worry about as they aren't taking up resources.
I dont' know a whole lot about this stuff, but you might try running XMMS from the commandline exclusively for a bit. Tedious, yes, but when something goes wrong you can see any errors right there in front of you. I had trouble with this before, and I can't remember exactly, but I think at least when I ran it from the commandline if I had to Ctrl-C it, I didn't have to wait for the defunct process to clean itself up.
Might also check ~/.xsession-errors after it crashes, if you didn't run it from the commandline, and see if there's any info there.