https://bugs.kde.org/show_bug.cgi?id=388867
Maik Qualmann changed:
What|Removed |Added
CC||phil@free.fr
--- Comment #31 from Maik Qual
https://bugs.kde.org/show_bug.cgi?id=388867
Maik Qualmann changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #30 from Ian Robertson ---
Thanks, did the trick. ( db user cannot be @localhost, db runs on centos nas
box, digikam runs on various fedora elsewheres [ can only run digikam 4.x on
centos ] , suppose '%.barony.loc' would really be best )
I
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #29 from Maik Qualmann ---
I can not say why you are not a super user. It could help not to use the
wildcard character %, but "localhost". Or you can try to set the following
variable in mysql:
mysql> SET GLOBAL log_bin_trust_function_creat
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #28 from Ian Robertson ---
confirm grants look OK to me
[root@pro ~]# mysql -udigikam5 -pdigikam5 digikam5
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 114682
Server version: 5.5.56-MariaDB Maria
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #27 from Ian Robertson ---
Nice one Simon.
[ianrob01@nova ~]$ export QT_LOGGING_RULES="digikam.*=true"
[ianrob01@nova ~]$ digikam
digikam.general: AlbumWatch use QFileSystemWatcher
digikam.general: Database Parameters:
Type:
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #26 from Maik Qualmann ---
There may also be a global setting in Fedora, then set the content:
[Rules]
*.debug=true
qt.*.debug=false
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=388867
Simon changed:
What|Removed |Added
CC||freisi...@gmail.com
--- Comment #25 from Simon ---
The
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #24 from Maik Qualmann ---
Does this file exist? If yes, rename.
~/.config/QtProject/qtlogging.ini
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #23 from Ian Robertson ---
QT_LOGGING_RULES was not set
[ianrob01@nova ~]$ env | grep QT_LOGGING_RULES
[ianrob01@nova ~]$ echo $QT_LOGGING_RULES
explicitly setting null made no difference
[ianrob01@nova ~]$ export QT_LOGGING_RULES=""
[ianr
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #22 from Maik Qualmann ---
Please try in the console before executing digiKam to delete this variable.
This has nothing to do with the debug packages and does not need to be
installed.
export QT_LOGGING_RULES=""
digikam
Maik
--
You are
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #21 from Ian Robertson ---
Hi Maik,
Would very much like to give you more debug info am not familiar with
kdedebugdialog ( fired it up checked only digikam items , but dont see
any additional output ) have installed
digikam-debuginfo-5.9.
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #20 from Maik Qualmann ---
I want to see more messages from the console. You may need to enable the debug
messages in your distribution first. Maybe look in kdebugdialog, if the output
for digiKam is activated.
Maik
--
You are receiving t
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #19 from Ian Robertson ---
[ianrob01@nova ~]$ digikam
digikam.coredb: Core database: cannot process schema initialization
DB is available and working with 5.7 appimage or docker
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #18 from Maik Qualmann ---
Please start digiKam in a console and post the messages to see what happens
when the database is updated.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #17 from Ian Robertson ---
Mistaken upgrade was from 5.7
[ianrob01@nova ~]$ rpm -qa | grep digikam
digikam-libs-5.9.0-1.fc26.x86_64
digikam-5.9.0-1.fc26.x86_64
digikam-doc-5.9.0-1.fc26.noarch
from non updated machine
root@lenovo ~]# rpm -q
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #16 from Maik Qualmann ---
On which digiKam version updated? Please post the output of the console.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=388867
Ian Robertson changed:
What|Removed |Added
Platform|MS Windows |Fedora RPMs
CC|
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #14 from Maik Qualmann ---
Created attachment 111685
--> https://bugs.kde.org/attachment.cgi?id=111685&action=edit
dbconfig.xml
As I said, an 'image' table should not exist and was never created by digiKam.
This is an individual dbconfig.
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #13 from Maik Qualmann ---
There should be no mistake here. A table with the lowercase name "images"
should not exist. Presumably their database is corrupted by previous update
attempts. I'm going to create a custom dbconfig.xml for testing
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #12 from dajomu ---
(In reply to dajomu from comment #11)
> This bug is not fixed in digikam 5.9. "Failed to update the database schema
> from version 8 to version 9." Also running MariaDB 10.2.13
This is the output from DebugView;
[1788]
https://bugs.kde.org/show_bug.cgi?id=388867
dajomu changed:
What|Removed |Added
Resolution|FIXED |---
CC||da
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #10 from Maik Qualmann ---
Fix for digiKam-5.8.0: See Bug 388977
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=388867
Maik Qualmann changed:
What|Removed |Added
Attachment #109824|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=388867
Maik Qualmann changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/dig
|
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #8 from Maik Qualmann ---
Right, and it will not applied. It does not add CONSTRAINT and UNIQUE so the
conversion will not fail. Therefore, the database must also be copied using the
migration tool. I find it interesting that MySQL does not
https://bugs.kde.org/show_bug.cgi?id=388867
caulier.gil...@gmail.com changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=388867
mlr...@cs.com changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #6 from mlr...@cs.com ---
(In reply to Maik Qualmann from comment #5)
> Created attachment 109824 [details]
> dbconfig.xml
>
> It fails because of duplicate data in the AlbumRoots table. Normally, ALTER
> IGNORE TABLE should prevent this. I
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #5 from Maik Qualmann ---
Created attachment 109824
--> https://bugs.kde.org/attachment.cgi?id=109824&action=edit
dbconfig.xml
It fails because of duplicate data in the AlbumRoots table. Normally, ALTER
IGNORE TABLE should prevent this. I
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #4 from mlr...@cs.com ---
(In reply to caulier.gilles from comment #1)
> Please install DebugView program from Microsoft and run it while digiKam
> starting.
>
> https://docs.microsoft.com/en-us/sysinternals/downloads/debugview
>
> You will
https://bugs.kde.org/show_bug.cgi?id=388867
--- Comment #3 from mlr...@cs.com ---
(In reply to Maik Qualmann from comment #2)
> Do you use MySQL or MariaDB? An internal or external MySQL server?
>
> Maik
mySQL intern - MariaDB vs 10.2
Roeland
--
You are receiving this mail because:
You are wa
https://bugs.kde.org/show_bug.cgi?id=388867
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #2 from Maik
https://bugs.kde.org/show_bug.cgi?id=388867
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
34 matches
Mail list logo
