[Bug 2068753] [NEW] gvfs ssh/sftp mount broken in 24.04
Public bug reported: I use SSH file mounts in GNOME to go about my daily business. As of version 24.04 of Ubuntu, navigating to a folder of images and launching EoG fails to load the whole directory. EoG shows 1/1 files, and you can't navigate back and forth with the arrows. Copying between two sftp mounts also fails, and seems to crash the mount. Something isn't quite right with the mount, and this is a regression to what has been working for many years. ** Affects: gvfs (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/2068753 Title: gvfs ssh/sftp mount broken in 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2068753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054827] Re: [regression] GUI crashed after installed proposed package after mesa updates
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054827 Title: [regression] GUI crashed after installed proposed package after mesa updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2054827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977657] [NEW] install fatal error grub not installed nvme0
Public bug reported: ... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.15 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 Date: Sat Jun 4 14:23:31 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-22.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977657 Title: install fatal error grub not installed nvme0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1977657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959483] [NEW] Ubuntu fails to install
Public bug reported: Ubuntu fails to install ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.17 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 29 12:47:51 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: LANGUAGE=en_IE.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IE.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.17 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959483 Title: Ubuntu fails to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1959483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946520] [NEW] magic-proxy does not gracefully handle error conditions
Public bug reported:
During an impish build of ubuntu-cpc images with magic-proxy enabled,
the installation of certain packages tried to reach an internet endpoint
(specifically http://169.254.169.254/latest/meta-data/instance-id -
which appears to be used for EC2 metadata)
The magic-proxy log indicated :
10.10.10.2 - - [01/Oct/2021 13:21:26] urlopen() failed for
http://169.254.169.254/2009-04-04/meta-data/instance-id with [Errno 110]
Connection timed out
10.10.10.2 - - [01/Oct/2021 13:21:26] code 501, message [Errno 110] Connection
timed out
10.10.10.2 - - [01/Oct/2021 13:21:26] "GET /2009-04-04/meta-data/instance-id
HTTP/1.1" 501 -
Exception occurred during processing of request from ('10.10.10.2', 49672)
Traceback (most recent call last):
File "/usr/lib/python3.9/urllib/request.py", line 1346, in do_open
h.request(req.get_method(), req.selector, req.data, headers,
File "/usr/lib/python3.9/http/client.py", line 1279, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/lib/python3.9/http/client.py", line 1325, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/lib/python3.9/http/client.py", line 1274, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/lib/python3.9/http/client.py", line 1034, in _send_output
self.send(msg)
File "/usr/lib/python3.9/http/client.py", line 974, in send
self.connect()
File "/usr/lib/python3.9/http/client.py", line 945, in connect
self.sock = self._create_connection(
File "/usr/lib/python3.9/socket.py", line 844, in create_connection
raise err
File "/usr/lib/python3.9/socket.py", line 832, in create_connection
sock.connect(sa)
TimeoutError: [Errno 110] Connection timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/share/livecd-rootfs/magic-proxy", line 873, in __get_request
with urllib.request.urlopen(
File "/usr/lib/python3.9/urllib/request.py", line 214, in urlopen
return opener.open(url, data, timeout)
File "/usr/lib/python3.9/urllib/request.py", line 517, in open
response = self._open(req, data)
File "/usr/lib/python3.9/urllib/request.py", line 534, in _open
result = self._call_chain(self.handle_open, protocol, protocol +
File "/usr/lib/python3.9/urllib/request.py", line 494, in _call_chain
result = func(*args)
File "/usr/lib/python3.9/urllib/request.py", line 1375, in http_open
return self.do_open(http.client.HTTPConnection, req)
File "/usr/lib/python3.9/urllib/request.py", line 1349, in do_open
raise URLError(err)
urllib.error.URLError:
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.9/socketserver.py", line 683, in process_request_thread
self.finish_request(request, client_address)
File "/usr/lib/python3.9/socketserver.py", line 360, in finish_request
self.RequestHandlerClass(request, client_address, self)
File "/usr/lib/python3.9/socketserver.py", line 747, in __init__
self.handle()
File "/usr/lib/python3.9/http/server.py", line 427, in handle
self.handle_one_request()
File "/usr/lib/python3.9/http/server.py", line 415, in handle_one_request
method()
File "/usr/share/livecd-rootfs/magic-proxy", line 787, in do_GET
self.__get_request()
File "/usr/share/livecd-rootfs/magic-proxy", line 887, in __get_request
self.send_error(501, e.reason)
File "/usr/lib/python3.9/http/server.py", line 473, in send_error
'message': html.escape(message, quote=False),
File "/usr/lib/python3.9/html/__init__.py", line 19, in escape
s = s.replace("&", "") # Must be done first!
AttributeError: 'TimeoutError' object has no attribute 'replace'
Because magic-proxy is proxying all traffic to port 80, it will
intercept these sort of messages. The TimeoutError ends up bubbling up
to the serversocket handling code, which will then cause a broken pipe
for all future communications, effectively breaking future apt calls
from within the build environment.
The concrete problem here is that inside magic-proxy, self.send_error is
called with the argument of e.reason, which can be a string (no error)
or an exception (in case of a nested exception). If the nested exception
is passed into self.send_error, html.replace will try to be called on
the exception, hence the above exception.
In addition to fixing this specific problem, magic-proxy's request
handling should catch all exceptions to not interfere with higher up
socketserver handling.
** Affects: livecd-rootfs (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/1946520
Title:
magic-proxy does not gracefully handle error conditions
To manage notifications
[Bug 1945801] Re: Netplan doesn't work with DHCP DNS server
** Package changed: ubuntu => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945801 Title: Netplan doesn't work with DHCP DNS server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1945801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945801] [NEW] Netplan doesn't work with DHCP DNS server
Public bug reported: Network/hardware setup: pihole running on pi4 with local dns entries. Ex. somehost 192.168.1.10 udm pro configured with a manual dhcp name server giving the pihole's ip address fresh install ubuntu server on a VMware ESXi host using dhcp Problem: from the ubuntu server "ping somehost" and "nslookup somehost" are both unable to resolve the local ip from the pihole. this functionality works fine from both windows and osx "systemd-resolve --status" shows the correct pihole ip address in "Current DNS Server" and "DNS Servers" for the network interface ** 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/1945801 Title: Netplan doesn't work with DHCP DNS server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1945801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938289] Re: Please update to upstream release 20210728.00
## Conclusion Due to the completion of Google's testing and my own verification, I am marking verification-complete for all releases. ## Notes Testing of the new Google guest agents was primarily performed by Google themselves. They have given the +1. In addition, these images have gone through testing from the Canonical Public Cloud team. From my own testing images were produced with the guest agents directly from proposed and uploaded to GCE. These are the same images that Google used in their own testing. I verified: 1) The versions of packages 2) that the services were running/completed successfully 3) that my account and other project accounts were created 4) correct SSH keys were imported 5) the new packages provided parity with the existing agents. Bionic: google-compute-engine-oslogin 20210728.00-0ubuntu1~18.04.0 systemctl status google-oslogin-cache.service ● google-oslogin-cache.service - NSS cache refresh Loaded: loaded (/lib/systemd/system/google-oslogin-cache.service; static; vendor preset: enabled) Active: inactive (dead) since Mon 2021-09-27 14:17:57 UTC; 2h 14min ago Process: 30617 ExecStart=/usr/bin/google_oslogin_nss_cache (code=exited, status=0/SUCCESS) Main PID: 30617 (code=exited, status=0/SUCCESS) Focal: google-compute-engine-oslogin 20210728.00-0ubuntu1~20.04.0 systemctl status google-oslogin-cache.service ● google-oslogin-cache.service - NSS cache refresh Loaded: loaded (/lib/systemd/system/google-oslogin-cache.service; static; vendor preset: enabled) Active: inactive (dead) since Mon 2021-09-27 14:09:16 UTC; 3h 23min ago TriggeredBy: ● google-oslogin-cache.timer Process: 32376 ExecStart=/usr/bin/google_oslogin_nss_cache (code=exited, status=0/SUCCESS) Main PID: 32376 (code=exited, status=0/SUCCESS) Hirsute: google-compute-engine-oslogin 20210728.00-0ubuntu1~21.04.0 systemctl status google-oslogin-cache.service ● google-oslogin-cache.service - NSS cache refresh Loaded: loaded (/lib/systemd/system/google-oslogin-cache.service; static) Active: inactive (dead) since Mon 2021-09-27 14:11:58 UTC; 3h 42min ago TriggeredBy: ● google-oslogin-cache.timer Process: 33903 ExecStart=/usr/bin/google_oslogin_nss_cache (code=exited, status=0/SUCCESS) Main PID: 33903 (code=exited, status=0/SUCCESS) ** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-bionic verification-done-focal verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938289 Title: Please update to upstream release 20210728.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-compute-engine-oslogin/+bug/1938289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938440] Re: Please update gce-compute-image-packages to 20210629.00
** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-bionic verification-done-focal verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938440 Title: Please update gce-compute-image-packages to 20210629.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1938440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938286] Re: Please update to 20210629.00 upstream release
## Conclusion Due to the completion of Google's testing and my own verification, I am marking verification-complete for all releases. ## Notes Testing of the new Google guest agents was primarily performed by Google themselves. They have given the +1. In addition, these images have gone through testing from the Canonical Public Cloud team. From my own testing images were produced with the guest agents directly from proposed and uploaded to GCE. These are the same images that Google used in their own testing. I verified: 1) The versions of packages 2) that the services were running/completed successfully 3) that my account and other project accounts were created 4) correct SSH keys were imported 5) the new packages provided parity with the existing agents. Bionic: google-guest-agent 20210629.00-0ubuntu1~18.04.1 systemctl status google-guest-agent ● google-guest-agent.service - Google Compute Engine Guest Agent Loaded: loaded (/lib/systemd/system/google-guest-agent.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-09-22 20:06:24 UTC; 4 days ago Main PID: 1323 (google_guest_ag) Tasks: 12 (limit: 4666) CGroup: /system.slice/google-guest-agent.service └─1323 /usr/bin/google_guest_agent systemctl status google-shutdown-scripts.service ● google-shutdown-scripts.service - Google Compute Engine Shutdown Scripts Loaded: loaded (/lib/systemd/system/google-shutdown-scripts.service; enabled; vendor preset: enabled) Active: active (exited) since Wed 2021-09-22 20:06:23 UTC; 4 days ago Main PID: 1324 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4666) CGroup: /system.slice/google-shutdown-scripts.service systemctl status google-startup-scripts.service ● google-startup-scripts.service - Google Compute Engine Startup Scripts Loaded: loaded (/lib/systemd/system/google-startup-scripts.service; enabled; vendor preset: enabled) Active: inactive (dead) since Wed 2021-09-22 20:06:39 UTC; 4 days ago Main PID: 2325 (code=exited, status=0/SUCCESS) Focal: google-guest-agent 20210629.00-0ubuntu1~20.04.0 systemctl status google-guest-agent ● google-guest-agent.service - Google Compute Engine Guest Agent Loaded: loaded (/lib/systemd/system/google-guest-agent.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-09-22 20:04:08 UTC; 4 days ago Main PID: 656 (google_guest_ag) Tasks: 11 (limit: 4705) Memory: 18.8M CGroup: /system.slice/google-guest-agent.service └─656 /usr/bin/google_guest_agent systemctl status google-shutdown-scripts.service ● google-shutdown-scripts.service - Google Compute Engine Shutdown Scripts Loaded: loaded (/lib/systemd/system/google-shutdown-scripts.service; enabled; vendor preset: enabled) Active: active (exited) since Wed 2021-09-22 20:04:12 UTC; 4 days ago Main PID: 798 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4705) Memory: 0B CGroup: /system.slice/google-shutdown-scripts.service systemctl status google-startup-scripts.service ● google-startup-scripts.service - Google Compute Engine Startup Scripts Loaded: loaded (/lib/systemd/system/google-startup-scripts.service; enabled; vendor preset: enabled) Active: inactive (dead) since Wed 2021-09-22 20:04:21 UTC; 4 days ago Main PID: 1511 (code=exited, status=0/SUCCESS) Hirsute: google-guest-agent 20210629.00-0ubuntu1~21.04.0 systemctl status google-guest-agent ● google-guest-agent.service - Google Compute Engine Guest Agent Loaded: loaded (/lib/systemd/system/google-guest-agent.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-09-22 20:07:21 UTC; 4 days ago Main PID: 675 (google_guest_ag) Tasks: 10 (limit: 4700) Memory: 18.5M CGroup: /system.slice/google-guest-agent.service └─675 /usr/bin/google_guest_agent systemctl status google-shutdown-scripts.service ● google-shutdown-scripts.service - Google Compute Engine Shutdown Scripts Loaded: loaded (/lib/systemd/system/google-shutdown-scripts.service; enabled; vendor preset: enabled) Active: active (exited) since Wed 2021-09-22 20:07:25 UTC; 4 days ago Main PID: 808 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4700) Memory: 0B CGroup: /system.slice/google-shutdown-scripts.service systemctl status google-startup-scripts.service ● google-startup-scripts.service - Google Compute Engine Startup Scripts Loaded: loaded (/lib/systemd/system/google-startup-scripts.service; enabled; vendor preset: enabled) Active: inactive (dead) since Wed 2021-09-22 20:07:33 UTC; 4 days ago Main PID: 1446 (code=exited, status=0/SUCCESS) ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute ** Tags removed: verification-needed-bionic verification-needed-focal ** Tags added:
[Bug 1938553] Re: Please update to upstream release 20210608.1
## Conclusion Due to the completion of Google's testing and my own verification, I am marking verification-complete for all releases. ## Notes Testing of the new Google guest agents was primarily performed by Google themselves. They have given the +1. In addition, these images have gone through testing from the Canonical Public Cloud team. From my own testing images were produced with the guest agents directly from proposed and uploaded to GCE. These are the same images that Google used in their own testing. I verified: 1) The versions of packages 2) that the services were running/completed successfully 3) that my account and other project accounts were created 4) correct SSH keys were imported 5) the new packages provided parity with the existing agents. Bionic: google-osconfig-agent 20210608.1-0ubuntu1~18.04.1 systemctl status google-osconfig-agent ● google-osconfig-agent.service - Google OSConfig Agent Loaded: loaded (/lib/systemd/system/google-osconfig-agent.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-09-22 20:06:20 UTC; 4 days ago Main PID: 1096 (google_osconfig) Tasks: 11 (limit: 4666) CGroup: /system.slice/google-osconfig-agent.service └─1096 /usr/bin/google_osconfig_agent Focal: google-osconfig-agent 20210608.1-0ubuntu1~20.04.0 systemctl status google-osconfig-agent ● google-osconfig-agent.service - Google OSConfig Agent Loaded: loaded (/lib/systemd/system/google-osconfig-agent.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-09-22 20:04:06 UTC; 4 days ago Main PID: 569 (google_osconfig) Tasks: 10 (limit: 4705) Memory: 22.8M CGroup: /system.slice/google-osconfig-agent.service └─569 /usr/bin/google_osconfig_agent Hirsute: google-osconfig-agent 20210608.1-0ubuntu1~21.04.0 systemctl status google-osconfig-agent ● google-osconfig-agent.service - Google OSConfig Agent Loaded: loaded (/lib/systemd/system/google-osconfig-agent.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-09-22 20:07:17 UTC; 4 days ago Main PID: 579 (google_osconfig) Tasks: 8 (limit: 4700) Memory: 22.4M CGroup: /system.slice/google-osconfig-agent.service └─579 /usr/bin/google_osconfig_agent ** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-bionic verification-done-focal verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938553 Title: Please update to upstream release 20210608.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/1938553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938440] Re: Please update gce-compute-image-packages to 20210629.00
## Conclusion Due to the completion of Google's testing and my own verification, I am marking verification-complete for all releases. ## Notes Testing of the new Google guest agents was primarily performed by Google themselves. They have given the +1. In addition, these images have gone through testing from the Canonical Public Cloud team. From my own testing images were produced with the guest agents directly from proposed and uploaded to GCE. These are the same images that Google used in their own testing. I verified: 1) The versions of packages 3) that my account and other project accounts were created 4) correct SSH keys were imported 5) the new packages provided parity with the existing agents. Verified with the following package versions: Bionic: google-compute-engine 20210629.00-0ubuntu1~18.04.0 Focal: google-compute-engine 20210629.00-0ubuntu1~20.04.0 Hirsute: google-compute-engine 20210629.00-0ubuntu1~21.04.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938440 Title: Please update gce-compute-image-packages to 20210629.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1938440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938286] Re: Please update to 20210629.00 upstream release
** Tags removed: verification-done-bionic verification-done-focal verification-done-hirsute ** Tags added: verification-needed-bionic verification-needed-focal verification-needed-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938286 Title: Please update to 20210629.00 upstream release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/1938286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938289] Re: Please update to upstream release 20210728.00
** Tags removed: verification-done-bionic verification-done-focal verification-done-hirsute ** Tags added: verification-needed-bionic verification-needed-focal verification-needed-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938289 Title: Please update to upstream release 20210728.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-compute-engine-oslogin/+bug/1938289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938440] Re: Please update gce-compute-image-packages to 20210629.00
** Tags removed: verification-done-hirsute ** Tags added: verification-needed-hirsute ** Tags removed: verification-done-bionic verification-done-focal ** Tags added: verification-needed-bionic verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938440 Title: Please update gce-compute-image-packages to 20210629.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1938440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938553] Re: Please update to upstream release 20210608.1
** Tags removed: verification-done-bionic verification-done-focal verification-done-hirsute ** Tags added: verification-needed-bionic verification-needed-focal verification-needed-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938553 Title: Please update to upstream release 20210608.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/1938553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938289] Re: Please update to upstream release 20210728.00
Canonical's public cloud team has verified that images built with the proposed packages pass the same testing that we do on regular GCE images. ** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-bionic verification-done-focal verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938289 Title: Please update to upstream release 20210728.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-compute-engine-oslogin/+bug/1938289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938286] Re: Please update to 20210629.00 upstream release
** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-bionic verification-done-focal verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938286 Title: Please update to 20210629.00 upstream release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/1938286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938553] Re: Please update to upstream release 20210608.1
Canonical's public cloud team has verified that images built with the proposed packages pass the same testing that we do on regular GCE images. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute ** Tags removed: verification-needed-bionic verification-needed-focal ** Tags added: verification-done-bionic verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938553 Title: Please update to upstream release 20210608.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/1938553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938440] Re: Please update gce-compute-image-packages to 20210629.00
Canonical's public cloud team has verified that images built with the proposed packages pass the same testing that we do on regular GCE images. ** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-bionic verification-done-focal verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938440 Title: Please update gce-compute-image-packages to 20210629.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1938440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940723] Re: shim-signed fails to install if grub disk config is incorrect
do you mind providing your grub configuration? (I know you said it was system default in the other bug), but I'd like to compare it against our fresh VM boot just to see if anything was awry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940723 Title: shim-signed fails to install if grub disk config is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1940723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940723] Re: shim-signed fails to install if grub disk config is incorrect
I have been looking into why this has been happening on Azure Ubuntu VMs, but I have not been able to reproduce: I'm running: az vm create --name bug-test --resource-group canonical-patviafore --location southcentralus --image Canonical:0001-com-ubuntu-server- focal:20_04-lts:20.04.202107200 --size Standard_A2 --admin-username ubuntu --ssh-key-value And then doing an apt dist-upgrade. I will need some way to reproduce the issue to investigate further why only your Azure instances are affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940723 Title: shim-signed fails to install if grub disk config is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1940723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940588] Re: package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 32
@abaealter: I'm trying to reproduce the issue on Azure as that will give us an environment to investigate this bug a bit better, and I was not able to. Do you mind providing a little more information about your Azure environment? Do you have the URN that you are running with (if you don't know this, telling us the output of `cat /etc/cloud/build.info` would be useful as well) What instance type are you running on? Do you mind sharing your grub configuration? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940588 Title: package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1940588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938299] Re: Unable to SSH Into Instance when deploying Impish 21.10
** Tags added: rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938299 Title: Unable to SSH Into Instance when deploying Impish 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1938299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927231] [NEW] u-boot-update complains about a syntax error
Public bug reported: During cloud builds of riscv64 (impish), we do a u-boot-update inside our chroot. With version 4.0.3ubuntu1, the command fails with the following error message: /usr/sbin/u-boot-update: line 92: syntax error near unexpected token `<<<' We did not see this error with 4.0.2ubuntu5_all ** Affects: u-boot-menu (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/1927231 Title: u-boot-update complains about a syntax error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot-menu/+bug/1927231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920043] Re: Latest Focal Minimal disk images from livecd-rootfs do not boot
I have done testing on minimal images built from 2.664.19 livecd-rootfs and run them through qemu to verify they still boot. I have also tested cloud-specific images to make sure they do not double boot as part of this change. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920043 Title: Latest Focal Minimal disk images from livecd-rootfs do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1920043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920043] Re: Latest Focal Minimal disk images from livecd-rootfs do not boot
** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Pat Viafore (patviafore) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920043 Title: Latest Focal Minimal disk images from livecd-rootfs do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1920043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920043] Re: Latest Focal Minimal disk images from livecd-rootfs do not boot
Commit 4c504f678178104eceaf5b3aae40bcff20863235 needs to be backported to Focal to fix this -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920043 Title: Latest Focal Minimal disk images from livecd-rootfs do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1920043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920043] [NEW] Latest Focal Minimal disk images from livecd-rootfs do not boot
Public bug reported: [Impact] * Minimal images built from livecd-rootfs after March 12th do not boot. There are no broken images on cloud-images.ubuntu.com, but no further images will be published until this is fixed. Cloud-specific minimal images are unaffected, as they do the proper steps in their build hooks to mitigate this problem. [Test Plan] * Build a minimal image from livecd-rootfs in the focal branch. * Launch it through qemu to verify it boots: qemu-system-x86_64-cpu host -machine type=q35,accel=kvm -m 2048-snapshot -netdev id=net00,type=user,hostfwd=tcp::-:22 -device virtio-net-pci,netdev=net00 -drive if=virtio,format=qcow2,file=focal-server-cloudimg-amd64.img -drive if=virtio,format=raw,file=seed.img -nographic * Verify cloud-specific minimal builds still operate as intended (single boot, no double boot fallback) [Where problems could occur] * The changes are forcing a boot without initramfs for all minimal images. This was the default behavior before the March 12th change. [Bug Description] Here is the kernel panic: VFS: Cannot open root device "LABEL=cloudimg-rootfs" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: fe00 2306048 vda driver: virtio_blk fe01 2192367 vda1 eba1d37a-4dc1-4c42-8cab-ed045e561faa fe0e4096 vda14 9bbe6566-13bd-412a-9a58-8d85918ebe0f fe0f 108544 vda15 b4d6d9b6-0a70-41eb-9d71-5d64fc7e7d08 fe10 366 vdb driver: virtio_blk Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-1034-kvm #35-Ubuntu Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-1 04/01/2014 Call Trace: 0x92b471a8 0x92b23a3d 0x9332f5d4 0x9332f6b0 0x9332f7e7 0x9332f287 ? 0x92b4a5e0 0x92b4a5e9 0x92c00215 Kernel Offset: 0x1140 from 0x8100 (relocation range: 0x8000-0xbfff) ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]--- Kernel command line : Linux version 5.4.0-1034-kvm (buildd@lgw01-amd64-033) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #35-Ubuntu SMP Wed Feb 24 14:09:38 UTC ) Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1034-kvm root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 The root should be set to a PARTUUID, not a label. ** Affects: livecd-rootfs (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/1920043 Title: Latest Focal Minimal disk images from livecd-rootfs do not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1920043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
I have tested the changes in livecd-rootfs 2.664.18. Generic cloud images (qcow2, kvm, etc) cloud images now boot with an initramfs and don't have a double boot (tested with QEMU). I've also tested various cloud images (AWS, Google, Azure, Oracle) that have custom cloud kernels (which make use of the replace_kernel function) and confirmed that they don't boot with initramfs, but they still only have one boot. The only place I've seen a double boot was when booting the Azure image with qemu, but that was to be expected, since it has the linux-azure kernel and does not include all the things needed to boot in a non-Azure environment. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
** Description changed:
- A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
- 20.04 by “do-release-upgrade –d”.
+ [Impact]
+ Generic cloud images will boot without initramfs, fail, and then fall back,
resulting in a double boot performance hit
+
+ [Test Case]
+ Load up cloud images from
http://cloud-images.ubuntu.com/releases/focal/release/.
+
+ For example, using http://cloud-
+ images.ubuntu.com/releases/focal/release/ubuntu-20.04-server-cloudimg-
+ amd64.img :
+
+ qemu-system-x86_64-cpu host -machine type=q35,accel=kvm -m 2048
+ -nographic -snapshot -netdev
+ id=net00,type=user,hostfwd=tcp::-:22 -device virtio-net-
+ pci,netdev=net00 -drive if=virtio,format=qcow2,file=ubuntu-20.04
+ -server-cloudimg-amd64.img -drive if=virtio,format=raw,file=seed.img
+
+ Note: seed.img is created using cloud-localds and a cloud-init file
+ containing ssh keys.
+
+ Observe the double boot.
+
+ On a fixed system, there should only be one boot, and /boot/grub/grubenv
+ should show initrdless_boot_fallback_triggered=0.
+
+ [Regression Potential]
+ Cloud images (both generic and cloud-specific) images perform a double boot.
To mitigate the regression potential, testing will occur for all cloud-specific
kernels as well as all generic cloud images.
+
+
+ [Original Description]
+ A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu 20.04 by
“do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
- if [ "${initrdfail}" = 1 ]; then
- linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
- initrd/boot/initrd.img-5.6.0-050600-generic
- else
- linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
- #Dexuan: here the initrd line is missing!
- fi
- initrdfail
+ if [ "${initrdfail}" = 1 ]; then
+ linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
+ initrd/boot/initrd.img-5.6.0-050600-generic
+ else
+ linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
+ #Dexuan: here the initrd line is missing!
+ fi
+ initrdfail
}
-
- As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
+ As we can see, Ubuntu only uses the initrd.img if initrdfail=1.
+ Normally, initrdfail = 0, so when we boot the v5.6 kernel for the first
+ time, we must hit the “fail to mount rootfs” panic and the kernel will
+ automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel boots
for the 2nd time, the kernel should successfully boot up. Next, when
the kernel boots for the 3rd time, it panics again since the userspace
program resets initrdfail to 0, and next time when the kernel boots, it
can boot up successfully -- this “panic/success/panic/success” pattern
repeats forever…
-
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
+ It looks the setting may be intentional, but we should not assume a
+ customer kernel must have the necessary vmbus/storage drivers built-in.
- It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
-
- This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
+ This issue only
[Bug 1327801] Re: Bightness and contrast settings have no effect
Thank you for doing that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327801 Title: Bightness and contrast settings have no effect To manage notifications about this bug go to: https://bugs.launchpad.net/sane-backends/+bug/1327801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327801] Re: Bightness and contrast settings have no effect
Ideally, whoever wrote the original patch would be involved, because I assume his gamma fix was pertinent to some piece of hardware available to him, just happened to break the Canon LiDE scanners. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327801 Title: Bightness and contrast settings have no effect To manage notifications about this bug go to: https://bugs.launchpad.net/sane-backends/+bug/1327801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327801] Re: Bightness and contrast settings have no effect
Just looking at the log, it seems that unused-parameter error is enabled. I don't know how your pipeline works, but it's not dpkg- buildpackage, so it makes sense that the default CFLAGS (or CXXFLAGS) is set. genesys/low.cpp:636:76: error: unused parameter 'sensor' [-Werror =unused-parameter] You can either change the compiler flags or change the function signature from: bool should_enable_gamma(const ScanSession& session, const Genesys_Sensor& sensor) to: bool should_enable_gamma(const ScanSession& session, const Genesys_Sensor&) and it should be happy. If that fails too, a less elegant solution is to leave the if condition that uses it in, and make it return true instead of false. But I don't think that build is important to the distro issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327801 Title: Bightness and contrast settings have no effect To manage notifications about this bug go to: https://bugs.launchpad.net/sane-backends/+bug/1327801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327801] Re: Bightness and contrast settings have no effect
Sure, I used `dpkg-buildpackage -b``` to build it.
The change was just to remove the offending condition as was suggested:
diff -ur sane-backends-1.0.29.orig/backend/genesys/low.cpp
sane-backends-1.0.29/backend/genesys/low.cpp
--- sane-backends-1.0.29.orig/backend/genesys/low.cpp 2021-02-16
17:18:42.0 -0500
+++ sane-backends-1.0.29/backend/genesys/low.cpp2021-02-16
11:10:24.655216925 -0500
@@ -650,12 +650,6 @@
if ((session.params.flags & ScanFlag::DISABLE_GAMMA) != ScanFlag::NONE) {
return false;
}
-if (sensor.gamma[0] == 1.0f || sensor.gamma[1] == 1.0f || sensor.gamma[2]
== 1.0f) {
-return false;
-}
-if (session.params.depth == 16)
-return false;
-
return true;
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327801
Title:
Bightness and contrast settings have no effect
To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1327801/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327801] Re: Bightness and contrast settings have no effect
Hi Gunnar, Perhaps there is a mistake in that report. I certainly witnessed it in 1.0.29 on Ubuntu 20.04 and 20.10. I don't think it was an issue before that version, and it's unlikely to have been, as the revision that broke it was put in October 17, 2019; not certain about which specific release it made it into, though. My testing is on focal with sane-backends_1.0.29-0ubuntu5.2.dsc, updated with the suggested changes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327801 Title: Bightness and contrast settings have no effect To manage notifications about this bug go to: https://bugs.launchpad.net/sane-backends/+bug/1327801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327801] Re: Bightness and contrast settings have no effect
I have tracked the issue down to an upstream issue with sane-backends, with a fix here: https://gitlab.com/sane-project/backends/-/issues/271 This is not a simple-scan bug. ** Bug watch added: gitlab.com/sane-project/backends/-/issues #271 https://gitlab.com/sane-project/backends/-/issues/271 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327801 Title: Bightness and contrast settings have no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1327801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327801] Re: Bightness and contrast settings have no effect
Here is some debug output when a scan is initiated.
The brightness and contrast values do seem to apply from the front-end:
[+16.68s] DEBUG: scanner.vala:1674: Scanner.scan
("genesys:libusb:001:010", dpi=600, scan_mode=ScanMode.GRAY, depth=2,
type=single, paper_width=2159, paper_height=2794, brightness=-100,
contrast=100, delay=3000ms)
(I did set -100 and 100 respectively for this test).
** Attachment added: "ss-canonlide35.txt"
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1327801/+attachment/5464149/+files/ss-canonlide35.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327801
Title:
Bightness and contrast settings have no effect
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1327801/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327801] Re: Bightness and contrast settings have no effect
Like Michael in #17, I noticed that since around 20.04 my Canon LiDE 35 has no brightness-contrast control, making simple-scan unusable for me. I've worked around by using other software, but it's starting to bug me as more stuff needs to be submitted online in today's world. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327801 Title: Bightness and contrast settings have no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1327801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
As an update to this bug: The work to SRU has stalled, as we have found a regression (https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1902260). Once a fix is SRU'd to Groovy, I'll pick up the fix and SRU it back to Focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914148] [NEW] Firefox connstantly disabled on Apparmor
Public bug reported: Once again Apparmor policies are constantly disabled for Firefox. -I've reported this bug in December, then came a patch, then for the last month of January - regardless of updates, Firefox profiles are skipped. - You cannot be serious? -This is a consistent seccurity issue! - Please write rules that consistently work or teach us how to do so / deal with Mozilla "Feb 02 00:17:24 USER apparmor.systemd[1117]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Feb 02 00:17:24 USER apparmor.systemd[1118]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Feb 02 00:17:24 USER systemd[1]: Finished Load AppArmor profiles. ** Affects: apparmor (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/1914148 Title: Firefox connstantly disabled on Apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1914148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
Hi richmbx, I am currently working this, and currently doing testing to make sure it has integrated with Focal correctly. I expect it to begin the SRU process in the next day or so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580596] Re: Xenial & bionic vagrant box disk size is too small
I've confirmed that this has been fixed in the latest Xenial Vagrant box. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580596 Title: Xenial & bionic vagrant box disk size is too small To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1580596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580596] Re: Xenial & bionic vagrant box disk size is too small
Version 2.408.65 of livecd-rootfs has fixed this issue. Test case: Built a box with the version of livecd-rootfs vagrant box add build.output/livecd.ubuntu-cpc.vagrant.box --name xenial-test vagrant init xenial-test vagrant up vagrant ssh default Run `df -H` inside the vagrant box Observe Disk size of drive mounted at / and observe that the disk is ~ 40G To confirm that this won't break users upgrading to this box, but with < 40G disks, I checked the size of the VMDK backing the box. It was listed at 1.1G. I created a 15G file with `dd if=/dev/urandom of=filename bs=1024 count=15M` I was able to observe the VMDK growing by 15G. So if a user were to have a 10G box fully allocated, and then upgrade to the new box built with the latest version of livecd-rootfs, the user would not be impacted until they tried to fill up the 40G. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580596 Title: Xenial & bionic vagrant box disk size is too small To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1580596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911704] [NEW] flashplugin-installer removed Flash!
Public bug reported: 32.0.0.465ubuntu0.20.04.2 removed Flash from my system! It's not okay to remove plugins the user may be using without their permission. I need this plugin for work, and now I can't find a good way to reinstall it. ** Affects: flashplugin-nonfree (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/1911704 Title: flashplugin-installer removed Flash! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1911704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905054]
I can't speak for 3D, but seeing as the 2D rendering is still loads quicker than canvas, the "performance caveat" really isn't. What should PIXI, or any site, do with this information? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905054]
(In reply to Jeff Gilbert [:jgilbert] from comment #24) > (In reply to Pat Suwalski from comment #20) > > (In reply to Jeff Gilbert [:jgilbert] from comment #19) > > > Honestly at this point I'm tending towards #2. > > > Websites had the chance to handle this well and they have bungled it, so > > > I think we should disable failIfMajorPerformanceCaveat as it stands today. > > > > Are you suggesting PIXI doesn't handle this properly? > > Yes, that's what it sounds like. So what changed? If the system in question doesn't have a "major performance caveat" and the browser is reporting that it does, how is that PIXI mishandling it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905054]
(In reply to Jeff Gilbert [:jgilbert] from comment #19) > Honestly at this point I'm tending towards #2. > Websites had the chance to handle this well and they have bungled it, so I > think we should disable failIfMajorPerformanceCaveat as it stands today. Are you suggesting PIXI doesn't handle this properly? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905054]
Although Firefox 84b2 from official binaries worked fine, Firefox 84.0 from official binaries (firefox-84.0.tar.bz2) does not. Setting ```gfx.webrender.all``` as suggested above *does* work. This appears to be a capability detection issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905054] Re: Firefox 83 Breaks WebGL
Setting gfx.webrender.all as recommended in the upstream bug makes it work. It seems some detection code is broken. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905054] Re: Firefox 83 Breaks WebGL
Can anyone point me to where I can find the Firefox 82 debs? They seem to have disappeared from /var/cache/apt/archives, and I really need them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905054] Re: Firefox 83 Breaks WebGL
The Firefox 84 WebGL section looks a lot like the v83 section: HW_COMPOSITING available by default blocked by env: Acceleration blocked by platform OPENGL_COMPOSITING unavailable by default: Hardware compositing is disabled WEBRENDER available by default disabled by env: Not qualified WEBRENDER_QUALIFIED available by default denied by env: Not on allowlist WEBRENDER_COMPOSITOR disabled by default: Disabled by default WEBRENDER_ANGLE available by default unavailable by env: OS not supported WEBRENDER_DCOMP_PRESENT available by default disabled by user: User disabled via pref unavailable by env: Requires Windows 10 or later unavailable by runtime: Requires ANGLE WEBRENDER_SOFTWARE available by default denied by env: Not on allowlist OMTP available by default WEBGPU disabled by default: Disabled by default blocked by runtime: WebGPU can only be enabled in nightly -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905054] Re: Firefox 83 Breaks WebGL
Despite it working in The Firefox 84 beta, the Ubuntu build that came out does not work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580596] Re: Xenial & bionic vagrant box disk size is too small
Version 2.525.48 of livecd-rootfs has fixed this issue. Test case: Built a box with the version of livecd-rootfs vagrant box add build.output/livecd.ubuntu-cpc.vagrant.box --name bionic-test vagrant init bionic-test vagrant up vagrant ssh default Run `df -H` inside the vagrant box Observe Disk size of drive mounted at / and observe that the disk is ~ 40G To confirm that this won't break users upgrading to this box, but with < 40G disks, I checked the size of the VMDK backing the box. It was listed at 1.1G. I created a 15G file with `dd if=/dev/urandom of=filename bs=1024 count=15M` I was able to observe the VMDK growing by 15G. So if a user were to have a 10G box fully allocated, and then upgrade to the new box built with the latest version of livecd-rootfs, the user would not be impacted until they tried to fill up the 40G. ** Tags removed: verification-needed-bionic verification-needed-xenial ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580596 Title: Xenial & bionic vagrant box disk size is too small To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1580596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905054]
Can you guys try the Firefox 84b2 build? I tried it from the tarball and it worked perfectly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905054] Re: Firefox 83 Breaks WebGL
If I were to speculate, someone tried to fix the "blocked by env" errors in Firefox 82, in the process actually making that statement true with some kind of fail code. In 84 they may have actually fixed whatever the root problem reporting that message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905054] Re: Firefox 83 Breaks WebGL
I can verify that the beta snap works as well, but I thought you said in comment #2 that is a binary build straight from mozilla. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905054] Re: Firefox 83 Breaks WebGL
It's the "Acceleration blocked by platform" bits that are interesting. It seems that message is there in v82 where it works and v83 where it doesn't. The apparmor check seems relevant with that angle, I just want to make sure that it's not something related to Ubuntu. If it continues to work in 84-final, then I can probably wait to upgrade. I will keep on top of it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905054] Re: Firefox 83 Breaks WebGL
I just realized that the about:support output above is actually for Firefox 82, which is odd, because it does work even though the output suggests it shouldn't. Here's a lot for Firefox 83. The relevant section is different once again: Decision Log HW_COMPOSITING: available by default blocked by env: Acceleration blocked by platform OPENGL_COMPOSITING: unavailable by default: Hardware compositing is disabled WEBRENDER: available by default disabled by env: Not qualified WEBRENDER_QUALIFIED: available by default denied by env: Not on allowlist WEBRENDER_COMPOSITOR: disabled by default: Disabled by default (...) ** Attachment added: "f83.txt" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1905054/+attachment/5437543/+files/f83.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905054] Re: Firefox 83 Breaks WebGL
I just realized that the about:support output I supplied above is from firefox 82. I am confused by the HW_COMPOSITING section, when it clearly works in v82. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905054] Re: Firefox 83 Breaks WebGL
Indeed, I downloaded firefox-84.0b4.tar.bz2 and WebGL works correctly in that build. On 84, compared to 83 above: Decision Log HW_COMPOSITING available by default OPENGL_COMPOSITING available by default WEBRENDER available by default WEBRENDER_QUALIFIED available by default (...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905054] Re: Firefox 83 Breaks WebGL
Here is the output of about:support. I suspect this is the relevant part: Decision Log HW_COMPOSITING: available by default blocked by env: Acceleration blocked by platform OPENGL_COMPOSITING: unavailable by default: Hardware compositing is disabled WEBRENDER: opt-in by default: WebRender is an opt-in feature WEBRENDER_QUALIFIED: available by default denied by env: Not on allowlist WEBRENDER_COMPOSITOR: disabled by default: Disabled by default WEBRENDER_ANGLE: opt-in by default: WebRender ANGLE is an opt-in feature WEBRENDER_DCOMP_PRESENT: opt-in by default: WebRender DirectComposition is an opt-in feature OMTP: available by default WEBGPU: disabled by default: Disabled by default blocked by runtime: WebGPU can only be enabled in nightly The output of app-armor does not mention Firefox. ** Attachment added: "support.txt" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1905054/+attachment/5437540/+files/support.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905054] Re: Firefox 83 Breaks WebGL
Thanks for the ideas. drm driver as listed from lsmod: drm 491520 9 drm_kms_helper,i915 I tried the snap and it behaved the same way, the exact same console output. The snap was version 83.0-2 via snapcraft.io. I assume by "xrg" you mean "xorg"? I have not tried under an xorg session. So, it doesn't look like a packaging issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1905054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905054] [NEW] Firefox 83 Breaks WebGL
Public bug reported: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. ** Affects: firefox (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/1905054 Title: Firefox 83 Breaks WebGL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1905054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889124] Re: package r8168-dkms 8.048.00-1 failed to install/upgrade: installed r8168-dkms package post-installation script subprocess returned error exit status 10
This appears to be the same issue or at least related ** Attachment added: "Kernel 5.8.0-25 fails Builds correctly for 5.4.0-52-generic-x86_64" https://bugs.launchpad.net/ubuntu/+source/r8168/+bug/1889124/+attachment/5432706/+files/make.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889124 Title: package r8168-dkms 8.048.00-1 failed to install/upgrade: installed r8168-dkms package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/r8168/+bug/1889124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898556] [NEW] package ptex-jtex 1.7+1-15 failed to install/upgrade: installed ptex-jtex package post-installation script subprocess returned error exit status 1
Public bug reported: Hi, I do nknow what to write in here ProblemType: Package DistroRelease: Ubuntu 20.04 Package: ptex-jtex 1.7+1-15 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 5 10:24:05 2020 ErrorMessage: installed ptex-jtex package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-09-24 (11 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: ptex-jtex Title: package ptex-jtex 1.7+1-15 failed to install/upgrade: installed ptex-jtex package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ptex-jtex (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898556 Title: package ptex-jtex 1.7+1-15 failed to install/upgrade: installed ptex- jtex package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ptex-jtex/+bug/1898556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891224] [NEW] [Hyper-V] VSS and File Copy daemons intermittently fails to start
Public bug reported: We have most reliably reproduced this on a Standard_B1s in Azure in the North Europe region (>80% of the time). Tests in other regions/VM types do not show this failure as often (<1%). We have reproduced this in Xenial, Bionic, Focal, and Groovy. We saw an increase of test failures around a month ago. >From the journal : Aug 11 09:55:28 ubuntu systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_vss.device: Job sys-devices-virtual-misc-vmbus\x21hv_vss.device/start tim> Aug 11 09:55:28 ubuntu systemd[1]: Timed out waiting for device sys-devices-virtual-misc-vmbus\x21hv_vss.device. Aug 11 09:55:28 ubuntu systemd[1]: Dependency failed for Hyper-V VSS Protocol Daemon. Aug 11 09:55:28 ubuntu systemd[1]: hv-vss-daemon.service: Job hv-vss-daemon.service/start failed with result 'dependency'. Aug 11 09:55:28 ubuntu systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_vss.device: Job sys-devices-virtual-misc-vmbus\x21hv_vss.device/start fai> Aug 11 09:55:28 ubuntu systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_fcopy.device: Job sys-devices-virtual-misc-vmbus\x21hv_fcopy.device/start> Aug 11 09:55:28 ubuntu systemd[1]: Timed out waiting for device sys-devices-virtual-misc-vmbus\x21hv_fcopy.device. Aug 11 09:55:28 ubuntu systemd[1]: Dependency failed for Hyper-V File Copy Protocol Daemon. We've seen problems in the past with KVP daemons that looked very similar : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063 ** 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/1891224 Title: [Hyper-V] VSS and File Copy daemons intermittently fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889509] Re: grub boot error : "symbol 'grub_calloc' not found
Thank you @ianchanning for the recovery notes through the portal. I'll also add in a few links that might help. For users looking for general recovery steps : https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/GRUB2SecureBootBypass#Recovery For users looking how to mitigate this before rebooting: https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/GRUB2SecureBootBypass#Known_issues @hggdh2 Thank you for the informatoin, I am working with rcj on reproducing this issue. I was able to reproduce this issue with the following steps: Launch an Ubuntu VM in Azure az vm create --name grub-test --resource-group --location southcentralus --image Canonical:UbuntuServer:18.04-LTS:18.04.201906271 --size Standard_D2s_v3 --admin-username ubuntu --ssh-key-value Apt update and install grub: sudo apt update DEBIAN_FRONTEND=noninteractive sudo apt install grub2-common You will see a prompt indicating that grub has failed to install. Here's a pastebin of relevant disk information that I was able to gather before I installed grub. In #ubuntu-release on FreeNode there was talk of NVME devices exacerbating this bug, but there are no nvme devices on this instance (as checked by ls /dev/nvme*) https://pastebin.ubuntu.com/p/jD7kgDVtxk/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889509 Title: grub boot error : "symbol 'grub_calloc' not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811368] Re: Elan touchpad fingerprint reader is not recognized by ubuntu 18.10 and 20.04
** Summary changed: - Elan touchpad fingerprint reader is not recognized by ubuntu 18.10 + Elan touchpad fingerprint reader is not recognized by ubuntu 18.10 and 20.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811368 Title: Elan touchpad fingerprint reader is not recognized by ubuntu 18.10 and 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1811368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811368] Re: Elan touchpad fingerprint reader is not recognized by ubuntu 18.10
I'm using Ubuntu 20.04 and I have Elan fingerprint reader 04f3:3057 that cannot work yet. I hope you can solve the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811368 Title: Elan touchpad fingerprint reader is not recognized by ubuntu 18.10 and 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1811368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885159] Re: Firefox 78.0 RC hangs at startup on Ubuntu 16.04
I have this issue too on Ubuntu 16.04.6 LTS with ppa version ; I have a second version that I updated directly from Mozilla beta channel installed in the opt folder that was update from 78.0 b9 and work without any crash If this can help -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885159 Title: Firefox 78.0 RC hangs at startup on Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1885159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834875] Re: cloud-init growpart race with udev
We are seeing some failures still in Eoan (not Focal) with tracebacks involving growpart: 2020-05-29 10:14:29,218 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 851, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 360, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2558, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 307, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 206, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/465f461c-537a-4d09-acae-cf4469c962c5' It is still an intermittent failure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-initramfs-tools/+bug/1834875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580596] Re: Xenial & bionic vagrant box disk size is too small
** Description changed: [Impact] Users could not use vagrant boxes as a full computer (or anything requiring more than 10G of memory). This was a regression from our behavior in 14.04 [Test Case] vagrant init ubuntu/bionic64 (replace with ubuntu/eoan64 or ubuntu/xenial64 as needed) vagrant up vagrant ssh default Run `df -H` inside the vagrant box Observe Disk size of drive mounted at / (before the fix it will list ~10G, after the fix it will list ~40G) [Regression Potential] Making the disk size bigger for vagrant boxes does not increase the size of the box when running (not until that extra size is used). Therefore, the regression potential is low, as users with under 40G of disk space are still able to launch the new Vagrant images without running out of space. The 40G was also present in 14.04, which should improve confidence that - our users can use 40G Vagrant images. + our users can use 40G Vagrant images. This has also released with 20.04. [Original Description] The ubuntu/xenial64 box has only 10GB of disk whereas it was 40GB with the trusty box. This makes the box not really usable as a desktop computer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580596 Title: Xenial & bionic vagrant box disk size is too small To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1580596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580596] Re: Xenial & bionic vagrant box disk size is too small
** Description changed: - The ubuntu/xenial64 box has only 10GB of disk whereas it was 40GB with - the trusty box. + [Impact] + Users could not use vagrant boxes as a full computer (or anything requiring more than 10G of memory). This was a regression from our behavior in 14.04 + + [Test Case] + + vagrant init ubuntu/bionic64 (replace with ubuntu/eoan64 or ubuntu/xenial64 as needed) + vagrant up + vagrant ssh default + Run `df -H` inside the vagrant box + Observe Disk size of drive mounted at / (before the fix it will list ~10G, after the fix it will list ~40G) + + [Regression Potential] + + Making the disk size bigger for vagrant boxes does not increase the size + of the box when running (not until that extra size is used). Therefore, + the regression potential is low, as users with under 40G of disk space + are still able to launch the new Vagrant images without running out of + space. + + The 40G was also present in 14.04, which should improve confidence that + our users can use 40G Vagrant images. + + [Original Description] + The ubuntu/xenial64 box has only 10GB of disk whereas it was 40GB with the trusty box. This makes the box not really usable as a desktop computer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580596 Title: Xenial & bionic vagrant box disk size is too small To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1580596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580596] Re: Xenial & bionic vagrant box disk size is too small
** Merge proposal unlinked: https://code.launchpad.net/~patviafore/livecd-rootfs/+git/livecd-rootfs/+merge/384634 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580596 Title: Xenial & bionic vagrant box disk size is too small To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1580596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580596] Re: Xenial & bionic vagrant box disk size is too small
** Also affects: cloud-images/bb-series Importance: Undecided Status: New ** Also affects: cloud-images/x-series Importance: Undecided Status: New ** No longer affects: cloud-images/bb-series ** No longer affects: cloud-images/x-series -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580596 Title: Xenial & bionic vagrant box disk size is too small To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1580596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580596] Re: Xenial & bionic vagrant box disk size is too small
** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Pat Viafore (patviafore) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580596 Title: Xenial & bionic vagrant box disk size is too small To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1580596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876139] Re: Groovy cloud-images failing during growpart
This is now fixed, thank you ** Changed in: cloud-images Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876139 Title: Groovy cloud-images failing during growpart To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1876139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876139] Re: Groovy cloud-images failing during growpart
We're wary of fdisk being in a seed for cloud-image, because we want to make sure we remain consistent with the rest of the distro and bringing an old package forward with us (say if we as a distro move towards gdisk). I'm good with cloud-init depending on fdisk (or sometime in the future, gdisk) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876139 Title: Groovy cloud-images failing during growpart To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1876139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834875] Re: cloud-init growpart race with udev
Yes, we see it on Eoan and blocking tests, so if you could SRU it there, it'd be much appreciated. We have never seen it on Bionic to my knowledge. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834875] Re: cloud-init growpart race with udev
Sorry, we were waiting on a bug regarding dictionary keys being modified to resolve before we could verify this. We have not seen this in the past couple of runs in our testing, so I think we're good to proceed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM
We are no longer seeing this issue with the latest images. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820063 Title: [Hyper-V] KVP daemon fails to start on first boot of disco VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841827] Re: Install of linux-modules-nvidia requires a reboot before nvidia-smi recognizes driver
Nouveau was blacklisted in our images, so I am no longer seeing this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841827 Title: Install of linux-modules-nvidia requires a reboot before nvidia-smi recognizes driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1841827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834875] Re: cloud-init growpart race with udev
Adding in a passing version of journalctl ** Attachment added: "passing_journalctl_output.txt" https://bugs.launchpad.net/cloud-init/+bug/1834875/+attachment/5326024/+files/passing_journalctl_output.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834875] Re: cloud-init growpart race with udev
I'm attaching the output of a failing build ** Attachment added: "failing_journalctl_output.txt" https://bugs.launchpad.net/cloud-init/+bug/1834875/+attachment/5325941/+files/failing_journalctl_output.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851064] Re: [SRU] Update WALinuxAgent to 2.2.45
I have tested in Bionic, Xenial and Eoan. I've done reboot testing, verified that waagent is running, and that waagent booted with no errors. I have also performed our automated Azure testing suite on each image. It looks good from our end. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851064 Title: [SRU] Update WALinuxAgent to 2.2.45 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1851064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834875] Re: cloud-init growpart race with udev
I can get that going, and will report back on this bug when I have more information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858844] Re: [Dell XPS 15 9575] Screen brightness stopped working with linux-image-5.4.0-9-generic
For those looking for a workaround in the meantime, I've found that lxqt-config-brightness -i and lxqt-config-brightness -d on the command line are still able to control the screen brightness in my setup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858844 Title: [Dell XPS 15 9575] Screen brightness stopped working with linux- image-5.4.0-9-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857007] [NEW] Ubuntu now freezes from the start
Public bug reported: I now update the graphic driver and ubuntu 19.10 freezes from the start. Reboot is necessary.Multiple times until it works. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: julia 1069 F pulseaudio /dev/snd/controlC0: julia 1069 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Dec 19 13:03:13 2019 HibernationDevice: RESUME=UUID=b7cdfca6-a479-4b51-afb2-fdd14b39b95c MachineType: Dell Inc. Precision M4500 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-11-13 (35 days ago) dmi.bios.date: 11/20/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 041WH1 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd11/20/2010:svnDellInc.:pnPrecisionM4500:pvr0001:rvnDellInc.:rn041WH1:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4500 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857007 Title: Ubuntu now freezes from the start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856297] Re: Processes freeze and need to restart -skill will not stop the process
Can it be a graphic card issue when i am having the problem -Computer partially freezes and software updater will not respond. This also happens at different times. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/linux/+question/687302 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856297 Title: Processes freeze and need to restart -skill will not stop the process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1856297] Re: Processes freeze and need to restart -skill will not stop the process
I am not sure how I should check that ? I down graded because i was having problems. Am 17.12.19 um 08:56 schrieb Kai-Heng Feng: > Does this issue happen if proprietary Nvidia driver is used instead? > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856297 Title: Processes freeze and need to restart -skill will not stop the process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856297] [NEW] Processes freeze and need to restart -skill will not stop the process
Public bug reported: i first thought that it is a graphic issue. but update Manager freezes as well. that does not block ubuntu but but some programs we hen they freeze do ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: julia 1271 F pulseaudio /dev/snd/controlC0: julia 1271 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 10:34:11 2019 HibernationDevice: RESUME=UUID=b7cdfca6-a479-4b51-afb2-fdd14b39b95c MachineType: Dell Inc. Precision M4500 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-11-13 (29 days ago) dmi.bios.date: 11/20/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 041WH1 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd11/20/2010:svnDellInc.:pnPrecisionM4500:pvr0001:rvnDellInc.:rn041WH1:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4500 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856297 Title: Processes freeze and need to restart -skill will not stop the process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840686] Re: Xenial images won't reboot if disk size is > 2TB when using GPT
I have run our tests and am satisfied with the results. Our tests very closely matches what mruffell posted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840686 Title: Xenial images won't reboot if disk size is > 2TB when using GPT To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1840686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840686] Re: Xenial images won't reboot if disk size is > 2TB when using GPT
I have re-ran my test cases and the package you provided fixes the original issue that we saw. Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840686 Title: Xenial images won't reboot if disk size is > 2TB when using GPT To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1840686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843796] Re: ubuntu-drivers install --gpgpu should use a DKMS fallback when no linux-modules-nvidia package is available
I have tested this package in bionic-proposed, and all of my test cases passed. Tests cases: Testing NVIDIA drivers install on non-GPU instance does nothing Testing NVIDIA drivers install on GPU instance Specifying different versions for NVIDIA drivers install -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843796 Title: ubuntu-drivers install --gpgpu should use a DKMS fallback when no linux-modules-nvidia package is available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1843796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841827] Re: Install of linux-modules-nvidia requires a reboot before nvidia-smi recognizes driver
So after doing a little more digging: A modprobe -r nouveau will fix this. After issuing this command, an install does not require a reboot for nvidia-smi to find the driver. We are planning on blacklisting the module in our cloud images to address this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841827 Title: Install of linux-modules-nvidia requires a reboot before nvidia-smi recognizes driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1841827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841827] [NEW] Install of linux-modules-nviida requires a reboot before nvidia-smi recognizes driver
Public bug reported: When installing linux-modules-nvidia-418-generic using apt, I expect the nvidia driver to be available immediately after the install completes. However, I must reboot before nvidia-smi returns driver information. AS a side note: sudo udevadm control --reload && sudo udevadm trigger does not cause the driver to appear before the reboot. I was testing this on Disco. System information found in attachment. ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Attachment added: "System information" https://bugs.launchpad.net/bugs/1841827/+attachment/5285467/+files/disco-sysinfo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841827 Title: Install of linux-modules-nviida requires a reboot before nvidia-smi recognizes driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1841827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840686] Re: Xenial images won't reboot if disk size is > 2TB when using GPT
** Description changed: CPC team has recently converted Xenial images to use GPT instead of MBR. However, after booting an instance that has a disk size of 2049 GB or higher, we hang on the next subsequent boot (Logs indicate it hanging on "Booting Hard Disk 0". This works on Bionic, but what makes it strange is that they have the same kernel revision - 4.15.0-1-37. patrick_viafore@patviafore-test-3072-xenial:~$ lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 patrick_viafore@patviafore-test-3072-xenial:~$ sudo dpkg -l | grep linux-gcp ii linux-gcp4.15.0.1037.51 amd64Complete Google Cloud Platform (GCP) Linux kernel and headers ii linux-gcp-headers-4.15.0-10374.15.0-1037.39~16.04.1 amd64Header files related to Linux kernel version 4.15.0 To reproduce: 1) Create an image with a disk size of 3072 using a serial that has GPT gcloud compute instances create test-3072-xenial --image daily-ubuntu-1604-xenial-v20190731 --image-project ubuntu-os-cloud-devel --boot-disk-size 3072 Reboot the instance 2) It will hang on reboot and you cannot connect 3) Please note that later serials have the GPT change reverted. You can replace xenial with bionic in the above commands to get a bionic instance instead. - To test this out in a more slower fashion: - 1) Create an image with a disk size of 2048 using a serial that has GPT gcloud compute instances create test-2048-xenial --image daily-ubuntu-1604-xenial-v20190731 --image-project ubuntu-os-cloud-devel --boot-disk-size 2048 2) Resize the disk to 3072 3) Issue growpart /dev/sda 1 4) Issue resize2fs /dev/sda1 - 5) Issue rsize2fs /dev/sda1 instead + 5) Issue rsize2fs /dev/sda1 again On the second resize2fs, it tries to resize again, but on a working instance, it says there's nothing to resize. - - I've tried starting from a Xenial instance and doing a do-release-upgrade to get to bionic and then doing the growpart/resize2fs, but the issue still shows up. + I've tried starting from a Xenial instance and doing a do-release- + upgrade to get to bionic and then doing the growpart/resize2fs, but the + issue still shows up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840686 Title: Xenial images won't reboot if disk size is > 2TB when using GPT To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1840686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840686] Re: Xenial images won't reboot if disk size is > 2TB when using GPT
At first I thought it was related to https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=1e19b01be31fc5264a84d246023ecf29e44949df=25=0=0, and later I thought it was related to https://bugs.launchpad.net/bugs/1762748. However, I added the bionic archives to my Xenial instance and updated e2fsprogs and cloud-utils, then tried to grow the disk past 2048, and ran into the reboot issue again. I agree it was very close to, and the recreate information in that bug helped me narrow down what I was seeing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840686 Title: Xenial images won't reboot if disk size is > 2TB when using GPT To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1840686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840710] [NEW] EULA never offered for Nvidia drivers install
Public bug reported: Relevant system information here: https://pastebin.canonical.com/p/q6XqWt6THQ/ I was expecting that when I installed linux-modules-nvidia-generic-418 that I would get an option to accept or reject a EULA. However, on installation, no prompt is given to me, and after a reboot, I am able to see the driver with a `nvidia-smi` command. After doing some digging, installing this package writes out /etc/default/linux-modules-nvidia with latelink=true, and my debconf database also has a boolean for nvidia latelink set to true. ** Affects: linux-restricted-modules (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/1840710 Title: EULA never offered for Nvidia drivers install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1840710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
