[plasmashell] [Bug 371936] New: Plasma crash on Login
https://bugs.kde.org/show_bug.cgi?id=371936 Bug ID: 371936 Summary: Plasma crash on Login Product: plasmashell Version: 5.8.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: crgla...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.2) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.1.34-33-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Plasma crashed on login. I had locked the system overnight and at loggin back in the crash message occured. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdd32c267c0 (LWP 2432))] Thread 11 (Thread 0x7fdc50bbe700 (LWP 3153)): #0 0x7fdd2bbc703f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fdd2caba4cb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7fdd3092e22b in ?? () from /usr/lib64/libQt5Quick.so.5 #3 0x7fdd309300c5 in ?? () from /usr/lib64/libQt5Quick.so.5 #4 0x7fdd2cab9859 in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7fdd2bbc30a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7fdd2c3c202d in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7fdc53fff700 (LWP 3112)): #0 0x7fdd2bbc703f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fdd2caba4cb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7fdd3092e22b in ?? () from /usr/lib64/libQt5Quick.so.5 #3 0x7fdd309300c5 in ?? () from /usr/lib64/libQt5Quick.so.5 #4 0x7fdd2cab9859 in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7fdd2bbc30a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7fdd2c3c202d in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7fdc59910700 (LWP 3106)): #0 0x7ffedabbfd35 in clock_gettime () #1 0x7fdd2c3cec7d in clock_gettime () from /lib64/libc.so.6 #2 0x7fdd2cb5d8b1 in ?? () from /usr/lib64/libQt5Core.so.5 #3 0x7fdd2ccbd5d9 in QTimerInfoList::updateCurrentTime() () from /usr/lib64/libQt5Core.so.5 #4 0x7fdd2ccbec85 in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7fdd274aa8f1 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #6 0x7fdd274aadf8 in ?? () from /usr/lib64/libglib-2.0.so.0 #7 0x7fdd274aaf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #8 0x7fdd2ccbef4b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #9 0x7fdd2cc6e89b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #10 0x7fdd2cab502a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #11 0x7fdc5ad38cb7 in KCupsConnection::run() () from /usr/lib64/libkcupslib.so #12 0x7fdd2cab9859 in ?? () from /usr/lib64/libQt5Core.so.5 #13 0x7fdd2bbc30a4 in start_thread () from /lib64/libpthread.so.0 #14 0x7fdd2c3c202d in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7fdc66e3f700 (LWP 3097)): #0 0x7fdd2bbc703f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fdd2caba4cb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7fdd3092e22b in ?? () from /usr/lib64/libQt5Quick.so.5 #3 0x7fdd309300c5 in ?? () from /usr/lib64/libQt5Quick.so.5 #4 0x7fdd2cab9859 in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7fdd2bbc30a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7fdd2c3c202d in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7fdc760a8700 (LWP 3041)): #0 0x7fdd2bbc703f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fdd2caba4cb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7fdd3092e22b in ?? () from /usr/lib64/libQt5Quick.so.5 #3 0x7fdd309300c5 in ?? () from /usr/lib64/libQt5Quick.so.5 #4 0x7fdd2cab9859 in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7fdd2bbc30a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7fdd2c3c202d in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7fdc768a9700 (LWP 3023)): #0 0x7fdd2c3b9bfd in poll () from /lib64/libc.so.6 #1 0x7fdd274aae64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fdd274aaf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fdd2ccbef4b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fdd2cc6e89b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fdd2cab502a in QThread::exec() () from /usr/lib64/lib
[kwin] [Bug 344326] Buffer objects (VBO, FBO) need remapping after suspend/vt switch with NVIDIA
https://bugs.kde.org/show_bug.cgi?id=344326 --- Comment #123 from Chris --- I just updated, rebooted, and tested suspend. Still consistently getting the desktop label issue. Still using GTX 980. I'll be more specific with versions this time: Linux 4.8.6, Plasma/KWin 5.8.3, Nvidia 375.10 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 372260] New: Crash at shutdown
https://bugs.kde.org/show_bug.cgi?id=372260 Bug ID: 372260 Summary: Crash at shutdown Product: kontact Version: 5.2.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: crgla...@gmail.com Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.1.34-33-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Everytime I try to close Kontact I receive this crash report. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb62aec0800 (LWP 27187))] Thread 45 (Thread 0x7fb5177ea700 (LWP 30482)): #0 0x7fb627b6ebfd in poll () from /lib64/libc.so.6 #1 0x7fb61f108e64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb61f108f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb62868af4b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fb62863a89b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fb62848102a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fb628485859 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7fb620ecc0a4 in start_thread () from /lib64/libpthread.so.0 #8 0x7fb627b7702d in clone () from /lib64/libc.so.6 Thread 44 (Thread 0x7fb517feb700 (LWP 30476)): #0 0x7fb627b6accd in read () from /lib64/libc.so.6 #1 0x7fb616a3d073 in ?? () from /usr/lib64/tls/libnvidia-tls.so.367.57 #2 0x7fb61f149b60 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb61f108999 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #4 0x7fb61f108df8 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7fb61f108f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #6 0x7fb62868af4b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7fb62863a89b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #8 0x7fb62848102a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #9 0x7fb628485859 in ?? () from /usr/lib64/libQt5Core.so.5 #10 0x7fb620ecc0a4 in start_thread () from /lib64/libpthread.so.0 #11 0x7fb627b7702d in clone () from /lib64/libc.so.6 Thread 43 (Thread 0x7fb5187ec700 (LWP 30470)): #0 0x7fb627b6ebfd in poll () from /lib64/libc.so.6 #1 0x7fb61f108e64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb61f108f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb62868af4b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fb62863a89b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fb62848102a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fb628485859 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7fb620ecc0a4 in start_thread () from /lib64/libpthread.so.0 #8 0x7fb627b7702d in clone () from /lib64/libc.so.6 Thread 42 (Thread 0x7fb518fed700 (LWP 30465)): #0 0x7fb61f10880d in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #1 0x7fb61f108df8 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb61f108f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb62868af4b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fb62863a89b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fb62848102a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fb628485859 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7fb620ecc0a4 in start_thread () from /lib64/libpthread.so.0 #8 0x7fb627b7702d in clone () from /lib64/libc.so.6 Thread 41 (Thread 0x7fb51aff1700 (LWP 30459)): #0 0x7fb61f14acf9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7fb61f108e4a in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb61f108f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb62868af4b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fb62863a89b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fb62848102a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fb628485859 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7fb620ecc0a4 in start_thread () from /lib64/libpthread.so.0 #8 0x7fb627b7702d in clone () from /lib64/libc.so.6 Thread 40 (Thread 0x7fb51a7f0700 (LWP 30454)): #0 0x7fb627b6ebfd in poll () from /lib64/libc.so.6 #1 0x7fb61f108e64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb61f108f7c in g_main_c
[kwin] [Bug 344326] Buffer objects (VBO, FBO) need remapping after suspend/vt switch with NVIDIA
https://bugs.kde.org/show_bug.cgi?id=344326 --- Comment #124 from Chris --- New drivers with new kernel were recently released, Linux 4.8.8 and Nvidia 375.20. The problem isn't solved yet. There is a recently active thread on Nvidia's forums about an issue with resume-from-suspend that may be related, so I posted there. https://devtalk.nvidia.com/default/topic/919984/linux/resume-from-suspend-not-working-with-980-ti-drivers-352-370-kernels-3-16-4-4/ -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 372737] New: Crash on send, configure Kmail or filters
https://bugs.kde.org/show_bug.cgi?id=372737 Bug ID: 372737 Summary: Crash on send, configure Kmail or filters Product: kontact Version: 5.2.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: crgla...@gmail.com Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.1.34-33-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: I have been trying to reply ot or send new email or configure filters this morning. After every send I get this crash whether new or reply email. I have also tried to establish actuatlly re-establish filters after the latest version changes and Kmail/Kontact crashes. I have checked dependencies and Yast returns "all dependencies OK". The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbf1f0c4800 (LWP 32602))] Thread 7 (Thread 0x7fbea37fe700 (LWP 32610)): #0 0x7fbf150d603f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbf193802a3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbf196a1f01 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbf150d20a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbf1bd7d02d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fbea3fff700 (LWP 32609)): #0 0x7fbf150d603f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbf193802a3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbf196a1f01 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbf150d20a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbf1bd7d02d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fbea8a5d700 (LWP 32608)): #0 0x7fbf150d603f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbf193802a3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbf196a1f01 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbf150d20a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbf1bd7d02d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fbea927d700 (LWP 32607)): #0 0x7fbf150d603f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbf1937f2cd in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbf196a1f01 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbf150d20a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbf1bd7d02d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fbef7fff700 (LWP 32605)): #0 0x7fbf150d603f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbf19673433 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fbf19673459 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fbf150d20a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbf1bd7d02d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fbefd3f9700 (LWP 32604)): #0 0x7fbf1bd74bfd in poll () at /lib64/libc.so.6 #1 0x7fbf1330ee64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fbf1330ef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fbf1c890f4b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fbf1c84089b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fbf1c68702a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fbf1afb6aa5 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7fbf1c68b859 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fbf150d20a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fbf1bd7d02d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fbf1f0c4800 (LWP 32602)): [KCrash Handler] #6 0x7fbf1bccd0c7 in raise () at /lib64/libc.so.6 #7 0x7fbf1bcce478 in abort () at /lib64/libc.so.6 #8 0x7fbf1bd0a784 in () at /lib64/libc.so.6 #9 0x7fbf1bd10026 in malloc_printerr () at /lib64/libc.so.6 #10 0x7fbf1bd10d53 in _int_free () at /lib64/libc.so.6 #11 0x7fbf16fd521e in KCoreConfigSkeleton::~KCoreConfigSkeleton() () at /usr/lib64/libKF5ConfigCore.so.5 #12 0x7fbe91d8e377 in () at /usr/lib64/libkmailprivate.so.5 #13 0x7fbe91ec09c2 in () at /usr/lib64/libkmailprivate.so.5 #14 0x7fbf1bccfb39 in __run_exit_handlers () at /lib64/libc.so.6 #15 0x7fbf1bccfb85 in () at /lib64/libc.so.6 #16 0x7fbf1bcb9b2c in __libc_start_main () at /lib64/libc.so.6 #17 0x00404ca7 in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372889] New: Kdenlive crashes with SIGSEGV when opening project
https://bugs.kde.org/show_bug.cgi?id=372889 Bug ID: 372889 Summary: Kdenlive crashes with SIGSEGV when opening project Product: kdenlive Version: 16.08.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: cvagnet...@gmail.com Target Milestone: --- I was working on a project, and tried to remove a clip together with audio track and overlay title by ctrl-selecting all three and pressing Del on the keyboard. The audio track went away but the video and title remained. As they couldn't be deleted nor moved, I tried saving the project and re-opening it. When opening, it crashes before displaying the timeline but after the project bin has been loaded. I tried dropping all items from the cache, and even removed the clip from the drive. Kdenlive informs me about this on startup, and I select "remove clip", but it still crashes when accepting the dialog. Installed versions: libmlt++3: 6.3.0+git201610101603~ubuntu16.04.1 kdenlive: 4:16.08.2~ubuntu16.04.1 Thread 1 "kdenlive" received signal SIGSEGV, Segmentation fault. 0x76dc05c0 in Mlt::Properties::get(char const*) () from /usr/lib/x86_64-linux-gnu/libmlt++.so.3 --- (gdb) backtrace #0 0x76dc05c0 in Mlt::Properties::get(char const*) () from /usr/lib/x86_64-linux-gnu/libmlt++.so.3 #1 0x005c2e6a in Track::info (this=0x0) at /build/kdenlive-_W39Rj/kdenlive-16.08.2~ubuntu16.04.1/src/timeline/track.cpp:579 #2 0x005b4beb in Timeline::getTracksInfo (this=0x3d74500) at /build/kdenlive-_W39Rj/kdenlive-16.08.2~ubuntu16.04.1/src/timeline/timeline.cpp:682 #3 0x00524fdf in TransitionSettings::updateProjectFormat (this=0x2021890) at /build/kdenlive-_W39Rj/kdenlive-16.08.2~ubuntu16.04.1/src/project/transitionsettings.cpp:125 #4 0x008265a7 in MainWindow::connectDocument (this=0xd32fa0) at /build/kdenlive-_W39Rj/kdenlive-16.08.2~ubuntu16.04.1/src/mainwindow.cpp:1784 #5 0x00521240 in ProjectManager::doOpenFile (this=this@entry=0xca19a0, url=..., stale=, stale@entry=0x0) at /build/kdenlive-_W39Rj/kdenlive-16.08.2~ubuntu16.04.1/src/project/projectmanager.cpp:549 #6 0x00522d6f in ProjectManager::openFile (this=0xca19a0, url=...) at /build/kdenlive-_W39Rj/kdenlive-16.08.2~ubuntu16.04.1/src/project/projectmanager.cpp:489 #7 0x0086aee1 in ProjectManager::qt_static_metacall (_o=0xca19a0, _c=, _id=, _a=) at /build/kdenlive-_W39Rj/kdenlive-16.08.2~ubuntu16.04.1/obj-x86_64-linux-gnu/src/moc_projectmanager.cpp:184 #8 0x72320d2a in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x74e992e2 in KRecentFilesAction::urlSelected(QUrl const&) () from /usr/lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5 #10 0x74e99cb8 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5 #11 0x74e9a07b in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5 #12 0x72320d2a in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x74096ddf in KSelectAction::triggered(QAction*) () from /usr/lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5 #14 0x74099ebd in KSelectAction::actionTriggered(QAction*) () from /usr/lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5 #15 0x72320baf in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x738a095f in QActionGroup::triggered(QAction*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x738a15d9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x72320d2a in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7389d412 in QAction::triggered(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7389f898 in QAction::activate(QAction::ActionEvent) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x73a21e12 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x73a280ac in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x73a2c020 in QMenu::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x738e9f88 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x73a2ca73 in QMenu::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x738a705c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x738acc19 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x722f238b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from
[kdenlive] [Bug 372889] Kdenlive crashes with SIGSEGV when opening project
https://bugs.kde.org/show_bug.cgi?id=372889 Chris changed: What|Removed |Added CC||cvagnet...@gmail.com --- Comment #1 from Chris --- As I refused to let hours of editing go to waste, I started going over the project file editing out references by random until it finally opened without crashing. Here is the changes between my backup and the working file: 5365a5366,5381 > > > > >0 >1 >0 >0 >qtblend >1 > > > > > > 5376a5393 > -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372962] New: open libreoffice - options
https://bugs.kde.org/show_bug.cgi?id=372962 Bug ID: 372962 Summary: open libreoffice - options 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: chris.duggan1...@gmail.com Target Milestone: --- Application: kwin_x11 (5.8.3) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.8.10-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: Clicked on options within libreoffice and kwin crash happened - opensuse tumbleweed kde plasma version 5.8.3 -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f010ca70940 (LWP 13099))] Thread 5 (Thread 0x7f00de449700 (LWP 13699)): #0 0x7f010c3f3751 in ppoll () at /lib64/libc.so.6 #1 0x7f0109ac7b41 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f0109ac9428 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f0109a761ea in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f01098a48b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f010422da75 in () at /usr/lib64/libQt5Qml.so.5 #6 0x7f01098a9558 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f01056fc454 in start_thread () at /lib64/libpthread.so.0 #8 0x7f010c3fc39f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f00ddc48700 (LWP 13178)): #0 0x7f010570210f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f0108a31834 in () at /usr/lib64/libQt5Script.so.5 #2 0x7f0108a31879 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f01056fc454 in start_thread () at /lib64/libpthread.so.0 #4 0x7f010c3fc39f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f00e64a7700 (LWP 13175)): #0 0x7f010c3f3751 in ppoll () at /lib64/libc.so.6 #1 0x7f0109ac7b41 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f0109ac9428 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f0109a761ea in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f01098a48b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f010422da75 in () at /usr/lib64/libQt5Qml.so.5 #6 0x7f01098a9558 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f01056fc454 in start_thread () at /lib64/libpthread.so.0 #8 0x7f010c3fc39f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f00f533a700 (LWP 13123)): #0 0x7f010c3f368d in poll () at /lib64/libc.so.6 #1 0x7f0100ed7876 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f0100ed798c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f0109acc79b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f0109a761ea in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f01098a48b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f01034063e5 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f01098a9558 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f01056fc454 in start_thread () at /lib64/libpthread.so.0 #9 0x7f010c3fc39f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f010ca70940 (LWP 13099)): [KCrash Handler] #6 0x7f0104219130 in QQmlBinding::write(QQmlPropertyData const&, QV4::Value const&, bool, QFlags) () at /usr/lib64/libQt5Qml.so.5 #7 0x7f010421a095 in QQmlBinding::update(QFlags) () at /usr/lib64/libQt5Qml.so.5 #8 0x7f0104223d35 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7f01041ad5fe in QQmlComponentPrivate::complete(QQmlEnginePrivate*, QQmlComponentPrivate::ConstructionState*) () at /usr/lib64/libQt5Qml.so.5 #10 0x7f01041ad6c7 in QQmlComponentPrivate::completeCreate() () at /usr/lib64/libQt5Qml.so.5 #11 0x7f01041ad530 in QQmlComponent::create(QQmlContext*) () at /usr/lib64/libQt5Qml.so.5 #12 0x7f00e66e54b7 in () at /usr/lib64/qt5/plugins/org.kde.kdecoration2/kwin5_aurorae.so #13 0x7f010c01bed9 in () at /usr/lib64/libkwin.so.5 #14 0x7f010befc572 in KWin::Client::createDecoration(QRect const&) () at /usr/lib64/libkwin.so.5 #15 0x7f010befd15d in KWin::Client::updateDecoration(bool, bool) () at /usr/lib64/libkwin.so.5 #16 0x7f010bf5c175 in KWin::Client::manage(unsigned int, bool) () at /usr/lib64/libkwin.so.5 #17 0x7f010bedfa84 in KWin::Workspace::createClient(unsigned int, bool) () at /usr/lib64/libkwin.so.5 #18 0x7f010bf49387 in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) () at /usr/lib64/libkwin.so.5 #19 0x7f0109a7532f in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) (
[Powerdevil] [Bug 348082] monitor is randomly powered back on
https://bugs.kde.org/show_bug.cgi?id=348082 --- Comment #28 from Chris --- The issue no longer occurs for me. Hardware configuration hasn't changed, mouse, keyboard, monitor, etc. Latest debian-sid, wayland as pure as possible. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422455] Monitor power saving won't work when using DisplayPort cable
https://bugs.kde.org/show_bug.cgi?id=422455 --- Comment #14 from Chris --- The issue no longer occurs for me. Hardware configuration hasn't changed, mouse, keyboard, monitor, etc. Latest debian-sid, wayland as pure as possible. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 348529] Turn off screen after lock screen
https://bugs.kde.org/show_bug.cgi?id=348529 --- Comment #37 from Chris --- (In reply to Chris from comment #34) > The script above should work nicely, but it doesn't, not consistently at > least. > Related bugs: > https://bugs.kde.org/show_bug.cgi?id=348082 "monitor is randomly powered > back on" > https://bugs.kde.org/show_bug.cgi?id=422455 "Monitor power saving won't work > when using DisplayPort cable" Those two bugs no longer bother me, for a few month now, latest debian-sid, wayland as pure as possible. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 348529] Turn off screen after lock screen
https://bugs.kde.org/show_bug.cgi?id=348529 --- Comment #38 from Chris --- (In reply to mágoa mångata from comment #36) > This bug is kind of annoying. Is there any problem about not solving it? > Since this is small bug. It's not resolved for 7 years! > I think the only thing to do is to add an option for lock screen timeout in > the power settings. Have you tried the `kde-saver-script.sh` script from above? My system is now so well behaved in that regard that I don't need that anymore. But I believe that should work just fine. And that both with x11 (which I no longer use), and wayland. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422455] Monitor power saving won't work when using DisplayPort cable
https://bugs.kde.org/show_bug.cgi?id=422455 --- Comment #16 from Chris --- 5.17.0-2-amd64 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 455079] New: Basic effects not rendered
https://bugs.kde.org/show_bug.cgi?id=455079 Bug ID: 455079 Summary: Basic effects not rendered Product: kdenlive Version: 22.04.1 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: dume...@gmx.ch Target Milestone: --- Created attachment 149576 --> https://bugs.kde.org/attachment.cgi?id=149576&action=edit Screenshots on project settings Hello I am a new user of Kdenlive on Windows 10, 22.04.1. Kdenlive looks great! I created my first little test-project in Kdenlive with the effects I need at most. OBSERVED RESULT Following Effects work well in the editing project monitor but are not rendered correctly ( I haven't found any answer on the forum so far): - Video Fade in/out (-> Video appears as a hard cut) - zoom in/out (-> black video at rendering) Following effects work neither on the project monitor nor at rendering: - Chroma Key Basic (-> No transparency) On the other Hand, these effects work well - Wipe (crossfade) - Color saturation - Speed acceleration 125% I rendered on MP4-H264/ACC Format. I tried other formats but it didn't help. I tried to perform to perform this export on another Win 10 PC: The bugs remain the same. The bug appears on Full HD Video-Clips (mpeg 4 and mpeg 2) as well as on SD Avi or mpeg2 clips. SOFTWARE/OS VERSIONS Windows: 10 Version 2009 (x86_64) (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION See attached File -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466607] New: Bug re-introduced as of today's updates
https://bugs.kde.org/show_bug.cgi?id=466607 Bug ID: 466607 Summary: Bug re-introduced as of today's updates Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: cjd...@brokensolstice.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@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 *** Same issue as: https://bugs.kde.org/show_bug.cgi?id=353975 You said to open a new thread... I'm doing that. When 5.27 came out, it didn't fully fix the issue, it had horrible problems of recuperating after a screen blanking -- had to reboot because my screens would not come up. I turned off screen blanking, and it was again stable... for about 2 weeks. After applying updates today (mostly nvidia-related), the same problem is back... black screen STEPS TO REPRODUCE 1. Boot to KDE neon. OBSERVED RESULT Only one monitor is in use... the weird thing is, that the boot sequence can happen on one monitor, then when KDE comes up, the other monitor is the one KDE uses, and the one that was just working .25 seconds ago is black, and unrecoverable. Go to "configure display settings" and you keep getting: "A new output has been removed. Settings have been reloaded" (wait 2 seconds, then) "A new output has been added. Settings have been reloaded." Looping, endlessly. This is almost identical to the bug I mentioned above -- except even more debilitating. EXPECTED RESULT I expect both monitors to work. SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: 5.27.1 (available in About System) KDE Plasma Version: 5.27 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION 03:00.0 VGA compatible controller: NVIDIA Corporation TU104GL [Quadro RTX 5000] (rev a1) 03:00.1 Audio device: NVIDIA Corporation TU104 HD Audio Controller (rev a1) 03:00.2 USB controller: NVIDIA Corporation TU104 USB 3.1 Host Controller (rev a1) 03:00.3 Serial bus controller: NVIDIA Corporation TU104 USB Type-C UCSI Controller (rev a1) I've wiped my kde settings a 1000 times over now, and have rebuilt my profile from scratch... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 466646] New: Kate Session Launcher "Start Kate (no arguments)" does not work.
https://bugs.kde.org/show_bug.cgi?id=466646 Bug ID: 466646 Summary: Kate Session Launcher "Start Kate (no arguments)" does not work. Classification: Applications Product: kate Version: 22.12.2 Platform: Slackware OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sessions Assignee: kwrite-bugs-n...@kde.org Reporter: chrisret...@gmx.com Target Milestone: --- Created attachment 156856 --> https://bugs.kde.org/attachment.cgi?id=156856&action=edit Start Kate (no arguments) SUMMARY When using the Kate Session button in the System Tray, selecting "Start Kate (no arguments)" does not start Kate. It acts like when selecting "New Kate Session" and wants a session name entered. This problem has been around for a while I am just now getting around to reporting it. I've sort of adapted, but it is annoying enough to finally report this. :) STEPS TO REPRODUCE 1. Left click on Kate Session Launcher in the System Tray. 2. Select Start Kate (no arguments) (screenshot1) OBSERVED RESULT A box opens for entry of a session, similar to "New Kate Session" and does not start Kate. (screenshot2) EXPECTED RESULT Kate opens a new document. SOFTWARE/OS VERSIONS Operating System: Slackware -current KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.14 (64-bit) Graphics Platform: X11 Processors: 4 × AMD Phenom(tm) II X4 840 Processor Memory: 7.8 GiB of RAM Graphics Processor: NVIDIA GeForce GT 730/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: M68MT-S2 ADDITIONAL INFORMATION Not sure is useful. When using the Application Launcher and searching for Kate show two "Start Kate (no arguments)", selecting either one opens Kate without a session. (screenshot3). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 466646] Kate Session Launcher "Start Kate (no arguments)" does not work.
https://bugs.kde.org/show_bug.cgi?id=466646 --- Comment #1 from Chris --- Created attachment 156857 --> https://bugs.kde.org/attachment.cgi?id=156857&action=edit Result on selecting Start Kate (no arguments) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 466646] Kate Session Launcher "Start Kate (no arguments)" does not work.
https://bugs.kde.org/show_bug.cgi?id=466646 --- Comment #2 from Chris --- Created attachment 156858 --> https://bugs.kde.org/attachment.cgi?id=156858&action=edit View of search Kate Application Launcher -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466607] Bug re-introduced as of today's updates
https://bugs.kde.org/show_bug.cgi?id=466607 --- Comment #1 from Chris --- I had restored from a previous backup, and confirmed that the system worked. That update definitely broke things again. I waited about 7 days, did my update, and it worked fine. Another week later... (yesterday) I installed my updates, and this bug was reintroduced again (that is twice now since 5.27). I lost one monitor (as soon as I log into KDE... it works fine until then), the I get the infinite loop: "A new output has been removed. Settings have been reloaded" (wait 2 seconds, then) "A new output has been added. Settings have been reloaded." I don't know how to get a text dump from discover on the packages from Discover, I'd enumerate what was being updated, but there are too many to type by hand. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466607] Bug re-introduced as of today's updates
https://bugs.kde.org/show_bug.cgi?id=466607 --- Comment #2 from Chris --- I should add that I restored from the previous night's backups, and my monitors work normally again. It is definitely related to something being updated. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466607] Bug re-introduced as of today's updates
https://bugs.kde.org/show_bug.cgi?id=466607 --- Comment #4 from Chris --- A regression, maybe. But there were no nvidia updates this last round. I'm still sitting on several dozen updates, afraid to apply them. All I know is it works, I apply the updates, and breaks. Sounds like whatever it is, even if it is nvidia, kscreen will need to adapt. The curios thing here is that I have nvidia drivers at home on 4 different pc's and this did not happen. It only happens Quadro, with dual (same model) monitors. The other systems all have dual monitors, but they are not matched... I don't know if that is significant or not. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 465529] Baloo file extractor crashes on startup
https://bugs.kde.org/show_bug.cgi?id=465529 --- Comment #4 from Chris --- Created attachment 157516 --> https://bugs.kde.org/attachment.cgi?id=157516&action=edit New crash information added by DrKonqi baloo_file_extractor (5.104.0) using Qt 5.15.8 Every time I start my system up, baloo_file_extractor crashes. -- Backtrace (Reduced): #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140477036886336) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140477036886336) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=140477036886336, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7fc35d242476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7fc35d2287f3 in __GI_abort () at ./stdlib/abort.c:79 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 465529] Baloo file extractor crashes on startup
https://bugs.kde.org/show_bug.cgi?id=465529 Chris changed: What|Removed |Added CC||cjd...@brokensolstice.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 455269] "Examining (Failed)" notification when opening file in Kate after deleting folder from where I had previously opened a file
https://bugs.kde.org/show_bug.cgi?id=455269 Chris changed: What|Removed |Added CC||chrisret...@gmx.com --- Comment #5 from Chris --- Same issue here. When opening Kate on deleted files I set the same Examining (Failed) message popup. Operating System: Slackware -current KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.1.21 (64-bit) Graphics Platform: X11 Processors: 4 × AMD Phenom(tm) II X4 840 Processor Memory: 7.8 GiB of RAM Graphics Processor: NVIDIA GeForce GT 730/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: M68MT-S2 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 455269] "Examining (Failed)" notification when opening file in Kate after deleting folder from where I had previously opened a file
https://bugs.kde.org/show_bug.cgi?id=455269 --- Comment #6 from Chris --- Forgot to add Kate version. Version 22.12.3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459463] New: Paste Coordinates Significant Figures
https://bugs.kde.org/show_bug.cgi?id=459463 Bug ID: 459463 Summary: Paste Coordinates Significant Figures Classification: Applications Product: digikam Version: 7.8.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Geolocation-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: chris.c.cou...@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 *** STEPS TO REPRODUCE 1. Copy coordinates from Google Maps 2. Use Paste Coordinates in Geolocation Editor 3. OBSERVED RESULT Will note paste unless last two significant digits are removed. Would be faster and easier if you supported the full amount of digits Google supplies on copy/paste, even if you discard them internally. EXPECTED RESULT Simple copy/paste from Google Maps location. SOFTWARE/OS VERSIONS Windows: 7.8 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.
[kdevelop] [Bug 376716] CPP parser slow on all projects
https://bugs.kde.org/show_bug.cgi?id=376716 Chris changed: What|Removed |Added CC|k...@ontoemail.com | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459463] Paste Coordinates Lost Precision
https://bugs.kde.org/show_bug.cgi?id=459463 --- Comment #2 from Chris --- Well I just tried it again and it worked. Not sure what caused it not to work before and I have been modifying hundreds of entries since. :-( I will go back to direct copy/paste and if I run into the situation again I will post the particular coordinates. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 468681] New: Firefox U2F keys support problem
https://bugs.kde.org/show_bug.cgi?id=468681 Bug ID: 468681 Summary: Firefox U2F keys support problem Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: st...@kity.pl CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Created attachment 158212 --> https://bugs.kde.org/attachment.cgi?id=158212&action=edit Output for U2F Firefox teest on https://u2f.bin.coffee/ webpage On standard default installed version of Firefox there is problem with U2F keys support. All works ok with Falcon. On old Kde Neon (based on Ubuntu 20.04 LTS), with the same version of Firefox, all works good. After uninstall Firefox standard package version and install snap version, U2F is working. So looks like the problem is in Firefox from deb packet. STEPS TO REPRODUCE 1. Enable below options in Firefox settings (about:config) security.webauth.u2f=True security.webauth.u2f_enable_softtoken=True 2. Insert U2F key to usb 3. Enter into page: https://u2f.bin.coffee/ and click test buttons. OBSERVED RESULT There is error (example on the screenshot) EXPECTED RESULT Should communicate properly, without errors, with U2F key. SOFTWARE/OS VERSIONS Linux/KDE Plasma: The newest version with all updates (19 April 2023) ADDITIONAL INFORMATION Firefox: 112.0.1 (64 bits), arm architecture I used Yubico hardware U2F keys for test: YubiKey 5 NFC, YubiKey 5 Nano and -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451702] Various KDE apps lock up with 100% CPU usage when monitor powers off
https://bugs.kde.org/show_bug.cgi?id=451702 --- Comment #2 from Chris --- This doesn't seem to be happening anymore for me. -- You are receiving this mail because: You are watching all bug changes.
[analitza] [Bug 323370] Problem with horizontal and vertical marks while changing scale to other than 1 in 2D space
https://bugs.kde.org/show_bug.cgi?id=323370 Chris changed: What|Removed |Added Version|unspecified |8.0.0 Platform|Ubuntu |Archlinux Alias||nano CC||three6nine...@proton.me Component|analitzaplot|core -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469019] New: Payees match on a blank field
https://bugs.kde.org/show_bug.cgi?id=469019 Bug ID: 469019 Summary: Payees match on a blank field Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: developerch...@rebel.com.au Target Milestone: --- Created attachment 158453 --> https://bugs.kde.org/attachment.cgi?id=158453&action=edit shows badly matched payee "test" SUMMARY It is possible to have a blank string as the matching text on payees, when this happens any transaction matches the payee and therefore the transaction is incorrectly assigned to that payee. STEPS TO REPRODUCE 1. Create a payee 2. Set matching criteria to "Match on name below" 3. Leave the matching text field blank 4. Save the payee. 5. Import a number of transactions OBSERVED RESULT many of the imported transactions are assigned to the bad payee The attached image shows the payee "test" matching on multiple transactions each with a different actual payee EXPECTED RESULT An Error should occur when creating the payee preventing a blank matching field, also on import the payee match should be checked to ensure that the match is not occurring on a blank field SOFTWARE/OS VERSIONS Windows 10 Version 2009 (x86_64) KDE Frameworks Version: 5.99.0 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 466797] Problem connecting to calendar and contact with CalDAV protocol (in addition to problems with WebDAV and CardDAV)
https://bugs.kde.org/show_bug.cgi?id=466797 Chris changed: What|Removed |Added CC||junkspamwastema...@gmail.co ||m --- Comment #1 from Chris --- Comment on attachment 156979 --> https://bugs.kde.org/attachment.cgi?id=156979 Server access configuration & Result of an attempt to connect to a CalDAV server Hello, Following the exact steps described by Troupal, I encounter a similar error : "There was a problem with the request. HTTP error (405)." This error occurs in Akonadi, KOrganizer, KMail, Kontact, etc. (for both CalDAV and CardDAV). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3
https://bugs.kde.org/show_bug.cgi?id=401088 Chris changed: What|Removed |Added CC||chrisret...@gmx.com --- Comment #40 from Chris --- Operating System: Slackware64-current KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.1.28 (64-bit) Drives: Local Storage: total: 1.82 TiB used: 1.13 TiB (62.3%) ID-1: /dev/sda vendor: Western Digital model: WD10EZEX-22MFCA0 size: 931.51 GiB ID-2: /dev/sdb vendor: Western Digital model: WD10EZRX-00D8PB0 size: 931.51 GiB I have this problem. Not just with '/' but also with '/home/' and 'home/backup/' Filesystem Type Size Used Avail Use% Mounted on /dev/sda1 ext4 92G 40G 47G 46% / /dev/sda3 ext4 818G 499G 278G 65% /home /dev/sdb1 ext4 917G 623G 248G 72% /home/backup Today for example, it was just '/' and '/home/backup/'. I start my computer to runlevel 3 (CLI) and start KDE Plasma with startx. I do not use a GUI login. In one instance all the of the mounted locations came up. The system runs just fine, no issues. The 'df' command is fast real0m0.012s user0m0.007s sys 0m0.006s I will attach two screen shots, one showing today's, one showing all three mounts -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3
https://bugs.kde.org/show_bug.cgi?id=401088 --- Comment #41 from Chris --- Created attachment 158987 --> https://bugs.kde.org/attachment.cgi?id=158987&action=edit Two mount points. Today's file system not responding '/' and '/home/backup/' -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3
https://bugs.kde.org/show_bug.cgi?id=401088 --- Comment #42 from Chris --- Created attachment 158988 --> https://bugs.kde.org/attachment.cgi?id=158988&action=edit Three file systems not responding. Three file systems not responding, '/', '/home/', '/home/backup/' -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 348529] When screen is locked, turn off screen with a shorter timeout
https://bugs.kde.org/show_bug.cgi?id=348529 --- Comment #50 from Chris --- Created attachment 155925 --> https://bugs.kde.org/attachment.cgi?id=155925&action=edit Shorten screen power off timeout when screen is locked -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 463768] Discover crashes at start
https://bugs.kde.org/show_bug.cgi?id=463768 Chris changed: What|Removed |Added CC||chris11b...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 463768] Discover crashes at start
https://bugs.kde.org/show_bug.cgi?id=463768 --- Comment #3 from Chris --- Created attachment 155962 --> https://bugs.kde.org/attachment.cgi?id=155962&action=edit New crash information added by DrKonqi plasma-discover (5.26.1) using Qt 5.15.6 crashes at launch (im on steamdeck) -- Backtrace (Reduced): #6 0x7f0b6432ba1b in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) () at /usr/lib/libQt5Qml.so.5 #7 0x7f0b6432c52a in QQmlTypeLoader::setData(QQmlDataBlob*, QString const&) () at /usr/lib/libQt5Qml.so.5 #8 0x7f0b6432e011 in QQmlTypeLoader::loadThread(QQmlDataBlob*) () at /usr/lib/libQt5Qml.so.5 #9 0x7f0b6432e4d6 in QQmlTypeLoader::load(QQmlDataBlob*, QQmlTypeLoader::Mode) () at /usr/lib/libQt5Qml.so.5 #10 0x7f0b6432e89a in QQmlTypeLoader::getType(QUrl const&, QQmlTypeLoader::Mode) () at /usr/lib/libQt5Qml.so.5 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 487297] The "spectacle" program crashes when the time zone is set incorrectly
https://bugs.kde.org/show_bug.cgi?id=487297 Chris changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |FIXED --- Comment #6 from Chris --- I did provide the requested info a fortnight ago. However `sudo nixos-rebuild boot --upgrade` just now (unstable) and rebooting caused the bug not showing anymore, so I guess the issue can just be closed. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 472591] The file or folder Message recipient disconnected from message bus without replying does not exist.
https://bugs.kde.org/show_bug.cgi?id=472591
--- Comment #3 from Chris ---
Unfortunately... my above workaround has ceased to work.
I"m now getting:
kf.coreaddons: Some files could not be exported.
QDBusError("org.freedesktop.DBus.Error.NoReply", "Message recipient
disconnected from message bus without replying")
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 478902] New: Pan Not Working
https://bugs.kde.org/show_bug.cgi?id=478902 Bug ID: 478902 Summary: Pan Not Working Classification: Applications Product: krita Version: 5.2.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Move Assignee: krita-bugs-n...@kde.org Reporter: luvkitti...@gmail.com Target Milestone: --- SUMMARY *** Middle mouse 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: (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 483011] New: Floating Panels don't dodge with multiple windows
https://bugs.kde.org/show_bug.cgi?id=483011 Bug ID: 483011 Summary: Floating Panels don't dodge with multiple windows Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: junasai...@aol.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 166811 --> https://bugs.kde.org/attachment.cgi?id=166811&action=edit Display arrangement SUMMARY *** I run EndeavourOS, and just updated to KDE6, and am trying to use the floating panels, set to "dodge windows". I have three monitors, two horizontal stacked on top of each other, and one vertical one to their left. This issue occurs on all displays. If i place a panel on the side of a screen that's a shared edge with another monitor, (such as between the top and bottom horizontal screens), dodging doesn't work. If i move the panel to an "outside" edge of any of the three displays, dodging works just fine) Per screenshot of my displays for reference: Left and bottom of Sceptre display work fine. Bottom and right of Acer display work fine. Top and right of Gigabyte display work fine. Any of the 'inside' or 'shared' edges between the multiple monitors, the panels won't dodge at all. I can try to test anything else or provide other information that's applicable. *** STEPS TO REPRODUCE 1. Use EndeavourOS (or just Arch?) and KDE 6.0.1 2. Have multiple monitors 3. Make a "floating", "dodge windows" panel on any edge of a monitor that's not an "edge", but where my desktop extends to the next monitor. 4. The Panel will not dodge windows and hide itself, the window goes below it instead. OBSERVED RESULT The Panel will not dodge windows and hide itself, the window goes below it instead. EXPECTED RESULT The panel dodges the window, and hides itself. SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Graphics Platform: Wayland GPU: AMD Radeon RX 6800XT -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483011] Floating Panels don't dodge with multiple windows
https://bugs.kde.org/show_bug.cgi?id=483011 Chris changed: What|Removed |Added CC||junasai...@aol.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 487297] The "spectacle" program crashes when the time zone is set incorrectly
https://bugs.kde.org/show_bug.cgi?id=487297 Chris changed: What|Removed |Added CC||inkbottle...@gmail.com --- Comment #2 from Chris --- Hi, I have the same issue as the OP, with the exact same system. The output from `timedatectl` seems okay, though. I tried to run coredumpctl gdb 70296`, but besides providing information, I get `Failed to invoke gdb: No such file or directory`. So, I'll come back to it later. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 487297] The "spectacle" program crashes when the time zone is set incorrectly
https://bugs.kde.org/show_bug.cgi?id=487297 --- Comment #4 from Chris --- Created attachment 170152 --> https://bugs.kde.org/attachment.cgi?id=170152&action=edit coredumpctl gdb 123141 | wl-copy Hi Noah, I've been told on the nixos chat room that: "Thought without debug symbols it won't show much else beside what coredumpctl already shows". So I past the output of `coredumpctl gdb 123141`. Coredump resulting from invoking `spectacle` from command line and then clicking on `save` or `copy` or `configure` to name a few. Which results in the error message: "Unable to determine system time zone: please check your system configuration. Segmentation fault (core dumped)" But really my time zone seems perfectly okay. ``` $ timedatectl | grep zone Time zone: UTC (UTC, +) ``` If I can provide additional information I'm happy to do it, Cheers, Chris -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 488237] New: Crash during confirming face tags
https://bugs.kde.org/show_bug.cgi?id=488237 Bug ID: 488237 Summary: Crash during confirming face tags Classification: Applications Product: digikam Version: 8.3.0 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: chris.cru...@gmail.com Target Milestone: --- Application: digikam (8.3.0) Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.7.12-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux trixie/sid DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: I've been doing a lot of cleaning up of unconfirmed face tags, and Digikam is crashing frequently. I cannot find a pattern to the crashes. It happens when confirming a single face at a time and when doing multiple pictures with the same face. The crash can be reproduced sometimes. -- Backtrace: Application: digiKam (digikam), signal: Aborted [KCrash Handler] #4 0x7f807a6a3b0c in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x7f807a6554e2 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x7f807a63e4ed in abort () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x7f807a63f395 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x7f807a6ad455 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x7f807a6b1a1c in malloc () from /lib/x86_64-linux-gnu/libc.so.6 #10 0x7f807ace66c2 in QArrayData::allocate(unsigned long, unsigned long, unsigned long, QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f807ad5f9b7 in QString::QString(int, Qt::Initialization) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f807c15e563 in ?? () from /lib/x86_64-linux-gnu/libKF5Solid.so.5 #13 0x7f807c15ea36 in ?? () from /lib/x86_64-linux-gnu/libKF5Solid.so.5 #14 0x7f807c161188 in ?? () from /lib/x86_64-linux-gnu/libKF5Solid.so.5 #15 0x7f807c157cdd in ?? () from /lib/x86_64-linux-gnu/libKF5Solid.so.5 #16 0x7f807c158740 in ?? () from /lib/x86_64-linux-gnu/libKF5Solid.so.5 #17 0x7f807af07c32 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f807af07c32 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f807af0b253 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f807af0ba95 in QSocketNotifier::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f807bb62f82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f807aece0e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f807af2a345 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f8075109e3f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f807510bec7 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f807510c4e0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f807af2979a in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f807aecca8b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7f807aed5244 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x56147f0b30d4 in ?? () #31 0x7f807a63fc8a in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #32 0x7f807a63fd45 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #33 0x56147f0b3ce1 in ?? () [Inferior 1 (process 62322) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 488237] Crash during confirming face tags
https://bugs.kde.org/show_bug.cgi?id=488237 --- Comment #2 from Chris --- This collection is all on a local hard drive, although not the same one digikam is installed on. Digikam is installed through the debian package manager on the / drive. The photos reside on the /home partition, which is on a different physical disk. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 488237] Crash during confirming face tags
https://bugs.kde.org/show_bug.cgi?id=488237 --- Comment #4 from Chris --- I apologize, I don't exactly know what you need here, I'm not a developer. These are the last lines from gdm after a crash: [New Thread 0x7fff5b4006c0 (LWP 225213)] [New Thread 0x7fff43e006c0 (LWP 225216)] [New Thread 0x7fff5be006c0 (LWP 225217)] [New Thread 0x7fff5aa006c0 (LWP 225218)] [New Thread 0x7fff416006c0 (LWP 225219)] [Thread 0x7fff5aa006c0 (LWP 225218) exited] [Thread 0x7fff43e006c0 (LWP 225216) exited] [Thread 0x7fff416006c0 (LWP 225219) exited] [Thread 0x7fff5be006c0 (LWP 225217) exited] malloc(): unaligned tcache chunk detected malloc(): unaligned tcache chunk detected Thread 1 "digikam" received signal SIGABRT, Aborted. __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory. And the backtrace: #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #1 0x742a6b6f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78 #2 0x742584e2 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x742414ed in __GI_abort () at ./stdlib/abort.c:79 #4 0x74242395 in __libc_message (fmt=fmt@entry=0x743b655e "%s\n") at ../sysdeps/posix/libc_fatal.c:150 #5 0x742b0455 in malloc_printerr (str=str@entry=0x743b99a8 "malloc(): unaligned tcache chunk detected") at ./malloc/malloc.c:5765 #6 0x742b4a1c in tcache_get_n (ep=, tc_idx=) at ./malloc/malloc.c:3176 #7 tcache_get (tc_idx=) at ./malloc/malloc.c:3192 #8 __GI___libc_malloc (bytes=128) at ./malloc/malloc.c:3313 #9 0x748e66c2 in QArrayData::allocate(unsigned long, unsigned long, unsigned long, QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7495fee3 in QString::reallocData(unsigned int, bool) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7495ffdc in QString::resize(int) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7729485f in () at /usr/lib/digikam/libdigikamdatabase.so.8.3.0 #13 0x77299fa7 in Digikam::CollectionManager::updateLocations() () at /usr/lib/digikam/libdigikamdatabase.so.8.3.0 #14 0x74b07bd3 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x755529a8 in Solid::StorageAccess::accessibilityChanged(bool, QString const&) () at /lib/x86_64-linux-gnu/libKF5Solid.so.5 #16 0x74b07bd3 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x755b43dd in () at /lib/x86_64-linux-gnu/libKF5Solid.so.5 #18 0x74b07bd3 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x755b0159 in () at /lib/x86_64-linux-gnu/libKF5Solid.so.5 #20 0x74b07c32 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x755af791 in () at /lib/x86_64-linux-gnu/libKF5Solid.so.5 #22 0x74b07c32 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x74b07c32 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x74b0b253 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x74b0ba95 in QSocketNotifier::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x75762f82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x74ace0e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x74b2a345 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fffeeb0de3f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7fffeeb0fec7 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7fffeeb104e0 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x74b2979a in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x74acca8b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x74ad5244 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0xa0d4 in () #36 0x74242c8a in __libc_start_call_main (main=main@entry=0x8f60, argc=argc@entry=1, argv=argv@entry=0x7fffdc78) at ../sysdeps/nptl/libc_start_call_main.h:58 #37 0x74242d45 in __libc_start_main_impl (main=0x8f60, argc=1, argv=0x7fffdc78, init=, fini=, rtld_fini=, stack_end=0x7fffdc68) at ../csu/libc-start.c:360 #38 0xace1 in () -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 488237] Crash during confirming face tags
https://bugs.kde.org/show_bug.cgi?id=488237 --- Comment #8 from Chris --- (In reply to Maik Qualmann from comment #6) > One more thing, so that we can see more debug output from digiKam in the > terminal, please set this environment variable beforehand: > > export QT_LOGGING_RULES="digikam*=true" > > Maik I installed the digikam-dbgsym package, and set the environment variable you gave, then opened digikam and crashed it again. Drkonqi provided crash info of over 600 lines. See it at https://pastebin.com/ZS0XCdG4 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 487216] Dynamic word wrap doesn't stay active
https://bugs.kde.org/show_bug.cgi?id=487216 Chris changed: What|Removed |Added CC||f...@skymail.de --- Comment #4 from Chris --- Yes, I was just about to report this bug. (this is an automatic translation into English!) The automatic line break is set in: Settings -> Setup -> Appearance -> Automatic line break and View -> Line break -> Automatic line break I'm working on a file and suddenly I notice that a horizontal bar appears at the bottom and the line I'm writing on is getting longer and longer. Automatic line break no longer occurs. I haven't yet figured out whether it happens immediately when I open the file or at some point in the middle of working. Under Settings -> Setup -> Appearance -> Automatic line break the checkbox is still checked. But under View -> Line break -> Automatic line break it is missing and needs to be reset. If I do that, reset the checkbox, it lasts for a while. Maybe until I reopen the file next time, or maybe it lasts 10x closing and opening. It seems to randomly reoccur. By the way: Why are there two setting options (locations) for the same thing? Isn't that contradictory? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466607] Bug re-introduced as of today's updates
https://bugs.kde.org/show_bug.cgi?id=466607 --- Comment #7 from Chris --- Updated on 2/12/24... bug seems to have been corrected. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468830] Metadata is lost after write operation when the size of XMP JPEG segment is larger than 65535 bytes when using Exiftool backend
https://bugs.kde.org/show_bug.cgi?id=468830 --- Comment #19 from Chris --- Bug 481268 seems to be related or maybe the exact same: https://bugs.kde.org/show_bug.cgi?id=481268 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481938] Unable to leave session via Desktop menu on Plasma 6.0.0
https://bugs.kde.org/show_bug.cgi?id=481938 Chris changed: What|Removed |Added CC||cjd...@brokensolstice.com --- Comment #27 from Chris --- (In reply to Sean from comment #26) > (In reply to Rich Johnson from comment #5) > > I've created 2 files in /usr/share/dbus-1/services to make my Restart, > > Shutdown & Logout work again: > > > > $ cat org.kde.Shutdown.service > > [D-BUS Service] > > Name=org.kde.Shutdown > > Exec=/usr/bin/plasma-shutdown > > > > $ cat org.kde.LogoutPrompt.service > > [D-BUS Service] > > Name=org.kde.LogoutPrompt > > Exec=/usr/lib/x86_64-linux-gnu/libexec/ksmserver-logout-greeter > > > Thanks Rich Johnson, this works perfectly (for the other noobs out there I > created the file in Kate and just saved to the correct directly specified by > Rich) Thank you for that. Exactly what I needed. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 480235] Persistence in the remote desktop portal does not work across reboots
https://bugs.kde.org/show_bug.cgi?id=480235 chris changed: What|Removed |Added CC||kdebug_vo...@vllmr.eu -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409183] Using Password based authentication when Oauth2 is selected
https://bugs.kde.org/show_bug.cgi?id=409183 Chris changed: What|Removed |Added CC||inkbottle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 476527] Can't add EWS account with OAuth2 authentication, "OK" button stays greyed out until I enter random data for username and password
https://bugs.kde.org/show_bug.cgi?id=476527 Chris changed: What|Removed |Added CC||inkbottle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 457233] Please provide oauth2 login for IMAP - not just Gmail
https://bugs.kde.org/show_bug.cgi?id=457233 --- Comment #12 from Chris --- This bug has 3 duplicates, all of which have importance "NOR normal": 444301 455113 462042. I think it should be fair that the present issue has the same importance. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483428] New: 6.00 to 6.02 upgrade seemed to kill touchscreen on surface pro 7
https://bugs.kde.org/show_bug.cgi?id=483428 Bug ID: 483428 Summary: 6.00 to 6.02 upgrade seemed to kill touchscreen on surface pro 7 Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: chrismarine...@live.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY installed KDE Plasma 6 on Neon, installed surface kernel, https://github.com/linux-surface/linux-surface ... was working extremely well, after some restarts it did kill the surface kernel a couple of times and so had to re-install using steps in link above however, after updates the system to 6.02... the surface pro 7 touch screen does not work anymore.. *** 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. install surface pro 7 kernel via https://github.com/linux-surface/linux-surface on KDE Plasma 6.0 Neon 2. upgrade to 6.02 and re-install surface kernel... 3. touch screen no work! OBSERVED RESULT touch screen has no response for any touch, 2 finger, swipe, 4 fingers.. etc. EXPECTED RESULT expected it to work.. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.0 -> 6.02 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: Qt 6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466607] Bug re-introduced as of today's updates
https://bugs.kde.org/show_bug.cgi?id=466607 --- Comment #8 from Chris --- re-introduced again, as of today's updates. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483011] Floating Panels don't dodge with multiple windows
https://bugs.kde.org/show_bug.cgi?id=483011 --- Comment #2 from Chris --- (In reply to PapierFliegr from comment #1) My panels are set to translucent, and I'm not using tiling. If I understand you right, you say padding incorrectly makes panels think they're being touched when they're not? With my panel set to dodge windows, if it thought it was being touched, I'd expect it to be stuck 'hidden', but instead it's stuck "visible", and is visible on top of whatever window is there, whether the windows is maximized, floating, snapped to one side or corner of my screen, etc. Regardless, how does one set a padding amount? I don't see that in my panel settings, and searching online for it I'm not finding anything? I could at least play around with that setting and find if it helps. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 484053] New: Baloo crashing randomly and frequently
https://bugs.kde.org/show_bug.cgi?id=484053 Bug ID: 484053 Summary: Baloo crashing randomly and frequently Classification: Frameworks and Libraries Product: frameworks-baloo Version: 5.114.0 Platform: Other OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: cjd...@brokensolstice.com Target Milestone: --- Application: baloo_file_extractor (5.114.0) Qt Version: 5.15.12 Frameworks Version: 5.114.0 Operating System: Linux 6.5.0-10027-tuxedo x86_64 Windowing System: X11 Distribution: TUXEDO OS 2 DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: This was happening all the time with my KDE neon install, numerous times a day. I switched from Neon to Tuxedo the other day, a brand-new install... same thing is still happening. It doesn't appear to correspond to anything I was doing. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=137867053623616) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=137867053623616) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=137867053623616, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7d63ade42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7d63ade287f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7d63aeb7d418 in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0 #10 0x7d63aeb71c7a in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0 #11 0x7d63aeb721b0 in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0 #12 0x7d63aeb738c1 in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0 #13 0x7d63aeb7786d in mdb_cursor_del () from /lib/x86_64-linux-gnu/liblmdb.so.0 #14 0x7d63aeb790cb in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0 #15 0x7d63af6158d7 in Baloo::DocumentIdDB::del(unsigned long long) () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #16 0x7d63af622e9e in Baloo::Transaction::removePhaseOne(unsigned long long) () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #17 0x5bb09f5cfa03 in ?? () #18 0x5bb09f5d1196 in ?? () #19 0x7d63ae8f8ed6 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7d63ae8ea77f in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7d63ae8bd30a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7d63ae915b2b in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7d63ae91642c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7d63ad5c7d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7d63ad61d258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7d63ad5c53e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7d63ae9167f8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7d63ae8bbc2b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7d63ae8c41d4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x5bb09f5c6f83 in ?? () #31 0x7d63ade29d90 in __libc_start_call_main (main=main@entry=0x5bb09f5c62f0, argc=argc@entry=1, argv=argv@entry=0x7ffcb67e14e8) at ../sysdeps/nptl/libc_start_call_main.h:58 #32 0x7d63ade29e40 in __libc_start_main_impl (main=0x5bb09f5c62f0, argc=1, argv=0x7ffcb67e14e8, init=, fini=, rtld_fini=, stack_end=0x7ffcb67e14d8) at ../csu/libc-start.c:392 #33 0x5bb09f5c70c5 in ?? () [Inferior 1 (process 7914) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468830] Metadata is lost after write operation when the size of XMP JPEG segment is larger than 65535 bytes when using Exiftool backend
https://bugs.kde.org/show_bug.cgi?id=468830 Chris changed: What|Removed |Added CC||chrisc.gigam...@gmail.com --- Comment #18 from Chris --- I tried today with digiKam-8.3.0-20240120T105916-Win64.exe Metadata is no longer deleted, but keywords added (tags from the tags tree) are not longer written to the file. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466607] Bug re-introduced as of today's updates
https://bugs.kde.org/show_bug.cgi?id=466607 --- Comment #6 from Chris --- Updated system on 1/28/24... this bug was re-introduced. Had to restore from previous backup and hold off on applying update. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 480928] Always print in A4
https://bugs.kde.org/show_bug.cgi?id=480928 Chris changed: What|Removed |Added CC||cjd...@brokensolstice.com --- Comment #1 from Chris --- Same problem. Set to en_us everywhere. Set in KDE, set letter in cups, on the printer and every possible location. KDE apps always default to A4. GTK apps print in Letter just fine. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438784] Panning and zooming bug in Krita
https://bugs.kde.org/show_bug.cgi?id=438784 --- Comment #8 from chris --- this bug is still present in krita 5.0 beta 5. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 453365] New: Breeze cursor script generates png files that are too small
https://bugs.kde.org/show_bug.cgi?id=453365 Bug ID: 453365 Summary: Breeze cursor script generates png files that are too small Product: Breeze Version: master Platform: Debian stable OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: chris...@purelymail.com Target Milestone: --- SUMMARY *** The cursor build scripts (breeze/cursors/Breeze/build.sh and breeze/cursors/Breeze_Snow/build.sh) generate png files that are a few pixels smaller than the ones tracked in the repo. The cursors built from the smaller png files do not line up correctly with the hotspots defined in the cursor configuration files. *** STEPS TO REPRODUCE 1. Delete the build directory in a cursor folder. 2. On a system with Inkscape >= 0.92, run build.sh to generate new cursors. 3. Check dimensions of the png files. OBSERVED RESULT The pngs in build/x1 are 30 by 30 pixels. The pngs in build/x1_5 are 45 by 45 pixels. The pngs in build/x2 are 60 by 60 pixels. EXPECTED RESULT The pngs should be 32 by 32, 48 by 48, and 64 by 64 pixels. SOFTWARE/OS VERSIONS Latest master commit of Breeze repo. Inkscape >= 0.92 ADDITIONAL INFORMATION The build script controls the png size with the -d (export-dpi) flag, Inkscape switched from 90dpi as a default to 96dpi in version 0.92 (https://inkscape.org/release/inkscape-0.92/). A couple LTS distros, like Ubuntu 14.04 and 16.04, still use Inkscape versions prior to 0.92. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 453365] Breeze cursor script generates png files that are too small
https://bugs.kde.org/show_bug.cgi?id=453365 --- Comment #1 from Chris --- I submitted a pull request (https://invent.kde.org/plasma/breeze/-/merge_requests/218/) to correct this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451703] Adaptive sync keeps resetting to Automatic
https://bugs.kde.org/show_bug.cgi?id=451703 --- Comment #6 from Chris --- This issue seems to be fixed, here. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447514] New gradient smoothing is not applied to mesh gradients / Mesh gradients looking really blocky
https://bugs.kde.org/show_bug.cgi?id=447514 Chris changed: What|Removed |Added CC||chris.k.d.w...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453115] New: When merging payees transactions are lost and balances are corrupted
https://bugs.kde.org/show_bug.cgi?id=453115 Bug ID: 453115 Summary: When merging payees transactions are lost and balances are corrupted Product: kmymoney Version: 5.0.8 Platform: Other OS: Other Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: developerch...@rebel.com.au 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. Have a multiyear kmymoney file 2. Merge two payees OBSERVED RESULT Error is displayed saying "Cannot remove payee that is still referenced to a transaction" the transactions no longer appear in either payees (source nor destination) transaction list Balances are corrupted as transactions are deleted for multiple years of the source payee. Not sure what triggers the failed merge as other payees merge with no issue. May be related to bug https://bugs.kde.org/show_bug.cgi?id=408205 EXPECTED RESULT Merge to occur and balances to remain unchanged SOFTWARE/OS VERSIONS N/A Tried on win10 and ubuntu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451386] Black Screen with Movable Cursor after Screens Resume from Sleep
https://bugs.kde.org/show_bug.cgi?id=451386 --- Comment #12 from Chris --- I don't use scaling, and it happens to me (although I haven't tested 5.25 yet). -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 455938] New: Add an option for custom fonts
https://bugs.kde.org/show_bug.cgi?id=455938 Bug ID: 455938 Summary: Add an option for custom fonts Product: NeoChat Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: chris.k...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- I prefer using a monospace font for chat text. It's what I have set up for Konversation, Thunderbird, and Quaternion. However, I don't see any such option in NeoChat, where it uses some default variable-width font. Additionally, the font size in the chat window is rather small, making it uncomfortable to read, with no option to change it (the font and font size for the Room information and Members list is fine to me, though). Konversation allows setting custom fonts and font sizes for different areas of the chat window, and having similar options in NeoChat would make it much nicer to use. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 455079] Basic effects not rendered
https://bugs.kde.org/show_bug.cgi?id=455079 --- Comment #6 from Chris --- (In reply to emohr from comment #5) > Mmh. I tested on Win10 with an MTS clip and fade in/out show up in the > rendered file. > > Could you make a test? In the project bin right click on the clip which has > fade problems (i.e. video_panasonic_HD_01.mts) and choose “transcode to edit > friendly format…” and check if this type of file works as expected. Hi I did the “transcode to edit friendly format…” for the video_panasonic_HD_01.mts and FadeIn effect is now exported correctly :-) Unfortunately, the Zoom In export still doesn't work. I think the file format of video_panasonic_HD_01.mts is very common, since is has been generated by an 10 year old Panasonic camcorder. Would it help, if I send you the original file? Is there a way to upload it (File Size is 5.5 MB)? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 345599] When moving from a dock into the canvas area the cursor disappears but if it returns to a dock area the cursor reappears
https://bugs.kde.org/show_bug.cgi?id=345599 Chris changed: What|Removed |Added CC||omillie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 352190] Wish: auto select layer ; select multiple layers; to have an option to group multiple selected layers at once ...
https://bugs.kde.org/show_bug.cgi?id=352190 Chris changed: What|Removed |Added CC||omillie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458753] New: When I select the brush tool the brush does not appear on my canvas, i can not see the brush on the canvas but when i move away from it my cursor reappears. I have tried hidi
https://bugs.kde.org/show_bug.cgi?id=458753 Bug ID: 458753 Summary: When I select the brush tool the brush does not appear on my canvas, i can not see the brush on the canvas but when i move away from it my cursor reappears. I have tried hiding and moving layers yet I still can not see my brush when I go to the canvas. Product: krita Version: 5.1.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Brush Engine/Bristle Assignee: krita-bugs-n...@kde.org Reporter: omillie...@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 *** STEPS TO REPRODUCE 1. Upload image to cavas 2. Select freehand brush tool 3. Move cursor to canvas 4. Try to draw on said canvas OBSERVED RESULT Cursor does not appear EXPECTED RESULT Cursor should appear on the canvas SOFTWARE/OS VERSIONS Windows: Windows 7 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.
[krita] [Bug 458753] When I select the brush tool the brush does not appear on my canvas, i can not see the brush on the canvas but when i move away from it my cursor reappears. I have tried hiding an
https://bugs.kde.org/show_bug.cgi?id=458753 Chris changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458753] When I select the brush tool the brush does not appear on my canvas, i can not see the brush on the canvas but when i move away from it my cursor reappears. I have tried hiding an
https://bugs.kde.org/show_bug.cgi?id=458753 --- Comment #1 from Chris --- Nevermind i read that 5.1 is recommended to use with windows 8.1 or higher -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438874] Disk & Devices applet doesn't show USB removable devices and SD cards after disconnecting and re-connecting them
https://bugs.kde.org/show_bug.cgi?id=438874 --- Comment #45 from Chris --- (In reply to Fabio from comment #42) > > Is there any howto which explains how I can test your merge? > > I'm using archlinux. > > I have no idea about the correct way to do this kind of testing on Arch, but > as a dirty hack you can just grab the three updated files from > https://invent.kde.org/plasma/plasma-workspace/-/tree/master/applets/ > devicenotifier/package/contents/ui and replace the ones in your current > installation; in my case they are in the > /usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui folder. > Once the files are replaced, you need to restart plasma for it to pick up > the new version. Thanks for this. Works for me. FYI, I did not do a "Live swapping of files". I dropped out of Plasma to the CLI and the replaced the files. Ran startx to get back in to Plasma. May not be related. I still occasionally see a Plasma restart when "Safely Removing" the device. Very rare of this desktop, more often on my laptop. Since replacing the files on Sept 4 (Your post over at the Slackware Forum), I've only seen this once on my laptop. Using a USB device is a daily thing. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 443058] New: The font on windows to add/edit Activities is totally invisible
https://bugs.kde.org/show_bug.cgi?id=443058 Bug ID: 443058 Summary: The font on windows to add/edit Activities is totally invisible Product: kde Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: chrisl...@antrapol.com Target Milestone: --- Created attachment 141979 --> https://bugs.kde.org/attachment.cgi?id=141979&action=edit example activity window in Breath2 2021 Dark theme. Similar UI for light theme SUMMARY STEPS TO REPRODUCE 1. Right click on desktop 2. Select Show Activity Switcher 3. Click on + Create activity ... OBSERVED RESULT Using Breath2 2021 - Windows only visible for entry field Using Breath2 2021 Dark - Windows only visible for entry field EXPECTED RESULT The Windows to create activity should have label visible too. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 443058] The font on windows to add/edit Activities is totally invisible
https://bugs.kde.org/show_bug.cgi?id=443058 --- Comment #1 from Chris --- Created attachment 141980 --> https://bugs.kde.org/attachment.cgi?id=141980&action=edit Light theme example -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 443058] The font on windows to add/edit Activities is totally invisible
https://bugs.kde.org/show_bug.cgi?id=443058 --- Comment #2 from Chris --- OBSERVED RESULT Using Breath2 2021 - Windows only entry field is visible Using Breath2 2021 Dark - Windows only entry field is visible -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 443058] The font on windows to add/edit Activities is totally invisible
https://bugs.kde.org/show_bug.cgi?id=443058 Chris changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|DOWNSTREAM |--- --- Comment #4 from Chris --- Somehow I'm not so sure since I've tested the following themes: * Ant-Dark * Breath2 * Breath2 2021 * Breath2 2021 Dark * Breath2 2021 Light * Breeze * Breeze Dark * Breeze Twilight * McMojave * Oxygen * WhiteSur-dark ALL theme gave me the same output. Either background is dark or light, label is always not visible. I thought Breath2 is the default from Manjaro so should work but ends up still the same result. All themes messing this up? I'm not sure about this. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 Chris changed: What|Removed |Added CC|k...@ontoemail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451386] Black Screen with Movable Cursor after Screens Resume from Sleep
https://bugs.kde.org/show_bug.cgi?id=451386 Chris changed: What|Removed |Added CC||chris.k...@gmail.com --- Comment #4 from Chris --- I'm having a similar issue. When the display goes to sleep or I turn off the monitor, some KDE processes (konversation, kmail, akregator, etc) lock up with 100% CPU utilization, and when I wake/turn on the monitor, I just get a blank screen with a cursor. If I move the cursor, the screen will flicker with dirty contents and leave mouse trails all over the place. Blindly typing in my password apparently does nothing. I have found that I can kill the user (switching to a different tty, e.g. ctrl+alt+f2, kill kwin_wayland and various other processes running as the user) and it'll bring me back to the login screen where I can log back in and use the system again. Better than a full reboot, but hardly makes for a usable system whenever the monitor is turned off. I have also found that if I set Adaptive sync to Never in System Settings -> Display and Monitor, I can turn off the monitor and turn it back on and keep KWin-Wayland running properly. However the same KDE processes will still lock up with 100% CPU utilization (they become unresponsive and need to be closed/restarted), and the Adaptive sync setting resets to Automatic. Interestingly, this only started when I got a new monitor. I had an old hand-me-down Samsung monitor connected via HDMI, and never had any issues when the display went to sleep or I turned off the monitor. But once I replaced it with a newer LG 27GP850 monitor connected via Display Port, these issues started. I'm using Debian Unstable with kde-wayland 5.24.3-1. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451702] New: Various KDE apps lock up with 100% CPU usage when monitor powers off
https://bugs.kde.org/show_bug.cgi?id=451702 Bug ID: 451702 Summary: Various KDE apps lock up with 100% CPU usage when monitor powers off Product: kwin Version: 5.24.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: chris.k...@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 *** When the monitor is turned off with its power button, or the energy saver puts the screen to sleep, various KDE-based apps become unresponsive and jump to 100% CPU use (which in turn causes my CPU fan to rev up). When the monitor is turned back on and I try to focus the affected apps, it grays out and puts "(Not Responding)" in the titlebar. No amount of waiting seems to let them come back, although I can click the X on the titlebar and it'll close after a moment. Apps I know this occurs with are Konversation, KMail, Konsole, and Akregator, but I certainly haven't done extensive testing to know what other apps are or aren't affected. I do know Pale Moon and Pidgin (non-KDE apps) are not affected. STEPS TO REPRODUCE 1. Start some KDE apps. 2. Turn off the monitor, or let the power saving put the monitor to sleep. 3. Turn on the monitor. OBSERVED RESULT The aforementioned apps are unresponsive with htop showing them taking 100% CPU time. EXPECTED RESULT The apps continue to work normally. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Debian Linux kernel version 5.16.12, plasma-desktop package version 5.24.3-1 (available in About System) KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This only started happening when I got my new monitor, and seems to only happen under Wayland. The apps remain responsive with normal CPU use when the monitor turns off with X11. I don't know if it's related to bug #451386 at all, but both issues started for me at the same time, and both only happen with Wayland. I'm using a Radeon RX 580 and the amdgpu kernel driver, with an LG 27GP850 monitor connected via Display Port. My old monitor, which everything worked fine with, was a Samsung SyncMaster T24B350 connected via HDMI. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451703] New: Adaptive sync keeps resetting to Automatic
https://bugs.kde.org/show_bug.cgi?id=451703 Bug ID: 451703 Summary: Adaptive sync keeps resetting to Automatic Product: kwin Version: 5.24.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: chris.k...@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 *** The Adaptive sync setting, under System Settings -> Display and Monitor, keeps resetting back to Automatic (the default) when the monitor is turned off or goes to sleep. STEPS TO REPRODUCE 1. Change "Adaptive sync" to "Never" in System Settings and click Apply (then Keep). 2. Turn off the monitor, or let power saving put it to sleep 3. Turn on the monitor, or wake it up OBSERVED RESULT The "Adaptive sync" setting is set back to Automatic. EXPECTED RESULT The "Adaptive sync" setting stays on Never. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Debian Linux kernel version 5.16.12 (available in About System) KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I'm using a Radeon RX 580 with the amdgpu kernel driver, with an LG 27GP850 monitor connected via Display Port. Because of what seems to be bug #451386, Adaptive sync causes KWin-Wayland to seize up for me when the display is turned off or goes to sleep. I set Adaptive sync to Never which seems to partially work around the issue, letting KWin-Wayland remain functional when the monitor is turned off and back on (although bug #451702 prevents this from being a full workaround), but I found it keeps getting reset back to Automatic afterward. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451703] Adaptive sync keeps resetting to Automatic
https://bugs.kde.org/show_bug.cgi?id=451703 --- Comment #2 from Chris --- (In reply to sethmb from comment #1) > This issue is marked as resolved, and yet I am still experiencing it in the > latest version of Plasma. Is there a workaround or has it actually been > patched? Latest release version, or the latest git version? The current release version seems to be 5.24.3, but the patch fixing the issue will be in the upcoming 5.24.4 release, so unless you're using the latest git we need to wait for 5.24.4. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 348082] monitor is randomly powered back on
https://bugs.kde.org/show_bug.cgi?id=348082 --- Comment #26 from Chris --- My configuration is a tp x230, i5-3210m, dp external monitor Dell p2715q. System is debian sid, 5.14.0-3-amd64, P 5.23.0 F 5.86.0, wayland, save for sddm 0.19, which is still using x11. First step, after 10 min, both screens turn cold as stone, as they are expected to. Then, something like 10 min later, they both turn back on. Starting with the laptop monitor, likely because it's much faster at turning on. That with no interaction whatsoever, and don't bring the fancy mouse here, it can control its temper during an earthquake when it's in the mood to. This scenario makes me think it's more likely the wake-up call comes from the pc than from the screen? 50% of the time, depending on its mood, it doesn't do that at all, and keeps the monitor off indefinitely when there is no user interaction. I've searched and asked, and I didn't find the tiniest clue on how to debug that, have some insight on what's going on. I only have the view from the outside, and that is of erratic behavior. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock
https://bugs.kde.org/show_bug.cgi?id=435113 Chris changed: What|Removed |Added CC||ch...@loggytronic.com --- Comment #85 from Chris --- I have done a bit of investigating and found a problem with kcminit, but be warned - this could be a total red herring! Upgrading from Kubuntu 21.10 to 22.04 brought this(?) bug to me. "udevadm trigger -s input" does immediately break the settings. Previously on 21.10 I used kcminit mouse in a script to switch mouse buttons, that no longer works. Running the following: QT_LOGGING_RULES="*.debug=true" kcminit kcm_mouse has a message about not finding a shared library. I compared this with a 21.10 installation and found the kcm_mouse.so file has moved - symlinking it back re-enables kcminit behaviour. ln -s /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_mouse.so /usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_mouse.so (Note also in 21.10 "kcminit mouse" worked, now it is "kcminit kcm_mouse" only). Unfortunately "udevadm trigger -s input" still immediately breaks the settings and they are not automatically fixed (I was hoping fixing kcminit would work), so there's still something else going on. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 455079] Basic effects not rendered
https://bugs.kde.org/show_bug.cgi?id=455079 --- Comment #2 from Chris --- Created attachment 150799 --> https://bugs.kde.org/attachment.cgi?id=150799&action=edit Screenshots of timeline of non working effects -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 455079] Basic effects not rendered
https://bugs.kde.org/show_bug.cgi?id=455079 --- Comment #3 from Chris --- (In reply to emohr from comment #1) > Thank you for posting the report with the details. > > Can you try with version 22.04.3? We fixed some rendering issues there. > > How do you have applied the fade and zoom in/out? Can you make a screenshot > of the timeline containing these effects? Thank you for your answer. I tried version 22.04.03 with following results: - Chroma Key Basic -> works now, great! - Video Fade in/out -> still doesn't work: Video appears as a hard cut - zoom in/out -> still doesn't work: black video at rendering -> I added some screenshots in the attachment (Screenshots_20220721.pdf) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock
https://bugs.kde.org/show_bug.cgi?id=435113
--- Comment #87 from Chris ---
Once again, apologies if I'm hijacking the thread, but I think I'm getting
somewhere here. If we're lucky, it's something to do with this bug.
With this intercept program placed at /usr/bin/kcminit ...
#include
#include
void main(int argc, char** argv)
{
system("ps auxf > /tmp/kcminit.log");
execv("/usr/bin/kcminit-real", argv);
}
... I am proving that when I hotplug a mouse something executes kcminit to
configure it, because in my kcminit.log this turns up:
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
chris 2579 0.0 0.0 2772 1344 ? S 22:31 0:00
/usr/bin/kcminit mouse
chris 2580 0.0 0.0 2888 948 ?S22:31 0:00 \_ sh -c ps
auxf > /tmp/kcminit.log
chris 2581 0.0 0.0 7816 3512 ?R22:31 0:00 \_ ps
auxf
Note that the call is kcminit mouse, not kcminit kcm_mouse as it should be.
So I think there are two problems here, Firstly the so files have moved and
kcminit is looking in the wrong place for them. Secondly, whatever is calling
kcminit is calling it with "mouse" and not "kcm_mouse".
Modifying the intercept program to this:
#include
#include
#include
void main(int argc, char** argv)
{
system("ps auxf > /tmp/kcminit.log");
if (!strcmp(argv[1], "mouse")) argv[1] = "kcm_mouse";
execv("/usr/bin/kcminit-real", argv);
}
... fixes my system. (Where "fix" = absolute bodge hack).
Obviously to fix it properly would need whatever is calling kcminit to be
modified, and the so file situation sorted out. I can't tell what is executing
kcminit as it appears at the root level of the ps "forest".
Anyone want to dare to test this on your system?
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 457132] New: Touchscreen long press is mouse-right-click with Dolphin but not with Okular
https://bugs.kde.org/show_bug.cgi?id=457132 Bug ID: 457132 Summary: Touchscreen long press is mouse-right-click with Dolphin but not with Okular Product: okular Version: 22.04.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: inkbottle...@gmail.com Target Milestone: --- There has been a new functionality added to Plasma 5.25, namely long-press acting as right click on touchscreen tablet pc. On my latest Debian-sid install, this functionality is fully working with Dolphin. However it does not work with Okular (version 22.04.03). This functionality is pivotal, at least for two reason: On a tablet pc, once you've added an annotation you have no way to delete it, since it requires a right click on the annotation. Also, you can't leave fullscreen mode as described here: https://www.reddit.com/r/kde/comments/u3fm2x/getting_out_of_okular_full_screen_mode/ SOFTWARE/OS VERSIONS Linux/KDE Plasma: debian-sid plasma 5.25 kwin-wayland okular 22.04.03 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 348529] Turn off screen after lock screen
https://bugs.kde.org/show_bug.cgi?id=348529 --- Comment #40 from Chris --- (In reply to Kai Uwe Broulik from comment #4) > That script isn't particularly efficient. > I like the idea of reducing the timeout for turning off the screen when it's > locked (and/or making that a separate option since you might not want it to > turn off at all while not locked), though. I added it to my todo list. > Thanks. What do you think of the script there https://bugs.kde.org/show_bug.cgi?id=348529#c33? It does not, on the face of it, rely on an infinite loop, and it works both with x11 and wayland. dbus-monitor --session "type='signal',interface='org.freedesktop.ScreenSaver'" | while read x; do case "$x" in *"boolean true"*) echo SCREEN_LOCKED; kwriteconfig5 --file powermanagementprofilesrc --group AC --group DPMSControl --key idleTime 60; qdbus org.kde.Solid.PowerManagement /org/kde/Solid/PowerManagement org.kde.Solid.PowerManagement.refreshStatus ;; *"boolean false"*) echo SCREEN_UNLOCKED; kwriteconfig5 --file powermanagementprofilesrc --group AC --group DPMSControl --key idleTime 600; qdbus org.kde.Solid.PowerManagement /org/kde/Solid/PowerManagement org.kde.Solid.PowerManagement.refreshStatus ;; esac done It is quick and dirty cut and paste but I think it works, and I don't see why not? As they say in https://bugs.kde.org/show_bug.cgi?id=348529#c39, it could help having something like that integrated in System-Settings, instead on relying on users hacks. It is annoying having 30W plus, of monitor LED, glowing unnecessarily. (https://www.thehomehacksdiy.com/how-much-power-watts-does-a-monitor-use/) Keep in mind that for most users, monitor power button is not an option because it scrambles up all the settings. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457315] New: Trouble donating
https://bugs.kde.org/show_bug.cgi?id=457315 Bug ID: 457315 Summary: Trouble donating Product: krita Version: 5.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: chj...@hotmail.com Target Milestone: --- Unable to donate. Problem with website https://fund.krita.org/checkout/1/variation/2. "The webpage at https://acs2.3dsecure.no/mdpayacs/auth;mdsessionid=4CBB110DC0084B889421436B30E0940D might be temporarily down or it may have moved permanently to a new web address.". Also, you're not making it easy to give you money. I have to go through this entire process of signing in. You should at the very least provide Facebook, Google and Apple login. And maybe include the donation options within Krita itself, like a dropdown menu between "Window" and "Help". -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 457345] New: Cannot disable Zoom
https://bugs.kde.org/show_bug.cgi?id=457345 Bug ID: 457345 Summary: Cannot disable Zoom Product: gwenview Version: 22.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: chj...@hotmail.com Target Milestone: --- Hi there. Because my desktop zoom is assigned to ctrl+mousewheel, having zoom gwenview zoom enabled is very annoying. How do I disable it?I tried to hide the statusbar because that's where the zoom slider is, hoping that would solve the issue. But no luck. Is there a way to do this or perhaps resign CTRL to ALT or something? Or perhaps an option I could add to the config file? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 456883] Calender crash on startup after login
https://bugs.kde.org/show_bug.cgi?id=456883 Chris changed: What|Removed |Added CC||chris...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 456883] Calender crash on startup after login
https://bugs.kde.org/show_bug.cgi?id=456883 --- Comment #1 from Chris --- Created attachment 151035 --> https://bugs.kde.org/attachment.cgi?id=151035&action=edit New crash information added by DrKonqi kalendarac (5.20.1) using Qt 5.15.5 The application crashed on systemc start uo -- Backtrace (Reduced): #4 0x7f3e2fe46564 in KCalendarCore::Incidence::recurs() const () from /lib64/libKF5CalendarCore.so.5 #5 0x557a98996c5d in KalendarAlarmClient::checkAlarms() () #6 0x7f3e2f0728c6 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #7 0x7f3e2fc92106 in Akonadi::EntityTreeModel::collectionPopulated(long long) () from /lib64/libKF5AkonadiCore.so.5 #8 0x7f3e2fca2a82 in Akonadi::EntityTreeModelPrivate::itemFetchJobDone(long long, KJob*) () from /lib64/libKF5AkonadiCore.so.5 -- You are receiving this mail because: You are watching all bug changes.
