09-08-2024, 06:36 PM
Investigating lock up is difficult, especially if it is inconsistent.
When you say
Are you aware of anything that changed just before the lock ups began ?
Check any updates which occurred around that time to see exactly what changed.
Do you have any timeshift snapshots from the time when it worked as expected ?
You could try reviewing the logs after a lock up on starting kodi.
Power up normally, allow the laptop to fully boot and ensure any scheduled updates/upgrades are completed.
Once you are sure everything is settled, note the time (as hh:mm) and then initiate kodi.
If it works, stop kodi and shutdown.
Repeat (noting the time each time) until you get a lock up on starting kodi.
Then restart the machine but don't start kodi.
Review the logs from the previous boot.
As you know the date and time of a failed kodi launch, this command will show everything the machine could log.
Replace hh:mm with your value
When you say
Quote:Only solution, to shutdown and rebootDoes this mean you can do a controlled shutdown and reboot or do you mean forced power off and reboot ?
Are you aware of anything that changed just before the lock ups began ?
Check any updates which occurred around that time to see exactly what changed.
Do you have any timeshift snapshots from the time when it worked as expected ?
You could try reviewing the logs after a lock up on starting kodi.
Power up normally, allow the laptop to fully boot and ensure any scheduled updates/upgrades are completed.
Once you are sure everything is settled, note the time (as hh:mm) and then initiate kodi.
If it works, stop kodi and shutdown.
Repeat (noting the time each time) until you get a lock up on starting kodi.
Then restart the machine but don't start kodi.
Review the logs from the previous boot.
As you know the date and time of a failed kodi launch, this command will show everything the machine could log.
Replace hh:mm with your value
Code:
journalctl --since hh:mm
stevef
clueless
clueless