[krfb] [Bug 408405] krfb 19.4.0 bug report
https://bugs.kde.org/show_bug.cgi?id=408405 nl.smart changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 408862] Ktouch 19.04.2-1 graphic bug with the results
https://bugs.kde.org/show_bug.cgi?id=408862 --- Comment #5 from nl.smart --- Created attachment 121600 --> https://bugs.kde.org/attachment.cgi?id=121600=edit Ktouch 19.04.3 graphic bug_resolved_01 Ktouch 19.04.3 graphic bug_resolved_01 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409374] You can not enable sub-pixel rendering other than vendor default because system settings will put a check mark in the box to block anti-aliasing and make fonts unreadable
https://bugs.kde.org/show_bug.cgi?id=409374 Yaohan Chen changed: What|Removed |Added CC||yaohan.c...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 409924] Kate/Kwrite display invalid characters instead of normal whitespace (possible UTF-16 issue?)
https://bugs.kde.org/show_bug.cgi?id=409924 Tom Seewald changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #4 from Tom Seewald --- (In reply to Christoph Feck from comment #3) > What encoding did you set in Kate? The file is an UTF-16 file, but the > default encoding in Kate is UTF-8. Ah that explains it, I thought it would default to UTF-16 or switch to that when it encounters a UTF-16 file. I also must admit I didn't know there was a way to change this in the settings menu. This sounds like expected behavior though, so this isn't a bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395476] The minimum window size of System Settings is too big for a 1366x768 screen
https://bugs.kde.org/show_bug.cgi?id=395476 Christoph Feck changed: What|Removed |Added CC||marcantoine_manningham@outl ||ook.com --- Comment #12 from Christoph Feck --- *** Bug 409903 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409903] The settings app have a minimum size.
https://bugs.kde.org/show_bug.cgi?id=409903 Christoph Feck changed: What|Removed |Added Resolution|INTENTIONAL |DUPLICATE --- Comment #5 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 395476 *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 409924] Kate/Kwrite display invalid characters instead of normal whitespace (possible UTF-16 issue?)
https://bugs.kde.org/show_bug.cgi?id=409924 --- Comment #3 from Christoph Feck --- What encoding did you set in Kate? The file is an UTF-16 file, but the default encoding in Kate is UTF-8. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409931] Acer Switch Alpha 12 Stylus lift-off problem
https://bugs.kde.org/show_bug.cgi?id=409931 zac changed: What|Removed |Added Alias||entrain -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409931] New: Acer Switch Alpha 12 Stylus lift-off problem
https://bugs.kde.org/show_bug.cgi?id=409931 Bug ID: 409931 Summary: Acer Switch Alpha 12 Stylus lift-off problem Product: krita Version: 4.2.3 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: grave Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: doin.sw...@gmail.com Target Milestone: --- SUMMARY Similar to that of other reported problems. Let's say there are three states the stylus is in: 1. completely inactive. away from the screen, not being registered at all. 2. registered but not active. near enough to the screen to be picked up, moving the cursor around, but not touching (not clicking, drawing, etc) 3. active. drawing, clicking, pressure being applied etc. if i go to draw a line, it works fine (1->2->3). lets say after this i raise the stylus away, but not far away (3->2), to quickly begin another line (2->3), Krita doesnt respond with drawing a line- the cursor is just moved around. 1->2->3 must occur ever single time a line is to be drawn EXPECTED RESULT being able to go from 1->2 (works in 4.1) SOFTWARE/OS VERSIONS Windows: 10 64x macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION it is impossible to use like this, i have been staying at 4.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406548] [Wayland] Kwin always hangs when I open kdenlive or it hangs randomly when I open other windows
https://bugs.kde.org/show_bug.cgi?id=406548 Patrick Silva changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #9 from Patrick Silva --- This problem is no longer hapening on my systems (Arch running Plasma 5.16.3 and Neon unstable edition). -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 409930] New: Please automatically link to clear mentions of a given ticket ("ticket #12345")
https://bugs.kde.org/show_bug.cgi?id=409930
Bug ID: 409930
Summary: Please automatically link to clear mentions of a given
ticket ("ticket #12345")
Product: bugs.kde.org
Version: unspecified
Platform: Other
URL: https://bugs.kde.org/show_bug.cgi?id=409913#c1
OS: All
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: sysad...@kde.org
Reporter: chea...@gmail.com
CC: she...@kde.org
Target Milestone: ---
It would be very handy if, when a description or comment referred to a ticket
using unambiguous phrasing such as "ticket #123456" or "issue #123456", that
this text be automatically made a link to the ticket mentioned
(https://bugs.kde.org/show_bug.cgi?id=123456).
This already works for comments, as can be seen in ticket #409913's comment #1,
but not for tickets, as that same comment shows.
I put this ticket in the "general" component, but I suppose nothing prevents
addressing this with a code customization... please feel free to change the
component as you wish.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 407747] Plasmashell constantly crashing - segmentation fault
https://bugs.kde.org/show_bug.cgi?id=407747 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409427] Folder View widget can not drop files into folders on default settings
https://bugs.kde.org/show_bug.cgi?id=409427 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408857] my krita is not saving
https://bugs.kde.org/show_bug.cgi?id=408857 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408886] It do not open the pdf files
https://bugs.kde.org/show_bug.cgi?id=408886 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408624] When doing panel widget adds or removes, I have had sporadic but repeated crashes.
https://bugs.kde.org/show_bug.cgi?id=408624 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 409929] New: Ticket description templates has stray "KDE Plasma" string
https://bugs.kde.org/show_bug.cgi?id=409929 Bug ID: 409929 Summary: Ticket description templates has stray "KDE Plasma" string Product: bugs.kde.org Version: unspecified Platform: Other URL: https://bugs.kde.org/enter_bug.cgi?product=bugs.kde.or g OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sysad...@kde.org Reporter: chea...@gmail.com CC: she...@kde.org Target Milestone: --- The template for ticket descriptions includes a "SOFTWARE/OS VERSIONS" with several lines meant to collect information on the reporter's software versions. I left that template untouched at the end of this field. Understandably, this section includes a line about KDE Plasma, but there is also a "Linux/KDE Plasma: " line, which is presumably intended to query the Linux version, but which seems to contain a stray occurrence of "KDE Plasma", unless I'm missing something. SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409436] Crashes all the time as I edit files, and it doesn't seem to have a single cause.
https://bugs.kde.org/show_bug.cgi?id=409436 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 401927] Unable to add new investment
https://bugs.kde.org/show_bug.cgi?id=401927 --- Comment #7 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 396893] drkonqi does not find kdbgwin located in the same directory
https://bugs.kde.org/show_bug.cgi?id=396893 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 385925] Plasma Wayland: DrKonqi does not show up on crashes
https://bugs.kde.org/show_bug.cgi?id=385925 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 400464] On startup a foreign image is loaded to the screen (the image is actually an output image from qgis). Kmymoney operations seem to remain, but are unuseable as any information
https://bugs.kde.org/show_bug.cgi?id=400464 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 409424] Dolphin crashes continuously during coping file to External Harddisk and showes no icon for external drive
https://bugs.kde.org/show_bug.cgi?id=409424 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407484] Apps on primary screen maximising to dimensions of secondary screen (not the same size)
https://bugs.kde.org/show_bug.cgi?id=407484 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408739] melt crash exporting video in KDE neon
https://bugs.kde.org/show_bug.cgi?id=408739 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 362042] Bug report option offers itself after boot, asking wallet code
https://bugs.kde.org/show_bug.cgi?id=362042 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 356694] drkonqi causes the freeze of the entire system when Konsole, Kate or Systemsettings try to start.
https://bugs.kde.org/show_bug.cgi?id=356694 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] KDE application forgot their initial size after maximizing and closing them.
https://bugs.kde.org/show_bug.cgi?id=409919 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 409925] Remove or hide old components or application of bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=409925 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408036] Plastik doesn't unset resize borders for maximized clients
https://bugs.kde.org/show_bug.cgi?id=408036 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408035] Plastik decoration theme doesn't react to border size changes
https://bugs.kde.org/show_bug.cgi?id=408035 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 408037] Discover checks for updates before installing local package
https://bugs.kde.org/show_bug.cgi?id=408037 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408049] Touch activation on touchscreen for Folder View items almost never works (does work for Desktop view and for Folder View with touchpad )
https://bugs.kde.org/show_bug.cgi?id=408049 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 240086] The guided new bug report form is not suitable for feature requests, especially the "steps to reproduce" part
https://bugs.kde.org/show_bug.cgi?id=240086 Filipus Klutiero changed: What|Removed |Added CC||chea...@gmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #6 from Filipus Klutiero --- Thanks for reporting uetsah, Can you indicate the URL you use to report? I am seeing the Severity field above the description, but changing it does not affect the description in any case, so I am confirming this anyway. There are issues with interface text too - for one thing, the browser title is "Enter Bug". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408051] With touch, always activate items on single-click
https://bugs.kde.org/show_bug.cgi?id=408051 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] KDE application forgot their initial size after maximizing and closing them.
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #1 from Martin Flöser --- Restoring the size is the task of the applications. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 409928] New: Reversing a clip changes in/out points [incorrectly]
https://bugs.kde.org/show_bug.cgi?id=409928 Bug ID: 409928 Summary: Reversing a clip changes in/out points [incorrectly] Product: kdenlive Version: 19.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: kdeb...@nancyandthom.us Target Milestone: --- SUMMARY When reversing a clip, the [new] clip has a completely different range. STEPS TO REPRODUCE 1. Create a project 2. Add a clip 3. Insert clip in timeline; set in/out points to a portion of the clip that is not symmetric about the middle of the clip. 4. Reverse the clip 5. Playback OBSERVED RESULT Playback plays the clip in reverse, but between two completely different frames than the in/out points established in step 3. EXPECTED RESULT Clip playback is reversed between selected frames (in/out points). SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: appimage KDE Frameworks Version: appimage Qt Version: appimage ADDITIONAL INFORMATION It *appears* that the in/out points for the reversed clip are not being calculated correctly. I have not done the math to verify this, but what *seems* to be happening is: Clip has range of frames 0 to 99. Insert clip into timeline; set in point to frame 11 and out point to frame 25. Reverse clip. Reversed clip now has in point at frame 11 FROM THE END and out point at frame 25 FROM THE END. That is, the reversed clip plays from frame (99 - 11) through frame (99 - 25). In reverse, as expected. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 313424] Bugzilla forms not clear
https://bugs.kde.org/show_bug.cgi?id=313424 Filipus Klutiero changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #18 from Filipus Klutiero --- Reporter, you described several issues in this ticket. You described issues indicating the product affected, and an issue identifying the version affected. Thank you for reporting these, but doing that in a single ticket makes your requests harder to understand and can cause confusion. In the future, please open different tickets to report different issues (this ticket should have been at least 2). VERSION IDENTIFICATION Are you still affected by the version identification issue? If so, please file a new ticket specifically on this issue, indicating the operating system which you use. Please also attach a screenshot of the problematic screen; I'm afraid the "Desktop" screenshot you attached is not a screenshot of the right screen (it basically only shows a picture of a river). PRODUCT INDICATION The "drill-down" aspect is under discussion in ticket #360400. If you have specific advice on that aspect, please provide it there. The clarity aspect is more complicated. You may open a new ticket asking product descriptions to be clarified, but do not be surprised if someone requests examples. And if you provide examples, do not be surprised if the ticket is marked as resolved as soon as these examples are solved. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408115] Trash can on desktop created using a Desktop file rather than the Trashcan widget shows inappropriate context menu
https://bugs.kde.org/show_bug.cgi?id=408115 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 409927] New: "Extract Frame" extracts the wrong frame
https://bugs.kde.org/show_bug.cgi?id=409927 Bug ID: 409927 Summary: "Extract Frame" extracts the wrong frame Product: kdenlive Version: 19.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: kdeb...@nancyandthom.us Target Milestone: --- SUMMARY Extracting a frame from a clip in the clip monitor -- either "Extract Frame..." or "Extract Frame to Project..." -- extracts the wrong frame. Especially towards the end of long clips. STEPS TO REPRODUCE 1. Create a project (test project was 1280x720, 30 fps) 2. Add clip (test clip was 20:00:00 or so; 30.038 fps) 3. Select clip. 4. In clip monitor, navigate near end of clip. Note frame image. 5. Extract frame OBSERVED RESULT Extracted frame is *not* the frame pictured in the clip monitor. EXPECTED RESULT Extracted frame is the frame pictured in the clip monitor. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: applimage KDE Frameworks Version: appimage Qt Version: appimage ADDITIONAL INFORMATION This *may* be related to the difference in frame rate between the project and the source clip. Or it may not: transcoding the source clip to 30 fps still exhibits this behavior -- but not as severely (the extracted frame is "closer" to the frame pictured in the clip monitor; but still wrong). This is *not* the same as bug 384538. This is not using a proxy clip. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 409926] New: Image files with a colon in the filename are "invalid"
https://bugs.kde.org/show_bug.cgi?id=409926 Bug ID: 409926 Summary: Image files with a colon in the filename are "invalid" Product: kdenlive Version: 19.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: kdeb...@nancyandthom.us Target Milestone: --- SUMMARY Image files with a colon in the filename are reported as "invalid" in the clip monitor when the project is [re]opened. STEPS TO REPRODUCE 1. Create a project (test project was 1280x720, 30 fps) 2. Import an image with a colon in the filename. It will seem to work. 3. Import an image without a colon in the filename (using a copy of the same clip from step 2 is illustrative). It will seem to work. 4. Save the project. 5. Close the project (by closing kdenlive or opening a different project) 6. Open the test project. You can insert the clips into the timeline. Or not. Sometimes kdenlive will crash when trying to open the test project (especially after several open/add-images/save/close/open-another/close/open-test cycles) OBSERVED RESULT The image with a colon in its name is "invalid" in the clip viewer. If you added it to the timeline, it *may* appear distorted there. The image without a colon in its name works as expected. EXPECTED RESULT All imported clips appear, without distortion, in every use. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: appimage KDE Frameworks Version: appimage Qt Version: appimage ADDITIONAL INFORMATION PopOs 18.04 (Ubuntu derivative) running 19.04.3 appimage This *may* be related to bug 377131 -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 313424] Bugzilla forms not clear
https://bugs.kde.org/show_bug.cgi?id=313424 --- Comment #17 from Filipus Klutiero --- (In reply to Jekyll Wu from comment #7) > (In reply to comment #6) > > There are relatively few people in the world who understand the odd names > > for items in the list on the bug reporting web page. The descriptions > > understandable to only the insider and do not include all the surrounding > > parts of the component. > > No, bugs.kde.org receives around 350~400 reports per week, and most of them > are created by users, not developers. That possibly proves that maybe 200 people report to bugs.kde.org every week, which is probably less than the number of people who maintain(ed) KDE products. And anyone who reports *is* a developer. I believe the description of some products is good, but I would easily agree with the reporter if he merely claimed that many (maybe most) are understandable only to few people. Just in the screenshot he provided, we see Akonadi described as a "PIM framework". I don't think 1% of computer users could define PIM, and most professional software developers would say they've never even seen that acronym. I think most of the descriptions can be improved, but in reality, even if we were to craft the best 1-line description for each item, it would still be hard for someone who's used KDE for years without getting involved in development to understand what a large part of these products are about. Ultimately, this comes down to the fact that, to put it simply, "KDE is complicated". We could still do a lot better if we wanted, linking each product to its homepage. Reporter, on which URL did you take the "Web Site screen" (screen.png) screenshot? -- You are receiving this mail because: You are watching all bug changes.
[kde-gtk-config] [Bug 408172] Crash when closing system settings
https://bugs.kde.org/show_bug.cgi?id=408172 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- maybe duplicate of bug 405405 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409460] Canvas pan & zoom frame 'spacing' inconsistent
https://bugs.kde.org/show_bug.cgi?id=409460 --- Comment #50 from Aaron Lavarnway --- Awesome, I'll follow those as well. Thank you for all the help! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409894] Rotation Shift+Space action drifts when rotating
https://bugs.kde.org/show_bug.cgi?id=409894 Aaron Lavarnway changed: What|Removed |Added CC||i...@ralek.art -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409892] Zooming with ctrl+space+drag is not smooth
https://bugs.kde.org/show_bug.cgi?id=409892 Aaron Lavarnway changed: What|Removed |Added CC||i...@ralek.art -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 406020] Error message when kate shows the open file dialog after I open a file located in samba share
https://bugs.kde.org/show_bug.cgi?id=406020 --- Comment #10 from Patrick Silva --- bug 408174 seems related -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408180] Support additional org.freedesktop.Notifications capabilities
https://bugs.kde.org/show_bug.cgi?id=408180 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 409925] New: Remove or hide old components or application of bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=409925 Bug ID: 409925 Summary: Remove or hide old components or application of bugs.kde.org Product: bugs.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: product/component changes Assignee: sysad...@kde.org Reporter: marcantoine_manning...@outlook.com CC: christo...@krop.fr Target Milestone: --- SUMMARY It would be great if old and abandoned component were removed from the list of all component show. It would improve the usability of the bug tracking. STEPS TO REPRODUCE 1. Go to bugs.kde.org 2. Click on the New link OBSERVED RESULT The list of app and component contains old and unmaintained app and component. EXPECTED RESULT The list of app and component contains only maintained app and component 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.
[bugs.kde.org] [Bug 313424] Bugzilla forms not clear
https://bugs.kde.org/show_bug.cgi?id=313424 Filipus Klutiero changed: What|Removed |Added CC||chea...@gmail.com --- Comment #16 from Filipus Klutiero --- (In reply to tech from comment #6) > [...] > > Again, there should be a drill-down method that accepts the actual user name > for items on the desktop. If it has to do with a widget on the panel, one > should type widget, then panel and be given the correct category. I am sorry but can you clarify that last sentence? Provide an example? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 409924] Kate/Kwrite display invalid characters instead of normal whitespace (possible UTF-16 issue?)
https://bugs.kde.org/show_bug.cgi?id=409924 --- Comment #2 from Tom Seewald --- Created attachment 121599 --> https://bugs.kde.org/attachment.cgi?id=121599=edit Kwrite incorrectly displaying the file's contents -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 409924] Kate/Kwrite display invalid characters instead of normal whitespace (possible UTF-16 issue?)
https://bugs.kde.org/show_bug.cgi?id=409924 --- Comment #1 from Tom Seewald --- Created attachment 121598 --> https://bugs.kde.org/attachment.cgi?id=121598=edit Gnome's text editor correctly displaying the file's contents -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 409924] New: Kate/Kwrite display invalid characters instead of normal whitespace (possible UTF-16 issue?)
https://bugs.kde.org/show_bug.cgi?id=409924 Bug ID: 409924 Summary: Kate/Kwrite display invalid characters instead of normal whitespace (possible UTF-16 issue?) Product: kate Version: 19.04.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: encoding Assignee: kwrite-bugs-n...@kde.org Reporter: tseew...@gmail.com Target Milestone: --- Created attachment 121597 --> https://bugs.kde.org/attachment.cgi?id=121597=edit Text file that exhibits the problem SUMMARY Kate and Kwrite seemingly display invalid characters which makes the text file extremely hard to read. See the attached example.txt file that displays this problem. STEPS TO REPRODUCE 1. Redirect PowerShell output on a Windows machine to a text file. 2. Transfer the text file to a machine that has Plasma installed. 3. Open the text file using kwrite or kate. OBSERVED RESULT Invalid characters are displayed between every character (see bad-screenshot). EXPECTED RESULT No invalid characters are displayed (see good-screenshot). I can successfully view these files in Fedora using gnome's text editor, and visual studio code. SOFTWARE/OS VERSIONS I am currently running Fedora 30's KDE Spin. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 409886] K3b burning tools not burn any CD / DVD. It shown blank after burn
https://bugs.kde.org/show_bug.cgi?id=409886 Matthew Dawson changed: What|Removed |Added Assignee|matt...@mjdsystems.ca |k...@kde.org Component|general |Burning/Hardware Product|frameworks-kconfig |k3b CC||mich...@jabster.pl, ||tr...@kde.org --- Comment #1 from Matthew Dawson --- Re-assigning to the K3b product so this issue can be investigated. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 376697] Possible Duplicates should have the option to show only Bugs from the selected product
https://bugs.kde.org/show_bug.cgi?id=376697 Filipus Klutiero changed: What|Removed |Added CC||chea...@gmail.com --- Comment #2 from Filipus Klutiero --- (In reply to Simone Gaiarin from comment #1) > Showing the bugs from all products makes sense sometimes, because the user > may not know what is the product related to the bug he is submitting. > Example: a bug in the "Open with" dialog should be submitted to > frameworks-kio. This is not straightforward, so displaying bug from all the > products may be useful. Users have to indicate the product, so if they don't know, they're not supposed to be filing a ticket... although ticket #340420 comment #1 claims the kde pseudo-product can be used when users don't know. > [...] > > For me, at least, the products corresponding to the displayed possible > duplicated bugs should be displayed in the table by default. In this way, > especially in the second example, one can instantly see if the bugs are > related to the product he thinks the bug is related to. On that, I have to agree. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 213244] The application selection web page interface needs work.
https://bugs.kde.org/show_bug.cgi?id=213244 Filipus Klutiero changed: What|Removed |Added Status|REPORTED|RESOLVED CC||chea...@gmail.com Resolution|--- |DUPLICATE --- Comment #3 from Filipus Klutiero --- Thank you for reporting Taurnil, I agree this can be improved much, although I am not sure modules are the right way to go, and they've changed a lot since you filed this report. An interesting discussion has started in ticket #360400. Even though your ticket predates #360400, as #360400's scope is clear, I am marking this one as a duplicate of ticket #360400, but feel free to open a new ticket if you had other ideas, and don't hesitate if you have something to add on #360400. *** This bug has been marked as a duplicate of bug 360400 *** -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 360400] Very confusing and hard to navigate long list of products when searching or filing/creating tickets
https://bugs.kde.org/show_bug.cgi?id=360400 Filipus Klutiero changed: What|Removed |Added CC||taurnil.oro...@gmail.com --- Comment #5 from Filipus Klutiero --- *** Bug 213244 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 360400] Very confusing and hard to navigate long list of products when searching or filing/creating tickets
https://bugs.kde.org/show_bug.cgi?id=360400 Filipus Klutiero changed: What|Removed |Added Summary|Very confusing list of |Very confusing and hard to |products in search |navigate long list of ||products when searching or ||filing/creating tickets --- Comment #4 from Filipus Klutiero --- hvm, I hope you don't mind, but as this issue affects both ticket search and creation, and as you mentioned creation in your original Description, I am re-titling this ticket so the scope clearly includes filing tickets. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 302648] Issue tracker: visually distinguish developers
https://bugs.kde.org/show_bug.cgi?id=302648 Filipus Klutiero changed: What|Removed |Added Summary|mark developer names in |Issue tracker: visually |bugzilla|distinguish developers CC||chea...@gmail.com --- Comment #5 from Filipus Klutiero --- What would you define as a developer? Is there a list of all developers somewhere? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408321] Feature Request: Add Entry in Context Menu to Rename Drives
https://bugs.kde.org/show_bug.cgi?id=408321 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 365746] Operating System Menu should list "GNU+Linux", not "Linux"
https://bugs.kde.org/show_bug.cgi?id=365746
Filipus Klutiero changed:
What|Removed |Added
OS|Linux |FreeBSD
CC||chea...@gmail.com
--- Comment #1 from Filipus Klutiero ---
Unlike Linux, GNU is a project, not a product. There is probably no operating
system which is composed of all GNU products. For that reason, calling any
operating system "GNU+anything" would be misleading. Furthermore, if such a
system existed, it would include GNU Hurd, and the name "GNU+Linux" would
therefore be incorrect.
At the time where the page you refer to was written, the "GNU+Linux operating
system", if there is such a thing, was a lot younger and nowhere near as
complete as it is today. I must say I did not use it at that time, but from my
understanding, its development must have been a lot more centralized
("cathedral-like") than it is today ("bazaar-like"). In the current state of
that operating system, a much higher part of its pieces are not from the GNU
project. I arguably use that operating system, in the form of Kubuntu 19.04,
with Mozilla Firefox and Mozilla Thunderbird. Stating that my system's userland
was created by GNU would be exaggeratedly simplified. Very roughly, the
userland comes as much from the GNU, KDE, X.org, Qt, Mozilla and LibreOffice
projects. And there is probably more that doesn't come from any of these
projects than from GNU.
If there is such a thing as that "GNU+Linux operating system", "Linux" is a bad
name for it, and "GNU+Linux" is about equally bad. Where I do agree with you is
that users should not have to select "Linux" in that drop-down. The 2 Platform
dropdowns are currently a mess. Options in both are in large part duplicated
(for example, "MS Windows") in both. If I select PCLinuxOS in the first, I
shouldn't have to select "Linux" in the second. These fields are in a bad shape
and basically need to be re-designed from scratch. First of all, should they be
kept? Bugzilla seems to assume an issue affects a single platform, but that is
rarely the case. One option is to give up on these fields entirely and just
rely on the information in the Description and comments. The report template
already includes:
> SOFTWARE/OS VERSIONS
> Windows:
> macOS:
> Linux/KDE Plasma:
--
You are receiving this mail because:
You are watching all bug changes.
[calligrasheets] [Bug 409923] New: Visual glitch after undoing Merge Cells operation
https://bugs.kde.org/show_bug.cgi?id=409923 Bug ID: 409923 Summary: Visual glitch after undoing Merge Cells operation Product: calligrasheets Version: 3.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: calligra-sheets-bugs-n...@kde.org Reporter: aspotas...@gmail.com Target Milestone: --- Created attachment 121596 --> https://bugs.kde.org/attachment.cgi?id=121596=edit screenshot SUMMARY Visual glitch after undoing Merge Cells operation. STEPS TO REPRODUCE 1. Create empty document in calligra sheets. 2. Enter "123" in cell A1 3. Enter "abc" in cell A2 4. Select both cells A1-A2. 5. In panel "Cell formatting", click "merge cells into one ...". A1-A2 will become a single cell. 6. Undo "Merge Cells" operation (e.g. by pressing Ctrl+Z) OBSERVED RESULT You can see that A1 is empty, A2 contains "abc123". EXPECTED RESULT A1 contains "123", A2 contains "abc", exactly like it was before merging. SOFTWARE/OS VERSIONS Operating System: Fedora 30 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 Kernel Version: 5.1.16-300.fc30.x86_64 OS Type: 64-bit Processors: 2 × Intel® Celeron® CPU B800 @ 1.50GHz Memory: 3,8 ГиБ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408465] Have the option to capture mouse on corners when having multiple monitors
https://bugs.kde.org/show_bug.cgi?id=408465 Patrick Silva changed: What|Removed |Added CC||leftcr...@tutanota.com --- Comment #2 from Patrick Silva --- *** Bug 408390 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409917] Elliptical selection - after applying several times becomes irregular
https://bugs.kde.org/show_bug.cgi?id=409917 vanyossi changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||ghe...@gmail.com --- Comment #1 from vanyossi --- I've never seen that happening ever. On each new selection there is no change in the previous displayed selection. On a second investigation: This behaviour seems to be expected on small images since I could reproduce it easily on krita 3.3.3, however for it to happen the image size has to be extremely small (on my tests, 50 x 50). The selection display quality does not affect the effective selected area. Could you tell me How big is your image size in pixels? (width x height). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408390] Sticky screen edges for side docks in multihead context. (Unity feature)
https://bugs.kde.org/show_bug.cgi?id=408390 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 408465 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409901] configuration for switching desktops has "disappeared"
https://bugs.kde.org/show_bug.cgi?id=409901 --- Comment #5 from roger herz-fischler --- I did not notice Kai Uwe Broulik's comment until I submitted my own "discovery". Thank you. roger h-f -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409901] configuration for switching desktops has "disappeared"
https://bugs.kde.org/show_bug.cgi?id=409901 --- Comment #4 from roger herz-fischler --- Created attachment 121595 --> https://bugs.kde.org/attachment.cgi?id=121595=edit I found where to configure switching -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409922] New: Lag on tools
https://bugs.kde.org/show_bug.cgi?id=409922 Bug ID: 409922 Summary: Lag on tools Product: krita Version: 4.2.3 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Brush Engine/Bristle Assignee: krita-bugs-n...@kde.org Reporter: jcoke1...@gmail.com Target Milestone: --- SUMMARY Pencil tool has small lag before it starts moving. Every time its activated. STEPS TO REPRODUCE 1.Update to 4.2.3 OBSERVED RESULT 2. I've checked task manager to make sure nothing was using an absurd amount of recourse's, even restarted computer. 3. Rolled back update and everything works fine EXPECTED RESULT No lag SOFTWARE/OS VERSIONS Windows: current win10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Steam version -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 340420] Make it easier to file issue reports
https://bugs.kde.org/show_bug.cgi?id=340420 --- Comment #12 from Filipus Klutiero --- (In reply to Christoph Feck from comment #1) > Regarding new users, I do not see this as a problem. If someone picks the > wrong product, we can reassign it. You wouldn't be wrong to call me a perfectionist, but if I start filing a report and find myself unable to answer a question which mandates an answer, I will give up, not give an answer in which I'm not confident. I see 3 possible consequences of the current status: 1. Reporters waste excessive time determining the product, and may decide not to report further issues for that reason. 2. Reporters give up reporting the problem. 3. Reporters select the wrong product. If it takes time for developers to correct this, that means a duplicate ticket may be opened, again wasting reporter time. Or worst, it will take more time for product maintainers to be notified of the issue, which may be fixed late. > Additionally, many users simply use "kde" > as the product, because they do not exactly know where the issue is. This > has served us well in the last years. Thanks for bringing up this point. But I reported my first issue on this site in 2006, and I never knew that it was fine to select the kde product when the precise product is unknown. If you are saying that is the case: 1. It is not clear that the kde product is intended to be used this way. The product description is simply "General KDE Software problems". Does that mean problems which affect several applications, such as Qt issues? Is this intended for requests for new products? This is entirely unclear. 2. If it is fine to use the kde product this way, either: 1. Such usage should be split to a dedicated product, so triagers only have to monitor tickets in that product. 2. Or, if that's its only usage, it should be renamed to something clearer, like "unknown". 3. The duplicate finder should be taught that when filing an issue in that "unknown" pseudo-product, all products should be searched. Conversely, when filing an issue in a specific product, the "unknown" pseudo-product should be searched. 4. The pseudo-product to select when a reporter has too much difficulty identifying the precise product should be a lot more clear. It should be mentioned at the top, or even better - there should be an "I am not sure" button which allows to skip. > Not requiring the user to pick any product would increase our workload. That depends on who "we" are, and which work is being discussed. If "we" are KDE users: 1. Requiring to indicate the product largely increases the reporting workload for reporters. I have used KDE for over 15 years. I hit an issue after switching to Kubuntu 19.04 and to report it to KDE, even though I am a veteran user who spent several person-months developing KDE and helping KDE users, and even though I am a senior software developer who somewhat knows C++, I just had to spend over 1 person-day of work, just to figure out that the symptom actually resulted from 3 root issues, and locating each of these issues. Even with my level of knowledge way above the average reporter's, I am not convinced it was optimal for me to be the one doing all this work. 2. If reporters decide not to report, users will spend more time finding workarounds for the issues they hit. 3. If reporters decide not to report, resolution is delayed and users will waste more time dealing with the issues they hit. 4. If reporters refrain from reporting to KDE: 1. they will report to redistributors, which means reporters waste time filing duplicate issues. 2. potential users spend more time and/or have more difficulty evaluating the quality of KDE or specific KDE products before they pick KDE or choose between KDE products, as they do not have a complete database of issues to query. 5. If reporters decide to report on alternative channels, such as mailing lists, these channels are needlessly "polluted", which increases the time wasted by developers. 6. If reporters select the wrong product, as indicated above, other reporters may waste time filing a duplicate, and users may waste time with issues fixed later. > Btw, I use "https://bugs.kde.org/enter_bug.cgi?product=productname; to > report bugs. This way, I do not have to pick it from a large list. I am not sure what your point is. To use that, you need to know the "productname" (in fact, its codename in this ITS). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408507] notification does not allow copying via shortcut
https://bugs.kde.org/show_bug.cgi?id=408507 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 409921] New: Elisa can't find or open music in folders with # (number sign) in them
https://bugs.kde.org/show_bug.cgi?id=409921 Bug ID: 409921 Summary: Elisa can't find or open music in folders with # (number sign) in them Product: elisa Version: 0.4.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: pizzad...@linuxmail.org Target Milestone: --- SUMMARY Elisa can't find or open music in folders with # (number sign) in them. I have an album called "Mustard Plug - Yellow #5". I had to rename it to "Mustard Plug - Yellow Number 5" in order for Elisa to recognize it. If I tried to go to it manually in the files section, it said it could not find "Mustard Plug - Yellow" STEPS TO REPRODUCE 1. Create folder in music directory called "Blah Blah #1" 2. Notice that Elisa can't navigate to it in files section SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 30 KDE with mkyral/plasma-unstable copr repo KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 408551] Simple drawing/annotation tools
https://bugs.kde.org/show_bug.cgi?id=408551 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408573] Thumbnails of splash screens are missing in "System Settings > Startup and shutdown > Boot Splash"
https://bugs.kde.org/show_bug.cgi?id=408573 Patrick Silva changed: What|Removed |Added Product|ksplash |systemsettings Component|general |kcm_plymouth Assignee|unassigned-b...@kde.org |plasma-b...@kde.org CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409920] New: Plasma closed when changing twinkle(phone) systray from "auto" to "show"
https://bugs.kde.org/show_bug.cgi?id=409920 Bug ID: 409920 Summary: Plasma closed when changing twinkle(phone) systray from "auto" to "show" Product: plasmashell Version: 5.12.8 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: reisenwe...@web.de CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.8) Qt Version: 5.9.4 Frameworks Version: 5.45.0 Operating System: Linux 4.12.14-lp150.12.64-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: - What I was doing when the application crashed: RMB-click on systray popup-arrow - select "systrem tray settings". Select "Entries". In menu spot "twinkle" application and change setting from "auto" to "show" -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcac41cd1c0 (LWP 2872))] Thread 11 (Thread 0x7fc9cea00700 (LWP 27081)): #0 0x7fcab357d444 in pa_mainloop_dispatch () at /usr/lib64/libpulse.so.0 #1 0x7fcab357d88e in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #2 0x7fcab357d910 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #3 0x7fcab358b779 in () at /usr/lib64/libpulse.so.0 #4 0x7fcab2d14438 in () at /usr/lib64/pulseaudio/libpulsecommon-11.1.so #5 0x7fcabce5b569 in start_thread () at /lib64/libpthread.so.0 #6 0x7fcabd5ac85f in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7fc9a6ffd700 (LWP 27080)): #0 0x7fcabd5a20bb in poll () at /lib64/libc.so.6 #1 0x7fcab7ea3229 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fcab7ea333c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fcabded1c1b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fcabde7a09a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fcabdca94da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fcac1557025 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fcabdcae0ce in () at /usr/lib64/libQt5Core.so.5 #8 0x7fcabce5b569 in start_thread () at /lib64/libpthread.so.0 #9 0x7fcabd5ac85f in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fc9e9867700 (LWP )): #0 0x7fcabd59dba8 in read () at /lib64/libc.so.6 #1 0x7fcab7ee7d20 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fcab7ea2d38 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fcab7ea31d0 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fcab7ea333c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fcabded1c1b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fcabde7a09a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fcabdca94da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fc9ec184f67 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #9 0x7fcabdcae0ce in () at /usr/lib64/libQt5Core.so.5 #10 0x7fcabce5b569 in start_thread () at /lib64/libpthread.so.0 #11 0x7fcabd5ac85f in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fc9f95a8700 (LWP 4279)): #0 0x7fcabd59dba8 in read () at /lib64/libc.so.6 #1 0x7fcab7ee7d20 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fcab7ea2d38 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fcab7ea31d0 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fcab7ea333c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fcabded1c1b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fcabde7a09a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fcabdca94da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fcabdcae0ce in () at /usr/lib64/libQt5Core.so.5 #9 0x7fcabce5b569 in start_thread () at /lib64/libpthread.so.0 #10 0x7fcabd5ac85f in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fca09f0a700 (LWP 4161)): #0 0x7fcabd59dba8 in read () at /lib64/libc.so.6 #1 0x7fcab7ee7d20 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fcab7ea2d38 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fcab7ea31d0 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fcab7ea333c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fcabded1c1b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fcabde7a09a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fcabdca94da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fcac19a5cf2 in () at /usr/lib64/libQt5Quick.so.5 #9 0x7fcabdcae0ce in () at
[frameworks-kwallet] [Bug 400462] kwalletd legacy dbus service file
https://bugs.kde.org/show_bug.cgi?id=400462 --- Comment #2 from Stefan Brüns --- Git commit dc5c7229bc4ff75506c34197da5450808c969efe by Stefan Brüns. Committed on 17/07/2019 at 22:33. Pushed by bruns into branch 'master'. Remove kde4 migration agent completely Summary: The migration agent is some quite weird mechanism: - it starts the KDE4 kwalletd - to do this, it asks DBus to start it - as the old kwalletd never shipped a service file, kwalletd5 ships a service file for kwalletd(4), hardcoding its likely path. - it merges the old wallets via DBus requests When the migration has finished, a flag is set in the config and on the next start, the migration agent is skipped. When the migration fails (e.g. because kwalletd(4) is not installed), the migration is attempted on each start. Shipping a a service file pointing to the old daemon also breaks autostart of kwalletd5 for old applications - kwalletd5 provides the kwalletd interface, but only if it has been started already. This leads to a race during startup. See D16520 - proper kwalletd dbus service file for the legacy name Reviewers: #frameworks, cfeck, ngraham, aacid Reviewed By: aacid Subscribers: aacid, lbeltrame, kde-frameworks-devel, damjang Tags: #frameworks Differential Revision: https://phabricator.kde.org/D21002 M +0-10 src/runtime/kwalletd/CMakeLists.txt M +0-1src/runtime/kwalletd/kwalletd.h M +1-4src/runtime/kwalletd/main.cpp D +0-265 src/runtime/kwalletd/migrationagent.cpp D +0-59 src/runtime/kwalletd/migrationagent.h D +0-108 src/runtime/kwalletd/migrationwizard.cpp D +0-44 src/runtime/kwalletd/migrationwizard.h D +0-122 src/runtime/kwalletd/migrationwizard1.ui D +0-51 src/runtime/kwalletd/migrationwizard2.ui D +0-6src/runtime/kwalletd/org.kde.kwalletd.service https://commits.kde.org/kwallet/dc5c7229bc4ff75506c34197da5450808c969efe -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 409879] xdotool error KDEInit could not launch
https://bugs.kde.org/show_bug.cgi?id=409879 --- Comment #3 from amee...@amitlele.com --- surprisingly the error is only seen if the earlier mentioned launcher is added to the top panel and then launched. it works as expected when added to bottom panel. nothing of significance in journalctl or syslog or messages -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408360] pen pressure isn't working
https://bugs.kde.org/show_bug.cgi?id=408360 --- Comment #12 from 0DDGH0ST --- Can I just send a video of me trying to use the brushes, I still have no pen pressure in krita On Fri, Jul 12, 2019, 12:33 AM Bug Janitor Service wrote: > https://bugs.kde.org/show_bug.cgi?id=408360 > > Bug Janitor Service changed: > >What|Removed |Added > > > Resolution|WAITINGFORINFO |WORKSFORME > Status|NEEDSINFO |RESOLVED > > --- Comment #11 from Bug Janitor Service --- > This bug has been in NEEDSINFO status with no change for at least > 30 days. The bug is now closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > Thank you for helping us make KDE software even better for everyone! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 340420] Make it easier to file issue reports
https://bugs.kde.org/show_bug.cgi?id=340420 Filipus Klutiero changed: What|Removed |Added CC||chea...@gmail.com --- Comment #11 from Filipus Klutiero --- (In reply to Brylie Christopher Oxley from comment #7) > Ah! Christoph ... and Christophe! Apologies. :) Christoph, Christophe, Brylie Christopher... for Christ's sake, this is getting as confusing as KDE's product list! Thanks for reporting Brylie. Unfortunately as currently titled this ticket's scope is very wide. Would you mind if this ticket was re-titled to "Simplify filing the product/component part of tickets"? Anyone is free to open new tickets about other parts of the reporting process, of course. -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 409902] Cannot start flatpak apps under Gnome+Wayland
https://bugs.kde.org/show_bug.cgi?id=409902 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #3 from Patrick Silva --- I see the same error messages posted in comment 2 trying to open clementine on Arch Linux running Gnome 3.32.2 + flatpak 1.4.2 on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] New: KDE application forgot their initial size after maximizing and closing them.
https://bugs.kde.org/show_bug.cgi?id=409919 Bug ID: 409919 Summary: KDE application forgot their initial size after maximizing and closing them. Product: kwin Version: 5.16.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: marcantoine_manning...@outlook.com Target Milestone: --- SUMMARY KDE application like dolphin, discover and konsole have a really strange behavior in plasma-wayland. But, it doesn't happen with other app like firefox and chromium. STEPS TO REPRODUCE 1. Maximize a KDE application 2. Close the application 3. Reopen the application 4. Minimize the application OBSERVED RESULT The minimized application have the size of the maximized application. EXPECTED RESULT The minimized application have the size of the initial minimized application. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.12.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 409913] korgac (KOrganizer reminder daemon/client) is a product as well as a component
https://bugs.kde.org/show_bug.cgi?id=409913 --- Comment #1 from Filipus Klutiero --- (In reply to Filipus Klutiero from comment #0) > [...] > > This issue would probably not have appeared if bugs.kde.org offered a > product/component text filter field. This filter could also search in > component descriptions. This is under discussion in ticket #409913. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 409913] korgac (KOrganizer reminder daemon/client) is a product as well as a component
https://bugs.kde.org/show_bug.cgi?id=409913 Christophe Giboudeaux changed: What|Removed |Added CC||win...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 360400] Very confusing list of products in search
https://bugs.kde.org/show_bug.cgi?id=360400 Christophe Giboudeaux changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #3 from Christophe Giboudeaux --- *** This bug has been marked as a duplicate of bug 340420 *** -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 340420] Make it easier to file issue reports
https://bugs.kde.org/show_bug.cgi?id=340420 Christophe Giboudeaux changed: What|Removed |Added CC||hvm2...@gmail.com --- Comment #10 from Christophe Giboudeaux --- *** Bug 360400 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 360400] Very confusing list of products in search
https://bugs.kde.org/show_bug.cgi?id=360400 Filipus Klutiero changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 See Also||https://bugs.kde.org/show_b ||ug.cgi?id=340420 CC||chea...@gmail.com --- Comment #2 from Filipus Klutiero --- I very much agree with this. With the power JavaScript and the web platform has reached, there should really be a text field to dynamically filter through products, or - even better - the select multiple should be replaced with a fancy drop-down like those allowed by the Chosen jQuery plugin. This will probably be more complicated since components need to be considered too. Ideally, there would be a single text field where I'd type for example "korgac". If korgac is defined as a product, then that product would come up as the first suggestion. If korgac is instead defined as a component of the korganizer product, then that component would come up as the first suggestion. I think it would make sense, before attacking this issue, to reconsider the structure of products and components. Many products are small and have a single "general" component. Other products are big and have so many components that some are related; for example, amarok has components "Playback", "Playback/CUE sheet support", "Playback/Replay Gain", "Playback/Streams". Therefore, for a small product like abakus, a single-level categorization system would be better, while for a big product like amarok, a three-level categorization system would be better. So I think it would be best to allow a variable depth. A product could have sub-products, and any sub-product may have sub-sub-products. With this approach, we could put all products/components in a single widget which would ease filtering. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 340420] Make it easier to file issue reports
https://bugs.kde.org/show_bug.cgi?id=340420 Filipus Klutiero changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=360400 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 409918] New: Application start indicator doesn't show in plasma-wayland
https://bugs.kde.org/show_bug.cgi?id=409918 Bug ID: 409918 Summary: Application start indicator doesn't show in plasma-wayland Product: kde Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: marcantoine_manning...@outlook.com Target Milestone: --- SUMMARY When you launch an application the little bouncing icon doesn't show. STEPS TO REPRODUCE 1. Set application start indicator to bouncing cursor in system settings. 2. Launch an application OBSERVED RESULT The application launch but there is no little bouncing icon. EXPECTED RESULT A little bouncing icon show before the application start. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.12.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409917] New: Elliptical selection - after applying several times becomes irregular
https://bugs.kde.org/show_bug.cgi?id=409917 Bug ID: 409917 Summary: Elliptical selection - after applying several times becomes irregular Product: krita Version: 4.2.3 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: major Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: bullshitma...@yahoo.com Target Milestone: --- Created attachment 121593 --> https://bugs.kde.org/attachment.cgi?id=121593=edit Example of irregular shapes while using elliptical selection tool SUMMARY Since 4.2 version after making several elliptical selections it becomes squarish and irregular. STEPS TO REPRODUCE 1. Use elliptical selection tool 2. Make at least 4 (add) selections 3. Observe OBSERVED RESULT Irregular circles EXPECTED RESULT Round selection SOFTWARE/OS VERSIONS Windows: 10 home, 7 ultimate 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.
[konqueror] [Bug 409833] Konqueror crashes on close
https://bugs.kde.org/show_bug.cgi?id=409833 --- Comment #2 from Fernando Romero --- (In reply to Wolfgang Bauer from comment #1) > Looks like bug#407454, which should actually be fixed in the latest KDE > Applications 19.04.3. > > Which konqueror version are you using exactly? 5.0.97 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409903] The settings app have a minimum size.
https://bugs.kde.org/show_bug.cgi?id=409903 --- Comment #4 from marcantoine_manning...@outlook.com --- Created attachment 121592 --> https://bugs.kde.org/attachment.cgi?id=121592=edit Plasma x11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409903] The settings app have a minimum size.
https://bugs.kde.org/show_bug.cgi?id=409903 --- Comment #3 from marcantoine_manning...@outlook.com --- But, if it's intentional why in plasma x11, it can be smaller. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 358275] Browse and My Bugs should show REOPEN status by default
https://bugs.kde.org/show_bug.cgi?id=358275 Filipus Klutiero changed: What|Removed |Added CC||chea...@gmail.com --- Comment #1 from Filipus Klutiero --- Please provide an example. I rather find the opposite, if looking - for example -at https://bugs.kde.org/show_bug.cgi?id=339863 -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 334299] edit function for comments
https://bugs.kde.org/show_bug.cgi?id=334299 Filipus Klutiero changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||chea...@gmail.com --- Comment #5 from Filipus Klutiero --- I agree but think comments should always be editable. There should simply be a history of edits (if someone has read the previous versions, indeed). This will apparently be solved in Bugzilla 6, which would probably release this year... -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 409833] Konqueror crashes on close
https://bugs.kde.org/show_bug.cgi?id=409833 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at --- Comment #1 from Wolfgang Bauer --- Looks like bug#407454, which should actually be fixed in the latest KDE Applications 19.04.3. Which konqueror version are you using exactly? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 401152] In multi monitor configuration PC start with screen OFF
https://bugs.kde.org/show_bug.cgi?id=401152 Marcus changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406428] Video preview - no sound
https://bugs.kde.org/show_bug.cgi?id=406428 --- Comment #41 from Maik Qualmann --- An objdump of the two libQtAV.so.1 states that the 6.2 version is less linked to 3 libs: libGL.so.1 libX11.so.6 libpthread.so.0 Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409916] CMYK profiles not listed. Setting document to CMYK color mode - immediate crash
https://bugs.kde.org/show_bug.cgi?id=409916 Boudewijn Rempt changed: What|Removed |Added Severity|critical|crash CC||b...@valdyas.org Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com Ever confirmed|0 |1 Status|REPORTED|ASSIGNED Keywords||regression, release_blocker -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409916] New: CMYK profiles not listed. Setting document to CMYK color mode - immediate crash
https://bugs.kde.org/show_bug.cgi?id=409916 Bug ID: 409916 Summary: CMYK profiles not listed. Setting document to CMYK color mode - immediate crash Product: krita Version: 4.2.3 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: critical Priority: NOR Component: Color models Assignee: krita-bugs-n...@kde.org Reporter: bullshitma...@yahoo.com Target Milestone: --- SUMMARY There is no option to set document to CMYK color mode. In the list of color profiles there are no CMYK ones and setting document to CMYK results in crash. STEPS TO REPRODUCE 1. Try to set document to CMYK color mode 2. Hit "Apply" 3. Observe the inevitable crash OBSERVED RESULT Crash EXPECTED RESULT Document set to CMYK mode SOFTWARE/OS VERSIONS Windows: 10 home edition and win 7 ultimate 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.
[plasmashell] [Bug 387901] Task manager loses windows with multi monitor
https://bugs.kde.org/show_bug.cgi?id=387901 Siddhartha Sahu changed: What|Removed |Added CC||sh.siddhar...@gmail.com --- Comment #6 from Siddhartha Sahu --- I am seeing the same issue on git master with the icon-only task manager configured to only show applications in current screen. Disconnecting my external screens does not reset the task manager state and I have to restart plasmashell as a workaround. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409903] The settings app have a minimum size.
https://bugs.kde.org/show_bug.cgi?id=409903 Nate Graham changed: What|Removed |Added CC||n...@kde.org Summary|With kwin Wayland, the |The settings app have a |settings app have a minimum |minimum size. |size. | Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #2 from Nate Graham --- This is intentional, because if you make the window any smaller, then the individual pages' content can (and often does) get cut off. I know it's not the most elegant way to handle the situation (sorry!), but it was the best we could do for the moment given the state of the systemsettings codebase, which is quite old and hard to work with at this point. -- You are receiving this mail because: You are watching all bug changes.
