Bug 24115

Summary: fritzing - missing suggests/depends on qt5-database-plugin-sqlite
Product: Mageia Reporter: Christian Lohmaier <lohmaier+mageia>
Component: RPM PackagesAssignee: All Packagers <pkg-bugs>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: fri, geiger.david68210, lists.jjorge, loginov_alex, marja11
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: fritzing-0.9.3b-1.git20181017.mga7.src.rpm CVE:
Status comment:

Description Christian Lohmaier 2019-01-02 18:54:08 CET
Description of problem:
While apparently not strictly needed for running fritzing, not having the qt-plugin for sqlite installed causes fritzing to complain about it in terminal (lots of

QSqlQuery::prepare: database not open

lines)

How reproducible:
100%

Steps to Reproduce:
0. don't install/remove qt5-database-plugin-sqlite
1. cd /usr/share/fritzing/parts/ , launch fritzing (see bug#24114 )
2. see it complain about "QSqlDatabase: QSQLITE driver not loaded" and complain about "database not open" many times
3. close fritzing, install qt5-database-plugin-sqlite and do the same thing again
 → now no complaints to terminal, and it seems it uses sqlite to build a cache of the parts, so switching between different sets is faster (but that could also be side-effect of disk-cache, didn't bother to do proper benchmark)
Comment 1 Marja Van Waes 2019-01-02 21:28:20 CET
Assigning to all packagers collectively, since there is no registered maintainer for this package.

CC'ing some committers.

Assignee: bugsquad => pkg-bugs
CC: (none) => geiger.david68210, lists.jjorge, loginov_alex, marja11

Comment 2 David GEIGER 2019-01-02 22:23:10 CET
Should be fixed with fritzing-0.9.3b-2.git20181017.mga7!
Morgan Leijström 2019-01-03 00:26:20 CET

CC: (none) => fri

Comment 3 Christian Lohmaier 2019-01-03 12:14:39 CET
thanks for the quick fix, verified with fritzing-0.9.3b-3.git20181017.mga7
Comment 4 Morgan Leijström 2019-01-03 12:16:17 CET
Thank you both :)
Comment 5 David GEIGER 2019-01-04 08:23:45 CET
Fixed? or not? if yes please close this bug!
Comment 6 David GEIGER 2019-01-06 13:31:57 CET
Closing of this bug!

Resolution: (none) => FIXED
Status: NEW => RESOLVED