You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Void Linux running Lumina 1.6.2, I found that sometimes a bogus fluxbox-init file is created as fluxbox-init -no-slit (with the embedded space character in the filename). The running fluxbox process is listed for my desktop as /usr/bin/fluxbox -rc /home/karl/.config/lumina-desktop/fluxbox-init -no-slit -no-toolbar and so this bogus file is being used for the fluxbox configuration rather than the intended fluxbox-init which Lumina updates via its configuration GUI app. If I replace the bogus file with a symlink to the correct one:
ln -sf fluxbox-init fluxbox-init\ -no-slit
most if not all Fluxbox-related Lumina configuration things begin to work as intended.
The text was updated successfully, but these errors were encountered:
With Void Linux running Lumina 1.6.2, I found that sometimes a bogus fluxbox-init file is created as fluxbox-init -no-slit (with the embedded space character in the filename). The running fluxbox process is listed for my desktop as /usr/bin/fluxbox -rc /home/karl/.config/lumina-desktop/fluxbox-init -no-slit -no-toolbar and so this bogus file is being used for the fluxbox configuration rather than the intended fluxbox-init which Lumina updates via its configuration GUI app. If I replace the bogus file with a symlink to the correct one:
most if not all Fluxbox-related Lumina configuration things begin to work as intended.
The text was updated successfully, but these errors were encountered: