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?
I know I'm off in to the weeds a bit, but I'm trying to save a few iterations of effort.
What I'm looking to get done is to have Ubuntu set up and install to a ZFS mirror. Single disk zfs stripe works fine. Whenever I try to do a multi-disk root (ZFS mirror, LVM mirror), the installer gets jenky, picks a random disk, and tries to install on to an LVM volume, which then doesn't boot correctly.
I've found a script that is intended to run under Ubuntu Desktop to Do the Right Thing(tm).
I'm PXE booting, so I'm trying to minimize the changes required, but what I'm hoping to do is update the user-data file to ignore sections I dont need - in this case, I want to install the ZFS utilities and run the pool creation script as "Early" scripts, and hopefully leave the pool how/where the installer it expects to find it (/target, IIRC), and then let it do the rest of the job.
Is this possible by just removing the disk portion of the configuration?
At the end of the day, I could probably get by with just the Early and Late scripts, but thats heading down a road of taking over the installation that I'd prefer to not do if I can.
I have a legacy BIOS (it knows not from EFI or secure boot or anything newer than 2010.
I have a broken installation on an MBR formatted external drive /dev/sdc with partitions /dev/sdc1 labeled '/boot' and /dev/sdc3 labeled '/'
I installed from a live dvd which decided to create its own boot directory in the '/' partition. I copied over its contents to /dev/sdc1 so the contents of /boot appear to be correct. Using fdisk, I marked /dev/sdc1 active. However, it doesn't show up in my BIOS!
I have another installation on an internal drive which boots just fine and os_prober found BOTH boot directories on my external drive and added them to grub on the internal drive.
But I cannot boot from them. When I try, it says it can't find /boot/vmlinux which is clearly present (I can mount these partitions and look around).
What is going wrong? And why does my BIOS ignore this external drive?
Thanks in advance.
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.
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.
No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 26.04 LTS Release: 26.04 Codename: resolute
I switched from Windows to Ubuntu. I downloaded Google Chrome. When I opened it, it is stuck. I couldn't able to write a URL. I could just close it. I also download Brave browser and Microsoft Edge. The same thing is happening with them too.
I have tried to reinstall, but nothing changed.
does anyone know why widevine is not working for drm on older devices?
I have a lenovo b50 that no longer streams from ITVX, although some films seem to work, others don't. My dell optiplex 3020. 4th gen i5 with intel hd4060 graphics is also no longer being accepted by ITVX.
The browser, Firefox or Chrome, is displaying 'Update your browser'.
MTIA
[Edit] I am using Ubuntu desktop as installed yesterday 28th June. The latest 26.04 LTS So the latest version of browsers etc. with ubuntu restricted extras installed and DRM accepted on Firefox. I will logon later and edit in the browser version for you.
I have the same problem on Fedora workstation and Fedora Silverblue.
It simply freezes during installation and does not progress forward. I've tried different USB sticks, disabling Secure Boot, and nomodeset.Reference image of where I'm stuck at and idk if this is helpful
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?
For a couple weeks now, I've been experiencing random reboots on my laptop.
They happen once or twice a day or not at all, either while in use (black screen), from suspend, or at boot (-> GRUB-menu). All I do at the laptop is write texts and ocassionally game.
From my logs, these "Previous system reset reason" messages jump out at me:
internal CPU shutdown event occured - Coincides with reboot times, except at boot.software wrote 0x6 to reset control register 0xCF9 - Too many, but a few coincide with at boot.ACPI power state transition occurred - Rare, possibly unrelated.See sample logs HERE and HERE. (Some things are redacted.) Also, see my CPU information HERE.
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 44 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Vendor ID: AuthenticAMD
Model name: AMD Ryzen 3 7320U with Radeon Graphics
CPU family: 23
Model: 160
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 1
Stepping: 0
Frequency boost: enabled
CPU(s) scaling MHz: 37%
CPU max MHz: 4151.7300
CPU min MHz: 425.1780
BogoMIPS: 4791.29
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pg
e mca cmov pat pse36 clflush mmx fxsr sse sse2 ht s
yscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constan
t_tsc rep_good nopl xtopology nonstop_tsc cpuid ext
d_apicid aperfmperf rapl pni pclmulqdq monitor ssse
3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xs
ave avx f16c rdrand lahf_lm cmp_legacy svm extapic
cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw
ibs skinit wdt tce topoext perfctr_core perfctr_nb
bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_psta
te ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 a
vx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt
clwb sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occ
up_llc cqm_mbm_total cqm_mbm_local clzero irperf xs
aveerptr rdpru wbnoinvd cppc arat npt lbrv svm_lock
nrip_save tsc_scale vmcb_clean flushbyasid decodea
ssists pausefilter pfthreshold avic v_vmsave_vmload
vgif v_spec_ctrl umip rdpid overflow_recov succor
smca sev sev_es
Virtualization features:
Virtualization: AMD-V
Caches (sum of all):
L1d: 128 KiB (4 instances)
L1i: 128 KiB (4 instances)
L2: 2 MiB (4 instances)
L3: 4 MiB (1 instance)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-7
Vulnerabilities:
Gather data sampling: Not affected
Ghostwrite: Not affected
Indirect target selection: Not affected
Itlb multihit: Not affected
L1tf: Not affected
Mds: Not affected
Meltdown: Not affected
Mmio stale data: Not affected
Old microcode: Not affected
Reg file data sampling: Not affected
Retbleed: Mitigation; untrained return thunk; SMT enabled wit
h STIBP protection
Spec rstack overflow: Mitigation; Safe RET
Spec store bypass: Mitigation; Speculative Store Bypass disabled via p
rctl
Spectre v1: Mitigation; usercopy/swapgs barriers and __user poi
nter sanitization
Spectre v2: Mitigation; Retpolines; IBPB conditional; STIBP alw
ays-on; RSB filling; PBRSB-eIBRS Not affected; BHI
Not affected
Srbds: Not affected
Tsa: Not affected
Tsx async abort: Not affected
Vmscape: Mitigation; IBPB before exit to userspace
Since upgrading to Ubuntu 26.04, I've had Linux kernel panics at boot once in a blue moon. Could this be relevant?
The only software I've installed within these last few weeks are VSCodium and .NET SDK.
For VSCodium:
snap install codium --classicsudo rm /usr/local/bin/dotnet (again, see later)For .NET SDK:
sudo snap install dotnet-sdk --classic (or dotnet-sdk-100 when installing VSCodium)sudo ln -s /snap/dotnet-sdk/current/dotnet /usr/local/bin/dotnet (for dot-net-100)~.profile:
export DOTNET_CLI_TELEMETRY_OPTOUT=trueexport DOTNET_ROOT=/snap/dotnet-sdk/currentWhat I've tried:
What I haven't tried:
As suggested by ChanganAuto, I updated the BIOS. As it turns out, I was on version 306 (2023/07/25). I followed the instructions from both "BIOS Update" and my laptop vendor's:
/boot/efi/EFI/boot/efi/EFIWill update if the issue still persists.
The problem is still present, perhaps worse. I had 3 reboots this morning. Oddly enough, I had none yesterday. See today's boot logs: 08:33, 08:56, 09:55, 10:28.
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
My AMD RX 580 2048sp (a card that was previously used in a windows machine without flaws) has a few quirks in my Kubuntu 26.04 LTS machine.
Firstly, it over heats easily, which was addressed but not fixed by having better coolers, slightly limiting power usage and having fan speed configured to spin fast at the slightest heat.
Secondly, the main problem: sometimes, under specific environments and conditions, the system crashes. Image will turn into one solid shade, audio will glitch and the system won't work until rebooting. I have no idea what causes this, as it isn't related to temperature or heavy proceeding loads, as it can run graphically demanding games for hours. My guess is that there is one specific visual FX that the GPU can't process and then crashes. My reasoning is founded in 2 examples; in an emulator I have, most shaders run fine, but some crash consistently; and in one game the system crashes in the same exact spot but never anywhere else.
I have tried installing the amdgpu drivers, but that has done nothing and updating the system over months hasn't done anything, and unsinstalling said amdgpu packages has also made no difference. One thing that is important to not is that the prior GPU in this same distro didn't crash.
Edit: I have tried replicating the crash by installing a game that consistently crashes at the same spot. It crashes, I marked the time it did, waited 10 minutes (to make sure the logs are readable as being form different times), and this is the syslog from when the game opened and when it crashed:
2026-06-02T17:21:27.431856-03:00 EmperorPenguin steam[10260]: [2026-06-02 17:21:27] Saving metrics to disk (/home/cdanlb/.steam/debian-installation/package/steam_client_metrics.bin)
2026-06-02T17:22:59.562805-03:00 EmperorPenguin steam[10260]: [2026-06-02 17:22:59] uninstalled manifest found in /home/cdanlb/.steam/debian-installation/package/steam_client_ubuntu12 (1).
2026-06-02T17:23:56.417529-03:00 EmperorPenguin steam[10260]: chdir "/home/cdanlb/.steam/debian-installation/steamapps/common/Ardenfall Demo"
2026-06-02T17:23:56.425315-03:00 EmperorPenguin steam[10260]: ERROR: ld.so: object '/home/cdanlb/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
2026-06-02T17:23:56.446436-03:00 EmperorPenguin steam[10260]: ERROR: ld.so: object '/home/cdanlb/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
2026-06-02T17:23:56.460727-03:00 EmperorPenguin steam[10260]: Game Recording - would start recording game 1837770, but recording for this game is disabled
2026-06-02T17:23:56.461357-03:00 EmperorPenguin steam[10260]: Adding process 12471 for gameID 1837770
2026-06-02T17:23:56.464043-03:00 EmperorPenguin steam[10260]: ERROR: ld.so: object '/home/cdanlb/.steam/debian-installation/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
2026-06-02T17:23:56.470215-03:00 EmperorPenguin steam[10260]: ERROR: ld.so: object '/home/cdanlb/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
2026-06-02T17:23:56.486306-03:00 EmperorPenguin steam[10260]: ERROR: ld.so: object '/home/cdanlb/.steam/debian-installation/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
2026-06-02T17:23:56.527906-03:00 EmperorPenguin steam[10260]: Adding process 12472 for gameID 1837770
2026-06-02T17:23:56.580033-03:00 EmperorPenguin steam[10260]: Adding process 12473 for gameID 1837770
2026-06-02T17:23:56.601262-03:00 EmperorPenguin steam[10260]: Adding process 12474 for gameID 1837770
2026-06-02T17:23:57.496060-03:00 EmperorPenguin steam[10260]: Adding process 12563 for gameID 1837770
2026-06-02T17:23:58.721421-03:00 EmperorPenguin steam[10260]: ProtonFixes[12563] INFO: Running protonfixes on "GE-Proton10-26", build at 2025-12-07 22:33:15+00:00.
2026-06-02T17:23:58.721502-03:00 EmperorPenguin steam[10260]: ProtonFixes[12563] INFO: Running checks
2026-06-02T17:23:58.721553-03:00 EmperorPenguin steam[10260]: ProtonFixes[12563] INFO: All checks successful
2026-06-02T17:23:58.723375-03:00 EmperorPenguin steam[10260]: ProtonFixes[12563] INFO: Using global defaults for "Ardenfall Demo" (1837770)
2026-06-02T17:23:58.723503-03:00 EmperorPenguin steam[10260]: ProtonFixes[12563] INFO: No global protonfix found for "Ardenfall Demo" (1837770)
2026-06-02T17:23:58.788766-03:00 EmperorPenguin steam[10260]: fsync: up and running.
2026-06-02T17:23:58.805139-03:00 EmperorPenguin steam[10260]: Adding process 12564 for gameID 1837770
2026-06-02T17:23:58.805706-03:00 EmperorPenguin steam[10260]: Adding process 12565 for gameID 1837770
2026-06-02T17:23:58.856666-03:00 EmperorPenguin steam[10260]: Adding process 12566 for gameID 1837770
2026-06-02T17:23:58.908007-03:00 EmperorPenguin steam[10260]: Adding process 12569 for gameID 1837770
2026-06-02T17:23:58.908665-03:00 EmperorPenguin steam[10260]: Adding process 12571 for gameID 1837770
2026-06-02T17:23:58.959760-03:00 EmperorPenguin steam[10260]: Adding process 12574 for gameID 1837770
2026-06-02T17:23:59.011128-03:00 EmperorPenguin steam[10260]: Adding process 12583 for gameID 1837770
2026-06-02T17:23:59.062379-03:00 EmperorPenguin steam[10260]: Adding process 12588 for gameID 1837770
2026-06-02T17:23:59.769769-03:00 EmperorPenguin steam[10260]: Adding process 12599 for gameID 1837770
2026-06-02T17:24:00.323858-03:00 EmperorPenguin steam[10260]: Adding process 12622 for gameID 1837770
2026-06-02T17:24:00.533211-03:00 EmperorPenguin steam[10260]: Adding process 12641 for gameID 1837770
2026-06-02T17:24:00.745408-03:00 EmperorPenguin steam[10260]: Adding process 12651 for gameID 1837770
2026-06-02T17:24:00.835748-03:00 EmperorPenguin steam[10260]: Fossilize INFO: Overriding serialization path: "/home/cdanlb/.steam/debian-installation/steamapps/shadercache/1837770/fozpipelinesv6/steamapprun_pipeline_cache".
2026-06-02T17:24:01.020145-03:00 EmperorPenguin kded6[1857]: Registering ":1.255/StatusNotifierItem" to system tray
2026-06-02T17:24:01.057251-03:00 EmperorPenguin kded6[1857]: Service ":1.255" unregistered
2026-06-02T17:24:01.075966-03:00 EmperorPenguin kded6[1857]: Registering ":1.256/StatusNotifierItem" to system tray
2026-06-02T17:24:01.077626-03:00 EmperorPenguin kded6[1857]: Service ":1.256" unregistered
2026-06-02T17:24:01.081164-03:00 EmperorPenguin kded6[1857]: Registering ":1.257/StatusNotifierItem" to system tray
2026-06-02T17:24:01.107321-03:00 EmperorPenguin kded6[1857]: Service ":1.257" unregistered
2026-06-02T17:24:02.336885-03:00 EmperorPenguin steam[10260]: 06/02 17:24:02 minidumps folder is set to /tmp/dumps
2026-06-02T17:24:02.336961-03:00 EmperorPenguin steam[10260]: 06/02 17:24:02 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(20260527212129)/tid(12793)
2026-06-02T17:24:02.337010-03:00 EmperorPenguin steam[10260]: 06/02 17:24:02 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)/tid(12793)
My Ubuntu 24.04.4 LTS is installed on a dual-boot Dell Inc. Precision 5490 machine.
Every time I close my laptop's lid and the machine goes in suspension mode, when I get the lid up again the machine shows the screen with date and time but does not awake when I press enter or any other keys. The only thing I have been able to do at that point is to brute force power down by holding the power button pressed. This happens randomly, not all the times. I would prefer not doing this as forcing the machine to turn off this way might compromise the disk. What can I do?
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 want to install Ubuntu 22.04 LTS with a custom partitioning setup, including an encrypted root partition and a swap partition of 8 GiB. The default Ubuntu installer doesn't allow me to set a custom swap size. What can I do to achieve this?
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
After updating to Ubuntu 6.5.0-28-generic, my wifi adapter stopped being recognized. It had worked perfectly for the past month since first installing. I am using a tp-link AX3000 Archer TX55E. I tried the following:
lsmod | grep iwlwifi to confirm that the iwlwifi module is loaded.ip link to confirm that the wireless interface is not listed.Note: USB tethering to a cellphone works fine.
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).
I recently tried to install lubuntu on an old computer. After a successful install I installed updates however and restarted. But when the computer booted again I saw only a black screen.
After following the instructions here:
My computer boots to a black screen, what options do I have to fix it?
I edited grub menu to start OS with nomodeset.
The problem is that now while booting the computer is stuck on
[OK] started load/save RF kill switch status
The computer is an inspiron mini 1018
Any ideas?
I have installed the certificate but when I try to access the url with https it gives me 403 forbidden error, but when I try to use it with http it is working fine.
I have installed the certificate in /etc/ssl/certs/ and I have following files:
In apache I have placed .conf file in
<VirtualHost *:80>
ServerName test.com
ServerAlias www.test.com
ErrorLog /var/log/apache2/aspnetcoredemo-error.log
CustomLog /var/log/apache2/aspnetcoredemo-access.log common
Redirect permanent "/" "https://test.com/"
<Directory /home/ubuntu/app>
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Require all granted
</Directory>
</VirtualHost>
<VirtualHost *:443>
ServerAdmin admin@test.com
ServerName test.com
ServerAlias www.test.com
DocumentRoot /home/ubuntu/app
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
SSLEngine on
SSLCertificateFile /etc/ssl/certs/test_com.crt
SSLCACertificateFile /etc/ssl/certs/test_com.ca-bundle
SSLCertificateKeyFile /etc/ssl/certs/test_com.key
<Directory /home/ubuntu/app>
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Require all granted
</Directory>
</VirtualHost>
The website is create using .net core.
I don't know what wrong I am doing here.
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>
Last week my function keys suddenly became media keys. F4 now toggles play status, F5 skips to the next song, and F12 ejects my media tray. When I try to remap them with Keyboard Shortcuts, I'm told that they map to XF86AudioPlay, XF86AudioNext, and XF86AudioEject.
How do I get the old function key mapping back? If possible I'd like to avoid creating a keyboard mapping file - I didn't have one before these problems, so I'd just like to return to that state.
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!
I know there something called fancontrol, that enables you to control the speed of your system's ventilation. I'd like to let my fans spin a bit faster as my laptop is heating up very easilly. All tutorials and stuff I've found are for old versions of Ubuntu and don't seem to be working anymore.
Can anyone explain to me or give me a good link on how I can get it working on Ubuntu? Something different with the same effect is also fine.