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? Here is a screenshot:

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.

Thanks in advance.

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!

The output works, but no input is listed for my HyperX Cloud III headset on Ubuntu 26.04.

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.

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.

I'm looking for help diagnosing an intermittent hardware issue on an HPC node and would appreciate any insight into whether this points to a motherboard/SATA/backplane problem, a power issue, or something else.

After rebooting this node a few weeks ago, we began seeing SATA-related errors in the kernel logs, after which the SATA connection seemingly recovers:

ata7.00: exception Emask 0x10 SAct 0x400000 SErr 0x280100 action 0x6 frozen
ata7.00: irq_stat 0x08000000, interface fatal error
ata7: SError: { UnrecovData 10B8B BadCRC }
ata7.00: failed command: READ FPDMA QUEUED
ata7.00: cmd 60/80:b0:68:98:72/00:00:14:00:00/40 tag 22 ncq dma 65536 in
                                    res 40/00:b0:68:98:72/00:00:14:00:00/40 Emask 0x10 (ATA bus error)
ata7.00: status: { DRDY }
ata7: hard resetting link
ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata7.00: configured for UDMA/133
ata7: EH complete

However, the node occasionally powers off unexpectedly and later reboots. The IPMI SEL contains entries such as: Power Unit Pwr Unit Status | Power off/down | Asserted followed by boot events.

The system also reports a POST error after every boot: System Firmwares POST Err Sensor | Unknown Error | Asserted

After a couple of such reboots where everything else is seemingly fine, the node powers off completely.

The SSD itself appears healthy according to its SMART data, although the CRC_Error_Count increases with every reboot. The PSUs also appear stable (each draws ~750 W under load, out of a max power output of 2130 W).

In your experience, does this pattern suggest that power instability issues are at play, or is it a SATA connection issue that somehow leads to the system powering off intermittently? Additionally, is there any way to decode the recurring IPMI POST error?

Thanks so much for your help!

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:

• Firmware version: X13ATE.E.L3B256.2Z9.12D.XMC.R2S1E2P0S0T0W6F0.BC.Int
• OS Name: Ubuntu 26.04 LTS
• Kernel Version: Linux 7.0.0-22-generic
• Gnome version: 50
• Memory: 12 GB
• Disk Capacity: 256.1 GB
• Processor: Intel Pentium N4200 × 4
• OS Type: 64-bit

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:

• Ubuntu 24.04
• NVIDIA GeForce RTX 4060 Laptop GPU, driver 595.71.05
• Podman 4.9.3
• podman-compose 1.5.0 (pip)
• nvidia-container-toolkit installed, CDI spec at /etc/cdi/nvidia.yaml

My 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
'

Bare podman run

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 run

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?

System Information

Laptop: MSI Raider 18 HX AI A2XWJG

CPU: Intel Core Ultra 9 285HX

Storage:

• Phison 2TB NVMe SSD
• Samsung 2TB NVMe SSD

BIOS:

• Originally: E1824IMS.30F
• Updated to latest: E1824IMS.317

Operating System:

• Kubuntu (previously working normally)

Problem Description

The system was working normally until a reboot. After rebooting, Kubuntu no longer boots.

The system either drops into BusyBox (initramfs) with:

ALERT! UUID=<uuid> does not exist
Dropping to a shell!

or shows:

Kernel Panic!
VFS: Unable to mount root fs on unknown-block(0,0)

At first I suspected filesystem corruption, UUID mismatch, initramfs issues, or GRUB problems. However, extensive troubleshooting suggests the issue occurs before Linux can even detect the SSDs.

Key Findings

BIOS detects both SSDs

BIOS and Intel Rapid Storage Technology (RST) both detect:

Phison 2TB NVMe SSD
Samsung 2TB NVMe SSD

Both drives appear as:

Non-RAID Physical Disks

Therefore the SSDs are still visible at firmware level.

Linux cannot detect any NVMe devices

Booted Kubuntu 24.04.4 Live USB.

Kernel:

uname -r

Output:

6.17.0-14-generic

lsblk

lsblk

Output only shows the USB drive:

sda

No:

nvme0n1
nvme1n1

appear.

fdisk

sudo fdisk -l

Only shows the Live USB.

No internal NVMe drives are detected.

nvme-cli

sudo nvme list

Returns no NVMe devices.

dmesg

sudo dmesg | grep -i nvme

Returns nothing.

No NVMe controllers are discovered.

VMD-related messages

sudo dmesg | grep -i vmd

Shows:

vmd 0000:00:0e.0: Unknown Bus Offset Setting (3)

This message appears consistently.

PCI Information

lspci -nn

Shows:

00:0e.0 RAID bus controller:
Intel Corporation Volume Management Device NVMe RAID Controller

The VMD controller exists.

However, there are no NVMe child devices enumerated behind it.

Driver Status

lsmod | grep vmd

Shows:

vmd

The VMD module is loaded.

However:

sudo nvme list

still returns no devices.

Troubleshooting Already Performed

Boot Recovery Attempts

