It tried several times to install Ubuntu 26.10 daily build in my boxes virtual machine. It starts all right but at the Installation screen it does not start installation when clicking the Installation button. Tried with Lubuntu and Xubuntu 26.10 daily and both these version do install properly.
Why does Ubuntu 26.10 not install?
can someone please explain options more clearly please? Snap related?
Frequently Firefox freezes while I'm reading a lengthy page, so I've been doing lots of scrolling. Generally the pages have lots of graphics as well. Eventually either there's a Firefox not responding error or a gjs not responding error. This also happened on Firefox 151 and I was hoping 152 would fix it. This happens at least once a day. Running on a laptop with 4Gb ram. Firefox 152.0.3 gjs 1.72.4 Graphics card is Intel. My network speed varies between 40 and 60 checking on FAST. Having read about possible problems with RAM and swap overload using Firefox, I ran free -h with Firefox open, 3 tabs, and terminal the only apps running. There was 892Mb free RAM and 1.7G free swap. Odd that some resources suggested turning off hardware acceleration while Mozilla says turn it on for Firefox freezes. What are possible causes and fixes?
First of all, these are the laptop's specs:
Model: SAMSUNG LTD. 300E4A/300E5A/300E7A
Memory: 4 GiB
Processor: Intel Core i5-2450M x 4
Graphics: Intel HD Graphics 3000 (SNB GT2)
Disk: 1 TB HDD
It's old (10+ years) and I wanted to give it a new life just for lightwork. I checked and it is not under the supported hardware for ubuntu, but used the Try Ubuntu feature and it works, so I assume that even if it hasn't been tested to be in the supported devices tab it should work just fine.
The problem:
After the install process I rebooted and the PC asked to remove the bootable device and press enter, so I removed the USB flash drive I used and press enter. Now, when I try to boot the PC, it just gets stuck in a loop, trying to boot up. I can't get into the grub menu by holding down the Shift key. The only thing I can do is boot into BIOS in the Boot settings. I only have the option to change the Boot Priority Order. Another device appear on the list besides the HDD. I already tried changing the priorities, but nothing changes.
If I boot up with the bootable USB connected the grub menu appears without any input from me, and only two options are available: "Try or Install Ubuntu", and "Ubuntu (safe graphics)". The first time I clicked on the first option and just reinstalled the OS but the problem didn't go away. I can close the install window if I boot like that again and use Ubuntu as the Try Ubuntu feature, but nothing more.
I already tried different things I found online in forums, but I don't have the exact same issues or menus/options.
For example,I tried the solution in this forum, but I don't have the add customized boot option in my BIOS.
I also tried this one, but I don't have the Advanced options for Ubuntu on my GRUB menu.
The other thing that I tried was Boot-Repair twice. The first time it have back this link: https://paste.ubuntu.com/p/bpsF9b8Nqh/, and said to share it if the problem persists (which it does), and it also gave me this warning.
The second time I tried using Boot-Repair I got this error message: Glade2script-python3 Is Not Responding.
I screen recorded what happens when I turn on the PC with and without the USB:
Video 1: Booting without bootable USB and getting into BIOS
Video 2: Booting with bootable USB
I'm afraid I've gotten myself into something that's way above my understanding (I never used Linux before).
Edit: Result of sudo fdisk -l
Disk /dev/loop0: 3.19 GiB, 3422658560 bytes, 6684880 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop1: 565.31 MiB, 592769024 bytes, 1157752 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop2: 770.16 MiB, 807575552 bytes, 1577296 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop3: 19.65 MiB, 20602880 bytes, 40240 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop4: 66.85 MiB, 70094848 bytes, 136904 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop5: 273.7 MiB, 286994432 bytes, 560536 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop6: 16.5 MiB, 17301504 bytes, 33792 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop7: 4 KiB, 4096 bytes, 8 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: SAMSUNG HN-M101M
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: D564C26C-C9BF-49E9-9DC6-3A995C70E836
Device Start End Sectors Size Type
/dev/sda1 2048 4095 2048 1M BIOS boot
/dev/sda2 4096 1953521663 1953517568 931.5G Linux filesystem
Disk /dev/sdb: 14.51 GiB, 15581839360 bytes, 30433280 sectors
Disk model: STORE N GO
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x39ed4277
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 30433247 30431200 14.5G c W95 FAT32 (LBA)
Disk /dev/loop8: 606.08 MiB, 635518976 bytes, 1241248 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop9: 91.69 MiB, 96141312 bytes, 187776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop10: 394.98 MiB, 414167040 bytes, 808920 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop11: 18.82 MiB, 19738624 bytes, 38552 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop12: 15.69 MiB, 16449536 bytes, 32128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop13: 49.26 MiB, 51654656 bytes, 100888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop14: 227.55 MiB, 238604288 bytes, 466024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop15: 115.26 MiB, 120856576 bytes, 236048 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop16: 580 KiB, 593920 bytes, 1160 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
How would I copy several directories of files to a USB drive without delayed write?
In years past there has been a few suggestions however those posts usually provide a system wide answer. I'd prefer to limit delayed write on a drive by drive basis.
Adding the sync command appears to only sync the delayed write at the end of the copy rather than as each file is copied.
I am using XUbuntu 24.04 and 26.04
Just upgraded from 24.10 to 26.04 on VMware for W11. When I run:
gvim -geometry n1xn2+n3+n4
While n1 and n2 are understood properly, n3 and n4 are ignored, and the gvim window starts up in the center of the VM window. This was not a problem under 24.10 or before.
Thanks. Norm
From the App Center: I search for kdiskmark, click the install button, it turns very briefly to "installing" then goes back to Install. No error message or other indication of a problem.
From the snap store: instructions say to run: "sudo snap install kdiskmark" Result:
error: cannot perform the following tasks:
- Ensure prerequisites for "kdiskmark" are available (cannot install prerequisite "kde-frameworks-5-core18": no snap revision available as specified)
I found a random AppImage "KDiskMark-3.1.3-fio-3.34-x86-64.AppImage" on the Internet (bad for security). When run it reports "No FIO was found. Please install FIO before using kdiskmark". I ran "sudo apt install fio" which completed but had no effect on kdiskmark.
I tried to register an Ubuntu one account (three times) so I could post this question on the Ubuntu Discourse. At the last page of the registration process: "Oops...something went wrong."
I would be grateful if someone can tell me how install kdiskmark on Ubuntu 26.04. I don't understand why this would be difficult. It is right there in the Ubuntu App Centre.
Thanks.
My Ubuntu 24.04 machine will randomly restart. Often it hangs while doing so. Sometimes it is successful.
I am looking for an answer that will guide me through the steps I should take to home in on why this is happening. I would like to learn the steps to take to solve this mystery for myself.
I'm running Linux 6.17.0-35-generic on 24.04 with Wayland windowing and Gnome 46 (in case that makes a difference to the steps I should take).
Хочу установить synaptic, но выпадает ошибка. Прошу помощи. Текст с терминала ниже. Версия Ubuntu 25.10.
sudo apt install synaptic -y
Чтение списков пакетов… Готово
Построение дерева зависимостей… Готово
Чтение информации о состоянии… Готово
Вы можете запустить «apt --fix-broken install» для исправления этих ошибок.
Следующие пакеты имеют неудовлетворённые зависимости:
libc-bin : Зависит: libc6 (< 2.40) но 2.42-0ubuntu3.1 должен быть установлен
libc-dev-bin : Зависит: libc6 (< 2.40) но 2.42-0ubuntu3.1 должен быть установлен
Рекомендует: libc-devtools (> 2.39) но он не может быть установлен
libc6-dbg : Зависит: libc6 (= 2.39-0ubuntu8.7) но 2.42-0ubuntu3.1 должен быть установлен
libc6-dev : Зависит: libc6 (= 2.39-0ubuntu8.7) но 2.42-0ubuntu3.1 должен быть установлен
libnss-systemd : Зависит: systemd (= 255.4-1ubuntu8.16)
libpam-systemd : Зависит: systemd (= 255.4-1ubuntu8.16)
locales : Зависит: libc-bin (> 2.42)
synaptic : Зависит: libapt-inst2.0 (>= 0.8.16~exp12) но он не будет установлен
Зависит: libapt-pkg5.0 (>= 1.1~exp9) но он не будет установлен
Зависит: libept1.5.0 но он не будет установлен
Зависит: libgdk-pixbuf2.0-0 (>= 2.22.0) но он не будет установлен
Зависит: libxapian30 но он не будет установлен
Рекомендует: libgtk2-perl (>= 1:1.130) но он не будет установлен
Рекомендует: rarian-compat но он не будет установлен
systemd-sysv : Зависит: systemd (= 255.4-1ubuntu8.16)
N: Игнорируется файл «element-io.list.migrate» в каталоге «/etc/apt/sources.list.d/», так как он имеет неправильное расширение
E: Неудовлетворённые зависимости. Попытайтесь выполнить «apt --fix-broken install», не указывая имени пакета (или указав решение).
I know this question has been asked before for previous versions of Ubuntu but I cant seem to get .NEF raw photo thumbnails in my standard file manager which I think is known as Nautilus?
What is the correct way of achieving this?
SOLVED: https://github.com/emuskardin/nautilus-raw-thumbnails - copy github installation code.
I’m just not able to have this succeeds, whatever the mirror I use (mirror not shown in the command):
fakechroot fakeroot debootstrap noble root
It always ends with:
W: Failure while configuring required packages.
W: See /…/root/debootstrap/debootstrap.log for details (possibly the package
mawk is at fault)
And that file says:
Setting up base-files (13ubuntu10) ...
Setting up bash (5.2.21-2ubuntu4) ...
update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtin
Processing triggers for libc-bin (2.39-0ubuntu8) ...
Errors were encountered while processing:
mawk
Is it an issue with the mirrors or with debootstrap? I tried multiple different mirrors, including the default one.
Update: surprisingly, there is no issue with pbuilder or cowbuilder, while they too use deboostrap.
However, if I do the same for Debian Bookworm, on which I believe Ubuntu Noble is based, it can finish without any error:
fakechroot fakeroot debootstrap bookworm root http://ftp.fr.debian.org/debian/
…
I: Base system installed successfully.
Before each time I have a try, the root directory is emptied.
As a side note, I need it to try to compile an application which I am not able to compile on XUbuntu. I would like a fakechroot environment to try some things without polluting or breaking the system in use. May be I can use the Debian Bookworm minimal system for that, but I’m not sure, and anyway, it would be cleaner with the Ubuntu Noble minimal system.
IMAGE of shut down:
Must reinstall?
I'm using new Ubuntu (26.04) but there it writes something like this: No KScreen module found. Please check your KScreen installation.
I see it in /usr/bin/systemsettings.
How can I fix it? I tried install it but KScreen doesn't exist.
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 26.04 LTS
Release: 26.04
Codename: resolute
# apt policy kubuntu-desktop systemsettings kscreen
kubuntu-desktop:
Instalovaná verze: (žádná)
Kandidát: 1.496
Tabulka verzí:
1.496 500
500 http://cz.archive.ubuntu.com/ubuntu resolute/universe amd64 Packages
1.451.2 500
500 http://archive.ubuntu.com/ubuntu noble-updates/universe amd64 Packages
1.451 500
500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages
systemsettings:
Instalovaná verze: 4:6.6.4-0ubuntu1
Kandidát: 4:6.6.5-0ubuntu0.1
Tabulka verzí:
4:6.6.5-0ubuntu0.1 500 (fázována 10%)
500 http://cz.archive.ubuntu.com/ubuntu resolute-updates/universe amd64 Packages
*** 4:6.6.4-0ubuntu1 500
500 http://cz.archive.ubuntu.com/ubuntu resolute/universe amd64 Packages
100 /var/lib/dpkg/status
4:5.27.11-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages
kscreen:
Instalovaná verze: 4:6.6.4-0ubuntu1
Kandidát: 4:6.6.5-0ubuntu0.1
Tabulka verzí:
4:6.6.5-0ubuntu0.1 500 (fázována 10%)
500 http://cz.archive.ubuntu.com/ubuntu resolute-updates/universe amd64 Packages
*** 4:6.6.4-0ubuntu1 500
500 http://cz.archive.ubuntu.com/ubuntu resolute/universe amd64 Packages
100 /var/lib/dpkg/status
4:5.27.11-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages
Better version:
# apt policy ubuntu-desktop systemsettings kscreen
ubuntu-desktop:
Instalovaná verze: 1.570
Kandidát: 1.570
Tabulka verzí:
*** 1.570 500
500 http://cz.archive.ubuntu.com/ubuntu resolute/main amd64 Packages
100 /var/lib/dpkg/status
1.539.2 500
500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages
1.539 500
500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
systemsettings:
Instalovaná verze: 4:6.6.4-0ubuntu1
Kandidát: 4:6.6.5-0ubuntu0.1
Tabulka verzí:
4:6.6.5-0ubuntu0.1 500 (fázována 10%)
500 http://cz.archive.ubuntu.com/ubuntu resolute-updates/universe amd64 Packages
*** 4:6.6.4-0ubuntu1 500
500 http://cz.archive.ubuntu.com/ubuntu resolute/universe amd64 Packages
100 /var/lib/dpkg/status
4:5.27.11-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages
kscreen:
Instalovaná verze: 4:6.6.4-0ubuntu1
Kandidát: 4:6.6.5-0ubuntu0.1
Tabulka verzí:
4:6.6.5-0ubuntu0.1 500 (fázována 10%)
500 http://cz.archive.ubuntu.com/ubuntu resolute-updates/universe amd64 Packages
*** 4:6.6.4-0ubuntu1 500
500 http://cz.archive.ubuntu.com/ubuntu resolute/universe amd64 Packages
100 /var/lib/dpkg/status
4:5.27.11-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages
I have had many GPU problems in my current install of Kubuntu (I keep things as updated as possible). The previous GPU, an RX 580 8gb, had overheating issues (now found to be a hardware problem) and a system crashing issue, and now my RX 5500 xt 8gb also has a problem of randomly crashing in the game Cyberpunk 2077, and so far nowhere else. The game seems to be unstable on its own, as it can crash and glitch outside of graphics crashes. I am running it in medium graphics in windowed mode, on proton hotfix.
I have followed the guide "Dummy's guide to AMD GPU Issues", and besides enabling "amdgpu.gpu_recovery=1" in grub (which hasn't stopped crashing), this is the output I have been able to gather of all the goings-on in my system:
GPU: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5300/5500M] (rev c5)
Kernel: 7.0.0-27-generic
amdpgu driver info:
srcversion: 0E0CFBE086FCC89A36050F4
vermagic: 7.0.0-27-generic SMP preempt mod_unload modversions
parm: hws_gws_support:Assume MEC2 FW supports GWS barriers (false = rely on FW version check (Default), true = force supported) (bool)
Result of "sudo dmesg | grep -i "amdgpu\|gpu\|fence\|timeout" | tail -50":
# note: this appears to be the system after a boot, no info on the time of any crash.
[ 8.900765] amdgpu 0000:03:00.0: Trusted Memory Zone (TMZ) feature disabled as experimental (default)
[ 8.900807] amdgpu 0000:03:00.0: vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
[ 8.900816] amdgpu 0000:03:00.0: VRAM: 8176M 0x0000008000000000 - 0x00000081FEFFFFFF (8176M used)
[ 8.900818] amdgpu 0000:03:00.0: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
[ 8.900827] amdgpu 0000:03:00.0: [drm] Detected VRAM RAM=8176M, BAR=256M
[ 8.900828] amdgpu 0000:03:00.0: [drm] RAM width 128bits GDDR6
[ 8.900995] amdgpu 0000:03:00.0: 8176M of VRAM memory ready
[ 8.900997] amdgpu 0000:03:00.0: 7971M of GTT memory ready.
[ 8.901022] amdgpu 0000:03:00.0: [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 8.901117] amdgpu 0000:03:00.0: [drm] PCIE GART of 512M enabled (table at 0x0000008000900000).
[ 8.902615] amdgpu 0000:03:00.0: [VCN instance 0] Found VCN firmware Version ENC: 1.24 DEC: 8 VEP: 0 Revision: 9
[ 9.059120] amdgpu 0000:03:00.0: reserve 0x900000 from 0x81fd000000 for PSP TMR
[ 9.102514] amdgpu 0000:03:00.0: RAS: optional ras ta ucode is not available
[ 9.108541] amdgpu 0000:03:00.0: RAP: optional rap ta ucode is not available
[ 9.108544] amdgpu 0000:03:00.0: SECUREDISPLAY: optional securedisplay ta ucode is not available
[ 9.108593] amdgpu 0000:03:00.0: use vbios provided pptable
[ 9.108595] amdgpu 0000:03:00.0: smc_dpm_info table revision(format.content): 4.5
[ 9.138961] amdgpu 0000:03:00.0: SMU is initialized successfully!
[ 9.139327] amdgpu 0000:03:00.0: [drm] Display Core v3.2.369 initialized on DCN 2.0
[ 9.139330] amdgpu 0000:03:00.0: [drm] DP-HDMI FRL PCON supported
[ 9.163458] snd_hda_intel 0000:03:00.1: bound 0000:03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
[ 9.379822] amdgpu 0000:03:00.0: kiq ring mec 2 pipe 1 q 0
[ 9.886538] amdgpu 0000:03:00.0: Fence fallback timer expired on ring sdma0
[ 10.391576] amdgpu 0000:03:00.0: Fence fallback timer expired on ring sdma0
[ 10.391644] amdgpu: Virtual CRAT table created for GPU
[ 10.392036] amdgpu: Topology: Add GPU node [0x1002:0x7340]
[ 10.392059] amdgpu 0000:03:00.0: SE 1, SH per SE 2, CU per SH 12, active_cu_number 22
[ 10.392065] amdgpu 0000:03:00.0: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[ 10.392068] amdgpu 0000:03:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[ 10.392071] amdgpu 0000:03:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[ 10.392073] amdgpu 0000:03:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[ 10.392075] amdgpu 0000:03:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[ 10.392077] amdgpu 0000:03:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[ 10.392080] amdgpu 0000:03:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[ 10.392082] amdgpu 0000:03:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[ 10.392084] amdgpu 0000:03:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[ 10.392086] amdgpu 0000:03:00.0: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
[ 10.392089] amdgpu 0000:03:00.0: ring sdma0 uses VM inv eng 12 on hub 0
[ 10.392091] amdgpu 0000:03:00.0: ring sdma1 uses VM inv eng 13 on hub 0
[ 10.392093] amdgpu 0000:03:00.0: ring vcn_dec uses VM inv eng 0 on hub 8
[ 10.392095] amdgpu 0000:03:00.0: ring vcn_enc0 uses VM inv eng 1 on hub 8
[ 10.392097] amdgpu 0000:03:00.0: ring vcn_enc1 uses VM inv eng 4 on hub 8
[ 10.392099] amdgpu 0000:03:00.0: ring jpeg_dec uses VM inv eng 5 on hub 8
[ 10.421793] amdgpu: HMM registered 8176MB device memory
[ 10.422494] amdgpu 0000:03:00.0: Using BACO for runtime pm
[ 10.423408] amdgpu 0000:03:00.0: [drm] Registered 5 planes with drm panic
[ 10.430550] [drm] Initialized amdgpu 3.64.0 for 0000:03:00.0 on minor 0
[ 10.432422] amdgpu 0000:03:00.0: [drm] Cannot find any crtc or sizes
[ 10.618381] fbcon: amdgpudrmfb (fb0) is primary device
[ 10.747247] amdgpu 0000:03:00.0: [drm] fb0: amdgpudrmfb frame buffer device
Result of "sudo journalctl -b -0 --no-pager | grep -i "amdgpu\|gpu hung\|fence" | tail -50":
# note: this appears to be the system after a boot, no info on the time of any crash.
jun 28 13:52:35 EmperorPenguin kernel: amdgpu 0000:03:00.0: [drm] Detected VRAM RAM=8176M, BAR=256M
jun 28 13:52:35 EmperorPenguin kernel: amdgpu 0000:03:00.0: [drm] RAM width 128bits GDDR6
jun 28 13:52:35 EmperorPenguin kernel: amdgpu 0000:03:00.0: 8176M of VRAM memory ready
jun 28 13:52:35 EmperorPenguin kernel: amdgpu 0000:03:00.0: 7971M of GTT memory ready.
jun 28 13:52:35 EmperorPenguin kernel: amdgpu 0000:03:00.0: [drm] GART: num cpu pages 131072, num gpu pages 131072
jun 28 13:52:35 EmperorPenguin kernel: amdgpu 0000:03:00.0: [drm] PCIE GART of 512M enabled (table at 0x0000008000900000).
jun 28 13:52:35 EmperorPenguin kernel: amdgpu 0000:03:00.0: [VCN instance 0] Found VCN firmware Version ENC: 1.24 DEC: 8 VEP: 0 Revision: 9
jun 28 13:52:35 EmperorPenguin kernel: amdgpu 0000:03:00.0: reserve 0x900000 from 0x81fd000000 for PSP TMR
jun 28 13:52:35 EmperorPenguin kernel: amdgpu 0000:03:00.0: RAS: optional ras ta ucode is not available
jun 28 13:52:35 EmperorPenguin kernel: amdgpu 0000:03:00.0: RAP: optional rap ta ucode is not available
jun 28 13:52:35 EmperorPenguin kernel: amdgpu 0000:03:00.0: SECUREDISPLAY: optional securedisplay ta ucode is not available
jun 28 13:52:35 EmperorPenguin kernel: amdgpu 0000:03:00.0: use vbios provided pptable
jun 28 13:52:35 EmperorPenguin kernel: amdgpu 0000:03:00.0: smc_dpm_info table revision(format.content): 4.5
jun 28 13:52:35 EmperorPenguin kernel: amdgpu 0000:03:00.0: SMU is initialized successfully!
jun 28 13:52:35 EmperorPenguin kernel: amdgpu 0000:03:00.0: [drm] Display Core v3.2.369 initialized on DCN 2.0
jun 28 13:52:35 EmperorPenguin kernel: amdgpu 0000:03:00.0: [drm] DP-HDMI FRL PCON supported
jun 28 13:52:35 EmperorPenguin kernel: snd_hda_intel 0000:03:00.1: bound 0000:03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
jun 28 13:52:35 EmperorPenguin kernel: amdgpu 0000:03:00.0: kiq ring mec 2 pipe 1 q 0
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: Fence fallback timer expired on ring sdma0
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: Fence fallback timer expired on ring sdma0
jun 28 13:52:36 EmperorPenguin kernel: amdgpu: Virtual CRAT table created for GPU
jun 28 13:52:36 EmperorPenguin kernel: amdgpu: Topology: Add GPU node [0x1002:0x7340]
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: SE 1, SH per SE 2, CU per SH 12, active_cu_number 22
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: ring sdma0 uses VM inv eng 12 on hub 0
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: ring sdma1 uses VM inv eng 13 on hub 0
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: ring vcn_dec uses VM inv eng 0 on hub 8
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: ring vcn_enc0 uses VM inv eng 1 on hub 8
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: ring vcn_enc1 uses VM inv eng 4 on hub 8
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: ring jpeg_dec uses VM inv eng 5 on hub 8
jun 28 13:52:36 EmperorPenguin kernel: amdgpu: HMM registered 8176MB device memory
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: Using BACO for runtime pm
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: [drm] Registered 5 planes with drm panic
jun 28 13:52:36 EmperorPenguin kernel: [drm] Initialized amdgpu 3.64.0 for 0000:03:00.0 on minor 0
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: [drm] Cannot find any crtc or sizes
jun 28 13:52:36 EmperorPenguin kernel: fbcon: amdgpudrmfb (fb0) is primary device
jun 28 13:52:36 EmperorPenguin kernel: amdgpu 0000:03:00.0: [drm] fb0: amdgpudrmfb frame buffer device
jun 28 13:52:41 EmperorPenguin coolercontrold[1172]: Initialized GPU Devices: {"amdgpu":{"driver name":["amdgpu"],"locations":["/sys/class/hwmon/hwmon2","/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/0000:02:00.0/0000:03:00.0","pci:v00001002d00007340sv00001002sd00000B0Cbc03sc00i00"],"channels":["GPU Load","fan1","freq1","freq2","power1_average"],"temps":["temp1","temp2","temp3"],"driver version":["7.0.0-27-generic"]}}
jun 28 13:52:42 EmperorPenguin lact[2308]: 2026-06-28T16:52:42.225776Z INFO lact_daemon::system::power_profiles_daemon: conflicting power-profiles-daemon action amdgpu_dpm is already disabled
jun 28 13:52:42 EmperorPenguin lact[2308]: 2026-06-28T16:52:42.258159Z INFO lact_daemon::server::handler: AMDGPU DRM initialized
jun 28 13:52:42 EmperorPenguin lact[2308]: 2026-06-28T16:52:42.259622Z INFO lact_daemon::server::handler: initialized amdgpu controller for GPU 1002:7340-1002:0B0C-0000:03:00.0 at '/sys/class/drm/card0/device'
Syslog during time of latest crash:
2026-06-28T13:20:44.661432-03:00 EmperorPenguin systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
2026-06-28T13:20:44.679414-03:00 EmperorPenguin dbus-daemon[857]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
2026-06-28T13:20:44.679551-03:00 EmperorPenguin systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
2026-06-28T13:20:53.587654-03:00 EmperorPenguin steam[12488]: Adding process 17814 for gameID 1091500
2026-06-28T13:20:53.991129-03:00 EmperorPenguin steam[12488]: Adding process 17817 for gameID 1091500
2026-06-28T13:20:54.043055-03:00 EmperorPenguin steam[12488]: Adding process 17827 for gameID 1091500
2026-06-28T13:20:54.704384-03:00 EmperorPenguin systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
2026-06-28T13:20:54.717819-03:00 EmperorPenguin steam[12488]: ATTENTION: default value of option vk_x11_override_min_image_count overridden by environment.
2026-06-28T13:20:55.963505-03:00 EmperorPenguin steam[12488]: message repeated 19 times: [ ATTENTION: default value of option vk_x11_override_min_image_count overridden by environment.]
2026-06-28T13:20:56.119515-03:00 EmperorPenguin steam[12488]: Fossilize INFO: Overriding serialization path: "/mnt/ext4/SteamLibrary/steamapps/shadercache/1091500/fozpipelinesv6/steamapprun_pipeline_cache".
2026-06-28T13:20:56.156417-03:00 EmperorPenguin steam[12488]: ATTENTION: default value of option vk_x11_override_min_image_count overridden by environment.
2026-06-28T13:20:56.209362-03:00 EmperorPenguin steam[12488]: message repeated 9 times: [ ATTENTION: default value of option vk_x11_override_min_image_count overridden by environment.]
2026-06-28T13:20:56.871869-03:00 EmperorPenguin kded6[1709]: Registering ":1.243/StatusNotifierItem" to system tray
2026-06-28T13:20:56.904072-03:00 EmperorPenguin kded6[1709]: Service ":1.243" unregistered
2026-06-28T13:20:56.908621-03:00 EmperorPenguin kded6[1709]: Registering ":1.244/StatusNotifierItem" to system tray
2026-06-28T13:20:56.911798-03:00 EmperorPenguin kded6[1709]: Service ":1.244" unregistered
2026-06-28T13:20:56.915486-03:00 EmperorPenguin kded6[1709]: Registering ":1.245/StatusNotifierItem" to system tray
2026-06-28T13:20:56.943895-03:00 EmperorPenguin kded6[1709]: Service ":1.245" unregistered
2026-06-28T13:20:56.949235-03:00 EmperorPenguin kded6[1709]: Registering ":1.246/StatusNotifierItem" to system tray
2026-06-28T13:20:56.954349-03:00 EmperorPenguin kded6[1709]: Service ":1.246" unregistered
2026-06-28T13:20:56.957135-03:00 EmperorPenguin kded6[1709]: Registering ":1.247/StatusNotifierItem" to system tray
2026-06-28T13:20:56.984366-03:00 EmperorPenguin kded6[1709]: Service ":1.247" unregistered
2026-06-28T13:20:56.986791-03:00 EmperorPenguin kded6[1709]: Registering ":1.248/StatusNotifierItem" to system tray
2026-06-28T13:20:56.992444-03:00 EmperorPenguin kded6[1709]: Service ":1.248" unregistered
2026-06-28T13:21:00.246709-03:00 EmperorPenguin steam[12488]: 06/28 13:21:00 minidumps folder is set to /tmp/dumps
2026-06-28T13:21:00.246803-03:00 EmperorPenguin steam[12488]: 06/28 13:21:00 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(20260624232445)/tid(17927)
2026-06-28T13:21:00.246837-03:00 EmperorPenguin steam[12488]: 06/28 13:21:00 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)/tid(17927)
2026-06-28T13:21:15.180823-03:00 EmperorPenguin steam[12488]: reaping pid: 17717 -- gameoverlayui
2026-06-28T13:26:06.448726-03:00 EmperorPenguin kernel: perf: interrupt took too long (3139 > 3133), lowering kernel.perf_event_max_sample_rate to 63000
2026-06-28T13:29:41.036661-03:00 EmperorPenguin dbus-daemon[1373]: [session uid=1000 pid=1373 pidfd=5] Activating via systemd: service name='org.kde.spectacle' unit='app-org.kde.spectacle.service' requested by ':1.18' (uid=1000 pid=1497 comm="/usr/bin/kwin_wayland --wayland-fd 7 --socket wayl" label="unconfined")
2026-06-28T13:29:41.041742-03:00 EmperorPenguin systemd[1341]: Starting app-org.kde.spectacle.service - Spectacle screenshot capture utility...
2026-06-28T13:29:41.550676-03:00 EmperorPenguin dbus-daemon[1373]: [session uid=1000 pid=1373 pidfd=5] Successfully activated service 'org.kde.spectacle'
2026-06-28T13:29:41.559839-03:00 EmperorPenguin systemd[1341]: Started app-org.kde.spectacle.service - Spectacle screenshot capture utility.
2026-06-28T13:29:41.588589-03:00 EmperorPenguin spectacle[18467]: spectacle: Attempting to use Tesseract library "libtesseract.so.5"
2026-06-28T13:29:41.588701-03:00 EmperorPenguin spectacle[18467]: spectacle: Detected Tesseract version "5.5.0"
2026-06-28T13:29:41.588731-03:00 EmperorPenguin spectacle[18467]: spectacle: Loaded Tesseract runtime library from "libtesseract.so.5"
2026-06-28T13:29:46.746222-03:00 EmperorPenguin systemd[1341]: app-org.kde.spectacle.service: Consumed 2.758s CPU time over 5.706s wall clock time, 145.2M memory peak.
2026-06-28T13:30:01.632201-03:00 EmperorPenguin CRON[18575]: (root) CMD (if [ -x /etc/init.d/anacron ] && ! [ -d /run/systemd/system ]; then exec /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
2026-06-28T13:30:15.744637-03:00 EmperorPenguin systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
2026-06-28T13:30:15.808113-03:00 EmperorPenguin systemd[1]: sysstat-collect.service: Deactivated successfully.
2026-06-28T13:30:15.808248-03:00 EmperorPenguin systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
2026-06-28T13:30:44.657170-03:00 EmperorPenguin NetworkManager[1025]: <info> [1782664244.6566] dhcp4 (enp5s0): state changed new lease, address=192.168.0.104
2026-06-28T13:30:44.658494-03:00 EmperorPenguin dbus-daemon[857]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=1025 comm="/usr/sbin/NetworkManager --no-daemon" label="unconfined")
2026-06-28T13:30:44.662606-03:00 EmperorPenguin systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
2026-06-28T13:30:44.681456-03:00 EmperorPenguin dbus-daemon[857]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
2026-06-28T13:30:44.681575-03:00 EmperorPenguin systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
2026-06-28T13:30:48.475230-03:00 EmperorPenguin plasmashell[1785]: qml: Weather code: 113 -> Icon: clear-day
2026-06-28T13:30:48.475936-03:00 EmperorPenguin plasmashell[1785]: qml: Weather updated: 29 Sunny clear-day
2026-06-28T13:30:54.709861-03:00 EmperorPenguin systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
If needed, the crash that happens is that the game will freeze, the GPU won't send signal anymore and when it gives any signal it's all artifacts, the system being unresponsive.
I just upgraded my Ubuntu 24.04-4 MATE install to the latest version. I noticed that in Firefox the save dialog box refuses to save a file on the proposed location when hitting [Enter] like it always did. I first blamed Firefox but it is system-wide. Any GTK app has this unwanted behavior. Other PCs, a fully up-to-date Linux Mint 22.3 workstation and a fresh test install of Ubuntu 24.04 MATE on an HP USDT (Ultra Small Desktop) save just fine on [Enter].
But not only that, I also noticed files being overwritten without any warning when clicking Save (or using [Alt]+s). Barring a complete system re-install, how can I fix this?
Here's the thing, I recently replace my phone and somehow termius can't run on background. So can I ssh to my router and send command via ssh to my laptop so my phone can disconnect and my computer still running the command and using my router as an anchor?
TL;DR: Yes.
After lot of wrapping my head around things and discovering my blunder with nomodeset, it seems that what's actually happening is everything works out of the box after all. The only missing piece is actually selecting the Quadro for use. This can be done by setting DRI_PRIME=1 in an application's environment. See this answer.
However, I'm still not quite satisfied, because I want the Quadro in use for most everything. I can export the variable in my shell rc file easily enough, but editing all of my application shortcuts is a pain. So I guess one last update: Does anyone know of a way to make the nouveau driver the default? Note that prime-select provided by the nvidia-prime package functions, but has no actual effect.
FINAL EDIT: I'm pretty satisfied that I've done all the research I can do short of learning how to write my own driver, but I seem to be barred from posting an answer, so this is it:
As above, "Yes."
A couple more ways to select the discrete (just learned that's the term for a stand-alone) GPU:
switcherooctlswitcheroo under the hood.That said, it kind of sucks. A couple spot tests:
My last resort solution to all of this is to make my system dual-boot with an older LTS that supports the official drivers (my "graphics" OS), so to anyone else in the same situation, there's your solution.
I am setting up an older machine with an Nvidia Quadro K1100M. After installing 26.04, one of the first things I confirmed was that I could connect multiple monitors, and sure enough, it worked out of the box with no issues.
Fast-forward to me doing a bunch of installation and configuration (i.e. running my clunky install script and taking a few manual steps), when I notice that I can no longer connect multiple monitors. Here's some relevant output:
> xrandr
Screen 0: minimum 16 x 16, current 1920 x 1080, maximum 32767 x 32767
None-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 508mm x 285mm
1920x1080 59.96*+
1440x1080 59.99
1400x1050 59.98
1280x1024 59.89
1280x960 59.94
1152x864 59.96
1024x768 59.92
800x600 59.86
640x480 59.38
320x240 59.29
1680x1050 59.95
1440x900 59.89
1280x800 59.81
1152x720 59.97
960x600 59.63
928x580 59.88
800x500 59.50
768x480 59.90
720x480 59.71
640x400 59.95
320x200 58.14
1600x900 59.95
1368x768 59.88
1280x720 59.86
1024x576 59.90
864x486 59.92
720x400 59.27
640x350 59.28
> sudo lshw -c video
*-display UNCLAIMED
description: VGA compatible controller
product: GK107GLM [Quadro K1100M]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller bus_master cap_list
configuration: latency=0
resources: memory:f4000000-f4ffffff memory:e0000000-efffffff memory:f0000000-f1ffffff ioport:e000(size=128) memory:f5000000-f507ffff
*-display
description: VGA compatible controller
product: 4th Gen Core Processor Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
logical name: /dev/fb0
version: 06
width: 64 bits
clock: 33MHz
capabilities: msi pm vga_controller bus_master cap_list fb
configuration: depth=32 latency=0 mode=1920x1080 resolution=1920,1080 visual=truecolor xres=1920 yres=1080
resources: memory:f5400000-f57fffff memory:d0000000-dfffffff ioport:f000(size=64) memory:c0000-dffff
The xrandr output is when external monitor(s) are connected. Any configuration of how many monitors/which ports they connect to makes no difference. Unfortunately, I did not record this output after a fresh installation, so I don't have that for comparison. UPDATE: I realized I can easily boot from USB to gather this output. I've added it at the end of the post.
So there's no driver installed for the GPU, and the OS doesn't see any displays that I connect to the machine. Can anyone shed any light on what might have changed? I really don't want to start over from a fresh installation, and even if I do, there's no guarantee I won't end right back here.
Some more details about drivers:
ubuntu-drivers list produces no output.
Nvidia recommends 418.113. but if I try to run the installer, it fails to build with a bunch of errors about missing header files, e.g. nv-misc.h. I had previously tried using the Additional Drivers dialog on a 24.10 installation to install I believe it was 390.x, but the result was the same.
The nvidia-legacy PPA doesn't appear to have 390 past mantic. When I was trying this on 24.10, I had pretty much concluded that I was going to need to downgrade to an earlier LTS to get it to work, until I tried 26.04 and it magically worked out of the box (until it magically didn't, hence this post).
Nouveau supports my GPU. My theory is that it claimed the GPU out of the box, which is why multiple monitors were briefly working, but then later dropped it for unknown reasons. Here is the output of lsmod | grep nouveau:
nouveau 3178496 0
gpu_sched 69632 1 nouveau
drm_gpuvm 57344 1 nouveau
mxm_wmi 12288 1 nouveau
drm_ttm_helper 20480 1 nouveau
drm_exec 12288 2 drm_gpuvm,nouveau
ttm 135168 2 drm_ttm_helper,nouveau
drm_display_helper 303104 1 nouveau
i2c_algo_bit 16384 1 nouveau
video 77824 3 dell_wmi,dell_laptop,nouveau
wmi 36864 8 video,dell_wmi,wmi_bmof,dell_smm_hwmon,dell_smbios,dell_wmi_descriptor,mxm_wmi,nouveau
UPDATE: As mentioned above, we can gather output from a working setup on the same machine by booting the installation materials from USB. Here's more lshw output demonstrating that the GPU is correctly using nouveau. I've elided the xrandr output, but it's what you'd expect.
> sudo lshw -c video
*-display
description: VGA compatible controller
product: GK107GLM [Quadro K1100M]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:01:00.0
logical name: /dev/fb1
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller bus_master cap_list rom fb
configuration: depth=32 driver=nouveau latency=0 mode=1920x1080 resolution=1920,1080 visual=truecolor xres=1920 yres=1080
resources: irq:47 memory:f4000000-f4ffffff memory:e0000000-efffffff memory:f0000000-f1ffffff ioport:e000(size=128) memory:f5000000-f507ffff
*-display
description: VGA compatible controller
product: 4th Gen Core Processor Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
logical name: /dev/fb0
version: 06
width: 64 bits
clock: 33MHz
capabilities: msi pm vga_controller bus_master cap_list rom fb
configuration: depth=32 driver=i915 latency=0 mode=1920x1080 resolution=1920,1080 visual=truecolor xres=1920 yres=1080
resources: irq:48 memory:f5400000-f57fffff memory:d0000000-dfffffff ioport:f000(size=64) memory:c0000-dffff
UPDATE 2: Okay, so started over and ran my install script only. After a restart, the problem was still there.
Then I ran it section by section with a restart in-between, and I found the culprit:
# make sure grub shows the full startup sequence
sudo sed -i 's/quiet splash/nomodeset/' /etc/default/grub
sudo update-grub
So apparently turning off the startup splash screen breaks something in the chain of logic that allows hardware display drivers to load correctly. This is wildly unexpected but nonetheless true. I'll probably ask separately why that might be.
I should probably note that I hadn't inspected glxinfo (available from mesa-utils) output before asking the question. There's actually a key nugget to be found there. Fresh install:
> glxinfo | grep "OpenGL renderer"
OpenGL renderer string: Mesa Intel(R) HD Graphics 4600 (HSW GT2)
Broken install (after turning off startup splash):
> glxinfo | grep "OpenGL renderer"
OpenGL renderer string: llvmpipe (LLVM 21.1.8, 256 bits)
So in the broken state we're actually using the software renderer and not the onboard graphics as I had previously assumed.
However, we also find that it still isn't using the Quadro in the "working" (multiple monitors-supported) state. I know prime-select is the tool to use to switch renderers when one has the Nvidia drivers installed, but it's as yet unclear if I can find and use a standalone version of it, or if I need to find another method.
UPDATE 3: nomodeset is doing what it's supposed to do, so that's entirely user error. Getting the Quadro selected is still pending.
I am having a HP laptop with AMD ryzen 3 3250u processor and I installed ubuntu 26 LTS and I tried to add a hibernation device in the laptop using a swap file but what I am experiencing is that when I run the command sudo systemctl hibernate my screen goes blank for sometime and return back to the lockscreen, sometime it work for the first time and subsequent hibernate fails, I am pasting my configuration files
/etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p8 during curtin installation
/dev/disk/by-uuid/4c859583-daba-499b-9918-8bc642b14b80 / ext4 defaults 0 1
# /boot/efi was on /dev/nvme0n1p1 during curtin installation
/dev/disk/by-uuid/D6BC-8F6E /boot/efi vfat defaults 0 1
/swapfile none swap sw 0 0
/etc/default/grub
# If you change this file or any /etc/default/grub.d/*.cfg file,
# run 'update-grub' afterwards to update /boot/grub/grub.cfg.
# For full documentation of the options in these files, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`( . /etc/os-release && echo ${NAME} )`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash resume=UUID=4c859583-daba-499b-9918-8bc642b14b80 resume_offset=169984"
GRUB_CMDLINE_LINUX=""
# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
#GRUB_DISABLE_OS_PROBER=false
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE/GOP/UGA
# you can see them in real GRUB with the command `videoinfo'
#GRUB_GFXMODE=640x480
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
findmnt -no UUID -T /swapfile
4c859583-daba-499b-9918-8bc642b14b80
sudo filefrag -v /swapfile | awk '$1=="0:" {print substr($4,1,length($4)-2)}'
169984
here is the result for the kernel command
journalctl --since today -p emerg..err
Jun 22 17:44:22 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP>
Jun 22 17:44:22 Zenbook kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20251212>
Jun 22 17:44:22 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:44:22 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:44:22 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:44:22 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:44:22 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:44:22 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:44:22 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:44:22 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:44:25 Zenbook systemd[1]: Failed to activate swap swapfile.swap - /swapfile.
Jun 22 17:44:26 Zenbook kernel: ACPI Error: No handler for Region [RCM0] (000000002bbd688e) [S>
Jun 22 17:44:26 Zenbook kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler (20251212/>
Jun 22 17:44:26 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.ESDT due to previous err>
Jun 22 17:44:26 Zenbook kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to pre>
Jun 22 17:44:28 Zenbook systemd[1]: Failed to activate swap swapfile.swap - /swapfile.
Jun 22 17:44:29 Zenbook systemd[1]: Failed to activate swap swapfile.swap - /swapfile.
Jun 22 17:44:35 Zenbook kernel:
Jun 22 17:44:35 Zenbook kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (>
Jun 22 17:44:35 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.WQBC due to previous err>
Jun 22 17:44:35 Zenbook kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (>
Jun 22 17:44:35 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.WQBE due to previous err>
Jun 22 17:44:41 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:41 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:42 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:42 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:42 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:42 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:43 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:44 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:45 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:46 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:46 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:46 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:47 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:47 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:47 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:47 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:49 Zenbook gdm-password][2992]: gkr-pam: unable to locate daemon control file
Jun 22 17:44:53 Zenbook systemd[3231]: Failed to start app-gnome-snap\x2duserd\x2dautostart-37>
Jun 22 17:44:56 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:56 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:57 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:58 Zenbook systemd[3231]: Failed to start snap.prompting-client.daemon.service - >
Jun 22 17:45:00 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:45:00 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:45:10 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:45:11 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:45:27 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:45:27 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:48:00 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:48:01 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:48:49 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:48:49 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:49:21 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:49:21 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:49:24 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:49:25 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:49:40 Zenbook gdm3[1640]: Gdm: Failed to list cached users: GDBus.Error:org.freedesk>
-- Boot 6222b8fdb133452c9a58e6ee5f5c0f39 --
Jun 22 17:50:01 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP>
Jun 22 17:50:01 Zenbook kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20251212>
Jun 22 17:50:01 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:50:01 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:50:01 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:50:01 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:50:01 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:50:01 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:50:01 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:50:01 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:50:01 Zenbook kernel: Failed to create device parport0
Jun 22 17:50:05 Zenbook kernel: ACPI Error: No handler for Region [RCM0] (00000000d3275a16) [S>
Jun 22 17:50:05 Zenbook kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler (20251212/>
Jun 22 17:50:05 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.ESDT due to previous err>
Jun 22 17:50:05 Zenbook kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to pre>
Jun 22 17:50:14 Zenbook kernel:
Jun 22 17:50:14 Zenbook kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (>
Jun 22 17:50:14 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.WQBC due to previous err>
Jun 22 17:50:14 Zenbook kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (>
Jun 22 17:50:14 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.WQBE due to previous err>
Jun 22 17:50:20 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:20 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:21 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:21 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:21 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:22 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:22 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:24 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:24 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:25 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:25 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:25 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:25 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:45 Zenbook gdm-password][3131]: gkr-pam: unable to locate daemon control file
Jun 22 17:50:51 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:51 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:52 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:52 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:54 Zenbook systemd[3204]: Failed to start snap.prompting-client.daemon.service - >
Jun 22 17:50:56 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:56 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:51:15 Zenbook systemd-sleep[5143]: Failed to put system to sleep. System resumed aga>
Jun 22 17:51:15 Zenbook kernel: PM: hibernation: Image allocation is 79836 pages short
Jun 22 17:51:15 Zenbook systemd[1]: Failed to start systemd-hibernate.service - System Hiberna>
Jun 22 17:51:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:51:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:51:34 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:51:35 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:51:51 Zenbook chronyd[1427]: Could not connect to [2620:2d:4002:1::3123]:4460 (4.ntp>
Jun 22 17:51:52 Zenbook chronyd[1427]: Could not connect to [2620:2d:4000:1::2123]:4460 (1.ntp>
Jun 22 12:28:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 12:28:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 12:28:31 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 12:28:32 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 12:43:13 Zenbook systemd-sleep[9679]: Failed to put system to sleep. System resumed aga>
Jun 22 12:43:13 Zenbook kernel: PM: hibernation: Image allocation is 116000 pages short
Jun 22 12:43:13 Zenbook systemd[1]: Failed to start systemd-hibernate.service - System Hiberna>
-- Boot f38d6bb7801c425387f1a8e9dbed4398 --
Jun 22 12:55:39 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP>
Jun 22 12:55:39 Zenbook kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20251212>
Jun 22 12:55:39 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 12:55:39 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 12:55:39 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 12:55:39 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 12:55:39 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 12:55:39 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 12:55:39 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 12:55:39 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 12:55:43 Zenbook kernel: ACPI Error: No handler for Region [RCM0] (000000003573ea84) [S>
Jun 22 12:55:43 Zenbook kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler (20251212/>
Jun 22 12:55:43 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.ESDT due to previous err>
Jun 22 12:55:43 Zenbook kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to pre>
Jun 22 12:55:51 Zenbook kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (>
Jun 22 12:55:51 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.WQBC due to previous err>
Jun 22 12:55:51 Zenbook kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (>
Jun 22 12:55:51 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.WQBE due to previous err>
Jun 22 12:56:00 Zenbook chronyd[1458]: Could not connect to [2620:2d:4002:1::3123]:4460 (4.ntp>
Jun 22 12:57:43 Zenbook gdm-password][3020]: gkr-pam: unable to locate daemon control file
Jun 22 12:57:51 Zenbook systemd[3095]: Failed to start snap.prompting-client.daemon.service - >
Jun 22 12:58:16 Zenbook kernel: PM: hibernation: Image allocation is 83357 pages short
Jun 22 12:58:16 Zenbook systemd-sleep[4989]: Failed to put system to sleep. System resumed aga>
Jun 22 12:58:17 Zenbook systemd[1]: Failed to start systemd-hibernate.service - System Hiberna>
free
total used free shared buff/cache available
Mem: 5479732 3315900 944936 138456 1614868 2163832
Swap: 16777212 42820 16734392
sudo swapon --show
NAME TYPE SIZE USED PRIO
/swapfile file 16G 925.1M -1
ls -lha /dev/disk/by-uuid
total 0
drwxr-xr-x 2 root root 160 Jun 28 22:19 .
drwxr-xr-x 12 root root 240 Jun 28 22:19 ..
lrwxrwxrwx 1 root root 10 Jun 28 22:19 15cf6fe2-efa4-47b6-9adc-bb279ca2ef48 -> ../../sda4
lrwxrwxrwx 1 root root 10 Jun 28 22:19 28D6-4C0F -> ../../sda3
lrwxrwxrwx 1 root root 15 Jun 28 22:19 4E4A61734A61592B -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 10 Jun 28 22:19 8E5A33945A337853 -> ../../sda2
lrwxrwxrwx 1 root root 15 Jun 28 22:19 C260-A33D -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 10 Jun 28 22:19 b8cfc018-6aa3-407c-bae8-4c7f643c146d -> ../../sda5
I have a Lenovo IdeaPad Slim 3 16ABR8 running Ubuntu 25.10 (latest kernel, AMD Ryzen). My main issue is that after waking up from sleep (suspend / s2idle) the built-in keyboard stops working completely. What I have tried: GRUB parameters: i8042.nopnp i8042.reset atkbd.reset rtw89_pci.disable_aspm=1 These work after a cold boot: the keyboard works, Fn keys, Caps Lock LED, and NumPad all function correctly. systemd scripts to reload atkbd or ideapad_laptop modules — did not manage to get a stable solution after suspend. My laptop uses s2idle sleep mode (S3 is not available). Symptoms after waking up from sleep: All keys on the built-in keyboard are unresponsive. Fn keys (volume, brightness) do not work. Caps Lock LED does not light up; NumPad does not respond. External keyboard works fine. Questions: Is there a working way to fully restore the built-in keyboard after sleep on Lenovo IdeaPad Slim 3 16ABR8 in Ubuntu 25.10? Is it possible to somehow bypass s2idle so that module reloads happen correctly? What safe systemd sleep hooks or other methods have people used successfully on this model? Any tested solutions or guidance would be greatly appreciated.
I managed to mount Iphone device to Ubuntu using ifuse as explained here
Now I want to do image recovery using photorec , when I run: photorec ~/iphone I get the following error:
Unable to open file or device iphone2: Inappropriate ioctl for device
Can you please tell me how I can recover deleted files from iphone connected to Ubuntu using photorec correctly? thanks
I'm working remotely via SSH connection and need to use some GUI applications on the remote machine. I do not have an X-Server for X forwarding on my local machine, but a RDP client.
Can I somehow enable RDP via command line?
Usually one would do this in the Settings app in the "Sharing" tab.
I run Ubuntu 22.04 LTS with Remote Desktop that is built in and it is great! (see attached image) However, when my internet connection breaks the service seems to hang up and I need to reboot the computer in order to be able to connect again. The normal sshd always works even after a connection issue so I wonder how do I: Reset this service from command line?
It seems to me that just resetting it will work but I don't know what service it is... Thanks for any suggestion :-)
I use cutycapt to make screenshots of web pages. When I switched from Kubuntu 16.04 to Kubuntu 20.04 I noticed that font rendering quality degraded significantly. I made several screenshots of the same page and enlarged the same fragment on both screenshots for comparison. Command which was used:
cutycapt --out=screenshot.png --url=http://www.debianadmin.com/how-to-disable-ipv6-in-debian.html
Here's the one made in Kubuntu 16.04 (cutycapt version 0.0~svn6-3.1, depends on libqtwebkit4 version 2.3.2-0ubuntu11):
My system is set to full hinting. Letter stems on this screenshot are sharp and their hinting is obviously set to "full".
Now the screenshot made in Kubuntu 20.04 (cutycapt version 0.0~svn10-0.1build1, depends on libqt5webkit5 version 5.212.0~alpha4-1ubuntu2):
All letters are surrounded by gray fringe. Take a look at the word "comment" — all stems in letter "m" have different thickness. It looks like "slight" hinting to me or even no hinting at all.
I'm quite confident that both systems are properly configured to use full hinting (in System Settings > Fonts and in /etc/fonts/conf.d/) and all other fonts obey these settings.
I tried adding .config/fontconfig/fonts.conf with contents:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<match target="font">
<edit name="antialias" mode="assign"><bool>true</bool></edit>
<edit name="hinting" mode="assign"><bool>true</bool></edit>
<edit name="hintstyle" mode="assign"><const>hintfull</const></edit>
<edit name="rgba" mode="assign"><const>rgb</const></edit>
<edit name="autohint" mode="assign"><bool>false</bool></edit>
<edit name="lcdfilter" mode="assign"><const>lcddefault</const></edit>
</match>
</fontconfig>
But these settings were ignored.
As far as I know cutycapt uses QtWebKit library. I don't know whether these rendering settings are controlled by Qt or WebKit engine directly. I also tried PhantomJS and wkhtmltoimage to capture screenshots in 20.04 but they produce the same blurred text. Any advices regarding tuning hinting or alternative software are welcome.
P.S. If someone knows how I can also enable subpixel antialiasing on these screenshots it would be nice.
Whenever I boot up, my monitor's settings are always zoomed in about at 10, out of a scale of 0-100.
It also happens if I turn my monitor off and on again.
If I change my Display settings to rotate my screen orientation from Landscape to Portrait and back, but not Landscape to Flipped Landscape and back.
And changing the Scale in the Display Settings menu doesn't mess up the Zoom again, either.
I have a Dell SP2208WFP, and my Monitors.xml looks like:
<monitors version="2">
<configuration>
<logicalmonitor>
<x>0</x>
<y>0</y>
<scale>0</scale>
<primary>yes</primary>
<monitor>
<monitorspec>
<connector>HDMI-A-1</connector>
<vendor>DEL</vendor>
<product>SP2208WFP</product>
<serial>RR268831CT0U</serial>
</monitorspec>
<mode>
<width>1680</width>
<height>1050</height>
<rate>59.954250335693359</rate>
</mode>
</monitor>
</logicalmonitor>
</configuration>
</monitors>
...
And now, Scale is reset to 1... Because I exited a fullscreen app or something??
...
It even happens in Recovery Mode, when I don't have a DISPLAY variable set.
...
But, it doesn't seem to happen if I connect through the screwy connection cables instead of HDMI...
Still happens in 26.04 Ubuntu Desktop, Doesn't happen on my Windows 10 machine, and zoom level changes accordingly when I between them using a UGreen HDMI splitter (ACBUGN50966).
Recently Okular has become a great tool to annotate pdfs.
I have added some annotations (stamps) using okular to a pdf. I would like these annotations to become flat. By flat I mean that they are no longer selectable and deletable so that they are not distinguishable from the original pdf.
A Bug report has been filed on the KDE bugtracking system.
My laptop's hard disk is 1 TB and total memory is 8 GB, it has two partition. One is for C drive where windows installed and other is for Ubuntu installation ; size 512 GB
While installing Ubuntu, what type of partition should I create?
Should I create swap or not? If yes.. How much size should I allocate? ( total memory 8 GB)
Creating a root partition, How much size should I allocate? Help me to manage! Thanks in advance
As a long time user of Ubuntu (10y+) I have noticed the relationship between Ubuntu and public Wifi hotspots (without wifi security) that require login through a web page have not always been easy...
At times, I was able to be automatically redirected to a web page for logging in, but I have been experiencing the same problem for a while: after connecting to the open wifi network, the browser does not redirect to the login page! I have just updated to 16.04 and I was disappointed to see it did not fix the problem.
I tried deleting the connection from Network Manager but this doesn't change anything. The behaviour is the same with any browser (Chromium, Firefox, Opera, etc). I have dual-boot on this machine and no problem connecting to those network in Windows...I don't really know what else to try...
Is anyone else experiencing this issue? Any help to troubleshoot (or solve) the problem is highly appreciated. Please let me know if you need command outputs for diagnostics.
Update: Today, I did manage to connect to one of these wifi networks, but received a warning first :
However, I tried to connect to a Starbucks network afterwards and still have the same problem. Thaller below pointed to a possible problem in the NetworkManager.conf file: could anyone maybe post a normal file so I can see what's wrong with mine?
Gnome-Terminal is terrible.
It's buggy and whenever Gnome-Shell restarts or resumes from suspend, all Gnome-Terminal windows become unusable and can't be closed. There's an old ticket opened for it, but it'll likely never be fixed.
In the meantime, I've been trying to use other terminal packages. Unfortunately, Gnome-Shell still thinks Gnome-Terminal is what it should use whenever I select "open in terminal" in various menus. If I uninstall Gnome-Terminal, these menus disappear. What's the easiest way to keep the menus, but make my preferred terminal window open instead?
Explanation: I work for IBM and trying to prototype netboot (pxe) for ubuntu. The goal is to have a maas deployment server deploy out to 4 VMs managed under ubuntu 14.0.4 to test out juju bundle #39 (openstack base). Since my team does not have 4 physical servers we are attempting this using VMs. Note this is ppc64el environment.
Problem With a installed mini.iso for netboot (pxe) in a VM we encounter "Guest has not initialized the display yet". VM does not boot, goes to paused and maas cannot be used for this VM.
Questions
The netboot mini.iso from wiki.ubuntu.com/ppc64el.
Can it be used to establish a VM to boot from pxe?
Are these only for installation on bare metal?
I found this at https://lists.gnu.org/archive/html/qemu-discuss/2015-03/msg00027.html that says "kernel that won't work on this board model" or "kernel has no graphics support". This is leading me to believe that using the netboot/pxe mini.iso cannot be done in VM and needs to be bare metal.
Is putting the netboot iso into VM possible?
Is it not possible because the VM emulation graphics card is not
supported for the mini.iso?
QEMU window opens up, but I am getting this error "Guest has not initialized the display yet" I had enabled -sdl option while configuring qemu, but I am still getting that error.
This isn't an error. It is just QEMU telling you that the guest OS has not yet done what it needs to do to turn on the emulated graphics card and display output.
In this case the likely reason for this is that you've tried to run a kernel that won't work on this board model, and so it has crashed before it got anywhere. You can also see this message if the kernel has no graphics support built in and is just doing output to serial console.
vm6.xml or parts of it that are relevant
/usr/bin/qemu-system-ppc64le
<controller type='usb' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
</controller>
<controller type='pci' index='0' model='pci-root'/>
<controller type='virtio-serial' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</controller>
<interface type='bridge'>
<mac address='00:1a:64:30:12:11'/>
<source bridge='br3'/>
<model type='rtl8139'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</interface>
<serial type='pty'>
<target port='0'/>
<address type='spapr-vio' reg='0x30000000'/>
</serial>
<console type='pty'>
<target type='serial' port='0'/>
<address type='spapr-vio' reg='0x30000000'/>
</console>
<input type='tablet' bus='usb'/>
<input type='keyboard' bus='usb'/>
<input type='mouse' bus='usb'/>
<graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
Envirionment Info
Server: ubuntu 14.04 trusty - ppc64el
/wiki.ubuntu.com/ppc64el netboot mini.iso being used
juju: //jujucharms.com/u/james-page/openstack-base/bundle/39/
Openstack with ceph storage, requires 4 machines
using maas to boot VMs: askubuntu.com/questions/292061/how-to-configure-maas-to-be-able-to-boot-virtual-machines
Outcome Added Sep 22, 2015
==========================
Explanation of what was done to make things work and example of xml (XML Code secion). The xml helps to start making ppc64le work to get to running state (not paused). Once we got the VM to running state we still had to modify in virt-manager to setup scsi disk for deployed vm. The XML code below is the version that was finally modified in virt-manager with 8G scsi disk.
Notes
Need to run ppc64_cpu --smt=off
xml: Needed to specify arch ppc64
xml: Used qemu-system-ppc64 qemu
Added on 10/07/2014. I forgot to mention that the xml has to be changed to use VNC console. See the supplied XML. Need to use VNC. Have to have the console tags, which I believe should be there. Also if you setup XML you may run into issue with bus slot definition where it says already used slots. If this is the case you may have to adjust bus/slot numbers as shown in example below.
<console type='pty'>
<target type='serial' port='0'/>
<address type='spapr-vio' reg='0x30000000'/>
</console>
<graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0' keymap='en-us'>
<listen type='address' address='0.0.0.0'/>
</graphics>
Note that this gets vm into running state.
Now the original xml contained mini.iso . However once running in maas the vm commissioned to ready state. Then when deployed (start button) hit issue where VM started up but failed deployment. From virt-manager removed the mini-iso and created a scsi disk of 8G. The scsi disk is needed my maas to put the deployed OS (in our case ubuntu 14.04 trusty).
Note on virt-manager: Using virt-manager makes things real easy. Our setup used private network and we normally use vnc to connect to servers. The server that has all the VMs on it (the VM server) we connect to via vnc. Now from there we tried to connect via vnc to the maas deployment server (on a ubuntu 15.04 level). We could not make vnc work on the 15.04 server. So we used ssh -X xll forwarding. Not the solution for product level but if you are testing this environment out this works in a pinch.
Note that to access the ubuntu properly you need to setup the ssh keys as specified by ubuntu documentation.
See: /maas.ubuntu.com/docs/nodes.html
Note we used root for our testing so if you do this for testing then maas userid does not have to be setup and just ssh-keygen (this is done on maas deployment server).
The target server that has the VMs (VM server in the doc) needs the public key so ssh-copy-id -i ~/.ssh/id_rsa ubuntu@x.x.x.x has to be done and you have to use ubuntu userid. The ubuntu userid is the default userid of deployed VMs.
Once the above is done you can access the deployed VM from the VM server using something like this ssh ubuntu@x.x.x.x (x.x.x.x is the ip address of created ubuntu VM)
Once this was fixed mass deployed to the server ubuntu 14.04.
If you run virt-manager you can see the sequence of processing during deploy.
Now in the test case we ran observed in virt-manager that the boot sequence was still off network so changed that to disk. Stopped VM, restarted VM and came up with ubuntu 14.04.
Connect to the newly created VM using ssh ubuntu@x.x.x.x (x.x.x.x is the ipaddress of created ubuntu VM). Note you can obtain the newly created ipaddress from the edit node page, go to bottom and select discovered information. ipaddress is listed in that area a ways down, probably better to copy to a notepad, editor and then search for address start. We used private network so just searched for 192.
Use uname -a and lscpu to check if OS is correct. Should show architecture as ppc64le:
root@ubuntur2n2:~# uname -a
Linux ubuntur2n2 3.19.0-25-generic #26-Ubuntu SMP Fri Jul 24 21:18:29 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
root@ubuntur2n2:~# lscpu
Architecture: ppc64le
Byte Order: Little Endian
CPU(s): 192
On-line CPU(s) list: 0,8,16,24,32,40,48,56,64,72,80,88,96,104,112,120,128,136,144,152,160,168,176,184
Off-line CPU(s) list: 1-7,9-15,17-23,25-31,33-39,41-47,49-55,57-63,65-71,73-79,81-87,89-95,97-103,105-111,113-119,121
-127,129-135,137-143,145-151,153-159,161-167,169-175,177-183,185-191
Thread(s) per core: 1
Core(s) per socket: 6
Socket(s): 4
NUMA node(s): 4
XML Code
<domain type='kvm'>
<name>vm5</name>
<uuid>1e964a47-4a69-4b59-a5b4-637a1234f47d</uuid>
<description>vm5 for PoC</description>
<memory unit='KiB'>4194304</memory>
<currentMemory unit='KiB'>4194304</currentMemory>
<vcpu placement='static'>2</vcpu>
<os>
<type arch='ppc64' machine='pseries-2.2'>hvm</type>
<bootmenu enable='yes'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/bin/qemu-system-ppc64</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2'/>
<source file='/var/lib/libvirt/images/vm5-1.qcow2'/>
<target dev='sda' bus='scsi'/>
<boot order='1'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<controller type='usb' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
</controller>
<controller type='pci' index='0' model='pci-root'/>
<controller type='ide' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
</controller>
<controller type='scsi' index='0'>
<address type='spapr-vio' reg='0x2000'/>
</controller>
<interface type='bridge'>
<mac address='00:1a:64:14:53:14'/>
<source bridge='br3'/>
<model type='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</interface>
<serial type='pty'>
<target port='0'/>
<address type='spapr-vio' reg='0x30000000'/>
</serial>
<console type='pty'>
<target type='serial' port='0'/>
<address type='spapr-vio' reg='0x30000000'/>
</console>
<input type='tablet' bus='usb'/>
<input type='keyboard' bus='usb'/>
<input type='mouse' bus='usb'/>
<graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0' keymap='en-us'>
<listen type='address' address='0.0.0.0'/>
</graphics>
<video>
<model type='vga' vram='16384' heads='1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</video>
<memballoon model='virtio'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
</memballoon>
</devices>
</domain>
Please pardon my inexperience with Linux and related packages. I am very new to such systems.
I have installed Ubuntu 14.04 in a Windows Hyper-V virtual machine (VM). For a VM on a Windows host, instead of connecting through the Hyper-V Manager, it is suggested to connect to a VM with a remote desktop connection (RDC). To connect to the Ubuntu VM with the Windows terminal server RDC, I installed the Xrdp package in the Ubuntu VM. To sidestep 3D complications with the Unity desktop interface, I installed the Xfce4 package in the VM. Things work generally well.
However, mouse scrolling is very slow. In other words, it takes several scrolls of the mouse wheel to scroll the display of various windows.
Upon further inspection, I found the mouse settings (Application Menu/Settings/Mouse and Touchpad) are not present (other settings such as the Keyboard are present). In particular, I tried the following command to evaluate Xfce4 mouse settings, however I received a message about Xlib that might be related to Xrdp:
$ xfce4-mouse-settings
Xlib: extension "XInputExtension" missing on display ":10.0".
(xfce4-mouse-settings:14760): xfce4-mouse-settings-CRITICAL **: XI is not present.
Here is my main question:
1) How can I improve/increase the mouse scroll speed in Ubuntu 14.04 with Xfce4 and Xrdp?
However, the situation also leads me to ask the following questions:
2) How can I install the Mouse and Touchpad settings in Ubuntu 14.04 with Xfce4 and Xrdp?
3) Is Xrdp a preferred RDC for Ubuntu 14.04 in a Windows Hyper-V VM?
4) Is Xfce4 a preferred desktop interface for Ubuntu 14.04 in a Windows Hyper-V VM?
Thanks for any ideas or suggestions you may have!
I have a desktop (Ubuntu 13.04 & Win 7 Home Premium) and a Laptop (Ubuntu 12.04), both having WiFi adapters. I also have a WiFi router connected to internet which both my computers can access.
I want to share files between my desktop and my laptop using WiFi (similar to Homegroup on Windows 7 but without using Ethernet cables). How do I set-up that?
I want to share files using both OSs, if anyone have have information about sharing files with any of the OS please answer!