Would you mind trying flatpaks? Those had working screensharing and do
not work anymore for me with 21.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950040
Title:
Wayland Screensharing broken
@vanvugt: Thanks for having a look. Have you tried firefox from flatpak or any
other flatpak application?
Also is the "pipewire-media-session" package installed by default? It didn't
seem to be the case for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Tagged regression-release since Wayland Screensharing worked fine in Ubuntu
21.04.
@vanvugt, could you have a look?
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Instead of downgrading (see #2) it also helps to install the package
"pipewire-media-session". This looks like a packaging bug somewhere, since that
would need to be a hard dependency somewhere.
Flatpak apps remain broken though w.r.t screen-sharing.
--
You received this bug notification
For Chromium via Flatpak I get
[304:456:1106/144346.048939:ERROR:base_capturer_pipewire.cc(206)] PipeWire
stream state error: wrong resource type/version
[304:456:1106/144346.048966:ERROR:base_capturer_pipewire.cc(193)] PipeWire
remote error: wrong resource type/version
Everything run via flatpak still has broken screensharing, Firefox from
deb package and Google Chrome via deb package work fine with the
downgraded packages from #2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Downgrading to the following package versions from Ubuntu 21.04 makes
screen sharing work on Ubuntu 21.10:
gstreamer1.0-pipewire_0.3.24-3_amd64.deb
libpipewire-0.3-0_0.3.24-3_amd64.deb
libpipewire-0.3-modules_0.3.24-3_amd64.deb
libspa-0.2-modules_0.3.24-3_amd64.deb
pipewire_0.3.24-3_amd64.deb
Relevant output in journal:
Nov 06 11:14:08 pc xdg-desktop-por[6355]: Unhandled parent window type
Nov 06 11:14:08 pc xdg-desktop-por[6355]: Failed to associate portal window
with parent window
Nov 06 11:14:08 pc GeckoMain[11893]: gdk_wayland_window_configure: assertion
'height > 0' failed
Public bug reported:
Freshly installed Ubuntu 21.10, screen sharing does not work with any
browser, tested the following options:
- Firefox snap
- Firefox deb
- Chromium snap
- Chromium flatpak
Steps to reproduce:
1. Go to
Public bug reported:
Upstream report of this issue: https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/4071
A colleague tested the latest daily of Ubuntu 21.10 and had a red tint after
installing the proprietary nvidia drivers. Did not happen with gnome-shell
versions < 40.
Changing display
No longer a problem in Ubuntu 21.04. In gnome settings go to
"Applications", select Remmina and toggle "Inhibit system keyboard
shortcuts". That gives the application permission to grab the keyboard.
** Changed in: remmina (Ubuntu)
Status: Triaged => Invalid
--
You received this bug
Thank you all for sorting this out quickly. I can confirm everything
works fine now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922423
Title:
Can't connect to some OpenVPN providers using
Done: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4040
Thanks for having a look!
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4040
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4040
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
When I try to input a german umlaut like "ü" in a gnome-shell password
prompt using the onscreen keyboard, nothing appears in the input field.
In regular applications like gedit umlauts work however, so it seems to
be specific to password prompts.
Couldn't find anything
Public bug reported:
There is a bug fixed upstream
https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/issues/64
This makes it impossible to use my VPN connections on Ubuntu 21.04. Please
backport that fix before the release.
** Affects: network-manager-openvpn (Ubuntu)
Importance:
@Daniel Could you triage this to make it in before the release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922423
Title:
Can't connect to some OpenVPN providers using openvpn 2.5.0 and nm-
** Attachment added: "libinput.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1919310/+attachment/5477212/+files/libinput.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919310
** Attachment added: "xinput.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1919310/+attachment/5477211/+files/xinput.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919310
Public bug reported:
Hardware: Dell XPS 13 9310 2-in-1 with Dell Premium Active Pen (PN579X).
When using the Wayland session, I can't see a cursor moving when
hovering with the pen. In the Xorg session a mouse cursor is shown that
follows the pen as I hover over the display.
It would be nice to
Thanks Daniel, great work as always! Confirmed that downgrading to gjs
1.67.2-1 and libgjs0g 1.67.2-1 solves the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918738
Title:
Regression:
Public bug reported:
Title pretty much says it all: I'm testing Ubuntu Hirsute (21.04), fully
upgraded as of today (Gnome-shell 3.38.3) and the osk keys for Backspace, Enter
and Capitalize as well as for collapsing the keyboard do not work. Pressing
them just does nothing.
Related logs in
@didrocks Any ETA for the 21.04 channel? I'd like to test this asap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802533
Title:
[MIR] pipewire
To manage notifications about this bug go to:
@seb128: Yes that's still an issue unfortunately (tested with btrfs
subvolume).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442649
Title:
nautilus trash doesn't include btrfs and zfs subvolumes
Thanks, will this land in focal too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896622
Title:
scp-dbus-service.py crashed with SIGSEGV
To manage notifications about this bug go to:
Public bug reported:
I printed something, afterwards I wanted to print again, but the printer did
not receive the print job, so I cancelled the job and tried to start it yet
again. Unfortunately it did not resolve the situation.
So I cancelled the print job and while at it, I changed the
Can confirm the issue with a Dell Precision M4700: While memtest of
Ubuntu 18.04.5 server iso works, memtest of Ubuntu 20.04.1 server iso
freezes instantly after 1 second.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@seb128: Yes, it's really annoying. I have to be really careful not to
zoom too much in and out my documents as everytime it could be the last
time before evince and all it's child windows freezes indefinitely.
It seems to me like it happens in the rendering code. Reproducing
sometimes need
Also note that this deadlock happens both in wayland and xorg gnome
session. The backtrace I generated in
https://gitlab.gnome.org/GNOME/evince/-/issues/1222 was in the xorg
session though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: apport
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/1866996
Title:
apport-retrace sandbox can not be used with https mirrors in
sources.list
Still happens as of Ubuntu 20.04, I reported it to upstream now:
https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1016
** Changed in: gnome-software (Ubuntu)
Status: Expired => Confirmed
** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/-/issues #1016
@vanvugt: What would be your proposed way to fix this in Ubuntu if
upstream doesn't change their mind? A new extension? Adding a patch to
the package?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- Here I collect a couple of issues regarding apport-retrace with "-S
- system".
+ If /etc/apt/sources.list only contains https mirrors (and not a single
+ http:// entry), then apport-retrace fails to determine the default
+ mirror:
- 1. apport-retrace does not work for
@Brian: I will open a separate bug for comment #9 soon, as this issue
here is about the https issue.
Since you asked to reproduce please fully upgrade your focal
installation and use the files as found in the attached tar archive.
Command to reproduce is:
apport-retrace -v -s -R -S system
@Brian: Thanks for merging the patch. As for reproducing the https
issue: The issue happens if ALL entries in fstab are https mirrors, like
deb https://mirror.init7.net/ubuntu/ focal main restricted universe multiverse
deb-src https://mirror.init7.net/ubuntu/ focal main restricted universe
Public bug reported:
I am not using the ubuntu modifications of gnome-shell and therefore the
Appearance tab in the gnome-control center is essentially useless, and
what's worse choosing an option in the window colors selection simply
crashes control center.
Therefore it would be appreciated to
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273764
Title:
Grub ignores TIMEOUT options on /etc/default/grub
To manage notifications about this bug go to:
I tried to rootcause my flicker over the last few days, it was
definitely not due to the kernel and neither due to plymouth (tried by
installing the respective packages from focal in eon and vice versa in
focal). One thing I wanted to try next was initramfs but did not have
the time to test.
Regarding the video showing the flicker: I missed to film the upper part
of the screen, so you don't get to see the cursor flashing up in the
upper left corner.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@vanvugt Coming from the other bug report I'm trying to describe my
problem:
First of all I don't see purple as I have disabled the purple grub by running
chmod -x /etc/grub.d/05_debian_theme
Secondly: In Ubuntu 19.10 there is no flicker happening for me, while in
Ubuntu 20.04 there is a
@vanvugt: Why is it then that it flickers in focal but does not flicker
in eoan for me?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836858
Title:
i915: Display flickers (monitor loses signal
** Description changed:
- This is a reintroduction of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am
experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did
not happen before in Ubuntu 19.04.
-
+ This is a reintroduction of
+
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321861/+files/UdevDb.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Attachment removed: "AlsaDevices.txt"
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321859/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860390
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321854/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321855/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321852/+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/1860390
Title:
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321853/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860390
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321858/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860390
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321860/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860390
Title:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321856/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860390
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321857/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321849/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Card0.Amixer.values.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321848/+files/Card0.Amixer.values.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Card0.Codecs.codec.2.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321850/+files/Card0.Codecs.codec.2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
This is a reintroduction of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am
experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did
not happen before in Ubuntu 19.04.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321851/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "AplayDevices.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321846/+files/AplayDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1860390/+attachment/5321847/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860390
Title:
Dell
Public bug reported:
This is a reintroduction of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957 which I am
experiencing with Ubuntu 20.04 fully upgraded on a Dell XPS 13 9360. This did
not happen before in Ubuntu 19.04.
It seems that the Dell 9360 is set to go into s2idle
Affects me too on a Dell XPS 13 9360, I opened a new bug here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808957
Title:
Dell XPS 13
** Changed in: evince (Ubuntu)
Status: Fix Committed => 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/1436555
Title:
evince crashed with SIGSEGV in
@William: I downloaded your pdf and checked: It does not reliably
trigger this issue for me. But I experience the freeze issue almost
daily, it happens randomly while zooming in documents. Sometimes I open
a document and within the first zoom it freezes, sometimes I have to
play around for minutes
@vanvugt: Also tested Focal on the XPS 13 9360 now, it's flickering
there. So the issue is fixed in Eoan but not in Focal. Could you push
the fix to Focal too?
** Tags removed: eoan
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@vanvugt No flickering for me on an XPS 13 9360 apart from the
brightness getting adjusted at the same time the spinner starts. When
the brightness is set to maximum before rebooting I don't notice
anything apart from the spinner appearing. In a perfect world the
brightness would be adjusted
Public bug reported:
Take a fresh installation of Ubuntu and remove the package netplan.io.
Now you will observe, that network-manager no longer detects wired connections.
Installing ifupdown instead of netplan does not help this situation.
In debian sid networkmanager detects the wired
Indeed, I forgot to upgrade so I missed the issue. Now that I did I see
the hiss is indeed much louder. Thanks Kai for sending this upstream
already.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've had this issue since 2017 all the time. As you can see in the
comments, Kai suggested that this is an hardware issue. He developed a
workaround for the kernel that I tested, however it made the general
output volume significantly lower, see #96, which is the reason this fix
was never shipped.
It doesn't work for me, the relevant files mentioned here (e.g.
/usr/share/initramfs-tools/hooks/cryptroot) have changed significantly in the
meantime.
Only specifying header= in crypttab does not work for me, the file is
not included in the initramfs.
@therealmarv: Could you tell me how you
I had exactly the same problem. Indeed removing the lines in the other files
solved the issue!
I don't think I have followed the same guide but some other guide (don't
remember which on exactly) a few years ago which roughly suggested the same.
Thanks Steve for resolving this, thanks Xavier for
would be great if someone from Ubuntu/Canonical could triage this
issue!?
** Tags added: disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804314
Title:
Wrong WARNING Option 'hash' missing in
I can confirm this bug. I have a similar crypttab with only "luks" on the very
right and I get the same warning every boot.
Unlocking the drive works without any problems. This did not happen with
previous ubuntu versions.
** Tags added: cosmic
--
You received this bug notification because
I have forwarded the info to the Debian maintainers Guido Günther, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698504
He would like to see the patch upstreamed ...
@Till, @shemgp could you please propose your patch to upstream?
Furthermore, could you please arrange with the Debian
Got my touchpad replaced in November, I have never seen this issue
again, Dell support on twitter is amazing btw.
** Changed in: dell-sputnik
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you
The thing that makes this bug so annoying for me is that sometimes I do
not experience it for weeks and suddenly it appears and does not stop
but in the end stops again as unexpected as it started. This bug is
clearly non deterministic.
I even managed to find a way to reproduce it, but only under
For the output volume I made the following observations:
* Even with a volume boost of 150% in Pulseaudio (the maximum), the output
volume is still significantly lower than the unpatched kernel
* With 150% pulseaudio boost, I can hear disortions and crackling, so the sound
quality gets
Kai, I compile my own kernels and I would like to use this right now,
could you please link me the patch? The test kernel floods my syslog
badly with touchpad debug entries (unrelated to this bug).
Now regarding testing: By software boost you mean we should test both:
Microphone software boost
Kai: I do not understand your last comment, could you elaborate? Did you
mean we should test if software boost = pulseaudio boost performs well
enough?
Kai, I am quite happy with
http://people.canonical.com/~khfeng/lp1654448-2/ please link me the
patch as the only drawback would be the lower
Could you please post the patch for
http://people.canonical.com/~khfeng/lp1654448-2/ ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and 9350, Realtek ALC3246, Headphone
Kai, http://people.canonical.com/~khfeng/lp1654448-2/ does not have the
hiss :-).
Would compensating the lower output volume with setting pulseaudio to
100+% make the quality worse? Does setting pulseaudio to e.g. 130%
disort the quality?
--
You received this bug notification because you are a
Kai, Thank you very much for looking into this and answering questions. Kudos!
I think the behavior should remain as it is if the output volume is reduced
that much AND support for microphone devices is crippled.
My arguments: It is still better to hear the hiss when music is at low volume
than
Yeah but I don't think it gets through to the right people. If I read most of
the forums discussions no one acknowledges the problem. Only suggestions are to
install the latest drivers.
The 9360 came out one year after the 9350 and still has the same issue. User's
experiences are not that grave
Kai: I understand what you are saying ... but I would find it great if
you could point that out to Dell ... just because now it is bad, does
not mean it can't be improved in the future. With proper hardware
testing this could have been avoided.
--
You received this bug notification because you
Kai: Yeah but it would be nevertheless good to communicate that to the right
people of Dell.
Is this an integrated component I can't exchange? Is it Intel integrated Audio
or is it an external chip?
Hence I would like to do something on hardware level ... is this not
possible?
--
You
Kai: So you are saying the sound card is buggy on a hardware level? Does
this only affect XPS13's or are other Laptops possibly affected too? I
guess all that are using the same soundcard?
How about communicating this to Dell? Or isn't this their fault? Is the
vendor of the sound card to fault?
Kai: Confirmed my assumption, your patch SIGNIFICANTLY lowers the output
volume!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio
load-module module-echo-cancel aec_method=webrtc sink_name=cancel.out
source_name=cancel.src
set-default-source cancel.src
set-default-sink cancel.out
does not change anything either. To make the hiss disappear I have to
mute the hardware output device.
Would be glad if someone could point out
Regarding the second question: The workaround "amixer -c 0 set
'Headphone Mic Boost',0 1" does lower the output volume significantly.
If your patch does the same as the workaround, then the output volume
would be significantly lower, I have not tested this yet though.
--
You received this bug
Another question: You say your code does the same as the workaround
"amixer -c 0 set 'Headphone Mic Boost',0 1" ... so the output volume is
decreased too with your patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
load-module module-echo-cancel aec_method=webrtc source_name=cancel
set-default-source cancel
does not improve the situation. The hiss remains unchanged for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks very much for the code!! Out of interest, how would you achieve
the noise cancellation with pulseaudio?
I tried
load-module module-echo-cancel source_name=test
set-default-source test
which did not work.
A new device appears called "Built-in Audio Analog Stereo (echo
cancelled with
When you connect the jack you can choose between 3 options normally
(with the kernel in [1] only two now)... isn't it somehow possible to
operate with microphone disabled by default ... but leave the user the
option to use a traditional mircophone? The white noise should then only
be triggered
Yes that solves the issue :-). Could you link me the code changes?
But are you sure you can't fix the support for traditional microphones? :-(
Would be a sad loss, could you elaborate why this is not possible?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Yes it disappears! (forgot to run alsamixer as root).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss
To manage
amixer -c 0 set 'Headphone Mic Boost',0 1 does not work, it says
"Headphone Mic Boost" not found, so yes, I am however not familiar with
alsamixer. Where would I find "Headphone Mic Boost"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Same situation :-(. The hiss is cleary audible, no change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss
To manage
This time there are no KHFENG entries in dmesg.
** Attachment added: "new.txt"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+attachment/4900217/+files/new.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+attachment/4900166/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Unfortunately the hiss is still there :-(.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss
To manage notifications about
Is it already the new one as of now? I have just tried it and it did not
help :-(.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and 9350, Realtek ALC3246, Headphone
I confirm Daniel van Vugt, same for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss
To manage notifications about this
1 - 100 of 222 matches
Mail list logo
