[Bug 1942927] Re: claws-mail package outdated (security risk)
** Changed in: claws-mail (Ubuntu) Status: New => Fix Released ** Changed in: sylpheed (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942927 Title: claws-mail package outdated (security risk) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/claws-mail/+bug/1942927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062135] Re: Add Cirrus Logic CS35L56 amplifier support
Boot with 6.8.0-38.38 kernel, both the left and right speakers work fine. ** Tags removed: verification-needed-noble-linux ** Tags added: verification-done-noble-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062135 Title: Add Cirrus Logic CS35L56 amplifier support To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2062135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2004203] Re: With needrestart, apt-get does not respect non-interactive instruction when upgrading services
@franz-s Sorry, just saw this. We typically don't backport new versions but cherry-pick fixes. Can you give the package from this PPA [1] a try and let me know if it fixes the issue? [1] https://launchpad.net/~juergh/+archive/ubuntu/needrestart ** Also affects: needrestart (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ubuntu-advantage-tools (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: ubuntu-advantage-tools (Ubuntu Jammy) ** Changed in: needrestart (Ubuntu Jammy) 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/2004203 Title: With needrestart, apt-get does not respect non-interactive instruction when upgrading services To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2004203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 495880] Re: File Roller cannot handle archive that doesn't encode filenames in UTF-8
Should be fixed in https://code.launchpad.net/~mitya57/ubuntu/+source/unzip/+git/unzip/+merge/466860 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/495880 Title: File Roller cannot handle archive that doesn't encode filenames in UTF-8 To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/495880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 477755] Re: Please reinclude the patch for codepage-based zip filenames
*** This bug is a duplicate of bug 580961 *** https://bugs.launchpad.net/bugs/580961 Should be fixed in https://code.launchpad.net/~mitya57/ubuntu/+source/unzip/+git/unzip/+merge/466860 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/477755 Title: Please reinclude the patch for codepage-based zip filenames To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unzip/+bug/477755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580961] Re: unzip fails to deal correctly with filename encodings
Should be fixed in https://code.launchpad.net/~mitya57/ubuntu/+source/unzip/+git/unzip/+merge/466860 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/580961 Title: unzip fails to deal correctly with filename encodings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-jp-improvement/+bug/580961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955908] Update Released
The verification of the Stable Release Update for oem-stella-beldum-meta has completed successfully and the package is now being 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955908 Title: [MIR][jammy] oem-stella-beldum-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1955908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971434] Re: Display powersave only blanks, but does not turn off
+1, fresh 24.04 install running wayland on intel drivers. At this point it seems like the bug affects many different setups. xset dpms force off Does trigger the correct behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1998754] Re: [MIR][jammy] oem-somerville-muk-meta
This bug was fixed in the package oem-somerville-muk-meta - 22.04~ubuntu1 --- oem-somerville-muk-meta (22.04~ubuntu1) jammy; urgency=medium * Meta package for Somerville Muk. (LP: #1998754) -- Kai-Chuan Hsieh Mon, 05 Dec 2022 09:26:21 +0800 ** Changed in: oem-somerville-muk-meta (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1998754 Title: [MIR][jammy] oem-somerville-muk-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1997656] Update Released
The verification of the Stable Release Update for oem-somerville-marill- meta has completed successfully and the package is now being 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1997656 Title: [MIR][jammy] oem-somerville-marill-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1997656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1997654] Update Released
The verification of the Stable Release Update for oem-somerville- lapras-13-meta has completed successfully and the package is now being 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1997654 Title: [MIR][jammy] oem-somerville-lapras-13-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1997654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1998754] Update Released
The verification of the Stable Release Update for oem-somerville-muk- meta has completed successfully and the package is now being 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1998754 Title: [MIR][jammy] oem-somerville-muk-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1979915] Re: mate-screensaver stops working but not crashing
KS>> What does "stops working" mean? It couldn't be more vague. It means "ceased functioning", like, no longer running. :-) FYI: This is only about Ubuntu-MATE 20.04. Ubuntu-MATE 22.04 LTS does not have this bug. Besides that, I can not get you any further information since I upgraded to 22.04 some time ago. This because 20.04 went out of support since april 2023. I still do have a 20.04 ISO but I have no spare computer left to install 20.04 again to assist in squashing this bug, sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1979915 Title: mate-screensaver stops working but not crashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-menus/+bug/1979915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1979915] Re: mate-screensaver stops working but not crashing
Bug fixed in Ubuntu-MATE 22.04 LTS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1979915 Title: mate-screensaver stops working but not crashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-menus/+bug/1979915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069109] [NEW] Security Bug in libde265-0 pkg for Jammy
Public bug reported: Hi Team, We are getting one below vernerability of package (libde265-0), kindly let us know the fix of this pkg over Ubuntu22.04 ditro. libde265-0 1.0.8-1ubuntu0.3 Thanks & Regards, Bhupendra ** Affects: libde265 (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/2069109 Title: Security Bug in libde265-0 pkg for Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libde265/+bug/2069109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069110] [NEW] netplan breaks route_localnet set in /proc/sys/net/ipv4/conf after apply/try
Public bug reported: Hello, VERSION: 0.106-2+deb12u1 Our server provider uses netplan so I've tried to migrate our configuration to netplan. We use internally developed transparent proxy similar to https://github.com/cloudflare/mmproxy/. For the proper functionality route_localnet must be enabled on the interface - echo 1 > /proc/sys/net/ipv4/conf/ens3/route_localnet After restarting network using 'netplan apply' or 'netplan try' the setting resets back to 0 and routing become broken. I've tried using networkd-dispatcher and putting script to routable.d and seems it executes BEFORE netplan reset to setting back to 0 so the result is not as intended - interface will keep set at 0 at the end. Therefore, We had to go back to ifupdown and use post-up/post-down scripts to setup everything properly. ** Affects: nplan (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/2069110 Title: netplan breaks route_localnet set in /proc/sys/net/ipv4/conf after apply/try To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/2069110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068562] Re: [SRU] libreoffice 24.2.4 for noble
** Description changed: [Impact] * LibreOffice 24.2.4 is in its forth bugfix release of the 24.2 line: https://wiki.documentfoundation.org/ReleasePlan/24.2#24.2.4_release * Version 24.2.3 is currently released in noble. For a list of fixed bugs compared to 24.2.3 see the list of bugs fixed in the release candidates of 24.2.4 (that's a total of 72 bugs): https://wiki.documentfoundation.org/Releases/24.2.4/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/24.2.4/RC2#List_of_fixed_bugs 24.2.4 RC2 is identical to the 24.2.4 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_242/1128/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/16170947/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-noble-libreoffice-libreoffice-prereleases/noble/amd64/libr/libreoffice/20240606_092112_973f5@/log.gz - * [arm64] ... + * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-noble-libreoffice-libreoffice-prereleases/noble/arm64/libr/libreoffice/20240610_175744_394b8@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-noble-libreoffice-libreoffice-prereleases/noble/armhf/libr/libreoffice/20240606_173254_c760d@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-noble-libreoffice-libreoffice-prereleases/noble/ppc64el/libr/libreoffice/20240606_091731_4cba9@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-noble-libreoffice-libreoffice-prereleases/noble/s390x/libr/libreoffice/20240606_095827_24f71@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice * Packaging changes are staged at https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/log/?h=wip/noble-24.2 [Regression Potential] * A minor release with a total of 72 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068562 Title: [SRU] libreoffice 24.2.4 for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2068562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063150] Re: No sound, stutters and clicks after upgrade to 24.04
Problem that no sound device is available on my Dell Precission 5520 was solved by a recent system update. No blacklisting of 'snd_soc_avs' was required. Could be that the later kernel avoids the problem or that the update changes some kernel/system settings. The kernel after the upgrade is 6.8.0-35-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063150 Title: No sound, stutters and clicks after upgrade to 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067669] Re: Mute/mic LEDs no function on ProBook 440/460 G11
SRU sent for noble 6.8-hwe. https://lists.ubuntu.com/archives/kernel-team/2024-June/151411.html ** Changed in: oem-priority Status: Confirmed => 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/2067669 Title: Mute/mic LEDs no function on ProBook 440/460 G11 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2067669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066044] Re: New upstream release 535.179
Maybe this is now "Won't Fix" in favour of bug 2067597? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066044 Title: New upstream release 535.179 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2066044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902458] Re: pyasn1 error during certificate renewal
[Expired for freeipa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: freeipa (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902458 Title: pyasn1 error during certificate renewal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1902458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069093] Re: When I put my Lenovo T14 g3n 3 to sleep by closing the lid, it often does not wake again when I open the lid
*** This bug is a duplicate of bug 2064595 *** https://bugs.launchpad.net/bugs/2064595 ** This bug has been marked a duplicate of bug 2064595 S2idle regression -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069093 Title: When I put my Lenovo T14 g3n 3 to sleep by closing the lid, it often does not wake again when I open the lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063417] Re: Fix system hang while entering suspend with AMD Navi3x graphics
** Tags removed: verification-needed-noble-linux ** Tags added: verification-done-noble-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063417 Title: Fix system hang while entering suspend with AMD Navi3x graphics To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062951] Re: Random flickering with Intel i915 on Linux 6.8 (Ubuntu 24.04)
info regarding bug 2046315 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062951 Title: Random flickering with Intel i915 on Linux 6.8 (Ubuntu 24.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069025] Re: kernel BUG at mm/migrate.c:663 on 6.8.0-1009-aws #9-Ubuntu
Hi Ariel, Are you using zfs? I see you have the module listed. Your oops looks very similar to this discussion here: https://github.com/openzfs/zfs/issues/15140 It doesn't seem anyone has come to any conclusions yet. I'll do some more research. Thanks, Matthew ** Bug watch added: github.com/openzfs/zfs/issues #15140 https://github.com/openzfs/zfs/issues/15140 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069025 Title: kernel BUG at mm/migrate.c:663 on 6.8.0-1009-aws #9-Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws/+bug/2069025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063827] Re: Gnome apps segfault in Nvidia Wayland sessions on Noble
Looks like this bug has only ever been observed with AMD CPUs, which might be a factor. Also I wonder if the Nvidia driver misconfiguration might be caused by third party software like Steam? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063827 Title: Gnome apps segfault in Nvidia Wayland sessions on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/egl-wayland/+bug/2063827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069092] Re: whole system hangs
In case the problem is bug 2062426, please try the workarounds from bug 2060268. If that does not solve it then please follow these steps: 1. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069092 Title: whole system hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2069092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1997653] Update Released
The verification of the Stable Release Update for oem-somerville-hoppip- meta has completed successfully and the package is now being 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1997653 Title: [MIR][jammy] oem-somerville-hoppip-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1997653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 493273] Re: xhfs crashes
** Merge proposal linked: https://code.launchpad.net/~liushuyu-011/ubuntu/+source/hfsutils/+git/hfsutils/+merge/467317 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/493273 Title: xhfs crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hfsutils/+bug/493273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 493273] Re: xhfs crashes
** Bug watch added: Debian Bug tracker #421457 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421457 ** Also affects: hfsutils (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421457 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/493273 Title: xhfs crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hfsutils/+bug/493273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064064] Re: Add support of TAS2781 amp of audio
Boot with 6.8.0-38.38 kernel, both the left and right speakers work fine. ** Tags removed: verification-needed-noble-linux ** Tags added: verification-done-noble-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064064 Title: Add support of TAS2781 amp of audio To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2064064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063067] Re: Fix bluetooth connections with 3.0 device
** Tags removed: verification-needed-focal-linux-hwe-5.15 verification-needed-mantic-linux ** Tags added: verification-done-focal-linux-hwe-5.15 verification-done-mantic-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063067 Title: Fix bluetooth connections with 3.0 device To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen
Hi everyone, Patches are on the Ubuntu Kernel Team mailing list: Cover letter: https://lists.ubuntu.com/archives/kernel-team/2024-June/151409.html Patch: https://lists.ubuntu.com/archives/kernel-team/2024-June/151410.html I will go talk to the kernel team now, I can't promise anything, but will try and get this prioritised. I will write back with what they say. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068738 Title: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069058] Re: GNOME screen recorder, why are video colors and sizes wrong?
The accented text colour is due to one or two factors: 1. Lossy video encoding (we're not going to change that) 2. GTK3 apps (including Desktop Icons NG) still use RGB font antialiasing, which is no longer present in GTK4 apps. You can remove that by running: gsettings set org.gnome.desktop.interface font-antialiasing 'grayscale' and log in again. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Changed in: ubuntu Status: Incomplete => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069058 Title: GNOME screen recorder, why are video colors and sizes wrong? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2069058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1997655] Update Released
The verification of the Stable Release Update for oem-somerville-lapras- meta has completed successfully and the package is now being 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1997655 Title: [MIR][jammy] oem-somerville-lapras-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1997655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1997655] Re: [MIR][jammy] oem-somerville-lapras-meta
This bug was fixed in the package oem-somerville-lapras-meta - 22.04~ubuntu1 --- oem-somerville-lapras-meta (22.04~ubuntu1) jammy; urgency=medium * Meta package for Somerville Lapras. (LP: #1997655) -- Dirk Su Tue, 30 Aug 2022 13:22:05 +0800 ** Changed in: oem-somerville-lapras-meta (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/1997655 Title: [MIR][jammy] oem-somerville-lapras-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1997655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068908] Re: VM guest resolution is not saved anymore
If you have a VM running KDE or LXQt and it boots to a black screen then see bug 2063143. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068908 Title: VM guest resolution is not saved anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2068908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069048] Re: gnome-shell crash (signal 11)
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: noble ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069048 Title: gnome-shell crash (signal 11) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2069048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069039] Re: Disk password prompt isn't shown in external monitor
** Tags added: simpledrm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069039 Title: Disk password prompt isn't shown in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2069039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen
** Summary changed: - Kernel update 5.15.0-112 might cause severe problems with specific AMD GPUs + AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen ** Description changed: - System is not booting while using AMD Picasso/Raven 2 graphics after - update to 5.15.0-112 + BugLink: https://bugs.launchpad.net/bugs/2068738 - Graphics: - Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series] - vendor: Hewlett-Packard driver: amdgpu v: kernel bus-ID: 04:00.0 - Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati - unloaded: fbdev,modesetting,vesa gpu: amdgpu resolution: 1600x900~60Hz - OpenGL: renderer: AMD Radeon Vega 3 Graphics (raven2 LLVM 15.0.7 DRM 3.42 - 5.15.0-107-generic) - v: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.2 direct render: Yes + [Impact] - Several reports: + On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is + enabled, the system fails to boot correctly, and all users see is a + black screen. + This is caused by a null pointer dereference when enabling the IOMMU + after the device has been initialised. It should happen the other way + around. + + AMD-Vi: AMD IOMMUv2 loaded and initialized + ... + amdgpu: Topology: Add APU node [0x15d8:0x1002] + kfd kfd: amdgpu: added device 1002:15d8 + kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8 + ... + amdgpu :06:00.0: amdgpu: amdgpu_device_ip_init failed + amdgpu :06:00.0: amdgpu: Fatal error during GPU init + amdgpu :06:00.0: amdgpu: amdgpu: finishing device. + ... + BUG: kernel NULL pointer dereference, address: 013c + ... + CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu + ... + RIP: 0010:amdgpu_dm_fini+0x149/0x1f0 [amdgpu] + ... + Call Trace: + + ? srso_return_thunk+0x5/0x10 + ? show_trace_log_lvl+0x28e/0x2ea + ? show_trace_log_lvl+0x28e/0x2ea + ? dm_hw_fini+0x23/0x30 [amdgpu] + ? show_regs.part.0+0x23/0x29 + ? __die_body.cold+0x8/0xd + ? __die+0x2b/0x37 + ? page_fault_oops+0x13b/0x170 + ? srso_return_thunk+0x5/0x10 + ? do_user_addr_fault+0x321/0x670 + ? srso_return_thunk+0x5/0x10 + ? __free_pages_ok+0x34a/0x4f0 + ? exc_page_fault+0x77/0x170 + ? asm_exc_page_fault+0x27/0x30 + ? amdgpu_dm_fini+0x149/0x1f0 [amdgpu] + dm_hw_fini+0x23/0x30 [amdgpu] + amdgpu_device_ip_fini_early.isra.0+0x278/0x312 [amdgpu] + amdgpu_device_fini_hw+0x156/0x208 [amdgpu] + amdgpu_driver_unload_kms+0x69/0x90 [amdgpu] + amdgpu_driver_load_kms.cold+0x81/0x107 [amdgpu] + amdgpu_pci_probe+0x1d1/0x290 [amdgpu] + local_pci_probe+0x4b/0x90 + ? srso_return_thunk+0x5/0x10 + pci_device_probe+0x119/0x200 + really_probe+0x222/0x420 + __driver_probe_device+0xe8/0x140 + driver_probe_device+0x23/0xc0 + __driver_attach+0xf7/0x1f0 + ? __device_attach_driver+0x140/0x140 + bus_for_each_dev+0x7f/0xd0 + driver_attach+0x1e/0x30 + bus_add_driver+0x148/0x220 + ? srso_return_thunk+0x5/0x10 + driver_register+0x95/0x100 + __pci_register_driver+0x68/0x70 + amdgpu_init+0x7c/0x1000 [amdgpu] + ? 0xc0e0b000 + do_one_initcall+0x49/0x1e0 + ? srso_return_thunk+0x5/0x10 + ? kmem_cache_alloc_trace+0x19e/0x2e0 + do_init_module+0x52/0x260 + load_module+0xb45/0xbe0 + __do_sys_finit_module+0xbf/0x120 + __x64_sys_finit_module+0x18/0x20 + x64_sys_call+0x1ac3/0x1fa0 + do_syscall_64+0x56/0xb0 + ... + entry_SYSCALL_64_after_hwframe+0x67/0xd1 + + A workaround does exist. Users can set "nomodeset" or "amd_iommu=off" to + GRUB_CMDLINE_LINUX_DEFAULT, update-grub and reboot. + + [Fix] + + The regression was caused by the following commit that landed in + 5.15.0-112-generic, and 5.15.150 upstream: + + commit 3c7e53c0d4b43ffe6e7715414b5f2b3177881ecd ubuntu-jammy + Author: Yifan Zhang + Date: Tue Sep 28 15:42:35 2021 +0800 + Subject: drm/amdgpu: init iommu after amdkfd device init + Link: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=3c7e53c0d4b43ffe6e7715414b5f2b3177881ecd + + The fix is to revert this patch, as it was not suppose to be backported + to 5.15 stable. + + The mailing list discussion with AMD developers is: + + https://lore.kernel.org/amd-gfx/20240523173031.4212-1-w_ar...@gmx.de/ + + The fix hasn't been acknowledged by Greg KH or Sasha Levin yet, so + sending as a Ubuntu SAUCE patch. If the upstream status changes, we can + NAK and resend. + + [Testcase] + + You need a system with an AMD Picasso/Raven 2 device. It will likely be + an APU, and not a discrete graphics card, but any AMD Picasso/Raven 2 + device is affected. + + Install the kernel and boot. Make sure full modesetting is enabled. + + There is a test kernel available in the ppa below: + + https://launchpad.net/~mruffell/+archive/ubuntu/lp2068738-test + + If you install the test kernel, your system should boot successfully. + + [Where problems could occur] + + We are reverting a problematic patch and going back to how it was before + 5.15.0-112-generic. This should no
[Bug 2039148] Re: lxd-installer can race or temp-fail and then block itself
This bug was fixed in the package lxd-installer - 6 --- lxd-installer (6) oracular; urgency=medium * Makefile: install scripts into /usr/sbin (instead of /sbin) * Makefile: make lxd-installer script executable * lxd-installer-service: set shell options * Install LXD from $LTS/stable/ubuntu-$VERSION as default channel (LP: #2067425): - lxd-installer-service: use $LTS/stable/ubuntu-$VERSION as default channel - d/tests/install-on-demand: update expected channel * d/lxd-installer@.service: remove wrapper shell * d/lxd-installer.socket: don't start service if /snap/bin/lxd is detected * d/tests/*: start lxd-installer.socket after purging LXD snap * scripts/lxc: use variable substitution to avoid forking to basename * Wait for snapd to be seeded before asking for LXD snap to be installed: (LP: #2039148) - scripts/lxc: wait for lxd-installer.socket to be present - lxd-installer-service: wait for snapd to be seeded * d/*: refresh packaging - d/control: switch to debhelper-compat 12 - d/compat: remove now unneeded file - d/control: make it explicit that root is not required to build - d/control: bump standards-version to 4.5.0 (no change required) -- Simon Deziel Tue, 11 Jun 2024 15:18:20 -0400 ** Changed in: lxd-installer (Ubuntu Oracular) Status: Triaged => 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/2039148 Title: lxd-installer can race or temp-fail and then block itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2039148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067425] Re: lxd-installer should default to pulling LXD from the $LTS/stable/ubuntu-XX.YY channel
This bug was fixed in the package lxd-installer - 6 --- lxd-installer (6) oracular; urgency=medium * Makefile: install scripts into /usr/sbin (instead of /sbin) * Makefile: make lxd-installer script executable * lxd-installer-service: set shell options * Install LXD from $LTS/stable/ubuntu-$VERSION as default channel (LP: #2067425): - lxd-installer-service: use $LTS/stable/ubuntu-$VERSION as default channel - d/tests/install-on-demand: update expected channel * d/lxd-installer@.service: remove wrapper shell * d/lxd-installer.socket: don't start service if /snap/bin/lxd is detected * d/tests/*: start lxd-installer.socket after purging LXD snap * scripts/lxc: use variable substitution to avoid forking to basename * Wait for snapd to be seeded before asking for LXD snap to be installed: (LP: #2039148) - scripts/lxc: wait for lxd-installer.socket to be present - lxd-installer-service: wait for snapd to be seeded * d/*: refresh packaging - d/control: switch to debhelper-compat 12 - d/compat: remove now unneeded file - d/control: make it explicit that root is not required to build - d/control: bump standards-version to 4.5.0 (no change required) -- Simon Deziel Tue, 11 Jun 2024 15:18:20 -0400 ** Changed in: lxd-installer (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067425 Title: lxd-installer should default to pulling LXD from the $LTS/stable/ubuntu-XX.YY channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd-installer/+bug/2067425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069039] Re: Disk password prompt isn't shown in external monitor
This is probably a "Won't Fix" but I'll give others time to chime in and correct me... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069039 Title: Disk password prompt isn't shown in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2069039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069039] Re: Disk password prompt isn't shown in external monitor
Timo is right I think. Secondary monitors will only wake up after: 1. The native kernel DRM graphics driver is loaded. 2. Plymouth detects the new driver and switches to it. And the native kernel DRM graphics drivers seem to be loading slightly later now that we have kicked them out of the initrd. In fact I think there might be a hard limit where they can't even start loading until the root FS is decrypted. We want to keep those drivers out of the initrd because they've become bloated, but also because they take so long (up to 10 seconds) to load that they're not helpful to Plymouth wanting to display boot graphics very early. So we rely on SimpleDRM for that instead, which apparently can only display on the original BIOS display?? You should be able to work around it by adding 'amdgpu' to '/etc/initramfs-tools/modules' and then run: sudo update-initramfs -k all -u ** Package changed: plymouth (Ubuntu) => initramfs-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069039 Title: Disk password prompt isn't shown in external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2069039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065128] Re: rtw89_8852ce - Lost WIFI connection after suspend
** Description changed: [Impact] Lost WIFI connection after suspend. While this happen, the WIFI module couldn't detect any AP, re-enable module and reboot OS without any help. There only way to get it back is cold boot. [Fix] Realtek provides a fix which has been included in rtw maintainer's tree https://lore.kernel.org/linux-wireless/20240426061200.44262-1-pks...@realtek.com/T/#mbfcb37c2fdc85ba280743f2b07fbf1fa8719eb79 + + The commits has been included in v6.10-rc1 + 4e5957101d42 wifi: rtw89: 8852c: refine power sequence to imporve power consumption + 535c045da60f wifi: rtw89: reset AFEDIG register in power off sequence [Test case] 1. Boot into OS 2. open terminal to keep checking dmesg or check the wifi connection from GUI 3. suspend/resume multiple times 4. check the wifi connection [Where problems could occur] What the 2 commits should be safe and won't introduce any regression. 1. Reset AFEDIG register before BB reset in power off sequence 2. Adjust power and clock parameters ** Changed in: linux (Ubuntu Oracular) 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/2065128 Title: rtw89_8852ce - Lost WIFI connection after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2065128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2045737] Re: Logitech MX Master 3 is detected as a keyboard in Power Statistics
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upower (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/2045737 Title: Logitech MX Master 3 is detected as a keyboard in Power Statistics To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/2045737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059259] Re: ubuntu_ltp sched:starvation fails with ARM64 on bos2 region
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059259 Title: ubuntu_ltp sched:starvation fails with ARM64 on bos2 region To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2059259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2031954] Re: SRU: update gcc-snapshot to the GCC 12.1.0 release
Just to be clear (to move this along) - does using this gcc-snapshot in the kernel build result in bootable kernels? (ie: does this fix https://bugs.launchpad.net/ubuntu/+source/gcc-12/+bug/2031927 ?) I think that's the question we want answered before releasing this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2031954 Title: SRU: update gcc-snapshot to the GCC 12.1.0 release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-snapshot/+bug/2031954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069045] Re: 5.15.0-112 fails to initialize NVidia video card
Hello Evgueni, Are you sure it is an Nvidia card? We have a known regression for 5.15.0-112-generic with AMD cards, over in bug 2068738. The symptom is a black screen on boot. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069045 Title: 5.15.0-112 fails to initialize NVidia video card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067071] Re: cannot upgrade from 23.10 to 24.04, error in _install_t64_replacement_packages
It looks like you made some code changes to fix, but I did try the
upgrade again and fails the same way:
res = f(*args, **kwargs)
^^
File "/tmp/ubuntu-release-upgrader-vh4mksxv/DistUpgrade/DistUpgradeCache.py",
line 626, in distUp
grade
self.pre_upgrade_rule()
File "/tmp/ubuntu-release-upgrader-vh4mksxv/DistUpgrade/DistUpgradeCache.py",
line 497, in pre_up
grade_rule
self.quirks.run("PreDistUpgradeCache")
File
"/tmp/ubuntu-release-upgrader-vh4mksxv/DistUpgrade/DistUpgradeQuirks.py", line
95, in run
func()
File
"/tmp/ubuntu-release-upgrader-vh4mksxv/DistUpgrade/DistUpgradeQuirks.py", line
191, in PreDi
stUpgradeCache
self._install_t64_replacement_packages()
File
"/tmp/ubuntu-release-upgrader-vh4mksxv/DistUpgrade/DistUpgradeQuirks.py", line
1845, in _install_t64_replacement_packages
if replacement.candidate._cand != ver:
^^^
AttributeError: 'NoneType' object has no attribute '_cand'
Any chance the changes could be released or is there a way I can test
them?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067071
Title:
cannot upgrade from 23.10 to 24.04, error in
_install_t64_replacement_packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2067071/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067720] Re: pytorch 2.1.2+dfsg-4 FTBFS with llvm 18
This bug was fixed in the package pytorch - 2.1.2+dfsg-4ubuntu1 --- pytorch (2.1.2+dfsg-4ubuntu1) oracular; urgency=medium * Fix FTBFS with LLVM 18. (LP: #2067720) - d/p/0011-Update-caffe2-with-LLVM-18-API-change-109408.patch: - d/p/0012-Fix-build-for-llvm-18-115652.patch: - d/p/0013-Update-for-an-API-change-in-LLVM-18.-117086.patch: - d/p/0014-Replaced-getInt8PtrTy-with-getUnqual-113455.patch: - d/p/0015-Update-apis-incompatible-with-llvm-versions-in-codeg.patch: - d/p/0016-Revert-upstream-commit-32643bc9266271ebf3b935573189e.patch: Backport patches from upstream to fix the issue. -- Sergio Durigan Junior Mon, 10 Jun 2024 14:38:33 -0400 ** Changed in: pytorch (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/2067720 Title: pytorch 2.1.2+dfsg-4 FTBFS with llvm 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pytorch/+bug/2067720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068738] Re: Kernel update 5.15.0-112 might cause severe problems with specific AMD GPUs
Hi Xie, Thanks for trying the test kernel, and its great news that we have identified the fix. I'll write up a SRU template, and get the patch sent off to the kernel team today. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068738 Title: Kernel update 5.15.0-112 might cause severe problems with specific AMD GPUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068026] Re: initramfs-tools hook does not support zstd-compressed kernel modules
** Changed in: open-vm-tools (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: open-vm-tools (Ubuntu) Importance: Undecided => High ** Changed in: open-vm-tools (Ubuntu) Status: New => Triaged ** Changed in: open-vm-tools (Ubuntu) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068026 Title: initramfs-tools hook does not support zstd-compressed kernel modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librem-ec-acpi/+bug/2068026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068918] Re: New bugfix release 24.0.9
This bug was fixed in the package mesa - 24.0.9-0ubuntu1 --- mesa (24.0.9-0ubuntu1) oracular; urgency=medium * New upstream release. (LP: #2068918) -- Timo Aaltonen Mon, 10 Jun 2024 18:50:20 +0300 ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068918 Title: New bugfix release 24.0.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2068918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064393] Re: Merge chrony from Debian unstable for oracular
This bug has a simple fix identified and would be worth inclusion in the merge: https://bugs.launchpad.net/ubuntu/+source/linuxptp/+bug/2068526 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064393 Title: Merge chrony from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2064393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2025658] Re: Missing Conflicts: desktop-base
Bumping this issue. I cannot install GNOME on kubuntu 24.04 because of this error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2025658 Title: Missing Conflicts: desktop-base To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/2025658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740751] Re: indicator-multiload display keeps resetting on its own
Happened on 22.04. dconf reset -f /de/mh21/indicator-multiload/ Fixed it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740751 Title: indicator-multiload display keeps resetting on its own To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-multiload/+bug/1740751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941785] Re: ec2-hibinit-agent: Add support for IMDSv2
** Changed in: cloud-images Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941785 Title: ec2-hibinit-agent: Add support for IMDSv2 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1941785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067918] Re: cups-browsed high-cpu usage
This randomly happens on my 24.10 (devel repos) desktop. I don't have to have even printed anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067918 Title: cups-browsed high-cpu usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2067918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069093] [NEW] When I put my Lenovo T14 g3n 3 to sleep by closing the lid, it often does not wake again when I open the lid
Public bug reported: I have a Lenovo ThinkPad T14 Gen 3. I got it last fall and installed Ubuntu 23.10 the day after 23.10 was released. After a couple weeks of issues while 23.10 stabilized, it worked pretty much fine. Sometime in April of this year, my device/OS combo which had been working suddenly developed a problem. Suddenly I began seeing a problem where when I closed the lid to sleep the machine, waited a while, and then opened the screen again, the screen would be black and the unit would be totally nonresponsive. When the device is in this state, the red LED on the back in the "THINK" logo stays at a fixed value rather than pulsating as it normally does during sleep, and the lights on the FKEYs (for example normally I can tap F1 which will mute/unmute the speakers or F4 which will mute/unmute the mic, and both these actions will toggle a light on that key) are nonresponsive. The only way to exit this state is to hold the power button until the unit turns off, then press the power button again to rewake. (The fact the FKEY lights do not respond makes me believe the device has actually crashed at this point and it isn't just a stuck-off screen.) For a couple months after this I saw the problem between every other day and twice a day. Last week I upgraded to 24.04 to see if this would help with the problem. It has not resolved the problem. Since the upgrade I have seen the problem twice. I gathered the attached logs immediately after waking following one of these lockups/hard power cycles. This has been a huge inconvenience so I will happily gather any other logs needed. Two other pieces of information, not sure if helpful: 1. *Once*, exactly once in April, when I saw this problem, upon opening the screen the screen lit up and displayed three lines of a text error. The words "amd ring 0 error" were visible. The screen then went black (and stayed black) before I could record the other text. 2. The "Firmware Updater" app currently says my "System Firmware" can be upgraded from 0.1.46 to 0.1.52. I didn't see that until this week. I am going to try installing this firmware update and I will report back here if it does/doesn't make a difference. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-35-generic 6.8.0-35.35+1 ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4 Uname: Linux 6.8.0-35-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 11 15:34:33 2024 InstallationDate: Installed on 2023-10-18 (238 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: LENOVO 21CF000CUS ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-35-generic root=UUID=ecb1730b-cbe1-457c-a4f8-23e2eaf89020 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-35-generic N/A linux-backports-modules-6.8.0-35-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-06-03 (8 days ago) dmi.bios.date: 08/08/2023 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET70W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CF000CUS dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrR23ET70W(1.40):bd08/08/2023:br1.40:efr1.31:svnLENOVO:pn21CF000CUS:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF000CUS:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CF000CUS dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069093 Title: When I put my Lenovo T14 g3n 3 to sleep by closing the lid, it often does not wake again when I open the lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
I've just tried the proposed 1.0.2-3ubuntu0.1 package on a clean Noble VM and it fixed the startup issues, as expected, for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068738] Re: Kernel update 5.15.0-112 might cause severe problems with specific AMD GPUs
Hi Matthew, thanks for the quick fix. It works for me. ``` # uname -rv 5.15.0-112-generic #122+TEST2068738v20240610b1-Ubuntu SMP Mon Jun 10 05:02:07 UTC 2 # inxi -G Graphics: Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series] driver: amdgpu v: kernel Device-2: Lite-On HP Webcam type: USB driver: uvcvideo Display: server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa gpu: amdgpu resolution: 1920x1080~60Hz OpenGL: renderer: AMD Radeon Vega 3 Graphics (raven2 LLVM 15.0.7 DRM 3.42 5.15.0-112-generic) v: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.2 ``` Also tried `vkcube` and it also works. So I guess that this is fixed. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068738 Title: Kernel update 5.15.0-112 might cause severe problems with specific AMD GPUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Autopkgtest regression report (fail2ban/1.0.2-3ubuntu0.1)
All autopkgtests for the newly accepted fail2ban (1.0.2-3ubuntu0.1) for noble have finished running. The following regressions have been reported in tests triggered by the package: freedombox/unknown (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/noble/update_excuses.html#fail2ban [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2041655] Re: ddcci-dkms FTBS with kernel 6.5 in jammy
This bug was fixed in the package ddcci-driver-linux - 0.4.1-3ubuntu3 --- ddcci-driver-linux (0.4.1-3ubuntu3) jammy; urgency=medium * Support Linux 6.5 (LP: #2041655): - debian/patches/linux-6.3.patch - debian/patches/linux-6.5.patch -- Andrea Righi Fri, 27 Oct 2023 12:12:00 + ** Changed in: ddcci-driver-linux (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/2041655 Title: ddcci-dkms FTBS with kernel 6.5 in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddcci-driver-linux/+bug/2041655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2041655] Update Released
The verification of the Stable Release Update for ddcci-driver-linux has completed successfully and the package is now being 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2041655 Title: ddcci-dkms FTBS with kernel 6.5 in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddcci-driver-linux/+bug/2041655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069058] Re: GNOME screen recorder, why are video colors and sizes wrong?
And are you using x11 or wayland? Did you try to adjust the settings before screenshotting? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069058 Title: GNOME screen recorder, why are video colors and sizes wrong? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2069058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2041655] Re: ddcci-dkms FTBS with kernel 6.5 in jammy
ddcci-driver-linux (0.4.3-2) unstable; urgency=medium * Add upstream candidate patches to build with versions 6.2, 6.3, and 6.4 of the kernel. Closes: #1037974. ** Changed in: ddcci-driver-linux (Ubuntu) Status: Confirmed => 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/2041655 Title: ddcci-dkms FTBS with kernel 6.5 in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddcci-driver-linux/+bug/2041655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055010] Re: Gedit has an invalid regular expression, the error is not fatal, but immediately occurs at its start, additionally, it has a critical level GTK error as well
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gedit (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/2055010 Title: Gedit has an invalid regular expression, the error is not fatal, but immediately occurs at its start, additionally, it has a critical level GTK error as well To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2055010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066904] Re: New upstream release 470.256.02 ERD12
This bug was fixed in the package nvidia-graphics-drivers-470-server - 470.256.02-0ubuntu1 --- nvidia-graphics-drivers-470-server (470.256.02-0ubuntu1) oracular; urgency=medium * New upstream release (LP: #2066904) -- Kuba Pawlak Thu, 23 May 2024 15:33:43 +0200 ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Oracular) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066904 Title: New upstream release 470.256.02 ERD12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-470/+bug/2066904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064472] Re: Merge tgt from Debian unstable for oracular
** Merge proposal linked: https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/tgt/+git/tgt/+merge/467306 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064472 Title: Merge tgt from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/2064472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2041215] Re: dahdi-dkms FTBS with linux 6.5 on jammy
This bug was fixed in the package dahdi-linux - 1:2.11.1~dfsg-1ubuntu12~22.04.3 --- dahdi-linux (1:2.11.1~dfsg-1ubuntu12~22.04.3) jammy; urgency=medium * Support Linux 6.5 (LP: #2041215): - debian/patches/Linux-6.5-abi.patch -- Andrea Righi Thu, 26 Oct 2023 14:30:50 + ** Changed in: dahdi-linux (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/2041215 Title: dahdi-dkms FTBS with linux 6.5 on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/2041215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2041215] Update Released
The verification of the Stable Release Update for dahdi-linux has completed successfully and the package is now being 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2041215 Title: dahdi-dkms FTBS with linux 6.5 on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/2041215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066979] Re: EC2: cloud-init network fails in ipv6-only subnet with multi-NICs
Verification results attached. `verify_2066979.txt` contains results of manual verification as laid out in the bug description. `multinic-2066979-template.json` contains one of the supporting files used in those tests. `_integration_tests.txt` contains the automated regression integration test results for each series. Explanations of warnings of hiccups are in comments at the top of files. ** Attachment added: "2066979.tar.gz" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2066979/+attachment/5788565/+files/2066979.tar.gz ** Tags removed: verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic verification-needed-noble ** Tags added: verification-done verification-done-focal verification-done-jammy verification-done-mantic verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066979 Title: EC2: cloud-init network fails in ipv6-only subnet with multi-NICs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2066979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066985] Re: EC2 multi-nic ENI rendering fails if ENI activator not used
** Tags removed: verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic verification-needed-noble ** Tags added: verification-done verification-done-focal verification-done-jammy verification-done-mantic verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066985 Title: EC2 multi-nic ENI rendering fails if ENI activator not used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2066985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2041215] Re: dahdi-dkms FTBS with linux 6.5 on jammy
[ 2:40PM 10264 ] [
bdmurray@impulse:/tmp/pkgs/noble/dahdi-linux-2.11.1.0.20170917~dfsg ]
$ grep -A4 "#if LINUX_VERSION_CODE >= KERNEL_VERSION(6, 4, 0)"
drivers/dahdi/dahdi-sysfs-chan.c
#if LINUX_VERSION_CODE >= KERNEL_VERSION(6, 4, 0)
dahdi_class = class_create("dahdi");
#else
dahdi_class = class_create(THIS_MODULE, "dahdi");
#endif
The same changes are in mantic.
** Changed in: dahdi-linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2041215
Title:
dahdi-dkms FTBS with linux 6.5 on jammy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/2041215/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066985] Re: EC2 multi-nic ENI rendering fails if ENI activator not used
Verification results attached. `verify_2066985.txt` contains results of manual verification as laid out in the bug description. `multinic-2066985-template.json` contains one of the supporting files used in those tests. `_integration_tests.txt` contains the automated regression integration test results for each series. ** Attachment added: "2066985.tar.gz" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2066985/+attachment/5788564/+files/2066985.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066985 Title: EC2 multi-nic ENI rendering fails if ENI activator not used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2066985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2024134] Update Released
The verification of the Stable Release Update for xlnx-firmware has completed successfully and the package is now being 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2024134 Title: [SRU] IMX274 Probe failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xlnx-firmware/+bug/2024134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2024134] Re: [SRU] IMX274 Probe failure
This bug was fixed in the package xlnx-firmware - 2022.1-5-0ubuntu1~22.04 --- xlnx-firmware (2022.1-5-0ubuntu1~22.04) jammy; urgency=medium * Backport to jammy - New upstream version 2022.1_22.04_5 - Fix: IMX274 Probe failure (LP: #2024134) -- Ethan Hsieh Thu, 29 Jun 2023 17:17:10 +0800 ** Changed in: xlnx-firmware (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/2024134 Title: [SRU] IMX274 Probe failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xlnx-firmware/+bug/2024134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064751] Re: [SRU] revert security-regression in Focal's libcrypto++
Hi Mark, Note that I made a small tweak to the changelog to close this bug. This looks mostly good to me. The symbol change may make this more interesting. I learned enough about abi-compliance-checker to do some analysis there and it claims that the ABI is unchanged, but we would benefit from a second set of eyeballs on that. If I have that detail incorrect, the rdeps would need rebuilds. Uploading to Focal. ** Changed in: libcrypto++ (Ubuntu Focal) Assignee: Dan Bungert (dbungert) => (unassigned) ** Changed in: libcrypto++ (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064751 Title: [SRU] revert security-regression in Focal's libcrypto++ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcrypto++/+bug/2064751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2024237] Update Released
The verification of the Stable Release Update for gnome-remote-desktop has completed successfully and the package is now being 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2024237 Title: gnome-remote-desktop-daemon segfaults on push_queue -> pw_stream_queue_buffer -> on_frame_ready -> grd_thread_dispatch_in_impl -> egl_task_source_dispatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2024237] Re: gnome-remote-desktop-daemon segfaults on push_queue -> pw_stream_queue_buffer -> on_frame_ready -> grd_thread_dispatch_in_impl -> egl_task_source_dispatch
This bug was fixed in the package gnome-remote-desktop - 42.9-0ubuntu0.22.04.2 --- gnome-remote-desktop (42.9-0ubuntu0.22.04.2) jammy; urgency=medium * debian/patches: Add upstream fixes for a shutdown crash (LP: #2024237) -- Marco Trevisan (Treviño) Tue, 29 Aug 2023 16:47:38 +0200 ** Changed in: gnome-remote-desktop (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/2024237 Title: gnome-remote-desktop-daemon segfaults on push_queue -> pw_stream_queue_buffer -> on_frame_ready -> grd_thread_dispatch_in_impl -> egl_task_source_dispatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059340] Re: crash in libsofthsm2 on armhf after time_t transition
I have encountered a similar problem when running test case of ima-evm- utils with softhsm used as engine on Ubuntu 24.04 (Noble). In this case I am also crashing in pkcs11_slot_unref when this line here is called: CRYPTOKI_call(slot->ctx, C_CloseAllSessions(slot->id)); https://github.com/OpenSC/libp11/blob/libp11-0.4.12/src/p11_slot.c#L433 ima-evm-utils: https://github.com/mimizohar/ima-evm-utils-test/ The evmctl utility has left main() when the crash occurs. So this function is called via some OpenSSL destructor code path. When OPENSSL_cleanup() is called before main() exits then this crash does NOT occur. When single stepping through the crash then it seems that C_CloseAllSessions() does not get called anymore but the crash occurs when it seems like it was trying to call this function. 0x77fb3530 <+96>:call 0x77fae110 0x77fb3535 <+101>: mov0x98(%rbx),%rdi 0x77fb353c <+108>: mov$0x1af,%edx 0x77fb3541 <+113>: mov%r13,%rsi 0x77fb3544 <+116>: call 0x77fadea0 => 0x77fb3549 <+121>: mov0x8(%rbx),%rax 0x77fb354d <+125>: mov0x70(%rbx),%rdi 0x77fb3551 <+129>: mov(%rax),%rax 0x77fb3554 <+132>: call *0x78(%rax) <- crash occurs here 0x77fb3557 <+135>: mov0x78(%rbx),%rdi Notes: - When SoftHSM is used in a test case via an OpenSSL provider, this same crash does NOT occur. - The same test passes on Fedora (latest) when using SoftHSM either via engine or provider interfaces. - Another problem is that I cannot use OPENSSL_cleanup before main() exit since tests on AltLinux and Debian end up failing then for some unknown reason. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059340 Title: crash in libsofthsm2 on armhf after time_t transition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/softhsm2/+bug/2059340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063841] Update Released
The verification of the Stable Release Update for virtualbox has completed successfully and the package is now being 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063841 Title: [SRU] virtualbox crash on network traffic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/2063841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063841] Re: [SRU] virtualbox crash on network traffic
This bug was fixed in the package virtualbox-hwe - 7.0.16-dfsg-2ubuntu1.24.04.2 --- virtualbox-hwe (7.0.16-dfsg-2ubuntu1.24.04.2) noble; urgency=medium * Add patch 162843 to fix an host crash with some network modes. LP: #2063841 -- Gianfranco Costamagna Fri, 26 Apr 2024 12:51:11 +0200 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063841 Title: [SRU] virtualbox crash on network traffic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/2063841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063841] Re: [SRU] virtualbox crash on network traffic
This bug was fixed in the package virtualbox - 7.0.16-dfsg-2ubuntu1 --- virtualbox (7.0.16-dfsg-2ubuntu1) noble; urgency=medium * Add patch 162843 to fix an host crash with some network modes. LP: #2063841 -- Gianfranco Costamagna Fri, 26 Apr 2024 12:51:11 +0200 ** Changed in: virtualbox (Ubuntu Noble) Status: Fix Committed => Fix Released ** Changed in: virtualbox-hwe (Ubuntu Noble) 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/2063841 Title: [SRU] virtualbox crash on network traffic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/2063841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069092] Re: Xorg freeze
it happens very randomly, cant record it with second camera, cant trigger that. After several hours of using pc that happens. ** Summary changed: - Xorg freeze + whole system hangs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069092 Title: whole system hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2069092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060992] Re: aws: Support hibernation on Graviton
Batch tested the proposed kernel for Jammy 6.5 and achieved 99+% success rate on CLI/console initiated Hibernate/Resumes. Complete batch tests across all ARM supported instance types ran previously, limited this test to the M6g family as confirmation. High level testing details: 1.) Spun up instance with patched AMI + this hibinit-agent ppa (https://launchpad.net/~mitchdz/+archive/ubuntu/ec2-hibinit-agent-arm). 2.) Started up bashscript "heartbeat" on the instance, pushing timestamp to dynamoDB table every 30 seconds. 3.) Hibernated instance through the AWS CLI 4.) Resumed instance through the AWS CLI 5.) Confirmed "heartbeat" updates to dynamoDB table after resume 6.) Repeated once more. Manually tested instance initiated hibernation successfully: High level testing details: 1.) Spun up instance with patched AMI + this hibinit-agent patch (https://git.launchpad.net/~secarola/ubuntu/+source/ec2-hibinit-agent/commit/?h=applied/ubuntu/jammy-devel&id=034ec3ffdc8cbd9d319aa5815f02d60ec3e27f93). 2.) Connected to the instance and started up bash script "heartbeat" on the instance, writing to text file every second with new timestamp. #!/bin/bash while : do echo $(date) > text.txt sleep 1 done 3.) Hibernated instance through the GuestOS. sudo swapon --priority=32767 /swap-hibinit sudo systemctl hibernate 4.) Confirmed that hosting environments reported the instance as Hibernated and not shutdown. 4.) Resumed instance through the AWS CLI 5.) Connected to the instance and confirmed the date was still being written to the text file cat text.txt ** Tags removed: verification-needed-jammy-linux-aws-6.5 ** Tags added: verification-done-jammy-linux-aws-6.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060992 Title: aws: Support hibernation on Graviton To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2060992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063879] Update Released
The verification of the Stable Release Update for easyeffects has completed successfully and the package is now being 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063879 Title: [SRU] EasyEffects Depends: calf-plugins should be Recommends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/easyeffects/+bug/2063879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063879] Re: [SRU] EasyEffects Depends: calf-plugins should be Recommends
This bug was fixed in the package easyeffects - 7.1.6-1ubuntu0.24.04.1 --- easyeffects (7.1.6-1ubuntu0.24.04.1) noble; urgency=medium * No-change SRU backport to noble (LP: #2063879) -- Erich Eickmeyer Wed, 29 May 2024 08:57:24 -0700 ** Changed in: easyeffects (Ubuntu Noble) 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/2063879 Title: [SRU] EasyEffects Depends: calf-plugins should be Recommends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/easyeffects/+bug/2063879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069092] [NEW] whole system hangs
Public bug reported: Under "tested" nvidia driver it hangs, when i compiled manually on 23.10 version which is far before newer i never had hard crash. But it was pissing me off since every kernel update had to recompile driver again. Secondly, on 23.10 i was staying on wayland, now on X11. Not sure what is causing hard crash. Totally dead, before it happens i have slown down for about 1,2 seconds, then dead, no ctrl+alt+f2345 works, only power ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4 Uname: Linux 6.8.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 535.171.04 Tue Mar 19 20:30:00 UTC 2024 GCC version: ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Tue Jun 11 21:52:14 2024 DistUpgraded: 2024-05-23 01:17:19,732 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GA107M [GeForce RTX 3050 Mobile] [1558:5e00] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [1002:1638] (rev c6) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [1558:5e00] InstallationDate: Installed on 2024-03-16 (87 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) MachineType: MEDION Crawler E25 ProcEnviron: LANG=pl_PL.UTF-8 LANGUAGE= PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-35-generic root=UUID=aa02f2dd-89eb-4b06-a98f-3fe963c633ae ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to noble on 2024-05-23 (20 days ago) dmi.bios.date: 05/10/2022 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: NHxxEx dmi.board.vendor: MEDION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05RME1:bd05/10/2022:br7.5:svnMEDION:pnCrawlerE25:pvrNotApplicable:rvnMEDION:rnNHxxEx:rvr1.0:cvnMEDION:ct10:cvrN/A:skuML-21000830031834: dmi.product.family: Erazer dmi.product.name: Crawler E25 dmi.product.sku: ML-210008 30031834 dmi.product.version: Not Applicable dmi.sys.vendor: MEDION version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 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:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze kubuntu noble possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069092 Title: whole system hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2069092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968430] Re: tripwire --init Segmentation Fault
I remade the deb package from the same sources on a currently updated system with no change. Removing '--enable-static' from debian/rules resulted a working 'tripwire --init'. Hope it helps someone else. Brief notes (I was building on 'nebula' and running on 'muggle2'). search for the amd64 package for ubuntu at https://debian.pkgs.org/sid/debian-main-amd64/ Package Homepagehttps://launchpad.net/ubuntu/jammy/+source/tripwire ssh nebula # [update system] cd ~/dpkg-rebuild mkdir tripwire cd !$ wget \ https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/tripwire/2.4.3.7-4/tripwire_2.4.3.7-4.dsc \ https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/tripwire/2.4.3.7-4/tripwire_2.4.3.7.orig.tar.gz \ https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/tripwire/2.4.3.7-4/tripwire_2.4.3.7-4.debian.tar.xz # verify checksums on web page sha256sum * dpkg-source -x tripwire_2.4.3.7-4.dsc # tab completion is nice # bump version + changelog entry - see https://wiki.debian.org/BuildingTutorial dch -n time debuild -b -uc -us # 2m47s on nebula, i9-12900K. didn't seem parallel at all cd .. ls # looky at all those shiny new debs! ls -l tripwire_2.4.3.7-4.1_amd64.* -rw-r--r-- 1 schanzle 771div 148316 Jun 10 18:12 tripwire_2.4.3.7-4.1_amd64.build -rw-r--r-- 1 schanzle 771div7096 Jun 10 18:12 tripwire_2.4.3.7-4.1_amd64.buildinfo -rw-r--r-- 1 schanzle 771div1391 Jun 10 18:12 tripwire_2.4.3.7-4.1_amd64.changes -rw-r--r-- 1 schanzle 771div 1864346 Jun 10 18:12 tripwire_2.4.3.7-4.1_amd64.deb # installed on muggle2...tripwire --initsuspense... # dang, still crashed. Software interrupt forced exit: Segmentation Fault real7m28.401s # try rebuilding w/o --enable-static in debian/rules # YES!! Successful 'tripwire --init' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968430 Title: tripwire --init Segmentation Fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tripwire/+bug/1968430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2041831] Re: /usr/bin/update-manager:11:g_type_check_instance_is_fundamentally_a:g_object_ref:gdk_event_copy:pygi_boxed_copy_in_place:arg_boxed_to_py_cleanup
Apport didn't work for me either, so I ran gdb python manually. The traceback is identical to the OP one in bug #2027941. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2041831 Title: /usr/bin/update- manager:11:g_type_check_instance_is_fundamentally_a:g_object_ref:gdk_event_copy:pygi_boxed_copy_in_place:arg_boxed_to_py_cleanup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/2041831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068805] Re: "Install Now" button disappears for good if all packages unselected
I think you got segfaults because you hit bug #2027941 (or #2041831, the "secret" report, dunno which one should be made duplicate). I guess you used a mouse click to deselect :) If you use the spacebar to deselect, you can probably reproduce this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068805 Title: "Install Now" button disappears for good if all packages unselected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2068805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066914] Re: tmux 3.4 stalls during active pane zoom
It seems that a recently launched tmux server behaves better and the performance gets worse over time. With that anecdotal evidence, it's hard to say if my tmux.conf influences the slowness but it seems to slow down the longer run it without my configuration. Is there any interesting information I can collect during the degradation that would inform what is happening during the grid reflow/reallocation? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066914 Title: tmux 3.4 stalls during active pane zoom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/2066914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2055114] Re: fail2ban is broken in 24.04 Noble
The new package has been working good for me EXCEPT wordpress thinks it isn't running even though it is AND it acts on the WordPress filters and jails I have installed. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Tue, 11 Jun 2024, Brian Murray wrote: > Date: Tue, 11 Jun 2024 20:05:13 - > From: Brian Murray <2055...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 2055114] Re: fail2ban is broken in 24.04 Noble > > Hello Robert, or anyone else affected, > > Accepted fail2ban into noble-proposed. The package will build now and be > available at > https://launchpad.net/ubuntu/+source/fail2ban/1.0.2-3ubuntu0.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: fail2ban (Ubuntu Noble) > Status: Confirmed => Fix Committed > > ** Tags added: verification-needed verification-needed-noble > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2055114 > > Title: > fail2ban is broken in 24.04 Noble > > Status in fail2ban package in Ubuntu: > Fix Released > Status in fail2ban source package in Noble: > Fix Committed > Status in fail2ban source package in Oracular: > Fix Released > > Bug description: > [ Impact ] > * fail2ban fails to start on Ubuntu 24.04, due to new Python and deprecated > classes (now vendored upstream) > > [ Test Plan ] > * Install and check systemctl status fail2ban. > > [ Where problems could occur ] > * Nowhere, fixing a program failing to start > > [ Other info ] > Was working in 22.04, but after upgrading to 24.04 I get this: > > × fail2ban.service - Fail2Ban Service > Loaded: loaded (/etc/systemd/system/fail2ban.service; enabled; preset: > enabled) > Active: failed (Result: exit-code) since Sun 2024-02-25 02:27:29 PST; 1 > day 18h ago > Duration: 2.330s > Docs: man:fail2ban(1) > Process: 1130 ExecStartPre=/bin/mkdir -p /run/fail2ban (code=exited, > status=0/SUCCESS) > Process: 1133 ExecStart=/usr/local/bin/fail2ban-server -xf start > (code=exited, status=255/EXCEPTION) > Main PID: 1133 (code=exited, status=255/EXCEPTION) > CPU: 660ms > > Feb 25 02:27:26 mx1 systemd[1]: Starting fail2ban.service - Fail2Ban > Service... > Feb 25 02:27:26 mx1 systemd[1]: Started fail2ban.service - Fail2Ban Service. > Feb 25 02:27:28 mx1 fail2ban-server[1133]: 2024-02-25 02:27:28,952 fail2ban > [1133]: ERROR No module named 'asynchat' > Feb 25 02:27:29 mx1 systemd[1]: fail2ban.service: Main process exited, > code=exited, status=255/EXCEPTION > Feb 25 02:27:29 mx1 systemd[1]: fail2ban.service: Failed with result > 'exit-code'. > > grep fail2ban syslog > 2024-02-25T02:25:17.813593-08:00 mx1 systemd[1]: Stopping fail2ban.service - > Fail2Ban Service... > 2024-02-25T02:27:26.625640-08:00 mx1 systemd[1]: Starting fail2ban.service - > Fail2Ban Service... > 2024-02-25T02:27:26.678572-08:00 mx1 systemd[1]: Started fail2ban.service - > Fail2Ban Service. > 2024-02-25T02:27:28.954548-08:00 mx1 fail2ban-server[1133]: 2024-02-25 > 02:27:28,952 fail2ban[1133]: ERROR No module named > 'asynchat' > 2024-02-25T02:27:29.004733-08:00 mx1 systemd[1]: fail2ban.service: Main > process exited, code=exited, status=255/EXCEPTION > 2024-02-25T02:27:29.004834-08:00 mx1 systemd[1]: fail2ban.service: Failed > with result 'exit-code'. > > Seems 24.04 is missing a python 3.12 module 'asynchat'. > > This leaves my systems vulnerable to brute-force password guessing > attacks. > > ProblemType: Bug > DistroRelease: Ubuntu 24.04 > Package: fail2ban 1.0.2-3 > Uname: Linux 6.7.6 x86_64 > ApportVersion: 2.2
[Bug 2069090] [NEW] error on my packaged jammy
Public bug reported: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 [origin: unknown] ProcVersionSignature: Ubuntu 5.15.0-107.117-generic 5.15.149 Uname: Linux 5.15.0-107-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 600:109:116:37:2024-06-01 21:52:42.417328142 -0600:2024-06-01 16:32:12.914270998 -0600:/var/crash/_usr_bin_gnome-shell.122.uploaded 640:0:116:34569:2024-06-01 23:29:36.522152900 -0600:2024-06-01 23:29:37.522152900 -0600:/var/crash/_usr_bin_add-apt-repository.0.crash 644:0:116:0:2024-06-01 21:49:43.722818411 -0600:2024-06-01 21:49:43.722818411 -0600:/var/crash/_usr_bin_gnome-shell.122.upload 640:122:116:17606803:2024-06-02 22:21:30.263546943 -0600:2024-06-02 22:34:26.278599780 -0600:/var/crash/_usr_bin_gnome-shell.122.crash 640:1000:116:135087:2024-06-02 00:23:26.533292770 -0600:2024-06-02 00:23:27.533292770 -0600:/var/crash/_usr_lib_x86_64-linux-gnu_webkit2gtk-4.0_WebKitWebProcess.1000.crash CurrentDesktop: ubuntu:GNOME Date: Sun Jun 2 23:35:59 2024 InstallationDate: Installed on 2022-04-26 (768 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to jammy on 2024-06-01 (1 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting ** Affects: ubuntu-release-upgrader (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/2069090 Title: error on my packaged jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2069090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068750] Re: [SRU] webkit2gtk does not ask for smartcard PIN
Closing this ticket as not needed anymore. Feel free to open again if this functionality is needed. ** Changed in: webkit2gtk (Ubuntu) Status: New => Fix Released ** Changed in: webkit2gtk (Ubuntu Focal) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068750 Title: [SRU] webkit2gtk does not ask for smartcard PIN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2068750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066275] Please test proposed package
Hello Scarlett, or anyone else affected, Accepted sddm into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sddm/0.20.0-2ubuntu4.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 sddm in Ubuntu. https://bugs.launchpad.net/bugs/2066275 Title: [SRU] Fix black screen on second boot due to video drivers not being ready. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/2066275/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 2066275] Re: [SRU] Fix black screen on second boot due to video drivers not being ready.
I don't understand why a second bug was created for this SRU when using bug 2063143 (of which bug 2065321 is a duplicate) would likely have more people willing to do the verification. ** Changed in: sddm (Ubuntu Noble) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066275 Title: [SRU] Fix black screen on second boot due to video drivers not being ready. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/2066275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066275] Re: [SRU] Fix black screen on second boot due to video drivers not being ready.
I looked at the source code for sddm in Oracular and discovered that this change is included in it so I'm marking the Oracular task as Fix Released. ** Changed in: sddm (Ubuntu) Status: Confirmed => 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/2066275 Title: [SRU] Fix black screen on second boot due to video drivers not being ready. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/2066275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
