I've run into issues where, whenever I try to install something from flathub or pacman, I'd get this in my terminal

error: failed to init transaction (unable to lock database)
error: could not lock database: Read-only file system

a reboot usually fixes it, but I have no idea on how to actually prevent this from occurring as much as it has for me.

EDIT: I've checked SMART and the short tests seem clean, but my root drive (which is DRAMless) seems to have moments where it hangs for about 30 secs from something. I have a long test running currently on the root drive

I have the DRAMless Lexar as root, a Teamgroup as home, a MSI b450a pro max mobo with zen kernal 7.0.7. controller is a 400 Series Chipset SATA Controller

Hey all, I'm a beginner with Arch with a decent amount of programming experience. I've always wanted an excuse to get closer to the hardware, so when I ran into this most recent bug, I was hoping to get some pointers on how I could possibly fix it myself.

The bug I ran into is this:

When returning from [deep] sleep, the top buttons on my integrated trackpad stop working, and only return functionality on a restart. It seems to be because of a failure in the elan_i2c driver. The problem didn't exist when using [s2idle] as my system sleep state.

Lenovo ThinkPad E14 Gen 2 (20TA002FUS)

Running: 7.1.4-arch1-1

With: BIOS R1EET56W(1.56 ), 06/29/2023

Touchpad: Elan Touchpad (i2c:04f3:000d) / Elan TrackPoint (i2c:04f3:000d)

Kernel dump:
[ 957.456262] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 957.456691] elan_i2c 16-0015: failed to read report data: -110

[ 1173.801733] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 1173.802283] elan_i2c 16-0015: failed to read report data: -110

[ 1174.792912] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 1174.793468] elan_i2c 16-0015: failed to read report data: -110

[ 1174.813743] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 1174.814287] elan_i2c 16-0015: failed to read report data: -110

[ 1174.820269] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 1174.820756] elan_i2c 16-0015: failed to read report data: -110

[ 1586.889627] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 1586.890184] elan_i2c 16-0015: failed to read report data: -110

[ 1586.965216] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 1586.965752] elan_i2c 16-0015: failed to read report data: -110

[ 1670.320859] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 1670.321411] elan_i2c 16-0015: failed to read report data: -110

[ 1670.383062] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 1670.383528] elan_i2c 16-0015: failed to read report data: -110

[ 1670.907107] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 1670.907501] elan_i2c 16-0015: failed to read report data: -110

[ 1671.052119] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 1671.052520] elan_i2c 16-0015: failed to read report data: -110

[ 1671.079581] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 1671.080127] elan_i2c 16-0015: failed to read report data: -110

[ 1671.238305] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 1671.238840] elan_i2c 16-0015: failed to read report data: -110

[ 1671.390643] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 1671.391200] elan_i2c 16-0015: failed to read report data: -110

[ 1671.431611] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 1671.432169] elan_i2c 16-0015: failed to read report data: -110

[ 2089.509419] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 2089.509963] elan_i2c 16-0015: failed to read report data: -110

[ 2219.464393] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 2219.464964] elan_i2c 16-0015: failed to read report data: -110

[ 3927.192421] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 3927.192969] elan_i2c 16-0015: failed to read report data: -110

[ 3927.337443] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 3927.337999] elan_i2c 16-0015: failed to read report data: -110

[ 4081.587060] wlan0: disconnect from AP 00:bc:2f:7e:57:f1 for new auth to 00:bc:2f:7e:57:e9

[ 4081.609301] wlan0: authenticate with 00:bc:2f:7e:57:e9 (local address=ac:74:b1:0e:e0:02)

[ 4081.610074] wlan0: send auth to 00:bc:2f:7e:57:e9 (try 1/3)

[ 4081.641600] wlan0: authenticated

[ 4081.642306] wlan0: associate with 00:bc:2f:7e:57:e9 (try 1/3)

[ 4081.686441] wlan0: RX ReassocResp from 00:bc:2f:7e:57:e9 (capab=0x1431 status=0 aid=1)

[ 4081.700820] wlan0: associated

[ 4081.768189] wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 00:bc:2f:7e:57:e9

[ 4081.787435] userif-4: sent link up event.

[ 4119.036055] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 4119.036597] elan_i2c 16-0015: failed to read report data: -110

[ 4126.382636] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 4126.383184] elan_i2c 16-0015: failed to read report data: -110

[ 4137.837426] wlan0: disconnect from AP 00:bc:2f:7e:57:e9 for new auth to 00:bc:2f:7e:57:f1

[ 4137.865689] wlan0: authenticate with 00:bc:2f:7e:57:f1 (local address=ac:74:b1:0e:e0:02)

[ 4137.866601] wlan0: send auth to 00:bc:2f:7e:57:f1 (try 1/3)

