I have a hp laptop 15s fq as my main pc and from the moment I started using it, I had many problems. Im asking here because sadly I had no luck on zorin forums and I was wondering if there is something I can do Firstly, I have a intel i5 and an intel irisxe gpu and from the moment I installed zorin on it, I was immediately met with tiny scaling on 1920x1080 and it wasnt usable. So my only solution was fractional scaling to 125% witch worked fine until I was met with screen tearing on xorg. Wayland was a temporary fix as x11 apps on wayland where blurry A guy at hp community told me to edit graphics configuration like this

Section "Device"    
    
    Identifier  "Intel Graphics"    
    
    Driver      "intel"    
    
    Option      "TearFree" "true"    
    
    Option      "AccelMethod" "sna"    
    
    Option      "DRI" "3"    
    
    Option      "TripleBuffer" "true" EndSection

But this only made it worse because it froze x11 and I had to force reboot Secondly, I started having severe slowdown and distorted audio while I was charging or doing things like playing some lightweight discord games which I didn't expect to do this... Sometimes audio gets distorted for now reason at all. As a dev having such slowdown while using many windows open it is bad...Its like my keyboard has a delay.. Other times it just doesn't have problems at all *when its mostly not charging. I have to note that I have a nvme ssd and ddr16gb ram so I don't really understand the reason it does that Can anyone help?

I’m using a VPS with Ubuntu 22.04 and XFCE desktop (4 vCPU, 16GB RAM). But it's extremely slow — even when idle, opening a browser or switching tabs takes 10–15 seconds. I tried killing all processes and using htop, but nothing is eating resources. Time inside the VPS also lags. Is this a system misconfiguration or could it be an issue with the host node? Any advice would be appreciated. Thanks!

If I restore a tar archive or do any other bulky filesystem operation I observe kworker running at close to 100% CPU utilization and operations which was done in 10-15 minutes takes a week. When the operation is complete the system appears as normal. This is an ext4 filesystem on top of lvm on top of mdadm. I did a few: echo l > /proc/sysrq-trigger And I observed the following: [15858776.231727] Sending NMI from CPU 3 to CPUs 0-2,4-7: [15858776.231738] NMI backtrace for cpu 6 [15858776.231744] CPU: 6 PID: 32516 Comm: kworker/u16:4 Tainted: G T 6.6.13-gentoo #1 [15858776.231751] Hardware name: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F/X9SRE/X9SRE-3F/X9SRi/X9SRi-3F, BIOS 1.0a 03/06/2012 [15858776.231755] Workqueue: writeback wb_workfn (flush-252:4) [15858776.231769] RIP: 0010:ext4_get_group_info+0x12/0x60 [15858776.231780] Code: 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 48 8b 87 38 05 00 00 3b 70 40 73 49 41 54 41 89 f4 55 89 fd 53 8b 88 b0 00 00 00 89 f3 48 8b 40 38 41 d3 ec 48 83 e8 [15858776.231785] RSP: 0018:ffffa91005d7f6e8 EFLAGS: 00000283 [15858776.231790] RAX: ffff901dd559f000 RBX: 0000000000000002 RCX: 0000000000000002 [15858776.231794] RDX: 0000000000000002 RSI: 000000000001dad5 RDI: ffff901dd55b1000 [15858776.231798] RBP: 000000000001dad5 R08: 0000000000000009 R09: 0000000000000300 [15858776.231801] R10: 0000000000000001 R11: 0000000000000000 R12: 000000000001dad5 [15858776.231804] R13: ffff901dc36fe098 R14: 0000000000000002 R15: ffff901dc8d4fc38 [15858776.231808] FS: 0000000000000000(0000) GS:ffff902cffd80000(0000) knlGS:0000000000000000 [15858776.231813] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [15858776.231817] CR2: 000018c403504000 CR3: 0000000af6c2c005 CR4: 00000000000606e0 [15858776.231821] Call Trace: [15858776.231825] [15858776.231828] ? nmi_cpu_backtrace+0x84/0xf0 [15858776.231837] ? nmi_cpu_backtrace_handler+0x8/0x10 [15858776.231846] ? nmi_handle+0x58/0x150 [15858776.231853] ? ext4_get_group_info+0x12/0x60 [15858776.231860] ? default_do_nmi+0x69/0x170 [15858776.231870] ? exc_nmi+0xfe/0x130 [15858776.231878] ? end_repeat_nmi+0x16/0x67 [15858776.231889] ? ext4_get_group_info+0x12/0x60 [15858776.231896] ? ext4_get_group_info+0x12/0x60 [15858776.231903] ? ext4_get_group_info+0x12/0x60 [15858776.231910] [15858776.231912] [15858776.231914] ext4_mb_good_group+0x24/0xf0 [15858776.231922] ext4_mb_find_good_group_avg_frag_lists+0x89/0xe0 [15858776.231929] ext4_mb_regular_allocator+0x44e/0xe60 [15858776.231939] ext4_mb_new_blocks+0x9db/0x1040 [15858776.231948] ? ext4_find_extent+0x3bd/0x410 [15858776.231955] ext4_ext_map_blocks+0x382/0x1890 [15858776.231962] ? release_pages+0x122/0x3e0 [15858776.231971] ? filemap_get_folios_tag+0x1c5/0x1f0 [15858776.231983] ext4_map_blocks+0x18a/0x610 [15858776.231990] ? ext4_alloc_io_end_vec+0x15/0x50 [15858776.231997] ext4_do_writepages+0x74d/0xc80 [15858776.232007] ? preempt_count_add+0x65/0xa0 [15858776.232016] ext4_writepages+0xbd/0x1a0 [15858776.232026] do_writepages+0xc6/0x1a0 [15858776.232032] ? __schedule+0x2fb/0x890 [15858776.232041] __writeback_single_inode+0x3b/0x360 [15858776.232048] ? _raw_spin_lock+0xe/0x30 [15858776.232055] writeback_sb_inodes+0x1f9/0x4d0 [15858776.232064] __writeback_inodes_wb+0x47/0xe0 [15858776.232072] wb_writeback+0x265/0x2d0 [15858776.232080] wb_workfn+0x32c/0x4b0 [15858776.232087] ? _raw_spin_unlock+0xd/0x30 [15858776.232095] ? finish_task_switch.isra.0+0x8c/0x270 [15858776.232106] process_one_work+0x134/0x2f0 [15858776.232115] worker_thread+0x2f2/0x410 [15858776.232123] ? preempt_count_add+0x65/0xa0 [15858776.232130] ? _raw_spin_lock_irqsave+0x12/0x40 [15858776.232139] ? __pfx_worker_thread+0x10/0x10 [15858776.232146] kthread+0xf1/0x120 [15858776.232153] ? __pfx_kthread+0x10/0x10 [15858776.232158] ret_from_fork+0x2b/0x40 [15858776.232164] ? __pfx_kthread+0x10/0x10 [15858776.232169] ret_from_fork_asm+0x1b/0x30 [15858776.232180] Is the call to ext4_mb_find_good_group_avg_frag_lists an indication of a fragmentation issue, if not how can I debug this issue? No problems are reported in /proc/mdstat and I see no /dev/sdX /dev/mdX related errors in the kernel log.

