[BUG] Unable to run script to update tried both

[thorrrr]

Describe the bug

I am attempting to update 2.12.3 to latest version i have tried stable and rolling both give same error
On CachyOS hyprland + ML4W but on the latest release it fails at point 6

Steps to reproduce

Just open terminal zhrc here type bash <(curl -s https://ml4w.com/os/stable)

Expected behavior

Install like normal

Screenshots

No response

Distribution

Arch Linux

If Other, specify

No response

Additional context

-- Section 6: Conditional reload ---
No critical failures — attempting Hyprland and Waybar reload...
ok
hyprctl reload exit code: 0

:: Theme: /ml4w-glass-center
waybar launch exit code: 0

=== Summary: 2026-07-08T17:41:36+01:00 ===
Critical files: 13/13
Packages missing: 1
Services down: 1
Reload: attempted
Log: /home/dale/Projects/Cachy-Dot-Brain/reports/post-update-20260708-174133.log
[INFO] Cleaning up temporary files...
[SUCCESS] Setup process finished!
╭─dale at cachyos-dell in ~
╰─○ [2026-07-08 17:41:36.613] [info] Using configuration file /home/dale/.config/waybar/themes/ml4w-glass-center/config-custom
[2026-07-08 17:41:36.613] [info] Including resource file: ~/.config/ml4w/settings/waybar-quicklinks.json
[2026-07-08 17:41:36.614] [info] Including resource file: ~/.config/waybar/modules.json
[2026-07-08 17:41:36.616] [info] Including resource file: ~/.config/ml4w/settings/waybar-custom-modules.json
[2026-07-08 17:41:36.621] [info] Discovered appearance 'dark'
[2026-07-08 17:41:36.621] [info] Using CSS file /home/dale/.config/waybar/themes/ml4w-glass-center/default/style-custom.css
[2026-07-08 17:41:36.639] [info] Hyprland IPC starting
[2026-07-08 17:41:36.640] [info] Loading persistent workspaces from Waybar config
[2026-07-08 17:41:36.641] [info] Loading persistent workspaces from Hyprland workspace rules
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No s╭─dale at cachyos-dell in ~
╰─○ Full
[2026-07-08 17:41:36.973] [info] Bar configured (width: 1904, height: 60) for output: eDP-1
[2026-07-08 17:41:36.973] [error] Item '': No icon name or pixmap given.
╭─dale at cachyos-dell in ~
╰─○ shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current direct

Code of Conduct

• I agree to follow this project's Code of Conduct

[thorrrr]

I rebooted tried again and now get
Section 6: Conditional reload ---
No critical failures — attempting Hyprland and Waybar reload...
ok
hyprctl reload exit code: 0

:: Theme: /ml4w-glass-center
waybar launch exit code: 0

=== Summary: 2026-07-08T17:59:07+01:00 ===
Critical files: 13/13
Packages missing: 1
Services down: 1
Reload: attempted
Log: /home/dale/Projects/Cachy-Dot-Brain/reports/post-update-20260708-175904.log
[INFO] Cleaning up temporary files...
[SUCCESS] Setup process finished!
╭─dale at cachyos-dell in ~
╰─○ [2026-07-08 17:59:07.539] [info] Using configuration file /home/dale/.config/waybar/themes/ml4w-glass-center/config-custom
[2026-07-08 17:59:07.539] [info] Including resource file: ~/.config/ml4w/settings/waybar-quicklinks.json
[2026-07-08 17:59:07.539] [info] Including resource file: ~/.config/waybar/modules.json
[2026-07-08 17:59:07.540] [info] Including resource file: ~/.config/ml4w/settings/waybar-custom-modules.json
[2026-07-08 17:59:07.543] [info] Discovered appearance 'dark'
[2026-07-08 17:59:07.543] [info] Using CSS file /home/dale/.config/waybar/themes/ml4w-glass-center/default/style-custom.css
[2026-07-08 17:59:07.557] [info] Hyprland IPC starting
[2026-07-08 17:59:07.558] [info] Loading persistent workspaces from Waybar config
╭─dale at cachyos-dell in ~
╰─○ Full
[2026-07-08 17:59:07.834] [info] Bar configured (width: 1904, height: 60) for output: eDP-1
[2026-07-08 17:59:07.834] [error] Item '': No icon name or pixmap given.
╭─dale at cachyos-dell in ~
╰─○

[thorrrr]

Feedback from CC Opus trying to fix it myself hope it helps
Follow-up on this — dug further and found a second, more serious bug underneath the getcwd noise.

The getcwd errors are cosmetic and traceable: the installer invokes the user post-install script from inside its own temp directory (e.g. /tmp/ml4w-installer-XXXXX), then deletes that
directory as part of cleanup. Any process the post-script spawns (hyprctl reload, waybar restart) inherits that now-deleted working directory and spams shell-init: error retrieving current
directory on every subsequent invocation until the process is killed and restarted from a valid cwd. Fixed on my end by adding cd "$HOME" at the top of my post-install script — but this will
bite anyone with a post-install hook that launches a long-running process (like waybar), since the fix has to live in the hook, not the installer.

The real bug: separately, and more importantly — three consecutive runs of the stable install script (bash <(curl -s https://ml4w.com/os/stable)) completed with [SUCCESS] Setup process
finished! on all three, but wrote zero new files to ~/.mydotfiles/com.ml4w.dotfiles.stable/.config/. Confirmed via stat: every ML4W-managed directory (hypr, waybar, ml4w, kitty) still shows an
mtime from 19 May — a month before any of today's three runs. Only packages/fonts/cursors/icons (installed via pacman/yay/wget, separate code paths) actually refreshed. The dotfiles config
copy itself silently did nothing, three times in a row, while reporting success each time.

Looking at copy_with_blacklist in ~/.local/share/ml4w-dotfiles-installer/utils.sh: the copy loop runs as find . -mindepth 1 | while read -r item; do ... done — a while loop in a pipeline
subshell. The function's overall return code comes from that pipeline, which is 0 regardless of whether any individual cp -a inside the loop actually succeeds or runs at all. So a completely
empty or broken clone, or a loop that exits early for any reason, still reports success — there's no verification step confirming files actually landed after the copy.

Suggested fix: after copy_with_blacklist returns, verify at least N files were written (or diff source/dest file counts) and fail loud if the copy produced nothing, rather than trusting the
loop's own exit code.

Environment: CachyOS (rolling), Hyprland, com.ml4w.dotfiles.stable profile active, upgrading from a config last touched 19 May under the .stable profile scheme.

[mylinuxforwork]

Thanks for testing and sharing your feedback.
I will look into it with the next main release.

[thorrrr]

Thanks for testing and sharing your feedback. I will look into it with the next main release.

Hi Stephan
Should i wait for you to deploy a fix or is there a hack i could use to get the upgrade installed ?

[mylinuxforwork]

My suggestion for now would be to create a manual backup from your .mydotfiles folder. Then switch to a tty, remove the folder and run the installation script again.
After the new installation you can bring back your customization.

[mylinuxforwork]

I have just released 2.14.1 Please try to install this version.

[thorrrr]

I have just released 2.14.1 Please try to install this version.

▎ Tested 2.14.1 today (installer 0.2.5, hyprland-dotfiles-stable.dotinst, update of existing 2.12.3 profile on Arch/CachyOS). Same behaviour as reported: the installer completes with success
▎ output, but copy_with_blacklist writes nothing — I captured mtimes on ~/.mydotfiles/com.ml4w.dotfiles.stable/.config (and hypr/waybar/ml4w subdirs plus version.json) immediately before and
▎ after the run, and every timestamp is byte-identical. version.json still reads 2.12.3 post-install, and the Welcome app confirms it. The restore/merge phase and package setup all run
▎ normally — it's specifically the profile content copy that silently no-ops. Happy to run a debug build or share logs.