[frameworks-kxmlgui] [Bug 439526] [single-process] kcommandbar displays options from other konsole windows
https://bugs.kde.org/show_bug.cgi?id=439526 Waqar Ahmed changed: What|Removed |Added Assignee|konsole-de...@kde.org |kdelibs-b...@kde.org CC||waqar@gmail.com Version|21.04.2 |5.84.0 Product|konsole |frameworks-kxmlgui Component|single-process |general -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 439526] [single-process] kcommandbar displays options from other konsole windows
https://bugs.kde.org/show_bug.cgi?id=439526 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kxmlgui/-/merge_requests/71 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 407058] KDE Plasma5 can't change resolution in VM after last update
https://bugs.kde.org/show_bug.cgi?id=407058 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439181] New systemmonitor application does not show any graphics, this also happens with objects for cpu control
https://bugs.kde.org/show_bug.cgi?id=439181 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 438956] Scroll up doesn't work
https://bugs.kde.org/show_bug.cgi?id=438956 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.
[kwin] [Bug 440316] New: Track Mouse effect doesn't work when caps lock is on (Wayland)
https://bugs.kde.org/show_bug.cgi?id=440316 Bug ID: 440316 Summary: Track Mouse effect doesn't work when caps lock is on (Wayland) Product: kwin Version: 5.22.3 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: k2squa...@icloud.com Target Milestone: --- On Wayland, the Track Mouse desktop effect animation doesn't work when caps lock is on. 1) Enable Track Mouse in desktop effects. 2) Turn on caps lock. 3) Press the default key combo to activate the Track Mouse animation: ctrl+meta. Nothing happens. 4) Turn off caps lock and press ctrl+meta again. The animation displays as expected. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210725 KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.4-1-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i7-6600U CPU @ 2.60GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 520 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439699] Tag is reset to nothing on adding or removing a storage
https://bugs.kde.org/show_bug.cgi?id=439699 Emmet O'Neill changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com CC||emmetoneill@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440315] Resource tag chooser doesn't update when active bundles change.
https://bugs.kde.org/show_bug.cgi?id=440315 Emmet O'Neill changed: What|Removed |Added Keywords||release_blocker -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440315] Resource tag chooser doesn't update when active bundles change.
https://bugs.kde.org/show_bug.cgi?id=440315 Emmet O'Neill changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440315] Resource tag chooser doesn't update when active bundles change.
https://bugs.kde.org/show_bug.cgi?id=440315 Emmet O'Neill changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440315] Resource tag chooser doesn't update when active bundles change.
https://bugs.kde.org/show_bug.cgi?id=440315 --- Comment #1 from Emmet O'Neill --- I also want to add that this bug occurs the other way around also: if you originally open the brush preset chooser with "Krita 4 Default Resources" disabled (only a single eraser visible), and then enable that bundle before selecting "Erasers" in the tag chooser combo box above, you'll still see only 1 eraser when there should be 3! I don't know this system that well yet, but it might hint that some aspect of the filtering is being cached (or not being refreshed/invalidated) when it should be. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440315] New: Resource tag chooser doesn't update when active bundles change.
https://bugs.kde.org/show_bug.cgi?id=440315 Bug ID: 440315 Summary: Resource tag chooser doesn't update when active bundles change. Product: krita Version: git master (please specify the git hash!) Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: emmetoneill@gmail.com Target Milestone: --- SUMMARY Something is wrong with filtering resources, because despite the fact that the visible set of brush presets gets smaller as you deactivate bundles while viewing ALL tags, selecting a specific tag from the tag chooser combo box causes presets from deactivated bundles to continue to show up. STEPS TO REPRODUCE 1. Open brush preset chooser while all bundles are enabled in the "storage resources" menu at the upper right. 2. Notice that there are 3 erasers among the presets. (Default) 3. Set the tag chooser combobox above to "Erasers". 4. You will see only the 3 eraser presets. 5. Open the "storage resources" menu at the upper right, and disable the "Krita 4 Default Resources" bundle. 6. Notice that there is now only 1 eraser preset now. (ALL tag) 7. Set the tag chooser combobox above to "Erasers", once again. 8. Count the number of erasers! OBSERVED RESULT 3 eraser presets are still visible, despite the fact that 2 of them exist in a bundle that is no longer active. EXPECTED RESULT Only 1 eraser preset should be visible! 2/3 of the eraser presets belong to the "Krita 4 Default Resources" bundle, which we've deactivated. But, for some reason, they are both still visible when we set the "tag chooser" combobox above to the "Erasers" tag. SOFTWARE/OS VERSIONS Fedora Linux 34 GNOME ;D -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 440314] New: Screen Brightness slider shows no percentage
https://bugs.kde.org/show_bug.cgi?id=440314 Bug ID: 440314 Summary: Screen Brightness slider shows no percentage Product: systemsettings Version: 5.22.3 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_powerdevil Assignee: plasma-b...@kde.org Reporter: coderb...@outlook.com CC: k...@privat.broulik.de Target Milestone: --- SUMMARY Screen Brightness slider shows no percentage. It's not a bug, but it's more handy to show current percentage of brightness like in the Battery and Brightness applet. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433122] Graphical glitch in headerbar and progress bar after relocating panel on X11 without Qt scaling
https://bugs.kde.org/show_bug.cgi?id=433122 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433122] Graphical glitch in headerbar and progress bar after relocating panel on X11 without Qt scaling
https://bugs.kde.org/show_bug.cgi?id=433122 Nate Graham changed: What|Removed |Added Component|Media Player|general Summary|Graphical glitch in |Graphical glitch in |headerbar and progress bar |headerbar and progress bar ||after relocating panel on ||X11 without Qt scaling Assignee|k...@privat.broulik.de |k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433122] Graphical glitch in headerbar and progress bar
https://bugs.kde.org/show_bug.cgi?id=433122 Nate Graham changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED --- Comment #6 from Nate Graham --- Re-opening because I found a way to reproduce this: 1. Use a 200% scale factor 2. Don't use Qt scaling (i.e. be on X11 and make sure PLASMA_USE_QT_SCALING=1 is not set) 3. Move your panel to a different screen edge 4. Open the System Tray 5 If it doesn't happen, move the panel to another screen edge again. Keep doing this until you see it. I can reproduce it on the first or second time. Deleting the Plasma SVG cache and restarting plasmashell fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 440095] No support for "dc cvac" and "dc cvap" on Arm64
https://bugs.kde.org/show_bug.cgi?id=440095 --- Comment #7 from kevinz --- Yes, already attached. Please help to check and review. Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440313] digiKam 7.3.0 FTBFS with Qt 5.9.5 [patch]
https://bugs.kde.org/show_bug.cgi?id=440313 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Summary|digiKam 7.3.0 FTBFS with Qt |digiKam 7.3.0 FTBFS with Qt |5.9.5 |5.9.5 [patch] -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 432995] Device Profile for Built-In Audio not applying
https://bugs.kde.org/show_bug.cgi?id=432995 c...@hotmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from c...@hotmail.com --- Upgrade to Kubuntu 21.04 seems to have solved this problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404092] Unable to set correct resolution on external display in Wayland session
https://bugs.kde.org/show_bug.cgi?id=404092 Zamundaaa changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435834] Wayland - Multi-monitor - Turning Off main desktop monitor and back on again results in main monitor losing the bottom half of the screen (THE TASKBAR) & other Anomilies
https://bugs.kde.org/show_bug.cgi?id=435834 --- Comment #6 from Zamundaaa --- Was the only thing that changed between it working and not, Plasma updating to 5.22.3 or was there a kernel update involved as well? The only information you can really provide is the wayland log again; unfortunately I'm not sure if there even is much information to get with such old drivers. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 440286] Unable to hide big ugly toolbar
https://bugs.kde.org/show_bug.cgi?id=440286 --- Comment #3 from Rajinder Yadav --- OK I finally got the right-click on menu bar (was doing it on the toolbar). The option is missing from the menu. Also right-clicking on the menu bar seem unconventional imho, should work off the toolbar you want to hide. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 440286] Unable to hide big ugly toolbar
https://bugs.kde.org/show_bug.cgi?id=440286 --- Comment #2 from Rajinder Yadav --- @David I have tired these things, the options are just not available. https://youtu.be/7qQdjZPcLvk -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 315894] Usability: Allow to edit entries in the search result list view
https://bugs.kde.org/show_bug.cgi?id=315894 gjditchfi...@acm.org changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/pim/ ||korganizer/commit/48485e4fb ||dc7b70a30972bb3ac2d529b9877 ||46aa --- Comment #4 from gjditchfi...@acm.org --- Git commit 48485e4fbdc7b70a30972bb3ac2d529b987746aa by Glen Ditchfield. Committed on 26/07/2021 at 01:14. Pushed by gditchfield into branch 'release/21.08'. Bind keyboard shortcuts in the Search dialog's results Bind the Delete key to the "Delete" action, and Return to "Edit...". This finishes off M +22 -0src/dialog/searchdialog.cpp M +2-0src/dialog/searchdialog.h https://invent.kde.org/pim/korganizer/commit/48485e4fbdc7b70a30972bb3ac2d529b987746aa -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440313] New: digiKam 7.3.0 FTBFS with Qt 5.9.5
https://bugs.kde.org/show_bug.cgi?id=440313 Bug ID: 440313 Summary: digiKam 7.3.0 FTBFS with Qt 5.9.5 Product: digikam Version: 7.3.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Database Assignee: digikam-bugs-n...@kde.org Reporter: savo...@savos.tech Target Milestone: --- Created attachment 140347 --> https://bugs.kde.org/attachment.cgi?id=140347=edit Patch to fix FTBFS SUMMARY digiKam 7.3.0 FTBFS with Qt 5.9.5 due introducing use of the QScopedPointer get function (added in Qt 5.11). STEPS TO REPRODUCE 1. Download digiKam 7.3.0 source and extract. 2. Attempt building source using pbuilder in a clean chroot with all appropriate build dependencies including Qt 5.9.5 (and KDE 5.44.0). 3. Build fails with errors as described below. OBSERVED RESULT The build fails with repeated errors relative a QScopedPointer function: "no member named 'get'" These errors are due use of the get function in three files (see below). EXPECTED RESULT That the build succeeds with Qt 5.9.5 as Qt 5.9 is listed as the minimum Qt build dependency for digiKam. SOFTWARE/OS VERSIONS Windows: n/a macOS: n/a Linux/KDE Plasma: Ubuntu 18.04 / KDE 5.44 (available in About System) KDE Plasma Version: 5.44 KDE Frameworks Version: 5.44 Qt Version: 5.9.5 ADDITIONAL INFORMATION With digiKam 7.3.0 three source files are now using the QScopedPointer get function found only in Qt 5.11 and newer. Those files are as follows: core/libs/database/dbjobs/dbjobsthread.cpp core/libs/database/haar/haariface_p.cpp core/libs/dngwriter/dngwriter_convert.cpp Yet Mainpage.dox still lists Qt 5.9 as a sufficient build dependency. Please change use of QScopedPointer get function to data function, which is identical according to official documentation, so that the build can still be successful without patching on Qt 5.9.5 (as found in Ubuntu 18.04 LTS Bionic, for example). The attached patch fixes the build for Qt 5.9.5 by making the suggested change. Official documentation of relevance is found here: https://doc.qt.io/archives/qt-5.11/qscopedpointer.html -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440312] New: Severe memory leak with kwin wayland and javafx app with es2 ( not on kwin x11 )
https://bugs.kde.org/show_bug.cgi?id=440312 Bug ID: 440312 Summary: Severe memory leak with kwin wayland and javafx app with es2 ( not on kwin x11 ) Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: pereira.a...@gmail.com Target Milestone: --- SUMMARY Hi, This is a weird bug, but from all my testing ( more than a week trying to find out what was happening ), its a bug that only happens on kwin wayland ( not on x11 ). So, I have to use an javafx proprietary app, that when using with kwin wayland, works completly fine, until screensaver activates and turns off the monitors. By screensaver, I mean just the power idle setting to turn the monitors off, not any fancy screensaver effect. What happens is that the app is running fine, usually using about 1GB/2GB of ram ( I have 16GB, so lots of free ram ). As soon as the screensaver activates ( this can be a 1 minute idle timeout or 1 hour, doesn't matter ), in seconds, all ram is filled and oom daemon either starts killing or ( if oom daemon disabled ) the computer gets unresponsive. It fills around 13/14 GB of ram and 4 GB of swap space in seconds. I am writting this bug report on kwin wayland, because this doesn't happen on kwin X11. It also doesn't happen on gnome wayland. It also doesn't happen on sway. Also this only happens when javafx is using es2 gpu acceleration ( doesn't happen on software mode, but software mode is almost unusable, the app is very graphic intensive ). I have tested also with kde stable releases on gentoo and arch, and kde master git on opensuse. I also tried the latest jdk different GC's and with different heap memory settings. I understand that this is not much info or that its hard to say that is not a bug elsewhere. But the bug is reproducible. Unfortunatly, its a proprietary app. I will try to find an open source javafx app to make it easier to be reproducible by others. Please let me know what further steps I can take to track this issue and provide better info. STEPS TO REPRODUCE 1. start app 2. dont touch computer to let screensaver kick in 3. watch in another computer through ssh memory get completly filled seconds after monitors turn off OBSERVED RESULT Memory starts getting completly filled and all swap is used. OOM either kicks in and kills apps or computer gets unresponsive. EXPECTED RESULT Like what happens on kwin x11, gnome wayland or sway... memory keeps about the same after screensaver as before. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434339] To delete widgets, you must show the widget explorer with a menu item named "Add widgets"
https://bugs.kde.org/show_bug.cgi?id=434339 --- Comment #7 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/302 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434339] To delete widgets, you must show the widget explorer with a menu item named "Add widgets"
https://bugs.kde.org/show_bug.cgi?id=434339 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-desktop/-/merge_requests/533 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #445 from michel --- Well, as one can see, the calculation of the KDE responsible persons works out. They sit out the problem, simply do nothing, the stupid users will eventually keep their mouths shut. The once existing transparency, exemplary and appreciated by all users, has gently and quietly fallen asleep, the would-be gods no longer let them look at their cards and do what they want. If you scratch the surface, as I did in a German Linux forum, someone who seems to belong to this circle immediately feels attacked and reacts irritably and with impertinent and unobjective statements. There is no one to turn to, who is willing and able to have an objective discussion. And so a once great and excellent idea degenerates to a pride of place of a few, the users stand powerlessly by and fight only against impenetrable fog, what becomes of the matter "KDE" is ultimately no longer traceable, neither goals nor their realization are known. However, such behavior is not KDE-specific. It can be found these days in every non-functioning form of government without the participation of the "subjects". Therefore, the KDE team is in good company. We users just have to guzzle, what we are accused of. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 108161] Cannot use the save dialog to save file if the name contains a slash (unlike when using KNewFileMenu to create a new file)
https://bugs.kde.org/show_bug.cgi?id=108161 --- Comment #10 from Sergey Kondakov --- (In reply to Nate Graham from comment #9) > Yeah, I think there has to be a way to make this work at least in the UI. > What macOS does is allow the user to use the slash character in filenames > (through the GUI of course) but silently represents them as a colon > character in the actual POSIX filename. We could maybe do something similar. > It's kind of lying to the user about the underlying representation, but the > user generally doesn't care about the underlying representation. :) Fraction/division slash may work - ⁄ (U+2044) and ∕ (U+2215). But colon wouldn't as it's a normal and often-used character in Linux. These slashes stay too close to letters unlike a normal slash. Which is why, I assume, KDE3 used web-like "escape" encoding. But escape encoding is ugly. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440311] Creating nameless brush tip from clipboard does not save tip correctly and can make krita crash.
https://bugs.kde.org/show_bug.cgi?id=440311 Halla Rempt changed: What|Removed |Added Severity|normal |crash CC||ha...@valdyas.org Platform|Other |Microsoft Windows OS|Other |Microsoft Windows -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440311] New: Creating nameless brush tip from clipboard does not save tip correctly and can make krita crash.
https://bugs.kde.org/show_bug.cgi?id=440311 Bug ID: 440311 Summary: Creating nameless brush tip from clipboard does not save tip correctly and can make krita crash. Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: alanscode...@gmail.com Target Milestone: --- Created attachment 140346 --> https://bugs.kde.org/attachment.cgi?id=140346=edit crash log SUMMARY Creating nameless brush tip from clipboard does not save the brush tip file correctly. Also this causes the current version of krita to crash when choosing a preset that has it set as it's brush tip. The crashing does not happen with an older build I had been using (d01cd76e94), though the general problem does. I've lost several tips to this, but just didn't really dig into why at the time. STEPS TO REPRODUCE 1. Create a new file, draw something. Select and copy. 2. Create brush tip from clipboard, don't name it. 4. Restart krita. To make it crash, do the same but save a brush preset before restarting, then try to select it after restart. I've also had problems going to the predefined brush tips in the brush editor making things crash using a database that had several problematic brush presets, but could not replicate with a fresh one. OBSERVED RESULT The brush tip disappears on restart, probably because the brush tip file is empty/invalid. In the log I see `dependent resource "2021-07-26T18:13.gbr" misses.` when I open the brush presets list. In the older version I don't get that, instead when I select the brush I get: `Using fallback brush brushFileName = "2021-07-26T18:13.gbr"` In the resources folder I see it saves a file with a date for a name (e.g. 2021-07-26T18) when I save the brush, but it has no extension or size. Also, I wonder if the lack of the part after the colon in the filename is part of the problem? If I name the tip, this doesn't happen. A proper .gbr file is created. Strangely, deleting the file or even the database, does not help, still crashes. The only fix is deleting the preset manually or using an older build of krita to "fix" the preset and assign a properly saved tip to it, then open in new krita. SOFTWARE/OS VERSIONS Windows 10 Krita: 178019461d -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440296] Issue with external Mariadb 10.6.3
https://bugs.kde.org/show_bug.cgi?id=440296 --- Comment #14 from Antonio Rojas --- The patch doesn't help, sadly. As a workaround, could the MARIADB_CLIENT_CACHE_METADATA feature be disabled from the digikam code, or should that be done in Qt? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 160399] too wide error message for property-behaviour error
https://bugs.kde.org/show_bug.cgi?id=160399 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/523 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 158073] [FreeBSD] KMountPoint doesn't get mount options for devices not in /etc/fstab
https://bugs.kde.org/show_bug.cgi?id=158073 Ahmad Samir changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/kio/-/commit/c96f9db ||5397c0ac8fb4824a02e1d61ed0a ||79e4e5 Version Fixed In||5.85 Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 440310] New: In plasma-systemmonitor, on 12-thread CPU, "Core 11" and "Core 12" sensors sort above "Core 3"
https://bugs.kde.org/show_bug.cgi?id=440310 Bug ID: 440310 Summary: In plasma-systemmonitor, on 12-thread CPU, "Core 11" and "Core 12" sensors sort above "Core 3" Product: plasma-systemmonitor Version: 5.22.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: nyanpas...@tuta.io CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 140345 --> https://bugs.kde.org/attachment.cgi?id=140345=edit Screenshot of the CPUs sensor group list. SUMMARY On my 12-thread CPU, when I try adding CPU statistics to a plasma-systemmonitor graph, the sorting order of my CPU cores is incorrect. STEPS TO REPRODUCE 1. Open plasma-systemmonitor. 2. Click "Add New Page..." and "Add". 3. Click the "System Monitor Sensor", and in the right sidebar, click Total Sensors or Sensors. 4. Click "CPUs" and look at the list of sensor groups. OBSERVED RESULT The sort order is "All, Core 1, Core 2, Core 11, Core 12, Core 3..., Core 10, [Group] CPU". EXPECTED RESULT Cores are sorted in numeric order (I think)? SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.4-zen2-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GT 730/PCIe/SSE2 ADDITIONAL INFORMATION I don't know where the order comes from, or if there's a technical explanation for the strange order. I don't think the 5600X is NUMA, so that shouldn't be it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 119513] I want to set bookmarks for files
https://bugs.kde.org/show_bug.cgi?id=119513 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com --- Comment #3 from Ahmad Samir --- It looks like the xdg spec only supports bookmarks to directories: https://specifications.freedesktop.org/recent-file-spec/recent-file-spec-0.2.html -- You are receiving this mail because: You are watching all bug changes.
[kolf] [Bug 440301] crash after hole 18
https://bugs.kde.org/show_bug.cgi?id=440301 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Albert Astals Cid --- That version of kolf is super old. Like almost a decade old probably, please update to something that we are actually developing and see if it still has this problem. -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 439897] Heaptrack produces impossible/incorrect stack traces
https://bugs.kde.org/show_bug.cgi?id=439897 --- Comment #2 from Matt Whitlock --- (In reply to Milian Wolff from comment #1) > Since you are using gentoo: Are the debug symbols you are using for > plasmashell and qt and so forth matching the build that you profiled? Yes. The debug symbols get installed (beneath /usr/lib/debug) at the same time as the binaries are installed to the live file system by the package manager. The debug symbols are produced in the same build process that produces the executable/library binaries and are then split apart from the binaries to be filed separately. Gentoo doesn't use separate packages for debug symbols like some distros do. > Is this easily reproducible for me somehow? I'm not sure. Have you tried Heaptrack with GCC 11 yet? I am thinking there may be an issue with the debug info that the compiler is generating, as I am seeing impossible stack traces in GDB while interactively debugging my own programs too. What I observe is that a stack frame will show as belonging to a leaf function that has already returned, and in fact the frame that called the leaf function is not represented separately in the stack trace, but rather the frame that shows as the leaf function *is* the frame that called the leaf function, and the information about the caller of the leaf function is absent from the stack trace. It is as though GCC is *overwriting* the source location information in the current stack frame when it invokes the (presumably inlined) leaf function and then forgets to restore it when it's finished with the leaf function. That would explain why my Heaptrack output is making no sense to me and has been utterly useless for tracking down a memory leak. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356446] Enable Qt scaling on X11
https://bugs.kde.org/show_bug.cgi?id=356446 Nate Graham changed: What|Removed |Added Depends on|428895 | Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=428895 [Bug 428895] [x11] Maximized windows don't fill 1px of screen on HiDPI -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428895] [x11] Maximized windows don't fill 1px of screen on HiDPI
https://bugs.kde.org/show_bug.cgi?id=428895 Nate Graham changed: What|Removed |Added Blocks|356446 | Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=356446 [Bug 356446] Enable Qt scaling on X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428895] [x11] Maximized windows don't fill 1px of screen on HiDPI
https://bugs.kde.org/show_bug.cgi?id=428895 --- Comment #10 from Nate Graham --- Can confirm with the Plasma X11 session when using Qt scaling as well as Plasma scaling. Not related to that, then. Must be exclusively a KWin issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390295] The active virtual desktop is no longer remembered between sessions
https://bugs.kde.org/show_bug.cgi?id=390295 --- Comment #14 from Brian Kaye --- Won't be switching to wayland real soon. Here are the tests I ran. 1. Configured in X firefox in desktop 3 and Konsole in desktop 4. Restart with X put Konsole in desktop 1 and firefox in proper desktop. 2. Configured as in 1. and restarted in wayland. Same problem but everything slower to start. 3. Configured in wayland as in 1. Restarted in wayland. Different problem. The Konsole application did not restart. Desktop icons took a long time to show up. 4. Configured in wayland as in 1. Restarted in X. Different problem. The Konsole application did not show up. Took long time (~ 20 seconds) for desktop icons to show up. Login was slow. Have not tried a second login yet. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 225658] recursive setting of ownership fails if directory already matches the ownership requested
https://bugs.kde.org/show_bug.cgi?id=225658 Ahmad Samir changed: What|Removed |Added Version Fixed In||5.85 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/kio/commit/42b516631 ||4dcbc3018f56fd6450dbcd54b66 ||42fc --- Comment #2 from Ahmad Samir --- Git commit 42b5166314dcbc3018f56fd6450dbcd54b6642fc by Ahmad Samir. Committed on 26/07/2021 at 21:09. Pushed by ahmadsamir into branch 'master'. KPropertiesDialog: fix applying permissions recursively If "apply recursively" is enabled for dirA, we need to apply the owner/group permissions to the contents of that dir, even if the owner/group weren't changed in the dialog, since the items under that dir could have different permissions. FIXED-IN: 5.85 M +9-6src/widgets/kpropertiesdialog.cpp https://invent.kde.org/frameworks/kio/commit/42b5166314dcbc3018f56fd6450dbcd54b6642fc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356446] Enable Qt scaling on X11
https://bugs.kde.org/show_bug.cgi?id=356446 Nate Graham changed: What|Removed |Added Depends on||423390 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=423390 [Bug 423390] [X11] Bottom Plasma panel and desktop are not fully adjacent to screen border (1 pixel on the right and bottom) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356446] Enable Qt scaling on X11
https://bugs.kde.org/show_bug.cgi?id=356446 Bug 356446 depends on bug 423390, which changed state. Bug 423390 Summary: [X11] Bottom Plasma panel and desktop are not fully adjacent to screen border (1 pixel on the right and bottom) https://bugs.kde.org/show_bug.cgi?id=423390 What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423390] [X11] Bottom Plasma panel and desktop are not fully adjacent to screen border (1 pixel on the right and bottom)
https://bugs.kde.org/show_bug.cgi?id=423390 Nate Graham changed: What|Removed |Added Blocks||356446 Status|CONFIRMED |RESOLVED Resolution|--- |NOT A BUG --- Comment #5 from Nate Graham --- This is caused by using Qt scaling on X11, which is not supported and is known to cause this kind of bug. So don't do it. :) If you have PLASMA_USE_QT_SCALING=1 set in your environment, unsetting it should fix the problem. Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=356446 [Bug 356446] Enable Qt scaling on X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356446] Enable Qt scaling on X11
https://bugs.kde.org/show_bug.cgi?id=356446 Nate Graham changed: What|Removed |Added Depends on||422559 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=422559 [Bug 422559] Plasma dialog corners and shadows do not respect the scale factor on X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422559] Plasma dialog corners and shadows do not respect the scale factor on X11
https://bugs.kde.org/show_bug.cgi?id=422559 Nate Graham changed: What|Removed |Added Blocks||356446 Resolution|--- |NOT A BUG Status|CONFIRMED |RESOLVED --- Comment #5 from Nate Graham --- This is caused by using Qt scaling on X11, which is not supported cna is known to cause this kind of bug. So don't do it. :) Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=356446 [Bug 356446] Enable Qt scaling on X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356446] Enable Qt scaling on X11
https://bugs.kde.org/show_bug.cgi?id=356446 Bug 356446 depends on bug 422559, which changed state. Bug 422559 Summary: Plasma dialog corners and shadows do not respect the scale factor on X11 https://bugs.kde.org/show_bug.cgi?id=422559 What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356446] Enable Qt scaling on X11
https://bugs.kde.org/show_bug.cgi?id=356446 Nate Graham changed: What|Removed |Added Summary|plasmashell does not|Enable Qt scaling on X11 |respect | |QT_DEVICE_PIXEL_RATIO on X | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356446] plasmashell does not respect QT_DEVICE_PIXEL_RATIO on X
https://bugs.kde.org/show_bug.cgi?id=356446 Nate Graham changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #62 from Nate Graham --- All of the issues that are possible to fix on X11 without turning on Qt scaling have been un-duped and I am in the process of fixing them. See the open bug reports in the See Also field for details. As a result, I don't believe we will need to ever use Qt scaling on X11 to achieve a pleasant high DPI experience on X11. Turning on Qt scaling on X11 simply causes too many bugs compared to the number that it fixes. Closing this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395956] [Wayland] Calendar events are not shown at first
https://bugs.kde.org/show_bug.cgi?id=395956 popov895 changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #8 from popov895 --- Closed due to the end of LTS Edition. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408055] Plasma panel height is ignoring both "force font dpi" and "scale display" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408055 Nate Graham 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 356446] plasmashell does not respect QT_DEVICE_PIXEL_RATIO on X
https://bugs.kde.org/show_bug.cgi?id=356446 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=408055 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408055] Plasma panel height is ignoring both "force font dpi" and "scale display" in system settings when resizing window in virtualbox with auto-resize guest display enabled
https://bugs.kde.org/show_bug.cgi?id=408055 Nate Graham changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REPORTED See Also||https://bugs.kde.org/show_b ||ug.cgi?id=356446 --- Comment #11 from Nate Graham --- Un-duping since this should be possible to fix separately even if Bug 356446 is never fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381794] System tray icon size on high DPI screen is small
https://bugs.kde.org/show_bug.cgi?id=381794 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #16 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/301 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 390147] Units::roundToIconSize returns incorrect result for SizeSmallMedium when screen scaling >= 2
https://bugs.kde.org/show_bug.cgi?id=390147 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #7 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/301 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419239] Plasma applets popups are not flagged SkipSwitcher
https://bugs.kde.org/show_bug.cgi?id=419239 --- Comment #11 from popov895 --- Looks like this has already been fixed. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439517] Filtered folders/files remain visible after renaming
https://bugs.kde.org/show_bug.cgi?id=439517 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/system/dolphin/-/merge_requests/246 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440308] Can't drag to rearrange favorite apps anymore
https://bugs.kde.org/show_bug.cgi?id=440308 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440296] Issue with external Mariadb 10.6.3
https://bugs.kde.org/show_bug.cgi?id=440296 --- Comment #13 from Maik Qualmann --- Ok, then try the current git / master with the patch from Comment 10. It's the only thing I can think of ... Maik -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 437701] "File Type Options" button assumes presence of filetypes KCM and does nothing if it is not present
https://bugs.kde.org/show_bug.cgi?id=437701 Ahmad Samir changed: What|Removed |Added Version Fixed In||5.85 Latest Commit||https://invent.kde.org/fram ||eworks/kwidgetsaddons/commi ||t/21f35a4698c9ee32f6870c930 ||f6c372dff0b1fd6 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #10 from Ahmad Samir --- Git commit 21f35a4698c9ee32f6870c930f6c372dff0b1fd6 by Ahmad Samir. Committed on 26/07/2021 at 20:24. Pushed by ahmadsamir into branch 'master'. kmimetypeeditor: display an error message if keditfiletype couldn't be started FIXED-IN: 5.85 M +12 -1src/kmimetypeeditor.cpp M +4-0src/kmimetypeeditor.h https://invent.kde.org/frameworks/kwidgetsaddons/commit/21f35a4698c9ee32f6870c930f6c372dff0b1fd6 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440296] Issue with external Mariadb 10.6.3
https://bugs.kde.org/show_bug.cgi?id=440296 --- Comment #12 from Antonio Rojas --- (In reply to Maik Qualmann from comment #11) > Akonadi is also affected: Bug 439769 > > Maik That's not related. We are already shipping a workaround for that. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440296] Issue with external Mariadb 10.6.3
https://bugs.kde.org/show_bug.cgi?id=440296 --- Comment #11 from Maik Qualmann --- Akonadi is also affected: Bug 439769 Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356446] plasmashell does not respect QT_DEVICE_PIXEL_RATIO on X
https://bugs.kde.org/show_bug.cgi?id=356446 --- Comment #61 from Nate Graham --- Git commit 32bfd1ed01f0cbd48071dadf89458edbb8edfd1e by Nate Graham. Committed on 26/07/2021 at 18:31. Pushed by ngraham into branch 'master'. Handle huge icons in Units::roundToIconSize() This function was missing a use case for icons that are between the sizes of huge and enormous, causing huge-sized icons to appear too large on X11 when not using Qt scaling. This commit fixes that, and addresses one of the sources of complaints when using scaling on X11. Small icons are still too small, but that must and will be handled separately. M +3-0src/declarativeimports/core/units.cpp https://invent.kde.org/frameworks/plasma-framework/commit/32bfd1ed01f0cbd48071dadf89458edbb8edfd1e -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 385275] When exiting the application don't force user to save, unsaved document only save it as temporary
https://bugs.kde.org/show_bug.cgi?id=385275 --- Comment #8 from Piotr Mierzwinski --- I tested this also in Neon updated at Jul, 24th 2021 (details belwow) and noticed that when I close kate with not saved file then it doesn't ask me for saveing this file. The same is happen when I have in kate not saved file and try to logoff or shutdown the system. Nice. Only the problem is that after kate starts with new session of Plasma then changes made before closing are not restored, so nothing was swapped in moment on kate was closed. Second thing is that this (not asking for file save not saved file) works only in Kate. When I tried to do the same with kwrite, it asked me for saveing file. Please notice that I had the same setting in both. Kate 21.11.70 Plasma 5.22.80 Framework 5.85 Qt-5.15.3 Graphics X11 Kernel 5.8.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440296] Issue with external Mariadb 10.6.3
https://bugs.kde.org/show_bug.cgi?id=440296 --- Comment #10 from Maik Qualmann --- Git commit 2775af8e0af34ff5241368d9296ad21a2d0de3f0 by Maik Qualmann. Committed on 26/07/2021 at 19:58. Pushed by mqualmann into branch 'master'. remove for a test the workaround for mariaDB >= 10.2 and QTBUG-63108 M +2-2core/libs/album/manager/albummanager_database.cpp https://invent.kde.org/graphics/digikam/commit/2775af8e0af34ff5241368d9296ad21a2d0de3f0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #39 from Andrew Ammerlaan --- (In reply to Zamundaaa from comment #38) > Could you check if the monitor still turns off on login now? I added a > commit that might resolve that Perfect, it works flawlessly now. There's a very nice transition from sddm to black to a fade-in of the splash screen, it is the same on all monitors! Thank you very much for your efforts -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440308] Can't drag to rearrange favorite apps anymore
https://bugs.kde.org/show_bug.cgi?id=440308 --- Comment #2 from Noah Davis --- (In reply to Nate Graham from comment #1) > Noah, can you investigate? will do. I think I forgot to re-add this. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440296] Issue with external Mariadb 10.6.3
https://bugs.kde.org/show_bug.cgi?id=440296 --- Comment #9 from Maik Qualmann --- Could possibly be relevant: https://bugreports.qt.io/projects/QTBUG/issues/QTBUG-95071?filter=allissues Maik -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 440309] New: Request: add functionality to test diplay settings before applying them
https://bugs.kde.org/show_bug.cgi?id=440309 Bug ID: 440309 Summary: Request: add functionality to test diplay settings before applying them Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- Would be helpful if the "Display Settings" section (the one where one can configure screen resolution and related stuff) would have a button to test the changes before applying them, in the same way as e.g. MS windows - that is, one sets a new display setting (e.g. testing a different screen and resolution), clicks "test", it changes to the new settings for 5 seconds or so, and then comes back to the old setting. This would be especially helpful in settings in which some change could result in an invalid display that does not allow visual cues to revert - for example, in my own setup, if I try to switch to a laptop screen after another screen is already running on HDMI, it shows only random noise on the screen, so I cannot click back on 'reset' to change the settings (this is a mesa bug so unrelated). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 129518] dont use kioslave URLs when opening files by non-KDE programs
https://bugs.kde.org/show_bug.cgi?id=129518 Ahmad Samir changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED CC||a.samir...@gmail.com --- Comment #9 from Ahmad Samir --- I tested this: - opened a .tgz file in dolphin - opening a text file in e.g. kate, it opened it using the kioslave, so tar:/ url scheme - opening a text file in libreoffice writer, the file was "downloaded" to ~/.cache/kioexec/krun/* and then opened in libreoffice writer the issue looks fixed, of sorts, to me. Closing as such, feel free to reopen if you disagree. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440296] Issue with external Mariadb 10.6.3
https://bugs.kde.org/show_bug.cgi?id=440296 Maik Qualmann changed: What|Removed |Added CC||ayr...@gmail.com --- Comment #8 from Maik Qualmann --- *** Bug 440132 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440132] Digikam crashes scanning for new items
https://bugs.kde.org/show_bug.cgi?id=440132 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from Maik Qualmann --- I close this bug as a duplicate of Bug 440296, since we already have a possible cause there. *** This bug has been marked as a duplicate of bug 440296 *** -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440283] Changing the value of iconOffsetY inside a custom indicator (with a Binding) doesn't appear to move the icons up nor down
https://bugs.kde.org/show_bug.cgi?id=440283 --- Comment #4 from Cyrus <0jf2fh...@relay.firefox.com> --- Awesome! Thank you for the quick fix! I'm happy to bring some competition to the indicator market :) A bit of a bummer for the icon scale, but totally understandable. Once I'm more familiar (and better) with QML and C++, I'd love to try and implement that feature (if it hasn't been implemented by that time) and also help with Latte development. Thanks again for all your work on this great app! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440308] Can't drag to rearrange favorite apps anymore
https://bugs.kde.org/show_bug.cgi?id=440308 Nate Graham changed: What|Removed |Added Priority|NOR |VHI Assignee|k...@davidedmundson.co.uk|noaha...@gmail.com Keywords||regression --- Comment #1 from Nate Graham --- Noah, can you investigate? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440308] New: Can't drag to rearrange favorite apps anymore
https://bugs.kde.org/show_bug.cgi?id=440308 Bug ID: 440308 Summary: Can't drag to rearrange favorite apps anymore Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: n...@kde.org CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 After the big code refactor in https://invent.kde.org/plasma/plasma-desktop/-/commit/9d9c4f169ed424e976636a6d5fa23c7a1e40576b landed, I can't drag favorited apps to re-arrange them anymore. Both grid view and list view are affected, though I didn't use list view before, so I don't know if drag-re-ordering used to work there. But I know it used to work for grid view and it's broken now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391682] Many Plasma UI elements (e.g. radiobuttons, checkboxes) are scaled incorrectly when using a scale factor
https://bugs.kde.org/show_bug.cgi?id=391682 Nate Graham 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 391682] Many Plasma UI elements (e.g. radiobuttons, checkboxes) are scaled incorrectly when using a scale factor
https://bugs.kde.org/show_bug.cgi?id=391682 Nate Graham changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REPORTED See Also||https://bugs.kde.org/show_b ||ug.cgi?id=356446 Ever confirmed|1 |0 Summary|Inconsistent HiDPI |Many Plasma UI elements |Rendering |(e.g. radiobuttons, ||checkboxes) are scaled ||incorrectly when using a ||scale factor --- Comment #18 from Nate Graham --- Un-duping since this appears to be different from Bug 390147 after all. The fix may be similar, but fixing that will not automatically fix this. Looking into it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356446] plasmashell does not respect QT_DEVICE_PIXEL_RATIO on X
https://bugs.kde.org/show_bug.cgi?id=356446 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=391682 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 440095] No support for "dc cvac" and "dc cvap" on Arm64
https://bugs.kde.org/show_bug.cgi?id=440095 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #6 from Mark Wielaard --- (In reply to kevinz from comment #5) > Could you point me how to submit patches to Valgrind? > Thanks! Best is to attach a patch to this bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 136746] When attempting to copy a file to a filesystem that doesn't support some of the characters in the filename, inform the user of this fact
https://bugs.kde.org/show_bug.cgi?id=136746 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/520 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366088] Not scaled icons on a HiDPI screen: the right button menu on the desktop
https://bugs.kde.org/show_bug.cgi?id=366088 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=356446 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356446] plasmashell does not respect QT_DEVICE_PIXEL_RATIO on X
https://bugs.kde.org/show_bug.cgi?id=356446 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=381794, ||https://bugs.kde.org/show_b ||ug.cgi?id=366088 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381794] System tray icon size on high DPI screen is small
https://bugs.kde.org/show_bug.cgi?id=381794 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=356446 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 440306] DrKonqi fails to recognise kmozillahelper
https://bugs.kde.org/show_bug.cgi?id=440306 Christopher Yeleighton changed: What|Removed |Added URL|https://github.com/openSUSE |https://github.com/openSUSE |/kmozillahelper |/kmozillahelper/issues/32 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438703] Missing translations for a few common buttons like OK and Cancel (Kate official builds only)
https://bugs.kde.org/show_bug.cgi?id=438703 --- Comment #12 from Christoph Cullmann --- Hi, I tried that now: if I move the "translations" folder to the bin dir, for me all is "consistent". I am just too dumb to find the right place to alter that in craft. Hannah, have you some pointers? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 390147] Units::roundToIconSize returns incorrect result for SizeSmallMedium when screen scaling >= 2
https://bugs.kde.org/show_bug.cgi?id=390147 Nate Graham changed: What|Removed |Added CC||battagli...@gmail.com --- Comment #6 from Nate Graham --- *** Bug 391682 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391682] Inconsistent HiDPI Rendering
https://bugs.kde.org/show_bug.cgi?id=391682 --- Comment #17 from Nate Graham --- Largely tracked already by BUG 381794 and Bug 366088, but also some of BUG 390147. Arbitrarily re-marking as a duplicate of BUG 381794 because we can't multi-dupe. :) *** This bug has been marked as a duplicate of bug 390147 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 420132] At 2x scale, UI elements appear squished (padding disappears) when used with some GPUs
https://bugs.kde.org/show_bug.cgi?id=420132 --- Comment #3 from Nate Graham --- *** This bug has been marked as a duplicate of bug 390147 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 390147] Units::roundToIconSize returns incorrect result for SizeSmallMedium when screen scaling >= 2
https://bugs.kde.org/show_bug.cgi?id=390147 Nate Graham changed: What|Removed |Added CC||maximumsometh...@gmail.com --- Comment #5 from Nate Graham --- *** Bug 420132 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 440306] DrKonqi fails to recognise kmozillahelper
https://bugs.kde.org/show_bug.cgi?id=440306 Christopher Yeleighton changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 440306] DrKonqi fails to recognise kmozillahelper
https://bugs.kde.org/show_bug.cgi?id=440306 Christopher Yeleighton changed: What|Removed |Added URL||https://github.com/openSUSE ||/kmozillahelper -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438765] Animation: Infinite "update" loop with transform mask
https://bugs.kde.org/show_bug.cgi?id=438765 --- Comment #3 from grum...@grum.fr --- Hi I can confirm on last tested appimage (krita-5.0.0-prealpha-627782b-x86_64.appimage) that something has been fixed. It's not 100% fixed, but I think we can consider that problem is not noticeable anymore and bug can stay in "FIXED" status To be more precise: - Hide group layer "GroupAnim" -> We can see activity on hidden transform mask layers - Wait 4s -> We can see activity on hidden transform mask layers And then, no unexpected activity occurs anymore on hidden transform layers. Grum999 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 390147] Units::roundToIconSize returns incorrect result for SizeSmallMedium when screen scaling >= 2
https://bugs.kde.org/show_bug.cgi?id=390147 Nate Graham changed: What|Removed |Added CC||pos...@posteo.eu --- Comment #4 from Nate Graham --- *** Bug 424465 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 424465] Wallpaper's open dialog's icons too small (with scaling 2.0)
https://bugs.kde.org/show_bug.cgi?id=424465 --- Comment #6 from Nate Graham --- *** This bug has been marked as a duplicate of bug 390147 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440307] New: Cannot switch tabs with Ctrl+Tab anymore
https://bugs.kde.org/show_bug.cgi?id=440307 Bug ID: 440307 Summary: Cannot switch tabs with Ctrl+Tab anymore Product: plasmashell Version: 5.22.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: k...@privat.broulik.de CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Since the recent rewrite I cannot switch tabs with Ctrl+Tab anymore STEPS TO REPRODUCE 1. Open Kickoff 2. Hit Ctrl+Tab OBSERVED RESULT Nothign happens EXPECTED RESULT I cycle between apps and places tabs SOFTWARE/OS VERSIONS Linux/KDE Plasma: git master as of 2021-07-24 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381794] System tray icon size on high DPI screen is small
https://bugs.kde.org/show_bug.cgi?id=381794 Nate Graham changed: What|Removed |Added CC||tildear...@protonmail.com --- Comment #15 from Nate Graham --- *** Bug 426978 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426978] System Tray icon spacing is larger than before when not using Qt scaling
https://bugs.kde.org/show_bug.cgi?id=426978 --- Comment #10 from Nate Graham --- *** This bug has been marked as a duplicate of bug 381794 *** -- You are receiving this mail because: You are watching all bug changes.