[plasmashell] [Bug 371559] After a half-day starts slow, freezing and consume CPU
https://bugs.kde.org/show_bug.cgi?id=371559 --- Comment #5 from Alexey --- I update to 5.8.3 . Problem still there -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 446207] Regression: Missing toolbar actions
https://bugs.kde.org/show_bug.cgi?id=446207 Alexey changed: What|Removed |Added CC||swe...@gmail.com --- Comment #1 from Alexey --- the same for me on Fedora 35 -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 446848] Gcompris say alphabet letter names instead of actual letter sound.
https://bugs.kde.org/show_bug.cgi?id=446848 Alexey changed: What|Removed |Added CC||vazh...@boot-keys.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Alexey --- Is it a duplicate for https://bugs.kde.org/show_bug.cgi?id=428863 ? *** This bug has been marked as a duplicate of bug 428863 *** -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 428863] The letter sounds should be the phonemes, not the letter names
https://bugs.kde.org/show_bug.cgi?id=428863 Alexey changed: What|Removed |Added CC||fuxfwgc4a2i...@gmail.com --- Comment #2 from Alexey --- *** Bug 446848 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 469326] New: Green/white tick are too far in activity "Letter in which word"
https://bugs.kde.org/show_bug.cgi?id=469326 Bug ID: 469326 Summary: Green/white tick are too far in activity "Letter in which word" Classification: Applications Product: gcompris Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: jaz...@gmail.com Reporter: vazh...@boot-keys.org Target Milestone: --- Created attachment 158671 --> https://bugs.kde.org/attachment.cgi?id=158671&action=edit gcompris activity "Letter in which word" with ticks SUMMARY I use package gcompris-qt from Devuan testing repository. In activity "Letter in which word", when I select words, green ticks are placed too far from the word. It would be great to place ticks closer to the selected word, or maybe just highlight selected words instead of using ticks (or even both). STEPS TO REPRODUCE 1. Choose activity "Letter in which word". 2. Click on any word. 3. Observe green/white tick. OBSERVED RESULT Ticks are too far from selected words. EXPECTED RESULT The selected words has ticks near, or words are highlighted as an alternative. SOFTWARE/OS VERSIONS gcompris-qt: 3.1-2. Linux/KDE Plasma: Devuan 5 daedalus/ceres (based on Debian 12 bookworm). Desktop environment: XFCE 4.18.2. KDE Plasma Version: - KDE Frameworks Version: - Qt Version: 5.15.8 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 469326] Green/white tick are too far in activity "Letter in which word"
https://bugs.kde.org/show_bug.cgi?id=469326 --- Comment #4 from Alexey --- Created attachment 158805 --> https://bugs.kde.org/attachment.cgi?id=158805&action=edit gcompris with installed "qt5-image-formats-plugins", activity "Letter in which word" I've installed a package `qt5-image-formats-plugins` and now I see pictures together with words. I will try to create a bugreport for maintainers. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485771] Desktop icons disappear after icon update (including the trash icon)
https://bugs.kde.org/show_bug.cgi?id=485771 Alexey changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|FIXED |--- Ever confirmed|1 |0 CC||alsubb...@gmail.com --- Comment #23 from Alexey --- Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.4-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Bug is still unfixed. To reproduce just 1. right click on *.desktop icon on the desktop 2. press OK button Icon is disappears from Desktop although it is in the ~/Desktop folder. To restore icon visibility I change room mode from folder to desktop and back. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 325574] Unable to modify file on Android device using kio-mtp
https://bugs.kde.org/show_bug.cgi?id=325574 Alexey changed: What|Removed |Added CC||alexi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482653] New: Keyboard layout widget/tray entry state change leads to focus application launcher with current window unfocus
https://bugs.kde.org/show_bug.cgi?id=482653 Bug ID: 482653 Summary: Keyboard layout widget/tray entry state change leads to focus application launcher with current window unfocus Classification: Plasma Product: kwin Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: alexi...@gmail.com Target Milestone: --- Created attachment 166547 --> https://bugs.kde.org/attachment.cgi?id=166547&action=edit demo STEPS TO REPRODUCE 1. Add some keyboard layouts; 2. Add keyboard layout widget / system tray entry; 3. Switch layout with shortcut / click on widget; OBSERVED RESULT Switching keyboard layout leads to Application launcher focus/unfocus. EXPECTED RESULT Switching keyboard layout just switches keyboard layout. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482653] Keyboard layout widget/tray entry state change leads to focus application launcher with current window unfocus
https://bugs.kde.org/show_bug.cgi?id=482653 --- Comment #2 from Alexey --- (In reply to Vlad Zahorodnii from comment #1) > Cannot reproduce Did you add the Keyboard layout widget? Maybe you need to reboot your system, because sometimes this is not reproducible for some reason. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482653] Keyboard layout widget/tray entry state change leads to focus application launcher with current window unfocus
https://bugs.kde.org/show_bug.cgi?id=482653 --- Comment #3 from Alexey --- Created attachment 166586 --> https://bugs.kde.org/attachment.cgi?id=166586&action=edit keyboard settings Added keyboard settings to attachments. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482653] Keyboard layout widget/tray entry state change leads to focus application launcher with current window unfocus
https://bugs.kde.org/show_bug.cgi?id=482653 --- Comment #5 from Alexey --- It looks like the bug belongs to the 'plasmashell' product and the 'Keyboard Layout' component, but I don't see this component when editing the bug report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482720] New: Desktop icons text is blurry
https://bugs.kde.org/show_bug.cgi?id=482720 Bug ID: 482720 Summary: Desktop icons text is blurry Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: plasma-b...@kde.org Reporter: alexi...@gmail.com CC: h...@kde.org Target Milestone: 1.0 Created attachment 166592 --> https://bugs.kde.org/attachment.cgi?id=166592&action=edit Desktop icons text demo SUMMARY After update to Plasma 6 I noticed that the text of desktop icons looked blurry... more blurry than usual. Related to: https://www.reddit.com/r/kde/comments/1b8dhhn/wayland_plasma_6_and_blurry_text/. STEPS TO REPRODUCE 1. Open Plasma 6 (Wayland session with 1920x1080 125% display). 2. Compare text under icon with text in edit mode. OBSERVED RESULT Text under desktop icons looks blurry. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Unfortunately, I can't provide a demo of what the font looked like before the update, but I hope that what I described in this demo is not just my imagination. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482722] New: Fonts break when reaching the very bottom of the left panel
https://bugs.kde.org/show_bug.cgi?id=482722 Bug ID: 482722 Summary: Fonts break when reaching the very bottom of the left panel Classification: Applications Product: systemsettings Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: alexi...@gmail.com Target Milestone: --- Created attachment 166593 --> https://bugs.kde.org/attachment.cgi?id=166593&action=edit Bug demonstration STEPS TO REPRODUCE 1. Minimize System Settings application window; 2. Scroll to the bottom of the left settings panel. OBSERVED RESULT Some of the text is cut off, some of the characters are smudged or are at different heights. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479891] Some text glyphs in QML software are mis-aligned or squished when using a fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=479891 --- Comment #16 from Alexey --- Created attachment 166602 --> https://bugs.kde.org/attachment.cgi?id=166602&action=edit 1920x1080 125% (System settings dialog) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479891] Some text glyphs in QML software are mis-aligned or squished when using a fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=479891 --- Comment #17 from Alexey --- Created attachment 166603 --> https://bugs.kde.org/attachment.cgi?id=166603&action=edit 1920x1080 125% (System settings dialog 2) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479891] Some text glyphs in QML software are mis-aligned or squished when using a fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=479891 --- Comment #18 from Alexey --- (In reply to Marco Martin from comment #15) > *** Bug 482720 has been marked as a duplicate of this bug. *** Bug 482722 may also be related to this issue but the artifacts described there achieved through certain actions. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482653] Keyboard layout widget/tray entry state change leads to focus application launcher with current window unfocus
https://bugs.kde.org/show_bug.cgi?id=482653 --- Comment #9 from Alexey --- (In reply to Roman from comment #7) > New info: > This problem will be solved if you remove the keyboard layout widget from > the tray. > That exist in both modes (X11/wayland) Yes, but temporary; after reboot the issue restores. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482653] Keyboard layout widget/tray entry state change leads to focus application launcher with current window unfocus
https://bugs.kde.org/show_bug.cgi?id=482653 --- Comment #10 from Alexey --- (In reply to Roman from comment #8) > New info[2]: > If you add display of the layout to the SYSTEM TRAY on the panel, the bug > does not appear. > Only if it is a separate widget, then it appears. Yes, it looks like the issue only applies to the widget position of the Keyboard layout component. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482653] Keyboard layout widget/tray entry state change leads to focus application launcher with current window unfocus
https://bugs.kde.org/show_bug.cgi?id=482653 Alexey changed: What|Removed |Added CC||alexi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488519] New: Panel changes wallpapers at background
https://bugs.kde.org/show_bug.cgi?id=488519 Bug ID: 488519 Summary: Panel changes wallpapers at background Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: alexi...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 170513 --> https://bugs.kde.org/attachment.cgi?id=170513&action=edit Bug demonstration *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY If the panel height is from 32 to 38 inclusive, there is a fill below and to the right of the floating panel. OBSERVED RESULT See attachment. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION Desktop resolution: 1920x1080 Scaling: 1.25 (Wayland) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488519] Panel changes wallpapers at background
https://bugs.kde.org/show_bug.cgi?id=488519 Alexey changed: What|Removed |Added Version|6.0.1 |6.0.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488519] Panel changes wallpapers at background
https://bugs.kde.org/show_bug.cgi?id=488519 Alexey changed: What|Removed |Added Platform|Other |Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474488] Panel flickering at the top of some fullscreen games
https://bugs.kde.org/show_bug.cgi?id=474488 --- Comment #23 from Alexey --- (In reply to Zamundaaa from comment #22) > The problem is that the window is not actually fullscreen. The problem is not reproducible in other desktop environments, so even if the change didn't fix the problem, it's still a problem on the KWin side. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485840] New: Panel attracts the cursor to itself on some fullscreen games
https://bugs.kde.org/show_bug.cgi?id=485840 Bug ID: 485840 Summary: Panel attracts the cursor to itself on some fullscreen games Classification: Plasma Product: kwin Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: alexi...@gmail.com Target Milestone: --- Created attachment 168709 --> https://bugs.kde.org/attachment.cgi?id=168709&action=edit Bug demonstration SUMMARY This bug report is related to https://bugs.kde.org/show_bug.cgi?id=474488 (maybe). As in the mentioned bug, this bug affects some full-screen games and is not reproducible on other compositors like Mutter or Hyprland. Like the previous issue involving the annoying flickering of the full screen game window with the visible system bar (the hidden panel did not caused this behavior), this issue has the same "triggers" but has a different observable result: the cursor moves to the bar (only when system panel is visible too). There seem to be too many bugs associated with the panel lately, from apps losing focus when there are standalone widgets in the panel, to less detectable bugs like this that can persist for years. As a complete amateur in such questions, I am sincerely interested in why this is even possible. STEPS TO REPRODUCE 1. Set "Always visible" to panel; 2. Launch game with detectable behavior (for example, HoMM3); 3. Perform “trigger” actions that lead to an issue (see attachments). OBSERVED RESULT ... EXPECTED RESULT ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485840] Panel attracts the cursor to itself on some fullscreen games
https://bugs.kde.org/show_bug.cgi?id=485840 --- Comment #1 from Alexey --- An important point: in the demo you can see that some of the triggers of the mentioned bug 474488 still cause windows to flicker. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485840] Panel attracts the cursor to itself on some fullscreen games
https://bugs.kde.org/show_bug.cgi?id=485840 --- Comment #3 from Alexey --- (In reply to fanzhuyifan from comment #2) > Is this on wayland or x11? It's Wayland, but something tells me that it's reproducible regardless of session. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485879] New: Incorrect text placement when renaming in Dolphin
https://bugs.kde.org/show_bug.cgi?id=485879 Bug ID: 485879 Summary: Incorrect text placement when renaming in Dolphin Classification: Applications Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: alexi...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 168728 --> https://bugs.kde.org/attachment.cgi?id=168728&action=edit Bug demonstration SUMMARY After upgrading to Plasma 6, I started to feel something strange when renaming files in Dolphin. After some observation, I realized that the rename text was no longer centered and was positioned to the left. STEPS TO REPRODUCE 1. Open Dolphin; 2. Select "Rename" for some entry. OBSERVED RESULT Text is shifted to the left after the rename field is changed. EXPECTED RESULT Text must be centered during renaming. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION This is a late report; the bug was discovered in the Plasma 6 release version. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485879] Incorrect text placement when renaming in Dolphin
https://bugs.kde.org/show_bug.cgi?id=485879 --- Comment #1 from Alexey --- I just saw recent reports with renaming, where the authors do not pay attention to left alignment; maybe I'm overthinking something? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485840] Panel attracts the cursor to itself on some fullscreen games
https://bugs.kde.org/show_bug.cgi?id=485840 Alexey changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474488] Panel flickering at the top of some fullscreen games
https://bugs.kde.org/show_bug.cgi?id=474488 Alexey changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #24 from Alexey --- (In reply to Alexey from comment #23) > (In reply to Zamundaaa from comment #22) > > The problem is that the window is not actually fullscreen. > The problem is not reproducible in other desktop environments, so even if > the change didn't fix the problem, it's still a problem on the KWin side. Today I was able to reproduce the bug with Diablo II under Wine. Yes, this bug report should be reopened. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 484383] New: Breeze GTK strange black lines between some elements
https://bugs.kde.org/show_bug.cgi?id=484383 Bug ID: 484383 Summary: Breeze GTK strange black lines between some elements Classification: Plasma Product: Breeze Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: plasma-b...@kde.org Reporter: alexi...@gmail.com CC: agrine...@gmail.com, uhh...@gmail.com Target Milestone: --- Created attachment 167699 --> https://bugs.kde.org/attachment.cgi?id=167699&action=edit bug demonstration STEPS TO REPRODUCE 1. Set Breeze as theme for GTK applications; 2. Open Lutris. OBSERVED RESULT Black lines on left panel. EXPECTED RESULT No black lines on left panel (like with "default" GTK theme). SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480402] New: KDE causes some fullscreen Wine/Proton games to twitch when interacting
https://bugs.kde.org/show_bug.cgi?id=480402 Bug ID: 480402 Summary: KDE causes some fullscreen Wine/Proton games to twitch when interacting Classification: Plasma Product: kwin Version: 5.27.10 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: alexi...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Add bottom Panel with "Always Visible" visibility option; 2. Launch Wine application that forces fullscreen resolution (in my case - HoMM3 under wine-ge-8-25); 3. Try to do some actions (in my case - click some in-game buttons). OBSERVED RESULT Fullscreen window shrinks making free space on top and in place of the panel, then returns to its original position. EXPECTED RESULT Nothing like this. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.114.0 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.7.1-arch1-1 (64-bit) ADDITIONAL INFORMATION Tested both on X11 and Wayland sessions. Observed on: - HotA (HoMM3 + HD) under Wine while interact with some action buttons; - Path of Exile under Steam's Proton Experimental while interact with options menu. Seems like this effect doesn't appears when Panel has "Auto Hide" or "Windows Can Cover" visibility option. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480402] KDE causes some fullscreen Wine/Proton games to twitch when interacting
https://bugs.kde.org/show_bug.cgi?id=480402 --- Comment #1 from Alexey --- Created attachment 165287 --> https://bugs.kde.org/attachment.cgi?id=165287&action=edit Bug demonstration -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 486971] New: "Activities" switching not working after update to plasma 6
https://bugs.kde.org/show_bug.cgi?id=486971 Bug ID: 486971 Summary: "Activities" switching not working after update to plasma 6 Classification: I don't know Product: kde Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: alexbesporoc...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Before updete i switched Activities with alt+q but now its not working and i ever not see such settings STEPS TO REPRODUCE 1. alt+q 2. 3. OBSERVED RESULT nothing EXPECTED RESULT changing activity SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 486975] New: When i open console and trying to write something it crashes
https://bugs.kde.org/show_bug.cgi?id=486975 Bug ID: 486975 Summary: When i open console and trying to write something it crashes Classification: Applications Product: konsole Version: master Platform: Manjaro OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: alexbesporoc...@gmail.com Target Milestone: --- Created attachment 169447 --> https://bugs.kde.org/attachment.cgi?id=169447&action=edit System parameters *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY [alexbespik@pc ~]$ konsole Segmentation fault (core dumped) STEPS TO REPRODUCE 1. open xterm 2. type konsole 3. or tap on icon OBSERVED RESULT konsole krashes EXPECTED RESULT konsole open 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 445935] New: Wrong/Zero selection. Less then 1 px
https://bugs.kde.org/show_bug.cgi?id=445935 Bug ID: 445935 Summary: Wrong/Zero selection. Less then 1 px Product: krita Version: 5.0.0-beta2 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: o-di...@ya.ru Target Milestone: --- Created attachment 143845 --> https://bugs.kde.org/attachment.cgi?id=143845&action=edit Not create any selections less than 1px If we click without drag on 1px size that make empty invisible selection. OBSERVED RESULT See attachment video EXPECTED RESULT Not create any selections less than 1px -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432763] Random stamp glitches on stroke with smudge engine(dull) and texture
https://bugs.kde.org/show_bug.cgi?id=432763 Alexey changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||o-di...@ya.ru OS|Microsoft Windows |All Ever confirmed|0 |1 --- Comment #1 from Alexey --- I has that trouble too... a long, long time -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426850] New: Improve Color Adjustment Curves
https://bugs.kde.org/show_bug.cgi?id=426850 Bug ID: 426850 Summary: Improve Color Adjustment Curves Product: krita Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Filters Assignee: krita-bugs-n...@kde.org Reporter: o-di...@ya.ru Target Milestone: --- Created attachment 131855 --> https://bugs.kde.org/attachment.cgi?id=131855&action=edit Improve Color Adjustment Curves 1.Green — To improve the accuracy of working with curves, it is suggested to add an eyedropper to select the image point, this selection will add a point on the curve in the corresponding value. 2.Orange — Shows the losing of detail in the image when changing the Input / Output curves. Color mask of the degree of loss. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426852] New: Option for create a blank frame in auto mode
https://bugs.kde.org/show_bug.cgi?id=426852 Bug ID: 426852 Summary: Option for create a blank frame in auto mode Product: krita Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: o-di...@ya.ru Target Milestone: --- Now: - We draw a circle - Go to the next frame - We draw a square - And we get a circle+square in this frame, and a circle in the previous one But! For frame-by-frame animation, you often need to draw in a EMPTY frame That is now: - We draw a circle - Go to the next frame - Press a DELETE... - We draw a square - And we get a square in this keyframe, and a circle in the previous one It would be nice to get an option (check mark), activating which we will get clean a new one frame, without of the content of the previous frame. Would be nice and more-more-more useful! ::) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426850] Improve Color Adjustment Curves
https://bugs.kde.org/show_bug.cgi?id=426850 --- Comment #2 from Alexey --- Yes, thank's! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426852] Option for create a blank frame in auto mode
https://bugs.kde.org/show_bug.cgi?id=426852 --- Comment #3 from Alexey --- (In reply to Boudewijn Rempt from comment #1) > Please consult the manual to learn how to use Krita's animation tools... Yes, thank's! I decided to read it again, maybe I missed something from the previous times, but no. ::D -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426852] Option for create a blank frame in auto mode
https://bugs.kde.org/show_bug.cgi?id=426852 --- Comment #4 from Alexey --- (In reply to Dmitry Kazakov from comment #2) > Well, this feature has been implemented in Krita 5.0 branch, but it is not > yet present in Krita 4.3/4.4 branches. Good news! -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 411681] Yakuake always shown on second monitor on wayland
https://bugs.kde.org/show_bug.cgi?id=411681 Alexey changed: What|Removed |Added CC||skobkin...@ya.ru -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 411681] Yakuake always shown on second monitor on wayland
https://bugs.kde.org/show_bug.cgi?id=411681 --- Comment #10 from Alexey --- Same here. Excerpt from screenfetch: > OS: Gentoo testing > Kernel: x86_64 Linux 5.12.10-gentoo-skobkin > Resolution: No X Server > DE: KDE 5.83.0 / Plasma 5.22.1 > WM: KWin > GPU: AMD Radeon RX 6800 XT (SIENNA_CICHLID, DRM 3.40.0, > 5.12.10-gentoo-skobkin, LLVM 12.0.0) $ yakuake --version yakuake 21.04.2 Answers for questions in the thread: > Do you happen to have scaling enabled? No. I have 3 displays with 100% scaling. >From left to right: 1920x1080, 2560x1080, 1920x1080. > I am having the issue, clicking in the desktop or a window in the desired > display will allow yakuake to pop up there. Did you try ? It doesn't follow > mouse, but just use active display? Doesn't work for me. Clicking on the desktop or on the window on different display doesn't help to show yakuake after hiding on different display. But if I choose "Screen" -> "Screen X" in the menu it'll show on that screen next time I press the hotkey after hiding it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436112] New: Move layer with content + select it
https://bugs.kde.org/show_bug.cgi?id=436112 Bug ID: 436112 Summary: Move layer with content + select it Product: krita Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: Tools/Move Assignee: krita-bugs-n...@kde.org Reporter: o-di...@ya.ru Target Milestone: --- Created attachment 137853 --> https://bugs.kde.org/attachment.cgi?id=137853&action=edit Move layer with content and select it It's very convenient when we can get automatic selection (in the layer stack) of the newly moved layer (can be an option). Thus, we can immediately call the transformation of this layer, instead of calling the layer selection tool or selecting it in the layer stack. This is especially useful when you need to edit many layers one by one! STEPS TO REPRODUCE 1. Take a Move tool 2. Activate 'move layer with content' (& maybe a 'select moved layer' checker is needed) 3. Move layer OBSERVED RESULT 4. Moved layer is not selected EXPECTED RESULT 4. Moved layer is selected ::) ADDITIONAL INFORMATION Thank's for your hard work! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436705] New: Krita crashes on exit every time
https://bugs.kde.org/show_bug.cgi?id=436705 Bug ID: 436705 Summary: Krita crashes on exit every time Product: krita Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: drevobo...@gmail.com Target Milestone: --- SUMMARY Crash report appears every time I close Krita. STEPS TO REPRODUCE 1. Start Krita. 2. Exit Krita (method does note make sense). OBSERVED RESULT Krash message appears in KDE system tray. EXPECTED RESULT No crashes should appear. SOFTWARE/OS VERSIONS Application: krita (4.2.9) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-72-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.2 LTS ADDITIONAL INFORMATION -- Information about the crash: The crash can be reproduced every time. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6626f7fc80 (LWP 19248))] Thread 3 (Thread 0x7f660ec9b700 (LWP 19257)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f662be8c0b0 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f662be8bf16 in QSemaphore::tryAcquire(int, int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f662d34f9aa in KisTileDataSwapper::run() () from /lib/x86_64-linux-gnu/libkritaimage.so.18 #4 0x7f662be899d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6629e60609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f662baff293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f661d88f700 (LWP 19253)): #0 0x7f662baf2aff in __GI___poll (fds=0x7f661801cf50, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f662965136e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f66296514a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f662c0a9583 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f662c0504db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f662be88785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6629e93efa in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f662be899d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6629e60609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f662baff293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f6626f7fc80 (LWP 19248)): [KCrash Handler] #6 0x7f662cab3b1a in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7f662cac344e in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f662cac3474 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f662cac3474 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f662cac3509 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f662cab83dc in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f662caa7908 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f662caa7e1d in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f662c07b01e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f662caa7c29 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f662cb7b931 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f662c07b01e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f662caa7c29 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f662cb7ddf8 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f662c07b01e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f662caa7c29 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f660d4b825d in ?? () from /usr/lib/python3/dist-packages/PyQt5/QtWidgets.cpython-38-x86_64-linux-gnu.so #23 0x7f660dd303f5 in ?? () from /usr/lib/python3/dist-packages/PyQt5/QtCore.cpython-38-x86_64-linux-gnu.so #24 0x7f6614022b60 in ?? () from /usr/lib/python3/dist-packages/sip.cpython-38-x86_64-linux-gnu.so #25 0x7f660dd300a0 in ?? () from /usr/lib/python3/dist-packages/PyQt5/QtCore.cpython-38-x86_64-linux-gnu.so #26 0x7f660e1a41aa in ?? () from /lib/x86_64-linux-gnu/libpython3.8.so.1.0 #27 0x7f660e1ed500 in PyVectorcall_Call () from /lib/x86_64-linux-gnu/libpython3.8.so.1.0 #28 0x7f660e052017 in ?? () from /lib/x86_64-linux-gnu/libpython3.8.so.1.0 #29 0x7f660e0d83ad in Py_FinalizeEx () from /lib/x86
[krita] [Bug 436705] Krita crashes on exit every time
https://bugs.kde.org/show_bug.cgi?id=436705 --- Comment #2 from Alexey --- (In reply to Halla Rempt from comment #1) > Krita 4.2.9 is very old. Please update to a more recent version of Krita, > and use the appimage. Thank you for the answer! Can you please provide me a manual of preferable way to upgrade Krita? Actually I prefer to use packages provided with my Linux distribution.. All of them are up to date. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435337] Contiguous Tool Bug
https://bugs.kde.org/show_bug.cgi?id=435337 Alexey changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||o-di...@ya.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466681] Mouse is lagging/skipping frames when entering Task Manager area
https://bugs.kde.org/show_bug.cgi?id=466681 Alexey changed: What|Removed |Added CC||ale...@toklovich.com --- Comment #15 from Alexey --- (In reply to Felipe Castilho from comment #14) > It seems to be happening again on 5.27.8, maybe a regression or something? > (I can provide video proof and/or more information if needed) I can confirm, it happens on my setup as well, 5.27.10 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479766] New: kickoff unstable on wayland
https://bugs.kde.org/show_bug.cgi?id=479766 Bug ID: 479766 Summary: kickoff unstable on wayland Classification: Plasma Product: plasmashell Version: 5.92.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: alexey@icloud.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 Created attachment 164878 --> https://bugs.kde.org/attachment.cgi?id=164878&action=edit The video shows the problem Unable to use application launcher The problem occurs even if a different applet is created to run the applications, they both may not work, and may work at random times I haven't noticed this problem on x11 The problem is also present in plasma 5 STEPS TO REPRODUCE 1. Use wayland session 2. Do your business 3. After some time, the problem appears OBSERVED RESULT Kickoff don't work SOFTWARE/OS VERSIONS Linux kernel: 6.6.10-zen1-1-zen GPU: NVIDIA GEFORCE RTX 4060 Ti with proprietary driver [545.29.06] KDE Plasma Version: 5.92.0 KDE Frameworks Version: 5.248.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479766] kickoff unstable on wayland
https://bugs.kde.org/show_bug.cgi?id=479766 Alexey changed: What|Removed |Added Flags||performance-, Wayland+, ||X11? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479766] kickoff unstable on wayland
https://bugs.kde.org/show_bug.cgi?id=479766 Alexey changed: What|Removed |Added Flags|X11?|X11- -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472743] New: Splitting lines by Shift+Enter: works in the edit window, but not on the canvas
https://bugs.kde.org/show_bug.cgi?id=472743 Bug ID: 472743 Summary: Splitting lines by Shift+Enter: works in the edit window, but not on the canvas Classification: Applications Product: krita Version: 5.1.5 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: o-di...@ya.ru Target Milestone: --- Created attachment 160584 --> https://bugs.kde.org/attachment.cgi?id=160584&action=edit enter The lines can be separated by pressing Enter. The expected behavior occurs. But when you press Shift+Enter, the lines are separated in the editor window, but not on the canvas, which is not the expected behavior. This is misleading, as if the function does not work. STEPS TO REPRODUCE 1. add some words 2. move the text to another line by pressing Shift+Enter 3. apply text changes OBSERVED RESULT the text shows an undivided string EXPECTED RESULT the text shows a line break SOFTWARE/OS VERSIONS all os -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472743] Splitting lines by Shift+Enter: works in the edit window, but not on the canvas
https://bugs.kde.org/show_bug.cgi?id=472743 --- Comment #1 from Alexey --- Created attachment 160585 --> https://bugs.kde.org/attachment.cgi?id=160585&action=edit shift+enter -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472746] New: Snap to pixel: completely overlaps all other snapping options
https://bugs.kde.org/show_bug.cgi?id=472746 Bug ID: 472746 Summary: Snap to pixel: completely overlaps all other snapping options Classification: Applications Product: krita Version: 5.1.5 Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: o-di...@ya.ru Target Milestone: --- By default 'Snap to pixel' is enabled. And this completely overlaps all other snapping options. Like snap to grid or guides, which is needed more often. SIMPLE SOLUTION Disable 'Snap to pixel' by default COMPLEX SOLUTION Add priority parameters for binding types. For example. If we set the priority of the grid above the pixel, the result will be: "snap to pixel", but "snap to grid" if the distance to the grid line is less than 20 pixels (this should be in settings) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472746] Snap to pixel: completely overlaps all other snapping options
https://bugs.kde.org/show_bug.cgi?id=472746 --- Comment #2 from Alexey --- (In reply to tomtomtomreportingin from comment #1) > On my end, a fresh install of Krita has "Snap to Pixel" disabled by default. But still, we need a way to work with both the grid and the pixel at the same time -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407403] Transformation and Mirror mode
https://bugs.kde.org/show_bug.cgi?id=407403 --- Comment #1 from Alexey --- We can draw in mirroring mode, but we can't make selection or transform mirrored. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466693] Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog.
https://bugs.kde.org/show_bug.cgi?id=466693 Bug 466693 depends on bug 419055, which changed state. Bug 419055 Summary: Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog. https://bugs.kde.org/show_bug.cgi?id=419055 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419055] Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog.
https://bugs.kde.org/show_bug.cgi?id=419055 Alexey changed: What|Removed |Added CC||alsubb...@gmail.com Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419055] Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog.
https://bugs.kde.org/show_bug.cgi?id=419055 --- Comment #3 from Alexey --- I have the same bug on my system: Discover 5.27.6 Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.4.6-200.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × 11th Gen Intel® Core™ i7-11800H @ 2.30GHz Memory: 31,0 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: Micro-Star International Co., Ltd. Product Name: Creator Z16 A11UE System Version: REV:1.0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466693] Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog.
https://bugs.kde.org/show_bug.cgi?id=466693 Alexey changed: What|Removed |Added CC||alsubb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466693] Discover checks for updates daily, regardless of the frequency set in the Software Sources dialog.
https://bugs.kde.org/show_bug.cgi?id=466693 --- Comment #7 from Alexey --- Can I add here that I have the same bug in Fedora which uses dnf as a package manager instead of apt? Or should I create a new bug? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 472175] Fetching updates lasts hours and hours.
https://bugs.kde.org/show_bug.cgi?id=472175 --- Comment #5 from Alexey --- (In reply to Nate Graham from comment #3) > Thanks, that's helpful. I guess it's stuck reloading the cache or some repo > over and over again? Have you installed any non-default RPM repos on your > system? Hi, again! Yes, I have several non-default RPM repos: ode Visual Studio Code docker-ce-stable Docker CE Stable - x86_64 expressvpn-repo expressvpn fedoraFedora 38 - x86_64 fedora-cisco-openh264 Fedora 38 openh264 (From Cisco) - x86_64 fedora-modularFedora Modular 38 - x86_64 google-chrome google-chrome oneAPIIntel® oneAPI repository rpmfusion-nonfree RPM Fusion for Fedora 38 - Nonfree rpmfusion-nonfree-nvidia-driver RPM Fusion for Fedora 38 - Nonfree - NVIDIA Driver rpmfusion-nonfree-steam RPM Fusion for Fedora 38 - Nonfree - Steam rpmfusion-nonfree-updates RPM Fusion for Fedora 38 - Nonfree - Updates updates Fedora 38 - x86_64 - Updates updates-modular Fedora Modular 38 - x86_64 - Updates -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 472175] Fetching updates lasts hours and hours.
https://bugs.kde.org/show_bug.cgi?id=472175 Alexey changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 472175] Fetching updates lasts hours and hours.
https://bugs.kde.org/show_bug.cgi?id=472175 --- Comment #2 from Alexey --- [asubbota ~]$ pkmon Transactions: [none] daemon connected=1 network status=online Transactions: 1 /2414_caacaedc Transactions: 1 /2414_caacaedc 2 /2415_dcdcabeb /2414_caacaedc allow_cancel 1 /2414_caacaedc percentage 32 /2414_caacaedc role refresh-cache /2414_caacaedc sender /usr/bin/plasma-discover /2414_caacaedc status loading-cache /2415_dcdcabeb allow_cancel 1 /2415_dcdcabeb percentage -1 /2415_dcdcabeb role refresh-cache /2415_dcdcabeb sender /usr/libexec/DiscoverNotifier /2415_dcdcabeb status wait ^[[2;5~/2414_caacaedc status download-repository /2414_caacaedc status loading-cache /2414_caacaedc percentage 38 /2414_caacaedc percentage 39 /2414_caacaedc status download-repository /2414_caacaedc status loading-cache /2414_caacaedc percentage 44 /2414_caacaedc status download-repository /2414_caacaedc status loading-cache /2414_caacaedc percentage 51 /2414_caacaedc status download-repository /2414_caacaedc status loading-cache /2414_caacaedc percentage 57 /2414_caacaedc percentage 58 /2414_caacaedc status download-repository /2414_caacaedc status loading-cache /2414_caacaedc percentage 63 /2414_caacaedc status download-repository /2414_caacaedc status loading-cache /2414_caacaedc percentage 70 /2414_caacaedc status download-repository /2414_caacaedc status loading-cache /2414_caacaedc percentage 76 /2414_caacaedc percentage 77 /2414_caacaedc status download-repository /2414_caacaedc status loading-cache /2414_caacaedc percentage 82 ... -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 472175] New: Fetching updates lasts hours and hours.
https://bugs.kde.org/show_bug.cgi?id=472175 Bug ID: 472175 Summary: Fetching updates lasts hours and hours. Classification: Applications Product: Discover Version: 5.27.6 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updates (offline) Assignee: plasma-b...@kde.org Reporter: alsubb...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 160241 --> https://bugs.kde.org/attachment.cgi?id=160241&action=edit Discover shows this for hours SUMMARY *** Fetching updates lasts hours and hours. *** STEPS TO REPRODUCE 1. Wait for "updates ready" notification 2. Open discover and click on fetching updates OBSERVED RESULT Fetching updates progress bar is about to finish but gets stuck there for hours EXPECTED RESULT It finishes in reasonable time (most in 1 minute I suppose) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 38 (KDE Plasma spin) (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446890] New: Cursor and outline color
https://bugs.kde.org/show_bug.cgi?id=446890 Bug ID: 446890 Summary: Cursor and outline color Product: krita Version: 5.0.0-beta2 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: o-di...@ya.ru Target Milestone: --- Created attachment 144488 --> https://bugs.kde.org/attachment.cgi?id=144488&action=edit Cursor and outline color The cursor color selection option actually selects the outline color. There is no way to select the cursor color. In addition, the selected color is not inverted if the outline is on top of the same color and the outline is not visible. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447255] Transform Mask make wrong calculation with perspective with a 90degree turn
https://bugs.kde.org/show_bug.cgi?id=447255 --- Comment #1 from Alexey --- Created attachment 144705 --> https://bugs.kde.org/attachment.cgi?id=144705&action=edit with fill layer -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447255] Transform Mask make wrong calculation with perspective with a 90degree turn
https://bugs.kde.org/show_bug.cgi?id=447255 --- Comment #2 from Alexey --- Created attachment 144707 --> https://bugs.kde.org/attachment.cgi?id=144707&action=edit same t.mask on paint layer -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447255] New: Transform Mask make wrong calculation with perspective with a 90degree turn
https://bugs.kde.org/show_bug.cgi?id=447255 Bug ID: 447255 Summary: Transform Mask make wrong calculation with perspective with a 90degree turn Product: krita Version: 5.0.0-beta2 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: o-di...@ya.ru Target Milestone: --- Created attachment 144704 --> https://bugs.kde.org/attachment.cgi?id=144704&action=edit perspective with a 90degree turn Transform Mask make wrong calculation with perspective with a 90degree turn STEPS TO REPRODUCE 1. Add Transform Mask 2. Get perspective transform 3. Rotate it by 90° or open attachment ::) OBSERVED RESULT Glitched image with perspective transform EXPECTED RESULT Normal image with perspective transform SOFTWARE/OS VERSIONS Krita 4.4.7, ANGLE, OpenGL, Win7x62 sp1 Krita 5.0.0-beta5, OpenGL, Linux Mint 19.2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449748] New: Scale/rotation-based spacing
https://bugs.kde.org/show_bug.cgi?id=449748 Bug ID: 449748 Summary: Scale/rotation-based spacing Product: krita Version: unspecified Platform: Other OS: All Status: REPORTED Severity: minor Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: o-di...@ya.ru Target Milestone: --- Created attachment 146393 --> https://bugs.kde.org/attachment.cgi?id=146393&action=edit without scale/rotation-based spacing Krita uses only the brush offset to calculate the spacing. This leads to a bad result in a number of cases. For example: at the end of the stroke when we no longer lead with the pen but only release it. Or when we want to make a short stroke with increasing pressure (see attachments) STEPS TO REPRODUCE 1. (see attachments) 2. take any smudge brush 3. draw a short stroke (or press without offset) with a large pressure difference at the beginning and end -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449748] Scale/rotation-based spacing
https://bugs.kde.org/show_bug.cgi?id=449748 --- Comment #1 from Alexey --- Created attachment 146394 --> https://bugs.kde.org/attachment.cgi?id=146394&action=edit without scale/rotation-based spacing 2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449748] Scale/rotation-based spacing
https://bugs.kde.org/show_bug.cgi?id=449748 --- Comment #2 from Alexey --- Created attachment 146395 --> https://bugs.kde.org/attachment.cgi?id=146395&action=edit without scale/rotation-based spacing 3 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449748] Scale/rotation-based spacing
https://bugs.kde.org/show_bug.cgi?id=449748 --- Comment #3 from Alexey --- Created attachment 146396 --> https://bugs.kde.org/attachment.cgi?id=146396&action=edit without scale/rotation-based spacing 4 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449748] Scale/rotation-based spacing needs
https://bugs.kde.org/show_bug.cgi?id=449748 Alexey changed: What|Removed |Added Summary|Scale/rotation-based|Scale/rotation-based |spacing |spacing needs -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435007] New: Cursor Glitching (huge green artifacts)
https://bugs.kde.org/show_bug.cgi?id=435007 Bug ID: 435007 Summary: Cursor Glitching (huge green artifacts) Product: krita Version: 4.4.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: chestiras...@gmail.com Target Milestone: --- SUMMARY Cursor Glitching (huge green artifacts) STEPS TO REPRODUCE 1. Nvidia GTX1060 6GB, Any Render Option in Krita 2. Drawing display - Huion Kamvas 22 Plus (I've tried this on drawing display and drawing tablet both) using Windows 8 + Pointer Input 3. Any changes to cursor (changing gui size, pressing spacebar to drag canvas, etc.) OBSERVED RESULT Cursor becomes huge with green pixelated outline for a very short time, but it happens very often EXPECTED RESULT Normal cursor SOFTWARE/OS VERSIONS Windows: Windows 10 Pro 20H2 19042.870 ADDITIONAL INFORMATION I've tried recreating this bug in other drawing software (Clip Studio Paint), but nothing similar happened. It doesn't happen with Windows interface too, only in Krita. Graphics card and drivers are both working well and up to date -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435007] Cursor Glitching (huge green artifacts)
https://bugs.kde.org/show_bug.cgi?id=435007 --- Comment #1 from Alexey --- Created attachment 137098 --> https://bugs.kde.org/attachment.cgi?id=137098&action=edit Cursor Glitching Showcase Video -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430954] New: System settings crashed when I was changing tabs from "Colors" to "Application Style"
https://bugs.kde.org/show_bug.cgi?id=430954 Bug ID: 430954 Summary: System settings crashed when I was changing tabs from "Colors" to "Application Style" Product: systemsettings Version: 5.20.4 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: esbo...@gmail.com Target Milestone: --- Application: systemsettings5 (5.20.4) Qt Version: 5.15.2 Frameworks Version: 5.77.0 Operating System: Linux 5.4.0-58-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.20 -- Information about the crash: - What I was doing when the application crashed: I was on the "Colors" tab. Then I clicked "Application Style" tab. The crash does not seem to be reproducible. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [New LWP 4000] [New LWP 4001] [New LWP 4006] [New LWP 4008] [New LWP 4027] [New LWP 4028] [New LWP 4063] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f8504ac1aff in __GI___poll (fds=0x7ffc79ef4428, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f85004f98c0 (LWP 3999))] Thread 8 (Thread 0x7f84c7928700 (LWP 4063)): #0 0x7f8502bb611f in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f8502bb766b in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8502bb80db in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8502bb82e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f850508cfbb in QEventDispatcherGlib::processEvents (this=0x7f84ac25f750, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f85050311ab in QEventLoop::exec (this=this@entry=0x7f84c7927cc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #6 0x7f8504e4ba12 in QThread::exec (this=this@entry=0x55f002717950) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #7 0x7f8504048fa9 in QQmlThreadPrivate::run (this=0x55f002717950) at qml/ftw/qqmlthread.cpp:155 #8 0x7f8504e4cbac in QThreadPrivate::start (arg=0x55f002717950) at thread/qthread_unix.cpp:329 #9 0x7f85034ca609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f8504ace293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f84c8129700 (LWP 4028)): #0 __libc_disable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:83 #1 0x7f8504ac1b13 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:29 #2 0x7f8502bb81ae in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8502bb8533 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f84cae9ceda in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #5 0x7f8502be1931 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f85034ca609 in start_thread (arg=) at pthread_create.c:477 #7 0x7f8504ace293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f84d7ed7700 (LWP 4027)): #0 0x7f8504ac1aff in __GI___poll (fds=0x55f0002ac110, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f8502bb81ae in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8502bb82e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8502bb8331 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8502be1931 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f85034ca609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f8504ace293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f84e5816700 (LWP 4008)): #0 __GI___libc_read (nbytes=16, buf=0x7f84e5815ab0, fd=17) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=17, buf=0x7f84e5815ab0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f8502c0089f in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8502bb7cfe in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8502bb8152 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f8502bb82e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f850508cfbb in QEventDispatcherGlib::processEvents (this=0x7f84db60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f85050311ab in QEventLoop::exec (this=this@entry=0x7f84e5815cc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #8 0x7f8504e4ba12 in QThread::exec (this=this@entry=0x55efffbf5e90)
[plasmashell] [Bug 491582] KDE does not position Wine application tray icon pop-up menus correctly
https://bugs.kde.org/show_bug.cgi?id=491582 --- Comment #3 from Alexey --- (In reply to Konrad Materka from comment #2) > Is it OK if you disable fraction scaling? Are you using multiple screens? no and no. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477673] KDEConnect - sshfs finished with exit code 1 when attempting to browse
https://bugs.kde.org/show_bug.cgi?id=477673 Alexey changed: What|Removed |Added CC||alexi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490365] New: Dolphin's notification about the background process takes up half the width in Notifications and overlaps the lower content with action buttons
https://bugs.kde.org/show_bug.cgi?id=490365 Bug ID: 490365 Summary: Dolphin's notification about the background process takes up half the width in Notifications and overlaps the lower content with action buttons Classification: Plasma Product: plasmashell Version: 6.1.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: alexi...@gmail.com CC: k...@privat.broulik.de Target Milestone: 1.0 Created attachment 171708 --> https://bugs.kde.org/attachment.cgi?id=171708&action=edit Demo See the attachment. STEPS TO REPRODUCE 1. Run some operation in Dolphin, e.g. Compress directory; 2. Minimize notification; 3. Open "Notifications"; 4. Delete some notification under Dolphin's operation notification. OBSERVED RESULT See attachments. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel version: 6.9.9-arch1-1 (64-bit) Graphics platform: Wayland (with fractional scaling 1.25) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490365] Dolphin's notification about the background process takes up half the width in Notifications and overlaps the lower content with action buttons
https://bugs.kde.org/show_bug.cgi?id=490365 Alexey changed: What|Removed |Added CC||alexi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491582] New: KDE does not position Wine application tray icon pop-up menus correctly
https://bugs.kde.org/show_bug.cgi?id=491582 Bug ID: 491582 Summary: KDE does not position Wine application tray icon pop-up menus correctly Classification: Plasma Product: kwin Version: 6.1.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: alexi...@gmail.com Target Milestone: --- Created attachment 172512 --> https://bugs.kde.org/attachment.cgi?id=172512&action=edit Demo 1 SUMMARY Since some release (probably the 6th), my Wine applications that use tray menus (mainly game launchers) stopped displaying the menu. The tray icon still displayed animation, but the menu did not open. Today I decided to move the bottom panel to the left and found that with this arrangement, the launcher menus are visible on the screen. STEPS TO REPRODUCE 1. Open some Wine app with tray menus; 2. Try to right click it (or do something else to open menu). OBSERVED RESULT Popup tray menu opens correctly with correct position. EXPECTED RESULT Popup tray menu shows something out of screen with bottom panel and nearly at bottom left corner with left-aligned panel. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Wayland session, fractional scaling (1.25). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491582] KDE does not position Wine application tray icon pop-up menus correctly
https://bugs.kde.org/show_bug.cgi?id=491582 --- Comment #1 from Alexey --- Created attachment 172513 --> https://bugs.kde.org/attachment.cgi?id=172513&action=edit Demo 2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491582] KDE does not position Wine application tray icon pop-up menus correctly
https://bugs.kde.org/show_bug.cgi?id=491582 Alexey changed: What|Removed |Added Platform|Other |Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 401824] [Wayland] Label of "Install" and "Remove" buttons is black when Discover is started via "Manage 'app'" feature of the apps launchers and when I open a local file (de
https://bugs.kde.org/show_bug.cgi?id=401824 Alexey changed: What|Removed |Added CC||alexeyloze...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 401824] [Wayland] Label of "Install" and "Remove" buttons is black when Discover is started via "Manage 'app'" feature of the apps launchers and when I open a local file (de
https://bugs.kde.org/show_bug.cgi?id=401824 --- Comment #8 from Alexey --- thanks, it seems I understood what caused such a failure. Thx. чт, 4 июл. 2019 г. в 18:06, Patrick Silva : > https://bugs.kde.org/show_bug.cgi?id=401824 > > --- Comment #7 from Patrick Silva --- > Currently I can't reproduce this behavior using the "Manage'app'" feature > from > the apps launchers. > However it is still reproducible when I open a .flatpakref file while > Discover > is already running. > > Operating System: Arch Linux > KDE Plasma Version: 5.16.2 > KDE Frameworks Version: 5.59.0 > Qt Version: 5.13.0 > > -- > 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.
[krita] [Bug 376722] Grayscale Color Space: Inversion with Artifacts
https://bugs.kde.org/show_bug.cgi?id=376722 Alexey changed: What|Removed |Added Resolution|WORKSFORME |FIXED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407401] New: Layer is saved without FX
https://bugs.kde.org/show_bug.cgi?id=407401 Bug ID: 407401 Summary: Layer is saved without FX Product: krita Version: 4.1.7 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: layer styles Assignee: krita-bugs-n...@kde.org Reporter: o-di...@ya.ru Target Milestone: --- If we add FX for layer and use a 'Save Layer/Mask' function, layer be saved without FX. The same behavior we see if we call the "Isolate Layer" function. All OS version. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407403] New: Transformation and Mirror mode
https://bugs.kde.org/show_bug.cgi?id=407403 Bug ID: 407403 Summary: Transformation and Mirror mode Product: krita Version: 4.1.7 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: o-di...@ya.ru Target Milestone: --- Created attachment 119963 --> https://bugs.kde.org/attachment.cgi?id=119963&action=edit With and without Mirror Tool (fake process) If we enable the Mirror Tool (Horizontal or Vertical), we can painting with it correctly and get a mirrored image. But if we create a some selection and transform the image, we won't have a mirrored image. Because selection and Transform/Move Tools is not working with the Mirror Tool. (See attachment with fake work process how could it be) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407405] New: Pixel paint, Line Tool and Grid with 1px offset!
https://bugs.kde.org/show_bug.cgi?id=407405 Bug ID: 407405 Summary: Pixel paint, Line Tool and Grid with 1px offset! Product: krita Version: 4.1.7 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: o-di...@ya.ru Target Milestone: --- Created attachment 119965 --> https://bugs.kde.org/attachment.cgi?id=119965&action=edit dancing pixels The Brush Tool and Grid cannot snap to the center of the pixel. This causes some problems when trying to draw pixel art. The basic problem with diagonal lines. If we use the Line Tool, we get an uneven line with artifacts (see attachment). Since our line can't bind exactly to the center of the pixel (or something else) — we get a 'dancing pixels'. 1. Take an empty layer 2. Take Line Tool and 'pixel1' brush with sharpness 3. Try to draw a couple of good diagonal lines -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404875] New: Kwin crashed
https://bugs.kde.org/show_bug.cgi?id=404875 Bug ID: 404875 Summary: Kwin crashed Product: kwin Version: 5.13.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mrflomast...@gmail.com Target Milestone: --- Application: kwin_x11 (5.13.5) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.18.0-15-generic x86_64 Distribution: Ubuntu 18.10 -- Information about the crash: - What I was doing when the application crashed: каждый раз когда я закрываю крышку ноутбука он ходит в ожидание, при выходе из режима ожидания выходит ошибка The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc3e2622840 (LWP 5436))] Thread 6 (Thread 0x7fc3c61f7700 (LWP 11159)): #0 0x7fc3ecc0d7d6 in __GI_ppoll (fds=0x7fc3c0001328, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fc3eb7ae141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fc3eb7af5b9 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fc3eb75f16b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc3eb5ae0b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc3eb5b7c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc3ea3e8164 in start_thread (arg=) at pthread_create.c:486 #7 0x7fc3ecc19def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fc3c55f5700 (LWP 5459)): #0 0x7fc3ea3ee2eb in futex_wait_cancelable (private=, expected=0, futex_word=0x7fc3eb1cbfb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fc3ea3ee2eb in __pthread_cond_wait_common (abstime=0x0, mutex=0x7fc3eb1cbf68, cond=0x7fc3eb1cbf90) at pthread_cond_wait.c:502 #2 0x7fc3ea3ee2eb in __pthread_cond_wait (cond=0x7fc3eb1cbf90, mutex=0x7fc3eb1cbf68) at pthread_cond_wait.c:655 #3 0x7fc3eb0d4e2a in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7fc3eb0d4e49 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7fc3ea3e8164 in start_thread (arg=) at pthread_create.c:486 #6 0x7fc3ecc19def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fc3da9fc700 (LWP 5455)): #0 0x7fc3ecc0d7d6 in __GI_ppoll (fds=0x7fc3c8000d28, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fc3eb7ae141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fc3eb7af5b9 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fc3eb75f16b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc3eb5ae0b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc3e9c191f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fc3eb5b7c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc3ea3e8164 in start_thread (arg=) at pthread_create.c:486 #8 0x7fc3ecc19def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fc3e0945700 (LWP 5440)): #0 0x7fc3ecc0d7d6 in __GI_ppoll (fds=0x7fc3d400eb88, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fc3eb7ae141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fc3eb7af5b9 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fc3eb75f16b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc3eb5ae0b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc3e96fd545 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fc3eb5b7c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc3ea3e8164 in start_thread (arg=) at pthread_create.c:486 #8 0x7fc3ecc19def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fc3e1a66700 (LWP 5439)): #0 0x7fc3ecc0d6d9 in __GI___poll (fds=0x7fc3e1a65c78, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc3ec712917 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fc3ec71453a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fc3e1f5a159 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fc3eb5b7c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc3ea3e8164 in start_thread (arg=
[yakuake] [Bug 396697] Does not open with multi monitor on left screen when panel located right screen
https://bugs.kde.org/show_bug.cgi?id=396697 Alexey changed: What|Removed |Added CC||swe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscd] [Bug 160253] Don't work interface elements in CD-audio player
https://bugs.kde.org/show_bug.cgi?id=160253 --- Comment #2 from Alexey --- Hello. I am sorry, I forgot about this bug. It's too old. I do not using KDE now, I using different desktop environment. I can not help to check is this bug still exist in KDE. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422805] New: Not correct size an mask layer when converting it from the paint layer
https://bugs.kde.org/show_bug.cgi?id=422805 Bug ID: 422805 Summary: Not correct size an mask layer when converting it from the paint layer Product: krita Version: 4.3.0-beta2 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Resize/Scale Image/Layer Assignee: krita-bugs-n...@kde.org Reporter: o-di...@ya.ru Target Milestone: --- Created attachment 129227 --> https://bugs.kde.org/attachment.cgi?id=129227&action=edit Not correct size an mask layer when converting it from the paint layer and invert Not correct size an mask layer when converting it from the paint layer and invert. STEPS TO REPRODUCE 1. Create a paint layer №1 with an color 2. Create a paint layer №2 with black color 3. Convert №2 to transparency mask 4. Use invert color for p.l. №2 OBSERVED RESULT Mask size not equal layer size EXPECTED RESULT Mask size equal layer size See attached video. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422805] Not correct size an mask layer when converting it from the paint layer
https://bugs.kde.org/show_bug.cgi?id=422805 --- Comment #1 from Alexey --- Not correct size an mask layer when converting it from the paint layer and invert Not correct size an mask layer when converting it from the paint layer and invert. STEPS TO REPRODUCE 1. Create a paint layer №1 with an color 2. Create a paint layer №2 with white color 3. Convert №2 to transparency mask 4. Use invert color for p.l. №2 OBSERVED RESULT Mask size not equal layer size EXPECTED RESULT Mask size equal layer size See attached video. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422805] Not correct size an mask layer when converting it from the paint layer
https://bugs.kde.org/show_bug.cgi?id=422805 --- Comment #2 from Alexey --- Not correct size an mask layer when converting it from the paint layer and invert STEPS TO REPRODUCE 1. Create a paint layer №1 with an color 2. Create a paint layer №2 with white color 3. Convert №2 to transparency mask 4. Use invert color for p.l. №2 OBSERVED RESULT Mask size not equal layer size EXPECTED RESULT Mask size equal layer size See attached video. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422805] Not correct size an mask layer when converting it from the paint layer
https://bugs.kde.org/show_bug.cgi?id=422805 --- Comment #3 from Alexey --- I don't know how to delete the first and second comments ::) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422805] Not correct size an mask layer when converting it from the paint layer
https://bugs.kde.org/show_bug.cgi?id=422805 --- Comment #7 from Alexey --- Good job! ::)(In reply to Dmitry Kazakov from comment #6) > Git commit 0c68de311da58565ef93ebe2baca24286900e025 by Dmitry Kazakov. > Committed on 13/06/2020 at 09:44. > Pushed by dkazakov into branch 'master'. > > Fix applying invert filter on transparency masks > > We should care about KisFilter::needsTransparentPixels() when > auto-cropping processing area. > Related: bug 329846 > > M +3-0libs/ui/tool/strokes/kis_filter_stroke_strategy.cpp > > https://invent.kde.org/graphics/krita/commit/ > 0c68de311da58565ef93ebe2baca24286900e025 -- You are receiving this mail because: You are watching all bug changes.
