Bug 319420

Summary:	failed to update the database schema from version 5 to version 6
Product:	[Applications] digikam	Reporter:	tim <tim>
Component:	Database-Schema	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	grave	CC:	caulier.gilles
Priority:	NOR
Version First Reported In:	3.1.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:	7.0.0
Sentry Crash Report:
Attachments:	Screenshot of error

Description tim 2013-05-06 17:49:16 UTC

When loading digikam from console or within kde the following error message appears. Albums are unusable and import or scanning system for media files cannot take place.

Reproducible: Always

Steps to Reproduce:
1. Go to console
2. execute digikam as user
3. crash and burn :(
Actual Results:  
tim@wykeradio:~> digikam
Fontconfig warning: "/etc/fonts/conf.d/56-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work.
digikam(7661)/digikam (core): Schema update to V 6 failed! 
libv4l2: error getting pixformat: Invalid argument
"/org/freedesktop/UDisks2/drives/ST1000LM010_9YH146_W100X8J2" : property "DeviceNumber" does not exist 
"/org/freedesktop/UDisks2/drives/ST1000LM010_9YH146_W100X8J2" : property "Device" does not exist 
"/org/freedesktop/UDisks2/drives/ST3160023AS_5MT0PZ27" : property "DeviceNumber" does not exist 
"/org/freedesktop/UDisks2/drives/ST3160023AS_5MT0PZ27" : property "Device" does not exist 
"/org/freedesktop/UDisks2/drives/ST31000528AS_9VP59X3B" : property "DeviceNumber" does not exist 
"/org/freedesktop/UDisks2/drives/ST31000528AS_9VP59X3B" : property "Device" does not exist 
tim@wykeradio:~> 

Expected Results:  
Should of loaded surely...

Linux 3.7.10-1.4-pae #1 SMP Fri Apr 19 12:06:34 UTC 2013 (8ef74f8) i686 athlon i386 GNU/Linux

Comment 1 tim 2013-05-06 17:50:53 UTC

Created attachment 79737 [details]
Screenshot of error

Comment 2 caulier.gilles 2013-11-20 22:16:29 UTC


*** This bug has been marked as a duplicate of bug 283502 ***

Comment 3 caulier.gilles 2020-01-01 21:42:33 UTC

Not reproducible with 7.0.0 beta1.