Backporting to LTS is a good idea IMHO. A few additional use cases to
consider
- Users on the threshold who experience slight initrd image growth due
to any module update
- Users who thought they might be able to continue just using older
images may fail to recognize grub will eventually remove
-> If an user somehow met this issue, then the system is not able to
boot.
It can boot, if it did previously, and this issue will get fixed pretty
quick IMHO in the updates repository given it impacts current 20.04,
22.04 and 22.10.
Here is just the workaround part, for current 22.10 or 22.04 to
Worth noting this had the unintended consequence of temporarily breaking
some modern certified systems, like my XPS 13 9380 when jumping from
22.04 to 22.10, in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320
--
You received this bug notification because you are a member of Ubuntu
To
My XPS 13 9380 (no luks) also triggers this on 5.19 after the 22.10
upgrade; I can see the initrd is about 7% bigger in 22.10 over 22.04.
-rw-r--r-- 1 root root 111203941 Oct 30 18:16 initrd.img-5.15.0-52-generic
-rw-r--r-- 1 root root 120222346 Oct 31 21:39 initrd.img-5.19.0-23-generic
#103
We have noticed this as well. Using VPN we use a special resolver to
handle private IP space, and now, looking into this further it does look
like the network-manager is ignoring the dns= specified in the system-
connections (set via the network manager settings gui).
My settings below, noting X.
I managed to bring both screens up at 30Hz by passing video resolutions
as kernel parameters
video=DP-3:3840x2160@30 video=DP-4:3840x2160@30
This means I do not have to do any display port replugging on startup.
I still have to manually change the refresh from 30Hz to 60Hz in the
settings. If th
Public bug reported:
I recently started using a Cable-Matters-201355 with my XPS 9380 (8th
Gen TB3). The dock supports dual 4K DP @ 60Hz via thunderbolt with PD
input. (HBR3 compliant USB-C Dock (DSC/DP1.4 support) that uses all 4
high speed lanes to get dual 60Hz)
Both displays boot mirrored wh
Below is the output after I made the change and continued the 16.04
dist-upgrade process.
820 upgraded, 17 newly installed, 3 to remove and 144 not upgraded.
215 not fully installed or removed.
Need to get 0 B/494 MB of archives.
After this operation, 142 MB of additional disk space will be used.
So,
I have no idea what happened; manual setting of localtime to UTC
(command below) fixed the configuration of the package, allowing the
upgrade to continue.
Anyway, I executed the following command to set to UTC, and then
proceeded to complete the dist-upgrade from 15.05, and the error from
tz
Public bug reported:
Everything looks fine; Not sure what is invalid about the format. I am
EST, the output is in UTC.
Breaks the upgrade after from 15.05 at a point where is says it
completed with errors, but some 200+ packages remaining.
Setting up tzdata (2016a-1) ...
Current default time
Still present in 15.10; I rewired a new jack twice before I realized
what was going on here.
# lspci
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller
(rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen
Core Processor Integrated Grap
Public bug reported:
In order to enable X11 forwarding from an external host you must
explicitly set the Xserver to listen by overriding the xserver-command.
Previously you could set the xserver-allow-tcp=true and it would do this
automatically.
I would have expected this change in behaviour to s
12 matches
Mail list logo
