[dolphin] [Bug 440911] New: Dolphin crashed when opening VisualStudioCode.
https://bugs.kde.org/show_bug.cgi?id=440911 Bug ID: 440911 Summary: Dolphin crashed when opening VisualStudioCode. Product: dolphin Version: 20.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: goretant...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.12.3) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.0-25-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.4 Distribution: Ubuntu 21.04 -- Information about the crash: - What I was doing when the application crashed: I right clicked in Dolphin while V.S.C. was opening and it crashed, possibly due to not a lot of ram installed and having multiple firefox tabs open, 1 youtube video included. Also had Konsole and SmartGit open too if that helps. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7fb68cc35864 in __GI_abort () at abort.c:79 #6 0x7fb68cc98736 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fb68cdbd953 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:155 #7 0x7fb68cd373fa in __GI___fortify_fail (msg=msg@entry=0x7fb68cdbd93b "stack smashing detected") at fortify_fail.c:26 #8 0x7fb68cd373c6 in __stack_chk_fail () at stack_chk_fail.c:24 #9 0x7fb68b08e33f in QPixmap::transformed(QTransform const&, Qt::TransformationMode) const () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #10 0x7fb68b08e5cb in QPixmap::scaled(QSize const&, Qt::AspectRatioMode, Qt::TransformationMode) const () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #11 0x7fb68b09d6b1 in QPixmapIconEngine::pixmap(QSize const&, QIcon::Mode, QIcon::State) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #12 0x7fb68b09aae5 in QPixmapIconEngine::paint(QPainter*, QRect const&, QIcon::Mode, QIcon::State) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #13 0x7fb68b099b70 in QIcon::paint(QPainter*, QRect const&, QFlags, QIcon::Mode, QIcon::State) const () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #14 0x7fb68b797a50 in QCommonStyle::drawControl(QStyle::ControlElement, QStyleOption const*, QPainter*, QWidget const*) const () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7fb68469325c in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/styles/breeze.so #16 0x7fb68b9b8411 in QStyledItemDelegate::paint(QPainter*, QStyleOptionViewItem const&, QModelIndex const&) const () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7fb68ba007f0 in QTreeView::drawRow(QPainter*, QStyleOptionViewItem const&, QModelIndex const&) const () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fb68ba046ad in QTreeView::drawTree(QPainter*, QRegion const&) const () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fb68ba0b097 in QTreeView::paintEvent(QPaintEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7fb68b7575de in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7fb68b805b32 in QFrame::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7fb68ac2452b in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7fb68b714772 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7fb68ac247ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7fb68b74f53a in QWidgetPrivate::sendPaintEvent(QRegion const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7fb68b74fd62 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7fb68b7511c3 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7fb68b750fe2 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x7fb68b750fe2 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fb68b750fe2 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) ()
[kwin] [Bug 440094] Intermittent Kwin crash on wayland
https://bugs.kde.org/show_bug.cgi?id=440094 ha...@dayfamilyweb.com changed: What|Removed |Added Attachment #140222|0 |1 is obsolete|| Assignee|kwin-bugs-n...@kde.org |ha...@dayfamilyweb.com Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #7 from ha...@dayfamilyweb.com --- Created attachment 140678 --> https://bugs.kde.org/attachment.cgi?id=140678=edit kwin_wayland backtrace dump with debuging symbols Hi, here's the crash with the right debuging symbols. Sorry it took a while for me to work out which ones I need to install. (Can also upload the coredump if needed but its 300MB) All the other things that crash at the same time have this in their stacktrace if that helps: QMessageLogger::fatal (this=this@entry=0x7fffac3b1980, msg=msg@entry=0x7fcbb2f9d0b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 396177] Plasmashell dialog regression when KDE is used with Xmonad introduced by fix for 381242
https://bugs.kde.org/show_bug.cgi?id=396177 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421376] Krita hiccups while painting every few seconds
https://bugs.kde.org/show_bug.cgi?id=421376 --- Comment #7 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.
[krita] [Bug 438419] Reference images aren't visible on opening a .kra file
https://bugs.kde.org/show_bug.cgi?id=438419 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436396] System Tray popup inappropriately appears in the center of the panel
https://bugs.kde.org/show_bug.cgi?id=436396 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 438886] Godot MIME icon doesn't appear to be working
https://bugs.kde.org/show_bug.cgi?id=438886 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 439097] Sometimes when I minimize a fullscreen window and maximize it again,then it just freezes
https://bugs.kde.org/show_bug.cgi?id=439097 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440782] the color selector freeze all the time, it is useless, i have to work with the color codes
https://bugs.kde.org/show_bug.cgi?id=440782 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 439796] YOUTUBE VIDEOS AND VLC DO NOT LOAD WHEN LMMS AND ROSEGARDEN IS RUNNING
https://bugs.kde.org/show_bug.cgi?id=439796 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 426464] Transparent Plasma themes are missing transparency in Wayland session with proprietary NVIDIA driver
https://bugs.kde.org/show_bug.cgi?id=426464 walktmp+s3...@gmail.com changed: What|Removed |Added CC||walktmp+s3...@gmail.com --- Comment #11 from walktmp+s3...@gmail.com --- Konsole and panels drawn by kwin have working transparency so plasmashell is evidently doing something wrong here. mpv and chromium require setting opengl-es=yes and use-gl=desktop respectively otherwise both render a an empty window no clue if this is related. Also see http://download.nvidia.com/XFree86/Linux-x86_64/470.42.01/README/xwayland.html -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 439327] Elisa doesn't not run after installation on Ubuntu 20.0.4
https://bugs.kde.org/show_bug.cgi?id=439327 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 439301] Open the Spectacle screenshot tool in openSUSE Tumbleweed 20210626 to screenshot a selection of the screen only for it to crash.
https://bugs.kde.org/show_bug.cgi?id=439301 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 439333] Infinite Notification Crash
https://bugs.kde.org/show_bug.cgi?id=439333 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439012] Magic wand tool not working. Selection deleted when attempting to invert selection
https://bugs.kde.org/show_bug.cgi?id=439012 --- Comment #4 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.
[Discover] [Bug 440373] Discover crash
https://bugs.kde.org/show_bug.cgi?id=440373 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439613] Task Manager does not show some applications under Wayland
https://bugs.kde.org/show_bug.cgi?id=439613 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #9 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440367] Kwin crashes and titlebars disappear
https://bugs.kde.org/show_bug.cgi?id=440367 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 440635] Scam detector is confused by links created by KMail itself
https://bugs.kde.org/show_bug.cgi?id=440635 --- Comment #8 from Laurent Montel --- (In reply to Thiago Macieira from comment #7) > > It was a bug created from a specific url found long time ago: > > " > > > "href=\"http://g-ecx.images-amazon.com/images/G/01/barcodes/blank003. > > jpg%5CnUse\">http://g-ecx.images-amazon.com/images/G/01/barcodes/blank003. > > jpg/nUse" > > > > => I fixed it and now all autotest works. > > This one should have triggered the warning, because it isn't the same URL. > You may want to do the backslash replacement only on the path component > instead of the whole URL, if this case is still important. yep it warns and it's ok in my patch. Perhaps I need to replace only in path component indeed. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 406338] No print preview available
https://bugs.kde.org/show_bug.cgi?id=406338 Ralf Habacker changed: What|Removed |Added Latest Commit|https://commits.kde.org/kmy |https://invent.kde.org/offi |money/0dd809ab050c558a158a5 |ce/kmymoney/commit/664363de |37ee568e4b8c689fcb8 |006838ccca96e0542dde56c5bac ||daf1c Version Fixed In|4.8.5 |5.2.0 --- Comment #6 from Ralf Habacker --- Git commit 664363de006838ccca96e0542dde56c5bacdaf1c by Ralf Habacker. Committed on 13/08/2021 at 05:54. Pushed by habacker into branch 'master-print-preview-406338'. Add print preview support to reports and home view FIXED-IN:5.2.0 M +2-0kmymoney/kmymoney.cpp M +1-0kmymoney/menus/menuenums.h M +1-1kmymoney/misc/kmm_printer.h M +12 -0kmymoney/plugins/views/reports/kreportsview.cpp M +1-0kmymoney/plugins/views/reports/kreportsview.h M +13 -0kmymoney/plugins/views/reports/kreportsview_p.h M +19 -0kmymoney/views/khomeview.cpp M +1-0kmymoney/views/khomeview.h M +1-0kmymoney/views/kmymoneyview.cpp https://invent.kde.org/office/kmymoney/commit/664363de006838ccca96e0542dde56c5bacdaf1c -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 440895] Breeze Dark/Breeze Light Plasma Style broke after installing and using some themes
https://bugs.kde.org/show_bug.cgi?id=440895 --- Comment #3 from strangequark --- (In reply to Nate Graham from comment #2) > WhiteSur-dark is the culprit. To fix this, delete the following folder: > ~/.local/share/plasma/desktoptheme/default > > Please report this to the developer. > > *** This bug has been marked as a duplicate of bug 439661 *** Thanks! -- You are receiving this mail because: You are watching all bug changes.
[Mangonel] [Bug 440871] Opening the Application Menu causes the Plasma Wayland session to crash
https://bugs.kde.org/show_bug.cgi?id=440871 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #3 from Nate Graham --- Are you really using Mangonel, and not Kickoff or some other menu? Also, can you please attach a backtrace of the crash? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 434004] Scrollbar and last row flicker when details sidebar is resized
https://bugs.kde.org/show_bug.cgi?id=434004 David Edmundson changed: What|Removed |Added CC||noaha...@gmail.com Assignee|ksysguard-b...@kde.org |notm...@gmail.com Product|plasma-systemmonitor|frameworks-qqc2-desktop-sty ||le Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 440669] System monitor crash on start
https://bugs.kde.org/show_bug.cgi?id=440669 David Redondo changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-systemmonitor/-/c ||ommit/955948e28f2bb4c6551d7 ||a6662e1d5527b3d8e9b Status|REPORTED|RESOLVED Version Fixed In||5.22 Resolution|--- |FIXED CC||k...@david-redondo.de --- Comment #1 from David Redondo --- Fixed in PLasma 5.22 already -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439990] Updating filters make them not working anymore
https://bugs.kde.org/show_bug.cgi?id=439990 Halla Rempt changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/39de844d6 ||8165affccb92e8d053143c3fecc ||bf38 Resolution|--- |FIXED --- Comment #5 from Halla Rempt --- Git commit 39de844d68165affccb92e8d053143c3feccbf38 by Halla Rempt, on behalf of L. E. Segovia. Committed on 12/08/2021 at 13:30. Pushed by rempt into branch 'master'. GMic: update to 2.9.8 This update rolls all existing updates into a single patch and integrates the following new changes: - Update the plugin to the new GMic-Qt API (while also ignoring it, because to implement the plugin architecture it needs to run within our QCoreApplication) - Add support for compiling under MSVC (this includes support for FFTW3, LTO, Control Flow Guard, the MinGW stack size increase, and a fix to the CreateThread callback signature in GMic) - Add support for Android (future proof) - Make FFTW3 a truly optional library (the GMic-Qt toggle is a dud at present, this patch fixes it) - Increase the minimum on-launch update timeout to 60s (as soon as you have some ping, the update will spuriously fail) - Restore compatibility with stock GMic-Qt settings (previously, due to an oversight on my part, it wrote them willy-nilly in the Krita namespace) It also adds new defines that allow to disable the following: - Dark Theme mode - Internet access by default - GMic-Qt's own i18n management, thus respecting the host app's language - All updates altogether M +1-13rdparty_plugins/CMakeLists.txt A +503 -03rdparty_plugins/ext_gmic/0001-Add-Krita-native-plugin.patch D +0-516 3rdparty_plugins/ext_gmic/0001-First-working-version-of-the-GMic-Qt-Krita-native-pl.patch A +289 -03rdparty_plugins/ext_gmic/0002-Add-support-for-MSVC.patch D +0-290 3rdparty_plugins/ext_gmic/0002-Remove-shared-segment-infrastructure.patch A +179 -03rdparty_plugins/ext_gmic/0003-Add-Android-support.patch D +0-170 3rdparty_plugins/ext_gmic/0003-Refactor-into-a-completely-Krita-native-plugin.patch D +0-33 3rdparty_plugins/ext_gmic/0004-Enable-all-input-modes-for-Krita-plugin.patch A +41 -03rdparty_plugins/ext_gmic/0004-Make-FFTW3-truly-optional.patch R +25 -25 3rdparty_plugins/ext_gmic/0005-Disable-GMic-Qt-s-own-theming-for-Krita.patch [from: 3rdparty_plugins/ext_gmic/0007-Disable-GMic-Qt-s-own-theming-for-Krita.patch - 065% similarity] D +0-82 3rdparty_plugins/ext_gmic/0005-Update-function-signatures-to-2.9.6.patch R +32 -32 3rdparty_plugins/ext_gmic/0006-Add-flag-to-disable-internet-access-by-default.patch [from: 3rdparty_plugins/ext_gmic/0008-Add-flag-to-disable-internet-access-by-default.patch - 051% similarity] D +0-186 3rdparty_plugins/ext_gmic/0006-Add-support-for-MSVC.patch R +8-8 3rdparty_plugins/ext_gmic/0007-Increase-on-launch-update-timeout-to-60s.patch [from: 3rdparty_plugins/ext_gmic/0009-Increase-on-launch-update-timeout-to-60s.patch - 055% similarity] A +66 -0 3rdparty_plugins/ext_gmic/0008-Enable-respecting-host-application-language.patch A +186 -0 3rdparty_plugins/ext_gmic/0009-Respect-settings-location-for-hosted-builds.patch A +132 -0 3rdparty_plugins/ext_gmic/0010-Disable-Internet-updates-in-Krita.patch M +15 -34 3rdparty_plugins/ext_gmic/CMakeLists.txt M +14 -19 plugins/extensions/qmic/gmic.h M +40 -48 plugins/extensions/qmic/kis_input_output_mapper.cpp M +5-5plugins/extensions/qmic/kis_qmic_interface.cpp https://invent.kde.org/graphics/krita/commit/39de844d68165affccb92e8d053143c3feccbf38 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 336369] Lock screen: power actions (sleep, shut down, restart) are missing
https://bugs.kde.org/show_bug.cgi?id=336369 --- Comment #45 from Krystof Jelinek --- (In reply to Nate Graham from comment #44) > That's an old argument that nobody still holds. This is going to happen > eventually. At the minimum, it's a requirement for Plasma Mobile, and if we > do it there, we might as well do it for Plasma Desktop too. I am pretty confident that quite a lot of people still hold it, and again I ask: how does it improve security? What is going to happen eventually? If you are talking about hiding the power options before logging in then again: you can turn off any device by holding down the power button (which might harm the hardware, it's an emergency poweroff), and hopefully, it will remain this way. You should be able to turn any device off when needed, and if you don't want your computer to do that, then you could at least hide the power settings from the GUI - but solving it by disabling it for everyone is the worst way possible. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 336369] Lock screen: power actions (sleep, shut down, restart) are missing
https://bugs.kde.org/show_bug.cgi?id=336369 --- Comment #46 from Nate Graham --- I mean the requested feature of showing power actions on the lock screen is going to get implemented eventually. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440832] Latte crashes after boot from autostart
https://bugs.kde.org/show_bug.cgi?id=440832 --- Comment #5 from Jeff Hodd --- Created attachment 140663 --> https://bugs.kde.org/attachment.cgi?id=140663=edit Screenshot after login First of 3 screenshots. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 440800] Import of credot card transaction with invalid Payee
https://bugs.kde.org/show_bug.cgi?id=440800 George changed: What|Removed |Added Summary|Import of credot card |Import of credot card |transaction with invalid|transaction with invalid |merchant|Payee -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 440800] Import of credot card transaction with invalid merchant
https://bugs.kde.org/show_bug.cgi?id=440800 George changed: What|Removed |Added Platform|Mint (Debian based) |Mint (Ubuntu based) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 440635] Scam detector is confused by links created by KMail itself
https://bugs.kde.org/show_bug.cgi?id=440635 Thiago Macieira changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Thiago Macieira --- I can file this as a separate bug report but here's another link. You'll probably get a notification from KMail that the bugzilla email is a scam too. https://www.google.com/search?q=%5C The details window will say that link points to 'https://www.google.com/search?q=/', which is incorrect. It does not. Neither the status bar nor the actual link when opened in the browser suffered the backslash-to-forwardslash transformation. You're incorrectly passing the full, decoded URL through some path clean routine (QDir::cleanPath?). There are at least two mistakes there. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 440898] New: Settings for file picker (tree view, preview, etc.) are not remembered (in Firefox and other apps)
https://bugs.kde.org/show_bug.cgi?id=440898 Bug ID: 440898 Summary: Settings for file picker (tree view, preview, etc.) are not remembered (in Firefox and other apps) Product: xdg-desktop-portal-kde Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: simon.pfei...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open Firefox... 2. Save a file choose the "tree view" 3. Close the save-file-dialog 4. Open save-file-dialog again OBSERVED RESULT Open dialog again and it defaults to the default view EXPECTED RESULT Retain setting SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 34, Plasma 5.22.4 (available in About System) KDE Plasma Version: Plasma 5.22.4 KDE Frameworks Version: 5.83 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440832] Latte crashes after boot from autostart
https://bugs.kde.org/show_bug.cgi?id=440832 --- Comment #9 from Michail Vourlakos --- (In reply to Jeff Hodd from comment #8) > BTW, this is not resolved or fixed. I see the same issue with your master > code base, so whatever the issue is, it's still there. > > I had a similar issue a few months ago with plasma, and it turned out the > plasma developer who helped out found that components were being started > before the corona startup was complete. Same issue here perhaps? Open a new topic, with details etc. The topic about the crash is fixed. Your topic is different. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440812] Document corruption: Cannot be saved anymore when color palette is embedded into document
https://bugs.kde.org/show_bug.cgi?id=440812 --- Comment #15 from Halla Rempt --- the big question now is... Are we going to make a 4.4.8... -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 440893] False positive "uninitialzied value" error on memeory allocated with new[]
https://bugs.kde.org/show_bug.cgi?id=440893 --- Comment #3 from Julian Seward --- > It's strange that in my case the data block is always filled with 0's > (abort() is never called), I'm using gcc 8.5.0 and c++17. The Linux kernel is obliged to zero out all memory pages it gives to a process, since not doing so would be a massive security hole. That's quite possibly what you're observing. > Just for my information is there a reason why valgrind only complained > about the first element of the array being uninitialized, and not the > rest of the array? Because all of those accesses will have the same stack trace, and Memcheck will only show the first one. Use -v if you want per-stack-trace error counts. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440763] Krita 5.0.0 prealpha bug : Unexpected pen pressure failure
https://bugs.kde.org/show_bug.cgi?id=440763 Halla Rempt changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #4 from Halla Rempt --- Krita CANNOT detect that, since it's the driver that stops sending tablet events, probably because its context for the krita process got corrupted. A tablet driver keeps data about running applications, and that data can get cleared away, or corrupted, and then it's possible that the driver cannot recreate that data, but all the same, Krita does not get any indication of that state. It just doesn't get tablet events anymore, but that's all. And PLEASE do not EVER AGAIN change the status of a bug report. Only developers should do that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 336369] Lock screen: power actions (sleep, shut down, restart) are missing
https://bugs.kde.org/show_bug.cgi?id=336369 David Redondo changed: What|Removed |Added CC||krystof...@gmail.com --- Comment #42 from David Redondo --- *** Bug 440897 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 439071] Okular print: cannot stretch smaller pages to bigger paper format
https://bugs.kde.org/show_bug.cgi?id=439071 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Nate Graham --- I asked because you have to, and then it works. :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 336369] Lock screen: power actions (sleep, shut down, restart) are missing
https://bugs.kde.org/show_bug.cgi?id=336369 --- Comment #43 from Krystof Jelinek --- (In reply to Kai Uwe Broulik from comment #6) > We removed the shutdown option and the like due to security reasons, so it > doesn't make sense to add a suspend option, I suppose? Why? How does that improve security? If I am literally next to the computer, then I can force a complete shutdown by holding down the power button. This does not make any sense... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439128] Cannot save a resource with the same name/filename as a deactivatede resource
https://bugs.kde.org/show_bug.cgi?id=439128 Halla Rempt changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/5f4f6a27b ||91b52967df12fc3c94a36b57a4c ||6e8c --- Comment #8 from Halla Rempt --- Git commit 5f4f6a27b91b52967df12fc3c94a36b57a4c6e8c by Halla Rempt. Committed on 12/08/2021 at 14:13. Pushed by rempt into branch 'rempt/version_deleted_resources'. Make it possible to save a resource over a deleted resource This creates a new version of a previously deactived resource when adding a resource with the same md5, filename or name. M +1-0libs/resources/KisResourceCacheDb.cpp M +4-0libs/resources/KisResourceLocator.cpp M +17 -3libs/resources/KisResourceModel.cpp M +11 -3libs/resources/KisResourceModel.h M +11 -0libs/resources/KoResource.cpp M +4-0libs/resources/KoResource.h M +16 -27 libs/ui/widgets/kis_workspace_chooser.cpp M +0-3libs/ui/widgets/kis_workspace_chooser.h https://invent.kde.org/graphics/krita/commit/5f4f6a27b91b52967df12fc3c94a36b57a4c6e8c -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 392877] balooctl index command with large number of files corrupts db
https://bugs.kde.org/show_bug.cgi?id=392877 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #5 from Nate Graham --- Cool. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 403153] ComboBox entry popup is not resized to delegate width
https://bugs.kde.org/show_bug.cgi?id=403153 --- Comment #20 from Nate Graham --- I'm sure all of them are still reproducible, since this is fixed only in Qt 6 and we're still using Qt 5. :) -- You are receiving this mail because: You are watching all bug changes.
[palapeli] [Bug 433403] Preview puzzle images are not shown
https://bugs.kde.org/show_bug.cgi?id=433403 --- Comment #12 from Marcel --- Thank you very much for your work. I was using the discover program on fedora and had the misconception that from the two versions viewed, that both were installed. Instead, only the fedora version was. After some fiddling, I was able to install the flatpak version too which kept viewing the preview images after several restarts. Now, something different. The new version seems to have a different location of the config, can I have the previous puzzles set up back, or is that config too different to do that. Also, I am missing the irregular puzzle cutter which I also loved to use. (pointers to other issues perhaps, or plugins) Anyways, so far so good. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434004] Scrollbar and last row flicker when details sidebar is resized
https://bugs.kde.org/show_bug.cgi?id=434004 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- Relevant: 15:39:49.077 ?libQt5Qml.so.5?|?libQt5Qml.so.5?|QQmlEnginePrivate::warning file:///home/opt/kde5/lib/qml/QtQuick/Controls.2/org.kde.desktop/ScrollView.qml:99:27: QML ScrollBar: Binding loop detected for property "visible" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439332] Ghost windows and popups
https://bugs.kde.org/show_bug.cgi?id=439332 --- Comment #8 from Matt W --- I'd like to follow up that I feel that while the ghosting bug is still going on, there are a lot of X issues I'm also facing. I can't say it's related, but very well could be. One of the issues I'm seeing is when I detach a chrome tab, and drag it, it goes SUPER slow and drags slowly. Then it snaps back weird. I also highlight text, click and pull it it also goes slowly. These are bugs that I'm not sure how to report, or if I should report, but odd behaviors that have recently (like last month or 2) started happening. Curious if others see weird issues too? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 403153] ComboBox entry popup is not resized to delegate width
https://bugs.kde.org/show_bug.cgi?id=403153 --- Comment #21 from Patrick Silva --- Can the fix be backported to KDE Qt? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 440876] an even easier way to test new Plasma versions
https://bugs.kde.org/show_bug.cgi?id=440876 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org --- Comment #2 from tagwer...@innerjoin.org --- Have a look at running your test systems as virtual machines. Check out KVM. You then have freedom to mix and match your systems and be sure that one does not corrupt/influence another. You also you get the options to do snapshots before changes to allow roll backs and to make complete backup copies of systems. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 387797] Scrollviews automatically scroll up or down when you hover over a partially-visible list item
https://bugs.kde.org/show_bug.cgi?id=387797 Lyubomir changed: What|Removed |Added CC||liubomi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 253678] Unprecise error message when creating symlink on partition that does not support that
https://bugs.kde.org/show_bug.cgi?id=253678 Ahmad Samir changed: What|Removed |Added Version Fixed In||5.86 Latest Commit||https://invent.kde.org/fram ||eworks/kio/commit/c27196acc ||33243db1da847a43a63f3442b26 ||1688 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Ahmad Samir --- Git commit c27196acc33243db1da847a43a63f3442b261688 by Ahmad Samir. Committed on 12/08/2021 at 09:59. Pushed by ahmadsamir into branch 'master'. kio_file: detect failure to create symlinks due to filesystem support The symlink() system call sets errno to EPERM (operation not permitted) when the filesystem doesn't support symlinks; check the filesystem type so that we can show a better error message. FIXED-IN: 5.86 M +26 -7src/ioslaves/file/file_unix.cpp https://invent.kde.org/frameworks/kio/commit/c27196acc33243db1da847a43a63f3442b261688 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440763] Krita 5.0.0 prealpha bug : Unexpected pen pressure failure
https://bugs.kde.org/show_bug.cgi?id=440763 --- Comment #3 from stephen --- *re-installed my tablet driver...* -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 440866] In kinfocenter "Graphics Platform" should be translated to "Plateforme graphique"
https://bugs.kde.org/show_bug.cgi?id=440866 --- Comment #2 from Méven Car --- Merci -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439128] Cannot save a resource with the same name/filename as a deactivatede resource
https://bugs.kde.org/show_bug.cgi?id=439128 Halla Rempt changed: What|Removed |Added Status|REPORTED|ASSIGNED Summary|Can't name brush after a|Cannot save a resource with |deleted brush. |the same name/filename as a ||deactivatede resource Ever confirmed|0 |1 --- Comment #7 from Halla Rempt --- I think we should simply re-activate the resource and save the "new" brush as the latest version of that resource. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 440893] False positive "uninitialzied value" error on memeory allocated with new[]
https://bugs.kde.org/show_bug.cgi?id=440893 Tom Hughes changed: What|Removed |Added Status|REPORTED|RESOLVED CC||t...@compton.nu Resolution|--- |NOT A BUG --- Comment #1 from Tom Hughes --- I think you are confused... When there is no initializer the array new operator in C++ performs default initialization of each member of the array (https://en.cppreference.com/w/cpp/language/new#Construction). Default initialization for POD types like char does nothing (https://en.cppreference.com/w/cpp/language/default_initialization). Therefore that memory is uninitialized and valgrind is correct. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440897] New: Can not turn off computer - missing the shutdown, restart and other buttons and physical button does not do anything
https://bugs.kde.org/show_bug.cgi?id=440897 Bug ID: 440897 Summary: Can not turn off computer - missing the shutdown, restart and other buttons and physical button does not do anything Product: kscreenlocker Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: krystof...@gmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY When you boot the system up without any session running, you have the power control panel available at the login screen, and you can turn off the PC using physical buttons. However when you "lock" the session, those buttons disappear and you can't turn off the PC or even restart it. I can't see any options in the settings regarding this problem. STEPS TO REPRODUCE 1. Lock a session 2. Shutdown/sleep/restart buttons are not present and you can't turn off the PC by any other way (such as hardware buttons) OBSERVED RESULT You can't turn off a computer from a lockscreen. EXPECTED RESULT I expect to be able to do so SOFTWARE/OS VERSIONS KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440897] Can not turn off computer - missing the shutdown, restart and other buttons and physical button does not do anything
https://bugs.kde.org/show_bug.cgi?id=440897 David Redondo changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@david-redondo.de Resolution|--- |DUPLICATE --- Comment #1 from David Redondo --- *** This bug has been marked as a duplicate of bug 336369 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 336369] Lock screen: power actions (sleep, shut down, restart) are missing
https://bugs.kde.org/show_bug.cgi?id=336369 --- Comment #44 from Nate Graham --- That's an old argument that nobody still holds. This is going to happen eventually. At the minimum, it's a requirement for Plasma Mobile, and if we do it there, we might as well do it for Plasma Desktop too. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440832] Latte crashes after boot from autostart
https://bugs.kde.org/show_bug.cgi?id=440832 --- Comment #4 from Jeff Hodd --- [root@bslxenvy64 latte]# cd /home/jghodd/.config/autostart [root@bslxenvy64 autostart]# ll total 8 -rw--- 1 jghodd jghodd 590 Jun 16 2020 kdock-thunderbird.desktop -rw-r--r-- 1 jghodd jghodd 301 Sep 17 2020 megasync.desktop lrwxrwxrwx 1 jghodd jghodd 50 Aug 9 16:52 org.kde.latte-dock.desktop -> /usr/share/applications/org.kde.latte-dock.desktop Don't need to reset my autostart. I use a symlink, so it's always pointing to whatever was most recently installed. The only time I found a double-start was if I logged out and logged back in without killing the latte-dock process before doing so. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440832] Latte crashes after boot from autostart
https://bugs.kde.org/show_bug.cgi?id=440832 --- Comment #6 from Jeff Hodd --- Created attachment 140664 --> https://bugs.kde.org/attachment.cgi?id=140664=edit 2 of 3 - locate and kill single instance of latte-dock. Desktop restored Shows the terminal where I locate the latte-dock process and kill it, showing how it clears the desktop. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440832] Latte crashes after boot from autostart
https://bugs.kde.org/show_bug.cgi?id=440832 --- Comment #7 from Jeff Hodd --- Created attachment 140665 --> https://bugs.kde.org/attachment.cgi?id=140665=edit 3 of 3 - same session - restart of latte-dock from sys menu Restart latte-dock from the system menu. It seems as if instead of a double-start, it may be starting too early. I only ever find one running instance. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440812] Document corruption: Cannot be saved anymore when color palette is embedded into document
https://bugs.kde.org/show_bug.cgi?id=440812 --- Comment #14 from Nico --- (In reply to Halla Rempt from comment #13) > Git commit 6551d98964c03978c0b9ce926e61498ac901f26e by Halla Rempt. > Committed on 12/08/2021 at 09:45. > Pushed by rempt into branch 'krita/4.3'. > > Fix loading and saving of document palettes > > The palettes weren't marked as global on loading, so they were > never saved, and the default return value for saving palettes > was "false" -- so if there were palettes, but they were not global > saving always failed. > > M +1-0plugins/impex/libkra/kis_kra_loader.cpp > M +5-4plugins/impex/libkra/kis_kra_saver.cpp > > https://invent.kde.org/graphics/krita/commit/ > 6551d98964c03978c0b9ce926e61498ac901f26e Awesome, thank you :) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 440800] Import of credot card transaction with invalid Payee
https://bugs.kde.org/show_bug.cgi?id=440800 --- Comment #1 from George --- Merchant should say Payee -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440832] Latte crashes after boot from autostart
https://bugs.kde.org/show_bug.cgi?id=440832 --- Comment #8 from Jeff Hodd --- BTW, this is not resolved or fixed. I see the same issue with your master code base, so whatever the issue is, it's still there. I had a similar issue a few months ago with plasma, and it turned out the plasma developer who helped out found that components were being started before the corona startup was complete. Same issue here perhaps? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 440800] Import of credit card transaction with invalid Payee
https://bugs.kde.org/show_bug.cgi?id=440800 Jack changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO Summary|Import of credot card |Import of credit card |transaction with invalid|transaction with invalid |Payee |Payee --- Comment #2 from Jack --- 5.0.8 was released January 2020. Is it possible for you to upgrade to a newer version? You can also try using an AppImage (https://kmymoney.org/appimage.html) I am not aware off any way to tell KMM to leave the Payee blank, but there are settings reagarding which OFX filed to use as the source for the Payee. However, you are correct that it should not create a payee from data unlrelated to the transaction. One additional thought - please look at the payee info for "Zelle Transfer Conf# T0BN438LM" and see if it has matching enabled, and if anything in the new transaction happens to meet the matching criteria. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 403153] ComboBox entry popup is not resized to delegate width
https://bugs.kde.org/show_bug.cgi?id=403153 --- Comment #22 from Nate Graham --- Not sure, but that would be a question for someone else. :) Maybe ask on kde-de...@kde.org? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440896] New: KisPaintOpDelegate loads dependent resources
https://bugs.kde.org/show_bug.cgi?id=440896 Bug ID: 440896 Summary: KisPaintOpDelegate loads dependent resources Product: krita Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: ha...@valdyas.org Target Milestone: --- Insteead of checking the database -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440896] KisPaintOpDelegate loads dependent resources
https://bugs.kde.org/show_bug.cgi?id=440896 Halla Rempt changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 Assignee|krita-bugs-n...@kde.org |ha...@valdyas.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440890] New: Preset marked as dirty when switching between stylus pen tip and eraser tip
https://bugs.kde.org/show_bug.cgi?id=440890 Bug ID: 440890 Summary: Preset marked as dirty when switching between stylus pen tip and eraser tip Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Tools/Freehand Assignee: krita-bugs-n...@kde.org Reporter: al...@alvinhc.com CC: dimul...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Activate pen tip end and select "c) Pencil-1 Hard"; if the preset is marked dirty, reload it from the brush editor 2. Activate eraser tip end and select "a) Eraser Circle"; if the preset is marked dirty, reload it from the brush editor 3. Switch between pen tip and eraser tip 4. One of the preset may be marked as dirty -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 429140] Latte Dock is unclickable when PLASMA_USE_QT_SCALING is set to 1
https://bugs.kde.org/show_bug.cgi?id=429140 --- Comment #3 from Michail Vourlakos --- I wont even look at it because Plasma is not really providing an official way to support screen scaling under X11. You can ask them if you want, the use of PLASMA_USE_QT_SCALING=1 is not advised and supported by Plasma team. So for scaling related issues under x11 first Plasma should define which way is officially supported in order for Latte afterwards to follow. Until then all scaling issues under x11 are considered irrelevant. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 439071] Okular print: cannot stretch smaller pages to bigger paper format
https://bugs.kde.org/show_bug.cgi?id=439071 Germano Massullo changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Germano Massullo --- (In reply to Nate Graham from comment #1) > Did you check the "Force Rasterization" checkbox? If not, does it work if > you do? I did not check and at the moment I don't have an A3 printer easily accessible. I have to schedule a test and go to an office that has it -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 440895] Breeze Dark/Breeze Light Plasma Style broke after installing and using some themes
https://bugs.kde.org/show_bug.cgi?id=440895 --- Comment #1 from strangequark --- Created attachment 140662 --> https://bugs.kde.org/attachment.cgi?id=140662=edit Easier to see with Breeze Light, because it's completely broken here. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 439478] Menu/tooltip background is transparent
https://bugs.kde.org/show_bug.cgi?id=439478 Manuel Geißer changed: What|Removed |Added Resolution|WAITINGFORINFO |LATER -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 439478] Menu/tooltip background is transparent
https://bugs.kde.org/show_bug.cgi?id=439478 --- Comment #13 from Manuel Geißer --- The issue still persists after today's kde software updates. I don't have the remotest idea what could be the cause :( -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 440893] False positive "uninitialzied value" error on memeory allocated with new[]
https://bugs.kde.org/show_bug.cgi?id=440893 --- Comment #2 from Bob Stafford --- Hi Tom, Thanks for the reply. Apologies if you got this twice, I think my first attempt to send failed because I sent it from a different variant of my company email address. It seems you're right I think this section in the page you mentioned is the key part "Default initialization of non-class variables with automatic and dynamic storage duration produces objects with indeterminate values (static and thread-local objects get zero initialized)" It's strange that in my case the data block is always filled with 0's (abort() is never called), I'm using gcc 8.5.0 and c++17. I guess there's nothing to say the compiler (or library) cannot zero the data if it wants to but I'll stop relying on that behaviour. Just for my information is there a reason why valgrind only complained about the first element of the array being uninitialized, and not the rest of the array? Cheers Bob S. On 8/12/21 6:02 AM, Tom Hughes wrote: > https://bugs.kde.org/show_bug.cgi?id=440893 > > Tom Hughes changed: > > What|Removed |Added > > Status|REPORTED|RESOLVED > CC||t...@compton.nu > Resolution|--- |NOT A BUG > > --- Comment #1 from Tom Hughes --- > I think you are confused... > > When there is no initializer the array new operator in C++ performs default > initialization of each member of the array > (https://en.cppreference.com/w/cpp/language/new#Construction). > > Default initialization for POD types like char does nothing > (https://en.cppreference.com/w/cpp/language/default_initialization). > > Therefore that memory is uninitialized and valgrind is correct. > -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 420939] Baloo purge not completing
https://bugs.kde.org/show_bug.cgi?id=420939 --- Comment #52 from tagwer...@innerjoin.org --- It's been a long journey with this bug but I think we've finally got there... >From your information (and in case someone else is seeing similar issues), there's a mergerfs configuration option "use_ino": https://github.com/trapexit/mergerfs#inodecalc That means that mergerfs provides calculated (but stable) inode numbers to things, like baloo, that need them. I can also say that the tangled mimetypes you found with video/mp2t and audio/vnd.dts.hd (Bug 440632) has been pinned down and I think sorted. It's likely to take a while though before it gets to peoples' desktops... -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 429140] Latte Dock is unclickable when PLASMA_USE_QT_SCALING is set to 1
https://bugs.kde.org/show_bug.cgi?id=429140 --- Comment #1 from Artur --- Created attachment 140660 --> https://bugs.kde.org/attachment.cgi?id=140660=edit New crash information added by DrKonqi latte-dock (0.10.0) using Qt 5.15.2 - What I was doing when the application crashed: The application crashes during the system start up. - Unusual behavior I noticed: - Custom settings of the application: I have set "PLASMA_USE_QT_SCALING=1" environment variable. This variable changes behaviour of the application. The application was crashing with the official ArchLinux package. I have compiled it my self to get useful backtraces. The bug still present. In addition I am using Window AppMenu (v0.7.1) and Active Window Control (v1.1) widgets. -- Backtrace (Reduced): #4 QString::QString (other=..., this=this@entry=0x7ffdc61b0010) at /usr/include/qt/QtCore/qstring.h:1093 #5 Latte::Layout::AbstractLayout::name (this=0x0) at /usr/src/debug/latte-dock-0.10.0/app/layout/abstractlayout.cpp:204 #6 0x558f461e1ca7 in Latte::Layouts::Synchronizer::currentLayoutsNames (this=) at /usr/src/debug/latte-dock-0.10.0/app/layouts/synchronizer.cpp:202 #7 0x558f461ca653 in Latte::Layouts::Manager::currentLayoutsNames (this=) at /usr/src/debug/latte-dock-0.10.0/app/layouts/manager.cpp:155 #8 0x558f46227940 in Latte::Settings::Controller::Layouts::initLayouts (this=this@entry=0x558f480525f0) at /usr/src/debug/latte-dock-0.10.0/app/settings/settingsdialog/layoutscontroller.cpp:582 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 429140] Latte Dock is unclickable when PLASMA_USE_QT_SCALING is set to 1
https://bugs.kde.org/show_bug.cgi?id=429140 Artur changed: What|Removed |Added CC||art.and...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440891] New: Preset marked as dirty on startup
https://bugs.kde.org/show_bug.cgi?id=440891 Bug ID: 440891 Summary: Preset marked as dirty on startup Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Tools/Freehand Assignee: krita-bugs-n...@kde.org Reporter: al...@alvinhc.com CC: dimul...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Select "c) Pencil-1 Hard"; if the preset is marked dirty, reload it from the brush editor 2. Close Krita and relaunch it 3. Open a file 4. Preset is marked as diry (opacity set to 100%) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440812] Document corruption: Cannot be saved anymore when color palette is embedded into document
https://bugs.kde.org/show_bug.cgi?id=440812 Halla Rempt changed: What|Removed |Added Keywords||regression --- Comment #12 from Halla Rempt --- This is a regression in Krita 4.4.5, probably from commit a7458f988ba563b12ef371969c31fba4620e1bca Author: Agata Cacko Date: Fri Jun 4 20:26:01 2021 +0200 Add more checks on saving to kra (no new strings) Before this commit, lots of functions that returns bool signalizing an error had their return value ignored. This commit adds additional checking of the return value. Cherry-picked from c29b9b5668, but edited to not contain any new user strings. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 440885] Edit Current Profile opens the editing of a new profile when attempting to edit the Default profile
https://bugs.kde.org/show_bug.cgi?id=440885 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com --- Comment #1 from Ahmad Samir --- That's working as intended. The "default"/built-in profile is special, it can't be edited (because it's created on demand from C++ code, i.e. it doesn't have a .profile file on disk). And the name "Default" is reserved. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440812] Document corruption: Cannot be saved anymore when color palette is embedded into document
https://bugs.kde.org/show_bug.cgi?id=440812 Halla Rempt changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/6551d9896 ||4c03978c0b9ce926e61498ac901 ||f26e Status|ASSIGNED|RESOLVED --- Comment #13 from Halla Rempt --- Git commit 6551d98964c03978c0b9ce926e61498ac901f26e by Halla Rempt. Committed on 12/08/2021 at 09:45. Pushed by rempt into branch 'krita/4.3'. Fix loading and saving of document palettes The palettes weren't marked as global on loading, so they were never saved, and the default return value for saving palettes was "false" -- so if there were palettes, but they were not global saving always failed. M +1-0plugins/impex/libkra/kis_kra_loader.cpp M +5-4plugins/impex/libkra/kis_kra_saver.cpp https://invent.kde.org/graphics/krita/commit/6551d98964c03978c0b9ce926e61498ac901f26e -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 440892] I am a Software developer .We provide best security services in usa.
https://bugs.kde.org/show_bug.cgi?id=440892 Jan Paul Batrina changed: What|Removed |Added Version|5.17.3 |unspecified Assignee|kdepim-b...@kde.org |n...@kde.org Component|ICal dir resource |Spam Product|Akonadi |Spam -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 387618] words less than 3 letters are ignored
https://bugs.kde.org/show_bug.cgi?id=387618 davidblunkett changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #10 from davidblunkett --- Struck this again, the key I need to search for is "L4" - it will have one hit out of 1800 emails. I could understand not searching live as you type until x or more characters but refusing to search at all is nuts -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440894] QtCreator pop-ups steal focus and are moved to top of window stack under wayland
https://bugs.kde.org/show_bug.cgi?id=440894 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |LATER CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Yeah :( This is something that will be addressed when we can rely on clients supporting explicit window activation, till then there isn't much we can do. Pragmatically for QtCreator this means Qt6. As a rubbish workaround you can run qtcreator --platform xcb -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440894] QtCreator pop-ups steal focus and are moved to top of window stack under wayland
https://bugs.kde.org/show_bug.cgi?id=440894 --- Comment #2 from Knut Andre Tidemann --- Well, thanks for the workaround at least! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 432077] Konsole flashes when it's closed by pressing Ctrl-D
https://bugs.kde.org/show_bug.cgi?id=432077 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/utilities/konsole/-/merge_requests/456 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 432077] Konsole flashes when it's closed by pressing Ctrl-D
https://bugs.kde.org/show_bug.cgi?id=432077 Ahmad Samir changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Version Fixed In||21.12 Latest Commit||https://invent.kde.org/util ||ities/konsole/commit/bbec72 ||250d080ce286a6762fb9beee4b6 ||e7981c9 --- Comment #3 from Ahmad Samir --- Git commit bbec72250d080ce286a6762fb9beee4b6e7981c9 by Ahmad Samir. Committed on 12/08/2021 at 12:25. Pushed by tcanabrava into branch 'master'. Prevent window "flashing" when closing the last session There are two scenarios when closing a window: A) clicking the close button on the title bar (or Ctrl+Shift+Q): ~MainWindow() ~ViewManager() ~TabbedViewContainer() ~TerminalDisplay() ~Session() B) closing the last session/tab in a window: SessionController::sessionFinished() ~Session() ~TerminalDisplay() ~TabbedViewContainer() ~MainWindow() ~ViewManager() the issue with the second case is that the TerminalDisplay is torn down first, which exposes the TabbedViewContainer widget, the latter has the same Qt::Window colour as the system colour scheme window background colour, if you're using a dark terminal colour scheme and a light-coloured system colour scheme, you could see some "flashing" when you close the last session with e.g. Ctrl+D. To fix this, in sessionFinished() check if TabbedViewContainer::count() is 1 (i.e. closing last tab/session), and emit the empty() signal in that case, which is connected to MainwWindow::close(), then the order of tear down becomes: SessionController::sessionFinished() ~Session() ~MainWindow() ~ViewManager() ~TabbedViewContainer() ~TerminalDisplay() FIXED-IN: 21.12 M +1-1src/MainWindow.cpp M +7-0src/ViewManager.cpp https://invent.kde.org/utilities/konsole/commit/bbec72250d080ce286a6762fb9beee4b6e7981c9 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 372464] Simple editing/annotation features (drawing Arrows / Text / Highlighting) after doing screenshot
https://bugs.kde.org/show_bug.cgi?id=372464 Johannes K. changed: What|Removed |Added CC||joker777vs@gmail.com --- Comment #15 from Johannes K. --- Hi, is there a way that it also saves the annotation settings so I don't have to change them every time I do another screenshot? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 440893] New: False positive "uninitialzied value" error on memeory allocated with new[]
https://bugs.kde.org/show_bug.cgi?id=440893 Bug ID: 440893 Summary: False positive "uninitialzied value" error on memeory allocated with new[] Product: valgrind Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: bobst...@eecradar.com Target Milestone: --- SUMMARY I've seen this with versions 3.16.1 (Opensuse RPMs) and 3.17.0 (built from source) (Note these versions are not an option in the bugtracking system) Using this code snippet int prod_size=256; char *p1 = new char[prod_size]; for(int i=0;i
[krita] [Bug 440763] Krita 5.0.0 prealpha bug : Unexpected pen pressure failure
https://bugs.kde.org/show_bug.cgi?id=440763 stephen changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REPORTED --- Comment #2 from stephen --- (In reply to Halla Rempt from comment #1) > Sorry, not a Krita bug. Krita does not contain any code whatsoever that > handles tablet api's directly. If something breaks it's either a local > problem, and OS problem or a driver problem, but it cannot be a bug in > Krita's code. Please, if it's not a bug, then at least, allow Krita to re-detect the tablet without restarting itself. This issue nevertheless is real and annoying. The fact that I reinstalled my tablet didn't fix it. Once again, this issue is only happening with Krita 5 build, not the 4.x ones. Do something if it can help. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440889] New: [Animation] "Drop Frames" button tooltip not translated
https://bugs.kde.org/show_bug.cgi?id=440889 Bug ID: 440889 Summary: [Animation] "Drop Frames" button tooltip not translated Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Translation Assignee: krita-bugs-n...@kde.org Reporter: al...@alvinhc.com Target Milestone: --- The string "Drop Frames Enable to preserve playback timing." is extracted to the POT template and translated in the target language, but the tool button tooltip on the animation/curve dockers shows the English text. You can test with the `x-test` pseudo-localization by setting the `LANGUAGE` env. (nightly dc559d37af) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 429140] Latte Dock is unclickable when PLASMA_USE_QT_SCALING is set to 1
https://bugs.kde.org/show_bug.cgi?id=429140 --- Comment #2 from Artur --- Yes, as well as previous reporter noted Latte Dock does not react to mouse input after manual restart after start up crash. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440766] Service menu actions are very slow when used with large numbers of files
https://bugs.kde.org/show_bug.cgi?id=440766 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440894] New: QtCreator pop-ups steal focus and are moved to top of window stack under wayland
https://bugs.kde.org/show_bug.cgi?id=440894 Bug ID: 440894 Summary: QtCreator pop-ups steal focus and are moved to top of window stack under wayland Product: kwin Version: 5.22.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: knut.tidem...@gmail.com Target Milestone: --- SUMMARY When changing a file opened in Qt Creator from another application, such as the terminal, a pop-up window will appear and steal the focus, asking to reload the contents of the file. This steals both keyboard focus and is put in front of all other windows. This really messes up with any ongoing typing. This might happen with other applications that have this behavior as well, but I've only really noticed it with Qt Creator. The behavior changed from plasma 5.21 to 5.22 as the popup was kept in the background in 5.21. Even setting focus stealing prevention for the Qt Creator application to 'Extreme' does not seem to resolve the issue. STEPS TO REPRODUCE 1. Open a file in Qt Creator 2. Change this file from the terminal OBSERVED RESULT Qt Creator and its pop-up notification steal focus and move to the front of the stack. EXPECTED RESULT The popup is opened in the background and does not steal keyboard focus. SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 440895] New: Breeze Dark/Breeze Light Plasma Style broke after installing and using some themes
https://bugs.kde.org/show_bug.cgi?id=440895 Bug ID: 440895 Summary: Breeze Dark/Breeze Light Plasma Style broke after installing and using some themes Product: systemsettings Version: 5.22.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_desktoptheme Assignee: plasma-b...@kde.org Reporter: random1123581...@protonmail.com Target Milestone: --- Created attachment 140661 --> https://bugs.kde.org/attachment.cgi?id=140661=edit On applying Breeze, the theme changes but it's not the Breeze theme. SUMMARY I was installing and applying a couple of themes, and now the Breeze (both Light and Dark) Plasma Styles appear to be broken for me. Attached video for the problem STEPS TO REPRODUCE 1. Install themes from the Get New Stuff window (I installed 'WhiteSur-dark') 2. Apply the theme 3. Apply Breeze theme OBSERVED RESULT Breeze theme should be reverted like it was before installing any other themes EXPECTED RESULT A different theme applies that is definitely not Breeze. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.22 User (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I think some parts of the Whitesur theme somehow got mixed with the Breeze theme? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 437612] Kio doesn't recognize tg:// URI for Telegram
https://bugs.kde.org/show_bug.cgi?id=437612 --- Comment #2 from Marzal --- In my setup works, in case you need some testing. Arch Linux + Telegram binary with Firefox or Chromium ¿Is this issue a dup of https://bugs.kde.org/show_bug.cgi?id=439132? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440899] Latte is not working properly after desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 --- Comment #4 from Jeff Hodd --- Created attachment 140667 --> https://bugs.kde.org/attachment.cgi?id=140667=edit Screenshot of systemsettings->Startup and Shutdown->Autostart -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 440747] Restore maximized full height window result in its previous height
https://bugs.kde.org/show_bug.cgi?id=440747 --- Comment #7 from Nate Graham --- Is Firefox running in CSD mode, or SSD mode? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 440748] Option in the file picker to open image
https://bugs.kde.org/show_bug.cgi?id=440748 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #3 from Nate Graham --- All right, so basically what you want is macOS's Quick Look functionality, but built into the file browser (as theirs is). -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440899] Latte is not working properly after desktop startup
https://bugs.kde.org/show_bug.cgi?id=440899 --- Comment #20 from Jeff Hodd --- Created attachment 140669 --> https://bugs.kde.org/attachment.cgi?id=140669=edit Screenshot of restarted dock with latte spacer -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 336369] Lock screen: power actions (sleep, shut down, restart) are missing
https://bugs.kde.org/show_bug.cgi?id=336369 --- Comment #48 from Krystof Jelinek --- (In reply to Nate Graham from comment #46) > I mean the requested feature of showing power actions on the lock screen is > going to get implemented eventually. Oh, sorry about that... there are some people that would probably want that removed as well, so that's the reasoning before my reaction and I apologize for it. -- You are receiving this mail because: You are watching all bug changes.
