Q4OS Forum

padota1663

Member

Registered: 2024-09-21

Posts: 38

Packagekit errors in syslog

Hi,
does someone know what is this error (spammed multiple times) in my syslog? It appears when the Packagekit daemon starts automatically:

2025-06-01T22:05:39.934004+02:00 scatorrrciooo-sorrrciooo systemd[1]: Started packagekit.service - PackageKit Daemon.
2025-06-01T22:05:41.060505+02:00 scatorrrciooo-sorrrciooo packagekitd[2213744]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_U
NKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == P
K_INFO_ENUM_CRITICAL' failed
2025-06-01T22:05:41.060895+02:00 scatorrrciooo-sorrrciooo packagekitd[2213744]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_U
NKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == P
K_INFO_ENUM_CRITICAL' failed
.............
------ ***logs cut for clarity*** ------
.............
2025-06-01T22:05:41.087083+02:00 scatorrrciooo-sorrrciooo packagekitd[2213744]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
2025-06-01T22:05:41.092286+02:00 scatorrrciooo-sorrrciooo PackageKit: get-updates transaction /543_bededdbb from uid 1000 finished with success after 1120ms
2025-06-01T22:10:44.762258+02:00 scatorrrciooo-sorrrciooo PackageKit: daemon quit
2025-06-01T22:10:44.791540+02:00 scatorrrciooo-sorrrciooo systemd[1]: packagekit.service: Deactivated successfully.
2025-06-01T22:10:44.791763+02:00 scatorrrciooo-sorrrciooo systemd[1]: packagekit.service: Consumed 1.200s CPU time.

How can I solve it? And, more importantly, is it something to be afraid of? The PC behaves normally anyways.

Thanks

padota1663

Member

Registered: 2024-09-21

Posts: 38

Re: Packagekit errors in syslog

Hello, can anyone help me?

Thanks

q4osteam

Q4OS Team

Registered: 2015-12-06

Posts: 5,127

Website

Re: Packagekit errors in syslog

Run in terminal:
$ sudo apt update
and post the output

padota1663

Member

Registered: 2024-09-21

Posts: 38

Re: Packagekit errors in syslog

Hi q4osteam,

sorry for the late reply, but I was away for work and I lost your last message.

Here's the result of "sudo apt update":

root@scatorrrciooo-sorrrciooo:~# sudo apt update
Trovato:1 http://security.debian.org bookworm-security InRelease
Trovato:2 http://deb.debian.org/debian bookworm InRelease
Trovato:3 http://deb.debian.org/debian bookworm-updates InRelease
Trovato:8 https://dl.google.com/linux/chrome/deb stable InRelease
Trovato:9 https://packages.mozilla.org/apt mozilla InRelease
Trovato:4 https://q4os.org/q4repo q4os-5-0-cn InRelease
Scaricamento di:5 https://q4os.org/qtderepo bookworm InRelease [4.637 B]
Scaricamento di:6 https://q4os.org/qextrepo bookworm-chrome-cn InRelease [1.844 B]
Scaricamento di:7 https://q4os.org/qextrepo bookworm-firefox-cn InRelease [3.224 B]
Trovato:10 https://boinc.berkeley.edu/dl/linux/stable/bookworm bookworm InRelease
Recuperati 9.705 B in 4s (2.562 B/s)
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze... Fatto
Lettura informazioni sullo stato... Fatto
254 pacchetti possono essere aggiornati: eseguire "apt list --upgradable" per vederli.
W: https://boinc.berkeley.edu/dl/linux/stable/bookworm/dists/bookworm/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
root@scatorrrciooo-sorrrciooo:~#

Thank you in advance.

q4osteam

Q4OS Team

Registered: 2015-12-06

Posts: 5,127

Website

Re: Packagekit errors in syslog

You need to update your system first. Do you perform updates manually ? Have you installed update manager ?

padota1663

Member

Registered: 2024-09-21

Posts: 38

Re: Packagekit errors in syslog

Hi, yes I know, I have to update my system (it's since the 12th of February that it's never been turned off or restarted, or even updated to avoid restarts) but at the moment I'm not able, as I have important pages opened in Firefox which I cannot close right now.

Let's put this question on hold then, I'll update it as soon as I'll be able to close FF, update everything and restart.

Thanks for now.