[Bug 2076395] Re: flash-kernel is not using new kernel with a version string that has more than two "-"
There are some tests for include_only_flavors in test_functions:test_include_only_flavors(); these can be run with FK_CHECKOUT=. ./test_functions Actually these tests use versions with 1, 2 and 3 dashes such as 5.15.0-1023, 5.15.0-1023-generic, 5.15.0-1023-raspi-nolpae. Would you mind adding a test case for your exact combination along with the fix? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076395 Title: flash-kernel is not using new kernel with a version string that has more than two "-" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2076395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069860] Re: [needs-packaging] cmocka-extensions
** Changed in: ubuntu Status: Incomplete => 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/2069860 Title: [needs-packaging] cmocka-extensions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2069860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069860] Re: [needs-packaging] cmocka-extensions
I'll respond at least for the version part since I chose the current changelog setup We've started cmocka-extensions from debian/ packaging created upstream (by an ex-Canonical employee :-), so the copyright is to them, but I guess we should now extend it to Canonical since we've developed some changes. This is also why there is a history of previous changelog entries that I preserved for clarity to the packagers who worked upstream and on the Ubuntu version of the package. I'm ok with dropping the previous changelog entries if you think they could break some tools. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069860 Title: [needs-packaging] cmocka-extensions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2069860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070070] Re: Support for Ubuntu Core tegra-igx images in jammy
I also booted the resulting Core image on a Jetson AGX Orin, I had to try a couple of times, not sure why, perhaps quirks with the BIOS and me trying to boot from a SD card reader, but eventually I got the installer prompt from Ubuntu Core, albeit I didn't manage to progress it, I think it demonstrates a good starting point for the image – might still have to address the kernel/userspace etc. Ubuntu Core Configure the network and setup an administrator account on this all-snap Ubuntu Core system. ** Tags removed: verification-needed ** Tags added: verification-done ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070070 Title: Support for Ubuntu Core tegra-igx images in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2070070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070070] Re: Support for Ubuntu Core tegra-igx images in jammy
Installed https://launchpad.net/ubuntu/+source/livecd-rootfs/2.765.44/+build/28611104/+files/livecd-rootfs_2.765.44_arm64.deb in a jammy arm64 LXD container and ran commands from the Test plan: ubuntu@jammy:~/build$ rm -rf auto local config rm -f livecd.*.model-assertion mkdir -p auto for s in config build clean; do ln -s /usr/share/livecd-rootfs/live-build/auto/$s auto/; done lb clean --purge export PROJECT=ubuntu-core ARCH=arm64 SUBARCH=tegra-igx SUITE=jammy IMAGEFORMAT=ubuntu-image CHANNEL=edge lb config sudo -E lb build [2024-06-28 13:46:32] lb_clean --purge P: Executing auto/clean script. [2024-06-28 13:46:32] lb_clean noauto --purge P: Executing auto/clean script. [2024-06-28 13:46:32] lb_clean noauto --all P: Cleaning chroot P: Executing auto/clean script. [2024-06-28 13:46:32] lb_clean noauto --cache [2024-06-28 13:46:32] lb_config P: Executing auto/config script. Building on jammy.lxd Configured ubuntu-image for the following model assertion: type: model authority-id: canonical series: 16 brand-id: canonical model: ubuntu-core-22-tegra-igx-edge architecture: arm64 base: core22 grade: signed snaps: - default-channel: 22-igx/edge id: 9pjCtYlNoT9Fx6RiHMhhBoIG6ZYXBvJc name: tegra type: gadget - default-channel: 22-igx/edge id: Rjyoy6Zhe9mlkBQqmVzaUdPB2TblFSwV name: tegra-kernel type: kernel - default-channel: latest/edge id: amcUKQILKXHHTlmSa7NMdnXSx02dNeeT name: core22 type: base - default-channel: latest/edge id: PMrrV4ml8uWuEUDBT8dSGnKUYbevVhc4 name: snapd type: snapd timestamp: 2024-04-23T15:12:16+00:00 sign-key-sha3-384: 9tydnLa6MTJ-jaQTFUXEwHl1yRx7ZS4K5cyFDhYDcPzhS7uyEkDxdUjg9g08BtNn AcLBXAQAAQoABgUCZipp6AAKCRDgT5vottzAEj6mD/9lINl13Ju5yVBySIxByJVzJ84nxFlpFLAh Bnb+7cNLAIWKLB57oG49oYx5aXpGaH3RNoQ9rGI/r7axRDgqpYStA0tFO0NM04sBWi4tkc2Cj+xj v/uX//p+Xwx9IcynnvPG2aavfebA3tzBN3AV+QTjgo4rHhIJNiNNx8Qs7FHYTvFuZh6tYHbMX7wd N0kE8axVCm8ado+vIbBmkzqE5EYoYtoer4DO90WqkmnGq07w+6Uth5AfUoXQfegl37xeXigAnhGO sKos/FDw/G7IcAzp24VI4HmCnCj7W0I6iKmuEUr6JiXZoD7eEXr/CNMQpeeO/HD2vXnAmBF3V8W/ 9brjFI5wTjHkxgMwzZ3z4RtqpG8Vx1Udcn6w2+cUzB3j5afJlg5mZAuE60StY38AVByaU4+PTSGv nVP5ZQHiFQzz23VWmc5/blVDHYuvYikXUjbTBWfFszAby/UJIPvfS+dTTRNz0+cIa0qgkCsDma6B qRDpepOXDw97mu1LwDH+SvLQM2Cnaa+tcO7cjslPiQq+MOjCVAgvOtZFi12lgpqJmwDiX8x4r3MZ /fu7DO+zfPzjmujhr8p/skjRUmAu1OOwe8lrUzvfKBjm0j+hY02o8mV2NkkqxItnqQ3tyyUwyxlW wXXWWlvCds7QJgP34C6m0CIhfwV8E2r/gaVvbkjv/Q== -- [2024-06-28 13:46:32] lb_build P: Executing auto/build script. WARNING: proceeding to download snaps ignoring validations, this default will change in the future. For now use --validation=enforce for validations to be taken into account, pass instead --validation=ignore to preserve current behavior going forward Fetching snapd Fetching tegra-kernel Fetching core22 Fetching tegra Worked fine, model assertion is correct and manifest is as expected: ubuntu@jammy:~/build$ ls auto config livecd.ubuntu-core-tegra-igx.img.xz livecd.ubuntu-core-tegra-igx.manifest livecd.ubuntu-core-tegra-igx.model-assertion output ubuntu@jammy:~/build$ cat livecd.ubuntu-core-tegra-igx.manifest core22 1522.snap snapd 22283.snap tegra-kernel 3.snap tegra 1.snap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070070 Title: Support for Ubuntu Core tegra-igx images in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2070070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069860] Re: [needs-packaging] cmocka-extensions
** Tags added: needs-packaging pe-archive-admin-request -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069860 Title: [needs-packaging] cmocka-extensions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2069860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2042849] Re: [needs-packaging] xlnx-platformstats package from Xilinx
Removing sponsoring tag as this is in NEW ** Tags removed: pe-sponsoring-request ** Tags added: pe-archive-admin-request -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2042849 Title: [needs-packaging] xlnx-platformstats package from Xilinx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2042849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2034648] Re: [needs-packaging] optee-os-s32
Hey, I'm removing the pe-sponsoring-request tag as this is taking a bit longer, feel free to readd and/or ping me when another review is needed :) ** Tags removed: pe-sponsoring-request -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2034648 Title: [needs-packaging] optee-os-s32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2034648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069875] Re: [needs-packaging] cmocka-mocks
Package ready for sponsoring review at https://launchpad.net/~nemos- team/+archive/ubuntu/archive-target/+sourcepub/16241780/+listing- archive-extra ** Tags added: needs-packaging ** Tags added: pe-sponsoring-request -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069875 Title: [needs-packaging] cmocka-mocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2069875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048228] Re: [needs-packaging] xmutil from Xilinx
This has been stalled for some time, let's drop the pe-sponsoring- request tag and re-add it when ready ** Tags removed: pe-sponsoring-request -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048228 Title: [needs-packaging] xmutil from Xilinx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2048228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069860] Re: [needs-packaging] cmocka-extensions
Hey Steve, Thanks for the feedback, just trying to pick a number that is higher than any previously used revisions, as Emlix is building their own debs using a Debian versioning scheme. Happy to reupload as -0ubuntu1, ignoring the Emlix versions entirely if you think that's a better strategy. (We'll pass feedback to Emlix about not using Debian revisions.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069860 Title: [needs-packaging] cmocka-extensions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2069860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070070] Re: Support for Ubuntu Core tegra-igx images in jammy
Uploaded 2.765.44, now in Unapproved https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=livecd- rootfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070070 Title: Support for Ubuntu Core tegra-igx images in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2070070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070070] Re: Support for Ubuntu Core tegra-igx images in jammy
** Merge proposal linked: https://code.launchpad.net/~rmartin013/livecd-rootfs/+git/livecd-rootfs/+merge/466187 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070070 Title: Support for Ubuntu Core tegra-igx images in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2070070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070070] [NEW] Support for Ubuntu Core tegra-igx images in jammy
Public bug reported: This bug is to track changes needed to be able to build jammy Ubuntu Core images for arm64+tegra-igx to support hardware based on NVIDIA Tegra SoCs. NB some initial support had already been backported; see LP #2015644. [ Impact ] * This allows building missing image flavors for the NVIDIA Tegra families of hardware, notably Ubuntu Core images for the tegra-igx subarch. * This should also allow building of classic ISO installer images for tegra-igx, albeit that's a lesser priority. [ Test Plan ] * Changes to livecd-rootfs were tested locally and can be tested from the -proposed package by building a Core image for tegra-igx as follows: sudo apt install livecd-rootfs mkdir build cd build rm -rf auto local config rm -f livecd.*.model-assertion mkdir -p auto for s in config build clean; do ln -s /usr/share/livecd-rootfs/live-build/auto/$s auto/; done lb clean --purge export PROJECT=ubuntu-core ARCH=arm64 SUBARCH=tegra-igx SUITE=jammy IMAGEFORMAT=ubuntu-image CHANNEL=edge lb config sudo -E lb build [ Where problems could occur ] * Changes are relatively light, but in the case of a regression for instance due to broken logic, this could break existing image builds, in which case an older livecd-rootfs could be reuploaded. [ Other Info ] * These images are still being developed and its possible further changes are needed as we iterate through the maturity of the image. ** Affects: livecd-rootfs (Ubuntu) Importance: Medium Status: Fix Released ** Affects: livecd-rootfs (Ubuntu Jammy) Importance: Medium Status: In Progress ** Also affects: livecd-rootfs (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released ** Changed in: livecd-rootfs (Ubuntu) Importance: Undecided => Medium ** Changed in: livecd-rootfs (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: livecd-rootfs (Ubuntu Jammy) 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/2070070 Title: Support for Ubuntu Core tegra-igx images in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2070070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069802] Re: [SRU] flash-kernel to support xilinx kria platforms with noble kernel
Word of warning, this is a complex topic! So as you know, flash-kernel gets triggered quite often: when the kernel gets updated, when packages participating in the contents of the initramfs get updated (initramfs-tools, packages shipping modules), it should probably also run when f-k gets updated but I think it doesn't right now. This happens through hooks in other packages when they are doing certain things (kernel post-installation runparts, initramfs post- generation runparts), and/or dpkg triggers, and/or regular package maintainer scripts. I /think/ Breaks should do the right thing in preventing most of these runs until the new files are in place. In general, the risks you're trying to manage: - system is unbootable after attempting an upgrade - system can't complete its upgrade and requires admin intervention - windows of time where the system would be unbootable if we pulled the cord One thing I'm worried about when I see kernel-flavor checks is that a "strict" f-k flavor check kicks in while in the middle of upgrading between flavors, resulting in the upgrade being aborted and/or leaving the system in an unbootable state. This could either be the old f-k being triggered with the new flavor, or it could also be the new f-k being triggered while the old flavor is still there. I think it's easy to kill the second case by listing both flavors in new f-k There are other things that can happen: both old and new flavors being on disk, and f-k being called to install the wrong, old one (I haven't looked at how the two would get sorted; would the highest version win, or would the name be preponderant?). In general with updates and upgrades, you can assume: - system might be updating from older packages in one series to newer packages in the same series - system might be upgrading from one series to the next, or for one LTS to the next, but a) latest updates must be installed before upgrading, b) can't jump a series or jump an LTS in an upgrade - system might be half-updated or half-upgraded and lose power, ideally we want this system to still boot and later continue with the update/upgrade - you can only count on enforcing the order of updates/upgrades through versioned dependencies such as depends/breaks/conflicts All of these scenarios are already quite hairy; let's say we have managed all of these perfectly in our packaging. We might also want to do backports: - backport a new kernel to an older Ubuntu (not sure we're planning this), but perhaps the f-k in that older Ubuntu doesn't support that flavor - backport a new f-k to an older Ubuntu (I think this is rare, but might be needed when you want to support a new flavor in an older and the f-k version in the older series didn't support it) but perhaps the new f-k is not ready to support the old kernel flavor The hardest stretch in backwards compat is when we are backporting a version of a package from one LTS to the previous LTS, then this package might be around from old LTS to next LTS, spanning 2 LTSes. You can probably ignore the backports scenarios for this work, just wanted to share them for completeness. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069802 Title: [SRU] flash-kernel to support xilinx kria platforms with noble kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2069802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069802] Re: [SRU] flash-kernel to support xilinx kria platforms with noble kernel
Alternatively, you can add a versioned conflict on f-k in the kernel package (Breaks << versions of f-k prior to the change) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069802 Title: [SRU] flash-kernel to support xilinx kria platforms with noble kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2069802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069802] Re: [SRU] flash-kernel to support xilinx kria platforms with noble kernel
I'm not sure if f-k supports having multiple device tree options; you probably also can't have multiple entries for the same machine but different kernels/device trees. My recommendation would be to add both transitional packages for upgrades, and provide the old device tree name in the new kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069802 Title: [SRU] flash-kernel to support xilinx kria platforms with noble kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2069802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069802] Re: [SRU] flash-kernel to support xilinx kria platforms with noble kernel
For the CMA change, I guess it's easy enough to release note this in oracular, but I'm less clear on noble: are we going to reroll existing images with the change? How will we communicate on the differences between old and new images with larger and smaller CMA? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069802 Title: [SRU] flash-kernel to support xilinx kria platforms with noble kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2069802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069802] Re: [SRU] flash-kernel to support xilinx kria platforms with noble kernel
Actually, sorry, I see that your other change on device tree names might require the new kernel flavor; are the new and old device tree names available in both old and new kernel? How do we ensure people don't upgrade to a broken combination? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069802 Title: [SRU] flash-kernel to support xilinx kria platforms with noble kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2069802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069802] Re: [SRU] flash-kernel to support xilinx kria platforms with noble kernel
Hi Talha, This is subjective, but I would suggest not dropping the xilinx-zynqmp flavor from the list immediately for two reasons: - might be useful across upgrades (e.g. I upgrade f-k but not the kernel) - in the case of a backport of f-k The f-k kernel flavors are an useful protection in the face of trying to run the raspi kernel on a xilinx platform, but I don't know if we'd gain much by enforcing the removal of the old kernel flavor name. We could drop it after the next LTS though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069802 Title: [SRU] flash-kernel to support xilinx kria platforms with noble kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2069802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2042849] Re: [needs-packaging] xlnx-platformstats package from Xilinx
** Changed in: ubuntu Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2042849 Title: [needs-packaging] xlnx-platformstats package from Xilinx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2042849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2042849] Re: [needs-packaging] xlnx-platformstats package from Xilinx
(I went ahead and uploaded this version after fixing copyright file.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2042849 Title: [needs-packaging] xlnx-platformstats package from Xilinx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2042849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2042849] Re: [needs-packaging] xlnx-platformstats package from Xilinx
Hi Talha, Did another pass on this, and I only spotted one area that should be easy to fix: debian/copyright says GPL-3+ for debian/, but license grant snippet says exactly version 3 is offered: License: GPL-3+ This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License version 3, as published by the Free Software Foundation. it also refers to the Lesser GPL for some reason "See the applicable version of the GNU Lesser General Public License for more details." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2042849 Title: [needs-packaging] xlnx-platformstats package from Xilinx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2042849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2034648] Re: [needs-packaging] optee-os-s32
I'm starting to take a look at optee-os-s32 (optee-
os-s32_3.18-bsp37.0-0ubuntu1~ppa4.dsc) towards sponsoring it.
0) I think it's worth stating why we want the package. optee-os provides
the "secure world" side of the OPTEE TEE implementation, which is
typically loaded very early in the boot process of Arm platforms such as
the NXP S32x family, and could be needed as part of the boot process.
NXP has forked from https://github.com/OP-TEE/optee_os/ to add support
for their S32x platform. Separately, NXP's OPTEE implementation can
optionally be built with support for NXP's discrete security component
called "HSE". We would like to add this package to Ubuntu as for its
binaries to be included in to-be-created Ubuntu images for S32x
platforms. These images would initially be without HSE support as it
currently depends on a proprietary non-redistributable NXP firmware.
1) First, I thought we had a copy of optee_os in Debian/Ubuntu for some time
already, but actually we only had optee_client (Source: optee-client) –
until... oracular since we just imported optee-os_4.2.0-3.dsc from Debian. It
was failing to build, I've just uploaded a build fix.
optee-os and optee-os-s32 probably have disjoint development history, but it
would be in our interest to keep these close as to find some similarities when
we address one issue in one to carry the fix in the other. Unfortunately, these
are quite far apart in terms of upstream versions. I'm not sure how much there
is to align on between the two packages, but at least the way the build is
called is slightly different since optee-os was failing to build due to taking
Ubuntu's LDFLAGS while optee-os-s32 builds and seems not pass LDFLAGS through.
It's not exactly a run of the mill shared ELF file to start with, but it might
be worth comparing the ways both are built. I think we should at least try to
align package names/splits and list of files as to imagine a world where S32x
support for upstream, and optee-os can build a flavor for S32x (much like the
u-boot package).
optee-os provides subdirs under usr/lib/optee for each target platform:
/usr/lib/optee/k3-am62x/tee-raw.bin
/usr/lib/optee/vexpress-qemu_armv8a/tee-header_v2.bin
/usr/lib/optee/vexpress-qemu_armv8a/tee-pageable_v2.bin
/usr/lib/optee/vexpress-qemu_armv8a/tee-pager_v2.bin
/usr/lib/optee/vexpress-qemu_armv8a-virtualized/tee-header_v2.bin
/usr/lib/optee/vexpress-qemu_armv8a-virtualized/tee-pageable_v2.bin
/usr/lib/optee/vexpress-qemu_armv8a-virtualized/tee-pager_v2.bin
while optee-os-dev provides a bunch of development files suc as headers,
pre-built binaries, assembly files and makefiles. These are also under platform
specific directories:
/usr/lib/optee-os-dev/PLATFORM/host_include/**/*.{h,ta,a,S}
/usr/lib/optee-os-dev/PLATFORM/host_include/conf.{mk,.h,cmake}
/usr/lib/optee-os-dev/PLATFORM/include/**/*.h
/usr/lib/optee-os-dev/PLATFORM/mk/*.mk
/usr/lib/optee-os-dev/PLATFORM/scripts/*.py
/usr/lib/optee-os-dev/PLATFORM/src/*.{S,c}
/usr/lib/optee-os-dev/PLATFORM/ta/*.ta
where PLATFORM is in arm-plat-k3, vexpress-qemu_armv8a,
vexpress-qemu_armv8a-virtualized. (I didn't attempt diffing the headers)
The optee-os-s32 deb follows a similar layout as optee-os:
/usr/lib/optee-os-s32/s32g2/tee-header_v2.bin
/usr/lib/optee-os-s32/s32g2/tee-pager_v2.bin
(not sure why no tee-pageable_v2, I don't know what it does)
while optee-os-s32-dev install similar headers as optee-os-dev but under a
slightly different pathes
/usr/share/optee-os-s32/export-ta_arm64/host_include/
/usr/share/optee-os-s32/export-ta_arm64/include/
/usr/share/optee-os-s32/export-ta_arm64/lib/
/usr/share/optee-os-s32/export-ta_arm64/mk/
/usr/share/optee-os-s32/export-ta_arm64/scripts/
/usr/share/optee-os-s32/export-ta_arm64/src/
/usr/share/optee-os-s32/export-ta_arm64/ta/
=> I think this should be "s32g2" instead of "export-ta_arm64" since
optee is built with PLATFORM=s32 PLATFORM_FLAVOR=s32g2
=> I think we should align the build command between optee-os and optee-
os-s32 (config flags)
2) In general, presence of .c/.S/.a files suggest we should use Built-
Using in packages build-depending on optee-* dev packages; this should
be documented in some README.Debian (also missing in Debian's optee-os)
3) optee-os-s32 build-depends on nemos-dev-cert and nemos-dev-key; first, I
don't think it makes sense to use a project specific key for general purpose
S32x enablement, so think this should be at least ubuntu-s32-default-key or
something rather than nemos-xyz, but in optee-os I've spotted files such as:
/usr/lib/optee-os-dev/arm-plat-k3/keys/default.pem
/usr/lib/optee-os-dev/arm-plat-k3/keys/default_ta.pem -> default.pem
these suggest that there is a strategy to build a default root of trust in
the optee-os package, so perhaps there is already a solution there.
4) IMO the build-dep on binutils can be dropped; binutils is pulled
through gcc through build-essential, so pretty much no package will list
it explicitly
5) optee-os-
[Bug 2056099] Re: [MIR] tree
[ NB: debdiff from Mate was uploaded to noble by Simon; see also bug #2060550; thanks Mate and Simon! ] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056099 Title: [MIR] tree To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tree/+bug/2056099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043448] Re: [needs-packaging] nemos-dev-key
Hi, I saw that Laider addressed the last remaining issue called here (the specific debian/copyright Indicator Weather copy-paste typo); reviewing only this change compared to 1.7, I sponsored the delta. Since this is a new package and the first time I am sponsporing it, I took a wider look and noted the following opportunities for improvement: * the control file lists Isaac as original maintainer with his Canonical address; this should be removed * I've personally just now subscribed to the nemos-team@LP mailing-list, perhaps Laider and others should too * description of the package is a bit terse, should mention that it is used to sign the boot in generated images for the NemOS project * subjective/personal perspective: I suspect this is broken down into too many very small packages; could probably be just a single package * there is no explanation/documentation for the Provides; this is likely a case of someone being able to craft their own key-carrying deb and host that privately (would need to think of hosting this so that only CI/CD for image generation could get access to the private key!) * there is no documentation as to where the pre-built files (rsa2048_private.pem, rsa2048_public.pem, u-boot-signature.dtsi) are coming from, nor how these were generated; these are fairly obvious (perhaps the u-boot device tree source snippet a bit less), but would seem useful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043448 Title: [needs-packaging] nemos-dev-key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2043448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056099] Re: [MIR] tree
Uploaded debdiff adding a basic unit test framework from upstream gitlab merge proposal to noble as tree 2.1.1-2ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056099 Title: [MIR] tree To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tree/+bug/2056099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058460] Re: Recursion limit too low for jammy universe
** Changed in: germinate (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058460 Title: Recursion limit too low for jammy universe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/germinate/+bug/2058460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043448] Re: [needs-packaging] nemos-dev-key
I'm getting all files installed in nemos-dev-key and the two other packages are empty: W: nemos-dev-cert: empty-binary-package W: nemos-dev-cert-u-boot: empty-binary-package Did you perhaps not git add newly added debian/*.install files? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043448 Title: [needs-packaging] nemos-dev-key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2043448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058460] Re: Recursion limit too low for jammy universe
** Changed in: germinate (Ubuntu) Assignee: (unassigned) => Loïc Minier (lool) ** Changed in: germinate (Ubuntu) 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/2058460 Title: Recursion limit too low for jammy universe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/germinate/+bug/2058460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2030784] Re: Backport Intel's AVX512 patches on openssl 3.0
It might cause performance regressions in production though; would you be able to document the failing tests here? I wonder if we would simply have to cherry pick more from 3.2 for these to pass. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2030784 Title: Backport Intel's AVX512 patches on openssl 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2030784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056291] [NEW] makedb hangs when a tempfile already exists
Public bug reported:
release: focal
libnss-db: 2.2.3pre1-6build6
We had an event where running makedb on a group file or password file
hanged/did not succeed. Using strace, we found out the temp file already
existed and it was trying in a loop:
openat(AT_FDCWD, "__db.group.db.t", O_RDWR|O_CREAT|O_EXCL, 0664) = -1 EEXIST
(File exists)
select(0, NULL, NULL, NULL, {tv_sec=1, tv_usec=1}) = 0 (Timeout)
stat("group.db.t", 0x7ffee4bafce0) = -1 ENOENT (No such file or directory)
stat("__db.group.db.t", {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
Also happened for __db.passwd.db.t file on other hosts with the same
version/release.
Removing the temp file solves it.
To reproduce, create a valid passwd.tdb file, then:
$ touch __db.passwd.db.t
$ makedb passwd.tdb -o passwd.db.t
Thank you
** Affects: libnss-db (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/2056291
Title:
makedb hangs when a tempfile already exists
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnss-db/+bug/2056291/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055402] Re: Though lintian call: error: troff: Segmentation fault
Thanks John! I've changed the bug tasks back to lintian as it sounds like the most reasonable short-term option would be to patch lintian to pick a predictable directory and update the apparmor profiles; later, we will have new apparmor to deal with this situation more elegantly -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055402 Title: Though lintian call: error: troff: Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/2055402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055402] Re: Though lintian call: error: troff: Segmentation fault
@Seth: I was only using /tmp/output to not write to the current dir; the typical case is lintian creating a safe tmpdir. ** Also affects: lintian (Ubuntu) Importance: Undecided Status: New ** Changed in: lintian (Ubuntu) Status: New => Confirmed ** No longer affects: groff (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055402 Title: Though lintian call: error: troff: Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/2055402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2006042] Re: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram
Quick update, this was still happening with Jammy, and it it still happening with Noble. The pattern I identified for 90% chances of hanging on wake up: - boot or wake up from suspend to RAM - use the laptop for a short time (short being less than a couple hours) - suspend to RAM -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2006042 Title: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055402] Re: Though lintian call: error: troff: Segmentation fault
I'm not sure how to properly fix this, we allow the shell to write anywhere, then file_inherit is triggered because we don't want man to write anywhere, which seems to be what we typically want to achieve with the apparmor profile. Should we teach lintian and perhaps every other tool to use a specific directory? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055402 Title: Though lintian call: error: troff: Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/groff/+bug/2055402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055402] Re: Though lintian call: error: troff: Segmentation fault
This is due to the apparmor profile and the man pipeline trying to flush and stat the output file which can be anywhere in the fs [Thu Feb 29 11:23:53 2024] audit: type=1400 audit(1709205849.791:651): apparmor="DENIED" operation="file_inherit" class="file" namespace="root//lxd-daily_" profile="man_groff" name="/tmp/output" pid=97274 comm="troff" requested_mask="w" denied_mask="w" fsuid=1001000 ouid=1001000 [Thu Feb 29 11:23:53 2024] audit: type=1400 audit(1709205849.819:652): apparmor="DENIED" operation="getattr" class="file" info="Failed name lookup - disconnected path" error=-13 namespace="root//lxd-daily_" profile="/usr/bin/man" name="apparmor/.null" pid=97274 comm="troff" requested_mask="r" denied_mask="r" fsuid=1001000 ouid=0 [Thu Feb 29 11:23:53 2024] audit: type=1400 audit(1709205849.819:653): apparmor="DENIED" operation="getattr" class="file" info="Failed name lookup - disconnected path" error=-13 namespace="root//lxd-daily_" profile="man_groff" name="apparmor/.null" pid=97274 comm="troff" requested_mask="r" denied_mask="r" fsuid=1001000 ouid=0 ** Description changed: groff crash when redirecting output to a file % man --warnings -E UTF-8 -l -Tutf8 -Z /usr/share/man/man1/cat.1.gz >output troff::3: fatal error: unable to flush output file: Permission denied groff: error: troff: Segmentation fault (core dumped) man: command exited with status 2: /usr/libexec/man-db/zsoelim | /usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE | preconv -e UTF-8 | tbl | groff -mandoc -Z -rLL=78n -rLT=78n -wmac -Tutf8 + + This is typically triggered by lintian when scanning man pages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055402 Title: Though lintian call: error: troff: Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/groff/+bug/2055402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055402] Re: Though lintian call: error: troff: Segmentation fault
** Description changed: - Hello, + groff crash when redirecting output to a file - I was trying to run lintian on some deb packages an run onto some errors - messages from groff. - - Steps to reproduce: - - 1. Setup a LXD container with mantic or Noble: - - lxc launch ubuntu-daily:noble #or lxc launch ubuntu:mantic - - 2. After getting connected to the container: Install lintian on it - - apt install lintian - - 3. Run lintian on some package inside the container: - - apt download tree && lintian tree_*.deb - - 4. Enjoy the groff-message logs: - - W: tree: groff-message command exited with status 2: /usr/libexec/man-db/zsoelim | /usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE | preconv -e UTF-8 | groff -mandoc -Z -rLL=117n -rLT=117n -wmac -Tutf8 [usr/share/man/man1/tree.1.gz:2] - W: tree: groff-message error: troff: Segmentation fault (core dumped) [usr/share/man/man1/tree.1.gz:1] - - * Container infos: - - lsb_release -rd - - No LSB modules are available. - Description:Ubuntu Noble Numbat (development branch) - Release:24.04 - - * Packages infos: - - apt-cache policy groff - groff: - Installed: (none) - Candidate: 1.23.0-3 - Version table: - 1.23.0-3 500 - 500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages - - apt-cache policy lintian - lintian: - Installed: 2.117.0ubuntu1 - Candidate: 2.117.0ubuntu1 - Version table: - *** 2.117.0ubuntu1 500 - 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages - 100 /var/lib/dpkg/status - - * Expected output (on Jammy): No segfault and no problem on the tested - package with lintian (tree_2.1.1-2_amd64.deb) + % man --warnings -E UTF-8 -l -Tutf8 -Z /usr/share/man/man1/cat.1.gz >output + troff::3: fatal error: unable to flush output file: Permission denied + groff: error: troff: Segmentation fault (core dumped) + man: command exited with status 2: /usr/libexec/man-db/zsoelim | /usr/libexec/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE | preconv -e UTF-8 | tbl | groff -mandoc -Z -rLL=78n -rLT=78n -wmac -Tutf8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055402 Title: Though lintian call: error: troff: Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/groff/+bug/2055402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055402] Re: Though lintian call: error: troff: Segmentation fault
** No longer affects: lintian (Ubuntu) ** No longer affects: ubuntu ** Changed in: groff (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/2055402 Title: Though lintian call: error: troff: Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/groff/+bug/2055402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962289] Re: Mediatek AIoT i500 support
Upload is pending review in focal Unapproved queue: https://launchpad.net/ubuntu/focal/+queue?queue_state=1&queue_text= -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962289 Title: Mediatek AIoT i500 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1962289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962289] Re: Mediatek AIoT i500 support
** Changed in: flash-kernel (Ubuntu Focal) Assignee: (unassigned) => Loïc Minier (lool) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962289 Title: Mediatek AIoT i500 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1962289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962289] Re: Mediatek AIoT i500 support
** Also affects: flash-kernel (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/1962289 Title: Mediatek AIoT i500 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1962289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962289] Re: Mediatek AIoT i500 support
flash-kernel (3.104ubuntu8) jammy; urgency=medium * mkimage_fit: subst KERNEL_VERSION in ITS file with actual kernel version. * Add DB entry, bootscript and ITS templates for Mediatek AIoT i500 board. Date: Sun, 03 Apr 2022 19:33:03 +0200 Changed-By: Ethan Hsieh Maintainer: Ubuntu Developers Signed-By: Loïc Minier https://launchpad.net/ubuntu/+source/flash-kernel/3.104ubuntu8 == OK: flash-kernel_3.104ubuntu8.tar.xz OK: flash-kernel_3.104ubuntu8.dsc -> Component: main Section: utils ** Changed in: flash-kernel (Ubuntu) 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/1962289 Title: Mediatek AIoT i500 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1962289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962289] Re: Mediatek AIoT i500 support
I've re-reviewed this, updated README to match the new behavior and
tweaked changelog slightly, and I've uploaded this to jammy - failing to
add the LP: #1962289 in changelog; it's currently in the UNAPPROVED
queue
https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=
I agree this should go with Debian along with a bazillion changes we
have in Ubuntu, but such "API" like changes would indeed ideally be
prioritized in our upstreaming efforts.
** Changed in: flash-kernel (Ubuntu)
Assignee: (unassigned) => Loïc Minier (lool)
** Changed in: flash-kernel (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962289
Title:
Mediatek AIoT i500 support
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1962289/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965821] Re: Jammy Freeze Exception
That's wonderful news, thank you Brian ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965821 Title: Jammy Freeze Exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bip/+bug/1965821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965821] Re: Jammy Freeze Exception
** Attachment added: "Installation log" https://bugs.launchpad.net/ubuntu/+source/bip/+bug/1965821/+attachment/5571504/+files/bip-install.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965821 Title: Jammy Freeze Exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bip/+bug/1965821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965821] Re: Jammy Freeze Exception
Let me know if you need more details or files. You can find me on IRC (or Canonical Mattermost). Thank you, Loïc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965821 Title: Jammy Freeze Exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bip/+bug/1965821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965821] Re: Jammy Freeze Exception
I've tested using that version of the code for more than 2 months without issues. SASL authentication feature has been tested in PLAIN mode and EXTERNAL with an SSL cert fingerprint. Also, it has been tested with multiple username/password lengths, including the ones triggering the specific cases (when the base64 SASL authentication challenge is exactly of 400 chars). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965821 Title: Jammy Freeze Exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bip/+bug/1965821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965821] Re: Jammy Freeze Exception
Debian package has been built and released in Debian sid: https://tracker.debian.org/pkg/bip See build logs, package/dbgsyms attached. ** Attachment added: "bip-0.9.3-build_master.zip" https://bugs.launchpad.net/ubuntu/+source/bip/+bug/1965821/+attachment/5571503/+files/bip-0.9.3-build_master.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965821 Title: Jammy Freeze Exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bip/+bug/1965821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965821] Re: Jammy Freeze Exception
** Patch added: "Changelog diff" https://bugs.launchpad.net/ubuntu/+source/bip/+bug/1965821/+attachment/5571501/+files/Changelog.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965821 Title: Jammy Freeze Exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bip/+bug/1965821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965821] Re: Jammy Freeze Exception
NEWS file changes since 0.9.2: 2022-03-10 (0.9.3) "sanitize our bip and add some layers" - Add SASL authentication support (EXTERNAL, PLAIN) - Handle some recommended GCC flags - fix /bip user info command -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965821 Title: Jammy Freeze Exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bip/+bug/1965821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965821] [NEW] Jammy Freeze Exception
Public bug reported: Bip 0.9.3 has been released upstream. Differences with currently schedules for release 0.9.2-1build2 are: - new feature: SASL authentication support - fixes for /BIP commands - bug/compilation warning fixes The SASL authentication support feature should have a limited impact on bip runtime stability, as the code change is quite limited too, and its code is only called during server connect phases, which happen scarcely during the daemon's life. We believe it is important it reaches Ubuntu LTS as Libera.Chat, one of the most used network for open-source, has made mandatory authentication through SASL when connecting from a list of IP pools, including from the network of one of the most popular hosting services in France (Scaleway). It's probable they included most popular hosting services around the world in that list. See https://libera.chat/guides/sasl#sasl-access-only-ip-ranges for more information. The other changes are fixes and should be included. Thank you! Loïc Gomez ** Affects: bip (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/1965821 Title: Jammy Freeze Exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bip/+bug/1965821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962289] Re: Mediatek AIoT i500 support
@Ethan: sounds good; perhaps one way to think about it could be: 1) the kernel knows which dtbs and dtbos are supported with a particular kernel build 2) flash-kernel has a clear and stable interface to pull the right bits into a FIT image but does not need to keep track of the list in flash-kernel itself One way to go would be to agree that all *.dtbo in a particular subdirectory of the kernel deb should be included, or even better, having a list of dtbos for a particular board; flash-kernel could keep the FIT image template, but would iterate over the dtbos listed in the kernel-provided file to generate the FIT image. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962289 Title: Mediatek AIoT i500 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1962289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962289] Re: Mediatek AIoT i500 support
Hi there, Thanks for the nice debdiffs; reading through these, I see the following changes: 1) a new boot script – fine, albeit flash-kernel seems to collect more and more of them and it would be good to avoid having too many 2) support for using the kernel ABI version in substs – why not, albeit it's a bit surprising this wasn't needed so far, and it looks like this might be breaking an abstraction 3) a new its file as a template for the FIT image; this one seems really wrong to me because it has this long list of dtbos which will likely evolve across kernel versions IMO the job of flash-kernel is to keep track of the method with which we install kernels/initramfses/other boot assets, but once a method is implemented, it can be used for a long time. Here, the list of dtbos is very long and seems very platform specific, so it's likely to evolve with kernel versions, so it will likely result in having to update flash-kernel for a new kernel, or having to manage versioned dependencies like "at least this version of flash-kernel to get the its that installs this list of dtbos". I'm not sure what the proper solution is, it could be that the its file should be provided by the kernel rather than flash-kernel, like dtbs, or perhaps we need to scan for dtbo files. What would be really useful would be to explain how these dtbos are being used, what's the scenario in which they are used in the FIT image? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962289 Title: Mediatek AIoT i500 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1962289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962133] Re: Intermittent very low fps(sometimes zero) with few specific h264 and h265 RTSP input streams sources when used with gst-v4l2 based gstreamer-1.0(version gst-1.14.5) decode pipeline
Please attach the reproducing pipeline; it's a bit tricky to organise access to Jetson hardware to the right people, so if you had a reproducer that we could run without Jetson hardware, that would be best! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962133 Title: Intermittent very low fps(sometimes zero) with few specific h264 and h265 RTSP input streams sources when used with gst-v4l2 based gstreamer-1.0(version gst-1.14.5) decode pipeline To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer1.0/+bug/1962133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962134] Re: Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on ubuntu-20.04
Hi Kunal, It might be tricky to organise testing on Jetson platforms for people that will prepare the fix. In any case, could you share instructions to reproduce? If there's a way to craft a test pipeline that trigger the issue without Jetson hardware, that would be best. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962134 Title: Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on ubuntu-20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1962134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962134] Re: Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on ubuntu-20.04
Would you be able to share a reproducing pipeline? ideally that can be run on vanilla Ubuntu rather than on specific hardware or with Nvidia added plugins -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962134 Title: Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on ubuntu-20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1962134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962134] Re: Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on ubuntu-20.04
This patch landed upstream in 1.17.90, marking only bionic and focal as possibly affected ** Also affects: gstreamer1.0 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: gstreamer1.0 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gstreamer1.0 (Ubuntu) Status: New => 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/1962134 Title: Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on ubuntu-20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1962134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962135] Re: Upgrade defalult gstreamer version 1.16 minor version on ubuntu-20.04
** Also affects: gstreamer1.0 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gstreamer1.0 (Ubuntu) Status: New => 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/1962135 Title: Upgrade defalult gstreamer version 1.16 minor version on ubuntu-20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1962135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962133] Re: Intermittent very low fps(sometimes zero) with few specific h264 and h265 RTSP input streams sources when used with gst-v4l2 based gstreamer-1.0(version gst-1.14.5) decode pipeline
The mentioned upstream patch was included in the 1.15.2 release and jammy and focal are unaffected; bionic does not have this patch in 1.14.5-0ubuntu1~18.04.3 ** Package changed: gstreamer1.0 (Ubuntu) => gst-plugins-base1.0 (Ubuntu) ** Also affects: gst-plugins-base1.0 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gst-plugins-base1.0 (Ubuntu) Status: New => 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/1962133 Title: Intermittent very low fps(sometimes zero) with few specific h264 and h265 RTSP input streams sources when used with gst-v4l2 based gstreamer-1.0(version gst-1.14.5) decode pipeline To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer1.0/+bug/1962133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962133] Re: Intermittent very low fps(sometimes zero) with few specific h264 and h265 RTSP input streams sources when used with gst-v4l2 based gstreamer-1.0(version gst-1.14.5) decode pipeline
Hi Kunal, thanks for your report; I looked at the upstream bug, and I didn't find a reproducer to confirm the bug and its resolution with the patch; would you have one? This might be a candidate for a SRU update; the process is outlined in https://wiki.ubuntu.com/StableReleaseUpdates and is largely about assessing risk of regressions. ** Bug watch added: bugzilla.gnome.org/ #796771 https://bugzilla.gnome.org/show_bug.cgi?id=796771 ** Also affects: gstreamer1.0 via https://bugzilla.gnome.org/show_bug.cgi?id=796771 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962133 Title: Intermittent very low fps(sometimes zero) with few specific h264 and h265 RTSP input streams sources when used with gst-v4l2 based gstreamer-1.0(version gst-1.14.5) decode pipeline To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer1.0/+bug/1962133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798363] Re: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
Same here on Razer Blade 15 Advanced Model (mid-2021). Trackpad isn't working after suspend. My kernel is 5.15.0-2-amd64. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798363 Title: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835712] Re: add support of android application in ubuntu
https://waydro.id/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835712 Title: add support of android application in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1835712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931278] Re: Creating FIT images is not supported
thanks for the patch! this might be easier to review as smaller atomic changes, but perhaps I can still follow around the debdiff :) 1) The its files are data, so they should to /usr/share; I wouldn't encourage local customizations by dropping them in /etc unless that's an important function; a way to give control would be to install a local flash-kernel database entry that overrides the shipped defaults for that hardware; this should be possible with /etc/flash-kernel/db? 2) would you add the new Boot-FIT-Path and Boot-ITS-Path to README? 3) seems "Boot-ITS-Path: /.../foo.its" should be written "U-Boot-ITS- Name: foo.its" and should be searched in the default flash-kernel directory 4) would it be possible to avoid the cp calls for kernel and initrd and just generate the fit image from their locations? the kernels / initrds tend to be big, so I suspect this adds non-trivial time to the run on SD cards 5) mkimage_fit(): why is padding needed? perhaps deserves a comment. Should this be a config? 6) the full path name in DTB-Id is the first one in the database, perhaps this suggests the corresponding deb should be in Required- Packages? would help with d-i usage 6) "cd" looks pretty singular compared to rest of functions; could it be avoided? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931278 Title: Creating FIT images is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1931278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805018] Re: Need activate more hardening option
To be read! https://blog.herecura.eu/blog/2020-05-30-kconfig-hardening-tests/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805018 Title: Need activate more hardening option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899208] [NEW] bug crach udpdate 20.04
Public bug reported: bug crach udpdate 20.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Oct 9 20:24:19 2020 InstallationDate: Installed on 2017-12-30 (1013 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-09 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899208 Title: bug crach udpdate 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1899208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893754] [NEW] shortcut active in search bar with french keyboard
Public bug reported: Keyboard shortcuts are active in the search bar with evolution 3.36.4-0ubuntu1 and 3.36.3-0ubuntu1 on Ubuntu 20.04 and the french keyboard. They are not active with the English keyboard. Steps to reproduce: * Install Ubuntu 20.04 in french * Install evolution * Go in a mailbox * Click on the search bar * Type Shift-5 on the keyboard What happens: * The current mail header changes color because the 5 shortcut is toggled * No 5 shows in the search bar What is expected: * The character 5 shows in the search bar Workaround: * Switch to an english keyboard ** Affects: evolution (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/1893754 Title: shortcut active in search bar with french keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1893754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885091] [NEW] ubiquity launches even if disc control fails.
Public bug reported: Hi, The live-usb check found an error but ubiquity started and failed after I started the installation. Please add condition to Ubiquity for not run this if the live-usb is in error. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: fail CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 25 09:43:09 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=fr_FR.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885091 Title: ubiquity launches even if disc control fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1885091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881631] Re: arm64 Ubuntu kernel builds missing CONFIG_NLS_ASCII
ubuntu-focal.git, focal/raspi2 branch: debian.raspi2/config/config.common.ubuntu:CONFIG_NLS_ASCII=y ubuntu-bionic.git, bionic/raspi2 branch: debian.raspi2/config/config.common.ubuntu:CONFIG_NLS_ASCII=y So not quite sure where this is coming from -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881631 Title: arm64 Ubuntu kernel builds missing CONFIG_NLS_ASCII To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1881631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805018] Re: Need activate more hardening option
Ubuntu 20.04 LTS (Focal Fossa) : config check is finished: 'OK' - 57 / 'FAIL' - 79 https://github.com/a13xp0p0v/kconfig-hardened- check/commit/e54cb30a2789c8f8ce15648d72299e243b3b27c1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805018 Title: Need activate more hardening option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859287] Re: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04
Can confirm 5.4.0-18.22 in proposed fixes iwlwifi for me; thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859287 Title: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859287] Re: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04
Should also mention I've upgraded all packages to latest in focal including linux-firmware 1.186. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859287 Title: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859287] Re: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04
Just to confirm that I still have broken WiFi with linux- image-5.4.0-14-generic 5.4.0-14.17 (but it works with linux- image-5.3.0-26-generic 5.3.0-26.28 and worked with iwlwifi backports when I tried). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859287 Title: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864722] [NEW] apparu lors de mise à niveau et impossible déconnexion
Public bug reported: Lors d'une tentative d'une mise à niveau, le problème a été signalé et la commande déconnexion n'est pas valide. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.29 ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211 Uname: Linux 4.4.0-174-generic i686 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: i386 CrashDB: ubuntu CurrentDesktop: LXDE Date: Tue Feb 25 22:30:20 2020 InstallationDate: Installed on 2014-01-03 (2244 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release i386 (20131016) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug dist-upgrade i386 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864722 Title: apparu lors de mise à niveau et impossible déconnexion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1864722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859287] Re: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04
Dkms module worked with 5.4.0-9-generic and current linux-firmware, thanks! ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859287/+attachment/5320091/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859287 Title: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859287] Re: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04
Tried with: linux-image-unsigned-5.5.0-050500rc6-generic_5.5.0-050500rc6.202001122031_amd64.deb linux-modules-5.5.0-050500rc6-generic_5.5.0-050500rc6.202001122031_amd64.deb (after disabling secure boot) => no wifi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859287 Title: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859287] [NEW] iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04
Public bug reported: Hi there, Laptop: Dell XPS 13 7390 2-in-1 Built-in wireless: Killer Wi-Fi 6 AX1650i 160MHz iwlwifi worked fine with 19.10 but breaks when upgrading to 20.04. Firmware crashes after loading and interface doesn't show up. This is with: linux-image-5.4.0-9-generic 5.4.0-9.12 linux-firmware 1.184 I've noticed the driver was trying to load a more recent firmware: Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2 I've downloaded this file from upstream iwlwifi firmware git and tried unloading/reloading iwlwifi. Driver crashes as well, but with a different error code. Best, - LM ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lool 1579 F pulseaudio /dev/snd/pcmC0D0p: lool 1579 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jan 11 15:02:08 2020 InstallationDate: Installed on 2019-12-02 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic root=UUID=854f3bc2-da3a-4a3c-82a1-6b04a932bb29 ro pcie_aspm=off plymouth.force-scale=3 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-11 (0 days ago) dmi.bios.date: 11/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 06CDVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd11/10/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: Hi there, Laptop: Dell XPS 13 7390 2-in-1 Built-in wireless: Killer Wi-Fi 6 AX1650i 160MHz iwlwifi worked fine with 19.10 but breaks when upgrading to 20.04. Firmware crashes after loading and interface doesn't show up. This is with: linux-image-5.4.0-9-generic 5.4.0-9.12 linux-firmware 1.184 I've noticed the driver was trying to load a more recent firmware: - Direct firmware load for iwlwifi-Qu-b0-hr-b0-49.ucode failed with error -2 + Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2 I've downloaded this file from upstream iwlwifi firmware git and tried unloading/reloading iwlwifi. Driver crashes as well, but with a different error code. Best, - LM ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: lool 1579 F pulseaudio - /dev/snd/pcmC0D0p: lool 1579 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: lool 1579 F pulseaudio + /dev/snd/pcmC0D0p: lool 1579 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jan 11 15:02:08 2020 InstallationDate: Installed on 2019-12-02 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic root=UUID=854f3bc2-da3a-4a3c-82a1-6b04a932bb29 ro pcie_aspm=off plymouth.force-scale=3 quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-9-generic N/A - linux-backports-modules-5.4.0-9-generic N/A - linux-firmware 1.184 + linux-restricted-modules-5.4.0-9-generic N/A + linux-backports-modules-5.4.0-9-generic N/A + linux-firmware 1.184 RfKill: - 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + 0: hci0: Bluetooth + Soft bloc
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20 - 5.3
** Bug watch added: Linux Kernel Bug Tracker #204837 https://bugzilla.kernel.org/show_bug.cgi?id=204837 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=204837 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 - 5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851263] Re: Ubuntu 18.04.3 LTS bump Glibc 2.27 to the latest stable
Hi Romain and thanks for your report, In general, we don't make large upstream updates after release, especially for LTS and even more so for a critical piece like glibc. If you've identified the single patch that would address your issue, it can be considered for the SRU process: https://wiki.ubuntu.com/StableReleaseUpdates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851263 Title: Ubuntu 18.04.3 LTS bump Glibc 2.27 to the latest stable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1851263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849542] Re: Thunderbird empty after update to 19.10
I got it. See it attached. ** Attachment added: "faulty file" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1849542/+attachment/5299645/+files/global-messages-db.sqlite -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849542 Title: Thunderbird empty after update to 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1849542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849542] Re: Thunderbird empty after update to 19.10
Just deleted global-messages-db.sqlite and now it looks like it works fine. I hopê I didn't loose anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849542 Title: Thunderbird empty after update to 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1849542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849542] [NEW] Thunderbird empty after update to 19.10
Public bug reported: HELP Just performed an upgrade from Ubuntu 19.04 to 19.10. Launched Thunderbird and the interface is empty. No emails, no folders, no calendar, I can't even open the "account settings" window. This is a complete disaster. I need thunderbird for my work. If I launch TB form terminal I get this: lalejand@Gedeon:~$ thunderbird JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined TypeError: aAttrDef.objectNounDef is undefined -- Exception object -- * -- Stack Trace -- defineAttribute@resource:///modules/gloda/gloda.js:1922:5 defineAttributes@resource:///modules/gloda/fundattr.js:71:35 init@resource:///modules/gloda/fundattr.js:43:12 @resource:///modules/gloda/everybody.js:13:15 @resource:///modules/gloda/public.js:8:57 nsAutoCompleteGloda@jar:file:///usr/lib/thunderbird/omni.ja!/components/glautocomp.js:516:32 createInstance@resource://gre/modules/XPCOMUtils.jsm:433:19 glodaSearch_XBL_Constructor@chrome://messenger/content/search.xml:73:16 JavaScript error: chrome://messenger/content/messenger.xul, line 1: TypeError: QuickFilterBarMuxer is undefined JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 470: TypeError: TagUtils is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined What can I do ? Release: Ubuntu 19.10 Package version: 1:68.1.2+build1-0ubuntu ** Affects: thunderbird (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/1849542 Title: Thunderbird empty after update to 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1849542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 641899] Re: Ubuntu Software Center is very slow
Ubuntu Team impresses me This fucking bug is 9 years old! Close all bugs reports after one year if you don't know how to fix them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/641899 Title: Ubuntu Software Center is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/641899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835712] [NEW] add support of android application in ubuntu
Public bug reported: Hello, it would be nice to be able to use android applications directly in Ubuntu without using virtualization. you should be able to do something like that: $ sudo snap-apk install FDroid.apk you can be inspired by Anbox (Android in a Box) but we really need to better integrate android software into the system menu. Thanks. ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: anbox android -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835712 Title: add support of android application in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1835712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805018] Re: Need activate more hardening option
config-5.0.0-16-generic: 'OK' - 43 / 'FAIL' - 60 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805018 Title: Need activate more hardening option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805018] Re: Need activate more hardening option
** Attachment added: "kconfig-hardened-check_config-5.0.0-16-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805018/+attachment/5268395/+files/kconfig-hardened-check_config-5.0.0-16-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805018 Title: Need activate more hardening option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805018] Re: Need activate more hardening option
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805018 Title: Need activate more hardening option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811984] Re: flash-kernel 3.90ubuntu3.18.10.1 fails with mkimage: not found if no uboot is used
NB: If you're using an official image and it's missing mkimage, could you point at the specific image you used? :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811984 Title: flash-kernel 3.90ubuntu3.18.10.1 fails with mkimage: not found if no uboot is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1811984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811984] Re: flash-kernel 3.90ubuntu3.18.10.1 fails with mkimage: not found if no uboot is used
This is by design, flash-kernel has different dependencies depending on the target hardware; the piece of software making the system bootable (e.g. the flash-kernel udeb in d-i/ubiquity) will install flash-kernel and the hardware-specific deps (such as u-boot-tools). ** Changed in: flash-kernel (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811984 Title: flash-kernel 3.90ubuntu3.18.10.1 fails with mkimage: not found if no uboot is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1811984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810601] [NEW] Graphics trouble
Public bug reported: Can't seem to get system to use nvidia driver instead of Nouveau ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-lowlatency 4.15.18 Uname: Linux 4.15.0-43-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Jan 5 16:03:44 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASRock Incorporation 2nd Generation Core Processor Family Integrated Graphics Controller [1849:0102] NVIDIA Corporation GF119 [NVS 310] [10de:107d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GF119 [NVS 310] [10de:1154] InstallationDate: Installed on 2018-08-14 (143 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-lowlatency root=UUID=89dc7f0c-2342-4866-bf1f-7d5c9635d42c ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.00 dmi.board.name: Z77 Extreme4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd03/02/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4-M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810601 Title: Graphics trouble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1810601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736940] Re: Ubuntu 16.04 LTS: SMBStatus shows wrong information
For the most curious: https://github.com/sonicnkt/wpkg-gp/issues/2#issuecomment-451371444 Thanks. ** Bug watch added: github.com/sonicnkt/wpkg-gp/issues #2 https://github.com/sonicnkt/wpkg-gp/issues/2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736940 Title: Ubuntu 16.04 LTS: SMBStatus shows wrong information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1736940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736940] Re: Ubuntu 16.04 LTS: SMBStatus shows wrong information
It would be good to take into account the comments from here: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1697817 The last versions of Windows 10 does not work well with the samba of Ubuntu 16.04 because of the SMB version. To make it simple with windows 10 1809, I can only run WPKG-GP with SMB v1 ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736940 Title: Ubuntu 16.04 LTS: SMBStatus shows wrong information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1736940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697817] Re: disable smb1 by default
Hi, It would be good to take into account the comments from here (I posted a patch that I hope will be used.) : https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1736940 The last versions of Windows 10 does not work well with the samba of Ubuntu 16.04 because of the SMB version. To make it simple with windows 10 1809, I can only run WPKG-GP with SMB v1 ! https://github.com/sonicnkt/wpkg-gp/issues/2 Thanks. ** Bug watch added: github.com/sonicnkt/wpkg-gp/issues #2 https://github.com/sonicnkt/wpkg-gp/issues/2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697817 Title: disable smb1 by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1697817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736940] Re: Ubuntu 16.04 LTS: SMBStatus shows wrong information
sudo smbstatus -b Samba version 4.3.11-Ubuntu PID Username Group MachineProtocol Version -- 9483 nobodynogroup 192.168.182.228 (ipv4:192.168.182.228:49712) Unknown (0x0311) 9483 nobodynogroup 192.168.182.228 (ipv4:192.168.182.228:49712) Unknown (0x0311) ** Changed in: samba4 (Ubuntu) Status: Incomplete => Confirmed ** Attachment added: "[PATCH] s3: add suport for SMB3_10 and SMB3_11 protocols in smbstatus" https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1736940/+attachment/5226619/+files/s3%3A%20add%20suport%20for%20SMB3_10%20and%20SMB3_11%20protocols%20in%20smbstatus.diff.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736940 Title: Ubuntu 16.04 LTS: SMBStatus shows wrong information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1736940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805018] Re: Need activate more hardening option
Current kernel configuration ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2013-2141 ** Attachment added: "config-4.18.0-11-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805018/+attachment/5216184/+files/config-4.18.0-11-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805018 Title: Need activate more hardening option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805018] Re: Need activate more hardening option
No log files is required. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805018 Title: Need activate more hardening option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805018] [NEW] Need activate more hardening option
Public bug reported: Hi, The current configuration of the linux kernel in Ubuntu is not secure enough. A simple test [1] of kernel in Ubuntu Disco clearly indicates 53 errors... Can we discuss possible options to activate by default? Enable the GCC_PLUGINS* would be for me the bare minimum. Thanks. Best regards, [1] https://github.com/a13xp0p0v/kconfig-hardened-check ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: hardened hardening linux secure ** Attachment added: "kconfig-hardened-check_config-4.18.0-11-generic" https://bugs.launchpad.net/bugs/1805018/+attachment/5216156/+files/kconfig-hardened-check_config-4.18.0-11-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805018 Title: Need activate more hardening option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730494] Re: drawing the stroke for a gesture creates black tiles on screen
Bug still present when upgrading from Ubuntu 16.04 LTS to 18.04 LTS, package is 0.6.0-0ubuntu11. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730494 Title: drawing the stroke for a gesture creates black tiles on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/easystroke/+bug/1730494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1684240] Re: Lagging square around mouse pointer
Hello Matthias, I've read your comment, and I must add I was having this problem while simply using the HDMI port on my laptop. So maybe it's some lucky "fix" in your case ? I'm not using nvidia drivers anymore since this problem was a real pain and was never fixed, plus another issue caused applications to suddenly stop refreshing at all except with alt+tab (which made quick complicated seeing what I do, "alt+tabbing" every second), so I can't tell if my input is still valid. Kind regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1684240 Title: Lagging square around mouse pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1684240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769358] [NEW] Thumbnail previews in Files/Nautilus only show when zoom is 150% or more
Public bug reported: Ubuntu 18.04 LTS Nautilus package: 1:3.26.3-0ubuntu4 I don't get thumbnail previews in Files (Nautilus) at the default zoom level when using List view. If I select 150% in the hamburger menu the thumbnails are displayed, and they are displayed in Grid view at all sizes. They are also displayed in the Open File dialog, even though the icon size there is smaller than in Files! ** Affects: nautilus (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/1769358 Title: Thumbnail previews in Files/Nautilus only show when zoom is 150% or more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1769358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
