[okular] [Bug 197726] Show annotations pop-up text in the reviews sidebar
https://bugs.kde.org/show_bug.cgi?id=197726 Kishore Gopalakrishnan changed: What|Removed |Added CC||rafael.palma.l...@gmail.com --- Comment #4 from Kishore Gopalakrishnan --- *** Bug 450748 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 450748] Show comments of the "Highlighter" and "Pop-up notes" in the sidebar
https://bugs.kde.org/show_bug.cgi?id=450748 Kishore Gopalakrishnan changed: What|Removed |Added Status|REPORTED|RESOLVED CC||kishor...@gmail.com Resolution|--- |DUPLICATE --- Comment #2 from Kishore Gopalakrishnan --- *** This bug has been marked as a duplicate of bug 197726 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 197726] Show annotations pop-up text in the reviews sidebar
https://bugs.kde.org/show_bug.cgi?id=197726 Kishore Gopalakrishnan changed: What|Removed |Added CC||toluterib...@gmail.com --- Comment #3 from Kishore Gopalakrishnan --- *** Bug 467173 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467173] Suggestion on how annotations are displayed in the sidebar
https://bugs.kde.org/show_bug.cgi?id=467173 Kishore Gopalakrishnan changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||kishor...@gmail.com --- Comment #1 from Kishore Gopalakrishnan --- *** This bug has been marked as a duplicate of bug 197726 *** -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 456328] Labplot 2.9 does not run
https://bugs.kde.org/show_bug.cgi?id=456328 --- Comment #6 from Alexander Semke --- (In reply to Peter from comment #5) > I have the same issues. I have an up-to-date Windows 10 64-Bit system, all > drivers are up-to-date. The PC has an integrated Intel Graphics and an > additional NVIDIA Quadro system. The last revision running on this PC was > the one released with > https://labplot.kde.org/2021/10/27/multi-axes-made-easy/. Already revision > 2.9 did not work. Now I tested 2.10. The same issue. What I see: the > initial logo pops-up for a few seconds, then disappears. That's all. I > would appreciate if you could investigate this now rather permanent issue. > There must have been some significant change from the test-version > introducing the multi-axes feature and the 2.9 release. > > PS: What I already tried with the latest 2.10 revision: installation for > only me, installation for all user's, installation in a directory which is > not MS Windows dominated. (I am aware of issues related to installation > into the MS default directories.) In my case: I installed into > C:\Progs\LabPlot. Installation via the MS Store. Installation of the > nightly build. Installation as Administrator. All behave the same: a few > seconds the logo, then nothing. > > Best regards, Peter. Can you please check the running processes after the splash screen disappears? Is the labplot process still running or is there any process anymore since it was killed for some reasons that we need to understand now? I assume the latter is the case and we need to debug... I had similar issues on my older Dell notebook where a "monitoring tool" from Dell blocked the loading of plugins for labplot which made the application crashing. After I stopped this tool, the problem was gone. Do you have something similar running on your system? Any anti-virus, etc.? Can you stop temporarily these services and start labplot again? We need to somehow nail down the actual problem on your system now. This is not a global problem with our windows build since we have many successful installations. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 467957] New: "Switch user" action creates a popup below the KRunner window
https://bugs.kde.org/show_bug.cgi?id=467957 Bug ID: 467957 Summary: "Switch user" action creates a popup below the KRunner window Classification: Plasma Product: krunner Version: 5.27.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@hexchain.org CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 157715 --> https://bugs.kde.org/attachment.cgi?id=157715&action=edit KRunner window on top of the popup dialog SUMMARY When invoking the "Switch User" action from KRunner, a popup is created below the KRunner window, making it unable to be interacted with. STEPS TO REPRODUCE Execute "Switch User" in KRunner. OBSERVED RESULT The KRunner window stays on top of the popup dialog. EXPECTED RESULT The KRunner window should either disappear or stay behind. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.8-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 467956] New: Kalendar crashing when saving an unedited event
https://bugs.kde.org/show_bug.cgi?id=467956 Bug ID: 467956 Summary: Kalendar crashing when saving an unedited event Classification: Applications Product: kalendar Version: 22.12.3 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: corod...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: kalendar (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 5.19.0-35-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: I was attempting to edit an existing event, as soon as I hit save Kalendar crashes The crash can be reproduced every time. -- Backtrace: Application: Kalendar (kalendar), signal: Segmentation fault [KCrash Handler] #4 0x55dd71d95e6c in ?? () #5 0x7f200f2f40d4 in QtPrivate::QSlotObjectBase::call (a=0x7fff9b876680, r=0x55dd73b4bae0, this=0x55dd747fdc60) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #6 doActivate (sender=0x55dd7303bd60, signal_index=3, argv=0x7fff9b876680) at kernel/qobject.cpp:3923 #7 0x7f200f2ed177 in QMetaObject::activate (sender=sender@entry=0x55dd7303bd60, m=m@entry=0x7f200f55b680 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff9b876680) at kernel/qobject.cpp:3983 #8 0x7f200f254b59 in QAbstractItemModel::dataChanged (this=this@entry=0x55dd7303bd60, _t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:557 #9 0x7f200f2915a1 in QSortFilterProxyModelPrivate::_q_sourceDataChanged (this=0x55dd73041aa0, source_top_left=..., source_bottom_right=..., roles=...) at itemmodels/qsortfilterproxymodel.cpp:1539 #10 0x7f200f2f4108 in doActivate (sender=0x55dd73032b00, signal_index=3, argv=0x7fff9b876930) at kernel/qobject.cpp:3935 #11 0x7f200f2ed177 in QMetaObject::activate (sender=sender@entry=0x55dd73032b00, m=m@entry=0x7f200f55b680 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff9b876930) at kernel/qobject.cpp:3983 #12 0x7f200f254b59 in QAbstractItemModel::dataChanged (this=this@entry=0x55dd73032b00, _t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:557 #13 0x7f200f2915a1 in QSortFilterProxyModelPrivate::_q_sourceDataChanged (this=0x55dd7303b440, source_top_left=..., source_bottom_right=..., roles=...) at itemmodels/qsortfilterproxymodel.cpp:1539 #14 0x7f200f2f4108 in doActivate (sender=0x55dd73032d10, signal_index=3, argv=0x7fff9b876be0) at kernel/qobject.cpp:3935 #15 0x7f200f2ed177 in QMetaObject::activate (sender=sender@entry=0x55dd73032d10, m=m@entry=0x7f200f55b680 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff9b876be0) at kernel/qobject.cpp:3983 #16 0x7f200f254b59 in QAbstractItemModel::dataChanged (this=this@entry=0x55dd73032d10, _t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:557 #17 0x7f200f2915a1 in QSortFilterProxyModelPrivate::_q_sourceDataChanged (this=0x55dd73033750, source_top_left=..., source_bottom_right=..., roles=...) at itemmodels/qsortfilterproxymodel.cpp:1539 #18 0x7f200f2f4108 in doActivate (sender=0x55dd73037c70, signal_index=3, argv=0x7fff9b876e90) at kernel/qobject.cpp:3935 #19 0x7f200f2ed177 in QMetaObject::activate (sender=, m=m@entry=0x7f200f55b680 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff9b876e90) at kernel/qobject.cpp:3983 #20 0x7f200f254b59 in QAbstractItemModel::dataChanged (this=, _t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:557 #21 0x7f201166dd2a in ?? () from /lib/x86_64-linux-gnu/libKF5ItemModels.so.5 #22 0x7f200f2f40d4 in QtPrivate::QSlotObjectBase::call (a=0x7fff9b8770f0, r=0x55dd73037c70, this=0x55dd730331e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #23 doActivate (sender=0x55dd7302f8d0, signal_index=3, argv=0x7fff9b8770f0) at kernel/qobject.cpp:3923 #24 0x7f200f2ed177 in QMetaObject::activate (sender=, m=m@entry=0x7f200f55b680 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff9b8770f0) at kernel/qobject.cpp:3983 #25 0x7f200f254b59 in QAbstractItemModel::dataChanged (this=, _t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:557 #26 0x7f20119848d4 in ?? () from /lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5 #27 0x7f201198edb9 in ?? () from /lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5 #28 0x7f200f2f4108 in doActivate (sender=0x55dd72fd4710, signal_index=3, argv=0x7fff9b877350) at kernel/qobject.cpp:3935 #29 0x7f20118d617b in Akonadi::Monitor::itemChanged(Akonadi::Item const&, QSet const&) () from /lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5 #30 0x7f20118e7692 in Akonadi::MonitorPrivate::emitItemsNotification(Akonadi::Protocol::Item
[systemsettings] [Bug 467174] On fresh Arch install with Firefox installed, nothing is set as default web browser
https://bugs.kde.org/show_bug.cgi?id=467174 --- Comment #6 from Yao Mitachi --- (In reply to Yao Mitachi from comment #5) > I may have to create a fresh install of Arch to do this. I'll try this soon. I created some free space on my drive and tried the Arch installer, but it ran into some issue. If I remember I'll try again another time. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466963] Filter Mask window crashes when choosing Map > Palettize
https://bugs.kde.org/show_bug.cgi?id=466963 Freya Lupen changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||penguinflyer2...@gmail.com --- Comment #1 from Freya Lupen --- Confirming that the Palettize filter dialog has a tendency to stop responding or crash, whether viewed through the Filters menu or the Filter Mask dialog, on 5.1.5 and 5.2.x. (Mostly tested on 5.2.x.) On Windows it usually stops responding. Turning off HiDPI support seems to let the Filter dialog work, but the Filter Mask dialog still crashes. On Linux it sometimes works and sometimes crashes. I tried turning HiDPI off because the backtrace while the Filter dialog hangs shows KisIconWidget::paintEvent() calling for DPI metrics. > frame #5: 0x7fff28362bfc Qt5Gui.dll`QWindow::devicePixelRatio() const > at qwindow.cpp:1322:52 > frame #6: 0x7fff5b1caf25 > Qt5Widgets.dll`QWidget::metric(QPaintDevice::PaintDeviceMetric) const at > qwidget.cpp:12598:51 > frame #7: 0x7fff14d11a0f > libkritaui.dll`std::__1::__function::__func std::__1::allocator, void > (QPainter&)>::operator()(QPainter&) [inlined] > QPaintDevice::devicePixelRatioF(this=0x01718d952100) const at > qpaintdevice.h:87:47 The Filter Mask dialog seems to crash in QMapData of KisSwatch, from KisFilterPalettize::processImpl(). > * thread #122, stop reason = Exception 0xc005 encountered at address > 0x7fff09194d86: Access violation reading location 0x > * frame #0: 0x7fff09194d86 libkritapigment.dll`QMapData KisSwatch>::createNode(int const&, KisSwatch const&, QMapNode KisSwatch>*, bool) [inlined] int > std::__1::__cxx_atomic_load[abi:v15000](__a=0xfeeefeeefeeefeee, > __order=memory_order_relaxed) at atomic:958:12 > frame #1: 0x7fff09194d86 libkritapigment.dll`QMapData KisSwatch>::createNode(int const&, KisSwatch const&, QMapNode KisSwatch>*, bool) [inlined] std::__1::__atomic_base false>::load[abi:v15000](this=0xfeeefeeefeeefeee, __m=memory_order_relaxed) > const at atomic:1588:17 > frame #2: 0x7fff09194d86 libkritapigment.dll`QMapData KisSwatch>::createNode(int const&, KisSwatch const&, QMapNode KisSwatch>*, bool) [inlined] int > QAtomicOps::loadRelaxed(_q_value=0xfeeefeeefeeefeee) at > qatomic_cxx11.h:239:25 > frame #3: 0x7fff09194d86 libkritapigment.dll`QMapData KisSwatch>::createNode(int const&, KisSwatch const&, QMapNode KisSwatch>*, bool) [inlined] > QBasicAtomicInteger::loadRelaxed(this=0xfeeefeeefeeefeee) const at > qbasicatomic.h:107:45 > frame #4: 0x7fff09194d86 libkritapigment.dll`QMapData KisSwatch>::createNode(int const&, KisSwatch const&, QMapNode KisSwatch>*, bool) [inlined] > QtPrivate::RefCount::ref(this=0xfeeefeeefeeefeee) at qrefcount.h:55:28 > frame #5: 0x7fff09194d86 libkritapigment.dll`QMapData KisSwatch>::createNode(int const&, KisSwatch const&, QMapNode KisSwatch>*, bool) [inlined] QMap QVariant>::QMap(this=0x01c2c40d9298, other=0x01c2f629d3f8) at > qmap.h:631:22 > frame #6: 0x7fff09194d82 libkritapigment.dll`QMapData KisSwatch>::createNode(int const&, KisSwatch const&, QMapNode KisSwatch>*, bool) [inlined] KoColor::KoColor(this=0x01c2c40d9260, > rhs=0x01c2f629d3c0) at KoColor.h:54:11 > frame #7: 0x7fff09194d74 libkritapigment.dll`QMapData KisSwatch>::createNode(int const&, KisSwatch const&, QMapNode KisSwatch>*, bool) [inlined] KisSwatch::KisSwatch(this=0x01c2c40d9260, > (null)=0x01c2f629d3c0) at KisSwatch.h:17:27 > frame #8: 0x7fff09194d74 libkritapigment.dll`QMapData KisSwatch>::createNode(this=0x01c2c7f22ea0, k=0x01c2f629d3b8, > v=0x01c2f629d3c0, parent=, left=) at > qmap.h:231:33 > frame #9: 0x7fff09194cc9 libkritapigment.dll`QMapNode KisSwatch>::copy(this=0x01c2f629d3a0, d=0x01c2c7f22ea0) const at > qmap.h:259:30 > frame #10: 0x7fff09194cf0 libkritapigment.dll`QMapNode KisSwatch>::copy(this=0x01c2c3dc3e70, d=0x01c2c7f22ea0) const at > qmap.h:262:31 > frame #11: 0x7fff09194cf0 libkritapigment.dll`QMapNode KisSwatch>::copy(this=0x01c2fad216e0, d=0x01c2c7f22ea0) const at > qmap.h:262:31 > frame #12: 0x7fff09195317 libkritapigment.dll`QMap KisSwatch>::detach_helper(this=0x01c2fab47db8) at qmap.h:976:63 > frame #13: 0x7fff091939ff > libkritapigment.dll`KisSwatchGroup::getSwatch(int, int) const [inlined] > QMap::detach(this=0x01c2fab47db8) at qmap.h:361:51 > frame #14: 0x7fff091939ec > libkritapigment.dll`KisSwatchGroup::getSwatch(int, int) const [inlined] > QMap::operator[](this=0x01c2fab47db8, > akey=0x0082c47fe91c) at qmap.h:680:5 > frame #15: 0x7fff091939ec > libkritapigment.dll`KisSwatchGroup::getSwatch(this=, column=2, > row=0) cons
[Discover] [Bug 466449] Discover crashes when manually installing RPM.
https://bugs.kde.org/show_bug.cgi?id=466449 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 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.
[Smb4k] [Bug 465392] Just flat doesn't work on Zorin 16.2
https://bugs.kde.org/show_bug.cgi?id=465392 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #10 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.
[plasmashell] [Bug 466370] Unable to create a Libre Office Calc file via the desktop right click context menu
https://bugs.kde.org/show_bug.cgi?id=466370 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 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.
[kaffeine] [Bug 466413] Kaffeine-Programmwechsel - Programm schließt sich
https://bugs.kde.org/show_bug.cgi?id=466413 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #4 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.
[kontact] [Bug 466308] Kontact crashes on launch
https://bugs.kde.org/show_bug.cgi?id=466308 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 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.
[plasmashell] [Bug 467351] The entire system tray + application launcher + wallpaper dissapears when unlocking after 5 minutes or more
https://bugs.kde.org/show_bug.cgi?id=467351 --- Comment #5 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.
[Qt/KDE Flatpak Runtime] [Bug 420529] "Background activity" notification appears while an app installed via flatpak/flathub is running
https://bugs.kde.org/show_bug.cgi?id=420529 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #22 from Thiago Sueto --- https://www.reddit.com/r/kde/comments/11ul75n/comment/jcrlzdu/?utm_source=share&utm_medium=web2x&context=3 > I once had this popup on one of my applications packaged as Flatpak as well. > From my testing on KDE it seems to get triggered when an application - > launched as Flatpak loses focus and / or has a tray icon - doesn't implement > the xdg background portal. > As for my app, I implemented xdg background portal using libportal and that > popup went away. This indeed seems to happen on an individual app basis. Telegram and KSnip work correctly and only trigger the notification when they're *closed* to the tray. Other apps do not work correctly. Additionally, this bug can lead to destructive behavior that I found out in the MicroOS Desktop channel: Firefox triggers this notification, and if the user clicks on Learn More and then select the option to stop it from running in the background, Firefox simply closes, and every time it gets opened again, it's immediately closed. The only way to revert the operation is by using Flatseal, going to the app's Portal settings and either clicking the cleanup/undo icon or allowing the app to run in the background. The Flatpak KCM lacks these settings, last I saw. So this is hard for users to find out, and if they cannot find this, they become incapable of reopening the application. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #53 from caulier.gil...@gmail.com --- Created attachment 157714 --> https://bugs.kde.org/attachment.cgi?id=157714&action=edit git rebase instruction 2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #52 from caulier.gil...@gmail.com --- Created attachment 157713 --> https://bugs.kde.org/attachment.cgi?id=157713&action=edit git rebase instruction 1 Hi Geoff, The rebase instruction is given in the merge request / Changes view, because there is a conflict to solve as another guy as committed a fix in the head repository (a translator who review typo). Gilles -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467955] Plugging in new display crashes Plasmashell
https://bugs.kde.org/show_bug.cgi?id=467955 --- Comment #1 from mira...@mirandastreeter.com --- Also forgot to add: This was using an X11 session, Xorg version 21.1.7 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467955] Plugging in new display crashes Plasmashell
https://bugs.kde.org/show_bug.cgi?id=467955 mira...@mirandastreeter.com changed: What|Removed |Added CC||mira...@mirandastreeter.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467955] New: Plugging in new display crashes Plasmashell
https://bugs.kde.org/show_bug.cgi?id=467955 Bug ID: 467955 Summary: Plugging in new display crashes Plasmashell Classification: Plasma Product: plasmashell Version: 5.27.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Multi-screen support Assignee: plasma-b...@kde.org Reporter: mira...@mirandastreeter.com CC: aleix...@kde.org, notm...@gmail.com Target Milestone: 1.0 Created attachment 157712 --> https://bugs.kde.org/attachment.cgi?id=157712&action=edit crash on new monitor SUMMARY When plugging in a new display, plasmashell can crash (mulitple times over) resulting in the new display having a blank screen (no shell). So far unable to reproduce after saving display settings and unplugging/replugging, but until that point the "new display" part may or may not be relevant. STEPS TO REPRODUCE 1. Plug in new monitor OBSERVED RESULT Plasmashell crashes (three times over in this case), leaving new screen blank EXPECTED RESULT Plasmashell does not crash, and loads properly on new display SOFTWARE/OS VERSIONS Linux/KDE Plasma KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Video Card: AMD RX 6600 XT Mesa Version: 23.0.1 Kernel Version: 6.2.8-arch1-1 Attached is journal output starting from once I plugged in the new screen, to when I first opened the display configuration in the settings app to check what had happened. Before the crash, I had DP-2 and DP-3, both 1920x1080@60, with DP-3 left of DP-2 I then plugged in HDMI-1 with a native res of 3840x2160@120, which lead to the crashing -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467675] digiKam fail to export to WEBP and WBMP formats
https://bugs.kde.org/show_bug.cgi?id=467675 --- Comment #29 from Geoff King --- (In reply to caulier.gilles from comment #24) > New test, with test01.jpg open in editor, edited with gmic/B&W, and exported > to webp, jp2, and wbmp. > > All is fine expected for wbmp which is broken due to a bug in KImageFormats > codecs. > > https://i.imgur.com/Jsd8Gp9.png > > Exif, makernotes, and XMP are here for webp, jp2. The original JPEG file do > not have any GPS data, so... > > Gilles For me there is definitely something wrong with using gmic and exporting to WEBP on MacOS. I have tried several times (GMIC black & white filter and others) and it gives a transparent file exporting to WEBP. I also tried this on Windows and it gave similar results (one quick test). I looked at Ubuntu also, and it doesn't have the gmic plugin in the appimage. If I use the same source file, process using the digikam built in black and white module, then export, it works fine. When exporting to WEBP with or without editing, I lose the EXIF data. I tried several files with same results so don't think is my files. most webp export tests at quality 73 Thanks, Geoff -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467945] Shapes: converting nodes to corner/smooth/symmetric works only in the last opened document
https://bugs.kde.org/show_bug.cgi?id=467945 Ahab Greybeard changed: What|Removed |Added Ever confirmed|0 |1 CC||ahab.greybe...@hotmail.co.u ||k Status|REPORTED|CONFIRMED --- Comment #1 from Ahab Greybeard --- I can confirm this bug for the 5.1.5 and the 29 Mar 5.2.0 prealpha (git 0e505556f4) appimages on Debian 10. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 443806] Dolphin should allow option to cache thumbnails for separate encrypted devices / locations
https://bugs.kde.org/show_bug.cgi?id=443806 --- Comment #20 from flan_suse --- (In reply to Alexander Wipperfürth from comment #19) > There is actually another workaround you guys could try, symlink the > folders you want to access on a regular basis and put the link into your > ~/ Sadly, this isn't feasible for myself (and probably many users), as we have different folders all over our drive. The issue needs to be resolved by upstream KDE. :( It's a matter of waiting now? I'm not even sure if this is being worked on. It used to work on earlier versions of KDE, until it was "fixed", and now we have our thumbnails on encrypted drives constantly being regenerated every time which costs time and CPU. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467634] Spectacle not respecting scaling when saving or copying to clipboard
https://bugs.kde.org/show_bug.cgi?id=467634 Noah Davis changed: What|Removed |Added CC||noaha...@gmail.com --- Comment #2 from Noah Davis --- I can't reproduce this and https://bugs.kde.org/show_bug.cgi?id=467398 seems to have some similarities. Can anyone else confirm whether this has been fixed? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467118] When pressing PrintScreen key to take new screenshot with main window open while using the "printScreen key takes new screenshot" setting, Spectacle closes
https://bugs.kde.org/show_bug.cgi?id=467118 Noah Davis changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/spectacle/commit/068c6 |hics/spectacle/commit/aef9e |f548688b3425a94786cacadbf53 |3a6a1df995e5f91dbdd922dc19d |02a6e123|0f23b10f --- Comment #7 from Noah Davis --- Git commit aef9e3a6a1df995e5f91dbdd922dc19d0f23b10f by Noah Davis. Committed on 30/03/2023 at 01:45. Pushed by ndavis into branch 'release/23.04'. Don't close all windows if activated by DBus with GUI and no CLI options No options and having a GUI is a heuristic for activating Spectacle via the PrintScreen key. Maybe we can find a better way to determine this later, but I'm trying to keep up with the release schedule for now. (cherry picked from commit 068c6f548688b3425a94786cacadbf5302a6e123) M +7-3src/SpectacleCore.cpp https://invent.kde.org/graphics/spectacle/commit/aef9e3a6a1df995e5f91dbdd922dc19d0f23b10f -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467954] kwin_wayland crashes
https://bugs.kde.org/show_bug.cgi?id=467954 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467118] When pressing PrintScreen key to take new screenshot with main window open while using the "printScreen key takes new screenshot" setting, Spectacle closes
https://bugs.kde.org/show_bug.cgi?id=467118 Noah Davis changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/spectacle/commit/068c6 ||f548688b3425a94786cacadbf53 ||02a6e123 Status|CONFIRMED |RESOLVED --- Comment #6 from Noah Davis --- Git commit 068c6f548688b3425a94786cacadbf5302a6e123 by Noah Davis. Committed on 30/03/2023 at 01:24. Pushed by ndavis into branch 'master'. Don't close all windows if activated by DBus with GUI and no CLI options No options and having a GUI is a heuristic for activating Spectacle via the PrintScreen key. Maybe we can find a better way to determine this later, but I'm trying to keep up with the release schedule for now. M +7-3src/SpectacleCore.cpp https://invent.kde.org/graphics/spectacle/commit/068c6f548688b3425a94786cacadbf5302a6e123 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423600] Desktop inherits DPI setting from SDDM login manager after first login
https://bugs.kde.org/show_bug.cgi?id=423600 --- Comment #28 from Alexander --- (In reply to akb825 from comment #2) > If the DPI scaling isn't 100%, it will be different for the login manager by > default unless you manually synchronize the settings under the Advanced > section of the "Login Screen (SDDM)" control panel. > > If you have synchronized the settings, it will have a section that looks > like this in /etc/sddm.conf.d/kde_settings.conf: > > [X11] > ServerArguments=-dpi 192 > > You can either change this section or modify the dpi argument value to force > them to differ. So I switched from KDE Neon to openSuse TW just to see if it was the same issue and yep, there it is. In the /etc/sddm.conf.d/kde_settings.conf the dpi was set to zero like "ServerArguments=-dpi 0". I changed it to 192 and the scaling was correct on logout. For some reason, it is not pulling the sync. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 467705] kdialog does not compile against Qt6/KF6
https://bugs.kde.org/show_bug.cgi?id=467705 bluescreenaven...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467494] Change of timezone is not reflected in Digital Clock applet's settings immediately
https://bugs.kde.org/show_bug.cgi?id=467494 Fushan Wen changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/ |1b65c6b362b081c5ca252356d24 |9db63631f17988cadcc1fd935a8 |0befcba72288c |218c1c05ecaa4 --- Comment #7 from Fushan Wen --- Git commit 9db63631f17988cadcc1fd935a8218c1c05ecaa4 by Fushan Wen. Committed on 30/03/2023 at 00:49. Pushed by fusionfuture into branch 'master'. applets/digital-clock: reload timezone after saving in Datetime KCM The datetime KCM emits a signal `clockUpdated` after the timezone is updated. Listen to the signal and reload the model when the signal is emitted. After the model is updated, re-apply selected timezones or select the updated default timezone when there is no selected timezone in the config dialog. This allows the default timezone in the widget's config dialog to be updated immediately after system timezone changes. FIXED-IN: 5.27.4 (cherry picked from commit 1b65c6b362b081c5ca252356d240befcba72288c) M +15 -6applets/digital-clock/plugin/timezonemodel.cpp M +3-0applets/digital-clock/plugin/timezonemodel.h https://invent.kde.org/plasma/plasma-workspace/commit/9db63631f17988cadcc1fd935a8218c1c05ecaa4 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467861] Copying a selection from a layer with alpha inheritance offsets the copy
https://bugs.kde.org/show_bug.cgi?id=467861 Freya Lupen changed: What|Removed |Added Resolution|--- |DUPLICATE CC||penguinflyer2...@gmail.com Status|REPORTED|RESOLVED --- Comment #2 from Freya Lupen --- *** This bug has been marked as a duplicate of bug 467811 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467811] Cut content from alpha inheriting layer pastes out of place
https://bugs.kde.org/show_bug.cgi?id=467811 Freya Lupen changed: What|Removed |Added CC||paleh21...@proton.me --- Comment #3 from Freya Lupen --- *** Bug 467861 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467811] Cut content from alpha inheriting layer pastes out of place
https://bugs.kde.org/show_bug.cgi?id=467811 Freya Lupen changed: What|Removed |Added CC||penguinflyer2...@gmail.com --- Comment #2 from Freya Lupen --- Seems to have been caused by commit e41db7b6, which checks whether a paste is within image boundaries. Apparently alpha-inheriting layers have an empty exactBounds(), so they are caught in the > (!clip->exactBounds().contains(image->bounds()) && > !clip->exactBounds().intersects(image->bounds())) check and get pasted at the center of the image. (libs/ui/actions/KisPasteActionFactories.cpp@234/235) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467954] New: kwin_wayland crashes
https://bugs.kde.org/show_bug.cgi?id=467954 Bug ID: 467954 Summary: kwin_wayland crashes Classification: Plasma Product: kwin Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: nicolas.fe...@gmx.de Target Milestone: --- #0 0x7fc38356fc97 in std::__uniq_ptr_impl >::_M_ptr() const (this=0x10) at /usr/include/c++/12/bits/unique_ptr.h:191 #1 std::unique_ptr >::get() const (this=0x10) at /usr/include/c++/12/bits/unique_ptr.h:462 #2 std::unique_ptr >::operator->() const (this=0x10) at /usr/include/c++/12/bits/unique_ptr.h:455 #3 KWaylandServer::SurfaceInterface::setOutputs(QList const&) (this=0x0, outputs=...) at /home/nico/kde6/src/kwin/src/wayland/surface_interface.cpp:905 #4 0x7fc3834197c8 in KWin::WaylandWindow::updateClientOutputs() (this=0x251c4f0) at /home/nico/kde6/src/kwin/src/waylandwindow.cpp:159 #5 0x7fc37fd9df7a in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc17e462d0, r=0x251c4f0, this=) at /home/nico/workspace/qt6/qtbase/src/corelib/kernel/qobjectdefs_impl.h:363 #6 doActivate(QObject*, int, void**) (sender=0x1278a10, signal_index=21, argv=0x7ffc17e462d0) at /home/nico/workspace/qt6/qtbase/src/corelib/kernel/qobject.cpp:3977 #7 0x7fc37fd9667f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x1278a10, m=m@entry=0x7fc383731fc0 , local_signal_index=local_signal_index@entry=18, argv=argv@entry=0x0) at /home/nico/workspace/qt6/qtbase/src/corelib/kernel/qobject.cpp:4037 #8 0x7fc383259a53 in KWin::Workspace::outputsChanged() (this=this@entry=0x1278a10) at /home/nico/kde6/build/kwin/src/kwin_autogen/EWIEGA46WW/moc_workspace.cpp:1319 #9 0x7fc38344be50 in KWin::Workspace::updateOutputs(QList const&) (this=this@entry=0x1278a10, outputOrder=...) at /home/nico/kde6/src/kwin/src/workspace.cpp:1381 #10 0x7fc38344caa6 in KWin::Workspace::slotOutputBackendOutputsQueried() (this=0x1278a10) at /home/nico/kde6/src/kwin/src/workspace.cpp:1270 #11 0x7fc37fd9df7a in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc17e464d0, r=0x1278a10, this=) at /home/nico/workspace/qt6/qtbase/src/corelib/kernel/qobjectdefs_impl.h:363 #12 doActivate(QObject*, int, void**) (sender=0x7fc36800d210, signal_index=3, argv=0x7ffc17e464d0) at /home/nico/workspace/qt6/qtbase/src/corelib/kernel/qobject.cpp:3977 #13 0x7fc37fd9667f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x7fc36800d210, m=m@entry=0x7fc383736300 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at /home/nico/workspace/qt6/qtbase/src/corelib/kernel/qobject.cpp:4037 #14 0x7fc3832512e0 in KWin::OutputBackend::outputsQueried() (this=this@entry=0x7fc36800d210) at /home/nico/kde6/build/kwin/src/kwin_autogen/TAC5DWH4SE/moc_outputbackend.cpp:214 #15 0x7fc38349e48a in KWin::DrmBackend::updateOutputs() (this=0x7fc36800d210) at /home/nico/kde6/src/kwin/src/backends/drm/drm_backend.cpp:329 #16 0x7fc37fd8f34c in QObject::event(QEvent*) (this=0x7fc36800d210, e=0x24968e0) at /home/nico/workspace/qt6/qtbase/src/corelib/kernel/qobject.cpp:1390 #17 0x7fc380f92a71 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x7fc36800d210, e=0x24968e0) at /home/nico/workspace/qt6/qtbase/src/widgets/kernel/qapplication.cpp:3284 #18 0x7fc37fd426a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x7fc36800d210, event=0x24968e0) at /home/nico/workspace/qt6/qtbase/src/corelib/kernel/qcoreapplication.cpp:1115 #19 0x7fc37fd42829 in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=) at /home/nico/workspace/qt6/qtbase/src/corelib/kernel/qcoreapplication.cpp:1533 #20 0x7fc37fd45600 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=data@entry=0xf4c100) at /home/nico/workspace/qt6/qtbase/src/corelib/kernel/qcoreapplication.cpp:1895 #21 0x7fc37feccd01 in QEventDispatcherUNIX::processEvents(QFlags) (this=0xf538f0, flags=...) at /home/nico/workspace/qt6/qtbase/src/corelib/kernel/qeventdispatcher_unix.cpp:432 #22 0x7fc3808933cd in QUnixEventDispatcherQPA::processEvents(QFlags) (this=, flags=...) at /home/nico/workspace/qt6/qtbase/src/gui/platform/unix/qunixeventdispatcher.cpp:27 #23 0x7fc37fd4d9f3 in QEventLoop::exec(QFlags) (this=this@entry=0x7ffc17e468d0, flags=..., flags@entry=...) at /home/nico/workspace/qt6/qtbase/src/corelib/global/qflags.h:34 #24 0x7fc37fd4a1e4 in QCoreApplication::exec() () at /home/nico/workspace/qt6/qtbase/src/corelib/global/qflags.h:74 #25 0x7fc3803aee4c in QGuiApplication::exec() () at /home/nico/workspace/qt6/qtbase/src/gui/kernel/qguiapplication.cpp:1888 #26 0x7fc380
[Breeze] [Bug 414777] Top-right-most pixel does not trigger right-most button in a GTK3 CSD headerbar app
https://bugs.kde.org/show_bug.cgi?id=414777 Fushan Wen changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/breeze-gtk/commit/0f8871 |ma/breeze-gtk/commit/83f4f7 |27b929ac2d50b22af1bb97fc254 |c184954eb89aaea52684f1ce076 |11b40aa |873e8c3 --- Comment #18 from Fushan Wen --- Git commit 83f4f7c184954eb89aaea52684f1ce076873e8c3 by Fushan Wen. Committed on 29/03/2023 at 16:56. Pushed by fusionfuture into branch 'Plasma/5.27'. gtk4/windowcontrols: extend control area to window borders This makes GTK4 window control buttons follow Fitts' law. (cherry picked from commit 0f887127b929ac2d50b22af1bb97fc25411b40aa) M +42 -152 src/gtk4/widgets/_window_decorations.scss https://invent.kde.org/plasma/breeze-gtk/commit/83f4f7c184954eb89aaea52684f1ce076873e8c3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421745] On Wayland, the color scheme of gtk3 apps is not immediately updated when I change the global theme; the apps need to be restarted
https://bugs.kde.org/show_bug.cgi?id=421745 Fushan Wen changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kde-gtk-config/commit/5f |ma/kde-gtk-config/commit/16 |75f4c94d5fc07cc3dd9b36c78a2 |08cf03670c71d85f110a7d2dda1 |97f3135feae |c576e939032 --- Comment #43 from Fushan Wen --- Git commit 1608cf03670c71d85f110a7d2dda1c576e939032 by Fushan Wen. Committed on 30/03/2023 at 00:21. Pushed by fusionfuture into branch 'master'. kded: provide `org.gtk.Settings` when `GTK_USE_PORTAL` is not set on Wayland A number of things that gnome-settings-daemon monitors for all the GTK+ applications aren't currently available for GTK+ Wayland clients, only through XSettings. As we already monitor fontconfig configurations, enabled GTK+ modules and whether applications should use animations, export those through a D-Bus interface. See https://bugzilla.gnome.org/show_bug.cgi?id=786693 Based on patch by Martin Blanchard https://bugzilla.gnome.org/show_bug.cgi?id=786694 Upstream change: https://github.com/GNOME/gnome-settings-daemon/commit/522640a6df95312669871e4f881afe4e37e495f9 FIXED-IN: 5.27.4 (cherry picked from commit 5f75f4c94d5fc07cc3dd9b36c78a297f3135feae) A +9-0.reuse/dep5 M +15 -2kded/CMakeLists.txt A +76 -0kded/gsd-xsettings-manager/gsd-xsettings-manager.cpp [License: GPL(v2.0+)] A +32 -0kded/gsd-xsettings-manager/gsd-xsettings-manager.h [License: GPL(v2.0+)] A +7-0kded/gsd-xsettings-manager/org.gtk.Settings.xml M +11 -0kded/gtkconfig.cpp M +4-0kded/gtkconfig.h https://invent.kde.org/plasma/kde-gtk-config/commit/1608cf03670c71d85f110a7d2dda1c576e939032 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 414777] Top-right-most pixel does not trigger right-most button in a GTK3 CSD headerbar app
https://bugs.kde.org/show_bug.cgi?id=414777 --- Comment #17 from Fushan Wen --- Git commit 59448164f7df462ae4a2c1119f6be59146d60399 by Fushan Wen. Committed on 29/03/2023 at 16:56. Pushed by fusionfuture into branch 'Plasma/5.27'. gtk3/titlebutton: extend control area to window borders (cherry picked from commit d11333a830a4fdf6482c176e9a036e236bc80134) M +21 -9src/gtk3/widgets/_window_decorations.scss M +7-3src/gtk4/widgets/_window_decorations.scss https://invent.kde.org/plasma/breeze-gtk/commit/59448164f7df462ae4a2c1119f6be59146d60399 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421745] On Wayland, the color scheme of gtk3 apps is not immediately updated when I change the global theme; the apps need to be restarted
https://bugs.kde.org/show_bug.cgi?id=421745 Fushan Wen changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.27.4 Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/kde-gtk-config/commit/5f |376c74f582a41a8e0eec7c4443d |75f4c94d5fc07cc3dd9b36c78a2 |8b7401be97f0d |97f3135feae Status|ASSIGNED|RESOLVED --- Comment #42 from Fushan Wen --- Git commit 5f75f4c94d5fc07cc3dd9b36c78a297f3135feae by Fushan Wen. Committed on 30/03/2023 at 00:17. Pushed by fusionfuture into branch 'Plasma/5.27'. kded: provide `org.gtk.Settings` when `GTK_USE_PORTAL` is not set on Wayland A number of things that gnome-settings-daemon monitors for all the GTK+ applications aren't currently available for GTK+ Wayland clients, only through XSettings. As we already monitor fontconfig configurations, enabled GTK+ modules and whether applications should use animations, export those through a D-Bus interface. See https://bugzilla.gnome.org/show_bug.cgi?id=786693 Based on patch by Martin Blanchard https://bugzilla.gnome.org/show_bug.cgi?id=786694 Upstream change: https://github.com/GNOME/gnome-settings-daemon/commit/522640a6df95312669871e4f881afe4e37e495f9 FIXED-IN: 5.27.4 A +9-0.reuse/dep5 M +15 -2kded/CMakeLists.txt A +76 -0kded/gsd-xsettings-manager/gsd-xsettings-manager.cpp [License: GPL(v2.0+)] A +32 -0kded/gsd-xsettings-manager/gsd-xsettings-manager.h [License: GPL(v2.0+)] A +7-0kded/gsd-xsettings-manager/org.gtk.Settings.xml M +11 -0kded/gtkconfig.cpp M +4-0kded/gtkconfig.h https://invent.kde.org/plasma/kde-gtk-config/commit/5f75f4c94d5fc07cc3dd9b36c78a297f3135feae -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 205447] [BiDi/Unicode] Non-BMP characters are incorrectly handled
https://bugs.kde.org/show_bug.cgi?id=205447 --- Comment #12 from Waqar Ahmed --- No longer reproducible, seems like no one closed this -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461142] Maximized windows use a different monitor to determine their bottom edge
https://bugs.kde.org/show_bug.cgi?id=461142 --- Comment #1 from jackygu...@hotmail.com --- It appears there is a very simple workaround: use kscreen-doctor to add a 1-pixel gap between the displays. Default KDE settings are not happy with this, but it works just fine. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 205447] [BiDi/Unicode] Non-BMP characters are incorrectly handled
https://bugs.kde.org/show_bug.cgi?id=205447 Waqar Ahmed changed: What|Removed |Added Resolution|--- |FIXED CC||waqar@gmail.com Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 467953] New: Custom sensors
https://bugs.kde.org/show_bug.cgi?id=467953 Bug ID: 467953 Summary: Custom sensors Classification: Applications Product: plasma-systemmonitor Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: niciceberg.pub...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Since each sensor's data is essentially retrieved (or at least can be) using a command, a proposed feature would be to add a custom sensor that reads the output of the periodically run command. Currently, only a limited number of sensors are available. With this approach, the user would be able to add their own sensor data sources, which would reduce your responsibility of managing all the exotic hardware cases, let users fix problems with their sensors (like my battery rate sensor reporting once in 20 seconds, despite the one in tlp reporting each second) by specifying different data sources, and improve customizability. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 467952] New: Annoying Loading Screen and Various API Errors
https://bugs.kde.org/show_bug.cgi?id=467952 Bug ID: 467952 Summary: Annoying Loading Screen and Various API Errors Classification: Frameworks and Libraries Product: frameworks-knewstuff Version: 5.104.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ad...@leinir.dk Reporter: dominicglus...@gmail.com CC: alexander.loh...@gmx.de, kdelibs-b...@kde.org Target Milestone: --- Created attachment 157711 --> https://bugs.kde.org/attachment.cgi?id=157711&action=edit Bug in effect knewstuff Seems to have a lot of network errors. Scrolling too fast will make this super long loading screen appear that isn't in the Ubuntu releases of KDE Plasma I've attached a simple recording of both bugs. Not sure where logs are stored but it happens without fail everytime I scroll through a "Get New Stuff" dialog. Another one I'll get is: Unknown Open Collaboration Service API error. (0) kde SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS (Arch) KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I have plasma-meta and kde-applications-meta installed since I use all of your apps as my default apps. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467951] New: Folder View not working
https://bugs.kde.org/show_bug.cgi?id=467951 Bug ID: 467951 Summary: Folder View not working Classification: Plasma Product: plasmashell Version: git-stable-Plasma/5.27 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: plasma-b...@kde.org Reporter: valerio.ga...@gmail.com CC: aleix...@kde.org, notm...@gmail.com Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. login 2. I can't see the content of the folder desktop 3. i have to switch from folder view to desktop view and back to see the content OBSERVED RESULT If i unplug the secon screen everything works EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: kde Neon 5.27 (available in About System) KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.18 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 409388] Backup and Restore KDE Connect Remote Commands
https://bugs.kde.org/show_bug.cgi?id=409388 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/536 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467675] digiKam fail to export to WEBP and WBMP formats
https://bugs.kde.org/show_bug.cgi?id=467675 --- Comment #28 from Geoff King --- WBMP corrupt export file bug filed here: https://bugs.kde.org/show_bug.cgi?id=467950 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 467950] New: Exporting a WBMP file on Digikam MacOS creates corrupt file.
https://bugs.kde.org/show_bug.cgi?id=467950 Bug ID: 467950 Summary: Exporting a WBMP file on Digikam MacOS creates corrupt file. Classification: Frameworks and Libraries Product: frameworks-kimageformats Version: 5.102.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alex.me...@kde.org Reporter: gski...@gmail.com CC: aa...@kde.org, kdelibs-b...@kde.org Target Milestone: --- SUMMARY WBMP file is created when exporting from Digikam, but is corrupt and small. See Digikam bug report thread here: https://bugs.kde.org/show_bug.cgi?id=467675#c25 STEPS TO REPRODUCE 1. Digikam 8.0.0 beta1. > Image Editor > Open a JPG for editing. 2. Click Export and select WBMP format 3. Export file. OBSERVED RESULT A file is exported, but is unusable. When trying to open it Digikam says it is corrupt. EXPECTED RESULT An image file. SOFTWARE/OS VERSIONS Windows: macOS: 12.6.3 Intel Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.15.8 ADDITIONAL INFORMATION Digikam Build date: 3/26/23 8:24 AM -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467675] digiKam fail to export to WEBP and WBMP formats
https://bugs.kde.org/show_bug.cgi?id=467675 --- Comment #27 from Geoff King --- Created attachment 157710 --> https://bugs.kde.org/attachment.cgi?id=157710&action=edit add missing jp2 test file from prior message Cannot attached test1.png and test4.jpg since they are too big. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #51 from Geoff King --- Hi Gilles, I created an account, forked, edited the text, saved 2 patch/commit files, and made a merge request. I got a message "Merge blocked: fast-forward merge is not possible. To merge this request, first rebase locally." Reading through the help file, I tried /rebase in a comment, but not sure that did anything. Any recommendations? Sorry to bother you with something like this, I've never used git or this system before so I'm probably missing something simple. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467949] New: Dolphin crashes when cut/pasting a folder to another expanded one
https://bugs.kde.org/show_bug.cgi?id=467949 Bug ID: 467949 Summary: Dolphin crashes when cut/pasting a folder to another expanded one Classification: Applications Product: dolphin Version: 22.08.2 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jean.clav...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.08.2) Qt Version: 5.15.6 Frameworks Version: 5.98.0 Operating System: Linux 5.19.0-38-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.10 DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: I'm sorry I don't remember more than that. It occured suddenly (no lag before) The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f1a37cc6082 in KFileItemModel::expandedParentsCount(KFileItemModel::ItemData const*) () at /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #5 0x7f1a37cf20e9 in KItemListView::hasSiblingSuccessor(int) const () at /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #6 0x7f1a37cf30c5 in KItemListView::updateSiblingsInformation(int, int) () at /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #7 0x7f1a37cf78ae in KItemListView::slotItemsRemoved(KItemRangeList const&) () at /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #8 0x7f1a35af36ff in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f1a37cb0af9 in KItemModelBase::itemsRemoved(KItemRangeList const&) () at /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #10 0x7f1a37ccc3d4 in KFileItemModel::slotItemsDeleted(KFileItemList const&) () at /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #11 0x7f1a35af36ff in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f1a3773e419 in KCoreDirLister::itemsDeleted(KFileItemList const&) () at /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #13 0x7f1a37742b48 in () at /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #14 0x7f1a37752943 in () at /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #15 0x7f1a37753914 in () at /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #16 0x7f1a37753ec5 in () at /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #17 0x7f1a35af36ff in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f1a37679ec9 in OrgKdeKDirNotifyInterface::FilesRemoved(QStringList const&) () at /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #19 0x7f1a3767b6e3 in OrgKdeKDirNotifyInterface::qt_metacall(QMetaObject::Call, int, void**) () at /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #20 0x7f1a36d7323b in () at /lib/x86_64-linux-gnu/libQt5DBus.so.5 #21 0x7f1a35ae7b30 in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f1a3676bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f1a35abae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f1a35abdeb1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f1a35b15427 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f1a33921569 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f1a339763c8 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7f1a3391ed20 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7f1a35b14aea in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7f1a35ab97cb in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x7f1a35ac1c2a in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x561f5209ce6e in () #33 0x7f1a35023510 in __libc_start_call_main (main=main@entry=0x561f5209a6e0, argc=argc@entry=3, argv=argv@entry=0x7ffc7bc68148) at ../sysdeps/nptl/libc_start_call_main.h:58 #34 0x7f1a350235c9 in __libc_start_main_impl (main=0x561f5209a6e0, argc=3, argv=0x7ffc7bc68148, init=, fini=, rtld_fini=, stack_end=0x7ffc7bc68138) at ../csu/libc-start.c:381 #35 0x561f5209d515 in () [Inferior 1 (process 3415) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 172630] [BiDi/Unicode] Cursor direction dependent upon last letter typed, not selected keyboard layout
https://bugs.kde.org/show_bug.cgi?id=172630 --- Comment #19 from Dotan Cohen --- (In reply to Christoph Cullmann from comment #18) > Git commit 5934689df192aa681c6d7856bd6eaed9f22790a5 by Christoph Cullmann, > on behalf of Waqar Ahmed. Thank you, I look forward to testing this. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467948] New: root Systemsettings dont match language
https://bugs.kde.org/show_bug.cgi?id=467948 Bug ID: 467948 Summary: root Systemsettings dont match language Classification: Applications Product: systemsettings Version: 5.27.3 Platform: Fedora RPMs OS: Other Status: REPORTED Severity: normal Priority: NOR Component: kcm_keyboard Assignee: plasma-b...@kde.org Reporter: amanita+kdeb...@mailbox.org CC: butir...@gmail.com Target Milestone: --- SUMMARY Sometimes you need to use root GUI applications and its really nice this is possible. I guess because its nieche its not very known and there may be many hidden bugs. You launch root dolphin like that: : pkexec env 'DISPLAY=$DISPLAY' 'XAUTHORITY=$XAUTHORITY' KDE_SESSION_VERSION=5 KDE_FULL_SESSION=true dolphin STEPS TO REPRODUCE 1. Launch Dolphin as root 2. See if your non QWERTY keyboard has the right settings 3. launch sudo systemsettings to adapt it OBSERVED RESULT The language is adapted correctly, the keyboard is wrong. EXPECTED RESULT The keyboard should be adapted too. This in general seems to be a way more common issue than language detection. SOFTWARE/OS VERSIONS Fedora 37 KDE 5.27.3 -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 467930] kinfocenter does not properly call graphics info commands
https://bugs.kde.org/show_bug.cgi?id=467930 --- Comment #2 from ltstarwars...@gmail.com --- (In reply to Paul Worrall from comment #1) > The extra lines come out on stderr if you issue those commands in bash so > can be difficult to spot amongst the stdout messages. (try 'command >out.txt > 2>&1' and then examine out.txt) Yeah, that got it. Sorry for the erroneous report. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 467898] marble-qt starts with small window which is empty
https://bugs.kde.org/show_bug.cgi?id=467898 Torsten Rahn changed: What|Removed |Added CC||r...@kde.org --- Comment #2 from Torsten Rahn --- Sounds strange - we haven't changed anything on the Marble-side that would explain such a behavior. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 467947] New: Display ksplash when waking from suspend?
https://bugs.kde.org/show_bug.cgi?id=467947 Bug ID: 467947 Summary: Display ksplash when waking from suspend? Classification: Plasma Product: ksplash Version: git-stable-Plasma/5.27 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: amanita+kdeb...@mailbox.org Target Milestone: --- SUMMARY I had my laptop deep sleep and got a black screen when waking it up again. This looked a bit concerning. If not even the screen locker is loaded, could ksplash be used to bridge that waiting time and make it look more "we have everything under control" ? STEPS TO REPRODUCE 1. Let your laptop deep sleep 2. Turn it on again 3. wait until the screenlocker appears OBSERVED RESULT The laptop has a black screen for quite a while EXPECTED RESULT Ksplash could show here, but only if its an overlay and not a process that prolongs other processes. SOFTWARE/OS VERSIONS Fedora 37 KDE Plasma 2.57.3 KDE Frameworks: 5.104.0 Qt: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 460160] Kate's main view can be resized by dragging the tab bar
https://bugs.kde.org/show_bug.cgi?id=460160 Waqar Ahmed changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467603] Okular crashed when using the 'Save Form' button in a PDF form
https://bugs.kde.org/show_bug.cgi?id=467603 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/graphics/okular/-/merge_requests/711 -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 467946] New: Change Ksplash to load as an overlay?
https://bugs.kde.org/show_bug.cgi?id=467946 Bug ID: 467946 Summary: Change Ksplash to load as an overlay? Classification: Plasma Product: ksplash Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: amanita+kdeb...@mailbox.org Target Milestone: --- SUMMARY Currently KSplash is contraproductive. It would make sense to use it for covering the loading tiles and all, but it just prolongs the process. OBSERVED RESULT Ksplash loads and the elements dont load until its finished. This makes it slower and has no use. EXPECTED RESULT Ksplash could be really useful. There are nice screens and displaying it as an overlay while the elements "settle down" (sometimes moving quite a lot at start) would be very nice. SOFTWARE/OS VERSIONS Fedora Kinoite 37 KDE 5.27.3 KDE Frameworks: 5.104.0 Qt: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 397389] Falkon crashes when launched
https://bugs.kde.org/show_bug.cgi?id=397389 Juraj changed: What|Removed |Added CC||sjeh...@yandex.com --- Comment #10 from Juraj --- *** Bug 467932 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 467932] Falkon freezes and crashes
https://bugs.kde.org/show_bug.cgi?id=467932 Juraj changed: What|Removed |Added CC||jurajora...@mailo.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Juraj --- *** This bug has been marked as a duplicate of bug 397389 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467945] New: Shapes: converting nodes to corner/smooth/symmetric works only in the last opened document
https://bugs.kde.org/show_bug.cgi?id=467945 Bug ID: 467945 Summary: Shapes: converting nodes to corner/smooth/symmetric works only in the last opened document Classification: Applications Product: krita Version: 5.1.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Vector Assignee: krita-bugs-n...@kde.org Reporter: fra...@pm.me Target Milestone: --- SUMMARY With more than one document opened, converting nodes to corner/smooth/symmetric works only in the document that was opened last. STEPS TO REPRODUCE 1. Open a file containing a vector layer and a shape (file A). 2. Open another file or create a new one (file B). 3. Go back to file A and try to convert a node to corner, smooth, or symmetric. OBSERVED RESULT - The node conversion to corner, smooth or symmetric doesn't work anymore in file A. - Closing file B does not fix this. - To have node conversion work again in file A, it has to be closed the reopened. SOFTWARE/OS VERSIONS Linux Mint 20.3 Cinnamon -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 467840] KDialog always has "-- KDialog" in titlebar, is meaningless to user
https://bugs.kde.org/show_bug.cgi?id=467840 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/kdialog/-/merge_requests/23 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467941] [Fedora Distupgrade using Discover] Update progress unavailable
https://bugs.kde.org/show_bug.cgi?id=467941 --- Comment #2 from Steve Cossette --- So, I've checked and it seems discover doesn'T really do update notification completion, so if anything, I can create a separate suggestion ticket about this. Though I think there should still be a "Downloading (5%)" in the progress bar or something to show the user how the update is progressing. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 467944] New: Percentage value not localisable
https://bugs.kde.org/show_bug.cgi?id=467944 Bug ID: 467944 Summary: Percentage value not localisable Classification: Applications Product: kolourpaint Version: 23.03.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: emir_s...@icloud.com Target Milestone: --- Created attachment 157709 --> https://bugs.kde.org/attachment.cgi?id=157709&action=edit screenshot See screenshot. The percentage value in Scale/Resize dialog is not localisable, therefore it is not possible to arrange the position of the sign (in my case - tr_TR, the number should follow the sign). See screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 441120] View difference does not work
https://bugs.kde.org/show_bug.cgi?id=441120 Bug Janitor Service changed: What|Removed |Added Status|REOPENED|ASSIGNED --- Comment #17 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/kate/-/merge_requests/1174 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467252] Clipboard nomenclature for next and previous is confusing
https://bugs.kde.org/show_bug.cgi?id=467252 --- Comment #6 from Nate Graham --- So having played with these actions a bit, here's a summary of what they do: "Next History Item" => Moves the first/active entry in the history to the bottom so it's the last item in the history, and then the item that was previously second in the history becomes first and hence active. "Previous History Item" => Moves the last item in the history that was moved there by using the "Next History Item" item back up to the top so it's the first item and hence active; the item that was previously first/active moves to the second position in the history list. I'm struggling to come up with better text that describes these. Maybe VDG folks can help. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 467920] Lost the default tab - how to restore it?
https://bugs.kde.org/show_bug.cgi?id=467920 Michał Dybczak changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Michał Dybczak --- I restored ksysguard to the default state but all my additional tabs I added are gone. All I had to do was to delete ~/.config/ksysguardrc This also fixed the issue with CPU and Network not being shown. Too bad there is no restore ability in GUI. There is option to remove tabs, even default ones, so there should be option to restore them. Closing the case. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 467943] Unable to see full account name in selection dropdown for QIF export
https://bugs.kde.org/show_bug.cgi?id=467943 Bob Swift changed: What|Removed |Added CC||bsw...@rsds.ca -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 467348] When using the app in a non-English language, cover overlay "Play" and "Add to Playlist" buttons do not work on startup until you switch to a different page and back
https://bugs.kde.org/show_bug.cgi?id=467348 Nate Graham changed: What|Removed |Added Summary|Cover overlay "Play" and|When using the app in a |"Add to Playlist" buttons |non-English language, cover |do not work when using the |overlay "Play" and "Add to |app in a non-English|Playlist" buttons do not |language|work on startup until you ||switch to a different page ||and back --- Comment #7 from Nate Graham --- Fascinating. Can confirm. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 443566] Make it easier for user to re-use existing security when adding to new investment account
https://bugs.kde.org/show_bug.cgi?id=443566 Bob Swift changed: What|Removed |Added CC||bsw...@rsds.ca -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 467943] New: Unable to see full account name in selection dropdown for QIF export
https://bugs.kde.org/show_bug.cgi?id=467943 Bug ID: 467943 Summary: Unable to see full account name in selection dropdown for QIF export Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: ux-ui Assignee: kmymoney-de...@kde.org Reporter: bsw...@rsds.ca Target Milestone: --- Created attachment 157708 --> https://bugs.kde.org/attachment.cgi?id=157708&action=edit Export dialog at default and expanded widths SUMMARY When you open the dialog box to export an account to a QIF file, the account selection dropdown is a fixed width that does not display the full name of the accounts in the list. Resizing the dialog box (increasing the width) extends the width of the "QIF Profile" selection but the width of the "Account to export" selection remains fixed. Hovering the mouse pointer over an item in the list does not display a tooltip with the full name of the item. STEPS TO REPRODUCE 1. Open the "QIF Export" dialog by selecting "File" > "Export" > "QIF..." from the menu bar on the main screen. 2. Increase the width of the "QIF Export" dialog by dragging the left or right edge of the dialog box. 3. OBSERVED RESULT The width of the "Account to export" selection remains fixed. The width of the "QIF Profile" selection expands to fill the width of the dialog box. EXPECTED RESULT The width of the "Account to export" and "QIF Profile" selections expand proportionally to the width of the dialog box. SOFTWARE/OS VERSIONS Windows: 7 and 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I am attaching screen images of the dialog box at different widths to illustrate that the width of the "Account to export" selection remains fixed. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 467372] Today's update fails with unmet dependencies
https://bugs.kde.org/show_bug.cgi?id=467372 --- Comment #10 from lnx...@westlot.net --- It's back as of today's update. I get the following: The following packages have unmet dependencies: neon-desktop: Depends: kinfocenter but it is not going to be installed Depends: kio-extras but it is not going to be installed Depends: powerdevil but it is not going to be installed Depends: sddm-theme-breeze but it is not going to be installed Recommends: dolphin but it is not going to be installed Recommends: dolphin-plugins but it is not going to be installed Recommends: gwenview but it is not going to be installed Recommends: hplip but it is not going to be installed Recommends: konsole but it is not going to be installed Recommends: okular but it is not going to be installed Recommends: phonon4qt5-backend-vlc but it is not going to be installed Recommends: plasma-widgets-addons but it is not going to be installed Recommends: plasma-workspace-wayland but it is not going to be installed Recommends: vlc but it is not going to be installed plasma-desktop: Depends: plasma-workspace (>= 4:5.14) but it is not going to be installed Depends: qml-module-org-kde-pipewire but it is not going to be installed Depends: libkf5notifyconfig5 but it is not going to be installed Depends: phonon4qt5 but it is not going to be installed Recommends: khelpcenter but it is not going to be installed Recommends: kinfocenter (>= 4:5.14) but it is not going to be installed Recommends: kio-extras but it is not going to be installed Recommends: powerdevil (>= 4:5.14) but it is not going to be installed -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467634] Spectacle not respecting scaling when saving or copying to clipboard
https://bugs.kde.org/show_bug.cgi?id=467634 João Figueiredo changed: What|Removed |Added CC||jf.mun...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 466172] SIGTRAP crash whenever getaddrinfo call is issued by valgrind
https://bugs.kde.org/show_bug.cgi?id=466172 --- Comment #8 from Mike J --- Hi. This bug can be closed. It is not caused by valgrind. In case it is of use in future to anyone, further checks have shown that TaniumClient version 7.4.9.1046 was running on the system and caused the problem. valgrind was working on the system with an earlier TaniumClient release, but stopped working when the TaniumClient package was upgraded late last year, affecting valgrind runs. As indirectly noted in the earlier comments, the C library getaddrinfo() function is dynamically loaded when first called by an application. I took valgrind out of the picture and ran "/usr/bin/hostname -d" under the control of the gdb debugger. - With TaniumClient running, on entry to getaddrinfo(), the int3 instruction is seen instead of the expected push %rbp instruction, corrupting the call stack and raising a SIGTRAP. If run with valgrind, valgrind catches the raised SIGTRAP signal in this case and exits with a core dump, showing a corrupt call stack. - When TaniumClient is stopped, the expected push %rbp instruction is instead seen. If run with valgrind, it runs correctly and completes normally. Thanks to Paul Floyd and Mark Wielaard for checking the problem and debugging advice which pointed me in the right direction for problem diagnosis. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 172630] [BiDi/Unicode] Cursor direction dependent upon last letter typed, not selected keyboard layout
https://bugs.kde.org/show_bug.cgi?id=172630 Christoph Cullmann changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/ktexteditor/commit/5 ||934689df192aa681c6d7856bd6e ||aed9f22790a5 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #18 from Christoph Cullmann --- Git commit 5934689df192aa681c6d7856bd6eaed9f22790a5 by Christoph Cullmann, on behalf of Waqar Ahmed. Committed on 29/03/2023 at 18:10. Pushed by cullmann into branch 'master'. Draw caret ourselves Drawing caret ourselves helps solve a few issues: 1. With custom line height, the caret is no longer smaller than line 2. Cursor direction depends on the block content, not keyboard layout (bug 172630). Our own cursor will not draw the direction marker and thus will avoid this issue 3. Make cursor insertion point a few pixels larger vertically (bug 452853). You can just increase the line height and the caret will be bigger :) Technically, this is not exactly what is requested, but it works. Making Cursor visually larger than the line is _possible_ but it means that now we need to _always_ dirty 3 lines for repaint: current line, line above, line below which is a lot of uneeded work for such a small thing. So this will do. It is also more efficient than the Qt implementation as the work done in here is a lot less. Related: bug 452853 M +24 -1src/render/katerenderer.cpp https://invent.kde.org/frameworks/ktexteditor/commit/5934689df192aa681c6d7856bd6eaed9f22790a5 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 452853] Make cursor insertion point a few pixels larger vertically
https://bugs.kde.org/show_bug.cgi?id=452853 Christoph Cullmann changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/ktexteditor/commit/5 ||934689df192aa681c6d7856bd6e ||aed9f22790a5 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Christoph Cullmann --- Git commit 5934689df192aa681c6d7856bd6eaed9f22790a5 by Christoph Cullmann, on behalf of Waqar Ahmed. Committed on 29/03/2023 at 18:10. Pushed by cullmann into branch 'master'. Draw caret ourselves Drawing caret ourselves helps solve a few issues: 1. With custom line height, the caret is no longer smaller than line 2. Cursor direction depends on the block content, not keyboard layout (bug 172630). Our own cursor will not draw the direction marker and thus will avoid this issue 3. Make cursor insertion point a few pixels larger vertically (bug 452853). You can just increase the line height and the caret will be bigger :) Technically, this is not exactly what is requested, but it works. Making Cursor visually larger than the line is _possible_ but it means that now we need to _always_ dirty 3 lines for repaint: current line, line above, line below which is a lot of uneeded work for such a small thing. So this will do. It is also more efficient than the Qt implementation as the work done in here is a lot less. Related: bug 172630 M +24 -1src/render/katerenderer.cpp https://invent.kde.org/frameworks/ktexteditor/commit/5934689df192aa681c6d7856bd6eaed9f22790a5 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 439595] Replacing Epub backends to mupdf
https://bugs.kde.org/show_bug.cgi?id=439595 luna sophia changed: What|Removed |Added CC||l...@unixpoet.dev -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 467937] Passive notification is hidden by overlay sheet
https://bugs.kde.org/show_bug.cgi?id=467937 ratijas changed: What|Removed |Added CC||m...@ratijas.tk -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467942] New: Windows Powertoys Text Extractor
https://bugs.kde.org/show_bug.cgi?id=467942 Bug ID: 467942 Summary: Windows Powertoys Text Extractor Classification: Applications Product: Spectacle Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: christian.tall...@gmx.de CC: k...@david-redondo.de Target Milestone: --- SUMMARY *** The Windows Powertoys Text Extractor is a nice tool that works similar to the sniping tool or Greenshot or KDE-Spectacle. You can select a rectangular part of the screen and it runs a OCR on the content and copies the text into your clipboard. I think a feature like that for Spectacle would be a really productive enhancement. It would be great if you could assign a different Hot-Key than the Screenshot Hot-Key for it. ** Currently you could take a screenshot with Spectacle. Run an OCR software on the saved screenshot e.g. Tesseract and then copy the results. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467941] [Fedora Distupgrade using Discover] Update progress unavailable
https://bugs.kde.org/show_bug.cgi?id=467941 --- Comment #1 from Steve Cossette --- Created attachment 157707 --> https://bugs.kde.org/attachment.cgi?id=157707&action=edit Update Progress -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467941] [Fedora Distupgrade using Discover] Update progress unavailable
https://bugs.kde.org/show_bug.cgi?id=467941 Steve Cossette changed: What|Removed |Added Summary|[Fedora Distupgrade using |[Fedora Distupgrade using |Discover] Minor UI issue|Discover] Update progress ||unavailable -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467941] New: [Fedora Distupgrade using Discover] Minor UI issue
https://bugs.kde.org/show_bug.cgi?id=467941 Bug ID: 467941 Summary: [Fedora Distupgrade using Discover] Minor UI issue Classification: Applications Product: Discover Version: 5.27.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updates (interactive) Assignee: plasma-b...@kde.org Reporter: farch...@gmail.com CC: aleix...@kde.org Target Milestone: --- Installed the new plasma that allows for updating using Discover from Fedora 37 to Fedora 38 (From here: https://copr.fedorainfracloud.org/coprs/aleasto/discover-distro-upgrade/packages/) Distro upgrade occurs in the background, but the discover UI seems to fail to show more information, or a decent estimation. The progress bar seems to be about accurate though. Shouldn't there be some kind of popup after it completed, to tell the user that it completed and a reboot is required to apply? The "More information" button is also greyed out and does nothing except make the update information smaller. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 393580] Improve parsing of the output with the auto evaluation option switched on.
https://bugs.kde.org/show_bug.cgi?id=393580 Alexander Semke changed: What|Removed |Added Resolution|--- |LATER Status|CONFIRMED |RESOLVED --- Comment #1 from Alexander Semke --- Will be addressed in https://invent.kde.org/education/cantor/-/issues/6. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467912] Image Editor ignores former window size at startup
https://bugs.kde.org/show_bug.cgi?id=467912 --- Comment #2 from Maik Qualmann --- Git commit 0c8aa2cddc36e7e08b103574e440e363020a065e by Maik Qualmann. Committed on 29/03/2023 at 19:22. Pushed by mqualmann into branch 'master'. try with disabled workaround for the KXMLGui The issue may have been resolved in the KF5 API. M +10 -8core/libs/widgets/mainview/dxmlguiwindow.cpp https://invent.kde.org/graphics/digikam/commit/0c8aa2cddc36e7e08b103574e440e363020a065e -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 467934] Percentage value not localisable
https://bugs.kde.org/show_bug.cgi?id=467934 --- Comment #2 from Emir SARI --- If that’s the case, shall I open a ticket with Qt? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 467887] Variables with multiple words (in camelCase or separated by underscore) are treated as separate words with ctrl
https://bugs.kde.org/show_bug.cgi?id=467887 --- Comment #4 from Waqar Ahmed --- This is a translation issue then, not sure where those are handled. So far I haven't seen any kate translation issues reported on bugzilla. You can also directly submit a translation fix to the KDE i18n team. They have a channel on matrix where you can reach out for more info. We have a bug open about being able to search for the english term in the "Command Bar". Unfortunately there is no way / i don't know of a way to get the actual untranslated text from a given action and provide it in the filter list. Also check https://docs.kde.org/stable5/en/kate/katepart/kate-part-multiple-cursors.html -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464592] Scrolling speed setting has no effect since Plasma 5.27 beta
https://bugs.kde.org/show_bug.cgi?id=464592 Nate Graham changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/commit/fec40b71631e |ma/kwin/commit/659cfcb4937f |d0e5104b92d53340764198d37c3 |36e3084478afcd0ac2518d53b3c |5 |d --- Comment #15 from Nate Graham --- Git commit 659cfcb4937f36e3084478afcd0ac2518d53b3cd by Nate Graham. Committed on 29/03/2023 at 17:39. Pushed by ngraham into branch 'Plasma/5.27'. Revert "backends/libinput: don't multiply v120 value by scroll speed" This reverts commit 9cd52b4060d5db3c7b10340e78236b3c216567cb. This commit broke the adjustable scroll speed feature on Wayland. That feature may not have been implemented in the most technically ideal way, but simply breaking it and leaving the mouse KCM with UI control that does nothing isn't great. Besides, there was always a simple way to avoid any scroll-related regressions caused by this feature: reset the scroll speed to its default value, which internally is a multiplier of 1 and exercises the same codepath that 9cd52b40 imposes on everyone. We can come up with a better implementation for Plasma 6. FIXED-IN: 5.27.4 (cherry picked from commit fec40b71631ed0e5104b92d53340764198d37c35) M +1-1src/backends/libinput/events.cpp https://invent.kde.org/plasma/kwin/commit/659cfcb4937f36e3084478afcd0ac2518d53b3cd -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 467887] Variables with multiple words (in camelCase or separated by underscore) are treated as separate words with ctrl
https://bugs.kde.org/show_bug.cgi?id=467887 --- Comment #3 from Alberto Torres Ruiz --- That's good to know, thank you very much. It was IMPOSSIBLE for me to find, because: 1. It only mentions camel case, not underscores at all (which are also affected by the option and most of my code is actually with underscores). 2. The translation into Spanish is nonsensical. 3. I already tried to search for "camel" everywhere but neither the word "camel" or "camello" is mentioned anywhere when it is not set to English. Should I file reports for usability issues? And why is the option on by default, anyway? On Tue, Mar 28, 2023 at 7:00 PM Waqar Ahmed wrote: > https://bugs.kde.org/show_bug.cgi?id=467887 > > Waqar Ahmed changed: > >What|Removed |Added > > > Resolution|--- |NOT A BUG > Status|REPORTED|RESOLVED > CC||waqar@gmail.com > > --- Comment #2 from Waqar Ahmed --- > Press, Alt + Ctrl + I, then Search and enter, => Toggle Camel > > This will disable camel hump cursor movement temporarily for the current > tab. > > It can be permanently disabled in the settings, search for "camel" > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462503] File copy fails if the device was not mounted before drag-and-drop
https://bugs.kde.org/show_bug.cgi?id=462503 Patrick Silva changed: What|Removed |Added Version|22.11.90|23.03.80 Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|FIXED |--- --- Comment #2 from Patrick Silva --- Can reproduce again with Dolphin 23.04 beta. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 467940] Translations for some strings are not applied
https://bugs.kde.org/show_bug.cgi?id=467940 --- Comment #2 from Emir SARI --- Created attachment 157705 --> https://bugs.kde.org/attachment.cgi?id=157705&action=edit 3 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 467940] Translations for some strings are not applied
https://bugs.kde.org/show_bug.cgi?id=467940 --- Comment #1 from Emir SARI --- Created attachment 157704 --> https://bugs.kde.org/attachment.cgi?id=157704&action=edit 2 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 467940] New: Translations for some strings are not applied
https://bugs.kde.org/show_bug.cgi?id=467940 Bug ID: 467940 Summary: Translations for some strings are not applied Classification: Applications Product: kalendar Version: 23.03.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: emir_s...@icloud.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 157703 --> https://bugs.kde.org/attachment.cgi?id=157703&action=edit 1 Kalendar has been translated into Turkish completely for a long time. However, some strings are still stuck in English. Please see screenshots. Some are fully in English, and some are mixed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 467934] Percentage value not localisable
https://bugs.kde.org/show_bug.cgi?id=467934 Waqar Ahmed changed: What|Removed |Added CC||waqar@gmail.com --- Comment #1 from Waqar Ahmed --- I am not sure if that is possible with QSpinbox... The additional text is just a suffix. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466227] Blur effect with TV Glitch [Burn-My-Windows] effect behaves differently after updating to KDE Plasma 5.27
https://bugs.kde.org/show_bug.cgi?id=466227 --- Comment #3 from saik --- I've attached what I assume is the same bug occurring on my device. The task switcher, for the first second(ish), displays as a blurred grey box. After a second, it 'loads in' and looks normal. This only occurs when: 1. Using plasma wayland 2. 'Visualization' for task switchers is on. 3. Using a Burn My Windows 'Window Open/Close Animation' desktop effect. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 467939] New: Clipped text in New... dialog
https://bugs.kde.org/show_bug.cgi?id=467939 Bug ID: 467939 Summary: Clipped text in New... dialog Classification: Applications Product: kalendar Version: 23.03.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: emir_s...@icloud.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 157702 --> https://bugs.kde.org/attachment.cgi?id=157702&action=edit screenshot In Kalendar New Task/Event dialog, the text for "Tap to set tags…" and "Click to set tags…" is clipped. See screenshot. The full string is "Ayarlamak için tıkla…" and "Ayarlamak için dokun…", but only "Ayarlamak için" is visible. And since the button width looks like it's fixed size, there is no way to show this. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 439697] Gwenview crashes in Gwenview::RasterImageItem::paint() when trying to rotate a jpg file quickly multiple times
https://bugs.kde.org/show_bug.cgi?id=439697 Nate Graham changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/gwenview/commit/5ddac2 |hics/gwenview/commit/8e8b02 |cc9ff426302771fb6c7aceae029 |5b79b44db957d164698b6868132 |53b945e |3b9a917 --- Comment #18 from Nate Graham --- Git commit 8e8b025b79b44db957d164698b68681323b9a917 by Nate Graham, on behalf of Nikita Karpei. Committed on 29/03/2023 at 18:53. Pushed by ngraham into branch 'release/23.04'. Save a shallow copy of the original image when rotating FIXED-IN: 23.04 The app crashes when trying to get an image from a document using document->image(). Looks like it can be destroyed from another thread so we should make a shallow copy of it. It's fast and fixes the crash. (cherry picked from commit 5ddac2cc9ff426302771fb6c7aceae02953b945e) M +11 -8lib/documentview/rasterimageitem.cpp M +1-0lib/documentview/rasterimageitem.h https://invent.kde.org/graphics/gwenview/commit/8e8b025b79b44db957d164698b68681323b9a917 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 465305] character counts are wrong when text includes emojis; each counted as two (2)
https://bugs.kde.org/show_bug.cgi?id=465305 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org --- Comment #4 from Christoph Cullmann --- Just to have some reasoning here: We use everywhere indices into UCS2 strings as columns. If we compute search matches, we use that, in the internal api we do that, e.g. for --column we do that. It would be a major effort to alter that and I don't see that it makes sense to spend our time on that. The cursor movement on editing is correct, that would be some issue, but that for rare characters the column offset is not as expected is IMHO no big issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466227] Blur effect with TV Glitch [Burn-My-Windows] effect behaves differently after updating to KDE Plasma 5.27
https://bugs.kde.org/show_bug.cgi?id=466227 saik changed: What|Removed |Added CC||trm...@case.edu --- Comment #2 from saik --- Created attachment 157701 --> https://bugs.kde.org/attachment.cgi?id=157701&action=edit Screenshot of the visual bug occurring on a 'Thumbnail Grid' task switcher. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 439697] Gwenview crashes in Gwenview::RasterImageItem::paint() when trying to rotate a jpg file quickly multiple times
https://bugs.kde.org/show_bug.cgi?id=439697 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||23.04 Latest Commit||https://invent.kde.org/grap ||hics/gwenview/commit/5ddac2 ||cc9ff426302771fb6c7aceae029 ||53b945e Status|ASSIGNED|RESOLVED --- Comment #17 from Nate Graham --- Git commit 5ddac2cc9ff426302771fb6c7aceae02953b945e by Nate Graham, on behalf of Nikita Karpei. Committed on 29/03/2023 at 18:53. Pushed by ngraham into branch 'master'. Save a shallow copy of the original image when rotating FIXED-IN: 23.04 The app crashes when trying to get an image from a document using document->image(). Looks like it can be destroyed from another thread so we should make a shallow copy of it. It's fast and fixes the crash. M +11 -8lib/documentview/rasterimageitem.cpp M +1-0lib/documentview/rasterimageitem.h https://invent.kde.org/graphics/gwenview/commit/5ddac2cc9ff426302771fb6c7aceae02953b945e -- You are receiving this mail because: You are watching all bug changes.