[Bug 2083988] Re: Cannot use virtiofs on Ubuntu 22.04
That was a good idea to check qemu-system-common to see if it had been altered but both dpkg -V and debsums report the files in the package have not been altered. The package is coming from the standard places: apt-cache madison qemu-system-common qemu-system-common | 1:6.2+dfsg-2ubuntu6.22 | http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages qemu-system-common | 1:6.2+dfsg-2ubuntu6.22 | http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages qemu-system-common | 1:6.2+dfsg-2ubuntu6 | http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages qemu | 1:6.2+dfsg-2ubuntu6 | http://archive.ubuntu.com/ubuntu jammy/main Sources But... this has nothing to do with it and I'm not sure what does. I rebooted the laptop and cannot reproduce the issue any more with any of the VMs that were not working yesterday. My suspicions lay with perhaps stale sockets left over since virtiosfd appears to have one per pid: # lsof -c virtiofsd | grep -i sock lsof: WARNING: can't stat() fuse.portal file system /run/user/1000/doc Output information may be incomplete. virtiofsd 4292 root3u unix 0x996fb37ccc80 0t067488 /var/lib/libvirt/qemu/domain-1-ubuntu22.04/fs0-fs.sock type=STREAM virtiofsd 4323 root3u unix 0x996fb37ccc80 0t067488 /var/lib/libvirt/qemu/domain-1-ubuntu22.04/fs0-fs.sock type=STREAM virtiofsd 4567 root3u unix 0x996f18858cc0 0t074528 /var/lib/libvirt/qemu/domain-2-sle15sp6/fs0-fs.sock type=STREAM virtiofsd 4587 root3u unix 0x996f18858cc0 0t074528 /var/lib/libvirt/qemu/domain-2-sle15sp6/fs0-fs.sock type=STREAM I am typically quite rude to my VMs and will often just destroy them instead of shutting them down from the guest instance. Perhaps some of that activity caused things to go out of sync, only working after sockets were properly cleaned up by a host shutdown and reboot.Oh well. I'll close this and much thanks for allowing me to bounce ideas off this group and for the insight into how things are supposed to work. ** Changed in: qemu (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083988 Title: Cannot use virtiofs on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2083988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083988] Re: Cannot use virtiofs on Ubuntu 22.04
Ah, tested with uvt and created a jammy VM. After changing the memory
to shared and adding the shared directory, I get the same issue... so
again pointing to something (subtle?) with libvirt:
Error starting domain: internal error: process exited while connecting to
monitor: 2024-10-09T22:43:58.738014Z qemu-system-x86_64: -device
vhost-user-fs-pci,id=fs0,chardev=chr-vu-fs0,tag=mydir,bus=pci.7,addr=0x0:
Failed to read msg header. Read 0 instead of 12. Original request 36.
2024-10-09T22:43:58.738071Z qemu-system-x86_64: -device
vhost-user-fs-pci,id=fs0,chardev=chr-vu-fs0,tag=mydir,bus=pci.7,addr=0x0:
vhost_backend_init failed: Protocol error
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57,
in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1384, in
startup
self._backend.create()
File "/usr/lib/python3/dist-packages/libvirt.py", line 1353, in create
raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: internal error: process exited while connecting to
monitor: 2024-10-09T22:43:58.738014Z qemu-system-x86_64: -device
vhost-user-fs-pci,id=fs0,chardev=chr-vu-fs0,tag=mydir,bus=pci.7,addr=0x0:
Failed to read msg header. Read 0 instead of 12. Original request 36.
2024-10-09T22:43:58.738071Z qemu-system-x86_64: -device
vhost-user-fs-pci,id=fs0,chardev=chr-vu-fs0,tag=mydir,bus=pci.7,addr=0x0:
vhost_backend_init failed: Protocol error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083988
Title:
Cannot use virtiofs on Ubuntu 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2083988/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083988] Re: Cannot use virtiofs on Ubuntu 22.04
Ok, so I have isolated this to some libvirt quirk or config. I followed this: https://virtio-fs.gitlab.io/howto-qemu.html Started virtiofsd manually and then the vm through qemu (running as root on the host): # export TESTDIR=/tmp # /usr/lib/qemu/virtiofsd --socket-path=/tmp/vhostqemu -o source=$TESTDIR -o cache=always & # qemu-system-x86_64 -M pc -cpu host --enable-kvm -smp 2 \ -m 4G -object memory-backend-file,id=mem,size=4G,mem-path=/dev/shm,share=on -numa node,memdev=mem \ -chardev socket,id=char0,path=/tmp/vhostqemu -device vhost-user-fs-pci,queue-size=1024,chardev=char0,tag=myfs \ -chardev stdio,mux=on,id=mon -mon chardev=mon,mode=readline -device virtio-serial-pci -device virtconsole,chardev=mon -vga none -display none \ -drive if=virtio,file=/var/lib/libvirt/images/ubuntu22.04.qcow2 We can see that the vm boots: # /usr/lib/qemu/virtiofsd --socket-path=/tmp/vhostqemu -o source=$TESTDIR -o cache=always & [1] 17313 root@jammy-laptop:/var/log/libvirt/qemu# virtio_session_mount: Waiting for vhost-user socket connection... root@jammy-laptop:/var/log/libvirt/qemu# qemu-system-x86_64 -M pc -cpu host --enable-kvm -smp 2 -m 4G -object memory-backend-file,id=mem,size=4G,mem-path=/dev/shm,share=on -numa node,memdev=mem -chardev socket,id=char0,path=/tmp/vhostqemu -device vhost-user-fs-pci,queue-size=1024,chardev=char0,tag=myfs -chardev stdio,mux=on,id=mon -mon chardev=mon,mode=readline -device virtio-serial-pci -device virtconsole,chardev=mon -vga none -display none -drive if=virtio,file=/var/lib/libvirt/images/ubuntu22.04.qcow2 virtio_session_mount: Received vhost-user socket connection virtio_loop: Entry fv_queue_set_started: qidx=0 started=1 fv_queue_set_started: qidx=1 started=1 fv_queue_thread: Start for queue 0 kick_fd 9 fv_queue_thread: Start for queue 1 kick_fd 12 Ubuntu 22.04.4 LTS ubuntu-server hvc0 ubuntu-server login: I was able to login and mount the filesystem with the command: sudo mount -t virtiofs myfs /mnt/tmp Shutting it down gives me the sequence of messages from virtiosfd: # sudo shutdown -h now fv_queue_set_started: qidx=0 started=0 fv_queue_thread: kill event on queue 0 - quitting fv_remove_watch: TODO! fd=9 fv_queue_set_started: qidx=1 started=0 fv_queue_thread: kill event on queue 1 - quitting fv_remove_watch: TODO! fd=12 virtio_loop: Unexpected poll revents 11 virtio_loop: Exit [1]+ Done/usr/lib/qemu/virtiofsd --socket-path=/tmp/vhostqemu -o source=$TESTDIR -o cache=always So this is something to do with how libvirt spawns virtiosfd I think... I'm not sure I understand that mechanism. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083988 Title: Cannot use virtiofs on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2083988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083988] Re: Cannot use virtiofs on Ubuntu 22.04
One thing that might make a difference is that I run NetworkManager and not netplan on this Jammy laptop. That seems to be necessary to deal with the company's VPN. Looking at the startup sequence, I wonder if I am failing where virtiosfd is spawned. From what I read, that needs to be run as root. We see that in /var/log/libvirt/qemu/ we get two logs when the guest is attempting to start: # ll /var/log/libvirt/qemu/ub* -rw--- 1 root root 832 Oct 9 11:41 /var/log/libvirt/qemu/ubuntu22.04-fs0-virtiofsd.log -rw--- 1 root root 27696 Oct 9 11:41 /var/log/libvirt/qemu/ubuntu22.04.log No timestamps so I can't tell exactly which is logged first. That would be a nice thing to have. Looking at syslog on the host, I think we get some valid timestamps corresponding to those logs: Oct 9 11:41:02 jammy-laptop dbus-daemon[1605]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.249' (uid=1000 pid=11068 comm="/usr/bin/python3 /usr/bin/virt-manager " label="unconfined") Oct 9 11:41:02 jammy-laptop systemd[1]: Starting Hostname Service... Oct 9 11:41:02 jammy-laptop dbus-daemon[1605]: [system] Successfully activated service 'org.freedesktop.hostname1' Oct 9 11:41:02 jammy-laptop systemd[1]: Started Hostname Service. Oct 9 11:41:15 jammy-laptop kernel: [11926.090059] audit: type=1400 audit(1728499275.656:306): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-7c3e5649-d58e-44e3-9c11-c2ceb3c21185" pid=11706 comm="apparmor_parser" Oct 9 11:41:15 jammy-laptop kernel: [11926.174003] audit: type=1400 audit(1728499275.740:307): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-7c3e5649-d58e-44e3-9c11-c2ceb3c21185" pid=11709 comm="apparmor_parser" Oct 9 11:41:15 jammy-laptop kernel: [11926.258421] audit: type=1400 audit(1728499275.824:308): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-7c3e5649-d58e-44e3-9c11-c2ceb3c21185" pid=11713 comm="apparmor_parser" Oct 9 11:41:15 jammy-laptop kernel: [11926.348758] audit: type=1400 audit(1728499275.912:309): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-7c3e5649-d58e-44e3-9c11-c2ceb3c21185" pid=11717 comm="apparmor_parser" Oct 9 11:41:15 jammy-laptop kernel: [11926.428053] audit: type=1400 audit(1728499275.992:310): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-7c3e5649-d58e-44e3-9c11-c2ceb3c21185" pid=11721 comm="apparmor_parser" Oct 9 11:41:16 jammy-laptop kernel: [11926.508897] audit: type=1400 audit(1728499276.072:311): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-7c3e5649-d58e-44e3-9c11-c2ceb3c21185" pid=11726 comm="apparmor_parser" Oct 9 11:41:16 jammy-laptop kernel: [11926.514785] audit: type=1400 audit(1728499276.080:312): apparmor="ALLOWED" operation="exec" profile="libvirtd" name="/usr/lib/qemu/virtiofsd" pid=11729 comm="rpc-libvirtd" requested_mask="x" denied_mask="x" fsuid=0 ouid=0 target="libvirtd//null-/usr/lib/qemu/virtiofsd" Oct 9 11:41:16 jammy-laptop kernel: [11926.515211] audit: type=1400 audit(1728499276.080:313): apparmor="ALLOWED" operation="file_inherit" profile="libvirtd//null-/usr/lib/qemu/virtiofsd" name="/dev/null" pid=11729 comm="virtiofsd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 Oct 9 11:41:16 jammy-laptop kernel: [11926.515224] audit: type=1400 audit(1728499276.080:314): apparmor="ALLOWED" operation="file_inherit" profile="libvirtd//null-/usr/lib/qemu/virtiofsd" name="/run/libvirt/qemu/8-ubuntu22.04-fs0-fs.pid" pid=11729 comm="virtiofsd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 Oct 9 11:41:16 jammy-laptop kernel: [11926.515230] audit: type=1400 audit(1728499276.080:315): apparmor="ALLOWED" operation="file_mmap" profile="libvirtd//null-/usr/lib/qemu/virtiofsd" name="/usr/lib/qemu/virtiofsd" pid=11729 comm="virtiofsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Oct 9 11:41:16 jammy-laptop NetworkManager[1607]: [1728499276.0865] manager: (vnet10): new Tun device (/org/freedesktop/NetworkManager/Devices/24) Oct 9 11:41:16 jammy-laptop systemd-udevd[11734]: Using default interface naming scheme 'v249'. Oct 9 11:41:16 jammy-laptop kernel: [11926.518751] virbr0: port 1(vnet10) entered blocking state Oct 9 11:41:16 jammy-laptop kernel: [11926.518753] virbr0: port 1(vnet10) entered disabled state Oct 9 11:41:16 jammy-laptop kernel: [11926.518811] device vnet10 entered promiscuous mode Oct 9 11:41:16 jammy-laptop kernel: [11926.518967] virbr0: port 1(vnet10) entered blocking state Oct 9 11:41:16 jammy-laptop kernel: [11926.518968] virbr0: port 1(vnet10) entered listening state Oct 9 11:41:16 jammy-laptop NetworkManager[1607]: [1728499276.0936] device (vnet10): state change: unman
[Bug 2083988] Re: Cannot use virtiofs on Ubuntu 22.04
I tried with Noble (24.04) and it worked fine the first time with an Ubuntu 24.04 guest. On the laptop with Jammy (22.04), I can reproduce the issue with any guest I think.I reproduced it with an Ubuntu 22.04 guest, a SLES15 SP6 guest and a Windows 10 guest. That suggests that there is something off about my host config, but I am not sure what. I focused on the Ubuntu 22.04 guest for simplicity.Thinking back, I dimly recall that I was never able to get this to work on Jammy. I've attached the xml for the guest since it is long. It was created with virt-manager. ** Attachment added: "ubuntu22.04.xml" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2083988/+attachment/5826594/+files/ubuntu22.04.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083988 Title: Cannot use virtiofs on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2083988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083988] [NEW] Cannot use virtiofs on Ubuntu 22.04
Public bug reported:
I run Kubuntu 22.04 on my laptop, secure boot enabled. First time
trying to use shared filesystems between host and guest.
Created an Ubuntu 22.04 VM for testing with virt-manager. Altered the
VM to enable shared memory:
And enabled /tmp from host to be shared (as a test):
Attempting to start the VM fails:
Error starting domain: internal error: process exited while connecting to
monitor: 2024-10-08T23:30:00.030286Z qemu-system-x86_64: -device
vhost-user-fs-pci,id=fs0,chardev=chr-vu-fs0,tag=hosttmp,bus=pci.8,addr=0x0:
Failed to read msg header. Read 0 instead of 12. Original request 36.
2024-10-08T23:30:00.030343Z qemu-system-x86_64: -device
vhost-user-fs-pci,id=fs0,chardev=chr-vu-fs0,tag=hosttmp,bus=pci.8,addr=0x0:
vhost_backend_init failed: Protocol error
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57,
in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1384, in
startup
self._backend.create()
File "/usr/lib/python3/dist-packages/libvirt.py", line 1353, in create
raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: internal error: process exited while connecting to
monitor: 2024-10-08T23:30:00.030286Z qemu-system-x86_64: -device
vhost-user-fs-pci,id=fs0,chardev=chr-vu-fs0,tag=hosttmp,bus=pci.8,addr=0x0:
Failed to read msg header. Read 0 instead of 12. Original request 36.
2024-10-08T23:30:00.030343Z qemu-system-x86_64: -device
vhost-user-fs-pci,id=fs0,chardev=chr-vu-fs0,tag=hosttmp,bus=pci.8,addr=0x0:
vhost_backend_init failed: Protocol error
In /var/log/libvirt/qemu/ubuntu22.04-fs0-virtiofsd.log I have:
virtio_session_mount: Waiting for vhost-user socket connection...
virtio_session_mount: Received vhost-user socket connection
virtio_loop: Entry
fv_panic: libvhost-user: Invalid slave_req_fd message (0 fd's)
virtio_session_mount: Waiting for vhost-user socket connection...
virtio_session_mount: Received vhost-user socket connection
virtio_loop: Entry
fv_panic: libvhost-user: Invalid slave_req_fd message (0 fd's)
Everything is up-to-date for 22.04.
One google hit for the fv_panic is at Red Hat:
https://bugzilla.redhat.com/show_bug.cgi?id=1993825
One upstream seems to be:
https://github.com/torokernel/torokernel/issues/428
And a Debian report: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1017394
It isn't clear to me if this is a configuration issue or a bug, but reading the
above it sounds like it might be a limitation of the virtiofs implementation.
I expected sharing filesystem between guest and host would work.
lsb_release -rd
Description:Ubuntu 22.04.5 LTS
Release:22.04
# apt-cache policy qemu-system-common
qemu-system-common:
Installed: 1:6.2+dfsg-2ubuntu6.22
Candidate: 1:6.2+dfsg-2ubuntu6.22
Version table:
*** 1:6.2+dfsg-2ubuntu6.22 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
100 /var/lib/dpkg/status
1:6.2+dfsg-2ubuntu6 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
# dpkg -l | grep qemu
ii ipxe-qemu
1.21.1+git-20220113.fbbdc3926-0ubuntu1
all PXE boot firmware - ROM images for qemu
ii ipxe-qemu-256k-compat-efi-roms
1.0.0+git-20150424.a25a16d-0ubuntu4
all PXE boot firmware - Compat EFI ROM images for qemu
ii libvirt-daemon-driver-qemu8.0.0-1ubuntu7.10
amd64Virtualization
daemon QEMU connection driver
ii qemu-block-extra 1:6.2+dfsg-2ubuntu6.22
amd64extra block
backend modules for qemu-system and qemu-utils
ii qemu-efi 2022.02-3ubuntu0.22.04.2
all transitional
dummy package
ii qemu-efi-aarch64 2022.02-3ubuntu0.22.04.2
all UEFI firmware
for 64-bit ARM virtual machines
ii qemu-efi-arm 2022.02-3ubuntu0.22.04.2
all UEFI firmware
for 32-bit ARM virtual machines
rc qemu-kvm 1:4.2-3ubuntu6.23
amd64
[Bug 2083433] [NEW] A newer version of the eric-ide package is available
Public bug reported: A newer version of the eric-ide package is available at PyPI. Installed: 23.2 Available: 24.10 Please ask the Debian package maintainer to package it. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: eric 23.2+ds1-2ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Oct 1 12:08:01 2024 InstallationDate: Installed on 2024-05-03 (151 days ago) InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240425.1) PackageArchitecture: all SourcePackage: eric UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eric (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083433 Title: A newer version of the eric-ide package is available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eric/+bug/2083433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080652] [NEW] Updates Available : Cannot Download / Install updates
Public bug reported: MSG reads: No network connection available: Cannot download packages whilst offline. UbuntuStudio 22.04.5 LTS NOTE: I am online typing this message regarding the Error. Running in Terminal Window "full-upgrade" is working. So, I am able to update & upgrade. But I get this ... Processing triggers for initramfs-tools (0.140ubuntu13.4) ... update-initramfs: Generating /boot/initrd.img-6.8.0-44-lowlatency W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega10_cap.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/psp_14_0_0_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/psp_14_0_0_toc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_6_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_6_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_sjt_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_sjt_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_9_4_3_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_9_4_3_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_imu.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_rlc_1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/sdma_4_4_2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/sdma_6_1_0.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_mes1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_5_0_mes_2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vcn_4_0_5.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vcn_4_0_3.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vpe_6_1_0.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/smu_13_0_6.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/smu_14_0_2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/dcn_3_5_1_dmcub.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/dcn_3_5_dmcub.bin for module amdgpu ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 ProcVersionSignature: Ubuntu 6.8.0-40.40.1~22.04.1-lowlatency 6.8.12 Uname: Linux 6.8.0-40-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Sep 13 08:35:46 2024 InstallationDate: Installed on 2024-05-24 (111 days ago) InstallationMedia: Ubuntu-Studio 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080652 Title: Updates Available : Cannot Download / Install updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076221] Re: [SRU] Add fibocom mbim service to send at command
Hi Steve, Sorry for the confusion. I’m Rick from the Fibocom R&D team, and I’d like to clarify the matter. The “service” mentioned here refers to an internal service within libmbim, not to a “.service” file managed by systemd. Libmbim defines various MBIM services according to the MBIM specification, such as the basic connect service, basic connect extension service, etc. We recommend that the HP Ubuntu team request Canonical to merge this patch into the OEM OS image. This patch is both mandatory and necessary for HP to utilize the functions we provide for executing firmware updates or firmware switch processes. Please kindly assist in reviewing and merging it. If there are any issues, please let me know. Best regards, Rick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076221 Title: [SRU] Add fibocom mbim service to send at command To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2076221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078934] [NEW] Clementine Icon doesn't show in sidebar
Public bug reported: Ubuntu: 24.04.1 LTS $ apt-cache policy clementine clementine: Installed: 1.4.0~rc1+git867-g9ef681b0e+dfsg-1ubuntu4 Candidate: 1.4.0~rc1+git867-g9ef681b0e+dfsg-1ubuntu4 Version table: *** 1.4.0~rc1+git867-g9ef681b0e+dfsg-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages 100 /var/lib/dpkg/status I expected the clementine icon to appear in the sidebar. I get an icon that is a grey square with a gear inside. I get the same result with IntelliJ but that was installed manually, not with apt-get or snap. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: clementine 1.4.0~rc1+git867-g9ef681b0e+dfsg-1ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 4 08:20:52 2024 ExecutablePath: /usr/bin/clementine InstallationDate: Installed on 2024-01-31 (217 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: clementine UpgradeStatus: Upgraded to noble on 2024-09-01 (3 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-07-22T10:59:07 ** Affects: clementine (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Attachment added: "Picture of sidebar icons" https://bugs.launchpad.net/bugs/2078934/+attachment/5813322/+files/Screenshot%20from%202024-09-04%2008-33-16.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078934 Title: Clementine Icon doesn't show in sidebar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clementine/+bug/2078934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077266] Re: Blank screen hang on bootup with Ryzen 7840U iGPU with Noble
If I look here: *'/boot/config-6.10.0-15-generic' * "CONFIG_DRM_RADEON=m # CONFIG_DRM_RADEON_USERPTR is not set CONFIG_DRM_AMDGPU=m CONFIG_DRM_AMDGPU_SI=y CONFIG_DRM_AMDGPU_CIK=y CONFIG_DRM_AMDGPU_USERPTR=y # CONFIG_DRM_AMDGPU_WERROR is not set" Or */boot/config-6.8.0-31-generic' * Is the same as above -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077266 Title: Blank screen hang on bootup with Ryzen 7840U iGPU with Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073041] Re: installed flatpak qbittorrent not saving settings
Now fixed with: "apt policy apparmor apparmor-utils apparmor: Installed: 4.0.1really4.0.1-0ubuntu2 Candidate: 4.0.1really4.0.1-0ubuntu2 Version table: *** 4.0.1really4.0.1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu oracular/main amd64 Packages 100 /var/lib/dpkg/status apparmor-utils: Installed: 4.0.1really4.0.1-0ubuntu2 Candidate: 4.0.1really4.0.1-0ubuntu2 Version table: *** 4.0.1really4.0.1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu oracular/main amd64 Packages 100 /var/lib/dpkg/status" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073041 Title: installed flatpak qbittorrent not saving settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2073041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2018539] Re: File selector extremely slow
I'm also encountering this error. It makes uploading any more than two files to a server a torturous workflow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2018539 Title: File selector extremely slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2018539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075355] [NEW] clicked on "More Search Tools" in dolphin, selected Catfish, received ERROR - could not open appstream://catfish
Public bug reported: Top of ERROR Pop-up shows "Error - Discover", and I clicked on the button "Report this issue". This is not a security issue. Just want to use another Search Tool as Dolphin Search can't find any file. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dolphin 4:21.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-44.44.1~22.04.1-lowlatency 6.5.13 Uname: Linux 6.5.0-44-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jul 31 12:50:03 2024 InstallationDate: Installed on 2024-05-24 (67 days ago) InstallationMedia: Ubuntu-Studio 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216) SourcePackage: dolphin UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dolphin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075355 Title: clicked on "More Search Tools" in dolphin, selected Catfish, received ERROR - could not open appstream://catfish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/2075355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046624] Re: apparmor breaks surfshark vpn
*** This bug is a duplicate of bug 2046844 *** https://bugs.launchpad.net/bugs/2046844 Hi John sorry late reply, been very busy, but all is good on my end: "sudo dmesg | grep -e DENIED -e audit [0.230954] audit: initializing netlink subsys (disabled) [0.230967] audit: type=2000 audit(1721752126.155:1): state=initialized audit_enabled=0 res=1 [8.814531] systemd-journald[848]: Collecting audit messages is disabled. [ 13.477436] audit: type=1400 audit(1721752139.268:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="busybox" pid=1499 comm="apparmor_parser" [ 13.477442] audit: type=1400 audit(1721752139.268:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="cam" pid=1501 comm="apparmor_parser" [ 13.477445] audit: type=1400 audit(1721752139.268:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="balena-etcher" pid=1495 comm="apparmor_parser" [ 13.477447] audit: type=1400 audit(1721752139.268:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="QtWebEngineProcess" pid=1494 comm="apparmor_parser" [ 13.477449] audit: type=1400 audit(1721752139.269:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="ch-checkns" pid=1502 comm="apparmor_parser" [ 13.477572] audit: type=1400 audit(1721752139.269:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="1password" pid=1491 comm="apparmor_parser" [ 13.477576] audit: type=1400 audit(1721752139.269:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name=4D6F6E676F444220436F6D70617373 pid=1493 comm="apparmor_parser" [ 13.477579] audit: type=1400 audit(1721752139.269:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="buildah" pid=1498 comm="apparmor_parser" [ 13.477593] audit: type=1400 audit(1721752139.269:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="Discord" pid=1492 comm="apparmor_parser" [ 13.477764] audit: type=1400 audit(1721752139.269:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="brave" pid=1497 comm="apparmor_parser" " And "sudo aa-status|grep surfshark surfshark /opt/Surfshark/surfshark (133781) surfshark /opt/Surfshark/surfshark (133784) surfshark /opt/Surfshark/surfshark (133785) surfshark /opt/Surfshark/surfshark (133787) surfshark /opt/Surfshark/chrome_crashpad_handler (133819) surfshark /opt/Surfshark/surfshark (133851) surfshark /opt/Surfshark/surfshark (133891) surfshark " And "apt policy apparmor apparmor: Installed: 4.0.1-0ubuntu1 Candidate: 4.0.1-0ubuntu1 Version table: *** 4.0.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu oracular/main amd64 Packages 100 /var/lib/dpkg/status " All this was good on Noble as well -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046624 Title: apparmor breaks surfshark vpn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073041] Re: installed flatpak qbittorrent not saving settings
Most likely related to this bug: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2072811 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073041 Title: installed flatpak qbittorrent not saving settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2073041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073041] Re: installed flatpak qbittorrent not saving settings
Forgot to mention, this brought to my attention by another user here: https://ubuntuforums.org/showthread.php?t=2499125&p=14197290#post14197290 We both have the same outcome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073041 Title: installed flatpak qbittorrent not saving settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2073041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073041] [NEW] installed flatpak qbittorrent not saving settings
Public bug reported: Some Flatpaks are not savings settings/preferences right now qbittorrent is a good example ie set settings/preferences for that session, then close. Next run It will not save them, and to add to that it sets the .deb install back to default settings, Only after I remove the flatpak version did the .Deb version return to function as expected. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: flatpak 1.14.8-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Jul 13 15:11:16 2024 InstallationDate: Installed on 2024-05-06 (68 days ago) InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424.2) SourcePackage: flatpak UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: flatpak (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073041 Title: installed flatpak qbittorrent not saving settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2073041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071518] Re: Kernel 5.15.0.113.123
me too. bug reported minutes after your post, 112 was similarly affected. I am now running 107. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071518 Title: Kernel 5.15.0.113.123 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2071518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071543] [NEW] failure to boot
Public bug reported: Latest 5,15 ... 113.123 112 was removed back to 107 as it failed to boot. 113 also fails to boot. rick@rick-HP-Pavilion-Notebook:~$ cat /proc/version_signature > version.log rick@rick-HP-Pavilion-Notebook:~$ sudo lspci -vnvn > lspci-vnvn.log [sudo] password for rick: pcilib: sysfs_read_vpd: read failed: No such device rick@rick-HP-Pavilion-Notebook:~$ ^C rick@rick-HP-Pavilion-Notebook:~$ my system data whilst using 112 recovery mode System: Kernel: 5.15.0-112-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy Machine: Type: Laptop System: HP product: HP Pavilion Notebook v: N/A serial: Chassis: type: 10 serial: Mobo: HP model: 80B5 v: 81.32 serial: UEFI: American Megatrends v: F.45 date: 04/28/2017 Battery: ID-1: BAT0 charge: 37.8 Wh (100.0%) condition: 37.8/37.8 Wh (100.0%) volts: 16.6 min: 14.6 model: Hewlett-Packard Primary type: Li-ion serial: N/A status: Full cycles: 340 CPU: Info: quad core model: AMD A10 Extreme Edition Radeon R8 4C+8G bits: 64 type: MT MCP smt: enabled arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB Speed (MHz): avg: 1397 min/max: 1400/2000 boost: enabled cores: 1: 1397 2: 1397 3: 1397 4: 1397 bogomips: 15970 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Hewlett-Packard driver: N/A bus-ID: 00:01.0 chip-ID: 1002:9874 class-ID: 0300 Device-2: AMD Topaz XT [Radeon R7 M260/M265 / M340/M360 M440/M445 530/535 620/625 Mobile] vendor: Hewlett-Packard driver: N/A pcie: speed: 2.5 GT/s lanes: 8 bus-ID: 04:00.0 chip-ID: 1002:6900 class-ID: 0380 Device-3: Cheng Uei Precision Industry (Foxlink) HP Truevision HD type: USB driver: uvcvideo bus-ID: 2-1:8 chip-ID: 05c8:0379 class-ID: 0e02 Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: ati,vesa unloaded: fbdev,modesetting,radeon gpu: N/A display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.0x11.3") s-diag: 583mm (23") Monitor-1: default res: 1920x1080 hz: 77 size: N/A OpenGL: renderer: llvmpipe (LLVM 15.0.7 256 bits) v: 4.5 Mesa 23.2.1-1ubuntu3.1~22.04.2 direct render: Yes Audio: Device-1: AMD Kabini HDMI/DP Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 00:01.1 chip-ID: 1002:9840 class-ID: 0403 Device-2: AMD Family 15h Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 00:09.2 chip-ID: 1022:157a class-ID: 0403 Sound Server-1: ALSA v: k5.15.0-112-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8136 class-ID: 0200 IF: eno1 state: down mac: Device-2: Broadcom BCM43142 802.11b/g/n vendor: Hewlett-Packard driver: bcma-pci-bridge v: N/A pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 14e4:4365 class-ID: 0280 Device-3: TP-Link TL-WN823N v2/v3 [Realtek RTL8192EU] type: USB driver: rtl8xxxu bus-ID: 2-3:4 chip-ID: 2357:0109 class-ID: serial: I am not too savvy with linux. My video card is not supported after the upgrade to 107, whick I am running now ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071543 Title: failure to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2071543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068018] [NEW] Dist upgrade from Ubuntu 23.10 to 24.04 does not work
Public bug reported: A popup window states "Could not calculate the upgrade. An unresolvable problem occured while calculating the upgrade. If none of this applies, then please report this bug using ... * It does not matter whether I am using the UI dist-upgrade or command line tool. * First time I ran it the error message included stuff about ppa. I have removed both the packages of external ppa's and the sources. * I did restart the computer * Kubuntu 23.10 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Jun 4 13:10:38 2024 InstallationDate: Installed on 2023-11-24 (193 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2024-06-04 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068018 Title: Dist upgrade from Ubuntu 23.10 to 24.04 does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2068018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066457] Re: Ubuntu 24.10 Oracular accented vowels does not work in Italian keyboard
I don't use it much but since corradoventu went to the trouble it affects me as well. "PRETTY_NAME="Ubuntu Oracular Oriole (development branch)" NAME="Ubuntu" VERSION_ID="24.10" VERSION="24.10 (Oracular Oriole)" VERSION_CODENAME=oracular ID=ubuntu ID_LIKE=debian 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"; UBUNTU_CODENAME=oracular LOGO=ubuntu-logo " -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066457 Title: Ubuntu 24.10 Oracular accented vowels does not work in Italian keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2066457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064869] Re: systemd bluetooth not honoring stop service
This will disable it for the current session: **" rfkill list 0: ideapad_wlan: Wireless LAN Soft blocked: yes Hard blocked: no 1: ideapad_bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no 3: hci1: Bluetooth Soft blocked: no Hard blocked: no 4: phy0: Wireless LAN Soft blocked: yes Hard blocked: no ┌───> │~ └─> rfkill block 1 2 (wrapper-2.0:231189): LIBDBUSMENU-GLIB-WARNING **: 09:57:44.532: Unable to replace properties on 0: Error getting properties for ID (wrapper-2.0:231189): LIBDBUSMENU-GLIB-WARNING **: 09:57:44.633: Unable to replace properties on 0: Error getting properties for ID " A check with rfkill *" rfkill list all 0: ideapad_wlan: Wireless LAN Soft blocked: yes Hard blocked: no 1: ideapad_bluetooth: Bluetooth Soft blocked: yes Hard blocked: no 2: hci0: Bluetooth Soft blocked: yes Hard blocked: no 3: hci1: Bluetooth Soft blocked: no Hard blocked: no 4: phy0: Wireless LAN Soft blocked: yes Hard blocked: no "* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064869 Title: systemd bluetooth not honoring stop service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2064869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064869] Re: systemd bluetooth not honoring stop service
I forgot this that "might" help. **" systemctl stop bluetooth.service ┌───> │~ └─> (wrapper-2.0:231189): LIBDBUSMENU-GLIB-WARNING **: 09:49:15.181: Unable to replace properties on 0: Error getting properties for ID (wrapper-2.0:231189): LIBDBUSMENU-GLIB-WARNING **: 09:49:16.283: Unable to replace properties on 0: Error getting properties for ID (wrapper-2.0:231189): LIBDBUSMENU-GLIB-WARNING **: 09:49:16.385: Unable to replace properties on 0: Error getting properties for ID (wrapper-2.0:231189): LIBDBUSMENU-GLIB-WARNING **: 09:49:16.888: Unable to replace properties on 0: Error getting properties for ID (wrapper-2.0:231189): LIBDBUSMENU-GLIB-WARNING **: 09:49:18.042: Unable to replace properties on 0: Error getting properties for ID (wrapper-2.0:231189): LIBDBUSMENU-GLIB-WARNING **: 09:49:18.243: Unable to replace properties on 0: Error getting properties for ID (wrapper-2.0:231189): LIBDBUSMENU-GLIB-WARNING **: 09:49:18.444: Unable to replace properties on 0: Error getting properties for ID (wrapper-2.0:231189): LIBDBUSMENU-GLIB-WARNING **: 09:49:18.545: Unable to replace properties on 0: Error getting properties for ID ┌───> │~ └─> systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset> Active: active (running) since Sun 2024-05-05 09:49:15 MDT; 13s ago Docs: man:bluetoothd(8) Main PID: 247580 (bluetoothd) Status: "Running" Tasks: 1 (limit: 16490) Memory: 1.1M (peak: 1.3M) CPU: 45ms CGroup: /system.slice/bluetooth.service └─247580 /usr/libexec/bluetooth/bluetoothd May 05 09:49:15 me-Legion-5-zfs bluetoothd[247580]: Endpoint registered: sender> May 05 09:49:15 me-Legion-5-zfs bluetoothd[247580]: Endpoint registered: sender> May 05 09:49:15 me-Legion-5-zfs bluetoothd[247580]: Endpoint registered: sender> May 05 09:49:15 me-Legion-5-zfs bluetoothd[247580]: Endpoint registered: sender> May 05 09:49:15 me-Legion-5-zfs bluetoothd[247580]: Endpoint registered: sender> May 05 09:49:15 me-Legion-5-zfs bluetoothd[247580]: Endpoint registered: sender> May 05 09:49:15 me-Legion-5-zfs bluetoothd[247580]: Failed to add UUID: Failed > May 05 09:49:15 me-Legion-5-zfs bluetoothd[247580]: Failed to add UUID: Failed > May 05 09:49:15 me-Legion-5-zfs bluetoothd[247580]: Failed to add UUID: Failed > May 05 09:49:15 me-Legion-5-zfs bluetoothd[247580]: Failed to add UUID: Faile" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064869 Title: systemd bluetooth not honoring stop service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2064869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064869] [NEW] systemd bluetooth not honoring stop service
Public bug reported: systemd stop bluetooth.service no longer stops bluetooth. And systemd disable bluetooth.service, restarts after reboot "systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset> Active: active (running) since Sun 2024-05-05 08:20:37 MDT; 1h 22min ago Docs: man:bluetoothd(8) Main PID: 140617 (bluetoothd) Status: "Running" Tasks: 1 (limit: 16490) Memory: 1.6M (peak: 1.9M) CPU: 57ms CGroup: /system.slice/bluetooth.service └─140617 /usr/libexec/bluetooth/bluetoothd May 05 08:20:37 me-Legion-5-zfs bluetoothd[140617]: Endpoint registered: sender> May 05 08:20:37 me-Legion-5-zfs bluetoothd[140617]: Endpoint registered: sender> May 05 08:20:37 me-Legion-5-zfs bluetoothd[140617]: Endpoint registered: sender> May 05 08:20:37 me-Legion-5-zfs bluetoothd[140617]: Endpoint registered: sender> May 05 08:20:37 me-Legion-5-zfs bluetoothd[140617]: Endpoint registered: sender> May 05 08:20:37 me-Legion-5-zfs bluetoothd[140617]: Endpoint registered: sender> May 05 08:20:37 me-Legion-5-zfs bluetoothd[140617]: Failed to add UUID: Failed > May 05 08:20:37 me-Legion-5-zfs bluetoothd[140617]: Failed to add UUID: Failed > May 05 08:20:37 me-Legion-5-zfs bluetoothd[140617]: Failed to add UUID: Failed > May 05 08:20:37 me-Legion-5-zfs bluetoothd[140617]: Failed to add UUID: Failed > lines 1-22/22 (END) " If you need more just ask. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sun May 5 09:38:14 2024 InstallationDate: Installed on 2024-04-19 (16 days ago) InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240419) MachineType: LENOVO 82JW ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ntiqi9@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_ntiqi9 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2023 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: HHCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76465 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 5 15ACH6 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnLENOVO:bvrHHCN36WW:bd12/07/2023:br1.36:efr1.36:svnLENOVO:pn82JW:pvrLegion515ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrLegion515ACH6:skuLENOVO_MT_82JW_BU_idea_FM_Legion515ACH6: dmi.product.family: Legion 5 15ACH6 dmi.product.name: 82JW dmi.product.sku: LENOVO_MT_82JW_BU_idea_FM_Legion 5 15ACH6 dmi.product.version: Legion 5 15ACH6 dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064869 Title: systemd bluetooth not honoring stop service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2064869/+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 2063254] Re: firewire_ohci stops under moderate load
Update: this is strangely related to nouveau On a machine with a "NVIDIA MCP89 [GeForce 320M]" the nvidia drivers have been removed from 22.04. nouveau when run normally now causes a hang [see other reports if curious] The described "firewire_ohci quits when using firefox" happens when kernel launched with kernel flag nomodeset When launched, instead, with nouveau.noaccel=1 ...normal usage does not affect firewire_ohci, as expected and desired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063254 Title: firewire_ohci stops under moderate load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2063254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063357] Re: attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS
** Attachment added: "screen-2024-04-24-17-49-34.png" https://bugs.launchpad.net/ubuntu/+source/lxqt-powermanagement/+bug/2063357/+attachment/5770120/+files/screen-2024-04-24-17-49-34.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063357 Title: attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-powermanagement/+bug/2063357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063357] Re: attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS
Thank you for the timely reply. I assumed the support site was a report, my apologies, as I assumed it was monitored. I found a very similar report, which I presume is "proper", here: https://bugs.launchpad.net/ubuntu/+source/lxqt-powermanagement/+bug/1987036 and indeed this is a few days older than the support site reference. I figured the description was sufficient, but will attach a brand-new screenshot. In English as requested. I installed backports and observed exactly the same behavior. Logs showed repeats of the crash until the rate-limiting shutdown of restarts for lxqt-powermanager: Apr 24 17:48:54 Konnekt kernel: lxqt-powermanag[20433]: segfault at e8e ip 7e8466908059 sp 7ffeed791208 error 4 in libQt5Core.so.5.15.3[7e846688e000+30f000] likely on CPU 0 (core 0, socket 0) Apr 24 17:48:54 Konnekt kernel: Code: 31 d2 f7 f1 49 8b 40 08 83 c2 01 48 63 f2 48 8d 04 f0 29 d1 74 d8 89 c9 48 8d 0c c8 eb 0c 0f 1f 00 48 83 c0 08 48 39 c8 74 c4 <48> 8b 10 49 39 d0 74 ef 49 89 d0 4c 89 c0 c3 0f 1f 84 00 00 00 00 This was with the backports version: $ lxqt-powermanagement -v lxqt-powermanagement 1.4.0 liblxqt 1.4.0 Qt5.15.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063357 Title: attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-powermanagement/+bug/2063357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063357] [NEW] attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS
Public bug reported: I have exactly the same problem as OP here (and the others who chime in): https://askubuntu.com/questions/1422776/energy-manager-error-when-reducing-screen-brightness-during-inactivity Reported 1 year 8 months ago, still seems broken LxQT Power Manager: In the settings section for "inactivity", I check the option "enable backlight change", in order to reduce the screen brightness after 1 minute of inactivity. If I press the "Check Backlight" button, nothing happens. Upon completion of 1 minute of inactivity, instead of the screen brightness being reduced, I see the power/battery icon disappear, then reappear a few times, then the system displays an alert of multiple manager crash errors, resulting in its autorun being disabled. Adjusting screen brightness via "lxqt-config-brightness" from "lxqt- config" works fine ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lxqt-powermanagement 0.17.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Wed Apr 24 10:03:12 2024 InstallationDate: Installed on 2023-10-31 (175 days ago) InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) SourcePackage: lxqt-powermanagement UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lxqt-powermanagement (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ** Summary changed: - attempting to use idle brightness in lxqt-powermanagement leads to crash + attempting to use idle brightness in lxqt-powermanagement leads to crashin 22.04.4 LTS ** Summary changed: - attempting to use idle brightness in lxqt-powermanagement leads to crashin 22.04.4 LTS + attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063357 Title: attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-powermanagement/+bug/2063357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063254] [NEW] firewire_ohci stops under moderate load
Public bug reported: This began in 6.5.0-27 afaict, and is very noticeable in 6.5.0-28 Using snd_dice to playback audio, doing anything else, even just scrolling in firefox or launching this bug report, causes the firewire driver to quit: Apr 23 12:48:53 Konnekt kernel: firewire_ohci :01:00.0: DMA context IT0 has stopped, error code: evt_timeout ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-extra-6.5.0-28-generic 6.5.0-28.29~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Tue Apr 23 13:08:53 2024 Dependencies: linux-modules-6.5.0-28-generic 6.5.0-28.29~22.04.1 wireless-regdb 2022.06.06-0ubuntu1~22.04.1 InstallationDate: Installed on 2023-10-31 (175 days ago) InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) SourcePackage: linux-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-6.5 (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/2063254 Title: firewire_ohci stops under moderate load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2063254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788044] Re: task kworker blocked for more than 120 seconds nouveau
I have found a fix. First I tried adding "nouveau.modeset=0" to bootflags, which got me to boot but no greeter. sddm appeared to be happily running but it failed to start the display server restarting it did not help "startx" worked, which gave me hope It appeared the session "seat" had been determined by systemd to have "CanGraphical" false Then I found this: https://github.com/mikhailnov/systemd/commit/c00bf275fdfbad3a9db8934b5e266b6abbdb8443 There's a heuristic hack which sets CanGraphical when the kernel starts w/o graphics, but only if this is done via "nomodeset" rather than the driver-specific ".modeset" flags So I just added "nomodeset" to boot flags, and now not only does 6.5.0-28 boot and land at a working greeter again, but all the weird sddm graphics bugs i'd been encountering since 6.5 are gone. Hope this helps someone else... And maybe this kernel issue will get fixed, some day -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788044 Title: task kworker blocked for more than 120 seconds nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788044] Re: task kworker blocked for more than 120 seconds nouveau
This is the closest, most recent report I could find with something which also appears kernel related Kernel 6.5.0-27 -- works fine Kernel 6.5.0-28 -- graphics hard-hangs - sddm never displays, vtty can't be activated shh works, sddm and x11 processes can not be killed, reboot hangs, hard power cycle required I see reports like this literally for years, yet seemingly no resolution. Now I'm bit, in a way suspiciously kernel version related Common internet "use nvidia drivers" wisdom is unworkable as old nvidia hardware is not supported on 22.04 04:00.0 VGA compatible controller: NVIDIA Corporation MCP89 [GeForce 320M] (rev a2) Again, for me, this is with 22.04, kernel 6.5.0-28 All the various combinations of nouveau flags to kernel boot which have helped reduce garbage or sddm troubles don't help. Here's a relevant boot log: Apr 20 21:06:29 Konnekt sddm-greeter[922]: Adding view for "LVDS-1" QRect(0,0 1280x800) Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 216004 put 216088 ib_get 0007 ib_put 0007 state 800081a4 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 21608c put 217b7c ib_get 0009 ib_put 000a state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 218ff0 put 21932c ib_get 000d ib_put 0012 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219a48 put 219a64 ib_get 001f ib_put 0024 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219a64 put 219a7c ib_get 0021 ib_put 0024 state 8024 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219a7c put 219a8c ib_get 0023 ib_put 0024 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219a8c put 219ccc ib_get 0025 ib_put 002a state 8024 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219de8 put 219df8 ib_get 002f ib_put 0030 state 4004 (err: INVALID_MTHD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: CACHE_ERROR - ch 3 [sddm-greeter[922]] subc 0 mthd data 2000 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 219ef0 put 21a2f0 ib_get 0033 ib_put 0038 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 0020b10960 put 0020b10ac8 ib_get 0042 ib_put 0044 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 21aff8 put 21bdf4 ib_get 004b ib_put 004c state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 21c248 put 21c620 ib_get 004d ib_put 004e state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 417a40 put 417a4c ib_get 0056 ib_put 0058 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 417b54 put 417b5c ib_get 005c ib_put 005e state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 4d3370 put 4d33f4 ib_get 0062 ib_put 0064 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 4db3c0 put 4db450 ib_get 0068 ib_put 006a state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 21d000 put 21d150 ib_get 006b ib_put 006c state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 417c50 put 417c5c ib_get 006e ib_put 0070 state 8000 (err: INVALID_CMD) push 00400040 Apr 20 21:06:29 Konnekt kernel: nouveau :04:00.0: fifo: DMA_PUSHER - ch 3 [sddm-greeter[922]] get 4d3630 put 4d3684 ib_get 007a
[Bug 2060398] [NEW] xfsettingsd crashed with SIGTRAP in g_log_writer_default()
*** This bug is a security vulnerability *** Public security bug reported: This is first boot after install on a KVM current iso dated today. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: xfce4-settings 4.18.4-0ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sun Apr 7 12:27:36 2024 ExecutablePath: /usr/bin/xfsettingsd InstallationDate: Installed on 2024-04-07 (0 days ago) InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2) ProcCmdline: xfsettingsd --display :0.0 --sm-client-id 2837f7668-f84c-4f47-91fe-5527e1d866ed ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 5 SignalName: SIGTRAP SourcePackage: xfce4-settings StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () __libc_start_call_main (main=main@entry=0x5ae474824800, argc=argc@entry=5, argv=argv@entry=0x7ffd992f56a8) at ../sysdeps/nptl/libc_start_call_main.h:58 Title: xfsettingsd crashed with SIGTRAP in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: ** Affects: xfce4-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace noble ** Information type changed from Private to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060398 Title: xfsettingsd crashed with SIGTRAP in g_log_writer_default() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/2060398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] Re: Ubuntu 22.04 unable to mount root partition
I tried Ubuntu 22.04 with kernel 5.13 on Acer Spin 5 SP513-54N. Touchpad, touchscreen, and stylus all work, but Wi-Fi does not work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965691] [NEW] No Epson Stylus Photo R220 or R200 drivers
Public bug reported: The gutenprint website says that they still support the earlier "Epson Stylus Photo" models, but the Ubuntu printer settings tool only shows drivers for the R240 and up. Is this a regression, or purposeful? See http://gimp-print.sourceforge.net/p_Supported_Printers.php The gutenprint site shows this sub-list of similarly supported drivers, including the R220: Epson Stylus Photo R200 escp2-r200 Epson Stylus Photo R210 escp2-r210 Epson Stylus Photo R220 escp2-r220 Epson Stylus Photo R230 escp2-r230 What you expected to happen? I expected the Ubuntu printer settings utility to offer the "Epson Stylus Photo R220" printer driver. What happened instead? The Ubuntu printer settings utility only offered the series R240 and above. System Info: Description: Ubuntu 20.04.4 LTS Release: 20.04 Cups Info: Installed: 2.3.1-9ubuntu1.1 Candidate: 2.3.1-9ubuntu1.1 Version table: *** 2.3.1-9ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages Note: Manually, I was able to successfully install openprinting- gutenprint_5.2.7-1lsb3.2_amd64.deb from the OpenPrinting site (which includes R220) but it would be better to find the R220 driver in the list of available print drivers through the automated Ubuntu printer settings utility. See https://www.openprinting.org/printer/Epson/Epson-Stylus_Photo_R220 for the Debian package(s). ** Affects: cups (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/1965691 Title: No Epson Stylus Photo R220 or R200 drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
Is this Linux patch series back-ported to older kernels, like the 5.13 kernel that came with my Ubuntu 20.04 installation, or any LTS kernel? I'm not fully familiar with the Linux kernel release behaviour. I'm asking this because I'm looking for the best way to apply this patch on an older kernel without building the kernel from source? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1950062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
I just verified the patch in Ubuntu 20.04 under kernel version 5.13. All of my components now show up in open RGB. I compiled the kernel myself using the steps provided in https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues/1984#note_872699651. As mentioned above, I was not able to verify the PPA provided by @vicamo. **System info:** PCPartPicker Part List: https://nl.pcpartpicker.com/list/7HW8Y9 - CPU: AMD Ryzen 5 5600G 3.9 GHz 6-Core Processor (€228.95 @ Amazon Netherlands) - Motherboard: Asus ROG STRIX B550-E GAMING ATX AM4 Motherboard (€226.81 @ Amazon Netherlands) - Memory: Crucial Ballistix RGB 16 GB (2 x 8 GB) DDR4-3200 CL16 Memory (€83.85 @ Megekko) - Memory: *Crucial Ballistix RGB 16 GB (2 x 8 GB) DDR4-3200 CL16 Memory (€83.85 @ Megekko) - Video Card: NVIDIA GeForce GTX 1070 8 GB Video Card (2-Way SLI) - Video Card: NVIDIA GeForce GTX 1070 8 GB Video Card (2-Way SLI) - Case: Fractal Design Meshify 2 Compact TG Light Tint ATX Mid Tower Case (€159.00 @ Amazon Netherlands) - Power Supply: Corsair HXi 750 W 80+ Platinum Certified Fully Modular ATX Power Supply (€197.99 @ Amazon Netherlands) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1950062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
I am now building the kernel from source using the following steps https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues/1984#note_872699651 to verify whether the patch solves my problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1950062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
Ah yea, that's a type. I used `sudo reboot now`. For me, after those steps the ram still didn't show up, so there might be another problem on my system. I also tried manually building the kernel with the patch, but I run into some unrelated issues. I think I will wait till the patch hits the upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1950062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
I tried the PPA from @vicamo on Ubuntu 20.04 with kernel 5.14, but It does not seem to work for me. I installed the PPA using the following commands: sudo add-apt-repository ppa:vicamo/ppa-1950062 sudo update` sudo install linux-oem-5.14-headers-5.14.0-2023 linux-oem-5.14-tools-5.14.0-2023 linux-oem-5.14-tools-host. sudo apt reboot. sudo openrgb Maybe I am doing something wrong. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1950062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
I am affected by this issue on my Ubuntu 20.04 system that is running kernel a 5.13 kernel. I have a ASUS rog stix b550-E gaming motherboard, an AMD 5600G CPU and use crucial ballistix ram. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1950062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960569] Re: Screen goes dim
@Daniel .. Thanks. * I think brightness-controller is a thin UI around xrandr. If something in Ubuntu is improperly changing "Brightness" and xrandr is the only cure, why remove brightness-controller? Or, do your comments about it apply equally to xrandr -- namely that I should avoid xrandr, too? * I rebooted and chose "GNOME" (one of two identically-named options); I'll report back when (if) the screens go dim again. If things stay stable, I will report back later to help close (and blame MATE). I did not notice whether one login option said "on Xorg"; I'll look for that next time. * Thinking back, I wonder if a screensaver was implicated in the problem. * (Unrelated) I liked the GNOME UI on 20.10; MATE 21.10 has some annoying differences, so I am happy to learn how to go back to GNOME while staying with the same version Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960569 Title: Screen goes dim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1960569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960569] [NEW] Screen goes dim
Public bug reported: I walk away from the machine; come back hours later to find that the screen is dim. The following command confirms that the cause is something in Ubuntu xrandr --listmonitors --verbose | egrep -3 -i 'gamma|backl|brightn' Has shown value for "Brightness" of 0.11, 0.18, 0.0018, 0.20, and possibly other values. (Gamma is all 1.0.) This occurs on both monitors that I have hooked up, but the values are usually different. I like a Brightness of 0.80, I know how to manually change with xrandr or a brightness-controller app. When the brightness is too low it is very hard to fix things without rebooting. I am currently running 21.10, but I have had mysterious crashes in older versions of Ubuntu; I now wonder if the was going all the way to zero in some of those crashes. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: MATE Date: Thu Feb 10 15:32:43 2022 DistUpgraded: 2022-02-03 15:56:57,188 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:2088] InstallationDate: Installed on 2021-01-25 (381 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Intel(R) Client Systems NUC9V7QNX ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-28-generic root=UUID=7374319a-8421-4977-a836-6882e295d7ca ro quiet splash crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2022-02-03 (6 days ago) dmi.bios.date: 11/30/2020 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QNCFLX70.0059.2020.1130.2122 dmi.board.name: NUC9V7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K47180-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.39 dmi.modalias: dmi:bvnIntelCorp.:bvrQNCFLX70.0059.2020.1130.2122:bd11/30/2020:br5.13:efr24.39:svnIntel(R)ClientSystems:pnNUC9V7QNX:pvrK47174-402:rvnIntelCorporation:rnNUC9V7QNB:rvrK47180-402:cvnIntelCorporation:ct35:cvr2.0:skuBKNUC9V7QNX: dmi.product.family: QN dmi.product.name: NUC9V7QNX dmi.product.sku: BKNUC9V7QNX dmi.product.version: K47174-402 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug impish possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960569 Title: Screen goes dim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
I'm not sure what's needed to bisect the kernel? What would I need to do? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954849] [NEW] package am-utils 6.2+rc20110530-3.2ubuntu2 failed to install/upgrade: installed am-utils package post-installation script subprocess returned error exit status 1
Public bug reported: failed to install through command lines ProblemType: Package DistroRelease: Ubuntu 20.04 Package: am-utils 6.2+rc20110530-3.2ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: libamu4:amd64: Install am-utils:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Dec 14 14:53:20 2021 ErrorMessage: installed am-utils package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-12-06 (8 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) 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: am-utils Title: package am-utils 6.2+rc20110530-3.2ubuntu2 failed to install/upgrade: installed am-utils package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: am-utils (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/1954849 Title: package am-utils 6.2+rc20110530-3.2ubuntu2 failed to install/upgrade: installed am-utils package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/am-utils/+bug/1954849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
The speed is limited on every boot now...I also notice my bios time
being reset to 2013...when unplugged from the wall (I'm going to open it
up, the cmos battery may have died.)
rt@sys76:~$ sudo grep . /sys/class/powercap/intel-rapl/intel-rapl\:0/*
[sudo] password for rt:
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_max_power_uw:4700
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_name:long_term
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_power_limit_uw:4700
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_time_window_us:27983872
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_max_power_uw:0
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_name:short_term
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_power_limit_uw:5875
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_time_window_us:2440
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/device: Is a directory
/sys/class/powercap/intel-rapl/intel-rapl:0/enabled:0
/sys/class/powercap/intel-rapl/intel-rapl:0/energy_uj:5242172615
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/intel-rapl:0:0: Is a directory
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/intel-rapl:0:1: Is a directory
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/intel-rapl:0:2: Is a directory
/sys/class/powercap/intel-rapl/intel-rapl:0/max_energy_range_uj:262143328850
/sys/class/powercap/intel-rapl/intel-rapl:0/name:package-0
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/power: Is a directory
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/subsystem: Is a directory
rt@sys76:~$
rt@sys76:~$
rt@sys76:~$
rt@sys76:~$
rt@sys76:~$
rt@sys76:~$
rt@sys76:~$ sudo rdmsr -c -p0 0x64F
rdmsr: CPU 0 cannot read MSR 0x064f
rt@sys76:~$ sudo strace rdmsr 0x64F
execve("/usr/sbin/rdmsr", ["rdmsr", "0x64F"], 0x7ffe9486b188 /* 16 vars */) = 0
brk(NULL) = 0x5633b869a000
arch_prctl(0x3001 /* ARCH_??? */, 0x7ffe398f8370) = -1 EINVAL (Invalid argument)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=79034, ...}) = 0
mmap(NULL, 79034, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fc1f8b19000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360q\2\0\0\0\0\0"...,
832) = 832
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"...,
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0",
32, 848) = 32
pread64(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
68, 880) = 68
fstat(3, {st_mode=S_IFREG|0755, st_size=2029224, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fc1f8b17000
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"...,
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0",
32, 848) = 32
pread64(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
68, 880) = 68
mmap(NULL, 2036952, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fc1f8925000
mprotect(0x7fc1f894a000, 1847296, PROT_NONE) = 0
mmap(0x7fc1f894a000, 1540096, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x25000) = 0x7fc1f894a000
mmap(0x7fc1f8ac2000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x19d000) = 0x7fc1f8ac2000
mmap(0x7fc1f8b0d000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7fc1f8b0d000
mmap(0x7fc1f8b13000, 13528, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fc1f8b13000
close(3)= 0
arch_prctl(ARCH_SET_FS, 0x7fc1f8b18580) = 0
mprotect(0x7fc1f8b0d000, 12288, PROT_READ) = 0
mprotect(0x5633b7d85000, 4096, PROT_READ) = 0
mprotect(0x7fc1f8b5a000, 4096, PROT_READ) = 0
munmap(0x7fc1f8b19000, 79034) = 0
openat(AT_FDCWD, "/dev/cpu/0/msr", O_RDONLY) = 3
pread64(3, 0x7ffe398f8288, 8, 1615) = -1 EIO (Input/output error)
write(2, "rdmsr: CPU 0 cannot read MSR 0x0"..., 40rdmsr: CPU 0 cannot read MSR
0x064f
) = 40
exit_group(4) = ?
+++ exited with 4 +++
rt@sys76:~$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945221
Title:
CPU frequency stuck at minimum value..again Ubuntu 20.04.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
@koba issue still occurs.
@Doug
rt@sys76:~$ sudo rdmsr -c -p0 0x1b2
0x3
rt@sys76:~$ sudo strace rdmsr 0x1b2
execve("/usr/sbin/rdmsr", ["rdmsr", "0x1b2"], 0x7fff4f90a298 /* 17 vars */) = 0
brk(NULL) = 0x56510cc31000
arch_prctl(0x3001 /* ARCH_??? */, 0x7ffe42320b10) = -1 EINVAL (Invalid argument)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=253505, ...}) = 0
mmap(NULL, 253505, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fec4390
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360q\2\0\0\0\0\0"...,
832) = 832
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"...,
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0",
32, 848) = 32
pread64(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
68, 880) = 68
fstat(3, {st_mode=S_IFREG|0755, st_size=2029224, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fec438fe000
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"...,
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0",
32, 848) = 32
pread64(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
68, 880) = 68
mmap(NULL, 2036952, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fec4370c000
mprotect(0x7fec43731000, 1847296, PROT_NONE) = 0
mmap(0x7fec43731000, 1540096, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x25000) = 0x7fec43731000
mmap(0x7fec438a9000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x19d000) = 0x7fec438a9000
mmap(0x7fec438f4000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7fec438f4000
mmap(0x7fec438fa000, 13528, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fec438fa000
close(3)= 0
arch_prctl(ARCH_SET_FS, 0x7fec438ff580) = 0
mprotect(0x7fec438f4000, 12288, PROT_READ) = 0
mprotect(0x56510cbb5000, 4096, PROT_READ) = 0
mprotect(0x7fec4396b000, 4096, PROT_READ) = 0
munmap(0x7fec4390, 253505) = 0
openat(AT_FDCWD, "/dev/cpu/0/msr", O_RDONLY) = 3
pread64(3, "\3\0\0\0\0\0\0\0", 8, 434) = 8
close(3)= 0
fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(0x88, 0), ...}) = 0
brk(NULL) = 0x56510cc31000
brk(0x56510cc52000) = 0x56510cc52000
write(1, "3\n", 23
) = 2
exit_group(0) = ?
+++ exited with 0 +++
rt@sys76:~$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945221
Title:
CPU frequency stuck at minimum value..again Ubuntu 20.04.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
ok
rt@sys76:~$ sudo rdmsr -c -p0 0x19c
0x8839080c
rt@sys76:~$ sudo rdmsr -c -p0 0x1aa
0x40
rt@sys76:~$ sudo rdmsr -c -p0 0x1b1
0x8839080c
rt@sys76:~$ sudo rdmsr -c -p0 0x16f
rdmsr: CPU 0 cannot read MSR 0x016f
rt@sys76:~$ sudo rdmsr -c -p0 0x1fc
0x4005d
rt@sys76:~$ sudo strace rdmsr 0x19C
execve("/usr/sbin/rdmsr", ["rdmsr", "0x19C"], 0x7ffdaa2d1488 /* 17 vars */) = 0
brk(NULL) = 0x55b45cb84000
arch_prctl(0x3001 /* ARCH_??? */, 0x7ffc77c46f80) = -1 EINVAL (Invalid argument)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=253505, ...}) = 0
mmap(NULL, 253505, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f35e41bf000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360q\2\0\0\0\0\0"...,
832) = 832
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"...,
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0",
32, 848) = 32
pread64(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
68, 880) = 68
fstat(3, {st_mode=S_IFREG|0755, st_size=2029224, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f35e41bd000
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"...,
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0",
32, 848) = 32
pread64(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
68, 880) = 68
mmap(NULL, 2036952, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f35e3fcb000
mprotect(0x7f35e3ff, 1847296, PROT_NONE) = 0
mmap(0x7f35e3ff, 1540096, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x25000) = 0x7f35e3ff
mmap(0x7f35e4168000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x19d000) = 0x7f35e4168000
mmap(0x7f35e41b3000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f35e41b3000
mmap(0x7f35e41b9000, 13528, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f35e41b9000
close(3)= 0
arch_prctl(ARCH_SET_FS, 0x7f35e41be580) = 0
mprotect(0x7f35e41b3000, 12288, PROT_READ) = 0
mprotect(0x55b45c8b1000, 4096, PROT_READ) = 0
mprotect(0x7f35e422a000, 4096, PROT_READ) = 0
munmap(0x7f35e41bf000, 253505) = 0
openat(AT_FDCWD, "/dev/cpu/0/msr", O_RDONLY) = 3
pread64(3, "\f\109\210\0\0\0\0", 8, 412) = 8
close(3)= 0
fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(0x88, 0x3), ...}) = 0
brk(NULL) = 0x55b45cb84000
brk(0x55b45cba5000) = 0x55b45cba5000
write(1, "8839080c\n", 98839080c
) = 9
exit_group(0) = ?
+++ exited with 0 +++
rt@sys76:~$ sudo strace rdmsr 0x1aa
execve("/usr/sbin/rdmsr", ["rdmsr", "0x1aa"], 0x7fffde650548 /* 17 vars */) = 0
brk(NULL) = 0x555d67d9f000
arch_prctl(0x3001 /* ARCH_??? */, 0x7ffd9bfd56d0) = -1 EINVAL (Invalid argument)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=253505, ...}) = 0
mmap(NULL, 253505, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fd5f63ff000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360q\2\0\0\0\0\0"...,
832) = 832
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"...,
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0",
32, 848) = 32
pread64(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
68, 880) = 68
fstat(3, {st_mode=S_IFREG|0755, st_size=2029224, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fd5f63fd000
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"...,
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0",
32, 848) = 32
pread64(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
68, 880) = 68
mmap(NULL, 2036952, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fd5f620b000
mprotect(0x7fd5f623, 1847296, PROT_NONE) = 0
mmap(0x7fd5f623, 1540096, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x25000) = 0x7fd5f623
mmap(0x7fd5f63a8000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x19d000) = 0x7fd5f63a8000
mmap(0x7fd5f63f3000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
Ok One terminal was running rt@sys76:~$ taskset -c 2 yes > /dev/null 2nd terminal data: rt@sys76:~$ grep . /sys/devices/system/cpu/intel_pstate/* /sys/devices/system/cpu/intel_pstate/max_perf_pct:100 /sys/devices/system/cpu/intel_pstate/min_perf_pct:50 /sys/devices/system/cpu/intel_pstate/no_turbo:0 /sys/devices/system/cpu/intel_pstate/num_pstates:27 /sys/devices/system/cpu/intel_pstate/status:active /sys/devices/system/cpu/intel_pstate/turbo_pct:38 rt@sys76:~$ rt@sys76:~$ rt@sys76:~$ rt@sys76:~$ rt@sys76:~$ rt@sys76:~$ rt@sys76:~$ grep . /sys/devices/system/cpu/cpu2/cpufreq/* /sys/devices/system/cpu/cpu2/cpufreq/affected_cpus:2 /sys/devices/system/cpu/cpu2/cpufreq/cpuinfo_max_freq:340 /sys/devices/system/cpu/cpu2/cpufreq/cpuinfo_min_freq:80 /sys/devices/system/cpu/cpu2/cpufreq/cpuinfo_transition_latency:0 /sys/devices/system/cpu/cpu2/cpufreq/related_cpus:2 /sys/devices/system/cpu/cpu2/cpufreq/scaling_available_governors:performance powersave /sys/devices/system/cpu/cpu2/cpufreq/scaling_cur_freq:798228 /sys/devices/system/cpu/cpu2/cpufreq/scaling_driver:intel_pstate /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor:powersave /sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq:340 /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq:80 /sys/devices/system/cpu/cpu2/cpufreq/scaling_setspeed: rt@sys76:~$ rt@sys76:~$ sudo rdmsr --bitfield 15:8 -u -a 0x198 [sudo] password for rt: 8 8 8 8 8 8 8 8 rt@sys76:~$ rt@sys76:~$ rt@sys76:~$ rt@sys76:~$ sudo rdmsr --bitfield 15:8 -u -a 0x199 17 17 34 17 17 34 17 17 rt@sys76:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
Now after another reboot the speed is stuck at 800mhz again and doesn't move rt@sys76:~$ uname -r 5.15.5-76051505-generic rt@sys76:~$ grep CONFIG_CPU_FREQ_DEFAULT /boot/config-5.15.5-76051505-generic # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL=y rt@sys76:~$ rt@sys76:~$ sudo turbostat --Summary --quiet --show Busy%,Bzy_MHz,IRQ,PkgWatt,PkgTmp,RAMWatt,GFXWatt,CorWatt --interval 10 [sudo] password for rt: Busy% Bzy_MHz IRQ PkgTmp PkgWatt CorWatt GFXWatt 2.42800 555043 1.590.050.02 15.37 800 17228 44 2.990.420.17 19.79 800 25124 44 3.500.510.15 31.52 800 42876 46 5.060.880.44 9.73800 14967 46 2.610.250.15 3.60800 735846 1.660.070.04 4.63800 852946 1.870.100.04 3.29800 724346 1.680.070.03 7.49800 12913 47 2.290.190.07 rt@sys76:~$ cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 4294.55 ms. hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 3.40 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 798 MHz. analyzing CPU 1: driver: intel_pstate CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 4294.55 ms. hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 3.40 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 798 MHz. analyzing CPU 2: driver: intel_pstate CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 4294.55 ms. hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 3.40 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 798 MHz. analyzing CPU 3: driver: intel_pstate CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 4294.55 ms. hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 3.40 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 798 MHz. analyzing CPU 4: driver: intel_pstate CPUs which run at the same hardware frequency: 4 CPUs which need to have their frequency coordinated by software: 4 maximum transition latency: 4294.55 ms. hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 3.40 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 798 MHz. analyzing CPU 5: driver: intel_pstate CPUs which run at the same hardware frequency: 5 CPUs which need to have their frequency coordinated by software: 5 maximum transition latency: 4294.55 ms. hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 3.40 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 799 MHz. analyzing CPU 6: driver: intel_pstate CPUs which run at the same hardware frequency: 6 CPUs which need to have their frequency coordinated by software: 6 maximum transition latency: 4294.55 ms. hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 3.40 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 798 MHz. analyzing CPU 7: driver: intel_pstate CPUs which run at the same hardware frequency: 7 CPUs which need to have their frequency coordinated by software: 7 maximum transition latency: 4
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
Yes I can get it to boot into active mode thanks to Doug, but after several minutes the cpu drops to 798-800mhz and won't increase no matter if I try and change it. I did notice that the scaling_governor always boots to powersave mode. When I change it to performance after several minutes the cpu drops to 798-800mhz again. I did find a similar problem "Linux kernel 5.8 defaults to passive mode for intel_pstate driver for cpu before skylake" but it always boots to the powersave governor and changing it doesn't fix the issue. https://www.reddit.com/r/linux/comments/ihdozd/linux_kernel_58_defaults_to_passive_mode_for/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
Here's a list I can't remember the last time it worked, if you do a google search on "ubuntu cpu lowest freq" seems to be a very common problem but none of the fixes work for me. I can't change the speed of my CPU's in my bios (a system76 linux machine). What do you want me to check in the bios? Here's the kernel versions rt@sys76:~$ uname --all Linux sys76 5.15.5-76051505-generic #202111250933~1638201579~20.04~09f1aa7~dev-Ubuntu SMP Tue Nov 30 x86_64 x86_64 x86_64 GNU/Linux rt@sys76:~$ rt@sys76:~$ dpkg --list | grep linux-image rc linux-image-4.10.0-27-generic 4.10.0-27.30~16.04.2 amd64Linux kernel image for version 4.10.0 on 64 bit x86 SMP rc linux-image-4.10.0-28-generic 4.10.0-28.32~16.04.2 amd64Linux kernel image for version 4.10.0 on 64 bit x86 SMP rc linux-image-4.10.0-30-generic 4.10.0-30.34~16.04.1 amd64Linux kernel image for version 4.10.0 on 64 bit x86 SMP rc linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 amd64Linux kernel image for version 4.10.0 on 64 bit x86 SMP rc linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1 amd64Linux kernel image for version 4.10.0 on 64 bit x86 SMP rc linux-image-4.10.0-42-generic 4.10.0-42.46~16.04.1 amd64Linux kernel image for version 4.10.0 on 64 bit x86 SMP rc linux-image-4.13.0-26-generic 4.13.0-26.29~16.04.2 amd64Linux kernel image for version 4.13.0 on 64 bit x86 SMP rc linux-image-4.15.0-101-generic 4.15.0-101.102 amd64Signed kernel image generic rc linux-image-4.15.0-106-generic 4.15.0-106.107 amd64Signed kernel image generic rc linux-image-4.15.0-108-generic 4.15.0-108.109 amd64Signed kernel image generic rc linux-image-4.15.0-109-generic 4.15.0-109.110 amd64Signed kernel image generic rc linux-image-4.15.0-111-generic 4.15.0-111.112 amd64Signed kernel image generic rc linux-image-4.15.0-112-generic 4.15.0-112.113 amd64Signed kernel image generic rc linux-image-4.15.0-115-generic 4.15.0-115.116 amd64Signed kernel image generic rc linux-image-4.15.0-117-generic 4.15.0-117.118 amd64Signed kernel image generic rc linux-image-4.15.0-118-generic 4.15.0-118.119 amd64Signed kernel image generic rc linux-image-4.15.0-20-generic 4.15.0-20.21 amd64Signed kernel image generic rc linux-image-4.15.0-22-generic 4.15.0-22.24 amd64Signed kernel image generic rc linux-image-4.15.0-23-generic 4.15.0-23.25 amd64Signed kernel image generic rc linux-image-4.15.0-24-generic 4.15.0-24.26 amd64Signed kernel image generic rc linux-image-4.15.0-29-generic 4.15.0-29.31 amd64Signed kernel image generic rc linux-image-4.15.0-30-generic 4.15.0-30.32 amd64Signed kernel image generic rc linux-image-4.15.0-32-generic 4.15.0-32.35 amd64Signed kernel image generic rc linux-image-4.15.0-33-generic 4.15.0-33.36 amd64Signed kernel image generic rc linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic rc linux-image-4.15.0-38-generic 4.15.0-38.41 amd6
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
ok... rt@sys76:~$ sudo cpupower -c all frequency-info [sudo] password for rt: analyzing CPU 0: driver: intel_cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 1: driver: intel_cpufreq CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 2: driver: intel_cpufreq CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 3: driver: intel_cpufreq CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 4: driver: intel_cpufreq CPUs which run at the same hardware frequency: 4 CPUs which need to have their frequency coordinated by software: 4 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 5: driver: intel_cpufreq CPUs which run at the same hardware frequency: 5 CPUs which need to have their frequency coordinated by software: 5 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 6: driver: intel_cpufreq CPUs which run at the same hardware frequency: 6 CPUs which need to have their frequency coordinated by software: 6 maximum transition latency: 20.0 us hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: conservative ondemand userspace powersave performance schedutil current policy: frequency should be within 1.70 GHz and 3.40 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 798 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes analyzing CPU 7: driver: intel_cpufreq CPUs which run at the same hardware frequency: 7 CPUs which need to have their frequency coordinated by software: 7 ma
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
rt@sys76:~$ sudo systemctl status thermald.service ● thermald.service - Thermal Daemon Service Loaded: loaded (/lib/systemd/system/thermald.service; enabled; v> Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago Process: 1319 ExecStart=/usr/sbin/thermald --systemd --dbus-enabl> Main PID: 1319 (code=exited, status=0/SUCCESS) Nov 30 09:41:40 sys76 thermald[1319]: 13 CPUID levels; family:model:s> Nov 30 09:41:40 sys76 thermald[1319]: Polling mode is enabled: 4 Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for> Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for> Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for> Dec 01 09:39:24 sys76 thermald[1319]: Terminating ... Dec 01 09:39:24 sys76 systemd[1]: Stopping Thermal Daemon Service... Dec 01 09:39:25 sys76 thermald[1319]: terminating on user request .. Dec 01 09:39:26 sys76 systemd[1]: thermald.service: Succeeded. Dec 01 09:39:26 sys76 systemd[1]: Stopped Thermal Daemon Service. lines 1-16/16 (END)...skipping... ● thermald.service - Thermal Daemon Service Loaded: loaded (/lib/systemd/system/thermald.service; enabled; ven> Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago Process: 1319 ExecStart=/usr/sbin/thermald --systemd --dbus-enable > Main PID: 1319 (code=exited, status=0/SUCCESS) Nov 30 09:41:40 sys76 thermald[1319]: 13 CPUID levels; family:model:ste> Nov 30 09:41:40 sys76 thermald[1319]: Polling mode is enabled: 4 Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for r> Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for r> Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for r> Dec 01 09:39:24 sys76 thermald[1319]: Terminating ... Dec 01 09:39:24 sys76 systemd[1]: Stopping Thermal Daemon Service... Dec 01 09:39:25 sys76 thermald[1319]: terminating on user request .. Dec 01 09:39:26 sys76 systemd[1]: thermald.service: Succeeded. Dec 01 09:39:26 sys76 systemd[1]: Stopped Thermal Daemon Service. ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● thermald.service - Thermal Daemon Service Loaded: loaded (/lib/systemd/system/thermald.service; enabled; vendor pre> Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago Process: 1319 ExecStart=/usr/sbin/thermald --systemd --dbus-enable --adapt> Main PID: 1319 (code=exited, status=0/SUCCESS) Nov 30 09:41:40 sys76 thermald[1319]: 13 CPUID levels; family:model:stepping 0> Nov 30 09:41:40 sys76 thermald[1319]: Polling mode is enabled: 4 Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading > Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading > Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading > Dec 01 09:39:24 sys76 thermald[1319]: Terminating ... Dec 01 09:39:24 sys76 systemd[1]: Stopping Thermal Daemon Service... Dec 01 09:39:25 sys76 thermald[1319]: terminating on user request .. Dec 01 09:39:26 sys76 systemd[1]: thermald.service: Succeeded. Dec 01 09:39:26 sys76 systemd[1]: Stopped Thermal Daemon Service. ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● thermald.service - Thermal Daemon Service Loaded: loaded (/lib/systemd/system/thermald.service; enabled; vendor preset> Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago Process: 1319 ExecStart=/usr/sbin/thermald --systemd --dbus-enable --adaptive> Main PID: 1319 (code=exited, status=0/SUCCESS) Nov 30 09:41:40 sys76 thermald[1319]: 13 CPUID levels; family:model:stepping 0x6:> Nov 30 09:41:40 sys76 thermald[1319]: Polling mode is enabled: 4 Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading raw> Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading raw> Nov 30 09:41:40 sys76 thermald[1319]: sensor id 5 : No temp sysfs for reading raw> Dec 01 09:39:24 sys76 thermald[1319]: Terminating ... Dec 01 09:39:24 sys76 systemd[1]: Stopping Thermal Daemon Service... Dec 01 09:39:25 sys76 thermald[1319]: terminating on user request .. Dec 01 09:39:26 sys76 systemd[1]: thermald.service: Succeeded. Dec 01 09:39:26 sys76 systemd[1]: Stopped Thermal Daemon Service. ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● thermald.service - Thermal Daemon Service ● thermald.service - Thermal Daemon Service ● thermald.service - Thermal Daemon Service ● thermald.service - Thermal Daemon Service ● thermald.service - Thermal Daemon Service ● thermald.service - Thermal Daemon Service ● thermald.service - Thermal Daemon Service Loaded: loaded (/lib/systemd/system/thermald.service; enabled; vendor preset: enabled) Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago Process: 1319 ExecStart=/usr/sbin/thermald --systemd --dbus-enable --adaptive (code=exited, status=0/> Main PID: 1319 (code=exited, status=0/SUCCESS) Nov 30 09:41:40 sys76 thermald[1319]: 13 CPUID levels; family:mod
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
I'm not sure if this is the right package ** Package changed: ubuntu => thermald (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945221] [NEW] CPU frequency stuck at minimum value..again Ubuntu 20.04.3
Public bug reported: I would really like to find out why my cpu's keep reverting back to a cpu powersave mode after I get a kernel update then reboot. I cleaned my laptops vent but this seems to happen whenever a new kernel is updated and installed. https://askubuntu.com/questions/1366090/ubuntu-20-04-3-lts-significant- throttling-of-intel-i7-processor?noredirect=1#comment2345549_1366090 Description:Ubuntu 20.04.3 LTS Release:20.04 Computer Summary Computer Processor Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Memory 16315MB (4407MB used) Machine TypeLaptop Operating SystemUbuntu 20.04.3 LTS User Name rt (rt) Date/Time Mon 30 Aug 2021 02:33:09 PM EDT Display Resolution 1920x1080 pixels OpenGL Renderer Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) X11 Vendor The X.Org Foundation Audio Devices Audio Adapter HDA-Intel - HDA Intel HDMI Audio Adapter HDA-Intel - HDA Intel PCH Audio Adapter USB-Audio - USB Audio Device Input Devices Power Button Sleep Button Lid Switch Power Button AT Translated Set 2 keyboard USB Audio Device ETPS/2 Elantech Touchpad Logitech Anywhere MX Video Bus HDA Intel PCH Mic HDA Intel PCH Front Headphone HDA Intel HDMI HDMI/DP,pcm:3 HDA Intel HDMI HDMI/DP,pcm:7 HDA Intel HDMI HDMI/DP,pcm:8 HDA Intel HDMI HDMI/DP,pcm:9 HDA Intel HDMI HDMI/DP,pcm:10 Printers (CUPS) OfficeJet_Pro_6978 Default SCSI Disks TSSTcorp CDDVDW SN-208DB ATA INTEL SSDMCEAC12 ATA ST1000LM014-1EJ1 Operating System Version Kernel Linux 5.4.0-81-generic (x86_64) Version #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 C Library GNU C Library / (Ubuntu GLIBC 2.31-0ubuntu9.2) 2.31 DistributionUbuntu 20.04.3 LTS Current Session Computer Name sys76 User Name rt (rt) Languageen_US.UTF-8 () Home Directory /home/rt Misc Uptime 20 minutes Load Average0.83, 1.37, 1.62 Available entropy in /dev/random3649 bits (healthy) rt@sys76:~$ dpkg -l *freq* | grep ii rt@sys76:~$ rt@sys76:~$ sudo turbostat --Summary --quiet --show Busy%,Bzy_MHz,PkgTmp,PkgWatt,GFXWatt,IRQ --interval 6 Busy% Bzy_MHz IRQ PkgTmp PkgWatt GFXWatt 2.95800 334747 2.160.01 2.76800 306949 2.150.01 5.85800 512248 2.730.01 11.87 800 800847 3.410.04 8.23800 577847 2.860.05 rt@sys76:~$ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 60 Model name: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Stepping:3 CPU MHz: 798.103 CPU max MHz: 3400. CPU min MHz: 800. BogoMIPS:4788.65 Virtualization: VT-x L1d cache: 128 KiB L1i cache: 128 KiB L2 cache:1 MiB L3 cache:6 MiB NUMA node0 CPU(s): 0-7 Vulnerability Itlb multihit: KVM: Mitigation: Split huge pages Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulne rable Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Meltdown: Mitigation; PTI Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitizatio n Vulnerability Spectre v2:Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIB P conditional, RSB filling Vulnerability Srbds: Mitigation; Microcode Vulnerability Tsx async abort: Not affected Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat p se36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xto pology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds _cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr
[Bug 1935767] Re: vanilla-gnome-default-settings will not install for impish-proposed
Thanks for this fix! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935767 Title: vanilla-gnome-default-settings will not install for impish-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-default-settings/+bug/1935767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939339] Re: Security exception raised by java.util.Properties.store() when using openjdk-16-jdk
Stuart Marks (from the Open JDK team) has found the problematic code in https://packages.debian.org/unstable/java/openjdk-16-source and identified two bugs in it, including the one responsible for this behavior. For that bug, he has recommended a fix. Please see his analysis at https://bugs.openjdk.java.net/browse/JDK-8272157 It would be great if an Ubuntu engineer could coordinate with Stuart, perhaps via the Open JDK issue, and apply the bug fixes he recommends. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939339 Title: Security exception raised by java.util.Properties.store() when using openjdk-16-jdk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-16/+bug/1939339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939339] Re: Security exception raised by java.util.Properties.store() when using openjdk-16-jdk
** Summary changed: - Security exception raised by java.util.Properties.store() when using openjdk-16-jdk-headless + Security exception raised by java.util.Properties.store() when using openjdk-16-jdk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939339 Title: Security exception raised by java.util.Properties.store() when using openjdk-16-jdk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-16/+bug/1939339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939339] [NEW] Security exception raised by java.util.Properties.store() when using openjdk-16-jdk
Public bug reported:
Since JDK 11, the Ubuntu "open jdk" packages have a defect which does
not appear in the actual Open JDK distros available from java.net. The
problem was discovered by Derby users (see
https://issues.apache.org/jira/browse/DERBY-7122) and reported as an
Open JDK bug (see https://bugs.openjdk.java.net/browse/JDK-8272157).
This is the problem: When trying to persist a java.util.Properties
object, an exception is raised when running under the java
SecurityManager. The exception occurs when java.util.Properties.store0()
calls java.util.Properties.getFormattedTimestamp() in order to format
the timestamp required by the contract of java.util.Properties.store().
The getFormattedTimestamp() method does not appear in Open JDK. There
the timestamp is formatted thusly:
bw.write("#" + new Date().toString());
The exception stack trace (see the repro below) is:
Exception in thread "main" java.security.AccessControlException: access denied
("java.lang.RuntimePermission" "getenv.SOURCE_DATE_EPOCH")
at
java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
at
java.base/java.security.AccessController.checkPermission(AccessController.java:1036)
at
java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:408)
at java.base/java.lang.System.getenv(System.java:1016)
at
java.base/java.util.Properties.getFormattedTimestamp(Properties.java:1599)
at java.base/java.util.Properties.store0(Properties.java:926)
at java.base/java.util.Properties.store(Properties.java:868)
at DERBY_7122.main(DERBY_7122.java:37)
At a minimum, could someone explain (with CVE numbers if available) the
security risk incurred by probing the value of the Linux environment
variable SOURCE_DATE_EPOCH?
Here is a sample program which demonstrates this problem. This program
runs fine on Open JDK distros from java.net.
import java.io.PrintWriter;
import java.util.Properties;
/**
* Demonstrate that Properties.store() fails under a security manager on Ubuntu.
*/
public class DERBY_7122
{
private static final String PROPERTY_FILE_NAME =
"/tmp/derby-7122.properties";
private static final String SECURITY_POLICY_FILE_NAME =
"/tmp/derby-7122.policy";
private static final String SECURITY_POLICY_FILE_URL = "file:" +
SECURITY_POLICY_FILE_NAME;
private final static String POLICY_FILE_PROPERTY =
"java.security.policy";
private static final String SECURITY_FILE_CONTENTS =
"grant\n" +
"{\n" +
" permission java.io.FilePermission \"/tmp/-\",
\"read,write,delete\";\n" +
"};\n"
;
public static void main(String... args) throws Exception
{
// write the policy file
try (PrintWriter pw = new PrintWriter(SECURITY_POLICY_FILE_NAME))
{ pw.write(SECURITY_FILE_CONTENTS); }
// start up a security manager using the policy file we just wrote
System.setProperty( POLICY_FILE_PROPERTY, SECURITY_POLICY_FILE_URL );
System.setSecurityManager( new SecurityManager() );
// create a small Properties object
Properties props = new Properties();
props.setProperty("foo", "bar");
// write the properties to disk.
props.store(new PrintWriter(PROPERTY_FILE_NAME), "this fails on ubuntu
with JVMs at level 11 and higher");
}
}
** Affects: openjdk-16 (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/1939339
Title:
Security exception raised by java.util.Properties.store() when using
openjdk-16-jdk
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-16/+bug/1939339/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938050] [NEW] package linux-modules-extra-4.4.0-204-generic 4.4.0-204.236 failed to install/upgrade: package linux-modules-extra-4.4.0-204-generic is not ready for configuration cannot configure
Public bug reported: Initial 16.04 esm installation went without a hitch. Soon after, software update reported no new updates. Today, updater tried to do updates but discovered some could not be installed without doing a "partial upgrade" first. This error occured during the "partial upgrade", and reported that "package linux-modules- extra-4.4.0-204-generic is not ready for configuration cannot configure (current status 'half-installed')" ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-modules-extra-4.4.0-204-generic 4.4.0-204.236 ProcVersionSignature: Ubuntu 4.4.0-211.243-generic 4.4.262 Uname: Linux 4.4.0-211-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30+esm1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rick 2218 F.... pulseaudio /dev/snd/controlC0: rick 2218 F pulseaudio Date: Mon Jul 26 10:44:38 2021 DuplicateSignature: package:linux-modules-extra-4.4.0-204-generic:4.4.0-204.236 Processing triggers for systemd (229-4ubuntu21.31+esm1) ... dpkg: error processing package linux-modules-extra-4.4.0-204-generic (--configure): package linux-modules-extra-4.4.0-204-generic is not ready for configuration ErrorMessage: package linux-modules-extra-4.4.0-204-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=d04e18df-5384-4207-9dbd-71d59bfc4150 InstallationDate: Installed on 2016-06-24 (1857 days ago) InstallationMedia: Ubuntu-Server 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-211-generic root=UUID=f2fbe206-5d00-4b50-92e9-72f30cc9b61e ro acpi=force PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.32 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux Title: package linux-modules-extra-4.4.0-204-generic 4.4.0-204.236 failed to install/upgrade: package linux-modules-extra-4.4.0-204-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: SOX5820J.86A.0603.2010.1117.1506 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DX58OG dmi.board.vendor: Intel Corporation dmi.board.version: AAG10926-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrSOX5820J.86A.0603.2010.1117.1506:bd11/17/2010:svn:pn:pvr:rvnIntelCorporation:rnDX58OG:rvrAAG10926-203:cvn:ct3:cvr: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938050 Title: package linux-modules-extra-4.4.0-204-generic 4.4.0-204.236 failed to install/upgrade: package linux-modules-extra-4.4.0-204-generic is not ready for configuration cannot configure (current status 'half- installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928534] [NEW] [82DG, Realtek ALC287, Speaker, Internal] No sound at all
Public bug reported: PC：Lenovo YOGA 14C Intel EVO CPU：i5-1135G7 sound card： cat /proc/asound/cards 0 [sofhdadsp ]: sof-hda-dsp - sof-hda-dsp LENOVO-82DG-Yoga14cITL2021-LNVNB161216 others info： inxi -SMA System:Host: rick Kernel: 5.8.0-53-generic x86_64 bits: 64 Desktop: Gnome 3.36.7 Distro: Ubuntu 20.04.2 LTS (Focal Fossa) Machine: Type: Convertible System: LENOVO product: 82DG v: Yoga 14cITL 2021 serial: Mobo: LENOVO model: LNVNB161216 v: SDK0L77769 WIN serial: UEFI: LENOVO v: F5CN34WW date: 08/25/2020 Audio: Device-1: Intel driver: sof-audio-pci Sound Server: ALSA v: k5.8.0-53-generic This laptop was Windows10 before I install Ubuntu-OS，since I installed Ubuntu-OS，there is no sound in SPEAKER anymore, but it still works when I'm using headphone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rick 25469 F pulseaudio /dev/snd/pcmC0D0p: rick 25469 F...m pulseaudio /dev/snd/pcmC0D6c: rick 25469 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 15 15:51:48 2021 InstallationDate: Installed on 2021-05-12 (2 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82DG, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2020 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: F5CN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0L77769 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 14cITL 2021 dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrF5CN34WW:bd08/25/2020:br1.34:efr1.34:svnLENOVO:pn82DG:pvrYoga14cITL2021:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct31:cvrYoga14cITL2021: dmi.product.family: Yoga 14cITL 2021 dmi.product.name: 82DG dmi.product.sku: LENOVO_MT_82DG_BU_idea_FM_Yoga 14cITL 2021 dmi.product.version: Yoga 14cITL 2021 dmi.sys.vendor: LENOVO ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928534 Title: [82DG, Realtek ALC287, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1928534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928488] [NEW] Receiving error for /var/cache/apt/archives/fonts-noto-cjk compressed data is corrupt
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu ???@???-OMEN:~$ lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking inSoftware Center ???-OMEN:~$ apt-cache policy fonts-noto-cjk fonts-noto-cjk: Installed: 1:20190410+repack1-2 Candidate: 1:20201206-cjk+repack1-1 Version table: 1:20201206-cjk+repack1-1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu hirsute/main i386 Packages *** 1:20190410+repack1-2 100 100 /var/lib/dpkg/status ???@???-OMEN:~$ apt-cache policy fonts-noto-extra fonts-noto-extra: Installed: 20200323-1build1 Candidate: 20201225-1build1 Version table: 20201225-1build1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu hirsute/universe i386 Packages *** 20200323-1build1 100 100 /var/lib/dpkg/status 3) What you expected to happen I went to execute the upgrade from Ubuntu 21.03 to 21.04 and now cosistently receiving this error. 4) What happened instead Continually reciving this error whenever I run Software Update or APT UPGRADE ???@???-OMEN:~$ sudo apt upgrade -y Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: fonts-noto-cjk fonts-noto-extra 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/128 MB of archives. After this operation, 11.3 MB of additional disk space will be used. (Reading database ... 235767 files and directories currently installed.) Preparing to unpack .../fonts-noto-cjk_1%3a20201206-cjk+repack1-1_all.deb ... Unpacking fonts-noto-cjk (1:20201206-cjk+repack1-1) over (1:20190410+repack1-2) ... dpkg-deb (subprocess): decompressing archive '/var/cache/apt/archives/fonts-noto -cjk_1%3a20201206-cjk+repack1-1_all.deb' (size=55140504) member 'data.tar': lzma error: compressed data is corrupt dpkg-deb: error: subprocess returned error exit status 2 dpkg: error processing archive /var/cache/apt/archives/fonts-noto-cjk_1%3a202012 06-cjk+repack1-1_all.deb (--unpack): cannot copy extracted data for './usr/share/fonts/opentype/noto/NotoSerifCJK-Bo ld.ttc' to '/usr/share/fonts/opentype/noto/NotoSerifCJK-Bold.ttc.dpkg-new': unex pected end of file or stream Preparing to unpack .../fonts-noto-extra_20201225-1build1_all.deb ... Unpacking fonts-noto-extra (20201225-1build1) over (20200323-1build1) ... dpkg-deb (subprocess): decompressing archive '/var/cache/apt/archives/fonts-noto -extra_20201225-1build1_all.deb' (size=72415620) member 'data.tar': lzma error: compressed data is corrupt dpkg-deb: error: subprocess returned error exit status 2 dpkg: error processing archive /var/cache/apt/archives/fonts-noto-extra_20201225 -1build1_all.deb (--unpack): cannot copy extracted data for './usr/share/fonts/truetype/noto/NotoSerifGeorgi an-ExtraCondensed.ttf' to '/usr/share/fonts/truetype/noto/NotoSerifGeorgian-Extr aCondensed.ttf.dpkg-new': unexpected end of file or stream Errors were encountered while processing: /var/cache/apt/archives/fonts-noto-cjk_1%3a20201206-cjk+repack1-1_all.deb /var/cache/apt/archives/fonts-noto-extra_20201225-1build1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: apt 2.2.3 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 14 11:11:23 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: Upgraded to hirsute on 2021-05-14 (0 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Description changed: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - rvinger@rvinger-OMEN:~$ lsb_release -rd - Description: Ubuntu 21.04 - Release: 21.04 + ???@???-OMEN:~$ lsb_release -rd + Description: Ubuntu 21.04 + Release: 21.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking inSoftware Center - rvinger@rvinger-OMEN:~$ apt-cache policy fonts-noto-cjk - fonts-noto-cjk: -Installed: 1:20190410+repack1-2 - Candidate: 1:20201206-cjk+repack1-1 - Version table: -1:20201206-cjk+repack1-1 500 -
[Bug 1924685] Re: No sound output/input available after installing 21.04
Dell Latitude-9520 has the same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924685 Title: No sound output/input available after installing 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924932] Re: Nautilus default behaviour for executable scripts is poor
I agree I think the default behavior in Nautilus Preferences should be "Ask what to do" for "Executable Text Files" gsettings set org.gnome.nautilus.preferences executable-text-activation ask -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924932 Title: Nautilus default behaviour for executable scripts is poor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1924932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924717] Re: Internal speaker doesn't work after plug in a headset
** Description changed: [Summary] Internal speaker doesn't work after plug in a headset. In the meantime, audio for HDMI/Buletooth headset/wired headset are working fine. Only Internal speaker doesn't work. But internal speaker working well if not plug wired headset in. + CID:202010-28313 https://certification.canonical.com/hardware/202010-28313/ ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-14-generic 5.11.0-14.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: u 1512 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: u 1512 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 05:07:59 2021 InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) MachineType: Dell Inc. Latitude 5520 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=8bcd3f6a-d6e8-494d-93fa-6f720bf6e582 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.11.0-14-generic N/A - linux-backports-modules-5.11.0-14-generic N/A - linux-firmware 1.197 + linux-restricted-modules-5.11.0-14-generic N/A + linux-backports-modules-5.11.0-14-generic N/A + linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: 1132343535 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/13/2021:br1.2:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5520 dmi.product.sku: 0A21 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924717 Title: Internal speaker doesn't work after plug in a headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924717] [NEW] Internal speaker doesn't work after plug in a headset
Public bug reported: [Summary] Internal speaker doesn't work after plug in a headset. In the meantime, audio for HDMI/Buletooth headset/wired headset are working fine. Only Internal speaker doesn't work. But internal speaker working well if not plug wired headset in. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-14-generic 5.11.0-14.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1512 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 05:07:59 2021 InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) MachineType: Dell Inc. Latitude 5520 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=8bcd3f6a-d6e8-494d-93fa-6f720bf6e582 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: 1132343535 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/13/2021:br1.2:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5520 dmi.product.sku: 0A21 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924717 Title: Internal speaker doesn't work after plug in a headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921567] [NEW] ubi-partman crashed when choosing guided encrypted llvm installation
Public bug reported: In the Kubuntu installer I choose guided encrypted LVM install and after clicking "Install Now" ubi-partman crashes with exit code 141. Choosing "Guided - use entire disk" does work without a problem. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.12 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: KDE Date: Sat Mar 27 06:00:59 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210326) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute kubuntu ubiquity-21.04.12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921567 Title: ubi-partman crashed when choosing guided encrypted llvm installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1921567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880749] Re: Ubuntu 20.04: virtualenv: pep517 requires toml, but it isn't bundled in venvs
> What is the impact of this? It seems to happily install PEP 517 packages as-is. @Stefano sorry for the delay here. Installing PEP517 packages is fine without the patch, but building them (building a wheel) is where the issue comes in. If you need a concrete example, download the .tar.gz of any project that is normally capable of producing wheels, such as 'sampleproject' from pypi (https://pypi.org/project/sampleproject/#files). Activate a fresh virtualenv, untar it the .tar.gz, cd into the project, and run: python -m pep517.build --binary --out-dir dist . Before the patch mentioned above, it will fail with: ModuleNotFoundError: No module named 'toml' The .deb's from the SRU above get us a step closer but seem to still have an issue/traceback (see attachment which includes the commands to reproduce). It looks to be due to the vendored pytoml being listed in `lib/python3.8/site-packages/pip/_vendor/__init__.py` in the virtualenv. Whereas doing similar steps in a ubuntu:20.10 container (and installing pep517 explicitly in the virtualenv) produces a successful result. ** Attachment added: "reproducer using latest SRU build above" https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1880749/+attachment/5462853/+files/pep517.build.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880749 Title: Ubuntu 20.04: virtualenv: pep517 requires toml, but it isn't bundled in venvs To manage notifications about this bug go to: https://bugs.launchpad.net/virtualenv/+bug/1880749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880749] Re: python3 virtualenvs include (broken) bundled pip deps
The impact of the pep517 issue isn't too big of an issue for us- we can work around it (installing toml). The "impact" is that we have a test scenario which runs `pip install pep517` (reports already installed) and then tries to do `python -m pep517.build --binary --out-dir dist .` (which fails due to the toml issue). As mentioned, we can work around this by installing toml. I'm more worried about the broader issue in the report, that virtualenvs are dirty in the first place, this limits their utility :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880749 Title: python3 virtualenvs include (broken) bundled pip deps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1880749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880749] Re: python3 virtualenvs include (broken) bundled pip deps
Sorry, posted that from the wrong account, that comment was by me (the original bug reporter). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880749 Title: python3 virtualenvs include (broken) bundled pip deps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1880749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909605] [NEW] regex "look behind" not working
Public bug reported: I absolutely needed look behind functionality, and it would not work in kate and kwrite. I finally solved the problem by opening the text file in libreoffice writer -- look behind is working there. ** Affects: kate (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/1909605 Title: regex "look behind" not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kate/+bug/1909605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.
I switched display managers from lightdm to gdm and it fixed the issue sudo systemctl status display-manager sudo dpkg-reconfigure lightdm systemctl status gdm.service sudo apt install --reinstall ubuntu-session reboot machine Info about the issue: https://bbs.archlinux.org/viewtopic.php?id=150017 https://askubuntu.com/questions/1245071/cant-lock-screen-with-shortcut- on-ubuntu-20-04-gnome -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898153 Title: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.
I get false rt@sys76:~$ gsettings get org.gnome.desktop.lockdown disable-lock-screen false -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898153 Title: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898492] [NEW] mosquitto broker websockets no longer work
Public bug reported: Ubuntu 20.04.1 LTS mosquitto 1.6.9-1 I have a MQTT-brokered weather station, which sends realtime updates to a webpage using paho to do MQTT over websockets Everything worked fine until upgrade from bionic to focal The mosquitto broker continued to work fine, but the websocket component stopped functioning The relevant config section for mosquitto is like this: listener 4 ciphers EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH certfile /etc/nginx/ssl/acme/site.crt cafile /etc/nginx/ssl/acme/site.fullchain keyfile /etc/nginx/ssl/acme/site.key protocol websockets --- The first issue, netstat confirmed that mosquitto was NOT listening on IPv4, but only on IPv6. IPv6 is not routed to the internet in my installation, so that was an undesirable change in functionality. Adding this stanza: socket_domain ipv4 ...at least got netstat to report IPv4 listening on the websocket port But the websocket server was not reachable from the Internet. It just didn't work, on either Chrome or Firefox, on ubuntu or Windows, though strangely it worked with Mobile Safari on iOS. I made some discoveries... focal uses mosquitto 1.6.9, on top of libwebsockets 3.2.1 [libwebsockets15] bionic used mosquitto 1.4.15, on top of libwebsockets 2.0.3 [libwebsockets8] I pulled down mosquitto 1.6.9 source and the source for both libwebsockets versions from packages.ubuntu.com mosquitto 1.6.9 built against libwebsockets 3.2.1 misbehaved exactly as stock Ubuntu focal builds, which was reassuring mosquitto 1.6.9 built against libwebsockets 2.0.3 functioned properly, as 1.4.15 did on bionic Everything else was left identical. you may note in this report that /usr/sbin/mosquitto is altered - I have replaced it with my hand-built frankenversion, to get my server back in business Cheers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mosquitto 1.6.9-1 [modified: usr/sbin/mosquitto] ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 4 17:07:46 2020 InstallationDate: Installed on 2018-03-07 (942 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mosquitto UpgradeStatus: Upgraded to focal on 2020-10-04 (0 days ago) ** Affects: mosquitto (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898492 Title: mosquitto broker websockets no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mosquitto/+bug/1898492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.
Sure The Keyboard Shortcuts for Lock Screen is set to Ctrl+Alt+L Found in Settings -> Keyboard Shortcuts -> Lock screen -> Ctrl+Alt+L 1) I can't lock the screen using the (keybinding / shortcut) Ctrl+Alt+L https://i.imgur.com/VKiXvZV.png 2) I can lock the screen by clicking on the lock option but the screen doesn't go blank https://i.imgur.com/JDHEs2Q.png 3) Here's something that looks interesting I found in the journalctlr file Oct 02 19:18:52 sys76 gnome-shell[2577]: meta_window_raise: assertion '!window->override_redirect' failed Oct 02 19:18:52 sys76 gnome-shell[2577]: meta_window_lower: assertion '!window->override_redirect' failed Oct 02 19:18:56 sys76 gsd-media-keys[2742]: Couldn't lock screen: Cannot invoke method; proxy is for the well-known name org.gnome.ScreenSaver without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag 4) The full file is below ** Attachment added: "journalctl -b 0 > jour.txt file requested" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+attachment/5416816/+files/jour.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898153 Title: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.
1. The specific steps or actions you took that caused you to encounter the problem. -I tried to set the screen to lock at a specific interval and it doesn't lock Settings-> Privacy-> Screen Lock -> Automatic Screen Lock -> Enabled Settings-> Privacy-> Screen Lock -> Automatic Screen Lock -> 30 seconds -The screen doesn't go blank at all (option found under) Settings-> Privacy-> Screen Lock -> Blank screen Delay -> 1 minute 2. The behavior you expected. It should lock the screen and have the screen go blank but it doesn't 3. The behavior you actually encountered (in as much detail as possible). Nothing happens the screen doesn't lock or goes blank. Please also ensure that you include the release and flavour of Ubuntu that you are using. I upgraded from 18.04 to 20.04.1 using the sotware updater GUI rt@sys76:~$ uname -a Linux sys76 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux About me including the file-manager being nemo I was just trying to include everything I could think of to help out. If you need anything else let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898153 Title: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.
Should be: Settings-> Privacy-> Screen Lock -> Automatic Screen Lock Delay -> 30 seconds -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898153 Title: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.
The options for locking, blanking and shortcut keys are in the gnome- control-center ** Package changed: ubuntu => gnome-control-center (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898153 Title: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.
rt@sys76:~$ uname -a Linux sys76 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898153 Title: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1898153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898153] [NEW] I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.
Public bug reported: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time. I think this issue also effects the shortcuts not working also. I'm using nemo as my file manager I followed these instructions below https://itsfoss.com/install-nemo-file-manager-ubuntu/ ** 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/1898153 Title: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1898153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1579585] Re: muon freezes when we enter wrong password
Hey Jackson
Thanks for feeding back on this. I'll do an install and retry the repo
steps, hopefully its fixed.
Rick
On Fri, 25 Sep 2020 21:59 Jackson Doak, <1579...@bugs.launchpad.net>
wrote:
> I cannot reproduce this in 20.10, can someone reproduce in any remaining
> supported releases?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1579585
>
> Title:
> muon freezes when we enter wrong password
>
> Status in muon package in Ubuntu:
> Confirmed
>
> Bug description:
> If I run Muon Package Manager and from Properties menu try to
> Configure Software Sources I am asked for password. If I type wrong
> one the window with password field freezes and I can't do much except
> forcing it to close.
>
> This is only output if I start muon from console:
>
> soee@TachikomaDell:~$ muon
> Invalid pixmap specified.
> No frame loaded
> No frame loaded
> No frame loaded
> No frame loaded
> No frame loaded
> No frame loaded
> Couldn't find the releasechecker script ("/home/soee/.local/share",
> "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
> No frame loaded
> No frame loaded
> No frame loaded
> org.kde.kdesu: Daemon not safe (not sgid), not using it.
>
> Description:Ubuntu 16.04 LTS
> Release:16.04
>
> muon:
> Installed: 4:5.6.0-0ubuntu1
> Candidate: 4:5.6.0-0ubuntu1
> Version table:
>*** 4:5.6.0-0ubuntu1 500
> 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64
> Packages
> 100 /var/lib/dpkg/status
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1579585/+subscriptions
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579585
Title:
muon freezes when we enter wrong password
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1579585/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1891764] Re: USB port no longer "seen" and therefor cannot mount flash drive
Yes, I sent the report when I noticed the problem: I put a thumb drive in the port and got nothing; I tried a mouse, a mic, and USB headphones, all nothing. It's as if the port no longer exists. ᐧ On Tue, Sep 1, 2020 at 8:10 PM Kai-Heng Feng <1891...@bugs.launchpad.net> wrote: > Was the log uploaded when the issue happened? Not seeing anything > relevant in dmesg. > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1891764 > > Title: > USB port no longer "seen" and therefor cannot mount flash drive > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > This USB port had been working; filled USB Lexar flashdrive was then > removed and new flash drive inserted. That one was also immediately > recognized and mounted and then suddenly it disappeared from view. Now > the drive itself is not found and nothing is mounted or installed when > inserted into that port (neither flash drive nor an external mouse). > > Ubuntu Release 20.04.1 LTS' 64-bit GNOME 3.36.3 > > Rick Feldman > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: linux-image-5.4.0-42-generic 5.4.0-42.46 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.6 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: owner 1173 F pulseaudio > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Sat Aug 15 13:07:00 2020 > GvfsMonitorError: >This tool has been deprecated, use 'gio mount' instead. >See 'gio help mount' for more info. > GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. > HotplugNewDevices: > > HotplugNewMounts: > > InstallationDate: Installed on 2019-01-28 (564 days ago) > InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.3) > MachineType: ASUSTeK Computer Inc. U56E > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic > root=UUID=8071e842-b8c0-41c4-8950-6964dd47ced3 ro quiet splash vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-5.4.0-42-generic N/A >linux-backports-modules-5.4.0-42-generic N/A >linux-firmware1.187.2 > SourcePackage: linux > Symptom: storage > UdevMonitorLog: >monitor will print the received events for: >UDEV - the event which udev sends out after rule processing > UdisksMonitorLog: >Monitoring the udisks daemon. Press Ctrl+C to exit. >13:07:30.351: The udisks-daemon is running (name-owner :1.11). > UpgradeStatus: Upgraded to focal on 2020-05-10 (96 days ago) > dmi.bios.date: 12/21/2011 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: U56E.213 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: U56E > dmi.board.vendor: ASUSTeK Computer Inc. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK Computer Inc. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrU56E.213:bd12/21/2011:svnASUSTeKComputerInc.:pnU56E:pvr1.0:rvnASUSTeKComputerInc.:rnU56E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: > dmi.product.family: U > dmi.product.name: U56E > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK Computer Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891764/+subscriptions > -- *Rick Feldman* *Lecturer in Economics & Entrepreneurship* *Committee Chair and Coordinator * * Entrepreneurship, Organizations, and Society (EOS)* *Office 124, Skinner Hall* *Mount Holyoke College* *feld...@mtholyoke.edu * *CELL: 413-537-7059* *CAMPUS PHONE: 538-2518* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891764 Title: USB port no longer "seen" and therefor cannot mount flash drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891764] [NEW] USB port no longer "seen" and therefor cannot mount flash drive
Public bug reported: This USB port had been working; filled USB Lexar flashdrive was then removed and new flash drive inserted. That one was also immediately recognized and mounted and then suddenly it disappeared from view. Now the drive itself is not found and nothing is mounted or installed when inserted into that port (neither flash drive nor an external mouse). Ubuntu Release 20.04.1 LTS' 64-bit GNOME 3.36.3 Rick Feldman ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 1173 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 13:07:00 2020 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2019-01-28 (564 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: ASUSTeK Computer Inc. U56E ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=8071e842-b8c0-41c4-8950-6964dd47ced3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 13:07:30.351: The udisks-daemon is running (name-owner :1.11). UpgradeStatus: Upgraded to focal on 2020-05-10 (96 days ago) dmi.bios.date: 12/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U56E.213 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U56E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU56E.213:bd12/21/2011:svnASUSTeKComputerInc.:pnU56E:pvr1.0:rvnASUSTeKComputerInc.:rnU56E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: U dmi.product.name: U56E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891764 Title: USB port no longer "seen" and therefor cannot mount flash drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880784] Re: Gamemode sets incorrect default governor
** Changed in: gamemode (Ubuntu) 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/1880784 Title: Gamemode sets incorrect default governor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/1880784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880784] [NEW] Gamemode sets incorrect default governor
Public bug reported: gamemode 1.5.1-0ubuntu3 in Ubuntu 20.04 LTS Gamemode sets the incorrect default cpu governor which causes huge performance decreases in some scenarios. What I expect to happen: Gamemode on exit should set the cpu governor back to system default (ondemand in Ubuntu's case I believe) What happens instead: Gamemode currently will set the cpu governor to powersave when exiting Fix: /etc/gamemode.ini - Commenting out line `defaultgov=powersave` will correctly set the cpu governor back to the system default https://github.com/FeralInteractive/gamemode/commit/1c9cd2de5bd47c04a124445eb5b567f37ec3e85f A fix is currently in gamemode master, but I hope this can be addressed in Ubuntu 20.04 ** Affects: gamemode (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/1880784 Title: Gamemode sets incorrect default governor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/1880784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880749] [NEW] python3 virtualenvs include (broken) bundled pip deps
Public bug reported: On a clean 20.04 machine (or container), observe the following: apt-get update apt-get install -y python3-virtualenv python3 -m virtualenv foo && source foo/bin/activate pip list You will notice there are a plethora of extra packages in the virtual environment that should not normally be there, resulting in a dirty virtual environment. The packages listed here are those that are bundled with pip: https://github.com/pypa/pip/tree/master/src/pip/_vendor To make matters worse, the latest release of pip bundles incompatible versions of libraries. The net result is that `pip install pep517` will show that it is already installed, and but `import pep517` will result in an ImportError. This problem has been fixed in the Debian Testing/Unstable python- virtualenv package. Could the Ubuntu package backport these fixes? This is blocking Ansible supporting 20.04 officially, since the dirty virtualenvs are causing our tests to fail. https://github.com/ansible/ansible/issues/69203 ** Affects: python-virtualenv (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/1880749 Title: python3 virtualenvs include (broken) bundled pip deps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1880749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1876496] Re: Using /var/log/msmtp for all users is broken
My apologies. I mistakenly remembered that /etc/msmtp was installed with 'apt', but now realize that I had copied it from somewhere else recommended by a google search. There is a lot of misinformation about your excellent addition to Linux. So my issue is not a bug, but you might want to enhance the man page with a mention of how to properly log in /etc/msmtp. Thanks again. On 5/6/20 4:23 PM, Simon Déziel wrote: > On 2020-05-06 4:09 p.m., Rick Poleshuck wrote: >> I will try that. If that works, > It's what I use on all my machines. > >> then the bug is only in the documentation referencing /var/log/msmtp. > I couldn't find any reference to that file in either the man page or > upstream doc [*] so please let us know what that is mentioned. > > *: https://marlam.de/msmtp/msmtp.html > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876496 Title: Using /var/log/msmtp for all users is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msmtp/+bug/1876496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1876496] Re: Using /var/log/msmtp for all users is broken
I will try that. If that works, then the bug is only in the documentation referencing /var/log/msmtp. On 5/6/20 3:40 PM, Simon Déziel wrote: > The msmtp group was created to allow one to protect /etc/msmtprc from > regular users as it can contain plaintext passwords. If you join users > to that group, you lose the ability to protect those passwords. > > Have you considered using 'syslog LOG_MAIL'? It should have everyone's > logs ending in /var/log/mail.log without needing special > group/permission handling. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876496 Title: Using /var/log/msmtp for all users is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msmtp/+bug/1876496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876623] [NEW] clean install crashed macbook pro 2010
Public bug reported: installation error 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: Sun May 3 16:29:43 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_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.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 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876623 Title: clean install crashed macbook pro 2010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1876623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876496] [NEW] Using /var/log/msmtp for all users is broken
Public bug reported: I recently installed msmtp on my ubuntu 20.04 system and had to make the following changes so that different users could write to the one log file /var/log/msmtp/msmtp.log 1. Create /var/log/msmtp with group msmtp and setgid permissions drwxrws--- 2. Add acl to /var/log/msmtp - setfacl -Rdm g:msmtp:rwx /var/log/msmtp 3. Remove owner for /var/log/msmtp from apparmor file /etc/apparmor.d/usr.bin.msmtp 4. Document that msmtp users need to be in msmtp unix group. I consider this to be a bug rather than an enhancement because /var/log/msmtp is referenced in various places. Logging to users home directory works fine. Ubuntu release: Ubuntu 20.04 LTS Package: msmtp/focal,now 1.8.6-1 amd64 Thanks to the development team for this great product. Rick Poleshuck ** Affects: msmtp (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/1876496 Title: Using /var/log/msmtp for all users is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msmtp/+bug/1876496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876496] Re: Using /var/log/msmtp for all users is broken
As an enhancement, I also created a logrotate profile for the log file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876496 Title: Using /var/log/msmtp for all users is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msmtp/+bug/1876496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
20.04 beta still has this issue 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/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869358] [NEW] Gnome Workspaces Show Phantom Windows
Public bug reported: All workspaces in Gnome are showing phantom windows from all other workspaces. Steps to reproduce: 1 - Have any program(s) open on any workspace(s) - Switch to another workspace via the Activities Overview - Phantom window(s) from all other workspaces are there 2 - Switch workspace via ctrl+alt+up/down prevents phantom windows from appearing - Access the Activities Overview from there without switching workspace causes phantom windows to appear Xorg: Phantom windows cannot be interacted with Phantom windows prevents what is behind it from being interacted with Wayland: Phantom windows can be interacted with Phantom windows do not appear to be considered in "focus" Phantom windows' title bars don't get highlighted and the close button remains gray instead of orange ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 04:16:05 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-23 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869358 Title: Gnome Workspaces Show Phantom Windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869250] [NEW] grup would not go onto windows boot manager so I deleted windows boot manager so Ubuntu Boot might be Primary boot package on win 10 on Dell 3750.
Public bug reported: grup would not go onto windows boot manager so I deleted windows boot manager so Ubuntu Boot might be Primary boot package on win 10 on Dell 3750. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CasperVersion: 1.394 Date: Thu Mar 26 12:07:21 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869250 Title: grup would not go onto windows boot manager so I deleted windows boot manager so Ubuntu Boot might be Primary boot package on win 10 on Dell 3750. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1869250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857814] Re: "Show details" option broken for Snap apps
Broken in 20.04 also, but now it shows this error message "Sorry! There are no details for that application" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857814 Title: "Show details" option broken for Snap apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1857814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853830] Re: [MIR] gamemode
A 32bit build would be greatly useful for use with Lutris. Lutris has a gamemode toggle in their program, but it requires both 32bit and 64bit gamemode -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853830 Title: [MIR] gamemode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/1853830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864758] [NEW] "Show Details" For Snap Programs - Error
Public bug reported: For Snap programs if you right click and "Show Details" in Gnome it will open Ubuntu Software and come up with an error message "Sorry! There are no details for that application" Expected outcome when clicking "Show Details" should be Ubuntu Software being opened to the program's page ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 25 15:27:09 2020 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2019-10-23 (125 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gnome-software UpgradeStatus: Upgraded to focal on 2020-02-22 (3 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864758 Title: "Show Details" For Snap Programs - Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1864758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 Same problem on 18.04 with Sony headset: s [WI-1000X]# info 38:18:4C:04:C7:2A Device 38:18:4C:04:C7:2A (public) Name: WI-1000X Alias: WI-1000X Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Vendor specific (-deca-fade-deca-deafdecacaff) >>>UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: Vendor specific (7b265b0e-2232-4d45-bef4-bb8ae62f813d) UUID: Vendor specific (81c2e72a-0591-443e-a1ff-05f988593351) UUID: Vendor specific (931c7e8a-540f-4686-b798-e8df0a2ad9f7) UUID: Vendor specific (96cc203e-5068-46ad-b32d-e316f5e069ba) UUID: Vendor specific (b9b213ce-eeab-49e4-8fd9-aa478ed1b26b) UUID: Vendor specific (f8d1fbe4-7966-4334-8024-ff96c9330e15) Modalias: usb:v054Cp0C63d0411 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768625 Title: Bluetooth headset HSP/HFP mode not working in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
