MX Linux Forum

Posted: **Sun Apr 20, 2025 6:27 am**

ive been lurking on the forums for a few weeks already, so hi again to everybody and thanks for creating and supporting this fine distribution :-)
my last post got quite convoluted, so here is my first serious thread/question:

description:
the problem i think is with the root account which i didnt enable at install.so i had a system which doesnt require password for root account and uses first user as administrator/superuser. this worked quite well until i got locked out after a kernel change with mx package installer. i have still no idea why that happens but the internet says its quite common and timeshift saved the day. the issue is described here for fedora, but its the same thing:

https://docs.fedoraproject.org/en-US/qu ... nt-locked/

i got advised by a forum member here to enable root account on my system to prevent this from happening in the future - which made sense to me.

PROBLEM: after setting a password for root in the mx user manager (administration>change user password) i cant boot into KDE gui anymore. at boot time, after GRUB menu it says:
starting initscrip for SDDM: sddmerror=unexpectedly disconnected from boot status daemon..tlp sysstat failed.
stopping VMWare services, starting VMWARE services
startpar services returned failure: tlp sysstat failed
"welcome to mxlinux: powered by debian": now i can login as root with the new set password, but i dont know how to start KDE.
"systemctl enable sddm" or "dpkg-reconfigure sddm" doesnt work
kernel 6.13.8.1, if that matters, sorry i cant make a proper copy paste or screenshot without GUI.
timeshift doesnt work, neither does changing kernel in advanced grub menu.
i booted from a different SSD, tried to look at the home folder of the described installation but it shows empty in dolphin and i cant access any files although it has over 300GB. ownership of the home folder is "root" so i guess i could access it when i will be able boot into KDE again?!
any ideas how to fix this would be highly appreciated...

Posted: **Sun Apr 20, 2025 6:42 am**

According to the forum rules (please read): Please provide full Quick System Info from the menu, use copy for forum button, no edits.
LiveUSB version is OK if needed.

Posted: **Sun Apr 20, 2025 7:01 am**

MX Linux 23.5, KDE 5.27.5, Frameworks 5.103.0, Qt 5.15.8, X11

how should i "provide full Quick System Info from the menu" when im stuck at boot?

cpu is intel 9600K, asrock Z390 MOBO, 32GB RAM. doesnt really matter i guess, as this problem is clearly in general from enabling root account on a running MX-system that had no enabled root account at install. it happens directly after reboot.

Posted: **Sun Apr 20, 2025 7:15 am**

samegold wrote: Sun Apr 20, 2025 7:01 am MX Linux 23.5, KDE 5.27.5, Frameworks 5.103.0, Qt 5.15.8, X11

how should i "provide full Quick System Info from the menu" when im stuck at boot?

From a live session?

Posted: **Sun Apr 20, 2025 7:21 am**

Let me repost:

According to the forum rules (please read): Please provide full Quick System Info from the menu, use copy for forum button, no edits.
LiveUSB version is OK if needed.

Posted: **Sun Apr 20, 2025 7:21 am**

j2mcgreg wrote: Sun Apr 20, 2025 7:15 am
samegold wrote: Sun Apr 20, 2025 7:01 am MX Linux 23.5, KDE 5.27.5, Frameworks 5.103.0, Qt 5.15.8, X11

how should i "provide full Quick System Info from the menu" when im stuck at boot?
From a live session?

if the live session is running from an usb stick, how should i read out the software that is installed on the SSD that doesnt boot? wouldnt the live-usb show the software versions of the live-system?

Posted: **Sun Apr 20, 2025 7:31 am**

It tells us about your system, so we can better help you.

Posted: **Sun Apr 20, 2025 7:38 am**

Eadwine Rose wrote: Sun Apr 20, 2025 7:31 am It tells us about your system, so we can better help you.

thanks, i understand that, but wouldnt the live-usb-info show the software versions of the live-USB-system instead of the not-booting system?

