While you're here, please consider supporting GamingOnLinux on:
Reward Tiers:
Patreon. Plain Donations: 
PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers:
Patreon. Plain Donations: PayPal.This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- GOG launch their Preservation Program to make games live forever with a hundred classics being 're-released'
- Valve dev details more on the work behind making Steam for Linux more stable
- Half-Life 2 free to keep until November 18th, Episodes One & Two now included with a huge update
- NVIDIA detail upcoming Linux driver features for Wayland and explain current support
- Direct3D to Vulkan translation layer DXVK v2.5 released with rewritten memory management
- > See more over 30 days here
-
Half-Life: Blue Shift remake mod Black Mesa: Blue Shift…
- a0kami -
The Walking Dead, The Expanse and more in the Telltale …
- Caldathras -
Half-Life 2 free to keep until November 18th, Episodes …
- wvstolzing -
Half-Life 2 free to keep until November 18th, Episodes …
- Caldathras -
The Walking Dead, The Expanse and more in the Telltale …
- Liam Dawe - > See more comments
- What do you want to see on GamingOnLinux?
- Liam Dawe - New Desktop Screenshot Thread
- Vortex_Acherontic - Types of programs that are irritating
- dvd - Weekend Players' Club 11/15/2024
- StoneColdSpider - Our own anti-cheat list
- Xpander - See more posts
Just a little warning for everyone.. if like me you upgraded to KDE 5.24 as soon as the tumbleweed update hit.. please be aware that in some cases it may break your KDE configuration..
For example:
https://www.reddit.com/r/kde/comments/sohpop/plasma_524_freezes_on_splash_screen_after_upgrade/
If you do end up with a broken desktop in the shape of appearing frozen or acting strange (like I did) it can be fixed by simply resetting the KDE configuration.
If you're on X11 you can do so by:
Hit Ctrl + Alt + F2
Login to your regular account
$ init 3
$ mv .config .config-bak
$ mv .cache .cache-bak
$ mv .kde4 .kde4-bak
$ reboot
You should now be able to login successfully using KDE. Copy back other app configs after you get to a working desktop.
I believe it's an akondi or mariadb related bug, as even with fresh config I'm getting errors when trying to start kmail:
~]$ kmail
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
akonadi.collectionattributetable OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation OK
akonadi.collectiontable OK
akonadi.flagtable OK
akonadi.mimetypetable OK
akonadi.parttable OK
akonadi.parttypetable OK
akonadi.pimitemflagrelation OK
akonadi.pimitemtable OK
akonadi.pimitemtagrelation OK
akonadi.relationtable OK
akonadi.relationtypetable OK
akonadi.resourcetable OK
akonadi.schemaversiontable OK
akonadi.tagattributetable OK
akonadi.tagremoteidresourcerelationtable OK
akonadi.tagtable OK
akonadi.tagtypetable OK
org.kde.pim.akonadiserver: Running DB initializer
org.kde.pim.akonadiserver: DB initializer done
org.kde.pim.akonadiserver: DATABASE ERROR:
org.kde.pim.akonadiserver: Error code: "2013"
org.kde.pim.akonadiserver: DB error: "Lost connection to server during query"
org.kde.pim.akonadiserver: Error text: "Lost connection to server during query QMYSQL3: Unable to execute statement"
org.kde.pim.akonadiserver: Values: QMap((":0", QVariant(qlonglong, 1))(":1", QVariant(qlonglong, 2)))
org.kde.pim.akonadiserver: Query: "SELECT count(DISTINCT PimItemTable.id), sum(PimItemTable.size), sum(CASE WHEN ( SeenFlags.Flag_id IS NOT NULL OR IgnoredFlags.Flag_id IS NOT NULL ) THEN 1 ELSE 0 END), PimItemTable.collectionId FROM PimItemTable LEFT JOIN PimItemFlagRelation AS SeenFlags ON ( PimItemTable.id = SeenFlags.PimItem_id AND SeenFlags.Flag_id = :0 ) LEFT JOIN PimItemFlagRelation AS IgnoredFlags ON ( PimItemTable.id = IgnoredFlags.PimItem_id AND IgnoredFlags.Flag_id = :1 ) GROUP BY PimItemTable.collectionId"
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Database error: Cannot open database.
org.kde.pim.akonadiserver: Last driver error: "QMYSQL: Unable to connect"
org.kde.pim.akonadiserver: Last database error: "Can't connect to local server through socket '/run/user/1000/akonadi/mysql.socket' (111)"
QSqlQuery::exec: database not open
org.kde.pim.akonadiserver: Database error: Cannot open database.
org.kde.pim.akonadiserver: Last driver error: "QMYSQL: Unable to connect"
org.kde.pim.akonadiserver: Last database error: "Can't connect to local server through socket '/run/user/1000/akonadi/mysql.socket' (111)"
QSqlQuery::exec: database not open
QSqlQuery::prepare: database not open
org.kde.pim.akonadiserver: DATABASE ERROR while PREPARING QUERY:
org.kde.pim.akonadiserver: Error code: ""
org.kde.pim.akonadiserver: DB error: ""
org.kde.pim.akonadiserver: Error text: ""
org.kde.pim.akonadiserver: Database error: Cannot open database.
org.kde.pim.akonadiserver: Query: "SELECT CollectionTable.id, CollectionTable.remoteId, CollectionTable.remoteRevision, CollectionTable.name, CollectionTable.parentId, CollectionTable.resourceId, CollectionTable.enabled, CollectionTable.syncPref, CollectionTable.displayPref, CollectionTable.indexPref, CollectionTable.cachePolicyInherit, CollectionTable.cachePolicyCheckInterval, CollectionTable.cachePolicyCacheTimeout, CollectionTable.cachePolicySyncOnDemand, CollectionTable.cachePolicyLocalParts, CollectionTable.queryString, CollectionTable.queryAttributes, CollectionTable.queryCollections, CollectionTable.isVirtual FROM CollectionTable"
org.kde.pim.akonadiserver: Last driver error: "QMYSQL: Unable to connect"
org.kde.pim.akonadiserver: Failed to query initial collections for scheduler!
org.kde.pim.akonadiserver: Not a fatal error, no collections will be scheduled for sync or cache expiration!
org.kde.pim.akonadiserver: Last database error: "Can't connect to local server through socket '/run/user/1000/akonadi/mysql.socket' (111)"
QSqlQuery::exec: database not open
org.kde.pim.akonadiserver: Database error: Cannot open database.
org.kde.pim.akonadiserver: Last driver error: "QMYSQL: Unable to connect"
org.kde.pim.akonadiserver: Last database error: "Can't connect to local server through socket '/run/user/1000/akonadi/mysql.socket' (111)"
QSqlQuery::exec: database not open
QSqlQuery::prepare: database not open
org.kde.pim.akonadiserver: DATABASE ERROR while PREPARING QUERY:
org.kde.pim.akonadiserver: Error code: ""
org.kde.pim.akonadiserver: DB error: ""
org.kde.pim.akonadiserver: Error text: ""
org.kde.pim.akonadiserver: Query: "SELECT CollectionTable.id, CollectionTable.remoteId, CollectionTable.remoteRevision, CollectionTable.name, CollectionTable.parentId, CollectionTable.resourceId, CollectionTable.enabled, CollectionTable.syncPref, CollectionTable.displayPref, CollectionTable.indexPref, CollectionTable.cachePolicyInherit, CollectionTable.cachePolicyCheckInterval, CollectionTable.cachePolicyCacheTimeout, CollectionTable.cachePolicySyncOnDemand, CollectionTable.cachePolicyLocalParts, CollectionTable.queryString, CollectionTable.queryAttributes, CollectionTable.queryCollections, CollectionTable.isVirtual FROM CollectionTable"
org.kde.pim.akonadiserver: Failed to query initial collections for scheduler!
org.kde.pim.akonadiserver: Not a fatal error, no collections will be scheduled for sync or cache expiration!
org.kde.pim.akonadiserver: DATABASE ERROR while PREPARING QUERY:
org.kde.pim.akonadiserver: Error code: "2006"
org.kde.pim.akonadiserver: DB error: "Server has gone away"
org.kde.pim.akonadiserver: Error text: "Server has gone away QMYSQL3: Unable to prepare statement"
org.kde.pim.akonadiserver: Query: "SELECT id, name FROM PartTypeTable WHERE ( ns = :0 AND name = :1 )"
org.kde.pim.akonadiserver: Error during selection of record with ns "ATR" from table "PartTypeTable" "Server has gone away QMYSQL3: Unable to prepare statement"
org.kde.pim.akonadiserver: DATABASE ERROR while PREPARING QUERY:
org.kde.pim.akonadiserver: Error code: "2006"
org.kde.pim.akonadiserver: DB error: "Server has gone away"
org.kde.pim.akonadiserver: Error text: "Server has gone away QMYSQL3: Unable to prepare statement"
org.kde.pim.akonadiserver: Query: "INSERT INTO PartTypeTable (name, ns) VALUES (:0, :1)"
org.kde.pim.akonadiserver: Error during insertion into table "PartTypeTable" "Server has gone away QMYSQL3: Unable to prepare statement"
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadicontrol: Akonadi server is now operational.
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally...
org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_unifiedmailbox_agent" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_unifiedmailbox_agent' crashed. No restart!
org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_maildispatcher_agent" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_maildispatcher_agent' crashed. No restart!
org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_newmailnotifier_agent" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_newmailnotifier_agent' crashed. No restart!
org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_sendlater_agent" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_sendlater_agent' crashed. No restart!
org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_archivemail_agent" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_archivemail_agent' crashed. No restart!
org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_indexing_agent" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_indexing_agent' crashed. No restart!
org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_mailfilter_agent" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_mailfilter_agent' crashed. No restart!
org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_migration_agent" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_migration_agent' crashed. No restart!
org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_followupreminder_agent" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_followupreminder_agent' crashed. No restart!
org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_mailmerge_agent" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_mailmerge_agent' crashed. No restart!
org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_notes_agent" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_notes_agent' crashed. No restart!
^C
My best guess is this occurs when trying to upgrade the configuration, which causes a hang and in turn a broken desktop. I'm still investigating further, might have to also reset the database?
In any case, if you run into this and don't have a home directory backup (like me
EDIT: Kmail works after a reset.. if you use it, and it doesn't launch see here:
https://userbase.kde.org/KMail/FAQs_Hints_and_Tips#Clean_start_after_a_failed_migration
Last edited by BlackBloodRum on 10 February 2022 at 5:26 am UTC
If you would like samples of my borg backup scripts, I can provide them. I always run a /home backup before system upgrades. (btrfs snapshots aren't great at protecting against drive failure.)
Tried rolling back to KDE 5.23.5 but after the upgrade attempt the configuration ended up broken there too (same bug then occurred on 5.23.5).
With that said, once the KDE config was reset, I could login to KDE 5.24 just fine (had it running for a day now, so far so good)
In my case, I don't backup my home directory because my OS install is on a NVME drive (/home too), which is BTRFS for / and ext4 for /home.
My actual "data" is stored on several spinning rust drives and then backed up across other spinning rust drives / computers. Even my games are stored on different SSD drives.
So, in my infinite wisdom figured I didn't need to backup /home since the data was expendable and didn't hold anything valuable.
Last edited by BlackBloodRum on 11 February 2022 at 3:47 pm UTC
View PC info
Last edited by Shmerl on 13 February 2022 at 7:15 am UTC
In my case the OS is on a tiny 1TB NVMe drive so data is on other much larger drives :-).
The OS itself is only backed up with btrfs snapshots.
My view is if the boot drive fails, or the OS breaks beyond repair (unlikely) then it's just a fresh install and mount my luks encrypted drives. Job done, data restored and working system.
My data disks however are backed up once a day to other drives.
Last edited by BlackBloodRum on 17 February 2022 at 1:50 pm UTC