View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004384 | Kali Linux | General Bug | public | 2017-12-04 01:27 | 2019-03-17 09:11 |
Reporter | atdtphreaker | Assigned To | sbrun | ||
Priority | normal | Severity | major | Reproducibility | N/A |
Status | resolved | Resolution | fixed | ||
Product Version | 2017.3 | ||||
Fixed in Version | 2018.1 | ||||
Summary | 0004384: Sound / Audio issues. | ||||
Description | Following UPDATE and UPGRADE, I no longer have sound capabilities (selection of device, output, input, volume control, etc). Sound works via online video and audio but without any control. Thanks for your time. | ||||
Steps To Reproduce | apt-get update && apt-get upgrade && apt-get dist-upgrade | ||||
Additional Information | root@kali:~# lspci | ||||
Attached Files | |||||
I have the same issue, there is no sound control (there even no output device detected in the sound setting), but there is sound I can play video or doing other things. I note when upgrade the system, the changlog mentioned that the Pulseaudio is not set as autospawn, and even I delete the file that set the autospawn=no, there issue is not resloved. |
|
I have the same issue after fresh install of 2017.3 on my Lenovo T420 |
|
I too, did as you noted when I updated (pulseaudio, autospawn alert), editing '/etc/pulse/client.conf.d/00-disable-autospawn.conf' without success. ..and then deleting it (as you also did), also WITHOUT success. |
|
The problem is that a condition has been added in files /usr/lib/systemd/user/pulseaudio.service and /usr/lib/systemd/user/pulseaudio.socket: ConditionUser=!root We just upload a new kali-default version 2017.3.3: it overrides the condition in Kali and fixes the issue. |
|
Same for me here, though I tried this temporary fix: pulseaudio -D Each time I boot kali, I type the command above, and the sound control is back. |
|
Okay, defaults ('kali-default version 2017.3.3') were implemented following update. ...sound functions have returned, seemingly. Thanks for the update. |
|
just for curiosity, how do you know the exact version of you kali, I only know it is 2017.3, because I install fresh 2017.3 in my computer, how do you find the version is 2017.3.3 |
|
As I was updating, "2017.3.3" was stated. All my knowing is based on mere assumption, I suppose. |
|
2017.3.3 refers to the version of the kali-defaults package (dpkg -s kali-defaults), there's no sub-version for kali in general. Closing this ticket since the problem has been fixed. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2017-12-04 01:27 | atdtphreaker | New Issue | |
2017-12-04 01:27 | atdtphreaker | File Added: Screenshot from 2017-12-03 20-14-23.png | |
2017-12-04 01:28 | atdtphreaker | File Added: Screenshot from 2017-12-03 20-13-10.png | |
2017-12-04 01:28 | atdtphreaker | File Added: Screenshot from 2017-12-03 20-13-29.png | |
2017-12-05 00:34 | DirtyOleg | Note Added: 0007657 | |
2017-12-05 04:16 | domc | Note Added: 0007658 | |
2017-12-05 05:48 | atdtphreaker | Note Added: 0007659 | |
2017-12-05 09:51 | sbrun | Note Added: 0007660 | |
2017-12-05 09:52 | sbrun | Assigned To | => sbrun |
2017-12-05 09:52 | sbrun | Status | new => assigned |
2017-12-05 11:06 |
|
Note Added: 0007662 | |
2017-12-05 22:49 | atdtphreaker | Note Added: 0007665 | |
2017-12-06 03:00 | DirtyOleg | Note Added: 0007666 | |
2017-12-06 03:08 | atdtphreaker | Note Added: 0007667 | |
2017-12-06 07:38 | rhertzog | Status | assigned => resolved |
2017-12-06 07:38 | rhertzog | Resolution | open => fixed |
2017-12-06 07:38 | rhertzog | Fixed in Version | => 2018.1 |
2017-12-06 07:38 | rhertzog | Note Added: 0007668 |