[Bug 2062374] [NEW] [Feature Request] Build dotnet-runtime-deps packages
Public bug reported:
Microsoft builds and recommends [1] building the packages `dotnet-
runtime-deps-6.0`, `dotnet-runtime-deps-7.0`, `dotnet-runtime-deps-8.0`.
These contain the dependencies needed by the .NET runtime for the
specific version.
This is useful if a developer created a self contained application that
is bundled with a runtime, because the bundled runtime still has
dependencies [2]. Having these packages improves the developer
experience, because developers do not need to install (& keep track of
changes to) runtime dependencies manually.
[Implementation details]
I already looked into how we would add these packages:
- `dotnet-runtime-deps-X.0` would just be an empty package
- `dotnet-runtime-X.0` would depend on `dotnet-runtime-deps-X.0`
- the `libicuXX` depends would move to `dotnet-runtime-deps-X.0`
- We need to capture the ${shlibs:Depends} of `dotnet-runtime-X.0` and copy it
I looked up that dh_shlibdeps generates `debian/*.substvars` where * is
the package name. The .substvars file will contain the substitution
values. Then we just need to "smartly" copy the values over from
`dotnet-runtime-X.0.substvar` into `dotnet-runtime-deps-X.0.substvar`
before calling dh_gencontrol in override_dh_gencontrol.
[1]
https://learn.microsoft.com/en-us/dotnet/core/distribution-packaging#recommended-packages
[2]
https://learn.microsoft.com/en-us/dotnet/core/install/linux-ubuntu-install?pivots=os-linux-ubuntu-2404=dotnet8#dependencies
** Affects: dotnet6 (Ubuntu)
Importance: Wishlist
Status: Triaged
** Affects: dotnet7 (Ubuntu)
Importance: Wishlist
Status: Triaged
** Affects: dotnet8 (Ubuntu)
Importance: Wishlist
Status: Triaged
** Changed in: dotnet8 (Ubuntu)
Status: New => Triaged
** Changed in: dotnet8 (Ubuntu)
Importance: Undecided => Wishlist
** Also affects: dotnet7 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: dotnet7 (Ubuntu)
Status: New => Triaged
** Changed in: dotnet7 (Ubuntu)
Importance: Undecided => Wishlist
** Also affects: dotnet6 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: dotnet6 (Ubuntu)
Status: New => Triaged
** Changed in: dotnet6 (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062374
Title:
[Feature Request] Build dotnet-runtime-deps packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2062374/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048926] Re: Not getting listed in dotnet --list-runtimes so facing an error missing 6.0 runtime
Setting this to invalid, based on the strong evidence that this is not related to the Ubuntu package. I will happily reopen the issue if the original reporter provides new information that suggests otherwise. ** Changed in: dotnet6 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048926 Title: Not getting listed in dotnet --list-runtimes so facing an error missing 6.0 runtime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2048926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2028242] Re: Integrate MS Smoke Tests into autopkgtests
Setting dotnet7 to "Won't Fix", because dotnet7 is near EoL and it is not worth fixing. ** Also affects: dotnet8 (Ubuntu) Importance: Undecided Status: New ** Changed in: dotnet8 (Ubuntu) Status: New => In Progress ** Changed in: dotnet8 (Ubuntu) Importance: Undecided => Wishlist ** Changed in: dotnet8 (Ubuntu) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Changed in: dotnet7 (Ubuntu) Status: In Progress => Won't Fix ** Changed in: dotnet7 (Ubuntu) Assignee: Dominik Viererbe (dviererbe) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2028242 Title: Integrate MS Smoke Tests into autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2028242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058746] Re: Support information in README.source is outdated
Fix was released with the March update. ** Changed in: dotnet6 (Ubuntu) Status: In Progress => Fix Released ** Changed in: dotnet7 (Ubuntu) Status: In Progress => Fix Released ** Changed in: dotnet8 (Ubuntu) Status: In Progress => 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/2058746 Title: Support information in README.source is outdated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2058746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060261] Re: [SRU] New upstream microrelease .NET 8.0.4 and SDK 8.0.104
I noticed that the binary packages aspnetcore-runtime-dbg-8.0, dotnet- runtime-dbg-8.0, dotnet-sdk-dbg-8.0 were not build on mantic and jammy. I build and tested the .NET 8 April Update in a new PPA: https://launchpad.net/~dviererbe/+archive/ubuntu/dotnet-april-ppa5 The new PPA also contains a S390X build on noble. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060261 Title: [SRU] New upstream microrelease .NET 8.0.4 and SDK 8.0.104 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet8/+bug/2060261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023531] Re: [MIR] dotnet6
> For Noble forward we only want v8 IIUC, that seems fine as you need to let go of the old at some point - or will that change again later? Correct and this should™ not change in the near/medium distant future. FYI: dotnet6 and dotnet7 was removed from noble for that reason (see LP: #2044511, #2044513). Should not be relevant for the MIR, but just FYI: We will provide dotnet6 and dotnet7 for noble in a PPA, with best effort support limited to the upstream lifespan. Microsoft even wants to stops providing builds in there own PPA starting with noble. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023531 Title: [MIR] dotnet6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2023531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060056] Re: [MIR] dotnet8
Lukas (slyon) asked if the *-dbg-* packages are needed in main. [1] We had a long discussion in the .NET Team and would like to have these binary packages in main. These packages contain .pdb files of the runtimes/SDK/standard libraries. These allow developers to step through library/framework code and therefore contribute to a frictionless developer experience. [1] https://code.launchpad.net/~dviererbe/ubuntu- seeds/+git/ubuntu/+merge/463930/comments/1247825 ** Description changed: This is a follow up to the dotnet6 MIR (see LP: #2023531). We would like to have dotnet8 in main too, which was already discussed during the dotnet6 MIR (see comment 13 [1]). The dotnet8 package is structurally nearly identical. We do this deliberately to lower the maintenance burden. [Notable differences] * There is a single public upstream repository [2] to download all the source code from, therefore uscan can be used to produce the a orig tarball. Note: We do not use uscan, because its limitations adds overhead for our purposes (e.g. using the security repository by default, removing non-linux files, conditionaly including ms prebuilds for bootstraping, etc.). * The source package and it's binary packages have a different upstream version scheme (see spec FO127 [3]). * The source package produces additional binary packages, which include managed code debug symbols (packages with the name pattern *-dbg-8.0). See upstream issue [4] and PR [5]. * We no longer need a .git folder in the orig tarball thanks of upstream efforts. + [Other] + + The naming pattern of the *-dbg-8.0 packages is a recommendation by + upstream that we follow. See [6] + [1] https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2023531/comments/13 [2] https://github.com/dotnet/dotnet [3] https://docs.google.com/document/d/1xKaDHPC9QuxFOGjqK_oNmlurPr6mcaWMc0S-_IRE6A0/edit?usp=sharing [4] https://github.com/dotnet/source-build/issues/3621 [5] https://github.com/dotnet/installer/pull/17454 + [6] https://learn.microsoft.com/en-us/dotnet/core/distribution-packaging#debug-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060056 Title: [MIR] dotnet8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet8/+bug/2060056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023531] Re: [MIR] dotnet6
Just FYI: Comment #13 states "[...] we would like to have all .NET packages in main. The only exception is .NET 7 in jammy that we want to keep in universe." .NET 7 will go EoL on May 14, 2024 and mantic will go EoL in July 2024. Therefore it does not make a lot of sense to MIR the dotnet7 package for mantic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023531 Title: [MIR] dotnet6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2023531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058746] Re: Support information in README.source is outdated
** Changed in: dotnet6 (Ubuntu) Status: Confirmed => In Progress ** Changed in: dotnet7 (Ubuntu) Status: Confirmed => In Progress ** Changed in: dotnet8 (Ubuntu) Status: Confirmed => 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/2058746 Title: Support information in README.source is outdated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2058746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2032945] Re: Integrate minimal smoke-test during build-time
** Changed in: dotnet6 (Ubuntu Jammy) Status: In Progress => Fix Released ** Changed in: dotnet6 (Ubuntu Lunar) Status: In Progress => Fix Released ** Changed in: dotnet6 (Ubuntu Mantic) Status: In Progress => Fix Released ** Changed in: dotnet7 (Ubuntu Jammy) Status: Triaged => Fix Released ** Changed in: dotnet7 (Ubuntu Lunar) Status: Triaged => Fix Released ** Changed in: dotnet7 (Ubuntu Mantic) Status: Triaged => Fix Released ** Changed in: dotnet7 (Ubuntu) Status: Invalid => Fix Released ** Changed in: dotnet6 (Ubuntu) Status: Invalid => 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/2032945 Title: Integrate minimal smoke-test during build-time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2032945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060259] Re: New upstream microrelease .NET 6.0.29 and SDK 6.0.129
I build and tested the April Update in this PPA: https://launchpad.net/~dviererbe/+archive/ubuntu/dotnet-april-ppa2 ** Summary changed: - New upstream microrelease .NET 6.0.29 and SDK 6.0.129 + [SRU] New upstream microrelease .NET 6.0.29 and SDK 6.0.129 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060259 Title: [SRU] New upstream microrelease .NET 6.0.29 and SDK 6.0.129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2060259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060261] Re: New upstream microrelease .NET 8.0.4 and SDK 8.0.104
I build and tested the April Update in this PPA: https://launchpad.net/~dviererbe/+archive/ubuntu/dotnet-april-ppa2 ** Summary changed: - New upstream microrelease .NET 8.0.4 and SDK 8.0.104 + [SRU] New upstream microrelease .NET 8.0.4 and SDK 8.0.104 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060261 Title: [SRU] New upstream microrelease .NET 8.0.4 and SDK 8.0.104 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet8/+bug/2060261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060260] Re: New upstream microrelease .NET 7.0.18 and SDK 7.0.118
I build and tested the April Update in this PPA: https://launchpad.net/~dviererbe/+archive/ubuntu/dotnet-april-ppa2 ** Summary changed: - New upstream microrelease .NET 7.0.18 and SDK 7.0.118 + [SRU] New upstream microrelease .NET 7.0.18 and SDK 7.0.118 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060260 Title: [SRU] New upstream microrelease .NET 7.0.18 and SDK 7.0.118 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet7/+bug/2060260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060260] [NEW] New upstream microrelease .NET 7.0.18 and SDK 7.0.118
Public bug reported: [Impact] * This correspond to an upcoming upstream microrelease (Microsoft Patch Tuesday microrelease). * It is beneficial for our latest LTS users to have access to the latest .NET stack. * This update is bundled with minor fixes: - updates Canonical support information - fixes/adds version parsing edge cases [Test Case] * The package should build successfully in mantic-proposed and jammy- proposed. * The packages should be installable on mantic and jammy on amd64 and arm64 architectures. * Autopackage tests should pass. * The usual manual tests that have been seen in the previous microreleases LP: #2057982, #2011809, #2024893, #2009855, #2003691, #2011675 (see Test Case section there). Note: The need for manual testing is largely reduced since the last SRU, because the autopkgtests improvements far exceeds the coverage provided by the mentioned manual test plans. [Regression Potential] * Upstream tests are usually satisfactory, but there is always a risk of something breaking. [Other] * dotnet7 was removed from the current development release. See LP: #2044513 for details. * 7.0.18 is the version number of the .NET Runtime and 7.0.118 is the version number of the .NET SDK. The package version only refers to the SDK version number. * We are only building the 7.0.1xx feature band, because this is the only feature band that allows to be build from source. See explanation of feature bands: https://learn.microsoft.com/en-us/dotnet/core/releases-and-support#feature-bands-sdk-only * Overview of how dotnet is versioned: https://learn.microsoft.com/en- us/dotnet/core/versions/ ** Affects: dotnet7 (Ubuntu) Importance: Undecided Assignee: Dominik Viererbe (dviererbe) Status: In Progress ** Affects: dotnet7 (Ubuntu Jammy) Importance: Undecided Assignee: Dominik Viererbe (dviererbe) Status: In Progress ** Affects: dotnet7 (Ubuntu Mantic) Importance: Undecided Assignee: Dominik Viererbe (dviererbe) Status: In Progress ** Also affects: dotnet7 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: dotnet7 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: dotnet7 (Ubuntu Jammy) Status: New => In Progress ** Changed in: dotnet7 (Ubuntu Mantic) Status: New => In Progress ** Changed in: dotnet7 (Ubuntu Jammy) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Changed in: dotnet7 (Ubuntu Mantic) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Summary changed: - New upstream microrelease .NET 7.0.18 and SDK 6.0.118 + New upstream microrelease .NET 7.0.18 and SDK 7.0.118 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060260 Title: New upstream microrelease .NET 7.0.18 and SDK 7.0.118 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet7/+bug/2060260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060259] [NEW] New upstream microrelease .NET 6.0.29 and SDK 6.0.129
Public bug reported: [Impact] * This correspond to an upcoming upstream microrelease (Microsoft Patch Tuesday microrelease). * It is beneficial for our latest LTS users to have access to the latest .NET stack. * This update is bundled with minor fixes: - updates Canonical support information - fixes/adds version parsing edge cases [Test Case] * The package should build successfully in mantic-proposed and jammy- proposed. * The packages should be installable on mantic and jammy on amd64 and arm64 architectures. * Autopackage tests should pass. * The usual manual tests that have been seen in the previous microreleases LP: #2057699, #1996499, #1983380, #2011807 (see Test Case section there). Note: The need for manual testing is largely reduced since the last SRU, because the autopkgtests improvements far exceeds the coverage provided by the mentioned manual test plans. [Regression Potential] * Upstream tests are usually satisfactory, but there is always a risk of something breaking. [Other] * dotnet6 was removed from the current development release. See LP: #2044511 for details. * 6.0.29 is the version number of the .NET Runtime and 6.0.129 is the version number of the .NET SDK. The package version only refers to the SDK version number. * We are only building the 6.0.1xx feature band, because this is the only feature band that allows to be build from source. See explanation of feature bands: https://learn.microsoft.com/en-us/dotnet/core/releases-and-support#feature-bands-sdk-only * Overview of how dotnet is versioned: https://learn.microsoft.com/en- us/dotnet/core/versions/ ** Affects: dotnet6 (Ubuntu) Importance: Undecided Assignee: Dominik Viererbe (dviererbe) Status: In Progress ** Affects: dotnet6 (Ubuntu Jammy) Importance: Undecided Assignee: Dominik Viererbe (dviererbe) Status: In Progress ** Affects: dotnet6 (Ubuntu Mantic) Importance: Undecided Assignee: Dominik Viererbe (dviererbe) Status: In Progress ** Also affects: dotnet6 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: dotnet6 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: dotnet6 (Ubuntu Jammy) Status: New => In Progress ** Changed in: dotnet6 (Ubuntu Mantic) 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/2060259 Title: New upstream microrelease .NET 6.0.29 and SDK 6.0.129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2060259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060259] Re: New upstream microrelease .NET 6.0.29 and SDK 6.0.129
** Changed in: dotnet6 (Ubuntu Jammy) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Changed in: dotnet6 (Ubuntu Mantic) Assignee: (unassigned) => Dominik Viererbe (dviererbe) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060259 Title: New upstream microrelease .NET 6.0.29 and SDK 6.0.129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2060259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060261] [NEW] New upstream microrelease .NET 8.0.4 and SDK 8.0.104
Public bug reported: [Impact] * This correspond to an upcoming upstream microrelease (Microsoft Patch Tuesday microrelease). * It is beneficial for our latest LTS users to have access to the latest .NET stack. * This update is bundled with minor fixes: - updates Canonical support information - fixes/adds version parsing edge cases [Test Case] * The package should build successfully in noble-proposed, mantic- proposed and jammy-proposed. * The packages should be installable on noble, mantic and jammy on amd64 and arm64 architectures. * Autopackage tests should pass. * The usual manual tests that have been seen in the previous microreleases LP: #2057982 (see Test Case section there). Note: The need for manual testing is largely reduced since the last SRU, because the autopkgtests improvements far exceeds the coverage provided by the mentioned manual test plans. [Regression Potential] * Upstream tests are usually satisfactory, but there is always a risk of something breaking. [Other] * 8.0.4 is the version number of the .NET Runtime and 8.0.104 is the version number of the .NET SDK. The package version only refers to the SDK version number. * We are only building the 8.0.1xx feature band, because this is the only feature band that allows to be build from source. See explanation of feature bands: https://learn.microsoft.com/en-us/dotnet/core/releases-and-support#feature-bands-sdk-only * Overview of how dotnet is versioned: https://learn.microsoft.com/en- us/dotnet/core/versions/ ** Affects: dotnet8 (Ubuntu) Importance: Undecided Assignee: Dominik Viererbe (dviererbe) Status: In Progress ** Affects: dotnet8 (Ubuntu Jammy) Importance: Undecided Assignee: Dominik Viererbe (dviererbe) Status: In Progress ** Affects: dotnet8 (Ubuntu Mantic) Importance: Undecided Assignee: Dominik Viererbe (dviererbe) Status: In Progress ** Affects: dotnet8 (Ubuntu Noble) Importance: Undecided Assignee: Dominik Viererbe (dviererbe) Status: In Progress ** Also affects: dotnet8 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: dotnet8 (Ubuntu Noble) Importance: Undecided Assignee: Dominik Viererbe (dviererbe) Status: In Progress ** Also affects: dotnet8 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: dotnet8 (Ubuntu Mantic) Status: New => In Progress ** Changed in: dotnet8 (Ubuntu Jammy) Status: New => In Progress ** Changed in: dotnet8 (Ubuntu Mantic) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Changed in: dotnet8 (Ubuntu Jammy) Assignee: (unassigned) => Dominik Viererbe (dviererbe) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060261 Title: New upstream microrelease .NET 8.0.4 and SDK 8.0.104 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet8/+bug/2060261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023531] Re: [MIR] dotnet6
As discussed in the MIR meeting I created a dotnet8 MIR bug; see LP: #2060056 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023531 Title: [MIR] dotnet6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2023531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060056] [NEW] [MIR] dotnet8
Public bug reported: This is a follow up to the dotnet6 MIR (see LP: #2023531). We would like to have dotnet8 in main too, which was already discussed during the dotnet6 MIR (see comment 13 [1]). The dotnet8 package is structurally nearly identical. We do this deliberately to lower the maintenance burden. [Notable differences] * There is a single public upstream repository [2] to download all the source code from, therefore uscan can be used to produce the a orig tarball. Note: We do not use uscan, because its limitations adds overhead for our purposes (e.g. using the security repository by default, removing non-linux files, conditionaly including ms prebuilds for bootstraping, etc.). * The source package and it's binary packages have a different upstream version scheme (see spec FO127 [3]). * The source package produces additional binary packages, which include managed code debug symbols (packages with the name pattern *-dbg-8.0). See upstream issue [4] and PR [5]. * We no longer need a .git folder in the orig tarball thanks of upstream efforts. [1] https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2023531/comments/13 [2] https://github.com/dotnet/dotnet [3] https://docs.google.com/document/d/1xKaDHPC9QuxFOGjqK_oNmlurPr6mcaWMc0S-_IRE6A0/edit?usp=sharing [4] https://github.com/dotnet/source-build/issues/3621 [5] https://github.com/dotnet/installer/pull/17454 ** Affects: dotnet8 (Ubuntu) Importance: Undecided Status: New ** Description changed: This is a follow up to the dotnet6 MIR (see LP: #2023531). We would like to have dotnet8 in main too, which was already discussed during the dotnet6 MIR (see comment 13 [1]). The dotnet8 package is structurally nearly identical. We do this deliberately to lower the maintenance burden. [Notable differences] * There is a single public upstream repository [2] to download all the source code from, therefore uscan can be used to produce the a orig tarball. Note: We do not use uscan, because its limitations adds overhead for our purposes (e.g. using the security repository by default, removing non-linux files, conditionaly including ms prebuilds for bootstraping, etc.). * The source package and it's binary packages have a different upstream version scheme (see spec FO127 [3]). * The source package produces additional binary packages, which include managed code debug symbols (packages with the name pattern *-dbg-8.0). See upstream issue [4] and PR [5]. + * We no longer need a .git folder in the orig tarball thanks of upstream + efforts. [1] https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2023531/comments/13 [2] https://github.com/dotnet/dotnet [3] https://docs.google.com/document/d/1xKaDHPC9QuxFOGjqK_oNmlurPr6mcaWMc0S-_IRE6A0/edit?usp=sharing [4] https://github.com/dotnet/source-build/issues/3621 [5] https://github.com/dotnet/installer/pull/17454 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060056 Title: [MIR] dotnet8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet8/+bug/2060056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039097] Re: dotnet command suggested as coming from dotnet-host package
** Changed in: dotnet8 (Ubuntu) Status: New => Confirmed ** Changed in: dotnet7 (Ubuntu) Status: New => Confirmed ** Changed in: dotnet6 (Ubuntu) Status: New => Confirmed ** Changed in: dotnet6 (Ubuntu) Importance: Undecided => Low ** Changed in: dotnet7 (Ubuntu) Importance: Undecided => Low ** Changed in: dotnet8 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039097 Title: dotnet command suggested as coming from dotnet-host package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2039097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046535] Re: Improve installation instruction on missing runtime
** Changed in: dotnet6 (Ubuntu) Status: New => Confirmed ** Changed in: dotnet7 (Ubuntu) Status: New => Confirmed ** Changed in: dotnet8 (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/2046535 Title: Improve installation instruction on missing runtime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2046535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044550] Re: Remove dotnet6 & dotnet7 autopkgtest dependencies in noble
Note: The new autopkgtests made this issue invalid. It was valid before. ** Changed in: dotnet8 (Ubuntu Noble) 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/2044550 Title: Remove dotnet6 & dotnet7 autopkgtest dependencies in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet8/+bug/2044550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046133] Re: Backport .NET 8 to jammy
** Changed in: dotnet8 (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: dotnet8 (Ubuntu Jammy) 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/2046133 Title: Backport .NET 8 to jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet8/+bug/2046133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046241] Re: autopkgtest 013 is architecture specific
Note: The new autopkgtests made this issue invalid. It was valid before. ** Changed in: dotnet8 (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/2046241 Title: autopkgtest 013 is architecture specific To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet8/+bug/2046241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057699] Re: [SRU] New upstream microrelease .NET 6.0.28 and SDK 6.0.128
** Changed in: dotnet6 (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/2057699 Title: [SRU] New upstream microrelease .NET 6.0.28 and SDK 6.0.128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2057699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057982] Re: [SRU] Is a ca-certificates dependency missing?
** Changed in: dotnet6 (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: dotnet7 (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/2057982 Title: [SRU] Is a ca-certificates dependency missing? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2057982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023531] Re: [MIR] dotnet6
> 17:46:03 - cpaelzer: just tests to be added, then it is good > 17:46:08 - cpaelzer: long things are finally good (See https://irclogs.ubuntu.com/2023/11/28/%23ubuntu-meeting.html#t15:46) The latest updates (LP: #2057982, #2057699) added minimal build time tests and extended the autopkgtest coverage by integrating the RedHat test suite. Therefore, the final requirement for the .NET MIR should be fulfilled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023531 Title: [MIR] dotnet6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2023531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046369] Re: dh-make-golang 0.6.0-2 fails to build from source
For some reason someone synced 0.7.0-1 and golang-github-google-go- github 60.0.0-1, so... my merge is no longer needed and this problem is solved. ** Changed in: dh-make-golang (Ubuntu) Status: In Progress => Fix Released ** Changed in: dh-make-golang (Ubuntu) Assignee: (unassigned) => Dominik Viererbe (dviererbe) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046369 Title: dh-make-golang 0.6.0-2 fails to build from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-make-golang/+bug/2046369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057982] Re: [SRU] Is a ca-certificates dependency missing?
The dotnet6 packages are handled in another SRU (see LP: #2057699). The regression reported above were caused by autopkgtest running older package versions with known to fail autopkgtests. This is one of the reason why this SRU caries autopkgtest changes. Therefore the above reported regressions can safely be ignored. dotnet8/noble fails to build because of clang defaults to version 18 in proposed: https://launchpad.net/ubuntu/+source/dotnet8/8.0.103-8.0.3-0ubuntu1 Mateus Rodrigues de Morais (~mateus-morais) already applied a patch to fix this in a PPA and tests pass, but we need to get this uploaded. Handling noble uploads is not part of the SRU anyway. Running autopkgtests against the other latests packages passes: 7.0.117-0ubuntu1~22.04.2 jammy/amd64: [1] 7.0.117-0ubuntu1~22.04.2 jammy/arm64: [2] 7.0.117-0ubuntu1~23.10.2 mantic/amd64: [3] 7.0.117-0ubuntu1~23.10.2 mantic/arm64: [4] 8.0.103-8.0.3-0ubuntu1~22.04.2 jammy/amd64: [5] 8.0.103-8.0.3-0ubuntu1~22.04.2 jammy/arm64: [6] 8.0.103-8.0.3-0ubuntu1~23.10.2 mantic/amd64:[7] 8.0.103-8.0.3-0ubuntu1~23.10.2 mantic/arm64:[8] [1] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/d/dotnet7/20240327_005240_f5428@/log.gz [2] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/d/dotnet7/20240327_015841_0299a@/log.gz [3] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/d/dotnet7/20240327_005627_40d31@/log.gz [4] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/arm64/d/dotnet7/20240327_030204_8a006@/log.gz [5] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/d/dotnet8/20240327_012456_95865@/log.gz [6] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/d/dotnet8/20240327_014048_5d7ca@/log.gz [7] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/d/dotnet8/20240327_013827_7ed88@/log.gz [8] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/arm64/d/dotnet8/20240327_025047_e55ac@/log.gz ** Tags removed: verification-needed verification-needed-jammy verification-needed-mantic ** Tags added: verification-done verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057982 Title: [SRU] Is a ca-certificates dependency missing? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2057982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057699] Re: [SRU] New upstream microrelease .NET 6.0.28 and SDK 6.0.128
The regression reported above were caused by autopkgtest running older package versions with known to fail autopkgtests. This is one of the reason why this SRU caries autopkgtest changes. Therefore the above reported regressions can safely be ignored. Running autopkgtests against the new packages passes: * 6.0.128-0ubuntu1~22.04.2 jammy/amd64: [1] * 6.0.128-0ubuntu1~22.04.2 jammy/arm64: [2] * 6.0.128-0ubuntu1~23.10.2 mantic/amd64: [3] * 6.0.128-0ubuntu1~23.10.2 mantic/arm64: [4] [1] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/d/dotnet6/20240327_004441_196db@/log.gz [2] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/d/dotnet6/20240327_020912_3f637@/log.gz [3] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/d/dotnet6/20240327_005258_533e7@/log.gz [4] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/arm64/d/dotnet6/20240327_120126_9732e@/log.gz ** Tags removed: block-proposed-jammy block-proposed-mantic verification-needed verification-needed-jammy verification-needed-mantic ** Tags added: verification-done verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057699 Title: [SRU] New upstream microrelease .NET 6.0.28 and SDK 6.0.128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2057699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046369] Re: dh-make-golang 0.6.0-2 fails to build from source
Rebuilding bettercap, distrobuilder, golang-github-weppos-publicsuffix- go against golang-github-google-go-github (60.0.0-1) resulted in build failures :/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046369 Title: dh-make-golang 0.6.0-2 fails to build from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-make-golang/+bug/2046369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046369] Re: dh-make-golang 0.6.0-2 fails to build from source
$ reverse-depends --release noble --arch=source src:golang-github-google-go-github Reverse-Build-Depends = * bettercap (for golang-github-google-go-github-dev) * dh-make-golang(for golang-github-google-go-github-dev) * distrobuilder (for golang-github-google-go-github-dev) * golang-github-weppos-publicsuffix-go * golang-github-zitadel-oidc(for golang-github-google-go-github-dev) $ reverse-depends --release noble --arch=source src:bettercap No reverse dependencies found $ reverse-depends --release noble --arch=source src:dh-make-golang No reverse dependencies found $ reverse-depends --release noble --arch=source src:distrobuilder No reverse dependencies found $ reverse-depends --release noble --arch=source src:golang-github-weppos-publicsuffix-go No reverse dependencies found $ reverse-depends --release noble --arch=source src:golang-github-zitadel-oidc Reverse-Build-Depends = * incus (for golang-github-zitadel-oidc-dev) $ reverse-depends --release noble --arch=source src:incus Reverse-Build-Depends = * distrobuilder (for golang-github-lxc-incus-dev) $ reverse-depends --release noble --arch=source src:dh-make-golang No reverse dependencies found Note: I have the feeling that the reverse-depends output for src:dh- make-golang is just empty, because packages buikld depend on the Provides: dh-sequence-golang :/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046369 Title: dh-make-golang 0.6.0-2 fails to build from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-make-golang/+bug/2046369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046369] Re: dh-make-golang 0.6.0-2 fails to build from source
** Changed in: dh-make-golang (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/2046369 Title: dh-make-golang 0.6.0-2 fails to build from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-make-golang/+bug/2046369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046369] Re: dh-make-golang 0.6.0-2 fails to build from source
I got a passing build of dh-make-golang - 0.7.0-1 with golang-github- google-go-github 60.0.0-1. See [1]. Actions to take: 1. Sync golang-github-google-go-github 60.0.0-1 from debian unstable 2. Sync dh-make-golang - 0.7.0-1 from debian unstable [1] https://launchpad.net/~dviererbe/+archive/ubuntu/lp2046369/+packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046369 Title: dh-make-golang 0.6.0-2 fails to build from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-make-golang/+bug/2046369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057982] Re: [SRU] Is a ca-certificates dependency missing?
This is not a real regression. The autopkgtest cloud was running older package versions that do miss fixes for the autopkgtest suite. Therefore the failure is to be expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057982 Title: [SRU] Is a ca-certificates dependency missing? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2057982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058766] Re: .NET 8 fails to build with clang 18
We will temporarily revert to glibc-17 and fix the issue with future upstream releases. Rationale: We want to Bootstrap .NET for S390X before 24.04 GA, but the 24.04 Beta and Release Candidate dates are getting closer and Archive Admins get progressively busier. Therefore, a working .NET version has currently higher priority than fixing this issue. ** Also affects: dotnet8 (Ubuntu Noble) Importance: Low Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058766 Title: .NET 8 fails to build with clang 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet8/+bug/2058766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058766] [NEW] .NET 8 fails to build with clang 18
Public bug reported: .NET 8 (8.0.103-8.0.3-0ubuntu1) fails to build on noble in -proposed. The reason for this is that llvm-defaults switched to version 18, see [1]. Upstream Issue: [2] [1] https://launchpad.net/ubuntu/+source/llvm-defaults/0.59~exp1 [2] https://github.com/dotnet/runtime/issues/99825 ** Affects: dotnet8 (Ubuntu) Importance: Low Status: Confirmed ** Affects: dotnet8 (Ubuntu Noble) Importance: Low Status: Confirmed ** Tags: foundations-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058766 Title: .NET 8 fails to build with clang 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet8/+bug/2058766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058746] [NEW] Support information in README.source is outdated
Public bug reported: The debian/README.source file still contains the old Ubuntu support policy, which is outdated. ** Affects: dotnet6 (Ubuntu) Importance: Low Assignee: Dominik Viererbe (dviererbe) Status: Confirmed ** Affects: dotnet7 (Ubuntu) Importance: Low Assignee: Dominik Viererbe (dviererbe) Status: Confirmed ** Affects: dotnet8 (Ubuntu) Importance: Low Assignee: Dominik Viererbe (dviererbe) Status: Confirmed ** Also affects: dotnet7 (Ubuntu) Importance: Undecided Status: New ** Also affects: dotnet8 (Ubuntu) Importance: Undecided Status: New ** Changed in: dotnet7 (Ubuntu) Status: New => Confirmed ** Changed in: dotnet8 (Ubuntu) Status: New => Confirmed ** Changed in: dotnet7 (Ubuntu) Importance: Undecided => Low ** Changed in: dotnet8 (Ubuntu) Importance: Undecided => Low ** Changed in: dotnet7 (Ubuntu) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Changed in: dotnet8 (Ubuntu) Assignee: (unassigned) => Dominik Viererbe (dviererbe) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058746 Title: Support information in README.source is outdated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2058746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058732] [NEW] Manpages don't mention that dpkg-genchanges generates Launchpad-Bugs-Fixed field
Public bug reported: The dpkg-genchanges(1) [1] does not mention that a Launchpad-Bugs-Fixed field is generated if the -v flag is specified. https://manpages.ubuntu.com/manpages/noble/en/man1/dpkg- genchanges.1.html ** Affects: dpkg (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/2058732 Title: Manpages don't mention that dpkg-genchanges generates Launchpad-Bugs- Fixed field To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/2058732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057699] Re: [SRU] New upstream microrelease .NET 6.0.28 and SDK 6.0.128
** Changed in: dotnet6 (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/2057699 Title: [SRU] New upstream microrelease .NET 6.0.28 and SDK 6.0.128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2057699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057982] Re: [SRU] Is a ca-certificates dependency missing?
** Changed in: dotnet6 (Ubuntu) Status: Invalid => Fix Committed ** Changed in: dotnet7 (Ubuntu) Status: Invalid => 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/2057982 Title: [SRU] Is a ca-certificates dependency missing? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2057982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057982] Re: [SRU] Is a ca-certificates dependency missing?
** Summary changed: - Is a ca-certificates dependency missing? + [SRU] Is a ca-certificates dependency missing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057982 Title: [SRU] Is a ca-certificates dependency missing? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2057982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046369] Re: dh-make-golang 0.6.0-2 fails to build from source
I am currently looking into this on my +1 shift. I already tried to disable lto, because of the warning: > dh_auto_build: warning: LTO optimize is enable in buildflags. But cgo doesn't > support it. LTO flags will > be stripped in cgo. Unfortunately this did not solve it and I have no experience with go, so I may have to ask @zhsj what could cause the error: cannot find package "golang.org/x/tools/go/vcs" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046369 Title: dh-make-golang 0.6.0-2 fails to build from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-make-golang/+bug/2046369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058410] Re: lbcd fails to migrate from 3.5.2-3 to 3.5.2-4
Upstream Bug: https://github.com/rra/lbcd/issues/1 Note: Upstream project is no longer maintained. ** Bug watch added: github.com/rra/lbcd/issues #1 https://github.com/rra/lbcd/issues/1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058410 Title: lbcd fails to migrate from 3.5.2-3 to 3.5.2-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lbcd/+bug/2058410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058410] Re: lbcd fails to migrate from 3.5.2-3 to 3.5.2-4
> You should also consider forwarding the patch to Debian My rationale was that debian does not enable lto and therefore does not need that change. > and raising the LTO issue with the upstream project I will do that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058410 Title: lbcd fails to migrate from 3.5.2-3 to 3.5.2-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lbcd/+bug/2058410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058410] Re: lbcd fails to migrate from 3.5.2-3 to 3.5.2-4
Don't ask me why, but disabling lto (link time optimization) solves the failure. Passing build in a PPA [1]. Download source package: $ dget https://launchpad.net/~dviererbe/+archive/ubuntu/lbcd/+sourcefiles/lbcd/3.5.2-4ubuntu1~ppa1/lbcd_3.5.2-4ubuntu1~ppa1.dsc [1] https://launchpad.net/~dviererbe/+archive/ubuntu/lbcd ** Changed in: lbcd (Ubuntu) Status: New => In Progress ** Changed in: lbcd (Ubuntu) Assignee: (unassigned) => Dominik Viererbe (dviererbe) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058410 Title: lbcd fails to migrate from 3.5.2-3 to 3.5.2-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lbcd/+bug/2058410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058410] [NEW] lbcd fails to migrate from 3.5.2-3 to 3.5.2-4
Public bug reported: The build failure is caused by a failing build time test. The failing assertion is at tests/util/network/server-t.c:482 [1]. [1] https://git.launchpad.net/ubuntu/+source/lbcd/tree/tests/util/network/server-t.c?h=applied/3.5.2-4=4d9a1643b4f82b247fe4b5ffc287dc044014a2a0#n482 ** Affects: lbcd (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/2058410 Title: lbcd fails to migrate from 3.5.2-3 to 3.5.2-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lbcd/+bug/2058410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057982] Re: Is a ca-certificates dependency missing?
** Description changed: + [Impact] + + * This fix improves the .NET developer experience with Ubuntu container + images. + + * This update is bundled with quality assurance improvements. +See section other for more details. + + [Test Case] + + * The packages should build successfully in the -proposed pocket of + their target release & architecture. + + * The packages should be installable on their target release & + architechture. + + * Autopkgtests should pass. + + * The usual manual tests that have been seen in previous microreleases +LP: #1996499, #1983380, #2011807 (see Test Case section there). + +Note: The need for manual testing is largely reduced since the last SRU, + because the autopkgtests improvements far exceeds the coverage + provided by the mentioned manual test plans. + + [Regression Potential] + + * Minimal, because this update just adds a dependency on ca-certificate + (which is widely used anyway) and increases the test coverage, but there + is always a risk of breaking something. + + [Other] + + * The dotnet6 packages SRU are handled by another SRU (currently in progress). +See LP: #2057699 + + * The quality assurance improvements include: +- Adding build time smoke test that fail the build if fundamental flaws + of the build artifacts are detected. +- Using the RedHat test suite which significantly increases the test coverage. + + * dotnet7 were removed from noble. +See LP: #2044511 for details. + + * Original Bug Report: + I was doing some (very basic) testing on Jammy. I didn't get the behavior I was expecting. I installed `ca-certificates` and the problem was resolved. I'm wondering if we're just missing having `ca- certificates` as a dependency. Observed behavior: https://gist.github.com/richlander/27c03db34b3f06fd044c611562def589 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057982 Title: Is a ca-certificates dependency missing? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2057982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058354] [NEW] Enabling FIPS breaks password hashing
Public bug reported:
We are running x11vnc 0.9.16-8 on a FIPS enabled Ubuntu 22.04 with
libvncserver1 0.9.13+dfsg-3build2 and libssl3 3.0.2-0ubuntu1.12+Fips1.
With the fips=1 kernel parameter enabling FIPS, it seems that the
password hashing is broken and only a clear text password is written:
$ cat /proc/sys/crypto/fips_enabled
1
$ x11vnc -storepasswd Abc /tmp/.testpw && cat /tmp/.testpw
stored passwd in file: /tmp/.testpw
Abc
Any connection attempt fails with a 'password check failed!' error.
Running x11vnc with
sudo /usr/bin/x11vnc -auth guess -forever -localhost -loop -noxdamage
-repeat -rfbauth /root/.vncpasswd -rfbport 5900 -shared
logs the following:
Got connection from client 127.0.0.1
0 other clients
Normal socket connection
check_access: client 127.0.0.1 matches host 127.0.0.1
incr accepted_client=1 for 127.0.0.1:54968 sock=10
Client Protocol Version 3.8
Protocol version sent 3.8, using 3.8
rfbProcessClientSecurityType: executing handler for type 2
Couldn't read password file: /root/.vncpasswd
rfbAuthProcessClientMessage: password check failed
rfbClientSendString("password check failed!")
client_count: 0
Client 127.0.0.1 gone
By turning off FIPS with fips=0 in the kernel, it works as expected:
$ cat /proc/sys/crypto/fips_enabled
0
$ x11vnc -storepasswd Abc /tmp/.testpw && cat /tmp/.testpw
stored passwd in file: /tmp/.testpw
�97l܊
** Affects: x11vnc (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/2058354
Title:
Enabling FIPS breaks password hashing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11vnc/+bug/2058354/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057982] Re: Is a ca-certificates dependency missing?
.NET 6 == PPA: https://launchpad.net/~dviererbe/+archive/ubuntu/dotnet6-0-128-ppa5 Mantic -- [download] $ dget https://launchpad.net/~dviererbe/+archive/ubuntu/dotnet6-0-128-ppa5/+sourcefiles/dotnet6/6.0.128-0ubuntu1~23.10.2~ppa/dotnet6_6.0.128-0ubuntu1~23.10.2~ppa.dsc [autopkgtest] - amd64: pass logs: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-dviererbe-dotnet6-0-128-ppa5/mantic/amd64/d/dotnet6/20240319_040337_effa4@/log.gz - arm64: pass logs: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-dviererbe-dotnet6-0-128-ppa5/mantic/arm64/d/dotnet6/20240319_074127_d35da@/log.gz Jammy - [download] $ dget https://launchpad.net/~dviererbe/+archive/ubuntu/dotnet6-0-128-ppa5/+sourcefiles/dotnet6/6.0.128-0ubuntu1~22.04.2~ppa/dotnet6_6.0.128-0ubuntu1~22.04.2~ppa.dsc [autopkgtest] - amd64: pass logs: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-dviererbe-dotnet6-0-128-ppa5/jammy/amd64/d/dotnet6/20240319_035721_f9088@/log.gz - arm64: waiting for build .NET 7 == PPA: https://launchpad.net/~dviererbe/+archive/ubuntu/7.0.117-7.0.17-ppa3 Mantic -- [download] $ dget https://launchpad.net/~dviererbe/+archive/ubuntu/7.0.117-7.0.17-ppa3/+sourcefiles/dotnet7/7.0.117-0ubuntu1~23.10.2~ppa/dotnet7_7.0.117-0ubuntu1~23.10.2~ppa.dsc [autopkgtest] - amd64: pass logs: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-dviererbe-7.0.117-7.0.17-ppa3/mantic/amd64/d/dotnet7/20240319_030315_d5d92@/log.gz - arm64: pass logs: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-dviererbe-7.0.117-7.0.17-ppa3/mantic/arm64/d/dotnet7/20240319_005057_9a5ea@/log.gz Jammy - [download] $ dget https://launchpad.net/~dviererbe/+archive/ubuntu/7.0.117-7.0.17-ppa3/+sourcefiles/dotnet7/7.0.117-0ubuntu1~22.04.2~ppa/dotnet7_7.0.117-0ubuntu1~22.04.2~ppa.dsc [autopkgtest] - amd64: pass logs: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-dviererbe-7.0.117-7.0.17-ppa3/jammy/amd64/d/dotnet7/20240319_025559_451cf@/log.gz - arm64: pass logs: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-dviererbe-7.0.117-7.0.17-ppa3/jammy/arm64/d/dotnet7/20240319_014502_cc889@/log.gz .NET 8 == PPA: https://launchpad.net/~dviererbe/+archive/ubuntu/8.0.103-8.0.3-ppa5 Mantic -- [download] $ dget https://launchpad.net/~dviererbe/+archive/ubuntu/8.0.103-8.0.3-ppa5/+sourcefiles/dotnet8/8.0.103-8.0.3-0ubuntu1~23.10.2~ppa/dotnet8_8.0.103-8.0.3-0ubuntu1~23.10.2~ppa.dsc [autopkgtest] - amd64: pass logs: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-dviererbe-8.0.103-8.0.3-ppa5/mantic/amd64/d/dotnet8/20240319_072708_e25b9@/log.gz - arm64: waiting Jammy - [download] $ dget https://launchpad.net/~dviererbe/+archive/ubuntu/8.0.103-8.0.3-ppa5/+sourcefiles/dotnet8/8.0.103-8.0.3-0ubuntu1~22.04.2~ppa/dotnet8_8.0.103-8.0.3-0ubuntu1~22.04.2~ppa.dsc [autopkgtest] - amd64: pass logs: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-dviererbe-8.0.103-8.0.3-ppa5/jammy/amd64/d/dotnet8/20240319_075425_0f6e6@/log.gz - arm64: waiting Noble - PPA: https://launchpad.net/~dviererbe/+archive/ubuntu/8.0.103-8.0.3-ppa6 [download} $ dget https://launchpad.net/~dviererbe/+archive/ubuntu/8.0.103-8.0.3-ppa6/+sourcefiles/dotnet8/8.0.103-8.0.3-0ubuntu1~ppa/dotnet8_8.0.103-8.0.3-0ubuntu1~ppa.dsc [autopkgtest] - amd64: pass logs: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dviererbe-8.0.103-8.0.3-ppa6/noble/amd64/d/dotnet8/20240319_083738_6@/log.gz - arm64: pass logs: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dviererbe-8.0.103-8.0.3-ppa6/noble/arm64/d/dotnet8/20240319_032720_e0776@/log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057982 Title: Is a ca-certificates dependency missing? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2057982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057699] Re: [SRU] New upstream microrelease .NET 6.0.28 and SDK 6.0.128
** Tags added: block-proposed-jammy block-proposed-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057699 Title: [SRU] New upstream microrelease .NET 6.0.28 and SDK 6.0.128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2057699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057699] Re: [SRU] New upstream microrelease .NET 6.0.28 and SDK 6.0.128
I just confirmed LP: #2057982 which affects this SRU, because I would like to include the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057699 Title: [SRU] New upstream microrelease .NET 6.0.28 and SDK 6.0.128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2057699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057982] Re: Is a ca-certificates dependency missing?
I replicated this with ubuntu:jammy and ubuntu:mantic also with dotnet8. CLI interactions like `dotnet new global.json --search` are also affected by this, even without installing a second SDK. I think we did not encounter this issue so far, because our test infrastructure installs ubuntu-minimal which installs ca-certificates. The impact should be limited to docker images which do not ship with ubuntu-minimal. I will prepare a bug fix, that adds ca-certificates to dotnet-sdk-6.0, dotnet-sdk-7.0 and dotnet-sdk-8.0. Still I do not fully understand why the restore action only fails when restoring projects with a lower SDK version :/ ** Also affects: dotnet6 (Ubuntu) Importance: Undecided Status: New ** Also affects: dotnet8 (Ubuntu) Importance: Undecided Status: New ** Also affects: dotnet6 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: dotnet7 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: dotnet8 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: dotnet6 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: dotnet7 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: dotnet8 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: dotnet6 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: dotnet7 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: dotnet8 (Ubuntu Noble) Importance: Undecided Status: New ** No longer affects: dotnet6 (Ubuntu Noble) ** No longer affects: dotnet7 (Ubuntu Noble) ** Changed in: dotnet6 (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: dotnet6 (Ubuntu Jammy) Status: New => In Progress ** Changed in: dotnet6 (Ubuntu Jammy) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Changed in: dotnet6 (Ubuntu Mantic) Importance: Undecided => Low ** Changed in: dotnet6 (Ubuntu Mantic) Status: New => In Progress ** Changed in: dotnet6 (Ubuntu Mantic) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Changed in: dotnet6 (Ubuntu) Importance: Undecided => Low ** Changed in: dotnet6 (Ubuntu) Status: New => In Progress ** Changed in: dotnet6 (Ubuntu) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Changed in: dotnet7 (Ubuntu) Importance: Undecided => Low ** Changed in: dotnet7 (Ubuntu) Status: New => In Progress ** Changed in: dotnet7 (Ubuntu) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Changed in: dotnet7 (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: dotnet7 (Ubuntu Jammy) Status: New => In Progress ** Changed in: dotnet7 (Ubuntu Jammy) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Changed in: dotnet7 (Ubuntu Mantic) Importance: Undecided => Low ** Changed in: dotnet7 (Ubuntu Mantic) Status: New => In Progress ** Changed in: dotnet7 (Ubuntu Mantic) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Changed in: dotnet8 (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: dotnet8 (Ubuntu Jammy) Status: New => In Progress ** Changed in: dotnet8 (Ubuntu Jammy) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Changed in: dotnet8 (Ubuntu Mantic) Importance: Undecided => Low ** Changed in: dotnet8 (Ubuntu Mantic) Status: New => In Progress ** Changed in: dotnet8 (Ubuntu Mantic) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Changed in: dotnet8 (Ubuntu Noble) Importance: Undecided => Low ** Changed in: dotnet8 (Ubuntu Noble) Status: New => In Progress ** Changed in: dotnet8 (Ubuntu Noble) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057982 Title: Is a ca-certificates dependency missing? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2057982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057699] Re: [SRU] New upstream microrelease .NET 6.0.28 and SDK 6.0.128
** Description changed: [Impact] - * This correspond to an upstream microrelease (Microsoft Patch Tuesday + * This correspond to an upstream microrelease (Microsoft Patch Tuesday microrelease). See: https://github.com/dotnet/source- build/discussions/4211 - * It is beneficial for our latest LTS users to have access to the + * It is beneficial for our latest LTS users to have access to the latest .NET stack. + + * This update is bundled with quality assurance improvements. +See section other for more details. [Test Case] - * The package should build successfully in mantic-proposed and jammy- + * The package should build successfully in mantic-proposed and jammy- proposed. - * The packages should be installable on mantic and jammy on amd64 and - arm64 architectures. + * The packages should be installable on mantic and jammy +on amd64 and arm64architectures. - * Autopackage tests should pass. (Note: this release coincides with - enhanced autopkgtests ) + * Autopackage tests should pass. - * The usual manual tests that have been seen in the previous microreleases [1] [2] [3] (see Test Case section there). -Note: The need for manual testing is largely reduced since the last SRU, because the autopkgtests nowadays cover a broad set of scenarios, that far exceeds the mentioned manual test plans. + * The usual manual tests that have been seen in the previous microreleases +LP: #1996499, #1983380, #2011807 (see Test Case section there). + + + Note: The need for manual testing is largely reduced since the last SRU, + because the autopkgtests improvements far exceeds the coverage + provided by the mentioned manual test plans. [Regression Potential] - * Upstream tests are usually satisfactory, but there is always a risk + * Upstream tests are usually satisfactory, but there is always a risk of something breaking. [Other] - * 6.0.28 is the version number of the .NET Runtime and 6.0.128 is the - version number of the .NET SDK. The package version only refers to the - SDK version number. + * The quality assurance improvements include: + - Adding build time smoke test that fail the build if fundamental flaws + of the build artifacts are detected. + - Using the RedHat test suite which significantly increases the test coverage. - Although the dotnet SDK 6.0.115 is part of the dotnet 6.0.15 release we - refer to the release as 6.0.115, because source build only supports the - 6.0.1xx feature band. (See https://github.com/dotnet/source- - build#support) + * dotnet6 was removed from the current development release. + See LP: #2044511 for details. - * We are only building the 6.0.1xx feature band, because this is the - only feature band that allows to be build from source. See explanation - of feature bands: https://learn.microsoft.com/en- - us/dotnet/core/releases-and-support#feature-bands-sdk-only + * 6.0.28 is the version number of the .NET Runtime and 6.0.128 is the version + number of the .NET SDK. The package version only refers to the SDK version + number. + + * We are only building the 6.0.1xx feature band, because this is the only + feature band that allows to be build from source. See explanation of feature + bands: https://learn.microsoft.com/en-us/dotnet/core/releases-and-support#feature-bands-sdk-only * Overview of how dotnet is versioned: https://learn.microsoft.com/en- us/dotnet/core/versions/ - - [1] https://launchpad.net/bugs/1996499 - [2] https://launchpad.net/bugs/1983380 - [3] https://launchpad.net/bugs/2011807 ** Description changed: [Impact] - * This correspond to an upstream microrelease (Microsoft Patch Tuesday - microrelease). See: https://github.com/dotnet/source- - build/discussions/4211 + * This correspond to an upstream microrelease (Microsoft Patch Tuesday microrelease). +See: https://github.com/dotnet/source-build/discussions/4211 * It is beneficial for our latest LTS users to have access to the latest .NET stack. - * This update is bundled with quality assurance improvements. -See section other for more details. + * This update is bundled with quality assurance improvements. + See section other for more details. [Test Case] * The package should build successfully in mantic-proposed and jammy- proposed. * The packages should be installable on mantic and jammy -on amd64 and arm64architectures. + on amd64 and arm64architectures. * Autopackage tests should pass. * The usual manual tests that have been seen in the previous microreleases -LP: #1996499, #1983380, #2011807 (see Test Case section there). - + LP: #1996499, #1983380, #2011807 (see Test Case section there). Note: The need for manual testing is largely reduced since the last SRU, - because the autopkgtests improvements far exceeds the coverage - provided by the mentioned manual test plans. +
[Bug 2057699] Re: [SRU] New upstream microrelease .NET 6.0.28 and SDK 6.0.128
Both build fine in a PPA https://launchpad.net/~dviererbe/+archive/ubuntu/dotnet6-0-128. Autopkgtest pass locally, but fail in the autopkgtest cloud, because they run out of disk space. I opened a merge proposal to add dotnet to big_packages: https://code.launchpad.net/~dviererbe/autopkgtest- cloud/+git/autopkgtest-package-configs/+merge/462296 To get the source packages: dotnet6/6.0.128-0ubuntu1~23.10.1: dget https://launchpad.net/~dviererbe/+archive/ubuntu/dotnet6-0-128/+sourcefiles/dotnet6/6.0.128-0ubuntu1~23.10.1/dotnet6_6.0.128-0ubuntu1~23.10.1.dsc dotnet6/6.0.128-0ubuntu1~22.04.1: dget https://launchpad.net/~dviererbe/+archive/ubuntu/dotnet6-0-128/+sourcefiles/dotnet6/6.0.128-0ubuntu1~22.04.1/dotnet6_6.0.128-0ubuntu1~22.04.1.dsc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057699 Title: [SRU] New upstream microrelease .NET 6.0.28 and SDK 6.0.128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2057699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057699] [NEW] [SRU] New upstream microrelease .NET 6.0.28 and SDK 6.0.128
Public bug reported: [Impact] * This correspond to an upstream microrelease (Microsoft Patch Tuesday microrelease). See: https://github.com/dotnet/source- build/discussions/4211 * It is beneficial for our latest LTS users to have access to the latest .NET stack. [Test Case] * The package should build successfully in mantic-proposed and jammy- proposed. * The packages should be installable on mantic and jammy on amd64 and arm64 architectures. * Autopackage tests should pass. (Note: this release coincides with enhanced autopkgtests ) * The usual manual tests that have been seen in the previous microreleases [1] [2] [3] (see Test Case section there). Note: The need for manual testing is largely reduced since the last SRU, because the autopkgtests nowadays cover a broad set of scenarios, that far exceeds the mentioned manual test plans. [Regression Potential] * Upstream tests are usually satisfactory, but there is always a risk of something breaking. [Other] * 6.0.28 is the version number of the .NET Runtime and 6.0.128 is the version number of the .NET SDK. The package version only refers to the SDK version number. Although the dotnet SDK 6.0.115 is part of the dotnet 6.0.15 release we refer to the release as 6.0.115, because source build only supports the 6.0.1xx feature band. (See https://github.com/dotnet/source- build#support) * We are only building the 6.0.1xx feature band, because this is the only feature band that allows to be build from source. See explanation of feature bands: https://learn.microsoft.com/en- us/dotnet/core/releases-and-support#feature-bands-sdk-only * Overview of how dotnet is versioned: https://learn.microsoft.com/en- us/dotnet/core/versions/ [1] https://launchpad.net/bugs/1996499 [2] https://launchpad.net/bugs/1983380 [3] https://launchpad.net/bugs/2011807 ** Affects: dotnet6 (Ubuntu) Importance: Undecided Assignee: Dominik Viererbe (dviererbe) Status: In Progress ** Affects: dotnet6 (Ubuntu Jammy) Importance: Undecided Assignee: Dominik Viererbe (dviererbe) Status: In Progress ** Affects: dotnet6 (Ubuntu Mantic) Importance: Undecided Assignee: Dominik Viererbe (dviererbe) Status: In Progress ** Also affects: dotnet6 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: dotnet6 (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: dotnet6 (Ubuntu Jammy) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Changed in: dotnet6 (Ubuntu Mantic) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Changed in: dotnet6 (Ubuntu) Status: New => In Progress ** Changed in: dotnet6 (Ubuntu Jammy) Status: New => In Progress ** Changed in: dotnet6 (Ubuntu Mantic) 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/2057699 Title: [SRU] New upstream microrelease .NET 6.0.28 and SDK 6.0.128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2057699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824530] Re: Heap Buffer Overflow in UzpPassword
I just looked in the wrong place (thanks ~juliank). The patch is also present in all supported Versions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1824530 Title: Heap Buffer Overflow in UzpPassword To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unzip/+bug/1824530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824530] Re: Heap Buffer Overflow in UzpPassword
The patch for this bug is present in the unzip package for focal, jammy, kinetic, lunar, mantic. The patch for this bug is NOT present in the unzip package for trusty, xenial, bionic. bionic reaches end of standard support this month, so we should set this to won't fix. BUT bionic is in extended security maintenance until April 2028 xenial is in extended security maintenance until April 2026 trusty is in extended security maintenance until April 2024 Because this is related to a CVE this should be covered by ESM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1824530 Title: Heap Buffer Overflow in UzpPassword To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unzip/+bug/1824530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970957] Re: suspend problem
Guys, can you resume your session by using the Ctrl+Alt+Fn key combo? E.g.: I have a similar problem where Ubuntu cannot resume from lock screen / dim screen. On screen lock the screen goes dark and then the monitor powers off. In this state mouse movements or key presses won't bring the lock screen back. To resume I have to use Ctrl+Alt+F1 and wait for the login screen to appear. Then I use Ctrl+Alt+F2 to switch back to the previous session, however I also have to move the mouse to bring back the lock screen. Only then I'm able to login again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970957 Title: suspend problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842320] Re: Out of Memory on boot with 5.2.0 kernel
Exactly the same problem with GRUB occurs on LG Gram 14 (2021) with Ubuntu 22.04. In my case it means that after upgrading Ubuntu from 21.10 to 22.04, GRUB no longer boots, showing "error: out of memory.". I had to boot another OS from USB which is not Ubuntu 22.04, because live image have the same problem. I`ve used the image of Ubuntu 20.04 LTS. CSM/UEFI and Secure boot enabled/disable - tried all and thats not related to this in any case. After chrooting and regenerating GRUB with GFXMODE set to 800x600, I could finally reach the stage of loading kernel and decrypting the disk. :) It still not booting due to another problems, but thats another case, not related to this problem. The real problem is that I cannot perform clean installation due to not booting USB live image of Ubuntu 22.04 with "error: out of memory.". For now I've tried to repack squashfs with GFXMODE=800x600 change applied and write that to USB stick, but for now without luck (still the same error) which is strange, because it helped in already installed Ubuntu 22.04. Maybe I missed something - I will dig into this later and let you know. I'm gonna also try @ybdjkfd fix. Also, its a little bit frustrating, because if something happens in the future with OS on my PC storage and it stops working, I can't revive it with USB stick with latest Ubuntu, because it's also not working. :) Keeping additional old OS versions on pendrives or specially prepared (with repacked squashfs) is not an ideal solution when sometimes "on the go" you just need to download the ISO. It generates unnecessary extra work, mounting/chrooting and systems juggling, so thats a real problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842320 Title: Out of Memory on boot with 5.2.0 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970585] Re: Logic for PermitRootLogin in config script is flipped
Oh, I did just see the explanation in the postinst and templates file: Template: openssh-server/permit-root-login Type: boolean Default: true Description: Disable SSH password authentication for root? ** Changed in: openssh (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/1970585 Title: Logic for PermitRootLogin in config script is flipped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970585] Re: Logic for PermitRootLogin in config script is flipped
** Description changed: In the config script of openssh-server, the debconf database is updated with the values that are read from sshd_config. But if I'm not mistaken the yes/no logic is flipped: if [ "$permit_root_login" = yes ]; then - db_set openssh-server/permit-root-login false + db_set openssh-server/permit-root-login false else - db_set openssh-server/permit-root-login true + db_set openssh-server/permit-root-login true fi Discovered this in openssh-server 7.6p1-4ubuntu0.5 on Ubuntu 18.04.5 - LTS. Checked that this still unchcanged in 8.9p1-3 on jammy. + LTS. Checked that this is still unchcanged in 8.9p1-3 on jammy. I marked this a vulnerability as this might lead to unintended flipped settings of permitting root to log in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970585 Title: Logic for PermitRootLogin in config script is flipped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970585] Re: Logic for PermitRootLogin in config script is flipped
** Information type changed from Private Security to Public Security ** Description changed: In the config script of openssh-server, the debconf database is updated with the values that are read from sshd_config. But if I'm not mistaken the yes/no logic is flipped: if [ "$permit_root_login" = yes ]; then - db_set openssh-server/permit-root-login false + db_set openssh-server/permit-root-login false else - db_set openssh-server/permit-root-login true + db_set openssh-server/permit-root-login true fi Discovered this in openssh-server 7.6p1-4ubuntu0.5 on Ubuntu 18.04.5 LTS. Checked that this still unchcanged in 8.9p1-3 on jammy. - I marked this a vulnerability as this might lead to unintend flipped + I marked this a vulnerability as this might lead to unintended flipped settings of permitting root to log in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970585 Title: Logic for PermitRootLogin in config script is flipped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965466] [NEW] [DEFENDER P10, Realtek ALC293, Mic, Internal] No sound at all
Public bug reported: auto-generated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mdb2244 F pulseaudio /dev/snd/controlC1: mdb2244 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 18 02:51:06 2022 InstallationDate: Installed on 2018-12-10 (1193 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Eingebautes Tongerät - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mdb2244 F pulseaudio /dev/snd/controlC1: mdb2244 F pulseaudio Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: No sound at all Title: [DEFENDER P10, Realtek ALC293, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 7.5 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05RME1 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH77Dx dmi.board.vendor: MEDION dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: N/A dmi.ec.firmware.release: 7.1 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RME1:bd08/29/2020:br7.5:efr7.1:svnMEDION:pnDEFENDERP10:pvrNotApplicable:rvnMEDION:rnNH77Dx:rvrNotApplicable:cvnMEDION:ct10:cvrN/A:skuML-21000930028862: dmi.product.family: Erazer dmi.product.name: DEFENDER P10 dmi.product.sku: ML-210009 30028862 dmi.product.version: Not Applicable dmi.sys.vendor: MEDION ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965466 Title: [DEFENDER P10, Realtek ALC293, Mic, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962626] Re: tracker-miner-fs-3 crashed with SIGABRT
*** This bug is a duplicate of bug 1962495 *** https://bugs.launchpad.net/bugs/1962495 might affect bugs: 1955758 1962495 1962623 1962624 1962626 1962630 1962633 I will add this text to all open bugs. affected parts: tracker-miner-fs-3 totem gvfsd-mtp udisksd background information: - installed 18.04 lts - dist-upgraded to 20.04 lts - back up before sending hardware for repair, got replacement hardware (with default rubbish) - restore on replaced hardware with -- modified filesystem (btrfs, dont remember previously used fs) and -- full-disk encryption (multiple luks2 partitions instead of home-only) - noticed that integrating grub-2.06 correctly (building package etc) would be too much effort - downgraded luks-headers from luks2 to luks1 to make it compatible with grub used in 20.04 - added grub-setup script to include cryptmount grub module etc. - got btrfs kernel warnings regularly - dist-upgraded to 22.04 lts (beta, late January) - still btrfs kernel warnings regularly [- many updates since, as to be expected.] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962626 Title: tracker-miner-fs-3 crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1962626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962624] Re: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected
*** This bug is a duplicate of bug 1955758 *** https://bugs.launchpad.net/bugs/1955758 might affect bugs: 1955758 1962495 1962623 1962624 1962626 1962630 1962633 I will add this text to all open bugs. affected parts: tracker-miner-fs-3 totem gvfsd-mtp udisksd background information: - installed 18.04 lts - dist-upgraded to 20.04 lts - back up before sending hardware for repair, got replacement hardware (with default rubbish) - restore on replaced hardware with -- modified filesystem (btrfs, dont remember previously used fs) and -- full-disk encryption (multiple luks2 partitions instead of home-only) - noticed that integrating grub-2.06 correctly (building package etc) would be too much effort - downgraded luks-headers from luks2 to luks1 to make it compatible with grub used in 20.04 - added grub-setup script to include cryptmount grub module etc. - got btrfs kernel warnings regularly - dist-upgraded to 22.04 lts (beta, late January) - still btrfs kernel warnings regularly [- many updates since, as to be expected.] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962624 Title: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1962624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962633] Re: tracker-miner-fs-3 crashed with SIGABRT
*** This bug is a duplicate of bug 1962495 *** https://bugs.launchpad.net/bugs/1962495 might affect bugs: 1955758 1962495 1962623 1962624 1962626 1962630 1962633 I will add this text to all open bugs. affected parts: tracker-miner-fs-3 totem gvfsd-mtp udisksd background information: - installed 18.04 lts - dist-upgraded to 20.04 lts - back up before sending hardware for repair, got replacement hardware (with default rubbish) - restore on replaced hardware with -- modified filesystem (btrfs, dont remember previously used fs) and -- full-disk encryption (multiple luks2 partitions instead of home-only) - noticed that integrating grub-2.06 correctly (building package etc) would be too much effort - downgraded luks-headers from luks2 to luks1 to make it compatible with grub used in 20.04 - added grub-setup script to include cryptmount grub module etc. - got btrfs kernel warnings regularly - dist-upgraded to 22.04 lts (beta, late January) - still btrfs kernel warnings regularly [- many updates since, as to be expected.] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962633 Title: tracker-miner-fs-3 crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1962633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953218] [NEW] package mysql-server-8.0 8.0.27-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
Public bug reported: just updating regularily with do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.27-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Dec 4 10:17:14 2021 ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic links: '/etc/mysql/my.cnf' MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: ['ntkonto', 'wikidb', 'ca-key.pem', 'server-key.pem', 'debian-5.7.flag', 'undo_002', 'da', 'WG@002dBiblio', 'horde2', 'nconf', 'mysql_dd_upgrade_info', 'undo_1_trunc.log', 'mysqld_safe.pid', 'server-cert.pem', 's9y_tk', 'ib_logfile1', 'darkman', 'webmoviedb', 'ca.pem', 'ib_logfile0', 'auto.cnf', 'netjuke', 'mysql_upgrade_info', 'horde', '#innodb_temp', 'undo_2_trunc.log', 'cpg', 'ib_buffer_pool', 'performance_schema', 'client-key.pem', 'diak', 'binlog.index', 'client-cert.pem', 'gallery2', 'pydio', 'ibtmp1', 'ibdata1', 'intranet', 'phpmyadmin', 'sys', '#ib_16384_1.dblwr', 'debian-5.6.flag', 'buerowg', 'public_key.pem', 'mysql', '#ib_16384_0.dblwr', 'ocb', 'private_key.pem', 'wikidb_hdm'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=0b33cf7f-bfbb-4b24-a021-f56d07d8b804 ro Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.27-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-12-04 (0 days ago) ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check 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/1953218 Title: package mysql-server-8.0 8.0.27-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1953218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943833] Re: Failed to update metadata for lvfs
I've been getting this on 20.04 in KDE's Discover application. When I just ran fwupdmgr refresh, it completed fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943833 Title: Failed to update metadata for lvfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1943833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
Identical problem. only that my machine is frozen after the nvidia error messages. Running Ubuntu 20.04 LTS / Nvidia driver 470.57.02 on Razer Blade 15 Advanced (2018) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1911055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946109] [NEW] touchpad is not wokring at all, does not get recognized
Public bug reported: Touchpad does not show after: cat /proc/bus/input/devices > ~/devices All drivers are up to date. Laptop is a: Fujitsu Lifebook U-7510 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 5 10:04:33 2021 InstallationDate: Installed on 2021-09-22 (13 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946109 Title: touchpad is not wokring at all, does not get recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1946109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946108] [NEW] touchpad is not wokring at all, does not get recognized
Public bug reported: Touchpad does not show after: cat /proc/bus/input/devices > ~/devices All drivers are up to date. Laptop is a: Fujitsu Lifebook U-7510 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 5 10:04:33 2021 InstallationDate: Installed on 2021-09-22 (13 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946108 Title: touchpad is not wokring at all, does not get recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1946108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944041] Re: ausweisapp2 package dependencies missing, starts without gui
added "misery" Andre Klitzing - hope I got the right person involved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944041 Title: ausweisapp2 package dependencies missing, starts without gui To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ausweisapp2/+bug/1944041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944041] [NEW] ausweisapp2 package dependencies missing, starts without gui
Public bug reported:
AusweisApp2 should provide a (interactive, graphical) welcome screen and
configuration dialog upon (at least first) startup.
This window does not pop up because components (qt-qml stuff) is not installed,
not depended upon.
There will be many linux users having trouble and switching to other
OSes / installations to get the identification with German ID cards (and
stay permits) going!
To fix this, the packages "qml-module-qtqml-models2 qml-module-qtquick-
controls qml-module-qtquick-controls2" (including dependencies, of
course) have to be installed.
However, I did not check further usage of the application, yet, ie if
there are further requirements they might pop up later in using the
application / dialogs.
AusweisApp2 (package ausweisapp2 version 1.20.0-1build1) does not open
the configuration dialog upon starting. In the Log (which is removed
when the application ends) lines like
UILoader::load(ui/base/UILoader.cpp:81):
Try to load UI plugin: "UIPlugInQml"
UILoader::load(ui/base/UILoader.cpp:89):
Load plugin:
QJsonObject({"IID":"governikus.UIPlugIn","MetaData":{"dependencies":[],"name":"UIPlugInQml"},"archreq":0,"className":"UIPlugInQml","debug":false,"version":330752})
...
W unknown(unknown:0) :
QQmlApplicationEngine failed to load component
W unknown(unknown:0) :
qrc:/qml/main.qml:29 module "QtQuick.Controls" is not installed
qrc:/qml/main.qml:30 module "QtGraphicalEffects" is not installed
qrc:/qml/main.qml:27 module "QtQml.Models" is not installed
qrc:/qml/main.qml:28 module "QtQuick" is not installed
...
...
UIPlugInQml::onQmlObjectCreated(ui/qml/UIPlugInQml.cpp:526):
QML engine initialization finished with fatal errors.
can be observed and the Dialog with greeting for first start and
configuration does not show up.
I tried many different "qml" packages, in the end was successful,
removed all of them (purge + autoremove), reinstalled (...) and got the
minimal set:
sudo apt install qml-module-qtqml-models2 qml-module-qtquick-controls
qml-module-qtquick-controls2
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ausweisapp2 1.20.0-1build1
ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133
Uname: Linux 5.4.0-84-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 18 14:03:56 2021
InstallationDate: Installed on 2018-12-10 (1012 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: ausweisapp2
UpgradeStatus: Upgraded to focal on 2020-04-25 (510 days ago)
** Affects: ausweisapp2 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944041
Title:
ausweisapp2 package dependencies missing, starts without gui
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ausweisapp2/+bug/1944041/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929854] Re: Vital and critical configuration files get overridden by system updates without warning
As to grub.cfg:
I set GRUB_TIMEOUT=5 in my /etc/default/grub, but the timeout for efi
was reset to 30 on every update. I didn't know that files in
/etc/default/grub.d are supposed to be changed, but I now changed
if [ \$grub_platform = efi ]; then
set timeout=${GRUB_RECORDFAIL_TIMEOUT:-30}
if [ x\$feature_timeout_style = xy ] ; then
set timeout_style=menu
fi
fi
in /etc/grub.d/00_header to ... GRUB_RECORDFAIL_TIMEOUT:-5 ... and hope
that this helps in the future.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929854
Title:
Vital and critical configuration files get overridden by system
updates without warning
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1929854/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929854] Re: Vital and critical configuration files get overridden by system updates without warning
As to sshd_config: I will, when the case arises again. Unfortunately, I don't use sshd in my boxes on a regular basis and so often discover only changes that possibly happened a long time ago. I remember a nasty change from "PasswordAuthentication no" to "#PasswordAuthentication yes", but honestly it was quite some time ago. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929854 Title: Vital and critical configuration files get overridden by system updates without warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1929854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931870] Re: [nouveau] System freezes several times per week, sometimes more than once per day
Thanks, this apparently solved the problem. I had to pin Font DPI down to 96 though, because the proprietary driver sets DPI must too high, which let to giant letters and a mismatch between applications respecting the DPI and those using a fixed 96 DPI anyway. ** Changed in: linux (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/1931870 Title: [nouveau] System freezes several times per week, sometimes more than once per day To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897523] Re: upgrade bug from 18.04 to 20.04; dpkg: error processing package ssmtp (--configure): installed ssmtp package post-installation script subprocess returned error exit status 2
Got the same issue. Is there any chance to solve this issue / bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897523 Title: upgrade bug from 18.04 to 20.04; dpkg: error processing package ssmtp (--configure): installed ssmtp package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ssmtp/+bug/1897523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897523] Re: upgrade bug from 18.04 to 20.04; dpkg: error processing package ssmtp (--configure): installed ssmtp package post-installation script subprocess returned error exit status 2
Here is my /var/lib/dpkg/info/ssmtp.config file.
set -e
. /usr/share/debconf/confmodule
if [ -f /etc/ssmtp/ssmtp.conf ]
then
for v in `grep -E
"^(root|mailhub|rewriteDomain|hostname|FromLineOverride)="
/etc/ssmtp/ssmtp.conf`
do
export $v
done
db_set ssmtp/root "$root"
if [ -n "$mailhub" ]
then
if [ `expr index "$mailhub" :` -ne 0 ]
then
db_set ssmtp/port "${mailhub#*:}"
db_set ssmtp/mailhub "${mailhub%:*}"
else
db_set ssmtp/port 25
db_set ssmtp/mailhub "$mailhub"
fi
fi
if [ -n "$rewriteDomain" ]
then
db_set ssmtp/rewritedomain "$rewriteDomain"
fi
if [ -n "$hostname" ]
then
db_set ssmtp/hostname "$hostname"
fi
if [ -n "$FromLineOverride" ]
then
if [ "$FromLineOverride" = "YES" ]
then
db_set ssmtp/fromoverride true
else
db_set ssmtp/fromoverride false
fi
fi
fi
db_input medium ssmtp/root || true
db_go
db_input medium ssmtp/mailhub || true
db_go
db_input low ssmtp/port || true
db_go
db_input medium ssmtp/rewritedomain || true
db_go
db_input low ssmtp/hostname || true
db_go
db_input medium ssmtp/fromoverride || true
db_go
# Program End
exit 0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897523
Title:
upgrade bug from 18.04 to 20.04; dpkg: error processing package ssmtp
(--configure): installed ssmtp package post-installation script
subprocess returned error exit status 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ssmtp/+bug/1897523/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931870] [NEW] System freezes several times per week, sometimes more than once per day
Public bug reported: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-55.62-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Jun 14 15:18:03 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297] InstallationDate: Installed on 2021-01-15 (150 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20QQS0KL13 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-55-generic root=UUID=35cef147-e021-4bdd-b8db-31a3192c8a6a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET38W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QQS0KL13 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: ZF211710 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN2NET38W(1.23):bd06/04/2020:br1.23:efr1.14:svnLENOVO:pn20QQS0KL13:pvrThinkPadP53:rvnLENOVO:rn20QQS0KL13:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QQS0KL13 dmi.product.sku: LENOVO_MT_20QQ_BU_Think_FM_ThinkPad P53 dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug fonts groovy kubuntu ubuntu ** Attachment added: "Relevant extract from /var/log/messages" https://bugs.launchpad.net/bugs/1931870/+attachment/5504504/+files/bug-report ** Description changed: - I used ubuntu-bug / other / system freeze to report this bug, even with extended diagnostic, and I really hope this information is attached, because I had to run ubuntu-bug three times until everything was fine. Otherwise this tool is useless and a hassle, and I could as well have copied the relevant part of my /var/log/messages here (which I'll do anyway, just in case). - There's an upload feature for attaching files on this web page (hidden behind a section "Extra options", which is by default closed and so conceals the feature), but the file dialog doesn't find any files in /tmp, so I had to move the report to a local user directory - - I'm absolutely unhappy with the bug reporting process in Ubuntu: it's - archaic, hard to use, loses information on the way (or at least does not - say what's being sent); then there's confusing information on bug - reporting on the network, most of it outdated or misleading, and in any - case overwhelming; there's several apps like apport (which does not work - at all), and ubuntu-bug, which reports exactly what it's going to - report, but then invokes a generic site with a fancy package (xorg) - which I don't know where it comes from, where I have to fill out - everything from beginning ... simply exhausting and disappointing. - ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-55.62-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Jun 14 15:18:03 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: - NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297] + NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297] InstallationDate: Installed on 2021-01-15 (150 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
[Bug 1929854] Re: Vital and critical configuration files get overridden by system updates without warning
Making changes to /usr/share/X11/locale/en_US.UTF-8/Compose was, at least for some time, the only way to make keyboard composition work in Ubuntu, as ~/.XCompose didn't work anymore, and creating a custom keyboard layout from scratch was not an option (my XCompose contains key compositions for almost the entire non-JCK UniCode character set in XCompose-coding). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929854 Title: Vital and critical configuration files get overridden by system updates without warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1929854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929854] Re: Vital and critical configuration files get overridden by system updates without warning
Hi Paride Thanks for your feedback. I'm a bit confused and concerned that a critical behaviour like this has to be addressed on package level and is not part of aptitude, but so be it. I will file individual bug reports against the affected packages when a configuration file is next overridden in this package, to avoid to address something that may have already been fixed (e.g. I couldn't say when the last time ssh was updated and sshd_config overridden, while Compose was overridden just recently, and grub.cfg gets overridden almost every time discovery runs). Dominik -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929854 Title: Vital and critical configuration files get overridden by system updates without warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1929854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929854] [NEW] Vital and critical configuration files get overridden by system updates without warning
Public bug reported: • In my /usr/share/X11/locale/en_US.UTF-8/Compose I have about 10'000 lines of special compose keys defined. • In my /boot/grub/grub.cfg I have a very complicated special setup for my various boot configurations, and a 5-sec timout for my EFI-config. • My /etc/ssh/sshd_config contains a well-balanced configuration All these files are regularly overridden WITHOUT EVEN A SINGLE WARNING or ASKING BACK by ubuntu system setups (discover). I set all of them to read-only by root and no-access for group and other users, but they still get overridden by every other system update. I even have a shutdown process in place which should actually make sure that changes to these files are reverted by writing a backup copy over any newly installed override — unfortunately, everything I did to run either a custom shutdown process or a startup process with systemd turned out to not work and be a nightmare to make work. How somebody could be as bold as to override vital configuration files like this without even asking for consent is one of the strange miracles in this world which I'll probably never understand. However, if "ubuntu" is really what it translates to, it should take a little bit more care about pre-existing configurations on systems on which it is set up and running well — until one system update suddenly jeopardizes the functioning of the entire system. I'm pretty sure these are not the only configuration files which are carelessly just overridden. They're just the ones every other update breaks my system and inflinges on my the costs of hours of research until I find out that — of course — it was an overridden critical system configuration again. The really mean thing is that you don't notice anything when you run the update … only next time you start your system and of course are not aware anymore that you did a system update, the new (absolutely wrong and/or insufficent) settings are in place and shoot you in the leg. Take an example from gentoo's etc-update feature which lets you merge new configuration files with pre-existing ones using a diff3-update. I went away from gentoo for other reasons, but I always praised that feature. Please make sure immediately that critical configuration files do not get overridden if they are non-writable by root, and then gradually introduce a system that merges changes to configuration files with the current situation on the target system. Or at least present the configs that would be changed in a particular directory, so that anybody who is interested in preserving local settings could merge them in a suitable way. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 27 18:48:15 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297] InstallationDate: Installed on 2021-01-15 (132 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20QQS0KL13 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-53-generic root=UUID=35cef147-e021-4bdd-b8db-31a3192c8a6a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET38W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QQS0KL13 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: ZF211710 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN2NET38W(1.23):bd06/04/2020:br1.23:efr1.14:svnLENOVO:pn20QQS0KL13:pvrThinkPadP53:rvnLENOVO:rn20QQS0KL13:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QQS0KL13 dmi.product.sku: LENOVO_MT_20QQ_BU_Think_FM_ThinkPad P53 dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
[Bug 1928172] [NEW] Xorg freeze
Public bug reported: If i sometimes missclick and click my Windows button on keyboard, Preview mode show up and sometimes i can't come back to full window mode, my Linux just freezes there. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Jest katalogiem: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Jest katalogiem: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Jest katalogiem: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.73.01 Thu Apr 1 21:40:36 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 12 08:02:20 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3283] InstallationDate: Installed on 2021-05-03 (8 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: MSI MS-7978 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=08cc25bc-76b2-4d2b-a729-e006642c7cb8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2016 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B.90 dmi.board.asset.tag: Default string dmi.board.name: B150 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB.90:bd12/21/2016:br5.12:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnB150GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7978 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang freeze hirsute ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928172 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1928172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925482] Re: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16
You're welcome! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925482 Title: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925482] Re: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16
You should now get all required debugging logs and also a similar debugging log from Ubuntu 20.10 to have further clues in the debugging process. ** Attachment added: "nvme_debugLog_Ubuntu_Groovy.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+attachment/5491786/+files/nvme_debugLog_Ubuntu_Groovy.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925482 Title: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925482] Re: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16
** Attachment added: "nvme_debugLog_kernel_5-12.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+attachment/5491785/+files/nvme_debugLog_kernel_5-12.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925482 Title: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925482] Re: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16
** Attachment added: "nvme_debugLog_kernel_5-11.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+attachment/5491784/+files/nvme_debugLog_kernel_5-11.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925482 Title: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925482] Re: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16
I did the tests with the three mentioned kernels and I also did an additional test with Ubuntu 20.10 (the file system there is ZFS, but that doesn't make that much of a difference). Every kernel aside the one from Ubuntu 20.10 crashed somewhere in the boot process. You'll find all debugging logs in the attachments of the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925482 Title: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925482] Re: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16
** Attachment added: "nvme_debugLog_kernel_5-10.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+attachment/5491783/+files/nvme_debugLog_kernel_5-10.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925482 Title: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925482] Re: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16
I was able to boot from SATA without reinstallation in Parallels and I'll try the PPAs later. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925482 Title: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925482] Re: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16
If it's helpful for you, I could also do the same procedure on the working VM with Ubuntu 20.10 and with a virtual NVMe drive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925482 Title: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925482] Re: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16
I was able to do a serial output based on the guide from https://www.hiroom2.com/2018/04/30/ubuntu-1804-serial-console-en/. In addition to that I also added your recommended boot parametre and I was able to add a virtual serial port, that can dump its output into a text file. You'll find the output as a text file in the attachments. ** Attachment added: "The serial logging output of the kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+attachment/5491125/+files/nvme_debugLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925482 Title: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925482] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1925482/+attachment/5490998/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925482 Title: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925482] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1925482/+attachment/5490997/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925482 Title: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925482] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1925482/+attachment/5490996/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925482 Title: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925482] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1925482/+attachment/5490995/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925482 Title: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925482] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1925482/+attachment/5491009/+files/acpidump.txt ** 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/1925482 Title: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925482] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1925482/+attachment/5491008/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925482 Title: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925482] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1925482/+attachment/5490994/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925482 Title: Ubuntu 21.04 won't boot with NVMe enabled on Parallels Desktop 16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
