[Bug 1932522] Re: [22.04 FEAT] New package request: libzpc: protected key crypto library (for s390x)
@paelzer: Looks like an issue with the BZ bridge (happened before, sometimes it just repeats a part of a previous comment)... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932522 Title: [22.04 FEAT] New package request: libzpc: protected key crypto library (for s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952584] [NEW] bash exec command unwanted behaviour
Public bug reported: (GNU bash 4.3.46) (ubuntu 16.04 LTS) Consider you have out.txt on current dir. --- >exec 123456789012>out.txt bash: exec: 123456789012: not found --- exec command prints indicated error for large numbers that is supposed to use as a fd but redirects /proc/$$/fd/1 to out.txt silently. Additionally, --- >exec 1234567890>out.txt bash: 123456789: Bad file descriptor --- For large numbers but not that large (I don't inspect the limits!), exec command rejects fd number but silently adds a new fd to current bash process. In every execution of the command, bash adds a new fd to itself again and again. ** Affects: bash (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/1952584 Title: bash exec command unwanted behaviour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1952584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928387] Re: [EHL] Integrated TSN controller (stmmac) driver support
** Changed in: linux-intel (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928387 Title: [EHL] Integrated TSN controller (stmmac) driver support To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1928387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939511] Re: [EHL] Integrated TSN controller (stmmac) driver support
*** This bug is a duplicate of bug 1945461 *** https://bugs.launchpad.net/bugs/1945461 ** This bug has been marked a duplicate of bug 1945461 Integrated TSN controller for sprint 2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939511 Title: [EHL] Integrated TSN controller (stmmac) driver support To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950979] Re: [RTL8821CE] Bluetooth devices seem to pair well but the connection isn't working
It might have been fixed by https://launchpad.net/ubuntu/+source/bluez/5.60-0ubuntu2.1 but it's still unclear... so let's just say fixed in 'Ubuntu'. ** Package changed: rtl8821ce (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Fix Released ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950979 Title: [RTL8821CE] Bluetooth devices seem to pair well but the connection isn't working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1950979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950979] Re: [RTL8821CE] Bluetooth devices seem to pair well but the connection isn't working
I confirm that the last update of Bluetooth packages has resolved the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950979 Title: [RTL8821CE] Bluetooth devices seem to pair well but the connection isn't working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952558] Re: Logitech USB wireless mouse
Thanks for the bug report. Please: 1. Replace the battery in the mouse and test it again. 2. If the bug still occurs then while it is happening (logged in and mouse not working) please run: journalctl -b0 > journal.txt 3. Attach the resulting text file here. ** 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/1952558 Title: Logitech USB wireless mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1952558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952581] [NEW] ACPI Error: No handler for Region [VRTC]
Public bug reported: From sniffing around seems to be something Kernal related specific to the recent Razor Blade laptops with GPUs. https://bugzilla.kernel.org/show_bug.cgi?id=205665 I don't think its Xorg but its graphic related? Fully documented here with screen shot https://askubuntu.com/questions/1376401/acpi-error-causing-suspend-loop-bug-in-21-10 Tried to register on bugzilla.kernal.org but since i'm not compiling my own Kernal they say its Ubuntu problem? ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.13.19-051319-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 470.82.00 Thu Oct 14 10:24:40 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 29 20:12:32 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: nvidia, 470.82.00, 5.13.0-20-generic, x86_64: installed nvidia, 470.82.00, 5.13.0-21-generic, x86_64: installed nvidia, 470.82.00, 5.13.19-051319-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. CometLake-H GT2 [UHD Graphics] [1a58:200f] NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [10de:249c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [1a58:200f] InstallationDate: Installed on 2021-10-24 (36 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Razer Blade 15 Advanced Model (Early 2021) - RZ09-036 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.19-051319-generic root=UUID=006b8912-4943-4915-bf29-0927fd50045f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2021 dmi.bios.release: 1.1 dmi.bios.vendor: Razer dmi.bios.version: 1.01 dmi.board.name: CH560 dmi.board.vendor: Razer dmi.board.version: 4 dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnRazer:bvr1.01:bd02/02/2021:br1.1:efr1.0:svnRazer:pnBlade15AdvancedModel(Early2021)-RZ09-036:pvr6.04:rvnRazer:rnCH560:rvr4:cvnRazer:ct10:cvr:skuRZ09-0367CE53: dmi.product.family: 1A58200F Razer Blade dmi.product.name: Blade 15 Advanced Model (Early 2021) - RZ09-036 dmi.product.sku: RZ09-0367CE53 dmi.product.version: 6.04 dmi.sys.vendor: Razer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952581 Title: ACPI Error: No handler for Region [VRTC] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1952581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930868] Re: Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197
Updated the debdiff, added "Breaks: linux-firmware (<= 1.202)" as Juerg suggested in this new debdiff. thx. ** Patch added: "firmware-sof_1.9-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1930868/+attachment/5544009/+files/firmware-sof_1.9-1ubuntu1.debdiff ** Summary changed: - Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 + [SRU][Jammy]Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930868 Title: [SRU][Jammy]Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof- apl.ri', which is also in package linux-firmware 1.197 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1930868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952556] Re: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong."
Sounds like bug 1952457 but we should figure out the root cause of this bug separately. Please: 1. Uninstall these extensions: 'mprisindicatorbut...@jasonlg1979.github.io', 'bat...@martin.zurowietz.de', 'multi-volume@tigersoldier', 'allowlockedremotedesk...@kamens.us' 2. Log in again and verify the bug still occurs. 3. If the bug does still occur then check for crashes using these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952556 Title: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952557] Re: Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly
This may be caused by gnome-shell quietly crashing on logout. Please: 1. Uninstall these extensions: 'mprisindicatorbut...@jasonlg1979.github.io', 'bat...@martin.zurowietz.de', 'multi-volume@tigersoldier', 'allowlockedremotedesk...@kamens.us' 2. Log in again and verify the bug still occurs. 3. If the bug does still occur then check for crashes using these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952557 Title: Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952457] Re: choosing Ubuntu on xorg fails to launch X, launches Wayland
Thanks for the bug report. Please: 1. Reboot. 2. Log in and reproduce the bug. 3. Run: journalctl -b0 > journal.txt 4. Attach the resulting text file here. 5. Also follow these steps to check for crashes: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => gdm3 (Ubuntu) ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Tags added: vmwgfx ** Tags added: vmware -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952457 Title: choosing Ubuntu on xorg fails to launch X, launches Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1952457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952515] Re: QA Test Ubuntu 22.04 Gnome-shell Crashed
** Changed in: gnome-shell (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/1952515 Title: QA Test Ubuntu 22.04 Gnome-shell Crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952544] Re: cryptsetup requires newer i915 firmwares that is not included in LTS 20.04.3
*** This bug is a duplicate of bug 1939986 *** https://bugs.launchpad.net/bugs/1939986 This is just a warning when the initrd is regenerated that some firmwares might be missing. In this case it's graphics firmware which has nothing to do with cryptsetup. ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid ** This bug has been marked a duplicate of bug 1939986 Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952544 Title: cryptsetup requires newer i915 firmwares that is not included in LTS 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1952544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952579] [NEW] Jammy update: v5.15.5 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.5 upstream stable release from git://git.kernel.org/ Linux 5.15.5 ALSA: hda: hdac_stream: fix potential locking issue in snd_hdac_stream_assign() ALSA: hda: hdac_ext_stream: fix potential locking issues x86/Kconfig: Fix an unused variable error in dell-smm-hwmon net: add and use skb_unclone_keeptruesize() helper btrfs: update device path inode time instead of bd_inode fs: export an inode_update_time helper ice: Delete always true check of PF pointer ice: Fix VF true promiscuous mode usb: max-3421: Use driver data instead of maintaining a list of bound devices ASoC: rsnd: fixup DMAEngine API ASoC: DAPM: Cover regression by kctl change notification fix selinux: fix NULL-pointer dereference when hashtab allocation fails bpf: Forbid bpf_ktime_get_coarse_ns and bpf_timer_* in tracing progs RDMA/netlink: Add __maybe_unused to static inline in C file hugetlbfs: flush TLBs correctly after huge_pmd_unshare signal: Replace force_fatal_sig with force_exit_sig when in doubt signal: Don't always set SA_IMMUTABLE for forced signals signal: Replace force_sigsegv(SIGSEGV) with force_fatal_sig(SIGSEGV) signal/x86: In emulate_vsyscall force a signal instead of calling do_exit signal/vm86_32: Properly send SIGSEGV when the vm86 state cannot be saved. signal/sparc32: In setup_rt_frame and setup_fram use force_fatal_sig signal/sparc32: Exit with a fatal signal when try_to_clear_window_buffer fails signal/s390: Use force_sigsegv in default_trap_handler signal/powerpc: On swapcontext failure force SIGSEGV exit/syscall_user_dispatch: Send ordinary signals on failure signal: Implement force_fatal_sig drm/amd/pm: avoid duplicate powergate/ungate setting drm/amdgpu: fix set scaling mode Full/Full aspect/Center not works on vga and dvi connectors drm/i915: Fix type1 DVI DP dual mode adapter heuristic for modern platforms drm/i915/dp: Ensure max link params are always valid drm/i915/dp: Ensure sink rate values are always valid drm/nouveau: clean up all clients on device removal drm/nouveau: use drm_dev_unplug() during device removal drm/nouveau: Add a dedicated mutex for the clients list drm/prime: Fix use after free in mmap with drm_gem_ttm_mmap drm/udl: fix control-message timeout drm/i915/guc: Unwind context requests in reverse order drm/i915/guc: Don't drop ce->guc_active.lock when unwinding context drm/i915/guc: Workaround reset G2H is received after schedule done G2H drm/i915/guc: Don't enable scheduling on a banned context, guc_id invalid, not registered drm/i915/guc: Fix outstanding G2H accounting drm/amd/display: Limit max DSC target bpp for specific monitors drm/amd/display: Update swizzle mode enums mac80211: drop check for DONT_REORDER in __ieee80211_select_queue mac80211: fix radiotap header generation cfg80211: call cfg80211_stop_ap when switch from P2P_GO type parisc/sticon: fix reverse colors net: stmmac: Fix signed/unsigned wreckage fs: handle circular mappings correctly btrfs: fix memory ordering between normal and ordered work functions Drivers: hv: balloon: Use VMBUS_RING_SIZE() wrapper for dm_ring_size net: stmmac: socfpga: add runtime suspend/resume callback for stratix10 platform spi: fix use-after-free of the add_lock mutex udf: Fix crash after seekdir printk: restore flushing of NMI buffers on remote CPUs after NMI backtraces drm/cma-helper: Release non-coherent memory with dma_free_noncoherent() KVM: nVMX: don't use vcpu->arch.efer when checking host state on nested state load KVM: SEV: Disallow COPY_ENC_CONTEXT_FROM if target has created vCPUs fbdev: Prevent probing generic drivers if a FB is already registered block: Check ADMIN before NICE for IOPRIO_CLASS_RT s390/dump: fix copying to user-space of swapped kdump oldmem s390/kexec: fix memory leak of ipl report buffer s390/vdso: filter out -mstack-guard and -mstack-size s390/boot: simplify and fix kernel memory layout setup s390/setup: avoid reserving memory above identity mapping pinctrl: ralink: include 'ralink_regs.h' in 'pinctrl-mt7620.c' scsi: qla2xxx: Fix mailbox direction flags in qla2xxx_get_adapter_id() ata: libata: add missing ata_identify_page_supported() calls ata: libata: improve ata_read_log_page() error message Revert "parisc: Reduce sigreturn trampoline to 3 instructions" Revert "drm/i915/tgl/dsi: Gate the ddi clocks after pll mapping" powerpc/8xx: Fix pinned TLBs with CONFIG_STRICT_KERNEL_RWX powerpc/xive: Change IRQ domain to a tree domain powerpc/signal32: Fix sigset_t copy KVM: x86/xen: Fix get_attr of KVM_XEN_ATTR_TYPE_SHARED_INFO
[Bug 1951877] Re: FTBFS - python-testtools does not support Python 3.10
I've used your git-ubuntu branch to generate the source package and upload it. You (server team) will have to break this merge into the 3 commits again during next merge with upstream (debian) as I did not have permission to upload to pkg/ubuntu/devel (not sure why). $ dput ubuntu python-testtools_2.5.0-2ubuntu1_source.changes D: Setting host argument. Checking signature on .changes gpg: /home/rafaeldtinoco/work/sources/ubuntu/jammy/python-testtools_2.5.0-2ubuntu1_source.changes: Valid signature from A93E0E0AD83C0D0F Checking signature on .dsc gpg: /home/rafaeldtinoco/work/sources/ubuntu/jammy/python-testtools_2.5.0-2ubuntu1.dsc: Valid signature from A93E0E0AD83C0D0F Uploading to ubuntu (via ftp to upload.ubuntu.com): Uploading python-testtools_2.5.0-2ubuntu1.dsc: done. Uploading python-testtools_2.5.0-2ubuntu1.debian.tar.xz: done. Uploading python-testtools_2.5.0-2ubuntu1_source.buildinfo: done. Uploading python-testtools_2.5.0-2ubuntu1_source.changes: done. Successfully uploaded packages. Please follow migration to check if it migrates good, let me know otherwise. PS: I have "quilt refreshed" your patch to avoid hunks (in the other SRU proposal as well). Make sure your patches apply clean wen you suggest a merge/fix. Thanks! ** Changed in: python-testtools (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951877 Title: FTBFS - python-testtools does not support Python 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/1951877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951583] Re: bbswitch dkms build failure with 5.15 on armhf and ppc64el
New debdiff in attach that relies on CONFIG_ACPI to determine if we need to check the power state in bbswitch_off(). ** Patch added: "bbswitch-fix-build-error-when-acpi-is-not-available.debdiff" https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1951583/+attachment/5544007/+files/bbswitch-fix-build-error-when-acpi-is-not-available.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951583 Title: bbswitch dkms build failure with 5.15 on armhf and ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1951583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780746] Re: oping (and noping) require root access to run
Applying patch 0004-allow-non-root-usage.patch patching file src/liboping.c Hunk #2 succeeded at 1669 (offset -1 lines). Refreshed the patch, generated src package, all good, patch fixes the issue. $ dput ubuntu liboping_1.10.0-1ubuntu0.1_source.changes Checking signature on .changes gpg: /home/rafaeldtinoco/work/sources/ubuntu/liboping_1.10.0-1ubuntu0.1_source.changes: Valid signature from A93E0E0AD83C0D0F Checking signature on .dsc gpg: /home/rafaeldtinoco/work/sources/ubuntu/liboping_1.10.0-1ubuntu0.1.dsc: Valid signature from A93E0E0AD83C0D0F Uploading to ubuntu (via ftp to upload.ubuntu.com): Uploading liboping_1.10.0-1ubuntu0.1.dsc: done. Uploading liboping_1.10.0-1ubuntu0.1.debian.tar.xz: done. Uploading liboping_1.10.0-1ubuntu0.1_source.buildinfo: done. Uploading liboping_1.10.0-1ubuntu0.1_source.changes: done. Successfully uploaded packages. ** Changed in: liboping (Ubuntu Bionic) Status: Triaged => 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/1780746 Title: oping (and noping) require root access to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liboping/+bug/1780746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949605] Re: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS
** Changed in: thunderbird (Ubuntu Focal) Assignee: rithu (sobhadurai) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949605 Title: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1949605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952554] Re: MediaTek doesnt get installed on Ubuntu 20.4
Hi, this header file input-polldev.h has been removed upstream: https://github.com/torvalds/linux/commit/278b13ce3a89698711c5a67792ba2dba41555433 And this commit has landed on hirsute 5.11, that's why you're not getting this file on Focal 5.11. There is nothing we can do here, you will need to contact the maintainer to update the code. Or use Focal 5.4 instead. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952554 Title: MediaTek doesnt get installed on Ubuntu 20.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932522] Re: [22.04 FEAT] New package request: libzpc: protected key crypto library (for s390x)
Comment #6 looks like an incomplete quote of comment #4, please double check what you wanted to answer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932522 Title: [22.04 FEAT] New package request: libzpc: protected key crypto library (for s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949605] Re: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS
** Changed in: thunderbird (Ubuntu Focal) Assignee: Olivier Tilloy (osomon) => rithu (sobhadurai) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949605 Title: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1949605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934944] Re: power-profiles-daemon package conflicts with TLP
Cause this issue is fixed in tlp, I will open a new bug to handle tlp and power-profiles-daemon. ** Changed in: oem-priority Assignee: (unassigned) => Bin Li (binli) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934944 Title: power-profiles-daemon package conflicts with TLP To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934944] Re: power-profiles-daemon package conflicts with TLP
After upgraded the power-profiles-daemon, the service will be enable again. ** Changed in: oem-priority Status: Triaged => Fix Released ** Changed in: oem-priority Assignee: Bin Li (binli) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934944 Title: power-profiles-daemon package conflicts with TLP To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841039] Re: Multiple keys have same keycode on HP ProBook 450 G6
Did u remove the battery first? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841039 Title: Multiple keys have same keycode on HP ProBook 450 G6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1841039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952568] Re: AMD GPU kernel driver unload error
kenrl 5.14.0-1005 # lsmod|grep amdgpu - amdgpu 7049216 4 iommu_v2 24576 1 amdgpu gpu_sched 36864 1 amdgpu drm_ttm_helper 16384 1 amdgpu ttm73728 2 amdgpu,drm_ttm_helper drm_kms_helper258048 1 amdgpu drm 557056 8 gpu_sched,drm_kms_helper,amdgpu,drm_ttm_helper,ttm i2c_algo_bit 16384 2 igb,amdgpu - root@yoshi-kvm01:~# systemctl stop display-manager.service root@yoshi-kvm01:~# killall lxqt-panel lxqt-panel: no process found root@yoshi-kvm01:~# echo 0 > /sys/class/vtconsole/vtcon1/bind root@yoshi-kvm01:~# modprobe -s -r amdgpu syslog - Nov 29 14:20:32 yoshi-kvm01 systemd[1]: Stopping Light Display Manager... Nov 29 14:20:32 yoshi-kvm01 systemd[1]: Stopping Session c1 of user lightdm. Nov 29 14:20:32 yoshi-kvm01 systemd[1]: session-c1.scope: Succeeded. Nov 29 14:20:32 yoshi-kvm01 systemd[1]: Stopped Session c1 of user lightdm. Nov 29 14:20:32 yoshi-kvm01 bluetoothd[2267]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSink/sbc Nov 29 14:20:32 yoshi-kvm01 bluetoothd[2267]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSource/sbc Nov 29 14:20:32 yoshi-kvm01 systemd[4070]: pulseaudio.service: Succeeded. Nov 29 14:20:33 yoshi-kvm01 systemd[1]: lightdm.service: Succeeded. Nov 29 14:20:33 yoshi-kvm01 systemd[1]: Stopped Light Display Manager. Nov 29 14:20:42 yoshi-kvm01 systemd[1]: Stopping User Manager for UID 123... Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Stopped target Main User Target. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Stopping Accessibility services bus... Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Stopping D-Bus User Message Bus... Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Stopping Virtual filesystem service... Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: run-user-123-gvfs.mount: Succeeded. Nov 29 14:20:42 yoshi-kvm01 systemd[4341]: run-user-123-gvfs.mount: Succeeded. Nov 29 14:20:42 yoshi-kvm01 systemd[1]: run-user-123-gvfs.mount: Succeeded. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: gvfs-daemon.service: Succeeded. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Stopped Virtual filesystem service. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: dbus.service: Succeeded. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Stopped D-Bus User Message Bus. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: at-spi-dbus-bus.service: Succeeded. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Stopped Accessibility services bus. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Stopped target Basic System. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Stopped target Paths. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Stopped target Sockets. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Stopped target Timers. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: dbus.socket: Succeeded. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Closed D-Bus User Message Bus Socket. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: dirmngr.socket: Succeeded. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Closed GnuPG network certificate management daemon. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: gpg-agent-browser.socket: Succeeded. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers). Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: gpg-agent-extra.socket: Succeeded. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Closed GnuPG cryptographic agent and passphrase cache (restricted). Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: gpg-agent-ssh.socket: Succeeded. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Closed GnuPG cryptographic agent (ssh-agent emulation). Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: gpg-agent.socket: Succeeded. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Closed GnuPG cryptographic agent and passphrase cache. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: pk-debconf-helper.socket: Succeeded. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Closed debconf communication socket. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: pulseaudio.socket: Succeeded. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Closed Sound System. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: snapd.session-agent.socket: Succeeded. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Closed REST API socket for snapd user session agent. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Reached target Shutdown. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: systemd-exit.service: Succeeded. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Finished Exit the Session. Nov 29 14:20:42 yoshi-kvm01 systemd[4070]: Reached target Exit the Session. Nov 29 14:20:42 yoshi-kvm01 systemd[1]: user@123.service: Succeeded. Nov 29 14:20:42 yoshi-kvm01 systemd[1]: Stopped User Manager for UID 123. Nov 29 14:20:42 yoshi-kvm01 systemd[1]: Stopping User Runtime Directory /run/user/123... Nov 29 14:20:42 yoshi-kvm01 systemd[1]: run-user-123.mount: Succeeded. Nov 29 14:20:42 yoshi-kvm01 systemd[4341]: run-user-123.mount: Succeeded. Nov 29 14:20:42 yoshi-kvm01
[Bug 1952568] Re: AMD GPU kernel driver unload error
kernel 5.14.0-1007 # lsmod|grep amdgpu - amdgpu 7049216 4 iommu_v2 24576 1 amdgpu gpu_sched 36864 1 amdgpu drm_ttm_helper 16384 1 amdgpu ttm73728 2 amdgpu,drm_ttm_helper drm_kms_helper258048 1 amdgpu drm 557056 8 gpu_sched,drm_kms_helper,amdgpu,drm_ttm_helper,ttm i2c_algo_bit 16384 2 igb,amdgpu - root@yoshi-kvm01:~# systemctl stop display-manager.service root@yoshi-kvm01:~# killall lxqt-panel lxqt-panel: no process found root@yoshi-kvm01:~# echo 0 > /sys/class/vtconsole/vtcon1/bind root@yoshi-kvm01:~# modprobe -s -r amdgpu syslog - Nov 29 14:28:11 yoshi-kvm01 systemd[1]: Stopping Light Display Manager... Nov 29 14:28:11 yoshi-kvm01 systemd[1]: Stopping Session c1 of user lightdm. Nov 29 14:28:11 yoshi-kvm01 systemd[1]: session-c1.scope: Succeeded. Nov 29 14:28:11 yoshi-kvm01 systemd[1]: Stopped Session c1 of user lightdm. Nov 29 14:28:11 yoshi-kvm01 bluetoothd[2241]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSink/sbc Nov 29 14:28:11 yoshi-kvm01 bluetoothd[2241]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSource/sbc Nov 29 14:28:11 yoshi-kvm01 systemd[4021]: pulseaudio.service: Succeeded. Nov 29 14:28:12 yoshi-kvm01 systemd[1]: lightdm.service: Succeeded. Nov 29 14:28:12 yoshi-kvm01 systemd[1]: Stopped Light Display Manager. Nov 29 14:28:21 yoshi-kvm01 systemd[1]: Stopping User Manager for UID 123... Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Stopped target Main User Target. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Stopping Accessibility services bus... Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Stopping D-Bus User Message Bus... Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Stopping Virtual filesystem service... Nov 29 14:28:21 yoshi-kvm01 systemd[4346]: run-user-123-gvfs.mount: Succeeded. Nov 29 14:28:21 yoshi-kvm01 systemd[1]: run-user-123-gvfs.mount: Succeeded. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: run-user-123-gvfs.mount: Succeeded. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: gvfs-daemon.service: Succeeded. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Stopped Virtual filesystem service. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: dbus.service: Succeeded. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Stopped D-Bus User Message Bus. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: at-spi-dbus-bus.service: Succeeded. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Stopped Accessibility services bus. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Stopped target Basic System. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Stopped target Paths. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Stopped target Sockets. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Stopped target Timers. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: dbus.socket: Succeeded. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Closed D-Bus User Message Bus Socket. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: dirmngr.socket: Succeeded. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Closed GnuPG network certificate management daemon. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: gpg-agent-browser.socket: Succeeded. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers). Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: gpg-agent-extra.socket: Succeeded. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Closed GnuPG cryptographic agent and passphrase cache (restricted). Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: gpg-agent-ssh.socket: Succeeded. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Closed GnuPG cryptographic agent (ssh-agent emulation). Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: gpg-agent.socket: Succeeded. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Closed GnuPG cryptographic agent and passphrase cache. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: pk-debconf-helper.socket: Succeeded. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Closed debconf communication socket. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: pulseaudio.socket: Succeeded. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Closed Sound System. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: snapd.session-agent.socket: Succeeded. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Closed REST API socket for snapd user session agent. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Reached target Shutdown. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: systemd-exit.service: Succeeded. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Finished Exit the Session. Nov 29 14:28:21 yoshi-kvm01 systemd[4021]: Reached target Exit the Session. Nov 29 14:28:21 yoshi-kvm01 systemd[1]: user@123.service: Succeeded. Nov 29 14:28:21 yoshi-kvm01 systemd[1]: Stopped User Manager for UID 123. Nov 29 14:28:21 yoshi-kvm01 systemd[1]: Stopping User Runtime Directory /run/user/123... Nov 29 14:28:21 yoshi-kvm01 systemd[4346]: run-user-123.mount: Succeeded. Nov 29 14:28:21 yoshi-kvm01 systemd[1]: run-user-123.mount: Succeeded. Nov 29 14:28:21 yoshi-kvm01
[Bug 1952570] Re: Normal Install on Daily Build
*** This bug is a duplicate of bug 1951399 *** https://bugs.launchpad.net/bugs/1951399 ** This bug has been marked a duplicate of bug 1951399 Ubuntu, Budgie, Kubuntu, Kylin, MATE, Xubuntu: jammy daily fails to install -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952570 Title: Normal Install on Daily Build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1952570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952570] [NEW] Normal Install on Daily Build
Public bug reported: Just Followed the installation nothing else. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 21.10.10 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: Budgie Date: Mon Nov 29 10:38:09 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-budgie.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2029) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-21.10.10 ubuntu-budgie -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952570 Title: Normal Install on Daily Build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1952570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952568] Re: AMD GPU kernel driver unload error
# systemctl stop display-manager.service # killall lxqt-panel # echo 0 > /sys/class/vtconsole/vtcon1/bind # modprobe -s -r amdgpu Killed syslog - tail -f /var/log/syslog Nov 29 14:06:16 yoshi-kvm01 systemd[4521]: Listening on D-Bus User Message Bus Socket. Nov 29 14:06:16 yoshi-kvm01 systemd[4521]: Reached target Sockets. Nov 29 14:06:16 yoshi-kvm01 systemd[4521]: Reached target Basic System. Nov 29 14:06:16 yoshi-kvm01 systemd[1]: Started User Manager for UID 0. Nov 29 14:06:16 yoshi-kvm01 systemd[1]: Started Session 3 of user root. Nov 29 14:06:16 yoshi-kvm01 systemd[4521]: Condition check resulted in Sound Service being skipped. Nov 29 14:06:16 yoshi-kvm01 systemd[4521]: Reached target Main User Target. Nov 29 14:06:16 yoshi-kvm01 systemd[4521]: Startup finished in 152ms. Nov 29 14:06:35 yoshi-kvm01 systemd[1]: Started Session 5 of user root. Nov 29 14:06:52 yoshi-kvm01 systemd[1]: Started Session 6 of user root. Nov 29 14:07:20 yoshi-kvm01 systemd[1]: Stopping Light Display Manager... Nov 29 14:07:20 yoshi-kvm01 systemd[1]: Stopping Session c1 of user lightdm. Nov 29 14:07:20 yoshi-kvm01 systemd[1]: session-c1.scope: Succeeded. Nov 29 14:07:20 yoshi-kvm01 systemd[1]: Stopped Session c1 of user lightdm. Nov 29 14:07:20 yoshi-kvm01 bluetoothd[2240]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSink/sbc Nov 29 14:07:20 yoshi-kvm01 bluetoothd[2240]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSource/sbc Nov 29 14:07:20 yoshi-kvm01 systemd[4242]: pulseaudio.service: Succeeded. Nov 29 14:07:20 yoshi-kvm01 systemd[1]: lightdm.service: Succeeded. Nov 29 14:07:20 yoshi-kvm01 systemd[1]: Stopped Light Display Manager. Nov 29 14:07:30 yoshi-kvm01 systemd[1]: Stopping User Manager for UID 123... Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Stopped target Main User Target. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Stopping Accessibility services bus... Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Stopping D-Bus User Message Bus... Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Stopping Virtual filesystem service... Nov 29 14:07:30 yoshi-kvm01 systemd[1]: run-user-123-gvfs.mount: Succeeded. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: run-user-123-gvfs.mount: Succeeded. Nov 29 14:07:30 yoshi-kvm01 systemd[4521]: run-user-123-gvfs.mount: Succeeded. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: gvfs-daemon.service: Succeeded. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Stopped Virtual filesystem service. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: dbus.service: Succeeded. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Stopped D-Bus User Message Bus. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: at-spi-dbus-bus.service: Succeeded. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Stopped Accessibility services bus. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Stopped target Basic System. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Stopped target Paths. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Stopped target Sockets. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Stopped target Timers. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: dbus.socket: Succeeded. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Closed D-Bus User Message Bus Socket. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: dirmngr.socket: Succeeded. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Closed GnuPG network certificate management daemon. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: gpg-agent-browser.socket: Succeeded. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers). Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: gpg-agent-extra.socket: Succeeded. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Closed GnuPG cryptographic agent and passphrase cache (restricted). Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: gpg-agent-ssh.socket: Succeeded. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Closed GnuPG cryptographic agent (ssh-agent emulation). Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: gpg-agent.socket: Succeeded. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Closed GnuPG cryptographic agent and passphrase cache. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: pk-debconf-helper.socket: Succeeded. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Closed debconf communication socket. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: pulseaudio.socket: Succeeded. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Closed Sound System. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: snapd.session-agent.socket: Succeeded. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Closed REST API socket for snapd user session agent. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Reached target Shutdown. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: systemd-exit.service: Succeeded. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Finished Exit the Session. Nov 29 14:07:30 yoshi-kvm01 systemd[4242]: Reached target Exit the Session. Nov 29 14:07:30 yoshi-kvm01 systemd[1]: user@123.service: Succeeded. Nov 29 14:07:30 yoshi-kvm01 systemd[1]: Stopped User Manager for UID
[Bug 1952568] [NEW] AMD GPU kernel driver unload error
Public bug reported: After updating the kernel from 5.14.0-1005 to 5.14.0-1007 on ubuntu20.04, if you unload the driver with the following command, the command will be forcibly terminated and the driver cannot be unloaded. Can be unloaded with 5.14.0-1005 without any problem sudo modprob -s -r amdgpu Driver information in lsmod - sudo lsmod |grep amdgpu amdgpu 7049216 -1 iommu_v2 24576 1 amdgpu gpu_sched 36864 1 amdgpu drm_ttm_helper 16384 1 amdgpu ttm73728 2 amdgpu,drm_ttm_helper drm_kms_helper258048 1 amdgpu drm 557056 6 gpu_sched,drm_kms_helper,amdgpu,drm_ttm_helper,ttm i2c_algo_bit 16384 2 igb,amdgpu - ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.14.0-1007-oem 5.14.0-1007.7 ProcVersionSignature: Ubuntu 5.14.0-1007.7-oem 5.14.14 Uname: Linux 5.14.0-1007-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Mon Nov 29 13:46:48 2021 InstallationDate: Installed on 2019-07-24 (858 days ago) InstallationMedia: Ubuntu-Server 19.04 "Disco Dingo" - Release amd64 (20190416.1) SourcePackage: linux-oem-5.14 UpgradeStatus: Upgraded to focal on 2020-05-02 (575 days ago) ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952568 Title: AMD GPU kernel driver unload error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1952568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952496] Re: ubuntu 20.04 LTS network problem
As a side note, it may be time to switch to a new protocol. As even Apple has dropped support for sharing AFP versions in the last few releases and is deprecating it's usage. You can use Samba to do SMBFS including the extra special apple stuff if you need timemachine support etc on your NAS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952496 Title: ubuntu 20.04 LTS network problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1952496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952496] Re: ubuntu 20.04 LTS network problem
To assist with this can you get the following outputs from the broken system: # Change 'hostname.local' to the hostname expected to work cat /etc/nsswitch.conf systemctl status avahi-daemon journalctl -u avahi-daemon --boot avahi-resolve-host-name hostname.local getent hosts hostname.local ** Changed in: avahi (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/1952496 Title: ubuntu 20.04 LTS network problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1952496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926439] Re: Dependencies conflicts breaks upgrade process
** Changed in: linux-restricted-modules (Ubuntu) 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/1926439 Title: Dependencies conflicts breaks upgrade process To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1926439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791908] Re: uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 2: -32 (exp. 1).
The issue is happening even after I would have a fresh install of the operating system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791908 Title: uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 2: -32 (exp. 1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791908] Re: uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 2: -32 (exp. 1).
I'm running Ubuntu Budgie 21.10 & I'm having the same issue with my computer always having same error in the log that is causing me to have to restart my computer every time, I was seeing that there was mention about the webcam, does that seem to be the issue most of the time with this bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791908 Title: uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 2: -32 (exp. 1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928565] Re: postfwd is broken in hirsute
[Expired for postfwd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: postfwd (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/1928565 Title: postfwd is broken in hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfwd/+bug/1928565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945053] Re: updating ubuntu 16.04 to 18.04 failed
[Expired for ubuntu-advantage-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-advantage-tools (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/1945053 Title: updating ubuntu 16.04 to 18.04 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1945053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944542] Re: [Lenovo IdeaPad 5 15IIL05] very slow
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: 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/1944542 Title: [Lenovo IdeaPad 5 15IIL05] very slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1944542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945413] Re: Dell system dual boots to blank tty1
[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdm3 (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/1945413 Title: Dell system dual boots to blank tty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952564] [NEW] notify-send -t option not using correct time
Public bug reported: If I use -t 5000 i expect to get 5 seconds to read the notification, however to get about 5 seconds I need to use ~15000 See attached screen capture (under 40 seconds long) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: notify-osd 0.9.35+20.04.20191129-0ubuntu1 Uname: Linux 5.15.5-051505-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Nov 28 22:18:21 2021 DesktopSession: 'gnome' GtkTheme: 'Breeze' IconTheme: 'breeze' InstallationDate: Installed on 2021-11-26 (2 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211126) MachineType: Micro-Star International Co., Ltd. MS-7B79 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.5-051505-generic root=UUID=b74ecfd8-5603-4e9d-a469-e8a6e754916f ro quiet splash amdgpu.ppfeaturemask=0x vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+23ubuntu1 libgl1-mesa-glx N/A libdrm2 2.4.107-8ubuntu1 xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 xserver-xorg-video-ati 1:19.1.0-2build1 SourcePackage: notify-osd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.G2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X470 GAMING PLUS (MS-7B79) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.G2:bd10/29/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B79:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPLUS(MS-7B79):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B79 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: notify-osd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "screencap.zip" https://bugs.launchpad.net/bugs/1952564/+attachment/5543965/+files/screencap.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952564 Title: notify-send -t option not using correct time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1952564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951032] Re: AArch64: Backport memcpy improvements
** Description changed: [impact] glibc 2.32 contained a number of improvements to the memcpy routines for server-grade AArch64 implementations (in particular, graviton2 & graviton3). They should be backported to focal, as the LTS releases are by far the most used on servers. [test case] Compile the test_memcpy.c that is attached to bug 1928508: $ gcc -g -O3 test_memcpy.c -o test_memcpy64 This should be run before and after installing the libc packages from - proposed. On graviton2 systems, this should show a substantial increase. - On other arm64 systems (raspberry pis of various vintage, thunderx2, - xgene, etc etc) at least no significant regression should be seen. + proposed. On graviton2 systems, this should show a substantial + improvement. On other arm64 systems (raspberry pis of various vintage, + thunderx2, xgene, etc etc) at least no significant regression should be + seen. [regression potential] Rebuilding glibc is always a little risky (toolchain bugs and incompatibilities between the old and new versions can be surprising). But the autopkgtests and some manual general testing can help here. For this specific change, there is a potential risk that the new memcpy implementation could be used on a system where it is not in fact the fastest. We should run the test case not only on the systems where it is expected to help, but other systems such as the RPi4 and the launchpad build farm to ensure performance is not regressed there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951032 Title: AArch64: Backport memcpy improvements To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1951032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952539] Re: Power Mode keeps switching back to balanced after performance is selected manually
Sounds like you need the fix for bug 1943162, which is only in 22.04 (http://cdimage.ubuntu.com/daily-live/current/) ** Package changed: gnome-control-center (Ubuntu) => power-profiles- daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952539 Title: Power Mode keeps switching back to balanced after performance is selected manually To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/1952539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951098] Re: When screen is locked the top bar with apps shows
It sounds like this might be specific to AppIndicator. Can you provide a photo of the issue? ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- appindicator (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951098 Title: When screen is locked the top bar with apps shows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1951098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928508] Re: Performance regression on memcpy() calls for AMD Zen
** Description changed:
[Impact]
On AMD Zen systems, memcpy() calls see a heavy performance regression in
Focal and Groovy, due to the way __x86_non_temporal_threshold is calculated.
Before 'glibc-2.33~455', cache values were calculated taking into
consideration the number of hardware threads in the CPU. On AMD Ryzen
and EPYC systems, this can be counter-productive if the number of
threads is high enough for the last-level caches to "overrun" each other
and cause cache line flushes. The solution is to reduce the allocated
size for these non_temporal stores, removing the number of threads from
the equation.
[Test Plan]
+ Compile the test_memcpy.c that is attached to this bug report:
+
+ $ gcc -mtune=generic -march=x86-64 -g -O3 test_memcpy.c -o test_memcpy64
+
+ This should be run before and after installing the libc packages from
+ proposed. On Ryzen and EPYC systems a substantial improvement should be
+ seen and on other systems, no significant change should be seen.
+
+ [Where problems could occur]
+ Since we're messing with the cacheinfo for x86 in general, we need to be
careful not to introduce further performance regressions on memory-heavy
workloads. Even though initial results might reveal improvement on AMD Ryzen
and EPYC hardware, we should also validate different configurations (e.g.
Intel, different buffer sizes, etc) to make sure we won't hurt performance in
other non-AMD environments.
+
+ [Other Info]
+ This issue has been fixed by the following upstream commit:
+ - d3c57027470b (Reversing calculation of __x86_shared_non_temporal_threshold)
+
+ $ git describe --contains d3c57027470b
+ glibc-2.33~455
+ $ rmadison glibc -s focal,focal-updates,groovy,groovy-proposed,hirsute
+ glibc | 2.31-0ubuntu9 | focal | source
+ glibc | 2.31-0ubuntu9.2 | focal-updates | source
+ glibc | 2.32-0ubuntu3 | groovy | source
+ glibc | 2.32-0ubuntu3.2 | groovy-proposed | source
+ glibc | 2.33-0ubuntu5 | hirsute | source
+
+ Affected releases include Ubuntu Focal and Groovy. Bionic is not
+ affected, and releases starting with Hirsute already ship the upstream
+ patch to fix this regression.
+
+ glibc exports this specific variable as a tunable, so we could also tweak it
with the GLIBC_TUNABLES env var:
+ $ hyperfine -n clean-env 'lxc exec focal env ./test_memcpy64 32' -n tunables
'lxc exec focal env
GLIBC_TUNABLES=glibc.cpu.x86_non_temporal_threshold=1024*1024*3*4
./test_memcpy64 32'
+ Benchmark #1: clean-env
+ Time (mean ± σ): 2.529 s ± 0.061 s[User: 6.0 ms, System: 4.7 ms]
+ Range (min … max):2.457 s … 2.615 s10 runs
+
+ Benchmark #2: tunables
+ Time (mean ± σ): 1.427 s ± 0.030 s[User: 6.5 ms, System: 3.8 ms]
+ Range (min … max):1.402 s … 1.482 s10 runs
+
+ Summary
+ 'tunables' ran
+ 1.77 ± 0.06 times faster than 'clean-env'
+
+ This solution is not ideal, but it offers a secondary way of fixing the
+ performance issues. However, the speed gains for memcpy() are noticeable
+ enough that we should strongly consider changing the defaults in the
+ Focal LTS release, so that it performs similarly to Bionic and future
+ Ubuntu releases starting with Hirsute.
+
+ [old test case section]
Attached to this bug is a short C program that exercises memcpy() calls in
buffers of variable length. This has been obtained from a similar bug report
for Red Hat, and is publicly available at [0].
This test program was compiled with gcc 10.2.0, using the following flags:
$ gcc -mtune=generic -march=x86_64 -g -03 test_memcpy.c -o test_memcpy64
Tests were performed with the following criteria:
- use 32Mb buffers ("./test_memcpy64 32")
- benchmark with the hyperfine tool [1], as it calculates relevant statistics
automatically
- benchmark with at least 10 runs in the same environment, to minimize
variance
- measure on AMD Zen (3700X) and on Intel Xeon (E5-2683), to ensure we don't
penalize one x86 vendor in favor of the other
Below is a comparison between two Focal containers, leveraging LXD to
make use of different libc versions on the same host:
$ hyperfine -n libc-2.31-0ubuntu9.2 'lxc exec focal ./test_memcpy64 32' -n
libc-patched 'lxc exec focal-patched ./test_memcpy64 32'
Benchmark #1: libc-2.31-0ubuntu9.2
Time (mean ± σ): 2.723 s ± 0.013 s[User: 4.7 ms, System: 5.1 ms]
Range (min … max):2.693 s … 2.735 s10 runs
Benchmark #2: libc-patched
Time (mean ± σ): 1.522 s ± 0.004 s[User: 3.9 ms, System: 5.6 ms]
Range (min … max):1.515 s … 1.528 s10 runs
Summary
'libc-patched' ran
1.79 ± 0.01 times faster than 'libc-2.31-0ubuntu9.2'
$ head -n5 /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 23
model : 113
model name : AMD Ryzen 7 3700X 8-Core Processor
[0] https://bugzilla.redhat.com/show_bug.cgi?id=1880670
[1]
[Bug 1950979] 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/1950979 Title: [RTL8821CE] Bluetooth devices seem to pair well but the connection isn't working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951032] Re: AArch64: Backport memcpy improvements
** Description changed: [impact] glibc 2.32 contained a number of improvements to the memcpy routines for server-grade AArch64 implementations (in particular, graviton2 & graviton3). They should be backported to focal, as the LTS releases are by far the most used on servers. [test case] - The testcase from https://bugs.launchpad.net/ubuntu/focal/+source/glibc/+bug/1928508 can be used for this too. + Compile the test_memcpy.c that is attached to bug 1928508: + + $ gcc -g -O3 test_memcpy.c -o test_memcpy64 + + This should be run before and after installing the libc packages from + proposed. On graviton2 systems, this should show a substantial increase. + On other arm64 systems (raspberry pis of various vintage, thunderx2, + xgene, etc etc) at least no significant regression should be seen. [regression potential] Rebuilding glibc is always a little risky (toolchain bugs and incompatibilities between the old and new versions can be surprising). But the autopkgtests and some manual general testing can help here. For this specific change, there is a potential risk that the new memcpy implementation could be used on a system where it is not in fact the fastest. We should run the test case not only on the systems where it is expected to help, but other systems such as the RPi4 and the launchpad build farm to ensure performance is not regressed there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951032 Title: AArch64: Backport memcpy improvements To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1951032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950979] Re: [RTL8821CE] Bluetooth devices seem to pair well but the connection isn't working
I'm not so sure. The RTL8821CE chip implements Bluetooth according to the manufacturer (https://www.realtek.com/en/products/communications-network- ics/item/rtl8821ce) and the above attachment Lspci.txt says: Kernel driver in use: rtl8821ce But then Lsusb.txt says it's running over the USB bus: Bus 001 Device 005: ID 0bda:c024 Realtek Semiconductor Corp. Bluetooth Radio So I assume it's a USB device implemented on the PCIe card, whose driver is rtl8821ce. But we can add a kernel task in case I've missed anything... ** Also affects: linux (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/1950979 Title: [RTL8821CE] Bluetooth devices seem to pair well but the connection isn't working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952041] Re: Fix i915 TypeC disconnect problems for Intel ADL-P
** Tags added: originate-from-1949168 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952041 Title: Fix i915 TypeC disconnect problems for Intel ADL-P To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952421] Re: Issue on sshd finds correct private key for a certificate when using ssh-agent
** Description changed:
- Reported as https://bugzilla.mindrot.org/show_bug.cgi?id=3254 upstream:
+ Reported as https://bugzilla.mindrot.org/show_bug.cgi?id=3254 upstream
- Please take a look at line 1936 in main() function in sshd.c.
+ [Impact]
+
+ * HostCertificate and HostKeyAgent are not working together in sshd due
+to a mismatched certificate's public key and private key. The function `
`sshkey_equal_public()`` incorrectly compares the certificate's public
+ key with a private key, never finding a match. The impact is that sshd
+ cannot use said certificate *even though* its private key is indeed in
+ ssh-agent.
+
+ * What it should do is compare the certificate's public key with a
+ public key in `sensitive_data`.
+
+ * Having this SRU-ed is a direct ask from one of the major cloud partners.
+ They are currently using a customised version of the package to work
+ around this issue, and we would like them to use a package directly from
+ our own archive.
+
+ * Looping through sensitive_data.host_pubkeys[j] *instead* of
+sensitive_data.host_keys[j] fixes the issue
+
+ [https://github.com/openssh/openssh-portable/blob/V_8_4/sshd.c#L1936]
/* Find matching private key */
- for (j = 0; j < options.num_host_key_files; j++) {
- if (sshkey_equal_public(key,
- sensitive_data.host_keys[j])) {
- sensitive_data.host_certificates[j] = key;
- break;
- }
- }
+ for (j = 0; j < options.num_host_key_files; j++) {
+ if (sshkey_equal_public(key,
+ sensitive_data.host_keys[j])) {
+ sensitive_data.host_certificates[j] = key;
+ break;
+ }
+ }
- the sshkey_equal_public() is trying to compare a cert's pub with a private
key, and it never find a match which makes sshd cannot use this certificate
even though its private key is in ssh-agent.
- I believe it should be comparing a cert's public key with a public key in
sensitive_data as follow.
+ vs.
/* Find matching private key */
- for (j = 0; j < options.num_host_key_files; j++) {
- if (sshkey_equal_public(key,
- sensitive_data.host_pubkeys[j])) {
- sensitive_data.host_certificates[j] = key;
- break;
- }
- }
+ for (j = 0; j < options.num_host_key_files; j++) {
+ if (sshkey_equal_public(key,
+ sensitive_data.host_pubkeys[j])) {
+ sensitive_data.host_certificates[j] = key;
+ break;
+ }
+ }
+
- https://github.com/openssh/openssh-portable/blob/V_8_4/sshd.c#L1936
+ [Test Plan]
- Due to this HostCertificate and HostKeyAgent not working together in
- sshd and this affects every version of openssh back till Focal, at
- least.
+ * Due to the empirical nature of this bug, the test is quite straight
+forward. *Without* the fix, one cannot use certificates to authenticate
+successfully (e.g. ``sshd -c /path/to/certificate.pem``)
+whereas with the fix (assuming the certificate matches a host key) you
+can create a channel.
+
+ [Where problems could occur]
+
+ * This has already been fixed both upstream and in Jammy without issue.
+However, if a regression where to happen it would probably be in one of
+two ways:
+
+ * A dependency/reverse-dependency issue stemming from the version
+bump that will happen if this fix is ported. We mitigate this risk
+by testing for these exact types of regression,
+and by selecting carefully what to label this new version.
+
+ * Accidentally breaking a set up that was made to work around this
+bug in the first place. The risk of this is lower, as the most
+likely fix is the one being implemented here anyway. Though
+to mitigate this more we can describe exactly what is happening
+with the fix in the changelog.
+
+
+ This affects every version of openssh back until Focal, at least.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952421
Title:
Issue on sshd finds correct private key for a certificate when using
ssh-agent
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1952421/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)
I have this bug too. wlp1s0IEEE 802.11 Mode:Managed Frequency:2.412 GHz Access Point: 54:89:98:2C:B6:05 Bit Rate=1 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=49/70 Signal level=-61 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:19 Missed beacon:0 ┌(monsterovich@dell)─(pts/0)─(~) └─(>) wget https://speed.hetzner.de/10GB.bin --2021-11-29 02:04:47-- https://speed.hetzner.de/10GB.bin Распознаётся speed.hetzner.de (speed.hetzner.de)... 88.198.248.254, 2a01:4f8:0:59ed::2 Подключение к speed.hetzner.de (speed.hetzner.de)|88.198.248.254|:443... соединение установлено. HTTP-запрос отправлен. Ожидание ответа... 200 OK Длина: 1048576 (9,8G) [application/octet-stream] Сохранение в каталог: ««10GB.bin»». 10GB.bin 0%[] 53,12M 588KB/sост 7h 21m The speed is incredibly low compared to external Wi-Fi adapter. wlx000db0045477 IEEE 802.11 Mode:Managed Frequency:2.412 GHz Access Point: 54:89:98:2C:B6:05 Bit Rate=65 Mb/s Tx-Power=20 dBm Retry short long limit:2 RTS thr:off Fragment thr:off Power Management:off Link Quality=70/70 Signal level=-31 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:462 Invalid misc:23 Missed beacon:0 ┌(monsterovich@dell)─(pts/0)─(~) └─(>) wget https://speed.hetzner.de/10GB.bin --2021-11-29 02:10:01-- https://speed.hetzner.de/10GB.bin Распознаётся speed.hetzner.de (speed.hetzner.de)... 88.198.248.254, 2a01:4f8:0:59ed::2 Подключение к speed.hetzner.de (speed.hetzner.de)|88.198.248.254|:443... соединение установлено. HTTP-запрос отправлен. Ожидание ответа... 200 OK Длина: 1048576 (9,8G) [application/octet-stream] Сохранение в каталог: ««10GB.bin.2»». 10GB.bin.20%[] 23,77M 2,69MB/sост 65m 19s -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670041 Title: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952544] Re: cryptsetup requires newer i915 firmwares that is not included in LTS 20.04.3
** Package changed: cryptsetup (Ubuntu) => linux-firmware (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952544 Title: cryptsetup requires newer i915 firmwares that is not included in LTS 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1952544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946872] Re: Merge logwatch from Debian unstable for 22.04
** Changed in: logwatch (Ubuntu) Milestone: ubuntu-21.11 => ubuntu-21.12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946872 Title: Merge logwatch from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1946872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946874] Re: Merge monitoring-plugins from Debian unstable for 22.04
** Changed in: monitoring-plugins (Ubuntu) Milestone: ubuntu-21.11 => ubuntu-22.01 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946874 Title: Merge monitoring-plugins from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1946874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946895] Re: Merge rdma-core from Debian unstable for 22.04
** Changed in: rdma-core (Ubuntu) Milestone: ubuntu-22.01 => ubuntu-21.11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946895 Title: Merge rdma-core from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rdma-core/+bug/1946895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946838] Re: Merge postfix from Debian unstable for 22.04
** Changed in: postfix (Ubuntu) Milestone: ubuntu-21.12 => ubuntu-21.11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946838 Title: Merge postfix from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1946838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
** Changed in: zsh (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/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952542] Re: systemd randomly crashes
** Changed in: systemd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952542 Title: systemd randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947115] Re: VAAPI / HW-acceleration not working Snap-packaged Firefox
gnome-3-38-2004 version 0+git.cd626d1 (revision 87 for amd64) is now in the stable channel, so the VA-API drivers are exposed for the firefox snap and other consumer snaps. ** Changed in: firefox (Ubuntu) Status: In Progress => Fix Released ** Tags added: snap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947115 Title: VAAPI / HW-acceleration not working Snap-packaged Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952489] Re: [Satellite S55-A, IDT 92HD99BXX, Speaker, ATAPI] fails after a while
Close this issue please, turns out I can't replicate this on another Toshiba S55-A5276 (borrowed another one from the office), might have just been an issue with that specific machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952489 Title: [Satellite S55-A, IDT 92HD99BXX, Speaker, ATAPI] fails after a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946855] Re: Merge dovecot from Debian unstable for 22.04
** Changed in: dovecot (Ubuntu) Milestone: ubuntu-22.01 => ubuntu-21.11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946855 Title: Merge dovecot from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1946855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946842] Re: Merge apr from Debian unstable for 22.04
** Changed in: apr (Ubuntu) Milestone: ubuntu-21.11 => ubuntu-21.12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946842 Title: Merge apr from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apr/+bug/1946842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950979] Re: [RTL8821CE] Bluetooth devices seem to pair well but the connection isn't working
This should be filed against package linux as the kernel provides bluetooth support, not the rtl8821ce package -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950979 Title: [RTL8821CE] Bluetooth devices seem to pair well but the connection isn't working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1950979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
In my pi4 case, I reverted to a previous kernel and didn't see the problem anymore. I was seeing it during snapshot send, though, I didn't to a full `find /storage` and touch every single file to confirm the problem was gone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 344257]
Created attachment 176539 Render in LibreOffice 7.2.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/344257 Title: [upstream] Impress truncates display of slide notes To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/344257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 344257]
Problem persists yet in LibreOffice 7.2.2 -In MS Office, notes show below sheet and you can scroll without problem -In LibreOffice, after showing in "View->Notes", you can see only part of notes, with a (IMO) bad UX experience (Attach image comparaison) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/344257 Title: [upstream] Impress truncates display of slide notes To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/344257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1353024]
Still present in Wine 6.22 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1353024 Title: Wine is creating .lnk files in addition to desktop shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/1353024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 344257]
Created attachment 176540 Render in MSOffice 2019 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/344257 Title: [upstream] Impress truncates display of slide notes To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/344257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952559] Re: (22.04) Volume is not Remembered Across Reboots
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1952559/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952559 Title: (22.04) Volume is not Remembered Across Reboots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1952559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950925] Re: alt-tab doesnt work anymore after upgrade to 21.10
Maybe related - but I had this thunderbird issue, too, but not anymore since upgrading to 21.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950925 Title: alt-tab doesnt work anymore after upgrade to 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1950925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806681]
5.15.5-arch1-1 HP ProBook x360 435 G8 [2.471928] hp_wmi: query 0x4 returned error 0x5 [2.474816] hp_wmi: query 0xd returned error 0x5 [2.545255] hp_wmi: query 0x1b returned error 0x5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806681 Title: hp_wmi: query 0xd returned error 0x5 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1072650] Re: gcc doesn't isssue a strict aliasing warning on a code that seems to break it
Launchpad has imported 2 comments from the remote bug at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60581.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2014-03-19T09:07:48+00:00 Rafał Mużyło wrote:
The problem is described here: https://bugs.gentoo.org/show_bug.cgi?id=505026
The code to trigger comes from a launchpad bug:
https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1072650
As you may notice, it's acros distros and affects many compiler versions
(confirmed for 4.6.3 on ubuntu, 4.7.3 and 4.8.2 on Gentoo).
Following code (AFAICT) violates strict aliasing rules:
#include
struct psuedo_hdr
{
int saddr;
int daddr;
char zero;
char protocol;
short len;
} __attribute__((packed));
int main()
{
unsigned int i;
unsigned int sum = 0;
struct psuedo_hdr hdr;
hdr.saddr = 0xaabbccdd;
hdr.daddr = 0x11223344;
hdr.zero = 0;
hdr.protocol = 6;
hdr.len = 2;
for (i = 0; i < sizeof(hdr); i += 2)
sum += *(short *)((char *)() + i);
printf("0x%x\n", sum);
return 0;
}
however, '-O2 -Wall' doesn't result in the strict aliasing warning.
Reply at: https://bugs.launchpad.net/ubuntu/+source/gcc-
defaults/+bug/1072650/comments/3
On 2014-03-19T10:00:27+00:00 Rguenth wrote:
The strict-aliasing warnings are broken - they are too easily to silence
(the (char *) cast for example). Generally warning for TBAA violations
is very hard if you want to avoid gazillions of false positives or
gazillions of false negatives. The present warning code delivers
neither :/
Reply at: https://bugs.launchpad.net/ubuntu/+source/gcc-
defaults/+bug/1072650/comments/5
** Changed in: gcc-defaults
Status: Unknown => Confirmed
** Changed in: gcc-defaults
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1072650
Title:
gcc doesn't isssue a strict aliasing warning on a code that seems to
break it
To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc-defaults/+bug/1072650/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950925] Re: alt-tab doesnt work anymore after upgrade to 21.10
I come from https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1932328 For me, they look related. Before using Thunderbird (or before it mis-behaves), Alt-TAB works. When Thunderbird goes wrong, Alt-TAB stops working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950925 Title: alt-tab doesnt work anymore after upgrade to 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1950925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
In reply to #56. I can confirm Alt-TAB stops working when Thunderbird mis-behaves. Normally it would show 1 more red (i.e. Window) dot than necessary. But today it is showing 5 extra dots. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1932328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
** Bug watch added: Debian Bug tracker #18 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=18 ** Also affects: zsh (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=18 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/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952555] Re: Flameshot can't take screenshots, 22.04, wayland
Also tested this bug on ubuntu 22.04 development branch by default apt policy says xdg-desktop-portal-gnome is not installed neither here i can reproduce what Jonathan described -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952555 Title: Flameshot can't take screenshots, 22.04, wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1952555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
** Changed in: php-defaults (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/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952555] Re: Flameshot can't take screenshots, 22.04, wayland
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: flameshot (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/1952555 Title: Flameshot can't take screenshots, 22.04, wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1952555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952559] [NEW] (22.04) Volume is not Remembered Across Reboots
Public bug reported: For example, I keep my speakers muted. But, when I restart, my speakers are at max volume. ** 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/1952559 Title: (22.04) Volume is not Remembered Across Reboots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1952559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952549] Re: SSID and password not properly quoted/escaped when writing YAML
I just tested the patch by modifying an Ubuntu 18 USB install stick and performing a clean install on another USB disk. The SSID and password are now indeed stored with single quotes, and as expected, an otherwise non-functioning SSID did in fact work after booting the newly installed system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952549 Title: SSID and password not properly quoted/escaped when writing YAML To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/1952549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951265] Re: package emacs-gtk 1:26.3+1-1ubuntu2 failed to install/upgrade: o subprocesso instalado, do pacote emacs-gtk, o script post-installation retornou erro do status de saída 1
*** This bug is a duplicate of bug 1809125 *** https://bugs.launchpad.net/bugs/1809125 ** This bug has been marked a duplicate of bug 1809125 package emacs-gtk 1:25.2+1-11 failed to install/upgrade: installed emacs-gtk package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951265 Title: package emacs-gtk 1:26.3+1-1ubuntu2 failed to install/upgrade: o subprocesso instalado, do pacote emacs-gtk, o script post-installation retornou erro do status de saída 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1951265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952538] Re: Report a problem in Ubuntu page: Step 1: "nameofprogram" unclear
I pushed this commit: https://git.launchpad.net/~ubuntu-core-doc/ubuntu/+source/ubuntu- docs/commit/?id=7be57788 ** Changed in: ubuntu-docs (Ubuntu) Status: Triaged => Fix Committed ** Changed in: ubuntu-docs (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952538 Title: Report a problem in Ubuntu page: Step 1: "nameofprogram" unclear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1952538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952555] Re: Flameshot can't take screenshots, 22.04, wayland
You have to have xdg-desktop-portal-gnome installed on your system. This requirement is listed as recommendation and should be pullin in automatically, but I don't know why your system did not have it installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952555 Title: Flameshot can't take screenshots, 22.04, wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1952555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952558] [NEW] Logitech USB wireless mouse
Public bug reported: USB logitech mouse doesn't work. If i use 'lsusb' command i see the device but nothing is working. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-40.44-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: fail CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 28 17:40:09 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:181d] InstallationDate: Installed on 2021-06-20 (161 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 006: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305FA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=c94512db-cc03-4296-8107-dcac2868441e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305FA.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305FA.210:bd05/19/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:skuASUS-NotebookSKU:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX305FA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu 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/1952558 Title: Logitech USB wireless mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1952558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952549] Re: SSID and password not properly quoted/escaped when writing YAML
The attachment "0001-When-writing-wireless-config-quote-SSID-and- password.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** 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/1952549 Title: SSID and password not properly quoted/escaped when writing YAML To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/1952549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952557] [NEW] Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly
Public bug reported: In Jammy when I have Chrome running and I log out of a Wayland session and then log back in and restart Chrome it says it wasn't shut down correctly. I'm pretty sure in earlier releases Chrome was given the opportunity to shut down cleanly when I logged out, but :shrug: I could be remembering this incorrectly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 28 11:17:25 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (834 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 40.5-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2021-11-09 (19 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952557 Title: Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952555] Re: Flameshot can't take screenshots, 22.04, wayland
Screenshots work in Xorg session. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952555 Title: Flameshot can't take screenshots, 22.04, wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1952555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952556] [NEW] Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong."
Public bug reported: On Jammy, I log out of a Wayland session, click my name on the login screen, go down to the options menu and select Ubuntu on Xorg, enter my password, get "Oh no! Something has gone wrong. A probleme has occurred and the system can't recover. Please log out and try again. [Log Out]" I click the log out button and log in again, and I'm logged into a Wayland session. Why was I logged into a Wayland session when I selected Xorg the last time I tried to log in? This issue is intermittent I had been able to log into an Xorg session just a few minutes prior. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 28 11:10:10 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (834 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 40.5-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2021-11-09 (19 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726 ** Affects: gnome-shell (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/1952556 Title: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952556] Re: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong."
I logged out immediately after logging in again as described above, then went to log in again and checked the options menu, and it correctly had "Ubuntu on Xorg" selected as my session type, but when I finished logging in I was in a Wayland session, not an Xorg session. So for some reason my selection of Xorg as my desired session is being ignored? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952556 Title: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952555] [NEW] Flameshot can't take screenshots, 22.04, wayland
Public bug reported: With all current packages from Jammy, Flameshot does nothing when I click on the top bar icon and select "Take screenshot". If, after doing that, I click on the icon again and select "Quit", *then* as Flameshot is exiting it pops up a notification that says "Unable to capture screen". There's some discussion that seems relevant at https://github.com/flameshot-org/flameshot/issues/1910, but that discussion claims screenshots work in Flameshot 10.2, and that appears to be the version currently in Jammy, so I'm not sure why it's not working. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: flameshot 0.10.2+ds1-1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 28 11:02:58 2021 InstallationDate: Installed on 2019-08-16 (834 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: flameshot UpgradeStatus: Upgraded to jammy on 2021-11-09 (19 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726 ** Affects: flameshot (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/1952555 Title: Flameshot can't take screenshots, 22.04, wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1952555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952549] Re: SSID and password not properly quoted/escaped when writing YAML
This is a plain patch of changes performed on a git clone of https://git.launchpad.net/ubuntu/+source/netcfg The fix is simple: use Single-Quoted style when outputting SSID or password, which means start and end with a single quote, and replace any instance of ' with ''. The code compiles, and should work, but is not tested. I have yet to figure out how to run netcfg without generating a modified bootable image and performing an install. ** Patch added: "0001-When-writing-wireless-config-quote-SSID-and-password.patch" https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/1952549/+attachment/5543931/+files/0001-When-writing-wireless-config-quote-SSID-and-password.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952549 Title: SSID and password not properly quoted/escaped when writing YAML To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/1952549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905220] Re: Release 0.33
** Changed in: mpv (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905220 Title: Release 0.33 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1905220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952542] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1952542/+attachment/5543930/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952542 Title: systemd randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952542] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1952542/+attachment/5543929/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952542 Title: systemd randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952542] SystemdFailedUnits.txt
apport information ** Attachment added: "SystemdFailedUnits.txt" https://bugs.launchpad.net/bugs/1952542/+attachment/5543928/+files/SystemdFailedUnits.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952542 Title: systemd randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952542] SystemdDelta.txt
apport information ** Attachment added: "SystemdDelta.txt" https://bugs.launchpad.net/bugs/1952542/+attachment/5543927/+files/SystemdDelta.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952542 Title: systemd randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952542] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1952542/+attachment/5543926/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952542 Title: systemd randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952542] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1952542/+attachment/5543925/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952542 Title: systemd randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952542] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1952542/+attachment/5543924/+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/1952542 Title: systemd randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952542] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1952542/+attachment/5543922/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952542 Title: systemd randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
