[krita] [Bug 408171] New: Filter layer properties layer name textbox not correctly themed
https://bugs.kde.org/show_bug.cgi?id=408171 Bug ID: 408171 Summary: Filter layer properties layer name textbox not correctly themed Product: krita Version: 4.2.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: minor Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: carl.ols...@gmail.com Target Milestone: --- SUMMARY The layer name textbox in the filter layer properties dialog is not correctly themed. It appears rendered in windows default theme while other layer properties dialogs theme it as expected following the rest of the Krita theme. STEPS TO REPRODUCE 1. Select Krita dark theme 2. Open filter layer properties dialog OBSERVED RESULT Layer name textbox is seemingly rendered using default windows theme (light with blue focus highlight). EXPECTED RESULT Layer name textbox themed in accordance with the rest of Krita. SOFTWARE/OS VERSIONS Windows: Microsoft Windows 10 Pro 10.0.17763 Build 17763 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408163] Metadata selecting and editing fails for date updating
https://bugs.kde.org/show_bug.cgi?id=408163 --- Comment #3 from Maik Qualmann --- Thanks for the animation. As I said, not reproduce here with the current GIT version of digiKam-6.2.0. We are both at the same version, my Qt version is already 5.12.3. Do you use sidecar files? Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408170] Layer properties window draws on top of other application windows
https://bugs.kde.org/show_bug.cgi?id=408170 --- Comment #1 from Carl Olsson --- Seems it's not a problem with all layer properties dialogs. It happens with the standard paint layer and fill layers, but not filter layers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408170] New: Layer properties window draws on top of other application windows
https://bugs.kde.org/show_bug.cgi?id=408170 Bug ID: 408170 Summary: Layer properties window draws on top of other application windows Product: krita Version: 4.2.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: carl.ols...@gmail.com Target Milestone: --- Created attachment 120468 --> https://bugs.kde.org/attachment.cgi?id=120468&action=edit Demonstrative image SUMMARY The layer properties dialog draws on top of other application windows and other Krita dialogs. Other krita dialogs don't have this problem. Perhaps to do with it being non-modal? STEPS TO REPRODUCE 1. Open layer properties dialog. 2. Switch to other application window which overlaps layer properties dialog. OBSERVED RESULT Layer properties dialog is drawn over top of other application window. EXPECTED RESULT Layer properties dialog should draw under other application window. SOFTWARE/OS VERSIONS Windows: Microsoft Windows 10 Pro 10.0.17763 Build 17763 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408169] New: Transparent pattern fill layer renders incorrect on load
https://bugs.kde.org/show_bug.cgi?id=408169 Bug ID: 408169 Summary: Transparent pattern fill layer renders incorrect on load Product: krita Version: 4.2.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: carl.ols...@gmail.com Target Milestone: --- Created attachment 120466 --> https://bugs.kde.org/attachment.cgi?id=120466&action=edit Above: after setting pattern, Below: after loading SUMMARY When loading a document with a pattern fill layer where the pattern is 1-bit or has alpha transparency it is rendered incorrectly as though the pattern Grid01.pat is rendered first, then the correct pattern is rendered over the top with transparency. It doesn't appear to happen with opaque (greyscale) patterns. STEPS TO REPRODUCE 1. Add fill layer with 1-bit pattern (eg. Stripes04.pat) 2. Observe correct pattern rendering 3. Save as Krita document 4. Close document 5. Reopen document OBSERVED RESULT Renders with what looks like Grid01.pat under selected pattern EXPECTED RESULT Render with selected pattern only SOFTWARE/OS VERSIONS Windows: Microsoft Windows 10 Pro 10.0.17763 Build 17763 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408163] Metadata selecting and editing fails for date updating
https://bugs.kde.org/show_bug.cgi?id=408163 --- Comment #2 from Aaron Wolf --- Created attachment 120467 --> https://bugs.kde.org/attachment.cgi?id=120467&action=edit Gif demonstrating bug 408163 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408167] Clone layers not updated when hidden fill layer changed
https://bugs.kde.org/show_bug.cgi?id=408167 Carl Olsson changed: What|Removed |Added Platform|Other |MS Windows OS|Linux |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408163] Metadata selecting and editing fails for date updating
https://bugs.kde.org/show_bug.cgi?id=408163 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- I can not reproduce it here. Gilles, can you please test it? Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 327480] Artificial sharp edges when using Color: Mix, Darken, Hue, Saturation, value in Wash Mode
https://bugs.kde.org/show_bug.cgi?id=327480 --- Comment #7 from vanyossi --- Created attachment 120465 --> https://bugs.kde.org/attachment.cgi?id=120465&action=edit Artificial edges more visible. Value set to pressure modifier. Both stroke blobs were made in a single stroke. On the left: the first dab is made with almost no pressure and the surounding dabas are made at strong pressure. Notice the edge is marked for the original shape if there is a change in the sensor value. On the right, eventually drawing over and over will remove the artifact as it only occurs on the "alpha" boundaries of the current stroke. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 327480] Artificial sharp edges when using Color: Mix, Darken, Hue, Saturation, value in Wash Mode
https://bugs.kde.org/show_bug.cgi?id=327480 vanyossi changed: What|Removed |Added Summary|Artificial sharp edges when |Artificial sharp edges when |using Color: Mix Fuzzy in |using Color: Mix, Darken, |Wash Mode |Hue, Saturation, value in ||Wash Mode -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 408168] New: symbol lookup error in kleopatra
https://bugs.kde.org/show_bug.cgi?id=408168 Bug ID: 408168 Summary: symbol lookup error in kleopatra Product: kleopatra Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aheine...@gnupg.org Reporter: storan...@gmail.com CC: kdepim-b...@kde.org, m...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. installed kleopatra via dnf 2. tried to open kleopatra via gnome menu 3. tried via terminal OBSERVED RESULT terminal output kleopatra: symbol lookup error: /lib64/libKF5KCMUtils.so.5: undefined symbol: _ZN12KQuickAddons12ConfigModule10pagePushedEP10QQuickItem 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 407138] Waiting for process to complete lasts forever and prevents saving or editing, causing work to be lost
https://bugs.kde.org/show_bug.cgi?id=407138 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[partitionmanager] [Bug 397302] KDE Partition manager crashing after upgrade
https://bugs.kde.org/show_bug.cgi?id=397302 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408149] Selection Transformation not available via Selection Tool.
https://bugs.kde.org/show_bug.cgi?id=408149 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #9 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408167] New: Clone layers not updated when hidden fill layer changed
https://bugs.kde.org/show_bug.cgi?id=408167 Bug ID: 408167 Summary: Clone layers not updated when hidden fill layer changed Product: krita Version: 4.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: carl.ols...@gmail.com Target Milestone: --- SUMMARY If a fill layer is hidden and the fill layer's pattern or colour are changed then any linked clone layers are not updated until visibility of the fill layer is toggled. May be related: https://bugs.kde.org/show_bug.cgi?id=405536 STEPS TO REPRODUCE 1. Add a fill layer with pattern 2. Clone fill layer 3. Hide fill layer 4. Change pattern in fill layer OBSERVED RESULT Clone layer pattern remains unchanged EXPECTED RESULT Clone layer pattern should be updated to match fill layer SOFTWARE/OS VERSIONS Windows: Microsoft Windows 10 Pro 10.0.17763 Build 17763 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408166] New: Rectangular grid spacing limits incorrect after resizing canvas
https://bugs.kde.org/show_bug.cgi?id=408166 Bug ID: 408166 Summary: Rectangular grid spacing limits incorrect after resizing canvas Product: krita Version: 4.2.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: carl.ols...@gmail.com Target Milestone: --- SUMMARY Normally the rectangular grid spacing appears to be limited to a maximum of half the image size, however after resizing an image the maximum spacing remains unchanged. Saving and reloading the resized image returns the grid spacing limit to the expected value for the image size. I don't see why it needs to be limited at all beyond the storage type limit. STEPS TO REPRODUCE 1. Create small image 2. Set rectangular grid spacing to maximum for image size 3. Resize canvas considerably larger 4. Try to increase grid spacing OBSERVED RESULT The grid spacing cannot be increased beyond the limit for the initial image size. EXPECTED RESULT The grid spacing should be able to increase to the expected limit of half the enlarged image size. SOFTWARE/OS VERSIONS Windows: Microsoft Windows 10 Pro 10.0.17763 Build 17763 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408163] Metadata selecting and editing fails for date updating
https://bugs.kde.org/show_bug.cgi?id=408163 caulier.gil...@gmail.com changed: What|Removed |Added Component|Usability-Mouse |Metadata-Editor CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408159] application launcher/menu stops showing when clicking the menu icon, sometimes plasmashell crashes
https://bugs.kde.org/show_bug.cgi?id=408159 --- Comment #2 from Ben Klopfenstein --- additional information: if I click the launcher icon OR a plasma implemented system tray icon too many times, the popup (menu, launcher, network details, etc) stops showing up. this particular behavior seems to be harder to trigger with the system tray, because if I click too quickly, plasmashell actually crashes. I can also get plasmashell to crash by clicking the application launcher too quickly -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407566] Dolphin crashes when opening a folder or a file
https://bugs.kde.org/show_bug.cgi?id=407566 --- Comment #7 from erkanisik --- https://i.hizliresim.com/1pjEjY.jpg -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408165] New: drag-and-drop cursor is not correct outside of same window
https://bugs.kde.org/show_bug.cgi?id=408165 Bug ID: 408165 Summary: drag-and-drop cursor is not correct outside of same window Product: kwin Version: 5.15.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: benk...@gmail.com Target Milestone: --- SUMMARY When dragging and dropping from one application to another, the cursor does not correctly indicate if the drag-and-drop target is valid. Within a single application, (dolphin for example) the cursor displays whether the drag-and-drop is a valid action, and changes between a 'no way' syymbol and an arrow with a + depending on if the target is acceptable. For instance dragging to the window borders is not acceptable and will not work. When dragging to another window, the cursor necessarily passes through the window border and changes to the 'no way' symbol. After exiting the window, it remains in this state, regardless of where you try to drag and drop, or if the target window will accept the drop. STEPS TO REPRODUCE 1. select a file in dolphin 2. drag it to the desktop 3. observe the cursor states during the drag 4. drop the file to the desktop 5. observe that a menu pops up, accepting the drop, even though the cursor indicated it was not going to work. OBSERVED RESULT When dragging to another window, the cursor necessarily passes through the window border and changes to the 'no way' symbol. After exiting the window, it remains in this state, regardless of where you try to drag and drop, or if the target window will accept the drop. EXPECTED RESULT The cursor state should indicate if the drop target is valid, both inside and outside the originating window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (available in About System) KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION This behavior differs somewhat when originating from an XWayland window - the cursor appears to change in response to the desktop accepting the drop, but if the cursor is moved over another window and then back to the desktop, it stops updating. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408149] Selection Transformation not available via Selection Tool.
https://bugs.kde.org/show_bug.cgi?id=408149 --- Comment #8 from Leo --- I would expect the selection being editable immediately, just as the crop tool selection is. Thus there is already similar functionality in Krita. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408149] Selection Transformation not available via Selection Tool.
https://bugs.kde.org/show_bug.cgi?id=408149 --- Comment #7 from Leo --- Yes, I noted that there has been some complex work put, and that vector masks are being used to achieve the editable selections. So kudos for that. It's a feature I have been missing in Krita for a long time. However, what I'm suggesting is that the selection should be immediately editable, with handles on the bounding box. See the attached images from other applications. Gimp and Inkscape already do this. How would it improve workflow? Zero further actions required to edit the selection versus the current two mouse clicks and movement. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 408162] wayland drag-n-drop from firefox to dolphin generates a pop-up menu with window decorations
https://bugs.kde.org/show_bug.cgi?id=408162 --- Comment #4 from Ben Klopfenstein --- It might be important to note that this only occurs for the first drag-n-drop to the application (dolphin). Once an action is chosen in that menu, all subsequent drag-n-drops seem to behave correctly (no window decorations). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 408162] wayland drag-n-drop from firefox to dolphin generates a pop-up menu with window decorations
https://bugs.kde.org/show_bug.cgi?id=408162 Ben Klopfenstein changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |fa...@kde.org CC||kdelibs-b...@kde.org Version|5.15.90 |5.58.0 Product|kwin|frameworks-kio Component|decorations |general --- Comment #3 from Ben Klopfenstein --- As suggested by fvogt here: https://matrix.to/#/!NIrfttwcKodEknQLjd:matrix.org/$1559338345398426pTfRZ:matrix.org?via=matrix.org&via=kde.org, this seems likely to be a bug in KIO, not kwin. I'm changing the -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408162] wayland drag-n-drop from firefox to dolphin generates a pop-up menu with window decorations
https://bugs.kde.org/show_bug.cgi?id=408162 --- Comment #2 from Ben Klopfenstein --- This also occurs with DnD from konqueror to dolphin, so it is not related (both running as native wayland apps) so this is not related to XWayland. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408164] the krita is closed sunddely
https://bugs.kde.org/show_bug.cgi?id=408164 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Hi Antonio, Thanks for making the effort to make a report, but you're not giving any information whatsoever that would enable us to do anything. For the version, you entered "4.1.5" -- if that is correct, please update to 4.2.0, which was released this week. If not, please try to reproduce the crash, and if you have found a way to reproduce, add a crash log. See https://docs.krita.org/en/reference_manual/dr_minw_debugger.html#dr-minw for instructions. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408164] Krita is closed suddenly
https://bugs.kde.org/show_bug.cgi?id=408164 Boudewijn Rempt changed: What|Removed |Added Severity|normal |crash Summary|the krita is closed |Krita is closed suddenly |sunddely| -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408161] UP ARROW doesn't work in konsole 19.04.1
https://bugs.kde.org/show_bug.cgi?id=408161 --- Comment #2 from Yuriy Vidineev --- Looks like I'm not the only one https://forum.kde.org/viewtopic.php?f=227&t=160348&sid=3135337f2e80224f72fb17126e687475 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408162] wayland drag-n-drop from firefox to dolphin generates a pop-up menu with window decorations
https://bugs.kde.org/show_bug.cgi?id=408162 --- Comment #1 from Ben Klopfenstein --- Firefox is in fact running in xwayland. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408164] New: the krita is closed sunddely
https://bugs.kde.org/show_bug.cgi?id=408164 Bug ID: 408164 Summary: the krita is closed sunddely Product: krita Version: 4.1.5 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: didioph...@gmail.com Target Milestone: --- SUMMARY 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.
[digikam] [Bug 408163] New: Metadata selecting and editing fails for date updating
https://bugs.kde.org/show_bug.cgi?id=408163 Bug ID: 408163 Summary: Metadata selecting and editing fails for date updating Product: digikam Version: 6.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability-Mouse Assignee: digikam-bugs-n...@kde.org Reporter: wolft...@gmail.com Target Milestone: --- SUMMARY I can edit the date in the metadata, but it won't save unless I use the date-picker approach STEPS TO REPRODUCE 1. choose Item > Edit Metadata… 2. *select* the year in one of the dates using the cursor, as in text editing 3. type new number 4. click apply OBSERVED RESULT The date reverts to the previous and does not apply EXPECTED RESULT The updated date is applied Note: if I click on the date and then use the up or down arrows to change it, then it works, but selecting a number and typing a new one is where it fails. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #58 from Guilherme Almeida --- Now I'm using Arch Linux with Optimus Manager and I am not being affected by the issue here. Kernel: 5.1.5-arch1-2-ARCH Kwin: 5.15.5 KDE FW: 5.58.0 Qt: 5.12.3 NVidia: 430.14-6 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 407527] Breeze icons needed for kcachegrind, kxstitch, knights, and smb4k
https://bugs.kde.org/show_bug.cgi?id=407527 --- Comment #10 from Jonathan Riddell --- krita gcompris-qt -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408162] wayland drag-n-drop from firefox to dolphin generates a pop-up menu with window decorations
https://bugs.kde.org/show_bug.cgi?id=408162 Ben Klopfenstein changed: What|Removed |Added Platform|Other |Archlinux Packages Version|unspecified |5.15.90 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408162] New: wayland drag-n-drop from firefox to dolphin generates a pop-up menu with window decorations
https://bugs.kde.org/show_bug.cgi?id=408162 Bug ID: 408162 Summary: wayland drag-n-drop from firefox to dolphin generates a pop-up menu with window decorations Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: benk...@gmail.com Target Milestone: --- Created attachment 120464 --> https://bugs.kde.org/attachment.cgi?id=120464&action=edit screenshot showing drag-and-drop context menu with window decorations SUMMARY Using wayland, When dragging a link from firefox to a dolphin window creates a pop-up that has window decorations STEPS TO REPRODUCE 1. use wayland. 2. open a new firefox window. open a new dolphin window. 3. click a link in firefox, and drag it into dolphin OBSERVED RESULT The menu comes up prompting the user whether they want to "move here, copy here, or link here." However, the menu has window decorations. If you choose one of the choices, the next time you drag/drop to dolphin, the menu does NOT have window decorations. EXPECTED RESULT Ignoring the fact that not all these choices make sense for a URL, menus should never have window decorations. Ideally, the menu should contain choices that are relevant in the context of a URL, but that should probably be a different bug. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (available in About System) KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION This occurs on wayland. I'm unsure if Firefox is running in XWayland, but I don't _think_ so, as it does smooth scrolling with touchscreen events, and that does not work under X11. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408161] UP ARROW doesn't work in konsole 19.04.1
https://bugs.kde.org/show_bug.cgi?id=408161 --- Comment #1 from Yuriy Vidineev --- Forgot to mention: up arrow still works fine in xterm. And CTRL+P works in konsole (but not the UP ARROW) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408161] New: UP ARROW doesn't work in konsole 19.04.1
https://bugs.kde.org/show_bug.cgi?id=408161 Bug ID: 408161 Summary: UP ARROW doesn't work in konsole 19.04.1 Product: konsole Version: 19.04.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: history Assignee: konsole-de...@kde.org Reporter: adeptsm...@gmail.com Target Milestone: --- SUMMARY In konsole 18.12 UP ARROW used to show previous command. It does nothing after update to konsole 19.04.1 on KDE Neon User with all updates STEPS TO REPRODUCE 1. Open konsole (19.04.1 version) 2. Push UP ARROW OBSERVED RESULT Nothing happened EXPECTED RESULT Previous command from .bash_history is displayed SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.15 (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.0 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 374864] Using "Capture the current pop-up only" option causes Spectacle to disappear with compositing enabled
https://bugs.kde.org/show_bug.cgi?id=374864 Nate Graham changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #16 from Nate Graham --- Thanks. Can you file a new bug for that? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408160] New: Workspace saves docker positions but not docker sizes (width, height) on restart.
https://bugs.kde.org/show_bug.cgi?id=408160 Bug ID: 408160 Summary: Workspace saves docker positions but not docker sizes (width, height) on restart. Product: krita Version: 4.2.0 Platform: MS Windows OS: Windows CE Status: REPORTED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: viktorsla...@viksl.com Target Milestone: --- Created attachment 120463 --> https://bugs.kde.org/attachment.cgi?id=120463&action=edit on the left the workspace before restarting (right column's width was increased) and on the right after restarting (positions loaded their sizes not) SUMMARY Dockers have their positions saved but not their size (width, height), so if you start Krita, adjust sizes of dockers then close Krita and start it again the dockesr will retain only their position not transformation (size) and will shrink to the smallest width/height possible depeding on wheter it's a horizontal or vertical docker. It's possible to do it manually, after restarting Krita (point 4. below), go to Window - Workspace - Select your new workspace, it remembers the positions and most importantly the sizes as well. STEPS TO REPRODUCE 1. Open Krita 2. Adjust your workspace as yo usee fit (for example bring one docker to half the screen width or height wise - height for horizontal dockers, width for vertical dockers) 3. Save the workspace through Window - Workspace - New Workspace... 4. Restart Krita OBSERVED RESULT Dockers retain their position but not width and/or height, their size is set to the smallest possible. EXPECTED RESULT Workspace being the same as when it was saved, so position, width and height of all dockers (UI elements) to be stored and loaded everytime the workspace is loaded (Krita started). SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION In the attachement you can see on the left the workspace before restarting (right column's width was increased) and on the right after restarting (positions loaded their sizes not). It's one of the default workspaces but it's the same with a new Workspace you create on your own. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 374864] Using "Capture the current pop-up only" option causes Spectacle to disappear with compositing enabled
https://bugs.kde.org/show_bug.cgi?id=374864 Ben Klopfenstein changed: What|Removed |Added Status|RESOLVED|REOPENED CC||benk...@gmail.com Resolution|FIXED |--- --- Comment #15 from Ben Klopfenstein --- The fix that was comitted only works for X11 - for wayland, this problem still exists. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 390451] Horizontal lines when I use 1.2 display scale under X11
https://bugs.kde.org/show_bug.cgi?id=390451 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 406770] Recent anti-aliasing change is causing black lines on HiDPI displays
https://bugs.kde.org/show_bug.cgi?id=406770 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408159] application launcher/menu stops showing when clicking the menu icon, sometimes plasmashell crashes
https://bugs.kde.org/show_bug.cgi?id=408159 --- Comment #1 from Ben Klopfenstein --- Actually, I seem to be able to make plasmashell crash by very quickly repeatedly clicking on system tray icons as well, but _not_ taskbar buttons, so I'm not really sure what the right component is. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408159] New: application launcher/menu stops showing when clicking the menu icon, sometimes plasmashell crashes
https://bugs.kde.org/show_bug.cgi?id=408159 Bug ID: 408159 Summary: application launcher/menu stops showing when clicking the menu icon, sometimes plasmashell crashes Product: plasmashell Version: 5.15.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: benk...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY sometimes, randomly, the application launcher stops appearing when clicking the menu button (or pressing the WIN shortcut key). STEPS TO REPRODUCE 1. upgrade to 5.15.90 on arch linux 2. press the menu button quickly/repeatedly. OBSERVED RESULT the application launcher shows / hides repeatedly, but eventually it stops and no longer will become visible when the button is pressed. switching to a different alternative (application menu) restores functionality, but that launcher can then be broken in the same manner. sometimes plasmashell crashes and starts back up when pressing the button quickly enough. EXPECTED RESULT the menu / launcher should be very robust and always show / hide when the button is pressed. plasmashell should never crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #133 from Søren Holm --- Great work Daniel. I switched from kmail to thunderbird some months ago and I hate it. I look forward to this automatic repair getting into my distribution :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408149] Selection Transformation not available via Selection Tool.
https://bugs.kde.org/show_bug.cgi?id=408149 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #6 from Boudewijn Rempt --- Note, a bunch of screenshots from other applications are not an answer to Scott's question. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408095] Sort items by manual
https://bugs.kde.org/show_bug.cgi?id=408095 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||6.2.0 Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/bff98bd59077 ||ad6e740f5d32654678bf1071e2c ||f --- Comment #4 from Maik Qualmann --- Git commit bff98bd59077ad6e740f5d32654678bf1071e2cf by Maik Qualmann. Committed on 31/05/2019 at 20:05. Pushed by mqualmann into branch 'master'. use creation date as fallback for manual item sort I think it's the best choice for most users. Using the last sort option also creates an opaque behavior. This does not affect views that have already been sorted manually. FIXED-IN: 6.2.0 M +2-1NEWS M +10 -1core/libs/database/models/itemsortsettings.cpp https://invent.kde.org/kde/digikam/commit/bff98bd59077ad6e740f5d32654678bf1071e2cf -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 408158] Power Management global shortcuts listed twice
https://bugs.kde.org/show_bug.cgi?id=408158 --- Comment #3 from Ben Klopfenstein --- I can confirm now that switching the key bindings to the other set of actions causes them to work. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 407721] Brightness keys no longer work with Plasma 5.16
https://bugs.kde.org/show_bug.cgi?id=407721 Antonio Rojas changed: What|Removed |Added CC||benk...@gmail.com --- Comment #10 from Antonio Rojas --- *** Bug 408158 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 408158] Power Management global shortcuts listed twice
https://bugs.kde.org/show_bug.cgi?id=408158 Antonio Rojas changed: What|Removed |Added Resolution|--- |DUPLICATE CC||aro...@archlinux.org Status|REPORTED|RESOLVED --- Comment #2 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 407721 *** -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 408138] Date of imported transactions not recognised
https://bugs.kde.org/show_bug.cgi?id=408138 --- Comment #3 from Christoph Vogtländer --- I confirm that the workaround in org.kde.skrooge-import-backend-aqbanking.desktop fixes the problem. Thank you very much. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 408158] Power Management global shortcuts listed twice
https://bugs.kde.org/show_bug.cgi?id=408158 --- Comment #1 from Ben Klopfenstein --- Created attachment 120462 --> https://bugs.kde.org/attachment.cgi?id=120462&action=edit Screenshot showing duplicated global shortcuts -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 408158] New: Power Management global shortcuts listed twice
https://bugs.kde.org/show_bug.cgi?id=408158 Bug ID: 408158 Summary: Power Management global shortcuts listed twice Product: Powerdevil Version: 5.15.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: benk...@gmail.com Target Milestone: --- SUMMARY Global shortcuts for Power Management appear to be duplicated, and those shortcuts do not currently work (i'm guessing that the un-assigned set are the ones that would actually work). STEPS TO REPRODUCE 1. Upgrade from current stable to 5.15.90 on Arch Linux 2. Reboot 3. Attempt to use global shortcuts for screen brightness, look in System Settings -> Shortcuts -> Global Shortcuts -> Power Management OBSERVED RESULT Each shortcut appears twice in the list, with the first having a key bound. the second is unbound. EXPECTED RESULT Only one set of shortcuts should be in the list SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION -- 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 --- Comment #97 from Jeffrey Bouter --- Created attachment 120461 --> https://bugs.kde.org/attachment.cgi?id=120461&action=edit Konsole Select Text There's no need to launch Midnight Commander, just selecting multiple lines will suffice. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 400838] Crash when closing message window with Qt 5.12
https://bugs.kde.org/show_bug.cgi?id=400838 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at --- Comment #5 from Wolfgang Bauer --- (In reply to Erik Quaeghebeur from comment #2) > Me (and others) are hitting this bug with 18.12.3 and Qt 5.12.3, so > reopening. (Updating version/platform/importance) According to https://bugs.gentoo.org/686842 this should be fixed already, no? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408157] "Tone Color Picker" cursor is not correctly positionned vs Mouse
https://bugs.kde.org/show_bug.cgi?id=408157 Maik Qualmann changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/85bede4b61ff ||03a3a9a2a783511044151f9244c ||7 Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||6.2.0 --- Comment #1 from Maik Qualmann --- Git commit 85bede4b61ff03a3a9a2a783511044151f9244c7 by Maik Qualmann. Committed on 31/05/2019 at 19:39. Pushed by mqualmann into branch 'master'. fix color picker cursor position FIXED-IN: 6.2.0 M +2-1NEWS M +1-1core/utilities/imageeditor/widgets/imageregionwidget.cpp https://invent.kde.org/kde/digikam/commit/85bede4b61ff03a3a9a2a783511044151f9244c7 -- 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 --- Comment #96 from Wolfgang Bauer --- (In reply to Lastique from comment #92) > Note that on my screenshot vertical and horizontal dashes are garbled. I > don't see that in Bug 406770. What you are seeing is bug#402415 that should be fixed in konsole 19.04.0, but you are using 18.12.3 that still has this problem. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 407060] incorrect YAML highlighted some text block
https://bugs.kde.org/show_bug.cgi?id=407060
Nibaldo G. changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Latest Commit||https://commits.kde.org/syn
||tax-highlighting/28b11e39fb
||a077fc1b41e27ee31439a331fd0
||66e
Resolution|--- |FIXED
Version Fixed In||5.59.0
--- Comment #3 from Nibaldo G. ---
Git commit 28b11e39fba077fc1b41e27ee31439a331fd066e by Nibaldo González.
Committed on 31/05/2019 at 18:58.
Pushed by ngonzalez into branch 'master'.
YAML: only comments after spaces and other improvements/fixes
Summary:
FIXED-IN: 5.59.0
Improvements and corrections to YAML.
**Changes:**
* Only highlight comments after spaces.
* Add folding indentation, like the Python highlighter.
* Avoid highlighting lists, hashes and strings within blocks with multiple
lines, incorrectly.
* Highlight two points of Keys in another color, to make it easier to
differentiate Keys and attributes in some color schemes.
* Changes in colors:
* The Keys are now in bold, helps to differentiate Keys and attributes,
especially in the Solarized schemes.
* Data types are highlighted with `dsOthers`, to differentiate from the
Attribute color.
* "Normal Text" is now `dsAttribute`, to unify the colors of attributes,
since in attributes with multiple lines the colors are inconsistent. This is
done according to other text editors such as VSCode and Atom, where the same
color is used for attributes and normal text.
{F6849805}
{F6849807}
Solarized scheme:
{F6849808}
Normal block & literal block:
{F6849809}
Reviewers: dhaumann, cullmann, #framework_syntax_highlighting
Reviewed By: dhaumann, cullmann, #framework_syntax_highlighting
Subscribers: kwrite-devel, kde-frameworks-devel
Tags: #kate, #frameworks
Differential Revision: https://phabricator.kde.org/D21411
M +34 -28 autotests/folding/test.yaml.fold
M +4-4autotests/html/example.rmd.html
M +98 -92 autotests/html/test.yaml.html
M +6-0autotests/input/test.yaml
M +4-4autotests/reference/example.rmd.ref
M +89 -83 autotests/reference/test.yaml.ref
M +190 -127 data/syntax/yaml.xml
https://commits.kde.org/syntax-highlighting/28b11e39fba077fc1b41e27ee31439a331fd066e
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 408133] Brush strokes terminate slowly after a prolonged drawing session
https://bugs.kde.org/show_bug.cgi?id=408133 spikestherac...@gmail.com changed: What|Removed |Added CC||spikestherac...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 408138] Date of imported transactions not recognised
https://bugs.kde.org/show_bug.cgi?id=408138 Bernhard Scheirle changed: What|Removed |Added Resolution|--- |FIXED CC||bernhard+...@scheirle.de Assignee|steph...@mankowski.fr |bernhard+...@scheirle.de Latest Commit||https://cgit.kde.org/skroog ||e.git/commit/?id=e11cac2094 ||d295b53d016f34ab5cacb7ed9c5 ||4da Status|ASSIGNED|RESOLVED Version Fixed In||2.20 --- Comment #2 from Bernhard Scheirle --- Hi, this is fixed in skrooge 2.20. As a workaround for 2.19 you can manually modify the "org.kde.skrooge-import-backend-aqbanking.desktop"*¹ file: 1. Replace the last line with: X-SKROOGE-csvcolumns=date|mode|comment|payee|amount|unit (Note the added "|unit") 2. Run "kbuildsycoca5" to update the desktop file cache. 3. Restart skrooge. *¹: On my system it is located in /usr/share/kservices5/. Run "kf5-config --path services" to get location on your system. Regards, Bernhard -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408149] Selection Transformation not available via Selection Tool.
https://bugs.kde.org/show_bug.cgi?id=408149 --- Comment #5 from Leo --- Created attachment 120460 --> https://bugs.kde.org/attachment.cgi?id=120460&action=edit Inkscape selection with handles to edit selection -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408149] Selection Transformation not available via Selection Tool.
https://bugs.kde.org/show_bug.cgi?id=408149 --- Comment #4 from Leo --- Created attachment 120459 --> https://bugs.kde.org/attachment.cgi?id=120459&action=edit Gimp selection with handles to edit selection -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408149] Selection Transformation not available via Selection Tool.
https://bugs.kde.org/show_bug.cgi?id=408149 --- Comment #3 from Leo --- Created attachment 120458 --> https://bugs.kde.org/attachment.cgi?id=120458&action=edit Gimp selection with handles to edit selection -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 408138] Date of imported transactions not recognised
https://bugs.kde.org/show_bug.cgi?id=408138 Stephane MANKOWSKI changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 Assignee|guillaume.deb...@gmail.com |steph...@mankowski.fr -- 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 --- Comment #95 from Postix --- I think I may have tracked it down a little bit in the source code: In TerminalDisplay.cpp of Konsole it says > 674: painter.fillRect(rect, color); > 678: painter.fillRect(rect, backgroundColor); If you comment out both, no background is drawn, but I also don't see any more horizontal or vertical lines (the latter in mc). When I set the first rect fixed to (0,0,100,20) for example and made a selection of the content or scrolled up and down to provoke those lines, the horizontal line was only drawn over the painted rect. Maby that's a starting point for further investigations. ;-) ## System Operating System: Manjaro Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 Kernel Version: 5.1.4-1-MANJARO Konsole: Master (926bc5715448bf62ad6060e64aef7c5c5e1d51f0) -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 408138] Date of imported transactions not recognised
https://bugs.kde.org/show_bug.cgi?id=408138 --- Comment #1 from Stephane MANKOWSKI --- Hi, Could you send me some samples of lines returned by the following command line? skrooge-sabb.py bulkdownload --output_folder /tmp/sample.csv The file will be in /tmp/sample.csv My email is in the "About" of Skrooge. -- 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 --- Comment #94 from Jeffrey Bouter --- Created attachment 120457 --> https://bugs.kde.org/attachment.cgi?id=120457&action=edit konsole_ls In current and above screenshot, you can see I'm using a black background. I've had to take a photograph, as pressing the screenshot buttons actually removes the visual artifact from konsole. -- 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 --- Comment #93 from Jeffrey Bouter --- Created attachment 120456 --> https://bugs.kde.org/attachment.cgi?id=120456&action=edit konsole_photo_prompt_return -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408147] From LightTable, "Open" picture does not open the right one
https://bugs.kde.org/show_bug.cgi?id=408147 --- Comment #6 from Alexandre Belz --- Thank you Maik for the correction. (And i confirm that the properties and correct indeed) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408147] From LightTable, "Open" picture does not open the right one
https://bugs.kde.org/show_bug.cgi?id=408147 Maik Qualmann changed: What|Removed |Added Version Fixed In||6.2.0 Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/caff86818650 ||cd38f35fbcc5783e607225c8272 ||8 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from Maik Qualmann --- Git commit caff86818650cd38f35fbcc5783e607225c82728 by Maik Qualmann. Committed on 31/05/2019 at 17:54. Pushed by mqualmann into branch 'master'. fix open from light table and remove navigation actions FIXED-IN: 6.2.0 M +2-1NEWS M +81 -30 core/app/items/utils/contextmenuhelper.cpp M +3-1core/app/items/utils/contextmenuhelper.h M +4-4core/app/items/utils/itemviewutilities.cpp M +1-1core/app/views/preview/itempreviewview.cpp https://invent.kde.org/kde/digikam/commit/caff86818650cd38f35fbcc5783e607225c82728 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 404825] the loudness wont adjust
https://bugs.kde.org/show_bug.cgi?id=404825 emohr changed: What|Removed |Added Flags|Brainstorm+ | Status|CONFIRMED |NEEDSINFO Version|18.12.1 |19.04.1 Resolution|--- |WAITINGFORINFO --- Comment #4 from emohr --- Tested with version 19.04.1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 404825] the loudness wont adjust
https://bugs.kde.org/show_bug.cgi?id=404825 --- Comment #3 from emohr --- Created attachment 120455 --> https://bugs.kde.org/attachment.cgi?id=120455&action=edit Loudness I tested with nightly build Windows and Linux version: it works. In windows you can only adjust the numbers with the mouse wheel or you move the slider. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #57 from Luca Carlon --- You just have to apply the two patches provided in the report. One to qtcore and the other to kwin. This fixed the issue for me. I hope someone could work on the release or describe what is blocking. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 403438] External monitor connected through displayport <-> HDMI is not detected in Plasma Wayland
https://bugs.kde.org/show_bug.cgi?id=403438 Dan G changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408157] "Tone Color Picker" cursor is not correctly positionned vs Mouse
https://bugs.kde.org/show_bug.cgi?id=408157 caulier.gil...@gmail.com changed: What|Removed |Added Component|Plugin-Bqm-Levels |Plugin-Editor-Levels CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408156] screen flickering when using direct3D11 via ANGLE on 4.2.0
https://bugs.kde.org/show_bug.cgi?id=408156 --- Comment #3 from vinnie --- (In reply to Boudewijn Rempt from comment #1) > Could you please also attach the output of help->system information for bug > reports ? Do you have a kind of selectable GPU setup, where you can select > which gpu an app runs on? sorry, forgot to do that earlier. should be here now. and yes, and i have tried both, and they both do the flickering. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408156] screen flickering when using direct3D11 via ANGLE on 4.2.0
https://bugs.kde.org/show_bug.cgi?id=408156 vinnie changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- Assignee|krita-bugs-n...@kde.org |vaatiam...@gmail.com --- Comment #2 from vinnie --- Created attachment 120454 --> https://bugs.kde.org/attachment.cgi?id=120454&action=edit logs for help>system information. i forgot this earlier. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408157] New: "Tone Color Picker" cursor is not correctly positionned vs Mouse
https://bugs.kde.org/show_bug.cgi?id=408157 Bug ID: 408157 Summary: "Tone Color Picker" cursor is not correctly positionned vs Mouse Product: digikam Version: 6.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-Bqm-Levels Assignee: digikam-bugs-n...@kde.org Reporter: alexandre.b...@live.fr Target Milestone: --- SUMMARY Tone Color Picker (Drop cursor shape) is not correctly aligned with the exact mouse position. STEPS TO REPRODUCE 1. Go to Editor window 2. Select "Adjust Levels" module 3. Select a Tone Color Picker (white typically) 4. Move the cursor between the parameter tab and the picture area. OBSERVED RESULT The Drop cursor is not aligned with the mouse position, making precise selection almost impossible. EXPECTED RESULT A precise part of the Drop icon (the very top ?) should exactly correspond to the Mouse cursor point. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION -- 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 --- Comment #92 from Lastique --- Could it be that the bug is masked with --notransparency by the black window background? (In reply to Nate Graham from comment #90) > Looks like that issue is tracked by Bug 406770. Note that on my screenshot vertical and horizontal dashes are garbled. I don't see that in Bug 406770. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 395783] Solver process crashed
https://bugs.kde.org/show_bug.cgi?id=395783 --- Comment #14 from Stanley Fertig --- I did, and it worked. But not the solver in kStars. -stan -- Stanley Fertig 35 Sidney Place Brooklyn, New York 11201 +1 917-361-0632 stanl...@nyc.rr.com > On May 30, 2019, at 8:35 PM, Jean-Claude wrote: > > https://bugs.kde.org/show_bug.cgi?id=395783 > > --- Comment #10 from Jean-Claude --- > Did you try to solve an image with the app Astrometry from CloudMakers (it > uses > the same folder) ? > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You are the assignee for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #84 from Stanley Fertig --- Ah yes, my mistake. Sorry! Here it is again with the correct commands; Illegal Instruction 4 once again. Running v3.2.3. OK, I’m very grateful, Rob. -stan -- Stanley Fertig 35 Sidney Place Brooklyn, New York 11201 +1 917-361-0632 stanl...@nyc.rr.com > On May 31, 2019, at 12:12 PM, Rob wrote: > > https://bugs.kde.org/show_bug.cgi?id=405437 > > --- Comment #82 from Rob --- > That's because a forward slash is missing. There is no file called: > > Applications/kstars.app/Contents/MacOS/astrometry/bin/solve-field > > it is called: > > /Applications/kstars.app/Contents/MacOS/astrometry/bin/solve-field > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #83 from Rob --- I have a suspicion that this may be a python issue. I will see what I can do about it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408156] screen flickering when using direct3D11 via ANGLE on 4.2.0
https://bugs.kde.org/show_bug.cgi?id=408156 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Could you please also attach the output of help->system information for bug reports ? Do you have a kind of selectable GPU setup, where you can select which gpu an app runs on? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408156] New: screen flickering when using direct3D11 via ANGLE on 4.2.0
https://bugs.kde.org/show_bug.cgi?id=408156 Bug ID: 408156 Summary: screen flickering when using direct3D11 via ANGLE on 4.2.0 Product: krita Version: 4.2.0-beta Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: vaatiam...@gmail.com Target Milestone: --- SUMMARY the screen flickers whenever i mouse around between the canvas and the dockers and UI. this is frustrating because it didnt happen on an older build i have, and i have tried to reinstall/mess with settings and nothing helps this new build. very frustrating because theres many bug fixes on the new version. STEPS TO REPRODUCE 1. i guess you would just open it with direct3D like i did and mouse around the dockers/UI and back into the canvas OBSERVED RESULT im not sure what to put here, but i do know it doesnt happen in openGL. sadly opengl is laggy for me, so i cant just alternatively use this as a solution for the time being. EXPECTED RESULT the screen area should flicker dark and light when you mouse around between the UI/dockers and the canvas. SOFTWARE/OS VERSIONS Windows: windows 10 home, 10.0.17763 build 17763 ADDITIONAL INFORMATION Intel Core i7 @ 2.20GHz Intel UHD Graphics 630 (MSI) 4095MB NVIDIA GeForce GTX 1070 (MSI) this doesnt happen on the previous krita build i have. (4.1.7) -- 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 Jeffrey Bouter changed: What|Removed |Added CC||k...@kn0x.org --- Comment #91 from Jeffrey Bouter --- (In reply to Harry ten Berge from comment #81) > Yes, confirmed that with '--notransparency' the artifacts are gone. I can confirm it is most certainly not. They are a lot less, but not gone. still depends on font size, font type, but it can still occur. This is on konsole 19.04.1 (KDE Neon 18.04) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 407902] KMyMoney crashes in LEAP15.1
https://bugs.kde.org/show_bug.cgi?id=407902 --- Comment #15 from Jack --- I haven't looked any further, but I wonder if it might be related to nss? I do not get the crash and have nss 3.40.1. If nss is the cause/trigger, then it might be that the appimage works because it has a different version that the system does. Can those who get the crash say which version of nss they have installed? It might be irrelevant, but let's see if there is any pattern. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #82 from Rob --- That's because a forward slash is missing. There is no file called: Applications/kstars.app/Contents/MacOS/astrometry/bin/solve-field it is called: /Applications/kstars.app/Contents/MacOS/astrometry/bin/solve-field -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 406770] Recent anti-aliasing change is causing black lines on HiDPI displays
https://bugs.kde.org/show_bug.cgi?id=406770 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=373232 -- 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 Nate Graham changed: What|Removed |Added Component|general |tabbar See Also||https://bugs.kde.org/show_b ||ug.cgi?id=406770 --- Comment #90 from Nate Graham --- Looks like that issue is tracked by Bug 406770. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408048] Selection by words is sticky in Midnight Commander
https://bugs.kde.org/show_bug.cgi?id=408048 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 407627] tldr++ output reprints
https://bugs.kde.org/show_bug.cgi?id=407627 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- 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 Nate Graham changed: What|Removed |Added Status|REOPENED|CONFIRMED --- Comment #89 from Nate Graham --- Can reproduce using Konsole 19.04 as well as from git master. -- 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 --- Comment #88 from Christoph Feck --- Please test Konsole 19.04, see bug 402415. I am unsure if anyone tested line graphics using fractional scaling. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408155] Workflow improvement : simply drag & drop pictures from Thumbnail to Map area
https://bugs.kde.org/show_bug.cgi?id=408155 Maik Qualmann changed: What|Removed |Added OS|Linux |MS Windows Platform|Other |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 408082] krarc stopped working with rpm
https://bugs.kde.org/show_bug.cgi?id=408082 --- Comment #1 from dutchk...@txoriaskea.org --- I tried this in opensuse Leap 15.1 on the same pc, with the same krusader version there is no problem entering rpm packages, so it must be something else that broke krarc -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408155] Workflow improvement : simply drag & drop pictures from Thumbnail to Map area
https://bugs.kde.org/show_bug.cgi?id=408155 Maik Qualmann changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408133] Brush strokes terminate slowly after a prolonged drawing session
https://bugs.kde.org/show_bug.cgi?id=408133 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408155] Workflow improvement : simply drag & drop pictures from Thumbnail to Map area
https://bugs.kde.org/show_bug.cgi?id=408155 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- I think we already have this as a wish. You found the geolocation editor? There you can drag and drop the images from the list onto the map. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408103] Krita messages to the user should use the .kra file name and not the document Title
https://bugs.kde.org/show_bug.cgi?id=408103 --- Comment #9 from Ahab Greybeard --- @David Revoy: That is simpler and would suit me from my personal P.O.V. However, at the moment, the Title is stored as the internal folder name inside the .kra file and that has to have a name of some kind. So the .kra file would need an internal indicator to say if the name was given by assignment of a Title or by some other means. Or some other solution. It gets more complicated the more you look at it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408155] New: Workflow improvement : simply drag & drop pictures from Thumbnail to Map area
https://bugs.kde.org/show_bug.cgi?id=408155 Bug ID: 408155 Summary: Workflow improvement : simply drag & drop pictures from Thumbnail to Map area Product: digikam Version: 6.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Geolocation Assignee: digikam-bugs-n...@kde.org Reporter: alexandre.b...@live.fr Target Milestone: --- Created attachment 120448 --> https://bugs.kde.org/attachment.cgi?id=120448&action=edit Map is greyed. SUMMARY When pictures are not yet Geotagged, the MAP area turns into grey, and it's not possible to easily place the pictures there. STEPS TO REPRODUCE 1. From Thumbnail tab, select a few pictures NOT geotagged 2. Drag them to the MAP area... 3. ... and drop where you want them to be Geotagged. OBSERVED RESULT Nothing happens. Pictures are still not Geotagged. EXPECTED RESULT The picture should get the Geo positionning of where they are dropped on the MAP area. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION many others Picture managers allow that workflow : Picasa, Darktable, LR, etc... -- You are receiving this mail because: You are watching all bug changes.
