The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips
The issue doesn't seem likely due to the settings UI, rather a driver
bug. Reassigning to the kernel, could add your 'journalctl -b 0' log to
the bug?
** Package changed: gnome-control-center (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
You have been subscribed to a public bug:
Intel AC9260 will connect to 5G WiFi without issue. However, after a
few minutes of use, the connection will slow to a crawl and eventually
time out until manually switched to a traditional WiFi. Other devices
on the same 5G network do not experience
The test results:
Model: PB71RD
board_name: PB50_70RF,RD,RC
- Ubuntu 18.04.3
suspend and wake up works, no other problems found
- Ubuntu 19.10
not possible to test as the system behaves very unstable even without the new
driver
Model: P970RC
board_name: P9XXRC
- Ubuntu 18.04.3
suspend and
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1845810
Title:
[XPS 13 9360, Realtek ALC3246, Black Headphone Out,
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
Hi Verdre,
>I'm making progress with figuring out potential workarounds for this issue
>right now, seems like the "Firmware wakeup failed" error on resume indeed is
>caused by another issue (that might still be related to PCI connection/ASPM
>issues) than the command timeout
OK; Thanks for this;
Hi Ganapathi,
I'm making progress with figuring out potential workarounds for this
issue right now, seems like the "Firmware wakeup failed" error on resume
indeed is caused by another issue (that might still be related to PCI
connection/ASPM issues) than the command timeout: I wasn't seeing the
> Could you give inputs on how did you get Fedora 30 installed on Surface 4; I
> created the image using 'dd' and tried to boot from it;It would get to grub,
> after I was getting the _ cursor forever;
That's weird, not sure why that wouldn't be working, if you get to grub
you probably did
Hi Ganapathi,
> OK; Thanks for this; I read it as 'these two issues have different root
> causes';
Not sure if that's the case since we enable link power saving after
every suspend again.
> it is enabled(above output of lspci -vvv); but is there a seperate check to
> know if it could be
Hi Verdre,
>Or you could try out Fedora 31 beta, which should have a 5.3 kernel
Thanks for this, it worked for me;
Now, I try to recreate like below(power save enabled):
1. connect to a known AP
2. ping to AP for few seconds
3. suspend(use rtcwake) and resume
4. goto #1
I do not see the error
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Assignee: (unassigned) => Andy Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Hi Verdre,
Could you give inputs on how did you get Fedora 30 installed on Surface
4; I created the image using 'dd' and tried to boot from it;It would get
to grub, after I was getting the _ cursor forever;
Regards,
Ganapathi
--
You received this bug notification because you are a member of
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
+
401 - 500 of 604 matches
Mail list logo
