Respin MX problem with Moksha

[Senpai]

Hi @AVLinux:
At the end I am not using the script provided by Bodhi to install Moksha, I just add the Bodhi repository and a “pinning” file to prioritize MX and Debian repositories over Bodho ones, but in the respin I am doing of Moksha over MX-Fluxbox installing Moksha as the only WM, in the installation everything works fine, all the user folders are shown as “Desktop, Documents Downloads, Music, Video, etc.. ...”, and although I configure the directory ‘/etc/skel’ as other times, adding the folders ‘.e, .elementary’ of my home and ‘dconf’ and some other in ‘skel/.config’, I can not get the user folders are displayed when creating the ISO and both the user ‘demo’ and to install the new usuarui from that ISO, only shows the folder ‘Desktop’, none more .... What am I missing, I don't have much experience using WM?

Code: Select all

Snapshot created on: 20250410_1225
System:
  Kernel: 6.1.0-32-amd64 [6.1.129-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-32-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Moksha v: 0.4.1.18373 vt: 7 dm: LightDM v: 1.32.0 Distro: Senpai Respin
    MX-Moksha-23.5_x64 Libretto febrero 22 2025 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Kvm System: QEMU product: Standard PC (Q35 + ICH9, 2009) v: pc-q35-7.2
    serial: <superuser required> Chassis: type: 1 v: pc-q35-7.2 serial: <superuser required>
  Mobo: N/A model: N/A serial: N/A BIOS: SeaBIOS v: 1.16.2-debian-1.16.2-1 date: 04/01/2014
CPU:
  Info: model: AMD Ryzen 5 5500 bits: 64 type: SMP arch: Zen 3 gen: 4 level: v3 note: check
    built: 2021-22 process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
    microcode: 0xA50000D
  Topology: cpus: 4x cores: 1 smt: <unsupported> cache: L1: 4x 128 KiB (512 KiB)
    desc: d-1x64 KiB; i-1x64 KiB L2: 4x 512 KiB (2 MiB) desc: 1x512 KiB L3: 4x 16 MiB (64 MiB)
    desc: 1x16 MiB
  Speed (MHz): avg: 3600 min/max: N/A cores: 1: 3600 2: 3600 3: 3600 4: 3600 bogomips: 28799
  Flags: avx avx2 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, no microcode
  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: disabled; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Red Hat Virtio 1.0 GPU driver: virtio-pci v: 1 alternate: virtio_pci ports:
    active: Virtual-1 empty: none bus-ID: 00:01.0 chip-ID: 1af4:1050 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositors: 1: enlightenment 2: Picom v: 10 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: swrast gpu: virtio-pci display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 506x284mm (19.92x11.18") s-diag: 580mm (22.84")
  Monitor-1: Virtual-1 model: QEMU Monitor built: 2014 res: 1920x1080 hz: 60 dpi: 150 gamma: 1.2
    size: 325x203mm (12.8x7.99") diag: 383mm (15.1") ratio: 16:10 modes: max: 1280x800 min: 640x480
  API: OpenGL v: 4.5 Mesa 22.3.6 renderer: llvmpipe (LLVM 15.0.6 256 bits) direct-render: Yes
Audio:
  Device-1: Intel 82801I HD Audio vendor: Red Hat QEMU Virtual Machine driver: snd_hda_intel
    v: kernel bus-ID: 00:1b.0 chip-ID: 8086:293e class-ID: 0403
  API: ALSA v: k6.1.0-32-amd64 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:
  Device-1: Red Hat Virtio 1.0 network driver: virtio-pci v: 1 modules: virtio_pci pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: N/A bus-ID: 01:00.0 chip-ID: 1af4:1041 class-ID: 0200
  IF-ID-1: eth0 state: up speed: -1 duplex: unknown mac: <filter>
Drives:
  Local Storage: total: 20 GiB used: 1.01 TiB (5146.7%)
  ID-1: /dev/vda maj-min: 254:0 model: N/A size: 20 GiB block-size: physical: 512 B
    logical: 512 B speed: <unknown> type: N/A serial: N/A scheme: MBR
  SMART Message: Unknown smartctl error. Unable to generate data.
Partition:
  ID-1: / raw-size: 20 GiB size: 19.52 GiB (97.59%) used: 9.47 GiB (48.5%) fs: ext4 dev: /dev/vda1
    maj-min: 254:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon or lm-sensors.
Repos:
  Packages: pm: dpkg pkgs: 2086 libs: 1023 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/bodhi-repositories.list
    1: deb http://packages.bodhilinux.com/bodhi bookworm b7debbie
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://debian.redimadrid.es/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://debian.redimadrid.es/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://ftp.cica.es/mirrors/Linux/MX-Packages/mx/repo/ bookworm main non-free
Info:
  Processes: 196 Uptime: 8m wakeups: 53 Memory: 3.82 GiB used: 820.4 MiB (21.0%) 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: BIOS (legacy, CSM, MBR)

Best regards

[AVLinux]

Hi,

Moksha, Enlightenment and Fluxbox have a non-standard way of starting applications, most DE's use the established XDG folders like ~/.config/autostart. Enlightenment and Moksha use ~/.e/e/applications/startup/

If you are creating a Moksha respin with MX-Snapshot and want the XDG User Directories to start up you will need to add the XDG-User-Dirs update to Moksha startup..

So Settings Panel-->Apps-->Startup Applications.

In the System Tab select 'User folders update' and then 'Add' and 'Apply' and this will add it to Moksha's startup.

If you want to verify or hand edit you can also control startup applications from ~/.e/e/applications/startup/.order text file

[Senpai]

Hi,

Moksha, Enlightenment and Fluxbox have a non-standard way of starting applications, most DE's use the established XDG folders like ~/.config/autostart. Enlightenment and Moksha use ~/.e/e/applications/startup/
If you are creating a Moksha respin with MX-Snapshot and want the XDG User Directories to start up you will need to add the XDG-User-Dirs update to Moksha startup..
So Settings Panel-->Apps-->Startup Applications.
In the System Tab select 'User folders update' and then 'Add' and 'Apply' and this will add it to Moksha's startup.
If you want to verify or hand edit you can also control startup applications from ~/.e/e/applications/startup/.order text file

Thanks AVLinux:
I had just discovered that I can include it in the “.e/e/applications/startup/startupcommands” file that I copy to “/etc/skel”, .
The graphic option you indicate me in “Configuration Panel > Applications > Startup applications. “I had not seen it as in the installation Moksha had the user folders, I thought that it was already configured by default.... I will use this one and try to create the ISO.
I'm really liking Molsha, but there are so many configuration options that I'm lost

Thanks for your help

[AVLinux]

Hi, yes the startupcommands is another possibility for sure, that is unique to Moksha and is a really handy feature!