On 25/07/2023 12:57, Nic wrote:
> On 7/25/23 3:07 AM, Rob H wrote:
>> On 24/07/2023 23:31, Nic wrote:
>>> On 7/24/23 5:48 PM, Rob H wrote:
>>>> On 24/07/2023 22:11, Nic wrote:
>>>>> On 7/24/23 12:52 PM, Rob H wrote:
>>>>>> On 24/07/2023 17:24, Nic wrote:
>>>>>>> On 7/24/23 11:54 AM, Rob H wrote:
>>>>>>>> On 24/07/2023 11:34, Nic wrote:
>>>>>>>>> On 7/24/23 2:48 AM, Rob H wrote:
>>>>>>>>>> On 23/07/2023 21:48, Nic wrote:
>>>>>>>>>>> On 7/23/23 3:38 PM, Rob H wrote:
>>>>>>>>>>>> On 23/07/2023 20:11, Paul wrote:
>>>>>>>>>>>>> On 7/23/2023 1:48 PM, Rob H wrote:
>>>>>>>>>>>>>> On 21/07/2023 23:21, pinnerite wrote:
>>>>>>>>>>>>>>> On Fri, 21 Jul 2023 19:22:41 +0100
>>>>>>>>>>>>>>> Rob H <rob@despammer.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On 21/07/2023 10:40, pinnerite wrote:
>>>>>>>>>>>>>>>>> On Tue, 18 Jul 2023 15:47:46 +0100
>>>>>>>>>>>>>>>>> Rob H <rob@despammer.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On 18/07/2023 15:21, Paul wrote:
>>>>>>>>>>>>>>>>>>> sudo update-grub
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks, yes I did that before I rebooted.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I saw that you had tested your dram.
>>>>>>>>>>>>>>>>> Just to be sure, I would test the disk drive.
>>>>>>>>>>>>>>>>> I usually run:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> # fsck -y -C -V /dev/sd(x)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> before getting elaborate.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> One other thing. I highly recommend the Logitech
>>>>>>>>>>>>>>>>> wireless mouse.
>>>>>>>>>>>>>>>>> It is very light on batteries and has not let me down
>>>>>>>>>>>>>>>>> since purchase about five or six years ago.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Best of luck
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks but silly question, how do I test the disc when
>>>>>>>>>>>>>>>> it is in use
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Boot up on a live CD/DVD or flash drive.
>>>>>>>>>>>>>>> My favourite's are Knoppix and Parted Magic.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have just booted up a live knoppix usb and ran
>>>>>>>>>>>>>> fsck -y -C -V /dev/sda
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> but got this:
>>>>>>>>>>>>>> Found a dos partition table in /dev/sdc
>>>>>>>>>>>>>> e2fsck_open2: Bad magic number in super block
>>>>>>>>>>>>>> fsck.ext2 Superblock invalid
>>>>>>>>>>>>>> fsck.ext2 Bad magic number in super-block while trying to
>>>>>>>>>>>>>> open /dev/sda
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The superblock could not be read or does not describe a
>>>>>>>>>>>>>> valid ext2/ext3/ext4 fileystem If the device is valid and
>>>>>>>>>>>>>> it realy contains and ext2/et3/ext4 filesystem (and not aq
>>>>>>>>>>>>>> swap or ufs or something else), then the superblock is
>>>>>>>>>>>>>> corrupt , and you might try running e2fsck with an
>>>>>>>>>>>>>> alternative superblock.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Does it mean my filesystem is corrupt or?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> The identifier "/dev/sda" is the entire disk, starting at
>>>>>>>>>>>>> the MBR (sector 0).
>>>>>>>>>>>>>
>>>>>>>>>>>>> Partition identifiers are "/dev/sda1" or "/dev/sda2". In
>>>>>>>>>>>>> one of those,
>>>>>>>>>>>>> you are more likely to find a file system and all the
>>>>>>>>>>>>> trimmings.
>>>>>>>>>>>>>
>>>>>>>>>>>>>     fsck -y -C -V /dev/sda1
>>>>>>>>>>>>>     fsck -y -C -V /dev/sda2
>>>>>>>>>>>>>
>>>>>>>>>>>>> If you use gparted
>>>>>>>>>>>>>
>>>>>>>>>>>>>     sudo gparted /dev/sda
>>>>>>>>>>>>>
>>>>>>>>>>>>> then graphically you can select some of these functions.
>>>>>>>>>>>>> The benefit of doing it graphically, is there will be
>>>>>>>>>>>>> little "hints" in the GUI, that the thing you are pointed
>>>>>>>>>>>>> at, is an EXT2 or a FAT32 or an NTFS. And you have a better
>>>>>>>>>>>>> idea what partition you are checking.
>>>>>>>>>>>>>
>>>>>>>>>>>>>     [Picture]
>>>>>>>>>>>>>
>>>>>>>>>>>>> https://i.postimg.cc/tJ29Pz4D/gparted-graphical-info.gif
>>>>>>>>>>>>>
>>>>>>>>>>>>> You can also do
>>>>>>>>>>>>>
>>>>>>>>>>>>>     sudo disktype /dev/sda
>>>>>>>>>>>>>
>>>>>>>>>>>>> and it will print out what it finds.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Or for that matter, with a booted system, try
>>>>>>>>>>>>>
>>>>>>>>>>>>>     gnome-disks
>>>>>>>>>>>>>
>>>>>>>>>>>>> and select the drive from the menu.
>>>>>>>>>>>>>
>>>>>>>>>>>>> 1) Create a partition (nominal partition type like 0x83)
>>>>>>>>>>>>> 2) Format it so the superblock will be there.
>>>>>>>>>>>>> 3) Don't mount it, if you're going to check it.
>>>>>>>>>>>>>     If it is mounted, then unmount it first, then check it.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Mounting a partition, does a certain amount of checking
>>>>>>>>>>>>> anyway.
>>>>>>>>>>>>> The assumption is, there is a partition not currently mounted,
>>>>>>>>>>>>> and it does not seem interested in accepting a mount command.
>>>>>>>>>>>>>
>>>>>>>>>>>>>     Paul
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> Thanks Paul, and both sda1 and sdc5 are clean with no
>>>>>>>>>>>> errors, after. I ran the said cmd
>>>>>>>>>>>>
>>>>>>>>>>>> So my ssd drive is ok as is the filesystem as well as no
>>>>>>>>>>>> errors with my ram sticks.
>>>>>>>>>>>> I would deduce then that it something to do with linux mint
>>>>>>>>>>>> itself??
>>>>>>>>>>>> On the LM forum , where I posted my problem, and I am not
>>>>>>>>>>>> the only one it seems, I was told to remove any powered usb
>>>>>>>>>>>> adaptors, which I did 2 days ago. All was well until earlier
>>>>>>>>>>>> today when it locked up again.
>>>>>>>>>>>>
>>>>>>>>>>>> I have yet to try your earlier suggestion with a RS232 cable.
>>>>>>>>>>> Is  a windows product also installed on this machine? I
>>>>>>>>>>> thought that a DOS partition might indicate such.
>>>>>>>>>>
>>>>>>>>>> No I don't have windows on this machine, but have a disk with
>>>>>>>>>> win10 for my aged laptop.
>>>>>>>>>>
>>>>>>>>>> I am not aware there is a DOS partition, but the boot
>>>>>>>>>> partition is fat 32. I'm not sure how that happened as I just
>>>>>>>>>> let the install do it's thing at the time.
>>>>>>>>>  From your post "I have just booted up a live knoppix usb and ran
>>>>>>>>> fsck -y -C -V /dev/sda
>>>>>>>>>
>>>>>>>>> but got this:
>>>>>>>>> Found a dos partition table in /dev/sdc"     How do you
>>>>>>>>> interpret this message? What is the purpose of the dos
>>>>>>>>> partition table? Question: How many drives are in this machine?
>>>>>>>>
>>>>>>>> There are x2 250Gb ssd drives, 1 for the boot partition and the
>>>>>>>> other for my /home partition.
>>>>>>>> There is also a 3rd spinning disc drive which I use for some
>>>>>>>> backups.
>>>>>>>>
>>>>>>>> just for information, my machine locked at about 10.30am this
>>>>>>>> morning, and I have been out since then to about 4.45pm , and
>>>>>>>> the machine was still locked up.
>>>>>>>>
>>>>>>>> I am now thinking about doing a new reinstall of LM, but I'm not
>>>>>>>> sure if that would cure the problem.
>>>>>>>>
>>>>>>> Take a look at the syslog in the Home directory
>>>>>>
>>>>>> Found it in /var/logs and found these 2 entries for this morning:
>>>>>>
>>>>>> Jul 24 10:30:45 rob-Z97 touchegg[644]: libinput error: client bug:
>>>>>> timer event5 debounce: scheduled expiry is in the past (-603ms),
>>>>>> your system is too slow
>>>>>> Jul 24 11:05:57 rob-Z97 touchegg[644]: libinput error: client bug:
>>>>>> timer event5 debounce short: scheduled expiry is in the past
>>>>>> (-4702ms), your system is too slow
>>>>>>
>>>>>> Can you put that into simple terms, as my system has 16Gb of ram
>>>>>> with an i5 cpu at 3.4Ghz.
>>>>>> Thanks
>>>>> Try disabling touchegg
>>>>
>>>> How do I do that, but found a link to remove it.
>>>>
>>> It is in the mouse/touchpad window.
>>
>> Not on my system it isn't. I have checked twice and don't see anything
>> that says touchegg
> It is mentioned in your error report from syslog.
>
> Look again for system settings then mouse, if you look at the mouse
> window   you will see a second tab (top center) which says Touchpad, hit
> the Touchpad tab and the window will tab so that you can disable it.

If you mean Touchpad, yes I have disabled that 'while typing', and also
click actions to 'Disabled' in the drop down box