https://bugs.kde.org/show_bug.cgi?id=264383
--- Comment #19 from Christophe Giboudeaux ---
Thanks for the feedback. both issues should be addressed with this change.
--
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-
https://bugs.kde.org/show_bug.cgi?id=264383
Christophe Giboudeaux changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Version Fixed In|
https://bugs.kde.org/show_bug.cgi?id=264383
--- Comment #17 from Simon Williams ---
The patch in comment #11 appears to solve the problem for mysqlcheck. Without
the patch akonadi issues many CHECK TABLE statements against the wrong MySQL
server when it starts up. With the patch this is no longer
https://bugs.kde.org/show_bug.cgi?id=264383
--- Comment #16 from Christophe Giboudeaux ---
Unless someone *really* tests the patch in comment#11, nothing will be done.
(ie: I don't need "should solve" answers, I need "it solves" or "it does not
solve")
eventually I'll create a system db to test
https://bugs.kde.org/show_bug.cgi?id=264383
--- Comment #15 from Simon Williams ---
This issue is reproducable in 1.8.1. A read of the source for 1.9.0 suggests
the bug is still there also.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.kde.org/show_bug.cgi?id=264383
--- Comment #14 from Simon Williams ---
The supplied patch should solve the problem with mysqlcheck, but a similar
change needs to be made for mysqladmin.
I'm concerned that there may be other client processes that we're missing. I've
checked through t
https://bugs.kde.org/show_bug.cgi?id=264383
--- Comment #13 from Simon Williams ---
Sorry ignore that, I was getting confused. I forget that the akonadiserver is
the mysql client as well.
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.kde.org/show_bug.cgi?id=264383
--- Comment #12 from Simon Williams ---
Unless that patch somehow applies to clients as well that won't fix it. The
clients are connecting to the wrong server. Changing the server is not going to
help.
--
You are receiving this mail because:
You are t
https://bugs.kde.org/show_bug.cgi?id=264383
--- Comment #11 from Christophe Giboudeaux ---
Created attachment 76312
--> https://bugs.kde.org/attachment.cgi?id=76312&action=edit
test patch
If anyone is willing to test, please apply this patch to the akonadi server
source, build, install then ru
https://bugs.kde.org/show_bug.cgi?id=264383
--- Comment #10 from Simon Williams ---
That is indeed the case for the mysqld process launched by Akonadi. But to be
extra clear, this only applies to the *SERVER* process. The whole point of this
bug is that Akonadi isn't using it's own server process
https://bugs.kde.org/show_bug.cgi?id=264383
--- Comment #9 from Christophe Giboudeaux ---
To clarify things. Please correct if anything is incorrect
AFAIU the mysql doc, the my.cnf files are ignored if --defaults-file is used.
That's the case for the mysqld process launched by the akonadi server
https://bugs.kde.org/show_bug.cgi?id=264383
--- Comment #8 from Simon Williams ---
The severity of this bug MUST be upgraded to CRITICAL. This is not just a
crash.
1. It affects other programs
2. It crashes other programs
3. It risks corrupting data
4. It risks corrupting data of other programs
12 matches
Mail list logo