Posted: **Sun Apr 20, 2025 8:02 am**

@samegold wrote:

thanks, i understand that, but wouldnt the live-usb-info show the software versions of the live-USB-system instead of the not-booting system?

We are not at the software stage yet. We need to be able to eliminate your hardware components as points of failure first. The QSI is the best way for you to deliver that information to us. As it stands, it's like you've called a mechanic to fix your car but you refuse to give him / her the make and model or have a look under the hood.

Posted: **Sun Apr 20, 2025 8:27 am**

j2mcgreg wrote: Sun Apr 20, 2025 8:02 am @samegold wrote:
thanks, i understand that, but wouldnt the live-usb-info show the software versions of the live-USB-system instead of the not-booting system?
We are not at the software stage yet. We need to be able to eliminate your hardware components as points of failure first. The QSI is the best way for you to deliver that information to us. As it stands, it's like you've called a mechanic to fix your car but you refuse to give him / her the make and model or have a look under the hood.

ive already posted the hardware specs above, what else do you need? the hardware has nothing to do with it as it runs fine and i run linux from it right now from a different SSD and the problem only occurs when enabling root on MX.
so again: how does the usb-live system know what software is running on the failed SSD? to me you seem like a mechanic that wants to know the exact model of the car stereo when someone complains about a flat-tire.

Posted: **Sun Apr 20, 2025 8:37 am**

OK.. it is in the forum rules, if you don't post them we can't help you.

Posted: **Sun Apr 20, 2025 8:54 am**

Eadwine Rose wrote: Sun Apr 20, 2025 8:37 am OK.. it is in the forum rules, if you don't post them we can't help you.

i dont think you could either way, so dont bother. maybe someone else will :-)

Posted: **Sun Apr 20, 2025 9:19 am**

samegold wrote: Sun Apr 20, 2025 8:54 am
Eadwine Rose wrote: Sun Apr 20, 2025 8:37 am OK.. it is in the forum rules, if you don't post them we can't help you.
i dont think you could either way, so dont bother. maybe someone else will :-)

@samegold No-ones going to help until you cooperate with the request. We aren't going to play 20 questions, when we can quickly look at the output of your QSI.

Boot up the live ISO , like you were told to do, and post the QSI from there. It will give us a starting point.

Posted: **Sun Apr 20, 2025 1:39 pm**

siamhie wrote: Sun Apr 20, 2025 9:19 am
samegold wrote: Sun Apr 20, 2025 8:54 am
Eadwine Rose wrote: Sun Apr 20, 2025 8:37 am OK.. it is in the forum rules, if you don't post them we can't help you.
i dont think you could either way, so dont bother. maybe someone else will :-)
@samegold No-ones going to help until you cooperate with the request. We aren't going to play 20 questions, when we can quickly look at the output of your QSI.

soo, are you going to delete all potential answers on the topic or is that just a figure of speech and/or your personal opinion?
please let me know, just in case, so i dont have to waste our time here.
because - no offense - my opinion is, if someone is going to ask 20 questions about my HARDWARE with a problem clearly related to SOFTWARE, then he has no idea what hes talking about and cant help anyone anyway.
i also asked 3 times already if the QSI can read software infos from external SSD/system or just from its own partition - still no answer - instead orders.
communication could be better on this forum IMO. heres a screenshot in case somebody is interested in the actual problem:

https://ibb.co/wN1x1hXX

INIT: version 3.06 booting
INIT: No inittab.d directory found
Using makefile-style concurrent boot in runlevel S.
Starting hotplug events dispatcher: systemd-udevd.
Synthesizing the initial hotplug events (subsystems)...done.
Synthesizing the initial hotplug events (devices)...done.
Waiting for /dev to be fully populated...done.
Starting Init script for Simple Desktop Display Manager: sddmerror: unexpectedly disconnected

