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.
I'm running Debian Sid and recently did an upgrade, which shot me up to kde 3.5.2. When this happened, arts stopped working and I get one of those handly little kde crash handler windows popping up with a notification of a crash. knotify also seems to crash when using a new user (as I don't have system sounds enabled with my default user).
When I attempt to run artsd from a terminal, I get:
unix_connect: can't connect to server (unix:/tmp/ksocket-dave/suna-585d-44792ea8)
Sounds don't work if attempting to use arts. If using OSS, sound works. ESD doesn't work. Alsa appears to work in the terminal. Of course, I can only play one sound at a time with OSS, which is not good for some applications. I'm guessing it might have to do with alsa, because I get constant crash handler windows popping up (disrupting system use until I ALT-CTRL-BACKSPACE) when attempting to set the sound server to use ALSA instead of Autodetect. If attempting to set it up for OSS, I get no such errors.
I appreciate any assistance, as I have been working on fixing this for the past 8 hours. Thank you.
There are similar reports regarding kanotix (Debian sid variant) and ubuntu dapper.
It is aparently a problem with libasound2, which was upgraded in the last few days.
If you haven't cleared the apt cache you can do this ti fix it -
dpkg -i libasound2_1.0.11-4_i386.deb
Otherwise wait til version 1.0.11-6 to see if it's fixed.
Actually, I did clear the apt cache, hoping that it would help if I were to downgrade to etch. Let's just say that when I did that I wasted a lot of time. I'm going to check the debian website to see if they have that particular package there. Be Right back.
I found 1.0.11-3, so I am going to see if that works. Just a sec.
Okay. It's set up. Now to reconfigure alsa again and get arts up and running.
Incase of that horrible pop-up blocking my ability to do anything, I will be posting this now and post a reply to my reply after restarting X.