On 7/24/2023 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

On 24/07/2023 19:36, Paul wrote:
> On 7/24/2023 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
>
> "gnome-shell[1713]: libinput error: client bug: timer event0 debounce short:
> scheduled expiry is in the past (-22ms), your system is too slow"
>
> https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1928261
>
> [This bug report is a duplicate of: Bug #1870597: libinput says "your system is too slow".]
>
> https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870597
>
> "To be fair, "your system is too slow" really means the architecture of Mutter
> (used in gnome-shell) is too slow. Not the hardware.
>
> This problem is being improved in newer versions of Mutter using some threading,
> but generally it's not an issue anyone should be concerned about. [HAH!]
> "
>
> https://en.wikipedia.org/wiki/Mutter_%28software%29
>
> "Mutter is a portmanteau of Metacity and Clutter."
>
> https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1241
>
> "WIP: clutter/frame-clock: Allow update dispatch while presentation is pending"
>
> But that observation was made three years ago.
>
> *******
>
> ###########################################################################################
> # Check the refresh rate on your monitor. It is running 30FPS or 60FPS ? Faster is better #
> ###########################################################################################
>
> Running the refresh rate faster, is a kind of workaround for a bad architecture.
>
> They're doing some kind of software operation on frame boundaries (VSYNC
> presumably), and one of the operations blocks some other activity, and
> it makes something "too slow".
>
> This is either in Mutter or Muffin (Muffin being a fork of Mutter
> and Muffin is used for Linux Mint Cinnamon).
>
> Paul
>

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

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

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.

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.

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.

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.

On 7/25/23 11:06 AM, Rob H wrote:
> 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
And the machine continues to lock? You still keep getting that error in
syslog?

On 25/07/2023 17:03, Nic wrote:
> On 7/25/23 11:06 AM, Rob H wrote:
>> 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
> And the machine continues to lock? You still keep getting that error in
> syslog?
>

On 7/25/23 12:43 PM, Rob H wrote:
> On 25/07/2023 17:03, Nic wrote:
>> On 7/25/23 11:06 AM, Rob H wrote:
>>> 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
>> And the machine continues to lock? You still keep getting that error
>> in syslog?
>>
>
> No it hasn't locked up yet, but it's too early to say yet. I'd like to
> give it another day or so before I can say if it has or not.
>
> No, no errors in syslog either yet, so fingers crossed.
> Thanks
>
fingers crossed

On 25/07/2023 18:00, Nic wrote:
> On 7/25/23 12:43 PM, Rob H wrote:
>> On 25/07/2023 17:03, Nic wrote:
>>> On 7/25/23 11:06 AM, Rob H wrote:
>>>> 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
>>> And the machine continues to lock? You still keep getting that error
>>> in syslog?
>>>
>>
>> No it hasn't locked up yet, but it's too early to say yet. I'd like to
>> give it another day or so before I can say if it has or not.
>>
>> No, no errors in syslog either yet, so fingers crossed.
>> Thanks
>>
> fingers crossed

On 7/26/23 9:11 AM, Rob H wrote:
> Jul 26 14:03:58 rob-Z97 systemd[1]: Starting casper-md5check Verify
> Live ISO checksums...
> Jul 26 14:03:58 rob-Z97 systemd[1]: Starting Record Runlevel Change in
> UTMP...
> Jul 26 14:03:58 rob-Z97 casper-md5check[2547]: .fopen md5_file: No
> such file or directory
> Jul 26 14:03:58 rob-Z97 casper-md5check[2547]: Checking integrity,
> this may take some time (or try: fsck.mode=skip)
> Jul 26 14:03:58 rob-Z97 systemd[1]: casper-md5check.service: Main
> process exited, code=exited, status=1/FAILURE
> Jul 26 14:03:58 rob-Z97 systemd[1]: casper-md5check.service: Failed
> with result 'exit-code'.
> Jul 26 14:03:58 rob-Z97 systemd[1]: Failed to start casper-md5check
> Verify Live ISO checksums.
How does this iso fit into the picture? What were you attempting to do
before the lockdown? What ever it was it resulted in some problem that a
request to run FSCK was noted.  Have you run FSCK from a live distro
yet? Have you had any power failures in your area recently, thus forcing
an immediate shutdown of your Linux machine?