Starting Common Unix Printing System: cupsd.
Starting S.M.A.R.T. daemon: smartd.
Starting virtual private network daemon:
Stopping VMware services:
VMware Authentication Daemon done
Virtual machine monitor done
Starting VMware services:
Virtual machine monitor done
Virtual machine communication interface done
VM communication interface socket family done
Virtual ethernet failed
VMware Authentication Daemon done
startpar: service(s) returned failure: tlp system start ... **failed!**

Welcome to MX Linux! Powered by Debian.
mx login: root
Password:
Last login: Sun Apr 20 20:08:23 CEST 2025 on tty1
root@mx:~#

Posted: **Sun Apr 20, 2025 3:33 pm**

samegold wrote: Sun Apr 20, 2025 1:39 pm please let me know, just in case, so i dont have to waste our time here.
because - no offense - my opinion is, if someone is going to ask 20 questions about my HARDWARE with a problem clearly related to SOFTWARE, then he has no idea what hes talking about

For someone who's been lurking on the forum for a few weeks, it sure seems like you haven't been paying attention.

Posted: **Sun Apr 20, 2025 4:02 pm**

samegold wrote: Sun Apr 20, 2025 1:39 pm i also asked 3 times already if the QSI can read software infos from external SSD/system or just from its own partition - still no answer - instead orders.
communication could be better on this forum IMO.

Communication has been quite clear up to this point.

if the QSI can read software infos from external SSD/system

Yes. Here is my QSI showing my USB attached NVMe drive that I store data on. It is listed as SDC under Drives:

Code: Select all

Snapshot created on: 20250411_1148
System:
  Kernel: 6.12.23-x64v3-xanmod1 arch: x86_64 bits: 64 compiler: gcc v: 14.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.23-x64v3-xanmod1 root=UUID=<filter> ro
    init=/lib/systemd/systemd
  Desktop: Fluxbox v: 1.3.7 vt: 7 dm: LightDM v: 1.32.0 Distro: MX-23.6_fluxbox_x64 Libretto
    September 15 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop Mobo: Micro-Star model: B550-A PRO (MS-7C56) v: 2.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: A.F0 date: 10/11/2023
CPU:
  Info: model: AMD Ryzen 9 5950X bits: 64 type: MT MCP arch: Zen 3+ gen: 4 level: v3 note: check
    built: 2022 process: TSMC n6 (7nm) family: 0x19 (25) model-id: 0x21 (33) stepping: 2
    microcode: 0xA20120E
  Topology: cpus: 1x cores: 16 tpc: 2 threads: 32 smt: enabled cache: L1: 1024 KiB desc: d-16x32
    KiB; i-16x32 KiB L2: 8 MiB desc: 16x512 KiB L3: 64 MiB desc: 2x32 MiB
  Speed (MHz): avg: 906 high: 3400 min/max: 550/5084 boost: disabled scaling:
    driver: amd-pstate-epp governor: performance cores: 1: 550 2: 550 3: 550 4: 550 5: 550 6: 550
    7: 550 8: 550 9: 550 10: 550 11: 550 12: 3400 13: 550 14: 3397 15: 550 16: 550 17: 550 18: 550
    19: 550 20: 550 21: 550 22: 550 23: 550 24: 550 25: 550 26: 3397 27: 550 28: 550 29: 3398
    30: 550 31: 550 32: 550 bogomips: 217598
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: always-on; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] vendor: Tul / PowerColor
    driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie:
    gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-3 empty: DP-1, DP-2, HDMI-A-1, Writeback-1
    bus-ID: 0b:00.0 chip-ID: 1002:73df class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: amdgpu unloaded: fbdev dri: radeonsi
    gpu: amdgpu display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00") s-diag: 777mm (30.58")
  Monitor-1: DP-3 mapped: DisplayPort-2 model: HP X27q serial: <filter> built: 2021
    res: 2560x1440 dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9
    modes: max: 2560x1440 min: 720x400
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon RX 6700 XT (navi22 LLVM 15.0.6 DRM 3.61
    6.12.23-x64v3-xanmod1) direct-render: Yes
