Thanks Raymond. I think I got some interesting results. I ran hdajacksensetest and amixer -c0 contents after a fresh boot (when my headphones were not detected) and ran them again after unplugging and plugging my headphones back in.
hdajacksensetest gave the same result for both tests: Pin 0x24 (Green Line Out, Rear side): present = Yes Pin 0x25 (Black Line Out, Rear side): present = No Pin 0x26 (Orange Line Out, Rear side): present = No Pin 0x27 (Grey Line Out, Rear side): present = No Pin 0x28 (Green Headphone, Front side): present = Yes Pin 0x29 (Pink Mic, Front side): present = No Pin 0x2a (Blue Line In, Rear side): present = No Pin 0x2b (Pink Mic, Rear side): present = No The amixer output changed after unplugging and plugging the headphones back in. I've attached text files showing the before/after output. ** Attachment added: "Output of "amixer -c0 contents" after (1) a fresh boot, and (2) unplugging and plugging headphones back in" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1442428/+attachment/4372625/+files/amixer_output.tar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1442428 Title: Headphones not detected after fresh boot or suspend/resume cycle, until unplugged and plugged back in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1442428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