I have two computers running fully updated Fedora 40. The two computers have the exact same packages installed. They are not identical, but very similar and bought at the same time: Dell Optiplex 7000 (SSF vs Micro). They have always performed essentially identically. Yet, this week one of the two began to behave *MUCH* slower than the other. Around 1/3 the speed. Commands top, free, and the benchmarks for the NVME SSD's show no sign of problems. It does not seem to be any process slowing down the computer. The one that has problems is the Micro, that has 16GB of DDR5 RAM vs 24GB of DDR4 of the SFF. I tried working in different NVMEs, I tried switching to an older kernel (kernel-6.10.11 vs kernel-6.11.3)... Nothing... Any ideas?

At almost each shutdown of my Linux Mint 18.2 Cinnamon 64-bit, I must wait ages at: > a stop job is running for make remote cups printers available locally *** Some information I find most useful: 1. I have one installed local USB printer unattached unless I need it. 2. That said, I don't have an idea what the system is waiting for. 3. The printer is HP, so HPLIP has been installed. 4. I repeat, that at shutdown, the printer is never attached to the USB. 5. But typically once a week I need to print on it. 6. May I simply disable the cups-browsed service to solve this? I mean:

sudo systemctl disable cups-browsed.service

and the printer would still work?

I am running Debian GNU/Linux 12.5.0 (bookworm) on a computer which has suddenly failed to boot and is extremely slow in emergency mode. Apologies in advance if I leave something important out, I am a Linux noob. ## Background ## The problem began while running qBittorrent-nox, whereupon I realized after a while that the web-client was not responding. Investigating further, I also noticed that tries to connect to the server with ssh timed out. I held in the power button after this in an attempt to do a hard restart, which in retrospect should probably not have been done. Powering up the machine again took a very long time (~5 minutes), which landed me in emergency mode with some error messages (see codebox in following chapter). While in emergency mode, every command took at least 10 seconds to respond, if not more. Soft restarting sucessfully booted the machine once, but the slowdown persisted. Every new soft restart after that has been into emergency mode. I tried running in GRUB, but it got permanently stuck on some line and did not boot. ## Tried fixes ## I've tried to run fsck -f on the EFI partition while in rescue mode. This seemingly did not do anything. I've tried running a shell on /dev/nvme0n1p1 while in rescue mode but was notified that there was no shell available on this partition. I've tried adding Storage=persistent to journald.conf as was suggested in but this did not do anything. I've looked into changing the file system type, as in , but decided against it since it looks like I have the correct file system type. I am currently out of ideas on what to look out for. Any help or input would be greatly appreciated. Thank you in advance! ## Terminal responses ## Upon starting the server I am greeted with the following text:

[    0.074473] x86/cpu: SGX disabled by BIOS.
/dev/nvme0n1p2: clean, 88626/31162368 files, 75905231/124645632 blocks
[ TIME ] Timed out waiting for device dev-dis...E5.device - /dev/disk/by-uuid/1002
[DEPEND] Dependency failed for systemd-fsck@d...System Check on /dev/disk/by-uuid/
[DEPEND] Dependency failed for boot-efi.mount - /boot/efi.
[DEPEND] Dependency failed for local-fs.target - Local File Systems.
[ TIME ] Timed out waiting for device dev-dis...y-uuid/f7809ea0-31f9-4370-ac28-531
[DEPEND] Dependency failed for dev-disk-by\x2...y-uuid/f7809ea0-31f9-4370-ac28-531
[DEPEND] Dependency failed for swap.target - Swaps.
[FAILED] Failed to start systemd-journal-flus...e - Flush Journal to Persistent St
You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or "exit" ot boot into default mode.
Give root password for maintenance
(or press Control-D to continue):

I ran journalctl -xb, but the text file is large (1600 lines) and I do not know what's relevant in it. Please let me know if and how I should include it in the question. Here's the response when running fdisk -l: ### fdisk -l ###

Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: INTEL SSDPEKNU512G8L                    
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: F4FA719B-6D68-4615-9F20-031696FFE5CD

Device             Start        End   Sectors   Size Type
/dev/nvme0n1p1      2048    1050623   1048576   512M EFI System
/dev/nvme0n1p2   1050624  998215679 997165056 475.5G Linux filesystem
/dev/nvme0n1p3 998215680 1000214527   1998848   976M Linux swap


Disk /dev/sda: 28.82 GiB, 30943995904 bytes, 60437492 sectors
Disk model: DataTraveler 3.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x03e7f784

Device     Boot Start      End  Sectors  Size Id Type
/dev/sda1  *     2048 60437471 60435424 28.8G  c W95 FAT32 (LBA)

Something that I noticed here is that my sda or sdb partitions were seemingly gone. /dev/sda1 Here is a usb stick that I use both as a recovery device and a way to transfer log files from the linux device to my home desktop. Here's the response when running systemctl status systemd-journald-service: ### status systemd-journald-service ###

● systemd-journald.service - Journal Service
     Loaded: loaded (/lib/systemd/system/systemd-journald.service; static)
     Active: active (running) since Thu 2024-05-30 13:07:03 CEST; 34min ago
TriggeredBy: ● systemd-journald-dev-log.socket
             ● systemd-journald.socket
             ● systemd-journald-audit.socket
       Docs: man:systemd-journald.service(8)
             man:journald.conf(5)
   Main PID: 718 (systemd-journal)
     Status: "Processing requests..."
      Tasks: 1 (limit: 9391)
     Memory: 5.4M
        CPU: 104ms
     CGroup: /system.slice/systemd-journald.service
             └─718 /lib/systemd/systemd-journald

