Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: wayland (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
** Bug watch added: Debian Bug tracker #969284
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969284
** Also affects: wayland (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969284
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Attachment added: "unattended-upgrades-dpkg.log.4"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1893889/+attachment/5406808/+files/unattended-upgrades-dpkg.log.4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Attachment added: "dpkg_-l"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1893889/+attachment/5406810/+files/dpkg_-l
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
Uploaded all historical log files in lp1893889-logs.tar.gz
Uploaded dpkg_-l
For convenient access also uploaded unattended-upgrades.log.4,
unattended-upgrades-dpkg.log.4 and dpkg.log.6 which have the lines from
the first instance of hitting the error
--
You received this bug notification
** Attachment added: "dpkg.log.6"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1893889/+attachment/5406809/+files/dpkg.log.6
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
** Attachment added: "unattended-upgrades.log.4"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1893889/+attachment/5406807/+files/unattended-upgrades.log.4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Attachment added: "all unattended-upgrades and dpkg logs"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1893889/+attachment/5406806/+files/lp1893889-logs.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I would say "Won't Fix" if it was up to me. Because those LEDs are
conceptually tied to the internal speaker and internal microphone. But
there is a related upstream enhancement request already:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/924
** Summary changed:
- Led for
Does it possible to add predefined nat chains? Like what the openwrt
does.
UFW can insert `ufw_prerouting_rule`, `ufw_postrouting_rule` on start, and
remove these on stop.
User can insert their custom rules in the ufw chains, without worry about the
flush/duplicate issues.
--
You received
Public bug reported:
unattended-upgrades attempted to upgrade nova from 2:17.0.9-0ubuntu1 to
2:17.0.10-0ubuntu2.1 (bionic-security), however nova-common contains a
modified conffile (/etc/nova/nova.conf) which prompts during upgrade and
leaves apt/dpkg in a permanent error state requiring manual
First, delete any cached copy of the .deb in question as it may be corrupted.
The package will be downloaded again when you reinstall it:
sudo rm /var/cache/apt/archives/libx264*
(Or, if you want to clear entire package cache, run: sudo apt clean)
Then you can try and reinstall the problematic
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1893880
Title:
package linux-image-4.4.0-186-generic 4.4.0-186.216 failed to
Public bug reported:
system does not restart properly
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-186-generic 4.4.0-186.216
ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223
Uname: Linux 4.4.0-184-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.24
It's more like a feature needs to be implemented in PulseAudio...
** Package changed: linux (Ubuntu) => pulseaudio (Ubuntu)
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
You have been subscribed to a public bug:
The F1 and F4 LEDs are not working when a USB-C headset is plugged in. The
LEDs work correctly for internal devices and when using the bantam jack. This
is on 20.04 LTS release.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.8
Architecture:
Public bug reported:
dpkg: error processing package lvm2 (--configure):
installed lvm2 package post-installation script subprocess returned error exit
status 1
Processing triggers for initramfs-tools (0.136ubuntu6.2) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-45-generic
Errors were
It looks like there are disconnection/reconnection problems with the USB
dongle for this mouse in your kernel log. So this might be a kernel bug
or it might be a hardware problem.
Please try:
* A different mouse
* A different kernel like https://kernel.ubuntu.com/~kernel-
Do you see the same problem in Google Chrome (or Chromium)? It looks
like bug 1893217 might be the same issue.
** Summary changed:
- [nvidia] Some GNOME apps are partially transparent/corrupt
+ [nvidia] Some apps are partially transparent/corrupt
--
You received this bug notification because
** Summary changed:
- Dell Inspirion 5391: headphones work only if I manually switch source port
every time and no different volume levels for speaker and headphones
+ Headphones work only if I manually switch source port every time
--
You received this bug notification because you are a
Might be related to bug 1881659.
** Changed in: pulseaudio (Ubuntu)
Status: New => Incomplete
--
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/1893846
Title:
Please run this command to send us more info about the machine:
apport-collect 1893846
** Tags added: focal
** Summary changed:
- headphones don't automatically works when plugged in
+ Sound doesn't switch to headphones automatically when plugged in
** Package changed:
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1886714
Please look in /var/crash and tell us if you have any crash files there.
Also next time the freeze happens, please then reboot and run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
** Tags added: amdgpu
** Summary changed:
- Screen freeze when loging in after a
You have been subscribed to a public bug:
1) Ubuntu 20.04.1 LTS
2) gnome-control-center 1:3.36.4-0ubuntu1
3) What you expected to happen:I expected to connect my headphone and listen to
any sound automatically.
4) What happened instead: In order to make the headset work, I must go to the
Thanks. I think this is probably a compositor (Mutter) bug. Although as
soon as Nvidia driver 450 reaches official updates (it hasn't yet) I
would also recommend trying that:
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450
** Summary changed:
- [nvidia] Some apps show
** Summary changed:
- Bluetooth disconnects, and then sound fails on reconnect
+ [Broadcom BCM20702A0] Bluetooth disconnects, and then sound fails on reconnect
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
Thanks. I wonder if you could also test regular Ubuntu for completeness?
Like just from a live USB boot:
https://releases.ubuntu.com/20.04/
I would like to rule out the possibility that this is unique to unity-
control-center.
** Summary changed:
- Headphones connect but don't appear as
*** This bug is a duplicate of bug 1892521 ***
https://bugs.launchpad.net/bugs/1892521
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1892521, so it is being marked as such. Please
hi @cpaelzer, sorry i missed reading this earlier, i'll give all the
test failures a look to see what can be done.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1892358
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
OK, I've spent some time investigating this one, so I decided to post my
progress here. Unfortunately I don't have a full fix yet, but I managed
to find some interesting pointers related to systemd.
First of all, I confirmed what Christian and Andreas were seeing: the
problem happens on every
this is fixed in sid
wayland (1.18.0-2~exp1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Add missing dependency on libffi-dev (closes: #969284).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in
Public bug reported:
ubuntu-bug shall try to find a package a command belongs to if the given
name does not match an installed package.
Now:
# ubuntu-bug ubuntu-bug
dpkg-query: Kein Paket gefunden, das auf ubuntu-bug passt
ubuntu-bug shall do in such cases:
- look for the package:
# dpkg -S
This bug was fixed in the package initramfs-tools - 0.137ubuntu12
---
initramfs-tools (0.137ubuntu12) groovy; urgency=medium
* d/tests: Add explicit call to partprobe on net test, specially in
prep-image and run-image. (LP: #1893675)
initramfs-tools (0.137ubuntu11) groovy;
This bug was fixed in the package initramfs-tools - 0.137ubuntu12
---
initramfs-tools (0.137ubuntu12) groovy; urgency=medium
* d/tests: Add explicit call to partprobe on net test, specially in
prep-image and run-image. (LP: #1893675)
initramfs-tools (0.137ubuntu11) groovy;
This bug was fixed in the package initramfs-tools - 0.137ubuntu12
---
initramfs-tools (0.137ubuntu12) groovy; urgency=medium
* d/tests: Add explicit call to partprobe on net test, specially in
prep-image and run-image. (LP: #1893675)
initramfs-tools (0.137ubuntu11) groovy;
--- Comment From s...@de.ibm.com 2020-09-01 12:36 EDT---
This is now fixed on flatpak master, see merged pull-request:
"Fix argument order of clone() for s390x in seccomp filter #3777"
https://github.com/flatpak/flatpak/pull/3777
--
You received this bug notification because you are a
Uploading additional grab with my camera showing the corruption on Gnome
Tweaks window where it looks as though a terminal window behind Firefox
(two windows back from this) is showing through.
** Attachment added: "IMG_20200901_095617.jpg"
Public bug reported:
I'm on 20.04, on a Dell XPS 9730. Upon boot, the wired connection comes
up fine but, after a seemingly random time, the interface fails. If I
watch the NetworkManager journal and try and switch the interface off
and then back on in Gnome Control Panel, the interface keeps
The only way to get this back is a reboot, which also hangs due to
trying to stop the NetworkManager service.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1893798
After discussing with Eric, seems initramfs-tools was "released" in
Groovy (even with autopkgtest), so I'm hereby attaching an updated
debdiff only with the autopkgtest fix.
** Patch added: "groovy_initramfs_lp1879980_lp1893675_V3.debdiff"
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1893797
Title:
package ubuntu-standard 1.325.1 failed to install/upgrade: package
Public bug reported:
Trying to upgrade 14.04 to 16.04
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: ubuntu-standard 1.325.1
ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
Uname: Linux 3.13.0-170-generic x86_64
NonfreeKernelModules: wl
ApportVersion:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: whoopsie-preferences (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie-preferences in
> No, it would not. The sum totality of the impact of this bug is the extra
warning messages in the log files.
Damn...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1860826
I found out the cause for this, but other backends are affected too probably
- basically the packagekit daemon assumes that packages can be trusted
themselves,
so backends that do not have trust information in packages need to explicitly
reject local packages as untrusted, so that PackageKit
The workaround doesn't seem to help. I also notice that when the
headphones connect, the Bluetooth settings window shows them connected
for a second or so, then disconnected again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
As soon as I can get an [Asus USB BT500](https://www.asus.com/Networking
/USB-BT500/) I will try that, as I suspect this issue is somehow related
to the chip in the dongle. It seems like all dongles with the same chip
has the same issue. The sound problem is probably (?) a secondary
effect, but
** Also affects: orca (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: at-spi2-atk (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: orca (Ubuntu Focal)
Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)
** Changed in: orca
** Also affects: pam (Ubuntu Groovy)
Importance: Undecided
Status: Invalid
** Also affects: gdm3 (Ubuntu Groovy)
Importance: Low
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: Confirmed
** Tags removed: rls-gg-incoming
--
You received this bug notification because
According to the log of #18, looks like after resuming, the pulseaudio
tried to set the pcm to 5.1 channels on the hdmi-surround-extra1, but
failed:
D: [pulseaudio] alsa-util.c: snd_pcm_hw_params_set_channels(6) failed: Invalid
argument
D: [pulseaudio] alsa-util.c: Trying hdmi:2,1 without
And could you please test this kernel:
https://people.canonical.com/~hwang4/testdetect/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1893566
Title:
[MS-7A40,
The patch of #17 is reverted from upstream, and the patch is cced to
stable, it will be in the ubuntu kernel sooner or later.
thx.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
Weird, even you plug the headphone before booting, the headphone is
still not recognized. I don't know why your headphone could work in this
situation.
this is from #3:
control.11 {
iface MIXER
name 'Headphone Playback Switch'
value.0 false
Please see attached. As you can see I have the Ubuntu Software tool to
the right, and I have Gnome Tweaks open to the left. You can also see
other apps that are showing normal functioning. Gnome Tweaks
particularly doesn't seem to show corrupted window decorations unless
Ubuntu Software is open.
Public bug reported:
I use Kubuntu 20.04.1 on Thinpad T495 with encrypted disk (LVMS) and
finger print reader.
PROBLEM:
1. I boot the laptop and can work
2. I log my user out and try to log in again with te password
3. I enter the password and press enter
4. The screen freezes and shows the
Public bug reported:
Hi!
after the latest update, I observe problems with the font size used by gdm and
the gnome gui.
It seems that the font size is now twice as large as before. This affects the
login screen as well as elements of the gui (top bar, icon names on the
desktop, pop up menus
** Also affects: landscape-client (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1893716
Title:
scripts in
** Also affects: base-files (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1893716
Title:
scripts in
I tested the packages below on 2 ThinkPads(one is Intel Only, another is
Intel + Nvidia), the sound functions works fine.
- libasound2, version 1.2.2-2.1ubuntu2
- libasound2-data, version 1.2.2-2.1ubuntu2
- alsa-ucm-conf, version 1.2.2-1ubuntu0.2
- pulseaudio, version 1:13.99.1-1ubuntu3.6
-
They don't appear in the audio device list at all. Thank you for the
workaround; I'll give it a try and let you know if it helps.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
Hi again,
On 2020-08-27 08:25, Alkis Georgopoulos wrote:
>> Possibly console-setup could be modified again, so the default
>> shortcut depends on XDG_CURRENT_DESKTOP ("No toggling" for GNOME
>> and "Alt+Shift" for others). That way there wouldn't be a need to
>> involve ubiquity or other
Public bug reported:
The version of wayland-client.pc in groovy has a Requires.private:
libffi, which means “pkg-config --static --libs wayland-client” requires
libffi.pc to be installed, but libwayland-dev does not depend on libffi-
dev.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package:
Debdiff for focal SRU.
** Patch added: "pulseaudio_13.99.1-1ubuntu3.7.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866194/+attachment/5406354/+files/pulseaudio_13.99.1-1ubuntu3.7.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch
On Tue, Sep 01, 2020 at 01:53:00AM -, Sterling Butters wrote:
> Would this bug cause a gnome-session initialization delay?
No, it would not. The sum totality of the impact of this bug is the extra
warning messages in the log files.
--
You received this bug notification because you are a
** Description changed:
+ [Impact]
+
+ Selected audio output device in Settings is ignored after upgrading to
+ Ubuntu 20.04.
+
+ [Test Case]
+
+ Start with an older version of Ubuntu like 19.04 or 19.10 and upgrade to
+ 20.04. When done, attempt to connect a Bluetooth or USB audio device and
67 matches
Mail list logo
