[krfb] [Bug 376614] New: VNC viewer frozen desktop cursor moves Remote desktop sees cursor
https://bugs.kde.org/show_bug.cgi?id=376614 Bug ID: 376614 Summary: VNC viewer frozen desktop cursor moves Remote desktop sees cursor Product: krfb Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: grundleb...@googlemail.com Reporter: ermschmi...@yahoo.com Target Milestone: --- VNC client Viewer connects and shows a frozen screen of the desktop. Cursor moves but no response from frozen desktop. While view at remote PC you are able to use the cursor (from the client PC) to control the desktop. Linux 4.9.6-gentoo-r1. KDE 5 Plasma. This started happening after upgrade from KDE 4 to KDE 5 plasma. I'm running a VM of the same setup as the Linux 4.9.6-gentoo-r1 but have not upgraded it to KDE 5 yet. Desktop sharing works fine. It's running Linux 4.1.15-gentoo-r1 and KDE SC Version 4.14.16. I have 2 other machines that are running Gentoo Linux with KDE 5 Plasma and there exhibiting the same problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374711] New: Kwin crashed for unknown reasons
https://bugs.kde.org/show_bug.cgi?id=374711 Bug ID: 374711 Summary: Kwin crashed for unknown reasons Product: kwin Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: bill6...@alumni.rutgers.edu Target Milestone: --- Application: kwin_x11 (5.8.3) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.36-8-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: Clicked a desktop widget to open Quicken 2016 with cxoffice. Quicken did open and kwin restarted on it's own. Currently running SUSE Leap 42.2 with plasma 5 The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc99acd5940 (LWP 7646))] Thread 10 (Thread 0x7fc8cd86a700 (LWP 21949)): #0 0x7fc99a7060af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc9978fd65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc992bb94eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fc992bb9995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fc9978fc9e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fc99a701734 in start_thread () at /lib64/libpthread.so.0 #6 0x7fc99a43fd3d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fc8ce26b700 (LWP 21948)): #0 0x7fc99a7060af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc9978fd65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc992bb94eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fc992bb9995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fc9978fc9e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fc99a701734 in start_thread () at /lib64/libpthread.so.0 #6 0x7fc99a43fd3d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fc8d014a700 (LWP 21947)): #0 0x7fc99a438b03 in select () at /lib64/libc.so.6 #1 0x7fc997b0b849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc997b0d0c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7fc997b0d527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fc997abcfdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fc9978f7f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fc9924e49b8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fc9978fc9e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fc99a701734 in start_thread () at /lib64/libpthread.so.0 #9 0x7fc99a43fd3d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fc976340700 (LWP 21865)): #0 0x7fc99a438b03 in select () at /lib64/libc.so.6 #1 0x7fc997b0b849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc997b0d0c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7fc997b0d527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fc997abcfdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fc9978f7f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fc9924e49b8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fc9978fc9e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fc99a701734 in start_thread () at /lib64/libpthread.so.0 #9 0x7fc99a43fd3d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fc977fff700 (LWP 13920)): #0 0x7fc99a7060af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc9978fd65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc992bb94eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fc992bb9995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fc9978fc9e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fc99a701734 in start_thread () at /lib64/libpthread.so.0 #6 0x7fc99a43fd3d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fc97587f700 (LWP 12824)): #0 0x7ffe30df1adc in clock_gettime () #1 0x7fc99a44c806 in clock_gettime () at /lib64/libc.so.6 #2 0x7fc9979a7826 in () at /usr/lib64/libQt5Core.so.5 #3 0x7fc997b0d989 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7fc997b0cdd1 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #5 0x7fc997b0d527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fc997abcfdb in QEventLo
[kwin] [Bug 397530] New: KDE Windows crashed
https://bugs.kde.org/show_bug.cgi?id=397530 Bug ID: 397530 Summary: KDE Windows crashed Product: kwin Version: 5.12.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: bill6...@alumni.rutgers.edu Target Milestone: --- Application: kwin_x11 (5.12.5) Qt Version: 5.9.4 Frameworks Version: 5.45.0 Operating System: Linux 4.12.14-lp150.12.13-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: KDE screen will flash then come back and report that KDE Windows has crashed. It is an intermittant problem and I cannot see any consistancecy in the cause. It will usually occure when I selesct a window, close a window, switch desktops. One result is that some open windows are moved to the top of the desktops far enough that the title bar is no longer visable. The windows may be moved down by selecting on the frame then selecting Move. My system is using a Ninvida GeForce display and runing two desktop screens off of it. Running SUSE Leap 15.2, but the problem has been occuring since the change to Leap 42.0 The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f967b9eb940 (LWP 2729))] Thread 9 (Thread 0x7f95acad4700 (LWP 4537)): #0 0x7f96743eb89d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f96785683eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f96735df398 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f96735df7ca in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f96785670ce in () at /usr/lib64/libQt5Core.so.5 #5 0x7f96743e5559 in start_thread () at /lib64/libpthread.so.0 #6 0x7f967b36982f in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f95ad545700 (LWP 4536)): #0 0x7f96743eb89d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f96785683eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f96735df398 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f96735df7ca in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f96785670ce in () at /usr/lib64/libQt5Core.so.5 #5 0x7f96743e5559 in start_thread () at /lib64/libpthread.so.0 #6 0x7f967b36982f in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f965551e700 (LWP 4534)): #0 0x7f9678788772 in () at /usr/lib64/libQt5Core.so.5 #1 0x7f9678788048 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #2 0x7f967873309a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f96785624da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #4 0x7f9672ee9cb5 in () at /usr/lib64/libQt5Qml.so.5 #5 0x7f96785670ce in () at /usr/lib64/libQt5Core.so.5 #6 0x7f96743e5559 in start_thread () at /lib64/libpthread.so.0 #7 0x7f967b36982f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f9654b9d700 (LWP 4533)): #0 0x7f967b35f186 in ppoll () at /lib64/libc.so.6 #1 0x7f9678786ba9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f9678788186 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f967873309a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f96785624da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f9672ee9cb5 in () at /usr/lib64/libQt5Qml.so.5 #6 0x7f96785670ce in () at /usr/lib64/libQt5Core.so.5 #7 0x7f96743e5559 in start_thread () at /lib64/libpthread.so.0 #8 0x7f967b36982f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f9657fff700 (LWP 3490)): #0 0x7f967b35f186 in ppoll () at /lib64/libc.so.6 #1 0x7f9678786ba9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f9678788186 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f967873309a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f96785624da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f9672ee9cb5 in () at /usr/lib64/libQt5Qml.so.5 #6 0x7f96785670ce in () at /usr/lib64/libQt5Core.so.5 #7 0x7f96743e5559 in start_thread () at /lib64/libpthread.so.0 #8 0x7f967b36982f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f9643fff700 (LWP 2798)): #0 0x7f96743eb89d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f967769a5e4 in () at /usr/lib64/libQt5Script.so.5 #2 0x7f967769a629 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f96743e5559 in start_thread () at /lib64/libpthread.so.0 #4 0x7f
[kde] [Bug 391014] New: Crashes on close
https://bugs.kde.org/show_bug.cgi?id=391014 Bug ID: 391014 Summary: Crashes on close Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bill6...@alumni.rutgers.edu Target Milestone: --- Application: showfoto (5.8.0) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.114-42-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: Hit the close butten on the window bar and got a crash message. -- Backtrace: Application: Showfoto (showfoto), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1596e099c0 (LWP 3861))] Thread 12 (Thread 0x7f153a013700 (LWP 3874)): #0 0x7f159253f0ff in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f159338a8ab in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f158e7b544b in QtAV::BlockingQueue::take() () at /usr/lib64/libQtAV.so.1 #3 0x7f158e8250cb in QtAV::ExtractThread::run() () at /usr/lib64/libQtAV.so.1 #4 0x7f1593389a29 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f159253a724 in start_thread () at /lib64/libpthread.so.0 #6 0x7f1592a81e8d in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f153a814700 (LWP 3873)): #0 0x7f159253f0ff in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f159338a8ab in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f158e7b544b in QtAV::BlockingQueue::take() () at /usr/lib64/libQtAV.so.1 #3 0x7f158e8250cb in QtAV::ExtractThread::run() () at /usr/lib64/libQtAV.so.1 #4 0x7f1593389a29 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f159253a724 in start_thread () at /lib64/libpthread.so.0 #6 0x7f1592a81e8d in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f153b015700 (LWP 3872)): #0 0x7f159253f0ff in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f159338a8ab in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f158e7b544b in QtAV::BlockingQueue::take() () at /usr/lib64/libQtAV.so.1 #3 0x7f158e8250cb in QtAV::ExtractThread::run() () at /usr/lib64/libQtAV.so.1 #4 0x7f1593389a29 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f159253a724 in start_thread () at /lib64/libpthread.so.0 #6 0x7f1592a81e8d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f153b816700 (LWP 3871)): [KCrash Handler] #6 0x7f1593382445 in QMutex::lock() () at /usr/lib64/libQt5Core.so.5 #7 0x7f159605323f in () at /usr/lib64/libdigikamcore.so.5.8.0 #8 0x7f159602bcaa in Digikam::LoadSaveThread::run() () at /usr/lib64/libdigikamcore.so.5.8.0 #9 0x7f1596069f1e in Digikam::DynamicThread::DynamicThreadPriv::run() () at /usr/lib64/libdigikamcore.so.5.8.0 #10 0x7f159338685e in () at /usr/lib64/libQt5Core.so.5 #11 0x7f1593389a29 in () at /usr/lib64/libQt5Core.so.5 #12 0x7f159253a724 in start_thread () at /lib64/libpthread.so.0 #13 0x7f1592a81e8d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f1548eb9700 (LWP 3870)): #0 0x7f159253f4a8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f159338a5e8 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f15933869e0 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f1593389a29 in () at /usr/lib64/libQt5Core.so.5 #4 0x7f159253a724 in start_thread () at /lib64/libpthread.so.0 #5 0x7f1592a81e8d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f1549724700 (LWP 3869)): #0 0x7f159253f0ff in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f159338a8ab in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f158e7b544b in QtAV::BlockingQueue::take() () at /usr/lib64/libQtAV.so.1 #3 0x7f158e8250cb in QtAV::ExtractThread::run() () at /usr/lib64/libQtAV.so.1 #4 0x7f1593389a29 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f159253a724 in start_thread () at /lib64/libpthread.so.0 #6 0x7f1592a81e8d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f154a0f3700 (LWP 3868)): #0 0x7f159253f0ff in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f159338a8ab in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f158e7b544b in QtAV::BlockingQueue::take() () at /usr/lib64/libQtAV.so.1 #3 0x7f158e8250cb in QtAV::ExtractThread::run() () at /usr/lib64/libQtAV.so.1 #4 0x7f1593389a29 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f159253a724 i
[systemsettings] [Bug 388975] New: System Settings crashed when typing in upper left search box
https://bugs.kde.org/show_bug.cgi?id=388975 Bug ID: 388975 Summary: System Settings crashed when typing in upper left search box Product: systemsettings Version: 5.11.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: j...@notjustbill.com Target Milestone: --- Application: systemsettings5 (5.11.5) Qt Version: 5.9.3 Frameworks Version: 5.41.0 Operating System: Linux 4.10.0-42-generic x86_64 Distribution: KDE neon User Edition 5.11 -- Information about the crash: - What I was doing when the application crashed: Searching for screen lock settings in search box, while using remote input feature of KDEconnect from an android device. Able to restart System Settings and complete my search in the same manner with no further crashes. The crash does not seem to be reproducible. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7651c0a8c0 (LWP 25440))] Thread 5 (Thread 0x7f761f629700 (LWP 25446)): #0 0x7f764d90470d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f764789f38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f764789f49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f764e22b6cb in QEventDispatcherGlib::processEvents (this=0x7f76180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f764e1d3e2a in QEventLoop::exec (this=this@entry=0x7f761f628ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f764dffc8f4 in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f764c0b1d25 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f764e001709 in QThreadPrivate::start (arg=0x1145570) at thread/qthread_unix.cpp:368 #8 0x7f76497286ba in start_thread (arg=0x7f761f629700) at pthread_create.c:333 #9 0x7f764d9103dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f76291ff700 (LWP 25445)): #0 0x7f764dff8b49 in std::__atomic_base::compare_exchange_strong (__m2=std::memory_order_relaxed, __m1=std::memory_order_release, __p2=0x0, __p1=@0x7f76291fea88: 0x1, this=0xe4d460) at /usr/include/c++/5/bits/atomic_base.h:752 #1 std::atomic::compare_exchange_strong (__m2=std::memory_order_relaxed, __m1=std::memory_order_release, __p2=0x0, __p1=@0x7f76291fea88: 0x1, this=0xe4d460) at /usr/include/c++/5/atomic:462 #2 QAtomicOps::testAndSetRelease (currentValue=, newValue=0x0, expectedValue=0x1, _q_value=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:299 #3 QBasicAtomicPointer::testAndSetRelease (currentValue=, newValue=0x0, expectedValue=, this=0xe4d460) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:264 #4 QBasicMutex::fastTryUnlock (current=, this=0xe4d460) at thread/qmutex.h:104 #5 QMutex::unlock (this=this@entry=0xe4d460) at thread/qmutex.cpp:337 #6 0x7f764e22b5f1 in QMutexLocker::unlock (this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:213 #7 QMutexLocker::~QMutexLocker (this=, __in_chrg=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:207 #8 QThreadData::canWaitLocked (this=0xe4d430) at ../../include/QtCore/5.9.3/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:253 #9 postEventSourcePrepare (s=0x7f76240012d0, timeout=0x7f76291feb14) at kernel/qeventdispatcher_glib.cpp:259 #10 0x7f764789e91d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f764789f2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f764789f49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f764e22b6cb in QEventDispatcherGlib::processEvents (this=0x7f76240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #14 0x7f764e1d3e2a in QEventLoop::exec (this=this@entry=0x7f76291fece0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #15 0x7f764dffc8f4 in QThread::exec (this=) at thread/qthread.cpp:515 #16 0x7f764c0b1d25 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #17 0x7f764e001709 in QThreadPrivate::start (arg=0xe4d110) at thread/qthread_unix.cpp:368 #18 0x7f76497286ba in start_thread (arg=0x7f76291ff700) at pthread_create.c:333 #19 0x7f764d9103dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f76357fc700 (LWP 25443)): #0 QTimerInfoList::timerWait (this=0x7f7630002ed0, tm=...) at kernel/qtimerinfo_unix.cpp:413 #1 0x7f764e22b43e in timerSourcePrepareHelper (timeout=0x7f76357fbb04, src=) at kernel/qeventdispatcher_glib.cpp:132 #2 timerSourcePrepare (source=, timeout=0x7f76357fbb04) at kernel/qeventdispatch
[plasmashell] [Bug 465829] New: The plasma panel will redraw the top boarder on top of any maximised application when it is set to "Windows can cover". The panel will also display additional boarder l
https://bugs.kde.org/show_bug.cgi?id=465829 Bug ID: 465829 Summary: The plasma panel will redraw the top boarder on top of any maximised application when it is set to "Windows can cover". The panel will also display additional boarder line when cursor is in an area with no icons or widgets. Classification: Plasma Product: plasmashell Version: 5.27.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: bill.h...@slmail.me CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Set panel to windows can cover. 2. Open any application maximised. 3. If you hover mouse cursor close the the bottom edge. 4. If you hover mouse cursor on any area of the panel without any icons or widgets. 5. Additionally wait for a minute or so with a maximised application. OBSERVED RESULT A boarder line appears on screen, which is the panel boarder line as far as I understand it. EXPECTED RESULT No boarder line should appear unexpectedly for the panel. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I am using KDE Plasma under wayland if that is relevant. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465829] The plasma panel will redraw the top boarder on top of any maximised application when it is set to "Windows can cover". The panel will also display additional boarder line w
https://bugs.kde.org/show_bug.cgi?id=465829 --- Comment #1 from Bill --- Update: The boarder line is also appearing while watching video in browser in full-screen mode. This is very distracting as it appears in the black bars area. I tried taking screenshots but whenever I do, panel refreshes and I am not able to capture it in a screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466016] New: OSD window rule does not work in wayland
https://bugs.kde.org/show_bug.cgi?id=466016 Bug ID: 466016 Summary: OSD window rule does not work in wayland Classification: Plasma Product: kwin Version: 5.27.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: bill73...@gmail.com Target Milestone: --- SUMMARY setting OSD window type does not work in wayland. STEPS TO REPRODUCE 1. Open a video in firefox 2. set video to "picture in picture" mode 3: Right click the window and select "configure special window settings" 4. Apply the rule "set window type: force: on screen display" 5. Press "apply" and "ok" in the window rules page OBSERVED RESULT Upon reopening the "configure special windows settings" page, the "set window type" rule is set back to "all window types" instead of "on screen display" EXPECTED RESULT OSD window type should be set, and the picture in picture video should display on top of all other windows. SOFTWARE/OS VERSIONS Linux gentoo (available in About System) KDE Plasma Version: 5.27 KDE Frameworks Version: 5.103 Qt Version: 5.15.8 ADDITIONAL INFORMATION This was an attempt to apply the fix for https://bugs.kde.org/show_bug.cgi?id=439573 in wayland, however this workaround doesn't appear to work. I noticed https://invent.kde.org/plasma/kwin/-/merge_requests/3612 was recently created, would it maybe be possible to have this be added to kwin rules or even replace the On Screen Display window rule in wayland? As far as I can tell, the wayland pip protocol would allow windows to present above other fullscreen windows. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465829] The plasma panel will redraw the top boarder on top of any maximised application when it is set to "Windows can cover". The panel will also display additional boarder line w
https://bugs.kde.org/show_bug.cgi?id=465829 --- Comment #3 from Bill --- Created attachment 156462 --> https://bugs.kde.org/attachment.cgi?id=156462&action=edit If you look at right at the top of the panel It shows the line I mentioned which shows up when watching full screen videos in browser. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465829] The plasma panel will redraw the top boarder on top of any maximised application when it is set to "Windows can cover". The panel will also display additional boarder line w
https://bugs.kde.org/show_bug.cgi?id=465829 --- Comment #4 from Bill --- (In reply to Nate Graham from comment #2) > Is the line blue? Hi Nate, It is not blue. Colour of the line seems to change based on the accent colour. I have attached the screenshot in an attempt to show what border line? outline? I mentioned in the bug report. Please let me know if you need any more information. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466177] New: Magic Lamp effect should not go below floating panel
https://bugs.kde.org/show_bug.cgi?id=466177 Bug ID: 466177 Summary: Magic Lamp effect should not go below floating panel Classification: Plasma Product: kwin Version: 5.27.0 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: bill73...@gmail.com Target Milestone: --- Created attachment 156560 --> https://bugs.kde.org/attachment.cgi?id=156560&action=edit Video of Magic lamp going past the panel. SUMMARY Magic Lamp effect goes offscreen, past the floating panel. STEPS TO REPRODUCE 1. Enable "magic lamp" desktop effect 2. Enable floating panels 3. Activate the magic lamp effect. OBSERVED RESULT The application does not get sucked into the apps position, and instead goes off screen, below where the app is positioned. EXPECTED RESULT The magic lamp effect should not go below the floating panel. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27 KDE Frameworks Version: 103 Qt Version: 5.15.8 ADDITIONAL INFORMATION This could be a matter of personal preference, but I think the magic lamp should go into the application icon on the taskbar, instead of going into the bottom of the screen below the floating panel. Video attached. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465829] The plasma panel will redraw the top boarder on top of any maximised application when it is set to "Windows can cover". The panel will also display additional boarder line w
https://bugs.kde.org/show_bug.cgi?id=465829 Bill changed: What|Removed |Added Version|5.27.0 |5.27.1 --- Comment #5 from Bill --- Just finished updating to 5.27.1. The artefact line that appears in the panel when an application is covering the panel or watching video in full screen still exists but it is now much thinner. Something has improved I don't know what was changed but thanks for the update, It is now far less noticeable if I am not looking directly in the area. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466778] New: Flickering line above panel when panel is in covered by other windows.
https://bugs.kde.org/show_bug.cgi?id=466778 Bug ID: 466778 Summary: Flickering line above panel when panel is in covered by other windows. Classification: Plasma Product: kwin Version: 5.27.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bill.h...@slmail.me Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Set panel to windows can cover. 2. Open any application maximised. 3. If you hover mouse cursor close to area of the panel 4. If you hover mouse cursor on any area of the panel without any icons or widgets, an additional line is visible. 5. Additionally wait for a minute or so with a maximised application. OBSERVED RESULT Following up with my previous bug report 465829, which is duplicate of 464526. 5.27.2 has greatly resolved the issue. The flickering/persisting line is not as obvious anymore, I think my case might be one of those rare edge cases where this issue is persisting. My screen resolution is 2256x1504 (3:2) @ 150% scaling on wayland. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma 5 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467044] New: sensor KDE app crashes desktop
https://bugs.kde.org/show_bug.cgi?id=467044 Bug ID: 467044 Summary: sensor KDE app crashes desktop Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: browbi...@live.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 Created attachment 157105 --> https://bugs.kde.org/attachment.cgi?id=157105&action=edit its that app with a different type of add-on enabled from the fedora store SUMMARY Sensor crashes desktop, and causes it to freeze when trying to re-boot into it. STEPS TO REPRODUCE 1. I downloaded new types of display graphics to display temperture for my CPU, and when switching to one of them it crashed. i had to remove it using the software store from another desktop i had installed to get KDE working again. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485594] Desktop Panel Moves When Starting An Application
https://bugs.kde.org/show_bug.cgi?id=485594 Bill changed: What|Removed |Added CC||mcdonal...@icloud.com --- Comment #5 from Bill --- I am also experiencing this bug but in some different conditions/ways. - I am seeing it in both OpenSUSE and Arch only - I am seeing this bug occur in both Wayland and X11 with latest Mesa/Vulkan-Radeon - I am not having problems with notification bubbles. - This issue for me occurs more in Wayland than X11. - This issue occurs when returning from sleep and when watching full-screen videos (YouTube for example). - Any time the panel is hidden automatically either by Chrome, a game or full screen video. The resolution is somewhat inconvenient having to slide the panel from 12 to 9 o'clock then down from 9 to 6 o'clock. I have tested this bug on FreeBSD 14.1, Fedora and Nobara. It does not occur. Only occurs in latest pulls. For me, this has occurred since the release of Plasma 6 (the first time I've tried Plasma since KDE 3.x). It has gotten progressively worse from 6.0.4 onward. It used to be a mild disturbance that occurred at freak times and without any regularity. Now I can see this happen upwards of 6-7 times a day depending on what I do. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 482261] New: User account details/icon disappear in NeoChat when resizing channels from full names to icon only view.
https://bugs.kde.org/show_bug.cgi?id=482261 Bug ID: 482261 Summary: User account details/icon disappear in NeoChat when resizing channels from full names to icon only view. Classification: Applications Product: NeoChat Version: 23.08.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: billy.nl...@slmail.me CC: c...@carlschwan.eu Target Milestone: --- Created attachment 166325 --> https://bugs.kde.org/attachment.cgi?id=166325&action=edit neochat with icon only channels view SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Resize neochat channels area to icon only view. 2. User name and NeoChat setting button disappears . OBSERVED RESULT 1. User name and NeoChat setting button disappears from view. EXPECTED RESULT 1. User name and NeoChat setting button should be icon only and stay interactive. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION Please see the attached screenshots, they visually show what I am trying to report. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 482261] User account details/icon disappear in NeoChat when resizing channels from full names to icon only view.
https://bugs.kde.org/show_bug.cgi?id=482261 --- Comment #1 from Bill --- Created attachment 166326 --> https://bugs.kde.org/attachment.cgi?id=166326&action=edit neochat with normal channels view -- You are receiving this mail because: You are watching all bug changes.
[pimsettingexporter] [Bug 325727] pimsettingexporter does not restore data it exported
https://bugs.kde.org/show_bug.cgi?id=325727 --- Comment #23 from Bill --- As noted in my comment from 2013, the report can be closed. I can't confirm whether the bug is fixed, because I did what I said in my response to the dev who said it wasn't an issue- I stopped using KDE, and haven't used it since. On March 9, 2021 5:36:09 PM EST, Justin Zobel wrote: >https://bugs.kde.org/show_bug.cgi?id=325727 > >--- Comment #22 from Justin Zobel --- >Thank you for the bug report. > >As this report hasn't seen any changes in 5 years or more, we ask if >you can >please confirm that the issue still persists. > >If this bug is no longer persisting or relevant please change the >status to >resolved. > >-- >You are receiving this mail because: >You reported the bug. ___ Bill Albertson b...@blowfish-labs.com -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 426423] New: Kleopatra adds extra characters to end of .gpg file extension. How to avoid?
https://bugs.kde.org/show_bug.cgi?id=426423 Bug ID: 426423 Summary: Kleopatra adds extra characters to end of .gpg file extension. How to avoid? Product: kleopatra Version: unspecified Platform: Other OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: general Assignee: aheine...@gnupg.org Reporter: beng...@jwdanforth.com CC: kdepim-b...@kde.org, m...@kde.org Target Milestone: --- SUMMARY Kleopatra adds extra characters to end of .gpg file extension. How to avoid? STEPS TO REPRODUCE 1. Press Sign/Encrypt in Kleopatra 2. Choose file to encrypt 3. Uncheck Sign as and Encrypt for me checkboxes. 4. Click on icon in left of field and choose equifax certificate 5. Leave rest of screen as is 6 Click Encrypt button 7. Click Overwrite on pop-up. *This pop-up is confusing as I don't understand the meaning as it says the .gpg file already exists but it doesn't 8. Click Finish button Filename generated will have random characters at end. Ex. 27164_TEST1.txt.gpg.nhSNVn. We then need to strip off the 'nhSNVn' in order to ftp in a normal gpg file. OBSERVED RESULT Example = 27164_TEST1.txt.gpg EXPECTED RESULT Example = 27164_TEST1.txt.gpg SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 427166] New: Spell Check Flags Correctly Spelled Words As Incorrect
https://bugs.kde.org/show_bug.cgi?id=427166 Bug ID: 427166 Summary: Spell Check Flags Correctly Spelled Words As Incorrect Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Keywords: usability Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: racinest...@startmail.com Target Milestone: --- Created attachment 132026 --> https://bugs.kde.org/attachment.cgi?id=132026&action=edit Screenshot Of Spell Check Errors SUMMARY Looked at bug list: Bug 388314 Status: RESOLVED FIXED.Yet is not fixed for me. Issue happened after fixing other issue: https://askubuntu.com/questions/1166826/how-to-fix-no-backend-found-for-spell-checking-in-kate-editor-settings Additional info: Software Manager lists Kate version as: Version 4;17.12.3-0ubuntu1 Mint 19.3 Cinnamon 32 Bit. Yet when when clicking on Submit Bug Report in Kate, version is 17.12.3 STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 427166] Spell Check Flags Correctly Spelled Words As Incorrect
https://bugs.kde.org/show_bug.cgi?id=427166 --- Comment #2 from Bill --- Thanks Justin. Sounds like that is the answer, because my other PC's (64 Bit) do not have that issue. Jesus loves you, have a good day. Bill On Tuesday, October 27, 2020 3:10 AM, Justin Zobel <bugzilla_nore...@kde.org> wrote: > > https://bugs.kde.org/show_bug.cgi?id=427166 > > Justin Zobel changed: > >What|Removed |Added > > CC||justin.zo...@gmail.com > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Justin Zobel --- > I can't replicate this on kate from git master. > > I know 32bit releases of most distros are no longer happening, is your PC 32bit > only or can it support a 64bit OS? > > -- > You are receiving this mail because: > You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 427166] Spell Check Flags Correctly Spelled Words As Incorrect
https://bugs.kde.org/show_bug.cgi?id=427166 --- Comment #4 from Bill --- OK thanks Justin On Tuesday, October 27, 2020 4:34 PM, Justin Zobel <bugzilla_nore...@kde.org> wrote: > > https://bugs.kde.org/show_bug.cgi?id=427166 > > --- Comment #3 from Justin Zobel --- > Sorry Bill I didn't mean to say it was caused by 32bit but that Mint's last > 32bit release was 19.3 as you have installed. > > There are other 32bit operating systems still being released but Mint has > stopped at 19.3. They should of course still get bugfixes for it though. > > -- > You are receiving this mail because: > You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 427166] Spell Check Flags Correctly Spelled Words As Incorrect
https://bugs.kde.org/show_bug.cgi?id=427166 --- Comment #6 from Bill --- Thanks Christoph for your time and effort. Jesus loves you and have a good day, Bill On Monday, November 9, 2020 5:23 PM, Christoph Feck <bugzilla_nore...@kde.org> wrote: > > https://bugs.kde.org/show_bug.cgi?id=427166 > > Christoph Feck changed: > >What|Removed |Added > > Status|NEEDSINFO |RESOLVED > Resolution|WAITINGFORINFO |WORKSFORME > > --- Comment #5 from Christoph Feck --- > Reporter confirms it works on the other system, which most likely has newer > software. > > -- > You are receiving this mail because: > You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429836] New: Unable To Open Krita File After Importing Jpeg Into Pattern Section of Fill Layer
https://bugs.kde.org/show_bug.cgi?id=429836 Bug ID: 429836 Summary: Unable To Open Krita File After Importing Jpeg Into Pattern Section of Fill Layer Product: krita Version: 4.4.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: layer styles Assignee: krita-bugs-n...@kde.org Reporter: whoiam6...@gmail.com Target Milestone: --- SUMMARY I’m having problems trying to open a Krita file. Either I click on the file or open a file while Krita 4.4.0 is on - the result is the same: The application opens up and then closes by itself. I have other Krita files that open up no problem like .kra , .jpg , .png, and so on. I’m thinking the problem may stem from importing two jpegs into the Pattern section of Fill Layer that I wanted to create textures for my artwork. Since I’ve done that I’ve been unable to open that file. STEPS TO REPRODUCE 1.Open Fill Layer 2.Import Jpeg under Pattern section 3.Select that Jpeg 4.Save as .kra File 5.Close File & Application 6.Attempt to reopen .kra file OBSERVED RESULT Application opens up and then shuts down. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429836] Unable To Open Krita File After Importing Jpeg Into Pattern Section of Fill Layer
https://bugs.kde.org/show_bug.cgi?id=429836
--- Comment #2 from Bill ---
rror occurred on Sunday, November 29, 2020 at 12:01:09.
krita.exe caused an Access Violation at location 7FFF6F138CC0 in module
libkritapigment.dll Reading from location 0008.
AddrPC Params
7FFF6F138CC0 3FF0 1E6B9090
libkritapigment.dll!0x58cc0 KoResource::name+0x0
7FFF6571FA28 00E9 0008
libkritaimage.dll!0xefa28 KisFillPainter::fillRectNoCompose+0x88
7FFF6F434F95 24B5F9E0 2237FD80 24B5F9E0
kritapatterngenerator.dll!0x4f95 KoPatternGenerator::generate+0x6f5
7FFF656CC66C 00031DEAF990 7FFF651F9D6D 0100
libkritaimage.dll!0x9c66c std::_Function_handler,
QSharedPointer, KisSharedPtr,
KisSharedPtr, QRegion const&,
KisPinnedSharedPtr)::{lambda()#2}>::_M_invoke+0xac
7FFF6592EB90 0010 1DEAF990 1EB1CB60
libkritaimage.dll!0x2feb90 KisUpdateJobItem::run+0x90
7FFF65028610 24790380 1EB1CB00
Qt5Core.dll!0x28610 QThreadPool::tryStart+0x520
7FFF6502162F
Qt5Core.dll!0x2162f QThread::qt_metacall+0x69f
7FFFC5F57034
KERNEL32.DLL!0x17034 BaseThreadInitThunk+0x14
7FFFC7C9CEC1
ntdll.dll!0x4cec1 RtlUserThreadStart+0x21
00014000-000140F6F000 krita.exe
7FFFC7C5-7FFFC7E46000 ntdll.dll6.2.19041.610
7FFFC5F4-7FFFC5FFD000 KERNEL32.DLL 6.2.19041.546
7FFFC599-7FFFC5C58000 KERNELBASE.dll 6.2.19041.572
7FFFC737-7FFFC740E000 msvcrt.dll 7.0.19041.546
7FFFA770-7FFFA774C000 libkritaglobal.dll
7FFF61D7-7FFF63285000 libkritaui.dll
7FFFA75B-7FFFA76F2000 libkritawidgetutils.dll
7FFFC75A-7FFFC774 USER32.dll 6.2.19041.610
7FFFC585-7FFFC5872000 win32u.dll 6.2.19041.630
7FFFC5CB-7FFFC5CDA000 GDI32.dll6.2.19041.546
7FFFC588-7FFFC5989000 gdi32full.dll 6.2.19041.572
7FFFC57B-7FFFC584D000 msvcp_win.dll 6.2.19041.546
7FFF6563-7FFF65BAD000 libkritaimage.dll
7FFFC56B-7FFFC57B ucrtbase.dll 6.2.19041.546
6144-6145A000 libgcc_s_seh-1.dll
6FC4-6FDA5000 libstdc++-6.dll
7FFFA754-7FFFA75A3000 libKF5ConfigCore.dll
7FFFA74E-7FFFA7537000 libKF5I18n.dll
7FFF6500-7FFF6562D000 Qt5Core.dll 5.12.9.0
7FFFC600-7FFFC60AC000 ADVAPI32.dll 6.2.19041.610
7FFFC774-7FFFC77DB000 sechost.dll 6.2.19041.546
7FFFC221-7FFFC221E000 libkritaversion.dll
7FFFC5CE-7FFFC5E04000 RPCRT4.dll 6.2.19041.630
7FFFC6A1-7FFFC6B3A000 ole32.dll6.2.19041.546
7FFFC78B-7FFFC7C05000 combase.dll 6.2.19041.572
7FFFC60B-7FFFC67F1000 SHELL32.dll 6.2.19041.610
7FFFC6CA-7FFFC6D0B000 WS2_32.dll 6.2.19041.546
7FFF6413-7FFF6474D000 Qt5Gui.dll 5.12.9.0
7FFF63BC-7FFF6412E000 Qt5Widgets.dll 5.12.9.0
7FFFAD82-7FFFAD85B000 Qt5Xml.dll 5.12.9.0
7FFFC05A-7FFFC05AE000 libkritacolor.dll
7FFFC058-7FFFC059F000 libkritacommand.dll
7FFF8F66-7FFF8F878000 libkritaflake.dll
7FFFC019-7FFFC01B1000 libkritaimpex.dll
7FFFA747-7FFFA74DC000 libkritalibbrush.dll
7FFFA743-7FFFA7468000 libkritametadata.dll
7FFFA739-7FFFA7423000 libkritaodf.dll
7FFF6F0E-7FFF6F385000 libkritapigment.dll
7FFFBFEB-7FFFBFED3000 libkritaplugin.dll
7FFFA732-7FFFA737F000 libkritapsd.dll
7FFFA70B-7FFFA70CF000 libkritastore.dll
7FFF8C6B-7FFF8C7D9000 libkritawidgets.dll
6494-64955000 libwinpthread-1.dll 1.0.0.0
7FFFA2EB-7FFFA2ED9000 libKF5ConfigGui.dll
7FFF8C90-7FFF8C996000 libKF5CoreAddons.dll
7FFFA265-7FFFA267A000 libKF5GuiAddons.dll
7FFFA22A-7FFFA22DD000 libKF5ItemViews.dll
7FFFA221-7FFFA223D000 libKF5WindowSystem.dll
7FFF77FD-7FFF780F9000 libKF5WidgetsAddons.dll
7FFF99EA-7FFF99EF8000 Qt5PrintSupport.dll 5.12.9.0
7FFFC6B4-7FFFC6C1A000 comdlg32.dll 6.2.19041.546
7FFFC5E9-7FFFC5F3E000 shcore.dll 6.2.19041.610
7FFFC731-7FFFC7365000 SHLWAPI.dll 6.2.19041.546
7FFF7BFC-7FFF7C0D1000 libfftw3.dll
7FFFA1E3-7FFFA1E7E000 libHalf-2_4.dll
7FFF6E8F-7FFF6EB48000 libexiv2.dll
7FFFC744-7FFFC7448000 PSAPI.DLL6.2.19041.546
7FFF96FC-7FFF96FFC000 libKF5Completion.dll
7FFF9558-7FFF955BE000 libpng16.dll
7FFF763C-7FFF764B3000 Qt5Multimedia.dll 5.12.9.0
7FFF7457-7FFF746FD000 Qt5Network.dll 5.12.9.0
7FFFC53C-7FFFC551D000
[krita] [Bug 429836] Unable To Open Krita File After Importing Jpeg Into Pattern Section of Fill Layer
https://bugs.kde.org/show_bug.cgi?id=429836
--- Comment #3 from Bill ---
Error occurred on Sunday, November 29, 2020 at 12:01:09.
krita.exe caused an Access Violation at location 7FFF6F138CC0 in module
libkritapigment.dll Reading from location 0008.
AddrPC Params
7FFF6F138CC0 3FF0 1E6B9090
libkritapigment.dll!0x58cc0 KoResource::name+0x0
7FFF6571FA28 00E9 0008
libkritaimage.dll!0xefa28 KisFillPainter::fillRectNoCompose+0x88
7FFF6F434F95 24B5F9E0 2237FD80 24B5F9E0
kritapatterngenerator.dll!0x4f95 KoPatternGenerator::generate+0x6f5
7FFF656CC66C 00031DEAF990 7FFF651F9D6D 0100
libkritaimage.dll!0x9c66c std::_Function_handler,
QSharedPointer, KisSharedPtr,
KisSharedPtr, QRegion const&,
KisPinnedSharedPtr)::{lambda()#2}>::_M_invoke+0xac
7FFF6592EB90 0010 1DEAF990 1EB1CB60
libkritaimage.dll!0x2feb90 KisUpdateJobItem::run+0x90
7FFF65028610 24790380 1EB1CB00
Qt5Core.dll!0x28610 QThreadPool::tryStart+0x520
7FFF6502162F
Qt5Core.dll!0x2162f QThread::qt_metacall+0x69f
7FFFC5F57034
KERNEL32.DLL!0x17034 BaseThreadInitThunk+0x14
7FFFC7C9CEC1
ntdll.dll!0x4cec1 RtlUserThreadStart+0x21
00014000-000140F6F000 krita.exe
7FFFC7C5-7FFFC7E46000 ntdll.dll6.2.19041.610
7FFFC5F4-7FFFC5FFD000 KERNEL32.DLL 6.2.19041.546
7FFFC599-7FFFC5C58000 KERNELBASE.dll 6.2.19041.572
7FFFC737-7FFFC740E000 msvcrt.dll 7.0.19041.546
7FFFA770-7FFFA774C000 libkritaglobal.dll
7FFF61D7-7FFF63285000 libkritaui.dll
7FFFA75B-7FFFA76F2000 libkritawidgetutils.dll
7FFFC75A-7FFFC774 USER32.dll 6.2.19041.610
7FFFC585-7FFFC5872000 win32u.dll 6.2.19041.630
7FFFC5CB-7FFFC5CDA000 GDI32.dll6.2.19041.546
7FFFC588-7FFFC5989000 gdi32full.dll 6.2.19041.572
7FFFC57B-7FFFC584D000 msvcp_win.dll 6.2.19041.546
7FFF6563-7FFF65BAD000 libkritaimage.dll
7FFFC56B-7FFFC57B ucrtbase.dll 6.2.19041.546
6144-6145A000 libgcc_s_seh-1.dll
6FC4-6FDA5000 libstdc++-6.dll
7FFFA754-7FFFA75A3000 libKF5ConfigCore.dll
7FFFA74E-7FFFA7537000 libKF5I18n.dll
7FFF6500-7FFF6562D000 Qt5Core.dll 5.12.9.0
7FFFC600-7FFFC60AC000 ADVAPI32.dll 6.2.19041.610
7FFFC774-7FFFC77DB000 sechost.dll 6.2.19041.546
7FFFC221-7FFFC221E000 libkritaversion.dll
7FFFC5CE-7FFFC5E04000 RPCRT4.dll 6.2.19041.630
7FFFC6A1-7FFFC6B3A000 ole32.dll6.2.19041.546
7FFFC78B-7FFFC7C05000 combase.dll 6.2.19041.572
7FFFC60B-7FFFC67F1000 SHELL32.dll 6.2.19041.610
7FFFC6CA-7FFFC6D0B000 WS2_32.dll 6.2.19041.546
7FFF6413-7FFF6474D000 Qt5Gui.dll 5.12.9.0
7FFF63BC-7FFF6412E000 Qt5Widgets.dll 5.12.9.0
7FFFAD82-7FFFAD85B000 Qt5Xml.dll 5.12.9.0
7FFFC05A-7FFFC05AE000 libkritacolor.dll
7FFFC058-7FFFC059F000 libkritacommand.dll
7FFF8F66-7FFF8F878000 libkritaflake.dll
7FFFC019-7FFFC01B1000 libkritaimpex.dll
7FFFA747-7FFFA74DC000 libkritalibbrush.dll
7FFFA743-7FFFA7468000 libkritametadata.dll
7FFFA739-7FFFA7423000 libkritaodf.dll
7FFF6F0E-7FFF6F385000 libkritapigment.dll
7FFFBFEB-7FFFBFED3000 libkritaplugin.dll
7FFFA732-7FFFA737F000 libkritapsd.dll
7FFFA70B-7FFFA70CF000 libkritastore.dll
7FFF8C6B-7FFF8C7D9000 libkritawidgets.dll
6494-64955000 libwinpthread-1.dll 1.0.0.0
7FFFA2EB-7FFFA2ED9000 libKF5ConfigGui.dll
7FFF8C90-7FFF8C996000 libKF5CoreAddons.dll
7FFFA265-7FFFA267A000 libKF5GuiAddons.dll
7FFFA22A-7FFFA22DD000 libKF5ItemViews.dll
7FFFA221-7FFFA223D000 libKF5WindowSystem.dll
7FFF77FD-7FFF780F9000 libKF5WidgetsAddons.dll
7FFF99EA-7FFF99EF8000 Qt5PrintSupport.dll 5.12.9.0
7FFFC6B4-7FFFC6C1A000 comdlg32.dll 6.2.19041.546
7FFFC5E9-7FFFC5F3E000 shcore.dll 6.2.19041.610
7FFFC731-7FFFC7365000 SHLWAPI.dll 6.2.19041.546
7FFF7BFC-7FFF7C0D1000 libfftw3.dll
7FFFA1E3-7FFFA1E7E000 libHalf-2_4.dll
7FFF6E8F-7FFF6EB48000 libexiv2.dll
7FFFC744-7FFFC7448000 PSAPI.DLL6.2.19041.546
7FFF96FC-7FFF96FFC000 libKF5Completion.dll
7FFF9558-7FFF955BE000 libpng16.dll
7FFF763C-7FFF764B3000 Qt5Multimedia.dll 5.12.9.0
7FFF7457-7FFF746FD000 Qt5Network.dll 5.12.9.0
7FFFC53C-7FFFC551D000
[Discover] [Bug 421380] New: Updates task bar link crashes discover.
https://bugs.kde.org/show_bug.cgi?id=421380 Bug ID: 421380 Summary: Updates task bar link crashes discover. Product: Discover Version: 5.12.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: waricht...@yahoo.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.12.8) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-99-generic x86_64 Distribution: Ubuntu 18.04.4 LTS -- Information about the crash: - What I was doing when the application crashed: Clicking on task bar link to apply updates. This started happening 1-2 weeks ago. now using apt to update until resolved. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7efbff6a0800 (LWP 1683))] Thread 10 (Thread 0x7efba7fff700 (LWP 1699)): #0 0x7efbfac81839 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7efbfb383775 in QBasicMutex::lockInternal() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7efbf8bf2f96 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #3 0x7efbf8bf3835 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #4 0x7efbf8bcf8cc in QSslSocket::startClientEncryption() () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #5 0x7efbf8bd0578 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #6 0x7efbf8bd8379 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #7 0x7efbfb599555 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7efbf8ba2f09 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #9 0x7efbf8ba5e78 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #10 0x7efbf8bb67ed in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7efbfd83e83c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7efbfd846104 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7efbfb56a8d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7efbfb5c44ed in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7efbf546b417 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7efbf546b650 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7efbf546b6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7efbfb5c38ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7efbfb56890a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7efbfb38723a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7efbfb38c17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7efbf759a6db in start_thread (arg=0x7efba7fff700) at pthread_create.c:463 #23 0x7efbfac8788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7efbb5412700 (LWP 1697)): #0 0x7efbfac760b4 in __GI___libc_read (fd=25, buf=0x7efbb5411cd0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7efbf54b02b0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7efbf546b0b7 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efbf546b570 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7efbf546b962 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7efbd0fe0276 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x7efbf5493175 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7efbf759a6db in start_thread (arg=0x7efbb5412700) at pthread_create.c:463 #8 0x7efbfac8788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7efbb5c13700 (LWP 1696)): #0 0x7efbfac7abf9 in __GI___poll (fds=0x565557fbe760, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7efbf546b5c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7efbf546b6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efbf546b721 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7efbf5493175 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7efbf759a6db in start_thread (arg=0x7efbb5c13700) at pthread_create.c:463 #6 0x7efbfac8788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7efbc5450700 (LWP 1692)): #0 0x7efbf75a09f3 in futex_
[ksysguard] [Bug 410678] New: Internal buffer too small to read \'/proc/cpuinfo\'
https://bugs.kde.org/show_bug.cgi?id=410678 Bug ID: 410678 Summary: Internal buffer too small to read \'/proc/cpuinfo\' Product: ksysguard Version: 5.16.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: billflemin...@gmail.com Target Milestone: --- Created attachment 121989 --> https://bugs.kde.org/attachment.cgi?id=121989&action=edit Fixed with huge CPUINFOBUFSIZE number. SUMMARY Ksysguard cannot parse cpu info on CPUs with lots of cores. Cannot see pretty CPU Freq turbo graphs on Ryzen 9. STEPS TO REPRODUCE 1. Buy Ryzen 9 or Threadripper 12 core and above 2. Prevent your wallet from filing divorce papers. (optional) 3. Run Ksysguard 4. Check system log file for errors OBSERVED RESULT Internal buffer too small to read \'/proc/cpuinfo\' EXPECTED RESULT Should be able to see CPU Frequency and add to graph SOFTWARE/OS VERSIONS Linux/KDE Plasma: Latest version compiled on ARCH ADDITIONAL INFORMATION See ./ksysguard/ksysguardd/Linux/cpuinfo.c:43: CPUINFOBUFSIZE For my 3900X CPU it reads about 1504 char per CPU core when you read proc/cpuinfo. While this is fixed by setting a huge number for CPUINFOBUFSIZE I recommend that either you increase the array based on number of CPUs, or use a smaller buffer and re-use it for each CPU. Otherwise the huge size for CPUINFOBUFSIZE to accommodate new CPUs (128 threads) would be a pretty big silly number. After changing CPUINFOBUFSIZE and make install I can see the purdy graph attached. Next stop moar overclocking... Bill -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 410678] Internal buffer too small to read \'/proc/cpuinfo\'
https://bugs.kde.org/show_bug.cgi?id=410678 Bill changed: What|Removed |Added CC||billflemin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415402] New: QIF Import - unclear guidance produces unusable file
https://bugs.kde.org/show_bug.cgi?id=415402 Bug ID: 415402 Summary: QIF Import - unclear guidance produces unusable file Product: kmymoney Version: 5.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: w...@mindspring.com Target Milestone: --- SUMMARY Platform LinuxMint 64bit v.19.2 Attempting new installation of KMyMoney = installation OK Attempting import of QIF data file = KMyMoney asks to "set date format", but provides no guidance on what might be the correct setting. I chose %d/%m/%y, but the import produced month-day-year and the import failed. I attempted to cancel the import, but KMyMoney imported the data anyway, producing a corrupted start. Unclear how to delete the entire import to start over. Would be most helpful for KMyMoney to display a short sample data line from import with the chosen option, so user could SEE whether his/her choice would work or not (as Excel displays with imports) STEPS TO REPRODUCE 1. Start KMyMoney 2. Click File/Import/QIF 3. Select import file 4. "Import" asks what date format to use OBSERVED RESULT New user (me) has no idea what the proper setting should be. I changed the default to month-day-year (U.S. Quicken format, I thought), and the import failed, asking whether I wanted to cancel. At that point, my intent was to cancel import WITHOUT importing any data. KMyMoney proceeded to import all data, but result was not usable. It would be most helpful for KMyMoney to display just one line of the sample import, so user could SEE what will result from their import choice. ALSO, how do I delete all my imported data so I can re-do the import? Thanks EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: LinuxMint 19.2 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478331] Kwin performance tanks in gpu bound scenarios
https://bugs.kde.org/show_bug.cgi?id=478331 --- Comment #1 from Bill --- No longer able to reproduce. Please close. -- You are receiving this mail because: You are watching all bug changes.
[kdesvn] [Bug 473930] New: The system close (shut down) frequently when we change to another bookmark.
https://bugs.kde.org/show_bug.cgi?id=473930 Bug ID: 473930 Summary: The system close (shut down) frequently when we change to another bookmark. Classification: Applications Product: kdesvn Version: 2.1.0 Platform: Debian stable OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: kdesvn-bugs-n...@kde.org Reporter: sergiomino...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I use Linux Debian. STEPS TO REPRODUCE 1. Open one bookmark on local disk 2. Change to another bookmark on WordPress repo 3. Open another bookmark on local disk KDESVN shut down. SOFTWARE/OS VERSIONS Linux Debian Gnome Memory 8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 478149] New: Kamoso crashes when camera is disabled in UEFI/BIOS settings
https://bugs.kde.org/show_bug.cgi?id=478149 Bug ID: 478149 Summary: Kamoso crashes when camera is disabled in UEFI/BIOS settings Classification: Applications Product: kamoso Version: 22.12.3 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: user1...@tuta.io Target Milestone: --- Application: kamoso (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-13-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: Dell Latitude E6420 Laptop - Cameara is disabled via the UEFI settings, microphone is enabled. Kamoso opens and allow the user to start recording (presumably audio only, as no video is shown), but once recording is stopped, Kamoso crashes. I suspect this crash would also happen in reverse (camera enabled, microphone disabled) and if both are disabled (though I did not test). Obviously, it could handle these scenarios more gracefully. I believe this issue is related to/the same as Bug 462424. Hope that helps! The crash can be reproduced every time. -- Backtrace: Application: Kamoso (kamoso), signal: Segmentation fault PID: 1857 (kamoso) UID: 1000 (debian) GID: 1000 (debian) Signal: 11 (SEGV) Timestamp: Wed 2023-12-06 17:59:27 AEST (1min 7s ago) Command Line: /usr/bin/kamoso -qwindowtitle Kamoso Executable: /usr/bin/kamoso Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.kamoso-a1ea12c28f0d47728e029021ded1bb9c.scope Unit: user@1000.service User Unit: app-org.kde.kamoso-a1ea12c28f0d47728e029021ded1bb9c.scope Slice: user-1000.slice Owner UID: 1000 (debian) Boot ID: 62f9d16ffd75474b8092b5a26dd3b203 Machine ID: 5d40b852866c48039fbbc9212516fcfe Hostname: E6420 Storage: /var/lib/systemd/coredump/core.kamoso.1000.62f9d16ffd75474b8092b5a26dd3b203.1857.170184956700.zst (present) Size on Disk: 6.3M Message: Process 1857 (kamoso) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.17-1~deb12u1.amd64 Module libudev.so.1 from deb systemd-252.17-1~deb12u1.amd64 Stack trace of thread 1857: #0 0x7f0a204a9d3c n/a (libc.so.6 + 0x8ad3c) #1 0x7f0a2045af32 raise (libc.so.6 + 0x3bf32) #2 0x7f0a2115db46 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b46) #3 0x7f0a2045afd0 n/a (libc.so.6 + 0x3bfd0) #4 0x55ef61d26450 n/a (kamoso + 0x14450) #5 0x55ef61d2e549 n/a (kamoso + 0x1c549) #6 0x55ef61d29292 n/a (kamoso + 0x17292) #7 0x55ef61d244e3 n/a (kamoso + 0x124e3) #8 0x7f0a226822c1 _ZN19QQmlPropertyPrivate5writeEP7QObjectRK16QQmlPropertyDataRK8QVariantP15QQmlContextData6QFlagsINS2_9WriteFlagEE (libQt5Qml.so.5 + 0x2822c1) #9 0x7f0a225a68ba _ZN3QV414QObjectWrapper11setPropertyEPNS_15ExecutionEngineEP7QObjectP16QQmlPropertyDataRKNS_5ValueE (libQt5Qml.so.5 + 0x1a68ba) #10 0x7f0a225a6ffb _ZN3QV414QObjectWrapper14setQmlPropertyEPNS_15ExecutionEngineEP15QQmlContextDataP7QObjectPNS_6StringENS0_12RevisionModeERKNS_5ValueE (libQt5Qml.so.5 + 0x1a6ffb) #11 0x7f0a225a715b _ZN3QV414QObjectWrapper10virtualPutEPNS_7ManagedENS_11PropertyKeyERKNS_5ValueEPS4_ (libQt5Qml.so.5 + 0x1a715b) #12 0x7f0a2252f333 _ZN3QV46Lookup14setterFallbackEPS0_PNS_15ExecutionEngineERNS_5ValueERKS4_ (libQt5Qml.so.5 + 0x12f333) #13 0x7f0a225c13a4 n/a (libQt5Qml.so.5 + 0x1c13a4) #14 0x7f0a225c53df n/a (libQt5Qml.so.5 + 0x1c53df) #15 0x7f0a22557c2e _ZN3QV48Function4callEPKNS_5ValueES3_iPKNS_16ExecutionContextE (libQt5Qml.so.5 + 0x157c2e) #16 0x7f0a226e144d _ZN24QQmlJavaScriptExpression8evaluateEPN3QV48CallDataEPb (libQt5Qml.so.5 + 0x2e144d) #17 0x7f0a22692baf _ZN25QQmlBoundSignalExpression8evaluateEPPv (libQt5Qml.so.5 + 0x292baf) #18 0x7f0a226942f8 n/a (libQt5Qml.so.5 + 0x2942f8) #19 0x7f0a226c677f _ZN12QQmlNotifier10emitNotifyEP20QQmlNotifierEndpointPPv (libQt5Qml.so.5 + 0x2c677f) #20 0x7f0a20ee8a8d n/a (libQt5Core.so.5 + 0x2e8a8d) #21 0x7f0a1acf5422 _ZN12QQuickAction14checkedChangedEb (libQt5QuickTemplates2.so.5 + 0x8b422) #22 0x7f0a1acf35ea _ZN20QQuickAbstractButton10setCheckedEb (libQt5QuickTemplates2.so.5 + 0x895ea) #23 0x7f0a1acf36ff _ZN27QQuickAbstractButtonPrivate6
[kwin] [Bug 478331] New: Kwin performance tanks in gpu bound scenarios
https://bugs.kde.org/show_bug.cgi?id=478331 Bug ID: 478331 Summary: Kwin performance tanks in gpu bound scenarios Classification: Plasma Product: kwin Version: git master Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bill73...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Login to plasma wayland 2. Open any(?) game that will be gpu bound, ive personally tested Rocket League (steam version, proton) and Risk of Rain 2 (steam, proton). 3. Ensure vsync is disabled, i've notice if vsync is on then kwin renders at its intended framerate OBSERVED RESULT Kwin will render (based on the show fps desktop effect) at roughly half the framerate of the game. For example, in Rocket League the game renders at about ~300 fps, then kwin will render at about 150. In Risk of Rain 2, the game will run at about 135 fps and kwin will render at about 75. This has a very noticeable impact on visual quality, as the framerate is being nearly halfed. EXPECTED RESULT Kwin should render at roughly the games framerate, which is what it does if i enable vsync. SOFTWARE/OS VERSIONS Linux/KDE Plasma: gentoo / git master using kdesrc build KDE Plasma Version: git master KDE Frameworks Version: git master Qt Version: 6.6.1 from gentoo packages ADDITIONAL INFORMATION Kwin wayland works as intended on version 5.27.10. GPU: 5700xt, mesa git CPU: 12900k Monitor: 1440p 240hz LG 27GR95QE -- You are receiving this mail because: You are watching all bug changes.
[ksirk] [Bug 456495] New: Ksirk 20.12.1 Debian 11 After enemy defeated programme freezes. Debian 10 works fine.
https://bugs.kde.org/show_bug.cgi?id=456495 Bug ID: 456495 Summary: Ksirk 20.12.1 Debian 11 After enemy defeated programme freezes. Debian 10 works fine. Product: ksirk Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: nemhi...@gmail.com Reporter: billsto...@westnet.com.au CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.20.5 (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Tried re installing (from debian) no change. -- You are receiving this mail because: You are watching all bug changes.
[ksirk] [Bug 456495] Ksirk 20.12.1 Debian 11 After enemy defeated programme freezes. Debian 10 works fine.
https://bugs.kde.org/show_bug.cgi?id=456495 --- Comment #3 from Bill. --- On Thursday, 21 July 2022 4:57:03 AM AWST you wrote: > https://bugs.kde.org/show_bug.cgi?id=456495 > > Albert Astals Cid changed: > >What|Removed |Added > > Status|REPORTED|NEEDSINFO > CC||aa...@kde.org > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Albert Astals Cid --- > Can you try in a version that is not 2 years old? > > Give the flathub version a try > https://flathub.org/apps/details/org.kde.ksirk Tried flathub ksirk same result (same ksirk ver). I have an old Debian on a stick I use if I wish to play. Bill. -- You are receiving this mail because: You are watching all bug changes.
[ksirk] [Bug 456495] Ksirk 20.12.1 Debian 11 After enemy defeated programme freezes. Debian 10 works fine.
https://bugs.kde.org/show_bug.cgi?id=456495 --- Comment #4 from Bill. --- On Thursday, 21 July 2022 4:57:03 AM AWST you wrote: > https://bugs.kde.org/show_bug.cgi?id=456495 > > Albert Astals Cid changed: > >What|Removed |Added > > Status|REPORTED|NEEDSINFO > CC||aa...@kde.org > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Albert Astals Cid --- > Can you try in a version that is not 2 years old? > > Give the flathub version a try > https://flathub.org/apps/details/org.kde.ksirk Tried flathub ksirk same result (same ksirk ver). I have an old Debian on a stick I use if I wish to play. Bill. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 450664] New: Kdenlive produces the render file but then the gui disappears and I have to restart Kdenlive
https://bugs.kde.org/show_bug.cgi?id=450664 Bug ID: 450664 Summary: Kdenlive produces the render file but then the gui disappears and I have to restart Kdenlive Product: kdenlive Version: 21.12.2 Platform: Snap OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: claybir...@comcast.net Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT kdenlive crashes after producing the render file EXPECTED RESULT I expect the render dialog box to stay open and allow me to clean up and continue to work within Kdenlive SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: ubuntu 20.04.3 LTS 64 bit (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION MLT 7.4.0. Kdenlive was installed with snap.. Unbuntu Gnome ver 3.36.8.Using render setting MP4 H264/AAC -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 450664] Kdenlive produces the render file but then the gui disappears and I have to restart Kdenlive
https://bugs.kde.org/show_bug.cgi?id=450664 --- Comment #2 from Bill --- First of all thank you for your quick response. Second rendering from AppImage did WORK... Success, Kdenlive did not crash and the MP4 output file played perfectly. I am not a Linux expert, but my son is proficient in it. I used to use Adobe Premier Pro, but since using Linux and Kdenlive, I won't go back to Windows and Adobe.. Again Thank you. Bill -Original Message- From: emohr Sent: Wednesday, February 23, 2022 11:34 AM To: claybir...@comcast.net Subject: [kdenlive] [Bug 450664] Kdenlive produces the render file but then the gui disappears and I have to restart Kdenlive https://bugs.kde.org/show_bug.cgi?id=450664 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from emohr --- That could be a snap-pak issue. Please try with the current Kdenlive AppImage version 21.21.2 to see if there are any packaging issues https://kdenlive.org/en/download/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486214] New: High CPU usage on kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=486214 Bug ID: 486214 Summary: High CPU usage on kwin_wayland Classification: Plasma Product: kwin Version: 6.0.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: billy.nl...@slmail.me Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Use system as normal 2. Btop shows high cpu and power usgae by kwin_wayland 3. OBSERVED RESULT kwin_wayland usage cpu constantly, causing higher power draw, stoping cpu from deeper sleep state EXPECTED RESULT kwin_wayland should not be using cpu consultant, it should allow cpu to fall into deeper sleep state when no in active use SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-1240P Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Framework Product Name: Laptop (12th Gen Intel Core) System Version: A4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486214] High CPU usage on kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=486214 --- Comment #1 from Bill --- Created attachment 168952 --> https://bugs.kde.org/attachment.cgi?id=168952&action=edit hotspot logs -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486214] High CPU usage on kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=486214 --- Comment #2 from Bill --- Created attachment 168953 --> https://bugs.kde.org/attachment.cgi?id=168953&action=edit btop_screenshot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486214] High CPU usage on kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=486214 --- Comment #3 from Bill --- Created attachment 168954 --> https://bugs.kde.org/attachment.cgi?id=168954&action=edit intel_gpu_top_screenshot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486214] High CPU usage on kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=486214 --- Comment #4 from Bill --- Created attachment 168955 --> https://bugs.kde.org/attachment.cgi?id=168955&action=edit powertop_screenshot I left the system to idle for about 10 mins, then took this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486214] High CPU usage on kwin_wayland when idle
https://bugs.kde.org/show_bug.cgi?id=486214 Bill changed: What|Removed |Added Summary|High CPU usage on |High CPU usage on |kwin_wayland|kwin_wayland when idle -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486214] High CPU usage on kwin_wayland when idle
https://bugs.kde.org/show_bug.cgi?id=486214 --- Comment #6 from Bill --- (In reply to Zamundaaa from comment #5) > I don't see anything particularly weird in the flamegraph, most of the CPU > time is in compositing and processing Wayland events. There is a somewhat > odd QThreadPool thing in there taking up a not insignificant part of CPU > time, but it's not enough to cause this issue I've made few more observations since. The issue is not persistent and constant as it was when I reported it, that seem to have been the right moment where I caught it in full swing. laptop was asleep for few hours after reporting this bug and I didn't see the same CPU usage by kwin_wayland that day. It does reaper occasionality, especially where it does uses significant cpu time just sitting around idling for some reason? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474911] New: Folders with custom icons keep reverting to the default folder icon / Dolphin forgets folder icons set by user
https://bugs.kde.org/show_bug.cgi?id=474911 Bug ID: 474911 Summary: Folders with custom icons keep reverting to the default folder icon / Dolphin forgets folder icons set by user Classification: Applications Product: dolphin Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: zotsynszklargtk...@cazlq.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When I set custom icons for folders in Dolphin, they later revert back to the default folder icon seemingly at random. This is caused by closing then re-opening Dolphin, or sometimes by simply refreshing the current view. This happens despite the `.directory` files being present. STEPS TO REPRODUCE 1. Change the icons of multiple folders. 2. Close then re-open Dolphin, or refresh the current view. OBSERVED RESULT The folders revert back to the default folder icon. EXPECTED RESULT Folders should keep the icons that the user set for them. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: Void Linux (available in About System) KDE Plasma Version: N/A (using XFCE) KDE Frameworks Version: 5.107.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION Folder thumbnails are off. Drive is NTFS. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 3212] Option to hide backup files as well as dotfiles?
https://bugs.kde.org/show_bug.cgi?id=3212 Bill changed: What|Removed |Added Resolution|FIXED |--- CC||zotsynszklargtk...@cazlq.co ||m Status|RESOLVED|REOPENED --- Comment #83 from Bill --- (In reply to Luke Horwell from comment #81) > Just wanted to note: To unhide any of the file extensions affected by this > change / Dolphin 23.08, use "File Associations" in System Settings to create > a new file type for them. To the contrary, removing *.old and *.bak from the > "application/x-trash" association still kept them hidden (which makes sense > since the file types probably fell back to the system association, which is > still "application/x-trash") How do I do that in XFCE? I would very much like my .bak and .old files to be visible in Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 3212] Option to hide backup files as well as dotfiles?
https://bugs.kde.org/show_bug.cgi?id=3212 --- Comment #84 from Bill --- Update: I found a workaround which works in XFCE to unhide .bak/.old files in Dolphin. Create the file /usr/share/mime/packages/backup.xml with the following contents: http://www.freedesktop.org/standards/shared-mime-info"; type="application/x-backup"> Backups Then run: sudo update-mime-database /usr/share/mime -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484470] New: Dolphin KIO gdrive unable to open google drive folder. "Loading folder" displayed indefinitely.
https://bugs.kde.org/show_bug.cgi?id=484470 Bug ID: 484470 Summary: Dolphin KIO gdrive unable to open google drive folder. "Loading folder" displayed indefinitely. Classification: Applications Product: dolphin Version: 23.08.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: wbkaminski...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY KIO gdrive unable to open google drive folder. "Loading folder" displayed indefinitely. STEPS TO REPRODUCE 1. Open Dolphin 2. Open Network 3. Open Google Drive OBSERVED RESULT "Loading..." & "Loading folder..." displayed indefinitely. EXPECTED RESULT google2 and shared folders should be displayed. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 23.10 (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Kernel Version: 6.5.0-26-generic (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C56 System Version: 2.0 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 471638] New: Picture of the Day wallpaper when using Unsplash as source does not work
https://bugs.kde.org/show_bug.cgi?id=471638 Bug ID: 471638 Summary: Picture of the Day wallpaper when using Unsplash as source does not work Classification: Plasma Product: kdeplasma-addons Version: 5.27.6 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Picture of the Day Assignee: plasma-b...@kde.org Reporter: bill.h...@slmail.me CC: i...@guoyunhe.me, qydwhotm...@gmail.com Target Milestone: --- Created attachment 159981 --> https://bugs.kde.org/attachment.cgi?id=159981&action=edit Screenshot of the desktop. SUMMARY STEPS TO REPRODUCE 1. Go to Desktop and wallpaper setting using context menu 2. Select Picture of the day as Wallpaper type 3. Select Unsplash wallpaper as Provider 4. Select All for Category (could be any) 5. Apply settings OBSERVED RESULT 1. Wallpaper is a picture with unsplash logo with text under "We couldn't find that photo" EXPECTED RESULT 1. A Picture of day should be selected based on category. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma 5.27.6 (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 471638] Picture of the Day wallpaper when using Unsplash as source does not work
https://bugs.kde.org/show_bug.cgi?id=471638 --- Comment #2 from Bill --- (In reply to Tobias Fella from comment #1) > https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/422 well, That's that. Thanks for letting me know. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 472487] New: [Feature Request] Clicking on “Files” in Elisa sidebar should default to default system “Music” folder.
https://bugs.kde.org/show_bug.cgi?id=472487 Bug ID: 472487 Summary: [Feature Request] Clicking on “Files” in Elisa sidebar should default to default system “Music” folder. Classification: Applications Product: Elisa Version: 23.04.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: bill.h...@slmail.me Target Milestone: --- I think clicking on “Files” on the left side bar of Elisa should navigate to default "Music" folder on the system, rather than Home or Root. It should grab the xdg user directory and point there, then users can navigate elsewhere easily if their files aren’t in that directory. ADDITIONAL INFORMATION Relevent forum topic post: https://discuss.kde.org/t/clicking-on-files-should-default-to-music-folder/3054 Thank you Justin for pointing me to request this here. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 459680] Sidebar animation stutter that can magically be resolved by clicking into "Appearance"
https://bugs.kde.org/show_bug.cgi?id=459680 Bill changed: What|Removed |Added CC||bill73...@gmail.com --- Comment #2 from Bill --- Created attachment 156159 --> https://bugs.kde.org/attachment.cgi?id=156159&action=edit Video of bug -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 459680] Sidebar animation stutter that can magically be resolved by clicking into "Appearance"
https://bugs.kde.org/show_bug.cgi?id=459680 --- Comment #3 from Bill --- I am able to confirm this bug on a 144hz monitor. I have a 3700x and 5700xt, and have been having this issue since using plasma (over a year ago), and am able to reproduce this on both x11 and wayland. Video attached. I have also been able to reproduce this in kinfocenter, however you cant "fix" the animations because there is no "appearance" tab. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464035] New: Multiple bugs with auto hide on the plasma panel
https://bugs.kde.org/show_bug.cgi?id=464035 Bug ID: 464035 Summary: Multiple bugs with auto hide on the plasma panel Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: bill73...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 155125 --> https://bugs.kde.org/attachment.cgi?id=155125&action=edit Tar file containing videos of bugs 1, 2, and 3. SUMMARY Bug 1: When Floating panels and auto hide are both enabled, the animation is rather janky, video attached. Bug 2: Right clicking on an application, moving the cursor, and clicking into the panel will sometimes cause the panel to auto hide. Video attached. Bug 3: Plasma panel may sometimes auto hide when the cursor is above or right clicks a wine widget. Video attached. Bug 1: STEPS TO REPRODUCE 1. Enable auto hide on the plasma panel 2. Enable floating panels 3. Activate the floating panel animation. Bug 2: STEPS TO REPRODUCE 1: Right click on application in the plasma panel 2: Wait a few moments, if you left click immediately the bug will not occur 3: Click into an empty space in the plasma panel, the panel will hide Bug 3: 1: Turn off floating panels, I could not reproduce this with floating panels on. 2: Open a wine application which has a widget, for example the epic games store. 3: Hover over or right click the application. In certain spots, the cursor will change and the panel will hide. Bug 1: OBSERVED RESULT Non smooth, janky animation Bug 2: OBSERVED RESULT Plasma panel hides after clicking into empty space Bug 3: OBSERVED RESULT Plasma panel hides when hovering over a wine widget. Bug 1: EXPECTED RESULT Smooth animation Bug 2: EXPECTED RESULT Plasma panel should not auto hide after clicking into it. Bug 3: EXPECTED RESULT Plasma panel should stay open when hovering over widget. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Plasma wayland session. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464073] New: Poor animation quality with auto hide and floating panels
https://bugs.kde.org/show_bug.cgi?id=464073 Bug ID: 464073 Summary: Poor animation quality with auto hide and floating panels Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: bill73...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 155163 --> https://bugs.kde.org/attachment.cgi?id=155163&action=edit Video demonstrating the animation SUMMARY When Floating panels and auto hide are both enabled, the animation is rather janky, video attached. STEPS TO REPRODUCE 1. Enable auto hide on the plasma panel 2. Enable floating panels 3. Activate the floating panel animation. OBSERVED RESULT Non smooth, janky animation EXPECTED RESULT Smooth animation SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Plasma wayland session. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464074] New: Clicking into auto hide panel from application context menu sometimes closes it
https://bugs.kde.org/show_bug.cgi?id=464074 Bug ID: 464074 Summary: Clicking into auto hide panel from application context menu sometimes closes it Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: bill73...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 155164 --> https://bugs.kde.org/attachment.cgi?id=155164&action=edit Video demonstrating the behavior SUMMARY Right clicking on an application, moving the cursor, and clicking into the panel will sometimes cause the panel to auto hide. Video attached. STEPS TO REPRODUCE 1: Right click on application in the plasma panel 2: Wait a few moments, if you left click immediately the bug will not occur 3: Click into an empty space in the plasma panel, the panel will hide OBSERVED RESULT Plasma panel hides after clicking into empty space EXPECTED RESULT Plasma panel should not auto hide after clicking into it. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Plasma wayland session. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464075] New: Plasma panel sometimes unexpectedly auto hides with wine widgets
https://bugs.kde.org/show_bug.cgi?id=464075 Bug ID: 464075 Summary: Plasma panel sometimes unexpectedly auto hides with wine widgets Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: bill73...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY Plasma panel may sometimes auto hide when the cursor is above or right clicks a wine widget. Video attached. STEPS TO REPRODUCE 1. Enable auto hide on the plasma panel 2. Enable floating panels 3. Activate the floating panel animation. OBSERVED RESULT Plasma panel hides when hovering over a wine widget. EXPECTED RESULT Plasma panel should stay open when hovering over widget. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Plasma wayland session. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464075] Plasma panel sometimes unexpectedly auto hides with wine widgets
https://bugs.kde.org/show_bug.cgi?id=464075 --- Comment #1 from Bill --- Created attachment 155165 --> https://bugs.kde.org/attachment.cgi?id=155165&action=edit Video demonstrating behavior with wine widget -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464035] Multiple bugs with auto hide on the plasma panel
https://bugs.kde.org/show_bug.cgi?id=464035 --- Comment #2 from Bill --- (In reply to Nate Graham from comment #1) > > Multiple bugs > Thanks for the bug report! Unfortunately reporting multiple distinct issues > makes this ticket not actionable. See > https://community.kde.org/Get_Involved/ > Issue_Reporting#Multiple_issues_in_a_single_Bugzilla_ticket for more > explanation. > > Can you ask you to open a new bug report for each specific issue? Thanks > again! Thank you for the quick response, sorry, I have recreated the issues in: https://bugs.kde.org/show_bug.cgi?id=464073 https://bugs.kde.org/show_bug.cgi?id=464074 https://bugs.kde.org/show_bug.cgi?id=464075 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464075] Plasma panel sometimes unexpectedly auto hides with wine widgets
https://bugs.kde.org/show_bug.cgi?id=464075 --- Comment #2 from Bill --- (In reply to Bill from comment #0) > SUMMARY > Plasma panel may sometimes auto hide when the cursor is above or right > clicks a wine widget. Video attached. > > STEPS TO REPRODUCE > 1. Enable auto hide on the plasma panel > 2. Enable floating panels > 3. Activate the floating panel animation. > > OBSERVED RESULT > Plasma panel hides when hovering over a wine widget. > > > EXPECTED RESULT > Plasma panel should stay open when hovering over widget. > > SOFTWARE/OS VERSIONS > KDE Plasma Version: 5.26.5 > KDE Frameworks Version: 5.101.0 > Qt Version: 5.15.7 > Plasma wayland session. Meant to be > STEPS TO REPRODUCE >1: Turn off floating panels, I could not reproduce this with floating panels >on. >2: Open a wine application which has a widget, for example the epic games >store. >3: Hover over or right click the application. In certain spots, the cursor >will change and the panel will hide. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464073] Poor animation quality with auto hide and floating panels
https://bugs.kde.org/show_bug.cgi?id=464073 --- Comment #2 from Bill --- (In reply to Nate Graham from comment #1) > Huh, cannot reproduce with current git master. Thanks for the video; it made > testing this very easy. > > It's possible this has already been fixed for 5.27 with your recent changes, > Niccolò. Do you think that's possible? Can confirm this has been fixed in plasmashell git, bug no longer happens after updating to it! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464073] Poor animation quality with auto hide and floating panels
https://bugs.kde.org/show_bug.cgi?id=464073 Bill changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 391014] New: Crashes on close
https://bugs.kde.org/show_bug.cgi?id=391014 Bug ID: 391014 Summary: Crashes on close Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bill6...@alumni.rutgers.edu Target Milestone: --- Application: showfoto (5.8.0) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.114-42-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: Hit the close butten on the window bar and got a crash message. -- Backtrace: Application: Showfoto (showfoto), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1596e099c0 (LWP 3861))] Thread 12 (Thread 0x7f153a013700 (LWP 3874)): #0 0x7f159253f0ff in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f159338a8ab in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f158e7b544b in QtAV::BlockingQueue::take() () at /usr/lib64/libQtAV.so.1 #3 0x7f158e8250cb in QtAV::ExtractThread::run() () at /usr/lib64/libQtAV.so.1 #4 0x7f1593389a29 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f159253a724 in start_thread () at /lib64/libpthread.so.0 #6 0x7f1592a81e8d in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f153a814700 (LWP 3873)): #0 0x7f159253f0ff in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f159338a8ab in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f158e7b544b in QtAV::BlockingQueue::take() () at /usr/lib64/libQtAV.so.1 #3 0x7f158e8250cb in QtAV::ExtractThread::run() () at /usr/lib64/libQtAV.so.1 #4 0x7f1593389a29 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f159253a724 in start_thread () at /lib64/libpthread.so.0 #6 0x7f1592a81e8d in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f153b015700 (LWP 3872)): #0 0x7f159253f0ff in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f159338a8ab in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f158e7b544b in QtAV::BlockingQueue::take() () at /usr/lib64/libQtAV.so.1 #3 0x7f158e8250cb in QtAV::ExtractThread::run() () at /usr/lib64/libQtAV.so.1 #4 0x7f1593389a29 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f159253a724 in start_thread () at /lib64/libpthread.so.0 #6 0x7f1592a81e8d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f153b816700 (LWP 3871)): [KCrash Handler] #6 0x7f1593382445 in QMutex::lock() () at /usr/lib64/libQt5Core.so.5 #7 0x7f159605323f in () at /usr/lib64/libdigikamcore.so.5.8.0 #8 0x7f159602bcaa in Digikam::LoadSaveThread::run() () at /usr/lib64/libdigikamcore.so.5.8.0 #9 0x7f1596069f1e in Digikam::DynamicThread::DynamicThreadPriv::run() () at /usr/lib64/libdigikamcore.so.5.8.0 #10 0x7f159338685e in () at /usr/lib64/libQt5Core.so.5 #11 0x7f1593389a29 in () at /usr/lib64/libQt5Core.so.5 #12 0x7f159253a724 in start_thread () at /lib64/libpthread.so.0 #13 0x7f1592a81e8d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f1548eb9700 (LWP 3870)): #0 0x7f159253f4a8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f159338a5e8 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f15933869e0 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f1593389a29 in () at /usr/lib64/libQt5Core.so.5 #4 0x7f159253a724 in start_thread () at /lib64/libpthread.so.0 #5 0x7f1592a81e8d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f1549724700 (LWP 3869)): #0 0x7f159253f0ff in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f159338a8ab in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f158e7b544b in QtAV::BlockingQueue::take() () at /usr/lib64/libQtAV.so.1 #3 0x7f158e8250cb in QtAV::ExtractThread::run() () at /usr/lib64/libQtAV.so.1 #4 0x7f1593389a29 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f159253a724 in start_thread () at /lib64/libpthread.so.0 #6 0x7f1592a81e8d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f154a0f3700 (LWP 3868)): #0 0x7f159253f0ff in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f159338a8ab in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f158e7b544b in QtAV::BlockingQueue::take() () at /usr/lib64/libQtAV.so.1 #3 0x7f158e8250cb in QtAV::ExtractThread::run() () at /usr/lib64/libQtAV.so.1 #4 0x7f1593389a29 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f159253a724 i
[kwin] [Bug 397530] New: KDE Windows crashed
https://bugs.kde.org/show_bug.cgi?id=397530 Bug ID: 397530 Summary: KDE Windows crashed Product: kwin Version: 5.12.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: bill6...@alumni.rutgers.edu Target Milestone: --- Application: kwin_x11 (5.12.5) Qt Version: 5.9.4 Frameworks Version: 5.45.0 Operating System: Linux 4.12.14-lp150.12.13-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: KDE screen will flash then come back and report that KDE Windows has crashed. It is an intermittant problem and I cannot see any consistancecy in the cause. It will usually occure when I selesct a window, close a window, switch desktops. One result is that some open windows are moved to the top of the desktops far enough that the title bar is no longer visable. The windows may be moved down by selecting on the frame then selecting Move. My system is using a Ninvida GeForce display and runing two desktop screens off of it. Running SUSE Leap 15.2, but the problem has been occuring since the change to Leap 42.0 The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f967b9eb940 (LWP 2729))] Thread 9 (Thread 0x7f95acad4700 (LWP 4537)): #0 0x7f96743eb89d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f96785683eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f96735df398 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f96735df7ca in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f96785670ce in () at /usr/lib64/libQt5Core.so.5 #5 0x7f96743e5559 in start_thread () at /lib64/libpthread.so.0 #6 0x7f967b36982f in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f95ad545700 (LWP 4536)): #0 0x7f96743eb89d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f96785683eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f96735df398 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f96735df7ca in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f96785670ce in () at /usr/lib64/libQt5Core.so.5 #5 0x7f96743e5559 in start_thread () at /lib64/libpthread.so.0 #6 0x7f967b36982f in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f965551e700 (LWP 4534)): #0 0x7f9678788772 in () at /usr/lib64/libQt5Core.so.5 #1 0x7f9678788048 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #2 0x7f967873309a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f96785624da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #4 0x7f9672ee9cb5 in () at /usr/lib64/libQt5Qml.so.5 #5 0x7f96785670ce in () at /usr/lib64/libQt5Core.so.5 #6 0x7f96743e5559 in start_thread () at /lib64/libpthread.so.0 #7 0x7f967b36982f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f9654b9d700 (LWP 4533)): #0 0x7f967b35f186 in ppoll () at /lib64/libc.so.6 #1 0x7f9678786ba9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f9678788186 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f967873309a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f96785624da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f9672ee9cb5 in () at /usr/lib64/libQt5Qml.so.5 #6 0x7f96785670ce in () at /usr/lib64/libQt5Core.so.5 #7 0x7f96743e5559 in start_thread () at /lib64/libpthread.so.0 #8 0x7f967b36982f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f9657fff700 (LWP 3490)): #0 0x7f967b35f186 in ppoll () at /lib64/libc.so.6 #1 0x7f9678786ba9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f9678788186 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f967873309a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f96785624da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f9672ee9cb5 in () at /usr/lib64/libQt5Qml.so.5 #6 0x7f96785670ce in () at /usr/lib64/libQt5Core.so.5 #7 0x7f96743e5559 in start_thread () at /lib64/libpthread.so.0 #8 0x7f967b36982f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f9643fff700 (LWP 2798)): #0 0x7f96743eb89d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f967769a5e4 in () at /usr/lib64/libQt5Script.so.5 #2 0x7f967769a629 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f96743e5559 in start_thread () at /lib64/libpthread.so.0 #4 0x7f
[systemsettings] [Bug 388975] New: System Settings crashed when typing in upper left search box
https://bugs.kde.org/show_bug.cgi?id=388975 Bug ID: 388975 Summary: System Settings crashed when typing in upper left search box Product: systemsettings Version: 5.11.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: j...@notjustbill.com Target Milestone: --- Application: systemsettings5 (5.11.5) Qt Version: 5.9.3 Frameworks Version: 5.41.0 Operating System: Linux 4.10.0-42-generic x86_64 Distribution: KDE neon User Edition 5.11 -- Information about the crash: - What I was doing when the application crashed: Searching for screen lock settings in search box, while using remote input feature of KDEconnect from an android device. Able to restart System Settings and complete my search in the same manner with no further crashes. The crash does not seem to be reproducible. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7651c0a8c0 (LWP 25440))] Thread 5 (Thread 0x7f761f629700 (LWP 25446)): #0 0x7f764d90470d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f764789f38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f764789f49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f764e22b6cb in QEventDispatcherGlib::processEvents (this=0x7f76180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f764e1d3e2a in QEventLoop::exec (this=this@entry=0x7f761f628ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f764dffc8f4 in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f764c0b1d25 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f764e001709 in QThreadPrivate::start (arg=0x1145570) at thread/qthread_unix.cpp:368 #8 0x7f76497286ba in start_thread (arg=0x7f761f629700) at pthread_create.c:333 #9 0x7f764d9103dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f76291ff700 (LWP 25445)): #0 0x7f764dff8b49 in std::__atomic_base::compare_exchange_strong (__m2=std::memory_order_relaxed, __m1=std::memory_order_release, __p2=0x0, __p1=@0x7f76291fea88: 0x1, this=0xe4d460) at /usr/include/c++/5/bits/atomic_base.h:752 #1 std::atomic::compare_exchange_strong (__m2=std::memory_order_relaxed, __m1=std::memory_order_release, __p2=0x0, __p1=@0x7f76291fea88: 0x1, this=0xe4d460) at /usr/include/c++/5/atomic:462 #2 QAtomicOps::testAndSetRelease (currentValue=, newValue=0x0, expectedValue=0x1, _q_value=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:299 #3 QBasicAtomicPointer::testAndSetRelease (currentValue=, newValue=0x0, expectedValue=, this=0xe4d460) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:264 #4 QBasicMutex::fastTryUnlock (current=, this=0xe4d460) at thread/qmutex.h:104 #5 QMutex::unlock (this=this@entry=0xe4d460) at thread/qmutex.cpp:337 #6 0x7f764e22b5f1 in QMutexLocker::unlock (this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:213 #7 QMutexLocker::~QMutexLocker (this=, __in_chrg=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:207 #8 QThreadData::canWaitLocked (this=0xe4d430) at ../../include/QtCore/5.9.3/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:253 #9 postEventSourcePrepare (s=0x7f76240012d0, timeout=0x7f76291feb14) at kernel/qeventdispatcher_glib.cpp:259 #10 0x7f764789e91d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f764789f2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f764789f49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f764e22b6cb in QEventDispatcherGlib::processEvents (this=0x7f76240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #14 0x7f764e1d3e2a in QEventLoop::exec (this=this@entry=0x7f76291fece0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #15 0x7f764dffc8f4 in QThread::exec (this=) at thread/qthread.cpp:515 #16 0x7f764c0b1d25 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #17 0x7f764e001709 in QThreadPrivate::start (arg=0xe4d110) at thread/qthread_unix.cpp:368 #18 0x7f76497286ba in start_thread (arg=0x7f76291ff700) at pthread_create.c:333 #19 0x7f764d9103dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f76357fc700 (LWP 25443)): #0 QTimerInfoList::timerWait (this=0x7f7630002ed0, tm=...) at kernel/qtimerinfo_unix.cpp:413 #1 0x7f764e22b43e in timerSourcePrepareHelper (timeout=0x7f76357fbb04, src=) at kernel/qeventdispatcher_glib.cpp:132 #2 timerSourcePrepare (source=, timeout=0x7f76357fbb04) at kernel/qeventdispatch
[krfb] [Bug 376614] New: VNC viewer frozen desktop cursor moves Remote desktop sees cursor
https://bugs.kde.org/show_bug.cgi?id=376614 Bug ID: 376614 Summary: VNC viewer frozen desktop cursor moves Remote desktop sees cursor Product: krfb Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: grundleb...@googlemail.com Reporter: ermschmi...@yahoo.com Target Milestone: --- VNC client Viewer connects and shows a frozen screen of the desktop. Cursor moves but no response from frozen desktop. While view at remote PC you are able to use the cursor (from the client PC) to control the desktop. Linux 4.9.6-gentoo-r1. KDE 5 Plasma. This started happening after upgrade from KDE 4 to KDE 5 plasma. I'm running a VM of the same setup as the Linux 4.9.6-gentoo-r1 but have not upgraded it to KDE 5 yet. Desktop sharing works fine. It's running Linux 4.1.15-gentoo-r1 and KDE SC Version 4.14.16. I have 2 other machines that are running Gentoo Linux with KDE 5 Plasma and there exhibiting the same problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374711] New: Kwin crashed for unknown reasons
https://bugs.kde.org/show_bug.cgi?id=374711 Bug ID: 374711 Summary: Kwin crashed for unknown reasons Product: kwin Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: bill6...@alumni.rutgers.edu Target Milestone: --- Application: kwin_x11 (5.8.3) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.36-8-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: Clicked a desktop widget to open Quicken 2016 with cxoffice. Quicken did open and kwin restarted on it's own. Currently running SUSE Leap 42.2 with plasma 5 The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc99acd5940 (LWP 7646))] Thread 10 (Thread 0x7fc8cd86a700 (LWP 21949)): #0 0x7fc99a7060af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc9978fd65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc992bb94eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fc992bb9995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fc9978fc9e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fc99a701734 in start_thread () at /lib64/libpthread.so.0 #6 0x7fc99a43fd3d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fc8ce26b700 (LWP 21948)): #0 0x7fc99a7060af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc9978fd65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc992bb94eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fc992bb9995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fc9978fc9e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fc99a701734 in start_thread () at /lib64/libpthread.so.0 #6 0x7fc99a43fd3d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fc8d014a700 (LWP 21947)): #0 0x7fc99a438b03 in select () at /lib64/libc.so.6 #1 0x7fc997b0b849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc997b0d0c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7fc997b0d527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fc997abcfdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fc9978f7f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fc9924e49b8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fc9978fc9e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fc99a701734 in start_thread () at /lib64/libpthread.so.0 #9 0x7fc99a43fd3d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fc976340700 (LWP 21865)): #0 0x7fc99a438b03 in select () at /lib64/libc.so.6 #1 0x7fc997b0b849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc997b0d0c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7fc997b0d527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fc997abcfdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fc9978f7f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fc9924e49b8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fc9978fc9e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fc99a701734 in start_thread () at /lib64/libpthread.so.0 #9 0x7fc99a43fd3d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fc977fff700 (LWP 13920)): #0 0x7fc99a7060af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc9978fd65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc992bb94eb in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fc992bb9995 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fc9978fc9e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fc99a701734 in start_thread () at /lib64/libpthread.so.0 #6 0x7fc99a43fd3d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fc97587f700 (LWP 12824)): #0 0x7ffe30df1adc in clock_gettime () #1 0x7fc99a44c806 in clock_gettime () at /lib64/libc.so.6 #2 0x7fc9979a7826 in () at /usr/lib64/libQt5Core.so.5 #3 0x7fc997b0d989 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7fc997b0cdd1 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #5 0x7fc997b0d527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fc997abcfdb in QEventLo
[ghostwriter] [Bug 492363] Ghostwriter crashes with a segment fault on very fresh installed neon after one character is typed.
https://bugs.kde.org/show_bug.cgi?id=492363 Bill changed: What|Removed |Added CC||billy.nl...@slmail.me --- Comment #1 from Bill --- I am experiencing the same bug with ghostwriter in flatpak version. I have tried removing any and all ghost writer related files I could find, reinstalling, it still crashing the moment I type anything. System Information ``` Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.6-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-1240P Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Framework Product Name: Laptop (12th Gen Intel Core) System Version: A4 ``` Running the application log ``` fprun -v org.kde.ghostwriter F: No installations directory in /etc/flatpak/installations.d. Skipping F: Opening system flatpak installation at path /var/lib/flatpak F: Opening user flatpak installation at path /home/bill/.local/share/flatpak F: Opening user flatpak installation at path /home/bill/.local/share/flatpak F: Opening system flatpak installation at path /var/lib/flatpak F: Skipping parental controls check for app/org.kde.ghostwriter/x86_64/stable since parental controls are disabled globally F: Opening user flatpak installation at path /home/bill/.local/share/flatpak F: Opening system flatpak installation at path /var/lib/flatpak F: /var/lib/flatpak/runtime/org.kde.Platform/x86_64/6.7/397775c1eec24fd5032fe12f579b886178352172deb60f8c80a372925e69cf46/files/lib32 does not exist F: Cleaning up unused container id 1761282217 F: Cleaning up per-app-ID state for org.kde.ghostwriter F: Cleaning up unused container id 3460480520 F: Cleaning up per-app-ID state for org.kde.ghostwriter F: Allocated instance id 2405861914 F: Add defaults in dir /org/kde/ghostwriter/ F: Add locks in dir /org/kde/ghostwriter/ F: Allowing dri access F: Allowing wayland access F: Allowing pulseaudio access F: Pulseaudio user configuration file '/home/bill/.config/pulse/client.conf': Error opening file /home/bill/.config/pulse/client.conf: No such file or directory F: Running '/usr/bin/bwrap --args 40 -- /usr/bin/xdg-dbus-proxy --args=39' F: Running '/usr/bin/bwrap --args 38 -- ghostwriter' [ 0.161 2 ghostwriter ] INFO Backup files will be stored in "/home/bill/.var/app/org.kde.ghostwriter/data/ghostwriter/backups/" ``` -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 332876] valgrind (memcheck) hangs intermittently
https://bugs.kde.org/show_bug.cgi?id=332876 Bill Torpey changed: What|Removed |Added CC||wallstp...@gmail.com --- Comment #15 from Bill Torpey --- Just FYI -- the problem mentioned previously had remained through the 3.11 release -- however, with the 3.12.0 release it appears that it has resolved itself. I'm curious if there were any changes that you think may have caused this? >From the release notes, it looks like 361615 could be a candidate? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #235 from Bill Michaelson --- (In reply to abrahams from comment #234) > I've dealt with this situation by sticking with Kubuntu 14.04, which is a > long-term release and should be maintained for a few years more. Not a > permanent solution, unfortunately. I'm doing the same while I look for alternatives. I would live with this problem but based on this thread and experience, I fear there are other regressions that are more serious that will never be fixed. In particular, during my brief attempt to use 5, I was unable to use tabbed windows which I find to be immensely convenient. Perhaps I overlooked something there. It is very discouraging. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 376259] New: Konqueror KDE Crash
https://bugs.kde.org/show_bug.cgi?id=376259 Bug ID: 376259 Summary: Konqueror KDE Crash Product: konqueror Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: wrrei...@gmail.com Target Milestone: --- Application: konqueror (4.14.25) KDE Platform Version: 4.14.25 Qt Version: 4.8.6 Operating System: Linux 4.4.36-8-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: Used Konqueror to log into Vanguard.com. On Vanguard site select video which opened in new tab. Closed video tab and Konqueror crsshed. KDE Plasma Version 5.8.3 Memory 7.7 GiB RAM openSUSE-Leap-42.2 -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdcca396780 (LWP 24990))] Thread 11 (Thread 0x7fdc48941700 (LWP 25303)): #0 0x7fdcc79508e9 in syscall () at /lib64/libc.so.6 #1 0x7fdcc4a9a8ef in g_cond_wait () at /usr/lib64/libglib-2.0.so.0 #2 0x7fdca8743502 in () at /usr/lib64/libgstbase-1.0.so.0 #3 0x7fdca8744936 in gst_data_queue_pop () at /usr/lib64/libgstbase-1.0.so.0 #4 0x7fdc49c3bbb8 in () at /usr/lib64/gstreamer-1.0/libgstcoreelements.so #5 0x7fdca847b399 in () at /usr/lib64/libgstreamer-1.0.so.0 #6 0x7fdcc4a7e32c in () at /usr/lib64/libglib-2.0.so.0 #7 0x7fdcc4a7d9a5 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7fdcc8c59734 in start_thread () at /lib64/libpthread.so.0 #9 0x7fdcc7954d3d in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7fdc49362700 (LWP 25302)): #0 0x7fdcc79508e9 in syscall () at /lib64/libc.so.6 #1 0x7fdcc4a9a8ef in g_cond_wait () at /usr/lib64/libglib-2.0.so.0 #2 0x7fdca847b57b in () at /usr/lib64/libgstreamer-1.0.so.0 #3 0x7fdcc4a7e32c in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fdcc4a7d9a5 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7fdcc8c59734 in start_thread () at /lib64/libpthread.so.0 #6 0x7fdcc7954d3d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fdcb089b700 (LWP 25297)): #0 0x7fdcc79508e9 in syscall () at /lib64/libc.so.6 #1 0x7fdcc4a9a8ef in g_cond_wait () at /usr/lib64/libglib-2.0.so.0 #2 0x7fdca8743502 in () at /usr/lib64/libgstbase-1.0.so.0 #3 0x7fdca8744936 in gst_data_queue_pop () at /usr/lib64/libgstbase-1.0.so.0 #4 0x7fdc49c3bbb8 in () at /usr/lib64/gstreamer-1.0/libgstcoreelements.so #5 0x7fdca847b399 in () at /usr/lib64/libgstreamer-1.0.so.0 #6 0x7fdcc4a7e32c in () at /usr/lib64/libglib-2.0.so.0 #7 0x7fdcc4a7d9a5 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7fdcc8c59734 in start_thread () at /lib64/libpthread.so.0 #9 0x7fdcc7954d3d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fdc5a855700 (LWP 25054)): #0 0x7fdcc8c5e0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdc5b8bed39 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #2 0x7fdc5b8bf7d9 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #3 0x7fdcc8c59734 in start_thread () at /lib64/libpthread.so.0 #4 0x7fdcc7954d3d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fdc5b056700 (LWP 25053)): #0 0x7fdcc8c5e0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdc5b8bed39 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #2 0x7fdc5b8bf7d9 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #3 0x7fdcc8c59734 in start_thread () at /lib64/libpthread.so.0 #4 0x7fdcc7954d3d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fdc5b857700 (LWP 25052)): #0 0x7fdcc8c5e0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdc5b8bed39 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #2 0x7fdc5b8bf7d9 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #3 0x7fdcc8c59734 in start_thread () at /lib64/libpthread.so.0 #4 0x7fdcc7954d3d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fdc6175e700 (LWP 25025)): #0 0x7fdcc8c5e0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdcaae0595d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7fdcab0ba806 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7fdcc8c59734 in start_thread () at /lib64/libpthread.so.0 #4 0x7fdcc7954d3d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fdcb3c29700 (LWP 25024)): #0 0x7fdcc8c60d1d in read () at /lib64/libpthread.so.0 #1 0x7fdcc4a99670 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fdcc4a58e49 in g_main
[digikam] [Bug 150531] SCHEMA : add album password-protect feature
https://bugs.kde.org/show_bug.cgi?id=150531 Bill Goodman changed: What|Removed |Added CC||bg+k...@cyclos.com --- Comment #25 from Bill Goodman --- I have a related but somewhat different request. I would like to be able to launch digikam for a friend or child to browse without allowing them to make any modifications. Digikam is a great tool for searching for interesting photos in many different ways using tags, etc. But I would never allow a child to access the system this way because they could do massive damage to the tags, captions and other info in the database and photos. I would like to have a protected mode where after "locking" digiKam, no changes to the database or photos would be allowed until a password was supplied. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376423] New: Inconsistent ENTER key in thumbnails view
https://bugs.kde.org/show_bug.cgi?id=376423 Bug ID: 376423 Summary: Inconsistent ENTER key in thumbnails view Product: digikam Version: 5.4.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Thumbnails Assignee: digikam-de...@kde.org Reporter: bg+k...@cyclos.com Target Milestone: --- The action of the ENTER key is inconsistent in the thumbnails view. With an image selected in the thumbnails view, hitting the ENTER key sometimes opens the preview view and sometimes does nothing. To reproduce, double-click an image in the thumbnails view to open the preview window. Exit the preview window by pressing the ESCAPE key. At this point, you can move the selection to different images using the UP/DOWN/LEFT/RIGHT arrow keys. Pressing ENTER will open the selected image in preview. This is the desired operation (in my opinion). If, instead of using the arrow keys, you move the selection to another image by clicking on it with the mouse, the ENTER key will NOT open the preview. This also seems to be the default mode when the thumbnail view is first opened. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376425] New: Light table window not activated or brought to front
https://bugs.kde.org/show_bug.cgi?id=376425 Bug ID: 376425 Summary: Light table window not activated or brought to front Product: digikam Version: 5.4.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Usability Assignee: digikam-de...@kde.org Reporter: bg+k...@cyclos.com Target Milestone: --- In the thumbnails view, click the Light Table button to open the Light Table Window. Switch back to the main DigiKam window containing the thumbnails view. Click the Light Table button again. Nothing happens. It seems like a normal expectation would be for the Light Table window to be activated and brought to the front. This is especially a problem when the main window is maximized because the Light Table window is hidden behind and the Light Table button appears to do nothing. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 359815] Window is not maximized after exiting full screen mode
https://bugs.kde.org/show_bug.cgi?id=359815 Bill Goodman changed: What|Removed |Added CC||bg+k...@cyclos.com --- Comment #3 from Bill Goodman --- I see this same problem in Windows 7. With a maximized thumbnails or preview window, after clicking the Full Screen icon to enter full screen mode and then exiting full screen mode, the window is no longer maximized. This operation is not consistent. Sometimes the window is properly restored as maximized, but usually it is restored in the standard window state. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 359815] Window is not maximized after exiting full screen mode
https://bugs.kde.org/show_bug.cgi?id=359815 --- Comment #4 from Bill Goodman --- (In reply to Bill Goodman from comment #3) > I see this same problem in Windows 7. With a maximized thumbnails or preview > window, after clicking the Full Screen icon to enter full screen mode and > then exiting full screen mode, the window is no longer maximized. > > This operation is not consistent. Sometimes the window is properly restored > as maximized, but usually it is restored in the standard window state. Ooops. I'm sorry. Please ignore this comment. I am seeing this on a different component. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376426] New: Exit Full Screen does not restore maximized window
https://bugs.kde.org/show_bug.cgi?id=376426 Bug ID: 376426 Summary: Exit Full Screen does not restore maximized window Product: digikam Version: 5.4.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Usability Assignee: digikam-de...@kde.org Reporter: bg+k...@cyclos.com Target Milestone: --- Maximize the main DigiKam window with either thumbnails or preview. Click Full Screen icon to switch to full screen mode. Click Exit Full Screen icon to exit full screen mode. Window usually restores to "normal" mode instead of maximized mode. I have found that this failure does not always happen, but typically once it fails, it continues to fail. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376427] New: Range selection in thumbnail view gets wrong endpoint
https://bugs.kde.org/show_bug.cgi?id=376427 Bug ID: 376427 Summary: Range selection in thumbnail view gets wrong endpoint Product: digikam Version: 5.4.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Thumbnails Assignee: digikam-de...@kde.org Reporter: bg+k...@cyclos.com Target Milestone: --- The selection anchor or endpoint seems to get changed incorrectly when switching between Thumbnail and Preview modes. As an example: !) Select the 1st image in a thumbnail view. 2) Double-click the image to enter preview. 3) In preview, click the 2nd image in the filmstrip. 4) Press ESCAPE key to return to thumbnail view. The 2nd image is selected. 5) SHIFT-CLICK the 4th image. Images 1-4 are selected. Only images 2-4 should be selected. Note that if step #3 is changed so that the 2nd image is selected by using the RIGHT-ARROW key, the selection in step 5 will operate correctly. It seems like there is a difference in how the selections are registered depending on whether it is a mouse click or an arrow key. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376423] Inconsistent ENTER key in thumbnails view
https://bugs.kde.org/show_bug.cgi?id=376423 --- Comment #2 from Bill Goodman --- (In reply to caulier.gilles from comment #1) > I think this problem have been fixed in next release. > > Take a look to 5.5.0 pre version available here : > > https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM > > Gilles Caulier I installed the version above on Windows 7. The issue is still there. ENTER has no effect after the selection is changed with a mouse click. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 281742] ICONVIEW : wrong selection start when browsing images
https://bugs.kde.org/show_bug.cgi?id=281742 --- Comment #13 from Bill Goodman --- (In reply to Maik Qualmann from comment #12) > *** Bug 376427 has been marked as a duplicate of this bug. *** Great! I can confirm that this fix seems to have fixed the problem observed on Windows 7. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376423] Inconsistent ENTER key in thumbnails view
https://bugs.kde.org/show_bug.cgi?id=376423 --- Comment #4 from Bill Goodman --- There is a configuration setting (Views>Icons>Thumbnail click action) which selects either preview or image editor. This seems to be for a "double-click" action in spite of the name saying "click". It seems natural to me for the ENTER key to do the same action that double-click does in this context. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376640] New: Changing tag name does not update sidecar metadata
https://bugs.kde.org/show_bug.cgi?id=376640 Bug ID: 376640 Summary: Changing tag name does not update sidecar metadata Product: digikam Version: 5.5.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Metadata-Editor Assignee: digikam-de...@kde.org Reporter: bg+k...@cyclos.com Target Milestone: --- When I add a tag to an image, the sidecar file is updated as expected. However, if I change the name of a tag which has already been applied to an image, the sidecar file is not updated. Settings Use lazy synchronization = OFF Read from sidecar files = ON Write to sidecar files = ON (Write to XMP sidecar only) Select an image in thumbnail view. Create a new tag "tag1". Click Apply. Exit DigiKam. Verify sidecar file includes "tag1". Start DigiKam. Select same image. Right click "tag1" and choose "Properties". Change Title to "tag2". Click Apply. (thumbnail shows tag2) Exit DigiKam. Sidecar still contains "tag1". If you do "Album>Write Metadata to Images", the sidecar will update to include "tag2" as expected. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376640] Changing tag name does not update sidecar metadata
https://bugs.kde.org/show_bug.cgi?id=376640 --- Comment #1 from Bill Goodman --- An additional problem which may be related. If you use the tag manager to delete a tag which is assigned to some images, the tag is removed from the images in the database, but the sidecar files are not updated with this change (i.e. the sidecar still has the deleted tag). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376650] New: Write Meta Data hangs if album is empty
https://bugs.kde.org/show_bug.cgi?id=376650 Bug ID: 376650 Summary: Write Meta Data hangs if album is empty Product: digikam Version: 5.5.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Metadata Assignee: digikam-de...@kde.org Reporter: bg+k...@cyclos.com Target Milestone: --- Select an empty album. Execute Album>Write Metadata to Images menu command. Processing begins with "Synchronizing image metadata with database" but progress never advances beyond 0%. Attempting to execute other metadata write commands is blocked. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 376708] New: KStars 2.7.5 (WIN) Plate Solver Command Line Arguments Error
https://bugs.kde.org/show_bug.cgi?id=376708
Bug ID: 376708
Summary: KStars 2.7.5 (WIN) Plate Solver Command Line Arguments
Error
Product: kstars
Version: unspecified
Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: mutla...@ikarustech.com
Reporter: b...@outlook.com
Target Milestone: ---
When customizing the option arguments for the plate solver in KStars/Ekos I
noticed a fair amount of inconsistencies.
With the default values all enabled through the UI button, the options show
this:
--no-verify --no-plots --resort --no-fits2fits --downsample 2 -O -L 0 -H 0 -u
aw -3 287.817 -4 89.9972 -5 30
When I attempt to use Blind Solve via the Load and Slew button, this is what
the ANSVR log shows:
[2017-02-20 03:18:48] [Connect from 127.0.0.1]
[2017-02-20 03:18:48] POST /api/login HTTP/1.1
[2017-02-20 03:18:48] removing stale tmpdir /var/tmp/platesolve/45
[2017-02-20 03:18:48] removing stale tmpdir /var/tmp/platesolve/46
[2017-02-20 03:18:48] POST /api/upload HTTP/1.1
[2017-02-20 03:18:48] request_json is:
{"allow_commercial_use":"n","allow_modifications":"n","center_dec":24,"center_ra":45,"downsample_factor":2,"publicly_visible":"n","radius":2.440489677610497e-152,"scale_lower":2.1132927118286117e+214,"scale_type":"ul","scale_units":"arcminwidth","scale_upper":2.234263831832233e-52,"session":"64"}
[2017-02-20 03:18:48] UPLOAD: session is 64
[2017-02-20 03:18:48] upload type is: FITS
[2017-02-20 03:18:48] GET /api/submissions/64 HTTP/1.1
scale_args: -u arcminwidth -L 2.11329271182861e+214 -H 2.23426383183223e-52 -3
45 -4 24 -5 2.4404896776105e-152
UPLOAD: /opt/ansvr/run_solver 480 /usr/bin/solve-field -p -O -U none -B none -R
none -M none -N none -C cancel --crpix-center -z 2 -u arcminwidth -L
2.11329271182861e+214 -H 2.23426383183223e-52 -3 45 -4 24 -5
2.4404896776105e-152 stars.fit
[2017-02-20 03:18:48] SUBS: solve is not done yet
[2017-02-20 03:18:48] SUBS: jstr:
{"processing_finished":"0","user":"0","processing_started":"1","user_images":[],"jobs":[]}
[2017-02-20 03:18:50] GET /api/submissions/64 HTTP/1.1
Using timeout = 480
exec /usr/bin/solve-field -p -O -U none -B none -R none -M none -N none -C
cancel --crpix-center -z 2 -u arcminwidth -L 2.11329271182861e+214 -H
2.23426383183223e-52 -3 45 -4 24 -5 2.4404896776105e-152 stars.fit
Reading input file 1 of 1: "stars.fit"...
Computing image percentiles...
Extracting sources...
Downsampling by 2...
[2017-02-20 03:18:50] SUBS: solve is not done yet
[2017-02-20 03:18:50] SUBS: jstr:
{"processing_started":"1","user":"0","jobs":[],"user_images":[],"processing_finished":"0"}
[2017-02-20 03:18:52] GET /api/submissions/64 HTTP/1.1
simplexy: found 1595 sources.
[2017-02-20 03:18:52] SUBS: solve is not done yet
[2017-02-20 03:18:52] SUBS: jstr:
{"processing_finished":"0","user_images":[],"jobs":[],"user":"0","processing_started":"1"}
[2017-02-20 03:18:54] GET /api/submissions/64 HTTP/1.1
Solving...
Reading file "./stars.axy"...
backend-main.cScale range 2.72332e+212 to 2.87921e-54 is invalid: min must be
>= 0, max must be >= min.
:321:main: Failed to read job file "./stars.axy"
solve-field.c:518:run_backend backend failed. Command that failed was:
/usr/lib/astrometry/bin/backend ./stars.axy
ioutils.c:605:run_command_get_outputs Command failed: return value 255
FAILED
pid 1556 exiting
[2017-02-20 03:18:54] SUBS: solve is done
[2017-02-20 03:18:54] SUBS: jstr:
{"processing_started":"1","user":"0","user_images":[],"jobs":[64],"processing_finished":"1"}
[2017-02-20 03:18:54] GET /api/jobs/64 HTTP/1.1
[2017-02-20 03:18:54] JOBS: jobid: 64 calibration: ''
[2017-02-20 03:18:54] send job status
[2017-02-20 03:18:54] JOBS: jstr: {"status":"failure"}
[2017-02-20 03:18:54] JOBS: job completed in 6 seconds
scale_args: -u arcminwidth -L 2.11329271182861e+214 -H 2.23426383183223e-52 -3
45 -4 24 -5 2.4404896776105e-152
UPLOAD: /opt/ansvr/run_solver 480 /usr/bin/solve-field -p -O -U none -B none -R
none -M none -N none -C cancel --crpix-center -z 2 -u arcminwidth -L
2.11329271182861e+214 -H 2.23426383183223e-52 -3 45 -4 24 -5
2.4404896776105e-152 stars.fit
Using timeout = 480
exec /usr/bin/solve-field -p -O -U none -B none -R none -M none -N none -C
cancel --crpix-center -z 2 -u arcminwidth -L 2.11329271182861e+214 -H
2.23426383183223e-52 -3 45 -4 24 -5 2.4404896776105e-152 stars.fit
Reading input file 1 of 1: "stars.fit"...
Computing image percentiles...
Extracting sources...
Downsampling by 2...
simplexy: found 1595 sources.
Solving...
Reading file "./stars.axy"...
backend-main.cScale range 2.72332e+212 to 2.87921e-54 is invalid: min must be
>= 0, max must be >= min.
:321:main: Failed to read job file "./stars.axy"
solve-field.c:518:run_backend backend failed. Command that failed was:
/usr/lib/astrometry/bin/backend ./stars.axy
ioutils.c:60
[kstars] [Bug 376708] KStars 2.7.5 (WIN) Plate Solver Command Line Arguments Error
https://bugs.kde.org/show_bug.cgi?id=376708 --- Comment #2 from Bill Long --- Fantastic. Once the new build is live, I will be sure to grab it and do some testing. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 376708] KStars 2.7.5 (WIN) Plate Solver Command Line Arguments Error
https://bugs.kde.org/show_bug.cgi?id=376708 --- Comment #4 from Bill Long --- I tested this and the new module is fantastic. There is one remaining problem. The arguments defined dont actually get passed to the ANSVR: Configured this: -O --no-plots --no-verify --resort --downsample 2 Verbose window shows this: 2017-02-20T13:05:32 Using solver options: -O --no-plots --no-verify --resort --downsample 2 -3 45 -4 24 -5 15 ANSVR receives this: UPLOAD: /opt/ansvr/run_solver 480 /usr/bin/solve-field -p -O -U none -B none -R none -M none -N none -C cancel --crpix-center -z 2 -u arcminwidth -L 0 -H 0 -3 45 -4 24 -5 0 stars.fit If I put this in the custom box: -u arcsecperpix -L 6.85596 -H 7.57764 Verbose shows this: 2017-02-20T13:13:02 Using solver options: -O --no-plots --no-verify --resort --downsample 2 -u arcsecperpix -L 6.85596 -H 7.57764 -3 45 -4 24 -5 15 ANSVR receives this: UPLOAD: /opt/ansvr/run_solver 480 /usr/bin/solve-field -p -O -U none -B none -R none -M none -N none -C cancel --crpix-center -z 2 -u arcminwidth -L 0 -H 0 -3 45 -4 24 -5 0 stars.fit The problem with user inputted values disappearing is gone, those seem to work fine now. The actual command sent to the ANSVR still doesn't seem to use the right string. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 376736] New: KStars (WIN64) Does not save telescope information
https://bugs.kde.org/show_bug.cgi?id=376736 Bug ID: 376736 Summary: KStars (WIN64) Does not save telescope information Product: kstars Version: unspecified Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: b...@outlook.com Target Milestone: --- Created attachment 104136 --> https://bugs.kde.org/attachment.cgi?id=104136&action=edit Screenshot of the issue Simple bug here, when you try to save the telescope information in the telescope module you receive this error: 2017-02-20T13:51:31 Failed to save telescope information. See attachment for more details. I have rebooted, reinstalled, ran as admin, nothing seems to solve this issue. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 376736] KStars (WIN64) Does not save telescope information
https://bugs.kde.org/show_bug.cgi?id=376736 --- Comment #2 from Bill Long --- Thanks for the confirmation. I was wondering why I had the same problem trying this on a Linux host machine as well. Now it makes sense. I have a Raspberry Pi 3 arriving in the mail tomorrow, so I will set that up as my INDI Server using Linux. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 376736] KStars (WIN64) Does not save telescope information
https://bugs.kde.org/show_bug.cgi?id=376736 --- Comment #4 from Bill Long --- Well timed comment, as I just prepared the SD Card with Raspbian. I will grab Ubuntu Mate instead. Thanks for the tip! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376825] New: Tag displays do not display correctly after new database is selected
https://bugs.kde.org/show_bug.cgi?id=376825 Bug ID: 376825 Summary: Tag displays do not display correctly after new database is selected Product: digikam Version: 5.5.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tags Assignee: digikam-de...@kde.org Reporter: bg+k...@cyclos.com Target Milestone: --- Two different sequences cause the tags browser pane and the tags edit pane to not display existing tags correctly. First sequence -- Launch digiKam with an existing database. In Settings>Configure digiKam>Database select a different database which already exists. When prompted, choose to "Use Existing File". Tags browser pane and Tags edit pane are missing some tags which exist in the 2nd database. Quit digiKam and re-launch. Tags now appear correctly in both panes. Second sequence --- Launch digiKam with an existing database. In Settings>Configure digiKam>Database select a location for a new, non-existing database. When prompted, choose to "Create New Database". Add a collection which contains some photos. Select a photo in the thumbnails view. Create a new tag in the tags edit pane. Tag is not displayed in the edit pane or in the tags browser pane. (However, if you try to create the tag again, you will get an error that the "tag already exists" even though it is not displayed) Quit and re-launch digiKam and new tag appears. --- Note that this problem does not occur consistently for all databases and photos. However, when it does occur, it is completely repeatable. I have a database with 200 tags and it consistently displays 197 tags after I switch databases. Quit and relaunch will correctly display all 200 tags. I have not been able to determine a rule for which tags are not displayed. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 376871] New: KAlarm Crash
https://bugs.kde.org/show_bug.cgi?id=376871 Bug ID: 376871 Summary: KAlarm Crash Product: kalarm Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: djar...@kde.org Reporter: billrori...@gmail.com Target Milestone: --- Application: kalarm (2.11.13-5) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.4.0-64-generic x86_64 Distribution: KDE neon User Edition 5.9 -- Information about the crash: - What I was doing when the application crashed: I was trying to select the sound for an alarm, and when i clicked the button to open the file browser window, the application crashed. - Custom settings of the application: it is possible that the option to autoplay the sound file on mouse hover has something to do with it. I do not have solid proof of this, it is just a hunch. was going to try and disable it, but file browser window does not stay open long enough for me to click the radio button. The crash can be reproduced every time. -- Backtrace: Application: KAlarm (kalarm), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7a128569c0 (LWP 13209))] Thread 4 (Thread 0x7f79d8182700 (LWP 13225)): [KCrash Handler] #6 0x7f79f27924cb in vorbis_info_clear () from /usr/lib/x86_64-linux-gnu/libvorbis.so.0 #7 0x7f79cce365f4 in ?? () from /usr/lib/vlc/plugins/demux/libogg_plugin.so #8 0x7f79cce3669a in ?? () from /usr/lib/vlc/plugins/demux/libogg_plugin.so #9 0x7f79cce367b0 in ?? () from /usr/lib/vlc/plugins/demux/libogg_plugin.so #10 0x7f79d375cc60 in vlc_module_unload () from /usr/lib/libvlccore.so.8 #11 0x7f79d37112f2 in ?? () from /usr/lib/libvlccore.so.8 #12 0x7f79d3720436 in ?? () from /usr/lib/libvlccore.so.8 #13 0x7f79d37273cd in ?? () from /usr/lib/libvlccore.so.8 #14 0x7f7a084da6ba in start_thread (arg=0x7f79d8182700) at pthread_create.c:333 #15 0x7f7a0d8e182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f79e1501700 (LWP 13212)): #0 0x7f7a0d8d169d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f7a061f86f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7a061b4e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7a061b5330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f7a061b549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f7a0e41a75b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f7a0e3c50ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f7a0e1f4f64 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f7a0e1f9b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f7a084da6ba in start_thread (arg=0x7f79e1501700) at pthread_create.c:333 #10 0x7f7a0d8e182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f79e1d02700 (LWP 13211)): #0 0x7f7a0e419eaf in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f7a061b491d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7a061b52bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7a061b549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f7a0e41a75b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7a0e3c50ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f7a0e1f4f64 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f7a0eb10735 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f7a0e1f9b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f7a084da6ba in start_thread (arg=0x7f79e1d02700) at pthread_create.c:333 #10 0x7f7a0d8e182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f7a128569c0 (LWP 13209)): #0 0x7f7a084db98d in pthread_join (threadid=140161293231872, thread_return=0x0) at pthread_join.c:90 #1 0x7f79d372504f in input_Close () from /usr/lib/libvlccore.so.8 #2 0x7f79d34c6460 in libvlc_media_player_release () from /usr/lib/libvlc.so.5 #3 0x7f79d3a0c11b in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/phonon4qt5_backend/phonon_vlc.so #4 0x7f7a0e3f0663 in QObjectPrivate::deleteChildren() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7a0e3f9814 in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f79d3a06989 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/
[digikam] [Bug 374355] Video preview lags in the beginning
https://bugs.kde.org/show_bug.cgi?id=374355 --- Comment #13 from Bill Goodman --- The lag seems to be gone on my Windows 7 system. There is a 1-2 second delay the first time I play a video, but then the video plays correctly from the beginning. I think that previously it was advancing through the movie during that time without correctly showing video. And it seems that after the first play, on subsequent plays the video shows with no initial delay at all, like something is being cached somewhere. This seems to be true even if I exit digiKam and restart it. More good news: the extremely annoying repeat of audio at the end of playing a movie also seems to be fixed. Bad news: In preview, switching from one video to another while the first video is playing causes the media player to report an error and no video is shown. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374355] Video preview lags in the beginning
https://bugs.kde.org/show_bug.cgi?id=374355 --- Comment #16 from Bill Goodman --- Created attachment 104518 --> https://bugs.kde.org/attachment.cgi?id=104518&action=edit Screenshot of video switch failure Screenshot of DebugView log during video switch failure. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374355] Video preview lags in the beginning
https://bugs.kde.org/show_bug.cgi?id=374355 --- Comment #18 from Bill Goodman --- Created attachment 104519 --> https://bugs.kde.org/attachment.cgi?id=104519&action=edit DebugView log of video switch failure 1: Launch digiKam 276: Open preview of first video 283: Switch to second video -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374355] Video preview lags in the beginning
https://bugs.kde.org/show_bug.cgi?id=374355 --- Comment #19 from Bill Goodman --- I added a lengthy comment previously, but it seems to have disappeared. What I observe is that when a video is started in Preview, it plays normally. If I switch to a second video while the first is playing, I can hear the second video playing but there is no image. Only the message "An error has occurred with the media player...". If I wait until the audio stops and select another video, it plays properly. I don't think this was happening in the digiKam 5.5 version I downloaded on Feb 13. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374355] Video preview lags in the beginning
https://bugs.kde.org/show_bug.cgi?id=374355 --- Comment #21 from Bill Goodman --- When run from a console, it appears that control is immediately returned to the user, i.e. there is a console prompt. digiKam does not output any information at all. I looked in the Windows event viewer but did not find anything that seemed to be relevant to digiKam, QtAV or QT. Is the error message displayed by digiKam or by QtAV? Are you using a different version of QtAV now than what was used on Feb 13? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374355] Video preview lags in the beginning
https://bugs.kde.org/show_bug.cgi?id=374355 --- Comment #23 from Bill Goodman --- I just reinstalled digiKam 5.5 (11 Feb 2017). It does not have a problem with switching videos while one is playing. -- You are receiving this mail because: You are watching all bug changes.
