[Bug 2079924] Re: Could not determine the upgrade An unresolvable problem occurred while calculating the upgrade
this is not a bug. It's telling you to undo packages added by a ppa before the upgrade. ppas can introduce versions and dependencies not expected by the upgrader, so it's warning you now rather than risking a broken update. the ppa-purge command will do that for you and most of the time it works. It can be tricky to get the syntax correct and make sure you don't have any update or package management tool open at the sametieme. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079924 Title: Could not determine the upgrade An unresolvable problem occurred while calculating the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2079924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2061687] Re: Snapshot doesn't work until camera is unplugged and plugged back in
For me, the problem in 24.04 is reproducible, but not after I add my user to the video group. On Mon, 12 Aug 2024 at 06:55, Rex Tsai <2061...@bugs.launchpad.net> wrote: > ** Tags added: oem-priority > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2065288). > https://bugs.launchpad.net/bugs/2061687 > > Title: > Snapshot doesn't work until camera is unplugged and plugged back in > > To manage notifications about this bug go to: > https://bugs.launchpad.net/oem-priority/+bug/2061687/+subscriptions > > -- Tim Richardson -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061687 Title: Snapshot doesn't work until camera is unplugged and plugged back in To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2061687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2045820] Re: firefox snap .desktop missing StartupWMClass
thanks this works for me, thanks for this. Probably an example for all the other snaps and appimages out there with the same problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2045820 Title: firefox snap .desktop missing StartupWMClass To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2073214] Re: hugepages causes permissions error [apparmor profile]
gt; > And I still can't see why my huge page guests work and yours do not, but > on the other I could now recreate this at least outside of qemu (there is > still works for me) > And with my instruction everyone can recreate this more easily now. > > Hence I'm subscribing the package maintainer and expert of apparmor as > he might be able to help much better suggesting which rule might be more > appropriate for such code (which now is much easier to understand). > > @JJ - how should we guard correctly in apparmor to allow usage of for > anonymous via memfd_create as allocation backend files? > > ** Also affects: apparmor (Ubuntu) >Importance: Undecided >Status: New > > ** Changed in: libvirt (Ubuntu) >Status: New => Incomplete > > ** Summary changed: > > - hugepages causes permissions error [apparmor profile] > + How to express memfd_create usage for anonymous files for huge pages > correctly in apparmor? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2073214 > > Title: > How to express memfd_create usage for anonymous files for huge pages > correctly in apparmor? > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2073214/+subscriptions > > -- Tim Richardson -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073214 Title: How to express memfd_create usage for anonymous files for huge pages correctly in apparmor? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2073214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073214] Re: hugepages causes permissions error [apparmor profile]
after enabling audit.log I get this message when the profile is in enforce mode type=AVC msg=audit(1721533808.319:1238): apparmor="DENIED" operation="truncate" class="file" profile="libvirt-465a6629-3167-43fc-93da-4c7ef837d863" name="/" pid=37291 comm="qemu-system-x86" requested_mask="w" denied_mask="w" fsuid=64055 ouid=64055^]FSUID="libvirt-qemu" OUID="libvirt-qemu" therefore,adding / rw, to the apparmor profile allows it to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073214 Title: hugepages causes permissions error [apparmor profile] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2073214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073214] Re: hugepages causes permissions error [apparmor profile]
One workaround is to do
aa-complain /etc/apparmor.d/libvirt/libvirt-
You may need to
touch /etc/apparmor.d/libvirt/libvirt-.files
because the .files may not be present, it is created and removed
dynamically by libvirt
Another workaround is to (accidentally) break the apparmor profile so it
can't be correctly parsed. I believe that in this case, libvirt launches
the VM anyway, but with no apparmor profile ... this is a bit sneaky.
So if you want to investigate apparmor, you have to see the
libirt- profile in aa-status. It defaults to enforce. If it's not
there, fix the problem.
With aa-enforce on, vm launch fails but there is no logging anywhere I can find
of a DENIED message.
So as an absolute apparmor beginner, I have no clues.
The best I can do is with strace
on the libvirtd process
root@elecgear:/home/tim# strace -f -p 4818 2>&1 | grep memfd
[pid 11307] memfd_create("test", MFD_CLOEXEC|MFD_ALLOW_SEALING) = 3
[pid 11307] memfd_create("test", MFD_CLOEXEC|MFD_HUGETLB) = 3
[pid 11307] memfd_create("memory-backend-memfd",
MFD_CLOEXEC|MFD_ALLOW_SEALING|MFD_HUGETLB|21
[Bug 2073214] Re: hugepages causes permissions error [invalid, page pool too small]
(earlier I had disabled apparmor while investigating another problem but I forgot that I did this, sorry) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073214 Title: hugepages causes permissions error [invalid, page pool too small] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2073214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073214] Re: hugepages causes permissions error [invalid, page pool too small]
I want to reopen this. I think there is an apparmor problem. Here is how to reproduce: I made a new Ubuntu 24.04 desktop to an external drive on my AMD laptop. I did all suggested updates, set up virt-manager and installed hugeadm Then I download the image for the 24.04 server and installed it in a VM, I gave it 2GB ram. Verify that it boots with default memory settings. Using hugeadm, I create 4000 pages of 2MiB pages. Then I edit the XML of the vm as above, including shared memory and It fails with the same permission error as reported initially. Then I sudo systemctl disable apparmor and restart Now the VM starts fine. Enabling apparmor and restarting results again in a VM that will not start with hugepages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073214 Title: hugepages causes permissions error [invalid, page pool too small] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2073214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073214] Re: hugepages causes permissions error [invalid, page pool too small]
** Changed in: libvirt (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073214 Title: hugepages causes permissions error [invalid, page pool too small] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2073214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073214] Re: hugepages causes permissions error [invalid, page pool too small]
I can't work out the process owning the reserved pages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073214 Title: hugepages causes permissions error [invalid, page pool too small] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2073214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2073442] Re: Failed to autostart VM: cannot open directory '/dev/dri': No such file or directory
This is output after reinstating the fix journalctl -b 0 | grep -i -e "\[drm\] Initialized" -e "Starting libvirtd.service" Jul 18 20:31:17 black kernel: [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0 Jul 18 20:31:21 black kernel: [drm] Initialized amdgpu 3.57.0 20150101 for :03:00.0 on minor 1 Jul 18 20:31:21 black kernel: [drm] Initialized amdgpu 3.57.0 20150101 for :6d:00.0 on minor 0 Jul 18 20:31:36 black systemd[1]: Starting libvirtd.service - libvirt legacy monolithic daemon... the delay is very large; there is no longer a sleep added. tim@black:~$ sudo systemctl status libvirtd ● libvirtd.service - libvirt legacy monolithic daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: enabled) Drop-In: /etc/systemd/system/libvirtd.service.d └─override.conf Active: active (running) since Thu 2024-07-18 20:31:36 AEST; 2min 34s ago TriggeredBy: ● libvirtd-admin.socket ● libvirtd-ro.socket ● libvirtd.socket Docs: man:libvirtd(8) https://libvirt.org/ Main PID: 8954 (libvirtd) Tasks: 27 (limit: 32768) Memory: 34.5M (peak: 39.8M) CPU: 358ms CGroup: /system.slice/libvirtd.service ├─8954 /usr/sbin/libvirtd --timeout 120 ├─9079 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper ├─9080 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper └─9189 /usr/libexec/virtiofsd --fd=34 -o source=/home/tim/Downloads Jul 18 20:31:36 black systemd[1]: Started libvirtd.service - libvirt legacy monolithic daemon. Jul 18 20:31:36 black dnsmasq[9079]: started, version 2.90 cachesize 150 Jul 18 20:31:36 black dnsmasq[9079]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset nftset auth cryptohas> Jul 18 20:31:36 black dnsmasq-dhcp[9079]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h Jul 18 20:31:36 black dnsmasq-dhcp[9079]: DHCP, sockets bound exclusively to interface virbr0 Jul 18 20:31:36 black dnsmasq[9079]: reading /etc/resolv.conf Jul 18 20:31:36 black dnsmasq[9079]: using nameserver 127.0.0.53#53 Jul 18 20:31:36 black dnsmasq[9079]: read /etc/hosts - 8 names Jul 18 20:31:36 black dnsmasq[9079]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 names Jul 18 20:31:36 black dnsmasq-dhcp[9079]: read /var/lib/libvirt/dnsmasq/default.hostsfile On Thu, 18 Jul 2024 at 20:27, Tim Richardson wrote: > This is a 22.04 upgraded to 24.04. I never once saw this behaviour prior > to the upgrade (I always use this VM, it is my development environment, so > I would have noticed). > > However, I was not using Ubuntu kernels with 22.04, I was using liquorix. > Currently I am on a stock Ubuntu 24.04 kernel. > > The ten second delay is not needed, it seems. I was just being very > cautious (or silly). I removed it. > > > It is not passthrough, it is an Ubuntu guest using libvirt graphics, > shared memory, 3d acceleration. > The hardware is a PC with AMD Ryzen4 7700X and one AMD graphics card. > > > this is the case without the fix, when autostart failed: > > > journalctl -b 0 | grep -i -e "\[drm\] Initialized" -e "Starting > libvirtd.service" > Jul 18 20:10:20 black kernel: [drm] Initialized simpledrm 1.0.0 20200625 > for simple-framebuffer.0 on minor 0 > Jul 18 20:10:23 black systemd[1]: Starting libvirtd.service - libvirt > legacy monolithic daemon... > Jul 18 20:10:25 black kernel: [drm] Initialized amdgpu 3.57.0 20150101 for > :03:00.0 on minor 1 > Jul 18 20:10:25 black kernel: [drm] Initialized amdgpu 3.57.0 20150101 for > :6d:00.0 on minor 0 > > > A second run: > > tim@black:~$ journalctl -b 0 | grep -i -e "\[drm\] Initialized" -e > "Starting libvirtd.service" > Jul 18 20:19:54 black kernel: [drm] Initialized simpledrm 1.0.0 20200625 > for simple-framebuffer.0 on minor 0 > Jul 18 20:19:57 black systemd[1]: Starting libvirtd.service - libvirt > legacy monolithic daemon... > Jul 18 20:19:59 black kernel: [drm] Initialized amdgpu 3.57.0 20150101 for > :03:00.0 on minor 1 > Jul 18 20:19:59 black kernel: [drm] Initialized amdgpu 3.57.0 20150101 for > :6d:00.0 on minor 0 > > > DRI > > tim@black:~$ ll /dev/dri > total 0 > drwxr-xr-x 3 root root140 Jul 18 20:19 ./ > drwxr-xr-x 22 root root 6680 Jul 18 20:20 ../ > drwxr-xr-x 2 root root120 Jul 18 20:19 by-path/ > crw-rw+ 1 root video 226, 0 Jul 18 20:19 card0 > crw-rw+ 1 root video 226, 1 Jul 18 20:19 card1 > crw-rw+ 1 root render 226, 128 Jul 18 20:19 ren
Re: [Bug 2073442] Re: Failed to autostart VM: cannot open directory '/dev/dri': No such file or directory
uest > needs as it knows its definition) waiting for that if and only as needed. > Or I might overlook something obvious which the subject matter experts > there might know and share. > > But for now, I'd appreciate if you could help my curiosity by providing > the above. > > [1]: https://github.com/systemd/systemd/issues/25408 > [2]: https://github.com/joukewitteveen/xlogin/issues/15 > [3]: https://gitlab.com/libvirt/libvirt > [4]: https://listman.redhat.com/mailman/listinfo/libvir-list > > P.S. @Sergio who usually looks at these - sorry for stealing those > interesting cases in my morning, bad timezone luck for you :-P. Do not > be concerned, you might deal with is long enough down the road :-) > > ** Bug watch added: github.com/systemd/systemd/issues #25408 >https://github.com/systemd/systemd/issues/25408 > > ** Bug watch added: github.com/joukewitteveen/xlogin/issues #15 >https://github.com/joukewitteveen/xlogin/issues/15 > > ** Changed in: libvirt (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2073442 > > Title: > Failed to autostart VM: cannot open directory '/dev/dri': No such file > or directory > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2073442/+subscriptions > > -- Tim Richardson -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073442 Title: Failed to autostart VM: cannot open directory '/dev/dri': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2073442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073442] [NEW] Failed to autostart VM: cannot open directory '/dev/dri': No such file or directory
Public bug reported: After upgrading from 22.04 to 24.04, a VM set to autostart is no longer starting. service status indicates the problem is /dev/dri not existing. tim@black:~$ systemctl status libvirtd ○ libvirtd.service - libvirt legacy monolithic daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: enabled) Drop-In: /etc/systemd/system/libvirtd.service.d └─override.conf Active: inactive (dead) since Thu 2024-07-18 13:36:29 AEST; 5min ago Duration: 2min 50.748s TriggeredBy: ● libvirtd-ro.socket ● libvirtd-admin.socket ● libvirtd.socket Docs: man:libvirtd(8) https://libvirt.org/ Process: 5454 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited, status=0/SUCCESS) Main PID: 5454 (code=exited, status=0/SUCCESS) Tasks: 2 (limit: 32768) Memory: 24.3M (peak: 37.1M) CPU: 369ms CGroup: /system.slice/libvirtd.service ├─5820 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper └─5821 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper Jul 18 13:33:38 black libvirtd[5454]: hostname: black Jul 18 13:33:38 black libvirtd[5454]: cannot open directory '/dev/dri': No such file or directory Jul 18 13:33:38 black libvirtd[5454]: internal error: Failed to autostart VM 'ubuntu24.04': cannot open directory '/dev/dri': No such file or directory Jul 18 13:33:44 black dnsmasq[5820]: reading /etc/resolv.conf Jul 18 13:33:44 black dnsmasq[5820]: using nameserver 127.0.0.53#53 Jul 18 13:33:44 black dnsmasq[5820]: reading /etc/resolv.conf Jul 18 13:33:44 black dnsmasq[5820]: using nameserver 127.0.0.53#53 Jul 18 13:36:29 black systemd[1]: libvirtd.service: Deactivated successfully. Jul 18 13:36:29 black systemd[1]: libvirtd.service: Unit process 5820 (dnsmasq) remains running after unit stopped. Jul 18 13:36:29 black systemd[1]: libvirtd.service: Unit process 5821 (dnsmasq) remains running after unit stopped. This override fixes it: /etc/systemd/system/libvirtd.service.d/override.conf [Unit] After=multi-user.target dev-dri.device [Service] ExecStartPre=/bin/sleep 10 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libvirt-daemon-system 10.0.0-2ubuntu8.2 ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8 Uname: Linux 6.8.0-38-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 18 13:41:03 2024 InstallationDate: Installed on 2023-08-10 (343 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: libvirt UpgradeStatus: Upgraded to noble on 2024-07-16 (2 days ago) modified.conffile..etc.apparmor.d.abstractions.libvirt-qemu: [modified] modified.conffile..etc.apparmor.d.usr.lib.libvirt.virt-aa-helper: [modified] modified.conffile..etc.apparmor.d.usr.sbin.libvirtd: [modified] modified.conffile..etc.init.d.apport: [modified] modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf'] mtime.conffile..etc.apparmor.d.abstractions.libvirt-qemu: 2024-07-16T10:47:15.550409 mtime.conffile..etc.apparmor.d.usr.lib.libvirt.virt-aa-helper: 2024-07-16T14:54:43.518479 mtime.conffile..etc.apparmor.d.usr.sbin.libvirtd: 2024-07-16T14:53:58.911077 mtime.conffile..etc.init.d.apport: 2024-04-23T21:30:10 ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073442 Title: Failed to autostart VM: cannot open directory '/dev/dri': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2073442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073214] Re: hugepages causes permissions error
** Changed in: libvirt (Ubuntu) Status: Incomplete => Invalid ** Summary changed: - hugepages causes permissions error + hugepages causes permissions error [invalid, page pool too small] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073214 Title: hugepages causes permissions error [invalid, page pool too small] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2073214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2073214] Re: hugepages causes permissions error
u) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2073214 > > Title: > hugepages causes permissions error > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2073214/+subscriptions > > -- Tim Richardson -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073214 Title: hugepages causes permissions error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2073214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073214] Re: hugepages causes permissions error
When I reboot I see a directory libvirt and then libvert/qemu tim@black:/dev/hugepages$ tree -pug [drwxrwx--t root hugetlb ] . └── [drwxr-xr-x root root] libvirt └── [drwxr-xr-x root root] qemu 3 directories, 0 files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073214 Title: hugepages causes permissions error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2073214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073214] Re: hugepages causes permissions error
** Description changed:
Today I upgraded from 22.04 to 24.04
+
+ 10.0.0-2ubuntu8.2
+
I have a VM with 16GB of hugepages allocated to it.
This no longer works.
I can not defeat the virtual machine start up error (from virtual
manager):
Error starting domain: internal error: QEMU unexpectedly closed the
monitor (vm='ubuntu24.04'): 2024-07-16T04:54:51.443751Z qemu-
system-x86_64: failed to resize memfd to 17179869184: Permission denied
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 1402, in
startup
self._backend.create()
File "/usr/lib/python3/dist-packages/libvirt.py", line 1379, in create
raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: internal error: QEMU unexpectedly closed the monitor
(vm='ubuntu24.04'): 2024-07-16T04:54:51.443751Z qemu-system-x86_64: failed to
resize memfd to 17179869184: Permission denied
I have done this:
sudo aa-complain /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper
sudo aa-complain /etc/apparmor.d/usr.sbin.libvirtd
While I did not have to take any such steps with 22.04, I have mounted
sudo mount -t hugetlbfs -o mode=1770,gid=kvm none /dev/hugepages
and these permissions are observed:
root@black:/etc/apparmor.d# ls -ld /dev/hugepages
drwxrwx--t 3 root kvm 0 Jul 16 14:47 /dev/hugepages
root@black:/etc/apparmor.d# id libvirt-qemu
uid=64055(libvirt-qemu) gid=109(kvm)
groups=109(kvm),139(libvirt),64055(libvirt-qemu),1002(hugetlb)
I have edited /etc/libvirt/qemu.conf to uncomment the mount point of the
hugepages, even though this was not necessary with 22.04
log entries don't add anything (for me):
2024-07-16T04:54:51.443751Z qemu-system-x86_64: failed to resize memfd to
17179869184: Permission denied
2024-07-16 04:54:51.477+: shutting down, reason=failed
-
kernel stuff:
# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-6.8.0-38-generic
root=UUID=756dca1f-0eb5-440e-a84e-dfa56a27e355 ro quiet splash zswap.enabled=1
zswap.compressor=lz4 zswap.zpool=z3fold mitigations=off vt.handoff=7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073214
Title:
hugepages causes permissions error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2073214/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073214] [NEW] hugepages causes permissions error
Public bug reported:
Today I upgraded from 22.04 to 24.04
10.0.0-2ubuntu8.2
I have a VM with 16GB of hugepages allocated to it.
This no longer works.
I can not defeat the virtual machine start up error (from virtual
manager):
Error starting domain: internal error: QEMU unexpectedly closed the
monitor (vm='ubuntu24.04'): 2024-07-16T04:54:51.443751Z qemu-
system-x86_64: failed to resize memfd to 17179869184: Permission denied
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 1402, in
startup
self._backend.create()
File "/usr/lib/python3/dist-packages/libvirt.py", line 1379, in create
raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: internal error: QEMU unexpectedly closed the monitor
(vm='ubuntu24.04'): 2024-07-16T04:54:51.443751Z qemu-system-x86_64: failed to
resize memfd to 17179869184: Permission denied
I have done this:
sudo aa-complain /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper
sudo aa-complain /etc/apparmor.d/usr.sbin.libvirtd
While I did not have to take any such steps with 22.04, I have mounted
sudo mount -t hugetlbfs -o mode=1770,gid=kvm none /dev/hugepages
and these permissions are observed:
root@black:/etc/apparmor.d# ls -ld /dev/hugepages
drwxrwx--t 3 root kvm 0 Jul 16 14:47 /dev/hugepages
root@black:/etc/apparmor.d# id libvirt-qemu
uid=64055(libvirt-qemu) gid=109(kvm)
groups=109(kvm),139(libvirt),64055(libvirt-qemu),1002(hugetlb)
I have edited /etc/libvirt/qemu.conf to uncomment the mount point of the
hugepages, even though this was not necessary with 22.04
log entries don't add anything (for me):
2024-07-16T04:54:51.443751Z qemu-system-x86_64: failed to resize memfd to
17179869184: Permission denied
2024-07-16 04:54:51.477+: shutting down, reason=failed
kernel stuff:
# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-6.8.0-38-generic
root=UUID=756dca1f-0eb5-440e-a84e-dfa56a27e355 ro quiet splash zswap.enabled=1
zswap.compressor=lz4 zswap.zpool=z3fold mitigations=off vt.handoff=7
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- hugespages causes permissions error
+ hugepages causes permissions error
** Description changed:
Today I upgraded from 22.04 to 24.04
I have a VM with 16GB of hugepages allocated to it.
This no longer works.
I can not defeat the virtual machine start up error (from virtual
manager):
Error starting domain: internal error: QEMU unexpectedly closed the
monitor (vm='ubuntu24.04'): 2024-07-16T04:54:51.443751Z qemu-
system-x86_64: failed to resize memfd to 17179869184: Permission denied
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 1402, in
startup
- self._backend.create()
- File "/usr/lib/python3/dist-packages/libvirt.py", line 1379, in create
- raise libvirtError('virDomainCreate() failed')
+ 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 1402, in
startup
+ self._backend.create()
+ File "/usr/lib/python3/dist-packages/libvirt.py", line 1379, in create
+ raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: internal error: QEMU unexpectedly closed the monitor
(vm='ubuntu24.04'): 2024-07-16T04:54:51.443751Z qemu-system-x86_64: failed to
resize memfd to 17179869184: Permission denied
-
I have done this:
sudo aa-complain /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper
sudo aa-complain /etc/apparmor.d/usr.sbin.libvirtd
-
- While I did not have to take any such steps with 22.04, I have mounted
-
+ While I did not have to take any such steps with 22.04, I have mounted
sudo mount -t hugetlbfs -o mode=1770,gid=kvm none /dev/hugepages
and these permissions are observed:
[Bug 2073210] [NEW] 22.04 -> 24.04, pkg virtiofsd was not installed
Public bug reported: I upgraded 22.04 to 24.04 today on a workstation PC which runs VMs managed by virtual-manager VMs using the "hardware device" filesystem did not start. The package virtiofsd needed to be installed. Has this been split into a separate package from some other package in 24.04 with resepct to 22.04? I think it should be installed if the libvirt family of packages is installed. ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073210 Title: 22.04 -> 24.04, pkg virtiofsd was not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2073210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068789] Re: VA-API not available to VLC .deb (flatpak works) in 24.04
** Description changed: I have hardware decoding working with mpv, evidence is nvtop. Hardware is AMD 7840U igpu. - test file is a vp9 encoding. + test file is a vp9 encoding. - vlc .deb does not show VA-API has a decoding option + vlc .deb does not show VA-API as a decoding option - However, the flatpak package works. - The snap package does not work. + However, the flatpak package works. + The snap package does not work. Ubuntu 24.04 This was reported by another user here https://www.reddit.com/r/Ubuntu/comments/1d8m8lj/comment/l7ix1oo/?context=3 and I confirm it. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: vlc 3.0.20-3build6 Uname: Linux 6.9.3-060903-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 8 13:45:29 2024 InstallationDate: Installed on 2024-01-07 (153 days ago) InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: vlc UpgradeStatus: Upgraded to noble on 2024-04-11 (57 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068789 Title: VA-API not available to VLC .deb (flatpak works) in 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/2068789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068789] [NEW] VA-API not available to VLC .deb (flatpak works) in 24.04
Public bug reported: I have hardware decoding working with mpv, evidence is nvtop. Hardware is AMD 7840U igpu. test file is a vp9 encoding. vlc .deb does not show VA-API has a decoding option However, the flatpak package works. The snap package does not work. Ubuntu 24.04 This was reported by another user here https://www.reddit.com/r/Ubuntu/comments/1d8m8lj/comment/l7ix1oo/?context=3 and I confirm it. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: vlc 3.0.20-3build6 Uname: Linux 6.9.3-060903-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 8 13:45:29 2024 InstallationDate: Installed on 2024-01-07 (153 days ago) InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: vlc UpgradeStatus: Upgraded to noble on 2024-04-11 (57 days ago) ** Affects: vlc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068789 Title: VA-API not available to VLC .deb (flatpak works) in 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/2068789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061584] Re: Rendering issues in VirtualBox with 3d on (GTK ngl backend)
the rendering problem is identical when using virt-manager with the virtio video driver with open gl 3D accel enabled. persists even in latest kisak fresh mesa. workaround is export GSK_RENDERER=gl in ~/.profile or where ever you set your environment variables. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061584 Title: Rendering issues in VirtualBox with 3d on (GTK ngl backend) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061118] Re: Rendering issues in virtual machines (GTK ngl backend)
Please note that for virtio/virt-manager, setting this envionment variable in ~/.profile may be a workaround. export GSK_RENDERER=gl this at least fixes Files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in virtual machines (GTK ngl backend) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061118] Re: Rendering issues in virtual machines (GTK ngl backend)
This affects qemu/kvm too. On vanilla 22.04 host, gtk4 apps (e.g. Files) from 24.04 do not render properly (with 3D/openGL enabled) via virt-manager mesa in the 24.04 guest is 24.0.5-1 Fedora 40 guest with all updates has the same problem (open files apps and view files in list view, for example) Both hosts I see this on use AMD graphics. Wayland in host and guest. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in virtual machines (GTK ngl backend) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058227] Re: Crash during upgrade from Mantic to Noble due to Python 3.12
the issues in Comment #10 appear to be closed, and they are not mentioned anyway on https://discourse.ubuntu.com/t/noble-numbat-24-04-release-status-tracking/44043 so it is confusing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058227 Title: Crash during upgrade from Mantic to Noble due to Python 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/2058227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061687] Re: Snapshot doesn't work until camera is unplugged and plugged back in
For me the fix included the new version of pipewire (now released in 24.04) AND adding my user to the video group -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061687 Title: Snapshot doesn't work until camera is unplugged and plugged back in To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2061687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060390] Re: Snapshot No Camera Found
I confirm the findings of @corradoventu : fixing this requires both pipewire1.0.5-1 AND adding my user to group video. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060390 Title: Snapshot No Camera Found To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/2060390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065288] Re: gnome 46 camera app requires systemctl --user restart pipewire
*** This bug is a duplicate of bug 2061687 *** https://bugs.launchpad.net/bugs/2061687 ** This bug has been marked a duplicate of bug 2061687 Snapshot doesn't work until camera is unplugged and plugged back in -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065288 Title: gnome 46 camera app requires systemctl --user restart pipewire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2065288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065288] Re: gnome 46 camera app requires systemctl --user restart pipewire
** Package changed: ubuntu => pipewire (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065288 Title: gnome 46 camera app requires systemctl --user restart pipewire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2065288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065288] [NEW] gnome 46 camera app requires systemctl --user restart pipewire
Public bug reported: In ubuntu 24.40 the camera app will not see my laptop camera until I do this: systemctl --user restart pipewire this is required in every log in. The camera problem also affects other usage, such as using the laptop camera in google meet via firefox. It is probably a pipewire problem. I don't know where to report it. see also: https://ubuntuforums.org/showthread.php?t=2497176&p=14187369 My laptop is thinkpad T14 P14S This problem did not exist in 23.10 ** 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/2065288 Title: gnome 46 camera app requires systemctl --user restart pipewire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2065288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c
@sbeattie I tested the package you built for 22.04 and it fixes the problem 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/2060354 Title: Segfaults and assertion failures in Xorg's render/glyph.c To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/2060354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c
@sbeattie It's broken in mantic too. In xwayland, the window dies. in xorg, the session crashes, badly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060354 Title: Segfaults and assertion failures in Xorg's render/glyph.c To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/2060354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c
Yeah, for me it crashed 100% of the time with no changes, and removing a configuration file (which among other things removed my non-default preference for grayscale antialias) completely stopped the crashing. This is in a kvm/qemu VM. So from my perspective, and from a few others users, it looks like the cause and a good workaround. But other people in the set of JetBrains tickets report intermittent, unpredictable crashing that doesn't benefit from such a settings change. I think think upstream is talking about race conditions. So far in the bug report (the Ubuntu one) I don't understand what the proposed course of action is. I think this is the upstream bug report: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1659 ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1659 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1659 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060354 Title: Segfaults and assertion failures in Xorg's render/glyph.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2060354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c
for what it's worth, JetBrains bug reports find that the problem is triggered by requesting grayscale anti-aliasing. https://youtrack.jetbrains.com/issue/IDEA-350864/Idea.sh-abort-X-window -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060354 Title: Segfaults and assertion failures in Xorg's render/glyph.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2060354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971434] Re: Display powersave only blanks, but does not turn off
I use the wayland session. I sort of have this bug. The screens do power off, but then the backlights resume. It is still a blank screen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974268] [NEW] Does this package conflict with systemd oom?
Public bug reported: Ubuntu now defaults to systemd oom handling. Is there a way to warn an upgrade user who has earlyoom installed that the two are in conflict (assuming that they are). ** Affects: earlyoom (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/1974268 Title: Does this package conflict with systemd oom? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/earlyoom/+bug/1974268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971112] Re: File picker gets bigger more and more each time!
I see this in the xorg session in the flatpak firefox save downloads dialog, for instance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971112 Title: File picker gets bigger more and more each time! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1971112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
see also https://bugzilla.redhat.com/show_bug.cgi?id=2072070 for lengthy discussion. ** Bug watch added: Red Hat Bugzilla #2072070 https://bugzilla.redhat.com/show_bug.cgi?id=2072070 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967437] Re: does not detect battery discharge 22.04 beta thinkpad x1 g9
Sorry, out of habit I installed the snap. The .deb works fine, so I am using that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967437 Title: does not detect battery discharge 22.04 beta thinkpad x1 g9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerstat/+bug/1967437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
Ubuntu 22.04. I still have this problem intel-media-va-driver 22.3.0 tigerlake laptop $ apt-cache show intel-media-va-driver Package: intel-media-va-driver Architecture: amd64 Version: 22.3.0+dfsg1-1 tim@ochre:~$ vainfo libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_10 libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit tim@ochre:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966571 Title: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1966571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967437] [NEW] does not detect battery discharge 22.04 beta thinkpad x1 g9
Public bug reported: On Tigerlake Thinkpad X1, ubuntu 22.04 beta powerstat -d 0 reports Device is not discharging, cannon measure power usage. this worked previously, including with the snap installed on Fedora 35 kernel is 5.15.0-23-generic ** Affects: powerstat (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/1967437 Title: does not detect battery discharge 22.04 beta thinkpad x1 g9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerstat/+bug/1967437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952107] Re: Google Contacts API Deprecated
** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952107] Re: Google Contacts API Deprecated
(... Ubuntu 21.10) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952107] Re: Google Contacts API Deprecated
I used proposed-updates today to get the latest evolution, and contact sync works again. So 3.40.4-1ubuntu2 works. (amd64 arch) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938096] Re: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend
I have this laptop. Bug happens on S3 suspend, much better on modern standby (once it took two minutes or so for the touchpad to resume, every other time it has worked). Modern suspend does not use much battery. Mine slept for 8:20h last night and the battery percentage declined from 96% to 94%. my kernel is 5.13 and the session is Wayland gnome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938096 Title: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise
It doesn't corrupt boots. It's inconvenient. On Wed, 1 Sept 2021, 15:31 martin, <1396...@bugs.launchpad.net> wrote: > This sounds like a massive, GIGANTIC bug which is corrupting people's > boot setups. It's a wonder that it hasn't been fixed after SEVEN YEARS. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1396379 > > Title: > installer uses first EFI system partition found even when directed > otherwise > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396379 Title: installer uses first EFI system partition found even when directed otherwise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927767] Re: All apps crashed in my X11 session, then terminal console crashed, reboot failed
No data available from (1) or (2) and the problem has not reoccurred. I have commented line 23 of crashdb.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927767 Title: All apps crashed in my X11 session, then terminal console crashed, reboot failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1927767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927767] [NEW] All apps crashed in my X11 session, then terminal console crashed, reboot failed
Public bug reported: The reboot failed with many services that could not stop. I think there may have been a crash in the network stack. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim4093 F pulseaudio /dev/snd/controlC2: tim4093 F pulseaudio /dev/snd/controlC0: tim4093 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 8 03:07:12 2021 InstallationDate: Installed on 2020-11-22 (166 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE WIFI ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax mitigations=off crashkernel=192M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux StagingDrivers: ashmem_linux UpgradeStatus: Upgraded to hirsute on 2021-04-23 (14 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33g dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33g:bd03/25/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITEWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITEWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE WIFI dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute staging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927767 Title: All apps crashed in my X11 session, then terminal console crashed, reboot failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926289] Re: pdfarranger TypeError: only pages can be inserted
The flathub version is fixed too. Please see upstream bug report https://github.com/pdfarranger/pdfarranger/issues/478 which is closed as fixed in new release. ** Bug watch added: github.com/pdfarranger/pdfarranger/issues #478 https://github.com/pdfarranger/pdfarranger/issues/478 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926289 Title: pdfarranger TypeError: only pages can be inserted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdfarranger/+bug/1926289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925989] Re: after upgrade to 21.04, zram only 1 device of 256MB on 64 GB system
Update. I had zram-tools installed as well. Or at least, I have it after the upgrade to 21.04 I removed it and zram-config, and reinstalled zram-config, and it works fine. However, this still doesn't make much sense: if they were both installed previously, why did it stop working? I stepped through the /etc/bin/init-zram-swapping and works perfectly well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925989 Title: after upgrade to 21.04, zram only 1 device of 256MB on 64 GB system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1925989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925989] [NEW] after upgrade to 21.04, zram only 1 device of 256MB on 64 GB system
Public bug reported: Under 20.10, my machine of 64GB had 8 zram devices of 2GB each. After the 21.04 upgrade, zram was still configured, but now with one 1 device of 256MB. dpkg-reconfigure did not fix this purge and reinstall did not fix this. $ cat /proc/swaps FilenameTypeSizeUsed Priority /dev/zram0 partition 262140 0 100 $ lsblk -d | grep -e ^NAME -e disk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT zram0 252:00 256M 0 disk [SWAP] nvme0n1 259:00 953.9G 0 disk nvme1n1 259:40 931.5G 0 disk This is output from my system prior to upgrade (that is under 20.10) $ lsblk -d | grep -e ^NAME -e disk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOIN zram0 252:0016M 0 disk [SWAP] zram1 252:10 2G 0 disk [SWAP] zram2 252:2016M 0 disk [SWAP] zram3 252:30 2G 0 disk [SWAP] zram4 252:4016M 0 disk [SWAP] zram5 252:50 2G 0 disk [SWAP] zram6 252:60 2G 0 disk [SWAP] zram7 252:7016M 0 disk [SWAP] zram8 252:80 2G 0 disk [SWAP] zram9 252:9016M 0 disk [SWAP] zram10 252:10 0 2G 0 disk [SWAP] zram11 252:11 016M 0 disk [SWAP] zram12 252:12 0 2G 0 disk [SWAP] zram13 252:13 0 2G 0 disk [SWAP] zram14 252:14 016M 0 disk [SWAP] zram15 252:15 0 2G 0 disk [SWAP] ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: zram-config 0.6 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 24 15:47:18 2021 Dependencies: InstallationDate: Installed on 2020-11-22 (152 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: zram-config UpgradeStatus: Upgraded to hirsute on 2021-04-23 (0 days ago) ** Affects: zram-config (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/1925989 Title: after upgrade to 21.04, zram only 1 device of 256MB on 64 GB system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1925989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise
Note: you don't have to physically remove the internal drive. You simple need to temporarily remove the boot flag from the EFI partition, do the install and the turn on the boot flag again. Very easy. I document it here: https://askubuntu.com/a/1056079/152287 On Sun, 7 Mar 2021 at 02:46, Andrew Bauer <1396...@bugs.launchpad.net> wrote: > This appears to be the problem I ran into with Ubuntu Desktop 20.10 as > reported here: > > https://askubuntu.com/questions/1321431/ubuntu-desktop-20-10-on-usb-flash-drive-boots-only-on-original-computer > > If it is the same problem (and not a limitation with the latest [but > old] ASUS N551VW BIOS) then please escalate this ABOVE CRITICAL. > > I'm sure a lot more Windows 10 users would delight to have a bootable > Ubuntu system on a USB Flash Drive (or an externally USB-connected SSD, > e.g. in an ICY BOX) if the "Device for boot loader installation" set to > /dev/sdb would really write something there. I also noticed a couple of > error messages during booting - one was only a few seconds on the screen > so I was not able to capture it. I will post what I have (in AskUbuntu) > if it is of any assistance to you. My laptop works perfectly (error- > free) with Windows 10. > > Apparently the workaround is to remove Disk 0 (Windows 10 drive) from > the laptop. I will give this a try though I doubt that the casual user > would go so far as to unscrew the back cover of their laptop to remove > their HD/SSD. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1396379 > > Title: > installer uses first EFI system partition found even when directed > otherwise > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions > -- Tim Richardson -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396379 Title: installer uses first EFI system partition found even when directed otherwise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
Google has not removed API access. They have stopped a google key from working. It works fine, as far as I can tell. But you need to get your own key. The well known PPA with VAAPI, https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev, has always worked like this. I use Fedora on another machine, and with my own keys, Chromium works exactly as before. On Sat, 6 Mar 2021 at 03:00, Michel-Ekimia <1816...@bugs.launchpad.net> wrote: > Sorry to use this bug report as a forum but IMO it is useless to spend > more time on chromium. > > Ubuntu & users should define a Blink-based open source browser like > Brave that could be supported nicely upstream unlike whats google is > doing by removing sync API access with google services > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1816497 > > Title: > [snap] vaapi chromium no video hardware decoding > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions > -- Tim Richardson -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise
You don't have to unplug them. The minimal workaround, and what I always use, is before the install, unflag the EFI partitions of drives you don't want to target. Somewhere in this bug report I have my tips on this, and I also wrote it up here https://askubuntu.com/a/1056079/152287 On Sat, 30 Jan 2021 at 09:09, Robert Bernecky <1396...@bugs.launchpad.net> wrote: > I have lost about a month of my time with this bug!! > I thought I was doing something wrong with UUID or GPT vs MBR or ZFS or ... > It creamed my live benchmark system that I had spent considerable time > installing and customizing. > > Just today, I stumbled onto this archaic bug report, which remains unfixed > after seven years! > > Since my system has several nvme drives, I can't just unplug them to work > around the problem. > > > I agree that this bug is critical, not just "high". > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1396379 > > Title: > installer uses first EFI system partition found even when directed > otherwise > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions > -- Tim Richardson -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396379 Title: installer uses first EFI system partition found even when directed otherwise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736222] Re: speech-dispatcher distorts all sound
I just installed Ubuntu 20.10 on a machine that was running Pop!os 20.04
and 20.10 (a fairly new AMD Ryzen desktop system, different to the
machine I had the problem on earlier, which was a laptop). Not 24 hours
later, this problem again. I thought there was something wrong with Team
app ('bloody microsoft') but then my next meeting in Google Meet had the
same problem. And YouTube.
Then I remembered this.
This time I just removed speech-dispatcher. Maybe it is not installed by
default on pop, not sure. An ugly papercut.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736222
Title:
speech-dispatcher distorts all sound
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736222] Re: speech-dispatcher distorts all sound
My sound control panel reports three speech-dispatcher entries in Volume Levels. I don't know why. My session is about two days old and I haven't had any instance of distortion, so the workaround referred to in my previous comment, a config change, may be a good idea for package maintainers to implement. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736222 Title: speech-dispatcher distorts all sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
If you want to test this, force YouTube to serve H264, which your card supports judging by the vainfo results. A 4k 60fps YouTube video won't be in a codec your hardware can handle, I guess. There are 'h264ify' extensions for Chromium. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736222] Re: speech-dispatcher distorts all sound
I will try this workaround/config change: https://github.com/brailcom/speechd/issues/198#issuecomment-619605269 ** Bug watch added: github.com/brailcom/speechd/issues #198 https://github.com/brailcom/speechd/issues/198 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736222 Title: speech-dispatcher distorts all sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736222] Re: speech-dispatcher distorts all sound
This bug started affecting me in the past week although I've been on 20.04 since launch. I have removed the packages including orca. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736222 Title: speech-dispatcher distorts all sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878279] Re: Touchpad not recognized on Lenovo Ideapad 5 14IIL05 81YH
device is an IdeaPad 5 14 (14ARE05) with a Ryzen 5 4600 Now on kernel 5.8 observation is that the touchpad sometimes doesn't work. So far, shutdown and remove AC then restart fixes it every time. This was true on 5.7 too. Something goes wrong with hardware initialisation? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: Touchpad not recognized on Lenovo Ideapad 5 14IIL05 81YH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1878279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)
@olepet I have 14ARE05 too, same symptoms. It seems the hardware is different, we need a new bug. I see no elan modules loaded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881319 Title: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
I tested this today, and with HDMI connection, I no longer have the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876636] Re: 20.04 Freeze on startup when HDMI plugged in
*** This bug is a duplicate of bug 1872159 *** https://bugs.launchpad.net/bugs/1872159 ** This bug is no longer a duplicate of bug 1874194 Ubuntu 20.04 HDMI connected, no boot ** This bug has been marked a duplicate of bug 1872159 booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876636 Title: 20.04 Freeze on startup when HDMI plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1876636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
*** This bug is a duplicate of bug 1872159 *** https://bugs.launchpad.net/bugs/1872159 ** This bug has been marked a duplicate of bug 1872159 booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874194 Title: Ubuntu 20.04 HDMI connected, no boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844641] Re: Login screen not keyboard accessible after using NoMachine
I experience this in 20.04 as well: remote session with Workstation, after termination the greeter on this host does not respond to the mouse. The keyboard allows access to virtual terminals and ctrl-alt- delete reboots. Hopefully nomachine has an answer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844641 Title: Login screen not keyboard accessible after using NoMachine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1844641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise
Easiest workaround is to use gparted or similar to remove the EFI/boot flag on existing EFI partitions before the install. On Sun, 10 May 2020 at 19:55, Christian Nassau <1396...@bugs.launchpad.net> wrote: > I think I have just been hit by that bug too: fresh install of (X)Ubuntu > 20.04 on a new computer with a new SSD, which also happened to have an > old HDD with an existing EFI boot paritition. I chose the "expert" > option for the partitioning dialog in install and explicitly specified > the new SSD as the intended boot device. The install used the existing > EFI on the old HDD instead. > > Recovering was not easy (with hindsight there might have been better > options): I physically removed (!) the HDD, installed a 2nd copy of > Ubuntu 20.04 on a new separate partition on the SSD, again in "expert > mode". During installation I was warned that there was no EFI partition > and the system would be unusable, so I manually created an EFI partition > for /boot/efi on the SSD. I then replaced the relevant lines in > /etc/fstab of the first attempt with the correct ones from the 2nd. > After a succesful reboot into the fixed system I added the old HDD again > and manually ran "apt-get --reinstall install grub-common os-prober > grub-efi-amd64" to rescan the HDD for extra grub entries. > > To prevent others from running into this problem it would make sense to > add another warning to the "expert" install process: there already is a > check for the existence of at least one EFI partition in the system - > this check should also warn if the EFI partition is not on the device > that the user has explicitly selected for the boot loader. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1396379 > > Title: > installer uses first EFI system partition found even when directed > otherwise > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions > -- Tim Richardson -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396379 Title: installer uses first EFI system partition found even when directed otherwise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765363] Re: prime-select intel is not powering off the nvidia card
@vasyl: thanks, good comment. It pays to RTFM, apparently. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749779] Re: System freeze when going back and forth fullscreen mode with Firefox
For me in 20.04, bug is definitely still present. I have earlyoom active, and 32 gb a few seconds of "freeze" (which is not really a freeze) earlyoom activates and nukes a few things, including Firefox, which brings back interactive response. It also killed Chrome and Remmina, which was irritating, but that's what earlyoom is there to do; better than minutes of no keyboard response. Alt F2 seem to work after a few seconds too, which allows restart of the gnome shell. I will comment on the upstream bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749779 Title: System freeze when going back and forth fullscreen mode with Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1749779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
PS there is no text at all, the process gets as far as the spinning icon and stops. I don't see the fsck check start. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
Hi Sebastien, my most recent attachment #11 is from a failed boot. When it gets stuck, I get no keyboard response from Esc, ctrl-C. I don't think it is possible to log in to virtual terminals at this point in the boot, but if I try, I can get to a blank screen, which after a few seconds jumps back to the boot splash (stuck with the spinning ubuntu logo). There is a burst of CPU fan soon after it gets into this phase, then it stops. Also, it will suspend and resume quite well (of course, resuming back to the same screen). I tried a linux kernel parameter to enable a systemd emergency console, but I could not access that either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
I have been trying to work out how to log a failed session with plymouth debug messages. I finally succeeded, it is attached. Note that at the end of log file, it goes into suspend. That was me trying to power off the machine, and not holding the button long enough. It actually suspends and resume right back to the stuck plymouth display, but I don't know any way out except to force the machine off. ** Attachment added: "Boot log including plymouth trace messages" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872159/+attachment/5353608/+files/plymouth_fail.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
I have been investigating other bug reports. I can't find anything that helps my very much, but I did note references to timing. It is very puzzling why I don't have problems when booting from the installation to an external drive. That drive is actually a USB stick (ext4 formatted). My internal ssd uses lvm, the stick not, but the stick is also much slower, just in case that is relevant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
I installed 20.04 beta on a usb drive on the same machine, and reinstalled packages to resemble my main install as closely as possible. The bug does not occur when booting from the usb drive. The most significant difference I can think of is that the main install is on an lvm partition (unencrypted). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
** Attachment added: "boot messages with plymouth debugging messages" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+attachment/5352286/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
** Summary changed: - booting with splash hangs when external monitors are connected (pure intel laptop) + booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) ** Description changed: + I think this is a problem with the splash boot loader. This problem is + not reproduced if using nosplash. - I think this is a problem with the splash boot loader. + I have installed 20.04 to this laptop. Thinkpad T480, i7, intel + graphics. - I have installed 20.04 to this laptop. Clean install, not an upgrade. + Clean install of 20.04 beta, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. - I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. + I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. The fsck step does not commence. + In recovery mood, I can log in. - I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. + + With no external monitors attached, it works. + + I am used to having such problems with Nvidia graphics is involved, but + this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: - acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed - tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed + acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed + tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) -Subsystem: Lenovo UHD Graphics 620 [17aa:225d] + Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) + Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel laptop)
** Summary changed: - booting with splash hangs when external monitors are connected + booting with splash hangs when external monitors are connected (pure intel laptop) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected (pure intel laptop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: booting with splash hangs when external monitors are connected
** Attachment added: "journalctl -b-1 > journal.txt" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+attachment/5351782/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: booting with splash hangs when external monitors are connected
** Attachment added: "journalctl -b0 > journal.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872159/+attachment/5351769/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871641] Re: Ubuntu never finishes booting: A start job is running for Hold until boot process finishes up (3min 7s / no limit)
What happens if you edit /etc/default/grub to remove splash as a setting (that is, boot without plymouth). I was having similar problems to you, also with log message saying job was on hold. I did not wait beyond 3 minutes. In my case, this only happens if an external monitor is connected at boot. (see https://askubuntu.com/questions/33416/how-do-i-disable-the-boot- splash-screen-and-only-show-kernel-and-boot-text-inst for instructions on disabling splash screen) My bug report: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872159 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871641 Title: Ubuntu never finishes booting: A start job is running for Hold until boot process finishes up (3min 7s / no limit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1871641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: booting with splash hangs when external monitors are connected
** Also affects: plymouth (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/1872159 Title: booting with splash hangs when external monitors are connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: booting with splash hangs when external monitors are connected
boot.log could not be attached by the report tool, I added it manualy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] [NEW] booting with splash hangs when external monitors are connected
Public bug reported: I think this is a problem with the splash boot loader. I have installed 20.04 to this laptop. Clean install, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. In recovery mood, I can log in. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "boot.log" https://bugs.launchpad.net/bugs/1872159/+attachment/5351682/+files/boot.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg, Pop!OS fix works.
@Alberto, couldn't prime-select do this when going into hybrid or Optimus mode? Only users with nvidia hybrid graphics would go down this logic path, and they are only ones who need the fix (but only if they are using gdm3, sddm and lightdm continue to be unaffected by this) The set of users who "need" this fix are gdm3 users with hybrid Nvidia graphics (where "need" = want tear-free graphics on their laptop panel if Optimus, or on all displays if it's something like a T-series Thinkpad where the nvidia card has no direct access to any display). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg, Pop!OS fix works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856653] Re: CVE-2019-0154 caused major power problem, pls backport upstream's fix
not 'a fix', the intel maintainer's 5.4 patch has been applied by the ubuntu devs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856653 Title: CVE-2019-0154 caused major power problem, pls backport upstream's fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856653] Re: CVE-2019-0154 caused major power problem, pls backport upstream's fix
Confirming that a fix has been backported to 20.04, currently in the proposed kernel. I'm testing it, the power usage is great. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856653 Title: CVE-2019-0154 caused major power problem, pls backport upstream's fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
This bug persists in 20.04 daily. The one-line Pop!OS solution (https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/comments/26) works, just logout and login. Pop!OS has used this for several releases now, just saying. ** Summary changed: - nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg + nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg, Pop!OS fix works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg, Pop!OS fix works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856653] Re: CVE-2019-0154 caused major power problem, pls backport upstream's fix
Also, please note the upstream bug discussion also includes patches for 5.4 It seems that 5.4 is destined for 20.04. So far 5.4 upstream is still using the first release of this patch, which means 5.4 has the i915 RC6 bug. 5.4 is a LTS kernel bug so it strange to me, but please, I hope you can consider making sure that 20.04 does not launch with this nasty power regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856653 Title: CVE-2019-0154 caused major power problem, pls backport upstream's fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856653] Re: CVE-2019-0154 caused major power problem, pls backport upstream's fix
Yes, that little patch applies cleanly to every 5.3 hwe build I've done (about
five I'd say)
To be clear:
diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c
b/drivers/gpu/drm/i915/gt/intel_lrc.c
index 82b7ace62d97..b18f281d5d12 100644
--- a/drivers/gpu/drm/i915/gt/intel_lrc.c
+++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
@@ -510,7 +510,11 @@ execlists_user_begin(struct intel_engine_execlists
*execlists,
inline void
execlists_user_end(struct intel_engine_execlists *execlists)
{
+ struct intel_engine_cs *engine =
+ container_of(execlists, typeof(*engine), execlists);
+
execlists_clear_active(execlists, EXECLISTS_ACTIVE_USER);
+ mod_delayed_work(engine->i915->wq, &engine->i915->gem.retire_work, 0);
}
static inline void
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856653
Title:
CVE-2019-0154 caused major power problem, pls backport upstream's fix
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856653/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856653] Re: CVE-2019-0154 caused major power problem, pls backport upstream's fix
PS I've been running on hwe 5.3 from Ubuntu's kernel git repository for a few weeks, with the patch linked above, and it is stable on my Thinkpad T480. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856653 Title: CVE-2019-0154 caused major power problem, pls backport upstream's fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765888] Re: Please revert to debian-alternatives based prime-select
** Changed in: nvidia-prime (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765888 Title: Please revert to debian-alternatives based prime-select To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856653] Re: CVE-2019-0154 caused major power problem, pls backport upstream's fix
If the power-saving patch is backported,will this be updated? I'm on own patched kernel so I won't notice. It's an awful problem, by the way, it harms battery life on any laptop with intel graphics from 2016 or later. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856653 Title: CVE-2019-0154 caused major power problem, pls backport upstream's fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856653] Re: CVE-2019-0154 caused major power problem, pls backport maintainers fix
logs not applicable ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Summary changed: - CVE-2019-0154 caused major power problem, pls backport maintainers fix + CVE-2019-0154 caused major power problem, pls backport maintainer's fix ** Summary changed: - CVE-2019-0154 caused major power problem, pls backport maintainer's fix + CVE-2019-0154 caused major power problem, pls backport upstream's fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856653 Title: CVE-2019-0154 caused major power problem, pls backport upstream's fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856653] Re: CVE-2019-0154 caused major power problem, pls backport maintainers fix
** Description changed: https://gitlab.freedesktop.org/drm/intel/issues/614 the fix released as CVE-2019-0154 increases idle power consumption on intel i915 6th gen and later. - That's because the GPU does not enter RC6 any more. + That's because the GPU does not enter RC6 any more. - For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. Previously, it idled at 5W. - Effects on a T480 (8th gen) are less dramatic but still significant. + For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. Previously, it idled at 5W. + Effects on a T480 (8th gen) are less dramatic but still significant. + 5.5RC1 has the maintainer's second pass at this, which restores RC6 + idling - 5.5RC1 has the maintainers second pass at this, which restores RC6 idling - - The maintainers patch for 5.3 is here: - https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057 + The maintainer's patch for 5.3 is here: + https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057 I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it builds. I am testing it now. I think it would be very helpful to backport this if you can. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856653 Title: CVE-2019-0154 caused major power problem, pls backport maintainers fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856653] [NEW] CVE-2019-0154 caused major power problem, pls backport maintainers fix
Public bug reported: https://gitlab.freedesktop.org/drm/intel/issues/614 the fix released as CVE-2019-0154 increases idle power consumption on intel i915 6th gen and later. That's because the GPU does not enter RC6 any more. For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. Previously, it idled at 5W. Effects on a T480 (8th gen) are less dramatic but still significant. 5.5RC1 has the maintainer's second pass at this, which restores RC6 idling The maintainer's patch for 5.3 is here: https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057 I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it builds. I am testing it now. I think it would be very helpful to backport this if you can. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856653 Title: CVE-2019-0154 caused major power problem, pls backport maintainers fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847144] Re: network-manager-openvpn config import ignores tls-crypt section
You are correct. Thanks. I was so puzzled by this. I am using KDE. Possibly the network manager interface is different. This is what I did. Imported the openvpn config file into networkmanger. It makes a connection, it times out, and no amount of debugging gives any more hint. I edit the openvpn file, and extract the key block into a file. It is the key block in between and so my text file looks like this: -BEGIN OpenVPN Static key V1- 92e2de5ae6437298634a0ebe952 . . . cc05zxzxczczxxczxzxczxce902b498a5 -END OpenVPN Static key V1- I save it as blabla.key Then I opened the openvpn connection imported into nm, choose Advanced... on the VPM (openvpn) tab,Choose TLS Settings, and change only two things Mode is TLS-Crypt and Key File i give the path of the key file created just before. And immediately, the connection worked ** Attachment added: "2019-11-28_21-32.png" https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1847144/+attachment/5308442/+files/2019-11-28_21-32.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847144 Title: network-manager-openvpn config import ignores tls-crypt section To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1847144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend
With my T480 and the 5.0 ubuntu kernel, and the 5.3 in the proposed PPA, two finger scrolling does not work unless I specify psmouse.synaptics_intertouch=0 or =1 either value fixes it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling and click-and-drag no longer works after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
I just installed popOS 19.10 an an Optimus laptop, nvidia option. Out of the box you get gdm3 and tear-free prime-sync; it uses Jeremy Soller's solution (root rights granted in Xwrapper) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus)
Nvidia release notes for Linux, Solaris, and FreeBSD driver 440.26 [beta release] [long-lived branch release] (2019-10-17) have a comment: "Fixed a bug that could cause a blank screen on some DisplayPort monitors when logging in to GNOME, if the nvidia-drm kernel module parameter modeset=1 is specified." I haven't tested this, I hope the beta driver gets packaged. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714881 Title: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1714881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open
I haven't had this problem for several releases, so it is only triggered under some circumstances. I suspected the hangouts extension (which I no longer use) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1600622 Title: Screen doesn't lock or go to sleep when certain Chrome tabs are open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
19.10 beta and nvidia drivers 430 and 435 have the same problem. I have made the bug title correctly specific. ** Summary changed: - nvidia-drm.modeset=1 results in no monitors detected by Xorg + nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