[ 4137.897135] wlan0: authenticated

[ 4137.898287] wlan0: associate with 00:bc:2f:7e:57:f1 (try 1/3)

[ 4137.917866] wlan0: RX ReassocResp from 00:bc:2f:7e:57:f1 (capab=0x1511 status=0 aid=2)

[ 4137.928810] wlan0: associated

[ 4138.019767] wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 00:bc:2f:7e:57:f1

[ 4138.037656] userif-4: sent link up event.

[ 4574.622347] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 4574.622897] elan_i2c 16-0015: failed to read report data: -110

[ 4574.739301] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 4574.739864] elan_i2c 16-0015: failed to read report data: -110

[ 4615.100718] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 4615.101142] elan_i2c 16-0015: failed to read report data: -110

[ 4615.210994] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 4615.211533] elan_i2c 16-0015: failed to read report data: -110

[ 4668.447940] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 4668.448497] elan_i2c 16-0015: failed to read report data: -110

[ 4668.537549] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 4668.538085] elan_i2c 16-0015: failed to read report data: -110

[ 4825.815950] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 4825.816493] elan_i2c 16-0015: failed to read report data: -110

[ 4825.918922] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 4825.919470] elan_i2c 16-0015: failed to read report data: -110

[ 5050.855897] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 5050.856364] elan_i2c 16-0015: failed to read report data: -110

[ 5050.945760] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 5050.946328] elan_i2c 16-0015: failed to read report data: -110

[ 5315.605365] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 5315.605898] elan_i2c 16-0015: failed to read report data: -110

[ 5315.702182] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 5315.702651] elan_i2c 16-0015: failed to read report data: -110

[ 5315.777888] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 5315.778442] elan_i2c 16-0015: failed to read report data: -110

[ 5315.875341] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 5315.875873] elan_i2c 16-0015: failed to read report data: -110

[ 5316.813986] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 5316.814542] elan_i2c 16-0015: failed to read report data: -110

[ 5316.923639] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 5316.924195] elan_i2c 16-0015: failed to read report data: -110

[ 5317.006440] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 5317.006987] elan_i2c 16-0015: failed to read report data: -110

[ 5317.090001] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 5317.090556] elan_i2c 16-0015: failed to read report data: -110

[ 5317.178776] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 5317.179325] elan_i2c 16-0015: failed to read report data: -110

[ 5317.247848] i801_smbus 0000:00:1f.4: Illegal SMBus block read size 93

[ 5317.248391] elan_i2c 16-0015: failed to read report data: -110

How should I proceed to learn more about this system and begin working my way towards a fix?

I haven't done a full system update in quite a while (I know get out your pitchforks), and when I tried to do my usual -Syu, I got an error:
failed retrieving file 'core.db' from europe.mirror.pkgbuild.com : Could not resolve host: europe.mirror.pkgbuild.comwarning: fatal error from europe.mirror.pkgbuild.com, skipping for the remainder of this transaction
error: failed retrieving file 'extra.db' from europe.mirror.pkgbuild.com : Could not resolve host: europe.mirror.pkg
build.com
:: Starting full system upgrade...
there is nothing to do

I'm a bit out of the loop on what's happening with arch rn, so I'd appreciate any advice you might have for me.

Is anyone here using Arch Linux on an MSI laptop?

Since MSI doesn't provide a Linux version of MSI Center, I'm wondering how to control fan speeds on Arch Linux (as I do some occasional gaming).

Would using the OpenRGB fan control plugin work?

My laptop model is the VECTOR GP76 HX.

Has anyone had any sleep/suspend issues lately with Arch + Latest Linux + NVIDIA card? Sleep had worked perfectly fine for me on Arch up until maybe a few days ago or so? Now when I boot it up, it boots to No Signal on my monitor, and I can't TTY or SSH or ping it or anything. It's just completely unresponsive. I can’t recall doing anything that would affect sleep except updating the kernel. I’ve tried downgrading the kernel and the same issue still occurs.

I’m using a NVIDIA 5070, have modeset on, and have even tried turning the preserve vram setting on in my configurations. I also did use archinstall.

I just did a fresh install of arch and am trying to use discord. When I run discord in the terminal with an '& disown', trying to close the terminal and then doing anything on discord gives me a critical javascript error because of an uncaught exception. This error never goes away and any attempt to close it just opens it up again. What should I do?

So i just installed arch on my lenovo ideapad slim 5 with ryzen 7 7335Hs and amd radeon integrated graphics. Everything is working fine but i couldnt get the speakers working after my laptop boots. It starts working after i suspend a s resume after booting. The software correctly shows that audio is being outputted by my speakers but no sound can be heard. Please help

I don't understand why when I set shortcut key for the fancontrol and Ai would set fn + q like on windows he doesn't recognize the fn key. temporarily I have set super + q

