[Bug 1629543] Please test proposed package
Hello Thomas, or anyone else affected, Accepted plasma-workspace into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/plasma- workspace/4:5.27.11-0ubuntu4.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1629543 Title: [SRU] KDE does not start when using lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1629543/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1629543] Re: [SRU] KDE does not start when using lightdm
Accepting, but please fix the Test Plan. These should be step by step instructions on how to reproduce the problem, and it should be possible for a developer not familiar with the package to follow the steps unambiguously. What is the starting point? Which method to "switch to plasma" should they use? What should they see if the test is successful, and what do they see when the test fails? ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1629543 Title: [SRU] KDE does not start when using lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1629543/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 2065465] Re: [SRU] broken sub-menus on some "systray" indicators
These two packages conflict with each other. Have you checked user apt behaviour when this change hits? What will the user experience be over the transition? Are there any packages which depend on the old package that will block the switch, or force removal of the depending package, for some users? > + * Removed plasma-vault from desktop-recommends [ppc64el] Please explain this change. ** Changed in: kubuntu-meta (Ubuntu Noble) Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2065465 Title: [SRU] broken sub-menus on some "systray" indicators To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/2065465/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 2065915] Please test proposed package
Hello Scarlett, or anyone else affected, Accepted kmail into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/kmail/4:23.08.5-0ubuntu5.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2065915 Title: [SRU] Add multiarch lines for each architecture we want to support in our apparmor profiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2065915/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 2065915] Re: [SRU] Add multiarch lines for each architecture we want to support in our apparmor profiles.
I've accepted most of these. Thank you for working on this! For kmail, the changelog seemed to be based on Oracular instead of Noble as expected, and used a confusing version number. I have replaced that upload for you, also minimising whitespace changes. I will accept this one and reject the older upload shortly. The one upload that I see remaining is tellico. This seems to contain unrelated changes. There's a Standards-Version change that is extraneous in an SRU (nor mentioned in the changelog) and should be dropped. But there also a Build-Depends change from pkg-config to pkgconf that isn't mentioned in the changelog. Is this necessary to get the build to work, or can it also be dropped? I'll reject the upload for now; please re- upload with this corrected - either drop the unnecessary change, or if it is necessary then it must be mentioned in the changelog, SRU documentation for the change must be present, etc. If re-uploading then it isn't necessary but would be nice for the change to debian/tellico-apparmor to not contain any extra whitespace changes so that the diff is clean. I did this when I fixed kmail and noticed it was also clean in one or two of the other packages. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2065915 Title: [SRU] Add multiarch lines for each architecture we want to support in our apparmor profiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2065915/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 2065915] Please test proposed package
Hello Scarlett, or anyone else affected, Accepted cantor into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cantor/4:23.08.5-0ubuntu4.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2065915 Title: [SRU] Add multiarch lines for each architecture we want to support in our apparmor profiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2065915/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 2065915] Please test proposed package
Hello Scarlett, or anyone else affected, Accepted akregator into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/akregator/4:23.08.5-0ubuntu4.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2065915 Title: [SRU] Add multiarch lines for each architecture we want to support in our apparmor profiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2065915/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 2065915] Please test proposed package
Hello Scarlett, or anyone else affected, Accepted digikam into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/digikam/4:8.2.0-0ubuntu6.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2065915 Title: [SRU] Add multiarch lines for each architecture we want to support in our apparmor profiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2065915/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 2065915] Please test proposed package
Hello Scarlett, or anyone else affected, Accepted angelfish into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/angelfish/23.08.5-0ubuntu3.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2065915 Title: [SRU] Add multiarch lines for each architecture we want to support in our apparmor profiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2065915/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 2065915] Re: [SRU] Add multiarch lines for each architecture we want to support in our apparmor profiles.
Hello Scarlett, or anyone else affected, Accepted kgeotag into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/kgeotag/1.5.0-1ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: kgeotag (Ubuntu Noble) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2065915 Title: [SRU] Add multiarch lines for each architecture we want to support in our apparmor profiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2065915/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 2063987] Re: kmail does not start on noble
Marking this Triaged/High for Noble as it sounds like a credible report with clear reproduction steps. It needs a volunteer to work on it though. ** Also affects: kmail (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: kmail (Ubuntu Noble) Status: New => Triaged ** Changed in: kmail (Ubuntu Noble) Importance: Undecided => High -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kmail in Ubuntu. Matching subscriptions: kubuntu-bugs https://bugs.launchpad.net/bugs/2063987 Title: kmail does not start on noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmail/+bug/2063987/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
This change was reverted, so I'm reopening the bug task for Noble. See main tracking bug 2064672 and regression bug 2072811 for details. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
This change was reverted, so I'm reopening the bug task for Noble. See main tracking bug 2064672 and regression bug 2072811 for details. ** Changed in: apparmor (Ubuntu Noble) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 2065915] Re: [SRU] Fix hard coded path in apparmor profiles.
Thanks. The profiles there are a bit different though - IIUC, they're there so that people who wish to opt-in to applying AppArmor profiles have a library to easily consult and use. There's a complication though which is that due to a change in 24.04 it's now required to explicitly enable "userns" so we need a bunch of profiles for those AIUI. I'm not familiar with how that fits in with the apparmor-profiles package, which I believe is still optional. I believe it does make sense for packaging to ship a profile with "userns" where required so that the package works by default, and that's what I see those profiles doing and what you're now doing for these packages in Oracular. Up to there, everything seems correct. Using "cantor" as an example, it looks like you added specific confinement for AppArmor profiles prior to the release of 24.04 though. To then turn off confinement in an update in 24.04 would be a regression from the user's perspective - going from confined (more secure) to unconfined (less secure) - contrary to typical user expectations of what a stable release means. On the other hand it doesn't seem appropriate to mandate that you must now rewrite all the profiles you added so that they work and leave the package broken if you cannot. If I'm missing something in my understanding above, please correct me! I'm open to suggestions on how to resolve this dilemma, but I would like to explore further the possibility of fixing the existing profiles rather than removing confinement. You said that the "packages still didn't work". Maybe we can find somebody to help with that? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2065915 Title: [SRU] Fix hard coded path in apparmor profiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2065915/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 2065915] Re: [SRU] Fix hard coded path in apparmor profiles.
Thanks. Could you link directly to the uploads whose pattern you're following please? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2065915 Title: [SRU] Fix hard coded path in apparmor profiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2065915/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 2065915] Re: [SRU] Fix hard coded path in apparmor profiles.
On Tue, Jul 09, 2024 at 11:32:33AM -, Scarlett Gately Moore wrote: > Also, what is exceptional justification. I can't find it in the docs. The docs say that SRUs should be minimal. Search for "this tends to be well-correlated with minimising the size of those changes" in https://wiki.ubuntu.com/StableReleaseUpdates. I accept that the documentation could be clearer and we are working on that, but the current documentation does state this. Turning off confinement entirely seems like much more than the required minimal change to fix the bug. Since this doesn't appear to be following our documented expectations, that's why I say that it needs exceptional justification. Alternatively I'd like to see uploads that do appear to meet those expectations. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2065915 Title: [SRU] Fix hard coded path in apparmor profiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2065915/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 2065915] Re: [SRU] Fix hard coded path in apparmor profiles.
Thank you for working on this. I'm not doing my SRU shift but was surprised to see so many uploads appear in the SRU queue together so paused to take a look. It looks like you're removing AppArmor confinement wholesale for a large number of packages, which I think requires exceptional justification in an SRU but I don't see this provided anywhere. I would expect the minimal fix appropriate to fix the SRU to be to fix the specific multiarch path that is described as the underlying issue in bug 2064492. I see that was done initially in Oracular (eg. https://launchpad.net/ubuntu/+source/cantor/4:23.08.5-0ubuntu5) but then further changed again to drop confinement altogether (eg. https://launchpad.net/ubuntu/+source/cantor/4:23.08.5-0ubuntu6). Please could you explain why the former is (presumably) unsuitable? Separately, we usually present SRUs as fixing the actual bug they're fixing, rather than creating a separate bug. So I'd have expected only bug 2064492 without this bug 2065915 being created. It's not clear to me what is separate to track here. See "Do not create a meta-bug" in step 1 of https://wiki.ubuntu.com/StableReleaseUpdates#Procedure. But let's focus on the real question and not worry about that for now. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2065915 Title: [SRU] Fix hard coded path in apparmor profiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2065915/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 2052360] Re: empty /proc/cpuinfo can cause segfault
Hello dann, or anyone else affected, Accepted cmake into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cmake/3.22.1-1ubuntu1.22.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: cmake (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to cmake in Ubuntu. https://bugs.launchpad.net/bugs/2052360 Title: empty /proc/cpuinfo can cause segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/2052360/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 2052362] Re: cmake FTBFS due to test failure w/ git protocol.file.allow=user default
Hello dann, or anyone else affected, Accepted cmake into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cmake/3.22.1-1ubuntu1.22.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: cmake (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to cmake in Ubuntu. https://bugs.launchpad.net/bugs/2052362 Title: cmake FTBFS due to test failure w/ git protocol.file.allow=user default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/2052362/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1950959] Re: Missing dependency in libqt5gstreamer-dev
** Also affects: qtcreator (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: qtcreator (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qtcreator in Ubuntu. https://bugs.launchpad.net/bugs/1950959 Title: Missing dependency in libqt5gstreamer-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtcreator/+bug/1950959/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 2003388] Re: [SRU] REGRESSION: ubuntustudio-default-settings 22.04.26.1 breaks Ubuntu Studio login
> I have found the source of the problem though. It seems as though during my upload, that file did, in fact, sneak in [3], but why it didn't show up in the debdiff, I'll never know. FWIW, the debdiff is blind to symlinks. For example, if you make a change to file that is symlinked from elsewhere in the same package, then debdiff will present that as both files changed. Similarly, if a file is dereferenced and replaced by an equivalent real file, debdiff won't see that. So debdiffs don't round trip correctly in the case of symlinks. This makes use of debdiff to perform reviews dangerous, too. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-workspace in Ubuntu. https://bugs.launchpad.net/bugs/2003388 Title: [SRU] REGRESSION: ubuntustudio-default-settings 22.04.26.1 breaks Ubuntu Studio login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/2003388/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1983307] Re: [SRU] Can't load addons list in a non-English locale (already fixed upstream)
The Test Plan also says: > * Additionally if possible test that integration in an English based locale still works. Was this done please? And which version of the package was tested? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to knewstuff in Ubuntu. https://bugs.launchpad.net/bugs/1983307 Title: [SRU] Can't load addons list in a non-English locale (already fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/knewstuff/+bug/1983307/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1971091] Re: [SRU] kstars 3.5.7 crashes with segfault on startup on 22.04 and 22.10
Hello Rik, or anyone else affected, Accepted kstars into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/kstars/5:3.5.7-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: kstars (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy ** Tags removed: verification-needed verification-needed-jammy ** Tags added: lto regression-release -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kstars in Ubuntu. https://bugs.launchpad.net/bugs/1971091 Title: [SRU] kstars 3.5.7 crashes with segfault on startup on 22.04 and 22.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kstars/+bug/1971091/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1951399] Re: Ubuntu, Budgie, Kubuntu, Kylin, MATE, Xubuntu: jammy daily fails to install
debianutils in Ubuntu Jammy now has tempfile restored (with a deprecation warning) and the deprecation warning for which removed. That's the only task I was working on, so I'm unassigning myself from this bug. If this resolved this particular issue then this bug might be marked as Fix Released, except that we don't know what the status of which and tempfile will be in Ubuntu beyond Jammy. It may be the case that depending components need to move away from tempfile and which in the end anyway, in which case maybe the task should remain open. ** Changed in: ubiquity (Ubuntu Jammy) Assignee: Robie Basak (racb) => (unassigned) ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to ubiquity in Ubuntu. https://bugs.launchpad.net/bugs/1951399 Title: Ubuntu, Budgie, Kubuntu, Kylin, MATE, Xubuntu: jammy daily fails to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1951399/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1951399] Re: Ubuntu, Budgie, Kubuntu, Kylin, MATE, Xubuntu: jammy daily fails to install
** Merge proposal linked: https://code.launchpad.net/~racb/ubuntu/+source/debianutils/+git/debianutils/+merge/412397 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to ubiquity in Ubuntu. https://bugs.launchpad.net/bugs/1951399 Title: Ubuntu, Budgie, Kubuntu, Kylin, MATE, Xubuntu: jammy daily fails to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1951399/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1905341] [NEW] kdeconnect-app broken on Focal
Public bug reported: On a default Ubuntu (not Kubuntu) desktop install, kdeconnect-app does not work at all. When running it from a terminal, it outputs: QQmlApplicationEngine failed to load component qrc:/qml/main.qml:93 Cannot assign object of type "DevicesModel" to property of type "QAbstractItemModel*" as the former is neither the same as the latter nor a sub-class of it. And then hangs. This is fixed in upstream release v1.4.1, specifically upstream commit 58a400a. Groovy and Hirsute are not affected. ** Affects: kdeconnect (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: kdeconnect (Ubuntu Focal) Importance: High Status: Triaged ** Also affects: kdeconnect (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: kdeconnect (Ubuntu Focal) Status: New => Triaged ** Changed in: kdeconnect (Ubuntu Focal) Importance: Undecided => High ** Changed in: kdeconnect (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdeconnect in Ubuntu. https://bugs.launchpad.net/bugs/1905341 Title: kdeconnect-app broken on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1905341/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1835723] Update Released
The verification of the Stable Release Update for cmake has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to cmake in Ubuntu. https://bugs.launchpad.net/bugs/1835723 Title: std::bad_alloc during SVN update in CTest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1835723/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1774434] Update Released
The verification of the Stable Release Update for kdeconnect has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1774434 Title: SRU 1.3.1 for Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1774434/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1774434] Re: SRU 1.3.1 for Bionic
Cosmic is >= 1.3.1. ** Changed in: kdeconnect (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1774434 Title: SRU 1.3.1 for Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1774434/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1750465] Please test proposed package
Hello Stephen, or anyone else affected, Accepted plymouth into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/plymouth/0.9.2-3ubuntu18 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1750465 Title: upgrade attempting to process triggers out of order (package plymouth- theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1750465/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1663950] Re: [SECURITY VULNERABILITY] CVE 2017-5593: User Impersonation Vulnerability in Jabber protocol
** Changed in: kopete (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kopete in Ubuntu. https://bugs.launchpad.net/bugs/1663950 Title: [SECURITY VULNERABILITY] CVE 2017-5593: User Impersonation Vulnerability in Jabber protocol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kopete/+bug/1663950/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1581371] Re: Plasma Network Manager crashes
** Tags added: regression-proposed -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-nm in Ubuntu. https://bugs.launchpad.net/bugs/1581371 Title: Plasma Network Manager crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnm-qt/+bug/1581371/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1576930] Re: Excessive consumption RAM of mysqld daemon in Kubuntu 16.04
** Description changed: [Status] - Suspected cause is triaged upstream in MySQL; waiting fix. + Suspected cause is triaged upstream in MySQL; awaiting fix. [Workaround] Proposed in comment 10; please report success or failure. [Original Description] In the last days using Kubuntu 16.04 I've noticed that after a while of use, RAM consumption of mysqld daemon rises above 800 MB, even surpassing Firefox, as you can see in the attached images. Initially, when system is just booted, RAM consumption of mysqld daemon it remains approximately 135-140 MB, but I have seen how after a while, in a matter of a few minutes, without touching anything, consumption rises progressively to around 830 MB. In the second image you can see that mysqld daemon is related to Akonadi, which at the same time has a lot of threads running. It is possible that the problem is in managing Akonadi processes, but it is clear that consumption of mysqld daemon is not normal, and that there must be a problem, either MySQL or Akonadi, causing this situation. I tried replacing MySQL with MariaDB, but will not let me uninstall MySQL components without also uninstall a lot of applications as dependencies (like Akonadi, Amarok, Kontact, KAdressBook ...). What I can do, even as an interim solution? Here are the attached screenshots: https://www.sendspace.com/file/712oyk https://www.sendspace.com/file/qcqeem -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/1576930 Title: Excessive consumption RAM of mysqld daemon in Kubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1576930/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1576930] Re: Excessive consumption RAM of mysqld daemon in Kubuntu 16.04
So the workaround suggested upstream is to add: innodb-read-io-threads=1 innodb-write-io-threads=1 to ~/.local/share/akonadi/mysql.cnf Can someone please confirm if this is accurate and if it works? We'll need to wait for a fix from upstream, but in the meantime hopefully the workaround will work for those affected. ** Description changed: + [Status] + + Suspected cause is triaged upstream in MySQL; waiting fix. + + [Workaround] + + Proposed in comment 10; please report success or failure. + + [Original Description] + In the last days using Kubuntu 16.04 I've noticed that after a while of use, RAM consumption of mysqld daemon rises above 800 MB, even surpassing Firefox, as you can see in the attached images. Initially, when system is just booted, RAM consumption of mysqld daemon it remains approximately 135-140 MB, but I have seen how after a while, in a matter of a few minutes, without touching anything, consumption rises progressively to around 830 MB. In the second image you can see that mysqld daemon is related to Akonadi, which at the same time has a lot of threads running. It is possible that the problem is in managing Akonadi processes, but it is clear that consumption of mysqld daemon is not normal, and that there must be a problem, either MySQL or Akonadi, causing this situation. I tried replacing MySQL with MariaDB, but will not let me uninstall MySQL components without also uninstall a lot of applications as dependencies (like Akonadi, Amarok, Kontact, KAdressBook ...). What I can do, even as an interim solution? - Here are the attached screenshots: https://www.sendspace.com/file/712oyk https://www.sendspace.com/file/qcqeem ** Changed in: mysql-5.7 (Ubuntu) Status: New => Triaged ** Changed in: mysql-5.7 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/1576930 Title: Excessive consumption RAM of mysqld daemon in Kubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1576930/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1571867] Re: Please remove kdesdk-kioslaves
23:27 "
23:27 it's only for subvesion service in various KDE apps
(corresponding svn+{ssh,http,https} protocols), like Dolphin,
Konqueror and few others.
23:28 If you don't use subversion, or do not use GUI apps for
managing svn repoes, you'll have no use of this package.
23:28 "
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdesdk-kioslaves in Ubuntu.
https://bugs.launchpad.net/bugs/1571867
Title:
Please remove kdesdk-kioslaves
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdesdk-kioslaves/+bug/1571867/+subscriptions
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 1437846] Re: akonadi mysql 5.6 crash with signal 11
On Tue, Apr 21, 2015 at 10:45:03AM -, Philip Muškovac wrote: > Regarding the database upgrade, mysql_upgrade is installed by default, > so that *should* work, as long as mysql takes care of that (akonadi > doesn't) AFAIK, mysql packaging will only touch /var/lib/mysql. If you have a custom started daemon with a database elsewhere (which is what akonadi appears to do), mysql packaging won't touch it. akonadi packaging will need to take care of this. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1437846 Title: akonadi mysql 5.6 crash with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1437846/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1437846] Re: akonadi mysql 5.6 crash with signal 11
Thank you for taking the time to report this bug and helping to make Ubuntu better. I can't reproduce this. I tried installing akonadi-server and akonadi- mysql-backend but that doesn't seem to cause anything to start. I am not familiar with akonadi. Can someone please provide exact steps to reproduce this issue on a fresh Vivid cloud instance? ** Changed in: mysql-5.6 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1437846 Title: akonadi mysql 5.6 crash with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1437846/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1442939] Re: qtcreator crashed with SIGSEGV
No idea about missing debug symbols, but this happened on a fresh Vivid VM with current packages. ** Changed in: qtcreator (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qtcreator in Ubuntu. https://bugs.launchpad.net/bugs/1442939 Title: qtcreator crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtcreator/+bug/1442939/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1442939] Re: qtcreator crashed with SIGSEGV
No private information here as it was from a freshly installed VM. ** Information type changed from Private to Public -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qtcreator in Ubuntu. https://bugs.launchpad.net/bugs/1442939 Title: qtcreator crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtcreator/+bug/1442939/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
