Bug 1609328 - Dell 5289 - Audio combo jack not recognized
Summary: Dell 5289 - Audio combo jack not recognized
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pulseaudio
Version: 29
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-27 15:18 UTC by Verhoeckx
Modified: 2019-11-27 23:24 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-11-27 23:24:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Output of the command alsa-info.sh (39.41 KB, text/plain)
2018-07-27 15:18 UTC, Verhoeckx
no flags Details

Description Verhoeckx 2018-07-27 15:18:53 UTC
Created attachment 1471134 [details]
Output of the command alsa-info.sh

Description of problem:
Fedora 28 doesn't recognize the audio combo jack in the Dell 5289 laptop.
When I connect my headphones to the audio combo jack the headphones are not recognized in GNOME Setting -> sound or in AlsaMixer.


Version-Release number of selected component (if applicable):
Fedora: 28
GNOME: 3.28.2
PulseAudio: 12.2  (-rebootstrapped)
AlsaMixer: 1.1.16


How reproducible:
Always (I guess).


Steps to Reproduce:
1. Buy the Dell 5289 laptop ;-).
2. Install Fedora 28.
3. Connect headphones with the audio combo jack.
4. Play music.


Actual results:
* The headphones are not recognized as a device in GNOME Settings -> Sound.
* The headphones are not recognized in AlsMixer.
* No music is played through the audio jack.


Expected results:
* The headphones are recognized as a device in GNOME Settings -> Sound.
* The headphones are recognized as a device in AlsaMixer.
* Music is played through the audio jack.


Additional info:
Not yet.

Comment 1 Verhoeckx 2018-07-27 16:11:22 UTC
I followed the steps as described on the page 'How to debug sound problems'(https://fedoraproject.org/wiki/How_to_debug_sound_problems) on the Fedora Wiki.


Hardware information
The file 'also-info.txt' is attached to this bug report.


Is it PulseAudio?
When I remove PulseAudio the audio jack is still not recognized.


Mixer settings
When I run alsamixer -c0 the audio jack is not recognized.


Model parameter
The Subsystem ID of my sound card is 1028:07aa.

When is search " '1028:07aa' alsa " I get one result:
https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/660052

The bug (on Ubuntu) is still open and doesn't provide a 'model= parameter'.

Comment 2 Verhoeckx 2018-07-27 16:14:37 UTC
Let me know if I can help you to fix this bug!

Comment 3 Verhoeckx 2018-11-09 12:02:59 UTC
I upgraded my system to Fedora 29 and the audio Jack is still not recognized.
Let me know if there is something that I could do.

Comment 4 Rex Dieter 2018-11-09 16:12:54 UTC
Reaching out to report this to pulseaudio upstream is likely the best thing to do.

mailing list
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss

and/or formally file a bug:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues

Comment 5 Verhoeckx 2018-11-15 21:43:57 UTC
Hello Rex,

Thanks, I will do that!

J. Verhoeckx

Comment 6 Wim Taymans 2019-09-11 09:17:15 UTC
This is probably an alsa problem first, can you any of the events when you do:

  sudo evtest


You should get a list of all events like this:

sudo evtest 
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	Power Button
/dev/input/event1:	Power Button
/dev/input/event2:	Video Bus
/dev/input/event3:	Gaming KB  Gaming KB 
/dev/input/event4:	Gaming KB  Gaming KB  System Control
/dev/input/event5:	Gaming KB  Gaming KB  Consumer Control
/dev/input/event6:	Gaming KB  Gaming KB  Keyboard
/dev/input/event7:	Logitech USB Optical Mouse
/dev/input/event8:	Eee PC WMI hotkeys
/dev/input/event9:	HDA Intel PCH Front Mic
/dev/input/event10:	HDA Intel PCH Rear Mic
/dev/input/event11:	HDA Intel PCH Line
/dev/input/event12:	HDA Intel PCH Line Out
/dev/input/event13:	HDA Intel PCH Front Headphone
/dev/input/event14:	HD Pro Webcam C920
Select the device event number [0-14]: 


Can you paste the output here? Check if your audio jack is in the list.

Comment 7 Verhoeckx 2019-09-11 10:29:39 UTC
Hello Wim Taymans,

Sorry but in the meanwhile I got a different laptop and upgraded my system to Fedora Silverblue 30. On my new system (Dell XPS 13) the audio jack is luckily correctly recognized.

So you can close this bug report.

Yours sincerely,

Scott Trakker

Comment 8 Ben Cotton 2019-10-31 18:50:59 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Ben Cotton 2019-11-27 23:24:35 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.