Public bug reported:
When setting /etc/apparmor.d/usr.bin.chromium-browser to enforced mode,
chromium browser no longer starts on fully updated utopic as of today.
In the previous weeks this worked without problems, so something broke recently.
With chromium in enforced mode I get Could not
** Attachment added: my unmodified profile
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1374363/+attachment/4216041/+files/usr.bin.chromium-browser
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
Public bug reported:
Profiles in /etc/chromium-browser/policies/managed or /etc/chromium-
browser/policies/recommended are ignored when using the apparmor
profile.
Syslog excerpt:
Feb 7 17:10:11 ubuntu kernel: [23893.781721] audit: type=1400
audit(1423325411.004:109): apparmor=DENIED
** Summary changed:
- package modemmanager 1.4.0-1 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 100
+ [systemd] package modemmanager 1.4.0-1 failed to install/upgrade: subprocess
installed post-installation script returned error exit status
pitti, please have a look, this seems to be related to systemd.
I hit this bug when using debootstrap+chroot (deboostrapping vivid to a new
partition, then chrooting into the tree and then installing ubuntu-desktop):
When the host system is an upstart system (14.10, fully updated), installing
/var/log/apt/term.log of deboostrap system.
** Attachment added: /var/log/apt/term.log of deboostrap system.
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1447955/+attachment/4390775/+files/term.log
--
You received this bug notification because you are a member of Ubuntu
Touch
/var/log/apt/history.log of deboostrap system.
** Attachment added: /var/log/apt/history.log of deboostrap system.
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1447955/+attachment/4390781/+files/history.log
--
You received this bug notification because you are a member of
pitti, and how do you explain the strange behavior I observe with my deboostrap
install method? NOTE: It works with the utopic host, but not with the vivid one.
As I workaround touch /etc/init.d/modemmanager works.
--
You received this bug notification because you are a member of Ubuntu
Touch
Just retested today. I have a bash script that debootstraps vivid, chroots into
it and installs ubuntu-desktop.
From my utopic systeme everything is fine, but when the exact same script is
run from the vivid live-cd, it fails with installing modemmanager.
Regarding chroot mounts:
mount --bind
This really needs to be resolved, I subscribed Michael Vogt, the
original maintainer of this package, maybe he has an idea.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu.
pitti, awesome as always, thanks, your explanation is right. The missing
policy was the problem. Thanks very much!
For people coming here through googleing, that have that problem in a
chroot, see https://wiki.debian.org/chroot#Configuration
--
You received this bug notification because you are
sbeattie: Any chance of building bash with pie in the future? 16.10 has
4.8 as default kernel, so disabling pie should not be necessary
anymore!?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
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
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and
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: 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
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
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: 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: 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
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, 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
Kai: Confirmed my assumption, your patch SIGNIFICANTLY lowers the output
volume!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and 9350,
Subscribed Kai-Heng Feng, the submitter of the linked patch
(https://patchwork.kernel.org/patch/9128611/), maybe he could give a
status update!?
My two machines are affected too (XPS 13 9360), confirming the
workaround from #5
amixer -c 0 set 'Headphone Mic Boost',0 1
--
You received this bug
Wow, thanks for the quick reply, I am willing to provide any information
you need, thanks very much for having a look.
** Attachment added: "lshw"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+attachment/4869101/+files/lshw
--
You received this bug notification because
** Attachment added: "hwinfo"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+attachment/4869156/+files/hwinfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
** Attachment added: "hwinfo"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+attachment/4869155/+files/hwinfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
The mentioned workaround
amixer -c 0 set 'Headphone Mic Boost',0 1
has the drawback of significantly lowering the headphone volume!
You can easily test it listening to audio and switching back to
amixer -c 0 set 'Headphone Mic Boost',0 0
--
You received this bug notification because you are a
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
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and 9350,
I confirm Daniel van Vugt, same for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss
** 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
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
Same situation :-(. The hiss is cleary audible, no change.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and 9350, Realtek ALC3246,
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
Touch seeded packages, which is
Unfortunately the hiss is still there :-(.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss
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
Touch seeded packages, which is
Yes it disappears! (forgot to run alsamixer as root).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
XPS 13 9360 and 9350, Realtek ALC3246, Headphone
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
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
Touch seeded packages, which is subscribed to pulseaudio in
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
Touch seeded packages, which is subscribed to
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
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
Touch seeded
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
Kai, I have tested the 4.12 mainline kernel. The hiss is clearly audible.
Please make suggestions how I can help you.
My earphones are Bose Soundtrue Ultra, but I guess that wont be helpful
to know.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Addendum to the original description:
Steps to reproduce:
0. Make sure tlp is NOT installed
1. Plug in headphones
2. Make sure volume is not muted!
NOTES:
Ad 0.: tlp configures audio power saving, the hiss is only noticeable when
listening to music.
Ad 2.: If the headphones are muted then
@vanvugt: The earphones I tested (Bose Soundtrue Ultra) are Android
ones. I have also tested headphones with no microphone (Sennheiser
HD202).
@kaihengfeng: I will install Ubuntu from scratch in order to test your
kernelsl
--
You received this bug notification because you are a member of Ubuntu
Confirming Daniel van Vugt: The kernel
http://people.canonical.com/~khfeng/lp1654448/ does not improve the
situation.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
I tried blacklisting the snd_hda_codec_realtek module, sound works, but
now I can hear the coil whine, depending on the activity of the cpu/gpu.
Moving the mouse pointer around is clearly audible etc.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
@vanvugt: I can clearly reproduce the problem with headphones too, I do
not notice they "hide" anything.
I noticed the hiss listening to music so I can always clearly hear it
and it becomes very apparent in a quiet environment.
On another note, with the workaround in place the audio is way to
Kai-Heng Feng: Is there anybody still working in this? Are you sure Kailiang
noticed this bug?
Is there anything else I could do for you to help?
** Changed in: dell-sputnik
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Attachment removed: "hwinfo"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+attachment/4869156/+files/hwinfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
@spike speigel: The tlp issue in the arch Linux wiki is unrelated. The point I
was that when tlp is installed and no audio is currently playing, tlp turns off
the sound card and thus the hiss disappears.
The second point I was trying to say: Of course the white noise is audible when
nothing is
Regarding the Bose Quiet Comfort ... those are noise cancelling headphones, it
is no surprise to me that those cancel the hiss.
I have tested multiple normal earphones and I can reproduce the issue everytime.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
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
Touch seeded packages, which is subscribed to pulseaudio in 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.
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
** 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: 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
@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
@seb128: Yes that's still an issue unfortunately (tested with btrfs
subvolume).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1442649
Title:
nautilus trash doesn't
** Changed in: apport
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1866996
Title:
apport-retrace sandbox can not be used with
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
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
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
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
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
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
Touch seeded packages, which is subscribed to ubuntu-meta
67 matches
Mail list logo
