I booted the 4.17rc1 kernel.
In order to see output I connected an old TV to the DVI output, and that
output was successfully detected (through an DVI-HDMI adapter, if that
matters).
The output of /sys/class/drm/card0-HDMI-A-1 in this case:
dpms: Off
enabled: disabled
modes: (empty)
status:
I'm not sure if you asked for the contents of these files from a working
or non-working kernel, but I'll take the working kernel since that's
obviously a lot easier.
The monitor, Dell U2415, is connected via its input source "HDMI (MHL)
2". The monitor name "DELL U2415" shows up in the edid fil
I don't think it is the same bug. I have a card with HDMI and DVI
connectors (XFX RX 460). The HDMI connector is connected to the monitor,
the DVI connector is unplugged.
// David
On 2018-04-30 17:40, Harry Wentland wrote:
> Replied on the ticket.
>
> If this is about non-functioning LVDS or VG
Kernel 4.15.0-15-generic #16~lp1761751v2: Boots normally
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761751
Title:
Black screen on 18.04 + AMD RX460
To manage notifications about this bug go to:
The test kernel (4.15.0-15-generic #16~lp1761751) boots normally.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761751
Title:
Black screen on 18.04 + AMD RX460
To manage notifications about this b
Yeah, so I doubt it's a whitespace fix in the rxrpc driver. However, a
diff between the configs on v415-rc2 and v415-rc3 has lots of
differences, the most interesting being this one:
$ diff -u config-4.15.0-041500rc2-generic config-4.15.0-041500rc3-generic
/* ... snip ... */
@@ -5675,9 +5677,9 @@
Kernel 3d7682af228fd78dc46bc: Black screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761751
Title:
Black screen on 18.04 + AMD RX460
To manage notifications about this bug go to:
https://bugs
Kernel 5fc62f6a139a7b06b027bf442cd4205619506f59: Black screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761751
Title:
Black screen on 18.04 + AMD RX460
To manage notifications about this bug
Kernel 282ef4729195c8503f7101d574acfb5e7c8a8209: Black screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761751
Title:
Black screen on 18.04 + AMD RX460
To manage notifications about this bug
Linux version 4.15.0-041500rc1-generic (jsalisbury@kathleen) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #201804181224: Black screen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761751
Title:
Bla
There's nothing graphics related here:
$ git log v4.15-rc2..a0da456bbf95d2a9294799bb --oneline
a0da456 net: phy-micrel: check return code in flp center function
c7799c0 tipc: call tipc_rcv() only if bearer is up in tipc_udp_recv()
cfac7f8 tcp/dccp: block bh before arming time_wait timer
b484d8a Me
Kernel a0da456bbf95d2a9294799bb05c61bfb24736bb7: Black screen.
This is starting to feel a bit fishy but maybe git knows what it's
doing. :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761751
Titl
Kernel af57b7fffaf74ff337e479abb19026d72065673b: Black screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761751
Title:
Black screen on 18.04 + AMD RX460
To manage notifications about this bug
Kernel 2391f0b4808e3d5af348324d69f5f45c56a26836: Black screen.
Kernel 4.17-rc1: Black screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761751
Title:
Black screen on 18.04 + AMD RX460
To mana
> I built the first test kernel, up to the following commit:
You mean the second test kernel, I presume?
Kernel 6a5e05a47b6cb8e59bfad351444322b1e4012326: Black screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Possibly upstream bug found:
https://bugs.freedesktop.org/show_bug.cgi?id=105880
** Bug watch added: freedesktop.org Bugzilla #105880
https://bugs.freedesktop.org/show_bug.cgi?id=105880
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Kernel 4.15rc2+78d9b048446c3c0a83313444fb706f8f3bccdae7: Black screen.
Note: I installed the linux-image-...-generic deb only as the header
ones seemed to require libssl1.1...?
Anyway, I did some research on my own as well.
First, I had a look at the commits between 4.15rc2 and 4.15rc3. The only
4.15.0-041500rc2-generic - Boots normally
4.15.0-041500rc3-generic - Black screen
4.15.0-041500rc4-generic - Not tested
So something between rc2 and rc3 it is then...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
v4.14 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/ - Boots
normally
v4.15-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/ - Boots
normally
v4.15-rc5: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc5/ - Black
screen
v4.15-rc9: http://kernel.ubuntu.com/~kernel-p
Ok, so I found this message when trying to boot a faulty kernel without
workaround, if it helps:
[1.797127] [drm] Cannot find any crtc or sizes
[1.799000] [drm] Initialized amdgpu 3.23.0 20150101 for :23:00.0 on
minor 0
--
You received this bug notification because you are a member
** Description changed:
I've been running 16.04 + hwe kernel 4.15 for a while now and recently
I'm now having a black screen instead. I've also tried an 18.04 daily
live USB stick, which has the same issue.
It probably started during an upgrade this week or last week. As a start
I'm b
** Description changed:
I've been running 16.04 + hwe kernel 4.15 for a while now and recently
I'm now having a black screen instead. I've also tried an 18.04 daily
live USB stick, which has the same issue.
It probably started during an upgrade this week or last week. As a start
I'm b
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+attachment/5104013/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761751
Title:
Bl
Public bug reported:
I've been running 16.04 + hwe kernel 4.15 for a while now and recently
I'm now having a black screen instead. I've also tried an 18.04 daily
live USB stick, which has the same issue.
It probably started during an upgrade this week or last week. As a start
I'm blaming the Linu
** Changed in: libav (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643467
Title:
Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec
T
Marking as security; either Firefox is wrong or libavcodec is vulnerable
and probably we need security people to look at it to determine which
one it is...
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Description changed:
+ Note: Current workaround is to add pci=noaer to your kernel command
+ line:
+
+ 1) edit /etc/default/grub and and add pci=noaer to the line starting with
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this:
+ GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
+ 2) run
Btw, I reported mine upstream long ago and got response from upstream
that "I've thought about this problem a bit, but realistically I don't
have time to do the fix I'd like to do /.../ Anybody else who is
interested should feel free to take a crack at it."
See http://permalink.gmane.org/gmane.lin
Out of curiousity, do all of you have the combination of Skylake +
RTL8723BE, and second, do you experience (as I do) that wifi doesn't
work very well (often loses connections etc)?
...as the errors seem to indicate some kind of physical error between
the Skylake/Sunrise Point host controller and
Just in case it helps someone:
This symptom seems to have more than one root cause. For me, I had more
than one entry in /etc/crypttab, one being completely wrong. It was
probably a left-over from me switching hard drives a while ago, but then
the symptom only started to appear after a 14.04 -> 16
> It is unlikely that your patch fix the problem since none of the
drivers of those users have a volume control with multi channel
I found this:
control.15 {
iface MIXER
name 'Line Capture Route'
value.0 false
value.1 false
@Raymond, sometimes you're absolutely correct, and often your comments
are helpful, but this is one of the times when what you're talking about
seems unrelated to this particular bug (about PA crashing)...?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
@Fabio,
I've just uploaded pulseaudio 1:8.0-0ubuntu3 to xenial, and I've
included a patch that *might* fix this issue (the patch in the link,
which you say is broken, but I can click on it just fine). I'm not sure,
but it's worth a try. Hopefully it'll get through all testing to be
relelased in xe
Anyhow the first thing needed is probably an alsa-info:
https://wiki.ubuntu.com/Audio/AlsaInfo
And if possible to reproduce while logging is on, this would be helpful too:
https://wiki.ubuntu.com/PulseAudio/Log
Might not be enough to fix the bug, but should provide a few pointers w
r t where to
Oh, actually this seems fixed with today's latest image, after running a
"sudo apt-get update / sudo apt-get dist-upgrade" I can no longer
reproduce the problem.
Kristin, can you confirm that your problem is fixed in latest xenial?
** Changed in: pulseaudio (Ubuntu)
Status: Triaged => Inco
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549163
Title:
Bluetooth headset HSP/HFP mode not working in Xenial
To man
Confirmed and reproduced here. Relevant log message:
module-bluez5-device.c: Refused to switch profile to headset_head_unit:
Not connected
** Changed in: pulseaudio (Ubuntu)
Status: New => Triaged
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided => Critical
--
You received t
Indeed your alsa-info has some four-channel inputs. Which makes me think
maybe this patch:
https://lists.freedesktop.org/archives/pulseaudio-
discuss/2016-March/025659.html
...could solve the problem. Should at least be worth a try
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed => T
Hi and thanks for spotting! My BIOS has been updated now.
1) Dmidecode now shows:
01.06.00
02/25/2016
2) The hotkey still does not work, but now there is a message in dmesg
when you press it:
dell_wmi: Unknown key with scancode 0xe008 pressed
or
dell_wmi: Unknown key 0xe008 pressed
The forme
Hmm, but the log shows exactly what happens if someone changes the last
lines of /etc/pulse/default.pa from the below (this is the original):
### Make some devices default
#set-default-sink output
#set-default-source input
to this:
### Make some devices default
#set-default-sink output
set-defau
Relevant error in journalerrors.txt:
pulseaudio[3130]: [alsa-source-ALC888 Analog] alsa-mixer.c: Assertion
'pa_cvolume_compatible_with_channel_map(v, cm)' failed at modules/alsa
/alsa-mixer.c:1214, function pa_alsa_path_set_volume(). Aborting.
--
You received this bug notification because you a
equire you to get more logs, try test versions of Pulseaudio, etc).
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) => David Henningsson (diwic)
--
You received this bug notification because you are a
You haven't changed any configuration files (e g such as
/etc/pulse/default.pa ) so they now reference a hard-coded "source #2",
have you?
If not, could you reproduce this with a higher log level (e g by
following https://wiki.ubuntu.com/PulseAudio/Log ) and see if you get
more information out of
(Sorry for late answer)
I find it weird that the suggested change does not work; could you
submit a pulseaudio verbose log ( https://wiki.ubuntu.com/PulseAudio/Log
) where you select the front mic and try to record from it?
And also, one alsa-info from where pulseaudio fails to set front mic
inpu
*** This bug is a duplicate of bug 1539209 ***
https://bugs.launchpad.net/bugs/1539209
** This bug has been marked a duplicate of bug 1539209
pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
We now have 8.x in the archive for xenial.
** Changed in: pulseaudio (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1536166
Title:
Upgrade to 7.99.2 f
> The 7.99.2 is sort of final compared to 7.1
Btw, 7.99.x is the same as the release candidates for 8.0 - they are
meant for testing, they are not stable releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
I tried to look at this, but it looks like a fairly normal volume being
set. Anyone who can reproduce this? It looks like the highest crasher
for pulseaudio on xenial right now.
** Changed in: pulseaudio (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
Stack trace copied from errors.ubuntu.com.
** Attachment added: "stacktrace.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1551610/+attachment/4585352/+files/stacktrace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => David Henningsson (diwic)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 2016-02-25 09:29, Takashi Iwai wrote:
> On Thu, 25 Feb 2016 09:13:21 +0100,
> David Henningsson wrote:
>>
>> On one of the machines we enable, we found that the actual speaker volume
>> did not always correspond to the volume set in alsamixer. This patch
>> fixes
gLink: https://bugs.launchpad.net/bugs/1549660
Co-Authored-By: Kailang
Signed-off-by: David Henningsson
---
sound/pci/hda/patch_realtek.c | 23 +--
1 file changed, 21 insertions(+), 2 deletions(-)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
d.net/bugs/1549660
Co-Authored-By: Kailang
Signed-off-by: David Henningsson
---
sound/pci/hda/patch_realtek.c | 23 +--
1 file changed, 21 insertions(+), 2 deletions(-)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index efd4980..ab353b0 100644
Public bug reported:
On one of the machines we enable, we found that the actual speaker
volume did not always correspond to the volume set in alsamixer.
This bug is for tracking purposes; please do not triage.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linu
Verified with mainline kernel 4.5.0-040500rc5-generic, problem present
there as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1548844
Title:
Inspiron 13-7359: rfkill button has no effect
To
Public bug reported:
Nothing happens when the button to enable/disable rfkill (a k a
"airplane mode" or "wifi/bluetooth disable") is pressed.
Most other buttons seems to work according to evtest although some of
them has no effect (and the "switch video mode" button generates Alt-P).
Some of the
I hope it can be of
assistance to you. Thanks!
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
** Attachment added: "alsa-info.txt.q5CzKNx7En"
https://bugs.launchpad.net/bugs/135355/+attachment/4575479/+files/alsa-info.txt.q5CzKNx7En
--
You received this bug notific
To sum up: 2 bugs in the firmware were hiding that we were accessing the
wrong feature.
Signed-off-by: Benjamin Tissoires
Signed-off-by: Jiri Kosina
BugLink: https://bugs.launchpad.net/bugs/1540511
(cherry picked from commit 73e7d63efb4d774883a338997943bfa59e127085)
Signed-off-by: David Hennin
Ok, I've now built and tested a kernel with 4.4 + the below commit and
can confirm that this commit fixes the touchpad issue for me.
commit 8a7fa6187191f005d4b6d29913de6e128cc778e2
Author: Benjamin Tissoires
Date: Tue Dec 1 12:41:38 2015 +0100
HID: multitouch: fix input mode switching on s
https://bugzilla.kernel.org/show_bug.cgi?id=108481
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540511
Title:
Touchpad not wor
it bisect start
# new: [92e963f50fc74041b5e9e744c330dca48e04f08d] Linux 4.5-rc1
git bisect new 92e963f50fc74041b5e9e744c330dca48e04f08d
# old: [afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc] Linux 4.4
git bisect old afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc
# old: [1289ace5b4f70f1e68ce785735b82c7e483de86
A few more commits...
# new: [92e963f50fc74041b5e9e744c330dca48e04f08d] Linux 4.5-rc1
git bisect new 92e963f50fc74041b5e9e744c330dca48e04f08d
# old: [afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc] Linux 4.4
git bisect old afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc
# old: [1289ace5b4f70f1e68ce785735b82c7e
I'm working on it, here's the result so far:
$ git bisect log
git bisect start
# new: [92e963f50fc74041b5e9e744c330dca48e04f08d] Linux 4.5-rc1
git bisect new 92e963f50fc74041b5e9e744c330dca48e04f08d
# old: [afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc] Linux 4.4
git bisect old afd2ff9b7e1b367172f18ba7
Tested kernels so far:
4.3.0-7 ubuntu - good (touchpad working)
4.5.0-040500rc3 - good (touchpad working)
4.4.0-4 ubuntu - bad (touchpad not working)
4.4.1-040401 - bad (touchpad not working)
4.5.0-040500rc1 - good (touchpad working)
Looks like a temporary regression in 4.4 - maybe we can bisect
list-modems -p (when it says it's roaming)
** Attachment added: "list-modems.whenitsNOTworking.txt"
https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1540970/+attachment/4562301/+files/list-modems.whenitsNOTworking.txt
--
You received this bug notification because you are a member of Ubun
** Description changed:
+ Mobile data does not work, because it says I'm roaming - but I'm not
+ close to any foreign country, so it shouldn't say that.
+
+
+ ~$ system-image-cli -i
+ current build number: 249
+ device name: krillin
+ channel: ubuntu-touch/rc-proposed/bq-aquaris.en
+ last update
Public bug reported:
$ nmcli d
DEVICE TYPE STATE CONNECTION
ril_0gsm disconnected --
ril_1gsm unavailable --
ifb0 ifb unmanaged --
ifb1 ifb unmanaged --
lo loopback unmanaged --
For comparison, here's the output of the same commands when it's working
** Attachment added: "whenitsworking.txt"
https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1540970/+attachment/4562298/+files/whenitsworking.txt
--
You received this bug notification because you are a member of Ubun
** Description changed:
When running a dist-upgrade, I received the following warning:
Setting up linux-signed-image-4.4.0-2-generic (4.4.0-2.16) ...
warning: file-aligned section .text extends beyond end of file
warning: checksum areas are greater than image size. Invalid section table
Public bug reported:
When booting the latest xenial kernel (4.4.0-2.16), my touchpad is not
working. When booting 4.3 kernels, the touchpad is works.
Expected: When I move a finger touching the touchpad, an arrow should move
accordingly on the screen.
What happens instead: nothing.
I've tried a
Public bug reported:
When running a dist-upgrade, I received the following warning:
Setting up linux-signed-image-4.4.0-2-generic (4.4.0-2.16) ...
warning: file-aligned section .text extends beyond end of file
warning: checksum areas are greater than image size. Invalid section table?
ProblemTyp
Public bug reported:
I ran "sudo apt-get autoremove" and when python3.4 and
libpython3.4-minimal:amd64 were removed, the following error was shown
on the screen:
Removing python3.4-minimal (3.4.4-1) ...
Unlinking and removing bytecode for runtime python3.4
Removing libpython3.4-minimal:amd64 (3.4
Public bug reported:
Hi Luke,
Is there a reason you dropped unset_pulse_internal.patch (and two other
patches) from the latest version of alsa-utils?
Now when one runs alsamixer, it goes to PulseAudio by default. Is this expected
behaviour nowadays?
ProblemType: Bug
DistroRelease: Ubuntu 16.04
BugLink: https://bugs.launchpad.net/bugs/1529624
Signed-off-by: David Henningsson
---
sound/pci/hda/patch_realtek.c | 8
1 file changed, 8 insertions(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 3a89d82..2fdda51 100644
--- a/sound/pci/hda
I don't think this is PulseAudio. It's probably something in the kernel
or the Android HAL.
Anyway, after PulseAudio has been playing a sound, there is a five second
timeout until PulseAudio closes the hw stream. Or put it another way,
PulseAudio plays back five seconds of silence after every so
** Bug watch removed: Linux Kernel Bug Tracker #109691
http://bugzilla.kernel.org/show_bug.cgi?id=109691
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error received
Hi,
Indeed booting with pci=noaer (as suggested in the other bug) works
around this issue as well. I'll use that for the time being.
Thanks for working on it!
// David
On 2015-12-29 16:58, Bjorn Helgaas wrote:
> On Fri, Dec 18, 2015 at 11:30:33AM +0100, David Henningsson wrote:
>
** Attachment added: "Broken SVG print preview.png"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1530101/+attachment/4542146/+files/Broken%20SVG%20print%20preview.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Public bug reported:
Not sure this is the right package, but I need to start somewhere.
Steps to reproduce:
Download https://openclipart.org/download/224778/Green-Floral-Frame.svg
Display it with eog, notice that it looks just fine. Click "Print preview" for
either a real printer or the PDF pri
@simplehuman: Don't worry about this patch for now, it's just to help me
remember to upstream it later.
** Patch added: "0001-alsa-mixer-Add-Mic-Source-for-Xonar-STX.patch"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1171435/+attachment/4536658/+files/0001-alsa-mixer-Add-Mic-Sour
> A new option "Front Mic" in sound settings appeared. But... it is not
working.
Did you see my update in comment #30? It should be "Front Panel", not
"Front Mic". After editing, reboot and restart PulseAudio again. Is it
still not working?
--
You received this bug notification because you are a
Sorry, there's a mistake in the above instruction.
For the /usr/share/pulseaudio/alsa-mixer/paths/analog-input-front-mic.conf
file, instead add these lines:
[Element Mic Source]
enumeration = select
[Option Mic Source:Front Panel]
name = analog-input-microphone-front
required-any = any
(Notice
Could you try the following:
Edit this file:
/usr/share/pulseaudio/alsa-mixer/paths/analog-input-front-mic.conf
And add these lines:
[Element Mic Source]
enumeration = select
[Option Mic Source:Front Mic]
name = analog-input-microphone-front
required-any = any
Then edit this file:
/usr/share/
Start alsamixer from a terminal.
You might need to press F6 to select the Xonar sound card, then F4 to see
recording controls.
Use arrow keys to find a control named "Mic Source" and change it from "Mic
Jack" to "Front Panel". Does this enable recording for you?
--
You received this bug notific
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1487141
Title:
"wants to record audio" not localized
To manage notification
Public bug reported:
I have a 2-in-1 laptop with an accelerometer (Inspiron 13-7359). I would
like the screen to change orientation automatically when the screen is
rotated.
I've noticed that the accelerometer works correctly, by installing
iio-sensors-proxy and manually executing d-Bus methods.
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526330
Title:
Fix mic-in mode for a few Dell laptops
To manage notifications
These laptops support both headphone, headset and mic modes
for the 3.5mm jack.
Cc: sta...@vger.kernel.org
BugLink: https://bugs.launchpad.net/bugs/1526330
Signed-off-by: David Henningsson
---
sound/pci/hda/patch_realtek.c | 17 -
1 file changed, 12 insertions(+), 5 deletions
Public bug reported:
This is bug is for tracking purposes only, please do not triage.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: David Henningsson (diwic)
Status: In Progress
** Changed in
The spam rate is 150 lines per second. With ~80 characters per line,
that's about 50 MB per hour. As a very rough measure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected
> Otherwise, the modules are not installed with a message saying that
they are included since 3.99 kernel (not sure of the version as I didn't
save the results)
Oops, a problem with the DKMS packaging. Thanks for the heads up, will
be fixed in the next build.
--
You received this bug notificatio
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523232
Title:
Packard Bell DOTS inverted internal microphone
To manage notif
On the internal mic of the Packard Bell DOTS, one channel
has an inverted signal. Add a quirk to fix this up.
Cc: sta...@vger.kernel.org
BugLink: https://bugs.launchpad.net/bugs/1523232
Signed-off-by: David Henningsson
---
sound/pci/hda/patch_realtek.c | 1 +
1 file changed, 1 insertion
The easy way out is just to blame the hardware. The harder way is to
make sure we don't block other things while waiting for the hardware.
Which should be possible - the tricky thing is to avoid creating races
at the same time...
--
You received this bug notification because you are a member of U
@Raymond, the pcieport errors are unrelated and already reported as bug
1521173
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521606
Title:
[Inspiron 13-7359, Conexant CX20722, Black Mic, Left] Unr
Needs further investigation
** Changed in: alsa-driver (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521606
Title:
[Inspiron 13-7359, Conexant CX2072
I've tried upgrading BIOS to 1.2.0 (latest version on Dell website) and
also with the v4.4-rc3-wily kernel. The dmesg is still spammed with the
same error.
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Branch linked: lp:~diwic/unity-settings-daemon/lp1521664
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521664
Title:
what-did-you-plug-in dialog does not show up
To manage notifications about t
Looks like launchpad is working better today, so I just submitted a MP.
> Also is the name likely to change again? Could we get an autopkgtest
somewhere to let us know that u-s-d needs updating next time?
That is a good question and I understand your concern; but I think the
likelyhood of the po
Patch to resolve the bug (and cause a regression on PulseAudio < 6.0, so
don't backport to trusty).
For some reason launchpad didn't want me to push to a branch today, so
I'm uploading the patch here instead.
** Attachment added: "q.txt"
https://bugs.launchpad.net/ubuntu/+source/unity-setting
1 - 100 of 4716 matches
Mail list logo