Tried:

• Normal boot
• Recovery mode
• Older kernel entries
• BusyBox shell investigation

No success.

Live USB Testing

Tested with Kubuntu Live USB.

Live environment also cannot detect any NVMe devices.

BIOS Reset

Performed:

Load Optimized Defaults

No change.

BIOS Update

Updated BIOS:

E1824IMS.30F
→
E1824IMS.317

No change.

Kernel Parameters

Tried:

vmd.force=1
pci=nocrs

No improvement.

Driver Checks

Verified:

modprobe vmd
modprobe nvme
modprobe nvme_core

Modules load successfully.

Still no NVMe devices appear.

Current Assessment

At this point I do not believe the issue is:

• GRUB
• initramfs
• filesystem corruption
• UUID mismatch
• Btrfs corruption

because Linux cannot detect any NVMe devices at all.

The SSDs are visible to BIOS and Intel RST but are not being exposed to Linux.

The most suspicious clue is:

vmd 0000:00:0e.0: Unknown Bus Offset Setting (3)

combined with complete absence of any NVMe device enumeration.

Questions

1. Has anyone seen "Unknown Bus Offset Setting (3)" on Intel VMD systems before?
2. Could this indicate a VMD firmware issue or Linux VMD driver incompatibility with this platform?
3. Is there any way to bypass VMD and expose the NVMe drives directly to Linux?
4. Are there additional VMD debugging commands I should run?
5. Has anyone successfully used Linux on an MSI Raider 18 HX AI (Core Ultra 9 285HX) with Intel VMD enabled?

Any suggestions would be greatly appreciated. At the moment Linux cannot see any internal SSDs, so even reinstalling the operating system is not possible because no installation target appears.

The following error message occurred while downloading and installing Ubuntu in a Windows terminal.

Downloading: Ubuntu
Installing: Ubuntu

The system cannot find the file specified.
Error code: Wsl/InstallDistro/Service/RegisterDistro/CreateVm/HCS/  
ERROR_FILE_NOT_FOUND

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

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:

