Patches submitted to SRU:
https://lists.ubuntu.com/archives/kernel-team/2020-September/113701.html
https://lists.ubuntu.com/archives/kernel-team/2020-September/113702.html
https://lists.ubuntu.com/archives/kernel-team/2020-September/113703.html
--
You received this bug notification because you a
What is missing from your description is what happens after your system
has finished rebooting.
Does the share mount when you issue one of the following commands:
sudo mount -a
Or:
sudo mount /mnt/server_e
Both of those commands will reference the fstab declaration.
If it does this may not be
** Changed in: lttng-modules (Ubuntu Bionic)
Assignee: (unassigned) => Stefan Bader (smb)
** Changed in: lttng-modules (Ubuntu Xenial)
Assignee: (unassigned) => Stefan Bader (smb)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-hwe-5.4 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894424
** Also affects: lttng-modules (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: lttng-modules (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: lttng-modules (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: lttng-modules (Ubun
You may want to consider filing RFP bug in Debian:
https://www.debian.org/devel/wnpp/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896737
Title:
needs-packaging
To manage notifications about this
Focal test build at: https://launchpad.net/~smb/+archive/ubuntu/temp01
Verification in VM:
root@test-f1:/usr/src/lttng-modules-2.11.2# dpkg -l |grep lttng-modules-dkms
ii lttng-modules-dkms 2.11.2-1ubuntu0.2 all
Linux Trace Toolkit (LTTng) kernel modules
The bug is fixed when I updated mutter to 3.36.1-1ubuntu0.20.04.1.
BUT
After an "Automatic Screen Lock", the display turned off, the Gnome
Shell crash and show us a blank screen with the message "Oh no!
Something has gone wrong."
This bug did not appears before the update.
I have a NVIDIA c
SRU review: as discussed on IRC this needs further documentation please:
Why is an update to the 5.4 kernel required and how can we ensure that
existing users on Focal are not regressed?
Why is this not being fixed in Groovy first, as is the normal SRU
policy?
Thanks
--
You received this bug n
This bug was fixed in the package libreoffice - 1:6.4.6-0ubuntu0.20.04.1
---
libreoffice (1:6.4.6-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1892783)
-- Heather Ellsworth Mon, 24 Aug
2020 16:58:01 -0600
** Changed in: libreoffice (Ubuntu Focal)
Easiest is to just look at policykit log and see that it triggers the
untrusted action, fwiw. IMO.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1882098
Title:
Packagekit lets user install u
I have tested the fix on Focal and confirmed it works. Here is a link to the
diff in our PPA:
https://launchpadlibrarian.net/498490932/mdadm_4.1-5ubuntu1_4.1-5ubuntu1.1~wiktel1.20.04.1.diff.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Attached patch for xenial, but I can't test it.
$ pkcon install-local xterm_353-1ubuntu1_amd64.deb
Installing files [=]
Finished [=]
Fatal error: MIME type 'application/vnd.debian.binary-package' no
Seriously... 10 years and nothing? This device (BCM58200, 0a5c:5843) is
working with Fedora without any issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/602071
Title:
[0a5c:5801] Broadcom finge
This would be the proposed fix for focal which should also prepare us
for the coming hwe kernels as well. For bionic there likely will be a
similar change needed. At least to handle hwe-5.4 but potentially the
upstream change got backported to 4.15 as well.
** Patch added: "proposed-focal-fix.debd
Public bug reported:
Disks utility program and command line only seeing the drive as read
only. unable to write data to the disk. all works OK in Windows 10.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: brasero 3.12.2-6ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname
The verification of the Stable Release Update for libreoffice has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
This bug was fixed in the package cryptsetup - 2:2.3.3-1ubuntu6
---
cryptsetup (2:2.3.3-1ubuntu6) groovy; urgency=medium
* Introduce retry logic for external invocations after mdadm (LP: #1879980)
- Currently, if an encrypted rootfs is configured on top of a MD RAID1
array
This bug was fixed in the package apport - 2.20.11-0ubuntu47
---
apport (2.20.11-0ubuntu47) groovy; urgency=medium
[ Tiago Stürmer Daitx ]
* apport/ui.py: improve message when origin check fails as it can be
caused by empty apt list - candidate is limited to dpkg and we can't
This bug was fixed in the package apparmor - 3.0.0~beta1-0ubuntu6
---
apparmor (3.0.0~beta1-0ubuntu6) groovy; urgency=medium
* Drop d/p/lp1824812.patch: this patch was only needed with 2.13 and not
3.0. With AppArmor 3, the patch ends up setting SFS_MOUNTPOINT to the
wrong d
This bug was fixed in the package apparmor - 3.0.0~beta1-0ubuntu6
---
apparmor (3.0.0~beta1-0ubuntu6) groovy; urgency=medium
* Drop d/p/lp1824812.patch: this patch was only needed with 2.13 and not
3.0. With AppArmor 3, the patch ends up setting SFS_MOUNTPOINT to the
wrong d
This bug was fixed in the package apport - 2.20.11-0ubuntu47
---
apport (2.20.11-0ubuntu47) groovy; urgency=medium
[ Tiago Stürmer Daitx ]
* apport/ui.py: improve message when origin check fails as it can be
caused by empty apt list - candidate is limited to dpkg and we can't
This bug was fixed in the package apport - 2.20.11-0ubuntu47
---
apport (2.20.11-0ubuntu47) groovy; urgency=medium
[ Tiago Stürmer Daitx ]
* apport/ui.py: improve message when origin check fails as it can be
caused by empty apt list - candidate is limited to dpkg and we can't
This bug was fixed in the package apparmor - 3.0.0~beta1-0ubuntu6
---
apparmor (3.0.0~beta1-0ubuntu6) groovy; urgency=medium
* Drop d/p/lp1824812.patch: this patch was only needed with 2.13 and not
3.0. With AppArmor 3, the patch ends up setting SFS_MOUNTPOINT to the
wrong d
This bug was fixed in the package apparmor - 3.0.0~beta1-0ubuntu6
---
apparmor (3.0.0~beta1-0ubuntu6) groovy; urgency=medium
* Drop d/p/lp1824812.patch: this patch was only needed with 2.13 and not
3.0. With AppArmor 3, the patch ends up setting SFS_MOUNTPOINT to the
wrong d
This bug was fixed in the package apparmor - 3.0.0~beta1-0ubuntu6
---
apparmor (3.0.0~beta1-0ubuntu6) groovy; urgency=medium
* Drop d/p/lp1824812.patch: this patch was only needed with 2.13 and not
3.0. With AppArmor 3, the patch ends up setting SFS_MOUNTPOINT to the
wrong d
This bug was fixed in the package apport - 2.20.11-0ubuntu47
---
apport (2.20.11-0ubuntu47) groovy; urgency=medium
[ Tiago Stürmer Daitx ]
* apport/ui.py: improve message when origin check fails as it can be
caused by empty apt list - candidate is limited to dpkg and we can't
This bug was fixed in the package apparmor - 3.0.0~beta1-0ubuntu6
---
apparmor (3.0.0~beta1-0ubuntu6) groovy; urgency=medium
* Drop d/p/lp1824812.patch: this patch was only needed with 2.13 and not
3.0. With AppArmor 3, the patch ends up setting SFS_MOUNTPOINT to the
wrong d
This bug was fixed in the package apparmor - 3.0.0~beta1-0ubuntu6
---
apparmor (3.0.0~beta1-0ubuntu6) groovy; urgency=medium
* Drop d/p/lp1824812.patch: this patch was only needed with 2.13 and not
3.0. With AppArmor 3, the patch ends up setting SFS_MOUNTPOINT to the
wrong d
Same error occurs with Kubuntu 20.04 & 20.04.01 and Xubuntu 20.04.01 --
this error occurs at 90-91% of the way through the install process.
Suspect it's related to my video card: ASUS NVIDIA STRIX-GTX1050TI-04G-
GAMING graphics card. This card worked perfectly up until last week with
20.04 Xubuntu
Public bug reported:
no hay ningun problema
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.9timbuktu1
ProcVersionSignature: Ubuntu 4.15.0-1028.33-oem 4.15.18
Uname: Linux 4.15.0-1028-oem x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GN
I'll retry the test before we investigate further.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879980
Title:
Fail to boot with LUKS on top of RAID1 if the array is broken/degraded
To manage noti
Ah about this:
> If this isn't used for generating the final packages at all, why do
you propose to make users download an update?
Those files aren't included at all into the package, the README.sources
there was included to explain why we have such files, even though they
are not built.
It's ju
Autopkgtest failure found:
autopkgtest for systemd/246.4-1ubuntu1: amd64: Regression ♻ , arm64:
Pass, armhf: Pass, ppc64el: Pass, s390x: Ignored failure
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-groovy/groovy/amd64/s/systemd/20200922_22
> I don't understand why yaru-theme needs to be updated, either. I see
> that this has been done for yaru-theme once before, but I've found no
> explanation as to why.
I will make it clearer in the top post, but it should be quite easy to
spot looking at the shell's (data subdir) and yaru diffs:
Public bug reported:
please remove the build dependency on python3-venv. It's gone upstream.
** Affects: linux (Ubuntu)
Importance: High
Status: Confirmed
** Affects: linux-aws (Ubuntu)
Importance: High
Status: Confirmed
** Tags: rls-gg-incoming
** Also affects: l
The problem I hit (LP: #1896604) is not a cloud-init bug.
It seems that nobody stumbled on the original issue in the last ~4
years. Lacking activity and a reproducer I'm marking this as Incomplete,
let's see if anybody chimes it claiming it still affects them.
** Changed in: cloud-init (Ubuntu)
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885527
Title:
** Also affects: libreoffice (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884850
Title:
Xorg server uses unacceptably large amounts of memory (
Thank you Kai-Heng Feng - you're awesome.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853277
Title:
Lenovo ThinkBook 14-IML Touchpad not showing up in
/proc/bus/input/devices
To manage notific
@ David
I think pop-os disabled fractional scaling patch, so get in contact with them
please:
https://github.com/pop-os/mutter/commit/bc7c2658e4c873a28afeaf621fb24a1341c6d74c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
I was on kernel version 5.4.0.47-generic and was using the rtl8822be
repo of mid-kid on github. I didn't even need to boot on windoes first
to get wifi working, it was all fine, however when I updated to
5.4.0.48-generic that one stopped working, therefore I tried installing
the kernel above (5.9.0
focal/ussuri verified with [Test Case] and output is:
# apt-cache policy neutron-common
neutron-common:
Installed: 2:16.1.0-0ubuntu2
Candidate: 2:16.1.0-0ubuntu2
Version table:
*** 2:16.1.0-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
** Package changed: ubuntu => ubiquity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896782
Title:
Sound card stops working suddenly
To manage notifications about this bug go to:
https://
The kworker processes are generic in that they can do work for many kernel
parts,
so a particular kworker/number unfortunately doesn't help much to understand the
actual thing that the kworker was doing; we'll need the stack traces for that.
:)
Yes, if and once the issue starts happening again,
Public bug reported:
Greetings,
I am using Ubuntu 16.04.6 LTS as provided by Winsystems for their Vortex83DX3
PC104 board. This is an i686 architecture CPU.
ads@vortex:~/src$ apt-cache policy libxerces-c3.1
libxerces-c3.1:
Installed: (none)
Candidate: 3.1.3+debian-1
Version table:
Public bug reported:
httplib2 0.16 changed how 308 redirects are handled. This broke some
existing python packages that weren't expecting that change when talking
to Google servers that use 308 redirects. Like PyDrive.
= Reproducing =
Reproducing is a little difficult. I'm not entirely sure how,
** Package changed: ubuntu => alsa-driver (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896774
Title:
Headphone output stopped working after perfoming dist-upgrade
To manage notifications
An upload of gnome-shell to bionic-proposed has been rejected from the
upload queue for the following reason: "Fix appears incomplete, and no
progress in a month. Please see
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1838152/comments/5 and subsequent discussion.".
--
You received
An upload of gnome-shell to bionic-proposed has been rejected from the
upload queue for the following reason: "Fix appears incomplete, and no
progress in a month. Please see
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1838152/comments/5 and subsequent discussion.".
--
You received
** Also affects: gnome-shell-extension-appindicator (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal)
Importance: Undecided => High
** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal)
Assignee: (unassig
** Changed in: tracker (Ubuntu Focal)
Importance: Undecided => Low
** Changed in: tracker (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896073
Tit
> Moving from 1.0 to 1.1 spec might cause regressions on packages that
depend on libsejda-java as now el-api (and its implementation) must be
available on the classpath (default on Java EE). At this time the only
package that depends on libsejda-java is pdfsam.
Is it possible that any Ubuntu users
Could you please stop that reassigning game? You are right, it's either
on shared-mime-info or the qt integration, now the result of the
testcase provided is correct on GNOME (see comment 5), it's also correct
on a cloud instance (e.g no desktop integration) so it's only buggy on
KDE, you should ra
** Description changed:
[ Impact ]
Indicators using (big) pixmap icons cause the shell to use a lot of CPU
computation, which interfere with user experience
-
[ Test case ]
- Install mega client from https://mega.nz/sync
- Run it in ubuntu and ensure it doesn't block the UI w
Hello, I have exactly the same issue as the creator of this bug. I have
a Lenovo Legion 5 15ARH05H, model number 82B1000AUS
(https://psref.lenovo.com/Detail/Legion/Lenovo_Legion_5_15ARH05H?M=82B1000AUS),
and my touchpad is listed as MSFT0001:00 04F3:3186, not 04F3:3140.
How can I help add support
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
** Description changed:
AWS RDMA/efa driver: add support for new AWS EFA '0xefa1' devices.
[Impact]
The following 4 mainline commits are required to support the new device
features and ID:
d4f9cb5c5b22 RDMA/efa: Add EFA 0xefa1 PCI ID
a5d87b698547 RDMA/efa: User/kernel compatib
testing with xdgmime [1] (reference implementation of the spec [2] and
also used tests on shared-mine-type):
> ../xdgmime/src/print-mime-data .
test.py:
name: text/x-python
data: application/xhtml+xml
file: application/xhtml+xml
> ../xdgmime/src/test-mime test.py
File "tes
** Changed in: oem-priority
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/1888448
Title:
[MIR] oem-stella.cmit-meowth-meta
To manage notifications about
** Changed in: oem-priority
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/143
Title:
[MIR] oem-stella.cmit-pinsir-meta
To manage notifications about
** Changed in: oem-priority
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/144
Title:
[MIR] oem-stella.cmit-staryu-meta
To manage notifications about
Hey Chris, thanks for the review.
The GNOME maintainers sometime has a somewhat flexible definition of
what is a bugfix indeed.
The command has been added to help migrations from tracker2 to the new
tracker3, it's not strictly something we need in focal but at the same time
it's a new option so
** Changed in: oem-priority
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/145
Title:
[MIR] oem-stella.cmit-eevee-meta
To manage notifications about
The same day after I have reported this problem, kworker stopped consuming CPU.
I am pretty sure it was kworker/5 a problem.
Now I have executed "top" command, typed L and search string kworker and
all of the kworker processes are 0 CPU consumption (see attachment).
I think this problem "vanished
Done! You're welcome!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896717
Title:
[FFE] notcurses 1.7.4 for ubuntu 20.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
This bug was fixed in the package notcurses - 1.7.4+dfsg.1-2
Sponsored for nick black (dankamongmen)
---
notcurses (1.7.4+dfsg.1-2) unstable; urgency=medium
* New upstream version
* Update libnotcurses1.symbols
* Export TERM in CI scripts, fixing salsa CI build
-- Nick Black
Public bug reported:
AWS RDMA/efa driver: add support for new AWS EFA '0xefa1' devices.
[Impact]
The following 4 mainline commits are required to support the new device
features and ID:
d4f9cb5c5b22 RDMA/efa: Add EFA 0xefa1 PCI ID
a5d87b698547 RDMA/efa: User/kernel compatibility handshake mecha
> > dpkg -S /usr/bin/mimetype
> libfile-mimeinfo-perl: /usr/bin/mimetype
how is that supposed to prove it's a shared-mime-info bug?
** Changed in: shared-mime-info (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
In "Focal update: v5.4.62 upstream stable release" (bug #1895174) the
arguments of the trace event writeback_queue_io were changed from 3 to 4
by:
Author: Jan Kara
Date: Fri May 29 16:08:58 2020 +0200
writeback: Fix sync livelock due to b_dirty_time processing
BugLink: https://bug
@Kai, so you use a 'command is provided by a perl utility' as a reason
to reasing to shared-mime-info, what's the logic? also xdg-mime works
fine under GNOME or when using gio that uses shared-mime-info...
** Package changed: shared-mime-info (Ubuntu) => kde-cli-tools (Ubuntu)
--
You received th
CC [M] /var/lib/dkms/lttng-modules/2.11.2/build/probes/lttng-kprobes.o
In file included from
/var/lib/dkms/lttng-modules/2.11.2/build/probes/../probes/define_trace.h:87,
from
/var/lib/dkms/lttng-modules/2.11.2/build/probes/../instrumentation/events/lttng-module/writeback.h:736,
** Also affects: gnome-shell-extension-appindicator (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal)
Importance: Undecided => Low
** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal)
Assignee: (unassign
Here's a build log from my PPA:
https://launchpad.net/~sil2100/+archive/ubuntu/testing/+sourcepub/11592196
/+listing-archive-extra
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896744
Title:
[FFe]
** Tags added: rls-gg-incoming
** Changed in: discount (Ubuntu)
Status: New => Confirmed
** Changed in: discount (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
CC [M] /var/lib/dkms/lttng-modules/2.11.2/build/probes/lttng-kprobes.o
In file included from
/var/lib/dkms/lttng-modules/2.11.2/build/probes/../probes/define_trace.h:87,
from
/var/lib/dkms/lttng-modules/2.11.2/build/probes/../instrumentation/events/lttng-module/writeback.h:736,
** Description changed:
[ Impact ]
GNOME shell when using this indicator should export the
org.kde.StatusNotifierWatcher dbus interface, although some methods and
properties are missing or invalid
-
[ Test case ]
-
Run:
- gdbus call --session --dest org.gnome.Shell --object
This has been fixed in 34-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896785
Title:
Exported DBus interface is missing info or using wrong names
To manage notifications about this bug go to:
h
I can confirm this bug is fixed when I updated mutter to
3.36.1-1ubuntu0.20.04.1. Using NVIDIA Graphics card.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Title:
Shell text with wrong size
** Description changed:
+ SRU Justification:
+ ==
+
+ [Impact]
+
+ * With focal (and even eoan) it is no longer possible to run the
+ updateconfigs Debian build rule (needed in case of kernel option
+ updates) on all supported arhitectures.
+
+ * Changes upstream led to the fact
Public bug reported:
[MIR] discount, libtext-markdown-discount-perl (dependencies of lintian)
** Affects: discount (Ubuntu)
Importance: Undecided
Status: New
** Tags: groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Public bug reported:
Microsoft would like to request a change to the time keeping method in
the Azure images.
We would like to request that an Azure image uses the Azure host for
time sync by default. This will require the use of the Chrony package.
The Chrony package would need to be installed
Finally:
cc -iquote /root/qemu-5.0/b/user-static/linux-user -iquote linux-user -iquote
/root/qemu-5.0/tcg/arm -isystem /root/qemu-5.0/linux-headers -isystem
/root/qemu-5.0/b/user-static/linux-headers -iquote . -iquote /root/qemu-5.0
-iquote /root/qemu-5.0/accel/tcg -iquote /root/qemu-5.0/include
Public bug reported:
[ Impact ]
GNOME shell when using this indicator should export the
org.kde.StatusNotifierWatcher dbus interface, although some methods and
properties are missing or invalid
[ Test case ]
Run:
gdbus call --session --dest org.gnome.Shell --object-path
/StatusNotifierWatch
** Description changed:
- Find the update log attached (dpkg.log)
+ # What happened:
+
+ - Upgraded packages using: sudo apt-get update && sudo apt-get dist-
+ upgrade
+
+ - Following packages were installed:
+ pulseaudio-utils:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14
+ pulseaudio-module-x11:am
** Also affects: tracker (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896073
Title:
SRU the current 2.3.6 stable update
To manage notifi
I am currently preparing updates for this issue, and I just tested the
bionic update that includes this patch, and it works in my environment.
Could you please make sure you created the policy file ok, and have
rebooted after updating packagekit?
--
You received this bug notification because you
** Description changed:
[Availability]
* The package is present in universe and is built for all architectures.
[Rationale]
- * nftables is replacing iptables as the default CLI interface to
- interact with the Netfilter framework and to help that iptables is
- planned to Recommend:
** Attachment added: "Output of lspci -v"
https://bugs.launchpad.net/ubuntu/+bug/1896782/+attachment/5413527/+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/1896782
Title:
Sound c
I got the crash in the repro env.
dmesg holds no OOM which is good - also no other dmesg/journal entry that would
be related.
It might be depending on concurrent execution as this was the primary change to
last time.
And not having set up apport/whoopsie to catch the crash :-/
I've installed the
** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal)
Status: New => In Progress
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal)
Importa
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Title:
Shell text with w
Public bug reported:
Ubuntu 20.04 latest update.
With the latest update the sound goes off all of a sudden. Rebooting helps, but
only for an hour or so. I tried re-installing alsa-base et al. No luck.
PulseAudio Volume Control is not listing my soundcard at all.
I'm using NVIDIA GEForce GTX 16
** Package changed: ubuntu => turnip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907675
Title:
Add support for Ed25519 SSH keys
To manage notifications about this bug go to:
https://bugs.launchpa
Update to mutter 3.36.1-1ubuntu0.20.04.1 in focal/proposed also fixed
the bug for AMD.
Good work, thanks and cheers! :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Title:
Shell text with
Yes this uicheck-sw test in particular is flaky under resource
contention. If I run the test locally, it passes every time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892783
Title:
[SRU] libreof
These files come from RaspberryPi Foundation, who redistributed these
firmware files without a restriction.
They support these blobs, and so do we, to ensure that hw is working
correctly (i.e. bluetooth, wlan, etc).
If and when RaspberryPi releases updates to these blobs, Foundations
team will be
We're also seeing this in kernel builds.
https://launchpadlibrarian.net/498669973/buildlog_ubuntu-groovy-
armhf.linux_5.8.0-20.21_BUILDING.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890435
301 - 400 of 585 matches
Mail list logo
