[plasmashell] [Bug 486236] Cannot change a time zone.
https://bugs.kde.org/show_bug.cgi?id=486236 --- Comment #5 from gigastarcra...@proton.me --- (In reply to David Edmundson from comment #4) > >"Failed to set current time "org.freedesktop.PolicyKit1.Error.NotAuthorized" > >"Authorizing for 'org.freedesktop.timedate1.set-time': not authorized"" > > It's using a systemd path. I assume you don't have systemd? No, I use Artix OpenRC. I get warning "System policy prevents changing timezone" -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 89299] prevent paste of newline characters
https://bugs.kde.org/show_bug.cgi?id=89299 gudvinr+...@gmail.com changed: What|Removed |Added CC||gudvinr+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487738] crash: Data too big for buffer
https://bugs.kde.org/show_bug.cgi?id=487738 --- Comment #1 from p...@pfortin.com --- See attachment; crash report included: May 28 13:41:20 kwin_wayland_wrapper[40581]: Data too big for buffer (4108 > 4096) at the time I clicked on the notification icon and instantly crashed. As always: # coredumpctl --reverse No coredumps found. While wayland is missing features, my last use of X11 was too unstable for normal use. PS: Hitting Enter (for new line) in attachment description submitted report before I was done editing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487695] Windows always open on all activities since 6.0.5 - also can't move windows to other activities
https://bugs.kde.org/show_bug.cgi?id=487695 bastimeyer...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from bastimeyer...@gmail.com --- Looks like this was a build issue on my end. I've re-built everything and the issue is now gone. It didn't even make sense considering the commit histories of all the repos involved (kwin / plasma-workspace, and dependencies). Sorry for the unnecessary noise. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487738] New: crash: Data too big for buffer
https://bugs.kde.org/show_bug.cgi?id=487738 Bug ID: 487738 Summary: crash: Data too big for buffer Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: p...@pfortin.com Target Milestone: 1.0 Created attachment 169934 --> https://bugs.kde.org/attachment.cgi?id=169934=edit output of "journalctl -b -1 -g plasma > /tmp/plasmashell_crashes" *** 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 *** SUMMARY After some time, plasmashell starts crashing. When it starts, it just keeps getting worse, until every mouse click or mouse over triggers a crash. In this case, got a notification at a time I was too busy to read; then clicked notifications icon in systray --> instant crash. STEPS TO REPRODUCE 1. use the system -- 3 screens, panels on each screen. Only main screen has full panel. 2. mouse over|click any panel 3. OBSERVED RESULT crash & auto-restart (though not always -- need to issue plasmashell --replace) Journal log (see attachment for surrounding messages) May 28 13:41:20 kwin_wayland_wrapper[40581]: Data too big for buffer (4108 > 4096). May 28 13:41:20 kwin_wayland_wrapper[40581]: error in client communication (pid 2425188) EXPECTED RESULT no crash SOFTWARE/OS VERSIONS Operating System: Mageia 10 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.6.2 Kernel Version: 6.6.28-server-1.mga10 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-12700K Memory: 125.5 GiB of RAM Graphics Processor: AMD Radeon RX 6600 XT Manufacturer: Dell Inc. Product Name: XPS 8950 ADDITIONAL INFORMATION Once the crashes start, they become worse. The first was when I clicked the notification icon; then, it was emacs, desktop selection, or just moving mouse over taskbar (anywhere). -- You are receiving this mail because: You are watching all bug changes.
[klines] [Bug 487737] New: Disabling Show Next feature only affects the scoring system until the user restarts the game
https://bugs.kde.org/show_bug.cgi?id=487737 Bug ID: 487737 Summary: Disabling Show Next feature only affects the scoring system until the user restarts the game Classification: Applications Product: klines Version: 1.6.21123 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dim...@gmail.com Reporter: gosta...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY The bug happens when the Show Next feature is disabled. Immediately after disabling the Show Next feature, scores are awarded correctly (11 for 5 removed marbles). After starting New Game (Game -> New), scores are awarded incorrectly as if Show Next was enabled (10 for 5 removed marbles). STEPS TO REPRODUCE 1. Launch Kolor Lines. Disable Settings -> Show Next. (If it was already disabled, enable it and then disable again.) 2. Play the game and observe that completing a line of 5 marbles gives score 11. 3. Restart the game (Game -> New). 4. Play the game and observe that completing a line of 5 marbles gives score 10 now, even though Show Next is still disabled. OBSERVED RESULT Disabling "Settings -> Show Next" only affects the scoring system until the user restarts the game. EXPECTED RESULT Disabling "Settings -> Show Next" affects the scoring system for all subsequent games, until the user enables "Settings -> Show Next" again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487728] Plasma panel/widgets freeze randomly with explicit sync, can be unfreezed by going into overview
https://bugs.kde.org/show_bug.cgi?id=487728 --- Comment #1 from kodatar...@yahoo.com --- Just wanted to make a note that I was able to test other compositors which do have explicit sync(gnome & gamescope) in their own separate session and neither exhibit any problems. This was the reason I opened a different thread from my previous one and more on what the issue is more correctly. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 487733] New: Make annotations compatible with other readers like Kobo Elipsa and Google Drive
https://bugs.kde.org/show_bug.cgi?id=487733 Bug ID: 487733 Summary: Make annotations compatible with other readers like Kobo Elipsa and Google Drive Classification: Applications Product: okular Version: 24.05.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: elia...@protonmail.ch Target Milestone: --- SUMMARY Currently it is possible to read annotations done on Kobo Elipsa in Okular. But the other way around is not true. Most annotations done in Okular are invisible to Kobo Elipsa. The only visible annotation is the free-line. Why not make other kinds of annotations (highlights, text additions) compatible as well? It would be very useful if they were. Or is it something that Kobo needs to implement? -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 485810] Videos played in a detached window
https://bugs.kde.org/show_bug.cgi?id=485810 --- Comment #4 from wheniwasatrues...@gmail.com --- (In reply to wheniwasatruestar from comment #2) > Same on my side too. > PlasmaTube version: 24.02.2 > > Operating System: Archlinux > KDE Plasma Version: 6.0.4 > KDE Framework Version: 6.2.0 > Qt Version: 6.7.0 > Kernel Version: 6.8.9-arch1-2 (64 bit) > Graphics Platform: Wayland > Processors: 12x AMD Ryzen 5 7640U w/ Radeon 760M Graphics > Memory: 14.9 GiB of Ram Still the same on 24.05.0 of PlasmaTube. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487728] New: Plasma panel/widgets freeze randomly with explicit sync, can be unfreezed by going into overview
https://bugs.kde.org/show_bug.cgi?id=487728 Bug ID: 487728 Summary: Plasma panel/widgets freeze randomly with explicit sync, can be unfreezed by going into overview Classification: Plasma Product: kwin Version: 6.0.5 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kodatar...@yahoo.com Target Milestone: --- SUMMARY the plasma panel and widgets would randomly freeze when kwin has explicit sync patched in STEPS TO REPRODUCE 1. use kwin with explicit sync, panel & widgets would randomly freeze, open overview a few times to unfreeze OBSERVED RESULT panel & widgets - random freeze EXPECTED RESULT To continue working correctly SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.2-273-tkg-eevdf (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor Memory: 31,3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2 Kwin patched with explicit sync from aur: https://aur.archlinux.org/packages/kwin-explicit-sync On a side note: this also affects 6.1 beta as well -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 283373] digiKam shows splashscreen but won't start with no crash report generated.
https://bugs.kde.org/show_bug.cgi?id=283373 caulier.gil...@gmail.com changed: What|Removed |Added Summary|digikam shows splashscreen, |digiKam shows splashscreen |but won't start - no crash |but won't start with no |report genereted|crash report generated. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 283373] digikam shows splashscreen, but won't start - no crash report genereted
https://bugs.kde.org/show_bug.cgi?id=283373 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466031] Per-virtual-desktop tiling layouts
https://bugs.kde.org/show_bug.cgi?id=466031 kv3f5...@mailer.me changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466019 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466019] Allow saving tiling layouts
https://bugs.kde.org/show_bug.cgi?id=466019 kv3f5...@mailer.me changed: What|Removed |Added CC||kv3f5...@mailer.me See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466031 --- Comment #6 from kv3f5...@mailer.me --- I think that implicitly saving the layout per activity / virtual desktop would be the way to go. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 107302] Per-screen virtual desktops
https://bugs.kde.org/show_bug.cgi?id=107302 kv3f5...@mailer.me changed: What|Removed |Added CC||kv3f5...@mailer.me -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466031] Per-virtual-desktop tiling layouts
https://bugs.kde.org/show_bug.cgi?id=466031 kv3f5...@mailer.me changed: What|Removed |Added CC||kv3f5...@mailer.me --- Comment #8 from kv3f5...@mailer.me --- The tiling setup is also the same in all activities. We might want to differentiate tilings in those at least, as they represent a stronger division in general. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25
https://bugs.kde.org/show_bug.cgi?id=487370 --- Comment #16 from caulier.gil...@gmail.com --- Hi Maik, Note : The build with an older revision and Qt 6.7.0 under Windows pass, this is not a problem. The build with your last commits is under progress. I hope that upload will work as expected (i'm not at home today). Many times, rsync from MSYS2 close the connection socket, and i don't know why. I write a "try again" loop in the script in this case, but it's do not improve well the situation. I think the rsync Windows port is not perfect. Using a native CLI alternative to rsync under Windows is the hell... Gilles -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 487650] Partition Manager fails to read MS-DOS partition tables
https://bugs.kde.org/show_bug.cgi?id=487650 --- Comment #10 from a...@absolutelyfree.me --- I cloned the master branch, built, and installed and now everything seems to be working correctly on my end as well! I tested with disks that had their partition table and partitions created by KDE Partition Manager as well as by MS-DOS 6.22, both are working as expected. Thank you for your help with this! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 487723] make adding text UI a little easier to use
https://bugs.kde.org/show_bug.cgi?id=487723 imthenacho...@gmail.com changed: What|Removed |Added CC||imthenacho...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 487721] being able to change color of form field text
https://bugs.kde.org/show_bug.cgi?id=487721 imthenacho...@gmail.com changed: What|Removed |Added CC||imthenacho...@gmail.com Blocks|487723 | Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=487723 [Bug 487723] make adding text UI a little easier to use -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 487723] make adding text UI a little easier to use
https://bugs.kde.org/show_bug.cgi?id=487723 imthenacho...@gmail.com changed: What|Removed |Added Depends on|487721 | Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=487721 [Bug 487721] being able to change color of form field text -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 487721] being able to change color of form field text
https://bugs.kde.org/show_bug.cgi?id=487721 imthenacho...@gmail.com changed: What|Removed |Added Blocks||487723 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=487723 [Bug 487723] make adding text UI a little easier to use -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 487723] New: make adding text UI a little easier to use
https://bugs.kde.org/show_bug.cgi?id=487723 Bug ID: 487723 Summary: make adding text UI a little easier to use Classification: Applications Product: okular Version: 23.08.5 Platform: Kubuntu OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: imthenacho...@gmail.com CC: okular-de...@kde.org Depends on: 487721 Target Milestone: --- Okular is a fantastic PDF reader/tool. I find the text entry (typewriter) UI a little clunky. You have to draw a box and then enter text in a pop-up that gets embedded in. I think it would be a lot cleaner if you can just click where you want to start typing and then type live in the document. That way you can get a better sense of placement and what not. Kind of how Adobe PDF or PDF Studio do it. Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=487721 [Bug 487721] being able to change color of form field text -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 487721] New: being able to change color of form field text
https://bugs.kde.org/show_bug.cgi?id=487721 Bug ID: 487721 Summary: being able to change color of form field text Classification: Applications Product: okular Version: 23.08.5 Platform: Kubuntu OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: imthenacho...@gmail.com Target Milestone: --- This is just a small feature request. I think it would be great if we could change the font/text color of form fields. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487715] alt-d-s shortcut to open desktop settings does nothing until you click on the desktop once (Plasma 6.0.90)
https://bugs.kde.org/show_bug.cgi?id=487715 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 487566] Kcalc doesn't chain result into next calculation anymore
https://bugs.kde.org/show_bug.cgi?id=487566 --- Comment #11 from fanzhuyi...@gmail.com --- (In reply to Gabriel Barrantes from comment #10) > (In reply to Kerr Avon from comment #8) > > I agree with the comments. Please revert back to the previous behaviour or > > allow it in configuration settings. The input text is also too small for my > > eyesight and I don't see any setting to change that either. It was perfect > > before, so not sure why the UX changes were necessary. > > check the proposed behavior attachment, is that what you all are looking for? > ps: the font size thing will be fixed eventually... Looks good to me! You could also tag the usability/vdg team in the MR to get their feedback. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 196627] Right-click context menu for the Albums View.
https://bugs.kde.org/show_bug.cgi?id=196627 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.4.0 Summary|Right-click context menu|Right-click context menu |for the Albums GUI |for the Albums View. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 90040] Copy image location from right menu.
https://bugs.kde.org/show_bug.cgi?id=90040 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.4.0 CC||caulier.gil...@gmail.com Summary|copy image location from|Copy image location from |right menu |right menu. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 172776] Usability: Combine Edit and Album menus, and other ideas...
https://bugs.kde.org/show_bug.cgi?id=172776 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 166580] Interface configuration options for friendlier digiKam.
https://bugs.kde.org/show_bug.cgi?id=166580 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Interface configuration |Interface configuration |options for friendlier |options for friendlier |Digikam |digiKam. Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 210836] Menu items have all words capitalized.
https://bugs.kde.org/show_bug.cgi?id=210836 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Menu items have all words |Menu items have all words |capitalized |capitalized. CC||caulier.gil...@gmail.com Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 91541] Remove duplicate entry from Tools menu.
https://bugs.kde.org/show_bug.cgi?id=91541 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Remove duplicate entry from |Remove duplicate entry from |Tools menu |Tools menu. Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 154971] Closed menu-bar and toolbar can only be re-activated in config-file.
https://bugs.kde.org/show_bug.cgi?id=154971 caulier.gil...@gmail.com changed: What|Removed |Added Summary|closed menubar and toolbar |Closed menu-bar and toolbar |can only be re-activated in |can only be re-activated in |config-file |config-file. CC||caulier.gil...@gmail.com Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 108078] Failed to download file from Camera/Browse Directory Menu.
https://bugs.kde.org/show_bug.cgi?id=108078 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Summary|Failed to download file |Failed to download file |from Camera/Browse |from Camera/Browse |Directory Menu |Directory Menu. Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 145082] F10 and Ctrl-F10 don't focus menu and context menu.
https://bugs.kde.org/show_bug.cgi?id=145082 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Version Fixed In||8.4.0 Summary|F10 and Ctrl-F10 don't |F10 and Ctrl-F10 don't |focus menu and context menu |focus menu and context ||menu. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 144648] Ctrl-M doesn't toggle appearance of menu bar.
https://bugs.kde.org/show_bug.cgi?id=144648 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Version Fixed In||8.4.0 Summary|Ctrl-M doesn't toggle |Ctrl-M doesn't toggle |appearance of menu bar |appearance of menu bar. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 177231] Rotate context menu in view mode.
https://bugs.kde.org/show_bug.cgi?id=177231 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.4.0 Summary|Rotate context menu in view |Rotate context menu in view |mode|mode. CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 91840] "Generate all thumbnails" menu option.
https://bugs.kde.org/show_bug.cgi?id=91840 caulier.gil...@gmail.com changed: What|Removed |Added Summary|"Generate all thumbnails" |"Generate all thumbnails" |menu option |menu option. Version Fixed In||8.4.0 CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 111798] Disable "Remove tag" entry from the menu when none tag is assigned.
https://bugs.kde.org/show_bug.cgi?id=111798 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Disable "Remove tag" entry |Disable "Remove tag" entry |from the menu when none tag |from the menu when none tag |is assigned |is assigned. CC||caulier.gil...@gmail.com Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 103246] Usability: Clean up thumbnail Right Mouse Button menu.
https://bugs.kde.org/show_bug.cgi?id=103246 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Version Fixed In||8.4.0 Summary|Usability: Clean up |Usability: Clean up |thumbnail RMB menu |thumbnail Right Mouse ||Button menu. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 96369] Album menu to import images.
https://bugs.kde.org/show_bug.cgi?id=96369 caulier.gil...@gmail.com changed: What|Removed |Added Summary|album menu to import images |Album menu to import ||images. Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 94539] Add keyboard shortcuts (bindings) to menu functions in digikam picture viewer.
https://bugs.kde.org/show_bug.cgi?id=94539 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Summary|add keyboard shortcus |Add keyboard shortcuts |(bindings) to menu |(bindings) to menu |functions in digikam|functions in digikam |picture viewer |picture viewer. Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 114506] Wrong menu label for "Set as Tag Thumbnail" Drag and Drop operation.
https://bugs.kde.org/show_bug.cgi?id=114506 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.4.0 CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 113913] Image Editor: disable "remove tags" menu item when there are no common tags.
https://bugs.kde.org/show_bug.cgi?id=113913 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 91217] Right Mouse Button click on album does not give the album the selection focus.
https://bugs.kde.org/show_bug.cgi?id=91217 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.4.0 Summary|RMB click on album does not |Right Mouse Button click on |give the album the |album does not give the |selection focus |album the selection focus. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 113808] Tags view: can not change the tag icon with the contextual menu "Edit Tag Properties..." after setting a photo as tag thumbnail.
https://bugs.kde.org/show_bug.cgi?id=113808 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 110393] Context menu image rotate does not work as expected.
https://bugs.kde.org/show_bug.cgi?id=110393 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.4.0 Summary|context menu image rotate |Context menu image rotate |does not work as expected |does not work as expected. CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 114507] After modifying the digiKam main toolbar, all the tools menu have disappeared.
https://bugs.kde.org/show_bug.cgi?id=114507 caulier.gil...@gmail.com changed: What|Removed |Added Summary|After modifying the DigiKam |After modifying the digiKam |main toolbar, all the tools |main toolbar, all the tools |menu have disappeared. |menu have disappeared. Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 98524] digiKam crashes when right clicking image in image editor.
https://bugs.kde.org/show_bug.cgi?id=98524 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Digikam 0.7.2 cvs crashes |digiKam crashes when right |when right clicking image |clicking image in image |in image editor |editor. Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483509] system monitor widget horizontal bars fails to display more than 1 sensor when in panel
https://bugs.kde.org/show_bug.cgi?id=483509 --- Comment #6 from b...@alday.de --- Sorry, i forgot about the system details: Operating System: Manjaro Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.10.0-rc1-273-tkg-eevdf (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 31.0 GiB of RAM Graphics Processor: AMD Radeon RX 5600 XT Manufacturer: ASRock Product Name: B650M PG Lightning I also tried the 6.6 LTS kernel and default system theme with all the available alternative panels. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483509] system monitor widget horizontal bars fails to display more than 1 sensor when in panel
https://bugs.kde.org/show_bug.cgi?id=483509 b...@alday.de changed: What|Removed |Added CC||b...@alday.de --- Comment #5 from b...@alday.de --- Same here on Manjaro rolling release. With the change to Plasma 6 all Systemmonitor-Panel Apps decreased their size. I am on a 50" TV as display and when i use more than 2 cpu-sensors the size (height and width) is unusable. With all 12 cpu-sensors the size is so small on the 50" display, that i can see tiny pixels at the base when the cpu is under load. The same goes for the network sensors, they reduced their width by at least 50%, while still working in height. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487718] New: dolphin crashing on double tapping the spacebar.
https://bugs.kde.org/show_bug.cgi?id=487718 Bug ID: 487718 Summary: dolphin crashing on double tapping the spacebar. Classification: Applications Product: dolphin Version: 24.02.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: saurabh2...@glbajajgroup.org CC: kfm-de...@kde.org Target Milestone: --- Created attachment 169925 --> https://bugs.kde.org/attachment.cgi?id=169925=edit screen recording on double tapping the spacebar OS: Fedora Linux 40 (KDE Plasma) x86_64 Host: Inspiron 3584 Kernel: Linux 6.8.10-300.fc40.x86_64 Uptime: 2 hours, 9 mins Packages: 2738 (rpm), 13 (flatpak) Shell: bash 5.2.26 Display (AUO38ED): 1920x1080 @ 60Hz (as 960x540) [Built-in] DE: KDE Plasma 6.0.5 WM: KWin (Wayland) WM Theme: Breeze Theme: Breeze (Dark) [QT], Breeze [GTK3] Icons: breeze-dark [QT], breeze-dark [GTK3/4] Font: Noto Sans (10pt) [QT], Noto Sans (10pt) [GTK3/4] Cursor: Adwaita (24px) Terminal: konsole 24.2.2 CPU: Intel(R) Core(TM) i3-7020U (4) @ 2.30 GHz GPU: Intel HD Graphics 620 @ 1.00 GHz [Integrated] Memory: 4.92 GiB / 7.65 GiB (64%) Swap: 754.25 MiB / 7.65 GiB (10%) Disk (/): 59.60 GiB / 231.30 GiB (26%) - btrfs Local IP (wlp2s0): 192.168.136.223/24 * Battery: 26% [Discharging] Locale: en_US.UTF-8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487717] New: When adding a second screen with greater resolution than first screen, desktop wallpaper is constrained to smaller resolution of first monitor
https://bugs.kde.org/show_bug.cgi?id=487717 Bug ID: 487717 Summary: When adding a second screen with greater resolution than first screen, desktop wallpaper is constrained to smaller resolution of first monitor Classification: Plasma Product: kwin Version: git-stable-Plasma/6.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: briguy...@live.com Target Milestone: --- Created attachment 169924 --> https://bugs.kde.org/attachment.cgi?id=169924=edit This is a 2560x1440 resolution monitor, but wallpaper is constrained to 1920x1080. Black space should not be here and wallpaper should be full screen SUMMARY I have two monitors. Primary is 1920x1080, secondary is 2560x1440. I have both monitors using the same wallpaper settings. If I start my PC and only the single Primary monitor is enabled, and then at the desktop I turn on my second monitor, instead of scaling the wallpaper and desktop to 2560x1440, it instead thinks the background of the desktop should be 1920x1080. The taskbar extends across the entire screen as expected, and I can even move my cursor and desktop icons into the "black" area as shown in the screenshot. I am unable to right click to invoke the desktop context menu in the black space. Changing resolution and reverting keeps the 1920x1080 limit and does not fix it. STEPS TO REPRODUCE 1. Have two monitors, Monitor A 1920x1080 and Monitor B 2560x1440 2. Only have Monitor A turned on, and start PC and go to the desktop 3. While at the desktop, turn on Monitor B 4. Observe the desktop background of Monitor B OBSERVED RESULT Wallpaper and desktop background remains capped at 1920x1080 even on Monitor B which has a resolution of 2560x1440 EXPECTED RESULT Wallpaper and desktop update with each monitors resolution, even if they are added after you get to the desktop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.1 Beta 1 (available in About System) KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION Kernel: 6.9.2-arch1-1 Graphics Platform: Wayland GPU: Nvidia GPU Driver: 555.42.02-1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487664] [BUG] Panel being drawn over desktop folder labels
https://bugs.kde.org/show_bug.cgi?id=487664 jman12...@live.com changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487664] [BUG] Panel being drawn over desktop folder labels
https://bugs.kde.org/show_bug.cgi?id=487664 --- Comment #2 from jman12...@live.com --- (In reply to David Edmundson from comment #1) > We have our own panel avoidance, rather than going through _NET_WORKAREA as > that is not screen specific and therefore not usable enough. > > This is a third party product breaking things, sorry. > Maybe on wayand we can do something better. _NET_WORKAREA was just a guess. But KDE already has correct per screen information as when a window is maximized, it will not go into 'third-party' docks area. Therefore, the correct screen data already exists somewhere. This is not a problem specific with tint2. I don't use tint2, I only used it as it's common to have on different distro's. Every panel that is attempted to be used will have this problem. Please re-open as a bug withing KDE as this is definitely not a "a third party product breaking things". The code that lays out folders on the desktop is simply wrong. I understand this is annoying and somewhat hard to fix. If you need help. Let me know. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 487652] Misplacement of "Screen Edges" page in "Mouse & Touchpad" section of System Settings
https://bugs.kde.org/show_bug.cgi?id=487652 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 479548] Problem with key 6
https://bugs.kde.org/show_bug.cgi?id=479548 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||fanzhuyi...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #2 from fanzhuyi...@gmail.com --- (In reply to Thierry GRAUSS from comment #1) > The problem was with deadkeys keymap. When using french qwerty with deadkey > keymap, I have this behavior. If I select US international with Altgr > deadkey I don't have any problem anymore. > I had the problem with Kcalc but also with Signal and Smarthome3D. Is the deadkeys keymap a 3rd party software? If this problem also appears in other software, then it is very unlikely that this is actually a kcalc issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487713] New: Panel doesn't work occasionally when not present on primary display
https://bugs.kde.org/show_bug.cgi?id=487713 Bug ID: 487713 Summary: Panel doesn't work occasionally when not present on primary display Classification: Plasma Product: plasmashell Version: git-stable-Plasma/6.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: eputty...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 169922 --> https://bugs.kde.org/attachment.cgi?id=169922=edit a video on how the panel responds on different displays SUMMARY The entire panel stops visually updating when on a non-primary display with a fullscreen or maximized window on the main display without a panel. It's possible that this only happens on wayland with nvidia gpus, I haven't tested X11, but it's consistent at least. STEPS TO REPRODUCE 1. Have 2 displays connected and a panel only on one of them 2. Set the primary display to not have a panel 3. Maximize a window(firefox is most consistent) on the primary display 4. the panel still accepts input, but doesn't update until the window is no longer maximized or fullscreen. OBSERVED RESULT Panel seemingly unresponsive or broken when on non-primary display EXPECTED RESULT panel to function properly on all displays regardless of if there is a panel on the primary display SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux TKG kernel 6.9.1 on Arch Linux (available in About System) KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION Nvidia Driver 555.42.02 -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 487659] cant type as .4, must be 0.4.
https://bugs.kde.org/show_bug.cgi?id=487659 fanzhuyi...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Summary|Pressing enter to get the |cant type as .4, must be |answer, then trying to |0.4. |directly +-/* from the old | |number, the old number | |isn't fetched. Also cant| |type as .4, must be 0.4.| CC||fanzhuyi...@gmail.com Status|REPORTED|CONFIRMED --- Comment #3 from fanzhuyi...@gmail.com --- The first issue is being tracked in BUG 487566, so I modified the title to be about the decimal point -- cannot input those as .xyz. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487703] workspace.activateWindow missing
https://bugs.kde.org/show_bug.cgi?id=487703 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 487709] When Konsole calls firefox the text is uneven.
https://bugs.kde.org/show_bug.cgi?id=487709 fanzhuyi...@gmail.com changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||fanzhuyi...@gmail.com Status|REPORTED|NEEDSINFO --- Comment #1 from fanzhuyi...@gmail.com --- Does this only happen when you launch firefox from konsole, but not from other terminal apps? It is very unlikely that a konsole bug could be causing the issue here. Maybe you have some special environment variables set in the konsole session that is causing the issue? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487710] A way to make 3 finger gesture on touchpad not 1:1 for VD switching.
https://bugs.kde.org/show_bug.cgi?id=487710 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487710] New: A way to make 3 finger gesture on touchpad not 1:1 for VD switching.
https://bugs.kde.org/show_bug.cgi?id=487710 Bug ID: 487710 Summary: A way to make 3 finger gesture on touchpad not 1:1 for VD switching. Classification: Plasma Product: kwin Version: 6.0.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Gestures Assignee: kwin-bugs-n...@kde.org Reporter: matasniewulis2...@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 *** SUMMARY A way to make 3 finger touchpad gesture faster or more reliable? I am using OpenSUSE on my ThinkPad T14 G2 AMD with KDE on Wayland and the touchpad gestures are set up in a way that three finger up/down/left/right switches the virtual desktops by default. I use a top/bottom virtual desktops and when I use the three finger gesture to switch between them, I found that I can't just "flick" my fingers to switch - since it is a 1:1 gesture I have to travel some distance with my fingers til it completes the switching. Is there a way to speed it up or make it not 1:1 for just this particular gesture? For example simple 2 finger scroll on desktop achieves what i want - it switches instantly, but that ofcourse works only on the desktop, not when I am using another app. I use a remote desktop on one VT and my browser as well as terminal and ssh sessions on another VT, sometimes i need quick switching. I would like to avoid using a keyboard shortcut and just use the touchpad gesture. Is there a way to configure it the way i described it? STEPS TO REPRODUCE 1. Use KDE on Wayland with 3 finger touchpad gesture to switch VDs 2. Scroll with 3 fingers (slow gesture) 3. Scroll with 2 fingers on desktop (quick gesture) OBSERVED RESULT As it's a 1:1 gesture it requires longer movement and travel to trigger the switch EXPECTED RESULT Quick switching - identical to scrolling on the desktop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Opensuse Tumbleweed on latest Plasma 6.0.5 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 487508] Max Volume Seems to Be 153% Now Instead of a 150%
https://bugs.kde.org/show_bug.cgi?id=487508 dmatteo...@gmail.com changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||dmatteo...@gmail.com Ever confirmed|0 |1 --- Comment #1 from dmatteo...@gmail.com --- Can confirm the issue. Operating System: Arch Linux KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.2-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 487553] Reordering Plasma Search Plugins is Kinda Stuttery Now
https://bugs.kde.org/show_bug.cgi?id=487553 dmatteo...@gmail.com changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||dmatteo...@gmail.com Ever confirmed|0 |1 --- Comment #1 from dmatteo...@gmail.com --- Can confirm the issue. Operating System: Arch Linux KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.2-arch1-1 (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 487650] Partition Manager fails to read MS-DOS partition tables
https://bugs.kde.org/show_bug.cgi?id=487650
--- Comment #5 from a...@absolutelyfree.me ---
Sure thing:
> sudo sfdisk --json /dev/sda
{
"partitiontable": {
"label": "dos",
"id": "0x",
"device": "/dev/sda",
"unit": "sectors",
"sectorsize": 512,
"partitions": [
{
"node": "/dev/sda1",
"start": 63,
"size": 1012977,
"type": "6",
"bootable": true
}
]
}
}
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 487640] In Edit Mode, Panel Settings obscures settings popups for elements on the panel
https://bugs.kde.org/show_bug.cgi?id=487640 dmatteo...@gmail.com changed: What|Removed |Added CC||dmatteo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 487708] akregator 6.1.0 does not apply dark theme to the article content pane although the desktop uses a Dark Theme.
https://bugs.kde.org/show_bug.cgi?id=487708 --- Comment #1 from whatifgodwasoneo...@hotmail.com --- (In reply to whatifgodwasoneofus from comment #0) > QTWEBENGINE_CHROMIUM_FLAGS="--blink-settings=darkModeEnabled=default" Sorry, the correct cmdline for the workaround is: QTWEBENGINE_CHROMIUM_FLAGS="--blink-settings=darkModeEnabled=true" akregator -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 487708] akregator 6.1.0 does not apply dark theme to the article content pane although the desktop uses a Dark Theme.
https://bugs.kde.org/show_bug.cgi?id=487708 whatifgodwasoneo...@hotmail.com changed: What|Removed |Added CC||whatifgodwasoneofus@hotmail ||.com Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 487708] New: akregator 6.1.0 does not apply dark theme to the article content pane although the desktop uses a Dark Theme.
https://bugs.kde.org/show_bug.cgi?id=487708 Bug ID: 487708 Summary: akregator 6.1.0 does not apply dark theme to the article content pane although the desktop uses a Dark Theme. Classification: Applications Product: akregator Version: 6.1.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: internal browser Assignee: kdepim-b...@kde.org Reporter: whatifgodwasoneo...@hotmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Set the desktop's them to Breeze Dark 2. open Akregator, select a feed's article OBSERVED RESULT The article content is NOT rendered using the dark theme. EXPECTED RESULT The article content must be rendered using the dark theme. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION If I launch akregator forcing the dark mode via QT Web Engine env var, it works as expected: ``` QTWEBENGINE_CHROMIUM_FLAGS="--blink-settings=darkModeEnabled=default" akregator ``` However, it should work without this hack. My desktop theme changes during the day (via koi), and I'd like to enjoy this feature "dynamically". This is a long-awaited feature for akregator, which is available starting from v6.1.5 (24.05.0). Maybe it has not been thoroughly tested on all platforms? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 487706] New: Bug spotted with the "Enable Presentation mode" toggle
https://bugs.kde.org/show_bug.cgi?id=487706 Bug ID: 487706 Summary: Bug spotted with the "Enable Presentation mode" toggle Classification: Plasma Product: Powerdevil Version: 6.0.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dclark16+bugs@gmail.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 169920 --> https://bugs.kde.org/attachment.cgi?id=169920=edit Screenshot showing the problem *** 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 *** SUMMARY Bug spotted with the "Enable Presentation mode" toggle in the "Display Configuration" applet. STEPS TO REPRODUCE 1. Run in terminal #!/bin/bash while true do clear busctl --user call org.kde.Solid.PowerManagement.PolicyAgent /org/kde/Solid/PowerManagement/PolicyAgent org.kde.Solid.PowerManagement.PolicyAgent ListInhibitions sleep 10 done 2. Toggle the "Enable Presentation Mode" in the "Display Configuration" applet several times OBSERVED RESULT For each toggle on and off there will be a new entry in the terminal window. Even though the toggle is off the presentation mode doesn't actually get disabled and the list of them continues to grow with each toggle. EXPECTED RESULT When toggled on there should be a single entry for the presentation mode, which should prevent screen locking and the device from going to sleep. Once toggled back off the device should follow the configure power profile and the presentation mode removed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro 24.0 (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2 Qt Version: 6.7.1 ADDITIONAL INFORMATION Had been confirmed by other people. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417960] [Enhancement]. In Batch Queue Manager - ability to display preview image
https://bugs.kde.org/show_bug.cgi?id=417960 --- Comment #3 from caulier.gil...@gmail.com --- Git commit cc49d320a09b526a5b56bcd42030c84d03253882 by Gilles Caulier. Committed on 28/05/2024 at 18:24. Pushed by cgilles into branch 'master'. export BqmInfoIface class to 3rd party plugins. Related: bug 396743 M +1-0core/app/DigikamExportAPI.cmake https://invent.kde.org/graphics/digikam/-/commit/cc49d320a09b526a5b56bcd42030c84d03253882 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396743] Adding a way to preview assigned tools output before running the batch queue
https://bugs.kde.org/show_bug.cgi?id=396743 --- Comment #3 from caulier.gil...@gmail.com --- Git commit cc49d320a09b526a5b56bcd42030c84d03253882 by Gilles Caulier. Committed on 28/05/2024 at 18:24. Pushed by cgilles into branch 'master'. export BqmInfoIface class to 3rd party plugins. Related: bug 417960 M +1-0core/app/DigikamExportAPI.cmake https://invent.kde.org/graphics/digikam/-/commit/cc49d320a09b526a5b56bcd42030c84d03253882 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417960] [Enhancement]. In Batch Queue Manager - ability to display preview image
https://bugs.kde.org/show_bug.cgi?id=417960 --- Comment #2 from caulier.gil...@gmail.com --- Git commit f46339f8fb35b419c13ab2d902983284aa4bdd0e by Gilles Caulier. Committed on 28/05/2024 at 18:20. Pushed by cgilles into branch 'master'. Add new Batch queue Manager customized version of DInfoInterface class for plugins. 3 new methods are available to get the list of image patch from the current selected queue. The Goal later is to propose to end-user to reder a preview of an assigned tools list to a set of photo before to run a workflow. Related: bug 396743 M +1-0core/utilities/queuemanager/CMakeLists.txt A +65 -0core/utilities/queuemanager/dplugins/bqminfoiface.cpp [License: GPL(v2.0+)] A +63 -0core/utilities/queuemanager/dplugins/bqminfoiface.h [License: GPL(v2.0+)] M +2-2core/utilities/queuemanager/dplugins/dpluginbqm.cpp M +2-1core/utilities/queuemanager/dplugins/dpluginbqm.h M +7-1core/utilities/queuemanager/main/queuemgrwindow.cpp M +16 -13 core/utilities/queuemanager/main/queuemgrwindow.h M +4-4core/utilities/queuemanager/manager/batchtoolsfactory.cpp M +2-2core/utilities/queuemanager/manager/batchtoolsfactory.h M +31 -4core/utilities/queuemanager/views/queuelist.cpp M +11 -1core/utilities/queuemanager/views/queuelist.h M +2-2core/utilities/queuemanager/views/queuepool.cpp M +13 -13 core/utilities/queuemanager/views/queuepool.h https://invent.kde.org/graphics/digikam/-/commit/f46339f8fb35b419c13ab2d902983284aa4bdd0e -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396743] Adding a way to preview assigned tools output before running the batch queue
https://bugs.kde.org/show_bug.cgi?id=396743 --- Comment #2 from caulier.gil...@gmail.com --- Git commit f46339f8fb35b419c13ab2d902983284aa4bdd0e by Gilles Caulier. Committed on 28/05/2024 at 18:20. Pushed by cgilles into branch 'master'. Add new Batch queue Manager customized version of DInfoInterface class for plugins. 3 new methods are available to get the list of image patch from the current selected queue. The Goal later is to propose to end-user to reder a preview of an assigned tools list to a set of photo before to run a workflow. Related: bug 417960 M +1-0core/utilities/queuemanager/CMakeLists.txt A +65 -0core/utilities/queuemanager/dplugins/bqminfoiface.cpp [License: GPL(v2.0+)] A +63 -0core/utilities/queuemanager/dplugins/bqminfoiface.h [License: GPL(v2.0+)] M +2-2core/utilities/queuemanager/dplugins/dpluginbqm.cpp M +2-1core/utilities/queuemanager/dplugins/dpluginbqm.h M +7-1core/utilities/queuemanager/main/queuemgrwindow.cpp M +16 -13 core/utilities/queuemanager/main/queuemgrwindow.h M +4-4core/utilities/queuemanager/manager/batchtoolsfactory.cpp M +2-2core/utilities/queuemanager/manager/batchtoolsfactory.h M +31 -4core/utilities/queuemanager/views/queuelist.cpp M +11 -1core/utilities/queuemanager/views/queuelist.h M +2-2core/utilities/queuemanager/views/queuepool.cpp M +13 -13 core/utilities/queuemanager/views/queuepool.h https://invent.kde.org/graphics/digikam/-/commit/f46339f8fb35b419c13ab2d902983284aa4bdd0e -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487504] Bar Chart in vertical orientation is completely blank in a horizontal panel.
https://bugs.kde.org/show_bug.cgi?id=487504 bafroomhu...@gmail.com changed: What|Removed |Added CC||bafroomhu...@gmail.com --- Comment #3 from bafroomhu...@gmail.com --- I use line charts for my system monitor widgets, but I also have issues. I have them on a vertical panel, and they simply do not show up after the 6.0.5 update (In Nobara/Fedora 39). I don't know if I can interact with them. Several people I've spoken to have a similar issue. If it's not the same issue i can make a new bug report, but I figured it had something to do with this because of the similarities. I rolled back my system to avoid this issue until it's fixed, so I'm on plasma 6.0.4 KDE frameworks 6.1.0 QT 6.2.2 And it works fine up to this point. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487705] New: Widget customizations do not persist
https://bugs.kde.org/show_bug.cgi?id=487705 Bug ID: 487705 Summary: Widget customizations do not persist Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: hiph...@posteo.de Target Milestone: 1.0 SUMMARY Customizations for a number of widgets do not persist after logout or restart. I do not mean configuration through the "Configure XYZ" window, but customizations like adding a menu item to the favorites or changing which items are pinned in the icons-only task manager. I have noticed the problem with these widgeths: - Application menu - Dashboard - Icons-only task manager There might be more, these are just the ones I noticed. STEPS TO REPRODUCE 1. Create a new panel 2. Add the icons-only task manager widget to it 3. Change the entries of the widget 4. Log out and log back in OBSERVED RESULT The entries are back to what they were by default when the widget was added to the panel. EXPECTED RESULT My own customizations should persist. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Void Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.6.0 ADDITIONAL INFORMATION This happens both under X11 and Wayland. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 487704] New: Unknown error
https://bugs.kde.org/show_bug.cgi?id=487704 Bug ID: 487704 Summary: Unknown error Classification: Applications Product: krita Version: 5.2.2 Platform: Compiled Sources OS: All Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: japochech...@gmail.com Target Milestone: --- Created attachment 169919 --> https://bugs.kde.org/attachment.cgi?id=169919=edit gives an error when rendering animation, regardless of the file size (reinstalling the program did not help) gives an error when rendering animation, regardless of the file size (reinstalling the program did not help) Error occurred on Tuesday, March 26, 2024 at 15:44:13. krita.exe caused a Breakpoint at location 7FFCC124B502 in module KERNELBASE.dll. AddrPC Params 7FFCC124B502 0080 KERNELBASE.dll!wil::details::DebugBreak+0x2 7FFC61F35AAA 0297F93A7210 7FFC61F3BC2B Qt5Core.dll!qt_message_fatal+0xa 7FFC61F36A74 00DB1D5AB850 0297 0297F3371638 Qt5Core.dll!QMessageLogger::fatal+0x72 7FFCA4672F66 0297EDA74780 0297ED8F4038 0297F2C25770 libkritaglobal.dll!kis_assert_common+0x556 7FFCA4673081 7FFC5FAEECB8 libkritaglobal.dll!kis_assert_recoverable+0x11 7FFC5F5FFAF1 0297ED8F4510 0297 0297E2C1 libkritaui.dll!KisClipboard::clipFromKritaLayers+0x251 7FFC5F92399C 0040 0297E2C1 libkritaui.dll!KisPasteActionFactory::run+0x34c 7FFC5F6F66B5 0297809BFC30 7FFCC0DF1699 0040 libkritaui.dll!KisSelectionManager::paste+0x75 7FFC62130CBB 0022 7FFC623188E9 00DB1D5ABC20 Qt5Core.dll!doActivate+0x56b 7FFC5EF23AA4 Qt5Widgets.dll!QAction::activate+0xd4 7FFC5EF238E9 00DB1D5AF660 0297E4A10240 0297E2EBD601 Qt5Widgets.dll!QAction::event+0x19 7FFC5EF2C5A3 0001 Qt5Widgets.dll!QApplicationPrivate::notify_helper+0x103 7FFC5EF2D823 7FFC Qt5Widgets.dll!QApplication::notify+0x1e3 7FFC5F9B7388 0001 libkritaui.dll!KisApplication::notify+0xa8 7FFC620FDFB2 0297E888CB60 002F 0056 Qt5Core.dll!QCoreApplication::notifyInternal2+0x92 7FFC5E816A21 0297E84C8468 7FFC62425250 Qt5Gui.dll!QShortcutMap::dispatchEvent+0x8f1 7FFC5E815D9F Qt5Gui.dll!QShortcutMap::tryShortcut+0x6f 7FFC5E7C98E6 0001 0297E2EBD630 Qt5Gui.dll!QWindowSystemInterface::handleShortcutEvent+0x206 7FFC5E7E68D1 0297E881B540 0297E2C3C840 7FFC61FCD780 Qt5Gui.dll!QGuiApplicationPrivate::processKeyEvent+0xa1 7FFC5E7CD1EA 0297E2C3C910 0024 Qt5Gui.dll!QWindowSystemInterface::sendWindowSystemEvents+0xda 7FFC621520FC 0297F15BA9E0 00DB1D5AF660 Qt5Core.dll!QEventDispatcherWin32::processEvents+0x5c 7FFC61118A35 00DB1D5AF588 7FFC61F49D60 7FFC61FCD780 qwindows.dll!QWindowsGuiEventDispatcher::processEvents+0x15 7FFC620FB236 02970002 02970002 0297E892AB90 Qt5Core.dll!QEventLoop::exec+0x1e6 7FFC620FE54D 00DB1D5AF628 7FFC 00DB1D5AF5F8 Qt5Core.dll!QCoreApplication::exec+0x6d 7FFC6A4655D9 7FF7FD915110 krita.dll!krita_main+0x41a9 7FF7FD9113D6 krita.exe!__tmainCRTStartup+0x276 7FF7FD911156 krita.exe!WinMainCRTStartup+0x16 7FFCC21E7344 KERNEL32.DLL!BaseThreadInitThunk+0x14 7FFCC34826B1 ntdll.dll!RtlUserThreadStart+0x21 7FF7FD91-7FF7FD955000 krita.exe 5.2.2.100 7FFCC343-7FFCC3628000 ntdll.dll 6.2.19041.3996 7FFCC21D-7FFCC228D000 KERNEL32.DLL 6.2.19041.3636 7FFCC116-7FFCC1456000 KERNELBASE.dll6.2.19041.3996 7FFCC0DE-7FFCC0EE ucrtbase.dll 6.2.19041.3636 7FFC6A46-7FFC6AB05000 krita.dll 7FFCBB6C-7FFCBB6CD000 libkritamultiarch.dll 7FFCA641-7FFCA64FF000 libkritaresources.dll 7FFC624A-7FFC62AF8000 libkritaimage.dll 7FFCA467-7FFCA476A000 libkritaglobal.dll 7FFCC22A-7FFCC2A0B000 SHELL32.dll 6.2.19041.4170 7FFCC0AE-7FFCC0B7D000 msvcp_win.dll 6.2.19041.3636 7FFCC312-7FFCC32BE000 USER32.dll6.2.19041.3996
[plasmashell] [Bug 485313] Plasma containment (plus panel) misplaced after interrupting and resuming power to screen (by turning it off or back on again, or unplugging and replugging a USB-C charging
https://bugs.kde.org/show_bug.cgi?id=485313 --- Comment #8 from jy6x2b32p...@yahoo.com --- well, it happened to me again, on 6.0.90 in Gentoo. This time, I have all the data https://bugs.kde.org/show_bug.cgi?id=487699 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487701] New: Plasmashell crash when screen goes blank for a while with Plasma 6.0.90
https://bugs.kde.org/show_bug.cgi?id=487701 Bug ID: 487701 Summary: Plasmashell crash when screen goes blank for a while with Plasma 6.0.90 Classification: Plasma Product: plasmashell Version: git-stable-Plasma/6.1 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: ollil...@unitybox.de Target Milestone: 1.0 *** 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 *** SUMMARY Sometimes when the screen goes blank plasmashell seems to crash, i have firefox, thunderbird and konsole open, it looks like firefox and thunderbird are closed during this crash only konsole is alive on an empty desktop. My second screen is switched off. When i use the command "kstart plasmashell" the shell comes back and my second screen is reactivated, too. STEPS TO REPRODUCE 1. Wait for screen to go blank (Not everytime) 2. Move the mouse to reactivate the screen OBSERVED RESULT Plasmashell, firefox and thunderbird are closed, konsole remains active. EXPECTED RESULT The screen turns on and all my Programs are active SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo 2.14 (available in About System) KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION This bug shows first after the update to Plasma 6.0.90. journalctl --user -r after restarting plasmashell: [code]Mai 28 19:12:15 Cracked xdg-desktop-por[5493]: No skeleton to export Mai 28 19:12:15 Cracked xdg-desktop-por[5493]: Failed to create file chooser proxy: Fehler beim Aufruf von StartServiceByName für org.freedesktop.impl.portal.desktop.kde: Zeitüberschreitung wurde erreicht Mai 28 19:11:50 Cracked xdg-desktop-por[5493]: No skeleton to export Mai 28 19:11:50 Cracked xdg-desktop-por[5493]: Failed to create settings proxy: Fehler beim Aufruf von StartServiceByName für org.freedesktop.impl.portal.desktop.kde: Zeitüberschreitung wurde erreicht Mai 28 19:11:28 Cracked drkonqi-coredump-launcher[5801]: Nothing handled the dump :O Mai 28 19:11:28 Cracked drkonqi-coredump-launcher[5801]: Unable to find file for pid 2109 expected at "kcrash-metadata/firefox.4ed09713e8ef4929a948569943931ce3.2109.ini" Mai 28 19:11:28 Cracked systemd[1105]: Started Launch DrKonqi for a systemd-coredump crash (PID 5466/UID 0). Mai 28 19:11:27 Cracked systemd-coredump[5465]: [] Process 2109 (firefox) of user 1000 dumped core. Mai 28 19:11:27 Cracked systemd-coredump[5465]: elfutils disabled, parsing ELF objects not supported Mai 28 19:11:26 Cracked drkonqi-coredump-launcher[5544]: Nothing handled the dump :O Mai 28 19:11:26 Cracked drkonqi-coredump-launcher[5546]: Nothing handled the dump :O Mai 28 19:11:26 Cracked drkonqi-coredump-launcher[5544]: Unable to find file for pid 5487 expected at "kcrash-metadata/drkonqi.4ed09713e8ef4929a948569943931ce3.5487.ini" Mai 28 19:11:26 Cracked drkonqi-coredump-launcher[5546]: Unable to find file for pid 5517 expected at "kcrash-metadata/xdg-desktop-portal-kde.4ed09713e8ef4929a948569943931ce3.5517.ini" Mai 28 19:11:26 Cracked systemd[1105]: Started Launch DrKonqi for a systemd-coredump crash (PID 5524/UID 0). Mai 28 19:11:26 Cracked systemd[1105]: Started Launch DrKonqi for a systemd-coredump crash (PID 5496/UID 0). Mai 28 19:11:25 Cracked systemd[1105]: Failed to start Xdg Desktop Portal For KDE. Mai 28 19:11:25 Cracked systemd[1105]: plasma-xdg-desktop-portal-kde.service: Failed with result 'core-dump'. Mai 28 19:11:25 Cracked systemd[1105]: plasma-xdg-desktop-portal-kde.service: Main process exited, code=dumped, status=6/ABRT Mai 28 19:11:25 Cracked systemd-coredump[5523]: [] Process 5517 (xdg-desktop-por) of user 1000 dumped core. Mai 28 19:11:25 Cracked systemd-coredump[5523]: elfutils disabled, parsing ELF objects not supported Mai 28 19:11:25 Cracked systemd-coredump[5494]: [] Process 5487 (drkonqi) of user 1000 dumped core. Mai 28 19:11:25 Cracked systemd-coredump[5494]: elfutils disabled, parsing ELF objects not supported Mai 28 19:11:25 Cracked xdg-desktop-portal-kde[5517]: Available platform plugins are: vkkhrdisplay, vnc, linuxfb, xcb, offscreen, minimal, wayland-egl, wayland. Mai 28 19:11:25 Cracked xdg-desktop-portal-kde[5517]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Mai 28 19:11:25 Cracked xdg-desktop-portal-kde[5517]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. Mai 28 19:11:25 Cracked xdg-desktop-portal-kde[5517]: qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform
[plasmashell] [Bug 487699] plasmashell-6.0.90 crashes after screen unlock, on a laptop, with external monitor turned off before screen locked
https://bugs.kde.org/show_bug.cgi?id=487699 --- Comment #1 from jy6x2b32p...@yahoo.com --- Created attachment 169917 --> https://bugs.kde.org/attachment.cgi?id=169917=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487699] New: plasmashell-6.0.90 crashes after screen unlock, on a laptop, with external monitor turned off before screen locked
https://bugs.kde.org/show_bug.cgi?id=487699
Bug ID: 487699
Summary: plasmashell-6.0.90 crashes after screen unlock, on a
laptop, with external monitor turned off before screen
locked
Classification: Plasma
Product: plasmashell
Version: master
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: jy6x2b32p...@yahoo.com
Target Milestone: 1.0
Application: plasmashell (6.0.90)
(Compiled from sources)
Qt Version: 6.7.1
Frameworks Version: 6.2.0
Operating System: Linux 6.9.2-gentoo x86_64
Windowing System: Wayland
Distribution: "Gentoo Linux"
DrKonqi: 6.0.90 [KCrashBackend]
-- Information about the crash:
Laptop with 1. internal display disabled. 2. Lid closed. 3. External display
connected.
External display was turned off, and laptop was left to lock itself.
~8 minutes after locking, external display was turned on and session was
unlocked.
plasmashell briefly disappeared and appeared again after that.
Crash report was generated.
Automatic restart of plasmashell or drkonqi report doesn't happen if laptop
goes to sleep (which happens after display is turned on, if sleep is enabled in
power settings)
Duplicate of https://bugs.kde.org/show_bug.cgi?id=485313, but now with
different, new-er version of plasmashell and more information.
sddm wayland-session logs of the crash:
[20::36:51.811] unknown: FormData.buddyFor must be a direct child of the
attachee. Attachee: QQuickColumnLayout(0x55d27db7a870, parent=0x55d27f250720,
geometry=0,0 0x0), buddyFor: TextField_QMLTYPE_99(0x55d27e468ce0,
parent=0x55d27e25b300, geometry=0,0 0x0)
xsettingsd: Reloading configuration
xsettingsd: Loaded 20 settings from
/home/nho/.config/xsettingsd/xsettingsd.conf
[20::59:20.877] unknown: Creating a fake screen in order for Qt not to crash
[20::59:20.877] unknown: Creating a fake screen in order for Qt not to crash
[20::59:20.877] unknown: Creating a fake screen in order for Qt not to crash
[20::59:20.877] unknown: Creating a fake screen in order for Qt not to crash
[20::59:20.877] unknown: Creating a fake screen in order for Qt not to crash
[20::59:20.877] unknown: Creating a fake screen in order for Qt not to crash
[20::59:20.877] unknown: Creating a fake screen in order for Qt not to crash
[20::59:20.877] unknown: Creating a fake screen in order for Qt not to crash
[20::59:20.877] unknown: Creating a fake screen in order for Qt not to crash
[20::59:20.877] unknown: Creating a fake screen in order for Qt not to crash
[20::59:20.877] unknown: removing output "HDMI-A-1"
[20::59:20.878] unknown: Creating a fake screen in order for Qt not to crash
[20::59:20.878] unknown: handleScreenAdded QScreen(0x56002e8efdd0, name="")
QRect(0,0 0x0)
[20::59:20.878] unknown: Creating a fake screen in order for Qt not to crash
[20::59:20.878] unknown: handleScreenRemoved QScreen(0x56002dc73fc0,
name="HDMI-A-1")
[20::59:20.883] unknown:
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:237:17:
Unable to assign [undefined] to bool
[20::59:20.883] unknown:
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:366:21:
Unable to assign [undefined] to bool
[20::59:20.883] unknown: Exposed with no visual parent. Window positioning
broken.
[20::59:20.884] unknown: Exposed with no visual parent. Window positioning
broken.
[20::59:20.886] unknown: Exposed with no visual parent. Window positioning
broken.
[20::59:20.887] unknown: handleScreenAdded QScreen(0x56002f721bc0,
name="eDP-1") QRect(0,0 1536x864)
[20::59:20.887] unknown: handleOutputOrderChanged QList("eDP-1")
[20::59:20.887] unknown: screenOrderChanged, old order: QList() new order:
QList(QScreen(0x56002f721bc0, name="eDP-1"))
[20::59:20.899] unknown:
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:24:1:
QML ContainmentItem: Cannot anchor to an item that isn't a parent or sibling.
[20::59:20.899] unknown:
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:24:1:
QML ContainmentItem: Cannot anchor to an item that isn't a parent or sibling.
[20::59:20.899] unknown:
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:24:1:
QML ContainmentItem: Cannot anchor to an item that isn't a parent or sibling.
[20::59:20.899] unknown:
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:24:1:
QML ContainmentItem: Cannot anchor to an item that isn't a parent or sibling.
[20::59:20.903] unknown: handleScreenRemoved QScreen(0x56002e8efdd0, name="")
[20::59:20.904] unknown: Initializing
"/usr/lib64/qt6/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
[20::59:20.906] unknown: Initializing
[kwin] [Bug 487697] New: Enabling adaptive sync causes stuttering and some sort of flickering.
https://bugs.kde.org/show_bug.cgi?id=487697 Bug ID: 487697 Summary: Enabling adaptive sync causes stuttering and some sort of flickering. Classification: Plasma Product: kwin Version: git-stable-Plasma/6.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: forum.z8...@dralias.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 *** SUMMARY When enabling adaptive sync a lot of things on the desktop start stuttering in a way that looks like flicker because the brightness / colour changes. This is happening on 6.0.5 stable and on 6.1 beta installed via the kde-unstable Arch repo. STEPS TO REPRODUCE 1. Enable adaptive sync (setting it to always makes it easier to get these situations). 2. Just do nothing. 3. See the screen flicker. OBSERVED RESULT It feels a lot like the refresh rate of the display as a whole is being reduced. While the display is running smoothly with 200 Hz, when I enter fullscreen in VLC for example it feels a lot more like the cursour moves at around 60 Hz. Also when on the desktop moving the cursour slowly makes the flicker go away but as soon as I move the cursour too fast it comes back again in certain applications. Other applications like Firefox are smooth no matter the cursour speed as long as it is moving. Also typing insider Firefox gets rid of the flicker, I'm fairly certain that is because of a spinner animation from LanguageTool inside textboxes as that would cause the refresh rate to stay high I guess. EXPECTED RESULT Everything should be smooth as the refresh rate should only be reduced if there is nothing on the desktop requesting a higher refresh rate. So for example a cursour and the animations of VLC should increase the refresh rate to 200 Hz instead of staying at whatever the framerate of the video playing is. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 6.9.2-2-cachyos Mesa: 24.0.1-1 KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION I am aware that this might be a duplicate. However, the other issues are either with older versions, with the Nvidia driver, or markes as fixed upstream so this might still add value. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487695] New: Windows always open on all activities since 6.0.5 - also can't move windows to other activities
https://bugs.kde.org/show_bug.cgi?id=487695 Bug ID: 487695 Summary: Windows always open on all activities since 6.0.5 - also can't move windows to other activities Classification: Plasma Product: kwin Version: 6.0.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: activities Assignee: kwin-bugs-n...@kde.org Reporter: bastimeyer...@gmail.com Target Milestone: --- SUMMARY Since 6.0.5, launching any kind of application results in the app's windows always being visible on all activities. This was not the case on 6.0.4. In addition, windows can't be moved to other activities anymore. I've already reported BUG #483148 in the past, which broke moving windows to other activities via plasma's task manager when trying to move the window for the first time. This one is now fully broken. STEPS TO REPRODUCE 1. Have more than one activity set up 2. Don't have any special window rules defined 3. Open any kind of application 4. Switch to a different activity OBSERVED RESULT Application window is always visible on all activities and can't be moved / set to a specific activity only EXPECTED RESULT The application window should only be visible on the current activity, unless a specific window rule was applied SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION This was not the case on 6.0.4. Downgrading temporarily solves the issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 487682] KShortcutsEditor still does not allow modifier-only shortcuts
https://bugs.kde.org/show_bug.cgi?id=487682 fanzhuyi...@gmail.com changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |kdelibs-b...@kde.org Version|git-stable-Plasma/6.1 |6.2.0 Component|general |general Product|kwin|frameworks-kxmlgui --- Comment #1 from fanzhuyi...@gmail.com --- Reassigning to Frameworks / KXMLGUI, which provides kshortcutseditor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487682] KShortcutsEditor still does not allow modifier-only shortcuts
https://bugs.kde.org/show_bug.cgi?id=487682 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||fanzhuyi...@gmail.com Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 487693] New: When activating the Krita window with `Win` + ``, all the hotkeys related to Canvas Input Settings don’t work
https://bugs.kde.org/show_bug.cgi?id=487693 Bug ID: 487693 Summary: When activating the Krita window with `Win` + ``, all the hotkeys related to Canvas Input Settings don’t work Classification: Applications Product: krita Version: 5.2.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: fxck.useless.s...@protonmail.com Target Milestone: --- SUMMARY Short: When activating the Krita window with `Win` + ``, all the hotkeys related to Canvas Input Settings don’t work Full: When activating the Krita window with the hotkey `Win` + `` (e.g. `Win` + `2`), activation of Pan Mode and Relative Zoom Mode using the hotkeys is not available. However, if I return to Krita by manually clicking on its icon in the taskbar and not using a hotkey, everything works correctly. To activate Pan Mode and Relative Zoom Mode become possible again, need to interact with the Krita in some way. For example, open the brush selection palette/docker or the brush settings palette/docker (despite the fact that using Pan Mode / Relative Zoom Mode with hotkeys is not available, opening the mentioned palettes/dockers with hotkeys stay available). Or click on one of the main Krita menus in the upper part of the window (File, Edit, View, …). The situation in which it becomes necessary to activate the Krita window is when I temporarily switch to another window (e.g. PureRef software window) and need to return to Krita afterwards. I have now noticed that Line Tool also stops working. I guess the problem is not only with Pan Mode, Relative Zoom Mode and Line Tool, but with some other tools/functions too. It seems that when activating the Krita window with `Win` + ``, all the hotkeys related to Canvas Input Settings don’t work, but all the hotkeys related to Keyboard Shortcuts work correctly. This person seems to have a similar problem: https://www.reddit.com/r/krita/comments/upo0pn/zoom_and_pan_stops_working_sometimes_after/ STEPS TO REPRODUCE 1. Open Krita 2. Create new file 3. Switch to any other window (file explorer / web-browser / ...) 4. Switch to the Krita window using the hotkey `Win` + `` 5. Try using any Canvas Input Settings hotkey OBSERVED RESULT When switching to the Krita window using `Win` + ``, the hotkeys related to Canvas Input Settings do not work. EXPECTED RESULT When switching to the Krita window using `Win` + ``, the hotkeys related to Canvas Input Settings should work. SOFTWARE/OS VERSIONS Krita Version: 5.2.2 Qt Version (compiled): 5.15.7 Version (loaded): 5.15.7 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.19045 Pretty Productname: Windows 10 Version 2009 Product Type: windows Product Version: 10 OpenGL Info Vendor: "Google Inc. (AMD)" Renderer: "ANGLE (AMD, AMD Radeon HD 7400 Series Direct3D11 vs_5_0 ps_5_0, D3D11-8.17.10.1433)" Driver version: "OpenGL ES 3.0.0 (ANGLE 2.1.0 git hash: f2280c0c5f93+krita_qt5)" Shading language: "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0 git hash: f2280c0c5f93+krita_qt5)" Requested format: QSurfaceFormat(version 3.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Current format: QSurfaceFormat(version 3.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) GL version: 3.0 Supports deprecated functions false Is OpenGL ES: true supportsBufferMapping: true supportsBufferInvalidation: false forceDisableTextureBuffers: true Extensions: GL_OES_draw_elements_base_vertex GL_EXT_texture_filter_anisotropic GL_ANGLE_pack_reverse_row_order GL_OES_texture_border_clamp GL_EXT_blend_func_extended GL_EXT_color_buffer_float GL_OES_compressed_EAC_RG11_signed_texture GL_CHROMIUM_lose_context GL_EXT_robustness GL_ANGLE_base_vertex_base_instance GL_EXT_draw_buffers GL_CHROMIUM_copy_compressed_texture GL_OES_texture_float GL_NV_EGL_stream_consumer_external GL_OVR_multiview2 GL_OES_compressed_EAC_R11_signed_texture GL_EXT_texture_format_BGRA GL_NV_framebuffer_blit GL_EXT_debug_label GL_EXT_texture_norm16 GL_NV_fence GL_CHROMIUM_sync_query
[kwin] [Bug 487682] KShortcutsEditor still does not allow modifier-only shortcuts
https://bugs.kde.org/show_bug.cgi?id=487682 adrian.g...@t-online.de changed: What|Removed |Added CC||adrian.g...@t-online.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-sonnet] [Bug 421451] Kate raises hspell error when launched from command line
https://bugs.kde.org/show_bug.cgi?id=421451 gerrit.huebb...@gmail.com changed: What|Removed |Added CC||gerrit.huebb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438336] chatty qml warning output into log/terminal
https://bugs.kde.org/show_bug.cgi?id=438336 gerrit.huebb...@gmail.com changed: What|Removed |Added CC||gerrit.huebb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487043] Extreme stutters/hangs when using certain desktop effects when "~/.cache" is on slow storage
https://bugs.kde.org/show_bug.cgi?id=487043 duha.b...@gmail.com changed: What|Removed |Added CC||duha.b...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487633] Kio6 segfaults if trying to access an Samsung Galaxy S 8 via MTP in TWRP Recovery Manager
https://bugs.kde.org/show_bug.cgi?id=487633 --- Comment #4 from devz...@r-d-w.net --- Out of a coredump, gdb could gather more data then the 23 lines, HTH. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487633] Kio6 segfaults if trying to access an Samsung Galaxy S 8 via MTP in TWRP Recovery Manager
https://bugs.kde.org/show_bug.cgi?id=487633 --- Comment #3 from devz...@r-d-w.net --- Created attachment 169912 --> https://bugs.kde.org/attachment.cgi?id=169912=edit kio6 backtrace from coredump the attached backtrace from a coredump -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456280] WindowHeap window draw calls depend on draw calls of current desktop (freezes windows from other desktops until current desktop updates)
https://bugs.kde.org/show_bug.cgi?id=456280 --- Comment #60 from bastimeyer...@gmail.com --- Working perfectly fine on 6.0.5 using Wayland via AMDGPU. Never tested X11 or the overview effect, just the grid... I'm on Arch where I have a custom PKGBUILD for kwin and plasma-workspace (because I apply other unrelated patches - one of them patches out the grid gaps, which breaks the overview layout, so I don't use it). The only issue I've observed ever since the fix was implemented was about Konsole, which doesn't draw unless it's re-focused, meaning that when compiling large projects for example, peeking onto the desktop where Konsole's window has been moved to doesn't show the current status. Looks like an application bug though, not a kwin bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487633] Kio6 segfaults if trying to access an Samsung Galaxy S 8 via MTP in TWRP Recovery Manager
https://bugs.kde.org/show_bug.cgi?id=487633 --- Comment #2 from devz...@r-d-w.net --- i attached gdb first to dolphin, however that does not give anything, so I attached it to kiod6 continued it then it crashed wit the following backtrace: (gdb) continue Continuing. Thread 1 "kiod6" received signal SIGSEGV, Segmentation fault. 0x7d721697e1dd in ?? () from /usr/lib/libc.so.6 (gdb) backtrace #0 0x7d721697e1dd in ??? () at /usr/lib/libc.so.6 #1 0x7d7203f3a326 in ??? () at /usr/lib/libmtp.so.9 #2 0x7d7203f27ec4 in LIBMTP_Get_Filemetadata () at /usr/lib/libmtp.so.9 #3 0x7d720abf15cc in ??? () at /usr/lib/qt6/plugins/kf6/kiod/kmtpd.so #4 0x7d720abf6916 in ??? () at /usr/lib/qt6/plugins/kf6/kiod/kmtpd.so #5 0x7d7217d8463d in ??? () at /usr/lib/libQt6DBus.so.6 #6 0x7d7217d8538a in ??? () at /usr/lib/libQt6DBus.so.6 #7 0x7d7217d8eecf in ??? () at /usr/lib/libQt6DBus.so.6 #8 0x7d7217d8ef1a in ??? () at /usr/lib/libQt6DBus.so.6 #9 0x7d7216f8c0cf in QObject::event(QEvent*) () at /usr/lib/libQt6Core.so.6 #10 0x7d7217efc55c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt6Widgets.so.6 #11 0x7d7216f44e08 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt6Core.so.6 #12 0x7d7216f451cb in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt6Core.so.6 #13 0x7d72171a45ec in ??? () at /usr/lib/libQt6Core.so.6 #14 0x7d72165e4a89 in ??? () at /usr/lib/libglib-2.0.so.0 #15 0x7d72166469b7 in ??? () at /usr/lib/libglib-2.0.so.0 #16 0x7d72165e3f95 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #17 0x7d72171a28bd in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt6Core.so.6 #18 0x7d7216f4f0de in QEventLoop::exec(QFlags) () at /usr/lib/libQt6Core.so.6 #19 0x7d7216f4942d in QCoreApplication::exec() () at /usr/lib/libQt6Core.so.6 #20 0x57f5270393d9 in ??? () #21 0x7d7216839c88 in ??? () at /usr/lib/libc.so.6 #22 0x7d7216839d4c in __libc_start_main () at /usr/lib/libc.so.6 #23 0x57f5270396b5 in ??? () (gdb) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 487672] JXL can no longer be opened in Gwenview
https://bugs.kde.org/show_bug.cgi?id=487672 alerikaisatt...@protonmail.com changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from alerikaisatt...@protonmail.com --- kimageformats was missing. Installing it fixes the issue -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 487685] New: Elisa does not remember maximized window state when closed and relaunched, instead launches un-maximized and in full-screen size
https://bugs.kde.org/show_bug.cgi?id=487685 Bug ID: 487685 Summary: Elisa does not remember maximized window state when closed and relaunched, instead launches un-maximized and in full-screen size Classification: Applications Product: Elisa Version: 24.05.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: moyamat...@crodity.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 *** SUMMARY STEPS TO REPRODUCE 1. open elisa 2. maximize it and then close it 3. open elisa again OBSERVED RESULT Instead of opening in a maximized window, it opens in an un-maximized window with the size of a full-screen window EXPECTED RESULT It should open in a maximized state. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487617] Night Light System Tray toggle does not function after Night Light has been turned off with a keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=487617 kde-b...@txd.mozmail.com changed: What|Removed |Added CC||kde-b...@txd.mozmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371560] Drop KWin's global modifier-only key handling in favor of setting individual modifier keys as shortcuts where applicable (e.g. for Kickoff)
https://bugs.kde.org/show_bug.cgi?id=371560 adrian.g...@t-online.de changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=487682 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487682] KShortcutsEditor still does not allow modifier-only shortcuts
https://bugs.kde.org/show_bug.cgi?id=487682 adrian.g...@t-online.de changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=371560 -- You are receiving this mail because: You are watching all bug changes.
