https://bugs.kde.org/show_bug.cgi?id=454678
Techokami <techok...@holenet.info> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |RESOLVED
Resolution|--- |UNMAINTAINED
--- Comment #7 from Techokami <techok...@holenet.info> ---
Well after using those commands and getting scared that everything violently
broke, Kalendar is now functional again! Thank you Max!
I changed the status to reflect that WHY DID THIS EVEN HAPPEN IN THE FIRST
PLACE?! This was a clean install of Kalendar onto a clean install of the KDE
spin of Fedora 36! I was expecting everything to work out of the box, but
instead I had to do a ton of MySQL necromancy using outdated commands (did you
know that the -Q parameter for mysqladmin no longer exists?) which is just...
not good for normal users that aren't comfortable with the terminal. I really
want to know why there wasn't a more graceful failover here, or even why the
Akonadi database wasn't properly initialized. Like, when it tries to do ALTER
TABLE to set up the database, but it's not initialized so the table isn't
there, why not first issue a SQL command to check if the table exists in the
first place, and if it doesn't, make Akonadi initialize the database then try
again?
Welp, now I have a headache, but at least now I got a proper calendar program
to sync my Outlook calendar with, so I can get back all my appointments.
--
You are receiving this mail because:
You are watching all bug changes.
