[krita] [Bug 419283] New: Brush Cursor disappearing and Pixel Art brush Grid Lock Off - grid
https://bugs.kde.org/show_bug.cgi?id=419283 Bug ID: 419283 Summary: Brush Cursor disappearing and Pixel Art brush Grid Lock Off - grid Product: krita Version: 4.2.9 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: john.angelo.teno...@gmail.com Target Milestone: --- SUMMARY Brush cursor disappears in the canvas when using Color Picker between open tabs. STEPS TO REPRODUCE 1. Open two projects in Krita 2. Select a color using Color Picker in Tab 1 3. Switch to Tab 2 OBSERVED RESULT Brush Cursor disappears in the canvas when you switch to another tab. It reappears when you use Color Picker hotkey (pressing CTRL on canvas). Related to Bug#419282, Pixel Art brush cursor becomes off grid with the canvas' pixels an becomes erratic with pen/mouse movements. EXPECTED RESULT Brush cursor doesn't disappear and Pixel Art brush move smoothly with pen/mouse movement. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro (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.
[krita] [Bug 419282] Pixel Art brush Grid Locking
https://bugs.kde.org/show_bug.cgi?id=419282 john.angelo.teno...@gmail.com changed: What|Removed |Added Platform|Other |Manjaro -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419282] New: Pixel Art brush Grid Locking
https://bugs.kde.org/show_bug.cgi?id=419282 Bug ID: 419282 Summary: Pixel Art brush Grid Locking Product: krita Version: 4.2.9 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: john.angelo.teno...@gmail.com Target Milestone: --- SUMMARY Pixel Art brush cursor Locks into Pixel Grid. Looks and feels unresponsive to tablet strokes when using freehand drawing. Leads to inaccurate drawing when using Free Hand Brush Tool. STEPS TO REPRODUCE 1. Use the default "u)_Pixel_Art*" brushes 2. Move the pen/mouse around the canvas using Freehand Brush tool. 3. Draw using Freehand Brush tool. OBSERVED RESULT Brush Cursor locks into pixel grid and does not accurately respond/move with pen strokes resulting in inaccurate freehand drawing. EXPECTED RESULT Center of brush cursor should be in center of pointer and moves with pen. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro (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.
[konsole] [Bug 386740] konsole crashes for no reason
https://bugs.kde.org/show_bug.cgi?id=386740 wolfgang wayland changed: What|Removed |Added CC||wolfgangwayla...@comcast.ne ||t -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411543] Background mode: no keyboard focus after opening window
https://bugs.kde.org/show_bug.cgi?id=411543 Anton Karmanov changed: What|Removed |Added CC||bergentr...@insiberia.net --- Comment #2 from Anton Karmanov --- Possible fix has been added: https://invent.kde.org/kde/konsole/-/merge_requests/71 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418190] Using Alt+Tab on wayland only switches once and then doesn't switch any further. However, I can switch more using keyboard arrows.
https://bugs.kde.org/show_bug.cgi?id=418190 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.
[lattedock] [Bug 418785] latte-dock often close unexpectly and i have to restart it
https://bugs.kde.org/show_bug.cgi?id=418785 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418189] Plasma freeze when systemd automount NFS shares are not mounted
https://bugs.kde.org/show_bug.cgi?id=418189 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-frameworkintegration] [Bug 365938] Setting the application language does not affect some framework controls
https://bugs.kde.org/show_bug.cgi?id=365938 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. 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 415454] Timeline indicators
https://bugs.kde.org/show_bug.cgi?id=415454 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[frameworks-frameworkintegration] [Bug 358199] Maximised window go under the task bar when the second screen is set as primary
https://bugs.kde.org/show_bug.cgi?id=358199 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.
[frameworks-frameworkintegration] [Bug 357865] The QPA file dialog does not respect mime type filters
https://bugs.kde.org/show_bug.cgi?id=357865 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. 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.
[frameworks-frameworkintegration] [Bug 354491] Wonky dialog rendering (multiple dialog types)
https://bugs.kde.org/show_bug.cgi?id=354491 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.
[frameworks-frameworkintegration] [Bug 352304] QFileDialog opens in wrong size
https://bugs.kde.org/show_bug.cgi?id=352304 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.
[krita] [Bug 419281] New: Krita Actions - Copy Paste Layer Script
https://bugs.kde.org/show_bug.cgi?id=419281 Bug ID: 419281 Summary: Krita Actions - Copy Paste Layer Script Product: krita Version: 4.2.8 Platform: Other OS: other Status: REPORTED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: keyth2363...@gmail.com Target Milestone: --- SUMMARY Making a selection on a layer and using the STEPS TO REPRODUCE scenarioA 1. Make a Selection 2. use "copy_selection_to_new_layer" action for a new layer (becomes locked to layer) 3. try using "activateNextLayer" to select the new layer (will not work, originally I tried without it since it moves up but it has the same effect this being here or not) 4. try to use any action on the new layer but it will Always affect the original layer. scenarioB 1. Make a Selection 2. use "copy_selection_to_new_layer" action for a new layer 3. Create another script/button to do the rest of the actions 4. now "activateNextLayer" is not needed since the pause allows the layer selection to be Concrete. 5. try to use any action on the new layer but now it will work. OBSERVED RESULT Creating a new layer with a paste of any kind blocks any operation to the new layer, even layers changes. But if you part the same code in two parts it works. EXPECTED RESULT Ability to change layer after a paste command. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION As you can see the commands actually work if they are applied individually but they should be able to work along side each other. I was making a small copy paste and mirror script and I noticed this odd behavior, I will be posting my code to this link if it is quicker to take a look and test. My code considers if you have a selection or not active and if you don't it creates a selection, currently you need to press M1 and then M2 for it to execute whole. code: https://github.com/EyeOdin/mirror_tools Hopefully I could merge "Mirror_1" and "Mirror_2" into a single function without resorting to a break. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418318] The hover state should be clarifying, but not main
https://bugs.kde.org/show_bug.cgi?id=418318 Nate Graham changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-desktop/488c4b746d68e07 ||a44e538e8507229577a2c1bf8 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #10 from Nate Graham --- Git commit 488c4b746d68e07a44e538e8507229577a2c1bf8 by Nate Graham, on behalf of Eugene Popov. Committed on 27/03/2020 at 04:10. Pushed by ngraham into branch 'master'. [applets/taskmanager] Make the hover state clarifying, but not main Summary: I'm trying to make a custom appearance of the Task Manager by creating a new theme, but I ran into some issue. I expected that there are three main states (minimized, normal and active) and one clarifying state (hover). But I was surprised to find that there are four main states (minimized, normal, active and hover), and the hover state is also main, but not clarifying. I believe that the hover state should be clarifying for the main states, i.e. there must be three main states (minimized, normal and active) and three additional (minimzed-hover, normal-hover, active-hover). See https://phabricator.kde.org/P555 Reviewers: davidedmundson, #vdg Reviewed By: davidedmundson Subscribers: broulik, ngraham, epopov, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28306 M +2-10 applets/taskmanager/package/contents/ui/Task.qml M +13 -0applets/taskmanager/package/contents/ui/code/tools.js https://commits.kde.org/plasma-desktop/488c4b746d68e07a44e538e8507229577a2c1bf8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418318] The hover state should be clarifying, but not main
https://bugs.kde.org/show_bug.cgi?id=418318 Nate Graham changed: What|Removed |Added Version Fixed In||5.19.0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419062] Discover crash when closed in the middle of buffer
https://bugs.kde.org/show_bug.cgi?id=419062 Nate Graham changed: What|Removed |Added Version Fixed In||5.18.4 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375951] locally integrated menus
https://bugs.kde.org/show_bug.cgi?id=375951 --- Comment #27 from Chris Holland --- I've restarted interest in this feature after finding and modifying zzag's material decoration. I've bundled psifidotos's AppMenuModel.cpp from his appmenu widget. He bundled libdbusmenuqt so I've done the same as I couldn't iron out how to link to it. * https://i.imgur.com/R3qHgaN.png * https://github.com/Zren/material-decoration/tree/lim * https://github.com/psifidotos/applet-window-appmenu/tree/master/plugin * https://github.com/KDE/breeze/blob/master/kdecoration/breezesizegrip.cpp It's a work in progress. I'm not sure if I'll attempt to embed a Widget QMenu somehow, or if I'll stick with using KDecoration2::DecorationButtonType::Custom. While it'll be easier to theme "Custom" buttons, QMenu comes with "hover"+Left/Right Arrows to change submenues and other basic menu features. I recommend using the following command to test the LIM branch. It filters out the non-essential logging, and restarts KWin. sudo make install && QT_LOGGING_RULES="*=false;kdecoration.material=true" kstart5 -- kwin_x11 --replace Tip: I also found that just opening the System Settings > Window Decorations kcm was more convenient for testing the close/maximize/minimize buttons. kcmshell5 kwindecoration -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 419280] New: Ledgers account dropdown does not show categories or hidden equity accounts
https://bugs.kde.org/show_bug.cgi?id=419280 Bug ID: 419280 Summary: Ledgers account dropdown does not show categories or hidden equity accounts Product: kmymoney Version: 5.0.8 Platform: Debian stable OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: lifeofthe...@mail.com Target Milestone: --- In Ledgers, the account dropdown fails to reflect the actual account/category in two conditions: * When Configure -> General -> Filter -> "Show equity accounts" is disabled, viewing an equity account in Ledgers does not show the equity account in the accounts dropdown. (e.g. by double-clicking a transaction belonging to an equity account in Payees). Also, no "Account" column appears like in the following scenario. * Viewing a category in Ledgers does not update the accounts dropdown, irrespective of the "Show categories in the accounts list view" checkbox setting. An "Account" column appears instead, which is confusing for several reasons: 1. The column represents a category, not an account (unless you're going by the accounting definition, which confusingly overloads the word "account") 2. It is not consistent with the view for regular accounts. 3. The column only shows the leaf node of the account hierarchy, which conflates two different leaf nodes of the same name. 4. The "Account" column is unnecessarily redundant; in this view, only one category's transactions are shown. To resolve both scenarios, I think it's better to remove the "Account" column and add temporary entries to the accounts dropdown. These temporary entries would behave as follows: 1. When a category/hidden account is opened in Ledgers, a partial hieararchy is added to the accounts dropdown that consists of the category/hidden account and all its parents. 2. When a regular account or another category/hidden account is opened, the temporary entries should be updated as necessary for that account. 3. These entries should be stylized in italics (or something to distinguish them from regular entries) SOFTWARE/OS VERSIONS KDE Plasma Version: 4:4.14.38-3 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418825] Discover crashes on reviews
https://bugs.kde.org/show_bug.cgi?id=418825 Aleix Pol changed: What|Removed |Added CC||jcandido.fi...@gmail.com --- Comment #5 from Aleix Pol --- *** Bug 419273 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418825] Discover crashes on reviews
https://bugs.kde.org/show_bug.cgi?id=418825 Aleix Pol changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #6 from Aleix Pol --- seems like it's happening to other people too -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419273] I tried to mark another user's review as helpful.
https://bugs.kde.org/show_bug.cgi?id=419273 Aleix Pol changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Aleix Pol --- *** This bug has been marked as a duplicate of bug 418825 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419257] Discover opens automatically and halts plasma loading
https://bugs.kde.org/show_bug.cgi?id=419257 --- Comment #1 from Aleix Pol --- Can you check if it's for some weird reason on the Autostart section in system settings? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418825] Discover crashes on reviews
https://bugs.kde.org/show_bug.cgi?id=418825 --- Comment #4 from Aleix Pol --- I tried what you did and I still don't get a crash on either Neon or ArchLinux. Can you maybe try getting the backtrace by running discover from gdb? Here it's explained how to do it: https://wiki.ubuntu.com/Backtrace -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418201] Discover crashes when trying to delete GNOME Application Platfrom version 3.30.
https://bugs.kde.org/show_bug.cgi?id=418201 --- Comment #1 from Aleix Pol --- Would you be able to give us some more information? Like the output on the terminal or the backtrace with debug symbols? This is crashing when Qt is trying to render things, it's possible that it's a problem with your graphics drivers. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418928] Crash of Discover after clicking on "Installed software"
https://bugs.kde.org/show_bug.cgi?id=418928 --- Comment #1 from Aleix Pol --- Would you be able to provide the backtrace with debug symbols? It would really help us understand what's going on. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419051] Discover won't open
https://bugs.kde.org/show_bug.cgi?id=419051 --- Comment #2 from Aleix Pol --- Would you try running it from a terminal and telling us what output you get? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419062] Discover crash when closed in the middle of buffer
https://bugs.kde.org/show_bug.cgi?id=419062 Aleix Pol changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/dis ||cover/a78788762f4babc7c1178 ||7216b754ae1443f175e Resolution|--- |FIXED --- Comment #1 from Aleix Pol --- Git commit a78788762f4babc7c11787216b754ae1443f175e by Aleix Pol. Committed on 27/03/2020 at 01:44. Pushed by apol into branch 'Plasma/5.18'. flatpak: Don't insist on performing tasks after cancellation Such as flatpak_installation_list_installed_refs_for_update in this case. M +6-0libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp https://commits.kde.org/discover/a78788762f4babc7c11787216b754ae1443f175e -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419253] Discovery crashes while installing the package org.freedesktop Nvidia435
https://bugs.kde.org/show_bug.cgi?id=419253 Aleix Pol changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Aleix Pol --- Can you maybe try to provide a backtrace? Here it's briefly explained how to do it. Sorry for the bother. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 419279] New: Kate can't display Asian characters properly
https://bugs.kde.org/show_bug.cgi?id=419279 Bug ID: 419279 Summary: Kate can't display Asian characters properly Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: gabrielfer...@gmail.com Target Milestone: --- Created attachment 127039 --> https://bugs.kde.org/attachment.cgi?id=127039=edit Comparing Kate to FeatherPad Lines with some Asian characters have wrong height, cutting off the bottom of these characters. Try pasting 한국어 or 日本語 and at the same line _, the bottom of the line simply disappears, it seems to be some sort of miscalculation of line height (as these characters are taller). https://imgur.com/a/soELt03 (same text)(also available as attachment) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419278] Indeterminate crashing when changing QStyle under Wayland
https://bugs.kde.org/show_bug.cgi?id=419278 --- Comment #1 from Carson Black --- Errata: KDecoration, not QStyle -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419278] Indeterminate crashing when changing KDecoration under Wayland
https://bugs.kde.org/show_bug.cgi?id=419278 Carson Black changed: What|Removed |Added Summary|Indeterminate crashing when |Indeterminate crashing when |changing QStyle under |changing KDecoration under |Wayland |Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419278] New: Indeterminate crashing when changing QStyle under Wayland
https://bugs.kde.org/show_bug.cgi?id=419278 Bug ID: 419278 Summary: Indeterminate crashing when changing QStyle under Wayland Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: egl Assignee: kwin-bugs-n...@kde.org Reporter: uhh...@gmail.com Target Milestone: --- Created attachment 127038 --> https://bugs.kde.org/attachment.cgi?id=127038=edit Stacktrace SUMMARY KWin indeterminately crashes when changing the QStyle under Wayland [git master as of commit 745981f] STEPS TO REPRODUCE 1. Change QStyle 2. If it doesn't crash, try again OBSERVED RESULT KWin crashes changing QStyle EXPECTED RESULT KWin doesn't crash when changing QStyle -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419277] New: krita-4.2.9: CMake Error at cmake/modules/FindOpenEXR.cmake:43, 49, 55: string sub-command REGEX, mode MATCHALL needs at least 5 arguments total to command
https://bugs.kde.org/show_bug.cgi?id=419277 Bug ID: 419277 Summary: krita-4.2.9: CMake Error at cmake/modules/FindOpenEXR.cmake:43, 49, 55: string sub-command REGEX, mode MATCHALL needs at least 5 arguments total to command Product: krita Version: 4.2.9 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: andreas.sturmlech...@gmail.com Target Milestone: --- Created attachment 127037 --> https://bugs.kde.org/attachment.cgi?id=127037=edit build.log This is a regression over 4.2.8. cmake-3.17.0 ilmbase/openexr-2.3.0 ... CMake Error at cmake/modules/FindOpenEXR.cmake:43 (string): string sub-command REGEX, mode MATCHALL needs at least 5 arguments total to command. Call Stack (most recent call first): CMakeLists.txt:569 (find_package) CMake Error at cmake/modules/FindOpenEXR.cmake:49 (string): string sub-command REGEX, mode MATCHALL needs at least 5 arguments total to command. Call Stack (most recent call first): CMakeLists.txt:569 (find_package) CMake Error at cmake/modules/FindOpenEXR.cmake:55 (string): string sub-command REGEX, mode MATCHALL needs at least 5 arguments total to command. Call Stack (most recent call first): CMakeLists.txt:569 (find_package) -- Found OpenEXR: /usr/include;/usr/include/OpenEXR -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405879] Hang when clicking on the canvas with a stylus after changing layer opacity by entering a number
https://bugs.kde.org/show_bug.cgi?id=405879 andreas.sturmlech...@gmail.com changed: What|Removed |Added CC||andreas.sturmlechner@gmail. ||com Alias|crash, Krita, layer | -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 419276] Changing your own password via the GUI is not possible for normal users.
https://bugs.kde.org/show_bug.cgi?id=419276 a.m.wollmar...@miluriel.info changed: What|Removed |Added CC||a.m.wollmar...@miluriel.inf ||o -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418797] Crash when opening System Settings
https://bugs.kde.org/show_bug.cgi?id=418797 --- Comment #7 from Oded Arbel --- (In reply to David Edmundson from comment #6) > What's kci? Kubuntu Continuous Integration: https://phabricator.kde.org/w/kubuntu/kci/ Also: https://launchpad.net/~kubuntu-ci -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 419276] New: Changing your own password via the GUI is not possible for normal users.
https://bugs.kde.org/show_bug.cgi?id=419276 Bug ID: 419276 Summary: Changing your own password via the GUI is not possible for normal users. Product: policykit-kde-agent-1 Version: 5.18.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: d...@kde.org Reporter: a.m.wollmar...@miluriel.info Target Milestone: --- SUMMARY If a completely unprivileged user wants to change his own password via the KDE settings, he will be asked for the admin password for confirmation. However, the console command "passwd" can be used without it. STEPS TO REPRODUCE 1. Goes to the system settings 2. Goes ti User accounts 3. Tries to change the own password without root OBSERVED RESULT You will be asked to confirm the root password. EXPECTED RESULT It should be possible without root password for itself. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 Kernel Version: 5.4.28-1-MANJARO OS Type: 64-bit ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 419172] Baloo crash on login
https://bugs.kde.org/show_bug.cgi?id=419172 Martin Riethmayer changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Martin Riethmayer --- Thanks, fixed -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 419224] okular impossible to print
https://bugs.kde.org/show_bug.cgi?id=419224 --- Comment #3 from Albert Astals Cid --- You need to write in english, otherwise we can't help you here. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418797] Crash when opening System Settings
https://bugs.kde.org/show_bug.cgi?id=418797 --- Comment #6 from David Edmundson --- What's kci? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385522] Present Windows: Don't darken all windows and denote selection some other way than restoring original lightness
https://bugs.kde.org/show_bug.cgi?id=385522 Szczepan Hołyszewski changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #65 from Szczepan Hołyszewski --- *** This bug has been marked as a duplicate of bug 303438 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 Szczepan Hołyszewski changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 Szczepan Hołyszewski changed: What|Removed |Added CC||salvacort...@gmail.com --- Comment #7 from Szczepan Hołyszewski --- *** Bug 385522 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 419275] QIF Exporter does not display QIF Profile Dropdown Menu on macOS
https://bugs.kde.org/show_bug.cgi?id=419275 --- Comment #2 from a94c4...@opayq.com --- Created attachment 127036 --> https://bugs.kde.org/attachment.cgi?id=127036=edit QIF Exporter Default Profile -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 419275] QIF Exporter does not display QIF Profile Dropdown Menu on macOS
https://bugs.kde.org/show_bug.cgi?id=419275 --- Comment #1 from a94c4...@opayq.com --- Created attachment 127035 --> https://bugs.kde.org/attachment.cgi?id=127035=edit QIF Importer Default Profile -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 419275] New: QIF Exporter does not display QIF Profile Dropdown Menu on macOS
https://bugs.kde.org/show_bug.cgi?id=419275 Bug ID: 419275 Summary: QIF Exporter does not display QIF Profile Dropdown Menu on macOS Product: kmymoney Version: 5.0.8 Platform: Other OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: exporter Assignee: kmymoney-de...@kde.org Reporter: a94c4...@opayq.com Target Milestone: --- Created attachment 127034 --> https://bugs.kde.org/attachment.cgi?id=127034=edit Screenshot of Bug SUMMARY macOS QIF exporter does not display QIF Profile dropdown menu. STEPS TO REPRODUCE 1. File -> Export -> QIF menu item 2. 3. OBSERVED RESULT Export Button Greyed QIF Dropdown Menu can not be clicked to display options (Screenshot attached) EXPECTED RESULT QIF Dropdown menu profile selection available as shown in docs here - https://docs.kde.org/stable5/en/extragear-office/kmymoney/details.impexp.qifexp.html Export Button not Greyed Please Note - Default QIF Profile exists under Preferences -> Plugins -> QIF Importer SOFTWARE/OS VERSIONS Windows: macOS: 10.15.4 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION KMyMoney Version 5.0.80-c404e6723 -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 419274] New: Saving settings aren't respected
https://bugs.kde.org/show_bug.cgi?id=419274 Bug ID: 419274 Summary: Saving settings aren't respected Product: Skanlite Version: 2.1.0.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: m...@protonmail.ch Target Milestone: --- SUMMARY I set jpg as the default extension, but every time I get to save an image its default extension is set back to png despite of that. STEPS TO REPRODUCE 1. Set jpg as the default image format 2. Scan. 3. Save OBSERVED RESULT Png always comes out (at least on a "fresh" start of the program) EXPECTED RESULT Respect the preference (or better yet, I wonder why not just remembering the last used setting?) SOFTWARE/OS VERSIONS KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION Btw isn't it possible to get the jpeg quality slider in the path selection dialog? Irfanview would do this for example. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 418580] Some links in description pages show empty tooltip and nothing happens when such links are clicked
https://bugs.kde.org/show_bug.cgi?id=418580 Nate Graham changed: What|Removed |Added Component|discover|general Target Milestone|--- |Not decided Product|Discover|frameworks-kirigami Version|unspecified |5.68.0 CC||n...@kde.org Version Fixed In||5.59 Assignee|lei...@leinir.dk|notm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 419210] When i start playing music, the music is unmuted, but when it get's to the next song it automatically mutes.
https://bugs.kde.org/show_bug.cgi?id=419210 --- Comment #1 from Matthieu Gallien --- Thanks for your report We need more data to understand what happen. Could you please reproduce this bugs and get the log of Elisa (for example on console) ? We need the log with most debug outputs. You can set this by setting the following environment variable: export QT_LOGGING_RULES="*elisa*=true" -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 409010] [Wayland] Elisa crashed on close
https://bugs.kde.org/show_bug.cgi?id=409010 Matthieu Gallien changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #12 from Matthieu Gallien --- (In reply to Patrick Silva from comment #11) > First crash occured just once, it was never reproducible. > If backtrace generated by drkonqi is not halpful, I think > that this issue can be closed. Thanks for your reply. Closing this report. Do not hesitate to report new crashes and we will try to follow quickly. Best regards -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403843] Libinput touchpad KCM needs a scroll speed setting
https://bugs.kde.org/show_bug.cgi?id=403843 --- Comment #8 from Claudius Ellsel --- Ah, I wasn't aware of that. Thanks for mentioning! -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 419246] Importing .ics holidays calendar doesn't work
https://bugs.kde.org/show_bug.cgi?id=419246 --- Comment #2 from Allen Winter --- Created attachment 127033 --> https://bugs.kde.org/attachment.cgi?id=127033=edit greece.ics fixed -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 419246] Importing .ics holidays calendar doesn't work
https://bugs.kde.org/show_bug.cgi?id=419246 Allen Winter changed: What|Removed |Added CC||win...@kde.org --- Comment #1 from Allen Winter --- the ics files you refer to are not valid . or at least not valid enough to make KOrganizer happy. try loading greece.ics into https://icalendar.org/validator.html and you'll see some problems, especially the PRODID is missing. You did encounter a known bug that KOrganizer will tell you it successfully loaded a calendar even though it failed. I'll attach a new greece.ics where I added the PRODID. You should be able to load this succesfully -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 370940] DPI field shows: 300 DPI (I18N_EXCESS_ARGUMENTS_SUPPLIED)
https://bugs.kde.org/show_bug.cgi?id=370940 mirh changed: What|Removed |Added CC||m...@protonmail.ch --- Comment #3 from mirh --- Still a thing in latest git. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 396907] Amarok crashes when user clicks on Help ---> Diagnostics, while running under Wayland
https://bugs.kde.org/show_bug.cgi?id=396907 Heiko Becker changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/ama ||rok/4ae84cd433864f45b2130c2 ||7bca8a2c4c0ba0d5a --- Comment #2 from Heiko Becker --- Git commit 4ae84cd433864f45b2130c27bca8a2c4c0ba0d5a by Heiko Becker. Committed on 26/03/2020 at 20:21. Pushed by heikobecker into branch 'master'. Fix a crash when trying to open the DiagnosticDialog The possibility to discover the preferred phonon backend is gone since its qt5 port, causing 'KServiceTypeTrader::self()->preferredService( "PhononBackend" )' to return a null pointer, which causes a crash later on. Instead I borrowed some code from the old phonon kcm from plasma-desktop and slightly modified it. M +1-0CMakeLists.txt M +83 -8src/dialogs/DiagnosticDialog.cpp M +18 -0src/dialogs/DiagnosticDialog.h https://commits.kde.org/amarok/4ae84cd433864f45b2130c27bca8a2c4c0ba0d5a -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Roberth Sjonøy changed: What|Removed |Added CC||roberth.sjo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403843] Libinput touchpad KCM needs a scroll speed setting
https://bugs.kde.org/show_bug.cgi?id=403843 --- Comment #7 from Tim Richardson --- "New UI": libinput exposes a number of configurations for touchpads. For a long time, most of these options were not exposed to the touchpad kcm. This changed in Jan 2020 when a much richer kcm arrived, hence "new UI". -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419047] Closing Face Tag Delete Dialog Box still ends up deleting face tag
https://bugs.kde.org/show_bug.cgi?id=419047 --- Comment #4 from Maik Qualmann --- normal day => normal tag Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419047] Closing Face Tag Delete Dialog Box still ends up deleting face tag
https://bugs.kde.org/show_bug.cgi?id=419047 --- Comment #3 from Maik Qualmann --- We just had a bug report with these dialogs. Mario has implemented this function. This does not delete a tag, but resets a face tag marked back to a normal day. By choosing to remove it from the corresponding images. I'm still looking for the bug report. It is a bit misleading, but since we also have the possibility to make a normal tag to a face tag, there has to be a way back. Maik -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418797] Crash when opening System Settings
https://bugs.kde.org/show_bug.cgi?id=418797 --- Comment #5 from Oded Arbel --- (In reply to David Edmundson from comment #3) > From the output > > >module "org.kde.kirigami" version 2.12 is not installed The problem is clearly in the KCI packaging, where qml-module-org-kde-qqc2desktopstyle doesn't set up its dependencies properly - it shouldn't have been installed if its dependency (kirigami 2.12) is not available. How does one report bugs against that? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418797] Crash when opening System Settings
https://bugs.kde.org/show_bug.cgi?id=418797 --- Comment #4 from Oded Arbel --- Created attachment 127032 --> https://bugs.kde.org/attachment.cgi?id=127032=edit Temporary patch to unbreak system settings on KCI The problem seems to be in KCI only - downgrading qml-module-org-kde-qqc2desktopstyle to the version from the Ubuntu focal development tree solves the problem, as well as removing the kirigami 2.12 specific code from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ToolTip.qml by applying the attached patch. Other desktop behavior I described in previous comments is likely not fixed by the patch because there are other things in qml-module-org-kde-qqc2desktopstyle that require features from Kirigami 2.12. I'd also like to note that while 2.12 is the current version in git master, KCI unstable only has 2.11... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418797] Crash when opening System Settings
https://bugs.kde.org/show_bug.cgi?id=418797 David Edmundson changed: What|Removed |Added Resolution|--- |NOT A BUG CC||k...@davidedmundson.co.uk Status|CONFIRMED |RESOLVED --- Comment #3 from David Edmundson --- >From the output >module "org.kde.kirigami" version 2.12 is not installed -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418797] Crash when opening System Settings
https://bugs.kde.org/show_bug.cgi?id=418797
Oded Arbel changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0 |1
--- Comment #2 from Oded Arbel ---
Running `systemsettings5` from the console, we get this text, before the
application crashes (looks like from sidebar/SidebarMode.cpp:664):
org.kde.kwindowsystem: Loaded plugin
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemX11Plugin.so"
for platform "xcb"
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/main.qml:46:5:
Type CategoriesPage unavailable
CategoriesPage {
^
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/CategoriesPage.qml:55:17:
Type QQC2.ToolTip unavailable
QQC2.ToolTip {
^
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ToolTip.qml:26:1:
module "org.kde.kirigami" version 2.12 is not installed
import org.kde.kirigami 2.12 as Kirigami
^
"file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/main.qml:46:5:
Type CategoriesPage unavailable"
"file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/CategoriesPage.qml:55:17:
Type QQC2.ToolTip unavailable"
"file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ToolTip.qml:26:1:
module \"org.kde.kirigami\" version 2.12 is not installed"
Fatal error while loading the sidebar view qml component
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = systemsettings5 path = /usr/bin pid = 258303
KCrash: Arguments: /usr/bin/systemsettings5
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from
kdeinit
sock_file=/run/user/1000/kdeinit5__0
So all this seems to be a broken dependency in either Kubuntu focal and/or KCI
stable, where kirigami 2.12 is expected by only 2.5 is available.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 418797] Crash when opening System Settings
https://bugs.kde.org/show_bug.cgi?id=418797 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403843] Libinput touchpad KCM needs a scroll speed setting
https://bugs.kde.org/show_bug.cgi?id=403843 --- Comment #6 from Claudius Ellsel --- (In reply to Tim Richardson from comment #5) > Although changing the pointer speed in the touchpad kcm does not actually > seem to change the speed of two finger scrolling, which I obviously don't > use very much. > So in fact I actually confirm that there is a touchpad kcm when using > libinput, and pointer sensitivity can be controlled, but there is no control > over scrolling sensitivity. So basically you mixed up a setting for pointer sensitivity with scroll sensitivity? Also, what do you mean with "new UI"? -- 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 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419242] KWin doesn't recover after GPU reset
https://bugs.kde.org/show_bug.cgi?id=419242 --- Comment #9 from Shmerl --- Oh, I missed one preceding dmesg part: [16340.923960] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! [16345.787744] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=945004, emitted seq=945007 [16345.787817] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process kwin_x11 pid 1378 thread kwin_x11:cs0 pid 1451 [16345.787824] amdgpu :0f:00.0: GPU reset begin! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419242] KWin doesn't recover after GPU reset
https://bugs.kde.org/show_bug.cgi?id=419242 --- Comment #8 from Shmerl --- OK, it happened again, and I can tell it was a reset, since I see it in dmesg (see below). The session got corrupted again, but was reacting on some garbled fashion to input like before. I switched to tty, and run kwin_x11 --replace The result was: kwin_x11: FATAL ERROR while trying to open display. I probably should have set DISPLAY variable? And after set session was interrupted and fell out into sddm login. --- [16346.087369] [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KGQ disable failed [16346.353602] [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed [16346.614280] [drm:gfx_v10_0_cp_gfx_enable [amdgpu]] *ERROR* failed to halt cp gfx [16346.679190] pcieport :00:03.2: PME: Spurious native interrupt! [16346.695659] snd_hda_intel :0f:00.1: refused to change power state from D3hot to D0 [16346.799944] snd_hda_intel :0f:00.1: CORB reset timeout#2, CORBRP = 65535 [16347.079683] snd_hda_codec_hdmi hdaudioC0D0: Unable to sync register 0x2f0d00. -5 [16349.803271] amdgpu :0f:00.0: GPU reset succeeded, trying to resume [16349.803422] [drm] PCIE GART of 512M enabled (table at 0x008000E1). [16349.806417] [drm] PSP is resuming... [16349.983666] [drm] reserve 0xa0 from 0x81fe40 for PSP TMR [16350.175659] amdgpu :0f:00.0: RAS: ras ta ucode is not available [16350.199660] amdgpu: [powerplay] SMU is resuming... [16350.202662] amdgpu: [powerplay] SMU is resumed successfully! [16350.339655] [drm] kiq ring mec 2 pipe 1 q 0 [16350.352249] [drm] VCN decode and encode initialized successfully(under DPG Mode). [16350.352320] [drm] JPEG decode initialized successfully. [16350.352323] amdgpu :0f:00.0: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 [16350.352325] amdgpu :0f:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [16350.352326] amdgpu :0f:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [16350.352327] amdgpu :0f:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0 [16350.352327] amdgpu :0f:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0 [16350.352328] amdgpu :0f:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0 [16350.352329] amdgpu :0f:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0 [16350.352330] amdgpu :0f:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0 [16350.352331] amdgpu :0f:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0 [16350.352332] amdgpu :0f:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 [16350.352333] amdgpu :0f:00.0: ring sdma0 uses VM inv eng 12 on hub 0 [16350.352334] amdgpu :0f:00.0: ring sdma1 uses VM inv eng 13 on hub 0 [16350.352335] amdgpu :0f:00.0: ring vcn_dec uses VM inv eng 0 on hub 1 [16350.352336] amdgpu :0f:00.0: ring vcn_enc0 uses VM inv eng 1 on hub 1 [16350.352337] amdgpu :0f:00.0: ring vcn_enc1 uses VM inv eng 4 on hub 1 [16350.352338] amdgpu :0f:00.0: ring jpeg_dec uses VM inv eng 5 on hub 1 [16350.354293] [drm] recover vram bo from shadow start [16350.359554] [drm] recover vram bo from shadow done [16350.359556] [drm] Skip scheduling IBs! [16350.359557] [drm] Skip scheduling IBs! [16350.359583] amdgpu :0f:00.0: GPU reset(1) succeeded! [16350.359593] [drm] Skip scheduling IBs! ... [16350.359861] [drm] Skip scheduling IBs! [16350.359862] [drm] Skip scheduling IBs! [16350.359869] [drm] Skip scheduling IBs! [16350.560148] Renderer[2102]: segfault at 0 ip 7f15202eafcb sp 7f151a883eb0 error 6 in libxul.so[7f151b48f000+4e7c000] [16350.560155] Code: 48 8d 3d a0 a9 4c 02 e8 3b e2 1a fb 85 c0 75 02 58 c3 e8 40 e3 1a fb 0f 1f 84 00 00 00 00 00 50 48 8b 05 d8 a9 3c 02 48 89 10 <89> 34 25 00 00 00 00 e8 21 e3 1a fb 66 0f 1f 84 00 00 00 00 00 85 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kuserfeedback] [Bug 418981] Violation of KDE Software Privacy Policy
https://bugs.kde.org/show_bug.cgi?id=418981 gvgeo changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|NOT A BUG |--- --- Comment #3 from gvgeo --- With the close reason been fundamentally wrong, equalizing telemetry data with configuration properties, and no response, I don't see any reason for this bug to stay closed. Moreover, the given reasoning is not making any sense, as it does not address this bug or the problems created from it; 1. The bug describes exact steps which show, software collecting data that are not needed to function. In contrast to essential properties. 2. Data that are collected while telemetry is 'disabled', are retained and used as telemetry data, if and when user chooses to enable the corresponding telemetry level. The same occurs if a user chooses to stop telemetry for a while; data usage will continue to collected, and will be included when the user raise back telemetry level. Neither of these 2 issues were addressed. They break privacy policy and user expectations, with the potential to hurt kde image(especially the way you are handling it), and the second can create inaccurate data. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419273] New: I tried to mark another user's review as helpful.
https://bugs.kde.org/show_bug.cgi?id=419273 Bug ID: 419273 Summary: I tried to mark another user's review as helpful. Product: Discover Version: 5.18.3 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: jcandido.fi...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.18.3) Qt Version: 5.14.1 Frameworks Version: 5.68.0 Operating System: Linux 5.3.0-42-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: I wrote a review of an App without any problems. Then I tried to mark another user's evaluation as useful, it was at that moment that the crash occurred. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3ecf40b580 (LWP 18192))] Thread 14 (Thread 0x7f3e27fff700 (LWP 18267)): #0 0x7f3eca5ccbf9 in __GI___poll (fds=0x7f3e20003e70, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f3ec49835c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3ec49836dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3ecaf330db in QEventDispatcherGlib::processEvents (this=0x7f3e20006580, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f3ecaed263a in QEventLoop::exec (this=this@entry=0x7f3e27ffec60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f3ecace3317 in QThread::exec (this=) at thread/qthread.cpp:536 #6 0x7f3ecace47ec in QThreadPrivate::start (arg=0x7f3eac09ea50) at thread/qthread_unix.cpp:342 #7 0x7f3ec6b216db in start_thread (arg=0x7f3e27fff700) at pthread_create.c:463 #8 0x7f3eca5d988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f3e26ffd700 (LWP 18263)): #0 0x7ffd49dc099a in clock_gettime () #1 0x7f3eca5e8ea6 in __GI___clock_gettime (clock_id=clock_id@entry=1, tp=tp@entry=0x7f3e26ffc9e0) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f3ecaf329e1 in qt_clock_gettime (ts=0x7f3e26ffc9e0, clock=) at kernel/qelapsedtimer_unix.cpp:111 #3 do_gettime (frac=, sec=) at kernel/qelapsedtimer_unix.cpp:166 #4 qt_gettime () at kernel/qelapsedtimer_unix.cpp:175 #5 0x7f3ecaf31219 in QTimerInfoList::updateCurrentTime (this=this@entry=0x562822929830) at kernel/qtimerinfo_unix.cpp:91 #6 0x7f3ecaf317f5 in QTimerInfoList::timerWait (this=0x562822929830, tm=...) at kernel/qtimerinfo_unix.cpp:388 #7 0x7f3ecaf3344c in timerSourcePrepareHelper (timeout=0x7f3e26ffca94, src=) at kernel/qeventdispatcher_glib.cpp:133 #8 idleTimerSourcePrepare (source=, timeout=0x7f3e26ffca94) at kernel/qeventdispatcher_glib.cpp:213 #9 0x7f3ec4982b28 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f3ec49834fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f3ec49836dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f3ecaf330db in QEventDispatcherGlib::processEvents (this=0x562820aba3d0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #13 0x7f3ecaed263a in QEventLoop::exec (this=this@entry=0x7f3e26ffcc60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #14 0x7f3ecace3317 in QThread::exec (this=) at thread/qthread.cpp:536 #15 0x7f3ecace47ec in QThreadPrivate::start (arg=0x562820a7a7a0) at thread/qthread_unix.cpp:342 #16 0x7f3ec6b216db in start_thread (arg=0x7f3e26ffd700) at pthread_create.c:463 #17 0x7f3eca5d988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f3e277fe700 (LWP 18241)): #0 0x7f3ec49c9629 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f3ec49835af in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3ec49836dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3ecaf330db in QEventDispatcherGlib::processEvents (this=0x7f3e18000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f3ecaed263a in QEventLoop::exec (this=this@entry=0x7f3e277fdc60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f3ecace3317 in QThread::exec (this=) at thread/qthread.cpp:536 #6 0x7f3ecace47ec in QThreadPrivate::start (arg=0x562820f2f660) at thread/qthread_unix.cpp:342 #7 0x7f3ec6b216db in start_thread (arg=0x7f3e277fe700) at pthread_create.c:463 #8 0x7f3eca5d988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f3e40e0f700 (LWP 18237)): #0 0x7f3ec6b279f3 in futex_wait_cancelable (private=,
[digikam] [Bug 419047] Closing Face Tag Delete Dialog Box still ends up deleting face tag
https://bugs.kde.org/show_bug.cgi?id=419047 Kartik changed: What|Removed |Added CC||kartikx2...@gmail.com --- Comment #2 from Kartik --- Created attachment 127030 --> https://bugs.kde.org/attachment.cgi?id=127030=edit Second Dialog Box when Deleting Face Tags Hello Maik, I don't believe this is a duplicate of bug 384485, as that bug deals with Rejecting Face Suggestions. This bug is about pressing the close button of the Dialog Box when deleting face tags. Even if we press the Cross on the second dialog box (which asks whether tags should be removed from the images also), the tag will end up being deleted. I'm aware that the user had been asked for confirmation whether he wanted to delete the face tag or not. However, I personally associate pressing cross with a "I want to cancel this process". Currently pressing cross is mapped to the No button. Is it desirable to add a cancel button to the second dialog? So that pressing cross could instead not delete anything at all? Thanks Kartik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419187] Kwin High CPU usage when notification arrives
https://bugs.kde.org/show_bug.cgi?id=419187 --- Comment #2 from whew-...@outlook.com --- Disabling "Force (Full) Composition Pipeline" in NVIDIA settings and exporting KWIN_TRIPLE_BUFFER=1 seems to lower the usage spike significantly. OpenGL 3.1: ~10% OpenGL 2.0: ~10% XRender: <2% (These are measured in KSysGuard, Process Table, "CPU %" without dividing by number of CPUs) Unfortunately the lag is still there with OpenGL, although less severe. Using XRender makes it nearly unnoticeable. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 414440] Brightness gets maximized after screen times out.
https://bugs.kde.org/show_bug.cgi?id=414440 Pietro F. Fontana changed: What|Removed |Added Ever confirmed|0 |1 CC||pietro.font...@posteo.net Status|REPORTED|CONFIRMED --- Comment #1 from Pietro F. Fontana --- I can confirm this issue on a Plasma/Wayland session. Operating System: Manjaro Linux KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 Kernel Version: 5.5.13-1-MANJARO OS Type: 64-bit Device: Intel HD Graphics 620 driver: i915 v: kernel Display: wayland server: X.org 1.20.7 driver: modesetting See also this other report: https://bugs.kde.org/show_bug.cgi?id=383307 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384660] Part of the screen(s) "often" flickers when showing windows
https://bugs.kde.org/show_bug.cgi?id=384660 --- Comment #21 from triffid.hun...@gmail.com --- After more extensive experimentation, this certainly makes it a lot more difficult to trigger the underlying bug (my previously reliable trigger methods failed at first) but doesn't prevent it completely. My desktop is now flickering again when windows are shown, even with this patch :( -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 419226] Ark does not seem to support this file type.
https://bugs.kde.org/show_bug.cgi?id=419226 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- What file are we talking about? Can you share it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419197] Disabled system tray entries are diplayed as always shown
https://bugs.kde.org/show_bug.cgi?id=419197 Nicolas Fella changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-workspace/fede85a3d0ea5 ||a30755582e947cabd6bc7d1e4b8 Resolution|--- |FIXED --- Comment #1 from Nicolas Fella --- Git commit fede85a3d0ea5a30755582e947cabd6bc7d1e4b8 by Nicolas Fella. Committed on 26/03/2020 at 15:49. Pushed by nicolasfella into branch 'Plasma/5.18'. [applets/systemtray] Clear item from shown/hidden list when disabling entry Summary: Else the entry is still in cfg_shownItems/cfg_hiddenItems and the config UI will display it as shown instead of disabled. Reviewers: #plasma, kmaterka, broulik Reviewed By: #plasma, broulik Subscribers: broulik, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28311 M +6-0applets/systemtray/package/contents/ui/ConfigEntries.qml https://commits.kde.org/plasma-workspace/fede85a3d0ea5a30755582e947cabd6bc7d1e4b8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419197] Disabled system tray entries are diplayed as always shown
https://bugs.kde.org/show_bug.cgi?id=419197 Nate Graham changed: What|Removed |Added Version Fixed In||5.18.4 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 418979] Wrong LaTeX syntax highlighting after braces in optional argument of \cite
https://bugs.kde.org/show_bug.cgi?id=418979 Christoph Cullmann changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/syn ||tax-highlighting/213d4bb197 ||a3d86c053a5f9a2d31a665f0864 ||602 Status|CONFIRMED |RESOLVED --- Comment #1 from Christoph Cullmann --- Git commit 213d4bb197a3d86c053a5f9a2d31a665f0864602 by Christoph Cullmann, on behalf of Nibaldo González. Committed on 26/03/2020 at 15:48. Pushed by cullmann into branch 'master'. LaTeX: fix math parentheses in optional labels Summary: Single parentheses within `[...]` were highlighted as math text, but the math text is `\(...\)`. Reviewers: #framework_syntax_highlighting, dhaumann, cullmann, jpoelen Reviewed By: #framework_syntax_highlighting, cullmann Subscribers: kwrite-devel, kde-frameworks-devel Tags: #kate, #frameworks Differential Revision: https://phabricator.kde.org/D28303 M +4-0autotests/folding/highlight.tex.fold M +4-0autotests/html/highlight.tex.html M +4-0autotests/input/highlight.tex M +4-0autotests/reference/highlight.tex.ref M +4-4data/syntax/latex.xml https://commits.kde.org/syntax-highlighting/213d4bb197a3d86c053a5f9a2d31a665f0864602 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419197] Disabled system tray entries are diplayed as always shown
https://bugs.kde.org/show_bug.cgi?id=419197 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419234] There are no previews of wallpapers in the Desktop Settings window
https://bugs.kde.org/show_bug.cgi?id=419234 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396286] KF5 ofximporter "Map account" fails on MS Windows
https://bugs.kde.org/show_bug.cgi?id=396286 Thomas Baumgart changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||5.0.9 Latest Commit||https://commits.kde.org/kmy ||money/1989a4296d070c9ad9625 ||78815ab4fa169f61706 --- Comment #3 from Thomas Baumgart --- Git commit 1989a4296d070c9ad962578815ab4fa169f61706 by Thomas Baumgart. Committed on 26/03/2020 at 15:36. Pushed by tbaumgart into branch '5.0'. Fix local filename on windows for ofx banking FIXED-IN: 5.0.9 M +43 -24 kmymoney/plugins/ofx/import/ofxpartner.cpp M +17 -17 kmymoney/plugins/ofx/import/ofxpartner.h https://commits.kde.org/kmymoney/1989a4296d070c9ad962578815ab4fa169f61706 -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 419272] New: Apps that put folders with dots in /Frameworks/ folder will fail to sign
https://bugs.kde.org/show_bug.cgi?id=419272 Bug ID: 419272 Summary: Apps that put folders with dots in /Frameworks/ folder will fail to sign Product: Craft Version: unspecified Platform: Other OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Core Assignee: vonr...@kde.org Reporter: m...@dawidwrobel.com CC: kde-wind...@kde.org Target Milestone: --- SUMMARY codesign will refuse to sign the KMyMoney.app due to "tcl8.6" and "grantlee/5.2" in Framework/ folder. The reasoning behind this is explained here: https://developer.apple.com/library/archive/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG201 More discussion: https://stackoverflow.com/questions/37737829/codesign-osx-app-bundle-with-periods-in-macos-directory-names Proposed solution for QT-specific apps: https://github.com/pyinstaller/pyinstaller/wiki/Recipe-OSX-Code-Signing-Qt This is essentially an upstream QT issue, but still requires a workaround for craft to work properly. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT 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.
[krita] [Bug 414576] Zoom failure in 4.2.8 but not in 4.2.7.
https://bugs.kde.org/show_bug.cgi?id=414576 --- Comment #45 from Alex Mandrei --- (In reply to Alex Mandrei from comment #44) > (In reply to Alex Mandrei from comment #43) > > As with the update for the Krita 4.2.9(i was using the previous version > > before updating) the zooming is choppy ,it freezes anytime I zoom by holding > > control and drag.Zooming works fine by using the navigator docker or by > > using my mouse wheel.I didn't not experience such thing in the previous > > version(s). > > I'm new to this and i don't know what further information i should add:) > > > > There my system info > > Krita > > > > Version: 4.2.9 > > Languages: en_US, en > > Hidpi: true > > > > Qt > > > > Version (compiled): 5.12.7 > > Version (loaded): 5.12.7 > > > > OS Information > > > > Build ABI: x86_64-little_endian-llp64 > > Build CPU: x86_64 > > CPU: x86_64 > > Kernel Type: winnt > > Kernel Version: 10.0.18362 > > Pretty Productname: Windows 10 (10.0) > > Product Type: windows > > Product Version: 10 > > > > OpenGL Info > > > > Vendor: "NVIDIA Corporation" > > Renderer: "GeForce 410M/PCIe/SSE2" > > Version: "4.5.0 NVIDIA 382.05" > > Shading language: "4.50 NVIDIA" > > Requested format: QSurfaceFormat(version 2.0, options > > QFlags(), depthBufferSize -1, redBufferSize > > -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, > > stencilBufferSize -1, samples -1, swapBehavior > > QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace > > QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) > > Current format:QSurfaceFormat(version 4.5, options > > QFlags(DeprecatedFunctions), depthBufferSize > > 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, > > stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DoubleBuffer, > > swapInterval 1, colorSpace QSurfaceFormat::sRGBColorSpace, profile > > QSurfaceFormat::CompatibilityProfile) > > Version: 4.5 > > Supports deprecated functions true > > is OpenGL ES: false > > > > QPA OpenGL Detection Info > > supportsDesktopGL: true > > supportsAngleD3D11: true > > isQtPreferAngle: false > > > > Hardware Information > > > > GPU Acceleration: none > > Memory: 4077 Mb > > Number of Cores: 4 > > Swap Location: C:/Users/molne/AppData/Local/Temp > > > > Current Settings > > > > Current Swap Location: C:/Users/molne/AppData/Local/Temp > > Undo Enabled: 1 > > Undo Stack Limit: 30 > > Use OpenGL: 0 > > Use OpenGL Texture Buffer: 1 > > Use AMD Vectorization Workaround: 1 > > Canvas State: OPENGL_SUCCESS > > Autosave Interval: 900 > > Use Backup Files: 1 > > Number of Backups Kept: 1 > > Backup File Suffix: ~ > > Backup Location: Same Folder as the File > > Use Win8 Pointer Input: 0 > > Use RightMiddleTabletButton Workaround: 0 > > Levels of Detail Enabled: 0 > > Use Zip64: 0 > > > > > > Display Information > > Number of screens: 1 > > Screen: 0 > > Name: \\.\DISPLAY1 > > Depth: 32 > > Scale: 1 > > Resolution in pixels: 1680x1050 > > Manufacturer: > > Model: > > Refresh Rate: 60 > > Additional info ,i'm using a One by Wacom tablet(not the new Wacom one > display) and i have the latest drivers installed! I just tried some new settings and ,i enabled canvas acceleration and i put the by angle renderer and it works better now,it doesnt freezes anymore for like 5 seconds anytime i zoom but just zooms very laggy,like,it goes in laggy steps ,it s usable now tho but still bad.. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415669] Vanishing Point assistant, angle density slider has not-working up/down controls.
https://bugs.kde.org/show_bug.cgi?id=415669 Scott Petrovic changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/db1cc49ba2f4d4 ||f7287e852a6c4ec3d5922d5d4c --- Comment #3 from Scott Petrovic --- Git commit db1cc49ba2f4d4f7287e852a6c4ec3d5922d5d4c by Scott Petrovic. Committed on 26/03/2020 at 15:28. Pushed by scottpetrovic into branch 'master'. Change cursor to pointer on up and down arrow for sliderbox input Also fixed a couple sliders that had non-working up and down arrows M +13 -1libs/widgetutils/kis_slider_spin_box.cpp M +1-1plugins/assistants/Assistants/kis_assistant_tool.cc M +1-1plugins/tools/basictools/kis_tool_multihand.cpp https://invent.kde.org/kde/krita/commit/db1cc49ba2f4d4f7287e852a6c4ec3d5922d5d4c -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414576] Zoom failure in 4.2.8 but not in 4.2.7.
https://bugs.kde.org/show_bug.cgi?id=414576 --- Comment #44 from Alex Mandrei --- (In reply to Alex Mandrei from comment #43) > As with the update for the Krita 4.2.9(i was using the previous version > before updating) the zooming is choppy ,it freezes anytime I zoom by holding > control and drag.Zooming works fine by using the navigator docker or by > using my mouse wheel.I didn't not experience such thing in the previous > version(s). > I'm new to this and i don't know what further information i should add:) > > There my system info > Krita > > Version: 4.2.9 > Languages: en_US, en > Hidpi: true > > Qt > > Version (compiled): 5.12.7 > Version (loaded): 5.12.7 > > OS Information > > Build ABI: x86_64-little_endian-llp64 > Build CPU: x86_64 > CPU: x86_64 > Kernel Type: winnt > Kernel Version: 10.0.18362 > Pretty Productname: Windows 10 (10.0) > Product Type: windows > Product Version: 10 > > OpenGL Info > > Vendor: "NVIDIA Corporation" > Renderer: "GeForce 410M/PCIe/SSE2" > Version: "4.5.0 NVIDIA 382.05" > Shading language: "4.50 NVIDIA" > Requested format: QSurfaceFormat(version 2.0, options > QFlags(), depthBufferSize -1, redBufferSize > -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, > stencilBufferSize -1, samples -1, swapBehavior > QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace > QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) > Current format:QSurfaceFormat(version 4.5, options > QFlags(DeprecatedFunctions), depthBufferSize > 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, > stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DoubleBuffer, > swapInterval 1, colorSpace QSurfaceFormat::sRGBColorSpace, profile > QSurfaceFormat::CompatibilityProfile) > Version: 4.5 > Supports deprecated functions true > is OpenGL ES: false > > QPA OpenGL Detection Info > supportsDesktopGL: true > supportsAngleD3D11: true > isQtPreferAngle: false > > Hardware Information > > GPU Acceleration: none > Memory: 4077 Mb > Number of Cores: 4 > Swap Location: C:/Users/molne/AppData/Local/Temp > > Current Settings > > Current Swap Location: C:/Users/molne/AppData/Local/Temp > Undo Enabled: 1 > Undo Stack Limit: 30 > Use OpenGL: 0 > Use OpenGL Texture Buffer: 1 > Use AMD Vectorization Workaround: 1 > Canvas State: OPENGL_SUCCESS > Autosave Interval: 900 > Use Backup Files: 1 > Number of Backups Kept: 1 > Backup File Suffix: ~ > Backup Location: Same Folder as the File > Use Win8 Pointer Input: 0 > Use RightMiddleTabletButton Workaround: 0 > Levels of Detail Enabled: 0 > Use Zip64: 0 > > > Display Information > Number of screens: 1 > Screen: 0 > Name: \\.\DISPLAY1 > Depth: 32 > Scale: 1 > Resolution in pixels: 1680x1050 > Manufacturer: > Model: > Refresh Rate: 60 Additional info ,i'm using a One by Wacom tablet(not the new Wacom one display) and i have the latest drivers installed! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414576] Zoom failure in 4.2.8 but not in 4.2.7.
https://bugs.kde.org/show_bug.cgi?id=414576 Alex Mandrei changed: What|Removed |Added CC||mandrei.a...@gmail.com --- Comment #43 from Alex Mandrei --- As with the update for the Krita 4.2.9(i was using the previous version before updating) the zooming is choppy ,it freezes anytime I zoom by holding control and drag.Zooming works fine by using the navigator docker or by using my mouse wheel.I didn't not experience such thing in the previous version(s). I'm new to this and i don't know what further information i should add:) There my system info Krita Version: 4.2.9 Languages: en_US, en Hidpi: true Qt Version (compiled): 5.12.7 Version (loaded): 5.12.7 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.18362 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 OpenGL Info Vendor: "NVIDIA Corporation" Renderer: "GeForce 410M/PCIe/SSE2" Version: "4.5.0 NVIDIA 382.05" Shading language: "4.50 NVIDIA" Requested format: QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize -1, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Current format:QSurfaceFormat(version 4.5, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 1, colorSpace QSurfaceFormat::sRGBColorSpace, profile QSurfaceFormat::CompatibilityProfile) Version: 4.5 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsAngleD3D11: true isQtPreferAngle: false Hardware Information GPU Acceleration: none Memory: 4077 Mb Number of Cores: 4 Swap Location: C:/Users/molne/AppData/Local/Temp Current Settings Current Swap Location: C:/Users/molne/AppData/Local/Temp Undo Enabled: 1 Undo Stack Limit: 30 Use OpenGL: 0 Use OpenGL Texture Buffer: 1 Use AMD Vectorization Workaround: 1 Canvas State: OPENGL_SUCCESS Autosave Interval: 900 Use Backup Files: 1 Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Use Win8 Pointer Input: 0 Use RightMiddleTabletButton Workaround: 0 Levels of Detail Enabled: 0 Use Zip64: 0 Display Information Number of screens: 1 Screen: 0 Name: \\.\DISPLAY1 Depth: 32 Scale: 1 Resolution in pixels: 1680x1050 Manufacturer: Model: Refresh Rate: 60 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396286] KF5 ofximporter "Map account" fails on MS Windows
https://bugs.kde.org/show_bug.cgi?id=396286 --- Comment #2 from Thomas Baumgart --- citapinc: take your browser and load the 'empty' page from "http://www.ofxhome.com/api.php?all=yes;. Then direct your browser to show you the source code of the page and you will notice, that it not empty at all. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 388259] Drag and drop across dolphin instances: cursor must be moved after modifier key is pressed for modifier key to take effect
https://bugs.kde.org/show_bug.cgi?id=388259 --- Comment #23 from Patrick Silva --- Fixed on X11. :) But it's still broken on Wayland. :( dolphin 20.03.80 built from sources Operating System: Arch Linux KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.15.0 beta2 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 419271] New: false positives due to not recognizing vpxor as dependency breaking idiom
https://bugs.kde.org/show_bug.cgi?id=419271
Bug ID: 419271
Summary: false positives due to not recognizing vpxor as
dependency breaking idiom
Product: valgrind
Version: 3.13.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: rzarz...@redhat.com
Target Milestone: ---
Following code is a variant of dependency breaking idiom:
vmovdqa %xmm0,%xmm3
vpxor %xmm0,%xmm3,%xmm3
Value of xmm3 will always be cleared but it seems Valgrind misses that
when computing the validity bits:
(gdb) info registers xmm3 xmm3s1 xmm3s2
xmm3 {... uint128 = 0x}
xmm3s1 {... uint128 = 0xff00}
More output from gdb on debugging `gcm_ghash_avx` of OpenSSL:
Breakpoint 2, gcm_ghash_avx () at ghash-x86_64.s:1365
1365vzeroupper
(gdb) stepi
...
1598vmovdqa %xmm0,%xmm3
(gdb) info registers xmm0 xmm0s1 xmm0s2
xmm0 {... uint128 = 0x00b4560115ffdd21dcc25ea8}
xmm0s1 {... uint128 = 0xff00}
xmm0s2 {... uint128 = 0x}
(gdb) stepi
1599vmovdqa %xmm1,%xmm4
(gdb) info registers xmm3 xmm3s1 xmm3s2
xmm3 {... uint128 = 0x00b4560115ffdd21dcc25ea8}
xmm3s1 {... uint128 = 0xff00}
xmm3s2 {... uint128 = 0x}
(gdb) stepi
1600vmovdqa %xmm2,%xmm5
(gdb) stepi
1601subq$0x10,%rcx
(gdb)
1602jz .Ltail_avx
(gdb)
1696vpxor %xmm10,%xmm15,%xmm15
(gdb)
1698vpunpckhqdq %xmm15,%xmm15,%xmm8
(gdb)
1699vpxor %xmm0,%xmm3,%xmm3
(gdb) stepi
1700vpclmulqdq $0x00,%xmm6,%xmm15,%xmm0
(gdb) info registers xmm0 xmm0s1 xmm0s2
xmm0 {... uint128 = 0x00b4560115ffdd21dcc25ea8}
xmm0s1 {... uint128 = 0xff00}
xmm0s2 {... uint128 = 0x}
(gdb) info registers xmm3 xmm3s1 xmm3s2
xmm3 {... uint128 = 0x}
xmm3s1 {... uint128 = 0xff00}
xmm3s2 {... uint128 = 0x}
--
You are receiving this mail because:
You are watching all bug changes.
[kio-extras] [Bug 419244] kf5.kio.core: finished() called twice! Please fix the kio_sftp KIO slave
https://bugs.kde.org/show_bug.cgi?id=419244 --- Comment #2 from Erik Quaeghebeur --- For others encountering this issue: I worked around it by copying first from one server to local storage and the from local storage to the other server. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419270] Krita crashes immediately when launched from desktop launcher
https://bugs.kde.org/show_bug.cgi?id=419270 Marie Kalouguine changed: What|Removed |Added Platform|Appimage|Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419270] Krita crashes immediately when launched from desktop launcher
https://bugs.kde.org/show_bug.cgi?id=419270 Marie Kalouguine changed: What|Removed |Added Platform|Archlinux Packages |Appimage -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419270] Krita crashes immediately when launched from desktop launcher
https://bugs.kde.org/show_bug.cgi?id=419270 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |DOWNSTREAM CC||b...@valdyas.org Status|REPORTED|RESOLVED --- Comment #1 from Boudewijn Rempt --- Hi Marie, Please use the appimage instead of an Arch linux package; the problem is most likely a build error because some library didn't get updated after arch updated the Krita recipe. You can also report this to Arch Linux so they can fix their packages... But it's not a bug in Krita that we can fix. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419270] New: Krita crashes immediately when launched from desktop launcher
https://bugs.kde.org/show_bug.cgi?id=419270 Bug ID: 419270 Summary: Krita crashes immediately when launched from desktop launcher Product: krita Version: 4.2.9 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: marie.kalougu...@hotmail.com Target Milestone: --- Created attachment 127029 --> https://bugs.kde.org/attachment.cgi?id=127029=edit Result of running from cli SUMMARY STEPS TO REPRODUCE 1. use auto generated launcher ( associated command : krita %F ) 2. click on it OBSERVED RESULT Krita doesn't launch, immediately crashes. EXPECTED RESULT Normal launch. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION Kde bug report gives this backtrace : Application: krita (krita), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [KCrash Handler] #6 0x558612c1d410 in QtPrivate::RefCount::ref() () #7 0x558612c1c422 in main () [Inferior 1 (process 5879) detached] >From command line runs fine but with warnings (output in attachment). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419269] Old Touchpad KCM is enabled on X11 session of Desktop computer without a touchpad device despite synaptics driver is not installed
https://bugs.kde.org/show_bug.cgi?id=419269 --- Comment #1 from Patrick Silva --- Created attachment 127028 --> https://bugs.kde.org/attachment.cgi?id=127028=edit Touchpad KCM on Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419269] New: Old Touchpad KCM is enabled on X11 session of Desktop computer without a touchpad device despite synaptics driver is not installed
https://bugs.kde.org/show_bug.cgi?id=419269 Bug ID: 419269 Summary: Old Touchpad KCM is enabled on X11 session of Desktop computer without a touchpad device despite synaptics driver is not installed Product: systemsettings Version: 5.18.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 127027 --> https://bugs.kde.org/attachment.cgi?id=127027=edit Touchpad KCM on X11 xf86-input-libinput driver is installed and xf86-input-synaptics driver is not installed on my desktop computer running Arch Linux but I see the old Touchpad KCM in system settings when running X11 session anyway. On Wayland session I see the libinput Touchpad KCM as expected. Compare the attached screenshots please. STEPS TO REPRODUCE 1. use a desktop computer without a touchpad device and make sure synaptics touchpad driver is not installed 2. open system settings > input devices > touchpad on X11 session 3. open system settings > input devices > touchpad on X11 session on Wayland sesison EXPECTED RESULT libinput Touchpad kcm should always be present in system settings when synaptics touchpad driver is not installed. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 419263] Right click on system tray icon brings wrong menu
https://bugs.kde.org/show_bug.cgi?id=419263 --- Comment #6 from Michail Vourlakos --- (In reply to Yannick Roehlly from comment #5) > Hi Michail. > > I've tested the new code. It works! Thanks for the super fast answer and > correction. > > Concerning your last comment, I don't have the problem with the 0.9.9 > version. You are right, I checked it a line that was important, was lost during 0.9.10 if this is noticed by many users I will release 0.9.11 sooner -- You are receiving this mail because: You are watching all bug changes.
