Application: digikam (5.6.0) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.74-18.20-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: When installing OpenSuse 42.2 and updating Digikam to its latest version 5.6 the program can not connect to the existing database in my the user that already came using the application and CAN NOT OPEN THE PROGRAM. He stays for hours "tried to connect to the database" and nothing. The strange thing is that when creating a new user and log in with this new user, when opening Digikam for the first time the program works perfect. How can I do not to lose my database and the thousands of tags and saved things I had in digikam? (4 years of information) The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fea46230a00 (LWP 15345))] Thread 4 (Thread 0x7fe9fffff700 (LWP 15351)): #0 0x00007fea3e3910bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x00007fea41e4265b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x00007fea4577edd0 in Digikam::ScanController::run() () at /usr/lib64/libdigikamgui.so.5.6.0 #3 0x00007fea41e419e9 in () at /usr/lib64/libQt5Core.so.5 #4 0x00007fea3e38c744 in start_thread () at /lib64/libpthread.so.0 #5 0x00007fea41538aad in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fea054bb700 (LWP 15350)): #0 0x00007fea4152c28d in read () at /lib64/libc.so.6 #1 0x00007fea38212670 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fea381d1e49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fea381d22a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x00007fea381d242c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x00007fea4205433b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #6 0x00007fea42001feb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #7 0x00007fea41e3cf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x00007fea3e5b8295 in () at /usr/lib64/libQt5DBus.so.5 #9 0x00007fea41e419e9 in () at /usr/lib64/libQt5Core.so.5 #10 0x00007fea3e38c744 in start_thread () at /lib64/libpthread.so.0 #11 0x00007fea41538aad in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fea0d214700 (LWP 15349)): #0 0x00007fea4153020d in poll () at /lib64/libc.so.6 #1 0x00007fea329783e2 in () at /usr/lib64/libxcb.so.1 #2 0x00007fea32979fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x00007fea0e6e8839 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x00007fea41e419e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x00007fea3e38c744 in start_thread () at /lib64/libpthread.so.0 #6 0x00007fea41538aad in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fea46230a00 (LWP 15345)): [KCrash Handler] #6 0x00007fea44871c90 in Digikam::BdEngineBackend::status() const () at /usr/lib64/libdigikamcore.so.5.6.0 #7 0x00007fea434d5e14 in Digikam::CoreDbAccess::CoreDbAccess() () at /usr/lib64/libdigikamdatabase.so.5.6.0 #8 0x00007fea43474037 in Digikam::CollectionScanner::databaseInitialScanDone() () at /usr/lib64/libdigikamdatabase.so.5.6.0 #9 0x00007fea457cae18 in Digikam::DigikamApp::DigikamApp() () at /usr/lib64/libdigikamgui.so.5.6.0 #10 0x0000000000408938 in main(int, char**) (argc=1, argv=<optimized out>) at /usr/src/debug/digikam-5.6.0/core/app/main/main.cpp:236 Reported using DrKonqi
Which kind of database do you use exactly ?
Do you have the same debug trace on the console than bug #379959 ?
(In reply to caulier.gilles from comment #1) > ¿Qué tipo de base de datos utiliza exactamente? MySQL
Please try with current digiKam 5.7.0 pre version of AppImage Bundle available here : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM I just tested here with my mariadb server and all work fine. My settings : Type: "QMYSQL" DB Core Name: "digikam" DB Thumbs Name: "digikam" DB Face Name: "digikam" Connect Options: "" Host Name: "192.168.1.20" Host port: 3306 Internal Server: false Internal Server Path: "" Internal Server Serv Cmd: "" Internal Server Init Cmd: "" Username: "digikam" Password: "XXXXXXXX" Gilles Caulier
With next 5.8.0 release Mysql support have been well improved and a lots of bugs fixed. Please test with pre release 5.8.0 bundles that we provide and give us a feedback https://files.kde.org/digikam/ Thanks in advance Gilles Caulier
Can you reproduce the dysfunction using digiKam 6.0.0 pre-release bundle available here : https://files.kde.org/digikam/ Gilles Caulier
Can you reproduce the dysfunction using the last digiKam 6.0.0-beta3 just released ? https://www.digikam.org/news/2018-12-30-6.0.0-beta3_release_announcement/
Hi, Can you check if this problem still exist with last weekly bundle build of digiKam 7.0.0 available here: https://files.kde.org/digikam/ Thanks in advance Gilles Caulier
digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier
digiKam 7.2.0 official release is published with more than 360 files closed from bugzilla: https://www.digikam.org/news/2021-03-22-7.2.0_release_announcement/ Can you reproduce the dysfunction with this version ? Thanks in advance for your feedback Gilles Caulier
Hector, Stable digiKam 7.4.0 is published. Please check if problem is reproducible. https://www.digikam.org/download/ Thanks in advance
No feedback. not reproducible with 7.5.0. Closed