[plasmashell] [Bug 500710] popup on hover obscures focussed GUI in other apps in "icons and text panel"
https://bugs.kde.org/show_bug.cgi?id=500710 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 480527] Cannot edit bookmarks in folders via context menu
https://bugs.kde.org/show_bug.cgi?id=480527 --- Comment #4 from Bug Janitor Service --- 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read 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.
[konqueror] [Bug 31987] bookmark toolbar folder dropdown
https://bugs.kde.org/show_bug.cgi?id=31987 --- Comment #6 from Bug Janitor Service --- 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read 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.
[systemsettings] [Bug 501810] QML ComboBox doesn't render ListElement in kcm_kwinrules.
https://bugs.kde.org/show_bug.cgi?id=501810 --- Comment #6 from Roke Julian Lockhart Beedell <4wy78...@rokejulianlockhart.addy.io> --- Created attachment 179615 --> https://bugs.kde.org/attachment.cgi?id=179615&action=edit A Screenshot of "Window class (application)" with All ListElement Selected -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 500597] A shortcut trigger of "ctrl+r" can be assigned but does not work
https://bugs.kde.org/show_bug.cgi?id=500597 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 from Bug Janitor Service --- 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500441] Having autolock and suspend at the same time breaks lockscreen (can't be unlocked)
https://bugs.kde.org/show_bug.cgi?id=500441 --- Comment #11 from Bug Janitor Service --- 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read 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.
[kate] [Bug 501478] Kate's inbuilt terminal leaves visual glitches while resizing
https://bugs.kde.org/show_bug.cgi?id=501478 --- Comment #6 from Bug Janitor Service --- 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read 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.
[KAccounts] [Bug 502179] Can't connect Nextcloud with Online Accounts due to wrong URI
https://bugs.kde.org/show_bug.cgi?id=502179 Denys Madureira changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Denys Madureira --- I discovered the error. It was on my server. For some reason, this was affecting only Online Accounts. I had, on config.php, 'overwritewebroot' => '/', changing it to 'overwritewebroot' => '', fixed the issue. -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 502179] New: Can't connect Nextcloud with Online Accounts due to wrong URI
https://bugs.kde.org/show_bug.cgi?id=502179 Bug ID: 502179 Summary: Can't connect Nextcloud with Online Accounts due to wrong URI Classification: Frameworks and Libraries Product: KAccounts Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: deny...@zoho.com CC: ad...@leinir.dk, natalie_clar...@yahoo.de Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY When trying to connect a Nextcloud account through Online Accounts, we can't pass from the "Grant Access" step, it keeps loading forever. Checking the log in my Nextcloud instance I can see that this is due a typo in the URI. I have this on the log: "Requested uri (/remote.phpp/webdav) is out of base uri (/remote.php/webdav/)" As we can see, there is an additional "p" (in the end of remote.php) on the URI that KDE tries to access. STEPS TO REPRODUCE 1. Go to Online Accounts and try to add Nextcloud integration 2. Log in and try to grant access 3. Grant access stay loading forever and you receive this message on the Nextcloud log OBSERVED RESULT Grant access stay loading forever and we can't add Nextcloud account EXPECTED RESULT We are able to grant access and integrate our Nextcloud account through Online Accounts SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20250321 KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 Kernel Version: 6.13.7-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 31,2 GiB of RAM Graphics Processor: AMD Radeon RX 6400 ADDITIONAL INFORMATION I can grant access to the Nextcloud desktop app with no problem, the same for the android apps and all other apps/websites. This error only happens with the Online Accounts. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 502181] New: Visual bug displaying application in focus and crashes if you try to close before letting the apps load
https://bugs.kde.org/show_bug.cgi?id=502181 Bug ID: 502181 Summary: Visual bug displaying application in focus and crashes if you try to close before letting the apps load Classification: Applications Product: Discover Version: 5.27.5 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: buttfart...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 179848 --> https://bugs.kde.org/attachment.cgi?id=179848&action=edit A screenshot showing the output of "(gdb) backtrace" within the terminal (Wiki doesn't explain if there is an output file for gdb so I am attatching this screenshot as it is the only output). SUMMARY When opening Discover, the app will display the app in focus for around ten-ish seconds then load into the app store like usual. If you attempt to close Discover while the separate app in focus is still on-screen, it will stop responding and prompt you to terminate the app. If you choose not to and wait, it will close by itself after a few seconds. STEPS TO REPRODUCE 1. Boot up regularly 2. Use system regularly (I'm unsure as to what causes this issue but the apps that I use regularly include Youtube Music Desktop App, Librewolf, Libreoffice Writer, qBittorrent, the terminal, Visual Studio Code, Steam, and Counter Strike 2. It took about an hour for it to cook(?)) 3. Open discover 4. If you want it to crash, attempt to close discover while the app in focus is on screen OBSERVED RESULT Discover having visual bug + crashing when attempting to close EXPECTED RESULT Discover immediately loading into the store SOFTWARE/OS VERSIONS Linux/KDE Plasma: MX Linux 23 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Sometimes this bug will also happen alongside the desktop shortcuts refusing to open when clicked on -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 502181] Visual bug displaying application in focus and crashes if you try to close before letting the apps load
https://bugs.kde.org/show_bug.cgi?id=502181 Bug Janitor Service changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! However Plasma 5.27.5 is no longer eligible for support or maintenance from KDE; supported versions are 5.27. (LTS), and 6.3 (non-LTS) or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. If you need support for Plasma 5.27.5, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE. If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 502181] Visual bug displaying application in focus and crashes if you try to close before letting the apps load
https://bugs.kde.org/show_bug.cgi?id=502181 Bug Janitor Service changed: What|Removed |Added Severity|minor |crash -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 502183] New: Context Menu Closes When Hovering "Move To"
https://bugs.kde.org/show_bug.cgi?id=502183 Bug ID: 502183 Summary: Context Menu Closes When Hovering "Move To" Classification: Applications Product: kmail2 Version: 6.3.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: correlan...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY Title, not sure I can explain it any more. STEPS TO REPRODUCE 1. Right click an email in my inbox 2. Move your mouse down to try and hover over "Move message to" OBSERVED RESULT The context menu instantly closes after flashing the secondary context menu that should pop up EXPECTED RESULT A further context menu pops up to give me options for where to move it to SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Nobara Linux 41 KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 502183] Context Menu Closes When Hovering "Move To"
https://bugs.kde.org/show_bug.cgi?id=502183 Alexander changed: What|Removed |Added CC||correlan...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 502185] Screen glitch on second monitor
https://bugs.kde.org/show_bug.cgi?id=502185 --- Comment #1 from Sven Grewe --- *Each monitor is connected to one monitor. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 502185] Screen glitch on second monitor
https://bugs.kde.org/show_bug.cgi?id=502185 Sven Grewe changed: What|Removed |Added Keywords||regression, wayland-only -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498341] Clipboard text is sometimes non-pasteable
https://bugs.kde.org/show_bug.cgi?id=498341 --- Comment #23 from Xavier Corredor Llano --- For me this happens with non-KDE Wayland applications like: Libreoffice, Pycharm, VirtualBox, Firefox (all with Wayland enabled) and not always, it's just random, very annoying. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422166] Large number of files can be displayed in scientific notation in copying notification
https://bugs.kde.org/show_bug.cgi?id=422166 Nate Graham changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/cf206f9d6714ad6d3aff4d2bd ||d600ab00f8aee0c Resolution|--- |FIXED Version Fixed In||6.4.0 --- Comment #7 from Nate Graham --- Git commit cf206f9d6714ad6d3aff4d2bdd600ab00f8aee0c by Nate Graham. Committed on 29/03/2025 at 21:35. Pushed by ngraham into branch 'master'. applets/notifications: never use scientific notation for large numbers Normal people don't know how to read it. FIXED-IN: 6.4.0 M +6-3 applets/notifications/package/contents/ui/components/JobDetails.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/cf206f9d6714ad6d3aff4d2bdd600ab00f8aee0c -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 502186] New: time is wrong on different time zones
https://bugs.kde.org/show_bug.cgi?id=502186 Bug ID: 502186 Summary: time is wrong on different time zones Classification: Plasma Product: plasmashell Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tesafil...@googlemail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 179849 --> https://bugs.kde.org/attachment.cgi?id=179849&action=edit erroneous Tokyo time Hi there, to be perfectly honest, I'm not sure if this bug is related to the Plasma desktop environment, Linux, GNU, or chrony, but since I couldn't find any information about this on other plattforms, this is most likely the best spot. General description: When I use a time zone different from my local time, the clock shows the wrong time. My case: My system time zone is Berlin, my additional time zone is Tokyo. I guess, this is an issue with the time switch to summer time, since this wasn't erroneous before today. When I change the system time zone to Tokyo, the time is correct. System: Lenovo Yoga 7 14ASP9 83HN OS: openSUSE Tumbleweed Version: 20250328 Kernel: 6.13.8.1 Plasma: 6.3.3 Wayland Greetings -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 464034] OpenTimelineIO not working on macOS
https://bugs.kde.org/show_bug.cgi?id=464034 Julius Künzel changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/mult ||imedia/kdenlive/-/merge_req ||uests/561 Version Fixed In||25.04.0 Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 502187] New: KDE + Wayland global/system scaling system breaks applications ability to read monitors resolution.
https://bugs.kde.org/show_bug.cgi?id=502187 Bug ID: 502187 Summary: KDE + Wayland global/system scaling system breaks applications ability to read monitors resolution. Classification: Plasma Product: kwin Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: jtchristian1...@pm.me Target Milestone: --- Created attachment 179851 --> https://bugs.kde.org/attachment.cgi?id=179851&action=edit hardware information report SUMMARY Changing scaling from 100% to anything else in Wayland will cause games (and possibly other 3d application?) to not be able to recognize the resolution of the monitor.For example setting scale to 180% will cause games to think the monitors resolution is 1280x1024 in Final Fantasy XIV.I've tried many games and they all react exactly the same, the only solution is to set scaling to 100% (default) BEFORE launching a game.. but this means i need to basically stick my face right in front of my 4k monitor to be able to see anything just so i can launch a game, then when im done playing the game set it back to preferred scale. on advice from the RebornOS discord team, i tried switching to X11 display compositor and set the global scale to 180 and 200% and both options had no effect on an applications ability to read the monitors proper resolution. Appears to be a problem with KDE and Wayland specifically. in display configuration changed system scales or applications scales has zero effect on this problem.unfortunately switching back to X11 is not an option because it has no adaptive sync support. STEPS TO REPRODUCE 1. System Settings 2. Display Configuration 3. Change 'Scale' to any number than 100% 4. Launch game (or possibly other 3d application) and attempt to change resolution. OBSERVED RESULT EXPECTED RESULT No effect by global/system scaling in applications such as game rendering it unable to read monitors resolution. SOFTWARE/OS VERSIONS see attached file. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481997] Welcome Center appears after every boot after updating to KDE Plasma 6
https://bugs.kde.org/show_bug.cgi?id=481997 --- Comment #12 from Kevin Guertin --- I just want to add that I had this issue, too, in KDE Neon, and I only just upgraded from 5.27 a week ago, so it's still occurring on upgrade. In my situation, my upgrade from 5.27 to 6.3 was borked, so I installed KDE Neon from scratch, but never formatted any of my drives or mount points during the install so that I wouldn't lose anything at all. I just installed KDE Neon on top of everything. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 502182] Konsole's blur background lingers after the window being shaded (X11)
https://bugs.kde.org/show_bug.cgi?id=502182 deanrih changed: What|Removed |Added Summary|Konsole's blur background |Konsole's blur background |still present after the |lingers after the window |window being shade (X11)|being shaded (X11) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 502182] Konsole's blur background still present after the window being shade (X11)
https://bugs.kde.org/show_bug.cgi?id=502182 deanrih changed: What|Removed |Added Summary|Konsole's blurr background |Konsole's blur background |still present after the |still present after the |window being shade (X11)|window being shade (X11) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 502173] digikam - white screen
https://bugs.kde.org/show_bug.cgi?id=502173 --- Comment #2 from Maik Qualmann --- https://download.kde.org/stable/digikam/8.6.0/digiKam-8.6.0-Qt6-Win64.exe.mirrorlist Maik -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 485661] Kmail popup windows closes when trying to copy or move message to folder
https://bugs.kde.org/show_bug.cgi?id=485661 Colin J Thomson changed: What|Removed |Added CC||correlan...@gmail.com --- Comment #26 from Colin J Thomson --- *** Bug 502183 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422166] Large number of files can be displayed in scientific notation in copying notification
https://bugs.kde.org/show_bug.cgi?id=422166 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #6 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5357 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 460597] OpenTimelineIO export fails if file extension isn't specified in file name
https://bugs.kde.org/show_bug.cgi?id=460597 Julius Künzel changed: What|Removed |Added CC||bil...@gmail.com --- Comment #6 from Julius Künzel --- *** Bug 495963 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 502180] New: SVG mime type missing in desktop file
https://bugs.kde.org/show_bug.cgi?id=502180 Bug ID: 502180 Summary: SVG mime type missing in desktop file Classification: Applications Product: gwenview Version: 24.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: con...@ftml.net Target Milestone: --- There is no image/svg+xml in MimeType, hence dolphin tries to open SVG images with something else, usually with Chrome or Firefox. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 502162] In history view, icon overlaps text from notification with no word breaks (e.g. long URLs)
https://bugs.kde.org/show_bug.cgi?id=502162 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5358 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 502191] New: Discover is slower on Plasma then Cosmic for some reason
https://bugs.kde.org/show_bug.cgi?id=502191
Bug ID: 502191
Summary: Discover is slower on Plasma then Cosmic for some
reason
Classification: Applications
Product: Discover
Version: 6.3.3
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: discover
Assignee: plasma-b...@kde.org
Reporter: pollu...@proton.me
CC: aleix...@kde.org
Target Milestone: ---
Created attachment 179856
--> https://bugs.kde.org/attachment.cgi?id=179856&action=edit
discover slow on kde plasma
SUMMARY
Recently after coming back to using my pc iv noticed discover is acting slower
then usual on kde plasma, i tested on cosmic and its what it should be which is
very fast
STEPS TO REPRODUCE
1. Try to reproduce discover being slow which could be hard
2. Watch discover be slow
OBSERVED RESULT
Rlly slow that it takes minutes to load some applications just to install them
EXPECTED RESULT
Discover to be the normal speed at loading
SOFTWARE/OS VERSIONS
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Cachyos Linux
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.3
ADDITIONAL INFORMATION
libs QList("/usr/lib/qt6/plugins", "/usr/bin")
org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: false
org.kde.plasma.libdiscover: error loading "packagekit-backend" "Cannot load
library /usr/lib/qt6/plugins/discover/packagekit-backend.so:
libpackagekitqt6.so.1: cannot open shared object file: No such file or
directory"
QJsonObject({"IID":"org.kde.muon.AbstractResourcesBackendFactory","archlevel":4,"className":"PackageKitBackendFactory","debug":false,"version":395264})
qrc:/qt/qml/org/kde/discover/qml/BrowsingPage.qml:17:1: QML BrowsingPage:
Created graphical object was not placed in the graphics scene.
KNSCore::ResultsStream(0x55e5c4607430) fetching SearchRequest(id: 0,searchTerm:
"",categories: QList(),filter: KNSCore::Filter::Updates,page: -1,pageSize: 100)
KNSCore::ResultsStream(0x55e5c4607430) loading entries from provider
KNSCore::AtticaProvider(0x55e5bf3b1ca0)
KNSCore::ResultsStream(0x55e5c340e630) fetching SearchRequest(id: 1,searchTerm:
"",categories: QList(),filter: KNSCore::Filter::Updates,page: -1,pageSize: 100)
KNSCore::ResultsStream(0x55e5c340e630) loading entries from provider
KNSCore::AtticaProvider(0x55e5c3377150)
KNSCore::ResultsStream(0x55e5c4608210) fetching SearchRequest(id: 2,searchTerm:
"",categories: QList(),filter: KNSCore::Filter::Updates,page: -1,pageSize: 100)
KNSCore::ResultsStream(0x55e5c4608210) loading entries from provider
KNSCore::AtticaProvider(0x55e5c33c6fa0)
KNSCore::ResultsStream(0x55e5c4608730) fetching SearchRequest(id: 3,searchTerm:
"",categories: QList(),filter: KNSCore::Filter::Updates,page: -1,pageSize: 100)
KNSCore::ResultsStream(0x55e5c4608730) loading entries from provider
KNSCore::AtticaProvider(0x55e5c33cd0d0)
KNSCore::ResultsStream(0x55e5c4608c50) fetching SearchRequest(id: 4,searchTerm:
"",categories: QList(),filter: KNSCore::Filter::Updates,page: -1,pageSize: 100)
KNSCore::ResultsStream(0x55e5c4608c50) loading entries from provider
KNSCore::AtticaProvider(0x55e5c33d1e00)
KNSCore::ResultsStream(0x55e5c46091a0) fetching SearchRequest(id: 5,searchTerm:
"",categories: QList(),filter: KNSCore::Filter::Updates,page: -1,pageSize: 100)
KNSCore::ResultsStream(0x55e5c46091a0) loading entries from provider
KNSCore::AtticaProvider(0x55e5c33d6a60)
KNSCore::ResultsStream(0x55e5c4609730) fetching SearchRequest(id: 6,searchTerm:
"",categories: QList(),filter: KNSCore::Filter::Updates,page: -1,pageSize: 100)
KNSCore::ResultsStream(0x55e5c4609730) loading entries from provider
KNSCore::AtticaProvider(0x55e5c33db810)
KNSCore::ResultsStream(0x55e5c4609ca0) fetching SearchRequest(id: 7,searchTerm:
"",categories: QList(),filter: KNSCore::Filter::Updates,page: -1,pageSize: 100)
KNSCore::ResultsStream(0x55e5c4609ca0) loading entries from provider
KNSCore::AtticaProvider(0x55e5c33e06b0)
KNSCore::ResultsStream(0x55e5c460a210) fetching SearchRequest(id: 8,searchTerm:
"",categories: QList(),filter: KNSCore::Filter::Updates,page: -1,pageSize: 100)
KNSCore::ResultsStream(0x55e5c460a210) loading entries from provider
KNSCore::AtticaProvider(0x55e5c33e5460)
KNSCore::ResultsStream(0x55e5c460a780) fetching SearchRequest(id: 9,searchTerm:
"",categories: QList(),filter: KNSCore::Filter::Updates,page: -1,pageSize: 100)
KNSCore::ResultsStream(0x55e5c460a780) loading entries from provider
KNSCore::AtticaProvider(0x55e5c33ea350)
KNSCore::ResultsStream(0x55e5c460acf0) fetching SearchRequest(id:
10,searchTerm: "",categories: QList(),filter: KNSCore::Filter::Updates,page:
-1,pageSize: 100)
KNSCore::ResultsStream(0x55e5c460acf0) loading entries from provider
KNSCore::AtticaProvider(0x55e5c33ef240)
KNSCore::ResultsStream(0x55e5c460b260) fetching SearchRequest(id:
[plasma-systemmonitor] [Bug 502193] New: Jagged lines in graphs on Nvidia
https://bugs.kde.org/show_bug.cgi?id=502193 Bug ID: 502193 Summary: Jagged lines in graphs on Nvidia Classification: Applications Product: plasma-systemmonitor Version: 6.3.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: nep...@pm.me CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 179858 --> https://bugs.kde.org/attachment.cgi?id=179858&action=edit Jagged lines in graphs SUMMARY Lines in graphs look jagged (e.g. on the "History" page) using an Nvidia GPU. STEPS TO REPRODUCE 0. Use an Nvidia GPU 1. Open System Monitor 2. Go to the "History" page OBSERVED RESULT The lines in the graphs look jagged. EXPECTED RESULT Lines don't look jagged but normal (like they do using AMD or Intel GPUs). SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.3 Kernel Version: 6.13.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor Memory: 30,9 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4080 SUPER Manufacturer: ASRock Product Name: X670E Steel Legend -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 502192] New: When you click Remove All Preview Zones it doesn’t mark the project as changed
https://bugs.kde.org/show_bug.cgi?id=502192 Bug ID: 502192 Summary: When you click Remove All Preview Zones it doesn’t mark the project as changed Classification: Applications Product: kdenlive Version: 24.12.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: User Interface & Miscellaneous Assignee: j...@kdenlive.org Reporter: t...@smerkin.club Target Milestone: --- SUMMARY When you click Remove All Preview Zones it doesn’t mark the project as changed. STEPS TO REPRODUCE 1. Click Remove All Preview Zones 2. Observe the preview zones were removed 3. Observe the Save icon is greyed out 4. Close and re-open the project 5. The preview zone is no longer removed OBSERVED RESULT The project is being marked as changed and the Save function is greyed out EXPECTED RESULT The project should be identified as changed after the Preview Zones were removed and hence the Save functionality should be active. SOFTWARE/OS VERSIONS Windows: 10 22H2 KDE Frameworks Version: 6.9.0 Qt Version: 6.8.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 502185] Screen glitch on a 4:3 monitor
https://bugs.kde.org/show_bug.cgi?id=502185 --- Comment #3 from Sven Grewe --- Created attachment 179853 --> https://bugs.kde.org/attachment.cgi?id=179853&action=edit Screen Glitch Video -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 502187] KDE + Wayland global/system scaling system breaks applications ability to read monitors resolution.
https://bugs.kde.org/show_bug.cgi?id=502187 --- Comment #1 from Joshua --- Created attachment 179852 --> https://bugs.kde.org/attachment.cgi?id=179852&action=edit example of bug from application: Final Fantasy XIV -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 502188] New: The lock screen (not SDDM) sometimes not responding after type password and then login
https://bugs.kde.org/show_bug.cgi?id=502188 Bug ID: 502188 Summary: The lock screen (not SDDM) sometimes not responding after type password and then login Classification: Plasma Product: plasmashell Version: master Platform: Arch Linux OS: Linux Status: REPORTED Keywords: usability Severity: normal Priority: NOR Component: Screen locking Assignee: plasma-b...@kde.org Reporter: zx...@hotmail.com CC: zx...@hotmail.com Target Milestone: 1.0 SUMMARY The KDE lock screen (not SDDM) sometimes not responding after type password and then try login STEPS TO REPRODUCE 1. In KDE menu, click `Lock` or `Leave` 2. Wake up computer, it pops out a login interface, which looks like SDDM (but slightly different so I can tell it's not SDDM) 3. Input correct password, click `>` or hit Enter OBSERVED RESULT It's not responding (I can see password placeholder added when I'm typing, but nothing works besides that and context buttons). I have to click "Switch User" to go back to the *real* SDDM, then input my password, then login. EXPECTED RESULT Successfully login SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.3.3 (issue exists for long since Plasma6) KDE Frameworks Version: 6.12.0 (issue exists for long since Plasma6) Qt Version: 6.8.2 (issue exists for long since Plasma6) ADDITIONAL INFORMATION - It is not Caps Lock (or similar keyboard thing) causing me inputting wrong password -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 486215] App crashes allways
https://bugs.kde.org/show_bug.cgi?id=486215 --- Comment #2 from Bug Janitor Service --- 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read 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 502182] New: Konsole's blurr background still present after the window being shade (X11)
https://bugs.kde.org/show_bug.cgi?id=502182 Bug ID: 502182 Summary: Konsole's blurr background still present after the window being shade (X11) Classification: Plasma Product: kwin Version: 6.3.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: deanrikrikichsanhakiki+kde...@gmail.com Target Milestone: --- SUMMARY When Konsole (KDE Terminal) being shaded (hiding the content of the window but left the title bar alone), it still leaves the blurry background rectangle intact, while other app (that has native KDE title bar/frame and can be shaded) doesn't leave anything SETTINGS > Desktop Effects >> Appearance - Background Contrast: Disabled - Blur: Enabled -- Blur strength: level 11/15 (index 10) -- Noise strength: level 01/15 (index 0) - Desaturate Unresponsive Applications: Enabled - Fading Popups: Enabled - Fall Apart: Disabled - Full Screen: Enabled - Highlight Screen Edges and Hot Corners: Enabled - Login: Enabled -- Fade to black: Disabled - Logout: Enabled - Maximize: Enabled - Mouse Mark: Disabled - Sheet: Disabled - Sliding Popups: Enabled - Thumbnail Aside, Touch Points, Translucency, Wobbly Windows: Disabled - Minimize Animation: Squash >> KWin Scripts - All Disabled >> Konsole Profile Appearance STEPS TO REPRODUCE - Blur background: Enabled - Background color transparency: 20% >> Colors & Themes - Global Theme: Breeze Dark - Application Style: Breeze - Plasma Style: Breeze - Window Decorations: Breeze 1. Open Konsole 2. Right-Click the Title Bar -> More Actions -> Shade 3. Try to move the Title Bar around now do the same with other app, such as Kate 1. Open Kate 2. Right-Click the Title Bar -> More Actions -> Shade 3. Try to move the Title Bar around OBSERVED RESULT Konsole leave a "masked" blur rectangle background where the content supposed to be, and it seems to be "Click through" and sort of "non corporeal", and if you move the title bar, it looks like it moves the "mask" around but not the blur itself, which means the blur area can be "cut off" but "non destructively" as in if you move the title bar back to the original place, the blur still encompass the entire window content rectangle While Kate, doesn't leave anything behind where the window content supposed to be EXPECTED RESULT The "blur" part should be hidden when being shaded and then come back when unshaded like what happened with Kate. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.5-2-MANJARO (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i3-8100 CPU @ 3.60GHz Memory: 31.1 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2060 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500810] get randomly black screen
https://bugs.kde.org/show_bug.cgi?id=500810 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 from Bug Janitor Service --- 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 490970] [PLASMA][KWIN][6.1.3] Crash alt-tabbing
https://bugs.kde.org/show_bug.cgi?id=490970 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #22 from Bug Janitor Service --- 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500879] Notifications from a gtk app do not have the icon of the source app anymore
https://bugs.kde.org/show_bug.cgi?id=500879 --- Comment #17 from Nate Graham --- Oh, fantastic! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 502183] Context Menu Closes When Hovering "Move To"
https://bugs.kde.org/show_bug.cgi?id=502183 Colin J Thomson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||colin.thom...@g6avk.co.uk --- Comment #1 from Colin J Thomson --- *** This bug has been marked as a duplicate of bug 485661 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 502182] Konsole's blurr background still present after the window being shade (X11)
https://bugs.kde.org/show_bug.cgi?id=502182 --- Comment #1 from Dean Rikrik Ichsan Hakiki --- Since the video attachment is too large, I upload it on third party website here, but if there's a better way to add/send attachment, please let me know https://streamable.com/tlace4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 502175] Add an option for auto-pausing all media when plugging/unplugging audio devices
https://bugs.kde.org/show_bug.cgi?id=502175 --- Comment #1 from Fernando M. Muniz --- Also it also helps users avoid sudden loudness if the device malfunctions, the audio cable is poorly connected, and other accidents. Imagine watching videos with your headphones during the night, and then you move in a way that the audio cable is disconnected and your TV speakers play it at a high volume. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 502190] New: The KDE Linux OS shows entry shows in every single search
https://bugs.kde.org/show_bug.cgi?id=502190 Bug ID: 502190 Summary: The KDE Linux OS shows entry shows in every single search Classification: Applications Product: Discover Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: KDE Linux backend Assignee: plasma-b...@kde.org Reporter: jus...@kde.org CC: aleix...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Open Discover 2. Search for teamviewer OBSERVED RESULT KDE Linux shows up as a result EXPECTED RESULT It does not Operating System: KDE Linux 202503190255 KDE Plasma Version: 6.3.80 KDE Frameworks Version: 6.13.0 Qt Version: 6.8.2 Kernel Version: 6.13.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 PRO 4750U with Radeon Graphics Memory: 32 GiB of RAM (29.1 GiB usable) Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 20Y1001SAU System Version: ThinkPad P14s Gen 1 -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 489738] Scanned image have blue background.
https://bugs.kde.org/show_bug.cgi?id=489738 --- Comment #4 from Bug Janitor Service --- 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 502192] When you click Remove All Preview Zones it doesn’t mark the project as changed
https://bugs.kde.org/show_bug.cgi?id=502192 Jean-Baptiste Mardelle changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499893] No fingerprint auth option when laptop wakes from sleep
https://bugs.kde.org/show_bug.cgi?id=499893 Jason changed: What|Removed |Added CC||rocki...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 502190] The KDE Linux OS shows entry shows in every single search
https://bugs.kde.org/show_bug.cgi?id=502190 --- Comment #1 from Justin Zobel --- Just an additional note on this, I am in the process of upgrading KDE Linux in discover, so that might come into play? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 502164] Add the ability to show Headline properties on preview thumbnails.
https://bugs.kde.org/show_bug.cgi?id=502164 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Add the ability to |Add the ability to show |customize fields shown on |Headline properties on |preview thumbnails |preview thumbnails. Component|Preview-Image |Thumbs-IconView CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 502185] Screen glitch on a 4:3 monitor
https://bugs.kde.org/show_bug.cgi?id=502185 --- Comment #2 from Sven Grewe --- The issue is still there with only the 4:3 monitor connected to the pc PS: What did I wrote previously lol. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 502186] time is wrong on different time zones
https://bugs.kde.org/show_bug.cgi?id=502186 --- Comment #1 from tesafil...@googlemail.com --- Created attachment 179850 --> https://bugs.kde.org/attachment.cgi?id=179850&action=edit correct time after changing the system time -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 502185] Screen glitch on a 4:3 monitor
https://bugs.kde.org/show_bug.cgi?id=502185 Sven Grewe changed: What|Removed |Added Summary|Screen glitch on second |Screen glitch on a 4:3 |monitor |monitor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501211] Memory leak when window leaves full-screen 8 times or more
https://bugs.kde.org/show_bug.cgi?id=501211 Nick H changed: What|Removed |Added CC||kror...@gmail.com --- Comment #5 from Nick H --- Also getting this bug. I'll add full info if that's OK because I reproduce it slightly differently. SUMMARY When playing games with external monitor connected, Kwin_Wayland increasingly uses all of the memory until system is at 100% usage and then the system locks up. STEPS TO REPRODUCE 1. Load a game with an external monitor connected (a game that uses more memory will cause system to crash quicker). 2. Watch memory keep increasing until crash. OBSERVED RESULT System memory usage increases until system locks up and must be powered off. 'kwin_wayland --replace' is the quick (messy) fix or a reboot. The problem resumes as soon as the memory is cleared if system is used with an external monitor. I have done some testing withOUT an external display in a couple of games, eg Counter-Strike 2 and have observed memory usage is normal and drops off after exiting game. EXPECTED RESULT Memory should increase somewhat while gaming and then drop off afterwards. Not expected that kwin_wayland uses so much memory but rather it should be more the game. ADDITIONAL INFO I suspect watching full screen videos contributes also (with ext. monitor) but haven't tested yet. SOFTWARE/OS VERSIONS/HARDWARE Operating System: Garuda Linux KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.3 Kernel Version: 6.13.8-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor 1: AMD Radeon Graphics Graphics Processor 2: NVIDIA GeForce RTX 3060 Laptop GPU Manufacturer: ASUSTeK COMPUTER INC. Product Name: ASUS TUF Gaming A15 FA506QM_TUF506QM System Version: 1.0 Screens: 1. built in laptop 2. AOC CQ27G4 Monitor (DP) 3. SONY BRAVIA TV (HDMI) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 502184] New: "Clip Speed" Dialog box not longer limits speed slider to slowest allowable speed
https://bugs.kde.org/show_bug.cgi?id=502184 Bug ID: 502184 Summary: "Clip Speed" Dialog box not longer limits speed slider to slowest allowable speed Classification: Applications Product: kdenlive Version: 24.12.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Timeline & Editing Assignee: j...@kdenlive.org Reporter: pe...@peterjones.ca Target Milestone: --- SUMMARY The "Clip Speed" Dialog box used to ( a few version ago) limit the speed slider to slowest allowable speed for a clip. Now instead of stopping at the slowest position, you get a "Minimum speed is " warning. In other words, it lets you select an invalid speed which is ignored when you hit OK to exit the "Clip Speed" Dialog box/ STEPS TO REPRODUCE 1. Put two clips on the timeline with a short space between them 2. Right click on the first clip and select "change speed" 3. In the "Clip Speed" Dialog box, drag the slider all the way to the left. OBSERVED RESULT A "Minimum speed is ..." error message appears. Click the OK button to exit the "Clip Speed" Dialog box produces no change to the clip under these circumstances. EXPECTED RESULT The slider should (and used to) stop at the slowest allowable speed when sliding left. Then if you Click the OK button to exit the "Clip Speed" Dialog box the clip will now exactly fill the available space that had existed between the twp clips. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 454181] Ark doesn't preview HTML files anymore
https://bugs.kde.org/show_bug.cgi?id=454181 --- Comment #13 from bj.kdede...@bkaj.org --- Another data point: Kate's Print Preview displays a blank, white page when using the Breeze Dark theme. It displays with black text on white background when using Breeze Light theme. Current details on my Debian Testing installation: - Operating System: Debian GNU/Linux 12 - KDE Plasma Version: 6.3.2 - KDE Frameworks Version: 6.11.0 - Qt Version: 6.8.2 - Kernel Version: 6.12.20-amd64 (64-bit) - Graphics Platform: Wayland - Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor - Memory: 62.7 GiB of RAM - Graphics Processor: AMD Radeon RX 6600 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 502189] New: Password required to cancel updating sysupdated upgrade
https://bugs.kde.org/show_bug.cgi?id=502189 Bug ID: 502189 Summary: Password required to cancel updating sysupdated upgrade Classification: Applications Product: Discover Version: master Platform: KDE Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: KDE Linux backend Assignee: plasma-b...@kde.org Reporter: jus...@kde.org CC: aleix...@kde.org Target Milestone: --- Created attachment 179854 --> https://bugs.kde.org/attachment.cgi?id=179854&action=edit Screenshot STEPS TO REPRODUCE 1. Start a sysupdated update e.g. KDE Linux 2. Cancel the upgrade OBSERVED RESULT Password required as in Screenshot EXPECTED RESULT Password not required SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: Operating System: KDE Linux 202503190255 KDE Plasma Version: 6.3.80 KDE Frameworks Version: 6.13.0 Qt Version: 6.8.2 Kernel Version: 6.13.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 PRO 4750U with Radeon Graphics Memory: 32 GiB of RAM (29.1 GiB usable) Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 20Y1001SAU System Version: ThinkPad P14s Gen 1 -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 210526] Not all data is shown in the details view
https://bugs.kde.org/show_bug.cgi?id=210526 Baldrun Orv changed: What|Removed |Added Version|unspecified |6.3.2 Platform|unspecified |Manjaro --- Comment #7 from Baldrun Orv --- It has been more than Version:(using KDE 4.3.2) OS:Linux Problem: A person's details view doesn't show all the data which is provided in the editing dialogue. For me as a user it is inconvenient having to go into the editing dialogue to get the missing information. Allowing the user to choose what information is given in the details view is a good idea, but unfortunately this is limited to birthday, postal addresses, e-mail addresses, phone numbers and websites. Suggestion: --- Please let the details view show all the information which is provided in the editing dialogue (including categories, privacy status, nickname, husband's or wife's name, logo, geo-data, customized entry fields, etc.). It would be a very convenient feature being able to decided for each piece of information if it is shown in the details view or not. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408001] On X11, mouse jumps on autohidden panel when xinput property "Coordinate Transformation Matrix" is changed
https://bugs.kde.org/show_bug.cgi?id=408001 andre+...@lianse.eu changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408001] On X11, mouse jumps on autohidden panel when xinput property "Coordinate Transformation Matrix" is changed
https://bugs.kde.org/show_bug.cgi?id=408001 --- Comment #5 from andre+...@lianse.eu --- It still happens with KDE Plasma 6.3 KDE Framework 6.12 It makes no difference if I have "screen edges" configured or none -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 502141] App crashes in SfdiskBackend::readSectorsUsed() while refreshing if USB flash drive needing repairs is plugged in
https://bugs.kde.org/show_bug.cgi?id=502141
--- Comment #1 from Andrius Štikonas ---
Could you see if the following patch helps?
diff --git a/src/plugins/sfdisk/sfdiskbackend.cpp
b/src/plugins/sfdisk/sfdiskbackend.cpp
index e47c4e5..2fe99dd 100644
--- a/src/plugins/sfdisk/sfdiskbackend.cpp
+++ b/src/plugins/sfdisk/sfdiskbackend.cpp
@@ -515,6 +515,8 @@ bool SfdiskBackend::updateDevicePartitionTable(Device &d,
const QJsonObject &jso
*/
void SfdiskBackend::readSectorsUsed(const Device& d, Partition& p, const
QString& mountPoint)
{
+if (p.isFileSystemNullptr())
+return;
if (!mountPoint.isEmpty() && p.fileSystem().type() !=
FileSystem::Type::LinuxSwap && p.fileSystem().type() !=
FileSystem::Type::Lvm2_PV) {
const QStorageInfo storage = QStorageInfo(mountPoint);
if (p.isMounted() && storage.isValid())
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 502149] Ugly action names can be shown to the user when notification is in history pop-up
https://bugs.kde.org/show_bug.cgi?id=502149 --- Comment #7 from Naxdy --- Telegram is Qt. I also notice the reply action is missing from Nate's screenshot, which is weird -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Implement real session save/restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 Kimiblock Moe changed: What|Removed |Added CC||kimibl...@icloud.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 496926] On X11, desktop is black/missing after resuming from suspend or hibernation until plasmashell is restarted or TTYs are switched
https://bugs.kde.org/show_bug.cgi?id=496926 akb825 changed: What|Removed |Added CC||akb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 502152] New: Gap between menu and submenu
https://bugs.kde.org/show_bug.cgi?id=502152 Bug ID: 502152 Summary: Gap between menu and submenu Classification: Plasma Product: Breeze Version: 6.3.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: plasma-b...@kde.org Reporter: vsf...@gmail.com CC: agrine...@gmail.com, uhh...@gmail.com Target Milestone: --- Created attachment 179838 --> https://bugs.kde.org/attachment.cgi?id=179838&action=edit Screenshot of Galculator submenu SUMMARY In some GTK3 applications, there is a gap between the menu and submenu, as shown in the screenshot. STEPS TO REPRODUCE 1. Open GTk3 application with menubar (e.g. Galculator). 2. Open menuitem with submenu. OBSERVED RESULT Visible gap between menu and submenu. EXPECTED RESULT Submenu should be close to menu, like in Breeze Qt. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 502149] Ugly action names can be shown to the user when notification is in history pop-up
https://bugs.kde.org/show_bug.cgi?id=502149 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5353 -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 502103] Graphics glitches with fractional scaling on Wayland when forced into XWayland mode
https://bugs.kde.org/show_bug.cgi?id=502103 Nate Graham changed: What|Removed |Added Product|kde |kolourpaint CC||n...@kde.org Version|unspecified |24.12.3 Summary|Graphics glitches with |Graphics glitches with |fractional scaling on |fractional scaling on |Wayland |Wayland when forced into ||XWayland mode Component|general |general Status|REPORTED|NEEDSINFO Assignee|unassigned-b...@kde.org |kolourpaint-support@lists.s ||ourceforge.net Resolution|--- |WAITINGFORINFO --- Comment #3 from Nate Graham --- > If i open kolourpaint in xwayland mode with "Legacy X11 applications = scaled > by the system" the bug is there This isn't really supported or recommended; why are you forcing Kolourpaint into XWayland mode? It has native Wayland support so that should be used instead. If it works as a native Wayland app, isn't that preferable to use? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 502149] Ugly action names can be shown to the user when notification is in history pop-up
https://bugs.kde.org/show_bug.cgi?id=502149 --- Comment #4 from Naxdy --- That's interesting, Telegram looks very different for me (6.3.3 with my patch manually applied). Makes me wonder if there's something that landed in master that changed something wrt how actions are displayed? Gonna compile from master and have a look at what's going on -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 502149] Ugly action names can be shown to the user when notification is in history pop-up
https://bugs.kde.org/show_bug.cgi?id=502149 --- Comment #5 from Naxdy --- Created attachment 179837 --> https://bugs.kde.org/attachment.cgi?id=179837&action=edit Telegram notification on 6.3.3 w/ manual patch -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 502146] Check box size does not change with font size
https://bugs.kde.org/show_bug.cgi?id=502146 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- I can't reproduce this here; the checkbox font always has the set size after exiting the setup dialog. Is this possibly dependent on the font type you've set? Maik -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 420682] io_pgetevents is not supported
https://bugs.kde.org/show_bug.cgi?id=420682 Paul Floyd changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Paul Floyd --- I couldn't see the syscall number for ppc. The value was wrong for arm64, now corrected. Added x86 s390 mips32, mips64 and riscv64 as well as amd64. commit 19c00de89e0fa21c62a5c0c0d1b1cc081f4ce00a (HEAD -> master, origin/master, origin/HEAD, bug420682) Author: Paul Floyd Date: Fri Mar 28 21:45:15 2025 +0100 Bug 420682 - io_pgetevents is not supported -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 502150] New: Confusing setup for "Walk through windows" option
https://bugs.kde.org/show_bug.cgi?id=502150 Bug ID: 502150 Summary: Confusing setup for "Walk through windows" option Classification: Applications Product: systemsettings Version: 5.27.12 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pe...@turbofish.cc Target Milestone: --- *** SUMMARY The "shortcuts" option allows custom shortcuts for "Walk Through Windows", but if I set one, it doesn't work as expected. Described in detail here: https://discuss.kde.org/t/behaviour-of-meta-tab/32160/3 Setting "Walk Through Windows Alternative" works just fine, but this is super confusing STEPS TO REPRODUCE 1. Open "Settings" -> "'Workspace" -> "Shortcuts" -> "KWin" 2. Leave `Alt + Tab` as the "Walk Through Windows" default binding and set a custom shortcut for `Meta + Tab` OBSERVED RESULT `Alt + Tab` will still work as expected but `Meta + Tab` will not EXPECTED RESULT They should do the same -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 502151] New: Dual display suspend timeout problem and blackscreen while playing games
https://bugs.kde.org/show_bug.cgi?id=502151 Bug ID: 502151 Summary: Dual display suspend timeout problem and blackscreen while playing games Classification: Applications Product: systemsettings Version: 6.3.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: v_josi...@aol.com CC: plasma-b...@kde.org Target Milestone: --- gpu: AMD Radeon PowerColor rx 6600 Fighter I have two displays connected LG 22" and Dell 27". LG is connected via HDMI and Dell is connected via DisplayPort to HDMI cable. Problem is with Dell monitor when enter suspend after timeout it immediately turn on again. When both displays are active suspend work but after second suspending. First both displays suspend and immediately turn on and after second timeout displays suspend again. When just LG monitor is active suspend works fine. I have tried to switch cables. When switch Dell to HDMI and LG to DisplayPort, Dell display suspend but LG turn on. Also Dell monitor have black screen when play games on Steam. If switch to LG to play, game works normally. I played games on Sway and everything was fine. STEPS TO REPRODUCE 1 . Wait for timeout to suspend displays 2. Play game on steam OBSERVED RESULT 1. Dell monitor turns off and on 2. Dell display black screen EXPECTED RESULT 1. Display sleep 2. Play game normally SOFTWARE/OS VERSIONS (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Arch/plasma-desktop-6.3.3-1 KDE Plasma Version: 6.3.3 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477817] Need to save the login credentials for Mediawiki export persistent
https://bugs.kde.org/show_bug.cgi?id=477817 kde.me...@passmail.net changed: What|Removed |Added CC||kde.me...@passmail.net --- Comment #2 from kde.me...@passmail.net --- Thank you if you implement this. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 502141] App crashes in SfdiskBackend::readSectorsUsed() while refreshing if USB flash drive needing repairs is plugged in
https://bugs.kde.org/show_bug.cgi?id=502141 --- Comment #17 from Andrius Štikonas --- (In reply to Nate Graham from comment #16) > It appears to be super duper corrupted. It won't mount read/write, only RO. > My intention was to use Partition Manager to erase it, but I can't since it > runs this never-ending fsck on launch. Hmm, I didn't expect fsck on boot but it looks like specifically for FAT fsck.vfat -n -v is used to read Used Space: https://invent.kde.org/system/kpmcore/-/blob/master/src/fs/fat12.cpp?ref_type=heads#L113 I guess the proper fix would be to add timeout option to this command. As a quick hack return -1; at the beginning of that function should unblock you. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 495540] Accuracy of the auto tag feature is very bad
https://bugs.kde.org/show_bug.cgi?id=495540 --- Comment #14 from Michael Miller --- > I've tested the 8.6.0 release for Windows and the progress with both > auto-tag and face detection is remarkable! Even though auto-tag is not 100% > reliable in terms of finding their subjects in every photo (and it is not > expected to be at this stage of the tech) the accuracy is much improved and > on par, if not better than other tools. I've tested in DigiKam mostly with > EfficientNet B7. Congratulations for the great work done. Thank you for the kind words. The team worked hard on the updates and refinements for 8.6.0. It's nice to know you're happy with the changes. Help us spread the word about digiKam. We think the improvements in the past few releases really puts digiKam at the top of the digital asset management application list. Cheers, Mike -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 502171] New: kwin-wayland panel draws/places incorrectly if QT_USE_PHYSICAL_DPI=1
https://bugs.kde.org/show_bug.cgi?id=502171 Bug ID: 502171 Summary: kwin-wayland panel draws/places incorrectly if QT_USE_PHYSICAL_DPI=1 Classification: Plasma Product: plasmashell Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: mich...@actrix.gen.nz CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY With kwin-wayland, on a 27" 4K monitor I have set QT_USE_PHYSICAL_DPI=1 causes the panel background to be incorrectly drawn, and the panel dialog to be incorrectly placed. This does not happen for kwin-x11. This is only a bug for a special use-case, which you may decide not to support. However it would be useful to support it for those trying to do print-proofing or image-proofing where 1-inch on the screen needs to match 1-inch on paper. This is mainly because many linux tools are scaling-unaware, using this variable allows them to be used without waiting for them to support the use-case (if that ever happens). If a fix is trivial, please consider it. STEPS TO REPRODUCE 1. echo 'export QT_USE_PHYSICAL_DPI=1' >> $HOME/.config/plasma-workspace/env/hidpi.sh 2. login to kwin_wayland 3. in a Konsole, check QT_USE_PHYSICAL_DPI is set. 4. Observe and use the panel and launcher (standard launcher). OBSERVED RESULT Use launcher and see where the launcher dialog is placed - it is placed way above the panel instead of close to it. Observe the background placement of the panel (might need to be a floating panel - not sure). EXPECTED RESULT Behaves like kwin-X11 with correct launcher dialog placement and correct panel shadowing. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20250319 KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 Kernel Version: 6.13.5-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1650 SUPER Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 502147] 1440p monitor does not work after nvidia driver update
https://bugs.kde.org/show_bug.cgi?id=502147
--- Comment #2 from Tyler ---
(In reply to Jack from comment #1)
> I don't have a solution, but:
> - this is clearly not a bug in khelpcenter, although I'm not sure the proper
> product, perhaps kwin?
> - please post the Xorg log - it should say something about what monitors it
> recognizes
> - what happens if you start X with only the 1440 monitor connected, rather
> then unplugging the other one after starting X
If a boot up my system with just the 1440 monitor plugged in, I just get a
blank screen after it gets past the BIOS. If I unplug my 1440 monitor and plug
in the 1080 monitor while its in this state, I also just get a blank screen.
The 1080 monitor is the only one that works properly.
[19.290] (--) NVIDIA(GPU-0): DFP-0: disconnected
[19.290] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[19.290] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[19.290] (--) NVIDIA(GPU-0):
[19.292] (--) NVIDIA(GPU-0): Dell AW2518H (DFP-1): connected
[19.292] (--) NVIDIA(GPU-0): Dell AW2518H (DFP-1): Internal DisplayPort
[19.292] (--) NVIDIA(GPU-0): Dell AW2518H (DFP-1): 2670.0 MHz maximum pixel
clock
[19.292] (--) NVIDIA(GPU-0): Dell AW2518H (DFP-1): supports NVIDIA 3D
Vision stereo.
[19.292] (--) NVIDIA(GPU-0):
[19.295] (--) NVIDIA(GPU-0): DFP-2: disconnected
[19.295] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[19.295] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[19.295] (--) NVIDIA(GPU-0):
[19.295] (--) NVIDIA(GPU-0): DFP-3: disconnected
[19.295] (--) NVIDIA(GPU-0): DFP-3: Internal DisplayPort
[19.295] (--) NVIDIA(GPU-0): DFP-3: 2670.0 MHz maximum pixel clock
[19.295] (--) NVIDIA(GPU-0):
[19.295] (--) NVIDIA(GPU-0): DFP-4: disconnected
[19.295] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[19.295] (--) NVIDIA(GPU-0): DFP-4: 165.0 MHz maximum pixel clock
[19.295] (--) NVIDIA(GPU-0):
[19.295] (--) NVIDIA(GPU-0): DFP-5: disconnected
[19.295] (--) NVIDIA(GPU-0): DFP-5: Internal DisplayPort
[19.295] (--) NVIDIA(GPU-0): DFP-5: 2670.0 MHz maximum pixel clock
[19.295] (--) NVIDIA(GPU-0):
[19.295] (--) NVIDIA(GPU-0): DFP-6: disconnected
[19.295] (--) NVIDIA(GPU-0): DFP-6: Internal TMDS
[19.295] (--) NVIDIA(GPU-0): DFP-6: 165.0 MHz maximum pixel clock
[19.295] (--) NVIDIA(GPU-0):
[19.553] (II) NVIDIA(0): Setting mode "DP-0: nvidia-auto-select @1920x1080
+0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[19.724] (II) NVIDIA(0): Setting mode "DP-0: 1920x1080_240 @1920x1080 +0+0
{ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[19.813] (--) NVIDIA(GPU-0): DFP-0: disconnected
[19.813] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[19.813] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[19.813] (--) NVIDIA(GPU-0):
[19.814] (--) NVIDIA(GPU-0): Dell AW2518H (DFP-1): connected
[19.814] (--) NVIDIA(GPU-0): Dell AW2518H (DFP-1): Internal DisplayPort
[19.815] (--) NVIDIA(GPU-0): Dell AW2518H (DFP-1): 2670.0 MHz maximum pixel
clock
[19.815] (--) NVIDIA(GPU-0): Dell AW2518H (DFP-1): supports NVIDIA 3D
Vision stereo.
[19.815] (--) NVIDIA(GPU-0):
[19.818] (--) NVIDIA(GPU-0): DFP-2: disconnected
[19.818] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[19.818] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[19.818] (--) NVIDIA(GPU-0):
[19.818] (--) NVIDIA(GPU-0): DFP-3: disconnected
[19.818] (--) NVIDIA(GPU-0): DFP-3: Internal DisplayPort
[19.818] (--) NVIDIA(GPU-0): DFP-3: 2670.0 MHz maximum pixel clock
[19.818] (--) NVIDIA(GPU-0):
[19.818] (--) NVIDIA(GPU-0): DFP-4: disconnected
[19.818] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[19.818] (--) NVIDIA(GPU-0): DFP-4: 165.0 MHz maximum pixel clock
[19.818] (--) NVIDIA(GPU-0):
[19.818] (--) NVIDIA(GPU-0): DFP-5: disconnected
[19.818] (--) NVIDIA(GPU-0): DFP-5: Internal DisplayPort
[19.818] (--) NVIDIA(GPU-0): DFP-5: 2670.0 MHz maximum pixel clock
[19.818] (--) NVIDIA(GPU-0):
[19.819] (--) NVIDIA(GPU-0): DFP-6: disconnected
[19.819] (--) NVIDIA(GPU-0): DFP-6: Internal TMDS
[19.819] (--) NVIDIA(GPU-0): DFP-6: 165.0 MHz maximum pixel clock
[19.819] (--) NVIDIA(GPU-0):
[20.722] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-0): connected
[20.722] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-0): Internal
TMDS
[20.722] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAGEAR (DFP-0): 600.0 MHz
maximum pixel clock
[20.722] (--) NVIDIA(GPU-0):
[21.511] (II) NVIDIA(0): Setting mode "DP-0: 1920x1080_240 @1920x1080
+2560+180 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[21.583] (II) NVIDIA(0): Setting mode "DP-0: 1920x1080_240 @1920x1080
+2560+180 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, HDMI-0:
nvidia-auto-select @2560x1440 +0+0 {ViewPortIn=2560x1440,
ViewPortOut=2560x1440+0+0}"
[26.895] (WW) NVIDIA: Wait for channel idle timed out
[plasmashell] [Bug 502171] kwin-wayland panel draws/places incorrectly if QT_USE_PHYSICAL_DPI=1
https://bugs.kde.org/show_bug.cgi?id=502171 --- Comment #1 from Michael Hamilton --- Created attachment 179846 --> https://bugs.kde.org/attachment.cgi?id=179846&action=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 502173] New: digikam - white screen
https://bugs.kde.org/show_bug.cgi?id=502173 Bug ID: 502173 Summary: digikam - white screen Classification: Applications Product: digikam Version: 8.6.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Albums-MainView Assignee: digikam-bugs-n...@kde.org Reporter: fe...@posteo.de Target Milestone: --- Hello, after updating to version 8.6, Digikam starts with a completely white screen. The program itself runs, as everything that can be accessed with a right-click works. But how can I get rid of the white screen so that I can access the albums again? (Windows 10 OS). Maybe it's a Qt-problem? Greetings -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 502172] New: Krita on Android doesn't allow you to select FFmpeg to export videos
https://bugs.kde.org/show_bug.cgi?id=502172 Bug ID: 502172 Summary: Krita on Android doesn't allow you to select FFmpeg to export videos Classification: Applications Product: krita Version: 5.2.9 Platform: Android OS: Android 14.x Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: fernandodruzhi...@gmail.com Target Milestone: --- I installed FFmpeg on my Galaxy Tab S9 FE+ so I could export animations from Krita 5.2.9, but I can't configure it because the Android file explorer doesn't allow access to the location where FFmpeg is installed. Furthermore, the installation process on Android was complicated and tedious. I suggest Krita comes complete on Android, with all the features out of the box without the need to install and configure additional components. Due to Google restrictions, users don't have the same level of access to the file system as on other platforms, making manual configuration of tools like FFmpeg practically impossible. I imagine FFmpeg isn't the only thing missing from Krita to make it work 100% on Android, so integrating all the features out of the box would greatly improve the experience and make Krita more competitive with other drawing and animation apps that already come ready to use without any additional configuration. Steps to reproduce: 1. Install Krita 5.2.9 on an Android tablet. 2. Install FFmpeg manually. 3. Try configuring it in Krita to export animations. 4. Android's file explorer doesn't allow you to select the correct path. Platform and version: Device: Samsung Galaxy Tab S9 FE+ OS: Android Krita version: 5.2.9 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 477914] Flatpak: OpenTimelineIO exporting fail: The 'pyaaf2<1.7,>=1.4' not found ( pkg_resources.ContextualVersionConflict: (pyaaf2 1.7.1 )
https://bugs.kde.org/show_bug.cgi?id=477914 Julius Künzel changed: What|Removed |Added CC||julius.kuen...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Julius Künzel --- *** This bug has been marked as a duplicate of bug 479162 *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 479162] OTIO is not working
https://bugs.kde.org/show_bug.cgi?id=479162 Julius Künzel changed: What|Removed |Added CC||jijili...@yandex.com --- Comment #1 from Julius Künzel --- *** Bug 477914 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 479162] OTIO is not working
https://bugs.kde.org/show_bug.cgi?id=479162 Julius Künzel changed: What|Removed |Added Resolution|--- |FIXED CC||julius.kuen...@kde.org Latest Commit||https://invent.kde.org/mult ||imedia/kdenlive/-/merge_req ||uests/561 Status|REPORTED|RESOLVED Version Fixed In||25.04.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 502173] digikam - white screen
https://bugs.kde.org/show_bug.cgi?id=502173 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- This is an OpenGL problem. I suspect you're using the Qt5 version of digiKam. Use the Qt6 version, as indicated in the filename. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 502052] Not detecting rotated (on an angle) face
https://bugs.kde.org/show_bug.cgi?id=502052 --- Comment #4 from Michael Miller --- > Yes. Apologies for misusing the "recognising" term. I should have used > "detected". Hi Craig, Can you send me a copy of the image? My email can be found here: https://invent.kde.org/graphics/digikam/-/blob/master/AUTHORS Cheers, Mike -- You are receiving this mail because: You are watching all bug changes.
[KClock] [Bug 478236] New Alarm dialogue is still in 12 hour format after enabling 24 hour format
https://bugs.kde.org/show_bug.cgi?id=478236 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- Fixed by https://invent.kde.org/utilities/kclock/-/commit/960492aeaa667636d477b5bf874c1afa04858f81 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409226] Default setting or option to show UI on only primary screen or user-specified screen
https://bugs.kde.org/show_bug.cgi?id=409226 Roke Julian Lockhart Beedell <4wy78...@rokejulianlockhart.addy.io> changed: What|Removed |Added CC||4wy78uwh@rokejulianlockhart ||.addy.io -- You are receiving this mail because: You are watching all bug changes.
[KClock] [Bug 481170] Timer countdown not centered
https://bugs.kde.org/show_bug.cgi?id=481170 Kai Uwe Broulik changed: What|Removed |Added CC||social.calamari468@slmail.m ||e --- Comment #7 from Kai Uwe Broulik --- *** Bug 487164 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 501050] Light and dark mode are not detected correctly
https://bugs.kde.org/show_bug.cgi?id=501050 Carlos De Maine changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 502149] Ugly action names can be shown to the user when notification is in history pop-up
https://bugs.kde.org/show_bug.cgi?id=502149 --- Comment #6 from Kai Uwe Broulik --- App-foo.bar sounds like a GTK action. Maybe it's a difference between GTK notifications, portal or whatever. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462274] global shortcuts do not work for non-Latin symbols of foreign keyboard layouts, if active application has active input field
https://bugs.kde.org/show_bug.cgi?id=462274 --- Comment #9 from Eugene Savitsky --- Is this a dup of https://bugs.kde.org/show_bug.cgi?id=453661? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480490] Shortcuts not working in Kodi (and Plasma, Kate, Firefox) when the keyboard layout is changed from English
https://bugs.kde.org/show_bug.cgi?id=480490 Eugene Savitsky changed: What|Removed |Added CC||eugene.savit...@gmail.com --- Comment #8 from Eugene Savitsky --- This is not an app problem, but KDE as a whole. Set CTRL-/ (the key right to left hand Shift). It will work with English, Russian, but not Estonian layout. I believe this fixing this bug should fix all other issues as well: https://bugs.kde.org/show_bug.cgi?id=453661 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 502156] New: Crash when enabling DisplayPort MST
https://bugs.kde.org/show_bug.cgi?id=502156 Bug ID: 502156 Summary: Crash when enabling DisplayPort MST Classification: Plasma Product: kwin Version: 6.3.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kde-b...@ctacke.de Target Milestone: --- Created attachment 179842 --> https://bugs.kde.org/attachment.cgi?id=179842&action=edit Crash dump text SUMMARY I have a monitor setup with two monitors connected via a Display Port daisy chain. I can enable / disable the MST option on the first monitor to treat them either as one or two monitors. STEPS TO REPRODUCE 1. Running KDE plasma session on wayland 2. Enable MST OBSERVED RESULT Wayland crash. Screen is black with underscore character in topleft corner. Opening a console session works. System recovers after disabling MST. EXPECTED RESULT I can extend my screen to both monitors. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 41 KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION I sent an automatic crash report, but I can't find it . -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424460] Notifications don't dodge Panel edit mode toolbar
https://bugs.kde.org/show_bug.cgi?id=424460 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||6.4.0 Status|CONFIRMED |RESOLVED --- Comment #2 from Nate Graham --- As of git master (soon to become Plasma 6.4) they appear to dodge the ruler properly; closing! -- You are receiving this mail because: You are watching all bug changes.
[KClock] [Bug 487164] Progress circle off center when scaling KClock horizontally
https://bugs.kde.org/show_bug.cgi?id=487164 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Kai Uwe Broulik --- *** This bug has been marked as a duplicate of bug 481170 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447744] Notifications applet when started in Latte renames Plasma Desktop global shortcuts _k_friendly_name
https://bugs.kde.org/show_bug.cgi?id=447744 Nate Graham changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED --- Comment #10 from Nate Graham --- Latte Dock has been unmaintained ant not ported to Qt 6 for years; closing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 502153] Notifications created with `notify-send` don't honor the icon
https://bugs.kde.org/show_bug.cgi?id=502153 --- Comment #1 from Naxdy --- Cannot reproduce on current master (commit 92a41d44f701c39f175a2e33aba7718e62382c32) using the command you provided - do you have any other patches applied ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 502155] New: Conflicting desktop effects configuration items cause rendering anomalies
https://bugs.kde.org/show_bug.cgi?id=502155 Bug ID: 502155 Summary: Conflicting desktop effects configuration items cause rendering anomalies Classification: Plasma Product: kwin Version: 6.3.2 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-present-windows Assignee: kwin-bugs-n...@kde.org Reporter: qingwanni...@outlook.com Target Milestone: --- Created attachment 179841 --> https://bugs.kde.org/attachment.cgi?id=179841&action=edit 异常渲染的实际表现 This bug involves setting up some proper nouns within the project. I'm going to report the bug in my native language to ensure rigor, and I'm going to ask the Chinese volunteers in the KDE community for help. 这个bug涉及到设置项目内的一些专有名词。为了保证严谨，我打算这次采用母语汇报bug，也麻烦KDE社区的中文志愿者啦，感谢！ 复线过程： 在设置->应用和窗口->窗口管理->桌面特效中，如果同时打开“气泡滑动动效”和“窗口背景虚化”，则“应用程序启动器”的动画效果会出现渲染异常（参见附件）。异常在关闭“窗口背景虚化”只保留“气泡滑动动效”后消失，动画按照预期工作。 系统摘要： Operating System: Debian GNU/Linux 13 KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.12.20-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-10210U CPU @ 1.60GHz Memory: 15.4 GiB of RAM Graphics Processor 1: Mesa Intel® UHD Graphics Graphics Processor 2: llvmpipe Manufacturer: HUAWEI Product Name: NBLB-WAX9N System Version: M1030 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475139] Notification's "dodge Plasma popups" animation easing curve does not match that of the System Tray itself
https://bugs.kde.org/show_bug.cgi?id=475139 --- Comment #1 from Nate Graham --- This has gotten worse in git master, and probably in 6.3 too; now when notifications move out of the way, there is no animation at all. -- You are receiving this mail because: You are watching all bug changes.
