[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album
https://bugs.kde.org/show_bug.cgi?id=389355 --- Comment #12 from Axel Schmidt --- Log files for the error -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album
https://bugs.kde.org/show_bug.cgi?id=389355 --- Comment #11 from Axel Schmidt --- Gilles, i tried both version for linux now under (K)Ubuntu 18.04: digikam-6.2.0-git-20190503T152230-qtwebengine-x86-64.appimage digikam-6.2.0-git-20190503T152230-qtwebengine-x86-64.appimage both doesn't work. Both couldn't connect to mysql and than stops or exiting with error. The original digikam 5.6.0 from system start, can connect to mysql and work as expected and now under (K)Ubuntu 18.04 the error is gone... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album
https://bugs.kde.org/show_bug.cgi?id=389355 --- Comment #8 from Axel Schmidt --- Created attachment 120513 --> https://bugs.kde.org/attachment.cgi?id=120513=edit ErrorLog digikam-6.2.0-git-20190503T152230-qtwebengine-x86-64.appimage.log start with error can't connect to mysql and then exit with error -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album
https://bugs.kde.org/show_bug.cgi?id=389355 --- Comment #7 from Axel Schmidt --- Created attachment 120512 --> https://bugs.kde.org/attachment.cgi?id=120512=edit Errorlog digikam-6.2.0-git-20190529T102951-qtwebkit-x86-64.appimage Start with error can't connect to mysql, but mysql is working and than hang on icc profile on start screen with no more response. klick on startscreen than it disappear but no program window showed. digikam hang in tasklist without any cpu time... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album
https://bugs.kde.org/show_bug.cgi?id=389355 --- Comment #3 from Axel Schmidt <a...@asc-computer.com> --- Sorry i didn't saw your first answer! Comment #1: I'm not possible to test this problem, because i get before a exception, if i go into a album qand than stops the programm: gdb digikam GNU gdb (Ubuntu 8.0.1-0ubuntu1) 8.0.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from digikam...(no debugging symbols found)...done. (gdb) catch throw Haltepunkt 1 (throw) (gdb) run Starting program: /usr/bin/digikam [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffbffbd700 (LWP 24459)] [New Thread 0x7fffb7b68700 (LWP 24460)] [New Thread 0x7fffb6957700 (LWP 24461)] [New Thread 0x7fffb6156700 (LWP 24462)] [Thread 0x7fffb6156700 (LWP 24462) exited] [New Thread 0x7fffb6156700 (LWP 24463)] [New Thread 0x7fffa520f700 (LWP 24465)] [New Thread 0x7fff647c4700 (LWP 24466)] [New Thread 0x7fff63925700 (LWP 24467)] [New Thread 0x7fff63124700 (LWP 24468)] [New Thread 0x7fff62923700 (LWP 24469)] [New Thread 0x7fff62122700 (LWP 24470)] QFSFileEngine::open: No file name specified [New Thread 0x7fff60ebb700 (LWP 24471)] [New Thread 0x7fff4bfff700 (LWP 24472)] [New Thread 0x7fff4b7fe700 (LWP 24473)] [New Thread 0x7fff4affd700 (LWP 24474)] [New Thread 0x7fff4a7fc700 (LWP 24475)] [New Thread 0x7fff49ffb700 (LWP 24476)] [New Thread 0x7fff497fa700 (LWP 24477)] [New Thread 0x7fff48ff9700 (LWP 24478)] [New Thread 0x7fff27fff700 (LWP 24479)] [New Thread 0x7fff1f7fe700 (LWP 24480)] [New Thread 0x7fff277fe700 (LWP 24481)] [New Thread 0x7fff26ffd700 (LWP 24482)] [New Thread 0x7fff267fc700 (LWP 24483)] [New Thread 0x7fff25ffb700 (LWP 24484)] [New Thread 0x7fff257fa700 (LWP 24485)] [New Thread 0x7fff24ff9700 (LWP 24486)] [New Thread 0x7fff1700 (LWP 24487)] [New Thread 0x7fff1effd700 (LWP 24488)] [New Thread 0x7fff1e7fc700 (LWP 24489)] [New Thread 0x7fff1dffb700 (LWP 24490)] [New Thread 0x7fff1d7fa700 (LWP 24491)] [New Thread 0x7fff1cff9700 (LWP 24492)] [New Thread 0x7ffee7fff700 (LWP 24493)] [New Thread 0x7ffee77fe700 (LWP 24494)] [New Thread 0x7ffee6ffd700 (LWP 24495)] [New Thread 0x7ffee67fc700 (LWP 24496)] QFSFileEngine::open: No file name specified [New Thread 0x7ffee5ffb700 (LWP 24497)] [New Thread 0x7ffee57fa700 (LWP 24499)] [New Thread 0x7ffee4ff9700 (LWP 24500)] [New Thread 0x7ffee47f8700 (LWP 24502)] [Thread 0x7ffee4ff9700 (LWP 24500) exited] [New Thread 0x7ffee4ff9700 (LWP 24503)] [Thread 0x7ffee57fa700 (LWP 24499) exited] [Thread 0x7ffee5ffb700 (LWP 24497) exited] [Thread 0x7ffee47f8700 (LWP 24502) exited] [Thread 0x7ffee4ff9700 (LWP 24503) exited] [New Thread 0x7ffee4ff9700 (LWP 24504)] [Thread 0x7ffee4ff9700 (LWP 24504) exited] QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified [New Thread 0x7ffee4ff9700 (LWP 24505)] [Thread 0x7ffee4ff9700 (LWP 24505) exited] [New Thread 0x7ffee4ff9700 (LWP 24506)] [New Thread 0x7ffee4ff9700 (LWP 24507)] [Thread 0x7ffee4ff9700 (LWP 24506) exited] [New Thread 0x7ffee47f8700 (LWP 24508)] [New Thread 0x7ffee5ffb700 (LWP 24509)] [New Thread 0x7ffee57fa700 (LWP 24510)] [New Thread 0x7ffec2c8e700 (LWP 24511)] [New Thread 0x7ffec248d700 (LWP 24512)] [New Thread 0x7ffec1c8c700 (LWP 24513)] [New Thread 0x7ffec148b700 (LWP 24514)] [Thread 0x7ffee4ff9700 (LWP 24507) exited] [Thread 0x7ffec248d700 (LWP 24512) exited] [Thread 0x7ffec2c8e700 (LWP 24511) exited] [Thread 0x7ffec1c8c700 (LWP 24513) exited] [Thread 0x7ffee57fa700 (LWP 24510) exited] [Thread 0x7ffee5ffb700 (LWP 24509) exited] [Thread 0x7ffee47f8700 (LWP 24508) exited] [New Thread 0x7ffee47f8700 (LWP 24554)] [Thread 0x7ffee47f8700 (LWP 24554) exited] [Thread 0x7ffee7fff700 (LWP 24493) exited] [Thread 0x7ffee77fe700 (LWP 24494) exited] [Thread 0x7ffee67fc700 (LWP 24496) exited] [Thread 0x7ffee6ffd700 (LWP 24495) exited] [Thread 0x7ffec148b700 (LWP 24514) exited] [New Thread 0x7ffec148b700 (LWP 24561)] [New Thread 0x7ffee67fc700 (LWP 24562)] [Thread 0x7ffec148b700 (LWP 24561) exited] [New Thread 0x7ffec148b700 (LWP 24571)] [Thread 0x7ffec148b700 (LWP 24571) exited] [New Thread 0x7ffec148b700 (LWP 24583)] [Thread 0x7ffec148b700 (LWP 24583) exited] [New Thread 0x7ffec148b700
[digikam] [Bug 389355] New: digikam crash during metadata refresh if you at same time create an new album
https://bugs.kde.org/show_bug.cgi?id=389355 Bug ID: 389355 Summary: digikam crash during metadata refresh if you at same time create an new album Product: digikam Version: 5.6.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: a...@asc-computer.com Target Milestone: --- Application: digikam (5.6.0) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.13.0-31-generic x86_64 Distribution: Ubuntu 17.10 -- Information about the crash: First i started the maintenance -> refresh metadata and if you want during this process create a new album digicam crashed every time The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc641655380 (LWP 21347))] Thread 16 (Thread 0x7fc583950700 (LWP 24109)): #0 0x7fc639a4f072 in futex_wait_cancelable (private=, expected=0, futex_word=0x564ca34eb070) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fc639a4f072 in __pthread_cond_wait_common (abstime=0x0, mutex=0x564ca34eb020, cond=0x564ca34eb048) at pthread_cond_wait.c:502 #2 0x7fc639a4f072 in __pthread_cond_wait (cond=0x564ca34eb048, mutex=0x564ca34eb020) at pthread_cond_wait.c:655 #3 0x7fc63d8726cb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc63fef1074 in Digikam::ActionThreadBase::run() () at /usr/lib/digikam/libdigikamcore.so.5.6.0 #5 0x7fc63d87129d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc639a487fc in start_thread (arg=0x7fc583950700) at pthread_create.c:465 #7 0x7fc63cb88b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7fc5817fa700 (LWP 24100)): #0 0x7fc639a4f072 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fc5fc087b00) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fc639a4f072 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7fc5fc087ab0, cond=0x7fc5fc087ad8) at pthread_cond_wait.c:502 #2 0x7fc639a4f072 in __pthread_cond_wait (cond=0x7fc5fc087ad8, mutex=0x7fc5fc087ab0) at pthread_cond_wait.c:655 #3 0x7fc63d8726cb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc63fef1074 in Digikam::ActionThreadBase::run() () at /usr/lib/digikam/libdigikamcore.so.5.6.0 #5 0x7fc63d87129d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc639a487fc in start_thread (arg=0x7fc5817fa700) at pthread_create.c:465 #7 0x7fc63cb88b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7fc5a99fa700 (LWP 24034)): #0 0x7fc639a4f072 in futex_wait_cancelable (private=, expected=0, futex_word=0x564ca05c1970) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fc639a4f072 in __pthread_cond_wait_common (abstime=0x0, mutex=0x564ca05c1920, cond=0x564ca05c1948) at pthread_cond_wait.c:502 #2 0x7fc639a4f072 in __pthread_cond_wait (cond=0x564ca05c1948, mutex=0x564ca05c1920) at pthread_cond_wait.c:655 #3 0x7fc63d8726cb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc63fef1074 in Digikam::ActionThreadBase::run() () at /usr/lib/digikam/libdigikamcore.so.5.6.0 #5 0x7fc63d87129d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc639a487fc in start_thread (arg=0x7fc5a99fa700) at pthread_create.c:465 #7 0x7fc63cb88b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7fc5827fc700 (LWP 24006)): #0 0x7fc63cb82a49 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7fc63d8688c5 in QBasicMutex::lockInternal() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fc63d868c23 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fc63d4a5c54 in Digikam::CoreDbAccess::CoreDbAccess() () at /usr/lib/digikam/libdigikamdatabase.so.5.6.0 #4 0x7fc640e40147 in () at /usr/lib/digikam/libdigikamgui.so.5.6.0 #5 0x7fc640d707f3 in () at /usr/lib/digikam/libdigikamgui.so.5.6.0 #6 0x7fc63d86d581 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc63d87129d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc639a487fc in start_thread (arg=0x7fc5827fc700) at pthread_create.c:465 #9 0x7fc63cb88b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7fc582ffd700 (LWP 21367)): #0 0x7fc632f0f0ba in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc632f115db in g_main_context_prepare () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2
[kontact] [Bug 378864] New: Kmail 5.1.3 crashed on closing
https://bugs.kde.org/show_bug.cgi?id=378864 Bug ID: 378864 Summary: Kmail 5.1.3 crashed on closing Product: kontact Version: 5.1.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: a...@asc-computer.com Target Milestone: --- Application: kontact (5.1.3) Qt Version: 5.5.1 Operating System: Linux 4.8.0-46-generic x86_64 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: closing the application - Unusual behavior I noticed: imap inbox shows every email 2-4 times, so that kmail shows not the real 50 emails but nearly 200, but light grey and not markable, readable nor selectable, but shown in the list of emails... The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f46f3513940 (LWP 1501))] Thread 31 (Thread 0x7f46037fe700 (LWP 16211)): #0 0x7f470c79cb5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f4705fb838c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4705fb849c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f470d2df7eb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f470d286b4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f470d0a3834 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f470d0a87be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f47067e26ba in start_thread (arg=0x7f46037fe700) at pthread_create.c:333 #8 0x7f470c7a882d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 30 (Thread 0x7f4603fff700 (LWP 16209)): #0 0x7f4705ffca94 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f4705fb7f2a in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4705fb83f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4705fb849c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f470d2df7eb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f470d286b4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f470d0a3834 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f470d0a87be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f47067e26ba in start_thread (arg=0x7f4603fff700) at pthread_create.c:333 #9 0x7f470c7a882d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 29 (Thread 0x7f460ce6d700 (LWP 16202)): #0 0x7f470c79cb5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f4705fb838c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4705fb849c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f470d2df7eb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f470d286b4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f470d0a3834 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f470d0a87be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f47067e26ba in start_thread (arg=0x7f460ce6d700) at pthread_create.c:333 #8 0x7f470c7a882d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 28 (Thread 0x7f460d66e700 (LWP 16200)): #0 0x7f470c79cb5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f4705fb838c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4705fb849c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f470d2df7eb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f470d286b4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f470d0a3834 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f470d0a87be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f47067e26ba in start_thread (arg=0x7f460d66e700) at pthread_create.c:333 #8 0x7f470c7a882d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 27 (Thread 0x7f460de6f700 (LWP 16194)): #0 0x7ffdcd498939 in ?? () #1 0x7ffdcd498bd6 in clock_gettime () #2 0x7f470c7b6c86 in __GI___clock_gettime (clock_id=1, tp=0x7f460de6e9f0) at ../sysdeps/unix/clock_gettime.c:115 #3 0x7f470d158b86 in ?? ()
