Your message dated Tue, 18 Feb 2020 11:32:00 +0100
with message-id <[email protected]>
and subject line Re: Bug#895937: database upgrade from schema 8 to 9 fails -
workaround
has caused the Debian Bug report #895937,
regarding digikam: database upgrade from schema 8 to 9 fails
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
895937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895937
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: digikam
Version: 4:5.9.0-1
Severity: important
Dear Digikam Maintainer,
* What led up to the situation?
Upgrading to latest Unstable Digikam version
* What exactly did you do (or not do) that was effective (or
ineffective)?
No workaround tried as Digikam exits immediately after database
migration fails.
Error messages is as follow:
"
digikam.general: AlbumWatch use QFileSystemWatcher
digikam.general: Database Parameters:
Type: "QMYSQL"
DB Core Name: "digikamdb"
DB Thumbs Name: "digikam_thumbsdb"
DB Face Name: "digikam_faces"
Connect Options: ""
Host Name: "localhost"
Host port: 3306
Internal Server: false
Internal Server Path: ""
Internal Server Serv Cmd: ""
Internal Server Init Cmd: ""
Username: "digikam"
Password: ""
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 8
digikam.coredb: Core database: makeUpdates 8 to 9
digikam.dbengine: Failure executing query:
""
Error messages: "QMYSQL: Unable to execute query" "Illegal mix of
collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for
operation '='" 1267 2
Bound values: ()
digikam.dbengine: Error while executing DBAction [
"UpdateSchemaFromV7ToV9" ] Statement [ "CALL
drop_index_if_exists('AlbumRoots', 'identifier');" ]
digikam.coredb: Core database: schema update to V 9 failed!
digikam.coredb: Core database: cannot process schema initialization
KMemoryInfo: Platform identified : "LINUX"
KMemoryInfo: TotalRam: 16826564608
digikam.general: Allowing a cache size of 200 MB
QThreadStorage: Thread 0x7f10cf629bc0 exited after QThreadStorage 11
destroyed
"
Connecting to Mariadb Digikam databases as user "digikam" works,
checking databases (mysqlcheck) reports no error.
Thank you for your time.
-- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.17.0-rc1-deb64 (SMP w/16 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr:en_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages digikam depends on:
ii digikam-data 4:5.9.0-1
ii digikam-private-libs 4:5.9.0-1
ii kipi-plugins 4:5.9.0-1
ii libc6 2.27-3
ii libgcc1 1:8-20180414-1
ii libkf5configcore5 5.44.0-1
ii libkf5coreaddons5 5.44.0-1
ii libkf5filemetadata3 5.44.0-1
ii libkf5i18n5 5.44.0-1
ii libqt5core5a 5.10.1+dfsg-5
ii libqt5gui5 5.10.1+dfsg-5
ii libqt5sql5 5.10.1+dfsg-5
ii libqt5sql5-mysql 5.10.1+dfsg-5
ii libqt5sql5-sqlite 5.10.1+dfsg-5
ii libqt5widgets5 5.10.1+dfsg-5
ii libstdc++6 8-20180414-1
ii perl 5.26.1-6
Versions of packages digikam recommends:
ii chromium [www-browser] 66.0.3359.26-2
ii ffmpegthumbs 4:17.08.3-1
ii firefox [www-browser] 59.0.2-1
ii google-chrome-stable [www-browser] 65.0.3325.181-1
ii konqueror [www-browser] 4:17.08.3-2
ii lynx [www-browser] 2.8.9dev17-1
Versions of packages digikam suggests:
pn digikam-doc <none>
ii systemsettings 4:5.12.4-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4:6.4.0+dfsg-1
On Tue, Feb 18, 2020 at 11:27:15AM +0530, [email protected] wrote:
> On 17/02/2020 22:39, Agustin Martin wrote:
> > On Sat, Apr 21, 2018 at 02:16:26AM +0530, [email protected] wrote:
> > > Since Digikam crashes on Mariadb database conversion I tried reverting to
> > > older Digikam version, but that only gave me an empty view. So the
> > > database
> > > is unusable with the previous Digikam versions.
> > > Restoring a previous database version leads to the same result: failed
> > > conversion, corruption that makes it unusable with previous Digikam
> > > version.
> > >
> > > I downloaded the Digikam 5.9 appimage from digikam.org, which fails to
> > > convert the database too, but doesn't crash. From it I was able to migrate
> > > the Mariadb database to sqlite (conversion is very slow). Using the sqlite
> > > was totally impractical due to sluggishness and high system load, so I
> > > converted it back to "external Mysql" (Mariadb) with the exact same
> > > settings
> > > in database configuration as the previous one 'user, db names...).
> > > Again conversion is slow but about twice as fast as the other way round.
> > >
> > > Important, once conversion back to Mariadb is complete, and Digikam
> > > settings
> > > have been switched back to external Mysql database, Digikam scanned all
> > > content but displayed an empty view. I needed to close and relaunch
> > > before I
> > > could see the images.
> > >
> > > I can now use Digikam 5.9 from Debian Unstable with the newly converted
> > > Mariadb external database, I did not notice any data loss, tags are intact
> > > too..
> > >
> > > So problem solved for me, the double database conversion workaround is
> > > time
> > > expensive but works.
> >
> > Hi,
> >
> > According to upstream bugtracking system
> >
> > https://bugs.kde.org/show_bug.cgi?id=393855
> >
> > this seems fixed in digikam 6.0. Since Debian sid already has 6.4.0, I
> > expect
> > this problem to be fixed in Debian.
> >
> > Can we close this bug report?
> >
> > Thanks for your contribution to Debian.
> >
> > Regards,
> >
> Hi, as far as I am concerned this bug can be closed. All new upgrades
> proceeded without any problem regarding the database.
> Currently using 6.4 from unstable with Mariadb (about 60000 photos/videos in
> the main library, + tags and faces) and having no issues.
Thanks for the feedback. Closing bug report.
--
Agustin
--- End Message ---
_______________________________________________
pkg-kde-extras mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-extras
