Thank you for taking the time to file a bug report.
The logs are not very helpful in this case, the only thing I saw was:
[1mdpkg:[0m error processing package libsmbclient:amd64 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting
Thank you for taking the time to file a bug report.
After reading the logs I believe you tried to abort the package
installation in the middle of the process, I can't spot anything besides
that. You also need to be careful when upgrading to MySQL 8, please take
some time to read the upstream
Public bug reported:
This new upstream release contains an important fix to address LP
#1916485. runc now has special handling for seccomp profiles to avoid
making new syscalls unusable for glibc. Backporting this single fix
would be painful because upstream also updated some of the vendorized
Thanks for taking the time to file this bug.
While checking the logs I noticed this:
Mar 4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: Loaded settings
from: /usr/lib/realmd/realmd-defaults.conf /usr/lib/realmd/realmd-distro.conf
Mar 4 01:49:13 precision-3551-c3x-202002-27718
Thank you for taking the time to file a bug report.
I just tried to connect to an iscsi target from my Ubuntu Focal
workstation and I was not able to suspend and then wake up my system, as
both of you described. Your analyses seems right, the iscsi target might
be delaying the whole process.
I
Thank you for taking the time to file a bug report.
>From what you described it seems that Network Manager is the one
responsible for adding the unexpected routing rule, so this might not
affect OpenVPN itself. I quickly tried to reproduce your setup but did
not notice the bug there. Could you
Thanks for the review Robie,
I have tested the package on the proposed pocket by using this script:
#!/bin/sh
set -x
series=trusty
name=$series-upgrade
multipass delete $name
multipass purge
multipass launch $series --name $name
multipass exec $name -- sudo sh -c "cat
Thank you for taking the time to file a bug report.
The attached logs do not help too much, the only info I could extract
was dpkg returning the exit code 10. It seems that something is in an
inconsistent state in your system but I was not able to spot anything
with the provided information.
Thanks for taking the time to file this bug.
I am not able to reproduce this bug since I do not have an scsi device
to test it. I am subscribing Christian, he might have a better idea on
how to address this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thank you for this review Robie, we have now updated the package to only
ship two md5sum. The latest version of 50unattended-upgrades of Trusty
and Xenial.
I have already updated the MR with those changes and I Bryce is
reviewing that changes before uploading the new package.
--
You received
Public bug reported:
ruby-omniauth-remote-user is blocking ruby-defaults/1:2.7+2 migration
because it FTBFS. Related Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959557
I am one of the upstream maintainers and I can confirm this project is
quite dead, unmaintained for many
Also, please provide the userdata that you are using to configure cloud-
init too. I forgot to mention that on my last comment
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917036
Title:
Some of
Hi Kalpesh, thank you for reporting this issue. Can you please provide
the cloud-init logs for the instance that is failing ? Those logs would
be cloud-init.log and cloud-init-output.log
After providing that, you can change the status of this bug to new
again.
** Changed in: cloud-init (Ubuntu)
Thank you for taking the time to file a bug report.
Checking the mailman package in Ubuntu Focal I see the logrotate file
installed by this package contains some postrotate scripts that might be
setting back the ownership to list:list. Take a look at
/etc/logrotate.d/mailman and try to make the
Thank you for taking the time to file a bug report.
I set up a Focal LXD container and installed libsss-nss-idmap0 without
problems in it. I see you tried to install version 2.2.3-3ubuntu0.2, and
now in focal-updates we have 2.2.3-3ubuntu0.4, please try to install
this newer version and check if
I forwarded this bug to the upstream maintainers:
https://github.com/puma/puma/issues/2562
** Bug watch added: github.com/puma/puma/issues #2562
https://github.com/puma/puma/issues/2562
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I tested the attached debdiff in Canonistack VMs (s390x and arm64) and I
got no autopkgtest failure.
** Attachment added: "debdiff"
https://bugs.launchpad.net/ubuntu/+source/puma/+bug/1916954/+attachment/5467252/+files/debdiff
--
You received this bug notification because you are a member
Public bug reported:
The test is hanging on s390x and arm64 architectures only, blocking its
migration and also rails. Below my findings so far.
On s390x the TestPlugin#test_plugin is hanging, not sure why that is
happening exactly but this test is new (not present in the puma version
in
I will further increase this SRU bug with information that is lacking on
from the original bug proposal:
[Impact]
During an upgrade from trusty to xenial, users will be prompted to make a
decision regarding the diff on unattended-upgrades. This is not a good user
experience, specially because
So sad, Asus doesn't care about linux users, that's the reality ... Our
only hope is a community developed driver for this feature.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810183
Title:
Public bug reported:
By default the "transport" field is not set in
/etc/corosync/corosync.conf which means "udp" is used. However, it does
not work in Ubuntu Bionic on Azure for some reason, I thought it could
be some issue regarding multicast but I was told it is supported. In
order to make it
I backported the needed code to support the fence agent to Bionic and
Focal here in this PPA:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/ha-stack-ibm
The idea would be to SRU those patches and release them to Bionic and
Focal, instead of relying only on the PPA with Groovy's full HA
Thank you for taking the time to file a bug report.
I tried to reproduce your bug in a Ubuntu Hirsute container without
success. Moreover, I looked for an upstream bug report about any
incompatibility with glibc 2.33 but found nothing. Could you please
share your postfix config file to help us
Thank you for taking the time to file a bug report.
I tried to reproduce the crash you mentioned and I was not able to do
it. In a brand new Focal environment I was able to install iotop and
call it without any problem.
Since there is not enough information in your report to begin triage or to
Public bug reported:
If I leave the notebook closed for too much time and open it, it will
not wake up and I have to force reboot by pressing power. However if I
simply close and open at the same minute it works.
This kernel fixes the athk11 wifi, it works now but I think it might be
the cause
Public bug reported:
== Begin SRU Template ==
[Impact]
When upgrading from trusty to xenial, we are prompted about config changes on
50unattended-upgrades with the following diff:
--- /etc/apt/apt.conf.d/50unattended-upgrades root.root 0644 2017-05-08 19:21:39
+++
PPA with proposed packages:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/ha-stack-aws
** Description changed:
+ [Impact]
+
+ This update is considered as a hardware enablement feature which will
+ allow AWS users to make use of the IMDSv2 support recently added to
+ resource-agents.
Status: New => In Progress
** Changed in: fence-agents (Ubuntu Focal)
Status: New => In Progress
** Changed in: fence-agents (Ubuntu Groovy)
Status: New => In Progress
** Changed in: fence-agents (Ubuntu Bionic)
Assignee: (unassigned) => Lucas Kanashiro (lucas
onal layer
of defense against network abuses, customers utilizing it may choose to
disable IMDSv1. Disabling IMDSv2 today causes fence_aws to fail.
** Affects: resource-agents (Ubuntu)
Importance: Undecided
Assignee: Lucas Kanashiro (lucaskanashiro)
Status: Fix Released
Public bug reported:
Last year, AWS released "IMDSv2" in an effort to protect customers against some
potentially severe information leaks related to accidentally proxying this
local data to the network. Details
at
Thank you for taking the time to file a bug report.
>From the attached logs I can see this:
package:mysql-server-8.0:8.0.23-0ubuntu0.20.04.1
Setting up mysql-server-8.0 (8.0.23-0ubuntu0.20.04.1) ...
mysqld will log errors to /var/log/mysql/error.log
mysqld is running as pid 4837
Error: Unable to
FWIW here you can find the proposed package targeting Focal for testing:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/pacemaker-sql-
server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1872908 ***
https://bugs.launchpad.net/bugs/1872908
I have the same issue as Alexandre, proceeded with autoupdate and
sudednly my PC stopped recognizing my wifi adapter.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thanks for taking the time to file a bug and trying to make Ubuntu
better.
This is what I found in your logs:
Removing clamav (0.102.4+dfsg-0ubuntu0.20.04.1) ...
Removing clamav-daemon (0.102.4+dfsg-0ubuntu0.20.04.1) ...
Removing clamdscan (0.102.4+dfsg-0ubuntu0.20.04.1) ...
Removing
** Information type changed from Private Security to Private
** Information type changed from Private to Public Security
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Freezes randomly during usage and always after recovering from suspend
mode.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
ApportVersion:
Public bug reported:
Now the binary packages (bundler and ruby-bundler) previously provided
by src:bundler are now provided by src:rubygems. Please remove
src:bundler and its binary package from Hirsute to allow src:rubygems
migration.
** Affects: bundler (Ubuntu)
Importance: Undecided
Right, ruby-puppet-forge migrated to Debian testing yesterday :)
hopefully version 3.0.0-1 will work this out.
I believe we should also remove vagrant-librarian-puppet since it is
reverse dependency of the removed librarian-puppet.
--
You received this bug notification because you are a member
r10k has no reverse dependencies in hirsute:
$ reverse-depends -b -r hirsute r10k
No reverse dependencies found
$ reverse-depends -r hirsute r10k
No reverse dependencies found
librarian-puppet has the following reverse dependency:
$ reverse-depends -b -r hirsute librarian-puppet
Please remove the following source packages and associated binary
packages from hirsute:
* ruby-puppet-forge
* r10k
* librarian-puppet
* vagrant-librarian-puppet
** Summary changed:
- autopkgtest failure is blocking ruby-faraday{,-middleware} in hirsute-proposed
+ [RM] autopkgtest failure is
ruby-puppet-forge has the following reverse dependencies:
$ reverse-depends -b -r hirsute ruby-puppet-forge
Reverse-Build-Depends
* librarian-puppet
* r10k
$ reverse-depends -r hirsute ruby-puppet-forge
Reverse-Depends
* librarian-puppet
* r10k
Packages without architectures listed are
Please remove ruby-diaspora-federation source and binary packages from
hirsute.
** Summary changed:
- autopkgtest failure is blocking ruby-faraday{,-middleware} in hirsute-proposed
+ [RM] autopkgtest failure is blocking ruby-faraday{,-middleware} in
hirsute-proposed
--
You received this bug
Since ruby-diaspora-federation has no reverse dependencies we could
follow Debian to unblock other packages:
$ reverse-depends -r hirsute ruby-diaspora-federation
$ reverse-depends -b -r hirsute ruby-diaspora-federation
No reverse dependencies found
--
You received this bug notification because
FWIW ruby-puppet-forge was removed from Debian testing to allow
migration of ruby-faraday{,-middleware}:
https://tracker.debian.org/news/1224756/ruby-puppet-forge-removed-from-
testing/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FWIW ruby-diaspora-federation was removed from Debian testing to allow
the migration of ruby-faraday{,-middleware}:
https://tracker.debian.org/news/1198071/ruby-diaspora-federation-
removed-from-testing/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks Sergio! I forgot to run update-maintainer indeed :)
I was planning to commit this change in the salsa git repo but the
maintainer is in the middle of an upstream release bump and I did not
want to mix things up until it is done. But I am going to do that once
the package in git is in a
Public bug reported:
The test is failing because upstream does not support yet the newer
versions of faraday and faraday_middleware gems. Test log:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-hirsute/hirsute/amd64/r/ruby-diaspora-
Public bug reported:
The test is failing because upstream does not support yet the newer
versions of faraday and faraday_middleware gems. Test log:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-hirsute/hirsute/amd64/r/ruby-puppet-
Public bug reported:
nanoc/4.11.14-4 is blocked in hirsute-proposed because of an autopkgtest
failure in all architectures. Test log:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-hirsute/hirsute/amd64/n/nanoc/20210104_100140_2ea12@/log.gz
The attached debdiff add a patch to skip this test.
The proposed package is available in this PPA:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/nanoc/+packages
And now it passes in the Ubuntu autopkgtest infrastructure:
Sorry, I forgot to mention the version of the package I used in my Focal
verification work. Here it is:
lucas@vm01:~$ dpkg -l | grep resource-agents
ii resource-agents 1:4.5.0-2ubuntu2.2 amd64 Cluster Resource Agents
** Tags removed: verification-needed verification-needed-bionic
verification
I did the same verification work in a Focal cluster on Azure and
everything worked as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895343
Title:
Microsoft Azure Enablement: azure-lb
The linked Debian bug was already fixed and the new version builds fine
with OCaml >= 4.08.0. Now the DEP-8 test is failing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886992
Title:
FTBFS with
Thanks for taking the time to file this bug and trying to make Ubuntu
better.
Does upstream have any plan to release this feature? Since this is a new
feature (not a bug fix) I am setting the importance to Wishlist, and it
will be included in the Ubuntu development release as soon as upstream
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This sounds like an upstream bug to me. The best route to getting it
fixed in Ubuntu in this case would be to file an bug with the upstream
project. Have you tried to reproduce this bug using a newer rsync
Thanks for taking the time to file this bug and trying to make Ubuntu
better.
The upstream bug you mentioned might be related to what you faced, I am
subscribing Sergio who has been working on samba to check if this is
true. This is the upstream patch targeting 4.11 and it is not included
in
Backporting a new upstream release to a stable release is not usually
what we want (it might introduce new bugs). However, in this case we
have a small patch which can be backported to the current version in
Bionic. This seems to be what we need:
Any news on this driver?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879633
Title:
Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable
To manage notifications about this bug go to:
Thanks Sergio. I am adding the extra header in the patch and I am going
to upload it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912691
Title:
autopkgtest failure blocking runc migration
To
When applying the attached debdiff the test failure is fixed.
** Attachment added: "debdiff"
https://bugs.launchpad.net/ubuntu/+source/opengcs/+bug/1912691/+attachment/5455306/+files/debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
To make sure the package builds fine I uploaded it to this PPA:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/opengcs/+packages
And ran autopkgtest locally:
autopkgtest [17:30:56]: summary
dh-golang-autopkgtest PASS
--
You received this bug notification because
Public bug reported:
opencgs test is failing and blocking runc/1.0.0~rc92-0ubuntu1 from
migrating to hirsute:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-
hirsute/hirsute/amd64/o/opengcs/20210118_162901_84e57@/log.gz
This is the
Updated to the 460 drivers and it works with modeset=1. With modeset=1
and 450, it wasn't working.
I have a Quadro K2000 and a 2080 Super dual gpu, single monitor setup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Could you also confirm if this is happening only in Groovy? I see the
following versions of those two packages in case this is really an
incompatibility issue:
$ rmadison ceph-iscsi
ceph-iscsi | 3.4-0ubuntu2 | focal/universe | source, all
ceph-iscsi | 3.4-0ubuntu2 | groovy/universe | source,
Thanks for taking the time to file this bug and try to make Ubuntu
better.
I subscribed ubuntu-server and Sergio who has been working on this stack
recently to investigate what you described.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I did the verification of the package in proposed and it is working as
expected. I update all the nodes of my Bionic cluster on Azure and the
load balance feature is still working fine:
lucas@vm01:~$ sudo crm status
Stack: corosync
Current DC: vm03 (version 1.1.18-2b07d5c5a9) - partition
Hi SRU team,
I took a look at the 2 "regressions" listed above and it seems that none
of them are originated from this SRU. The pacemaker failure is happening
just in armhf and the same failure can be seen in the previous triggers
for glibc (after some retries it passed for some reason):
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743592
Title:
NGINX fails to start/install/upgrade if IPv6 is completely disabled.
To manage notifications
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743592
Title:
NGINX fails to start/install/upgrade if IPv6 is completely disabled.
To manage notifications about
I verified the test case using the package available in bionic-proposed
and I confirm it is working as expected. I set up a 3 nodes cluster on
AWS to test this.
Note: When installing fence-agents also install the Suggested
dependencies, otherwise the 'fence_aws' command will not work.
Thanks for taking the time to file this bug and try to make Ubuntu
better.
I suppose you are talking about 'tcp-initial-timeout' config option
which the upstream default is 30 seconds (300 * 100 milliseconds). Am I
right? Or are mentioning something else?
FWIW I got this info from upstream doc:
Thank you for taking the time to file a bug report.
I was not able to get many insights from the attached logs due to the
language, but I can see this:
Error: command ['/usr/sbin/apachectl', '-D DUMP_MODULES'] failed with exit code
1: AH00526: Syntax error on line 162 of
Thanks for taking the time to report this bug and try to make Ubuntu
better.
I have checked and this is happening just in Groovy. I am subscribing
ubuntu-server for further investigation.
** Also affects: nss (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: nss (Ubuntu
Thank you gwel! With your message I realized I did not have VirtualBox
installed from the expected source because I installed "virtualbox"
instead of "virtualbox-6.1":
$ apt-cache policy virtualbox
virtualbox:
Installed: 6.1.10-dfsg-1~ubuntu1.20.04.1
Candidate: 6.1.10-dfsg-1~ubuntu1.20.04.1
Public bug reported:
This happened during an "apt dist-upgrade".
Just in case error log is not part of the bug report here it goes:
$ cat /var/lib/dkms/virtualbox/6.1.10/build/make.log
DKMS make.log for virtualbox-6.1.10 for kernel 5.8.0-34-generic (x86_64)
mié 06 ene 2021 12:31:28 -03
make:
I have tested the scenario described in the Test Case section in the bug
description through all the target releases and they all seem good:
# Groovy
ubuntu@docker-groovy:~$ sudo apt install -t groovy-proposed docker.io
Reading package lists... Done
Building dependency tree
Reading state
The autopkgtest regressions reported above were handled. The ubuntu-fan
test failure was fixed after re-triggering it manually, and the
docker.io test in Xenial was indeed failing and I just uploaded version
18.09.7-0ubuntu1~16.04.8 fixing it. With that in place all the tests
should be passing.
Hi @sarthur, I am sorry if you felt ignored, this is not the Ubuntu
community intention. What you described seems to not be supported by
unattended-upgrades, therefore, it'd be a whishlist bug (feature
request) against it. I'd recommend to file this bug against Debian and
discuss it with the
I have tested the scenario described in the Test Case section in the bug
description through all the target releases and they all seem good:
# Groovy
ubuntu@docker-groovy:~$ sudo apt install -t groovy-proposed docker.io
Reading package lists... Done
Building dependency tree
Reading state
The autopkgtest regressions reported above were handled. The ubuntu-fan
test failure was fixed after re-triggering it manually, and the
docker.io test in Xenial was indeed failing and I just uploaded version
18.09.7-0ubuntu1~16.04.8 fixing it. With that in place all the tests
should be passing.
@orgads I filed another bug for the zfs issue you mentioned here:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1910133
>From what I can see this error is reported in Groovy and Hirsute while
configuring the package but it does not break the package installation.
--
You received
Public bug reported:
The postinst script uses the 'zfs mount' command to check mountpoints,
however, the zfs-fuse package is a suggested runtime dependency of
docker.io which might not be available and in this case the following
error will be reported during the package configuration step:
Public bug reported:
Lenovo ideapad 330.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion:
Thank you for taking the time to file a bug report.
I was able to reproduce a similar behavior following the steps you
described. I am going to mark this bug as Triaged ans subscribe our team
to take a look at it any time soon.
** Changed in: sssd (Ubuntu)
Status: New => Triaged
--
You
Thank you for taking the time to file a bug report.
Checking the attached logs the only thing I can see is your 'sh.desktop'
failing many times and some errors from the gnome-shell. I do not think
they are related to the problem you have. Moreover, what you described
does not help a developer to
+1 for the proposed debdiff, straightforward merge.
* Changelog:
- [√] changelog entry correct version and targeted codename
- [√] changelog entries correct
- [√] update-maintainer has been run
* Old Delta:
- [-] dropped changes are ok to be dropped
- [√] nothing else to drop
- [-]
** Description changed:
[Impact]
azure-lb is a handful resources agent if one is maintaining a cluster on
- Azure platform. azure-lb facilitate the operation of a load balancer
+ Azure platform. azure-lb facilitates the operation of a load balancer
implemented by Azure.
In Focal,
As you may have noticed the ruby2.5 tests were fixed on Bionic in
version 2.5.1-1ubuntu1.7 (accepted in Dec 1st). I am wondering if this
is nothing related to the glibc changes because the same tests passed
during the SRU process (you can see the log here [1]), and the test log
above mention
Thank you very mich PoHsu Lin.
Yes, it was related with my free space in the Filesystem partition.
Thanks a million for your great support.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Just installed Ubuntu 20.04 on my brand new XPS 13. Bluetooth is active
and it wont find anything. There is one time where it found "Audio
Device" and "Unknown" but I can't even click, but in majority of times
it wont find anything.
I tried `bluetoothctl` with `power on`,
Public bug reported:
Details of the error after installation. If I restart and the new kernel
tries to get active, it does not boot up and I need to delete it and go
to an old kernel 5.3... to get Linux mint 19.3 cinamon working again
Selecting previously unselected package
** Description changed:
+ [Impact]
+
+ Docker uses containerd under the hood. When containerd is upgraded it
+ stops and restarts its service; docker stops when containerd stops but
+ doesn’t restart. Particularly when doing unattended upgrades, an SRU
+ fix rolled out for containerd can
** Description changed:
+ [Impact]
+
+ Docker uses containerd under the hood. When containerd is upgraded it
+ stops and restarts its service; docker stops when containerd stops but
+ doesn’t restart. Particularly when doing unattended upgrades, an SRU
+ fix rolled out for containerd can
Sorry for the delay. I verified the package in proposed and it works as
expected:
$ multipass launch -n munin-test daily:16.04
$ multipass shell munin-test
# Add xenial-proposed to the sources list
$ sudo apt update && sudo apt upgrade -y
$ sudo apt install munin -y
$ sudo munin-run if_ens4
After checking all the changes needed to backport azure-events to Bionic
I agree with Rafael (comment #4). Let's recommend users wanting to use
azure-events to upgrade to Focal. I am removing azure-events from the
scope of the proposed SRUs.
** Summary changed:
- Microsoft Azure Enablement:
e Releases Update) team member, possible to be consider as HW enablement
within SRU guidelines.
** Changed in: resource-agents (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: resource-agents (Ubuntu Bionic)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
@vicamo, thank you very much for the instructions. I'm on groovy
actually, so that's probably why it didn't work the last time, I didn't
try to install the focal packages. I install the focal packages and
everything seems to be working well.
I already noticed the freeze on start problem is no
Same here. I have a masked jpg in an image, it will neither print as a
pdf nor will it be printed on a physical colour printer. Inkscape 1.0.1
(3bc2e813f5, 2020-09-07)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for taking the time to file a bug report.
Checking the attached logs I found this:
2020-11-30T17:51:13.420162Z 0 [ERROR] [MY-67] [Server] unknown variable
'query_cache_limit=1M'.
2020-11-30T17:51:13.420930Z 0 [ERROR] [MY-010119] [Server] Aborting
>From
I'm sorry for my inexperience. I have a XPS with the AX500 board, could
you provide some instructions for me to test it, @vicamo?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879633
Title:
Killer
901 - 1000 of 3436 matches
Mail list logo
