[kdenlive] [Bug 469958] New: Kdenlive effect motion tracker not working
https://bugs.kde.org/show_bug.cgi?id=469958 Bug ID: 469958 Summary: Kdenlive effect motion tracker not working Classification: Applications Product: kdenlive Version: 23.04.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: alicee...@gmx.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. Load a short video with 'easy' object (I used the hang glider per Youtube video) 2. Find and add 'Motion Tracker' effect to clip 3. Change to ANY algorithm (I tried them all). No other changes. Click 'Analyze' OBSERVED RESULT Progress bar run normally. When finished a brown error dialog pops up saying '...failed to filter source' Never gets to any keyframes but app does not crash. EXPECTED RESULT Per the many videos on YouTube, some copyable keyframes to inport to a 'Transform'. Never gets that far. SOFTWARE/OS VERSIONS Windows: 10, 64b Pro macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION A typical PC, Ryzen 5-3600, 32GB ram, 1TB M.2, Nvidia 1660Super w 6GB, etc. The detailed log that I get after the brown error box starts out: "Current Frame: 1, percentage: 0 Current Frame: 2, percentage: 0 Current Frame: 4, percentage: 1 Current Frame: 7, percentage:" and continues exactly this way until the last frame. I'm just assuming this is a bug since I have tried many clips and algorithms and it always fails the same way no matter what I have tried. BTW I did read the manual and other bugs but I saw nothing like this. I have a screen pic but don't know how to get it to you, if you even want it. Or perhaps I am doing something wrong. Either way, thanks. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 458274] New: Terrible contrast on dark mode
https://bugs.kde.org/show_bug.cgi?id=458274 Bug ID: 458274 Summary: Terrible contrast on dark mode Product: filelight Version: 22.08.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: al...@alicesworld.tech CC: martin.sandsm...@kde.org Target Milestone: --- Created attachment 151566 --> https://bugs.kde.org/attachment.cgi?id=151566&action=edit bad contrast, text is hard to read 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. Use breeze dark/materia dark/any QT dark theme 2. Open KDE File Light OBSERVED RESULT [Attached] EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 458274] Terrible contrast on dark mode
https://bugs.kde.org/show_bug.cgi?id=458274 --- Comment #1 from Alice --- I ran an older appimage version I found at https://apprepo.de/appimage/filelight, and here the text is in white when in dark mode and is readable -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 456811] New: Doesn't support dark mode on macOS
https://bugs.kde.org/show_bug.cgi?id=456811 Bug ID: 456811 Summary: Doesn't support dark mode on macOS Product: kate Version: 22.04.3 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: minor Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: quarkyal...@disroot.org Target Milestone: --- SUMMARY Kate doesn't support dark mode on macOS. STEPS TO REPRODUCE 1. Set macOS to use dark mode 2. Launch Kate OBSERVED RESULT It doesn't use dark mode. EXPECTED RESULT It uses dark mode (breeze dark). SOFTWARE/OS VERSIONS macOS: 12.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 456811] Doesn't automatically switch to dark mode on macOS
https://bugs.kde.org/show_bug.cgi?id=456811 Alice changed: What|Removed |Added Summary|Doesn't support dark mode |Doesn't automatically |on macOS|switch to dark mode on ||macOS -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 456811] Doesn't automatically switch to dark mode on macOS
https://bugs.kde.org/show_bug.cgi?id=456811 --- Comment #1 from Alice --- *I meant doesn't automatically switch to dark mode, not doesn't support. You can manually switch it to dark mode but it would be nice if it could do it automatically. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443182] New: Can't move icons in kickoff menu, Arch Linux
https://bugs.kde.org/show_bug.cgi?id=443182 Bug ID: 443182 Summary: Can't move icons in kickoff menu, Arch Linux Product: plasmashell Version: master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: quarkyal...@disroot.org CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY The icons are completely unmoveable in the Favorites section of the kickoff menu, the only way to move them is to unpin all of them and repin them in the order you want. The old menu allowed for moving these icons. STEPS TO REPRODUCE 1. Pin applications to favorites 2. Attempt to move them around OBSERVED RESULT They don't move at all. EXPECTED RESULT They get moved and placed where you want them. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: Plasma 5.22.90 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.
[plasmashell] [Bug 443182] Can't move icons in kickoff menu
https://bugs.kde.org/show_bug.cgi?id=443182 Alice changed: What|Removed |Added Summary|Can't move icons in kickoff |Can't move icons in kickoff |menu, Arch Linux|menu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475726] New: system settings crash on opening 'application style' when in gnome DE
https://bugs.kde.org/show_bug.cgi?id=475726 Bug ID: 475726 Summary: system settings crash on opening 'application style' when in gnome DE Classification: Applications Product: systemsettings Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: al...@askalice.me Target Milestone: --- Application: systemsettings (5.27.8) Qt Version: 5.15.11 Frameworks Version: 5.110.0 Operating System: Linux 6.5.5-x64v2-xanmod1-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: well dolphin looked really weird in gnome, it alternated between dark background on dark text to light backgrond on dark text, so i couldn't read half of the filenames, so i tried to alter my kde style but this page is still broken The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Aborted [KCrash Handler] #4 0x7f61a7cac83c in () at /usr/lib/libc.so.6 #5 0x7f61a7c5c668 in raise () at /usr/lib/libc.so.6 #6 0x7f61a7c444b8 in abort () at /usr/lib/libc.so.6 #7 0x7f61a82a00c2 in qt_assert(char const*, char const*, int) () at /usr/lib/libQt5Core.so.5 #8 0x7f61a82c6dc0 in () at /usr/lib/libQt5Core.so.5 #9 0x7f61989d3bf4 in () at /usr/lib/qt/plugins/styles/libqgtk2style.so #10 0x7f61a91e6f44 in QStyleFactory::create(QString const&) () at /usr/lib/libQt5Widgets.so.5 #11 0x7f6199ee1189 in () at /usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_style.so #12 0x7f61a62a4901 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at /usr/lib/libQt5Qml.so.5 #13 0x7f61a6250667 in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () at /usr/lib/libQt5Qml.so.5 #14 0x7f61a6251016 in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () at /usr/lib/libQt5Qml.so.5 #15 0x7f61a36849c2 in () at /usr/lib/libQt5QmlModels.so.5 #16 0x7f61a6900259 in () at /usr/lib/libQt5Quick.so.5 #17 0x7f61a68f1c7a in () at /usr/lib/libQt5Quick.so.5 #18 0x7f61a68f9aa7 in () at /usr/lib/libQt5Quick.so.5 #19 0x7f61a68fea0d in () at /usr/lib/libQt5Quick.so.5 #20 0x7f61a68f90b2 in QQuickItemView::modelUpdated(QQmlChangeSet const&, bool) () at /usr/lib/libQt5Quick.so.5 #21 0x7f61a84d06a3 in () at /usr/lib/libQt5Core.so.5 #22 0x7f61a3658a9b in QQmlInstanceModel::modelUpdated(QQmlChangeSet const&, bool) () at /usr/lib/libQt5QmlModels.so.5 #23 0x7f61a367d6cd in () at /usr/lib/libQt5QmlModels.so.5 #24 0x7f61a368034c in () at /usr/lib/libQt5QmlModels.so.5 #25 0x7f61a36866cb in QQmlDelegateModel::_q_modelReset() () at /usr/lib/libQt5QmlModels.so.5 #26 0x7f61a368d603 in QQmlDelegateModel::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib/libQt5QmlModels.so.5 #27 0x7f61a84d011f in () at /usr/lib/libQt5Core.so.5 #28 0x7f61a8458042 in QAbstractItemModel::modelReset(QAbstractItemModel::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #29 0x7f6199edd992 in () at /usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_style.so #30 0x7f6199edf269 in () at /usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_style.so #31 0x7f61a96e1c66 in () at /usr/lib/libKF5KCMUtils.so.5 #32 0x7f61a84c3024 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #33 0x7f61a91788ff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #34 0x7f61a849b5b8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #35 0x7f61a84a051b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #36 0x7f61a84e6588 in () at /usr/lib/libQt5Core.so.5 #37 0x7f61a6f0df19 in () at /usr/lib/libglib-2.0.so.0 #38 0x7f61a6f6c2b7 in () at /usr/lib/libglib-2.0.so.0 #39 0x7f61a6f0c112 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #40 0x7f61a84ea3cc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #41 0x7f61a849a2c4 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #42 0x7f61a849b763 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #43 0x55f8a694cbd9 in () #44 0x7f61a7c45cd0 in () at /usr/lib/libc.so.6 #45 0x7f61a7c45d8a in __libc_start_main () at /usr/lib/libc.so.6 #46 0x55f8a694d575 in () [Inferior 1 (process 295077) detached] The reporter indicates this bug may be a duplicate of or related to bug 474126. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 474126] System settings crash on opening 'Application Style'
https://bugs.kde.org/show_bug.cgi?id=474126 --- Comment #3 from Alice --- (In reply to Antonio Rojas from comment #1) > #9 0x7fd535f4fbf4 in () at /usr/lib/qt/plugins/styles/libqgtk2style.so > > The crash is in an unsupported style should i remove it? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 474126] New: System settings crash on opening 'Application Style'
https://bugs.kde.org/show_bug.cgi?id=474126 Bug ID: 474126 Summary: System settings crash on opening 'Application Style' Classification: Applications Product: systemsettings Version: 5.27.7 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: al...@askalice.me Target Milestone: --- Application: systemsettings (5.27.7) Qt Version: 5.15.10 Frameworks Version: 5.109.0 Operating System: Linux 6.4.12-arch1-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.27.7 [KCrashBackend] -- Information about the crash: navigating to Appearance -> Application Style causes this crash The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Aborted [KCrash Handler] #4 0x7fd55ce8e83c in () at /usr/lib/libc.so.6 #5 0x7fd55ce3e668 in raise () at /usr/lib/libc.so.6 #6 0x7fd55ce264b8 in abort () at /usr/lib/libc.so.6 #7 0x7fd55d6a0098 in qt_assert(char const*, char const*, int) () at /usr/lib/libQt5Core.so.5 #8 0x7fd55d6c6d78 in () at /usr/lib/libQt5Core.so.5 #9 0x7fd535f4fbf4 in () at /usr/lib/qt/plugins/styles/libqgtk2style.so #10 0x7fd55e5e6f94 in QStyleFactory::create(QString const&) () at /usr/lib/libQt5Widgets.so.5 #11 0x7fd536675189 in () at /usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_style.so #12 0x7fd55b4a6961 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at /usr/lib/libQt5Qml.so.5 #13 0x7fd55b44c76f in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () at /usr/lib/libQt5Qml.so.5 #14 0x7fd55b44d116 in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () at /usr/lib/libQt5Qml.so.5 #15 0x7fd55a915982 in () at /usr/lib/libQt5QmlModels.so.5 #16 0x7fd55bafb6e9 in () at /usr/lib/libQt5Quick.so.5 #17 0x7fd55bae9c2a in () at /usr/lib/libQt5Quick.so.5 #18 0x7fd55bafadf7 in () at /usr/lib/libQt5Quick.so.5 #19 0x7fd55baff9ad in () at /usr/lib/libQt5Quick.so.5 #20 0x7fd55baffc52 in QQuickItemView::modelUpdated(QQmlChangeSet const&, bool) () at /usr/lib/libQt5Quick.so.5 #21 0x7fd55d8d17f3 in () at /usr/lib/libQt5Core.so.5 #22 0x7fd55a8e9a9b in QQmlInstanceModel::modelUpdated(QQmlChangeSet const&, bool) () at /usr/lib/libQt5QmlModels.so.5 #23 0x7fd55a90e6ad in () at /usr/lib/libQt5QmlModels.so.5 #24 0x7fd55a91130c in () at /usr/lib/libQt5QmlModels.so.5 #25 0x7fd55a91768b in QQmlDelegateModel::_q_modelReset() () at /usr/lib/libQt5QmlModels.so.5 #26 0x7fd55a91e5c3 in QQmlDelegateModel::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib/libQt5QmlModels.so.5 #27 0x7fd55d8d126f in () at /usr/lib/libQt5Core.so.5 #28 0x7fd55d859182 in QAbstractItemModel::modelReset(QAbstractItemModel::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #29 0x7fd536671992 in () at /usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_style.so #30 0x7fd536673269 in () at /usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_style.so #31 0x7fd55eaf9c66 in () at /usr/lib/libKF5KCMUtils.so.5 #32 0x7fd55d8c4174 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #33 0x7fd55e57893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #34 0x7fd55d89c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #35 0x7fd55d8a165b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #36 0x7fd55d8e76d8 in () at /usr/lib/libQt5Core.so.5 #37 0x7fd55bf10a61 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #38 0x7fd55bf6dc29 in () at /usr/lib/libglib-2.0.so.0 #39 0x7fd55bf0e112 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #40 0x7fd55d8eb51c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #41 0x7fd55d89b404 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #42 0x7fd55d89c8a3 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #43 0x555d95a12bd9 in () #44 0x7fd55ce27cd0 in () at /usr/lib/libc.so.6 #45 0x7fd55ce27d8a in __libc_start_main () at /usr/lib/libc.so.6 #46 0x555d95a13575 in () [Inferior 1 (process 1322955) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 380375] New: Document preview does not work
https://bugs.kde.org/show_bug.cgi?id=380375 Bug ID: 380375 Summary: Document preview does not work Product: KBibTeX Version: 0.6 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: fisc...@unix-ag.uni-kl.de Reporter: butterflyonl...@gmail.com Target Milestone: --- There is no document preview content in Document Preview panel. It shows ``` Don't know how to show mimetype 'application/pdf'. Please install Okular to make use of its PDF viewing component ``` But I've installed Okular and configuration is set. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384996] New: Crash when configuring Digital Clock plasmoid in a panel
https://bugs.kde.org/show_bug.cgi?id=384996 Bug ID: 384996 Summary: Crash when configuring Digital Clock plasmoid in a panel Product: plasmashell Version: 5.10.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kashkay...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.5) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.12.13-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I was adding timezones to the Digital Clock plasmoid plasmashell version 5.10.5 on Arch Linux -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7af9cfec80 (LWP 10398))] Thread 19 (Thread 0x7f79f94d0700 (LWP 7)): #0 0x7f7aedbc3a84 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f7aedb7e138 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f7aedb7eb3b in () at /usr/lib/libglib-2.0.so.0 #3 0x7f7aedb7ed1c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f7af3bda064 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f7af3b7dfdb in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f7af39973ee in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f7af399c13b in () at /usr/lib/libQt5Core.so.5 #8 0x7f7af2b5508a in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f7af32a81bf in clone () at /usr/lib/libc.so.6 Thread 18 (Thread 0x7f39e7fff700 (LWP 11107)): #0 0x7f7aedbc3a69 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f7aedb7e153 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f7aedb7eb3b in () at /usr/lib/libglib-2.0.so.0 #3 0x7f7aedb7ed1c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f7af3bda064 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f7af3b7dfdb in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f7af39973ee in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f7af6b063d9 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f7af399c13b in () at /usr/lib/libQt5Core.so.5 #9 0x7f7af2b5508a in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f7af32a81bf in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7f79faffd700 (LWP 11060)): #0 0x7f7af2b5b38d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7af399d5cc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7a3b9692ef in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f7a3b96e339 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f7a3b9687f4 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f7a3b96e392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f7a3b9687f4 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f7a3b96bb43 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f7af399c13b in () at /usr/lib/libQt5Core.so.5 #9 0x7f7af2b5508a in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f7af32a81bf in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f79fb7fe700 (LWP 11059)): #0 0x7f7af2b5b38d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7af399d5cc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7a3b9692ef in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f7a3b96e339 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f7a3b9687f4 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f7a3b96e392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f7a3b9687f4 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f7a3b96bb43 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f7af399c13b in () at /usr/lib/libQt5Core.so.5 #9 0x7f7af2b5508a in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f7af32a81bf in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f79fbfff700 (LWP 11058)): #0 0x7f7af2b5b38d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/li
[plasmashell] [Bug 499989] Ability to disable inline divider on digital clock
https://bugs.kde.org/show_bug.cgi?id=499989 --- Comment #9 from alice --- > Its setting for custom spacing is omitted here to follow the principle: > "good design choices by default over unnecessary configuration." The > option could be introduced in the future if highly requested by users. https://invent.kde.org/plasma/plasma-workspace/-/commit/27755ed3004363cfb6df9b8b92921fa6406fb5a8 The digital clock settings has a grand total of seven options. This reads more like someone's personal preference and laziness to bother creating a setting for it and it shows. Since the original change has the bar remain even when the date isn't displayed it seems this commit did not spend enough time testing it's basic functionality. Next time consider adding a setting to the initial commit when you decide that your personal taste should trump everyone else's. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499989] Ability to disable inline divider on digital clock
https://bugs.kde.org/show_bug.cgi?id=499989 alice changed: What|Removed |Added CC||al...@alicehartley.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501574] New: Alt + Tab gets gradually slower over time
https://bugs.kde.org/show_bug.cgi?id=501574 Bug ID: 501574 Summary: Alt + Tab gets gradually slower over time Classification: Plasma Product: kwin Version: 6.3.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: ali.ali...@proton.me Target Milestone: --- Created attachment 179451 --> https://bugs.kde.org/attachment.cgi?id=179451&action=edit JournalCTL logs from KWIN SUMMARY ALT + TAB becomes slower over time, taking longer and longer to display the next window when pressing the combination. STEPS TO REPRODUCE 1. Use KDE Plasma as normal for a few hours, alt tab frequently, I used Audacity, and I closed it quite a lot while transferring sound files one at a time from my local storage to my media server using the split view. OBSERVED RESULT You'll see a delay of 1-2 seconds when switching tabs that won't go away no matter how many windows or processes you close. Everything else should perform as expected. EXPECTED RESULT Alt + Tab not slowing down at all after several hours. SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501574] Alt + Tab gets gradually slower over time
https://bugs.kde.org/show_bug.cgi?id=501574 --- Comment #1 from Alice --- Forgot to add, I'm using the 6.13.6-zen1-1-zen kernel (64-bit). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501574] Alt + Tab gets gradually slower over time
https://bugs.kde.org/show_bug.cgi?id=501574 --- Comment #3 from Alice --- Created attachment 179454 --> https://bugs.kde.org/attachment.cgi?id=179454&action=edit System Information -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501574] Alt + Tab gets gradually slower over time
https://bugs.kde.org/show_bug.cgi?id=501574 --- Comment #2 from Alice --- Created attachment 179453 --> https://bugs.kde.org/attachment.cgi?id=179453&action=edit GPU information -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501574] Alt + Tab gets gradually slower over time
https://bugs.kde.org/show_bug.cgi?id=501574 --- Comment #4 from Alice --- Created attachment 179455 --> https://bugs.kde.org/attachment.cgi?id=179455&action=edit Plasmashell logs -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501574] Alt + Tab gets gradually slower over time
https://bugs.kde.org/show_bug.cgi?id=501574 --- Comment #5 from Alice --- So I've done some using of my computer for a few hours, and it's definitely the combination of what I was doing with Audacity, Dolphin and transferring files. The alt tab is still fine even after sleep mode which was another theory of mine I had. Hopefully replicating it will show some possible results on your end? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435361] Graphical glitches (flashing) under wayland in kate
https://bugs.kde.org/show_bug.cgi?id=435361 --- Comment #10 from Alice McLafferty --- Indeed, I have no idea why having Firefox open would affect this behavior, but it is something I have noticed on my computer. I had about four windows open in Firefox, not sure if it's reproducible with only one window open. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435357] New: KWin no longer remebers window sizes and position, applications always open on the top left corner
https://bugs.kde.org/show_bug.cgi?id=435357 Bug ID: 435357 Summary: KWin no longer remebers window sizes and position, applications always open on the top left corner Product: kwin Version: 5.21.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: xnw...@yandex.com CC: isma...@gmail.com Target Milestone: --- SUMMARY On Fedora 34 beta (kwin 5.21.3), KWin no longer remembers the window position on Fedora 34 (KDE Spin). Applications will always open on the top left corner of the leftmost monitor. STEPS TO REPRODUCE 1. Install F34 KDE spin 2. Open any window, move it to somewhere else or resize it, then close it. 3. Reopen that application. OBSERVED RESULT Applications always open on the top left corner of the leftmost monitor. EXPECTED RESULT Window position and sizes are remembered like they were with kwin-5.20.5-1.fc33 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 (available in About System) KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I have two monitors attached to the system. This feature was functional on Fedora 33 since the very beginning. This bug is always reproducible, under both X11 and Wayland sessions. I have found no options to enable/disable this behavior in system settings. Only workaround I've found is to set custom window rules for every single application, which is physically impossible to do in practice. I susupect this is a Fedora specific issue, but I have not had the chance to try out another distro. I tried reading some of the config files in my home directory but was unable to find any clues either. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435357] KWin no longer remebers window sizes and position, applications always open on the top left corner
https://bugs.kde.org/show_bug.cgi?id=435357 Alice McLafferty changed: What|Removed |Added URL||https://bugzilla.redhat.com ||/show_bug.cgi?id=1944784 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktextwidgets] [Bug 435360] New: Backspace does not work if you press Ctrl+A and then press Backspace too quickly
https://bugs.kde.org/show_bug.cgi?id=435360 Bug ID: 435360 Summary: Backspace does not work if you press Ctrl+A and then press Backspace too quickly Product: frameworks-ktextwidgets Version: 5.80.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mon...@kde.org Reporter: xnw...@yandex.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 137330 --> https://bugs.kde.org/attachment.cgi?id=137330&action=edit Screencap from Dolphin's "New Folder" dialog SUMMARY Ctrl+A and Backspace do not work as intended if you do this too fast, the cursor is simply moved to the beginning of the line. This is reproducible on both of my Fedora systems (33 and 34). STEPS TO REPRODUCE 1. Open Kate or press F10 in Dolphin to get a text box you can use 2. Put in a line of text 3. Press Ctrl+A and then immediately press Backspace _very_ quickly OBSERVED RESULT Selected text does not get deleted if you do this too fast. EXPECTED RESULT Selected text should be deleted. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 33/34 (available in About System) KDE Plasma Version: 5.20.5 and 5.21.3 KDE Frameworks Version: 5.79.0 and 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I am unable to reproduce this with xdotool but it does work on both of my computers (both x11 and wayland). xdotool key --delay 0 ctrl+a key --delay 0 BackSpace -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktextwidgets] [Bug 435360] Backspace does not work if you press Ctrl+A and then press Backspace too quickly
https://bugs.kde.org/show_bug.cgi?id=435360 --- Comment #1 from Alice McLafferty --- Created attachment 137331 --> https://bugs.kde.org/attachment.cgi?id=137331&action=edit Screencap from Kate -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435361] New: Graphical glitches (flashing) under wayland in kate
https://bugs.kde.org/show_bug.cgi?id=435361 Bug ID: 435361 Summary: Graphical glitches (flashing) under wayland in kate Product: kwin Version: 5.21.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: xnw...@yandex.com Target Milestone: --- Created attachment 137332 --> https://bugs.kde.org/attachment.cgi?id=137332&action=edit A recording of the symptom. SUMMARY This is likely related to kwin but kate is the most common one that I noticed, whenever I press Ctrl+S, the line number column has a big chance of producing a flash. Fast flashing images really makes me uncomfortable so this makes kate very difficult use for me. STEPS TO REPRODUCE 1. Launch kate in a plasma wayland session 2. Press Ctrl+S 3. If you don't see it, press Ctrl+S again and again (but do not hold it down) OBSERVED RESULT The line number column sometimes flashes. EXPECTED RESULT There should be no graphical glitches. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34, kernel 5.11.11 (available in About System) KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.5.2 ADDITIONAL INFORMATION Changing compositor rendering backends does not help with this situation, and this does not happen in x11 sessions. I am using an RX550 with the amdgpu driver. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435361] Graphical glitches (flashing) under wayland in kate
https://bugs.kde.org/show_bug.cgi?id=435361 --- Comment #2 from Alice McLafferty --- Apologies, I meant 5.15.2. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435357] KWin no longer remebers window sizes and position, applications always open on the top left corner
https://bugs.kde.org/show_bug.cgi?id=435357 --- Comment #2 from Alice McLafferty --- Is this filed under the wrong component then? Maybe this is relevant? https://bugs.kde.org/show_bug.cgi?id=415150 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435361] Graphical glitches (flashing) under wayland in kate
https://bugs.kde.org/show_bug.cgi?id=435361 Alice McLafferty changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435357] KWin no longer remebers window sizes and position, applications always open on the top left corner
https://bugs.kde.org/show_bug.cgi?id=435357 --- Comment #4 from Alice McLafferty --- > Which windows are we talking about? KDE app windows or 3rd-party app windows > or all of them? All windows are affected, including KDE applications such as Kate or Dolphin. The _size_ of them seems to be retained, but the positions are not. > What is your Window Placement option Window Management -> Window Behavior -> Advanced -> Window Placement is set to "Minimal Overlapping" (default). Setting them to "center" makes it a little bit more tolerable to use temporarily. > If the leftmost window not the primary one? Does the problem go away if you > have only one monitor? Do you mean monitor? In Wayland session I have no way of setting a "primary monitor" (there is no such option in settings), and I can reproduce this with only a single monitor attached to the system as well. (physically disconnected the other display and re-logged in as well, just to be sure) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435357] KWin no longer remebers window sizes and position, applications always open on the top left corner
https://bugs.kde.org/show_bug.cgi?id=435357 --- Comment #6 from Alice McLafferty --- > On Wayland, lack of position memory is expected That is unfortunate, initially I thought this was a kwin feature (thus the bug report). So currently "everything opens on the top left corner" is the expected behavior with "Minimal Overlapping" in a wayland session? Additionally, I have tested this in an x11 session, and position + size do work correctly for KDE applications such as dolphin or ark. 3rd party applications unfortunately do not, and I was not aware of this being expected behavior either. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435357] KWin no longer remebers window sizes and position, applications always open on the top left corner
https://bugs.kde.org/show_bug.cgi?id=435357 --- Comment #9 from Alice McLafferty --- Guess this is currently unimplemented on wayland and unfixable on x11 then, thank you for the explanations. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktextwidgets] [Bug 435360] Backspace does not work if you press Ctrl+A and then press Backspace too quickly
https://bugs.kde.org/show_bug.cgi?id=435360 --- Comment #3 from Alice McLafferty --- I can reproduce this on a fresh Fedora 34 installation with no IME installed, and on my Fedora 33 installation which does have fcitx installed (but not activated). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435361] Graphical glitches (flashing) under wayland in kate
https://bugs.kde.org/show_bug.cgi?id=435361 --- Comment #4 from Alice McLafferty --- I highly suspect this is an issue with the graphics driver/graphics card but I do not have enough supporting evidence to prove it. Never had this kind of issues with i915. I don't see any error messages unfortunately. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktextwidgets] [Bug 435360] Backspace does not work if you press Ctrl+A and then press Backspace too quickly
https://bugs.kde.org/show_bug.cgi?id=435360 --- Comment #5 from Alice McLafferty --- Do the search fields in the clipboard and networkmanager widgets qualify as "plasma text fields"? If they do then yes I can reproduce it. On further inspection, it looks like Ctrl _might_ not have been physically released if I do this too fast, and other applications such as Firefox generally do not care and will clear the selection anyway. I'm having problems with KDE applications and plasma because they behave differently than everything else I'm accustomed to. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435361] Graphical glitches (flashing) under wayland in kate
https://bugs.kde.org/show_bug.cgi?id=435361 --- Comment #8 from Alice McLafferty --- Software versions have since changed so here are the new versions: Kate: 21.04.1 Linux/KDE Plasma: Fedora 34, kernel 5.12.8 KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 KWIN_USE_BUFFER_AGE=0 was placed into /etc/environment, computer was rebooted and I confirmed this variable has been set, but it's still very much reproducible just like the video showed. Another curious thing is that having Firefox running (doesn't matter if it's xwayland or wayland native) makes this issue significantly more difficult to reproduce with keyboard presses, but I can confirm it is still present. Additionally, I found another more effective way to reproduce this, it's holding Ctrl and keep scrolling up and down with the mouse wheel to repeatedly zoom in and out. This way I was able to reproduce this problem even with Firefox running, where it's incredibly difficult to reproduce the issue with F5 or Ctrl + S. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 217592] mouse cursor disappear when moved to topic, user list or channel tabs in conversation
https://bugs.kde.org/show_bug.cgi?id=217592 Isabell Alice changed: What|Removed |Added CC||isabellpa2...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 365064] New: Cannot search from google scholar
https://bugs.kde.org/show_bug.cgi?id=365064 Bug ID: 365064 Summary: Cannot search from google scholar Product: KBibTeX Version: 0.6 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Network/online search Assignee: fisc...@unix-ag.uni-kl.de Reporter: butterflyonl...@gmail.com When I search paper from google scholar, return "Searching 'Google Scholar' failed with error message: Error downloading http://scholar.google.com/ -server replied: Forbidden. -- You are receiving this mail because: You are watching all bug changes.