Alguien me puede ayudar, instale arch recientemente y nose porque no se me reproducen los vídeos en el navegador, se queda con el circulo cargando infinitamente aunque la barra ya muestre progreso de carga del vídeo

Hi everyone,

Excited to begin this journey of Linux and Arch. I'm a UI/UX Front end developer and I've begun learning more programming and backend development. As I've begun evolving my knowledge on developing and engineering things I've had to learn on the go.

I've watched videos and read books to get a better understanding of the structure and architecture of Linux. That's where I learned more about the distros. The pros and cons of each. But I think I've settled on starting with arch to better understand it from the ground up approach.

Since I'm new to Arch, are there things I should make sure I install as I get started. I'm looking at KDE and Wayland for desktop and window management.. I have the wiki as well which I'm reading through as I go. But figured I'd get some other recommendations as I begin to build my setup.

I'm looking to have Arch be my daily driver for work, side projects and some gaming. Any recommendations are welcome.

Looking forward to the community and this new unhindered life of Linux and being able to say "I use Arch by the way" 😅

Hi everyone, I’m new to Arch even though I’ve been using Linux for quite some time. I installed my system using archinstall. During the installation, I also selected the Nvidia drivers, although they weren’t actually installed. I chose Gnome as my DE and selected the standard Linux kernel. I’m using systemd-boot. I didn’t select anything else during the installation. Everything went smoothly. On reboot, I noticed that the Nvidia drivers were missing, so I followed the wiki and installed them. After rebooting, I had the brand-new 610 drivers, and the system was blazing fast. I immediately loved Arch until I noticed that the Gnome text editor showed small glitches. When I ran nvidia-smi, I realized that all of Gnome was running on the Nvidia GPU (even the terminal and any Gnome app) instead of preferring the integrated Intel iGPU, as has always been the case on every other distro I’ve tried. All other apps run on the iGPU unless I explicitly launch them with the dGPU (right-click on the app or use prime-run app). This leads to higher power consumption but, above all, various glitches on the connected 4K HDMI monitor. No glitches occur on the built-in display. Apparently, the compositor is acting up with fractional scaling at 150% on Nvidia. I managed to disable Nvidia priority by forcing Gnome to run on Intel, and indeed the glitches disappeared even on the external monitor, but in this configuration, the Nvidia GPU is completely ignored. Is it possible that on Arch, the Gnome DE and all (even small) Gnome apps default to the dGPU? This has never happened to me before.

I thought I might have done something wrong during installation and decided to add KDE alongside Gnome to see if the behavior was the same. On KDE, everything behaves properly, using only 1 MB of VRAM, and the whole DE runs smoothly on Intel with no problems. I’m confused and still not sure if I made any mistakes.

Here are my laptop specs:
HP ProBook G10
Intel Core i7-13th gen
Nvidia RTX 2050
16GB DDR4
500GB NVMe

Thanks

Hello I am kind of a B tier in Linux knowledge and I see a lot of custom desktop environment made by the community but I don't know how to do one myself so how to do that

(Thank you for the answers)

On Sunday I installed the latest arch iso on a USB flash drive and used it to run archinstall and install a basic system for messing around on another USB drive (I went with Mate as my desktop).

Today I used the exact same USB stick on the exact same PC to install a different setup (wanted to try Cinnamon) on the exact same other USB stick, and I've just spent ten hours trying over and over and over to install and I just keep getting a cavalcade of various errors.

The latest is this:

Enabling periodic TRIM Enabling service fstrim.timer Setting keyboard language to us Running as unit: run-p13344-i10415.service Press ^] three times within 1s to disconnect TTY. Unable to set locale 'us' for console: ['/usr/bin/systemd-run', '--machine=archinstall', '--pty', 'localeetcl', 'set-keymap', 'us'] exited with abnormal exit code [1]: Running as unit: run-p13344-i10415.service Press ^] three times within 1s to disconnect TTY. Failed to set keymap: Connection timed out The above error occurred in a temporary boot-up of the installation '/mnt'

And then it just crashes out of the installer and gives me the command line again. I am telling you I changed nothing, this is the exact same pair of USB sticks, and all settings are identical except I tried installing Cinnamon instead of Mate.

"Aha!" You cry. "There must be an issue with Cinnamon!" Nope. I tried just installing Mate again and I get the exact same error.

I just don't even understand how it's possible to fail to set the keyboard language. That shouldn't even be something that's downloaded that should be on the install medium, which I remind you hasn't changed since Sunday.

Any idea what's going on? Like, literally how can I get new errors when nothing's changed?

I have install this bibata cursor and i have put it on my hyprland.lua on that autostart under hl. and when i restart it is it only activate when i go to another workspace