May 30 13:07:03 SkibidiServer systemd-journald: File /var/log/journal/7063fd07468243ce889ee166584c6331/system.journal corrupted or uncleanly shut down, renaming and replacing.
May 30 13:07:03 SkibidiServer systemd-journald: Journal started
May 30 13:07:03 SkibidiServer systemd-journald: System Journal (/var/log/journal/7063fd07468243ce889ee166584c6331) is 184.0M, max 4.0G, 3.8G free.
May 30 13:06:30 SkibidiServer systemd: systemd-journald.service: Watchdog timeout (limit 3min)!
May 30 13:06:30 SkibidiServer systemd: systemd-journald.service: Killing process 276 (systemd-journal) with signal SIGABRT.

Here's the content of /etc/systemd/journald.conf: ### /etc/systemd/journald.conf ###

[Journal]
Storage=persistent

Here's the content of /etc/fstab: ### /etc/fstab ###

# / was on /dev/nvme0n1p2 during installation
UUID=6f0758b8-fd39-45c4-a0ed-e3cb67144a1c /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=1002-2BE5  /boot/efi       vfat    umask=0077      0       1
# swap was on /dev/nvme0n1p3 during installation
UUID=f7809ea0-31f9-4370-ac28-5310ffae8074 none            swap    sw              0       0

And finally, here's the response when running blkid

/dev/nvme0n1p3: UUID="f7809ea0-31f9-4370-ac28-5310ffae8074" TYPE="swap" PARTUUID="797058e6-c6cf-476e-aad9-7a99bddd79d5"
/dev/nvme0n1p1: UUID="1002-2BE5" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="519bfa3c-68d2-412d-bdea-b97f51a49d02"
/dev/nvme0n1p2: UUID="6f0758b8-fd39-45c4-a0ed-e3cb67144a1c" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="ea266a1a-45da-4e66-a399-6625f2b24259"
/dev/sda1: LABEL_FATBOOT="DEBIAN12_5_" LABEL="DEBIAN12_5_" UUID="22DD-A0FE" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="03e7f784-01"

Edit: Upon request, I've run fsck on all devices. Here's the response: ### fsck -f /dev/nvme0n1p1 ###

fsck from util-linux 2.38.1
fsck.fat 4.2 (2021-01-31)
/dev/nvme0n1p1: 8 files, 1493/130812 clusters

### fsck -f -y /dev/nvme0n1p2 ###

e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Inode 6946841 extent tree (at level 1) could be narrower. Optimize? yes
...A bunch of the same prompts which I answered yes to all, inode number was always 69468xx, varying between level 1 and 2...
.
Inode 12976130 extent tree (at level 2) could be narrower. Optimize? yes

Pass 1E: Optimizing extent trees
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/nvme0n1p2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/nvme0n1p2: 88632/31162368 files (0.3% non-contiguous), 75909135/124645632 blocks

After running this, the statement [FAILED] Failed to start systemd-journal-flus...e - Flush Journal to Persistent St has dissapeared when booting, but it still boots to emergency mode and is extremely slow. ### fsck -f /dev/nvme0n1p3 ###

fsck from util-linux 2.38.1

My Linux Mint Lenovo Thinkpad e14 is unrecognizable after booting today. Many simple tasks take 5+ times longer than they used to, and my CPU is much much higher than it used to be for the same tasks. Examples: tab switcher, right click, opening firefox, thunderbird, sublime, etc. - I ran sudo apt update && sudo apt upgrade *after* this started but it did not help - I've rebooted several times - Yesterday, I installed at least 1 new R packages as root, and accessed a remote HPC cluster for the first time - I booted into Windows 10 (dual boot) and everything seemed fine there, suggesting hardware is OK? ... Not sure if any of that is relevant output of inxi -Fxxxrz:

System:    Kernel: 5.15.0-105-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 4.8.6 wm: muffin 4.8.1 
           dm: LightDM 1.30.0 Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal 
Machine:   Type: Laptop System: LENOVO product: 20TA004HUS v: ThinkPad E14 Gen 2 serial:  Chassis: type: 10 
           serial:  
           Mobo: LENOVO model: 20TA004HUS v: SDK0J40697 WIN serial:  UEFI: LENOVO v: R1EET56W(1.56 ) date: 06/29/2023 
Battery:   ID-1: BAT0 charge: 16.6 Wh condition: 45.8/45.0 Wh (102%) volts: 11.1/11.1 model: LGC 5B10X026 type: Li-poly 
           serial:  status: Discharging cycles: 2794 
CPU:       Topology: Quad Core model: 11th Gen Intel Core i7-1165G7 bits: 64 type: MT MCP arch: Tiger Lake rev: 1 
           L2 cache: 12.0 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 44851 
           Speed: 727 MHz min/max: 400/4700 MHz Core speeds (MHz): 1: 492 2: 609 3: 1038 4: 446 5: 652 6: 588 7: 979 8: 667 
Graphics:  Device-1: Intel vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:9a49 
           Display: x11 server: X.Org 1.20.13 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa Intel Xe Graphics (TGL GT2) v: 4.6 Mesa 21.2.6 direct render: Yes 
Audio:     Device-1: Intel vendor: Lenovo driver: sof-audio-pci-intel-tgl bus ID: 00:1f.3 chip ID: 8086:a0c8 
           Sound Server: ALSA v: k5.15.0-105-generic 
Network:   Device-1: Intel driver: iwlwifi v: kernel port: 4000 bus ID: 00:14.3 chip ID: 8086:a0f0 
           IF: wlp0s20f3 state: up mac:  
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Lenovo driver: r8169 v: kernel port: 3000 
           bus ID: 04:00.0 chip ID: 10ec:8168 
           IF: enp4s0 state: down mac:  
