Recent Posts

Pages: 1 [2] 3 4 ... 10
11
Yes I agree, all of the appimages I have used were from github, where everything is very transparent. That is where the source code is kept, and issues can be logged, and also the original authors are the ones who have posted and maintained the code there.

Also, a lot of large single application websites also now host appimages for their own applications on their own download page and those are trustworthy.

But third party websites aren't as trustworthy since who knows where the code they are hosting comes from?
12
OKMO Retrol B02 Miniature Gas Petrol Hit & Miss Engine First Start Up & Running

This is the best out of the box Hit & Miss engine experience that I have had, just an absolutely awesome engine from Jin.


13
Yeah, I pretty much like the idea of appimage. I went and searched Waterfox one, and thought that 'appimagehub' was a legit source.

Anyway, when launching the expected browser app downloaded from that site, it showed only a text file, which begins like that:

Code: [Select]
!!!DON'T USE APPIMAGEHUB!!!

        .--.         _
       |o_o |       | |
       |:_/ |       | |
      //   \ \      |_|
     (|     | )      _
    /'\_   _/`\     (_)
    \___)=(___/

**Many AppImages on the platform come from unknown or suspicious users.**

I have no idea of what's going on that website, or is it a scam or prank or whatever. So obviously one has to be careful where to download appimages.

On a positive note, there is a site, where the actual Waterfox appimage (among many other apps) is available. I tested it, and it worked right away.

This is about a single app, but it seems that Github-related sites might be more thrustworthy  trustworthy source:

https://appimage.github.io/
14
Member Videos / Re: Stepperhead CNC Lathe Cutting Threads
« Last post by vtsteam on February 21, 2026, 08:39:55 PM »
That makes sense and it's nice to have a consistent spindle speed for more reasons than just threading. I know what you mean about doing something when the workshop warms up. Cabin fever here, waiting for winter to break its grip. This next week shows no sign of that happening. I was hoping to have my new electronic change gear finish mounted to the lathe in the next few days if I get a break from the snow plowing and bouts of bitter cold.
15
Hi Sorveltaja, sounds like there are linux kernel problems. I wonder if the flatpaks might have had a hand in  that. Generally it is thought on the boards I am on that flatpaks are problematic, while appimages are much preferred. Explanation to others unfamiliar with the terms.... these are a relatively recent form of "generic" application packages. Each uses a different method but they basically have all needed dependencies built in, and are supposedly OS agnostic. They are supposed to be able to be installed and work in any Linux.

As I said though, it seems flatpaks are not viewed favorably, at least in the Puppy Linux/EasyOS world. Appimages seem to work very well.
16
Vtsteam:

Thanks for the offer, good to know.

I should have been clearer about the subject. It (Linux system) isn't VM instance, but actual install on my pc. That Mint Mate installation is still accessible. It boots just fine, but some parts of it are apparently broken.

For example, when trying to uninstall Gimp, it gives following errors:

Code: [Select]
(Reading database ... 571681 files and directories currently installed.)
Removing gimp (2.10.36-3ubuntu0.24.04.1) ...
Setting up linux-image-6.17.0-14-generic (6.17.0-14.14~24.04.1) ...
Setting up linux-headers-6.17.0-14-generic (6.17.0-14.14~24.04.1) ...
/etc/kernel/header_postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.17.0-14-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area...
make -j6 KERNELRELEASE=6.17.0-14-generic -C /lib/modules/6.17.0-14-generic/build M=/var/lib/dkms/virtualbox/7.0.16/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.17.0-14-generic (x86_64)
Consult /var/lib/dkms/virtualbox/7.0.16/build/make.log for more information.
dkms autoinstall on 6.17.0-14-generic/x86_64 succeeded for nvidia
dkms autoinstall on 6.17.0-14-generic/x86_64 failed for virtualbox(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
 * dkms: autoinstall for kernel 6.17.0-14-generic
   ...fail!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
dpkg: error processing package linux-headers-6.17.0-14-generic (--configure):
 installed linux-headers-6.17.0-14-generic package post-installation script subprocess returned error exit status 11
dpkg: dependency problems prevent configuration of linux-headers-generic-hwe-24.04:
 linux-headers-generic-hwe-24.04 depends on linux-headers-6.17.0-14-generic; however:
  Package linux-headers-6.17.0-14-generic is not configured yet.

dpkg: error processing package linux-headers-generic-hwe-24.04 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic-hwe-24.04:
 linux-generic-hwe-24.04 depends on linux-headers-generic-hwe-24.04 (= 6.17.0-14.14~24.04.1); however:
  Package linux-headers-generic-hwe-24.04 is not configured yet.

dpkg: error processing package linux-generic-hwe-24.04 (--configure):
 dependency problems - leaving unconfigured
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for mate-menus (1.26.1+mint1) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Errors were encountered while processing:
 linux-headers-6.17.0-14-generic
 linux-headers-generic-hwe-24.04
 linux-generic-hwe-24.04
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up linux-headers-6.17.0-14-generic (6.17.0-14.14~24.04.1) ...
/etc/kernel/header_postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.17.0-14-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area...
make -j6 KERNELRELEASE=6.17.0-14-generic -C /lib/modules/6.17.0-14-generic/build M=/var/lib/dkms/virtualbox/7.0.16/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.17.0-14-generic (x86_64)
Consult /var/lib/dkms/virtualbox/7.0.16/build/make.log for more information.
dkms autoinstall on 6.17.0-14-generic/x86_64 succeeded for nvidia
dkms autoinstall on 6.17.0-14-generic/x86_64 failed for virtualbox(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
 * dkms: autoinstall for kernel 6.17.0-14-generic
   ...fail!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
dpkg: error processing package linux-headers-6.17.0-14-generic (--configure):
 installed linux-headers-6.17.0-14-generic package post-installation script subprocess returned error exit status 11
dpkg: dependency problems prevent configuration of linux-headers-generic-hwe-24.04:
 linux-headers-generic-hwe-24.04 depends on linux-headers-6.17.0-14-generic; however:
  Package linux-headers-6.17.0-14-generic is not configured yet.

dpkg: error processing package linux-headers-generic-hwe-24.04 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic-hwe-24.04:
 linux-generic-hwe-24.04 depends on linux-headers-generic-hwe-24.04 (= 6.17.0-14.14~24.04.1); however:
  Package linux-headers-generic-hwe-24.04 is not configured yet.

dpkg: error processing package linux-generic-hwe-24.04 (--configure):
 dependency problems - leaving unconfigured
Processing triggers for linux-image-6.17.0-14-generic (6.17.0-14.14~24.04.1) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.17.0-14-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area...
make -j6 KERNELRELEASE=6.17.0-14-generic -C /lib/modules/6.17.0-14-generic/build M=/var/lib/dkms/virtualbox/7.0.16/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.17.0-14-generic (x86_64)
Consult /var/lib/dkms/virtualbox/7.0.16/build/make.log for more information.
dkms autoinstall on 6.17.0-14-generic/x86_64 succeeded for nvidia
dkms autoinstall on 6.17.0-14-generic/x86_64 failed for virtualbox(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
 * dkms: autoinstall for kernel 6.17.0-14-generic
   ...fail!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: error processing package linux-image-6.17.0-14-generic (--configure):
 installed linux-image-6.17.0-14-generic package post-installation script subprocess returned error exit status 11
Errors were encountered while processing:
 linux-headers-6.17.0-14-generic
 linux-headers-generic-hwe-24.04
 linux-generic-hwe-24.04
 linux-image-6.17.0-14-generic

After all, it's not a critical system for me, and as mentioned earlier, I've been planning to replace it with another distro anyway.

BillTodd:

It seems you aren't the only one having things like that happen. Rob Braxman has a video where he describes how Win11 and TPM made his dual boot Linux installation inaccessible, without asking or informing about it (~21min):

 _https://www.youtube.com/watch?v=t1eX_vvAlUc
17
Member Videos / Re: Stepperhead CNC Lathe Cutting Threads
« Last post by jackary on February 21, 2026, 04:59:37 AM »
Hi vtsteam,
I used a 0.5 hp three phase motor running via a vectorless inverter. For screwcutting it works best using the largest back gear pulley which gives a 9 to one redution ratio from the motor spindle. This then results on a stable drive to the spindle with adequate torque so that the cutting force does not slow the spindle down. The light sensor senses one piece of 10mm wide black tape on the inside face of the large pulley, so this gives only one pulse per rev. I tried many variations but this worked best and was most stable. I think the utube video I show was made using the mid sized pulley drive, with the inverter wound down to about 10%. So the video shows slight variations in speed due to this. I should really make another video with the back gear pulley driving the spindle, perhaps when my workshop warms up.
Alan
18
May not be related to your problems , but windows has a bad habit of flagging disks as mounted and locked and not releasing them .

I have this problem if I launch Win11 and it sees my backup disk (which is ntfs ) . when i swap back to linux, the disk will be locked out until I run chkdsk in windows on it a couple of times.

Win 11 is just a PITA.
19
CNC / Re: It's new to me
« Last post by ddmckee54 on February 19, 2026, 11:57:37 PM »
This time I remembered to export the new CNC assembly as a JPG file.

The magenta colored bits are the parts that will be 3D printed.  I added all the spacers to the 3D model that will be used to bolt the main frame to the base, and the spacers that will turn the two Y extrusions into a sort of truss.  Coincidently, all those spacers also got printed today, and the center-points for the holes in the base got laid out.  I've got to get the holes drilled in the X and Y rails so I can verify that the locations are correct before I drill the base.
20
Member Videos / Re: Stepperhead CNC Lathe Cutting Threads
« Last post by vtsteam on February 19, 2026, 01:26:21 PM »
Hi Alan,  :beer: I see, so you used optical encoding DIY. Was it a single pulse per spindle revolution, or did you have more than one black tape location?

I don't remember if TurboCNC could use more than one. I know it was capable of threading well with one. That does require reasonably consistent spindle speed(s), because the software is interpolating to spindle speed for regulating the pulse rate of the stepper while threading.

What type of spindle motor did you use? Mine is not consistent in speed because it is a DC motor, so it varies somewhat with load. I therefore have to use positional sensing of the spindle, rather than speed sensing. That was made possible by recent low prices for high resolution rotary encoders.

The difficulty there is the high data rate required for processing the encoder output (3000 lines per spindle revolution plus direction sensing in mine). For an Arduino to keep up, I had to convert it into a Forth machine via an alternative bootloader, use interrupts, and integer math. It's helpful that threads aren't cut at very high RPM!

Very understandable that you kept Stepperhead one. Such a fine machine. I also like the fact that it runs on TurboCNC -- which I used to use as well (not with a lathe). I like the compactness and simplicity. I bought a license for the source code back then, too, and the owner of DAK was always very courteous about any questions I had.

Pages: 1 [2] 3 4 ... 10