I'm not a linux person, but I do recall there might have been a need to add the user to the dialout group. A quick search for "linux arduino dialout" might provide a solution.
If you don't see ports in the IDE, you'll have to check at the operating system level.
Please run lsusb without the board connected.
Next connect the board and run lsusb again?
Any differences? You can post the output here; please use code tags when doing so, one for each command.
Your output will look like Before
$ lsusb
Bus 001 Device 007: ID 04d9:1503 Holtek Semiconductor, Inc. Keyboard
Bus 001 Device 006: ID 2341:8036 Arduino SA Leonardo (CDC ACM, HID)
Bus 001 Device 005: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 004: ID 0458:003a KYE Systems Corp. (Mouse Systems) NetScroll+ Mini Traveler / Genius NetScroll 120
Bus 001 Device 003: ID 2341:0042 Arduino SA Mega 2560 R3 (CDC ACM)
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
After
$ lsusb
Bus 001 Device 007: ID 04d9:1503 Holtek Semiconductor, Inc. Keyboard
Bus 001 Device 006: ID 2341:8036 Arduino SA Leonardo (CDC ACM, HID)
Bus 001 Device 005: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 004: ID 0458:003a KYE Systems Corp. (Mouse Systems) NetScroll+ Mini Traveler / Genius NetScroll 120
Bus 001 Device 003: ID 2341:0042 Arduino SA Mega 2560 R3 (CDC ACM)
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
After connecting the Arduino in the previous step, run the dmesg command; the output will look something like
...
...
[ 4535.761608] ch341 1-5.4.4:1.0: device disconnected
[ 4571.060066] usb 1-5.4.4: new full-speed USB device number 11 using ehci-pci
[ 4571.139212] usb 1-5.4.4: New USB device found, idVendor=1a86, idProduct=7523
[ 4571.139219] usb 1-5.4.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 4571.139223] usb 1-5.4.4: Product: USB2.0-Serial
[ 4571.139832] ch341 1-5.4.4:1.0: ch341-uart converter detected
[ 4571.142878] usb 1-5.4.4: ch341-uart converter now attached to ttyUSB0
Post the last 20 or 30 lines. If your board has the CH340 serial-to-usb adapter (as above), check the dmesg output for BRLTTY. If it shows, uninstall it using sudo apt-get remove brltty.
mo@mo-lt:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f3:0c03 Elan Microelectronics Corp. WBF Fingerprint Sensor
Bus 001 Device 002: ID 0408:a061 Quanta Computer, Inc. HD User Facing
Bus 001 Device 004: ID 04ca:3016 Lite-On Technology Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
mo@mo-lt:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f3:0c03 Elan Microelectronics Corp. WBF Fingerprint Sensor
Bus 001 Device 002: ID 0408:a061 Quanta Computer, Inc. HD User Facing
Bus 001 Device 004: ID 04ca:3016 Lite-On Technology Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
mo@mo-lt:~$
That is a good point. Here is more info that may be helpful.
I had a desktop running Windows 10 that I used for development for Arduino. I successfully built Arduino projects with it. I am staring at three Wemos D1 Mini 8266 based clocks that have been running continuously for over a year.
I recently had a hard disk failure on the Windows 10 desktop machine. I rebuilt the desktop using Linux Mint. I haven't tried to program any Arduino supported boards since the crash until a couple of days ago.
It is good to know that the driver is pre-installed with Linux Mint.
I really appreciate all the help you have provided.
Use one of those to do the initial checks for the board detection; you know that they were programmable in the past. You don't mention if the Wemos D1 Mini ESP32 was also successfully programmed in the past.
The D1 Mini 8266 has a micro USB connector; I mentioned it before but make sure that you are using a data/sync cable and not a charge-only cable. I do not know what the other model Wemos board has (USB-C or micro-USB)?.