[Bug 2062951] Re: Random flickering with Intel i915 on Linux 6.8 (Ubuntu 24.04)
I recently upgraded from 22.04 to 24.04 (through v23.10 via do-release- upgrade) and now have symptoms similar to those described (flickering of windows, especially when moving them and I also get screen lockup when trying to dock a window to top/sides of desktop). Running two displays on my dell laptop, one via HDMI and the internal as well. ## Report details - **Date generated:** 2024-06-01 07:00:47 ## Hardware Information: - **Hardware Model:** Precision 5510 - **Memory:** 31Gi - **Processor:** Intel(R) Xeon(R) CPU E3-1505M v5 @ 2.80GHz - **Graphics:** Intel Corporation HD Graphics P530 (rev 06) - **Disk Capacity:** 2.4T ## Software Information: - **Firmware Version:** 1.23.0 - **OS Name:** Ubuntu 24.04 LTS - **OS Build:** 24.04 - **OS Type:** x86_64 - **GNOME Version:** 46.0 - **Windowing System:** x11 - **Kernel Version:** 6.8.0-31-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062951 Title: Random flickering with Intel i915 on Linux 6.8 (Ubuntu 24.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066972] [NEW] ubuntu-bug ubuntu-release-upgrader-core
Public bug reported: Unable to calculate upgrade use ppa-purge - removed ppa file from other software then tried to upgrade again ans till get unable to calculate upgrade and to report the bug in the summary - have submitted bug report ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.14 ProcVersionSignature: Ubuntu 6.5.0-35.35-generic 6.5.13 Uname: Linux 6.5.0-35-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri May 24 02:55:28 2024 InstallationDate: Installed on 2024-05-10 (14 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2024-05-23 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade mantic third-party-packages 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/2066972 Title: ubuntu-bug ubuntu-release-upgrader-core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2066972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064167] [NEW] v22.04 Fails to Boot due to Virtualbox DKMS Out of Bounds
Public bug reported: After Fresh install of UbuntuStudio v22.04 from thumb drive, receive this Error filling up the screen. Managed to write down the Error, screen fills up with ... "UBSAN: array index out of bounds in /var/lib/dkms/virtualbox 6.1.50/build/vboxdrv/SUPDrvGip" and Fails to Boot. ** Affects: virtualbox (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/2064167 Title: v22.04 Fails to Boot due to Virtualbox DKMS Out of Bounds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/2064167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059341] [NEW] Xorg freeze
Public bug reported: I have a server running ubuntu 22.04.4 LTS and the system boots fine and all the hardware is detected, but the HDMI output is freezing on the line: "r8169 000:03:00.0 emp3s0: renamed from eth0". I have managed to get past this previously by adding "nomodeset" to the GRUB boot options but I need the graphics driver for hardware transcoding as that's its main use so need to try and think of another way around this issue. I can ssh into the server fine, it seems to be working fine otherwise. I've seen that it might be when the igpu takes over. Here is my hardware: CPU: i5-13500T, RAM: 64GB DDR4, MOBO: ASRock B760M-ITX, HDDs: 1TB m.2 gen3, 12TB HDD, 8TB HDD, PSU: Corsair SF750.! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-101.111-generic 5.15.143 Uname: Linux 5.15.0-101-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Mar 27 22:51:48 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation AlderLake-S GT1 [8086:4680] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation AlderLake-S GT1 [1849:4680] InstallationDate: Installed on 2024-03-22 (5 days ago) InstallationMedia: Ubuntu-Server 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0033 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 2M/x2 /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 14: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 14: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: ASRock B760M-ITX/D4 WiFi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-101-generic root=UUID=1fdded36-c076-4a14-a7b9-ef9a6fe5a11f ro i915.alpha_support=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.05 dmi.board.name: B760M-ITX/D4 WiFi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.05:bd06/09/2023:br5.27:svnASRock:pnB760M-ITX/D4WiFi:pvrToBeFilledByO.E.M.:rvnASRock:rnB760M-ITX/D4WiFi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: B760M-ITX/D4 WiFi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: ASRock version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze jammy ubuntu uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059341 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2059341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052495] Re: [MIR] wsl-pro-service
I reviewed `wsl-pro-service` `0.1.1` as checked into Noble. This shouldn't be
considered a full audit but rather a quick gauge of maintainability. For the
sake of completeness, this review will also mention findings reported in
previous GitHub issues and Launchpad comments.
Ubuntu Pro for WSL (abbreviated UP4W) is a set of applications to manage Ubuntu
WSL instances, grant them Pro status, orchestrate instances from Landscape and
manage their lifecycle. It is mostly used in corporate environments.
A user can perform with the UP4W codebase the following steps:
1. Install the "Ubuntu Pro for WSL" from the Microsoft Store
2. Using the minimalist UI or the Windows Registry to attach an Ubuntu Pro token
3. Registering the WSL instances in Ubuntu Pro and Landscape
4. Verifying the status of the Ubuntu Pro token by using the `pro` client
inside the WSL instance, the Landscape client, or the Windows UP4W GUI.
Useful resources to understand the bigger picture are [the landing
page](https://ubuntu.com/desktop/wsl),
[repository](https://github.com/canonical/ubuntu-pro-for-wsl), [public
documentation](https://canonical-ubuntu-pro-for-wsl.readthedocs-hosted.com/en/la
test/#), and Canonical-specific specifications (WS0{25,27,28,31}).
The Windows agent can be installed on Windows via [the Microsoft
Store](https://apps.microsoft.com/detail/9pdxgncfsczv?rtc=1=fr-ch=CH). It
achieves the Windows-specific tasks of the UP4W infrastructure (such as getting
the subscription status from the Microsoft Store and setting the registries'
values), but will not be covered in this review. [Its
implementation](https://github.com/canonical/ubuntu-pro-for-wsl/tree/main/window
s-agent) can also be found on GitHub.
`wsl-pro-service` is a component of the UP4W Windows and Ubuntu infrastructure
owned by the Desktop team. It is meant to be a bridge between the `ubuntu-wsl`
API (interfacing the Windows host with the Ubuntu WSL instance). It is
implemented with a `systemd` service and a minimalistic CLI tool for Bash
completion and version retrieval.
The upstream codebase is in [the `wsl-pro-service` folder of the aforementioned
repository](https://github.com/canonical/ubuntu-pro-for-wsl/tree/main/wsl-pro-se
rvice).
- CVE History
- As this is new software (still in testing), there is no CVE assigned to it.
- Build-Depends
- The build process uses only the Debian toolchain, `debhelper` extensions for
Go and `apport` crash reporting, and the Go toolchain.
- Other dependencies
- The relevant Debian dependencies used when operating the service are:
- `ubuntu-advantage-tools`, which is required for its Ubuntu Pro CLI client;
and
- An optional `landscape-client`.
- The package vendors Go dependencies, which violate the Debian policy.
- These are updated by the upstream using a GHA called
`update-workspace-dependencies`, which is integrated into the
`auto-updates.yaml` workflow.
- In addition, the repository has GitHub's Dependabot set.
- pre/post inst/rm scripts
- The scripts are standard, as generated by `dh_installsystemd`.
- init scripts
- N/A
- systemd units
- There is a `systemd` unit called `wsl-pro-service` that runs
`/usr/libexec/wsl-pro-service -vv` as `root`.
- The service also leverages multiple `systemd` configuration directives to
confine itself as much as possible.
- dbus services
- N/A
- setuid binaries
- N/A
- binaries in PATH
- N/A
- sudo fragments
- N/A
- polkit files
- N/A
- udev rules
- N/A
- unit tests / autopkgtests
- Each Go module is tested accordingly.
- The testing coverage is reported by
[Codecov](https://app.codecov.io/gh/canonical/ubuntu-pro-for-wsl) to be 87%.
- These tests are also integrated into `autopkgtests`.
- cron jobs
- N/A
- Build logs
- N/A
- Processes spawned
- Because of the lack of other IPC methods with other involved binaries, the
service delegates operations to other binaries:
- `pro` for attaching and detaching Ubuntu Pro tokens;
- `wslinfo` for getting information about the WSl instance;
- `landscape-config` for manipulating the Landscape configuration; and
- `wslpath` for Windows-Linux path translations.
- The binaries are specified by name, so they will be searched in `$PATH`. As
the service runs as `root`, there is no risk of path hijacking.
- The commands are built by explicitly specifying the executables (hard-coded)
and their arguments. No instance of command injection was found during this
review.
- Memory management
- N/A
- File IO
- The service operates with the following files:
- `/etc/os-release` for obtaining the OS release;
- `/etc/resolve.conf` for obtaining the configured DNS server;
- `/proc/net/route` for getting the default gateway;
- `/etc/landscape/client.conf` as the Landscape configuration file;
- `/etc/landscape/client.conf.new` as the temporary Landscape configuration
file;
- `$USER_PROFILE/.address` for the address (`:`) of the gRPC
server created by [the Windows
[Bug 2052495] Re: [MIR] wsl-pro-service
Other patches were published in the meantime: - For the second item above, in the `347e747` commit; - Checking for a negative port number, in the `a6784f5` commit; and - Avoiding logging configuration items, in the `518a85` commit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052495 Title: [MIR] wsl-pro-service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wsl-pro-service/+bug/2052495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058029] [NEW] Display crashes on latest kernels
Public bug reported: My display crashes and nothing is displayed when I login to latest kernels. Not sure which kernel version started this issue. I can confirm that kernel version 5.15.0-76 works. System details given below. This is linux mint xfce desktop. - Type: Laptop System: Dell product: Inspiron 3180 v: 1.2.0 - Graphics: Device-1: AMD Stoney [Radeon R2/R3/R4/R5 Graphics] vendor: Dell driver: amdgpu v: kernel bus-ID: 00:01.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-1.1:3 Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa gpu: amdgpu resolution: 1366x768~60Hz OpenGL: renderer: STONEY (stoney LLVM 15.0.7 DRM 3.42 5.15.0-76-generic) v: 4.5 Mesa 23.2.1-1ubuntu3.1~22.04.2 direct render: Yes -- mathew@mathew-Inspiron-3180:~$ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 48 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 2 On-line CPU(s) list: 0,1 Vendor ID: AuthenticAMD Model name:AMD A6-9220e RADEON R4, 5 COMPUTE CORES 2C+3G CPU family: 21 Model: 112 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 1 Stepping:0 Frequency boost: enabled CPU max MHz: 1600. CPU min MHz: 1200. BogoMIPS:3193.98 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcn t aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_ msr tbm perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_ save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov Virtualization features: Virtualization:AMD-V Caches (sum of all): L1d: 64 KiB (2 instances) L1i: 128 KiB (2 instances) L2:2 MiB (2 instances) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0,1 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Mitigation; untrained return thunk; SMT disabled Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Retpolines, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected Srbds: Not affected Tsx async abort: Not affected -- ** 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/2058029 Title: Display crashes on latest kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052495] Re: [MIR] wsl-pro-service
The fourth item's crash has already been patched in a GitHub PR (https://github.com/canonical/ubuntu-pro-for-wsl/pull/622). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052495 Title: [MIR] wsl-pro-service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wsl-pro-service/+bug/2052495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052495] Re: [MIR] wsl-pro-service
Hi, As multiple security concerns appeared when performing the security review of this package, I had a discussion with Jean and Didier from the owning team. We concluded that reporting these issues before offering the final MIR report would be best. This is because no user is affected (as the package is still in beta), and transparency will catalyse the fixes. The concerns found are as follows: 1. Insecure gRPC communication: Because [`insecure.NewCredentials()`](https://pkg.go.dev/google.golang.org/grpc@v1.62.0/ credentials/insecure) is used in `internal/controlstream/session.go`, the created gRPC connections are unencrypted and unauthenticated. A malicious unprivileged user could make the agent connect the host to a rogue Landscape server, leading to command execution. As discussed with Didier, encryption seems unfeasible due to Windows Defender. A mitigation here will involve authentication (possibly with certificates), ensuring that the communication of the Ubuntu agent will occur only with the trusted Windows service. 2. Information leak in the temporary Landscape configuration file: `/etc/landscape/client.conf.new` is a temporary file created by the Ubuntu service in `internal/system/landscape.go` to store the Landscape configuration. This file can also store sensitive information such as the account-wide registration key, `registration_key`. This could lead to auto-registration of any computer on the Landscape server. As a mitigation, the permission model could be adjusted so that only the Landscape client can read it, not any user. 3. Command execution inside the Windows host: In `internal/system/system.go`, all mounts are iterated and checked for communication with the 9P protocol (which is standard for the second version of WSL). These drives are checked with `s.findCmdExe()` to contain the `cmd.exe` executable. [As USB drives can be made visible inside the WSL instance](https://learn.microsoft.com/en-us/windows/wsl/connect-usb), it may be possible for a rogue `cmd.exe` executable file from a USB drive to be executed. As discussed with Jean and Didier, this assumption should be manually validated. 4. Crash when using IPv6 domain servers: When detecting the address of the Windows host, the agent checks if the NAT mode is used. If so, then the `/etc/resolv.conf` file is parsed in search of `nameserver` entries. If the entry is an IPv6 entry, the address will be concatenated with the port using the `Sprintf` function. The result of this concatenation is ambiguous because it's not using the `[]:` IPv6 notation, further connections may crash. Please see [this](https://github.com/golang/go/issues/28308) proposed Golang vet check. Let me know if there is anything I can assist with in the meantime. Many thanks! ** Bug watch added: github.com/golang/go/issues #28308 https://github.com/golang/go/issues/28308 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052495 Title: [MIR] wsl-pro-service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wsl-pro-service/+bug/2052495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2019951] Re: [MIR] libmysofa
Thanks for the confirmation, Sebastien! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2019951 Title: [MIR] libmysofa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmysofa/+bug/2019951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047149] Re: [MIR] speexdsp
I reviewed `speexdsp` `1.2.1-1` as checked into Noble. This shouldn't be considered a full audit, but rather a quick gauge of maintainability that involves static and dynamic analysis techniques. Speex is an open-source and free audio compression codec specialised in reproducing human speech (at low bitrates, ~2.1–32 kbit/s/channel). The format is contained by other formats such as Ogg and Flash Video. The format was replaced by its parent organisation, Xiph, with the Opus format. Despite its obsoletion, the format is still supported by open-source software such as [OpenWrt](https://github.com/openwrt/packages/issues/3747). SpeexDSP is a library that includes the preprocessor, the acoustic echo canceller, the jitter buffer, and the resample. It should be noted that `speexdsp`'s code was part of main until Ubuntu 22.04. Before this release, the codebase wasn't represented by a separate package but as part of the `speex` package. As SpeexDSP is a no-dependency library, it can be linked by programs with `-lspeexdsp -lm`. Likewise, the simple input is the Speex-encoded data provided by the program linking SpeexDSP. As the library is written in C but lacks OS interaction, the codebase is prone to memory corruption issues that may ultimately lead to code execution in the context of the parent process. - CVE History - There is no CVE issued for SpeexDSP. - The Speex library, which is a sibling codebase as `speexdsp` was derived from it, has two other CVEs in the past: - CVE-2020-23904: Bogus stack buffer overflow that couldn't be validated by the maintainers. - CVE-2020-23903: Division by zero in `speexenc`, an example program - The Speex sibling codebase was also integrated into OSS-Fuzz. - The integration definition files are placed in the [Speex](https://gitlab.xiph.org/xiph/speex/-/blob/master/contrib/oss-fuzz/speexd ec_fuzzer.cc) and [OSS-Fuzz](https://github.com/google/oss-fuzz/tree/master/projects/speex) repositories. - [There are 13 bugs](https://bugs.chromium.org/p/oss-fuzz/issues/list?q=speex=1) between 2019 and 2021 that were maturely tackled by the maintainers. - Build-Depends - It depends only on `libm` and `libc`. - pre/post inst/rm scripts - N/A - init scripts - N/A - systemd units - N/A - dbus services - N/A - setuid binaries - N/A - binaries in PATH - N/A - sudo fragments - N/A - polkit files - N/A - udev rules - N/A - unit tests / autopkgtests - There is no unit test for the whole codebase. - The encoding and decoding of the Speex code are tested in the previously-mentioned sibling codebase and OSS-Fuzz. - cron jobs - N/A - Build logs - N/A - Processes spawned - N/A - Memory management - The allocations take place for the members of the "states". These are internal structures, with multiple fields, that contain the current state of a given operation executed by the library. - The library defines wrappers over the standard memory management functions in its `libspeexdsp/os_support.h` file. These wrapper functions are called in all files where memory management is needed. The functions are properly called: if the library allocates a lot of members in an initialisation function (for example, `speex_preprocess_state_init`, which deals with allocating `SpeexPreprocessState` structures), it also frees them in another specialised function (to continue the preprocessor example, in the `speex_preprocess_state_destroy` function). - File IO - Files are opened in: - `libspeexdsp/testecho.c`, which is a test program that has arguments corresponding to the files to be opened and written; and - `libspeexdsp/mdf.c`, in which the 3 file paths are hard-coded (for example, `aec_rec.sw`) and safely opened and written. - Logging - The library logs static messages using functions defined in its `libspeexdsp/os_support.h`, such as `speex_warning` and `speex_notify`. - It also exports a logging-related, speex_resampler_strerr, which deals with converting a resampling status code into a string. - Environment variable usage - N/A - Use of privileged functions - N/A - Use of cryptography / random number sources etc - N/A - Use of temp files - N/A - Use of networking - N/A - Use of WebKit - N/A - Use of PolicyKit - N/A - Any significant cppcheck results - `cppcheck` was run again with additional flags to include the headers. - No warning was generated. - The `cppcheck.manual.txt` file was additionally generated. - Any significant Coverity results - Coverity reported two issues with possible security impact. Both are in the `update_filer` function from `resample.c`, but they were manually invalidated: - `st->num_rate/st->den_rate` cannot trigger a division by zero. `st->den_rate` is set in the function `speex_resampler_set_rate_frac` to the value of one argument of `update_filter`. The argument is checked in the prologue of the function to contain a value different from 0. -
[Bug 2031491] Re: [MIR] libemail-simple-perl ( libemail-mime-perl dependency as libmail-dmarc-perl dependency)
** Changed in: libemail-simple-perl (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2031491 Title: [MIR] libemail-simple-perl ( libemail-mime-perl dependency as libmail- dmarc-perl dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libemail-simple-perl/+bug/2031491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2029379] Re: [MIR] promote libdbd-sqlite3-perl (libmail-dmarc-perl dependency)
** Changed in: libdbd-sqlite3-perl (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2029379 Title: [MIR] promote libdbd-sqlite3-perl (libmail-dmarc-perl dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbd-sqlite3-perl/+bug/2029379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054903] [NEW] ubuntu-bug ubuntu-release-upgrader-core
Public bug reported: ... .. . Get:116 http://archive.ubuntu.com/ubuntu jammy-backports/multiverse amd64 c-n-f Metadata [116 B] Fetched 81.0 MB in 6s (10.0 MB/s) Checking package manager Reading package lists... Done Building dependency tree Reading state information... Done Calculating the changes Calculating the changes Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. Restoring original system state Aborting Reading package lists... Done Building dependency tree Reading state information... Done >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>> That's what I see when I try to upgrade from ubuntu 20 to 22 I have tried looking into the log files /var/log/dist-upgrade main.log and apt.log. They are attached in a file. I do have installed BRIGHTNESS CONTROLLER. That app is great. 2 thumbs up! It prevents the light from my screen monitor to blow out the corneas in my eyes. It is really a good app. I can't sing enough praises for it. That might be was is holding up my upgrade. Please let me know. aTdHvAaNnKcSe, George ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.41 ProcVersionSignature: Ubuntu 5.4.0-172.190-generic 5.4.259 Uname: Linux 5.4.0-172-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Feb 24 18:15:45 2024 InstallationDate: Installed on 2018-01-28 (2218 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to focal on 2024-02-24 (0 days ago) mtime.conffile..etc.update-manager.release-upgrades: 2024-02-24T16:47:34.949122 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal third-party-packages ** Attachment added: "main.log and apt.log" https://bugs.launchpad.net/bugs/2054903/+attachment/5749051/+files/ubuntu_bug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054903 Title: ubuntu-bug ubuntu-release-upgrader-core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2054903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862822] Re: init_on_alloc=1 causes big performance regression for ZFS
> It can be turned off during boot by using init_on_alloc=0 kernel parameter. So any user who is affected by this performance issue can mitigate that by disabling the hardening option, after considering its possible consequences. And one can find the root cause only by test and compare with other kernel with init_on_alloc=0 by default, and iterate over all config options and kernel changes. Looks like another point to add into "someone's performance guide", because it can't be mitigated easily via kernel interface changes from module's side (AFAIK). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862822 Title: init_on_alloc=1 causes big performance regression for ZFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971693] Re: Alt+Tab is broken for Java (AWT/Swing) apps in Wayland session
~vanvugt Thanks! When should 42.1 come to Ubuntu 22.04? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971693 Title: Alt+Tab is broken for Java (AWT/Swing) apps in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1971693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971112] Re: File picker gets bigger more and more each time!
Confirmed now that the same bug happens on the default installed Firefox browser. Setup tested used two screens with different resolutions: 1366x768 and 1920x1080 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971112 Title: File picker gets bigger more and more each time! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1971112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971112] Re: File picker gets bigger more and more each time!
Hi, I get the same bug. It is mainly under Google Chrome, effecting multiple of my users (they only use file open on that). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971112 Title: File picker gets bigger more and more each time! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1971112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970605] [NEW] New video recording feature in new screenshot tool crashes
Public bug reported: The new screenshot tool with the video recording feature keeps crashing every time I try to record a part of my screen or the whole screen. The red timer shows up for less than a second on the top right of my screen and then it disappears. I've tried restarting my PC but it doesn't fix it. I have also tried OBS Studio to see if it crashes there, but it doesn't. Only the new screenshot tool in Ubuntu 22.04 does it. Screenshotting works fine, only the video recording has a problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 27 13:40:04 2022 DistUpgraded: 2022-04-25 15:08:16,726 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.60.02, 5.15.0-25-generic, x86_64: installed nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP107 [GeForce GTX 1050 Ti] [1458:3733] InstallationDate: Installed on 2021-11-08 (169 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-25 (1 days ago) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970605 Title: New video recording feature in new screenshot tool crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1970605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970413] [NEW] Moving windows around is laggy
Public bug reported: When I move a window around, it's lagging and sometimes it's freezing for a second. This is happening after the upgrade to Ubuntu 22.04. Also, it happens all the time, even after I restart my computer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 15:09:42 2022 DistUpgraded: 2022-04-25 15:08:16,726 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.60.02, 5.15.0-25-generic, x86_64: installed nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP107 [GeForce GTX 1050 Ti] [1458:3733] InstallationDate: Installed on 2021-11-08 (168 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-25 (1 days ago) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy performance ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970413 Title: Moving windows around is laggy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1970413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970106] [NEW] Running "pipenv shell" fails with AttributeError
Public bug reported:
I recently upgraded from Ubuntu 20.04 to 22.04
Running pipenv shell to create a virtual env results in the following
and no environment is created.
Traceback (most recent call last):
File "/usr/bin/pipenv", line 33, in
sys.exit(load_entry_point('pipenv==11.9.0', 'console_scripts', 'pipenv')())
File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py", line 722,
in __call__
return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py", line 697,
in main
rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py", line 1066,
in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py", line 895,
in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py", line 535,
in invoke
return callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/pipenv/cli.py", line 548, in shell
from .import core
File "/usr/lib/python3/dist-packages/pipenv/core.py", line 21, in
import requests
File "/usr/lib/python3/dist-packages/pipenv/vendor/requests/__init__.py",
line 65, in
from . import utils
File "/usr/lib/python3/dist-packages/pipenv/vendor/requests/utils.py", line
27, in
from .cookies import RequestsCookieJar, cookiejar_from_dict
File "/usr/lib/python3/dist-packages/pipenv/vendor/requests/cookies.py", line
172, in
class RequestsCookieJar(cookielib.CookieJar, collections.MutableMapping):
AttributeError: module 'collections' has no attribute 'MutableMapping'
Further info:
lsb_release -rd:
Description:Ubuntu 22.04 LTS
Release:22.04
apt-cache policy pipenv:
pipenv:
Installed: 11.9.0-1.1
Candidate: 11.9.0-1.1
Version table:
*** 11.9.0-1.1 500
500 http://gr.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: pipenv 11.9.0-1.1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 24 16:25:34 2022
InstallationDate: Installed on 2021-10-16 (189 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
SourcePackage: pipenv
UpgradeStatus: Upgraded to jammy on 2022-04-23 (0 days ago)
** Affects: pipenv (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/1970106
Title:
Running "pipenv shell" fails with AttributeError
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipenv/+bug/1970106/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963555] Re: xhci: Fix command ring abort, write all 64 bits to CRCR register.
You referenced the original report, patch, and promotion to Linux Next for review. The new information is that the resolution for the issue you referenced was reviewed and promoted by Greg KH from Linux Next to his queue for Linus https://lore.kernel.org/all/yayq%2fxdb%2fphss7%...@kroah.com/ in the production kernel back on December 5, 2021. BTW it was accepted into Linus's mainline queue with commit https://lore.kernel.org/all/163872600645.987.7156724710444619664.pr-tracker-...@kernel.org/ later that day. Interestingly Greg mentioned merging these changes into the stable queue. If he actually did so (I didn't notice where) it might help to make sure that 21.10 and 22.04 are immediately rebased to include the mainline included patches. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963555 Title: xhci: Fix command ring abort, write all 64 bits to CRCR register. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963555] Re: xhci: Fix command ring abort, write all 64 bits to CRCR register.
This appears to be the resolution upstream: https://lore.kernel.org/linux-usb/yay1eiy%2ff7ezp...@kroah.com/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963555 Title: xhci: Fix command ring abort, write all 64 bits to CRCR register. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963555] Re: xhci: Fix command ring abort, write all 64 bits to CRCR register.
I have also experienced this upstream bug which causes the USB hubs to drop all attached devices. This means that external drive devices all disappear almost as quickly as they appear. Basically it's a show stopper since I can't use my USB attached data drives at all any more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963555 Title: xhci: Fix command ring abort, write all 64 bits to CRCR register. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962021] Re: Make the deb package install the firefox snap
I just found it completely trashed my system on install. The reason was that I don't have snapd on my machine and installation attempted to install it, causing X to crash and login to reject my account because I'm not in 'nopasswdlogin' group. Reverting back to firefox=97.0.1+build1-0ubuntu1 and setting "apt-mark hold firefox" fixed 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/1962021 Title: Make the deb package install the firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1962021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954817] [NEW] Missing build dependency
Public bug reported: Versions >=0.9.0 require xkbregistry as a build dependency. The package "libxkbregistry-dev" provides this for Debian, and should be listed as a build dependency so the builds pass. ** Affects: waybar (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/1954817 Title: Missing build dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/waybar/+bug/1954817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1954478] Re: Loaded Evolution found gjs repeat calls from ding.js overloaded memory froze 21.04
Hi Sergio; I just run chown then ran chmod 777 so I could edited the entire code *# out of the ding.js. I am a very inexperienced programmer. I studied C, C++, J++, Python 2 and 3 but I never built a file for a program. I did desktop support for 20 years: Macintosh, PC -DOS, Windows form 2.0 to current windows 10, NTFS, OS/2, Unix using SMIT, Linux, UBUNTU but I would need many hour of troubleshooting to find what the problem is with the current Ding.js and why it constantly repeats the call to run GJS in an infinite loop. The program can still call ding.js but nothing will run . Cheers George Tucker Retired -Original Message- From: Sergio Costas <1954...@bugs.launchpad.net> Reply-To: Bug 1954478 <1954...@bugs.launchpad.net> To: george.tucker2...@gmail.com Subject: [Bug 1954478] Re: Loaded Evolution found gjs repeat calls from ding.js overloaded memory froze 21.04 Date: Fri, 10 Dec 2021 21:07:52 - Can you put the specific changes that you did to the code? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954478 Title: Loaded Evolution found gjs repeat calls from ding.js overloaded memory froze 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1954478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746582] Re: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Yevhen (yevhen.b) works in rasberry pi4 with ubuntu server 20.04 arm64 & mate-desktop thnx ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746582 Title: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1746582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951605] [NEW] failed. no reboot
Public bug reported: no reboot after restart ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.17 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 19 20:36:49 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.17 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951605 Title: failed. no reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1951605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947860] Re: qemu-arm-static swallows the program name, and shifts all arguments left
Just a note: qemu-arm-static itself has nothing to do with it. I tried older versions from hirsute and focal, and they exhibit the same behaviour. I can however confirm that the problem lies in the binfmt-P logic handling - if I re-register qemu-arm-static manually without the binfmt-P flag, it no longer swallows the first argument. So my hunch is that whatever part of the kernel/anything passes the arguments to qemu clearly is not binfmt-P aware, while qemu itself is, thus the discrepancy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947860 Title: qemu-arm-static swallows the program name, and shifts all arguments left To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1947860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945007] [NEW] package nvidia-kernel-common-460 (not installed) failed to install/upgrade: conflicting packages - not installing nvidia-kernel-common-460
Public bug reported: please check the error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-common-460 (not installed) ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 24 20:55:55 2021 ErrorMessage: conflicting packages - not installing nvidia-kernel-common-460 InstallationDate: Installed on 2021-05-07 (140 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-460 Title: package nvidia-kernel-common-460 (not installed) failed to install/upgrade: conflicting packages - not installing nvidia-kernel-common-460 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945007 Title: package nvidia-kernel-common-460 (not installed) failed to install/upgrade: conflicting packages - not installing nvidia-kernel- common-460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1945007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875920] Re: New default %PROFILE_MEDIUM breaks root ceritificates which use SHA1
Is it the same issue I've hit with apt on Focal? 'apt update' fails on https://mirror.yandex.ru/ubuntu with: Certificate verification failed: The certificate is NOT trusted. The certificate chain uses insecure algorithm. Could not handshake: Error in the certificate verification. [IP: 213.180.204.183 443] The issue is supposedly fixed in GnuTLS 3.7.2. Are there any plans to backport the fix to Focal? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875920 Title: New default %PROFILE_MEDIUM breaks root ceritificates which use SHA1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1875920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938996] [NEW] pulseaudio-utils overwrites /usr/share/bash-completion/completions/pulseaudio which belongs to pulseaudio
Public bug reported: Unpacking pulseaudio-utils (1:15.0+dfsg1-1ubuntu1) over (1:14.2-2ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-fIyGyr/16-pulseaudio-utils_1%3a15.0+dfsg1-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/bash-completion/completions/pulseaudio', which is also in package pulseaudio 1:14.2-2ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amarao 5329 F pulseaudio /dev/snd/pcmC0D7p: amarao 5329 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Thu Aug 5 12:07:36 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-22 (1505 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: error while loading shared libraries: libpulsecommon-14.2.so: cannot open shared object file: No such file or directory RebootRequiredPkgs: libc6 libc6 SourcePackage: pulseaudio UpgradeStatus: Upgraded to impish on 2021-06-03 (62 days ago) dmi.bios.date: 07/13/2020 dmi.bios.release: 2.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.14.2 dmi.board.name: 0PF86Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.14.2:bd07/13/2020:br2.14:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. modified.conffile..etc.xdg.Xwayland-session.d.00-pulseaudio-x11: [deleted] ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938996 Title: pulseaudio-utils overwrites /usr/share/bash- completion/completions/pulseaudio which belongs to pulseaudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1938996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934837] [NEW] package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1933842 *** https://bugs.launchpad.net/bugs/1933842 Public bug reported: I did an upgrade on a Dell Latitude E6410 from 18.04 to 20.04. It failed to install the package initramfs-tools. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jul 6 20:23:27 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-12-24 (2022 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-07-07 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934837 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1934837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933199] [NEW] Mainline builds for v5.10.37 to v5.10.45 contain packages for v5.11.0
Public bug reported: On the mainline kernel server, all folders for kernels v5.10.37 to v5.10.45 contain packages for kernel v5.11.0. https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10.37/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: build kernel mainline ** Attachment added: "v5.10.45 page with links for v5.11.0" https://bugs.launchpad.net/bugs/1933199/+attachment/5506192/+files/Selection_009.png ** Description changed: - On the mainline PPA server, all folders for kernels v5.10.37 to v5.10.45 - contain packages for kernel v5.11.0! + On the mainline kernel server, all folders for kernels v5.10.37 to + v5.10.45 contain packages for kernel v5.11.0. https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10.37/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933199 Title: Mainline builds for v5.10.37 to v5.10.45 contain packages for v5.11.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931762] [NEW] Error upgrading distro
Public bug reported: Error upgradeing to 20.04. error Dist-upgrade failed: 'E:Unable to correct problems, you have held broken packages.' Checked for boken packages: None Ran updates and autoclean ried removing Python as tlogs indivcate this may be a problem ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.44 ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Jun 12 10:53:45 2021 InstallationDate: Installed on 2017-01-11 (1612 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-06-12 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931762 Title: Error upgrading distro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1931762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931714] [NEW] installed openmpi-bin package post installation script subprocess error 2
Public bug reported: using sotware update to load gparted. I tried also upating to 21.04 and had the same problem. and most of my programs display a like error message. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gparted 1.1.0-0.1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 09:34:24 2021 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gparted UpgradeStatus: Upgraded to hirsute on 2021-06-08 (2 days ago) ** Affects: gparted (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute 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/1931714 Title: installed openmpi-bin package post installation script subprocess error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1931714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841826] Re: Going to sleep instead of logging in while lid closed & external display
It finally crashed, no video on suspend. I likely never reached 2 hrs. before I shut down. So everything's similar to others it seems. I'll try some things and see. If I can do anything I'll update. If it isn't avoidable at least I understand it and won't waste too much time until I see something posted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841826 Title: Going to sleep instead of logging in while lid closed & external display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1841826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841826] Re: Going to sleep instead of logging in while lid closed & external display
So far this only occurs on the initial login after boot-up. Subsequent suspends do not cause an issue. If I remove the laptop from the dock no issue, but now I only have the laptop screen. The machine I'm using is a W530. For me this appears to be an initial boot-up only issue, of course I still would like to fix this. I can see where if used in lab environments it can be a serious issue, especially if your remote. I've seen Windows Sleep issues years ago, I haven't seen that many lately in Windows. Certain code can cause sleep issues for this laptop, power managers for one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841826 Title: Going to sleep instead of logging in while lid closed & external display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1841826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841826] Re: Going to sleep instead of logging in while lid closed & external display
Lenovo 4338 Mini-Dock with Nvidia K1000M running Dual external monitors. Ubuntu 20.04 suspends after login as mentioned. This seemed to start after loading the Nvidia 390 driver since the Nouveau driver did not work correctly. The video is fine now and everything works fine except I login, the suspend occurs, I press the dock power button and the machine runs normally. My first assumption is its the video driver and I searched for suggested fixes or alternative drivers. Not sure which way to go seems like a few Lenovo users here are in the same place. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841826 Title: Going to sleep instead of logging in while lid closed & external display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1841826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912673] Re: sounds not working on Dell XPS 17 (9700)
I am facing the same issue, I have to login to different OS to use mic and sound. Do we have any news on fix release date? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912673 Title: sounds not working on Dell XPS 17 (9700) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909814] Re: Keyboard not working
Same problem, my Medion Akoya S15449 keyboard doesn't work in any linux distro i tried (Ubuntu 20.10,Pop os 20.10, Latest Arch Linux). It's not been detected by lsusb or lspci. I think it's a driver issue. I kindly ask to fix. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909814 Title: Keyboard not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751497] Re: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2
Just updated to 21.04 today and still getting this error. name -a ; cat /etc/os-release ; dmesg |grep nouveau Linux fedora 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux NAME="Ubuntu" VERSION="21.04 (Hirsute Hippo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 21.04" VERSION_ID="21.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=hirsute UBUNTU_CODENAME=hirsute [Fri Apr 23 10:35:55 2021] fb0: switching to nouveaufb from VESA VGA [Fri Apr 23 10:35:55 2021] nouveau :01:00.0: vgaarb: deactivate vga console [Fri Apr 23 10:35:55 2021] nouveau :01:00.0: NVIDIA G98 (298200a2) [Fri Apr 23 10:35:55 2021] nouveau :01:00.0: bios: version 62.98.29.00.00 [Fri Apr 23 10:35:55 2021] nouveau :01:00.0: bios: M0203T not found [Fri Apr 23 10:35:55 2021] nouveau :01:00.0: bios: M0203E not matched! [Fri Apr 23 10:35:55 2021] nouveau :01:00.0: fb: 512 MiB DDR2 [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: VRAM: 512 MiB [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: GART: 1048576 MiB [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: TMDS table version 2.0 [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: DCB version 4.0 [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: DCB outp 00: 02000300 0028 [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: DCB outp 01: 01000302 0030 [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: DCB outp 02: 04011310 0028 [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: DCB conn 00: 1030 [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: DCB conn 01: 0100 [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: MM: using M2MF for buffer copies [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: DRM: allocated 1920x1080 fb: 0x7, bo 675ec200 [Fri Apr 23 10:35:56 2021] fbcon: nouveaudrmfb (fb0) is primary device [Fri Apr 23 10:35:56 2021] nouveau :01:00.0: [drm] fb0: nouveaudrmfb frame buffer device [Fri Apr 23 10:35:56 2021] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on minor 0 [Fri Apr 23 10:37:54 2021] nouveau :01:00.0: Direct firmware load for nouveau/nv98_fuc084 failed with error -2 [Fri Apr 23 10:37:54 2021] nouveau :01:00.0: Direct firmware load for nouveau/nv98_fuc084d failed with error -2 [Fri Apr 23 10:37:54 2021] nouveau :01:00.0: msvld: unable to load firmware data [Fri Apr 23 10:37:54 2021] nouveau :01:00.0: msvld: init failed, -19 [Fri Apr 23 10:38:08 2021] nouveau :01:00.0: Direct firmware load for nouveau/nv98_fuc084 failed with error -2 [Fri Apr 23 10:38:08 2021] nouveau :01:00.0: Direct firmware load for nouveau/nv98_fuc084d failed with error -2 [Fri Apr 23 10:38:08 2021] nouveau :01:00.0: msvld: unable to load firmware data [Fri Apr 23 10:38:08 2021] nouveau :01:00.0: msvld: init failed, -19 [Fri Apr 23 10:38:17 2021] nouveau :01:00.0: Direct firmware load for nouveau/nv98_fuc084 failed with error -2 [Fri Apr 23 10:38:17 2021] nouveau :01:00.0: Direct firmware load for nouveau/nv98_fuc084d failed with error -2 [Fri Apr 23 10:38:17 2021] nouveau :01:00.0: msvld: unable to load firmware data [Fri Apr 23 10:38:17 2021] nouveau :01:00.0: msvld: init failed, -19 *-display description: VGA compatible controller product: G98 [GeForce 8400 GS Rev. 2] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:30 memory:fd00-fdff memory:d000-dfff memory:fa00-fbff ioport:d800(size=128) memory:c-d dpkg -l |egrep 'nouveau|nvidia' ii libdrm-nouveau2:amd64 2.4.104-1build1 amd64Userspace interface to nouveau-specific kernel DRM services -- runtime ii nouveau-firmware 20091212-0ubuntu1 all Firmware for nVidia graphics cards ii xserver-xorg-video-nouveau1:1.0.17-1 amd64X.Org X server -- Nouveau display driver -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751497 Title: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751497/+subscriptions --
[Bug 1916079] [NEW] dual boot failed after windows 10 update
Public bug reported: ubuntu grub screen does not appear at startup. system only boots to Windows 10 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 18 16:10:54 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_CA.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916079 Title: dual boot failed after windows 10 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1916079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910870] [NEW] gnome-terminal-server crashed with SIGABRT in g_assertion_message_cmpnum
Public bug reported: Gnome terminal keeps crashing for me several times a day; I haven't been able to reproduce it consistently but it's happening I am scrolling the window. $ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 $ apt-cache policy gnome-terminal gnome-terminal: Installed: 3.36.2-1ubuntu1~20.04 Candidate: 3.36.2-1ubuntu1~20.04 Version table: *** 3.36.2-1ubuntu1~20.04 500 500 http://gr.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1.1-1ubuntu1 500 500 http://gr.archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Apport crash file" https://bugs.launchpad.net/bugs/1910870/+attachment/5451341/+files/_usr_libexec_gnome-terminal-server.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910870 Title: gnome-terminal-server crashed with SIGABRT in g_assertion_message_cmpnum To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1910870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904601] Re: lftp 4.8.1 crashes upon exit
any update on this? I retested it after upgrading libc6, as mentioned to other bug reports, but the problem remains -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904601 Title: lftp 4.8.1 crashes upon exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lftp/+bug/1904601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907212] Re: Power consumption regression after upgrade to 20.10 5.8.0-31-generic
Those errors aren't printed when booting with hdmi connected. Attached related dmesg output. Device `01:00.1` is suspended. I can confirm from documentation about this laptop (Acer aspire A715-71G) that the embedded display is connected to the intel GPU (eDP) and the HDMI port is connected to the nvidia GPU, this must be the most probable case on these laptops. Otherwise, maybe `01:00.1` device wouldn't exist. When booting with intel gpu only, HDMI interface isn't listed on xrandr and HDMI screen has no input. This is supposed to happen as HDMI is connected to nvidia and nvidia should be powered off, right? This also happens with previous kernels and should not be related with this bug. ** Attachment added: "dmesg_#37~lp1907212+4_hdmiconnectedbeforeboot_intel.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+attachment/5445188/+files/dmesg_%2337~lp1907212+4_hdmiconnectedbeforeboot_intel.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907212 Title: Power consumption regression after upgrade to 20.10 5.8.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908575] [NEW] Application crashes if a component inside a Kirigami.BasicListItem contentItem has an id
Public bug reported: Kirigami/QML applications crash when using Kirigami.BasicListItem as a delegate with a custom contentItem and component inside contentItem has an id and QQuickStyle's style is org.kde.desktop. Elisa for example. Removing the id or the org.kde.desktop style works. More info and an example app: https://bugs.kde.org/show_bug.cgi?id=430261 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: qml-module-org-kde-qqc2desktopstyle (not installed) ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 17 22:46:33 2020 InstallationDate: Installed on 2020-12-10 (7 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: qqc2-desktop-style UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qqc2-desktop-style (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908575 Title: Application crashes if a component inside a Kirigami.BasicListItem contentItem has an id To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qqc2-desktop-style/+bug/1908575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907212] Re: Power consumption regression after upgrade to 20.10 5.8.0-31-generic
5.8.0-35-generic #37~lp1907212+4 Nvidia gpu successfully powered down. $ cat /sys/bus/pci/devices/:01:00.1/power/runtime_status suspended The previous snd_hda_intel error messages aren't printed anymore, yet "snd_hda_intel :01:00.1: can't change power state from D3cold to D0 (config space inaccessible)" are printed about 20 times again at boot. ** Attachment added: "dmesg_37~lp1907212+4.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+attachment/5444175/+files/dmesg_37~lp1907212+4.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907212 Title: Power consumption regression after upgrade to 20.10 5.8.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907212] Re: Power consumption regression after upgrade to 20.10 5.8.0-31-generic
With this one 5.8.0-35-generic #37~lp1907212+3, nvidia gpu isn't powered down: $ cat /sys/bus/pci/devices/:01:00.1/power/runtime_status active $ cat /sys/bus/pci/devices/:01:00.1/power/control auto At ~242 there are also snd_hda_intel errors on attached dmesg, which are later reprinted every ~120 seconds. ** Attachment added: "dmesg_lp1907212+3.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+attachment/5443765/+files/dmesg_lp1907212+3.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907212 Title: Power consumption regression after upgrade to 20.10 5.8.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907212] Re: Power consumption regression after upgrade to 20.10 5.8.0-31-generic
With this kernel 5.8.0-35-generic #37~lp1907212+2 nvidia gpu is successfully powered down, and idle power consumption was normal at 5-6 watt. $ cat /sys/bus/pci/devices/:01:00.1/power/runtime_status suspended $ cat /sys/bus/pci/devices/:01:00.1/power/control auto On dmesg output there are a lot more `snd_hda_intel :01:00.1: can't change power state from D3cold to D0 (config space inaccessible)` complaints. I also rebooted at nvidia performance mode, everything is normal but `:01:00.1/power/runtime_status` is again suspended. I don't know if it is supposed to be like this but with 5.8.0-31-generic when booting with nvidia performance mode, `:01:00.1/power/runtime_status` is active. ** Attachment added: "dmesg_5.8.0-35~lp1907212+2.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+attachment/5443236/+files/dmesg_5.8.0-35~lp1907212+2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907212 Title: Power consumption regression after upgrade to 20.10 5.8.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907212] Re: Power consumption regression after upgrade to 20.10 5.8.0-31-generic
$ cat /sys/bus/pci/devices/:01:00.1/power/runtime_status active $ cat /sys/bus/pci/devices/:01:00.1/power/control auto They are the same with both 5.8.0-31-generic and 5.8.0-35-generic from https://people.canonical.com/~khfeng/lp1907212/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907212 Title: Power consumption regression after upgrade to 20.10 5.8.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907212] Re: Power consumption regression after upgrade to 20.10 5.8.0-31-generic
Dmesg after booting with provided kernel https://people.canonical.com/~khfeng/lp1907212/ High power consumption remains, `echo :01:00.1 | sudo tee /sys/module/snd_hda_intel/drivers/pci:snd_hda_intel/unbind` works. ** Attachment added: "dmesg_5.8.0-35-generic.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+attachment/5442741/+files/dmesg_5.8.0-35-generic.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907212 Title: Power consumption regression after upgrade to 20.10 5.8.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907212] Re: Power consumption regression after upgrade to 20.10 5.8.0-31-generic
$ uname -r 5.10.0-051000rc6-generic Dmesg attached after booting with intel gpu and 5.10, high power consumption remains, again `echo :01:00.1 | sudo tee /sys/module/snd_hda_intel/drivers/pci:snd_hda_intel/unbind` works. ** Attachment added: "dmesg_intel_powersavingmode_5.10.0-051000rc6-generic.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+attachment/5442453/+files/dmesg_intel_powersavingmode_5.10.0-051000rc6-generic.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907212 Title: Power consumption regression after upgrade to 20.10 5.8.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907212] Re: Power consumption regression after upgrade to 20.10 5.8.0-31-generic
It was certainly working with 5.4.0-* from 20.04 at some time, I have been mainly using dGPU for 2-3 months, and wouldn't have noticed any regressions. Strangely, I tested with 5.4.0-56-generic that remained after the upgrade, and it is also not powering down dGPU. 20.10 didn't upgrade nvidia driver, I currently have 450.80.02 Something important I just noticed, at 19.10 and 20.04 nvidia vga and related audio function devices weren't visible at lspci when booting with intel gpu only, but after upgrading to 20.10 they are visible again when booting with intel gpu. I suspect this mechanism was essential for power management and it has changed with 20.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907212 Title: Power consumption regression after upgrade to 20.10 5.8.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907212] Re: Power consumption regression after upgrade to 20.10 5.8.0-31-generic
This error on dmesg is relevant `snd_hda_intel :01:00.1: can't change power state from D3cold to D0 (config space inaccessible)`, if I unbind the nvidia audio device function with `echo :01:00.1 > /sys/module/snd_hda_intel/drivers/pci:snd_hda_intel/unbind` power consumption returns to normal, idling at 5-6 watts and runtime_status becomes suspended. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907212 Title: Power consumption regression after upgrade to 20.10 5.8.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907212] Re: Power consumption regression after upgrade to 20.10 5.8.0-31-generic
** Summary changed: - Power consumption regression after ugrade to 20.10 5.8.0-31-generic + Power consumption regression after upgrade to 20.10 5.8.0-31-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907212 Title: Power consumption regression after upgrade to 20.10 5.8.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907212] Re: Power consumption regression after ugrade to 20.10 5.8.0-31-generic
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+attachment/5441929/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907212 Title: Power consumption regression after upgrade to 20.10 5.8.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907212] Re: Power consumption regression after ugrade to 20.10 5.8.0-31-generic
** Attachment added: "lspci-vnvn" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+attachment/5441928/+files/lspci-vnvn -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907212 Title: Power consumption regression after upgrade to 20.10 5.8.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907212] [NEW] Power consumption regression after upgrade to 20.10 5.8.0-31-generic
Public bug reported: After upgrading to Ubuntu 20.10 which ships kernel 5.8.0-31-generic, battery life is considerably less and power consumption is about 10 watts more idle, (idling at 14-15 watts) using integrated graphics. This is a hybrid GPU laptop Intel HD 630/GP107M, and based on past experiences a possible cause is not powering off the dedicated GPU completely while using the integrated. Running sudo powertop --auto-tune doesn't eliminate the issue. $ cat /sys/bus/pci/devices/:01:00.0/power/runtime_status suspended $ cat /sys/bus/pci/devices/:01:00.0/power/runtime_suspended_time 1815948 $ cat /sys/bus/pci/devices/:01:00.1/power/runtime_status active $ cat /sys/bus/pci/devices/:01:00.1/power/runtime_suspended_time 3827 Device "01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller" appears active, does this mean that the audio subsystem of dGPU keeps it enabled, causing the 10-watt consumption? ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1907212/+attachment/5441927/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907212 Title: Power consumption regression after upgrade to 20.10 5.8.0-31-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 327362] Re: Some ISPs have .local domain which disables avahi-daemon
Discussion on this new issue: https://github.com/lathiat/nss- mdns/issues/75 ** Bug watch added: github.com/lathiat/nss-mdns/issues #75 https://github.com/lathiat/nss-mdns/issues/75 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/327362 Title: Some ISPs have .local domain which disables avahi-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/327362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 327362] Re: Some ISPs have .local domain which disables avahi-daemon
After some more searching I found an explanation of this issue in Ubuntu 20.04 and the correct way to disable it: https://github.com/lathiat/nss- mdns#etcmdnsallow -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/327362 Title: Some ISPs have .local domain which disables avahi-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/327362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 327362] Re: Some ISPs have .local domain which disables avahi-daemon
It seems not "fixed", but rather broken again in Ubuntu 20.04. My ISP DNS servers respond to all ".local" queries with "127.0.0.200", and mDNS just doesn't work in this case. Setting AVAHI_DAEMON_DETECT_LOCAL=0 does not help. This is regression from 18.04 where mDNS worked fine with default settings. And it's a pity, as mDNS is even more important after NetBIOS/SMB1 retirement in 20.04. Should I post details here or start a new issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/327362 Title: Some ISPs have .local domain which disables avahi-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/327362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905741] Re: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output
I confirm that the version 0.62.0-2ubuntu2.12 fixes the 0.62.0-2ubuntu2.11 bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905741 Title: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905741] Re: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output
# lsb_release -rd Description: Ubuntu 18.04.5 LTS Release: 18.04 I have an Epson TM BA Thermal network printer, configured in CUPS After today's unattended upgrade it stopped working Logs found on server [540009.389033] pdftoraster[63919]: segfault at d0400 ip 557a50f569a8 sp 7ffd5ca826d8 error 6 in pdftoraster[557a50f52000+8000] Thu Nov 26 14:14:19 2020: apport: report /var/crash/_usr_lib_cups_filter_pdftoraster.7.crash already exists and unseen, doing nothing to avoid disk usage DoS # dpkg -S /usr/lib/cups/filter/pdftoraster cups-filters-core-drivers: /usr/lib/cups/filter/pdftoraster Start-Date: 2019-11-25 17:01:06 Install cups-filters-core-drivers:amd64 # dpkg -l|grep cups-filters-core-drivers ii cups-filters-core-drivers 1.20.2-0ubuntu3.1 I checked what was updated with unattended upgrade Start-Date: 2020-11-24 06:20:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libpulse0:amd64 (1:11.1-1ubuntu7.10, 1:11.1-1ubuntu7.11) End-Date: 2020-11-24 06:20:10 and I rolled back # wget https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/17383699/+files/poppler-utils_0.62.0-2ubuntu2.10_amd64.deb # wget https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/17383699/+files/libpoppler73_0.62.0-2ubuntu2.10_amd64.deb # ls apt/ libpoppler73_0.62.0-2ubuntu2.10_amd64.deb poppler-utils_0.62.0-2ubuntu2.10_amd64.deb #dpkg -R --install apt/ and started to work again and of course apt-mark hold libpoppler73 poppler-utils # apt-cache policy poppler-utils libpoppler73 poppler-utils: Installed: 0.62.0-2ubuntu2.10 Candidate: 0.62.0-2ubuntu2.11 Version table: 0.62.0-2ubuntu2.11 500 500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://gr.archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages *** 0.62.0-2ubuntu2.10 100 100 /var/lib/dpkg/status 0.62.0-2ubuntu2 500 500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages libpoppler73: Installed: 0.62.0-2ubuntu2.10 Candidate: 0.62.0-2ubuntu2.11 Version table: 0.62.0-2ubuntu2.11 500 500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://gr.archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages *** 0.62.0-2ubuntu2.10 100 100 /var/lib/dpkg/status 0.62.0-2ubuntu2 500 500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905741 Title: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905704] Re: xpdf segmentation fault
# lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 I have an Epson TM BA Thermal network printer, configured in CUPS After today's unattended upgrade it stopped working Logs found on server [540009.389033] pdftoraster[63919]: segfault at d0400 ip 557a50f569a8 sp 7ffd5ca826d8 error 6 in pdftoraster[557a50f52000+8000] Thu Nov 26 14:14:19 2020: apport: report /var/crash/_usr_lib_cups_filter_pdftoraster.7.crash already exists and unseen, doing nothing to avoid disk usage DoS # dpkg -S /usr/lib/cups/filter/pdftoraster cups-filters-core-drivers: /usr/lib/cups/filter/pdftoraster Start-Date: 2019-11-25 17:01:06 Install cups-filters-core-drivers:amd64 # dpkg -l|grep cups-filters-core-drivers ii cups-filters-core-drivers 1.20.2-0ubuntu3.1 I checked what was updated with unattended upgrade Start-Date: 2020-11-24 06:20:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libpulse0:amd64 (1:11.1-1ubuntu7.10, 1:11.1-1ubuntu7.11) End-Date: 2020-11-24 06:20:10 and I rolled back # wget https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/17383699/+files/poppler-utils_0.62.0-2ubuntu2.10_amd64.deb # wget https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/17383699/+files/libpoppler73_0.62.0-2ubuntu2.10_amd64.deb # ls apt/ libpoppler73_0.62.0-2ubuntu2.10_amd64.deb poppler-utils_0.62.0-2ubuntu2.10_amd64.deb #dpkg -R --install apt/ and started to work again and of course apt-mark hold libpoppler73 poppler-utils # apt-cache policy poppler-utils libpoppler73 poppler-utils: Installed: 0.62.0-2ubuntu2.10 Candidate: 0.62.0-2ubuntu2.11 Version table: 0.62.0-2ubuntu2.11 500 500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://gr.archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages *** 0.62.0-2ubuntu2.10 100 100 /var/lib/dpkg/status 0.62.0-2ubuntu2 500 500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages libpoppler73: Installed: 0.62.0-2ubuntu2.10 Candidate: 0.62.0-2ubuntu2.11 Version table: 0.62.0-2ubuntu2.11 500 500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://gr.archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages *** 0.62.0-2ubuntu2.10 100 100 /var/lib/dpkg/status 0.62.0-2ubuntu2 500 500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Attachment added: "_usr_lib_cups_filter_pdftoraster.7.crash" https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905704/+attachment/5438244/+files/_usr_lib_cups_filter_pdftoraster.7.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905704 Title: xpdf segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668309] Re: Scaling on xps13 means only a part of the screen is visible at any time.
Yes, the problem seems to be that Ubuntu bundles an abandonware remote desktop package. I think the solution must be either to switch to a package that's supported, or to start maintaining vino. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668309 Title: Scaling on xps13 means only a part of the screen is visible at any time. To manage notifications about this bug go to: https://bugs.launchpad.net/vino/+bug/1668309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902778] [NEW] Touchpad dosen't work
Public bug reported: My touchpad dosent work after installation ubuntu!! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 3 21:27:30 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-11-03 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902778 Title: Touchpad dosen't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1902778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900841] [NEW] Bookeen Saga device undetected by Calibre
Public bug reported: Mobile e-reader device "Saga" made by Bookeen is well-detected in my Linux environment as an external USB device but Calibre does not notice it when I plug it in... Switching to another device such as "Bookeen Muse" or "generic" in the control pannel does not help to fix the problem. ** Affects: calibre (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/1900841 Title: Bookeen Saga device undetected by Calibre To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1900841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899492] [NEW] crash during ubuntu 20.04 installation in dell g5 15
Public bug reported: a crash during ubuntu installation ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 12 17:05:15 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899492 Title: crash during ubuntu 20.04 installation in dell g5 15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1899492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898960] [NEW] package libgnutls30:amd64 3.6.9-5ubuntu1.2 failed to install/upgrade: package libgnutls30:amd64 is already installed and configured
Public bug reported: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 19.10 Package: libgnutls30:amd64 3.6.9-5ubuntu1.2 ProcVersionSignature: Ubuntu 5.3.0-64.58-generic 5.3.18 Uname: Linux 5.3.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.9 AptdaemonVersion: 1.1.1+bzr982-0ubuntu28.2 Architecture: amd64 CrashReports: 600:0:124:339942:2020-10-08 01:43:49.454015254 +:2020-10-08 01:43:50.454015254 +:/var/crash/libgnutls30:amd64.0.crash Date: Thu Oct 8 01:43:50 2020 DpkgTerminalLog: Preparing to unpack .../libgnutls30_3.6.13-2ubuntu1.3_amd64.deb ... Unpacking cups-server-common (2.3.1-9ubuntu1.1) over (2.2.12-2ubuntu1.1) ... dpkg: error processing package libgnutls30:amd64 (--configure): package libgnutls30:amd64 is already installed and configured DuplicateSignature: package:libgnutls30:amd64:3.6.9-5ubuntu1.2 Unpacking cups-server-common (2.3.1-9ubuntu1.1) over (2.2.12-2ubuntu1.1) ... dpkg: error processing package libgnutls30:amd64 (--configure): package libgnutls30:amd64 is already installed and configured ErrorMessage: package libgnutls30:amd64 is already installed and configured InstallationDate: Installed on 2020-10-03 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4ubuntu0.1 SourcePackage: dpkg Title: package libgnutls30:amd64 3.6.9-5ubuntu1.2 failed to install/upgrade: package libgnutls30:amd64 is already installed and configured UpgradeStatus: Upgraded to eoan on 2020-10-08 (0 days ago) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package eoan third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898960 Title: package libgnutls30:amd64 3.6.9-5ubuntu1.2 failed to install/upgrade: package libgnutls30:amd64 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1898960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721648] Re: lsmem -v replaced with -V
Same behavior in 20.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721648 Title: lsmem -v replaced with -V To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1721648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] Re: resource timeout not respecting units
This bug is preventing Charmed Kubernetes from working with hacluster on Ubuntu 20.04 (Focal). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881762 Title: resource timeout not respecting units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896384] [NEW] Error upgrading distro
Public bug reported: Trying to update system from 18.04 to 20.04 get error An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu Please use the tool 'ppa-purge' from the ppa-purge package to remove software from a Launchpad PPA and try the upgrade again. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. There are no errors shown in main.log ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Sep 20 14:57:04 2020 InstallationDate: Installed on 2017-01-11 (1348 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to bionic on 2020-09-20 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896384 Title: Error upgrading distro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1896384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895475] [NEW] package linux-image-unsigned-5.4.0-47-generic 5.4.0-47.51~18.04.1 failed to install/upgrade: installed linux-image-unsigned-5.4.0-47-generic package pre-removal script subprocess r
Public bug reported: Was upgrading the system from 18.04 to 20.04. Got a warning that it was trying to remove the running kernel so I followed the recommendation and aborted the removal. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-unsigned-5.4.0-47-generic 5.4.0-47.51~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Sep 13 13:59:58 2020 ErrorMessage: installed linux-image-unsigned-5.4.0-47-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2019-11-02 (315 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: linux-hwe-5.4 Title: package linux-image-unsigned-5.4.0-47-generic 5.4.0-47.51~18.04.1 failed to install/upgrade: installed linux-image-unsigned-5.4.0-47-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-09-13 (0 days ago) ** Affects: linux-hwe-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895475 Title: package linux-image-unsigned-5.4.0-47-generic 5.4.0-47.51~18.04.1 failed to install/upgrade: installed linux-image- unsigned-5.4.0-47-generic package pre-removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1895475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677398] Re: Apparmor prevents using storage pools and hostdev networks
I stumbled upon the same issue but with dir based pools. I have all relevant information posted on a SO question, do you want me to paste them here too? The question is here: https://stackoverflow.com/questions/63767647/virt-aa-helper-doesnt-add- path-for-storage-pool-in-apparmor-generated-rules -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677398 Title: Apparmor prevents using storage pools and hostdev networks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1677398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872984] Re: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic
Hello Kai. After several reboots this morning I was convinced the issue would no longer reproduce. A couple minutes ago I have rebooted the system and the issue reproduced, and I was unable to get the wifi card working even though I have rebooted into Windows and back into Linux several times. I have installed 5.9.0-rc1+ and tried rebooting again into Windows and then Linux, this time successfully connecting to Wifi. I will be updating you if the issue reproduces. Let me know if you need any kind of logs that could help debug this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872984 Title: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872984] Re: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic
Without testing the new kernel (I have 5.4.0-42-generic), I have tried https://bugzilla.kernel.org/show_bug.cgi?id=206411#c11, and then booted to Windows, connected to a network, and powered off windows with the "Fast Boot" option disabled in Power Options. So far, with several reboots, the wifi works correctly. I will be updating you if the issue reappears, but so far this seems to be a good fix for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872984 Title: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872984] Re: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic
@pe83 As of today, I am still experiencing these issues with a fresh install of Ubuntu 20 on a Lenovo Legion Y530-15ICH. The only solution I see fit at this time is a downgrade to 19. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872984 Title: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891259] Re: snap installation with core18 fails at 'Ensure prerequisites for "etcd" are available' in air-gapped environments
** Changed in: charm-etcd Importance: Undecided => Medium ** Changed in: charm-etcd Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891259 Title: snap installation with core18 fails at 'Ensure prerequisites for "etcd" are available' in air-gapped environments To manage notifications about this bug go to: https://bugs.launchpad.net/charm-etcd/+bug/1891259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891137] [NEW] package mysql-server 8.0.21-0ubuntu0.20.04.4 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным
Public bug reported: systematically stuck at Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → /lib/systemd/system/mysql.service. Tried deleting everything mysql related and installing again, won't help. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server 8.0.21-0ubuntu0.20.04.4 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 AptOrdering: libnss3:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 11 06:45:59 2020 ErrorMessage: проблемы зависимостей — оставляем не настроенным InstallationDate: Installed on 2020-07-15 (26 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLVarLibDirListing: ['ibdata1', 'server-cert.pem', 'server-key.pem', 'sys', 'ca.pem', 'performance_schema', 'ibtmp1', 'auto.cnf', 'client-cert.pem', 'ib_logfile1', 'ib_logfile0', '#ib_16384_0.dblwr', 'private_key.pem', 'mysql', 'debian-5.7.flag', 'public_key.pem', 'binlog.02', 'ib_buffer_pool', 'undo_001', 'undo_002', 'mysql.ibd', '#ib_16384_1.dblwr', 'binlog.03', 'client-key.pem', 'binlog.index', '#innodb_temp', 'ca-key.pem', 'binlog.01'] PackageArchitecture: all ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=bd42ab7e-ff0d-49dd-9e6f-92bb78f86f82 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: mysql-8.0 Title: package mysql-server 8.0.21-0ubuntu0.20.04.4 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891137 Title: package mysql-server 8.0.21-0ubuntu0.20.04.4 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1891137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889425] [NEW] new version breaks gnome solitaire
Public bug reported: Updated to 2.40.13-3ubuntu0.1 and now gnome solitaire cards don't display properly. Anyway to install the old version 2.40.13-3 until this is fixed? Thanks, George (this is a Mint 19.3 box) ** Affects: librsvg (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/1889425 Title: new version breaks gnome solitaire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1889425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888172] [NEW] Grub installer package did not install during a fresh ubuntu installation
Public bug reported: Grub installer package did not install during a fresh ubuntu installation ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 20 09:22:05 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888172 Title: Grub installer package did not install during a fresh ubuntu installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1888172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559739] Re: Systemd service script for daemon doesn't use /etc/default/transmission-daemon
Still an issue in 20.04 The $CONFIG_DIR variable is not getting rendered properly but if I hardcode everything in OPTIONS it works properly -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559739 Title: Systemd service script for daemon doesn't use /etc/default /transmission-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1559739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887776] Re: install of 20.04 from live USB with presistance for acer swift 5 i7 laptop dual boot with win10 failed at grub2 uefi
An update to the situation. 1. I reconfirmed the valid checksum of the ISO file used - yep all good. 2. I erased and reformatted the USB used to restore the ISO file to, in the failed install. Note that it was a brand new 32GB device used in the first attempt. 3. Restored the ISO file to this device and did not set it up for persistence. Just a straight bootable Live USB with Ubuntu 20.04. 4. Booted from the USB and went straight to the install stage. Did not 'try' (or road test) the software (which I had previously). 5. Selected the option to wipe the partially completed, failed install. 6. Magic happened, and the install worked successfully, as expected. Dual boot works as expected. 7. I do not know where or what the initial problem may have been. Try Live with persistence? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887776 Title: install of 20.04 from live USB with presistance for acer swift 5 i7 laptop dual boot with win10 failed at grub2 uefi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1887776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887776] [NEW] install of 20.04 from live USB with presistance for acer swift 5 i7 laptop dual boot with win10 failed at grub2 uefi
Public bug reported: debug info sent automatically during failed install. excerpt from syslog: Jul 16 15:29:30 ubuntu /plugininstall.py: Exception during installation: Jul 16 15:29:30 ubuntu /plugininstall.py: Traceback (most recent call last): Jul 16 15:29:30 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1767, in Jul 16 15:29:30 ubuntu /plugininstall.py: install.run() Jul 16 15:29:30 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 62, in wrapper Jul 16 15:29:30 ubuntu /plugininstall.py: func(self) Jul 16 15:29:30 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 233, in run Jul 16 15:29:30 ubuntu /plugininstall.py: self.configure_bootloader() Jul 16 15:29:30 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 929, in configure_bootloader Jul 16 15:29:30 ubuntu /plugininstall.py: raise install_misc.InstallStepError( Jul 16 15:29:30 ubuntu /plugininstall.py: ubiquity.install_misc.InstallStepError: GrubInstaller failed with code 1 Jul 16 15:29:30 ubuntu /plugininstall.py: Jul 16 15:29:41 ubuntu systemd[1]: zsysd.service: Succeeded. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/efi.img ./boot/grub/grub.cfg ./boot/grub/loopback.cfg CasperMD5CheckResult: fail CasperVersion: 1.445 Date: Thu Jul 16 15:30:01 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity persistent --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887776 Title: install of 20.04 from live USB with presistance for acer swift 5 i7 laptop dual boot with win10 failed at grub2 uefi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1887776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887539] Re: [UBUNTU 18.04.4] Charmed Kubernetes local deployment failed for s390x because of etcd error
We're aware of this issue and committed a fix back in March, but it looks like we never released it. See https://bugs.launchpad.net/etcd-snaps/+bug/1869232 ** No longer affects: charm-etcd ** Changed in: etcd-snaps Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887539 Title: [UBUNTU 18.04.4] Charmed Kubernetes local deployment failed for s390x because of etcd error To manage notifications about this bug go to: https://bugs.launchpad.net/etcd-snaps/+bug/1887539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887539] Re: [UBUNTU 18.04.4] Charmed Kubernetes local deployment failed for s390x because of etcd error
** Also affects: charm-etcd Importance: Undecided Status: New ** Also affects: etcd-snaps Importance: Undecided Status: New ** No longer affects: cdk8s -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887539 Title: [UBUNTU 18.04.4] Charmed Kubernetes local deployment failed for s390x because of etcd error To manage notifications about this bug go to: https://bugs.launchpad.net/charm-etcd/+bug/1887539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home
I redeployed the system where this failures was original observed and recreated the issue. Running 'sudo vgck --updatemetadata s5lp8-vg' did work around this bug, when run after the upgrade but prior to the reboot. Here is the vgdisplay output requested by Steve: ubuntu@s5lp8:~$ sudo vgdisplay --- Volume group --- VG Name s5lp8-vg System ID Formatlvm2 Metadata Areas1 Metadata Sequence No 4 VG Access read/write VG Status resizable MAX LV0 Cur LV3 Open LV 3 Max PV0 Cur PV1 Act PV1 VG Size <64.00 GiB PE Size 4.00 MiB Total PE 16383 Alloc PE / Size 16377 / 63.97 GiB Free PE / Size 6 / 24.00 MiB VG UUID 3B7wkv-AIvn-5A7N-pmWB-7y7h-ylkd-jUIfRd ** Changed in: lvm2 (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874381 Title: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881018] Re: sru cloud-init (19.4.33 to 20.2-45) Xenial, Bionic, Eoan and Focal
Solutions QA has tested Cloud-init 20.2-45-g5f7825e2 within our CI testing of Foundation Cloud Builds on Bionic. Artifacts for all test runs are available by following the links on the test plan page here: https://solutions.qa.canonical.com/#/testplans/testplaninstance/06ff68c9-dd19-4470-98d5-a475708b6cc9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881018 Title: sru cloud-init (19.4.33 to 20.2-45) Xenial, Bionic, Eoan and Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881003] Re: sru curtin 2020-05-27 - 20.1-0ubuntu1
Solutions-QA completed validation using python3-curtin_20.1-2-g42a9667f from maas to deploy kubernetes on focal. Deployment artifacts are available here: https://solutions.qa.canonical.com/#/testplans/testplaninstance/5c3995e7-6595-414a-9894-885fb0f54748 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881003 Title: sru curtin 2020-05-27 - 20.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1881003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881003] Re: sru curtin 2020-05-27 - 20.1-0ubuntu1
Solutions-QA has completed our validation using python3-curtin_20.1-2-g42a9667f-0ubuntu1~18.04.1. Deployment artifacts are available here: https://solutions.qa.canonical.com/#/testplans/testplaninstance/5c3995e7-6595-414a-9894-885fb0f54748 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881003 Title: sru curtin 2020-05-27 - 20.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1881003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872984] Re: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic
I am experiencing the same issue on a Lenovo Y530-15ICH. After BIOS update, the issue seemed to no longer occur, however, it has now reappeared. I am currently running BIOS version 8JCN53WW (Dec 2019), the latest. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872984 Title: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879370] Re: Ubuntu dock glitches in auto-hide during setting
Reported upstream https://github.com/micheleg/dash-to-dock/issues/1232 ** Bug watch added: github.com/micheleg/dash-to-dock/issues #1232 https://github.com/micheleg/dash-to-dock/issues/1232 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879370 Title: Ubuntu dock glitches in auto-hide during setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1879370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879370] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1879370/+attachment/5373557/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879370 Title: Ubuntu dock glitches in auto-hide during setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1879370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879370] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1879370/+attachment/5373558/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879370 Title: Ubuntu dock glitches in auto-hide during setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1879370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879370] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1879370/+attachment/5373559/+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/1879370 Title: Ubuntu dock glitches in auto-hide during setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1879370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879370] [NEW] Ubuntu dock glitches in auto-hide during setting
Public bug reported: When "Auto-hide the Dock" is enabled and there is a maximized window, so that the dock is hidden, upon moving the mouse to the bottom of the screen, sometimes the dock glitches and initiates a hide-show animation without stopping instead from showing up until the cursor moves away from the dock. https://youtu.be/Lw2HBmLhd6w This bug was first noticed after upgrading to ubuntu 20.04 from 19.10 Description:Ubuntu 20.04 LTS Release:20.04 gnome-shell-extension-ubuntu-dock: Installed: 67ubuntu20.04.5 Candidate: 67ubuntu20.04.5 Version table: *** 67ubuntu20.04.5 500 500 http://gr.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://gr.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-27 (204 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (9 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected focal ** Tags added: apport-collected focal ** Description changed: When "Auto-hide the Dock" is enabled and there is a maximized window, so that the dock is hidden, upon moving the mouse to the bottom of the screen, sometimes the dock glitches and initiates a hide-show animation without stopping instead from showing up until the cursor moves away from the dock. https://youtu.be/Lw2HBmLhd6w This bug was first noticed after upgrading to ubuntu 20.04 from 19.10 Description: Ubuntu 20.04 LTS Release: 20.04 gnome-shell-extension-ubuntu-dock: Installed: 67ubuntu20.04.5 Candidate: 67ubuntu20.04.5 Version table: *** 67ubuntu20.04.5 500 500 http://gr.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://gr.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-10-27 (204 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 + PackageArchitecture: all + ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 + Tags: focal + Uname: Linux 5.4.0-29-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-05-09 (9 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879370 Title: Ubuntu dock glitches in auto-hide during setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1879370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875252] Re: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers
@Rajasekharan N (rajasekharan, thanks for letting me know. Good thing I haven’t looked for updates this week before I read your comment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875252 Title: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875252] Re: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers
That patch fixed the problem for me as well! Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875252 Title: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
