[digikam] [Bug 426888] Digikam crashes shortly after I attempt to start it
https://bugs.kde.org/show_bug.cgi?id=426888 Steven P. Ulrick changed: What|Removed |Added Version|unspecified |7.2.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426888] Digikam crashes shortly after I attempt to start it
https://bugs.kde.org/show_bug.cgi?id=426888 --- Comment #2 from Steven P. Ulrick --- Digikam scanned my rather large directory of photos and then promptly crashed when it finished. Here is the backtrace that was produced after Digikam finished scanning my photos and then proceeded to crash: Application: digiKam (digikam), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3c1d253a00 (LWP 2213549))] Thread 7 (Thread 0x7f3c0092c700 (LWP 2213690)): #0 0x7f3c3c8abd45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3c3cd19943 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #2 0x7f3c3cd199d1 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #3 0x7f3c3ef8a3c3 in Digikam::ParkingThread::run() () at /usr/local/spu/kde/kde-20200922/lib64/libdigikamcore.so.7.2.0 #4 0x7f3c3cd13e26 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f3c3c8a54e2 in start_thread () at /lib64/libpthread.so.0 #6 0x7f3c3c7d46c3 in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f3c0112d700 (LWP 2213595)): #0 0x7f3c3c8abd45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3c3cd19943 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #2 0x7f3c3cd199d1 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #3 0x7f3c4001d5e4 in Digikam::ScanController::run() () at /usr/local/spu/kde/kde-20200922/lib64/libdigikamgui.so.7.2.0 #4 0x7f3c3cd13e26 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f3c3c8a54e2 in start_thread () at /lib64/libpthread.so.0 #6 0x7f3c3c7d46c3 in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f3c0328c700 (LWP 2213553)): #0 0x7f3c3c79b6b7 in clock_gettime@GLIBC_2.2.5 () at /lib64/libc.so.6 #1 0x7f3c3cf18095 in qt_gettime() () at /lib64/libQt5Core.so.5 #2 0x7f3c3cf16bdd in QTimerInfoList::updateCurrentTime() () at /lib64/libQt5Core.so.5 #3 0x7f3c3cf16fe9 in QTimerInfoList::timerWait(timespec&) () at /lib64/libQt5Core.so.5 #4 0x7f3c3cf18554 in timerSourcePrepareHelper(GTimerSource*, int*) () at /lib64/libQt5Core.so.5 #5 0x7f3c3cf18602 in timerSourcePrepare(_GSource*, int*) () at /lib64/libQt5Core.so.5 #6 0x7f3c323cedea in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #7 0x7f3c323cf79b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #8 0x7f3c323cf9a3 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #9 0x7f3c3cf188a3 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #10 0x7f3c3cec223b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #11 0x7f3c3cd12cd5 in QThread::exec() () at /lib64/libQt5Core.so.5 #12 0x7f3c3df8ef6a in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #13 0x7f3c3cd13e26 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #14 0x7f3c3c8a54e2 in start_thread () at /lib64/libpthread.so.0 #15 0x7f3c3c7d46c3 in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f3c0ca4b700 (LWP 2213552)): #0 0x7f3c3c8abd45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3c0e4a6edb in util_queue_thread_func () at /usr/lib64/dri/r600_dri.so #2 0x7f3c0e4a6aeb in impl_thrd_routine () at /usr/lib64/dri/r600_dri.so #3 0x7f3c3c8a54e2 in start_thread () at /lib64/libpthread.so.0 #4 0x7f3c3c7d46c3 in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f3c0db9e700 (LWP 2213551)): #0 0x7f3c3c8abd45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3c0e4a6edb in util_queue_thread_func () at /usr/lib64/dri/r600_dri.so #2 0x7f3c0e4a6aeb in impl_thrd_routine () at /usr/lib64/dri/r600_dri.so #3 0x7f3c3c8a54e2 in start_thread () at /lib64/libpthread.so.0 #4 0x7f3c3c7d46c3 in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f3c0ff7d700 (LWP 2213550)): #0 0x7f3c3c7c9a5f in poll () at /lib64/libc.so.6 #1 0x7f3c2efab38a in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f3c2efacfea in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f3c100a3d48 in QXcbEventQueue::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f3c3cd13e26 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f3c3c8a54e2 in start_thread () at /lib64/libpthread.so.0 #6 0x7f3c3c7d46c3 in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f3c1d253a00 (LWP 2213549)): [KCrash Handler] #4 0x7f3c3c70f625 in raise () at /lib64/libc.so.6 #5 0x7f3c3c6f88d9 in abort () at /lib64/libc.so.6 #6 0x7f3c3caf8756 in __gnu_cxx::__verbose_terminate_handler() [clone .cold] () at /lib64/libstdc++.so.6 #7 0x7f3c3cb046dc in __cxxabiv1::__terminate(void (*)()) () at /lib64/libstdc++.so.6 #8 0x7f3c3cb04747 in () at /lib64/libstdc++.so.6 #9 0x7f3c3cb049b9 in () at /lib64/libs
[digikam] [Bug 426888] Digikam crashes shortly after I attempt to start it
https://bugs.kde.org/show_bug.cgi?id=426888 --- Comment #1 from Steven P. Ulrick --- When I delete digikamrc & digikam_systemrc and attempt to restart Digikam, it starts up fine. We'll see what happens now. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426888] New: Digikam crashes shortly after I attempt to start it
https://bugs.kde.org/show_bug.cgi?id=426888 Bug ID: 426888 Summary: Digikam crashes shortly after I attempt to start it Product: digikam Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: meow8...@gmail.com Target Milestone: --- Application: digikam (7.2.0-beta1) Qt Version: 5.13.2 Frameworks Version: 5.70.0 Operating System: Linux 5.8.9-101.fc31.x86_64 x86_64 Windowing system: X11 Distribution: Fedora 31 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: I attempted to open Digikam, the splash screen came up for a few seconds, and then it crashed. It does the exact same thing every time I try to start Digikam. I compile Digikam from the GIT repo. The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f508206fa00 (LWP 2213029))] Thread 7 (Thread 0x7f50625ed700 (LWP 2213036)): #0 0x7f50a16c7d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f50a1b35943 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #2 0x7f50a1b359d1 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #3 0x7f50a3da63c3 in Digikam::ParkingThread::run() () at /usr/local/spu/kde/kde-20200922/lib64/libdigikamcore.so.7.2.0 #4 0x7f50a1b2fe26 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f50a16c14e2 in start_thread () at /lib64/libpthread.so.0 #6 0x7f50a15f06c3 in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f5062dee700 (LWP 2213034)): #0 0x7f50a16c7d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f50a1b35943 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #2 0x7f50a1b359d1 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #3 0x7f50a4e395e4 in Digikam::ScanController::run() () at /usr/local/spu/kde/kde-20200922/lib64/libdigikamgui.so.7.2.0 #4 0x7f50a1b2fe26 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f50a16c14e2 in start_thread () at /lib64/libpthread.so.0 #6 0x7f50a15f06c3 in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f5063fff700 (LWP 2213033)): #0 0x7f50a16cb87c in read () at /lib64/libpthread.so.0 #1 0x7f50972335af in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f50971eb3b7 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f50971eb812 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f50971eb9a3 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f50a1d348a3 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f50a1cde23b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f50a1b2ecd5 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f50a2daaf6a in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #9 0x7f50a1b2fe26 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7f50a16c14e2 in start_thread () at /lib64/libpthread.so.0 #11 0x7f50a15f06c3 in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f5068aed700 (LWP 2213032)): #0 0x7f50a16c7d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f506f2afedb in util_queue_thread_func () at /usr/lib64/dri/r600_dri.so #2 0x7f506f2afaeb in impl_thrd_routine () at /usr/lib64/dri/r600_dri.so #3 0x7f50a16c14e2 in start_thread () at /lib64/libpthread.so.0 #4 0x7f50a15f06c3 in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f5069c34700 (LWP 2213031)): #0 0x7f50a16c7d45 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f506f2afedb in util_queue_thread_func () at /usr/lib64/dri/r600_dri.so #2 0x7f506f2afaeb in impl_thrd_routine () at /usr/lib64/dri/r600_dri.so #3 0x7f50a16c14e2 in start_thread () at /lib64/libpthread.so.0 #4 0x7f50a15f06c3 in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f5074d99700 (LWP 2213030)): #0 0x7f50a15e5a5f in poll () at /lib64/libc.so.6 #1 0x7f5093dc738a in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f5093dc8fea in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f5074ebfd48 in QXcbEventQueue::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f50a1b2fe26 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f50a16c14e2 in start_thread () at /lib64/libpthread.so.0 #6 0x7f50a15f06c3 in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f508206fa00 (LWP 2213029)): [KCrash Handler] #4 0x7f50a152b625 in raise () at /lib64/libc.so.6 #5 0x7
[kio] [Bug 362873] cannot open file (or folder) after rename
https://bugs.kde.org/show_bug.cgi?id=362873 Steven P. Ulrick changed: What|Removed |Added CC||meow8...@gmail.com --- Comment #8 from Steven P. Ulrick --- I'm seeing the same behavior on Fedora 23. Fully updated and rebooted as of this morning. -- You are receiving this mail because: You are watching all bug changes.
