[digikam] [Bug 476578] digikam crashes when opening 'Tools' menu
https://bugs.kde.org/show_bug.cgi?id=476578 --- Comment #3 from Karsten de Freese --- the 8.2.0 AppImage seems to work fine so far. I'll wait for the official release to update my installations (Linux and Win10), to avoid database incompatibilities between the versions. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476578] New: digikam crashes when opening 'Tools' menu
https://bugs.kde.org/show_bug.cgi?id=476578 Bug ID: 476578 Summary: digikam crashes when opening 'Tools' menu Classification: Applications Product: digikam Version: 8.1.0 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: karsten.defre...@posteo.de Target Milestone: --- Application: digikam (8.1.0) Qt Version: 5.15.11 Frameworks Version: 5.111.0 Operating System: Linux 6.5.9-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: - started digikam - opened 'Tools' menu, no other action yet - digikam crashed => repeated two times with same result, while the check for new items was still running => another attempt when the check for new items was already finished did not lead to a crash Specific system settings: external mariadb, shared with Win10 installation (as per https://mail.kde.org/pipermail/digikam-users/2018-March/026586.html) The reporter is unsure if this crash is reproducible. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault [KCrash Handler] #4 0x7f377ef04e76 in () at /lib64/libQt5Core.so.5 #5 0x7f3781921be4 in Digikam::Album::childAtRow(int) const () at /lib64/libdigikamgui.so.8.1.0 #6 0x7f3781914955 in Digikam::AbstractAlbumModel::index(int, int, QModelIndex const&) const () at /lib64/libdigikamgui.so.8.1.0 #7 0x7f378193b400 in () at /lib64/libdigikamgui.so.8.1.0 #8 0x7f377f1253e3 in () at /lib64/libQt5Core.so.5 #9 0x7f377f085ffe in QAbstractItemModel::rowsInserted(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) () at /lib64/libQt5Core.so.5 #10 0x7f377f08ef4a in QAbstractItemModel::endInsertRows() () at /lib64/libQt5Core.so.5 #11 0x7f377f0bc595 in () at /lib64/libQt5Core.so.5 #12 0x7f377f0c0465 in () at /lib64/libQt5Core.so.5 #13 0x7f377f0c36bd in () at /lib64/libQt5Core.so.5 #14 0x7f377f1253e3 in () at /lib64/libQt5Core.so.5 #15 0x7f377f085ffe in QAbstractItemModel::rowsInserted(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) () at /lib64/libQt5Core.so.5 #16 0x7f377f08ef4a in QAbstractItemModel::endInsertRows() () at /lib64/libQt5Core.so.5 #17 0x7f37819101e5 in Digikam::AbstractAlbumModel::slotAlbumAdded(Digikam::Album*) () at /lib64/libdigikamgui.so.8.1.0 #18 0x7f377f125442 in () at /lib64/libQt5Core.so.5 #19 0x7f3781918052 in Digikam::AlbumManager::signalAlbumAdded(Digikam::Album*) () at /lib64/libdigikamgui.so.8.1.0 #20 0x7f378194ec4a in Digikam::AlbumManager::scanPAlbums() () at /lib64/libdigikamgui.so.8.1.0 #21 0x7f377f1253e3 in () at /lib64/libQt5Core.so.5 #22 0x7f377f12921a in QTimer::timeout(QTimer::QPrivateSignal) () at /lib64/libQt5Core.so.5 #23 0x7f377f118e5b in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #24 0x7f377fda519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #25 0x7f377f0ed198 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #26 0x7f377f1454c9 in QTimerInfoList::activateTimers() () at /lib64/libQt5Core.so.5 #27 0x7f377f145d74 in () at /lib64/libQt5Core.so.5 #28 0x7f3771913f30 in () at /lib64/libglib-2.0.so.0 #29 0x7f3771915b58 in () at /lib64/libglib-2.0.so.0 #30 0x7f377191620c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #31 0x7f377f1460d6 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #32 0x7f377f0ebc2b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #33 0x7f377ffadc67 in QDialog::exec() () at /lib64/libQt5Widgets.so.5 #34 0x7f378182f7c1 in Digikam::DigikamApp::slotMaintenance() () at /lib64/libdigikamgui.so.8.1.0 #35 0x7f377f1253e3 in () at /lib64/libQt5Core.so.5 #36 0x7f377fd9e8b2 in QAction::triggered(bool) () at /lib64/libQt5Widgets.so.5 #37 0x7f377fda142f in QAction::activate(QAction::ActionEvent) () at /lib64/libQt5Widgets.so.5 #38 0x7f377ff25f02 in () at /lib64/libQt5Widgets.so.5 #39 0x7f377ff2dd33 in () at /lib64/libQt5Widgets.so.5 #40 0x7f377fde6d58 in QWidget::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #41 0x7f377fda519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #42 0x7f377fdad5cf in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #43 0x7f377f0ed198 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #44 0x7f377fdab92e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /lib64/libQt5Widgets.so.5 #45 0x7f377fe002ba in () at /lib64/libQt5Widgets.so.5 #46
[digikam] [Bug 440590] digikam 7.3.0 fails to start: cannot process schema initialization
https://bugs.kde.org/show_bug.cgi?id=440590 --- Comment #12 from Karsten de Freese --- Finally, success :-) Basically following the same process as below, I used a 7.2.0 AppImage to open the database (as opposed to the installed 7.3.0). After the manual upgrade was run, and the 7.2.0 AppImage terminated, I could successfully launch 7.3.0 without obvious issues so far. So the key point appears to be to use a *working* digikam installation to open the database before upgrade. Maybe this has impact on the automatic update to be built into 7.4.0? Thanks again for your support! - Karsten -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440590] digikam 7.3.0 fails to start: cannot process schema initialization
https://bugs.kde.org/show_bug.cgi?id=440590
--- Comment #11 from Karsten de Freese ---
No success yet - I could restore the original behaviour, and run the manual
upgrade,
but digikam fails to start with the upgraded database.
This is what I did (all using the installed copy of digikam 7.3.0):
- I restored
-- $HOME/.local/share/digikam/
-- $HOME/.config/digikam*
-- the database directory (/var/lib/digikam_db in my case)
to the state before the update.
- I started digikam 7.3.0 (local installation)
The original error messages popped up - so far as expected.
("Failed to update the database schema from version 12 to version 13...")
- while the error messages were still shown, a manual database upgrade ran
successfully
("mariadb-upgrade
--socket=/home/karsten/.local/share/digikam/db_misc/mysql.socket")
- I clicked ok the digikam error messages and digikam terminated after a while
=> so far so good
- BUT: Starting digikam again did result in the error seen yesterday:
"An error occurred during the internal server start.
Details:
Database process exited unexpectedly during initial connection.
Executable: /usr/sbin/mysqld
Arguments: --defaults-file=/home/karsten/.local/share/digikam/mysql.conf,
--datadir=/var/lib/digikam_db/MySQL/.mysql.digikam/db_data,
--socket=/home/karsten/.local/share/digikam/db_misc/mysql.socket
Process error: Process crashed"
(formatting by myself)
The debug output in the terminal at this point:
digikam.widgets: Use installed icons
digikam.general: Switch to widget style: ""
digikam.general: Switch to application font: QFont(Noto
Sans,10,-1,5,50,0,0,0,0,0)
digikam.general: AlbumWatch is disabled
digikam.general: Database Parameters:
Type: "QMYSQL"
DB Core Name: "digikam"
DB Thumbs Name:"digikam"
DB Face Name: "digikam"
DB Similarity Name:"digikam"
Connect Options:
"UNIX_SOCKET=/home/karsten/.local/share/digikam/db_misc/mysql.socket"
Host Name: ""
Host port: -1
Internal Server: true
Internal Server Path: "/var/lib/digikam_db/MySQL"
Internal Server Admin Cmd: "mysqladmin"
Internal Server Serv Cmd: "/usr/sbin/mysqld"
Internal Server Init Cmd: "mysql_install_db"
Username: "root"
Password: ""
digikam.databaseserver: Database Parameters:
Type: "QMYSQL"
DB Core Name: "digikam"
DB Thumbs Name:"digikam"
DB Face Name: "digikam"
DB Similarity Name:"digikam"
Connect Options:
"UNIX_SOCKET=/home/karsten/.local/share/digikam/db_misc/mysql.socket"
Host Name: ""
Host port: -1
Internal Server: true
Internal Server Path: "/var/lib/digikam_db/MySQL"
Internal Server Admin Cmd: "mysqladmin"
Internal Server Serv Cmd: "/usr/sbin/mysqld"
Internal Server Init Cmd: "mysql_install_db"
Username: "root"
Password: ""
digikam.databaseserver: Internal Server data path:
"/var/lib/digikam_db/MySQL/.mysql.digikam/db_data"
digikam.databaseserver: The mysql configuration was already up-to-date:
"/home/karsten/.local/share/digikam/mysql.conf"
digikam.databaseserver: Database server: "/usr/sbin/mysqld"
("--defaults-file=/home/karsten/.local/share/digikam/mysql.conf",
"--datadir=/var/lib/digikam_db/MySQL/.mysql.digikam/db_data",
"--socket=/home/karsten/.local/share/digikam/db_misc/mysql.socket")
digikam.databaseserver: "Database process exited unexpectedly during initial
connection."
digikam.databaseserver: Executable: "/usr/sbin/mysqld"
digikam.databaseserver: Arguments:
"--defaults-file=/home/karsten/.local/share/digikam/mysql.conf,
--datadir=/var/lib/digikam_db/MySQL/.mysql.digikam/db_data,
--socket=/home/karsten/.local/share/digikam/db_misc/mysql.socket"
digikam.databaseserver: Stdout: ""
digikam.databaseserver: Stderr: "2021-08-05 12:13:56 0 [Note] /usr/sbin/mysqld
(mysqld 10.5.10-MariaDB-log) starting as process 29222 ...\n"
digikam.databaseserver: Exit code: 6
digikam.databaseserver: Process error: "Process crashed"
digikam.databaseserver: Cannot start internal database server
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 440590] digikam 7.3.0 fails to start: cannot process schema initialization
https://bugs.kde.org/show_bug.cgi?id=440590 --- Comment #9 from Karsten de Freese --- under /var/lib/digikam_db/MySQL there is (only) .mysql.digikam/db_data/: karsten@osl-i5:~/Downloads> ls -al /var/lib/digikam_db/MySQL/.mysql.digikam/db_data/ total 156M drwxr-xr-x 1 karsten karsten 736 Aug 4 22:36 . drwxr-xr-x 1 karsten karsten 14 Jul 6 2018 .. drwx-- 1 karsten karsten 2,5K Aug 4 18:51 digikam drwx-- 1 karsten karsten 2,7K Aug 4 18:23 mysql drwx-- 1 karsten karsten 12 Aug 4 18:23 performance_schema drwx-- 1 karsten karsten0 Jul 6 2018 test -rw-rw 1 karsten karsten 80K Aug 4 18:39 aria_log.0001 -rw-rw 1 karsten karsten 52 Aug 4 18:39 aria_log_control -rw-rw 1 karsten karsten 9,1K Aug 4 18:39 ib_buffer_pool -rw-rw 1 karsten karsten 76M Aug 4 18:39 ibdata1 -rw-rw 1 karsten karsten 64M Aug 4 22:36 ib_logfile0 -rw-rw 1 karsten karsten 12M Aug 4 22:36 ibtmp1 -rw-rw 1 karsten karsten0 Jul 6 2018 multi-master.info -rw-rw 1 karsten karsten 1,7K Aug 4 16:01 mysql-bin.000141 -rw-rw 1 karsten karsten 1,7K Aug 4 16:01 mysql-bin.000142 -rw-rw 1 karsten karsten 1,7K Aug 4 16:07 mysql-bin.000143 -rw-rw 1 karsten karsten 2,9K Aug 4 16:59 mysql-bin.000144 -rw-rw 1 karsten karsten 365 Aug 4 16:59 mysql-bin.000145 -rw-rw 1 karsten karsten 1,7K Aug 4 16:59 mysql-bin.000146 -rw-rw 1 karsten karsten 1,7K Aug 4 17:16 mysql-bin.000147 -rw-rw 1 karsten karsten 2,9K Aug 4 18:13 mysql-bin.000148 -rw-rw 1 karsten karsten 342 Aug 4 18:13 mysql-bin.000149 -rw-rw 1 karsten karsten 1,6K Aug 4 18:15 mysql-bin.000150 -rw-rw 1 karsten karsten 49K Aug 4 18:39 mysql-bin.000151 -rw-rw 1 karsten karsten 209 Aug 4 18:30 mysql-bin.index -rw-rw 1 karsten karsten 11 Aug 4 18:39 mysql-bin.state -rw-rw 1 karsten karsten 8,7K Aug 4 22:36 mysql.err -rw-r--r-- 1 karsten karsten 3,3M Aug 4 22:36 mysql.err.old -rw-r--r-- 1 karsten karsten 16 Aug 4 18:23 mysql_upgrade_info is this what's expected? Anyway, I'm afraid that my configuration is indeed corrupted by now. So I should see what I can collect from backups now, and restart with a 7.2.0 AppImage just to have a clean start. Could you point me to the files/directories I'd need to recover? - $HOME/.local/share/digikam/ - the Internal Server Path (currently set to "/var/lib/digikam_db/MySQL" in my config) (is this the same path configred in the 'Database Configuration' dialogue?) - probably some more? Thanks very much for your help! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440590] digikam 7.3.0 fails to start: cannot process schema initialization
https://bugs.kde.org/show_bug.cgi?id=440590
--- Comment #7 from Karsten de Freese ---
ok, I think that's what I've done, but let's try again..
I start 7.3.0 via CLI:
- on the CLI:
karsten@osl-i5:~/Downloads> digikam
digikam.widgets: Use installed icons
digikam.general: Switch to widget style: ""
digikam.general: Switch to application font: QFont(Noto
Sans,10,-1,5,50,0,0,0,0,0)
digikam.general: AlbumWatch is disabled
digikam.general: Database Parameters:
Type: "QMYSQL"
DB Core Name: "digikam"
DB Thumbs Name:"digikam"
DB Face Name: "digikam"
DB Similarity Name:"digikam"
Connect Options:
"UNIX_SOCKET=/home/karsten/.local/share/digikam/db_misc/mysql.socket"
Host Name: ""
Host port: -1
Internal Server: true
Internal Server Path: "/var/lib/digikam_db/MySQL"
Internal Server Admin Cmd: "mysqladmin"
Internal Server Serv Cmd: "/usr/sbin/mysqld"
Internal Server Init Cmd: "mysql_install_db"
Username: "root"
Password: ""
digikam.databaseserver: Database Parameters:
Type: "QMYSQL"
DB Core Name: "digikam"
DB Thumbs Name:"digikam"
DB Face Name: "digikam"
DB Similarity Name:"digikam"
Connect Options:
"UNIX_SOCKET=/home/karsten/.local/share/digikam/db_misc/mysql.socket"
Host Name: ""
Host port: -1
Internal Server: true
Internal Server Path: "/var/lib/digikam_db/MySQL"
Internal Server Admin Cmd: "mysqladmin"
Internal Server Serv Cmd: "/usr/sbin/mysqld"
Internal Server Init Cmd: "mysql_install_db"
Username: "root"
Password: ""
digikam.databaseserver: Internal Server data path:
"/var/lib/digikam_db/MySQL/.mysql.digikam/db_data"
digikam.databaseserver: The mysql configuration was already up-to-date:
"/home/karsten/.local/share/digikam/mysql.conf"
digikam.databaseserver: Database server: "/usr/sbin/mysqld"
("--defaults-file=/home/karsten/.local/share/digikam/mysql.conf",
"--datadir=/var/lib/digikam_db/MySQL/.mysql.digikam/db_data",
"--socket=/home/karsten/.local/share/digikam/db_misc/mysql.socket")
digikam.databaseserver: "Database process exited unexpectedly during initial
connection."
digikam.databaseserver: Executable: "/usr/sbin/mysqld"
digikam.databaseserver: Arguments:
"--defaults-file=/home/karsten/.local/share/digikam/mysql.conf,
--datadir=/var/lib/digikam_db/MySQL/.mysql.digikam/db_data,
--socket=/home/karsten/.local/share/digikam/db_misc/mysql.socket"
digikam.databaseserver: Stdout: ""
digikam.databaseserver: Stderr: "2021-08-04 21:31:44 0 [Note] /usr/sbin/mysqld
(mysqld 10.5.10-MariaDB-log) starting as process 16738 ...\n"
digikam.databaseserver: Exit code: 6
digikam.databaseserver: Process error: "Process crashed"
digikam.databaseserver: Cannot start internal database server
- an error popup window occurs with text "... Database process exited
unexpectedly during initial connection.Executable:
/usr/sbin/mysqldArguments:
--defaults-file=/home/karsten/.local/share/digikam/mysql.conf,
--datadir=/var/lib/digikam_db/MySQL/.mysql.digikam/db_data,
--socket=/home/karsten/.local/share/digikam/db_misc/mysql.socketProcess
error: Process crashed"
- I keep the error popup as it is and start the upgrade in a 2nd terminal:
karsten@osl-i5:/data/karsten/Downloads> mariadb-upgrade
--socket=/home/karsten/.local/share/digikam/db_misc/
Version check failed. Got the following error when calling the 'mysql' command
line client
ERROR 2002 (HY000): Can't connect to local MySQL server through socket
'/home/karsten/.local/share/digikam/db_misc/' (111)
FATAL ERROR: Upgrade failed
(-- no new output on the digikam CLI)
- I click ok on the error message, then the 'Database Configuration' dialog
appears:
-- location of database files: /var/lib/digikam_db/MySQL
-- all mysql binaries have checkmarks in the first column
-- on the digikam CLI:
digikam.general: Testing "mysql_install_db" ...
digikam.general: Found "mysql_install_db"
digikam.general: Testing "mysqladmin" ...
digikam.general: Found "mysqladmin"
digikam.general: Testing "mysqld" ...
digikam.general: Testing "mysqld" ...
digikam.general: Testing "/usr/bin/mysqld" ...
digikam.general: All Binaries Found : false
digikam.general: Testing "/usr/sbin/mysqld" ...
digikam.general: Found "
[digikam] [Bug 440590] digikam 7.3.0 fails to start: cannot process schema initialization
https://bugs.kde.org/show_bug.cgi?id=440590 --- Comment #5 from Karsten de Freese --- A restart did not change the situation unfortunately, and trying to run the manual update command while the installed 7.3.0 was showing its error message still did not work (this is what I understood from https://mail.kde.org/pipermail/digikam-users/2021-July/032479.html): karsten@osl-i5:~> mariadb-upgrade --socket=/home/karsten/.local/share/digikam/db_misc/ Version check failed. Got the following error when calling the 'mysql' command line client ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/home/karsten/.local/share/digikam/db_misc/' (111) FATAL ERROR: Upgrade failed (Actually directory /home/karsten/.local/share/digikam/db_misc/ is empty at this moment.) When I start the 7.4.0 AppImage, I get the same error message, and when closing the message, the 'Database Configuration' window shows mysqld as missing. Does this point to something? Which Mariadb server version should I have installed? Currently this is 10.5.10. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440590] digikam 7.3.0 fails to start: cannot process schema initialization
https://bugs.kde.org/show_bug.cgi?id=440590 --- Comment #3 from Karsten de Freese --- Thanks for the ultra-quick reply, which helped me move on, but with no good result yet.. - I tried the manual update first. Directory /home/karsten/.local/share/digikam/db_misc/ was empty, and probably because of this the upgrade fails (as described by Jens in one of his earlier posts). - Then I downloaded the 7.4.0 AppImage. It did actually produce the same GUI error messages as the 7.3.0 installation. - Erroneously, I started the manual update again while the GUI error messages from the 7.4.0 AppImage were still open, and the manual update succeeded then. - After closing the 7.4.0 error messages I started the installed 7.3.0 version, which produced: "An error occurred during the internal server start. Details: Database process exited unexpectedly during initial connection.Executable: /usr/sbin/mysqldArguments: --defaults-file=/home/karsten/.local/share/digikam/mysql.conf, --datadir=/var/lib/digikam_db/MySQL/.mysql.digikam/db_data, --socket=/home/karsten/.local/share/digikam/db_misc/mysql.socketProcess error: Process crashed" but after closing the error message and confirming the database configuration, digikam continued to start up correctly ONCE. A second start of digikam however resulted in the same error messsage. Closing the message window brings up the database configuration window, and confirming the current configuration brings back the error message etc. etc. The path to db files is set to /var/lib/digikam_db/MySQL. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440590] New: digikam 7.3.0 fails to start: cannot process schema initialization
https://bugs.kde.org/show_bug.cgi?id=440590
Bug ID: 440590
Summary: digikam 7.3.0 fails to start: cannot process schema
initialization
Product: digikam
Version: 7.3.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: grave
Priority: NOR
Component: Database-Schema
Assignee: digikam-bugs-n...@kde.org
Reporter: karsten.defre...@posteo.de
Target Milestone: ---
SUMMARY
After installing OpenSUSE tumbleweed snapshot 20210727 (which provides digikam
7.3.0) on top of an earlier installation with digikam 7.2.0, digikam fails to
start during 'scanning collections'with GUI message
"Failed to update the database schema from version 12 to version 13. Please
read the error messages printed on the console and report this error as a bug
at bugs.kde.org."
STEPS TO REPRODUCE
1. a digikam 7.2.0 installation from e.g. tumbleweed snapshot 20210712, with a
local mySQL database, and some 10k pictures on a server in a local network
2. update to a snapshot with digikam 7.3.0 (I used 20210727)
3. try to start digikam
OBSERVED RESULT
GUI message:
"Failed to update the database schema from version 12 to version 13. Please
read the error messages printed on the console and report this error as a bug
at bugs.kde.org."
CLI message:
karsten@osl-i5:~> digikam -v
digikam 7.3.0
karsten@osl-i5:~> export QT_LOGGING_RULES="digikam*=true"
karsten@osl-i5:~> digikam
digikam.widgets: Use installed icons
digikam.general: Switch to widget style: ""
digikam.general: Switch to application font: QFont(Noto
Sans,10,-1,5,50,0,0,0,0,0)
digikam.general: AlbumWatch is disabled
digikam.general: Database Parameters:
Type: "QMYSQL"
DB Core Name: "digikam"
DB Thumbs Name:"digikam"
DB Face Name: "digikam"
DB Similarity Name:"digikam"
Connect Options:
"UNIX_SOCKET=/home/karsten/.local/share/digikam/db_misc/mysql.socket"
Host Name: ""
Host port: -1
Internal Server: true
Internal Server Path: "/var/lib/digikam_db/MySQL"
Internal Server Admin Cmd: "mysqladmin"
Internal Server Serv Cmd: "/usr/sbin/mysqld"
Internal Server Init Cmd: "mysql_install_db"
Username: "root"
Password: ""
digikam.databaseserver: Database Parameters:
Type: "QMYSQL"
DB Core Name: "digikam"
DB Thumbs Name:"digikam"
DB Face Name: "digikam"
DB Similarity Name:"digikam"
Connect Options:
"UNIX_SOCKET=/home/karsten/.local/share/digikam/db_misc/mysql.socket"
Host Name: ""
Host port: -1
Internal Server: true
Internal Server Path: "/var/lib/digikam_db/MySQL"
Internal Server Admin Cmd: "mysqladmin"
Internal Server Serv Cmd: "/usr/sbin/mysqld"
Internal Server Init Cmd: "mysql_install_db"
Username: "root"
Password: ""
digikam.databaseserver: Internal Server data path:
"/var/lib/digikam_db/MySQL/.mysql.digikam/db_data"
digikam.databaseserver: The mysql configuration was already up-to-date:
"/home/karsten/.local/share/digikam/mysql.conf"
digikam.databaseserver: Database server: "/usr/sbin/mysqld"
("--defaults-file=/home/karsten/.local/share/digikam/mysql.conf",
"--datadir=/var/lib/digikam_db/MySQL/.mysql.digikam/db_data",
"--socket=/home/karsten/.local/share/digikam/db_misc/mysql.socket")
digikam.databaseserver: Internal database server started
digikam.databaseserver: Running 0 seconds...
digikam.dbengine: Loading SQL code from config file
"/usr/share/digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected: 3 found: 3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version 12
digikam.coredb: Core database: makeUpdates 12 to 13
digikam.dbengine: Failure executing query:
""
Error messages: "QMYSQL: Unable to execute query" "Column count of mysql.proc
is wrong. Expected 21, found 20. Created with MariaDB 100215, now running
100510. Please use mariadb-upgrade to fix this error" "1558" 2
Bound values: ()
digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV12ToV13" ]
Statement [ "\nDROP PROCEDURE IF EXISTS
create_index_if_not_exists;\n" ]
digikam.coredb: Core database: schema update to V 13 failed!
digikam.coredb: Core database: cannot process schema initialization
digikam.general: KMemoryInfo: Platform identified : "LINUX"
digikam.general: KMemoryInfo: TotalRam: 16685096960
digikam.general: Allowing a cache size of 400 MB
digikam.databaseserver: Shutting down database server
digikam.databaseserver: Internal database server stopped
QThreadStorage: Thread 0x7fdb3ba0f2c0 exited after
[korganizer] [Bug 345565] completed recurring to-do recurs on wrong date
https://bugs.kde.org/show_bug.cgi?id=345565 --- Comment #5 from Karsten de Freese --- It appears that the problems can be worked around under specific conditions: - have start & due dates on the same day (e.g. via different times) - save the to-do before entering the recurrence -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 345498] monthly To-do given incorrect start and due dates
https://bugs.kde.org/show_bug.cgi?id=345498 --- Comment #5 from Karsten de Freese --- It appears that the problems can be worked around under specific conditions: - have start & due dates on the same day (e.g. via different times) - save the to-do before entering the recurrence -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 345498] monthly To-do given incorrect start and due dates
https://bugs.kde.org/show_bug.cgi?id=345498 --- Comment #4 from Karsten de Freese --- still an issue with Korganizer 5.12.3 (I'm using Tumbleweed) -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 345565] completed recurring to-do recurs on wrong date
https://bugs.kde.org/show_bug.cgi?id=345565 Karsten de Freese changed: What|Removed |Added CC||kars...@maxi-dsl.de --- Comment #4 from Karsten de Freese --- still an issue with Korganizer 5.12.3 (I'm using Tumbleweed) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 Karsten de Freese changed: What|Removed |Added CC||kars...@maxi-dsl.de -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 390024] "Compare" button not enabled on the initial dialog even after filling the file names
https://bugs.kde.org/show_bug.cgi?id=390024 Karsten de Freese changed: What|Removed |Added CC||kars...@maxi-dsl.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 318357] GROUP : group by file-names [patch]
https://bugs.kde.org/show_bug.cgi?id=318357 Karsten de Freese <kars...@maxi-dsl.de> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #20 from Karsten de Freese <kars...@maxi-dsl.de> --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 345498] monthly To-do given incorrect start and due dates
https://bugs.kde.org/show_bug.cgi?id=345498 Karsten de Freese <kars...@maxi-dsl.de> changed: What|Removed |Added CC||kars...@maxi-dsl.de --- Comment #2 from Karsten de Freese <kars...@maxi-dsl.de> --- I can confirm this issue with KOrganizer 5.3 KDE Applications 16.08.2 OpenSUSE leap 42.2 also for other frequencies of recurrence. When setting up a non-recurring to-do, everything seems to work as expected - I can set start dates, due dates and reminders without the different settings influencing each other. However if the to-do is set to recurring, response to the settings is erratic. An example: - I set up a to-do, starting the next day (at a specific time), and due one day later. A reminder is set at 15min before due time. - the to-do is shown correctly in the to-do list view, and also more detailed via the 'show' context menu entry - when I add a weekly recurrence, start and due dates are mysteriously moved by two days in the to-do list view, while via the 'show' context menu only the due date is shifted, and only by one day.. In other cases I've also seen the reminder being changed in addition, recurrence setting being greyed out, or also an error messages when trying to save the modified task (something like 'only allocated resources are allowed to make changes', I can't reproduce this right now). The behavior does seem independent of the calendar type I select - local personal calendar vs. CalDAV -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376351] create a tool to automatically group jpeg and raw images with same name
https://bugs.kde.org/show_bug.cgi?id=376351 --- Comment #5 from Karsten de Freese <kars...@maxi-dsl.de> --- thanks for the quick help! 'context menu select group -> group selected by type' did exactly what I was looking for. This function did not catch my attention before, probably because I was assuming that it would do the same thing as 'view -> group pictures -> by format', instead of the slightly different wording. With the changed UI string this will certainly be more obvious..! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376351] New: create a tool to automatically group jpeg and raw images with same name
https://bugs.kde.org/show_bug.cgi?id=376351 Bug ID: 376351 Summary: create a tool to automatically group jpeg and raw images with same name Product: digikam Version: 5.4.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: kars...@maxi-dsl.de Target Milestone: --- hi digikam team, I've just moved my photo collection from shotwell to digikam, for the fantastic number of interesting features, and most importantly, the option to use a central mysql database. There's one thing I’m missing though, and I may very well just not have found out how to do it: I'd like to group jpeg and raw files of the same photo, as I usually have my camera set to produce both formats for each shot. With my existing photo collection, it's not really feasible to do this by hand. I've seen ticket 126149, but I'm not able to find the functionality I understand from this ticket in digikam 5.4 - instead, grouping images by file type (view/group pictures/by format) just separates them into two lists for jpeg and raw. So what am I looking for: - a way to combine files with same filename, but different 'picture type' extensions into a group (in my & similar cases it will be exactly two files with the same date/time, and extensions .JPG and e.g. .ORF) - either put the .JPG on top or make it configurable - this could be done automatically for all jpeg/raw pairs (I understand that this is what is described in 126149?) - or as a BQM tool to be run manually (in this case, ideally this functionality should also be available during image download) There are quite some similar feature requests, most already resolved, so please excuse me if I just don't see the obvious.. thanks for looking into this - Karsten -- You are receiving this mail because: You are watching all bug changes.
