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.
Unless things are radically different than they have been in the past, I think that is a physical function of the connector itself, not a software feature.
I expect it is a bad headphone jack on your box.
I was thinking of laptops with integrated speakers when I answered, and that would be true.
If you are on a desktop with a front headphone jack and rear speaker connection you will probably have to go into your mixer and mute the speakers, to my knowledge headphone insertion is not auto detected, and it would not interrupt the speakers.
Actually, while a bad jack could result in the same problem, at can also be completely a software issue these days.
Most likely (other than a bad jack) the sound chip is very new (i.e. spanking new laptop??), and either the kernel driver, or the alsa package, is not quite new enough to have full/correct specs of the chip, leading to failing jack-sensing. A related possibility (and relatively common too, if you read the alsa-devel or kernel mailing lists) is that the BIOS incorrectly reports the "pin widgets" of the chip, which misleads the driver.
Two (or more) ways to diagnose:
--Install the newest alsa package you can find.
--Upgrade to a very new kernel.
--both of the above.
..and see if that fixes it.
If nothing is broken at all in either software or hardware, I suppose it's possible too that the machine simply does not mute the speakers when headphones are connected, in which case you'd need to manually mute the speakers when using phones (but this sounds rather funny to me too.)