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?
I would like to install Ubuntu 26.04 LTS on a SSD using full disk encryption and using the following partitions. How would I accomplish this?
Partition 1
Size Format Mount Point Description
1.0 GB FAT /boot/efi EFI System
Partition 2
Size Format Mount Point Description
2.0 GB Ext4 /boot Extended Boot Partition
Partition 3
Size Format Mount Point Description
100 GB Ext4/ / Filesystem Root
LVM
Partition 4
Size Format Mount Point Description
126 GB Ext4/ /home Personal User Home Directories
LVM
Free Space
16 GB free space
this is the only info i can give
zig met uitpakken van ssh-import-id (5.11-0ubuntu3) over (5.11-0ubuntu2.24.04.1) ...
Voorheen niet geselecteerd pakket sysbench wordt geselecteerd.
Uitpakken van .../1354-sysbench_1.0.20+ds-7build1_amd64.deb wordt voorbereid...
Bezig met uitpakken van sysbench (1.0.20+ds-7build1) ...
Uitpakken van .../1355-xbrlapi_6.7-1ubuntu3_amd64.deb wordt voorbereid...
Bezig met uitpakken van xbrlapi (6.7-1ubuntu3) over (6.6-4ubuntu5) ...
Fouten gevonden tijdens verwerken van:
/tmp/apt-dpkg-install-NCP10T/1094-linux-modules-6.17.0-35-generic_6.17.0-35.35\_amd64.deb
/tmp/apt-dpkg-install-NCP10T/1106-linux-modules-6.17.0-29-generic_6.17.0-29.29\_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
luuk@luuk-750XGK:\~$ sudo apt upgrade -y
bash: /usr/bin/sudo: Bestand of map bestaat niet
luuk@luuk-750XGK:\~$ ls -l /usr/bin/sud
ls: cannot access '/usr/bin/sud': No such file or directory
luuk@luuk-750XGK:\~$ ls -l /usr/bin/sudo
ls: cannot access '/usr/bin/sudo': No such file or directory
so uhm yeah sudo is gone how do i fix this
EDIT: This is a straightup misintepretation of what nomodeset does (see comments). I'm leaving it up for reference, but mods, do what you will.
This is a follow-on to this question. I discovered in the course of that investigation that on a machine with an Nvidia Quadro K1100M GPU running a fresh install of 26.04 (no relevant testing yet to expand that case to other hardware/Ubuntu versions), running the following to turn off the grub splash screen and instead display full startup output, which should have nothing to do with the startup process beyond output display, actually breaks the chain of logic that allows hardware display drivers to load correctly:
# make sure grub shows the full startup sequence
sudo sed -i 's/quiet splash/nomodeset/' /etc/default/grub
sudo update-grub
Some relevant output from glxinfo (available from mesa-utils) demonstrates this. On a fresh ("working") installation:
> glxinfo | grep "OpenGL renderer"
OpenGL renderer string: Mesa Intel(R) HD Graphics 4600 (HSW GT2)
On a broken install (after turning off startup splash):
> glxinfo | grep "OpenGL renderer"
OpenGL renderer string: llvmpipe (LLVM 21.1.8, 256 bits)
I can switch between "broken" and "working" at will by updating /etc/default/grub as above and restarting.
So in the broken state we're using only the software renderer and not any hardware (onboard graphics being the renderer used on the fresh install). Per the referenced question, this is not our ideal state, but that isn't relevant to this question, which is specifically about why configuring grub's display properties would break hardware display driver functionality.
Also, the differing lines plus context from sudo lshw -c video output from the referenced question. Working:
*-display
...
product: GK107GLM [Quadro K1100M]
...
logical name: /dev/fb1
...
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
...
product: 4th Gen Core Processor Integrated Graphics Controller
...
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
Broken:
*-display UNCLAIMED
...
product: GK107GLM [Quadro K1100M]
...
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
...
product: 4th Gen Core Processor Integrated Graphics Controller
...
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
I am having a horrible time looking for a terminal program with both of the desiderata in the title.
It doesn't have to be packaged, I know my way with compiling programs from source. But it has to work inside Gnome - which already excludes some obvious candidates like xterm (when I run xterm my Super key stops showing the Gnome Shell overview).
Here's my journey so far:
I started with gnome-terminal inside tmux. But I don't know if tmux supports direct color, and even if it does when I ssh to a different host, that's already 3 levels of pty translation. What are the odds of that working correctly?
Then I got alacritty and I was really happy with it for a long time.
At least it does have its own keyboard select/copy/paste, fully
accessible from the keyboard, and ostensibly it also has direct color.
But ... today I tried to customize the tig program, which can use
the 256 color indexed palette but not direct color, and I realized alacritty
can't do both at the same time. If I have direct color enabled with
TERM=alacritty-direct and COLORTERM=truecolor, references to the
256 palette all fetch some shade of dark blue. If I had to guess,
alacritty uses the same escape sequence for both and misinterprets
the palette reference as a reference to some narrow band of direct colors.
Now I'm looking at gnome-terminal again, and I see it doesn't have this problem. But it has apparently no way to select text from the keyboard, and that's a must for me. What can I do?
It this possible? I’d prefer not to change for sshd_config file, but it doesn’t appear to pick-up the Daemon.conf file Port 333 configuration statement.
johnl@Johns-HP-15a~$ sudo systemctl status sshd
• ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/usr/lib/systemd/system/ssh.service; disabled; preset: enabled)
Active: active (running) since Mon 2026-06-22 12:40:23 EDT; 4min 43s ago
Invocation: d98ba72a0db14550b296f065c9b58967
TriggeredBy: • ssh.socket
Docs: man:sshd(8)
man:sshd_config(5)
Process: 9642 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
Main PID: 9645 (sshd)
Tasks: 1 (limit: 19067)
Memory: 2.8M (peak: 3.7M)
CPU: 64ms
CGroup: /system.slice/ssh.service
└─9645 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"
Jun 22 12:40:23 Johns-HP-15a systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
Jun 22 12:40:23 Johns-HP-15a sshd[9645]: Server listening on 0.0.0.0 port 22.
Jun 22 12:40:23 Johns-HP-15a sshd[9645]: Server listening on :: port 22.
Jun 22 12:40:23 Johns-HP-15a systemd[1]: Started ssh.service - OpenBSD Secure Shell server.
johnl@Johns-HP-15a~$ cat /etc/ssh/sshd_config.d/Daemon.conf
Protocol 2
Port 333
PermitEmptyPasswords no
X11Forwarding no
MaxAuthTries 3
PermitRootLogin prohibit-password
johnl@Johns-HP-15a~$
I have a MAAS 3.7.2 deployment with separate region and rack controllers. The rack controller (10.x.y.51) cannot connect to the Temporal service on the region controller (10.x.y.50), causing the maas-agent service to crash in a restart loop.
This prevents the httpproxy.sock from being created, which results in 502 errors when machines attempt PXE boot.
- MAAS Version: 3.7.2-17972-g.35e297c4d (both)
- Temporal Port: 5271 (gRPC frontend)
On Rack Controller
maas-agent Temporal connection failures:
maas-agent[46264]: ERR Temporal client error error="failed reaching server: context deadline exceeded while waiting for connections to become ready" maas.pebble[45464]: Service "agent" stopped unexpectedly with code 1 maas.pebble[45464]: Service "agent" on-failure action is "restart", waiting ~500ms before restart (backoff 1)
PXE boot 502 errors (machine 10.x.z.18 requesting bootx64.efi):
maas-rackd[45499]: provisioningserver.rackdservices.tftp: [info] bootx64.efi requested by 10.x.z.18
maas-http[45608]: [crit] connect() to unix:/run/snap.maas/httpproxy.sock failed (2: No such file or directory)
maas-http[45612]: 127.0.0.1 - - "GET /images/bootx64.efi HTTP/1.1" 502 166
On region controller:
Temporal is running and healthy
$ sudo netstat -tlnp | grep temporal
tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN temporal-serv
tcp6 0 0 :::5271 :::* LISTEN temporal-serv
tcp6 0 0 :::5272 :::* LISTEN temporal-serv
tcp6 0 0 :::5273 :::* LISTEN temporal-serv
I've tried to open firewall tcp/udp all ports between region controller and rack controller and the problem persisted.
1. The Temporal config shows rpcAddress: "localhost:7233" but the server listens on port 5271. Is the rack agent trying to connect to the wrong endpoint?
2. How does the rack controller learn the Temporal endpoint from the region? Is there a configuration file I should check/edit?
3. The Temporal frontend requires TLS client auth (requireClientAuth: true). Could certificate trust be preventing the connection?
4. What's the correct way to configure the rack's agent to connect to the region's Temporal service?
More info:
maas --version
MAAS 3.7.2 (3.7.2-17972-g.35e297c4d)
Postgres 16
Any suggestion / guidance is greatly appreciated!
I’m having an issue where Ubuntu refuses to boot up. I’m not exactly sure why this is happening, but I did some research and I do remember installing FUSE the previous night. I’m not exactly sure if that’s part of the issue, but even then trying to boot to recovery mode fails since I’m dual booting from a MacBook Pro 2015 and the window between the Apple logo closing and the Ubuntu splash window appearing is very short.
[ OK ] Started NetworkManager-dispatcher.. Manager Script Dispatcher Service.
[ OK ] Started bolt.service - Thunderbolt system service.
[ OK ] Started ModemManager.service - Modem Manager.
[ OK ] Started udisks2.service - Disk Manager.
[ OK ] Finished apport.service - automatic crash report generation.
[ OK ] Started snapd.service - Snap Daemon.
Starting systemd-timedated.service - Time & Date Service...
[ OK ] Started NetworkManager.service - Network Manager.
[ OK ] Reached target network.target - Network.
Starting NetworkManager-wait-onlin.ce - Network Manager Wait Online...
Starting cups.service - CUPS Scheduler...
Starting openvpn.service - OpenVPN service...
[ OK ] Started snap.cups.cups-browsed.ser.snap application cups.cups-browsed.
[ OK ] Started snap.cups.cupsd.service - .ce for snap application cups.cupsd.
Starting systemd-user-sessions.service - Permit User Sessions...
[ OK ] Started unattended-upgrades.service - Unattended Upgrades Shutdown.
[ OK ] Finished openvpn.service - OpenVPN service.
[ OK ] Started systemd-timedated.service - Time & Date Service.
[ OK ] Finished systemd-user-sessions.service - Permit User Sessions.
Starting gdm.service - GNOME Display Manager...
Starting plymouth-quit-wait.servic.d until boot process finishes up...
[ OK ] Finished snapd.seeded.service - Wait until snapd is fully seeded.
[ OK ] Started cups.service - CUPS Scheduler.
[ OK ] Started gdm.service - GNOME Display Manager.
It was working perfectly yesterday. I just can’t figure out what it is. I’m running Ubuntu 26.04, and I installed FUSE via the sudo apt-get install fuse libfuse2 command in the terminal.
My laptop has sound, when I play a song from Windows it does, but there is no sound from Ubuntu, and today I reinstalled Ubuntu from scratch and uninstalled Windows.
Specs:
I'm setting up a local AI stack with Ollama and Open WebUI using rootless podman-compose on Ubuntu 24.04. Both containers share a network, but when I started testing, I noticed the Ollama container was falling back to CPU inference — even though native Ollama on the host accesses the RTX 4060 Laptop GPU just fine.
My setup:
/etc/cdi/nvidia.yamlMy short debugging:
# Checked the CDI devices
nvidia-ctk cdi list
: '
INFO[0000] Found 3 CDI devices
nvidia.com/gpu=0
nvidia.com/gpu=GPU-3cb61464-c22f-067b-dcb8-ea32dda1197d
nvidia.com/gpu=all
'
ollama run ministral-3:8b "Hi"
# Hello! How can I assist you today? 😊
# Checks if CDI spec exists
head -20 /etc/cdi/nvidia.yaml
: '
cdiVersion: 0.7.0
kind: nvidia.com/gpu
devices:
- name: "0"
containerEdits:
deviceNodes:
- path: /dev/nvidia0
major: 195
fileMode: 438
permissions: rwm
- path: /dev/dri/card0
major: 226
fileMode: 432
permissions: rwm
gid: 44
- path: /dev/dri/renderD129
major: 226
minor: 129
fileMode: 432
'
podman run --rm --device nvidia.com/gpu=all --security-opt=label=disable ubuntu nvidia-smi -L
# Error: setting up CDI devices: unresolvable CDI devices nvidia.com/gpu=all
podman-compose -f compose.yaml --profile gpu-podman up -d ollama-gpu-podman
# Error: unable to start container "5f5fd11ffa125aef013245690ba61e088460aee7a22c562af7326e12a43d1fec": setting up CDI devices: unresolvable CDI devices nvidia.com/gpu=all
My compose.yaml for the Ollama service:
services:
ollama-gpu-podman:
image: ollama/ollama:latest
container_name: ollama-container
profiles:
- gpu-podman
restart: unless-stopped
networks:
- ollama-network
devices:
- nvidia.com/gpu=all
security_opt:
- label=disable
How do I fix it?
I have a Kubuntu server with two SFP+ ports and two 2.5Gbps Ethernet ports.
One of the 10Gbps SFP+ port is connected to a the 10Gbps SFP+ port on the switch using a CAT6 cable. Length 1.5m
I had no problems with it until it was getting hotter.
The connection stuttered and when I pinged from the server to the router, the ping stuttered also.
I noticed the SFP+ modules were really hot and I disconnected them and fall back on the 2.5Gbps Ethernet port.
I searched the internet and SFP+ copper, seems to get really hot.
Then I asked the seller and he proposed some tiny cooling ribs on the SFP+ modules.
Personally, I do not think that’s an adequate solution and definitely, not in a business situation.
Is there anybody out there who has experienced anything similar and found a decent solution?
Would it be possible to configure the 2.5Gbps as a fallback port when the SFP+ modules aren’t connected?
Of course, server IP must remain the same.
Or is there another solution which I didn’t think of?
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.
My Lenovo ThinkPad x1 Carbon Gen 9, is connected to the ThinkPad docking station (https://support.lenovo.com/gb/en/solutions/PD500180) via USB-C. I've installed Synaptic repository and installed Displaylink driver, this is confirmed at the newest version.
I have 2 Full HD monitors connected to the docking station via HDMI cable and this set up works on a Windows 11 device used for work, an old HP Elitebook running Mint (I can't remember version of the top of my head).
I've gone through a lot of suggested fixes online, including:
The next thing I am trying is another wipe of the device + new Ubuntu 24.04 boot - edit this did not fix the issue.
Edit 25/06 - I followed instructions to download the standalone driver (https://support.displaylink.com/knowledgebase/articles/684649). When I had to run the file from terminal - I received the command not found error.
Output from xrandr when docking station connected:
Screen 0: minimum 16 x 16, current 1920 x 1200, maximum 32767 x 32767
eDP-1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 300mm x 190mm
1920x1200 59.88*+
1600x1200 59.87
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.52
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.96
1920x1080 59.96
1600x900 59.95
1368x768 59.88
1280x720 59.86
1024x576 59.90
864x486 59.92
720x400 59.55
640x350 59.77
System details:
I can also provide clearer information if needed.
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
I followed the same steps on 26.04 for overlayroot that I used on 24.04 and it doesn't work.
sudo apt-get install overlayroot
sudo nano /etc/overlayroot.conf
set overlayroot="" to overlayroot="tmpfs"
write out
df -h shows /dev/sda2 is still being mounted on / when it should be mounted in a write protected state. Any changes made do persist between restarts.
How can I get this to work properly?
I am running Ubuntu 24.04.4 on a ThinkPad T14s. I am having trouble connecting to the Eduroam WiFi network at my school on Ubuntu. When I try to connect, it takes a long time and usually only connects after multiple attempts. Sometimes it fails several times before finally connecting.
I do not have this issue with other WiFi networks. They connect quickly and work normally. The problem only happens with eduroam.
Here is the Eduroam security configuration that shows the security configuration I am using for Eduroam.
Has anyone experienced this issue before or knows what might be causing the slow connection and repeated connection attempts?
Folks, I have recently purchased this laptop: https://psref.lenovo.com/Product/Yoga/Yoga_Pro_9_14IRP8
And I can only get the front speakers working on Ubuntu 22.04 which results in the sound being not great to say the least.
From reading around I found out that the laptop comes with two sets of speakers like many new Yoga laptops and both of them are supposed to be playing at the same time: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165
Same issue on Fedora: https://discussion.fedoraproject.org/t/problem-with-sound-on-new-lenovo-laptops/72456
I was not able to get the speakers running with the tricks above, does anyone have an idea? Thank you in advance.
I am currently running the kernel: 6.2.0-33-generic.
Does anybody know how, in Ubuntu using tmux, to copy an entire terminal and/or copy multiple terminal pages?
The usual trick I use in the terminal in a non-tmux session is to scroll up to the top of where I'd like to highlight, left click and drag some text, then release the left mouse button, then scroll down a few screens (or however far is desired) then hold shift, then left click and drag and it will include all the lines where I started highlighting above all the way down to where I started the 2nd highlighting. This trick does not work in tmux however, since when I start a new highlight area, even if holding shift, tmux looses the previous highlight area.
Many of the other posts on the various interwebs have instructions to the effect of:
CTRL+b, [.CTRL+SPACE to start copying.ALT+w or CTRL+w to copy into Tmux buffer.CTRL+b, ] to paste in a possibly different Tmux pane/window.But when I do this, on step 4 nothing gets highlighted, i.e. Ctrl + Space in step 3 does not seem to enter a copy mode. I'm not sure if this is due to certain hotkeys being preempted by Ubuntu or for some other reason.
I'm using Ubuntu 20.04 and tmux 2.8.
Any suggestions?
I try to customize storage layout in user-data for autoinstall here is part of my user-data
storage:
#layout:
# name: direct
config:
- type: disk
match:
size: largest
#ssd: true
id: ssd0
ptable: gpt
wipe: superblock
- type: partition # create partitions on ssd0
number: 1
id: efi-partition
device: ssd0
size: 256M
flag: boot # uefi partition needs boot flag
grub_device: true # and must be the grub device?
- type: partition
number: 2
id: boot-partition
device: ssd0
size: 768M
- type: partition
number: 3
id: root-partition
device: ssd0
size: -1
- type: format # format partitions on ssd0
id: efi-format
volume: efi-partition
fstype: fat32 # ESP gets FAT32
label: ESP
- type: format
id: boot-format
volume: boot-partition
fstype: ext4
label: BOOT
- type: format
id: root-format
volume: root-partition
fstype: ext4 # / (root) gets ext4, xfs, btrfs
label: ROOT
- type: mount # mount formatted partitions on ssd0
id: root-mount # / (root) gets mounted first
device: root-format
path: /
- type: mount
id: boot-mount # /boot gets mounted next
device: boot-format
path: /boot
- type: mount
id: efi-mount # /boot/efi gets mounted next
device: efi-format
path: /boot/efi
then I got this error during the installation
"autoinstall config did not create needed bootloader partition"
I am really frustrated with this "autoinstller" ...
I want the user to choose the file named "main folder"
but if i just use
read foldername
ls $foldername
it just reads the words "main" and "folder" separately (basically executing ls main instead of ls "main folder"how can i make so it includes spaces ?
I have tried read -r foldername but no luck
How to disable the shortcut keys for "Keybindings for desktop switching" for Lubuntu 20.04 as described in https://manual.lubuntu.me/stable/F/keyboard_shortcuts.html?
I need to use some of the keys there in Emacs, but Lubuntu 20.04 seems to intercept those keys before they even reach Emacs.
I rent a VPS from Contabo for about half a year now. It worked fine until now, because it started producing "Temporary failure in name resolution" errors. I read that this is a DNS error. I tried nameserver 8.8.8.8 and nameserver 1.1.1.1 but the problems are still here.
Yesterday I completely reinstalled the VPS, but it didn't work.
Results of /etc/resolv.conf:
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 127.0.0.53
options edns0
search invalid
Results of resolvectl status:
Global
LLMNR setting: no
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test
Link 2 (eth0)
Current Scopes: DNS
DefaultRoute setting: yes
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 213.136.95.11
DNS Servers: 213.136.95.10
213.136.95.11
DNS Domain: invalid
Results of sudo systemctl status systemd-resolved.service:
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2020-05-21 21:45:08 CEST; 1 day 14h ago
Docs: man:systemd-resolved.service(8)
https://www.freedesktop.org/wiki/Software/systemd/resolved
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Main PID: 460 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 9487)
Memory: 7.5M
CGroup: /system.slice/systemd-resolved.service
└─460 /lib/systemd/systemd-resolved
May 23 11:59:44 vmi329703.contaboserver.net systemd-resolved[460]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 23 12:00:18 vmi329703.contaboserver.net systemd-resolved[460]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 23 12:00:20 vmi329703.contaboserver.net systemd-resolved[460]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 23 12:00:31 vmi329703.contaboserver.net systemd-resolved[460]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 23 12:00:48 vmi329703.contaboserver.net systemd-resolved[460]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 23 12:01:05 vmi329703.contaboserver.net systemd-resolved[460]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 23 12:01:15 vmi329703.contaboserver.net systemd-resolved[460]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 23 12:01:29 vmi329703.contaboserver.net systemd-resolved[460]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 23 12:01:55 vmi329703.contaboserver.net systemd-resolved[460]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
May 23 12:02:21 vmi329703.contaboserver.net systemd-resolved[460]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
I have a Discord bot, and usually the problem comes up there.
I'm using mongodb database to save my application data into collection but by some reasons the mongodb connection is break and there is lot of problems occurs and I want to check the mongodb connection through terminal command. I searched for it and I found three commands which will be used but I'm confused that which command I have to use in the golang code.
Command 1. pgrep mongod this command will return me PID (process Id).
Command 2. ps -ef | grep mongod this command will returns me mongodb 15678 1 1 13:58 ? 00:00:01 /usr/bin/mongod --config /etc/mongod.conf
Command 3. ps -ef | grep mongod | grep -v grep | wc -l | tr -d ' ' this command I found from the stackoverflow accepted answer and it may be returns 0, 1. if there is other value except 0 then your mongodb is running as the answer say you can see link of the question
link:- https://stackoverflow.com/questions/31561098/how-to-check-if-mongo-db-is-running-on-mac
Command 4. service --status-all | grep mongod will show me the mongod service with a signed like [ + ], or [ - ]. In the documentation they says that if the service with [ + ] the service is running and [ - ] the service is stopped. But on my localhost the mongod is running and it will show me [ - ] mongod when I execute this command. Why?
link:- https://www.rosehosting.com/blog/how-to-list-all-services-in-linux/
Please tell me that which Command I have to used to check that the mongodb is running or not I have to use that command in my golang code.
It's an interesting problem I never saw before. The hard disk of this laptop has a harware problem (on a specific sector it got some problems).
That's why if I let Ubuntu installation to create the partitions, using the whole space, that fails.
However, if I create the partitions, without using the entire space, that passes (the partitions are created and it goes forward to installation).
I created the following partitions, on the 500GB hard drive:
100GB ext4, mount: /2GB swap1GB EFIIf I don't create the EFI partition, Grub fails to be installed. So, I saw that Ubuntu was going to create the EFI partition, by default, and I created it manually when selecting the Something else option.
The installation went well. It even displayed the alert saying that everything was successful.
But, when restarting the laptop, it doesn't boot from the HDD. I don't see the HDD option in the BIOS.
I tried to add it, but it asks me about the path for boot––which I have no idea what it is.
How to solve this? How can I get Ubuntu running on this laptop?
It doesn't have Secure Boot or anything similar in BIOS.
I have a live usb drive which I can use to access the hard drive, which works nicely.
Just trying to get a basic setup of openSSH going on an Ubuntu box to work remotely. Main issue: RSA keys fail auth. ssh DOES work using the password for auth, but I would much rather limit it to only allow ssh keys for auth.
Note that I refer to desktop and laptop. Desktop: machine acting as server. Laptop: machine acting as client.
Things that I have tried:
The relevant things I can think to include are the -vvv when attempting to connect on the laptop, the permissions of ~/.ssh on both machines, sshd_config on desktop, relevant entries in var/log/auth.log on the desktop. Obviously, if there is anything else that I can include that could help anyone resolve this issue, I will gladly provide relevant info.
Here is the -vvv when trying to auth:
➜ /home/troy
≫ ssh -vvv -i .ssh/id_rsa lenny@xxx.xxx.xxx.229 -p xxx40
OpenSSH_7.4p1, OpenSSL 1.0.2k 26 Jan 2017
debug1: Reading configuration data /etc/ssh/ssh_config
debug2: resolving "xxx.xxx.xxx.229" port xxx40
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to xxx.xxx.xxx.229 [xxx.xxx.xxx.229] port xxx40.
debug1: Connection established.
debug1: identity file .ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file .ssh/id_rsa-cert type -1
debug1: identity file /home/troy/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/troy/.ssh/id_rsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.4
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.2p2 Ubuntu-4ubuntu2.1
debug1: match: OpenSSH_7.2p2 Ubuntu-4ubuntu2.1 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to xxx.xxx.xxx.229:xxx40 as 'lenny'
debug3: put_host_port: [xxx.xxx.xxx.229]:xxx40
debug3: hostkeys_foreach: reading file "/home/troy/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file /home/troy/.ssh/known_hosts:5
debug3: load_hostkeys: loaded 1 keys from [xxx.xxx.xxx.229]:xxx40
debug3: order_hostkeyalgs: prefer hostkeyalgs: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,ext-info-c
debug2: host key algorithms: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com,zlib
debug2: compression stoc: none,zlib@openssh.com,zlib
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
debug2: host key algorithms: ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com
debug2: compression stoc: none,zlib@openssh.com
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug1: kex: algorithm: curve25519-sha256@libssh.org
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:M57GEOh/5elIh2RU446bRCamJ21QosRFOYaYx8u5Za4
debug3: put_host_port: [xxx.xxx.xxx.229]:xxx40
debug3: put_host_port: [xxx.xxx.xxx.229]:xxx40
debug3: hostkeys_foreach: reading file "/home/troy/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file /home/troy/.ssh/known_hosts:5
debug3: load_hostkeys: loaded 1 keys from [xxx.xxx.xxx.229]:xxx40
debug3: hostkeys_foreach: reading file "/home/troy/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file /home/troy/.ssh/known_hosts:5
debug3: load_hostkeys: loaded 1 keys from [xxx.xxx.xxx.229]:xxx40
debug1: Host '[xxx.xxx.xxx.229]:xxx40' is known and matches the ECDSA host key.
debug1: Found key in /home/troy/.ssh/known_hosts:5
debug3: send packet: type 21
debug2: set_newkeys: mode 1
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: SSH2_MSG_NEWKEYS received
debug2: set_newkeys: mode 0
debug1: rekey after 134217728 blocks
debug2: key: .ssh/id_rsa (0x55a0c58221f0), explicit, agent
debug2: key: /home/troy/.ssh/id_rsa (0x55a0c582fe00), agent
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512>
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey
debug3: start over, passed a different list publickey
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: .ssh/id_rsa
debug3: send_pubkey_test
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey
debug1: Offering RSA public key: /home/troy/.ssh/id_rsa
debug3: send_pubkey_test
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
Permission denied (publickey).
And here is ~/.ssh on the desktop:
lenny@Timubukuntu:~/.ssh$ ls -la
total 12
drwx------. 2 lenny lenny 4096 Feb 27 21:49 .
drwxr-x---. 21 lenny lenny 4096 Feb 27 22:16 ..
-rw-------. 1 lenny lenny 1146 Feb 27 20:35 authorized_keys
And the ~/.ssh on the laptop:
➜ /home/troy/.ssh
≫ ls -la
total 20
drwx------ 2 troy users 4096 Feb 27 21:53 .
drwx------ 30 troy users 4096 Feb 27 23:03 ..
-rw------- 1 troy users 1679 Feb 27 20:32 id_rsa
-rw-r--r-- 1 troy users 394 Feb 27 20:32 id_rsa.pub
-rw-r--r-- 1 troy users 1416 Feb 27 15:13 known_hosts
And the sshd_config on the desktop:
lenny@Timubukuntu:/etc/ssh$ cat sshd_config
# Package generated configuration file
# See the sshd_config(5) manpage for details
# What ports, IPs and protocols we listen for
Port xxx40
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
#ListenAddress 0.0.0.0
Protocol 2
# HostKeys for protocol version 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key
HostKey /etc/ssh/ssh_host_ed25519_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes
# Lifetime and size of ephemeral version 1 server key
KeyRegenerationInterval 3600
ServerKeyBits 1024
# Logging
SyslogFacility AUTH
LogLevel INFO
# Authentication:
LoginGraceTime 120
PermitRootLogin prohibit-password
StrictModes yes
RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile home/lenny/.ssh/authorized_keys
# Don't read the user's ~/.rhosts and ~/.shosts files
IgnoreRhosts yes
# For this to work you will also need host keys in /etc/ssh_known_hosts
RhostsRSAAuthentication no
# similar for protocol version 2
HostbasedAuthentication no
# Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication
#IgnoreUserKnownHosts yes
# To enable empty passwords, change to yes (NOT RECOMMENDED)
PermitEmptyPasswords no
# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
ChallengeResponseAuthentication no
# Change to no to disable tunnelled clear text passwords
PasswordAuthentication no
# Kerberos options
#KerberosAuthentication no
#KerberosGetAFSToken no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes
X11Forwarding yes
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
#UseLogin no
#MaxStartups 10:30:60
#Banner /etc/issue.net
# Allow client to pass locale environment variables
AcceptEnv LANG LC_*
Subsystem sftp /usr/lib/openssh/sftp-server
# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication. Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM yes
And here is the relevant info in /var/log/auth.log on the desktop:
Feb 27 22:52:31 Timubukuntu sshd[1901]: Connection closed by 67.20.206.135 port 36566 [preauth]
Today I tried to switch to another shell.
First I tried fish, and used chsh -s fish to change fish to default. After some time I found it cannot use ~/.bashrc (&& needs to be replaced by and).
Because I prefer to reusing ~/.bashrc, I found zsh which seems an easier one and followed this documentation to switch to zsh.
While I was running sh -c "$(curl -fsSL https://raw.githubusercontent.com/robbyrussell/oh-my-zsh/master/tools/install.sh)", suddenly it asked me to enter Password:. I entered the root password but got PAM: Authentication failure.
Then I tried chsh -s bash and chsh -s zsh, it always asked me for a password and threw PAM: Authentication failure (not system password). I can't figure this out.
I ran openvpn client on my Ubuntu 14.04 successfully, but the sites with https (SSL protocol) cannot be opened while http sites seems working fine.
I know about changing owners/permissions on particular programs/files, but how can I control which users have access to the network card (NIC) or have the power to create network sockets?
I am fairly familiar with setting up servers, and ubuntu is generally my flavor of choice, but I just installed 12.04 desktop and I am seeing some behavior in network manager that is really puzzling. The network connection works fine if I leave it set on dhcp, but I would like a static IP address for my new web server. When I go into network manager and edit the connection for the one and only NIC I can select MANUAL from the dropdown menu but as soon as I do the Save button becomes greyed out. Even after filling out all fields for the connection it is still grey and I am unable to save the static IP connection information. Any thoughts would be greatly appreciated. I'm hoping there is just some new setting that I am unaware of....
On another note, if I stop the network manager and go edit the interfaces file (and the appropriate hosts/routes/dns files), I do get a static ip address assigned and I can contact my server from the outside, however, the server cannot find the internet. Can't ping even its own ip... I can ping the loopback interface though.
I'm really confused on this one. Hoping someone can offer some help.
How can I make an application automatically start when I have logged in?