[kmail2] [Bug 492833] Can't login to Outlook, and account folder had absent when I logged in.
https://bugs.kde.org/show_bug.cgi?id=492833 --- Comment #3 from Leo C. --- KMail is also seperated from Kontact without why. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 492833] Can't login to Outlook, and account folder had absent when I logged in.
https://bugs.kde.org/show_bug.cgi?id=492833 --- Comment #2 from Leo C. --- Created attachment 173453 --> https://bugs.kde.org/attachment.cgi?id=173453&action=edit Despite I logged in, but it still need a new account. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 492833] Can't login to Outlook, and account folder had absent when I logged in.
https://bugs.kde.org/show_bug.cgi?id=492833 --- Comment #1 from Leo C. --- Created attachment 173452 --> https://bugs.kde.org/attachment.cgi?id=173452&action=edit It still can receive new mail, but folder are absent. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 492833] New: Can't login to Outlook, and account folder had absent when I logged in.
https://bugs.kde.org/show_bug.cgi?id=492833 Bug ID: 492833 Summary: Can't login to Outlook, and account folder had absent when I logged in. Classification: Applications Product: kmail2 Version: 6.2.0 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: leonclar...@outlook.com Target Milestone: --- Created attachment 173451 --> https://bugs.kde.org/attachment.cgi?id=173451&action=edit No folder after I logged in. SUMMARY Sorry to bother team, but I can't login too Google Mail, Outlook, and if I logged in, no mail folder was appeared. STEPS TO REPRODUCE 1. Open K-Mail 2. Login to Google Mail or Outlook OBSERVED RESULT With Google Mail account : It really point to OAuth2 login, but when I filled information and got authentication successfully, account folder is still absent in menu. 60 second timeout is too short, especially who have TOTP like me. With Outlook account: It "logged in" without a notice. I must go to settings -> SMTP server and then Restart -> It point to OAuth2 login. When I logged in there's still no folder in menu. (Outlook has abandoned Basic Authentication and moved to OAuth2). EXPECTED RESULT Folders with account in menu. Longer timeout. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.7-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 6.6 GiB of RAM Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION I installed from dnf -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 492829] New: Misplaced fingerprint table.
https://bugs.kde.org/show_bug.cgi?id=492829 Bug ID: 492829 Summary: Misplaced fingerprint table. Classification: Applications Product: kleopatra Version: 3.2.0.240800 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aheine...@gnupg.org Reporter: leonclar...@outlook.com CC: kdepim-b...@kde.org, m...@kde.org Target Milestone: --- Created attachment 173449 --> https://bugs.kde.org/attachment.cgi?id=173449&action=edit This is the image point misplaced table. SUMMARY A table has misplaced on username section. STEPS TO REPRODUCE 1. Open Kleopatra 2. Click an username 3. OBSERVED RESULT Misplaced fingerprint,name,email table, cover up GPG key name. I can't move or resize table. It's a feature or bug? EXPECTED RESULT I want it placed correctly. I'm really sorry if it's duplicate. Thank you. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.7-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 6.6 GiB of RAM Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION None. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 490291] New: some apps is hanging or freezing while using it
https://bugs.kde.org/show_bug.cgi?id=490291 Bug ID: 490291 Summary: some apps is hanging or freezing while using it Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: englishious@gmail.com Target Milestone: --- I’m experiencing an issue with an app that hangs while I’m using it. The problem occurs intermittently, causing the app to freeze and become unresponsive. I’ve tried restarting the app and my device, but the issue persists. This interruption affects my workflow and productivity, making it challenging to complete tasks efficiently. I’m looking for suggestions on how to resolve this issue or any troubleshooting steps I can follow. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 316734] After waking the system, the desktop gets displayed for a moment before the lock screen appears
https://bugs.kde.org/show_bug.cgi?id=316734 leo changed: What|Removed |Added CC||leohyam...@gmail.com Version|unspecified |6.0.5 Platform|Arch Linux |Manjaro --- Comment #83 from leo --- (In reply to Nate Graham from comment #76) > As David hinted at, this is fixable on Wayland, but it's a game of > whack-a-mole on X11. It's one of those things where if you want a better > experience here, use Wayland. Wayland is unusable for me as I am using an Nvidia graphics card and have found compatibility to be quite poor. Any assistance regarding fixing with X11 would be appreciated. OS: Manjaro 24.0.3 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3 Kernel Version: 6.9 Graphics Platform: X11 GPU: NVIDIA AD107M [GeForce RTX 4060 Max-Q / Mobile] CPU: Intel Core Ultra 9 185H Mesa Version: 24.1.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455431] "Spare Layouts" feature on Wayland
https://bugs.kde.org/show_bug.cgi?id=455431 Leo changed: What|Removed |Added CC||leo.sh@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486620] New: Network share subfolders disappear when expanding folder in detail mode
https://bugs.kde.org/show_bug.cgi?id=486620 Bug ID: 486620 Summary: Network share subfolders disappear when expanding folder in detail mode Classification: Applications Product: dolphin Version: 24.02.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: view-engine: details mode Assignee: dolphin-bugs-n...@kde.org Reporter: leo.ho...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When browsing SMB network shares in detail mode and trying to expand the subfolder view from the expansion arrow, the subfolder may disappear from view completely and return only after clicking refresh manually. STEPS TO REPRODUCE 1. Open SMB network share 2. Set view to details mode 3. Click expand arrow next to some subfolder to expand view OBSERVED RESULT The subfolder vanishes from view and only returns if view is refreshed manually (either by clicking refresh from menu or jumping to some other path/location). EXPECTED RESULT Subfolder expands to show contents. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION This seem to be some kind of view refreshing problem? I have only managed to reproduce it on my local network shares and even there it is not 100% consistent. Sometimes I can click 5 to 10 subfolders and they vanish and then on 11th the dolphin will expand the view as it should. But the vanished subfolders do stay hidden until refresh is clicked. When browsing remote network shares over VPN, I can't reproduce this, maybe because there is enough network delay when clicking expand that dolphin manages to refresh the folder tree view (I'm just theorizing). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 485908] New: Shift key locked
https://bugs.kde.org/show_bug.cgi?id=485908 Bug ID: 485908 Summary: Shift key locked Classification: Applications Product: krita Version: 5.2.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: leoterr...@hotmail.com Target Milestone: --- When the "shift:both_capslock" keyboard option is active (in X11) the Shift key is locked( activated) to press it in Krita, to unlocked need press Ctrl or Alt two times EXPECTED RESULT Shift key should be kept only while keeping it( without functioning as a switch) SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 485121] New: Pan tool seem to be "hardcoded" to wacom pen button 1
https://bugs.kde.org/show_bug.cgi?id=485121 Bug ID: 485121 Summary: Pan tool seem to be "hardcoded" to wacom pen button 1 Classification: Applications Product: krita Version: 5.2.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: mindwakerstud...@gmail.com Target Milestone: --- SUMMARY The wacom pen button 1 always uses the pan tool to pan around the canvas regardless of the modifiers I change in Wacom Tablet Properties and/or inside Krita Canvas Input Settings. I'd like the button 1 (closest to the tip) to be the button to change brush size, this is possible in CSP and PS(CS6). I briefly managed to make it work when removing Krita inside the Wacom Tablet Properties application list and using the "All Other" application settings, but after I re-opened Krita the functionality got lost and the pan tool was default again and no amount of settings and input switching brought back the brush size change functionality. STEPS TO REPRODUCE 1. Have a Wacom Intuos (not pro) M Bluetooth (connected with the USB cable) 2. Krita in its default settings 3. Assign shift + Left click or just Shift in Wacom Tablet Properties to the pen button closest to the tip and try to change brush size inside Krita. OBSERVED RESULT The "shift + left click" uses the pan tool instead. Changing this setting to anything else will also result to Krita using the pan tool. The "move hand" logo appears and moves around the canvas. Not changing to the actual tool. The same functionality as pressing down on space bar and left click holding and moving the mouse. EXPECTED RESULT Shift + Left click as per in Krita's default settings should change the brush size with the wacom pen but does not. -- You are receiving this mail because: You are watching all bug changes.
[Koko] [Bug 471142] Koko doesn`t show samba-Images
https://bugs.kde.org/show_bug.cgi?id=471142 Leo changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464532] New: The Flatpak kcm is not showing my flatpak apps
https://bugs.kde.org/show_bug.cgi?id=464532 Bug ID: 464532 Summary: The Flatpak kcm is not showing my flatpak apps Classification: Applications Product: systemsettings Version: 5.26.90 Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: kcm_flatpak Assignee: plasma-b...@kde.org Reporter: leo3...@riseup.net CC: joshiesuha...@gmail.com Target Milestone: --- Created attachment 155442 --> https://bugs.kde.org/attachment.cgi?id=155442&action=edit screenshot SUMMARY The flatpak permissions kcm is broken and not showing the flatpaks I have installed STEPS TO REPRODUCE 1. Install flatpak-kcm if its not installed 2. Open the kcm OBSERVED RESULT No flatpak apps appear even if you have flatpak apps installed EXPECTED RESULT It should list the flatpak apps I have installed so I can configure the permissions SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 5.15.89-1-lts (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION All the flatpaks are installed as user instead of system wide -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 327192] GPG - PGP Key-Pair Generation Failure Ubuntu T-Bird AND Kleopatra
https://bugs.kde.org/show_bug.cgi?id=327192 --- Comment #5 from Leo Rivers --- > REPORTED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 455752] New: subwindows format
tosave Interval: 420 Use Backup Files: true Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Backup Location writable: false Use Win8 Pointer Input: false Use RightMiddleTabletButton Workaround: false Levels of Detail Enabled: false Use Zip64: false Display Information Number of screens: 2 Screen: 0 Name: DP-0 Depth: 24 Scale: 1 Resolution in pixels: 1920x1080 Manufacturer: LG Electronics Model: MP59G- Refresh Rate: 74.9725 Screen: 1 Name: HDMI-0 Depth: 24 Scale: 1 Resolution in pixels: 1920x1080 Manufacturer: LG Electronics Model: LG IPS FULLHD Refresh Rate: 60 Current Settings Current Swap Location: /tmp Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 200 Use OpenGL: true Use OpenGL Texture Buffer: true Disable Vector Optimizations: false Disable AVX Optimizations: false Canvas State: OPENGL_SUCCESS Autosave Interval: 420 Use Backup Files: true Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Backup Location writable: false Use Win8 Pointer Input: false Use RightMiddleTabletButton Workaround: false Levels of Detail Enabled: false Use Zip64: false Current Settings Current Swap Location: /tmp Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 200 Use OpenGL: true Use OpenGL Texture Buffer: true Disable Vector Optimizations: false Disable AVX Optimizations: false Canvas State: OPENGL_SUCCESS Autosave Interval: 420 Use Backup Files: true Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Backup Location writable: false Use Win8 Pointer Input: false Use RightMiddleTabletButton Workaround: false Levels of Detail Enabled: false Use Zip64: false Current Settings Current Swap Location: /tmp Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 200 Use OpenGL: true Use OpenGL Texture Buffer: true Disable Vector Optimizations: false Disable AVX Optimizations: false Canvas State: OPENGL_SUCCESS Autosave Interval: 420 Use Backup Files: true Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Backup Location writable: false Use Win8 Pointer Input: false Use RightMiddleTabletButton Workaround: false Levels of Detail Enabled: false Use Zip64: false - SESSION: 20 Jun 2022 00:47:48 -0300. Executing /usr/bin/krita Krita Version: 5.0.2, Qt version compiled: 5.15.2, loaded: 5.15.3. Process ID: 2238 -- -- -- -- -- -- -- -- 20 Jun 2022 00:47:48 -0300: Style: breeze. Available styles: Breeze, Oxygen, Windows, Fusion 20 Jun 2022 00:49:41 -0300: CLOSING SESSION SESSION: 20 Jun 2022 18:10:32 -0300. Executing /usr/bin/krita Krita Version: 5.0.2, Qt version compiled: 5.15.2, loaded: 5.15.3. Process ID: 10444 -- -- -- -- -- -- -- -- 20 Jun 2022 18:10:32 -0300: Style: breeze. Available styles: Breeze, Oxygen, Windows, Fusion 20 Jun 2022 18:10:34 -0300: Database is up to date. Version: 0.0.15, created by Krita 5.0.2, at lun jun. 20 00:47:52 2022 20 Jun 2022 18:10:48 -0300: CLOSING SESSION SESSION: 21 Jun 2022 17:25:01 -0300. Executing /usr/bin/krita Krita Version: 5.0.2, Qt version compiled: 5.15.2, loaded: 5.15.3. Process ID: 1800 -- -- -- -- -- -- -- -- 21 Jun 2022 17:25:01 -0300: Style: breeze. Available styles: Breeze, Oxygen, Windows, Fusion 21 Jun 2022 17:25:02 -0300: Database is up to date. Version: 0.0.15, created by Krita 5.0.2, at lun jun. 20 00:47:52 2022 21 Jun 2022 17:27:30 -0300: CLOSING SESSION SESSION: 21 Jun 2022 17:38:49 -0300. Executing /usr/bin/krita Krita Version: 5.0.2, Qt version compiled: 5.15.2, loaded: 5.15.3. Process ID: 1710 -- -- -- -- -- -- -- -- 21 Jun 2022 17:38:49 -0300: Style: breeze. Available styles: Breeze, Oxygen, Windows, Fusion 21 Jun 2022 17:38:51 -0300: Database is up to date. Version: 0.0.15, created by Krita 5.0.2, at lun jun. 20 00:47:52 2022 21 Jun 2022 17:39:16 -0300: Created image "Sin nombre", 2480 * 3508 pixels, 300 dpi. Color model: Entero de 8 bits/canal RGB/Alfa (sRGB-elle-V2-srgbtrc.icc). Layers: 2 21 Jun 2022 17:54:14 -0300: Autosaving: /home/leo/.krita-1710-document_0-autosave.kra 21 Jun 2022 17:54:14 -0300: Converting from application/x-krita to application/x-krita. Location: /home/leo/.krita-1710-document_0-autosave.kra. Real location: /home/leo/.krita-1710-document_0-autosave.kra. Batchmode: 0. Configuration: none 21 Jun 2022 17:54:14 -0300: Completed saving /home/leo/.krita-1710-document_0-autosave.kra (mime: application/x-krita). Result: OK. Warning: . Size: 685110 - -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 455554] ANSI background color malfunction
https://bugs.kde.org/show_bug.cgi?id=44 --- Comment #3 from Leo Savernik --- In the latest konsole I noticed that ANSI background tinting stopped working properly: \033]11;#32\a where #32 can be any #rrggbb color code. *Steps to reproduce* 1. Open fresh Konsole 2. (optional) Fill screen with arbitrary foreground content 3. printf '\033]11;#32\a' *Expected results* Whole Terminal background is immediately tinted dark red. *Actual results* Terminal background stays black. Only if terminal window is forced to be repainted, the background tint will show. This is a regression compared to former Konsole (19.12.3) I compared with. ANSI background tint should *always* cause the Konsole display to be repainted. See attached screenshots. (1) is former Konsole (19.12.3), (1) is current Konsole (21.12.3). The last screenshot displays successful tinting of current Konsole when a full redraw was triggered. This is a usability issue: I use background tinting on remote shells to be able to tell at a glance whether the command I'm typing will have local effects. It's unfortunate that this bug was distributed in a Kubuntu LTS. Maybe backporting can be done. *Software versions* Linux/KDE Plasma: 5.24.4 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 455554] ANSI background color malfunction
https://bugs.kde.org/show_bug.cgi?id=44 --- Comment #2 from Leo Savernik --- Created attachment 149899 --> https://bugs.kde.org/attachment.cgi?id=149899&action=edit Konsole after having applied ANSI background with forced refresh -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 455554] ANSI background color malfunction
https://bugs.kde.org/show_bug.cgi?id=44 --- Comment #1 from Leo Savernik --- Created attachment 149898 --> https://bugs.kde.org/attachment.cgi?id=149898&action=edit Konsole immediately after having applied ANSI background -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 455554] New: ANSI background color malfunction
https://bugs.kde.org/show_bug.cgi?id=44 Bug ID: 44 Summary: ANSI background color malfunction Product: konsole Version: 21.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: emulation Assignee: konsole-de...@kde.org Reporter: l.saver...@aon.at Target Milestone: --- Created attachment 149897 --> https://bugs.kde.org/attachment.cgi?id=149897&action=edit Konsole before applying ANSI background In the latest konsole I noticed that ANSI background tinting stopped working properly: \033]11;#32\a where #32 can be any #rrggbb color code. *Steps to reproduce* 1. Open fresh Konsole 2. (optional) Fill screen with arbitrary foreground content 3. printf '\033]11;#32\a' *Expected results* Whole Terminal background is immediately tinted dark red. *Actual results* Terminal background stays black. Only if terminal window is forced to be repainted, the background tint will show. This is a regression compared to former Konsole (19.12.3) I compared with. ANSI background tint should *always* cause the Konsole display to be repainted. See attached screenshots. (1) is former Konsole (19.12.3), (1) is current Konsole (21.12.3). The last screenshot displays successful tinting of current Konsole when a full redraw was triggered. This is a usability issue: I use background tinting on remote shells to be able to tell at a glance whether the command I'm typing will have local effects. It's unfortunate that this bug was distributed in a Kubuntu LTS. Maybe backporting can be done. *Software versions* Linux/KDE Plasma: 5.24.4 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449987] krita suffer a fatal error and doesnt let me use the app anymore
https://bugs.kde.org/show_bug.cgi?id=449987 --- Comment #3 from Leo --- Created attachment 146606 --> https://bugs.kde.org/attachment.cgi?id=146606&action=edit Captura de pantalla (207).png --- Comment #4 from Leo --- Created attachment 146607 --> https://bugs.kde.org/attachment.cgi?id=146607&action=edit Captura de pantalla (206).png -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449987] krita suffer a fatal error and doesnt let me use the app anymore
https://bugs.kde.org/show_bug.cgi?id=449987 --- Comment #2 from Leo --- Greetings, i put the files like you told me and apparently the program works again, i havent try to use it but it opens normally again.Thank you very much.:) Mensaje original De: Alvin Wong Fecha: 11/2/2022 12:55 a. m. (GMT-06:00) A: leonardolara...@gmail.com Asunto: [krita] [Bug 449987] krita suffer a fatal error and doesnt let me use the app anymore https://bugs.kde.org/show_bug.cgi?id=449987Alvin Wong changed: What |Removed |Added CC| |al...@alvinhc.com--- Comment #1 from Alvin Wong ---Hi, other Steam applications probably has nothing to do with this. Reinstallingdoes not reset the settings of Krita so that wouldn't help. Do you rememberwhere exactly did you move the resources (I assume you changed the resourcelocation)?Please follow these steps to check the Krita configuration file:1. Open Notepad2. Inside Notepad, select "File -> Open" from the menu3. In the filename, input "%localappdata%\kritarc" (without quotes)4. Find the two lines starting with "ResourceCacheDbDirectory=" and"ResourceDirectory="5. Note these two lines and reply to this bug report with them so we can seewhat was happening.To fix your Krita configuration, you can just remove these two lines and savethe file. This should cause Krita to use the default resource location. (Pleaseclose the file before launching Krita.)-- You are receiving this mail because:You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449987] New: krita suffer a fatal error and doesnt let me use the app anymore
https://bugs.kde.org/show_bug.cgi?id=449987 Bug ID: 449987 Summary: krita suffer a fatal error and doesnt let me use the app anymore Product: krita Version: 5.0.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: leonardolara...@gmail.com Target Milestone: --- Created attachment 146567 --> https://bugs.kde.org/attachment.cgi?id=146567&action=edit error message I was testing the pen pressure on the tablet and the app, and I was also moving where the resources were stored, I passed them to data (they were on windows) I have krita on steam and I was using another steam application (I don't know if this is relevant, the app was dead by daylight), once I finished playing, I wanted to enter the app but an error message appeared, I managed to enter the app using a file I was working on, uninstall the app and reinstall it and when I wanted to enter by both ways I could not. i tried to install krita from the website and the same message appear STEPS TO REPRODUCE 1. open another steam app 2. open krita (steam version) 3. move the storage and pen pressure 4. close both apps 5. done, the error will appear, now you can only enter the app using an old file 6. uninstall and reinstall krita 7. i can no longer use or enter krita OBSERVED RESULT error message EXPECTED RESULT be able to still using krita SOFTWARE/OS VERSIONS Windows: 5.0.2 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.
[kdenlive] [Bug 448996] New: Randomly Crash
https://bugs.kde.org/show_bug.cgi?id=448996 Bug ID: 448996 Summary: Randomly Crash Product: kdenlive Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Documentation Assignee: ttg...@gmail.com Reporter: fndle...@gmail.com Target Milestone: --- One more things I realize since I used Kdenlive from the older version until now, and this problem haven't fix yet here on Microsoft Windows version. So annoying when the Kdenlive app oftenly random crash when I do my works on it. Sometime it suddenly stuck and closed by itself. When I open the app again, it doesn't recover my work at all, and I need to do everything all over again. FYI the auto recovery was turned on but only recover my work if I haven't save my project. If I already save the project, every single change that I made after the save, will be lost and not recovered if the app crash when I forgot to hit that "save" button. Even if the recovery message pop up, I click "recover" and it says error can't recover or something like that. It is so annoying and frustrated to do things once again, if it crash. Please fix this on the next version. If you guys unable to fix the random crash, at least fix the recovery system, so it could recover my work safely whenever the app or my computer itself crash. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 447912] New: Bugs In Kdenlive
https://bugs.kde.org/show_bug.cgi?id=447912 Bug ID: 447912 Summary: Bugs In Kdenlive Product: kdenlive Version: 21.12.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: fndle...@gmail.com Target Milestone: --- - Export Frame not working in this new version while it works before in the old version - The buttons on the left top where the "save" etc until "render" button also missing. It used to be there in the old version - I can't resize project monitor too far like what i always do in the old version especially when i need to do keyframing. Please fix all this.. I want the KDE like the old version used to :'( -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 447911] New: Bugs In Kdenlive
https://bugs.kde.org/show_bug.cgi?id=447911 Bug ID: 447911 Summary: Bugs In Kdenlive Product: kdenlive Version: 21.12.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: fndle...@gmail.com Target Milestone: --- - Export Frame not working in this new version while it works before in the old version - The buttons on the left top where the "save" etc until "render" button also missing. It used to be there in the old version - I can resize project monitor too far like what i always do in the old version especially when i need to do keyframing. Please fix all this.. I want the KDE like the old version used to :'( -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 447104] SUMMARY import (drag and drop) jpg image with out extension (.jpg), Kdenlive does not recognize the file as a jpg and then offers to transcode the image. No Cancel available.
https://bugs.kde.org/show_bug.cgi?id=447104 Leo changed: What|Removed |Added Summary|SUMMARY import (drag and|SUMMARY import (drag and |drop) jpg image with out|drop) jpg image with out |extension (.jpg), Kdenlive |extension (.jpg), Kdenlive |does not recognize the file |does not recognize the file |as a jpg and then offers to |as a jpg and then offers to |transcode the image.|transcode the image. No ||Cancel available. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 447104] New: SUMMARY import (drag and drop) jpg image with out extension (.jpg), Kdenlive does not recognize the file as a jpg and then offers to transcode the image.
https://bugs.kde.org/show_bug.cgi?id=447104 Bug ID: 447104 Summary: SUMMARY import (drag and drop) jpg image with out extension (.jpg), Kdenlive does not recognize the file as a jpg and then offers to transcode the image. Product: kdenlive Version: 21.04.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: l...@guildmedia.net Target Milestone: --- SUMMARY import (drag and drop) jpg image with out extension (.jpg), Kdenlive does not recognize the file as a jpg and then offers to transcode the image. Cannot get duration for file /home/xxx [Transcode] However there is no way to cancel this notification which now remains on the interface until the application is closed. STEPS TO REPRODUCE 1. import image missing extension 2. 3. OBSERVED RESULT notification remains on the interface until application is closed. EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210515 KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.13.1-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 32 × Intel® Xeon® CPU E5-2690 0 @ 2.90GHz Memory: 62.7 GiB of RAM Graphics Processor: AMD CEDAR ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 432507] New: Discover crashes on startup
https://bugs.kde.org/show_bug.cgi?id=432507 Bug ID: 432507 Summary: Discover crashes on startup Product: Discover Version: 5.20.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: leowagz...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY When I start discover on Arch Linux, it opens for a second, and loads a little bit, then crashes after maybe 2 seconds. STEPS TO REPRODUCE 1. Open Discover 2. Wait 2 seconds 3. OBSERVED RESULT Program exits immediately EXPECTED RESULT Program runs, allowing user to install programs. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 428263] Clip speed does not work on image sequences
https://bugs.kde.org/show_bug.cgi?id=428263 Leo changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|FIXED |--- --- Comment #3 from Leo --- Please read the title and description of the bug report. Image SEQUENCE and NOT a single / static image. I have tested this, yet again with an IMAGE SEQUENCE clip and "Change Speed" does not work. For Image Sequences, this function is broken. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 428030] Turn off KDE connect
https://bugs.kde.org/show_bug.cgi?id=428030 --- Comment #6 from Leo Gaspard --- Hmm… but if that's the case, then why does it need a permanent notification even when not connected to a computer? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 428030] Turn off KDE connect
https://bugs.kde.org/show_bug.cgi?id=428030 --- Comment #4 from Leo Gaspard --- It'd definitely fit quite well a number of use cases, though I'm not sure whether it'd be possible to do so on android without additional permissions to read the wifi network names, which could maybe end up being repulsive? One use case that wouldn't be solved by such a solution would be when eg. giving classes, where one wants to use KDE connect to pass slides on the computer but not whitelist the whole university network, as it's not rare to be on the university network without actually giving classes and needing KDE connect — in this kind of situations, I see only an “on/off” toggle as a proper solution, as the alternative would be to manually add/remove the university wifi before/after each class. Now, for full disclosure, it's not a use case I personally tried yet (didn't give a course “physically” since trying out KDE connect yet), so I may be missing some data points that'd remove it altogether (eg. maybe the university wifi will break KDE connect anyway next time I can try it there) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 428030] Turn off KDE connect
https://bugs.kde.org/show_bug.cgi?id=428030 --- Comment #2 from Leo Gaspard --- I don't have any hard numbers either way for battery issues, as KDE connect probably doesn't consume much by itself and only hooks into requiring things that consume battery — so this part of the top post may be a non-issue, and this bugreport is mostly for the “leak the information that my phone is running KDE connect on the local network even when there's no computer I want to connect to” part of the issue. Now, maybe I'm mis-assuming how KDE connect works, and there is actually no such information leak? (Well, for complete transparency, I as a perfectionist wouldn't like having processes I have no use for running in the background anyway when I could just kill it and restart it next time I need it, but I also totally understand this alone is not reason enough to add a “shutdown KDE connect” button) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 428263] Clip speed does not work on image sequences
https://bugs.kde.org/show_bug.cgi?id=428263 --- Comment #1 from Leo --- Change clip speed works as expected on a normal video clip. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 428263] New: Clip speed does not work on image sequences
https://bugs.kde.org/show_bug.cgi?id=428263 Bug ID: 428263 Summary: Clip speed does not work on image sequences Product: kdenlive Version: 20.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: l...@guildmedia.net Target Milestone: --- SUMMARY Clip speed does not work on image sequences STEPS TO REPRODUCE 1. Add image sequence clip to timeline 2. Right click, clip in timeline, Change Speed 3. Timeline playback / Render timeline OBSERVED RESULT Clip playback is stuck on first frame. Clip speed 100% works. Any other speed, slower (50%) or faster (200%) does not work. EXPECTED RESULT Image sequence plays at the specified speed SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSuse Tumbleweed 20200819 (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 428030] New: Turn off KDE connect
https://bugs.kde.org/show_bug.cgi?id=428030 Bug ID: 428030 Summary: Turn off KDE connect Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: k...@leo.gaspard.io Target Milestone: --- It appears to be impossible to turn off the KDE connect application, as shown by the persistent notification never going away, including when swiping out the application window. Would it be possible to add a button somewhere to turn KDE connect off, so that it stops (I assume) multicasting (thus broadcasting the phone's identity) and consuming battery (though I don't have hard numbers on how much battery is consumed)? As far as I understand, the only way to stop KDE connect is the force stop button of android, and even then it'll come back on the next reboot… which is sad. Does this sound like a reasonable thing to add to KDE connect? Cheers, Leo -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425399] Moving/Resizing keyboard shortcut stop working after typing in a window
https://bugs.kde.org/show_bug.cgi?id=425399 Leo changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #5 from Leo --- Pardon me! The problem was solved after deleting the ~/.kde folder. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425399] Moving/Resizing keyboard shortcut stop working after typing in a window
https://bugs.kde.org/show_bug.cgi?id=425399
--- Comment #4 from Leo ---
(In reply to Vlad Zahorodnii from comment #3)
> (In reply to Leo from comment #2)
> > Hi. I have configured global shortcuts for KWin, not custom.
>
> I cannot reproduce the bug. What global shortcuts did you configure?
I have configured Quick Tile Window to the {Buttom, Top, Left, Right, etc}.
Also in my case other shortcuts such as Alt+F4 do not work.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 425399] Moving/Resizing keyboard shortcut stop working after typing in a window
https://bugs.kde.org/show_bug.cgi?id=425399 --- Comment #2 from Leo --- (In reply to Vlad Zahorodnii from comment #1) > > 1. Setup keyboard shortcut for moving/resizing windows (System > > Preferences=>Shortcuts=>KWin) > > What shortcuts exactly did you set? From the attached screen recording, it > looks like you assigned custom shortcuts to quick tile actions. Hi. I have configured global shortcuts for KWin, not custom. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425399] New: Moving/Resizing keyboard shortcut stop working after typing in a window
https://bugs.kde.org/show_bug.cgi?id=425399 Bug ID: 425399 Summary: Moving/Resizing keyboard shortcut stop working after typing in a window Product: kwin Version: 5.19.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: l...@app-gateway.nl Target Milestone: --- Created attachment 130898 --> https://bugs.kde.org/attachment.cgi?id=130898&action=edit Screen record After upgrading from 18.04 to 20.04, the keyboard shortcuts for moving/resizing the active window, for example, to the left side of the screen or to expand the window to full screen, stopped working for me. As soon as a window is opened, for example, the Konsole window, the keyboard shortcuts work, but as soon as the window receives input from the keyboard, the window title ceases to be active and the keyboard shortcuts stop working until the window is minimized and maximized again. STEPS TO REPRODUCE 1. Setup keyboard shortcut for moving/resizing windows (System Preferences=>Shortcuts=>KWin) 2. Open any window 3. Try moving/resizing with shortcuts (it will work) 4. Press any keys on your keyboard (at this point, the window title will become inactive) 5. Try moving/resizing with shortcuts again (it won't work anymore) 6. Minimize the window and maximize it 7. Try your shortcuts again (this will work again) Below I have attached a video that shows the problem. Operating System: KDE neon 5.19 KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 Kernel Version: 5.4.0-42-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz Memory: 15.5 GiB of RAM Graphics Processor: GeForce MX130/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 414407] Can't load database (plugin)
https://bugs.kde.org/show_bug.cgi?id=414407 --- Comment #35 from Leo --- Doohh -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 418389] Phonon4Qt5 installation issue
https://bugs.kde.org/show_bug.cgi?id=418389 --- Comment #1 from Leo --- Sorry, Not a bug I needed to install libphonon4qt5-dev -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 418389] Phonon4Qt5 installation issue
https://bugs.kde.org/show_bug.cgi?id=418389 Leo changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- 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 #115 from Leo --- Perhaps I made more settings than necessary in the profile, but there was no time for me to test. -- 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 #114 from Leo ---
(In reply to purplecandy from comment #113)
> Happened to me to I'm using ASUS Fx504 - Gtx 1050 and running Kubuntu 19.10.
> Eversince I activated NVIDIA every time I switch applications or drag them
> to edges everything hangs.
>
> Recently my kwin also crashed and the Compositer was disabled, that seems to
> have almost fixed it but it's not helpful. Also system wasn't able to
> generate any backtrace for the crash
Hi. I managed to solve the problem by adding a profile for nvidia. My profile
will look like this:
cat /home/leo/.nv/nvidia-application-profiles-rc
{
"rules": [
{
"pattern": {
"feature": "procname",
"matches": "kwin_x11"
},
"profile": "profile_327b23c6"
}
],
"profiles": [
{
"name": "profile_327b23c6",
"settings": [
{
"key": "GLFSAAMode",
"value": 0
},
{
"key": "GLNoDsoFinalizer",
"value": false
},
{
"key": "GLSingleThreaded",
"value": false
},
{
"key": "GLSyncToVblank",
"value": false
},
{
"key": "GLThreadedOptimizations",
"value": false
},
{
"key": "GLAllowFXAAUsage",
"value": false
},
{
"key": "GLGSYNCAllowed",
"value": false
}
]
}
]
}
--
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 Leo changed: What|Removed |Added Version|5.16.5 |5.15.4 --- Comment #112 from Leo --- As a workaround, you can use the command: sudo prime-select intel && sudo prime-select nvidia After this command, the system continues to use the Nvidia GPU, but without windows hanging. -- 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 Leo changed: What|Removed |Added Version|5.15.4 |5.16.5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411463] Copy Paste layer group to another document, group is flattened, group layers not preserved.
https://bugs.kde.org/show_bug.cgi?id=411463 --- Comment #5 from Leo --- The reason I list this as an inconsistent behaviour is this: There is: a) Layer / Copy Layer Layer / Paste Layer It works as expected. b) Edit / Copy Layer / Paste Layer This works However c) Edit / Copy Edit / Paste Flattens the the layer group. So if workflow b) successfully pastes the layer group, then workflow c) should also exhibit the same behaviour. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411463] Copy Paste layer group to another document, group is flattened, group layers not preserved.
https://bugs.kde.org/show_bug.cgi?id=411463 Leo changed: What|Removed |Added Resolution|WORKSFORME |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #4 from Leo --- I started recording the video as requested and in the process figured out the issue. Yes, I can copy the group layer. No, I can not "Edit / Paste" (ctrl V) the layer group to a new document without it being flattened. HOWEVER If, I "Layer / Paste Layer" Then pasting a layer group to a new document works. This is an inconsistent behaviour. -- 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 Leo changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #111 from Leo --- (In reply to Vlad Zahorodnii from comment #108) > You need at least 5.12.4 It doesn’t work for me( -- 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 Leo changed: What|Removed |Added CC||bloody.f...@gmail.com --- Comment #107 from Leo --- I have exactly the same problem. This happens every time I move a window from one monitor to another by dragging it to the top of the desktop so that the window becomes the maximum size. NVidia driver: 435.21 Prime Profile: NVidia Operating System: KDE neon User Edition 5.16 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.3 Kernel Version: 5.0.0-29-generic OS Type: 64-bit Processors: Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz Memory: 7,9GG -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411463] Copy Paste layer group to another document, group is flattened, group layers not preserved.
https://bugs.kde.org/show_bug.cgi?id=411463 Leo changed: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411463] New: Copy Paste layer group to another document, group is flattened, group layers not preserved.
https://bugs.kde.org/show_bug.cgi?id=411463 Bug ID: 411463 Summary: Copy Paste layer group to another document, group is flattened, group layers not preserved. Product: krita Version: 4.2.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: l...@guildmedia.net Target Milestone: --- SUMMARY Copy and paste layer group from one document to another flattens the group to a single layer. Expected result is the group layers are preserved. STEPS TO REPRODUCE 1. two documents, one with a layer group containing multiple layers 2. Copy the layer group 3. Paste to the other document OBSERVED RESULT Layer group has been flattened to a single layer. EXPECTED RESULT Expected result is the group layers are preserved. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: openSUSE Tumbleweed 20190209 KDE Plasma Version: 5.14.5 Qt Version: 5.12.0 KDE Frameworks Version: 5.54.0 Kernel Version: 4.20.6-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-2670QM CPU @ 2.20GHz Memory: 15.6 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408149] Editable Selection Outlines
https://bugs.kde.org/show_bug.cgi?id=408149 Leo changed: What|Removed |Added Summary|Selection Transformation|Editable Selection Outlines |not available via Selection | |Tool. | --- Comment #14 from Leo --- Yes, exactly the selection made, the outline, not the content. I see now that the selection outline can be moved, by hovering over it. Thus what I am suggesting is when hovering over the corners of the outline, that would enable resizing of the selection. Take a look at how GIMP handles resizing of the selection outlines. And before you say it, yes, I know, this is Krita and not GIMP. Editable selections outlines would be a very handy feature. -- 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 #12 from Leo --- Then let me propose this then. You've stated that the selection transform is a pain in the neck. I can see that you've used a best fit option to do this using vector masks. What then if only resizing of the selection is made directly available from the tool. Rotation, rounded corners ect., could still be exposed with the current context menu option. The crop tool already offers this functionality. Thus similar code already exists in Krita to mark out an area and adjust it, without having to resort to any extra mouse clicks or menu options. Surely a copy of the crop tool selection code could be repurposed for the selection tool. It's a no brainer that being able to adjust the selection on the fly improves the user experience / workflow, especially if having to work to pixel perfect selection. Consider the ease of use that is available with the crop tool, and how that also would then translate into the selection tool. It is a feature I have often wished for in Krita, and something that I have missed since switching from GIMP. It makes for great improvement in user workflow. -- 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.
[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.
[krita] [Bug 408149] New: Selection Transformation not available via Selection Tool.
https://bugs.kde.org/show_bug.cgi?id=408149 Bug ID: 408149 Summary: Selection Transformation not available via Selection Tool. Product: krita Version: 4.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: l...@guildmedia.net Target Milestone: --- SUMMARY Selection transformation should be available directly from the transform tool, and not require an extra menu option to expose it. STEPS TO REPRODUCE 1. Mark selection with selection tool 2. Menu - Edit Selection 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.
[kdelibs] [Bug 347404] crash when opening a project from mounted ftp location [KDirListerCache::slotRedirection]
https://bugs.kde.org/show_bug.cgi?id=347404 --- Comment #2 from leo venturini --- (In reply to Andrew Crouthamel from comment #1) > Dear Bug Submitter, > > This bug has been stagnant for a long time. Could you help us out and > re-test if the bug is valid in the latest version? I am setting the status > to NEEDSINFO pending your response, please change the Status back to > REPORTED when you respond. > > Thank you for helping us make KDE software even better for everyone! Hello, I'm sorry but I have upgraded to Ubuntu 18 and I did not installed Kdevelop anymore, so I can't re-test. Anyway, I stopped trying to mount (s)ftp location to use project and got used to open files directly on server from within Kdevelop. Thanks anyway for the effort and keep up the good work -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399821] New: Recent Documents - Thumbnails
https://bugs.kde.org/show_bug.cgi?id=399821 Bug ID: 399821 Summary: Recent Documents - Thumbnails Product: krita Version: 4.2.0-preview Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: l...@guildmedia.net Target Milestone: --- SUMMARY On application start up or any state where no documents are loaded, the main work space presents the Recent Documents list. It is noted that this will display a thumbnail for .kra files but not for other file types. STEPS TO REPRODUCE 1. Start Krita or close all current documents OBSERVED RESULT Recent Documents only show thumbnails for .kra files and not other file types. EXPECTED RESULT Thumbnails for all file types are displayed. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.1 KDE Frameworks Version: 5.47.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kicker] [Bug 79807] "Recent Documents": Set number of documents
https://bugs.kde.org/show_bug.cgi?id=79807 Leo changed: What|Removed |Added CC||l...@guildmedia.net Status|RESOLVED|REOPENED Resolution|UNMAINTAINED|--- --- Comment #6 from Leo --- Allow the user to configure the number of recent documents that Krita remembers. Settings / Configure Krita / General / Miscellaneous / Recent Documents Or perhaps better Settings / Configure Krita / General / Sessions / Recent Documents This would affect the file menu and the initial work space which also shows recent documents when none are loaded. This is possible in KDE applications, as the Kate editor allows the user to define the number of recent documents. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399390] New: play animation
https://bugs.kde.org/show_bug.cgi?id=399390 Bug ID: 399390 Summary: play animation Product: krita Version: 4.1.3 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: sifi...@hotmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. make frames wanted 2. to rest(support) on play 3. to look at the result(profit) OBSERVED RESULT My animation does not work, she dashes(launches) but does not move. Nevertheless I have well of frame different EXPECTED RESULT My animation works SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 4.1.3 KDE Frameworks Version: Windows 10 (x86_64) Qt Version: Windows 10 (x86_64) ADDITIONAL INFORMATION I am French, sorry for my English -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 398385] New: wi-fi connection loss while awaiking from the sleep mode
https://bugs.kde.org/show_bug.cgi?id=398385 Bug ID: 398385 Summary: wi-fi connection loss while awaiking from the sleep mode Product: plasma-nm Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: leo.wire...@gmail.com Target Milestone: --- After awaiking from the sleep mode, system doesn't make any attempts to reconnectto wi-fi. Unplugging wi-fi' USB cable and plugging it back required every time to establish lost connection. No other way to initiate the reconnection. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 397684] New: Enabling "Enhanced Media Controls" breaks Home Assistant
https://bugs.kde.org/show_bug.cgi?id=397684 Bug ID: 397684 Summary: Enabling "Enhanced Media Controls" breaks Home Assistant Product: plasma-browser-integration Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Firefox Assignee: k...@privat.broulik.de Reporter: leotheverto+kdeb...@gmail.com Target Milestone: --- When "Enhanced Media Controls" is enabled, Home Assistant fails to load and throws "TypeError: this._meta.byKey is not a function". Now I realize this may not sound like an issue on your side but interestingly enough, the LastPass extension seems to have caused the exact same problem in the past: https://github.com/home-assistant/home-assistant-polymer/issues/448 and per the referenced issues, also caused problems for other projects using web components (https://github.com/webcomponents/webcomponentsjs/issues/819, https://github.com/appreciated/vaadin-app-layout/issues/98). Now if this is really caused by the same addon behaviour then the plasma browser integration could very well also break other websites using similar polymer/webcomponent code but I haven't gotten a chance to check it yet. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 135899] Let Krita remember the last used settings or save it in the .kra-file
https://bugs.kde.org/show_bug.cgi?id=135899 Leo changed: What|Removed |Added Resolution|WONTFIX |--- CC||l...@guildmedia.net Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #3 from Leo --- You've come to the conclusion, but I as another user and former UX and UI developer agree with Jeroen jsvrp...@gmail.com Saving the current settings to the .kra will save time. Every time I load my .kra file I have to set my grids and guides all over again. I want to start my project where I left it off, not reconfigure Krita all over again before I get down to work. This is a pretty standard feature for a vast majority of software. Even a text editor such as Kate remembers where I was in the document when I last closed it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392292] Krita Crash on Startup (Open SUSE RPM package)
https://bugs.kde.org/show_bug.cgi?id=392292 --- Comment #8 from Leo --- * Which version of opensuse is this? Tumbleweed * Have you also reported this to the opensuse people? No, how do I do so? * What version of Krita is in the main repository? 4.0.0-2.1 * What version of python3, sip and python3-qt5 do you have? # python3 --version 2.7.14 Python 3.4.3 python3-qt5 5.10-1.1 | x86_64 | openSUSE:Factory python3-sip 4.19.7-1.1 | x86_64 | openSUSE:Factory -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392292] Krita Crash on Startup (Open SUSE RPM package)
https://bugs.kde.org/show_bug.cgi?id=392292 Leo changed: What|Removed |Added CC||l...@guildmedia.net --- Comment #6 from Leo --- Created attachment 111854 --> https://bugs.kde.org/attachment.cgi?id=111854&action=edit Crash on start - crash report I have now installed Krita from the main repository and still have the same crash. krita | package | 4.0.0-2.1 | x86_64 | (System Packages) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392292] Krita Crash on Startup
https://bugs.kde.org/show_bug.cgi?id=392292 --- Comment #2 from Leo --- (In reply to wolthera from comment #1) > This is only on opensuse? Does it also happen with the appimages? I can not comment about other distros. However the appimage works for me. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392295] New: Feature Request: Pop-up Palette - Canvas - Fit to Page
https://bugs.kde.org/show_bug.cgi?id=392295 Bug ID: 392295 Summary: Feature Request: Pop-up Palette - Canvas - Fit to Page Product: krita Version: 4.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: l...@guildmedia.net Target Milestone: --- Feature Request: Pop-up Palette - Canvas - Fit to Page Between the the Zoom 100% button and Zoom slider an additional Fit to Page option. OR better still Replace the 100% Zoom button with the same Zoom drop down option found at the bottom right corner of the Krita application window, which would give access to all options, Fit to Width, Fit to Page, 25%, ... 100%, ... ect. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392292] New: Krita Crash on Startup
https://bugs.kde.org/show_bug.cgi?id=392292 Bug ID: 392292 Summary: Krita Crash on Startup Product: krita Version: 4.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: l...@guildmedia.net Target Milestone: --- Created attachment 111625 --> https://bugs.kde.org/attachment.cgi?id=111625&action=edit Crash Report Loads the splash screen / window gets as far as loading main window Crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390514] Krita Crash on loading Autosaved file
https://bugs.kde.org/show_bug.cgi?id=390514 --- Comment #2 from Leo --- Created attachment 110692 --> https://bugs.kde.org/attachment.cgi?id=110692&action=edit Autosaved file that Krita crashes on. As per requested, autosaved file that Krita crashes on. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390514] New: Krita Crash on loading Autosaved file
https://bugs.kde.org/show_bug.cgi?id=390514 Bug ID: 390514 Summary: Krita Crash on loading Autosaved file Product: krita Version: 3.3.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: l...@guildmedia.net Target Milestone: --- Application: krita (3.3.3) Qt Version: 5.10.0 Frameworks Version: 5.42.0 Operating System: Linux 4.15.1-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: Load recent file An autosaved file exists for this document. Do you want to open it instead. Yes Crash The crash can be reproduced every time. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f50d154af00 (LWP 7734))] Thread 7 (Thread 0x7f50899c2700 (LWP 7749)): #0 0x7f50c7ffe82d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f50ce974c2b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7f50cfac0075 in ?? () from /usr/lib64/libQt5Widgets.so.5 #3 0x7f50ce9738d0 in ?? () from /usr/lib64/libQt5Core.so.5 #4 0x7f50c7ff8558 in start_thread () from /lib64/libpthread.so.0 #5 0x7f50ce05d72f in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f50891c1700 (LWP 7748)): #0 0x7f50c7ffe82d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f50ce974c2b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7f50ce96d64f in QSemaphore::tryAcquire(int, int) () from /usr/lib64/libQt5Core.so.5 #3 0x7f50cbe6c5d3 in KisTileDataSwapper::waitForWork (this=) at /usr/src/debug/krita-3.3.3-1.1.x86_64/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:86 #4 0x7f50cbe6c7fa in KisTileDataSwapper::run (this=0x7f50cc333a60 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder+64>) at /usr/src/debug/krita-3.3.3-1.1.x86_64/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:92 #5 0x7f50ce9738d0 in ?? () from /usr/lib64/libQt5Core.so.5 #6 0x7f50c7ff8558 in start_thread () from /lib64/libpthread.so.0 #7 0x7f50ce05d72f in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f509febe700 (LWP 7743)): #0 0x7f50c7ffe82d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f50aae485bb in ?? () from /usr/lib64/dri/r600_dri.so #2 0x7f50aae482e7 in ?? () from /usr/lib64/dri/r600_dri.so #3 0x7f50c7ff8558 in start_thread () from /lib64/libpthread.so.0 #4 0x7f50ce05d72f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f50a6ac4700 (LWP 7742)): #0 0x7f50c7ffe82d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f50aae485bb in ?? () from /usr/lib64/dri/r600_dri.so #2 0x7f50aae482e7 in ?? () from /usr/lib64/dri/r600_dri.so #3 0x7f50c7ff8558 in start_thread () from /lib64/libpthread.so.0 #4 0x7f50ce05d72f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f50b15d7700 (LWP 7740)): #0 0x7ffc14562b62 in clock_gettime () #1 0x7f50ce06b016 in clock_gettime () from /lib64/libc.so.6 #2 0x7f50ceba01a1 in ?? () from /usr/lib64/libQt5Core.so.5 #3 0x7f50ceb9ea79 in QTimerInfoList::updateCurrentTime() () from /usr/lib64/libQt5Core.so.5 #4 0x7f50ceb9eff5 in QTimerInfoList::timerWait(timespec&) () from /usr/lib64/libQt5Core.so.5 #5 0x7f50ceba053e in ?? () from /usr/lib64/libQt5Core.so.5 #6 0x7f50c66df668 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #7 0x7f50c66e003b in ?? () from /usr/lib64/libglib-2.0.so.0 #8 0x7f50c66e021c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #9 0x7f50ceba078b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #10 0x7f50ceb476ba in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #11 0x7f50ce96e8da in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #12 0x7f50c8226bd5 in ?? () from /usr/lib64/libQt5DBus.so.5 #13 0x7f50ce9738d0 in ?? () from /usr/lib64/libQt5Core.so.5 #14 0x7f50c7ff8558 in start_thread () from /lib64/libpthread.so.0 #15 0x7f50ce05d72f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f50bb486700 (LWP 7739)): #0 0x7f50ce052f8b in poll () from /lib64/libc.so.6 #1 0x7f50cc594387 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f50cc59617a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f50bddfc8d9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f50ce9738d0 in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7f50c7ff8558 in start_thread () from /lib64/libpthread.so.0 #6 0x7f50ce05d72f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f50d154af00 (LWP 7734)): [KCrash Handler] #
[krfb] [Bug 279520] KRDC view is never refreshed after initial login with desktop effects enabled
https://bugs.kde.org/show_bug.cgi?id=279520 --- Comment #2 from Leo G. --- This Behaviour has been reproduced with SUSE Leap 42.2 and KDRC 5.0 There is no possibility to get a refreshed screen. The disabling of desktop effects does not work either. In SUSE 13.2 and KDRC 5.0 it works as expected. -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 279520] KRDC view is never refreshed after initial login with desktop effects enabled
https://bugs.kde.org/show_bug.cgi?id=279520 Leo G. changed: What|Removed |Added CC||leo_grae...@web.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377781] Krita Random Crash While Idle
https://bugs.kde.org/show_bug.cgi?id=377781 --- Comment #14 from Leo --- Created attachment 105119 --> https://bugs.kde.org/attachment.cgi?id=105119&action=edit Krita crash after turning monitors back on again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377781] Krita Random Crash While Idle
https://bugs.kde.org/show_bug.cgi?id=377781 --- Comment #13 from Leo --- (In reply to Dmitry Kazakov from comment #11) > Looks like it is *not* wayland, but some problem is XCB... > > QXcbConnection: XCB error: 3 (BadWindow), sequence: 56311, resource id: > 34089088, major code: 40 (TranslateCoords), minor code: 0 > > Leo, does your computer sleeps/hibernates in the meantime? If I turn the monitors off, and then on again, even in a short time, so hence, no lock screen, this will cause Krita to crash. This occurs with the current Krita 3.1.3-beta.1 appimage. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377781] Krita Random Crash While Idle
https://bugs.kde.org/show_bug.cgi?id=377781 --- Comment #12 from Leo --- (In reply to Dmitry Kazakov from comment #11) > Looks like it is *not* wayland, but some problem is XCB... > > QXcbConnection: XCB error: 3 (BadWindow), sequence: 56311, resource id: > 34089088, major code: 40 (TranslateCoords), minor code: 0 > > Leo, does your computer sleeps/hibernates in the meantime? sleeps/hibernates no, but when it goes idle after 30min, I have the screen set to blank and lock. So when I log back in, Krita has already crashed. I am now running Krita 3.1.3-beta.1 appimage. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377781] Krita Random Crash While Idle
https://bugs.kde.org/show_bug.cgi?id=377781 --- Comment #10 from Leo --- Created attachment 104726 --> https://bugs.kde.org/attachment.cgi?id=104726&action=edit Krita output to shell This is the output from Krita to the shell, without any crash. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377781] Krita Random Crash While Idle
https://bugs.kde.org/show_bug.cgi?id=377781 --- Comment #9 from Leo --- Created attachment 104725 --> https://bugs.kde.org/attachment.cgi?id=104725&action=edit Krita output including crash This output from Krita also includes when it crashed as I reported. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377781] Krita Random Crash While Idle
https://bugs.kde.org/show_bug.cgi?id=377781 --- Comment #8 from Leo --- (In reply to Boudewijn Rempt from comment #7) > Could you also start krita from a terminal and attach all terminal output? > Especially xcb errors are interesting. (In reply to Boudewijn Rempt from comment #6) > Hm... And are you using plain X11 or Wayland + X11? What desktop > environment? And do you have a drawing tablet connected? > > > The crash happens somewhere in the xcb code, apparently we get a > window/widget that doesn't have a valid windowHandle. > > I don't have tumbleweed, just the latest leap. But I'll start krita, load > some stuff and wait a while... loginctl show-session 2 -p Type Type=x11 Desktop: KDE 5 Plasma No drawing tablet. =( I want one. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377781] Krita Random Crash While Idle
https://bugs.kde.org/show_bug.cgi?id=377781 --- Comment #5 from Leo --- (In reply to Boudewijn Rempt from comment #4) > Sure, that's fine! Yes, I can confirm a similar crash with the most current Krita appimage. In all instances, I have file/s open that I have been working on. I will leave the computer for a break, perhaps an hour or more and return to find that Krita has crashed and no longer running. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377781] Krita Random Crash While Idle
https://bugs.kde.org/show_bug.cgi?id=377781 --- Comment #3 from Leo --- (In reply to Boudewijn Rempt from comment #2) > These are the official OpenSUSE packages? Does this also happen with the > 3.1.2 appimage we release? Yes, official OpenSuse package. 3.1.2.1-2.1-x86_64 from openSUSE:Tumbleweed I am also running the appimage now to see if the same crash occurs. Give me a few days. I use Krita frequently and for long periods. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377884] New: Krita Random Crash While Idle
https://bugs.kde.org/show_bug.cgi?id=377884 Bug ID: 377884 Summary: Krita Random Crash While Idle Product: krita Version: 3.1.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: l...@guildmedia.net Target Milestone: --- Application: krita (3.1.2) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.1-2-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: Krita crahes while running idle in the background. The crash can be reproduced sometimes. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4c10652d40 (LWP 1944))] Thread 6 (Thread 0x7f4bd55b0700 (LWP 2361)): #0 0x7f4c071c29a6 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4c0dcdd7fb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0xc7b3970) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=this@entry=0xc7b35b0, mutex=mutex@entry=0xc7b35a8, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f4c0edc7652 in QFileInfoGatherer::run (this=0xc7b3598) at dialogs/qfileinfogatherer.cpp:217 #4 0x7f4c0dcdc906 in QThreadPrivate::start (arg=0xc7b3598) at thread/qthread_unix.cpp:368 #5 0x7f4c071bc537 in start_thread () from /lib64/libpthread.so.0 #6 0x7f4c0d3d004f in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f4bd5dfd700 (LWP 2355)): #0 0x7f4c071c29a6 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4c0dcdd7fb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0xb9b6090) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=mutex@entry=0xb9b6070, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f4c0dcd6806 in QSemaphore::tryAcquire (this=0xb9af6d0, n=n@entry=1, timeout=timeout@entry=-1) at thread/qsemaphore.cpp:220 #4 0x7f4c0b1fb873 in KisTileDataSwapper::waitForWork (this=this@entry=0x7f4c0b6cda60 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder+64>) at /usr/src/debug/krita-3.1.2.1/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:86 #5 0x7f4c0b1fbaaa in KisTileDataSwapper::run (this=0x7f4c0b6cda60 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder+64>) at /usr/src/debug/krita-3.1.2.1/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:92 #6 0x7f4c0dcdc906 in QThreadPrivate::start (arg=0x7f4c0b6cda60 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder+64>) at thread/qthread_unix.cpp:368 #7 0x7f4c071bc537 in start_thread () from /lib64/libpthread.so.0 #8 0x7f4c0d3d004f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f4bd65fe700 (LWP 2354)): #0 0x7f4c071c29a6 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4c0dcdd7fb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0xb9b5e20) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=this@entry=0xb9af6b8, mutex=mutex@entry=0xb9af6b0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f4c0dcd6513 in QSemaphore::acquire (this=this@entry=0x7f4c0b6cda30 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder+16>, n=n@entry=1) at thread/qsemaphore.cpp:143 #4 0x7f4c0b1e11ee in KisTileDataPooler::waitForWork (this=0x7f4c0b6cda20 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder>) at /usr/src/debug/krita-3.1.2.1/libs/image/tiles3/kis_tile_data_pooler.cc:165 #5 0x7f4c0b1e19fa in KisTileDataPooler::run (this=0x7f4c0b6cda20 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder>) at /usr/src/debug/krita-3.1.2.1/libs/image/tiles3/kis_tile_data_pooler.cc:187 #6 0x7f4c0dcdc906 in QThreadPrivate::start (arg=0x7f4c0b6cda20 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder>) at thread/qthread_unix.cpp:368 #7 0x7f4c071bc537 in start_thread () from /lib64/libpthread.so.0 #8 0x7f4c0d3d004f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f4bea29a700 (LWP 1983)): #0 0x7f4c0d3c67bd in poll () from /lib64/libc.so.6 #1 0x7f4c05915896 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f4c059159ac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f4c0df0148b in QEventDispatcherGlib::processEvents (this=0x7f4be40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f4c0deaa5ea in QEventLoop::exec (this=this@entry=0x7f4bea299cb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f4c0dcd7b03 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7f4c073eab99 in ?? () from /usr/lib64/libQt5DBus.
[krita] [Bug 377781] New: Krita Random Crash While Idle
https://bugs.kde.org/show_bug.cgi?id=377781 Bug ID: 377781 Summary: Krita Random Crash While Idle Product: krita Version: 3.1.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: l...@guildmedia.net Target Milestone: --- Application: krita (3.1.2) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.1-2-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: While not in use and sitting in the background Krita will crash. The crash can be reproduced sometimes. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcaf1eead40 (LWP 1923))] Thread 5 (Thread 0x7fcab6d4c700 (LWP 2455)): #0 0x7fcae8a5a9a6 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fcaef5757fb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0xc960a60) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=this@entry=0xc9606a0, mutex=mutex@entry=0xc960698, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fcaf065f652 in QFileInfoGatherer::run (this=0xc960688) at dialogs/qfileinfogatherer.cpp:217 #4 0x7fcaef574906 in QThreadPrivate::start (arg=0xc960688) at thread/qthread_unix.cpp:368 #5 0x7fcae8a54537 in start_thread () from /lib64/libpthread.so.0 #6 0x7fcaeec6804f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fcab754d700 (LWP 2451)): #0 0x7fcae8a5a9a6 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fcaef5757fb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0xbbadc20) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=mutex@entry=0xbbadc00, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fcaef56e806 in QSemaphore::tryAcquire (this=0xbba7260, n=n@entry=1, timeout=timeout@entry=-1) at thread/qsemaphore.cpp:220 #4 0x7fcaeca93873 in KisTileDataSwapper::waitForWork (this=this@entry=0x7fcaecf65a60 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder+64>) at /usr/src/debug/krita-3.1.2.1/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:86 #5 0x7fcaeca93aaa in KisTileDataSwapper::run (this=0x7fcaecf65a60 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder+64>) at /usr/src/debug/krita-3.1.2.1/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:92 #6 0x7fcaef574906 in QThreadPrivate::start (arg=0x7fcaecf65a60 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder+64>) at thread/qthread_unix.cpp:368 #7 0x7fcae8a54537 in start_thread () from /lib64/libpthread.so.0 #8 0x7fcaeec6804f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fcab7d4e700 (LWP 2450)): #0 0x7fcae8a5a9a6 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fcaef5757fb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0xbbad9b0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=this@entry=0xbba7248, mutex=mutex@entry=0xbba7240, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fcaef56e513 in QSemaphore::acquire (this=this@entry=0x7fcaecf65a30 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder+16>, n=n@entry=1) at thread/qsemaphore.cpp:143 #4 0x7fcaeca791ee in KisTileDataPooler::waitForWork (this=0x7fcaecf65a20 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder>) at /usr/src/debug/krita-3.1.2.1/libs/image/tiles3/kis_tile_data_pooler.cc:165 #5 0x7fcaeca799fa in KisTileDataPooler::run (this=0x7fcaecf65a20 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder>) at /usr/src/debug/krita-3.1.2.1/libs/image/tiles3/kis_tile_data_pooler.cc:187 #6 0x7fcaef574906 in QThreadPrivate::start (arg=0x7fcaecf65a20 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder>) at thread/qthread_unix.cpp:368 #7 0x7fcae8a54537 in start_thread () from /lib64/libpthread.so.0 #8 0x7fcaeec6804f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fcacbb27700 (LWP 1962)): #0 0x7fcaeec5e7bd in poll () from /lib64/libc.so.6 #1 0x7fcae71ad896 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fcae71ad9ac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fcaef79948b in QEventDispatcherGlib::processEvents (this=0x7fcac40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fcaef7425ea in QEventLoop::exec (this=this@entry=0x7fcacbb26cb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fcaef56fb03 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7fcae8c82b99 in ?? () from /usr/lib
[dolphin] [Bug 368367] Dolphin Crashes on right-click for list-menu options
https://bugs.kde.org/show_bug.cgi?id=368367 Leo Mauro changed: What|Removed |Added CC||lma...@usb.ve -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364573] New: Unreadable text in application launcher
https://bugs.kde.org/show_bug.cgi?id=364573 Bug ID: 364573 Summary: Unreadable text in application launcher Product: plasmashell Version: 5.6.5 Platform: Slackware Packages URL: http://i.imgur.com/rofh22W.png OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: j...@openmailbox.org CC: plasma-b...@kde.org Text in application launcher is unreadable with proprietary NVIDIA drivers 361.45. Mostly just affects the categories at the bottom, but I have seen it happen to program descriptions too. Doesn't affect function. Reproducible: Always Steps to Reproduce: 1. Open the application launcher. Actual Results: Doesn't show text properly, showing block silhouette instead. Expected Results: Text. Intel i5 4690k MSI GTX 970 8gb RAM Slackware-current 64-bit KDE 5.6.5 packages from Alien Bob Qt 5.6.1 Kernel 4.4.13 Proprietary NVIDIA drivers 361.45 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 344567] Cannot create a new session
https://bugs.kde.org/show_bug.cgi?id=344567 Leo Davis changed: What|Removed |Added CC||lda...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