On 26/07/2023 15:40, Nic wrote:
> On 7/26/23 9:11 AM, Rob H wrote:
>> Jul 26 14:03:58 rob-Z97 systemd[1]: Starting casper-md5check Verify
>> Live ISO checksums...
>> Jul 26 14:03:58 rob-Z97 systemd[1]: Starting Record Runlevel Change in
>> UTMP...
>> Jul 26 14:03:58 rob-Z97 casper-md5check[2547]: .fopen md5_file: No
>> such file or directory
>> Jul 26 14:03:58 rob-Z97 casper-md5check[2547]: Checking integrity,
>> this may take some time (or try: fsck.mode=skip)
>> Jul 26 14:03:58 rob-Z97 systemd[1]: casper-md5check.service: Main
>> process exited, code=exited, status=1/FAILURE
>> Jul 26 14:03:58 rob-Z97 systemd[1]: casper-md5check.service: Failed
>> with result 'exit-code'.
>> Jul 26 14:03:58 rob-Z97 systemd[1]: Failed to start casper-md5check
>> Verify Live ISO checksums.
> How does this iso fit into the picture? What were you attempting to do
> before the lockdown? What ever it was it resulted in some problem that a
> request to run FSCK was noted.  Have you run FSCK from a live distro
> yet? Have you had any power failures in your area recently, thus forcing
> an immediate shutdown of your Linux machine?

I have no idea how the above fits into the picture, I just posted it in
case it would mean something.

I wasn't attempting to do anything before the lockup , I just turned on
my monitor and started using the mouse,but it didn't move, and neither
was the keyboard responsive

I ran FSCK from a live distro on 24th July and posted back the results
at 07.48
For further information the results were shown that both ssd drives were
clean with no errors at that time.

On 7/26/23 11:33 AM, Rob H wrote:
> On 26/07/2023 15:40, Nic wrote:
>> On 7/26/23 9:11 AM, Rob H wrote:
>>> Jul 26 14:03:58 rob-Z97 systemd[1]: Starting casper-md5check Verify
>>> Live ISO checksums...
>>> Jul 26 14:03:58 rob-Z97 systemd[1]: Starting Record Runlevel Change
>>> in UTMP...
>>> Jul 26 14:03:58 rob-Z97 casper-md5check[2547]: .fopen md5_file: No
>>> such file or directory
>>> Jul 26 14:03:58 rob-Z97 casper-md5check[2547]: Checking integrity,
>>> this may take some time (or try: fsck.mode=skip)
>>> Jul 26 14:03:58 rob-Z97 systemd[1]: casper-md5check.service: Main
>>> process exited, code=exited, status=1/FAILURE
>>> Jul 26 14:03:58 rob-Z97 systemd[1]: casper-md5check.service: Failed
>>> with result 'exit-code'.
>>> Jul 26 14:03:58 rob-Z97 systemd[1]: Failed to start casper-md5check
>>> Verify Live ISO checksums.
>> How does this iso fit into the picture? What were you attempting to
>> do before the lockdown? What ever it was it resulted in some problem
>> that a request to run FSCK was noted.  Have you run FSCK from a live
>> distro yet? Have you had any power failures in your area recently,
>> thus forcing an immediate shutdown of your Linux machine?
>
> I have no idea how the above fits into the picture, I just posted it
> in case it would mean something.
>
> I wasn't attempting to do anything before the lockup , I just turned
> on my monitor and started using the mouse,but it didn't move, and
> neither was the keyboard responsive
>
> I ran FSCK from a live distro on 24th July and posted back the results
> at 07.48
> For further information the results were shown that both ssd drives
> were clean with no errors at that time.
https://www.reddit.com/r/linuxmint/comments/wd3yel/failed_to_start_caspermd5check_verify_live_iso/
run systemctl disable casper-md5check.service

and see what happens

On Sun, 16 Jul 2023 18:43:54 +0100
Rob H <rob@despammer.com> wrote:

> On 16/07/2023 13:32, Yrrah wrote:
> > Rob H <rob@despammer.com>:
> >
> >> These last few weeks I have found that every now and again, becoming
> >> more frequent now, my Mint system seems to freeze, or at least my wired
> >> mouse does. (...)
> >
> > Can you still use the keyboard?
> >
> > Yrrah
> Yes I can

I don't have SSDs so this may be inappropriate but recently I spent days reporting and re-partitioning/formatting hard drives until I changed the SATA cables and all revealed as perfectly OK.

-
Linux Mint 21.1 kernel version 5.15.0-76-generic Cinnamon 5.6.8
AMD Phenom II x4 955 CPU 16Gb Dram 2TB Barracuda

