[kalendar] [Bug 454678] Kalendar immediately crashed upon starting
https://bugs.kde.org/show_bug.cgi?id=454678 Claudio Cambra changed: What|Removed |Added Status|RESOLVED|VERIFIED Resolution|UNMAINTAINED|UPSTREAM -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 454678] Kalendar immediately crashed upon starting
https://bugs.kde.org/show_bug.cgi?id=454678 Techokami changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #7 from Techokami --- 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.
[kalendar] [Bug 454678] Kalendar immediately crashed upon starting
https://bugs.kde.org/show_bug.cgi?id=454678 --- Comment #6 from Max Pastushkov --- (In reply to Techokami from comment #5) > So I tried running this in the terminal, and I also tried what Max did, but > to no avail. The console output is pretty long so I put it into a pastebin > for convenience: https://pastebin.com/WyyuKmys > Also, here is the contents of ~/.local/share/akonadi/Akonadi.error: > > 2022-06-13T20:59:44 [INFO ] org.kde.pim.akonadiserver: Starting up the > Akonadi Server... > 2022-06-13T20:59:45 [INFO ] org.kde.pim.akonadiserv2022-06-13T20:59:48 [INFO > ] org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited > normally... > i.SchemaVersionTable' doesn't exist QMYSQL: Unable to execute query\nQuery: > ALTER TABLE SchemaVersionTable ADD COLUMN version INTEGER NOT NULL DEFAULT 0" > 2022-06-13T20:59:45 [CRITICAL] org.kde.pim.akonadiserver: Unable to > initialize database. > 2022-06-13T20:59:48 [INFO ] org.kde.pim.akonadiserver: Shutting down > AkonadiServer... So it seems that both of our issues were caused by Akonadi not being able to communicate with its database. It is possible that the issue you are experiencing could be fixed using the commands mentioned in Bug 439769, Comment 3. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 454678] Kalendar immediately crashed upon starting
https://bugs.kde.org/show_bug.cgi?id=454678 --- Comment #5 from Techokami --- So I tried running this in the terminal, and I also tried what Max did, but to no avail. The console output is pretty long so I put it into a pastebin for convenience: https://pastebin.com/WyyuKmys Also, here is the contents of ~/.local/share/akonadi/Akonadi.error: 2022-06-13T20:59:44 [INFO ] org.kde.pim.akonadiserver: Starting up the Akonadi Server... 2022-06-13T20:59:45 [INFO ] org.kde.pim.akonadiserv2022-06-13T20:59:48 [INFO ] org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally... i.SchemaVersionTable' doesn't exist QMYSQL: Unable to execute query\nQuery: ALTER TABLE SchemaVersionTable ADD COLUMN version INTEGER NOT NULL DEFAULT 0" 2022-06-13T20:59:45 [CRITICAL] org.kde.pim.akonadiserver: Unable to initialize database. 2022-06-13T20:59:48 [INFO ] org.kde.pim.akonadiserver: Shutting down AkonadiServer... -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 454678] Kalendar immediately crashed upon starting
https://bugs.kde.org/show_bug.cgi?id=454678 [email protected] changed: What|Removed |Added Status|CONFIRMED |REPORTED Ever confirmed|1 |0 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 454678] Kalendar immediately crashed upon starting
https://bugs.kde.org/show_bug.cgi?id=454678 --- Comment #4 from [email protected] --- After further debugging, I found that the crash was actually due to Akonadi not being able to start. It complained about an error with MySQL. ~/.local/share/akonadi/db_data/mysql.err: 2022-06-11 17:21:39 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB 2022-06-11 17:21:39 0 [Note] InnoDB: Completed initialization of buffer pool 2022-06-11 17:21:39 0 [ERROR] InnoDB: File ./ib_logfile0 was not found 2022-06-11 17:21:39 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2022-06-11 17:21:39 0 [Note] InnoDB: Starting shutdown... 2022-06-11 17:21:39 0 [ERROR] Plugin 'InnoDB' init function returned error. 2022-06-11 17:21:39 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2022-06-11 17:21:39 0 [ERROR] Unknown/unsupported storage engine: innodb 2022-06-11 17:21:39 0 [ERROR] Aborting However, running "touch ~/.local/share/akonadi/db_data/ib_logfile0" seems to fix it, and Kalendar works without errors. Techokami, could you you paste the output of kalendar when running it from the console? -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 454678] Kalendar immediately crashed upon starting
https://bugs.kde.org/show_bug.cgi?id=454678 [email protected] changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 454678] Kalendar immediately crashed upon starting
https://bugs.kde.org/show_bug.cgi?id=454678 [email protected] changed: What|Removed |Added CC||[email protected] --- Comment #3 from [email protected] --- Experiencing the same issue on Arch Linux. Qt Version: 5.15.4 Frameworks Version: 5.94.0 Operating System: Linux 5.18.3-arch1-1 (64-bit) Windowing System: X11 Distribution: Arch Linux Backtrace (from gdb): #0 0x776e9858 in Akonadi::IncidenceChanger::history (this=0x556675b0) at /usr/include/c++/12.1.0/bits/unique_ptr.h:191 #1 0x555844bf in CalendarManager::undoRedoData (this=0x7fffd410) at /usr/src/debug/kalendar-22.04.2/src/calendarmanager.cpp:655 #2 CalendarManager::qt_static_metacall (_o=0x7fffd410, _c=, _id=, _a=) at /usr/src/debug/build/src/kalendar_autogen/EWIEGA46WW/moc_calendarmanager.cpp:431 #3 0x76d714bb in QQmlPropertyData::readProperty (property=, target=0x7fffd410, this=0x56156f48) at ../../include/QtQml/5.15.4/QtQml/private/../../../../../../qtdeclarative/src/qml/qml/qqmlpropertydata_p.h:357 #4 loadProperty (v4=0x55843af0, object=0x7fffd410, property=...) at /usr/src/debug/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:204 #5 0x76ea04c7 in QV4::QObjectWrapper::lookupGetterImpl > (useOriginalProperty=true, revertLookup=..., object=..., engine=0x55843af0, lookup=0x55e7dda0) at ../../include/QtQml/5.15.4/QtQml/private/../../../../../../qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper_p.h:262 #6 QV4::QQmlTypeWrapper::lookupSingletonProperty (l=0x55e7dda0, engine=0x55843af0, object=...) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmltypewrapper.cpp:547 #7 0x76ea0898 in QV4::QQmlTypeWrapper::virtualResolveLookupGetter (object=0x7fffec9c0510, engine=0x55843af0, lookup=0x55e7dda0) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmltypewrapper.cpp:467 #8 0x76d8db1a in QV4::Moth::VME::interpret (frame=0x7fffcd00, engine=0x55843af0, code=0x7fffdebb39dd ";\317\001") at /usr/src/debug/qtdeclarative/src/qml/jsruntime/qv4vme_moth.cpp:641 #9 0x76d97d64 in QV4::Moth::VME::exec (frame=, engine=) at /usr/src/debug/qtdeclarative/src/qml/jsruntime/qv4vme_moth.cpp:466 #10 0x76d3b7a6 in QV4::Function::call (this=, thisObject=, argv=, argc=, context=) at /usr/src/debug/qtdeclarative/src/qml/jsruntime/qv4function.cpp:69 #11 0x76e8fb0d in QQmlJavaScriptExpression::evaluate (this=0x55a11770, callData=0x7fffec9c04d0, isUndefined=0x7fffcec7) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmljavascriptexpression.cpp:212 #12 0x76e96699 in QQmlBinding::evaluate (this=this@entry=0x55a11770, isUndefined=isUndefined@entry=0x7fffcec7) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmlbinding.cpp:218 #13 0x76e98c8a in QQmlNonbindingBinding::doUpdate (this=0x55a11770, watcher=..., flags=..., scope=...) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmlbinding.cpp:254 #14 0x76e98813 in QQmlBinding::update (this=0x55a11770, flags=...) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmlbinding.cpp:194 #15 0x76ea4cbd in QQmlObjectCreator::finalize (this=0x5587dd10, interrupt=...) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmlobjectcreator.cpp:1393 #16 0x76e486ad in QQmlComponentPrivate::complete (state=0x55855ce8, enginePriv=0x55687b00) at /usr/include/qt/QtCore/qscopedpointer.h:116 #17 QQmlComponentPrivate::complete (enginePriv=0x55687b00, state=state@entry=0x55855ce8) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmlcomponent.cpp:983 #18 0x76e4887b in QQmlComponentPrivate::completeCreate (this=0x55855c60) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmlcomponent.cpp:1079 #19 0x76e48933 in QQmlComponent::completeCreate (this=0x55855b40) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmlcomponent.cpp:1062 #20 QQmlComponent::create (this=0x55855b40, context=) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmlcomponent.cpp:820 #21 0x76e9a17a in QQmlApplicationEnginePrivate::finishLoad (this=0x55687b00, c=0x55855b40) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmlapplicationengine.cpp:148 #22 0x76e9a61b in QQmlApplicationEnginePrivate::startLoad (this=, url=..., data=..., dataFlag=) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmlapplicationengine.cpp:132 #23 0x76e9a6d2 in QQmlApplicationEngine::load (this=this@entry=0x7fffd330, url=...) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmlapplicationengine.cpp:287 #24 0x55580de2 in main (argc=, argv=) at /usr/src/debug/kalendar-22.04.2/src/main.cpp:154 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 454678] Kalendar immediately crashed upon starting
https://bugs.kde.org/show_bug.cgi?id=454678 Techokami changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 454678] Kalendar immediately crashed upon starting
https://bugs.kde.org/show_bug.cgi?id=454678 --- Comment #2 from Techokami --- (In reply to Claudio Cambra from comment #1) > Do you have kdepim-runtime installed? Other users have described similar > crashes due to this: > > https://bugs.kde.org/show_bug.cgi?id=453016 I do, in fact, have this package installed. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 454678] Kalendar immediately crashed upon starting
https://bugs.kde.org/show_bug.cgi?id=454678 Claudio Cambra changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Claudio Cambra --- Do you have kdepim-runtime installed? Other users have described similar crashes due to this: https://bugs.kde.org/show_bug.cgi?id=453016 -- You are receiving this mail because: You are watching all bug changes.
