Yeah...the exclamation mark comments things out; however, if I remember correctly, the exclamation point should be enclosed with a left arrow, exclamation point, two dashes...followed by what is intended to be commented out...then closed with two dashes and a right arrow; such as...

<! -- put-some-stuff-here -->

Perhaps the exclamation point is causing jwm to have a nervous-jerkdown, because it's looking for the other characters but not seeing them?

I don't mean to butt in, but this may possibly help?

It has been a while since I used JWM or made a release of it, but this is something that I've done on every window manager that I've used for many years to help with font rendering, and it has always worked for me. Whether it will help with your scenario or not, I can't say for sure. However, it will only take a couple of minutes to find out.

1. Open your file manager as root, and navigate to /etc/fonts/

2. You may see a file there called fonts.conf; however, create a new file, and name it local.conf

3. Copy and paste the following into the newly created local.conf file...

<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
    <match target="font">
        <edit mode="assign" name="hinting" >
            <bool>true</bool>
        </edit>
        <edit mode="assign" name="autohint" >
            <bool>true</bool>
        </edit>
        <edit mode="assign" name="hintstyle" >
            <const>hintslight</const>
        </edit>
        <edit mode="assign" name="rgba" >
            <const>rgb</const>
        </edit>
        <edit mode="assign" name="antialias" >
            <bool>true</bool>
        </edit>
        <edit mode="assign" name="lcdfilter">
            <const>lcddefault</const>
        </edit>
    </match>

<!-- Set preferred serif, sans serif, and monospace fonts. -->
    <alias>
        <family>serif</family>
        <prefer>
            <family>Droid Serif</family>
        </prefer>
    </alias>
    <alias>
        <family>sans-serif</family>
        <prefer>
            <family>Droid Sans</family>
        </prefer>
    </alias>
    <alias>
        <family>sans</family>
        <prefer>
            <family>Droid Sans</family>
        </prefer>
    </alias>
    <alias>
        <family>monospace</family>
        <prefer>
            <family>Droid Sans Mono</family>
        </prefer>
    </alias>
    <alias>
        <family>mono</family>
        <prefer>
            <family>Droid Sans Mono</family>
        </prefer>
    </alias>

</fontconfig>

4. Save the file and close it. Then reboot.

If it helped, you'll know. If it didn't, you'll know, and you can curse me, my wife, my children, and anyone else that you want.

I've done the tar.bz2 way for years...even on stable systems.

I think it was Zephyr who mentioned what he does; which is, what I do...

1. Create a hidden folder in my Home folder called .firefox
2. Download the tar.bz2 from the official Mozilla site
    Note: I personally click on Download options and other languages in order to download Firefox-ESR
3. Extract it into the created .firefox folder
4. Create a firefox.desktop file in ~/.local/share/applications/ (so that it appears in my menu) that consists of the following information...

[Desktop Entry]
Name=Firefox
Exec=apulse /home/dan/.firefox/firefox/firefox
Terminal=false
Type=Application
Categories=Network;
Icon=firefox

If you notice the Exec= line, it leads off with apulse. I don't use pulseaudio, so you'll need to have apulse installed if you also don't use pulseaudio but want things like YouTube to have sound.

So, no matter which version you may "install", it will update itself automatically and independently from the repos of your system.

I don't use EFI.

I wonder why it doesn't work?

Have you looked at /usr/share/fonts/ ?

Ahhh!

So, if any names for updates are detected, it will notify you. Nice!

I don't know why I didn't combine the two script into one...I guess I was having a brain-fart that day? LOL!

I'm guessing the user would have to set the "frontend" that they want to use?

Thanks for the clue about changing the shebang; I wasn't aware of the possibility of what may happen with bash.

Thanks fsr!

Hi Ron...I've used two different startup sounds in the past. The one that I used on Miyo-Modern was the Deepin startup sound. The other one that I used was just a few seconds from a no copyright song. I don't think I've ever used any others except those two.

I'll just link both of them for you since I'm not sure which one you may be referring to.

The Deepin startup sound - https://u.pcloud.link/publink/show?code … 8JtbN4lOFy

The MiyoLinux startup sound - https://u.pcloud.link/publink/show?code … WJ5BhxGQqk

You should be able to sample them from the download pages. If you don't see the "Direct Download" button, just scroll down the page a few lines.

Ron,

I'm not sure what may have happened.

I just got that update yesterday too, and it went fine.

Periodically, I'll run updates and they don't complete. Terminal output usually says something to the effect of "failed to connect to blah-blah-blah debian.org".

Follow Altoid's latest advice first.

If that doesn't correct it, I would try...

apt-get install --reinstall linux-image-amd64

HoaS,

I hope that you know that while I was joking, I was also being serious. You always give good advice here.

Now...back to topic. 

Ron, you've corrected me on some of my mistakes. There's never a dumb question, and no one knows it all...well...except maybe HoaS....

LOLOLOLOLOLOLOLOLOL! 

...well, he does know a lot. 

Anywho...we all feel dumb at some point. We all have our strengths and weaknesses.

...except for HoaS. 

Thanks fsr!

I'll check this out whenever I get the time to...

No promises though!

Thank you for all that you do with both Devuan and Refracta...it's much appreciated!