I can't figure out what needs to be done to compile and install evdev:

https://unix.stackexchange.com/questions...ation-xfce

I did a sudo apt install to install evdev-tools, but something's still missing... some .h file, somewhere.

Can anyone help?

I installed Onboard virtual keyboard, set its setting in Accessibility to show at boot.

I removed Onboard, but its option is still displayed on the Accessibility tab. I think that's an oversight. I shouldn't see it after it's been removed. I have a screen capture, but i don't see a button to include an image. Here's an imgur URL, if you need to take a peek: https://imgur.com/a/fM7liII

I hate to say it, but it looks like, no, there's no native, virtual keyboard in Linux Lite. That makes sense: it's Lite.

Onboard is an option, but it looks... mmm... unfinished:its appearance doesn't match the rest of Linux Lite, even looking at its available themes.

I've also had a problem with it that resulted in a constant stream of <CR><LF>s (that may be just \n being sent in the Linux environment) being sent when opening up a terminal session. I removed Onboard, and I'm going to reinstall it to see if it's still there.

If you know of alternate, plugin, addons for hosting a virtual keyboard, please list them here. Thanks.

I've noticed 2 errors that were hurting us in terms of potential ad revenue. I have since fixed them because according to Google AdSense, the Forums earn more than the main website! Ads will appear a little 'fatter' too. The ad height is an experiment that I am going to run for one month to see if there is an impact on revenue. If there is none, I'll go back to the old, skinnier code. This is for information, there is no need to reply to this thread.

FYI, Column A represents members who will see ads, Column X refers to groups that are ad-free:

Hi everyone! Hope you're all having a nice life!

Here's a nice video on how to install Linux Lite

https://www.youtube.com/watch?v=jpo2MlvW2lk

I want to password protect a folder and thought cryptlocker would do it for me?
cannot seem to get it to install tried the terminal but the system can't seem to find it
anyone got any idea's? ???

I have a generic trade show kiosk with an ITX motherboard whose 47" touch screen is rotated into portrait orientation. With every disk access, it seems, and with every mouse movement from mouseover text item to mouseover text item, there almost always seems to be an equivalent, slight waviness that appears slightly in the screen, and also a bit of static on the speaker in exact relation to the waves or ripples on the screen. Not having had a trade show kiosk before, I have no idea what might be causing the visual and sound artifacts I'm getting. The speaker works well, otherwise, as does the monitor and touchscreen.

Well, I think I may have an idea, and I'm wondering if it could come from isolated PCB and component grounds—that whoever built it took the monitor's PCBs apart, reassembled them and other parts into the trade show cabinet, but maybe never grounded all the individual chassis grounds together. If so, now all the ground levels are floating and maybe causing the static.

If the individual components need a common ground bus, will that ground be different from the mains ground? I'm not an electrical engineer or electrician.

Is there anyone familiar with building and debugging trade show kiosks who can give me any pointers?

I am installing Linux Lite for a first time. I have two disks on my laptop and i am installing Linux Lite on the second disk. I created one partition for boot (unencrypted), and one partition for root (encrypted). The installation went well, and i also installed grub on the second hard disk.
But after rebooting i get to the grub boot screen, then it starts loading the system and then i get black screen with terminal input for <initramfs>.
How should i proceed? Is this a grub misconfiguration?

I keep seeing Jerry telling everyone to use Etcher or Rufus via his release announcements, and this annoys me greatly because both apps are bloated and terrible and have circumstances where they fail.

What I offer you is a simple, enlightening and powerful full proof method to install any OS to any medium except flash cards that works with any Linux including Live Linux pending 4-8GB RAM (for Live).  As an example, you can install tails to your internal hard drive or emmc. 

So you have Linux loaded and have downloaded the image file of your favorite distribution ready to be etched to your anything of sufficient capacity other than flash cards.

Let's begin.

Open terminal of choice.

Step 1:

cd /media
sudo mkdir iso
sudo mount -o loop /path/to/iso /media/iso
If you got no errors continue to step 2
Failure to put both paths or incorrectly expressed will produce an error.
If you see the following error: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage...
sudo fdisk -l -u=sectors pathtoiso
This will display the sector size of the image as well as the starting sector.
Just multiply them, so if sector size is 512, sector start is 2048 = 1048576
sudo mount -o loop,offset=1048576 pathtoiso /media/iso

Step 2:

sudo apt install gparted
sudo gparted
Find your target, delete all partitions on it, and apply.
In some instances, i.e., ISO9660, you cannot delete the partition thus you must format to "cleared" and apply.
Click on Device, create partition table, ms-dos.
Click on Partition, new, change partition type to FAT32, and apply.
Right-click on this new partition, select manage flags, and select boot.
Take note the /dev/ name of that partition which for me is sdc1 in the next step.

Step 3:

cd /media
sudo mkdir drive
sudo mount /dev/sdc1 /media/drive/
Be careful, a partition cannot end with a /, but a folder can.
sudo cp -a --no-preserve=mode,ownership /media/iso/. /media/drive/
Disregard all errors regarding symlinks; no critical/important live boot or installation file is ever symlinked.
FAT doesn't support symlinks, but is need for BIOS/EFI boot capability.
df -h
Look for the last loop device which refers to the /media/iso loop we created earlier
sudo umount /dev/loop0 (failure to do this step will yield device in use error in the next step)
sudo umount /media/drive/ (this will take a while but when complete the files are copied)
Before you go any further wait for your file manager to also show the drive is unmounted.

Step 4:

Set your bios to support legacy boot, turn off secure boot, at grub menu choose EFI boot option if available.
Normally EFI requires secure boot files, but many distros don't include them.
We do the above to bypass errors.
It goes without saying that many unofficial Windows distributions are flawed and may produce errors.
Often the solution is to use the original boot.wim (which includes all the drivers).
Authors trim this, and that is largely stupid.
As for Tails, it likes virtualization to be ON in BIOS/EFI and you need to remove "live-media=removable" from the boot sequence, and press F10 to continue to a successful boot.

so, I had thought my computer was crashing overnight. however:

(11-19-2020, 12:32 PM)stevef link Wrote:  Sounds like it could be a hardware fault.

Can you confirm that if the PC is left without the USB drive connected that it works ok and doesn't lock up ?

has lead me to see that it's the harddrive.  I found another tread where it was noted that someone else had this problem and the fix was to unmount the drive before rebooting.

When mine locks up terminal is locked up also, so no way to unmount it.  Anyway I will see if I can figure this out. Keep it posted.