• Changing boot settings
• Disabling PCIe tunneling
• Locked boot order (Ubuntu first, NVMe, USB listed in the order (should these be excluded)
• Turned off UEFI BIOS updates
• Used the ThinkPad emergency reset hole
• Turned of IPV4 and IPV6 network stack
• Intel AMT off
• memory protection off
• kernel DMA protection off
• Secure boot off
• USB docking station (40AF) firmware up to date
• updated all firmware with 'fwupdmgr'

The next thing I am trying is another wipe of the device + new Ubuntu 24.04 boot - edit this did not fix the issue.

I can also provide clearer information if needed.

I run a dual boot win11/ubuntu 24.04.4 on my pc at home because some software I use for work only works on Linux. The pc has two monitors. I left it running overnight so I could pick up my work where I left off and when I got back it told me I needed to restart for some problem (do not remember error code or anything) which is when I believe it moved to Linux kernel 6.17.0-35 and after this the mouse stopped working (wouldn’t move in response to input) and the NVIDIA drivers for my 4080 were wrong, locking the resolution to 1080x768 and failing to recognize the 2nd monitor. After updating the drivers to version 580, it recognizes both monitors and the correct resolution on Linux 0-35 but the mouse still didn’t work. Using lsusb also showed it detected the mouse was plugged in. The only previous kernel I have is 6.17.0-19-generic, where the mouse works but the drivers don’t. When I tried to install the drivers appropriate for 0-19 by changing the headers and autoinstalling the drivers they are still not correct after rebooting and selecting 0-19. Does anyone know the way to either get my mouse to work on 0-35(it also works correctly in win11 and BIOS) or the driver to work in 0-19?

Edit 1: I have also discovered there is no driver for my Ethernet adapter or wireless network controller via the command lspci -knn | grep Network -A3

I'm trying to connect to a legacy Samba server here on Ubuntu 26.04 using the command: sudo mount.cifs //192.168.0.3/emanoel /mnt cifs credentials=/home/emanoel/.smbcredentials,vers=1.0,iocharset=utf8,file_mode=0777,noperm,gid=1000,uid=1000 0 0

but I can't connect. I believe it's because of SMB 1.0, giving the following error:

mount error: Server abruptly closed the connection. This can happen if the server does not support the SMB version you are trying to use. The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0.mount error(112): Host is down. Refer to the mount.cifs(8) manual page (e.g., man mount.cifs) and kernel log messages (dmesg).

I added the fstab line, it passes without error, accessing it through Nautilus works without errors, but no files from the share appear.

Everything works as expected on Ubuntu 24.04.

This app called Software Install, named gnome-software-local-file-flatpak (also sometimes shows up as just Software, named org.gnome.Software) autostarts at login and keeps running in the background.

It is different from App Center snap-store which comes preinstalled. I had to download Software Install from apt (probably came as gnome-software or something), and I used it to install flatpaks (also supports snaps after I turned that setting on) keeps running in the background

How do I stop Software Install / Software from running in the background? I'm using Ubuntu LTS 26.04 with GNOME 50.

Things I've already tried to no avail:

1. Turned off automatic updates, show search results from application settings
2. Turned off startup at login from System Settings > App Permissions
3. "masked" some service from Terminal following some online results, but it shows that "such a service doesn't exist, creating one". If it is worthwhile to detail this step, let me know as a comment and I'll do it.
4. Following this answer, could not delete NoDisplay=True from /etc/xdg/autostart/gnome-software-service.desktop because no such file exists.

PS: This is one thing I dislike about Ubuntu. Things change so much and so quickly - there is no persistence in construction. Is distributed disorganization really a fundamental tenet of open source? On the contrary, I think Linux has been most successful in fields where developers have built things based on a unified scheme and purpose. Too many options isn't necessarily a good thing if it comes at the cost of being worried all the time about what's going wrong in your system.

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

I am trying to install Lubuntu 26.04 on an old computer, dual boot alongside Windows 10 on the same GPT SSD, however after a successful installation the computer boots into Windows. Grub does not appear, and I have no option to boot into Linux.

The motherboard is a Hybrid EFI Gigabyte 78LMT. Apparently it can make dual booting very tricky, but I lack the technical knowledge to understand details like these. Windows is installed in UEFI mode, but I can only boot from USB in legacy mode; hence, Lubuntu is not installed in EFI mode. The inability to boot USB in EFI mode is a known issue with this motherboard and its "hybrid EFI" technology.

Specs:

• Motherboard: Gigabyte GA-78LMT-USB3 Rev. 5.0

• CPU: AMD FX-8350 (8-core, 125W, AM3+)

• RAM: 8GB DDR3 1600 MHz (2×4 GB)

• GPU: AMD Radeon HD 7750 1GB GDDR5

I have tried this solution but boot-repair gives the following error:"The current session is in Bios-compatibility mode". I cannot setup the BIOS to boot USB in EFI mode, the option exists for CD/DVD only, as explained here:

Although Gigabyte's Hybrid EFI contains a full-fledged EFI implementation from an OS's perspective, the firmware setup utility provides almost no options to help you use this functionality. Specifically, only one firmware option, entitled "EFI CD/DVD Boot Option," on the "Advanced BIOS Features" menu, relates to this feature.

In another question, someone tried to install from CD, apparently without success. I have no CD/DVD drive to test this option.

I cannot find any UEFI settings to select Ubuntu as the default operating system to boot either; thus, it seems this solution will not work: no UEFI settings.

I can choose from which disk to boot; Windows and Ubuntu are on the same SDD. I have also an old HDD I use for backup attached to the motherboard; perhaps installing GRUB on it could be a solution?

I've done this many times on different systems, but this has me puzzled:

OS: Ubuntu 26

Had an external drive that I was mounting using the fstab.

/dev/sda1 /data ext4 defaults 0 0

I removed the drive and of course it rebooted and went into recovery mode. So I edited the /etc/fstab and removed the external drive mount. Now when it reboots, it still hangs up on trying to mount that drive.

Does Ubuntu 26 store the information that is/was in the fstab in another spot? Like a database or other file? I noticed the fstab in Ubuntu 26 is very minimal, so I'm guessing there is some sort of other place that needs to be updated??

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:

1. Enter ‘copy mode’ by pressing CTRL+b, [.
2. Use the arrow keys to go to the position from where you want to start copying. 3) Press CTRL+SPACE to start copying.
3. Use arrow keys to go to the end of text you want to copy. Press ALT+w or CTRL+w to copy into Tmux buffer.
4. Press 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 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

My computer is stuck at a black screen with cursor before logging in. After booting into Ubuntu 20.04 nothing is working, even the cursor is not moving. It's freezing. I also tried Ctrl+Alt+F4, but it's not opening the terminal. When I restart the system and in grub menu select Advanced options for Ubuntu and select Recovery mode, the recovery mode is not working either. It's stuck. Only the old recovery mode is working. How to fix this problem?

During the OS installation I think I have selected the option to install third-party drivers, firmware, codecs, etc., but I'm not sure.

Hardware specs:

• Intel Core i7
• Nvidia Gtx 1060
• 16 GB RAM
• 1TB NVMe SSD

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'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.

I recently switched to linux full time from windows and while I was trying to update my npm package using n, I got the new binaries in /usr/local/bin and previous version was in /usr/bin. So, it was always picking the previous version.

As per recommendation by a fellow user, I used hash -r command and it worked. But, I don't know what it did.

It would be very helpful if someone could explain its internals to me.

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 am trying to help a user solve an issue with a bootable USB drive, but there seems to be a file whose ownership cannot be edited. I thought it would have been possible with:

sudo chown user:user ldlinux.sys

When that is executed, however, terminal gives this error:

Operation not permitted

The extended chat I had with the user can be found here.

My printer is HP laser jet pro p1102. It is a share printer. When I try to print this error message pops up

Unable to connect to CIFS host

How can I make an application automatically start when I have logged in?