Audio:
  Device-1: Creative Labs CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series BlasterX AE-5 Plus]
    driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 05:00.0
    chip-ID: 1102:0012 class-ID: 0403
  Device-2: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: 0b:00.1 chip-ID: 1002:ab28 class-ID: 0403
  API: ALSA v: k6.12.23-x64v3-xanmod1 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Message: No PCI device data found.
  Device-1: NetGear Wireless_Device type: USB driver: mt7921u bus-ID: 4-1:2 chip-ID: 0846:9060
    class-ID: 0000 serial: <filter>
  IF: wlan0 state: up mac: <filter>
Drives:
  Local Storage: total: 8.41 TiB used: 1.31 TiB (15.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Western Digital model: WDS500G1X0E-00AFY0
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 613000WD temp: 36.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: SanDisk model: ST8000DM004-2CX188 size: 7.28 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5425 serial: <filter>
    rev: 0001 scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1B6Q
    scheme: GPT
  ID-4: /dev/sdc maj-min: 8:32 type: USB vendor: Samsung model: SSD 970 EVO size: 232.89 GiB
    block-size: physical: 4096 B logical: 512 B type: SSD serial: <filter> rev: 5102 scheme: MBR
Partition:
  ID-1: / raw-size: 465 GiB size: 456.63 GiB (98.20%) used: 11.89 GiB (2.6%) fs: ext4
    dev: /dev/nvme0n1p2 maj-min: 259:5
  ID-2: /boot/efi raw-size: 779 MiB size: 777.5 MiB (99.80%) used: 28 MiB (3.6%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:3
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 50 (default 100)
  ID-1: swap-1 type: partition size: 64 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdb2
    maj-min: 8:18
Sensors:
  System Temperatures: cpu: 30.9 C mobo: N/A gpu: amdgpu temp: 32.0 C mem: 30.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 710
Repos:
  Packages: pm: dpkg pkgs: 2338 libs: 1254 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://la.mxrepo.com/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/nordvpn.list
    1: deb https://repo.nordvpn.com/deb/nordvpn/debian stable main
  Active apt repos in: /etc/apt/sources.list.d/xanmod-release.list
    1: deb [signed-by=/etc/apt/keyrings/xanmod-archive-keyring.gpg] http://deb.xanmod.org releases main
  Active apt repos in: /etc/apt/sources.list.d/extrepo_librewolf.sources
    1: deb [arch=amd64 arm64] https://repo.librewolf.net librewolf main
Info:
  Processes: 506 Uptime: 22h 55m wakeups: 0 Memory: 31.26 GiB used: 2.76 GiB (8.8%) Init: systemd
  v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Posted: **Mon Apr 21, 2025 3:52 am**

if i access the home folder of the said installation from another linux PC i get this. its the locked home folder of the described system with the new root user that doesnt start KDE. it doesnt show the size of the folder.
i have the root passwort ofcourse, how can i unlock the home folder permanently, so i can access the files and maybe fix the bootup in the process? i would need to give back permissions to the first user, which is/was configured in KDE autologin and that would fix the KDE starting problem maybe? so basically disable the root account and go back how it was before.
i am using dolphin file manager.

https://i.postimg.cc/9FfgbtBJ/screen-HOMEfolder.png

Posted: **Mon Apr 21, 2025 4:42 am**

Image changed to link, you would have known this if you had read the forum rules.

Posted: **Mon Apr 21, 2025 10:55 am**

samegold wrote: Mon Apr 21, 2025 3:52 am if i access the home folder of the said installation from another linux PC i get this.

Post your QSI from the live ISO please. Like I said in post #13, We aren't going to play 20 questions.

Posted: **Mon Apr 21, 2025 7:03 pm**

if the QSI can read software infos from external SSD/system

"Yes. Here is my QSI showing my USB attached NVMe drive that I store data on. It is listed as SDC under Drives:"

that is not what i asked. it shows HARDWARE infos like vendor name, size, etc. which you can get probably in any OS by right-clicking on the hardware "properties".
SOFTWARE infos are for example: which OS version is installed on the SSD,which kernel, if any? and that is what matters.

thats why i asked:
"if the live session is running from an usb stick, how should i read out the software that is installed on the SSD that doesnt boot? wouldnt the live-usb show the software versions of the live-system?"

so im trying to explain this for the fifth time now and i dont know how to be any clearer, thanks for your reply though.

Posted: **Mon Apr 21, 2025 7:56 pm**

@samegold When you get to a command line, enter

startx

and do you get error messages there or does the GUI start ?

Posted: **Mon Apr 21, 2025 8:28 pm**

CharlesV wrote: Mon Apr 21, 2025 7:56 pm @samegold When you get to a command line, enter

startx

and do you get error messages there or does the GUI start ?

no it doesnt.

i get this:

https://ibb.co/TMy5Qmws

so right now im concentrating on "unlocking" the homefolder of the broken install by accessing it from a different linux machine. i hope i can atleast save some data that way:

https://postimg.cc/MX5r96Bd

it shows 0bytes, even though its over 300GB. so i think i need to take ownership of my own home folder, which is not trivial. all that happened because i assigned a password for root in mx user manager...
internet access is there but its also impossible to install anything at that stage as it says disk is full, even though there is still 20gb left...

Posted: **Mon Apr 21, 2025 8:35 pm**

samegold wrote: Sun Apr 20, 2025 6:27 am i got locked out after a kernel change with mx package installer.

Let's try this. Do you still get a grub menu? If so, select Advanced Options and boot to the previous working kernel.

Posted: **Mon Apr 21, 2025 8:40 pm**

samegold wrote: Mon Apr 21, 2025 8:28 pm
CharlesV wrote: Mon Apr 21, 2025 7:56 pm @samegold When you get to a command line, enter

startx

and do you get error messages there or does the GUI start ?
no it doesnt.

i get this:

https://ibb.co/TMy5Qmws

so right now im concentrating on "unlocking" the homefolder of the broken install by accessing it from a different linux machine. i hope i can atleast save some data that way:

https://postimg.cc/MX5r96Bd

it shows 0bytes, even though its over 300GB. so i think i need to take ownership of my own home folder, which is not trivial. all that happened because i assigned a password for root in mx user manager...
internet access is there but its also impossible to install anything at that stage as it says disk is full, even though there is still 20gb left...
file system is btfrs, if that matters.

Posted: **Mon Apr 21, 2025 8:52 pm**

i tried to select other kernel in grub ofcourse, i get something like:
modprobe fatal module vmmon not found in directory /lib/modules/*kernelversion*
failure: tlpsysstat failed.

filesystem is btfrs

i think it must be something about the root user not being configured in the autologin of KDE, as i had the first user configured as autologin.
but rightnow i just want to access the data in the locked homefolder, i dont care about the installation so much, i installed mx and other distros many times already , so i will do it again, no big deal.
timeshift also doesnt work.
edit: sorry for doublepost, you can delete the above post with the quotes.

Posted: **Mon Apr 21, 2025 10:03 pm**

Post the QSI from the live USB drive. That will show how the partitions are set up.

Posted: **Tue Apr 22, 2025 2:09 am**

Code: Select all

Drives:
  Local Storage: total: 1.36 TiB used: 1.05 TiB (77.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Corsair model: Force MP510 size: 447.13 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: ECFM12.3 temp: 34.9 C scheme: MBR
  ID-2: /dev/sda maj-min: 8:0 vendor: SanDisk model: SSDPR-CX400-512-G2 size: 476.94 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61.5
    scheme: MBR
  ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q
    scheme: GPT
Partition:
  ID-1: / raw-size: 400.39 GiB size: 393.03 GiB (98.16%) used: 312.95 GiB (79.6%) fs: ext4
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 6 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap

its "ID-3: /dev/sdb"

so is it "normal" that a folder shows size/size on disk "0 B" in a file manager?
if i run "properties" on ALL folders on that disk i get "size 22GB", but the "free space is 21GB of 410GB".
so, im not a mathematician, but that seems like BS. theres obviously over 300GB missing, and thats the 300 something GB of the home folder.

Posted: **Tue Apr 22, 2025 8:00 am**

@samegold
I think that the fact that Linux uses GiB as a memory measurement unit rather than GB which is used by Microsoft and all the manufacturers may have confused you. Read this for a good explanation:
https://massive.io/file-transfer/gb-vs- ... ifference/

Posted: **Tue Apr 22, 2025 9:18 am**

samegold wrote: Tue Apr 22, 2025 2:09 am
its "ID-3: /dev/sdb"

so is it "normal" that a folder shows size/size on disk "0 B" in a file manager?

What does this show in a terminal?

Code: Select all

lsblk --fs | grep -v loop

p.s. next time post the full QSI output and not a trimmed or edited version.

Posted: **Tue Apr 22, 2025 11:26 am**

samegold wrote: Sun Apr 20, 2025 6:27 am the problem i think is with the root account which i didnt enable at install.so i had a system which doesnt require password for root account and uses first user as administrator/superuser. this worked quite well until i got locked out after a kernel change with mx package installer. i have still no idea why that happens but the internet says its quite common and timeshift saved the day. the issue is described here for fedora, but its the same thing:

Don't thing changing the password of the root-account is the cause of the issue.
I guess rather somehow is related to the first issue mentioned with the other thread, where you suddenly have been forced
to enter into "Maintanaince mode", which you couldn't do without a root password.
So giving blind advises without analyzing the cause of the issue may not help or maybe misleading.

Also note: Using the term "Home" folder is potentially misleading (and confusing) by it's own,
b/c you can call "/home" directory a "Home folder", but you can also call "/home/samegold" the Home folder f the user "samegold".
And note also the, "/home" directory is properly owned by root but readable by all users, in oder they have access to
the subfolders to find their "home". And further root's "Home folder is not under /home but is "/root".
And yes, trying to GUI-login or autologin as root may not work. KDE will probably not work under root-account.

Posted: **Tue Apr 22, 2025 12:27 pm**

Share the full QSI so we can better see what is going on with your system.

And be glad people have been willing to help you this far.

Posted: **Wed Apr 23, 2025 11:14 am**

fehlix wrote: Tue Apr 22, 2025 11:26 am
Don't thing changing the password of the root-account is the cause of the issue.
I guess rather somehow is related to the first issue mentioned with the other thread, where you suddenly have been forced
to enter into "Maintanaince mode", which you couldn't do without a root password.

sorry, i dont know what you mean. that never happened. all i did was switching kernels, but that was a long time before the problem happened. i got the idea from you that enabling root would be a good thing, so i gave root a password in mx-user manager, clicked apply, and thats it. after reboot no more KDE, no more access to home-folder.

fehlix wrote: Tue Apr 22, 2025 11:26 am So giving blind advises without analyzing the cause of the issue may not help or maybe misleading.

sure, but better misleading than nothing i guess, since sometimes it cant really get worse. also nobody is stopping you from analyzing the cause, thats what the forum is for (supposedly). except of course you dont want to, which is fair enough :-)

fehlix wrote: Tue Apr 22, 2025 11:26 am Also note: Using the term "Home" folder is potentially misleading (and confusing) by it's own,
b/c you can call "/home" directory a "Home folder", but you can also call "/home/samegold" the Home folder f the user "samegold".
And note also the, "/home" directory is properly owned by root but readable by all users, in oder they have access to
the subfolders to find their "home". And further root's "Home folder is not under /home but is "/root".
And yes, trying to GUI-login or autologin as root may not work. KDE will probably not work under root-account.

yes, my wording may be not precise, im still working on it :-) but i thought in this context it was clear that i mean the home folder that contains /downloads /pictures /documents, etc...

Posted: **Wed Apr 23, 2025 11:54 am**

samegold wrote: Wed Apr 23, 2025 11:14 am sure, but better misleading than nothing i guess

When troubleshooting a problem, aim for as much clarity as you can. As How to Report Bugs Effectively says, "If the programmer can't tell what you meant, you might as well not have said anything."

Posted: **Wed Apr 23, 2025 12:11 pm**

samegold wrote: Wed Apr 23, 2025 11:14 am
fehlix wrote: Tue Apr 22, 2025 11:26 am So giving blind advises without analyzing the cause of the issue may not help or maybe misleading.
sure, but better misleading than nothing i guess, since sometimes it cant really get worse. also nobody is stopping you from analyzing the cause, thats what the forum is for (supposedly). except of course you dont want to, which is fair enough :-)

It goes both ways. You have been asked multiple times to post your QSI (in full), yet here we are on page four still scratching our heads.

Posted: **Wed Apr 23, 2025 12:45 pm**

j2mcgreg wrote: Tue Apr 22, 2025 8:00 am @samegold
I think that the fact that Linux uses GiB as a memory measurement unit rather than GB which is used by Microsoft and all the manufacturers may have confused you. Read this for a good explanation:
https://massive.io/file-transfer/gb-vs- ... ifference/

no, it didnt "confuse" me, since it has absolutely nothing to do with the topic and the difference is marginal.
i was trying to point out that the home folder shows "0 Byte" in the properties tab of any filemanager, while in reality it has over 300GB.
df -h:
/dev/sdc1 411G 389G 22G 95% /media/sam/Samsung870@500GB

DukeComposed wrote: Wed Apr 23, 2025 11:54 am
samegold wrote: Wed Apr 23, 2025 11:14 am sure, but better misleading than nothing i guess
When troubleshooting a problem, aim for as much clarity as you can. As How to Report Bugs Effectively says, "If the programmer can't tell what you meant, you might as well not have said anything."

your link is a nice textwall. are you a mason?
edit: updated my avatar to better fit in, hope you like it ;-)

siamhie wrote: Wed Apr 23, 2025 12:11 pm
It goes both ways. You have been asked multiple times to post your QSI (in full), yet here we are on page four still scratching our heads.

and i already asked 5 times: "wouldnt the live-usb-info show the software versions of the live-USB-system instead of the not-booting system?"
and yet you choose to ignore that 5 times, why is that?

Posted: **Wed Apr 23, 2025 12:49 pm**

I am issuing a warning. You have been asked multiple times to provide the info that is required to be shared when you ask for help, as per the forum rules, which you agreed with as soon as you started posting.

Posted: **Wed Apr 23, 2025 1:01 pm**

Eadwine Rose wrote: Wed Apr 23, 2025 12:49 pm I am issuing a warning. You have been asked multiple times to provide the info that is required to be shared when you ask for help, as per the forum rules, which you agreed with as soon as you started posting.

some people say its strange that the QSI that you are so aggressively asking for, even if its irrelevant, has a "Vulnerabilities" section, where all the CPU-mitigations are listed.
seems weird that you cant explain what you would need that for and ignore all relating questions and react aggressively. isnt that a security risk? hmmm...

i mean, its not like you are collecting hardware information from your users, are you?
im gonna save this thread, just in case it gets deleted because of a "technical error" or something ;-)

Posted: **Wed Apr 23, 2025 1:33 pm**

@samegold, why are you being so antagonizing in so many of your posts, slipping in snide remarks to people who respond? It comes off as strange and rude, and a weird thing to do if in actual need of help.

Posted: **Wed Apr 23, 2025 2:25 pm**

I give up....siamhie has left chat

MX Linux Forum

startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account