Drives:    Local Storage: total: 476.94 GiB used: 295.75 GiB (62.0%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: MZALQ512HALU-000L1 size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 
           serial:  rev: BL1QFXV7 scheme: GPT 
Partition: ID-1: / size: 342.50 GiB used: 295.71 GiB (86.3%) fs: ext4 dev: /dev/nvme0n1p6 
           ID-2: swap-1 size: 977.0 MiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p5 
Sensors:   System Temperatures: cpu: 46.0 C mobo: N/A 
           Fan Speeds (RPM): fan-1: 0 
Repos:     No active apt repos in: /etc/apt/sources.list 
           No active apt repos in: /etc/apt/sources.list.d/additional-repositories.list 
           Active apt repos in: /etc/apt/sources.list.d/deadsnakes-ppa-focal.list 
           1: deb http://ppa.launchpad.net/deadsnakes/ppa/ubuntu  focal main
           Active apt repos in: /etc/apt/sources.list.d/inkscape_dev-stable-focal.list 
           1: deb http://ppa.launchpad.net/inkscape.dev/stable/ubuntu  focal main
           No active apt repos in: /etc/apt/sources.list.d/mendeleydesktop.list 
           Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
           1: deb http://mirror.csclub.uwaterloo.ca/linuxmint-packages  ulyssa main upstream import backport
           2: deb http://mirror.csclub.uwaterloo.ca/ubuntu  focal main restricted universe multiverse
           3: deb http://mirror.csclub.uwaterloo.ca/ubuntu  focal-updates main restricted universe multiverse
           4: deb http://mirror.csclub.uwaterloo.ca/ubuntu  focal-backports main restricted universe multiverse
           5: deb http://security.ubuntu.com/ubuntu/  focal-security main restricted universe multiverse
           6: deb http://archive.canonical.com/ubuntu/  focal partner
           Active apt repos in: /etc/apt/sources.list.d/signal-xenial.list 
           1: deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt  xenial main
           Active apt repos in: /etc/apt/sources.list.d/slack.list 
           1: deb https://packagecloud.io/slacktechnologies/slack/debian/  jessie main
           Active apt repos in: /etc/apt/sources.list.d/sublime-text.list 
           1: deb https://download.sublimetext.com/  apt/stable/
           Active apt repos in: /etc/apt/sources.list.d/ubuntuhandbook1-gimp-focal.list 
           1: deb http://ppa.launchpad.net/ubuntuhandbook1/gimp/ubuntu  focal main
           Active apt repos in: /etc/apt/sources.list.d/zotero.list 
           1: deb [signed-by=/usr/share/keyrings/zotero-archive-keyring.gpg by-hash=force] https://zotero.retorque.re/file/apt-package-archive  ./
           Active apt repos in: /etc/apt/sources.list.d/librewolf.sources 
           1: deb [arch=amd64] https://deb.librewolf.net  focal main
Info:      Processes: 272 Uptime: 27m Memory: 15.32 GiB used: 2.21 GiB (14.4%) Init: systemd v: 245 runlevel: 5 Compilers: 
           gcc: 9.4.0 alt: 9 Shell: bash v: 5.0.17 running in: gnome-terminal inxi: 3.0.38

Any guidance on how to track down the source of this sudden slow-down is appreciated. FYI: cross posted [here](https://forums.linuxmint.com/viewtopic.php?t=418988) **Edit 1** additional info: - cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor | sort -u:

powersave

- lscpu | grep MHz:

CPU MHz:                            2800.000
CPU max MHz:                        4700.0000
CPU min MHz:                        400.0000

While it's in powersave mode, I don't think this is the issue, since the cpu is still ~60% and it does not explain the degree of slowdown.

On my Fedora 39 KDE, the boot time is too long; it's more than two minutes. This is the output of the command systemd-analyze:

Startup finished in 6.681s (firmware) + 3.405s (loader) + 1.176s (kernel) + 3.490s (initrd) + 54.218s (userspace) = 1min 8.971s 
graphical.target reached after 54.200s in userspace.

After seeing that the graphical target is taking up the max time to start up, I executed this command sudo systemctl list-dependencies graphical.target. This is the output I get:

graphical.target
● ├─accounts-daemon.service
● ├─power-profiles-daemon.service
● ├─rtkit-daemon.service
● ├─sddm.service
● ├─switcheroo-control.service
○ ├─systemd-update-utmp-runlevel.service
● ├─udisks2.service
● ├─upower.service
● └─multi-user.target
●   ├─abrt-journal-core.service
●   ├─abrt-oops.service
○   ├─abrt-vmcore.service
●   ├─abrt-xorg.service
●   ├─abrtd.service
●   ├─atd.service
×   ├─auditd.service
●   ├─avahi-daemon.service
●   ├─chronyd.service
●   ├─crond.service
●   ├─cups.path
●   ├─firewalld.service
○   ├─flatpak-add-fedora-repos.service
●   ├─irqbalance.service
○   ├─livesys-late.service
○   ├─livesys.service
●   ├─lm_sensors.service
●   ├─mcelog.service
○   ├─mdmonitor.service
●   ├─ModemManager.service
●   ├─mysqld.service
●   ├─NetworkManager.service
●   ├─plymouth-quit-wait.service
●   ├─plymouth-quit.service
●   ├─postgresql.service
●   ├─rsyslog.service
●   ├─smartd.service
○   ├─sssd.service
●   ├─systemd-ask-password-wall.path
●   ├─systemd-homed.service
●   ├─systemd-logind.service
●   ├─systemd-oomd.service
○   ├─systemd-update-utmp-runlevel.service
●   ├─systemd-user-sessions.service
●   ├─teamviewerd.service
○   ├─vboxservice.service
●   ├─basic.target
●   │ ├─-.mount
●   │ ├─tmp.mount
●   │ ├─paths.target
●   │ ├─slices.target
●   │ │ ├─-.slice
●   │ │ └─system.slice
●   │ ├─sockets.target
●   │ │ ├─avahi-daemon.socket
●   │ │ ├─cups.socket
●   │ │ ├─dbus.socket
●   │ │ ├─dm-event.socket
●   │ │ ├─iscsid.socket
●   │ │ ├─iscsiuio.socket
●   │ │ ├─pcscd.socket
●   │ │ ├─sssd-kcm.socket
●   │ │ ├─systemd-coredump.socket
●   │ │ ├─systemd-initctl.socket
●   │ │ ├─systemd-journald-audit.socket
●   │ │ ├─systemd-journald-dev-log.socket
●   │ │ ├─systemd-journald.socket
●   │ │ ├─systemd-udevd-control.socket
●   │ │ ├─systemd-udevd-kernel.socket
●   │ │ └─systemd-userdbd.socket
●   │ ├─sysinit.target
●   │ │ ├─dev-hugepages.mount
●   │ │ ├─dev-mqueue.mount
●   │ │ ├─dracut-shutdown.service
○   │ │ ├─iscsi-onboot.service
○   │ │ ├─iscsi-starter.service
●   │ │ ├─kmod-static-nodes.service
○   │ │ ├─ldconfig.service
●   │ │ ├─lvm2-lvmpolld.socket
●   │ │ ├─lvm2-monitor.service
●   │ │ ├─plymouth-read-write.service
●   │ │ ├─plymouth-start.service
●   │ │ ├─proc-sys-fs-binfmt_misc.automount
○   │ │ ├─selinux-autorelabel-mark.service
●   │ │ ├─sys-fs-fuse-connections.mount
●   │ │ ├─sys-kernel-config.mount
●   │ │ ├─sys-kernel-debug.mount
●   │ │ ├─sys-kernel-tracing.mount
○   │ │ ├─systemd-ask-password-console.path
○   │ │ ├─systemd-binfmt.service
○   │ │ ├─systemd-boot-random-seed.service
○   │ │ ├─systemd-firstboot.service
○   │ │ ├─systemd-hwdb-update.service
○   │ │ ├─systemd-journal-catalog-update.service
●   │ │ ├─systemd-journal-flush.service
●   │ │ ├─systemd-journald.service
○   │ │ ├─systemd-machine-id-commit.service
●   │ │ ├─systemd-modules-load.service
●   │ │ ├─systemd-network-generator.service
○   │ │ ├─systemd-pcrmachine.service
○   │ │ ├─systemd-pcrphase-sysinit.service
○   │ │ ├─systemd-pcrphase.service
○   │ │ ├─systemd-pstore.service
●   │ │ ├─systemd-random-seed.service
○   │ │ ├─systemd-repart.service
●   │ │ ├─systemd-resolved.service
●   │ │ ├─systemd-sysctl.service
○   │ │ ├─systemd-sysusers.service
●   │ │ ├─systemd-tmpfiles-setup-dev-early.service
●   │ │ ├─systemd-tmpfiles-setup-dev.service
●   │ │ ├─systemd-tmpfiles-setup.service
●   │ │ ├─systemd-udev-trigger.service
●   │ │ ├─systemd-udevd.service
○   │ │ ├─systemd-update-done.service
●   │ │ ├─systemd-update-utmp.service
●   │ │ ├─cryptsetup.target
●   │ │ ├─integritysetup.target
●   │ │ ├─local-fs.target
●   │ │ │ ├─-.mount
●   │ │ │ ├─boot-efi.mount
●   │ │ │ ├─media-Primary\x2dVolume.mount
●   │ │ │ ├─media-Secondary\x2dVolume.mount
○   │ │ │ ├─ostree-remount.service
●   │ │ │ ├─systemd-fsck-root.service
●   │ │ │ ├─systemd-remount-fs.service
●   │ │ │ └─tmp.mount
○   │ │ ├─swap.target
○   │ │ │ ├─dev-disk-by\x2duuid-83f883b3\x2dec24\x2d412a\x2db17e\x2d90251e3d5b0a.…
●   │ │ │ └─dev-zram0.swap
●   │ │ └─veritysetup.target
●   │ └─timers.target
●   │   ├─dnf-makecache.timer
●   │   ├─fstrim.timer
●   │   ├─logrotate.timer
●   │   ├─plocate-updatedb.timer
●   │   ├─raid-check.timer
●   │   ├─systemd-tmpfiles-clean.timer
●   │   └─unbound-anchor.timer
●   ├─getty.target
○   │ └─getty@tty1.service
●   ├─nfs-client.target
○   │ ├─auth-rpcgss-module.service
●   │ ├─rpc-statd-notify.service
●   │ └─remote-fs-pre.target
●   ├─remote-cryptsetup.target
●   └─remote-fs.target
●     └─nfs-client.target
○       ├─auth-rpcgss-module.service
●       ├─rpc-statd-notify.service
●       └─remote-fs-pre.target

And this is the output of the command systemd-analyze critical-chain. The time when unit became active or started is printed after the "@" character. The time the unit took to start is printed after the "+" character. graphical.target @48.691s └─multi-user.target @48.691s └─mysqld.service @47.214s +1.476s └─network-online.target @47.210s └─network.target @47.210s └─wpa_supplicant.service @47.205s +4ms └─basic.target @46.155s └─dbus-broker.service @46.124s +29ms └─dbus.socket @46.113s └─sysinit.target @46.110s └─systemd-resolved.service @46.029s +80ms └─systemd-tmpfiles-setup.service @45.907s +103ms └─local-fs.target @45.903s └─tmp.mount @45.895s +6ms └─systemd-journald.socket └─system.slice └─-.slice Additionally, these are the contents of /etc/fstab.

#
# /etc/fstab
# Created by anaconda on Sat Apr  6 12:14:37 2024
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
UUID=0c14ae1c-b017-4009-9e5f-d34ad79f8f1c /                       ext4    defaults        1 1
UUID=452B-16BD          /boot/efi               vfat    umask=0077,shortname=winnt 0 2
UUID=83f883b3-ec24-412a-b17e-90251e3d5b0a none                    swap    defaults        0 0
UUID=C07AC41E7AC412D8   /media/Primary-Volume                     ntfs    defaults        0 0
UUID=B0F8B100F8B0C5BE   /media/Secondary-Volume                   ntfs    defaults        0 0

I don't have a detailed idea about which service should be here and which shouldn't. Please note that during the time of booting, no grub menu is displayed. My system directly boots into Fedora. I don't know why it is taking so much time on Userspace. It was fine 2 hours ago.

I have a laptop with EndeavourOS on it. It has a Core i3-4405U (4) 1,6Ghz, and it's sometimes lagging, e.g. if I start a program like Firefox or a game like Minecraft. It just starts lagging so much that even the mouse is lagging, and nothing works anymore. The fan is speeding up, and my HDD is starting to spin like crazy. Is there anything I can do to fix it?

[zuna@zuna-80hw ~]$ LC_ALL=C free -g
               total        used        free      shared  buff/cache   available
Mem:               3           2           0           0           0           0
Swap:              0           0           0

I am a user of Ubuntu, Kali and lately Parrot for approximately the past 10-15 years (notebook, private use). Every now and then there are small problems to solve, but in general, everything works as it should. Except one fundamental issue that is a massive annoyance - copying files. Right now I try to copy a single 100GB file from my notebook to an external hard disk connected via USB. The first few GB go quite fast and then the speeds slows down to several hundred kb per second. On good days it remains at 3-4MB. Sometimes the speed increases for shorter periods of time just to slow down again. When copying folders with multiple smaller files the general behaviour is the same. This makes it basically impossible to copy large amounts of data. Over the years, I experienced this on four different notebooks (e.g. ASUS, DELL, ...) that were new when I got them. By now I probably had more than 10 different USB storage devices in use (e.g. Toshiba, Verbatim, ...). The story is always the same. Since I use Linux this was always like that. It also does not matter if I use the GUI or for example the cp command via terminal. When looking for this issue online people either say that this is known Linux bug for years and one just has to live with it or they get lost in the details of the hardware involved. Based on my experience over the years this really does not seem to be a problem of the involved hardware. At least some of my devices had Windows installed in parallel and of course I tested the storage devices on Windows machines as well. Everything was fine and the copying speeds were always acceptable. By acceptable I mean that I do not care about "minor differences" in speeds of 40MB vs. 60MB vs. 100MB but rather 40MB vs 800kB - a difference in the order "I have no clue if the copy process every reaches an end". This might be my last attempt to find a solution for this. What options do I have to reach acceptable file copy speeds in Linux? Has it something to do with the distributions all being Debian based? But why does this seem to affect certain people heavily and others not? Update: I adjusted the dirty_background_bytes and dirty_bytes as suggested. At the moment I want to copy a 50GB File from Parrot OS to an external 2TB USB hard disk. After approx. an hour, 27GB of the 50GB file are copied. The remaining time is 40min and stays almost constant as the speed keeps decreasing (9.9MB/sec at the moment). Not sure if I ever get a copy. This behaviour affects everything (e.g. pretty much unable to backups files). How can such a basic function of the operating system cause such issues. When I was using Windows in the past this did not happen. What do they implement differently? How does Apple do it? There must be a solution to this problem.

run this in terminal with internet off: while true;do sudo -n uptime 2>/dev/null;echo "date($((i++)))";sleep 0.1;done now turn internet on (WIFI here). The log will happen now every 5s to 10s... How to make sudo ignore internet? Also, why it behaves like that? Obs.: ubuntu 22.04 PS.: I use sudo -n uptime to alert if the terminal has sudo access (I color it all in red). So I get that problem on every command I run in the terminal. a log with the delays when WIFI is ON:

Fri  5 Jan 00:07:41 -03 2024(0)
Fri  5 Jan 00:07:47 -03 2024(1)
Fri  5 Jan 00:07:52 -03 2024(2)
Fri  5 Jan 00:07:57 -03 2024(3)
Fri  5 Jan 00:07:57 -03 2024(4)
Fri  5 Jan 00:08:02 -03 2024(5)
Fri  5 Jan 00:08:02 -03 2024(6)
Fri  5 Jan 00:08:13 -03 2024(7)
Fri  5 Jan 00:08:18 -03 2024(8)
Fri  5 Jan 00:08:18 -03 2024(9)
Fri  5 Jan 00:08:23 -03 2024(10)
Fri  5 Jan 00:08:28 -03 2024(11)
Fri  5 Jan 00:08:28 -03 2024(12)
Fri  5 Jan 00:08:34 -03 2024(13)
Fri  5 Jan 00:08:39 -03 2024(14)
Fri  5 Jan 00:08:44 -03 2024(15)
Fri  5 Jan 00:08:44 -03 2024(16)

when WIFI is OFF:

Fri  5 Jan 00:11:45 -03 2024(21)
Fri  5 Jan 00:11:45 -03 2024(22)
Fri  5 Jan 00:11:46 -03 2024(23)
Fri  5 Jan 00:11:46 -03 2024(24)
Fri  5 Jan 00:11:46 -03 2024(25)
Fri  5 Jan 00:11:46 -03 2024(26)
Fri  5 Jan 00:11:46 -03 2024(27)
Fri  5 Jan 00:11:46 -03 2024(28)
Fri  5 Jan 00:11:46 -03 2024(29)
Fri  5 Jan 00:11:46 -03 2024(30)
Fri  5 Jan 00:11:47 -03 2024(31)
Fri  5 Jan 00:11:47 -03 2024(32)
Fri  5 Jan 00:11:47 -03 2024(33)
Fri  5 Jan 00:11:47 -03 2024(34)
Fri  5 Jan 00:11:47 -03 2024(35)
Fri  5 Jan 00:11:47 -03 2024(36)
Fri  5 Jan 00:11:47 -03 2024(37)
Fri  5 Jan 00:11:47 -03 2024(38)
Fri  5 Jan 00:11:47 -03 2024(39)
Fri  5 Jan 00:11:48 -03 2024(40)
Fri  5 Jan 00:11:48 -03 2024(41)
Fri  5 Jan 00:11:48 -03 2024(42)
Fri  5 Jan 00:11:48 -03 2024(43)
Fri  5 Jan 00:11:48 -03 2024(44)
Fri  5 Jan 00:11:48 -03 2024(45)
Fri  5 Jan 00:11:48 -03 2024(46)
Fri  5 Jan 00:11:48 -03 2024(47)
Fri  5 Jan 00:11:49 -03 2024(48)
Fri  5 Jan 00:11:49 -03 2024(49)
Fri  5 Jan 00:11:49 -03 2024(50)
Fri  5 Jan 00:11:49 -03 2024(51)
Fri  5 Jan 00:11:49 -03 2024(52)
Fri  5 Jan 00:11:49 -03 2024(53)
Fri  5 Jan 00:11:49 -03 2024(54)
Fri  5 Jan 00:11:49 -03 2024(55)
Fri  5 Jan 00:11:50 -03 2024(56)
Fri  5 Jan 00:11:50 -03 2024(57)
Fri  5 Jan 00:11:50 -03 2024(58)
Fri  5 Jan 00:11:50 -03 2024(59)
Fri  5 Jan 00:11:50 -03 2024(60)
Fri  5 Jan 00:11:50 -03 2024(61)
Fri  5 Jan 00:11:50 -03 2024(62)
Fri  5 Jan 00:11:50 -03 2024(63)
Fri  5 Jan 00:11:50 -03 2024(64)
Fri  5 Jan 00:11:51 -03 2024(65)
Fri  5 Jan 00:11:51 -03 2024(66)
Fri  5 Jan 00:11:51 -03 2024(67)
Fri  5 Jan 00:11:51 -03 2024(68)
Fri  5 Jan 00:11:51 -03 2024(69)
Fri  5 Jan 00:11:51 -03 2024(70)
Fri  5 Jan 00:11:51 -03 2024(71)
Fri  5 Jan 00:11:51 -03 2024(72)
Fri  5 Jan 00:11:52 -03 2024(73)
Fri  5 Jan 00:11:52 -03 2024(74)
Fri  5 Jan 00:11:52 -03 2024(75)
Fri  5 Jan 00:11:52 -03 2024(76)
Fri  5 Jan 00:11:52 -03 2024(77)
Fri  5 Jan 00:11:52 -03 2024(78)
Fri  5 Jan 00:11:52 -03 2024(79)
Fri  5 Jan 00:11:52 -03 2024(80)
Fri  5 Jan 00:11:52 -03 2024(81)
Fri  5 Jan 00:11:53 -03 2024(82)
Fri  5 Jan 00:11:53 -03 2024(83)
Fri  5 Jan 00:11:53 -03 2024(84)
Fri  5 Jan 00:11:53 -03 2024(85)
Fri  5 Jan 00:11:53 -03 2024(86)
Fri  5 Jan 00:11:53 -03 2024(87)
Fri  5 Jan 00:11:53 -03 2024(88)
Fri  5 Jan 00:11:53 -03 2024(89)
Fri  5 Jan 00:11:54 -03 2024(90)
Fri  5 Jan 00:11:54 -03 2024(91)
Fri  5 Jan 00:11:54 -03 2024(92)
Fri  5 Jan 00:11:54 -03 2024(93)
Fri  5 Jan 00:11:54 -03 2024(94)
Fri  5 Jan 00:11:54 -03 2024(95)
Fri  5 Jan 00:11:54 -03 2024(96)
Fri  5 Jan 00:11:54 -03 2024(97)
Fri  5 Jan 00:11:54 -03 2024(98)
Fri  5 Jan 00:11:55 -03 2024(99)

I'm using Ubuntu 22.04. While I'm moving huge dataset (over 200GB) from SSD to HDD, my PC becomes slow after around 1 hours later. At the same time I'm executing Deep learning program(it becomes stop after same hour). I checked CPU, RAM and IO but there are no problems. Some command works fast(ex ls) but others are not(ex apt). And also the reboot speed becomes extremely slow.

I installed this firmware-realtek frimware file in my debian os for my wifi driver. If I uninstall this firmware-realtek . then my pc works very fast. If I install firmware-realtek again my pc works very slowly. sudo apt-get install firmware-realtek Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'firmware-realtek' instead of './firmware- realtek_20190114-2~deb9u1_all.deb' The following NEW packages will be installed: firmware-realtek 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/506 kB of archives. After this operation, 1,602 kB of additional disk space will be used. Get:1 /home/simba/Downloads/firmware-realtek_20190114-2~deb9u1_all.deb firmware-realtek all 20190114-2~deb9u1 [506 kB] Selecting previously unselected package firmware-realtek. (Reading database ... 136550 files and directories currently installed.) Preparing to unpack .../firmware-realtek_20190114-2~deb9u1_all.deb ... Unpacking firmware-realtek (20190114-2~deb9u1) ... Setting up firmware-realtek (20190114-2~deb9u1) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.140) ... update-initramfs: Generating /boot/initrd.img-5.10.0-16-amd64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168fp-3.fw for module r8169 W: Possible missing firmware /lib/firmware/i915/skl_huc_2.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_huc_2.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_huc_4.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_huc_9.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_33.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_huc_9.0.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_33.0.4.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_35.2.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_35.2.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_dmc_ver1_07.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1_27.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_04.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_dmc_ver1_04.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cnl_dmc_ver1_07.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_dmc_ver1_09.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_08.bin for module i915 W: Possible missing firmware /lib/firmware/i915/rkl_dmc_ver2_02.bin for module i915 How can I solve this problem ?

The filesystem is ext4, the machine hasn't been rebooted in years and we don't want to do that now either. We used to have a folder with millions of small (2-3kb of size) files. This almost broke the system so we fixed the code that was generating so many files and wrote a crontask that erased all the files within the directory (because rm wasn't working) At first everything went smooth, you type ls and you got full list of the 4-5 remaining files. On the next day however when I typed ls the system took forever to execute the command (it took minutes) and the system load went over **20** which scared me a lot. It's basically like this for months now. The first time of the day when I do ls the system borderline slows to a crawl and eventually returns a list of ... 5 files and no subfolders. I believe it's some ext4 cache, I've tried running various commands to no avail. Is there anything else I could do to force ext4 to erase the cache. The system is running in RAID 1 mode. Running cat /proc/mdstat shows that both drives are fully functional and synchronized. smartctl says the drive is in good health as well. hdparm returns the following hdparm -tT /dev/sda1 /dev/sda1: Timing cached reads: 19238 MB in 2.00 seconds = 9629.50 MB/sec Timing buffered disk reads: 316 MB in 3.01 seconds = 104.92 MB/sec

I copied a 16 GB USB memory stick to another 16 GB stick (cloned it), by using the following command: cp /dev/sdb /dev/sdd It took about 27 minutes, and the cloning works. But during the entire copy process, the mouse and cursor movement become erratic, and lag terribly. This makes using the laptop during the copy almost impossible. This happened to me on a previous occasion, so the effect is reproduci ble. What causes this effect? How do I stop the erratic behaviour? Are you able to replicate the behaviour on your computer?

I would like to remove or delete or uninstall ALL the installed apps or applications or programs or softwares from Linux... My computer is slowing down because I have installed a lot of useless softwares and it would take a lot of time to remove them one after the other by sudo apt remove. Is it possible to remove them all at once. However, I do not want to remove the essential softwares like Firefox web browser, etc. How to remove and clean my linux computer?

After installing Fedora 33 (also tried kubuntu and ubuntu 20.04) on my laptop, I have the problem that after some time, the CPU randomly gets stuck at low frequency (400MHz-800Mhz) and doesn't step up resulting in very slow response times. cpupower command doesn't change the CPUs speed even it returns status code 0. I have tried disabling intel_pstate and thermald. Some system info: $ uname -a Linux localhost.localdomain 5.10.7-200.fc33.x86_64 #1 SMP Tue Jan 12 20:20:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/*release Fedora release 33 (Thirty Three) $ grep "model name" /proc/cpuinfo model name : Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz $ grep "cpu MHz" /proc/cpuinfo cpu MHz : 800.004 cpu MHz : 800.002 cpu MHz : 800.001 cpu MHz : 800.002 cpu MHz : 800.005 cpu MHz : 800.001 cpu MHz : 800.000 cpu MHz : 800.002

$ cpupower frequency-info
    analyzing CPU 0:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency:  Cannot determine or is not supported.
  hardware limits: 400 MHz - 4.90 GHz
  available cpufreq governors: performance powersave
  current policy: frequency should be within 400 MHz and 4.90 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 500 MHz (asserted by call to kernel)
  boost state support:
    Supported: yes
    Active: yes

There seems to be a pathological case with one of the files I'm reading with less. The file is ~300MB in size, disk is fast (local NMVE) and the file can comfortably fit in memory, there is no swapping or anything like that. less --version gives me

less 563 (PCRE regular expressions)

on Arch Linux. I run with no commandline parameters (no -R or -S). The file I am reading is being written to. **Usage:** I notice using follow (pressing F) is generally slow for this file, but workable. Things are made worse by having a search active (for highlighting) while follow is in progress. Now if I search for the following: (something|something-else).*|.*warn and then hit F (follow), it totally grinds to a halt. I need to kill it from a different terminal. I've been using such regexes with much larger files with no issue. Could something be amiss? **Edit**: more exact steps and info: - happens with 50MB file, no long lines - another process appends to the file every 15s Steps: - I open the file, go to end (Shift+g) - search for (something|something-else).*|.*warn (says Pattern not found since at the end) - follow (Shift+f) -> CPU goes to 100% and seemingly never stops - instead of pressing Shift+f, the same happens if I press UpArrow following the search - if I reduce the regex to one of its parts (either (something|something-else).* or .*warn the operations take a few seconds, still slow but manageable - resident memory shows as 400MB in htop - **Ctrl+C doesn't work to interrupt it, need to kill from outside**

I am using PopOS as my OS I noticed that it takes too long to boot-up the reason might be because I use a HDD but, when I was using ubuntu the boot time was faster So, I checked the boot time with

-analyze

command this was the result:

Startup finished in 3.998s (kernel) + 44.094s (userspace) = 48.093s 
graphical.target reached after 44.028s in userspace

then I checked which process makes it slow by using this

-analyze blame

command and this was the result:

29.893s plymouth-quit-wait.service          
 9.881s networkd-dispatcher.service         
 8.984s accounts-daemon.service             
 7.326s udisks2.service                     
 6.843s systemd-journal-flush.service       
 6.358s fwupd.service                       
 5.468s system76-power.service              
 4.872s polkit.service                      
 4.309s dev-sda3.device                     
 4.219s avahi-daemon.service                
 4.138s NetworkManager.service              
 4.123s switcheroo-control.service          
 4.119s thermald.service                    
 4.115s systemd-logind.service              
 4.115s wpa_supplicant.service              
 3.147s ModemManager.service                
 2.954s gdm.service                         
 2.694s gpu-manager.service                 
 2.662s grub-initrd-fallback.service        
 2.523s grub-common.service                 
 2.490s apport.service                      
 2.260s apparmor.service                    
 1.688s e2scrub_reap.service                
 1.612s systemd-resolved.service            
 1.561s lvm2-monitor.service                
 1.296s user@1000.service                   
 1.185s networking.service                  
 1.025s systemd-udevd.service               
  961ms rsyslog.service                     
  892ms systemd-modules-load.service        
  790ms systemd-cryptsetup@cryptswap.service
  724ms keyboard-setup.service              
  623ms systemd-sysusers.service            
  528ms systemd-udev-trigger.service        
  481ms systemd-random-seed.service         
  461ms systemd-rfkill.service              
  426ms colord.service                      
  401ms systemd-sysctl.service              
  333ms upower.service                      
  321ms systemd-tmpfiles-setup-dev.service  
  305ms systemd-tmpfiles-setup.service      
  277ms ifupdown-pre.service                
  257ms dev-mapper-cryptswap.swap           
  251ms ufw.service                         
  182ms systemd-journald.service            
  180ms systemd-user-sessions.service       
  174ms pppd-dns.service                    
  126ms systemd-remount-fs.service          
  104ms systemd-timesyncd.service           
   91ms dev-hugepages.mount                 
   90ms dev-mqueue.mount                    
   89ms sys-kernel-debug.mount              
   88ms sys-kernel-tracing.mount            
   87ms blk-availability.service            
   84ms kmod-static-nodes.service           
   64ms setvtrgb.service                    
   54ms console-setup.service               
   37ms user-runtime-dir@1000.service       
   35ms systemd-update-utmp.service         
   24ms rtkit-daemon.service                
   13ms plymouth-start.service              
   11ms plymouth-read-write.service         
    8ms alsa-restore.service                
    5ms systemd-update-utmp-runlevel.service
    5ms resolvconf-pull-resolved.service    
    3ms sys-fs-fuse-connections.mount       
    2ms sys-kernel-config.mount             
    1ms finalrd.service

-quit-wait.service

is in the top of this list with 29 sec time to finish... Please answer these questions 1. What it does? 2. If it's not necessary than how to disable it? 3. Is there any other unnecessary process in the list that I can remove if yes than how Thanks!

(Manjaro 20, Linux 5.8.3, KDE, [this laptop](https://geizhals.de/schenker-xmg-a507-vsy-10504411-a1686447.html)) When reasonably much is going on in my system, the RAM and swap usage often goes much higher than it should. For example currently I have a VM with a VM in it running and two instances of Minecraft, also some smaller stuff like music. That might sound like much, but my CPU is totally fine and even the sum of all the RAM usage shown in the task manager seems to be less than 2GB. Despite this, almost all of my 16GB RAM and 16GB swap are in use by… something. This is the output of free:

total        used        free      shared  buff/cache   available
Mem:          15898       15218         151         305         527          92
Swap:         17490       16442        1047

This much calmer picture is seen in the task manager:  I've read [here](https://unix.stackexchange.com/a/261329/216015) that sometimes virtualisation causes weird RAM issues, but my outer VM is restricted to 8GB. Even if it somehow used all of that without showing it in the task manager, it would still not explain about a quarter of my RAM usage and none of the swap usage. free shows that I should not blame caching (for once). I've heard that disk I/O that can't be done in time gets queued up in RAM, but iotop shows nothing overly active. This is also not just a measurement error, I do indeed get lag spikes in pretty much everything due to this. So quite a portion of memory of the programs I'm actively using is in swap. What uses this additional RAM and why so much of it?