On 26/07/2023 18:18, Nic wrote:
> On 7/26/23 11:33 AM, Rob H wrote:
>> On 26/07/2023 15:40, Nic wrote:
>>> On 7/26/23 9:11 AM, Rob H wrote:
>>>> Jul 26 14:03:58 rob-Z97 systemd[1]: Starting casper-md5check Verify
>>>> Live ISO checksums...
>>>> Jul 26 14:03:58 rob-Z97 systemd[1]: Starting Record Runlevel Change
>>>> in UTMP...
>>>> Jul 26 14:03:58 rob-Z97 casper-md5check[2547]: .fopen md5_file: No
>>>> such file or directory
>>>> Jul 26 14:03:58 rob-Z97 casper-md5check[2547]: Checking integrity,
>>>> this may take some time (or try: fsck.mode=skip)
>>>> Jul 26 14:03:58 rob-Z97 systemd[1]: casper-md5check.service: Main
>>>> process exited, code=exited, status=1/FAILURE
>>>> Jul 26 14:03:58 rob-Z97 systemd[1]: casper-md5check.service: Failed
>>>> with result 'exit-code'.
>>>> Jul 26 14:03:58 rob-Z97 systemd[1]: Failed to start casper-md5check
>>>> Verify Live ISO checksums.
>>> How does this iso fit into the picture? What were you attempting to
>>> do before the lockdown? What ever it was it resulted in some problem
>>> that a request to run FSCK was noted.  Have you run FSCK from a live
>>> distro yet? Have you had any power failures in your area recently,
>>> thus forcing an immediate shutdown of your Linux machine?
>>
>> I have no idea how the above fits into the picture, I just posted it
>> in case it would mean something.
>>
>> I wasn't attempting to do anything before the lockup , I just turned
>> on my monitor and started using the mouse,but it didn't move, and
>> neither was the keyboard responsive
>>
>> I ran FSCK from a live distro on 24th July and posted back the results
>> at 07.48
>> For further information the results were shown that both ssd drives
>> were clean with no errors at that time.
> https://www.reddit.com/r/linuxmint/comments/wd3yel/failed_to_start_caspermd5check_verify_live_iso/
> run systemctl disable casper-md5check.service
>
> and see what happens

That didn't make any difference either, as my system locked up earlier,
less than 24 hours since a reboot.
It's looking more like a re install of LM now

On 7/27/2023 6:46 AM, pinnerite wrote:
> On Sun, 16 Jul 2023 18:43:54 +0100
> Rob H <rob@despammer.com> wrote:
>
>> On 16/07/2023 13:32, Yrrah wrote:
>>> Rob H <rob@despammer.com>:
>>>
>>>> These last few weeks I have found that every now and again, becoming
>>>> more frequent now, my Mint system seems to freeze, or at least my wired
>>>> mouse does. (...)
>>>
>>> Can you still use the keyboard?
>>>
>>> Yrrah
>> Yes I can
>
> I don't have SSDs so this may be inappropriate but recently I spent days reporting and re-partitioning/formatting hard drives until I changed the SATA cables and all revealed as perfectly OK.
>
> -
> Linux Mint 21.1 kernel version 5.15.0-76-generic Cinnamon 5.6.8
> AMD Phenom II x4 955 CPU 16Gb Dram 2TB Barracuda
>

SATA cables can be damaged by bending them (crushing them).
It affects the dielectric, if you pinch the conductors in there.
Sometimes, the elastic band they ship with, that coils the cable
up, damages the cable.

The other kind of defect, is the voltages used by the Southbridge
when driving the SATA port.

I've had one 2TB drive in the past, seemingly be damaged by
a voltage issue. I marked the cable as "Do Not Use" and left
in plugged in, to make it easier to avoid that port in future.
The drive was similarly retired and has not been used since.

Yours could be a creased-cable issue, but it could also be
an issue with the Southbridge voltages. Southbridges have
at least five motherboard regulator voltages feeding them,
and one of those voltages affects SATA drive interfaces.

And in case you were thinking "a modern system would do a better job",
there are some pretty egregious design choices in my AM4 motherboard.
The SOC power goes from 3.5W at idle, to 6.5W when running a
multithreaded compressor application. I could actually feel this
one day, when I stuck a finger on the Southbridge, and the damn
thing was hot, and... the Southbridge wasn't doing anything. And
this is because it shares a voltage with something else, the
voltage needed to be turned up for the something-else, and
the Southbridge gets hot for nothing. And, I guess, this
constitutes "good design practice" in 2023. All that buying
new kit gets you, is a new set of problems.

Paul