You are not logged in.
here is cat and stat
❯ stat /home/jrgiacone/.local/share/Steam/steam.sh
File: /home/jrgiacone/.local/share/Steam/steam.sh
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: 259,8 Inode: 9448519 Links: 1
Access: (0755/-rwxr-xr-x) Uid: ( 1000/jrgiacone) Gid: ( 1000/jrgiacone)
Access: 2024-10-31 07:21:00.885946724 -0700
Modify: 2024-10-24 09:51:12.000000000 -0700
Change: 2024-10-27 16:22:17.243538429 -0700
Birth: 2024-10-27 16:22:16.986871769 -0700
~
❯ cat /home/jrgiacone/.local/share/Steam/steam.sh
~
❯
Offline
you'd see the string noexec in the mount options and you'd need to get rid of the noexec in your fstab or wherever it is you're mounting your /home
But if unsure post the outputs you get so we can check
doesnt look like it is noexec...
I updated today too same issues.
Offline
Update for everyone, I deleted steam.sh from the .local/share/steam folder, now steam could run steam --reset which cleared the folder and running steam made it re download all files/ re create all of them. Steam is up and running and fixed, note half the files in there showed zero. There must have been a corruption at some point or something caused it to reset. On ext4 so weird.... But yea Seth was super helpful the empty cat lead me down the path to check
Offline
hm, so the "sledgehammer windows method: wipe all but the binary and have it reconstruct its environment on its own" helped for once here ... interesting
Online
You'll want to check disk health, something like this shouldn't be normal... what output do you get from
sudo smartctl -a /dev/sdX #Replace with actual device node, install smartmontools if you haven't already
Offline
hm, so the "sledgehammer windows method: wipe all but the binary and have it reconstruct its environment on its own" helped for once here ... interesting
how does this look:
❯ sudo smartctl -a /dev/nvme1n1
[sudo] password for jrgiacone:
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.11.5-arch1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: WDS100T3X0C-00SJG0
Serial Number: 21033Y803083
Firmware Version: 111110WD
PCI Vendor/Subsystem ID: 0x15b7
IEEE OUI Identifier: 0x001b44
Total NVM Capacity: 1,000,204,886,016 [1.00 TB]
Unallocated NVM Capacity: 0
Controller ID: 8215
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 1,000,204,886,016 [1.00 TB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 001b44 8b488d91b0
Local Time is: Thu Oct 31 20:45:21 2024 PDT
Firmware Updates (0x14): 2 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x0e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size: 128 Pages
Warning Comp. Temp. Threshold: 84 Celsius
Critical Comp. Temp. Threshold: 88 Celsius
Namespace 1 Features (0x02): NA_Fields
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 6.00W - - 0 0 0 0 0 0
1 + 3.50W - - 1 1 1 1 0 0
2 + 3.00W - - 2 2 2 2 0 0
3 - 0.1000W - - 3 3 3 3 4000 10000
4 - 0.0025W - - 4 4 4 4 4000 40000
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 2
1 - 4096 0 1
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 32 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 0%
Data Units Read: 19,851,264 [10.1 TB]
Data Units Written: 19,779,299 [10.1 TB]
Host Read Commands: 132,162,514
Host Write Commands: 96,883,356
Controller Busy Time: 405
Power Cycles: 1,283
Power On Hours: 5,144
Unsafe Shutdowns: 43
Media and Data Integrity Errors: 0
Error Information Log Entries: 1
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Error Information (NVMe Log 0x01, 16 of 256 entries)
No Errors Logged
Read Self-test Log failed: Invalid Field in Command (0x4002)
Offline
The "sledgehammer" is always the only solution when dealing with file corruption
the empty cat lead me down the path to check
stat btw showed the same.
The disk doesn't look suspicious, the file corruption might be down to
* hard reboots
* overly aggressive https://wiki.archlinux.org/title/Solid_state_drive#TRIM or
* https://wiki.archlinux.org/title/Solid_ … ing_(APST)
Offline