[Bug 1949575] Re: Upgrade to 0.104 to at least fix memory leak in clamdscan
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 memory leak in clamdscan To manage notifications about this bug go to: https://bugs.launchpad.net/clamav/+bug/1949575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949575] Re: Upgrade to 0.104 to at least fix memory leak in clamdscan
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 clamdscan To manage notifications about this bug go to: https://bugs.launchpad.net/clamav/+bug/1949575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949575] Re: Upgrade to 0.104 to at least fix memory leak in clamdscan
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 + https://discord.com/channels/63602074370595/636275790660501523/857472324148265021 + + Fix: + https://github.com/Cisco-Talos/clamav/pull/181 -- 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 clamdscan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1949575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949575] Re: Upgrade to 0.104 to at least fix memory leak in clamdscan
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949575 Title: Upgrade to 0.104 to at least fix memory leak in clamdscan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1949575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949575] [NEW] Upgrade to 0.104 to at least fix memory leak in clamdscan
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: upgrade-software-version -- 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 clamdscan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1949575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868109] Re: block probing fails with KeyError MAJOR
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 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: https://bugs.launchpad.net/curtin/+bug/1868109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868109] Re: block probing fails with KeyError MAJOR
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. -- 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: https://bugs.launchpad.net/curtin/+bug/1868109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868109] Re: block probing fails with KeyError MAJOR
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: https://bugs.launchpad.net/curtin/+bug/1868109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868109] Re: block probing fails with KeyError MAJOR
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: https://bugs.launchpad.net/curtin/+bug/1868109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868109] Re: block probing fails with KeyError MAJOR
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 probing fails with KeyError MAJOR To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1868109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868109] Re: block probing fails with KeyError MAJOR
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. https://bugs.launchpad.net/bugs/1868109 Title: block probing fails with KeyError MAJOR To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1868109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868109] Re: block probing fails with KeyError MAJOR
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: Traceback (most recent call last): File "/snap/subiquity/1999/lib/python3.6/site-packages/curtin/commands/main.py", line 202, in main ret = args.func(args) File "/snap/subiquity/1999/lib/python3.6/site-packages/curtin/commands/curthooks.py", line 1638, in curthooks builtin_curthooks(cfg, target, state) File "/snap/subiquity/1999/lib/python3.6/site-packages/curtin/commands/curthooks.py", line 1604, in builtin_curthooks setup_grub(cfg, target, osfamily=osfamily) File "/snap/subiquity/1999/lib/python3.6/site-packages/curtin/commands/curthooks.py", line 627, in setup_grub join_stdout_err + args + instdevs, env=env, capture=True) File "/snap/subiquity/1999/lib/python3.6/site-packages/curtin/util.py", line 275, in subp return _subp(*args, **kwargs) File "/snap/subiquity/1999/lib/python3.6/site-packages/curtin/util.py", line 141, in _subp cmd=args) curtin.util.ProcessExecutionError: Unexpected error while running command. The install fail is attached. Thank you for your commitment and patience, Michael! ** Attachment added: "1586336110.222144365.install_fail.crash" https://bugs.launchpad.net/subiquity/+bug/1868109/+attachment/5349400/+files/1586336110.222144365.install_fail.crash -- 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: https://bugs.launchpad.net/subiquity/+bug/1868109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868109] Re: block probing fails with KeyError MAJOR
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" https://bugs.launchpad.net/subiquity/+bug/1868109/+attachment/5348624/+files/subiquity-error.tar.xz -- 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: https://bugs.launchpad.net/subiquity/+bug/1868109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868109] Re: block probing fails with KeyError MAJOR
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 this bug go to: https://bugs.launchpad.net/subiquity/+bug/1868109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868109] Re: block probing fails with KeyError MAJOR
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: block probing fails with KeyError MAJOR To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1868109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868109] Re: Subiquity on Focal Live Server (current daily-live) crashes on block probe
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868109 Title: Subiquity on Focal Live Server (current daily-live) crashes on block probe To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1868109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868109] Re: Subiquity on Focal Live Server (current daily-live) crashes on block probe
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), transferring it onto the Samsung PM1725b 3.2TB PCIe 3.0x8 (AIC), renders a usable system. -- 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: Subiquity on Focal Live Server (current daily-live) crashes on block probe To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1868109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868109] Re: Subiquity on Focal Live Server (current daily-live) crashes on block probe
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868109 Title: Subiquity on Focal Live Server (current daily-live) crashes on block probe To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1868109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868109] Re: Subiquity on Focal Live Server (current daily-live) crashes on block probe
@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. https://bugs.launchpad.net/bugs/1868109 Title: Subiquity on Focal Live Server (current daily-live) crashes on block probe To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1868109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868109] [NEW] Subiquity on Focal Live Server (current daily-live) crashes on block probe
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 as virtual device. Expected Result: Subiquity would list the NVMe(SSD) that is residing in the first PCIe Slot of the Mainboard. Continuation of installation. Current Result: Crash of installation process, no listing of block devices. See attached screencast. Additional Information: Hardware Specs: Mainboard: Supermicro X11DPi-NT CPUs: 2 * Intel Xeon Gold 6226 SSD: Samsung PM1725b 3.2TB PCIe 3.0x8 (AIC) Installation log was sent via reporting functionality of subiquity. ** Affects: subiquity Importance: Undecided Status: New ** Affects: ubuntu Importance: Undecided Status: New ** Tags: pm1725b samsung supermicro x11dpi-nt ** Attachment added: "Screencast_2020-03-19_14:22:19.mp4" https://bugs.launchpad.net/bugs/1868109/+attachment/5338809/+files/Screencast_2020-03-19_14%3A22%3A19.mp4 ** Description changed: - We were unable to install Ubuntu Focal Live Server via subiquiti in the daily-live iso from 17.02.2020. + We were unable to install Ubuntu Focal Live Server via subiquity in the daily-live iso from 17.02.2020. Reason appears to be a failiure in the block device probing section. ISO was loaded via IPMI as virtual device. Expected Result: Subiquity would list the NVMe(SSD) that is residing in the first PCIe Slot of the Mainboard. Continuation of installation. Current Result: Crash of installation process, no listing of block devices. See attached screencast. + Additional Information: + Hardware Specs: + Mainboard: Supermicro X11DPi-NT + CPUs: 2 * Intel Xeon Gold 6226 + SSD: Samsung PM1725b 3.2TB PCIe 3.0x8 (AIC) - Additional Information: - Hardware Specs: -Mainboard: Supermicro X11DPi-NT -CPUs: 2 * Intel Xeon Gold 6226 -SSD: Samsung PM1725b 3.2TB PCIe 3.0x8 (AIC) - - Installation log was sent via reporting functionality of subiquity. + Installation log was sent via reporting functionality of subiquity. ** Description changed: - We were unable to install Ubuntu Focal Live Server via subiquity in the daily-live iso from 17.02.2020. + We were unable to install Ubuntu Focal Live Server via subiquity in the daily-live iso from 17.03.2020. Reason appears to be a failiure in the block device probing section. ISO was loaded via IPMI as virtual device. Expected Result: Subiquity would list the NVMe(SSD) that is residing in the first PCIe Slot of the Mainboard. Continuation of installation. Current Result: Crash of installation process, no listing of block devices. See attached screencast. Additional Information: Hardware Specs: Mainboard: Supermicro X11DPi-NT CPUs: 2 * Intel Xeon Gold 6226 SSD: Samsung PM1725b 3.2TB PCIe 3.0x8 (AIC) Installation log was sent via reporting functionality of subiquity. ** Description changed: - We were unable to install Ubuntu Focal Live Server via subiquity in the daily-live iso from 17.03.2020. + 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 as virtual device. Expected Result: Subiquity would list the NVMe(SSD) that is residing in the first PCIe Slot of the Mainboard. Continuation of installation. Current Result: Crash of installation process, no listing of block devices. See attached screencast. Additional Information: Hardware Specs: Mainboard: Supermicro X11DPi-NT CPUs: 2 * Intel Xeon Gold 6226 SSD: Samsung PM1725b 3.2TB PCIe 3.0x8 (AIC) Installation log was sent via reporting functionality of subiquity. ** Also affects: 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/1868109 Title: Subiquity on Focal Live Server (current daily-live) crashes on block probe To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1868109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 477510] Re: Broken paths in startup script and config file
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 config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavis-stats/+bug/477510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
