0.103.5 is now distributed, containing the memleak fix above.
Basically this issue can be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949575
Title:
Upgrade to 0.104 to at least fix
Looks like it was backported to 0.103.4 https://github.com/Cisco-
Talos/clamav/pull/203
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949575
Title:
Upgrade to 0.104 to at least fix memory leak in
updated desc
** Description changed:
clamav 0.104 is released.
Containing a fix for a bigger memleak of clamdscan.
https://github.com/Cisco-Talos/clamav/commit/8fd1c66d9954aaed5019fafdcfd170b98882a2fe
+
+ Bug characteristic with massif (valgrind) confirmation
+
** Description changed:
clamav 0.104 is released.
Containing a fix for a bigger memleak of clamdscan.
+
https://github.com/Cisco-Talos/clamav/commit/8fd1c66d9954aaed5019fafdcfd170b98882a2fe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
clamav 0.104 is released.
Containing a fix for a bigger memleak of clamdscan.
https://github.com/Cisco-Talos/clamav/commit/8fd1c66d9954aaed5019fafdcfd170b98882a2fe
** Affects: clamav (Ubuntu)
Importance: Undecided
Status: New
** Tags:
Mainboard firmware update worked. Installable and bootable in both
legacy and uefi mode.
** Changed in: subiquity
Status: New => Fix Released
** Changed in: subiquity (Ubuntu)
Status: New => Fix Released
** Changed in: curtin
Status: Fix Committed => Fix Released
--
You
Sorry for the delay. Installation continues and finishes in UEFI mode.
Now we ran into boot issues (SSD is the same model, but mainboard
isn't), but those are unlikely Software related (seems like an AHCI
Driver bug in the mainboard firmware) - so we can't confirm that the
installed OS boots.
--
So this issue can be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109
Title:
block probing fails with KeyError MAJOR
To manage notifications about this bug go to:
We'll try next week. Then i've physical access
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109
Title:
block probing fails with KeyError MAJOR
To manage notifications about this bug go to:
As soon those patches are in the daily live iso - we would like to test
again. Please send us a notice, so we can report back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109
Title:
block
After you mentioned UEFI, we are now able to install in bios legacy mode.
ヽ(•‿•)ノ
We still have a second system, that can be used to test the latest ISO on UEFI
mode
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well that worked for the block probing step :)
The device is now selectable and the installation process begins. :+1:
But the patched curtin (from your paste) seems to trip on a next error
during install:
Tags: focal uec-images
Title: install failed crashed with CalledProcessError
Traceback:
My colleague manually patched probert in the subiquity snap (fictional
snap revision 1999 based on 1626 and your PR above) and we get a
different stacktrace now.
** Attachment added: "probert patch applied"
Even if my last comment was sent on April 1st - it was no joke :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109
Title:
block probing fails with KeyError MAJOR
To manage notifications about
Hi Michael,
would it help to grant you SSH access into the installation session
(daily-live current iso) on that machine?
Regards
Malte
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868109
Title:
I'll attach just everything of /var/crash ;)
(Daily-live current ISO from yesterday and switch to subiquity snap edge
channel)
** Attachment added: "var_crash.tar.xz"
https://bugs.launchpad.net/subiquity/+bug/1868109/+attachment/5342062/+files/var_crash.tar.xz
--
You received this bug
The installation was tried with the Ubuntu Focal Live Server (daily-live
current) from 26.03.2020
(SHA256SUM b5a94bedc6833f2fabc4cda091cdcb8f5b8b5633ece68740145cedf6ec89b137)
On a sidenote: Installing on a desktop system, cloning the disk (in this
case a Samsung 970 EVO NVMe M.2 SSD),
Tried subiquity in the edge channel - no change in the installation process in
this regard.
The block probe still fails. The report was send via subiquity reporting
functionality 1585241307.605162859.block_probe_...
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@mwhudson : do you have any commands I should execute to confirm this?
Or is the Fix Committed Status not equal to "it will be on the next daily live
disc"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
We were unable to install Ubuntu Focal Live Server via subiquity in the
daily-live iso from 17.03.2020 (SHA256SUM
341d2990bab8d28a02414743eb45d74bb90771a8cc34ca0a792293cbbedfcecf).
Reason appears to be a failiure in the block device probing section.
ISO was loaded via IPMI
I've looked at the code closer, and make it run as a cron is definitely
wrong. Should be a service.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/477510
Title:
Broken paths in startup script and
21 matches
Mail list logo
