[Bug 1960898] Re: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject())
1.) Start Ubuntu 2.) Login 3.) Gnome-Shell appear for a short time 4.) I end back on the login screen 5.) I change to xorg and log in succesfully I reportat this on: https://discourse.ubuntu.com/t/since-update-to-jelly-wayland-do-not-anymore-work/26681 According to the feedback i got I Created this bug-report with 'ubuntu-bug gnome-shell' now I try to do 'ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash' I got the feedback, that it was already reportet on: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959507 So I'm currently not sure if it is a duplicate or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960898 Title: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1960898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920205] Re: [MIR] oem-somerville-weedle-meta
oem-somerville-weedle-meta 20.04~ubuntu1 has been put into https://launchpad.net/ubuntu/focal/+queue. ** Changed in: ubuntu Status: Confirmed => In Progress ** Tags removed: oem-needs-upload ** Tags added: oem-done-upload ** Description changed: [Background] Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details. [Impact] - 1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive. - 2. The background and impact of the situation for this change, and it's impact. + 1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive. + 2. The background and impact of the situation for this change, and it's impact. [Testing] - 1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware - 2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the hardware - 3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly. + 1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware + 2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the hardware + 3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly. [Regression Potential] Most potential regressions will live in the package set that will be installed via dependency of this package, which live in OEM archive (outside of Ubuntu) and control by OEM team. OEM team and other corresponding team need take responsibility of those dependency installed. [When switching kernel flavour] Check that the new kernel flavour works on the target platform. [Availability] This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet. The source code of the oem-somerville-weedle-meta for focal: - git clone -b weedle-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-somerville-projects-meta + git clone -b weedle-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-somerville-projects-meta [Rationale] We want to improve the hardware support for some Dell platforms. [Security] No CVE/known security issue. [Quality assurance] I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Dell platforms. oem-somerville-weedle-meta will be upgraded to 20.04ubuntu1 or the later version from OEM archive. [Dependencies] It only depends on ubuntu-oem-keyring. [Standards compliance] This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM. [Maintenance] Canonical OEM Enablement Team will take care of the maintenance. [Background information] Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details. Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to verify this MIR against the reference package in the archive. https://ubuntu.com/certified/202010-28295 - https://ubuntu.com/certified/202012-28569 - https://ubuntu.com/certified/202012-28584 - https://ubuntu.com/certified/202107-29292 - https://ubuntu.com/certified/202107-29293 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920205 Title: [MIR] oem-somerville-weedle-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960898] Re: Since Update to Jelly Wayland do not work
Oh sorry, I see the problem: [ 76.192764] Klappi org.gnome.Shell.desktop[3287]: Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) [ 76.201950] Klappi org.gnome.Shell.desktop[3287]: Bail out! Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) [ 76.202235] Klappi org.gnome.Shell.desktop[3287]: GNOME Shell crashed with signal 6 [ 76.202346] Klappi org.gnome.Shell.desktop[3287]: == Stack trace for context 0x560ede973210 == [ 76.202456] Klappi org.gnome.Shell.desktop[3287]: #0 560ee0d94590 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:1108 (32b00966a330 @ 13) [ 76.202558] Klappi org.gnome.Shell.desktop[3287]: #1 560ee0d944e8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:1180 (32b009663e70 @ 33) [ 76.202650] Klappi org.gnome.Shell.desktop[3287]: #2 560ee0d94448 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:1235 (32b009663ce0 @ 127) [ 76.202743] Klappi org.gnome.Shell.desktop[3287]: #3 560ee0d943b8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:1150 (32b00966a150 @ 15) ** Package changed: ubuntu => mutter (Ubuntu) ** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Since Update to Jelly Wayland do not work + Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960898 Title: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1960898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960899] [NEW] nfs-ganesha doesn't ship the ganesha-rados-grace binary target in Focal
Public bug reported: While the source is all present, the debian/control file doesn't build the binary package for ganesha-rados-grace. ** Affects: nfs-ganesha (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: nfs-ganesha (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nfs-ganesha (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: nfs-ganesha (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/1960899 Title: nfs-ganesha doesn't ship the ganesha-rados-grace binary target in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/1960899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848942] Re: Freeze on opening font viewer
Same issue with Ubuntu 20.04, gnome-font-viewer 3.34.0-2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848942 Title: Freeze on opening font viewer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1848942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960898] Re: Since Update to Jelly Wayland do not work
Thanks for the bug report. Can you explain in more detail what is not working? Maybe with a photo or video? ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Package changed: gnome-shell (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960898 Title: Since Update to Jelly Wayland do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
I created a PPA with prebuilt kernels for Jammy & Focal oem in https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1950062. Could you help verify them? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1950062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951837] Re: new kernel 5.4.0-90-generic contain error with snat in vrf
Hi, Thanks for reporting this issue. If the behavior fails due to a kernel update, it's unlikely to be a problem in the user space nftables tool. Looking for suspicious commits between 5.4.0-84.94 and 5.4.0-90.101, https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/commit/?id=318d87fed75ab207f5913ae5c6abf4f781c507f1 looks supicious and landed in 5.4.0-89.100. However, that commit was reverted in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/commit/?id=cb3a632a2da90d23629b59c8da26460af0bc455a , which landed in 5.4.0-97.110, published to focal at https://launchpad.net/ubuntu/+source/linux/5.4.0-97.110 on February 7, 2022. Are you still seeing this issue? ** Changed in: nftables (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951837 Title: new kernel 5.4.0-90-generic contain error with snat in vrf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958019]
Probably the models of laptop each need their own set of verbs. On 2/14/22 05:34, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > --- Comment #552 from Jürg Lempen (i...@jlempen.com) --- > Hi all, > > Good news for Lenovo Yoga Duet 7 13IML05 owners! > > The HDA verbs (and therefore the quirks) for the Yoga 7 work perfectly on the > Yoga Duet 7 13IML05 after the following patch is reverted: > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/diff/releases/5.4.89/alsa-hda-realtek-fix-speaker-volume-control-on-lenovo-c940.patch?id=1889f9ac9f9eb7f91ffc22e607a2e3db3db2e72e > > Thus, writing a kernel patch for the Yoga Duet 7 becomes trivial: > > --- a/sound/pci/hda/patch_realtek.c > +++ a/sound/pci/hda/patch_realtek.c > @@ -9008,7 +9008,7 @@ > SND_PCI_QUIRK(0x17aa, 0x3178, "ThinkCentre Station", > ALC283_FIXUP_HEADSET_MIC), > SND_PCI_QUIRK(0x17aa, 0x31af, "ThinkCentre Station", > ALC623_FIXUP_LENOVO_THINKSTATION_P340), > SND_PCI_QUIRK(0x17aa, 0x3813, "Legion 7i 15IMHG05", > ALC287_FIXUP_LEGION_15IMHG05_SPEAKERS), > - SND_PCI_QUIRK(0x17aa, 0x3818, "Lenovo C940", > ALC298_FIXUP_LENOVO_SPK_VOLUME), > + SND_PCI_QUIRK(0x17aa, 0x3818, "Yoga Duet 7 13IML05", > ALC287_FIXUP_YOGA7_14ITL_SPEAKERS), > SND_PCI_QUIRK(0x17aa, 0x3819, "Lenovo 13s Gen2 ITL", > ALC287_FIXUP_13S_GEN2_SPEAKERS), > SND_PCI_QUIRK(0x17aa, 0x3824, "Legion Y9000X 2020", > ALC285_FIXUP_LEGION_Y9000X_SPEAKERS), > SND_PCI_QUIRK(0x17aa, 0x3827, "Ideapad S740", > ALC285_FIXUP_IDEAPAD_S740_COEF), > > With this patch, the internal speakers, headphones, headset mic and internal > microphone all work on the Duet 7. > > Now, I'm not sure how to get this patch to be merged, as reverting the patch > for the C940 would obviously break sound on the C940. Why Lenovo decided to > use > the same subsystem ID (0x17aa, 0x3818) on both laptops is beyond me. I > haven't > been able to find another example of identical subsystem IDs for two > different > machines anywhere else in the "patch_realtek.c" file. At first, I thought > that > simply adding the quirk for the Yoga Duet 7 with the same subsystem ID might > work, as the different DMI info allows to distinguish between both laptops. > Well, that doesn't do the trick, so the only working fix right now is to > revert > the c940 patch. > > Perhaps someone from the ALSA team would know how to deal with this odd > issue. > > By the way, no need to compile the whole kernel, compiling the > 'snd-hda-codec-realtek.ko' module is enough. Backup and replace the module in > /lib/modules/5.x.x/kernel/sound/pci/hda/ with the new module you just > compiled > and reboot to have working sound. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958019]
Hi all, Good news for Lenovo Yoga Duet 7 13IML05 owners! The HDA verbs (and therefore the quirks) for the Yoga 7 work perfectly on the Yoga Duet 7 13IML05 after the following patch is reverted: https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/diff/releases/5.4.89/alsa-hda-realtek-fix-speaker-volume-control-on-lenovo-c940.patch?id=1889f9ac9f9eb7f91ffc22e607a2e3db3db2e72e Thus, writing a kernel patch for the Yoga Duet 7 becomes trivial: --- a/sound/pci/hda/patch_realtek.c +++ a/sound/pci/hda/patch_realtek.c @@ -9008,7 +9008,7 @@ SND_PCI_QUIRK(0x17aa, 0x3178, "ThinkCentre Station", ALC283_FIXUP_HEADSET_MIC), SND_PCI_QUIRK(0x17aa, 0x31af, "ThinkCentre Station", ALC623_FIXUP_LENOVO_THINKSTATION_P340), SND_PCI_QUIRK(0x17aa, 0x3813, "Legion 7i 15IMHG05", ALC287_FIXUP_LEGION_15IMHG05_SPEAKERS), - SND_PCI_QUIRK(0x17aa, 0x3818, "Lenovo C940", ALC298_FIXUP_LENOVO_SPK_VOLUME), + SND_PCI_QUIRK(0x17aa, 0x3818, "Yoga Duet 7 13IML05", ALC287_FIXUP_YOGA7_14ITL_SPEAKERS), SND_PCI_QUIRK(0x17aa, 0x3819, "Lenovo 13s Gen2 ITL", ALC287_FIXUP_13S_GEN2_SPEAKERS), SND_PCI_QUIRK(0x17aa, 0x3824, "Legion Y9000X 2020", ALC285_FIXUP_LEGION_Y9000X_SPEAKERS), SND_PCI_QUIRK(0x17aa, 0x3827, "Ideapad S740", ALC285_FIXUP_IDEAPAD_S740_COEF), With this patch, the internal speakers, headphones, headset mic and internal microphone all work on the Duet 7. Now, I'm not sure how to get this patch to be merged, as reverting the patch for the C940 would obviously break sound on the C940. Why Lenovo decided to use the same subsystem ID (0x17aa, 0x3818) on both laptops is beyond me. I haven't been able to find another example of identical subsystem IDs for two different machines anywhere else in the "patch_realtek.c" file. At first, I thought that simply adding the quirk for the Yoga Duet 7 with the same subsystem ID might work, as the different DMI info allows to distinguish between both laptops. Well, that doesn't do the trick, so the only working fix right now is to revert the c940 patch. Perhaps someone from the ALSA team would know how to deal with this odd issue. By the way, no need to compile the whole kernel, compiling the 'snd-hda- codec-realtek.ko' module is enough. Backup and replace the module in /lib/modules/5.x.x/kernel/sound/pci/hda/ with the new module you just compiled and reboot to have working sound. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960898] [NEW] Since Update to Jelly Wayland do not work
Public bug reported: Hardware: https://linux-hardware.org/?probe=1055dc7082 Worked without Problem in 21.04 Had some flicker and problem with the left dock in 21.10 not working since updating to 22.04 now I'm running xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Feb 15 08:07:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-15 (183 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-14 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960898 Title: Since Update to Jelly Wayland do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956063] Re: Change of video card from nVidia to AMD breaks Chromium Snap
Excellent, thanks for following up! I'm glad the issue is resolved for you. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956063 Title: Change of video card from nVidia to AMD breaks Chromium Snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955844] Re: Enlightenment cannot successfully start the enlightenment_system service since it can't become group root. Missing setuid bit?
The deb-package should install these files with suid bits. Otherwise it it not user-friendly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955844 Title: Enlightenment cannot successfully start the enlightenment_system service since it can't become group root. Missing setuid bit? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/enlightenment/+bug/1955844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960592] Re: `apt build-dep qemu-system-ppc` fails
Hi, I think this is actually a known non-issue. Your command is equal to: $ sudo apt build-dep qemu That is you asking for the complete build dependencies of qemu, which include some bits that need to be cross compiled for various architectures. That is what adds the dependencies to all the gcc-$arch cross compilation packages which are not available on ppc64 systems. But - if you do not want to build "all of qemu" and instead are just interested to build qemu on ppc64 - you can tell apt that this is what you want. From the man page: --arch-only Only process architecture-dependent build-dependencies. So with the following you most likely get what you actually wanted (and it works on ppc64): $ sudo apt --arch-only build-dep qemu If I'm wrong and you did want to build not only the ppc64 but also the arch independent binaries in ppc64, then this bug would actually be a feature request to the cross toolchain to be available on more architectures. Either way as I see it right now it does not seem to be a mistake in qemu, but you can let us know once you had time to read this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960592 Title: `apt build-dep qemu-system-ppc` fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1960592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960893] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (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/1960893 Title: i915 gives trace in dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960895] [NEW] apt ubuntu-driver-460 Point to 470.103.01-0ubuntu0.18.04.1
Public bug reported: libnvidia-cfg1-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-common-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 all [upgradable from: 460.106.00-0ubuntu1] libnvidia-compute-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-decode-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-encode-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-extra-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-fbc1-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-gl-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-ifr1-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] mesa-vdpau-drivers/bionic-updates 20.0.8-0ubuntu1~18.04.1 amd64 [upgradable from: 18.0.0~rc5-1ubuntu1] nvidia-compute-utils-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] nvidia-dkms-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] nvidia-driver-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] nvidia-kernel-common-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] nvidia-kernel-source-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] nvidia-prime/bionic-updates 0.8.16~0.18.04.1 all [upgradable from: 0.8.8] nvidia-utils-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] ubuntu-mono/bionic-updates 16.10+18.04.20181005-0ubuntu1 all [upgradable from: 16.10+18.04.20180421.1-0ubuntu1] x11-common/bionic-updates 1:7.7+19ubuntu7.1 all [upgradable from: 1:7.7+19ubuntu7] x11-xkb-utils/bionic-updates 7.7+3ubuntu0.18.04.1 amd64 [upgradable from: 7.7+3] xserver-common/bionic-updates,bionic-security 2:1.19.6-1ubuntu4.10 all [upgradable from: 2:1.19.6-1ubuntu4] xserver-xorg-core/bionic-updates,bionic-security 2:1.19.6-1ubuntu4.10 amd64 [upgradable from: 2:1.19.6-1ubuntu4] xserver-xorg-video-nvidia-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960895 Title: apt ubuntu-driver-460 Point to 470.103.01-0ubuntu0.18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960893] [NEW] i915 gives trace in dmesg
Public bug reported: [1.904158] kernel: [ cut here ] [1.904159] kernel: i915 :00:02.0: drm_WARN_ON(val == 0x) [1.904176] kernel: WARNING: CPU: 3 PID: 328 at drivers/gpu/drm/i915/display/intel_tc.c:761 intel_tc_port_init+0x1c4/0x1d0 [i915] [1.904264] kernel: Modules linked in: snd_hda_intel kvm_intel(+) snd_intel_dspcfg intel_rapl_msr(+) snd_intel_sdw_acpi kvm snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul ghash_clmulni_intel snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi i915(+) aesni_intel joydev crypto_simd cryptd rtw88_8821ce rtw88_8821c snd_seq rtw88_pci rtw88_core snd_seq_device intel_cstate nls_iso8859_1 snd_timer ttm mac80211 drm_kms_helper serio_raw cec hp_wmi rc_core processor_thermal_device_pci_legacy sparse_keymap processor_thermal_device i2c_algo_bit platform_profile wmi_bmof efi_pstore snd processor_thermal_rfim mei_me fb_sys_fops processor_thermal_mbox syscopyarea cfg80211 processor_thermal_rapl hid_multitouch mei ee1004 intel_rapl_common sysfillrect soundcore libarc4 sysimgblt intel_soc_dts_iosf mac_hid int3400_thermal wireless_hotkey dptf_pch_fivr acpi_pad acpi_thermal_rel int3403_thermal int340x_thermal_zone sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables [1.904304] kernel: x_tables autofs4 hid_generic nvme nvme_core i2c_i801 crc32_pclmul i2c_smbus intel_lpss_pci intel_lpss idma64 vmd xhci_pci xhci_pci_renesas wmi i2c_hid_acpi i2c_hid hid video pinctrl_tigerlake [1.904312] kernel: CPU: 3 PID: 328 Comm: systemd-udevd Not tainted 5.15.0-18-generic #18-Ubuntu [1.904314] kernel: Hardware name: HP HP Laptop 14s-dq2xxx/87FD, BIOS F.09 02/19/2021 [1.904315] kernel: RIP: 0010:intel_tc_port_init+0x1c4/0x1d0 [i915] [1.904369] kernel: Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 85 e8 35 e2 48 c7 c1 a0 ef bc c0 4c 89 ea 48 c7 c7 77 d8 be c0 48 89 c6 e8 1d ab 7c e2 <0f> 0b e9 55 ff ff ff 0f 1f 44 00 00 0f 1f 44 00 00 55 48 8b 17 80 [1.904370] kernel: RSP: 0018:a22780973808 EFLAGS: 00010286 [1.904372] kernel: RAX: RBX: 93cf4882e000 RCX: 0027 [1.904373] kernel: RDX: 93d0b7ba09c8 RSI: 0001 RDI: 93d0b7ba09c0 [1.904373] kernel: RBP: a22780973838 R08: 0003 R09: a4be0e12 [1.904374] kernel: R10: R11: 0001 R12: [1.904374] kernel: R13: 93cf41550720 R14: 93cf4882efa0 R15: [1.904375] kernel: FS: 7f63046e98c0() GS:93d0b7b8() knlGS: [1.904376] kernel: CS: 0010 DS: ES: CR0: 80050033 [1.904377] kernel: CR2: 7fc171f1aaa0 CR3: 00010715e006 CR4: 00770ee0 [1.904378] kernel: PKRU: 5554 [1.904378] kernel: Call Trace: [1.904379] kernel: [1.904381] kernel: intel_ddi_init+0x6a0/0xbd0 [i915] [1.904447] kernel: ? __cond_resched+0x1a/0x50 [1.904451] kernel: intel_setup_outputs+0x304/0xc70 [i915] [1.904514] kernel: intel_modeset_init_nogem+0x290/0x510 [i915] [1.904562] kernel: ? intel_irq_postinstall+0x38b/0x680 [i915] [1.904608] kernel: i915_driver_probe+0x1b7/0x470 [i915] [1.904648] kernel: ? mutex_lock+0x13/0x40 [1.904650] kernel: i915_pci_probe+0x58/0x140 [i915] [1.904689] kernel: local_pci_probe+0x48/0x90 [1.904692] kernel: pci_device_probe+0x115/0x1f0 [1.904693] kernel: really_probe+0x21b/0x420 [1.904696] kernel: __driver_probe_device+0x115/0x190 [1.904697] kernel: driver_probe_device+0x23/0xc0 [1.904699] kernel: __driver_attach+0xbd/0x1d0 [1.904700] kernel: ? __device_attach_driver+0x110/0x110 [1.904702] kernel: bus_for_each_dev+0x7c/0xc0 [1.904704] kernel: driver_attach+0x1e/0x20 [1.904705] kernel: bus_add_driver+0x135/0x200 [1.904707] kernel: driver_register+0x95/0xf0 [1.904708] kernel: __pci_register_driver+0x68/0x70 [1.904709] kernel: i915_register_pci_driver+0x23/0x30 [i915] [1.904746] kernel: i915_init+0x3b/0xfc [i915] [1.904793] kernel: ? 0xc0cad000 [1.904794] kernel: do_one_initcall+0x46/0x1d0 [1.904797] kernel: ? kmem_cache_alloc_trace+0x19e/0x2e0 [1.904800] kernel: do_init_module+0x62/0x280 [1.904801] kernel: load_module+0xac9/0xbb0 [1.904803] kernel: __do_sys_finit_module+0xbf/0x120 [1.904804] kernel: __x64_sys_finit_module+0x18/0x20 [1.904805] kernel: do_syscall_64+0x59/0xc0 [1.904807] kernel: ? fput+0x13/0x20 [1.904809] kernel: ? ksys_mmap_pgoff+0x150/0x2b0 [1.904810] kernel: ? exit_to_user_mode_prepare+0x37/0xb0 [1.904812] kernel: ? syscall_exit_to_user_mode+0x27/0x50 [1.904814] kernel: ? __x64_sys_mmap+0x33/0x40 [1.904816] kernel: ? do_syscall_64+0x69/0xc0 [1.904817] kernel: ? do_syscall_64+0x69/0xc0 [1.904818] kernel: ? syscall_exit_to_user_mode+0x27/0x50 [1.904819] kernel: ?
[Bug 1960313] Re: [snap] chromium crashes regularly
Sorry, I missed the prior crash, but hopefully this one contains something that is useful https://pastebin.ubuntu.com/p/c5TTS6bXdP/ Not sure if helpful, but I use `chromium` for sites related to google (or where I use google SSO to login). - gmail (regularly refresh this; it's set for manual refresh though so I'm hitting 'inbox' to refresh) - google docs (Ubuntu News etc; not today) - mewe (not often, ; I posted UWN this morning; ~7 hours ago) - youtube (my primary use of chromium; about all today really) chromium is left open & idle; most crashes are whilst idle. this time it wasn't idle; I was refreshing gmail page on one window, and in process of switching to a different youtube vid on other window.. (most sites (non-google); including launchpad etc. I use firefox) last few lines [260919:260923:0215/170900.786576:VERBOSE1:tls_handshaker.cc(104)] TlsClient: Continuing handshake [260919:260923:0215/170900.787131:VERBOSE1:tls_handshaker.cc(115)] TlsClient: SSL_do_handshake returned when entering early data. After retry, rv=-1, SSL_in_early_data=1 [260919:260923:0215/170900.886186:VERBOSE1:tls_handshaker.cc(104)] TlsClient: Continuing handshake [260919:260923:0215/170900.886515:VERBOSE1:tls_handshaker.cc(104)] TlsClient: Continuing handshake [260919:260923:0215/170900.886602:VERBOSE1:tls_client_handshaker.cc(513)] Client: handshake finished [260919:260923:0215/170901.181857:VERBOSE1:network_delegate.cc(34)] NetworkDelegate::NotifyBeforeURLRequest: https://signaler-pa.clients6.google.com/punctual/multi-watch/channel?VER=8=gWmA3cjvRDO-Io5thTAHCcfnERDeMKLhwP9a777x4MI=AIzaSyAWGrfCCr7albM3lmCc937gx4uIphbpeKQ=rpc=yEQaMB5z0Mt6Fvhpwnd8gQ=0=44=xmlhttp=258pfetv9dc5=1 [261888:1:0215/171008.533492:VERBOSE1:navigator_beacon.cc(88)] Send a beacon to "https://www.youtube.com/api/stats/qoe?fmt=134=251=WLB0NxJoDpXAjfpi=detailpage=yt=23858057%2C23983296%2C23986027%2C24001373%2C24002022%2C24002025%2C24002923%2C24004644%2C24007246%2C24044261%2C24080738%2C24082662%2C24135310%2C24139174%2C24148482%2C24153108%2C24154238%2C24166123%2C24170254=427307184=2988=IOEtbGcWoos=gWEHYvyMCcnT3LUP6fi20AI=streamingstats=AAXXzR-NuRq4yiwf=https%3A%2F%2Fwww.youtube.com%2F=p%3A%2F=y=Chrome=98.0.4758.80=WEB=2.20220211.01.00=UNIPLAYER=X11=DESKTOP=178983.821:B=178983.821:544511=178983.821:1:1=178983.821:0.000=178983.821:0.000;, initiator = "https://www.youtube.com/watch?v=IOEtbGcWoos; [261673:1:0215/171008.533581:VERBOSE1:navigator_beacon.cc(88)] Send a beacon to "https://www.youtube.com/api/stats/qoe?fmt=396=251=9cr_pXd_iSq_jENs=detailpage=yt=23858057%2C23983296%2C23986027%2C24001373%2C24002022%2C24002025%2C24002923%2C24004644%2C24007246%2C24044261%2C24080738%2C24082662%2C24135310%2C24139174%2C24148482%2C24153108%2C24154238%2C24166123%2C24170254=427307184=2988=WyvnnCTaYX8=RmEHYsDiG5j_4-EPzfq_sAo=streamingstats=AAXXzRwOLTlBdJbO=Chrome=98.0.4758.80=WEB=2.20220211.01.00=UNIPLAYER=X11=DESKTOP=179036.589:S=179036.589:234978=179036.589:1:1=179036.589:545.000=179036.589:0.000;, initiator = "https://www.youtube.com/watch?v=WyvnnCTaYX8=545s; [261966:1:0215/171008.533516:VERBOSE1:navigator_beacon.cc(88)] Send a beacon to "https://www.youtube.com/api/stats/qoe?fmt=243=251=W241DIQbCQin54FR=detailpage=yt=23858057%2C23983296%2C23986027%2C24001373%2C24002022%2C24002025%2C24002923%2C24004644%2C24007246%2C24044261%2C24080738%2C24082662%2C24135310%2C24139174%2C24148482%2C24153108%2C24154238%2C24166123%2C24170254=427307184=2988=ei6vTY8M0AQ=fWEHYsibCO6Z3LUPr4aIwAY=streamingstats=AAXXzR9QzmzLVf2K=https%3A%2F%2Fwww.youtube.com%2F=p%3A%2F=y=Chrome=98.0.4758.80=WEB=2.20220211.01.00=UNIPLAYER=X11=DESKTOP=178987.530:B=178987.530:882120=178987.530:1:1=178987.530:0.000=178987.530:0.000;, initiator = "https://www.youtube.com/watch?v=ei6vTY8M0AQ; [261986:1:0215/171008.754655:VERBOSE1:navigator_beacon.cc(88)] Send a beacon to "https://www.youtube.com/api/stats/qoe?fmt=396=251=nM27xePNofufu1Ro=detailpage=yt=23858057%2C23983296%2C23986027%2C24001373%2C24002022%2C24002025%2C24002923%2C24004644%2C24007246%2C24044261%2C24080738%2C24082662%2C24135310%2C24139174%2C24148482%2C24153108%2C24154238%2C24166123%2C24170254=427307184=2988=wbKYbLUkIpk=cGEHYokC5Yni3g_d4ozoDA=streamingstats=AAXXzR6IJlC41PJJ=battlefield%20battle=https%3A%2F%2Fwww.youtube.com%2Fresults%3Fsearch_query%3Dbattlefield%2Bbattle=ys=Chrome=98.0.4758.80=WEB=2.20220211.01.00=UNIPLAYER=X11=DESKTOP=179000.288:B=179000.288:849645=179000.288:1:1=179000.288:0.000=179000.288:0.000;, initiator = "https://www.youtube.com/watch?v=wbKYbLUkIpk=PLGIXPT9GK7e6tUaGi2mfZQ08dxGxBkBt4; [261999:1:0215/171008.533590:VERBOSE1:navigator_beacon.cc(88)] Send a beacon to
[Bug 1960892] [NEW] Starting "obs" creates a core dump
Public bug reported: This is on Jammy: $ dpkg -l|grep obs-studio ii obs-studio 27.1.3+dfsg1-2 amd64recorder and streamer for live video content $ obs Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in "" This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb. Aborted (core dumped) tom@thymian:~/devel/canonical/cloudware/cpc_jenkins/wt1$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: obs-studio 27.1.3+dfsg1-2 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 15 07:01:51 2022 InstallationDate: Installed on 2020-12-08 (433 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: obs-studio UpgradeStatus: Upgraded to jammy on 2021-11-30 (76 days ago) ** Affects: obs-studio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960892 Title: Starting "obs" creates a core dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/1960892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960892] Re: Starting "obs" creates a core dump
workaround - install from flathub . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960892 Title: Starting "obs" creates a core dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/1960892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948747] Re: [MIR] oem-sutton.newell-caesar-meta
oem-sutton.newell-caesar-meta 20.04~ubuntu1 has been put into https://launchpad.net/ubuntu/focal/+queue. ** Changed in: ubuntu Status: Confirmed => In Progress ** Tags removed: oem-needs-upload ** Tags added: oem-done-upload -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948747 Title: [MIR] oem-sutton.newell-caesar-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1948747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957948] Re: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1)
This bug seems to also be causing https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1960702 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957948 Title: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1957948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960702] Re: all snap apps gone after snap upgrade
Since using bash instead of fish fixes the issue, I think the problem lies in the snapd+fish integration. Possible workarounds: 1. Revert to bash via chsh as stated above 2. Upgrade fish to 3.2.0 which contains the fish_add_path 3. Wait for newer snapd (which reportedly contains a compatibility fix to continue working with fish 3.1) Also see https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1957948 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960702 Title: all snap apps gone after snap upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1960702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947210] Re: Firefox Snap can't copy or drag in Wayland
Excellent, thanks for following up Tommy. I'm glad the issue is resolved. I'm closing this here, would you mind closing the upstream bug report (https://bugzilla.mozilla.org/show_bug.cgi?id=1729901) yourself? ** Changed in: firefox (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/1947210 Title: Firefox Snap can't copy or drag in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1947210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960875] Re: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-z-systems Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960875 Title: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954965] Re: Need fwupd in focal to support Quectel's modem(EM120/160) firmware update
I have not found new version of fwupd in focal-proposed. It looks like there is some issued in LP#1949412 so the package is removed ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954965 Title: Need fwupd in focal to support Quectel's modem(EM120/160) firmware update To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1954965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954965] Re: Need fwupd in focal to support Quectel's modem(EM120/160) firmware update
** Changed in: fwupd (Ubuntu Focal) Status: Fix Committed => Confirmed ** Changed in: fwupd (Ubuntu Impish) Status: Fix Committed => Confirmed ** Tags removed: verification-needed verification-needed-focal verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954965 Title: Need fwupd in focal to support Quectel's modem(EM120/160) firmware update To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1954965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960891] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (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/1960891 Title: rtw_8821ce :01:00.0: failed to send h2c command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-azure-5.11/5.11.0.1029.32~20.04.27)
All autopkgtests for the newly accepted linux-meta-azure-5.11 (5.11.0.1029.32~20.04.27) for focal have finished running. The following regressions have been reported in tests triggered by the package: lxc/1:4.0.6-0ubuntu1~20.04.1 (arm64) snapd/2.54.2+20.04ubuntu2 (arm64) 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/focal/update_excuses.html#linux-meta-azure-5.11 [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/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954544] Re: No OpenSSL 3.0 support
** Changed in: xca (Debian) 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/1954544 Title: No OpenSSL 3.0 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xca/+bug/1954544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960891] [NEW] rtw_8821ce 0000:01:00.0: failed to send h2c command
Public bug reported: Unstable Wifi Sometimes most Wifi AP's (including my own) or not seen dmesg filled with [di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:54 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:56 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:56 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:56 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:56 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:56 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:58 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:58 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:58 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:58 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:44:58 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:00 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:00 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:00 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:00 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:00 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:02 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:04 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:04 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:04 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:04 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:04 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:06 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:06 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:06 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:06 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:06 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:08 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:08 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:08 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:08 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:08 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:10 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:12 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:12 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:12 2022] rtw_8821ce :01:00.0: failed to send h2c command [di feb 15 06:45:12 2022] rtw_8821ce :01:00.0: failed to send h2c command ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sander 1239 F pulseaudio /dev/snd/pcmC0D0p: sander 1239 F...m pulseaudio /dev/snd/seq:sander 1237 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 15 06:40:43 2022 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 004: ID 0bda:b00e Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus
[Bug 1924199] Re: [MIR] oem-somerville-cory-tgl-meta
Attach oem-somerville-cory-tgl-meta_20.04~ubuntu1.debdiff by oem-scripts 1.29. ** Summary changed: - [DRAFT][MIR] oem-somerville-cory-tgl-meta + [MIR] oem-somerville-cory-tgl-meta ** Description changed: - [DRAFT][Availability] + [Background] + + Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and + https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details. + + [Impact] + + 1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive. + 2. The background and impact of the situation for this change, and it's impact. + + [Testing] + + 1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware + 2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the hardware + 3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly. + + [Regression Potential] + + Most potential regressions will live in the package set that will be + installed via dependency of this package, which live in OEM archive + (outside of Ubuntu) and control by OEM team. OEM team and other + corresponding team need take responsibility of those dependency + installed. + + [When switching kernel flavour] Check that the new kernel flavour works + on the target platform. + + [Availability] This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet. The source code of the oem-somerville-cory-tgl-meta for focal: git clone -b cory-tgl-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-somerville-projects-meta [Rationale] We want to improve the hardware support for some Dell platforms. [Security] No CVE/known security issue. [Quality assurance] I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Dell platforms. - oem-somerville-cory-tgl-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive. + oem-somerville-cory-tgl-meta will be upgraded to 20.04ubuntu1 or the later version from OEM archive. [Dependencies] It only depends on ubuntu-oem-keyring. [Standards compliance] This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM. [Maintenance] Canonical OEM Enablement Team will take care of the maintenance. [Background information] Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details. Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to verify this MIR against the reference package in the archive. + + https://ubuntu.com/certified/202101-28592 + https://ubuntu.com/certified/202101-28594 + https://ubuntu.com/certified/202101-28595 + https://ubuntu.com/certified/202101-28596 + https://ubuntu.com/certified/202101-28602 + https://ubuntu.com/certified/202101-28604 + https://ubuntu.com/certified/202101-28605 ** Changed in: oem-priority Status: Confirmed => Fix Committed ** Changed in: ubuntu Status: New => Confirmed ** Patch added: "oem-somerville-cory-tgl-meta_20.04~ubuntu1.debdiff" https://bugs.launchpad.net/bugs/1924199/+attachment/5560927/+files/oem-somerville-cory-tgl-meta_20.04~ubuntu1.debdiff ** Tags removed: oem-scripts-0.82 ** Tags added: oem-needs-upload oem-scripts-1.29 ubuntu-certified -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924199 Title: [MIR] oem-somerville-cory-tgl-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959937] Re: gnome-shell crashed with SIGSEGV in meta_context_terminate()
** Bug watch added: Red Hat Bugzilla #2036604 https://bugzilla.redhat.com/show_bug.cgi?id=2036604 ** Also affects: gnome-shell (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=2036604 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/1959937 Title: gnome-shell crashed with SIGSEGV in meta_context_terminate() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1959937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960585] Re: gnome-shell crashed with SIGSEGV in maybe_update_frame_info() from notify_view_crtc_presented() from meta_kms_page_flip_data_flipped() from flush_callbacks() from callback_idle()
** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-42 fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960585 Title: gnome-shell crashed with SIGSEGV in maybe_update_frame_info() from notify_view_crtc_presented() from meta_kms_page_flip_data_flipped() from flush_callbacks() from callback_idle() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1960585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960868] Re: Dell Precision 5520 boots to the wrong VT (black screen)
*** This bug is a duplicate of bug 1811023 *** https://bugs.launchpad.net/bugs/1811023 ** This bug has been marked a duplicate of bug 1811023 Xorg aborts with ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960868 Title: Dell Precision 5520 boots to the wrong VT (black screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1960868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921503] Re: [MIR] oem-somerville-blastoise-meta
Attach oem-somerville-blastoise-meta_20.04~ubuntu1.debdiff by oem- scripts 1.29. ** Summary changed: - [DRAFT][MIR] oem-somerville-blastoise-meta + [MIR] oem-somerville-blastoise-meta ** Description changed: - [DRAFT][Availability] + [Background] + + Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and + https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details. + + [Impact] + + 1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive. + 2. The background and impact of the situation for this change, and it's impact. + + [Testing] + + 1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware + 2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the hardware + 3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly. + + [Regression Potential] + + Most potential regressions will live in the package set that will be + installed via dependency of this package, which live in OEM archive + (outside of Ubuntu) and control by OEM team. OEM team and other + corresponding team need take responsibility of those dependency + installed. + + [When switching kernel flavour] Check that the new kernel flavour works + on the target platform. + + [Availability] This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet. The source code of the oem-somerville-blastoise-meta for focal: git clone -b blastoise-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-somerville-projects-meta [Rationale] We want to improve the hardware support for some Dell platforms. [Security] No CVE/known security issue. [Quality assurance] I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Dell platforms. - oem-somerville-blastoise-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive. + oem-somerville-blastoise-meta will be upgraded to 20.04ubuntu1 or the later version from OEM archive. [Dependencies] It only depends on ubuntu-oem-keyring. [Standards compliance] This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM. [Maintenance] Canonical OEM Enablement Team will take care of the maintenance. [Background information] Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details. Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to verify this MIR against the reference package in the archive. + + https://ubuntu.com/certified/202103-28858 + https://ubuntu.com/certified/202103-28864 + https://ubuntu.com/certified/202103-28865 + https://ubuntu.com/certified/202103-28866 + https://ubuntu.com/certified/202103-28867 + https://ubuntu.com/certified/202103-28868 + https://ubuntu.com/certified/202103-28869 + https://ubuntu.com/certified/202103-28870 + https://ubuntu.com/certified/202104-28918 ** Changed in: oem-priority Status: Confirmed => Fix Committed ** Changed in: ubuntu Status: New => Confirmed ** Patch added: "oem-somerville-blastoise-meta_20.04~ubuntu1.debdiff" https://bugs.launchpad.net/bugs/1921503/+attachment/5560926/+files/oem-somerville-blastoise-meta_20.04~ubuntu1.debdiff ** Tags removed: oem-scripts-0.8 ** Tags added: oem-needs-upload oem-scripts-1.29 ubuntu-certified -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921503 Title: [MIR] oem-somerville-blastoise-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959937] Re: gnome-shell crashed with SIGSEGV in meta_context_terminate()
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5078 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5078 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5078 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (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/1959937 Title: gnome-shell crashed with SIGSEGV in meta_context_terminate() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1959937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1960776] Re: i386 installer crashes
* Sadly the Atom D2500 + the chipset is seen as 32-bit by the 14.04 64-bit installer. * (The 16.04 32/64bit versions both do not have 3D acceleration, only 12.04 and 14.04… and at least 14.04 still gets ESR patches). * 18.04 and newer only boot to a blinking black cursor. * Regarding this “GMA500” graphics chipsets and newer distros: it seems to be “up to the distro to implement for their needs and newer kernels, as Intel does not support this chipset” * The “recipe” or whatever it is called was originally released for the 3.x kernel line. * The EMGD project that is up and running, and needs an OS distro/maintainer to implement is located at the website below * So far community efforts have gotten support for up to 18.04 * https://github.com/EMGD-Community I’m eager to learn how to help, but not sure how I can at the moment other than donating to Ubuntu efforts, etc. Best, Eric From: nore...@launchpad.net on behalf of Dan Bungert <1960...@bugs.launchpad.net> Date: Monday, February 14, 2022 at 4:40 PM To: hilga...@gmail.com Subject: [Bug 1960776] Re: i386 installer crashes @Eric, have you tried the amd64 installer yet? Any better luck with that? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1960776 Title: i386 installer crashes Status in ubiquity package in Ubuntu: Invalid Bug description: This was an issue which occurred during setup and brought me to this bug report page. I need an older Ubuntu install for the GMA500 driver which has not been updated for newer distros sadly. (Should I open another bug for no 3D acceleration with GMA500 on 20.04 or 22.04?) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity 2.18.8.13 ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167 Uname: Linux 4.4.0-142-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 CasperVersion: 1.340.2 Date: Sun Feb 13 22:58:37 2022 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 (20190304.5) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1960776/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960776 Title: i386 installer crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1960776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466150] Re: grub-install breaks when ESP is on raid
** Tags added: hwcert-server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466150 Title: grub-install breaks when ESP is on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1466150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960362] Re: EDAC update for AMD Genoa support in 22.04
** Tags added: servcert-194 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960362 Title: EDAC update for AMD Genoa support in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960361] Re: hwmon: k10temp updates for AMD Genoa in 22.04
** Tags added: servcert-195 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960361 Title: hwmon: k10temp updates for AMD Genoa in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960364] Re: EDAC MCE updates for AMD Genoa in 22.04
91f75eb481cf is not a clean pull into 5.15 5176a93ab27a picks cleanly. ** Tags added: hwcert-server ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: servcert-193 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960364 Title: EDAC MCE updates for AMD Genoa in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946793] Re: aodh uses deprecated gnocchi api to aggregate metrics and doesn't work properly
Sorry, forgot to add aodh logs ** Attachment added: "logs.tar.xz" https://bugs.launchpad.net/aodh/+bug/1946793/+attachment/5560923/+files/logs.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946793 Title: aodh uses deprecated gnocchi api to aggregate metrics and doesn't work properly To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1946793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912616] Re: missing GDPR consent for Agenda application for meteo data (Ubuntu 20.10)
[Expired for gnome-weather (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-weather (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/1912616 Title: missing GDPR consent for Agenda application for meteo data (Ubuntu 20.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-weather/+bug/1912616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959681] Re: mic not working on HP-EliteBook-830-G7
@Dariusz, You said "The situation is different on impish - on this release the mic is available out of the box.". I remember the impish doesn't install firmware-sof-signed package out of box, so the the sof-cml.ri is still provided by linux-firmware of impish, and the sof-cml.ri in is impish is identical to the sof-cml.ri in the focal. If so, I guess this is not an issue on the sof-firmware, maybe it is an issue on the kernel of 5.4.0. So could you confirm the mic could work under impish without the firmware-sof-signed package? And could you upload the complete dmesg under focal with the original sof-firmware in focal? About the bionic, I am afraid we couldn't make the mic work under it. To make the mic work, not only needs the kernel and sof-firmware, also needs to upgrade the alsa-lib, alsa-ucm-conf and pulseaudio. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959681 Title: mic not working on HP-EliteBook-830-G7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1959681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960868] Re: Dell Precision 5520 boots to the wrong VT (black screen)
XorgLogOld.txt is showing that Xorg crashed. If that's a recurring issue then it might explain this bug. It looks most likely to be bug 1811023 which is also the most common Xorg crash globally for Ubuntu right now. It also seems to mostly affect Nvidia users. Please reproduce the issue a few more times and if you keep seeing Xorg crashes like: [ 4.932] (EE) Backtrace: [ 4.932] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55ac57b32aec] [ 4.933] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f2b8ea073c0] [ 4.933] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7f2b8e84418b] [ 4.933] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7f2b8e823859] [ 4.934] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 4.934] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7f2b8e823729] [ 4.934] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x46) [0x7f2b8e834f36] [ 4.934] (EE) 6: /usr/lib/xorg/Xorg (dixRegisterPrivateKey+0x239) [0x55ac579efb39] [ 4.934] (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_init+0xcf) [0x7f2a0961b37f] or log messages like: privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. then this is bug 1811023. ** Package changed: gdm3 (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-graphics-drivers-510 (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/1960868 Title: Dell Precision 5520 boots to the wrong VT (black screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1960868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960582] Re: [critical] dpkg error while processing - can't install nor upgrade
i have fix the dpkg problem following by this solution : https://unix.stackexchange.com/questions/161866/how-to-recreate-var-lib- dpkg-status sudo cp /var/backups/dpkg.status.0 /var/lib/dpkg/status sudo cp /var/backups/dpkg.statoverride.0 /var/lib/dpkg/statoverride sudo cp /var/backups/dpkg.diversions.0 /var/lib/dpkg/diversions sudo cp /var/backups/dpkg.arch.0 /var/lib/dpkg/arch sudo dpkg --clear-avail sudo apt update so there could be some bug that remove or change the dpkg status file while upgrade from older version of ubuntu. if you couldn't reproduce then perhaps we are not using the same environment, i am using a HP Elitebook 840 G7. after recreate dpkg status from backup, now i got this error: sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libc-bin : Depends: libc6 (> 2.35) but 2.34-0ubuntu3 is installed libc6-dbg : Depends: libc6 (= 2.35-0ubuntu1) but 2.34-0ubuntu3 is installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... failed. The following packages have unmet dependencies: libc-bin : Depends: libc6 (> 2.35) but 2.34-0ubuntu3 is installed libc6-dbg : Depends: libc6 (= 2.35-0ubuntu1) but 2.34-0ubuntu3 is installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. E: Unable to correct dependencies so i think the package manager of jammy not yet upgrade the libc to 2.35, if this is not bug too then i think you can feel free to close the ticket. 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/1960582 Title: [critical] dpkg error while processing - can't install nor upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1960582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1950062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960730] Re: calamares focal install to sony vaio - failure to boot
another QA-test install to - sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT) later daily/ISO, no-encryption used & failure again.. when I have time, I may use the box to explore documenting a 'fail to boot after install' page on discourse, but for now I may just switch SECURE-uEFI off (which it was supposed to be for my actual checklist-testcase!) either way; as I said in #lubuntu-devel xubuntu (focal.4) installed... I got a blue background MOK screen I don't normally get on first boot.. (I mostly use uEFI not SECURE-uEFI on this box) I accepted default.. didn't appear subsequent boot(s) though I recorded test in jammy section?? (http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/244330/testcases/1300/results/) so maybe i made a mistake?? NOTE: My Xubuntu thumb-drive contains 20.04 (ISO 2022-02-13) so I think I made the mistake on the iso.qa.ubuntu.com tracker & reported it against jammy where it should have been focal so xubuntu. 20.04.4 (daily) installed in this state on this box I'm pretty sure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960730 Title: calamares focal install to sony vaio - failure to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1960730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960868] Re: Dell Precision 5520 no longer boots properly (black screen)
Sounds like a variation of bug 1878838. ** Summary changed: - Xorg freeze + Dell Precision 5520 no longer boots properly (black screen) ** Summary changed: - Dell Precision 5520 no longer boots properly (black screen) + Dell Precision 5520 boots to the wrong VT (black screen) ** Package changed: xorg (Ubuntu) => gdm3 (Ubuntu) ** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags added: nvidia -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960868 Title: Dell Precision 5520 boots to the wrong VT (black screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1960868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960865] Re: System freeze
Thanks for the bug report. 1. If you experience a crash then please follow these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment 2. If you experience a freeze without any crash reports then it might be related to bug 1959888, even if not exactly the same. 3. You seem to have a lot of packages from "origin: unknown" shown in Dependencies.txt, so that might be a factor. But if we can confirm the cause of this problem is #1 or #2 instead then we won't have to worry about the package versions right now. ** 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/1960865 Title: System freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
I recently was able to work around this issue using the nvidia 510 drivers and following this suggestion: https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150/3 Thus far no issues with resuming. Not sure if it helps with 460 but thought I'd share. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1911055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960605] Re: System freeze
Thanks for that. Next: 1. Reboot and reproduce the system freeze again. 2. Next time you are able to log in please run: journalctl -b-1 > prevboot.txt 3. Attach the resulting text file here. ** Changed in: ubuntu Status: New => Incomplete ** Tags added: nvidia -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960605 Title: System freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960857] Re: gdm3 self-enables during upgrade
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960857 Title: gdm3 self-enables during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960336] Re: No login screen after recent update
> those drivers are always behind and rather unstable in my experience, especially with nouveau currently. I was suggesting the 5.5 beta driver which is the latest (December 2021) - https://www.synaptics.com/products/displaylink- graphics/downloads/ubuntu. It works with the official jammy kernel 5.15. I know that because it's what I'm using in development. Also please don't use the nouveau driver. It causes too many bugs so you should always stick to the Nvidia proprietary driver instead. --- The next steps here are: 1. Enable debug mode in /etc/gdm3/custom.conf: [debug] Enable=true 2. Reboot and reproduce the no-login-screen problem again. 3. Reboot again, this time into recovery/safe mode and run: journalctl -b-1 > debugprevboot.txt 4. Attach the resulting text file here. If you find the help you're getting here inadequate for any reason then you can also report the issue to GDM directly at: https://gitlab.gnome.org/GNOME/gdm/-/issues If you do that then please let us know the new issue ID here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960336 Title: No login screen after recent update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945661] Re: openstack commands fail with GTK3 error
I also get this error when I execute the "openstack XXX" command remotely in an Xshell, and I noticed that the same prompt seems to be related to trying to open the GUI - initialization. So, I run "openstack XXX" in putty, and no more related errors. System version: ubuntu20.04 tls openstack: W Possible solutions: use terminal tools without desktop functions, or cancel the installation of the desktop from the underlying system -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945661 Title: openstack commands fail with GTK3 error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-openstackclient/+bug/1945661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960709] Re: Recent bluez update broke Bluetooth for setups using a BT dongle
** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960709 Title: Recent bluez update broke Bluetooth for setups using a BT dongle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960875] Comment bridged from LTC Bugzilla
--- Comment From boris.m...@de.ibm.com 2022-02-14 20:28 EDT--- The root-patch which has introduced the bug is from kernel 5.11. Therefore, Ubuntu 21.10 and higher need to be fixed. The fix is already available in stable now: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/s390?h=v5.17-rc4=dd9cb842fa9d90653a9b48aba52f89c069f3bc50 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960875 Title: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend
I got the same issue with my Dell Inspiron 5155, everytime it went to sleep I can't boot the laptop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909005 Title: Ubuntu does not resume (wake up) from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959529] Re: Hipersocket page allocation failure on Ubuntu 20.04 based SSC environments
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin2004 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959529 Title: Hipersocket page allocation failure on Ubuntu 20.04 based SSC environments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960875] [NEW] [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call
Public bug reported: Description: s390/cio: verify the driver availability for path_event call Symptom: If no driver is attached to a device or the driver does not provide the path_event function, an FCES path-event on this device could end up in a kernel-panic. Problem: There can be path-event generated for devices which are not bound to any drivers. And this is not verified before callback. Solution: Make sure the driver is available before the callback. Reproduction: - Upstream-ID: dd9cb842fa9d90653a9b48aba52f89c069f3bc50 Problem-ID:196414 Distros: Ubuntu 21.10 and higher Preventive:yes Reported: - SupportTicket: - Reference: - Date: 2022-02-14 Author:Vineeth Vijayan Component: kernel ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-196419 severity-medium targetmilestone-inin2110 ** Tags added: architecture-s39064 bugnameltc-196419 severity-medium targetmilestone-inin2110 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => 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/1960875 Title: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960857] Re: gdm3 self-enables during upgrade
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 Ubuntu Servers don't have GNOME or `gdm3` installed as they are desktop packages. Your issue appears to have occurred because of packages added to your system, thus you'd benefit more from support I suspect. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1960857 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960857 Title: gdm3 self-enables during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960776] Re: i386 installer crashes
@Eric, have you tried the amd64 installer yet? Any better luck with that? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960776 Title: i386 installer crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1960776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960874] [NEW] package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1
Public bug reported: I tried to upgrade and just failed. I use Ubuntu 20.04 and 4.15.0-70-generic4.15.0-70-generic kernel. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.7 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 14 19:32:02 2022 ErrorMessage: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2018-04-27 (1389 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960874 Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1960874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960754] Re: gencache_init: Failed to create directory: /var/www/.cache/samba - Permission denied
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960754 Title: gencache_init: Failed to create directory: /var/www/.cache/samba - Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1960754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960842] Re: failed to load module `zsh/mathfunc': /lib/x86_64-linux-gnu/libm.so.6
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zsh (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/1960842 Title: failed to load module `zsh/mathfunc': /lib/x86_64-linux-gnu/libm.so.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1960842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947210] Re: Firefox Snap can't copy or drag in Wayland
@Sebastien Bacher (@seb128) I tried the procedure in Bug #1913775 and saw some strange behavior but I believe it must not be exactly the same issue. The bug I originally reported seems to be resolved in Firefox 97.0 snap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947210 Title: Firefox Snap can't copy or drag in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1947210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956063] Re: Change of video card from nVidia to AMD breaks Chromium Snap
Hi Olivier, Yes, this issue is no longer present with snap version 98.0.4758.80. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956063 Title: Change of video card from nVidia to AMD breaks Chromium Snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960865] Re: System freeze
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960865 Title: System freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1960865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947210] Re: Firefox Snap can't copy or drag in Wayland
My apologies to everyone who responded since I reported it in October -- apparently I missed seeing the notifications for this bug. I also installed a deb version and have been logging in via xorg to avoid it, and another bug affecting Zoom under Wayland. I just installed the current stable snap version and logged in via Wayland and copy/paste and drag/drop seem to be working fine both ways. Should I mark the bug resolved or is that my responsibility? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947210 Title: Firefox Snap can't copy or drag in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1947210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960364] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1960364 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (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/1960364 Title: EDAC MCE updates for AMD Genoa in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960336] Re: No login screen after recent update
from the newly installed system with 20.04, warnings came for /var/lib/gdm3.config and .local not being empty. root@ubuntu-inspiron-5482:/var/lib/gdm3# ls -lrta total 32 drwxr-xr-x 3 root root 4096 feb 5 12:33 .config drwx-- 3 gdm gdm 4096 feb 5 12:34 .nv drwx-- 4 gdm gdm 4096 feb 5 12:35 .local drwx-- 6 gdm gdm 4096 feb 5 12:35 .cache drwxr-xr-x 101 root root 4096 feb 5 12:37 .. -rw-r--r-- 1 gdm gdm feb 13 23:26 greeter-dconf-defaults drwx--x--x 6 gdm gdm 4096 feb 13 23:26 . is what that looks like on the broken system. On the one with warning, it shows 755 instead of 700 permissions. There is also no .nv dir. I will wipe it out, reinstall and see what happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960336 Title: No login screen after recent update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960364] Re: EDAC MCE updates for AMD Genoa in 22.04
** Changed in: linux (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960364 Title: EDAC MCE updates for AMD Genoa in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960362] Re: EDAC update for AMD Genoa support in 22.04
** Changed in: linux (Ubuntu) Status: Invalid => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Jeff Lane (bladernr) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960362 Title: EDAC update for AMD Genoa support in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960336] Re: No login screen after recent update
hi, this machine has not been much customised. I only switched display manager because the supplied one did not work. I cannot reinstall and lose data. Display link does not work on at least 2 of my systems with kernel 5.13 and they reopened a bug because I reported it - those drivers are always behind and rather unstable in my experience, especially with nouveau currently. I hope devs can come up with a better answer because I bet a lot of folks will run into this issue. I uninstalled caffeine, removed plugins from /usr/share and the problem remains. I would say I am rather handy with Linux, that is why I run dev builds sometimes and report issues. If I want buggy drivers and no support I can just install windows, man even macOS runs better on both machines. Please notify the gdm3 devs and gnome-extensions ones, because stuff changed there. You can also close the bug, but I am not gonna waste my time on finding the issue anymore then. Isn´t the whole point of open source software that users make it better :)? Also, I the time of reporting was right after the update, so it can´t be too hard to find. This issue does not occur on another machine with a recent install of 20.04 and having that updated. That said, this machine certainly does not go further back than 18.04, I think actually 20.04 too. How about we try to find the cause? You have not answered the question about where to find this plugins that are in the bug report, like xcaffeine. thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960336 Title: No login screen after recent update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960709] Re: Recent bluez update broke Bluetooth for setups using a BT dongle
Thanks for the reply, by the way :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960709 Title: Recent bluez update broke Bluetooth for setups using a BT dongle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960709] Re: Recent bluez update broke Bluetooth for setups using a BT dongle
Hello! I think the bug can be closed: > BTW, "ConditionPathIsDirectory" is not new. It's been there for two years already in Ubuntu 20.04. On the same date of the bluez package upgrade, I had to revert to an older kernel version due to the amdgpu driver incompatibility, so that should be the cause. The version was the Ubuntu mainline 5.11.16 (the latest compatible with 20.04 and with the amdgpu official drivers as of today), which I don't know if it's of any interest (if so, I can upload the information). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960709 Title: Recent bluez update broke Bluetooth for setups using a BT dongle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960361] Re: hwmon: k10temp updates for AMD Genoa in 22.04
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960361 Title: hwmon: k10temp updates for AMD Genoa in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960871] [NEW] linux-modules-extra-* fails to install due to dependency on unsigned package
Public bug reported: Several SRU tests are failing the test setup due to failure to install the modules-extra package: * Command: yes "" | DEBIAN_FRONTEND=noninteractive apt-get install --yes --force-yes automake bison build-essential byacc flex git keyutils libacl1-dev libaio- dev libcap-dev libmm-dev libnuma-dev libsctp-dev libselinux1-dev libssl- dev libtirpc-dev pkg-config quota xfslibs-dev xfsprogs gcc linux-modules- extra-4.15.0-1120-aws Exit status: 100 Duration: 0.908210039139 stdout: Reading package lists... Building dependency tree... Reading state information... xfsprogs is already the newest version (4.9.0+nmu1ubuntu2). xfsprogs set to manually installed. git is already the newest version (1:2.17.1-1ubuntu0.9). git set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-modules-extra-4.15.0-1120-aws : Depends: linux-image-unsigned-4.15.0-1120-aws but it is not going to be installed stderr: W: --force-yes is deprecated, use one of the options starting with --allow instead. E: Unable to correct problems, you have held broken packages. ** Affects: linux-aws (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/1960871 Title: linux-modules-extra-* fails to install due to dependency on unsigned package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1960871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960863] Re: armv8 paca: poly1305 users see segfaults when pointer authentication in use on AWS Graviton 3 instances
** Tags added: sts-sponsor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960863 Title: armv8 paca: poly1305 users see segfaults when pointer authentication in use on AWS Graviton 3 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960361] Re: hwmon: k10temp updates for AMD Genoa in 22.04
Refactored this to only address hwmon patches. ** Description changed: Patch pull request to include additional support for AMD Genoa in 22.04 - These two are already in Jammy: - e7d445ab26db 2021-10-19 14:07:17 +0200 x86/sme: Use #define USE_EARLY_PGTABLE_L5 in mem_encrypt_identity.c - 1ff2fc02862d 2021-12-05 16:44:52 +0100 x86/sme: Explicitly map new EFI memmap table as encrypted - - These remain to pick: - f95711242390 2021-12-10 12:51:28 +0100 EDAC: Add RDDR5 and LRDDR5 memory types - - e2be5955a886 2021-12-10 12:54:33 +0100 EDAC/amd64: Add support for AMD - Family 19h Models 10h-1Fh and A0h-AFh - - 5176a93ab27a 2021-12-22 17:19:18 +0100 x86/MCE/AMD, EDAC/mce_amd: Add - new SMCA bank types - - 91f75eb481cf 2021-12-22 17:22:09 +0100 x86/MCE/AMD, EDAC/mce_amd: - Support non-uniform MCA bank type enumeration - - 8bb050cd5cf4 2021-12-26 15:02:05 -0800 hwmon: (k10temp) Support up to 12 - CCDs on AMD Family of processors - - 3cf90efa1367 2021-12-26 15:02:05 -0800 hwmon: (k10temp) Add support for - AMD Family 19h Models 10h-1Fh and A0h-AFh - - f707bcb5d1cb 2021-12-26 15:02:05 -0800 hwmon: (k10temp) Remove unused - definitions + f707bcb5d1cb 5.17 hwmon: (k10temp) Remove unused definitions + 3cf90efa1367 5.17 hwmon: (k10temp) Add support for AMD Family 19h Models 10h-1Fh and A0h-AFh + 8bb050cd5cf4 5.17 hwmon: (k10temp) Support up to 12 CCDs on AMD Family of processors -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960361 Title: hwmon: k10temp updates for AMD Genoa in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960817] Re: Network Manager sets powersave on by default, thus making many WiFi connections unreliable
The actual git commit is https://git.launchpad.net/network- manager/commit/?id=b07d891427e6698838feb42e03ac668893125775 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960817 Title: Network Manager sets powersave on by default, thus making many WiFi connections unreliable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1960817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960863] Re: armv8 paca: poly1305 users see segfaults when pointer authentication in use on AWS Graviton 3 instances
Attached is a debdiff for openssl on Focal ** Patch added: "debdiff for openssl on Focal" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960863/+attachment/5560898/+files/lp1960863_focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960863 Title: armv8 paca: poly1305 users see segfaults when pointer authentication in use on AWS Graviton 3 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960869] [NEW] package xserver-xorg-legacy 2:1.20.13-1ubuntu1~20.04.2 failed to install/upgrade: afhængighedsproblemer - efterlader den ukonfigureret
Public bug reported: keep coming up ProblemType: Package DistroRelease: Ubuntu 20.04 Package: xserver-xorg-legacy 2:1.20.13-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-97.110-generic 5.4.162 Uname: Linux 5.4.0-97-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: bluez-cups:amd64: Install NULL: ConfigurePending Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Thu Feb 10 07:36:27 2022 DistUpgraded: 2020-10-22 18:53:10,042 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Fejl under kørsel af underprocessen “./xorg_fix_proprietary.py” (Ingen sådan fil eller filkatalog) (8)) DistroCodename: focal DistroVariant: ubuntu ErrorMessage: afhængighedsproblemer - efterlader den ukonfigureret ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:39f3] InstallationDate: Installed on 2019-11-18 (815 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 81D7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-97-generic root=UUID=c5543799-53e3-49ce-a975-66ef9ff1e3cf ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: xorg-server Title: package xserver-xorg-legacy 2:1.20.13-1ubuntu1~20.04.2 failed to install/upgrade: afhængighedsproblemer - efterlader den ukonfigureret UpgradeStatus: Upgraded to focal on 2020-10-22 (477 days ago) dmi.bios.date: 05/14/2021 dmi.bios.vendor: LENOVO dmi.bios.version: 8UCN19WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-17AST dmi.modalias: dmi:bvnLENOVO:bvr8UCN19WW:bd05/14/2021:svnLENOVO:pn81D7:pvrLenovoideapad330-17AST:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad330-17AST: dmi.product.family: ideapad 330-17AST dmi.product.name: 81D7 dmi.product.sku: LENOVO_MT_81D7_BU_idea_FM_ideapad 330-17AST dmi.product.version: Lenovo ideapad 330-17AST dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960869 Title: package xserver-xorg-legacy 2:1.20.13-1ubuntu1~20.04.2 failed to install/upgrade: afhængighedsproblemer - efterlader den ukonfigureret To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1960869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960742] Re: System freeze
Hi thanks for your help, please check at the attachment ** Attachment added: "PREVBOOT.TXT" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960742/+attachment/5560876/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960742 Title: System freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960868] [NEW] Xorg freeze
Public bug reported: I have several Dell Laptops model Precision 5520. Ubuntu LTS 20.04.2 seems to run fine without issues. After do a software update which appears to update to LTS 20.04.3, the laptops no longer boot properly. I end up at a black screen with an underscore cursor blinking at the upper left. If I then hold the Alt key down and click the right arrow a few times followed by the left arrow a few times, eventually I see the normal GUI login screen and I can log in. Please let me know if there is anything that can be done to avoid this problem. I have tried on several Dell laptops and I get the same behavior on all of them. There seems to be something broken in Ubuntu 20.04.3 for these lapotops. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-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 510.47.03 Mon Jan 24 22:58:54 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 14:37:36 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:07bf] Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf] InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a0 Elan Microelectronics Corp. Touchscreen Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=58eb98db-d059-4fbb-8a18-0c258fd3ab72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2020 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: 1203062 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:br1.20:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.product.sku: 07BF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang focal freeze ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960868 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1960868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831441] Re: Please add WS-Discovery ( WSD ) support for Windows Samba server discovery.
Since my last post I starting testing Ubuntu 22.04 and noticed there is a package wsdd2. https://packages.ubuntu.com/jammy/net/wsdd2 It's in jammy/universe. I installed it and I can connect to it from Win11 as WSD. So now I'm confused. Which one is which. They are not the same package but do the same thing - at least from the user's viewpoint. It will be confusing to have both, right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831441 Title: Please add WS-Discovery ( WSD ) support for Windows Samba server discovery. To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1831441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1320709] Re: incorrect info in /usr/share/doc/awstats/README.Debian.gz about logrotate
As Miriam indicates, this appears to have been addressed in the README via changing to the line Willie suggests in comment #4. I've also confirmed this change is in focal and jammy, so I think this can be closed as resolved now. ** Changed in: awstats (Ubuntu) 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/1320709 Title: incorrect info in /usr/share/doc/awstats/README.Debian.gz about logrotate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1320709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903776] Re: Changed ubuntu-keyring paths breaks upgrade to focal.
** Merge proposal linked: https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/415568 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903776 Title: Changed ubuntu-keyring paths breaks upgrade to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1903776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1881847] Re: If NFS server reboots, client somethings fails to remount the file system properly
I'm sorry it was some time ago when I submitted this. I have since upgraded to 5.13.19 and 5.16 on some machines and these latter kernels seems to have resolved the issue. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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 Mon, 14 Feb 2022, Andreas Hasenack wrote: > Date: Mon, 14 Feb 2022 20:21:46 - > From: Andreas Hasenack <1881...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1881847] Re: If NFS server reboots, > client somethings fails to remount the file system properly > > With NFSv4, user and group information is sent on the wire as names, > instead of uids. And these names are qualified with a domain. So for > example an exported directory containing files for the "ubuntu" user > will have the ownership sent to NFSv4 clients as "ubuntu@DOMAIN", where > "DOMAIN" is the DNS domain of the server. > > Whave I have seen in some testing is that after a reboot, for some > reason (probably service ordering), the NFS server bits do not know yet > the domain of the machine, and then this becomes "localdomain", and the > user is sent to the client as "ubuntu@localdomain". The client, being on > the same DNS domain, decides that "localdomain" is none of its business, > and declares that user as "nobody". > > You said there was a "hang", but maybe the issue above is realted > somehow? One way to see it is in the client logs, where "nfsidmap" is > called. If you configure /etc/request-key.d/id_resolver.conf to call > nfidmap with extra "-v -v -v" in the command line, it will be more > verbose in /var/log/syslog and say which user it's trying to resolve. > > If you see the "localdomain" issue, then try hardcoding the domain in > /etc/idmapd.conf on both the server and the client, to your actual DNS > domain, and see if that helps. > > > Hope this helps > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1881847 > > Title: > If NFS server reboots, client somethings fails to remount the file > system properly > > Status in nfs-utils package in Ubuntu: > New > > Bug description: > If the NFS server reboots, sometimes client servers fail to re- > establish the NFS mount properly. This is using NFS v4.2. The client > machine will hang if I try to do a df when an NFS mount is in this > condition. Attempting to access a file will likewise hang > indefinitely. This is a problem with the stock 5.3.0.x kernel and it > is a problem with 5.6 still. I have not tried 5.7 yet. I filed this > against nfs-kernel, but I am not 100% sure it is not nfs-common but > there is some sort of communications not happening between them. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: nfs-kernel-server 1:1.3.4-2.5ubuntu3 > Uname: Linux 5.6.0 x86_64 > ApportVersion: 2.20.11-0ubuntu27.2 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: MATE > Date: Tue Jun 2 21:34:31 2020 > InstallationDate: Installed on 2017-05-27 (1102 days ago) > InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) > SourcePackage: nfs-utils > UpgradeStatus: Upgraded to focal on 2020-04-26 (38 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1881847/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881847 Title: If NFS server reboots, client somethings fails to remount the file system properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1881847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903776] Re: Changed ubuntu-keyring paths breaks upgrade to focal.
** Also affects: landscape-client (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: landscape-client (Ubuntu Jammy) Importance: Undecided Assignee: Simon Poirier (simpoir) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903776 Title: Changed ubuntu-keyring paths breaks upgrade to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1903776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903776] Re: Changed ubuntu-keyring paths breaks upgrade to focal.
** Merge proposal linked: https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/415567 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903776 Title: Changed ubuntu-keyring paths breaks upgrade to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1903776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955844] Re: Enlightenment cannot successfully start the enlightenment_system service since it can't become group root. Missing setuid bit?
You could set the https://en.wikipedia.org/wiki/Setuid;>suid: # chmod 4755 /usr/lib/x86_64-linux-gnu/enlightenment/utils/enlightenment_sys # chmod 4755 /usr/lib/x86_64-linux-gnu/enlightenment/utils/enlightenment_system -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955844 Title: Enlightenment cannot successfully start the enlightenment_system service since it can't become group root. Missing setuid bit? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/enlightenment/+bug/1955844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955844] Re: Enlightenment cannot successfully start the enlightenment_system service since it can't become group root. Missing setuid bit?
A package e17 doesn't exist in Jammy. It's enlightenment with e25. ** Package changed: e17 (Ubuntu) => enlightenment (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955844 Title: Enlightenment cannot successfully start the enlightenment_system service since it can't become group root. Missing setuid bit? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/enlightenment/+bug/1955844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958196] Re: EAP-MSCHAPv2 is busted
** Merge proposal linked: https://code.launchpad.net/~eivnaes/ubuntu/+source/ppp/+git/ppp/+merge/415397 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958196 Title: EAP-MSCHAPv2 is busted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1958196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960740] Re: checkit-tiff v1.0.0 published Feb. 2021
** Changed in: checkit-tiff (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960740 Title: checkit-tiff v1.0.0 published Feb. 2021 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/checkit-tiff/+bug/1960740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956670] Re: Extend support for runtime power management for AMD's Yellow Carp
** Changed in: hwe-next Status: Fix Committed => Fix Released ** Changed in: linux-oem-5.14 (Ubuntu Focal) 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/1956670 Title: Extend support for runtime power management for AMD's Yellow Carp To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959971] Re: increase /boot partition size
@sil2100 @brian-murray: Thank you for your work and consideration on this. We addressed this issue Kubuntu Focus OEM ISO (https://kfocus.org/try) by increasing the /boot partition size and providing an app that monitors and removes unused kernels (https://kfocus.org/wf/tools#kclean). We want to share our findings upstream for the benefit of everyone that uses client Ubuntu with FDE. In summary, an additional 1.2G of disk space is a very small price to pay to avoid the expense of guiding non-expert users to recover from an over-full partition. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959971 Title: increase /boot partition size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1959971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960088] Re: a) "collections" has no attribute "callable"; b) PY_SSIZE_T_CLEAN
** Changed in: libapache2-mod-python (Ubuntu) Status: New => Triaged ** Changed in: libapache2-mod-python (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960088 Title: a) "collections" has no attribute "callable"; b) PY_SSIZE_T_CLEAN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-python/+bug/1960088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960831] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1960831/+attachment/5560832/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960831 Title: unmount gadget on filesystem panel in caja disconnects before dismount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1960831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
