Last update removes fractional scaling from gnome-control-center https://launchpad.net/ubuntu/+source/gnome-control-center/+changelog this is a big problem for me because since I have poor eyesight, a 125% or 133% magnification is very useful while a 200% is unusable. Besides, it doesn’t work! Bug #2141837 “gnome-control-center crash clicking on 'Displays'” : Bugs : gnome-control-center package : Ubuntu
2 Likes
I’ve been doing some testing of Ubuntu 26.04, on multiple different virtual machines on different networks. And in all cases I’m seeing /etc/resolv.conf being created containing search . rather than search LOCALDOMAIN (where LOCALDOMAIN is the local domain name).
Given that I’m seeing the problem on fresh installs with no manual changes to them. And on 3 different networks with different dhcp servers. All of which result in the correct resolv.conf search value being populated on older Ubuntu versions (surch as 22.04 and 24.04).
It suggests a regression in the resolv/dhcpclient setup. But I’m somewhat bemused that I can’t find any open bug reports or discussion about it. I thought other people would have noticed this by now? Since any network where you are relying on the dns search path to find other local hostnames, is broken by not having the right search value in /etc/resolv.conf
I can not access display settings at all. Right clicking on the desktop and selecting Display Settings does nothing. Clicking on Displays in Settings gives a not responding or immediate close.
running gnome-control-center from terminal yielded the following when trying to access display settings: GLib-GIO[15870]: ERROR: Settings schema ‘org.gnome.mutter.wayland’ does not contain a key named ‘xwayland-scaling-factor’
Trace/breakpoint trap (core dumped) gnome-control-center
Maybe just because of being in-between package updates? This is very much in a “rolling” state right now as the package base continues to bake.
Was a bug now fixed: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2141837
3 Likes
After linux-firmware changes: * Split linux-firmware into multiple packages (LP: #1958518) doing update i see a lot of error/warning messages like:
readlink: /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p8/driver/module: No such file or directory
readlink: /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/nvme/nvme0/nvme0n1/driver/module: No such file or directory
readlink: /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/nvme/nvme0/driver/module: No such file or directory
readlink: /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/nvme/driver/module: No such file or directory
readlink: /sys/devices/pci0000:00/driver/module: No such file or directory
readlink: /sys/devices/driver/module: No such file or directory
readlink: '/sys/class/extcon/*/driver/module': No such file or directory
should I worry?
Just for the record; I rebooted a little while ago into the latest 6.19 kernel on this resolute box, and my issues accessing element-desktop, opera etc. are all gone.
kernel fix 6.19.0-6.6
---------------
linux (6.19.0-6.6) resolute; urgency=medium
* resolute/linux: 6.19.0-6.6 -proposed tracker (LP: #2142114)
* Resolute update: v6.19.2 upstream stable release (LP: #2142112)
- Revert "driver core: enforce device_lock for driver_match_device()"
- Linux 6.19.2
* Resolute update: v6.19.1 upstream stable release (LP: #2142111)
- io_uring/io-wq: add exit-on-idle state
- io_uring: allow io-wq workers to exit when unused
- smb: client: split cached_fid bitfields to avoid shared-byte RMW races
- ksmbd: fix infinite loop caused by next_smb2_rcv_hdr_off reset in error
paths
- ksmbd: add chann_lock to protect ksmbd_chann_list xarray
- smb: server: fix leak of active_num_conn in ksmbd_tcp_new_connection()
- smb: smbdirect: introduce smbdirect_socket.recv_io.credits.available
- smb: smbdirect: introduce smbdirect_socket.send_io.bcredits.*
- smb: server: make use of smbdirect_socket.recv_io.credits.available
- smb: server: let recv_done() queue a refill when the peer is low on
credits
- smb: server: make use of smbdirect_socket.send_io.bcredits
- smb: server: fix last send credit problem causing disconnects
- smb: server: let send_done handle a completion without IB_SEND_SIGNALED
- smb: client: make use of smbdirect_socket.recv_io.credits.available
- smb: client: let recv_done() queue a refill when the peer is low on
credits
- smb: client: let smbd_post_send() make use of request->wr
- smb: client: remove pointless sc->recv_io.credits.count rollback
- smb: client: remove pointless sc->send_io.pending handling in
smbd_post_send_iter()
- smb: client: port and use the wait_for_credits logic used by server
- smb: client: split out smbd_ib_post_send()
- smb: client: introduce and use smbd_{alloc, free}_send_io()
- smb: client: use smbdirect_send_batch processing
- smb: client: make use of smbdirect_socket.send_io.bcredits
- smb: client: fix last send credit problem causing disconnects
- smb: client: let smbd_post_send_negotiate_req() use smbd_post_send()
- smb: client: let send_done handle a completion without IB_SEND_SIGNALED
- driver core: enforce device_lock for driver_match_device()
- Bluetooth: btusb: Add USB ID 7392:e611 for Edimax EW-7611UXB
- ALSA: hda/conexant: Add quirk for HP ZBook Studio G4
- crypto: iaa - Fix out-of-bounds index in find_empty_iaa_compression_mode
- crypto: octeontx - Fix length check to avoid truncation in
ucode_load_store
- crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly
- crypto: virtio - Add spinlock protection with virtqueue notification
- crypto: virtio - Remove duplicated virtqueue_kick in
virtio_crypto_skcipher_crypt_req
- nilfs2: Fix potential block overflow that cause system hang
- hfs: ensure sb->s_fs_info is always cleaned up
- wifi: rtw88: Fix alignment fault in rtw_core_enable_beacon()
- scsi: qla2xxx: Validate sp before freeing associated memory
- scsi: qla2xxx: Allow recovery for tape devices
- scsi: qla2xxx: Delay module unload while fabric scan in progress
- scsi: qla2xxx: Free sp in error path to fix system crash
- scsi: qla2xxx: Query FW again before proceeding with login
- sched/mmcid: Don't assume CID is CPU owned on mode switch
- bus: fsl-mc: fix use-after-free in driver_override_show()
- erofs: fix UAF issue for file-backed mounts w/ directio option
- xfs: fix UAF in xchk_btree_check_block_owner
- drm/exynos: vidi: use ctx->lock to protect struct vidi_context member
variables related to memory alloc/free
- PCI: endpoint: Avoid creating sub-groups asynchronously
- wifi: rtl8xxxu: fix slab-out-of-bounds in rtl8xxxu_sta_add
- Linux 6.19.1
* AppArmor blocks write(2) to network sockets with Linux 6.19 (LP: #2141298)
- SAUCE: apparmor: fix aa_label_sk_perm to check for RULE_MEDIATES_NET
-- Timo Aaltonen <timo.aaltonen@canonical.com> Wed, 18 Feb 2026 14:31:48 +0200
( Whilst I update this install at least three times per day; it takes me a lot longer to reboot, so I’m not always quick testing kernel changes )
1 Like
Display settings is working again and for the first time since owning my ASUS G14 2022 laptop I can finally enable VRR for the inbuilt display. 
Should save some battery/power usage at least as I don’t need 144 Hz all the time for coding!
My external monitor is ancient in comparison so no VRR for that.
Well, now Display settings is working again and I’m waiting for 50% and 75% scale options like in Cosmic desktop. For those with good eyesight and a 27" 1920x1080 monitor, scaling at 75% makes a 2560x1440 monitor which is still very readable on 27"
i filed a bug about those,
Try install from: Ubuntu 26.04 LTS “Resolute Raccoon” - Daily amd64 (20260301)
NOTHING HAPPENS Bug #2142973 “Try install from ISO dated Mar 1 - nothing happens...” : Bugs : subiquity
‘Preparing Ubuntu’ does not show.
live session works fine
click on icon ‘Install Ubuntu’ does nothing
click on icon ‘Install RELEASE’ does nothing
1 Like
It’s been like that for the last few daily builds. The 4th snapshot from 26th of february starts the installer but goes to “something went wrong”, logs not showing anything.
2 Likes
Bug on snapshot4 was: Bug #2142736 “ModuleNotFoundError: No module named 'curtin.vendo...” : Bugs : subiquity but is now changed to Bug #2142973 “Try install from ISO dated Mar 1 - nothing happens...” : Bugs : subiquity
Note: same problem with ISO from: Ubuntu 26.04 LTS (Resolute Raccoon) Daily Build
“Dangerous ISO” is the same of Daily but the snaps on Dangerous are all at ‘edge’ level.
Since with snaps in case of problems it is always possible to refresh to the ‘stable’ channel, I prefer to install from the “Dangerous” ISO.
I haven’t done a clean install, but I believe I’m fully updated. Now that I’m on GNOME 50 Beta, my extensions have broken as expected; I’ve managed to fix all of them except one.
Regarding the new default Ubuntu extensions, I’ve noticed an issue: the Snapcraft store is only available in English. As a spanish speaker, it feels odd that all my system results are in Spanish except for the new apps, so I’ve decided to disable it. Web searches are also English-only for now, though I assume they will eventually be localized. Still, I think being able to perform direct searches from there is a great improvement.
On the other hand, I’m still having trouble playing audio in Firefox and Spotify (Snap version). Conversely, I was finally able to install the NVIDIA drivers, which had been impossible for me since the arrival of Kernel 6.19.
I’m still happy with how this LTS is progressing. I’m looking forward to april so I can finally update my main work computer.
You mean snap-store == AppCenter? It seems strange to me that it isn’t in Spanish, given that it is in Italian.
try sudo snap remove snap-store
and then sudo snap install snap-store
App Center is in spanish; what isn’t in spanish are the Snap descriptions. I don’t mind seeing them in english within the App Center, but it feels weird in the GNOME search bar.
I’ve also noticed that the module is showing up twice, although one of them finds more results:
Lot of messages from apparmor: apparmor=“DENIED” operation=“open” class=“file” profile=“snap.firefox.firefox” name=“/proc/pressure/memory” https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2143001
Yes, same result when booting from snapshot 4. Once ‘something went wrong’ is shown, I opened a terminal session and manually started the bootstrap (typing from yesterday memory here, snap exec line found at the he Desktop shortcut that’s in ~/Desktop). For me, it gives a ‘not found error’ on ‘libc.so.6 GLIBC_2.42’. Did a full apt update&upgrade, updated the bootstrap snap.
2026-03-01T08:46:23.727376+00:00 ubuntu ubuntu-desktop-bootstrap[6064]: /bin/bash: /snap/ubuntu-desktop-bootstrap/515/usr/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.42’ not found (required by /usr/lib/x86_64-linux-gnu/libtinfo.so.6)
2026-03-01T08:46:23.727476+00:00 ubuntu systemd[3948]: ubuntu-desktop-installer.service: Main process exited, code=exited, status=1/FAILURE
Not sure what to do now (well, I took snapshot 2, that went well, and updated > 900 packages).
Edit: just saw it’s a bug, registered as #2142973
1 Like
GDM3 50 beta breaks login screen on FreeIPA-joined systems (Ubuntu 26.04) ?
Looks like the FreeIPA client and Ubuntu’s latest gdm3/gnome-session update from Friday broke logins. The change seems to cause the login screen to try to login to the gdm-greeter account instead.
After a lot of digging, here’s what’s actually happening:
GDM 50 beta introduced a new dynamic user system that allocates a temporary UID for the greeter session in the range 60578-60705. The problem is FreeIPA also allocates UIDs in that range (atleast for our FreeIPA server), so when GDM tries to spin up the greeter it collides with a FreeIPA domain user named “gdm-greeter” at uid=60578.
This didn’t happen with gdm3 49.2 because the greeter wasn’t launched as a full Wayland session back then. The new architecture in 50 beta creates a proper systemd-logind session for the greeter, which is what triggers the UID conflict.
Workaround until this is fixed:
Add this to /etc/gdm3/custom.conf:
[daemon]
AutomaticLoginEnable = true
AutomaticLogin = yourusername
Not ideal since it removes the password prompt on boot, but it gets you back in.
Has anyone else hit this? Is there already a bug filed for it, or are the developers aware? Would like to know if this is a known issue before submitting a report.
Successful install from Ubuntu 26.04 LTS “Resolute Raccoon” - Daily amd64 (20260304) Install (manual partitioning) in Ubuntu Desktop amd64 in Resolute Daily | Ubuntu QA
2 Likes