I have just upgraded to Ubuntu 22.04.01.
Turning on my laptop never starts Ubuntu immediately. Eventually (after several tries) I get a list of things to so, with Ubuntu at the top, so I select that and Ubuntu does open, but what worries and may explain my difficulties, if only I could understand it, is a warning message which always comes up. This reads as follows:

Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/dbus/service.py", line 715, in _message_cb
retval = candidate_method(self, *args, **keywords)
File "/usr/lib/python3/dist-packages/DellLinuxAssistant/telemetry/dbus_backend.py", line 375, in deal_message
QueueMessageClient(self.config, self.scheduler).LogLogMetricEvent("FRONTEND", "Dell Linux Assistant closes")
File "/usr/lib/python3/dist-packages/DellLinuxAssistant/telemetry/telemetry_common.py", line 300, in wrapper
return func(*args, **kw)
File "/usr/lib/python3/dist-packages/DellLinuxAssistant/telemetry/queue_message_client.py", line 107, in LogLogMetricEvent
return self.triggerSend(filePath, header, Schedule)
File "/usr/lib/python3/dist-packages/DellLinuxAssistant/telemetry/queue_message_client.py", line 51, in triggerSend
job = self.scheduler.add_interval_job(MessageHelper(self.configure).SendEvent, minutes=1, start_date=datetime.now()+timedelta(seconds=1), args=[filePath, header], max_runs=1)
File "/usr/lib/python3/dist-packages/ApschedulerStandalone/scheduler.py", line 347, in add_interval_job
return self.add_job(trigger, func, args, kwargs, **options)
File "/usr/lib/python3/dist-packages/ApschedulerStandalone/scheduler.py", line 285, in add_job
if not self.running:
File "/usr/lib/python3/dist-packages/ApschedulerStandalone/scheduler.py", line 148, in running
thread_alive = self._thread and self._thread.isAlive()
AttributeError: 'Thread' object has no attribute 'isAlive'

Something is going wrong. Can I fix it? Once Ubuntu is up and running everything seems to work OK, so it isn't the end of the world, but it is a nuisance and a waste of time and clearly something is going wrong.

You have some python that is producing errors. What is running that?

Have you been installing modules with pip? Or are you partially updated? Did you install something outside of your package manager?

https://packages.ubuntu.com/source/b...sc/apscheduler

Appears to be in threading

https://www.codecademy.com/resources...ading/is-alive
https://python.hotexamples.com/examp...-examples.html

There is no way to tell from looking at that. A python script/application has to have all imports installed, and they need to match.

This only started happening after I upgraded, which I did at the suggestion of Software Updater. It began as soon as I restarted after the upgrade, so it can't be caused by anything I installed. If that argument is fallacious, please let me know.
I tried running Software Updater and it assured me that everything was up to date.
According to the codeacademy.com site you sent the link to, a Thread object should have an attribute "is_alive" whereas the warning notice complains about there not being "isAlive".
I'm a bit wary (read "scared stiff") of altering something I didn't write and don't understand, but presumably scheduler stops dead when it detects the error, so I wouldn't have broken anything much.
What do you think I should do? I'm out of my depth here.

Software Updater.

Is that software updater set to check for updates every time you boot the machine? Turn that auto updating off.

I don't know how that ubuntu updater works. Maybe someone else does. Or is that part of a desktop environment? Like Gnome.

Is that the bootloader that you are talking about? Or something else.

https://wiki.ubuntu.com/SoftwareUpda..._automatically
https://wiki.ubuntu.com/SoftwareUpdates

You can set it to check for updates every day, every two days, every week, every fortnight or never.
I've changed from every day to every two days to see if that makes a difference. Not yet, obviously.
If it doesn't make a difference I'll try never and run it by hand for a few days.

I'm not much of a programmer, but based on this post in the Dell Community forum (link in the post below), it seems to be related to a python (version?) mismatch in the Dell Linux Assistant and/or Dell Recovery.

What do you think?

Looking around made me think that the solution should be installing / upgrading the somerville-dla-team ppa

Unfortunately, it didn't work for me (yet?), but I base this suggestion on these posts:

In askUbuntu
In SuperUser

Thanks for the post. I did not know about that.

https://linux.dell.com/repo/hardware/dsu/
https://www.dell.com/support/kbdoc/e...tem-update-dsu
https://linux.dell.com/repo/hardware/omsa.html

Makes me wonder why Ubuntu is using this.

Thanks drlv
Unfortunately, it didn't work for me (yet?),

Nor me. If you find a tweak that does work, please let me know. I think we're getting close.
If it doesn't get mended, perhaps I'll follow the suggestion to delete the Dell Linux assistant. Since it doesn't seem to be working it won't be a great loss.

Unfortunately I had several issues with the upgrade to Ubuntu 22.04 so I ditched it altogether and moved to Fedora ¯\_(ツ)_/¯

I just received an update to Dell-linux-assistant. Looks as if it worked.

i too upgraded from 20.04 to 22.04. never again. i always do fresh installs. a lot of buggy stuff has happened since then. maybe it's a dell firmware issue on the mother board.