[lattedock] [Bug 412148] New: Overlapping character strings and widgets (application titles, global menu) cause lattedock to shrink
https://bugs.kde.org/show_bug.cgi?id=412148 Bug ID: 412148 Summary: Overlapping character strings and widgets (application titles, global menu) cause lattedock to shrink Product: lattedock Version: 0.8.7 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: sinq...@cock.li Target Milestone: --- Created attachment 122775 --> https://bugs.kde.org/attachment.cgi?id=122775=edit Screenshot of the issue. SUMMARY When character strings overlap on the dock/panel itself lattedock will shrink, i.e the dock remains the horizontal length stays the same but the vertical length will shorten. This can occur with Active window control when show title is set to "always fit" and the title is several lines long. This can also occur when active window control is left justified and global menu is middle justified and there are a lot of global menu entries. STEPS TO REPRODUCE 1. Create a latte dock panel. 2. Set alignment to justify. 3. On the left justify add active window control to the panel with window title/application title enabled. 4. In the middle justify add global menu 5. on the right hand side add widgets (the goal is to force strings/widgets to ovrelap) 6.Open an app with lots of global menu entries (tex studio, calibre, etc). This works best on a smaller resolution screen (1366 x 768 in my case) 7. lattedock will shrink OBSERVED RESULT After strings/widgets overlap in lattedock, the dock/panel will shrink vertically by approx half EXPECTED RESULT Widgets should be aware of space taken up in lattedock and accomidate widget icons/strings. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux Plasma(available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412145] Dolphin is not aware of unclean mount on exfat
https://bugs.kde.org/show_bug.cgi?id=412145 --- Comment #1 from Brennan Kinney --- Output for performing `sudo fsck.exfat /dev/sdc1` exfatfsck 1.3.0 Checking file system on /dev/sdc1. WARN: volume was not unmounted cleanly. ERROR: fsync failed: Input/output error. File system checking stopped. ERRORS FOUND: 1, FIXED: 0. The error appears tied to the device becoming unavailable. A physical unplug and re-plug is required as /dev/sdc1 is no longer available afterwards. The warning is the same given when performing `mount -t exfat /dev/sdc1 /mnt/usb_stick`. Windows 7 and Windows 10 systems detected the errors but both failed to repair. The repair/scan could be ignored and data could be copied off the disk, but write activity appears to cause the device to fail in Windows as well, and it becomes available until physical reconnection is made. --- When Windows 7 performed a repair/fix, I was able to mount successfully in Dolphin, although while browsing the files, Dolphin became unresponsive, and ksysguard reported 50% CPU usage(4 cores/threads system), htop revealed <5-10% CPU activity, and ksysguard processes(all) sorted by CPU column showed nothing high usage. Eventually that dropped and Dolphin became responsive again, the mounted location became unavailable and could not mount again. Possibly related to this old bug: https://bugs.kde.org/show_bug.cgi?id=347565 Although another exfat device unmounts cleanly without getting corrupted. --- Related issues: Notification Panel, incorrect error(different from Dolphin): https://bugs.kde.org/show_bug.cgi?id=412146 Partition Manager, gets stuck scanning devices after a failed mount: https://bugs.kde.org/show_bug.cgi?id=412147 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 412146] New: Notification about a failed mount is incorrect
https://bugs.kde.org/show_bug.cgi?id=412146 Bug ID: 412146 Summary: Notification about a failed mount is incorrect Product: frameworks-knotifications Version: 5.61.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: polarathene-sig...@hotmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY When accessing a USB stick formatted with exfat(in a dirty state) via dolphin, the mount fails with a timeout error in Dolphin error dialog/status. When mounting via terminal, the error states the filesystem was not cleanly unmounted. At the same time, a notification on the panel pops up that claims "unauthorized access", but exfat does not have permissions and this is not the actual error. That is misleading to the user. STEPS TO REPRODUCE 1. Plug in USB with exfat partition in a dirty state. 2. Access it via Dolphin. 3. Timeout triggers a notification about a lack of permissions while Dolphin's error conveys different information. OBSERVED RESULT Inconsistent errors between Dolphin and the notification panel. Notification panel also is incorrect about the cause. EXPECTED RESULT Consistency, or at least the notification not claiming it's an authorization/permissions problem. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE (up to date), Kernel 4.19.69-1-MANJARO KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 412147] Stuck scanning devices
https://bugs.kde.org/show_bug.cgi?id=412147 Brennan Kinney changed: What|Removed |Added CC||polarathene-signup@hotmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 412146] Notification about a failed mount is incorrect
https://bugs.kde.org/show_bug.cgi?id=412146 Brennan Kinney changed: What|Removed |Added CC||polarathene-signup@hotmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 412147] New: Stuck scanning devices
https://bugs.kde.org/show_bug.cgi?id=412147 Bug ID: 412147 Summary: Stuck scanning devices Product: partitionmanager Version: 4.0.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: polarathene-sig...@hotmail.com Target Milestone: --- SUMMARY After a failed mount with Dolphin, an external USB stick(with corrupted exfat filesystem), seemed to be the cause of a device scan with PartitionManager being stuck. It remained on 50% for.. 5 mins or so, saying it was scanning /dev/sdc (the problematic device), and it was not possible to cancel this process(clicking the dialogs X button to close did nothing. I killed it via ksysguard. If a scan is performed prior to any attempt to mount the device, the scan performed fine, only after the failed mount(dirty filesystem which Windows itself cannot repair), does it cause this behaviour with scan. STEPS TO REPRODUCE 1. Fail to mount a corrupt(or possibly dirty/uncleanly mounted) exfat system. 2. Try to scan with PartitionManager(I had it open already so this was a 2nd scan) 3. Scan gets stuck when scanning the device with bad exfat filesystem. OBSERVED RESULT PartitionManager stuck scanning, unable to cancel/skip problematic device. EXPECTED RESULT Time out skip device and raise error/notification to user after, or permit cancelling the scan. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE (up to date), Kernel 4.19.69-1-MANJARO KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412145] Dolphin is not aware of unclean mount on exfat
https://bugs.kde.org/show_bug.cgi?id=412145 Brennan Kinney changed: What|Removed |Added CC||polarathene-signup@hotmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412096] Line tool brush size cannot be changed with shortcuts
https://bugs.kde.org/show_bug.cgi?id=412096 Aaron Lavarnway changed: What|Removed |Added CC||i...@ralek.art -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412145] New: Dolphin is not aware of unclean mount on exfat
https://bugs.kde.org/show_bug.cgi?id=412145 Bug ID: 412145 Summary: Dolphin is not aware of unclean mount on exfat Product: dolphin Version: 19.08.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: status Assignee: dolphin-bugs-n...@kde.org Reporter: polarathene-sig...@hotmail.com Target Milestone: --- SUMMARY When accessing a USB stick formatted with exfat(in a dirty state) via dolphin, the mount fails with a timeout error. Dolphin is unsure of what went wrong. When mounting via terminal, the error states the filesystem was not cleanly unmounted. STEPS TO REPRODUCE 1. Plug in USB with exfat partition in a dirty state. 2. Access it via Dolphin. 3. Timeout triggers a red status error where Dolphin is unsure of what went wrong. OBSERVED RESULT Unable to mount drive, Dolphin does not indicate the actual cause when that information should be available. EXPECTED RESULT The error should state that exfat filesystem was not cleanly unmounted and is in a dirty state. Then advise/link to how to repair(windows only I think, maybe 5.4 kernel will change this. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE (up to date), Kernel 4.19.69-1-MANJARO KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398990] Filter layer ignores transparency when merged with layers beneath it
https://bugs.kde.org/show_bug.cgi?id=398990 Raghavendra kamath changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |LATER --- Comment #28 from Raghavendra kamath --- > sorry if I was a little too aggressive. We are used to this kind of behaviour, you would be surprised how many users even curse us and say weird things and want the features that they think is prime importance, it feels sad when you put on hours of free volunteer work and rewarded with aggression, But we are now indifferent to it, so no problem. I am closing this bug report for now. Please open a forum discussions so that we can continue to discuss it with larger group of people and arrive at a conclusion. Thank you for your support -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 412144] Thead concurrency
https://bugs.kde.org/show_bug.cgi?id=412144 Nicolás Alvarez changed: What|Removed |Added CC||nicolas.alva...@gmail.com --- Comment #1 from Nicolás Alvarez --- What application gives you this error? Is it Dolphin, the file manager? -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 412144] New: Thead concurrency
https://bugs.kde.org/show_bug.cgi?id=412144 Bug ID: 412144 Summary: Thead concurrency Product: bugs.kde.org Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: product/component changes Assignee: sysad...@kde.org Reporter: projet...@gmail.com CC: christo...@krop.fr Target Milestone: --- Created attachment 122774 --> https://bugs.kde.org/attachment.cgi?id=122774=edit screenshot of error message SUMMARY There are two actions (New tab, New tab) which would like to use the same shortcut (Ctrl + T). It might is an error. STEPS TO REPRODUCE 1. Download some file with Firefox 2. Click on down arrow icon (download) 3. Ask to open; OBSERVED RESULT Error cause by thread concurrency; EXPECTED RESULT Open the file manager on downloaded directory SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Buster | Debian 10 (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.
[kwin] [Bug 411632] Kwin crashing on switching virtual desktop.
https://bugs.kde.org/show_bug.cgi?id=411632 --- 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.
[KBibTeX] [Bug 409415] Freeze when opening edit dialog for second time
https://bugs.kde.org/show_bug.cgi?id=409415 --- 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 412061] Rotating selection with Transform Tool makes the selection edge rough
https://bugs.kde.org/show_bug.cgi?id=412061 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #8 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412102] Open recent documents doesn't load on windows
https://bugs.kde.org/show_bug.cgi?id=412102 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 411620] No sound on AirPlay speakers
https://bugs.kde.org/show_bug.cgi?id=411620 --- 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.
[krita] [Bug 412143] New: color pick and brush stop working
https://bugs.kde.org/show_bug.cgi?id=412143 Bug ID: 412143 Summary: color pick and brush stop working Product: krita Version: 4.2.3 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: djduf...@ucdavis.edu Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. happens randomly while drawing with a tablet 2. 3. OBSERVED RESULT color picker chooses a color not part of what has been designated and the brush fails to create any color 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.
[Discover] [Bug 412142] Discover crashes when I click on Applications
https://bugs.kde.org/show_bug.cgi?id=412142 Franz changed: What|Removed |Added CC||franz-h...@mail.de --- Comment #1 from Franz --- I just downloaded and installed the latest build of kde neon. Now I would like to install a few apps I need from discover, but unfortunately discover crashes when I click an "applications". -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412142] New: Discover crashes when I click on Applications
https://bugs.kde.org/show_bug.cgi?id=412142 Bug ID: 412142 Summary: Discover crashes when I click on Applications Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: franz-h...@mail.de CC: aleix...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Start Discover 2. Click on Applications 3. Discover crashes immediately 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.
[frameworks-kiconthemes] [Bug 402172] Compiling against Qt 5.12 breaks QIcon::themeName with Plama platform plugin
https://bugs.kde.org/show_bug.cgi?id=402172 Bobby changed: What|Removed |Added CC||bo...@fiery.me --- Comment #3 from Bobby --- Hi there, I'd like to bump this report, confirming that I'm also getting the issue. Albert launcher (https://github.com/albertlauncher/albert) seems to be using QIcon::themeName to get user's preferred icon theme, and due to it returning empty string, Albert ends up failing in displaying the icons using user's preferred icon theme. A relevant bug report in their Git repo can be found here: https://github.com/albertlauncher/albert/issues/778, along with some other people confirming they also encountered the issue. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 410798] Audio and Video are out of sync
https://bugs.kde.org/show_bug.cgi?id=410798
--- Comment #3 from Colin Brash ---
Audio and Video are the same, eg: adding a single video file to the timeline
and the Video/Audio are separated as expected in Kdenlive, I believe the
problem occurs as you start cutting out sections of the Video/Audio (In my
example the Video/Audio sections are cut equally the same, ("No Cutting" of
different sections of Video and different sections of Audio) I believe the
Audio is in sync with the video, however it's incredibly difficult to select an
Audio section as the Waveform is way out of sync, eg: where you have a gap in
the waveform there will be sound, where there is a waveform showing sound there
is no sound, it's out of sync randomly, I hope this makes sense, thanks for
your response, it's much appreciated!!
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 410781] Open additional file from Dolphin will not show Kate on Wayland
https://bugs.kde.org/show_bug.cgi?id=410781 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- Same behavior with Kate 19.08.1 on Plasma 5.17 beta. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 mikz...@gmail.com changed: What|Removed |Added CC||mikz...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 412141] Krfb crashes soon after connecting, taking the entire system down with it
https://bugs.kde.org/show_bug.cgi?id=412141 oskarsma...@gmail.com changed: What|Removed |Added CC||oskarsma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 410818] Generic icon displayed when typing the name of a file instead of using the list in KFileDialog
https://bugs.kde.org/show_bug.cgi?id=410818 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 412141] New: Krfb crashes soon after connecting, taking the entire system down with it
https://bugs.kde.org/show_bug.cgi?id=412141 Bug ID: 412141 Summary: Krfb crashes soon after connecting, taking the entire system down with it Product: krfb Version: 19.08.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: grundleb...@googlemail.com Reporter: oskarsma...@gmail.com Target Milestone: --- SUMMARY Krfb STEPS TO REPRODUCE 1. Install Krfb and keep default settings. 2. Download VNC Viewer app for Android. 3. Connect to computer using VNC Viewer app. 4. Accept the connection from the computer. (It doesn't matter whether keyboard and mouse control are allowed or not.) 5. Wait. OBSERVED RESULT System freezes after a few seconds to minutes, and neither the VNC session nor the local keyboard and mouse can interact with the system until it is forcefully rebooted. EXPECTED RESULT Krfb actually works. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.16, kernel 4.18.0-25-generic (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398990] Filter layer ignores transparency when merged with layers beneath it
https://bugs.kde.org/show_bug.cgi?id=398990 --- Comment #27 from katearche...@yandex.ru --- (In reply to Raghavendra kamath from comment #26) > Hi Kate, > > Thank you very much for the images, that makes it clear to understand what > you want. > > From what I understand you want the filter to only applied to the selected > layer and merged down, disregarding the unselected layer, that is the filter > should not be applied to the unselected layer and it should be reverted to > how it looked without filter. > > Now as we have told you in previous comment that in krita the filter layers > are just like new "layers from visible + the filter applied to them" so we > try to keep the output as close to what users see prior to merging. > I understand what are you trying to say but it's not intuitive at all. Just for a moment wear my boots with my train of thought: I see two layers(and a bunch of other i'm not interested by), I want to merge these two layers, I select them to isolate from the others but, by some miracle, in the end I got not only the layers I've selected but all other layers merged in that I've NOT selected purposely and by intent because I was merging these two. To expand: Let's say you have two paint layers. They are displayed on a canvas exactly the same way as two layers from my latest example but merging them together won't result in the merging in layers that wasn't selected. What I grieve for is a lack of consistency: in the end filter or not it's all _layers_, they exist in a same docker etc and a user should not be bothered with all the booby traps here and there when in one case selected layers merging in one way and in the other case completely differently from the first. > In your scenarios the merged output changes from what you have prior to > merging, it might be easy to guess in simple situations like having two > three layer and some adjustment layers, but It gets tricky when you'll have > filters such as blur or when you'll have more than 10 or 20 layers in > between with different blend modes. > I understand that merging with different blend modes can lead to unexpected results as well, and that's the case for Photoshop and other layer/blending operating programs as well. But there is a great difference between cases: "selected layers merging with no additional pixels created" and "selected layers merging with all the pixels from non-selected layers merged in as well". > May I request you to also show us images what photoshop does when you have > blur as filter layer, as you had in your first attachment. I can do that but it would be of no use since photoshop' adjustment layers are indeed working somehow differently from Krita's filter layers(i'm not sure about it's inner workings). They have two adjustment layer systems in place, the legacy one, adjustment layers, and smart layers, which are more or less works as krita's filter layers. - The legacy one was there like forever and from my understanding it's designed to work as fast as possible, therefore only selected filters are available as adjustment layers. - Smart filters are applied to smart objects only and in this case the whole set of filters are available, they can be stacked, edited at any given moment turned off and on again etc. The catch is that to apply these smart filters to a set of layers you must convert them into a smart object beforehand. So in a sense photoshop' smart filters work the same way krita filter masks. Returning to the question: The blur filter is available only as a smart filter so it is attached to a smart object which itself is just one layer from a layer stack point of view. So it's already "merged" with filters applied to it in the stack and they only way to merge in with filters is to flatten a layer which is working(kinda obviously) the same way as in krita. > > The design of the filter layer in Krita is different from photoshop's > adjustment layers. And krita users are more accustomed to the behaviour that > we have now. Changing it will lead to discomfort to many of the krita users > who rely on the existing behaviour. > To be honest I'm s not sure that your average joe keeping in his head that merging selected layers with filter layers without grouping selected layers beforehand would lead to other results than as with grouping them and/or that the "feature" of merging in pixels that wasn't there before can be used in any workflow usefully. > Still if you feel like we need to change the behaviour I humbly suggest you > to start a discussion topic in forum, so that we can gather more support and > opinion from the artists and we will get know what they like. > > P.S. The bug title can be - [Wish bug] Make filter layer affect only the > selected layer when merging down. Yes, I do feel like this behavior is inconsistent and misleading and I'll make a topic on a forum about it later on, thanks for a meaningful discussion, sorry if I was a little too
[systemsettings] [Bug 411004] sddm setting page is too wild and cannot be resized smaller
https://bugs.kde.org/show_bug.cgi?id=411004 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411052] Make view scrollable while file is being dragged
https://bugs.kde.org/show_bug.cgi?id=411052 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411877] Touchscreen input locked to first screen
https://bugs.kde.org/show_bug.cgi?id=411877 --- Comment #3 from lo...@kde.bt.alestan.publicvm.com --- So I finally had a bit more time to dig into this, with a bit of grepping, I managed to find the relevant function: $kwin/libinput/connection.cpp:applyScreenToDevice Looks like there is no simple way to remap APDs to arbitrary virtual screen offsets. That said, adding additional heuristics for the mapping is pretty simple (for one, if there is only a single display attached, grab it with reasonable confidence, also, if there is already a APD attached, grab the next screen in line). It also should be easy to add a config file to override the auto-detection. Given the information available in the function, looks like mapping from touch device to EDID is going to be the most reliable. I'm not certain how to identify the touch device, as USB serial numbers are unreliable, and bus location is worse. I'll poke that a bit more and see what shakes out. All that said, I'm happy to attach a patch once I get it working, if I can get some help making sure it won't just waste everyone's time. To that end, I have a few questions. 1. Is it better to add a new section to one of the existing $HOME/.config/k*rc files, or to make a new ktouchrc (or some other name) file? 2. Do I put the config reading/writing inline in the `applyScreenToDevice` function, or in its own function (and where do I put that)? 3. Is there a better choice than EDID to remember the display, and is there an obvious choice for the input device? -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 399568] Dictionary plasmoid icon broken
https://bugs.kde.org/show_bug.cgi?id=399568 --- Comment #13 from Noah Davis --- This is an Oxygen icon and Oxygen icons are meant to be converted to PNGs. Perhaps this icon should be converted to a PNG when the applet is built? That, or the icon should be completely replaced with a Breeze icon. The latter should probably happen eventually, but the former would be enough to close this bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 399568] Dictionary plasmoid icon broken
https://bugs.kde.org/show_bug.cgi?id=399568 --- Comment #12 from Noah Davis --- (In reply to Patrick Silva from comment #10) > Created attachment 122762 [details] > screenshot taken on Plasma 5.17 beta > > Weird. I'm attaching a screenshot. And yes, I use breeze icon theme. This may be because you have the Oxygen icon theme installed and Breeze inherits from Oxygen on some distros. I can see in your screenshot that the blur effect is being used, even though the Qt SVG renderer does not support blur. This means the SVG has been converted to a PNG. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412140] New: delayed, slow motion when moving canvas with spacebar
https://bugs.kde.org/show_bug.cgi?id=412140 Bug ID: 412140 Summary: delayed, slow motion when moving canvas with spacebar Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: acc4commissi...@gmail.com Target Milestone: --- SUMMARY The title says it all. It gets worse when the krita application window is wider. It's not that much of a problem. So just a wishlist. SOFTWARE/OS VERSIONS Windows: Win7 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Krita Version: 4.3.0-prealpha (git 8c1b215) Languages: en_US Hidpi: false Qt Version (compiled): 5.12.5 Version (loaded): 5.12.5 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 6.1.7601 Pretty Productname: Windows 7 SP 1 (6.1) Product Type: windows Product Version: 7sp1 Hardware Information GPU Acceleration: desktop Memory: 16351 Mb Number of Cores: 8 Swap Location: C:/Users/(-)/AppData/Local/Temp -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412140] delayed, slow motion when moving canvas with spacebar (the pan tool)
https://bugs.kde.org/show_bug.cgi?id=412140 acc4commissi...@gmail.com changed: What|Removed |Added Summary|delayed, slow motion when |delayed, slow motion when |moving canvas with spacebar |moving canvas with spacebar ||(the pan tool) -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 412139] hover over battery icon seems to give time for only 1 battery rather than accounting for the 2 batteries.
https://bugs.kde.org/show_bug.cgi?id=412139 James Th changed: What|Removed |Added Summary|hover over battery icon |hover over battery icon |seems to give time for 1|seems to give time for only |battery rather than |1 battery rather than |accounting for two. |accounting for the 2 ||batteries. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 412139] New: hover over battery icon seems to give time for 1 battery rather than accounting for two.
https://bugs.kde.org/show_bug.cgi?id=412139 Bug ID: 412139 Summary: hover over battery icon seems to give time for 1 battery rather than accounting for two. Product: Powerdevil Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- SUMMARY If i hover over the battery icon at the bottom of my screen then I get the 'time-remaining' for only one battery, rather than it taking into account both internal batteries. STEPS TO REPRODUCE 1. have a laptop with 2 batteries, and hover over the battery icon, and it will show you something like: 2:05 remaining, 76% When it switches to the second internal battery it will then show e.g.5:00 remaining, 49% OBSERVED RESULT As above. EXPECTED RESULT 7:05 remaining, 99% (or whatever the actual combined values are for both batteries) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Opensuse TW (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION Happy to send a screenshot if that would be useful? -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 411425] The link ordering is correct by chance only and init of gdrive.so fails when linking with LTO enabled
https://bugs.kde.org/show_bug.cgi?id=411425 David Barchiesi changed: What|Removed |Added CC||da...@barchie.si -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412138] New: Regularly (nearly always) crashing on startup. Can not file valid report despite debugging symbols installed
https://bugs.kde.org/show_bug.cgi?id=412138 Bug ID: 412138 Summary: Regularly (nearly always) crashing on startup. Can not file valid report despite debugging symbols installed Product: Discover Version: 5.16.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: t...@tim-richardson.net CC: aleix...@kde.org Target Milestone: --- Created attachment 122773 --> https://bugs.kde.org/attachment.cgi?id=122773=edit Bug report trace SUMMARY For a week or Discover crashes on start. I get the interactive bug report tool. Each time it asks me to install debug symbols, but it never proceeds to file a valid bug report. I have plasma-discover-dbgsym installed Operating System: KDE neon 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: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 31.2 GiB of RAM 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.
[kmail2] [Bug 412137] New: message list behaviour
https://bugs.kde.org/show_bug.cgi?id=412137 Bug ID: 412137 Summary: message list behaviour Product: kmail2 Version: 5.12.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- SUMMARY if i select an email message in kmail, and then press the down arrow key, the action seems to be moving through the email message, rather than selecting the next email. STEPS TO REPRODUCE 1. select an email message so that its hilighted in blue. 2. Press the down/up arrow key, and it will scroll down/up the actual email message OBSERVED RESULT as above EXPECTED RESULT to select the next email message. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: opensuse TW (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 412092] Screen orientation icons are confusing in screen kcm
https://bugs.kde.org/show_bug.cgi?id=412092 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Nate Graham --- Thanks for the info. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 411286] Discover crashes after opening and check for update
https://bugs.kde.org/show_bug.cgi?id=411286 Thomas changed: What|Removed |Added CC||thomas.jo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 412092] Screen orientation icons are confusing in screen kcm
https://bugs.kde.org/show_bug.cgi?id=412092 --- Comment #4 from petrk --- Created attachment 122772 --> https://bugs.kde.org/attachment.cgi?id=122772=edit misplaced tooltips Another issue I just noticed, tooltips appear in weird spots. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 412092] Screen orientation icons are confusing in screen kcm
https://bugs.kde.org/show_bug.cgi?id=412092 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #3 from Roman Gilg --- The issue is also with these toolbar buttons that they have this massive gap between icon and edge. The icon could fill much more of the button. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 412092] Screen orientation icons are confusing in screen kcm
https://bugs.kde.org/show_bug.cgi?id=412092 --- Comment #2 from petrk --- It's just that it was hard for me to decipher meaning behind each icon. Thankfully there are mouseover tooltips. These icons are tiny, also people don't use square shaped screens that often. I'd like to suggest wider icon instead as a compromise, or a drop down menu. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412136] Executable: plasma-discover Signal: Segmentation fault (11) while fetching updates
https://bugs.kde.org/show_bug.cgi?id=412136 Ahmed Anan changed: What|Removed |Added CC||ananl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412136] New: Executable: plasma-discover Signal: Segmentation fault (11) while fetching updates
https://bugs.kde.org/show_bug.cgi?id=412136 Bug ID: 412136 Summary: Executable: plasma-discover Signal: Segmentation fault (11) while fetching updates Product: Discover Version: 5.16.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: ananl...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 122771 --> https://bugs.kde.org/attachment.cgi?id=122771=edit full text crash report SUMMARY plasma-discover crashes while fetching updates STEPS TO REPRODUCE 1. open discover 2. plasma-discover trying to fetching updates OBSERVED RESULT plasma-discover crashes after 4 seconds EXPECTED RESULT list of packages to update SOFTWARE/OS VERSIONS Operating System: KDE neon 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: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 5.7 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 409504] Spinner shown while Discover loads screenshots is partially hidden
https://bugs.kde.org/show_bug.cgi?id=409504 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 409504] Spinner shown while Discover loads screenshots is partially hidden
https://bugs.kde.org/show_bug.cgi?id=409504 Patrick Silva changed: What|Removed |Added CC||michaelalexsander@protonmai ||l.com --- Comment #3 from Patrick Silva --- *** Bug 411278 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 411278] Image loading symbol is buried of the far left
https://bugs.kde.org/show_bug.cgi?id=411278 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 409504 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 411327] Gwenview fails to open some (not all) Gimp XCF images
https://bugs.kde.org/show_bug.cgi?id=411327 Albert Astals Cid changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kim ||ageformats/5c4c05257cd89ab4 ||a082169db3f15c9998f79135 --- Comment #8 from Albert Astals Cid --- Git commit 5c4c05257cd89ab4a082169db3f15c9998f79135 by Albert Astals Cid. Committed on 20/09/2019 at 20:41. Pushed by aacid into branch 'master'. xcf: Fix regression when reading files with "unsupported" properties Summary: The fact that we don't know the property is most of the times not fatal, so what we have to do is just "skip" the property and hope for the best Reviewers: cfeck, apol, vkrause Reviewed By: vkrause Subscribers: kde-frameworks-devel Tags: #frameworks Differential Revision: https://phabricator.kde.org/D24114 M +6-1src/imageformats/xcf.cpp https://commits.kde.org/kimageformats/5c4c05257cd89ab4a082169db3f15c9998f79135 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 411428] file-picker support links locations in GTK file dialogues from KDE/Qt created link locations
https://bugs.kde.org/show_bug.cgi?id=411428 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412127] "KDE-Story (1.0) - 0 B" appears each time Discover reports updates are needed, even when no other updates needed.
https://bugs.kde.org/show_bug.cgi?id=412127 --- Comment #4 from Nate Graham --- FWIW there have been two newer versions of Ubuntu since the one you're using that both include the fix, but the next LTS version (20.04) isn't scheduled to be released until April or May of next year. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411431] Make tabs detachable when dragged off the tab bar
https://bugs.kde.org/show_bug.cgi?id=411431 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412127] "KDE-Story (1.0) - 0 B" appears each time Discover reports updates are needed, even when no other updates needed.
https://bugs.kde.org/show_bug.cgi?id=412127 --- Comment #3 from Nate Graham --- Yep! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 412131] baloo_file crashes after system startup
https://bugs.kde.org/show_bug.cgi?id=412131 --- Comment #1 from Stefan Brüns --- LMDB update required. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 412131] baloo_file crashes after system startup
https://bugs.kde.org/show_bug.cgi?id=412131 Stefan Brüns changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 412088] Xwayland apps become blurry after I enable fractional display scaling
https://bugs.kde.org/show_bug.cgi?id=412088 hum...@yahoo.fr changed: What|Removed |Added CC||hum...@yahoo.fr --- Comment #3 from hum...@yahoo.fr --- I am sorry if I do not understand but I tried to have the same applications open on Gnome Wayland and so using also Xwayland and the problem is not there. Is it desktop dependent Xwayland behavior? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412113] Permanent error
https://bugs.kde.org/show_bug.cgi?id=412113 --- Comment #4 from Maik Qualmann --- Git commit d73a25ed14440af7aabcc161d3a26adfdb9dd52a by Maik Qualmann. Committed on 20/09/2019 at 20:02. Pushed by mqualmann into branch 'master'. set QWebEngine settings after new page M +6-6core/app/views/stack/welcomepageview.cpp M +5-5 core/utilities/geolocation/geoiface/widgets/htmlwidget_qwebengine.cpp https://invent.kde.org/kde/digikam/commit/d73a25ed14440af7aabcc161d3a26adfdb9dd52a -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411524] A suggestion to change font style listing to default to "regular" rather than "bold" or "italic", upon choosing a new font
https://bugs.kde.org/show_bug.cgi?id=411524 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412135] Asan crash while painting.
https://bugs.kde.org/show_bug.cgi?id=412135 wolthera changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com --- Comment #1 from wolthera --- Assigning this to dmitry. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412095] lines containing certain Unicode characters aren't displayed correctly
https://bugs.kde.org/show_bug.cgi?id=412095 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Christoph Cullmann --- *** This bug has been marked as a duplicate of bug 404907 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 404907] ktexteditor: lineheight regression
https://bugs.kde.org/show_bug.cgi?id=404907 Christoph Cullmann changed: What|Removed |Added CC||glyphi...@gmail.com --- Comment #15 from Christoph Cullmann --- *** Bug 412095 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412095] lines containing certain Unicode characters aren't displayed correctly
https://bugs.kde.org/show_bug.cgi?id=412095 --- Comment #2 from glyphi...@gmail.com --- Created attachment 122770 --> https://bugs.kde.org/attachment.cgi?id=122770=edit Kwrite screenshot showing incorrectly-rendered lines Font is Liberation Mono, font style Regular, font size 9 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412135] New: Asan crash while painting.
https://bugs.kde.org/show_bug.cgi?id=412135 Bug ID: 412135 Summary: Asan crash while painting. Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Tile manager Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com Target Milestone: --- I got this when painting, I had just merged master to my branch. Have not tried to reproduce. = ==19028==ERROR: AddressSanitizer: heap-use-after-free on address 0x61145650 at pc 0x7f55fac41129 bp 0x7f558fe649c0 sp 0x7f558fe649b0 READ of size 8 at 0x61145650 thread T807 (Thread (pooled)) #0 0x7f55fac41128 in std::__atomic_base::load(std::memory_order) const /usr/include/c++/7/bits/atomic_base.h:396 #1 0x7f55fac41128 in Atomic::load(MemoryOrder) const /home/wolthera/krita/src/libs/image/3rdparty/lock_free_map/atomic.h:91 #2 0x7f55fac3fe56 in SimpleJobCoordinator::loadConsume() const /home/wolthera/krita/src/libs/image/3rdparty/lock_free_map/simple_job_coordinator.h:46 #3 0x7f55fac6471d in ConcurrentMap, DefaultValueTraits >::migrationInProcess() /home/wolthera/krita/src/libs/image/3rdparty/lock_free_map/concurrent_map.h:51 #4 0x7f55fac5a03f in KisTileHashTableTraits2::getTileLazy(int, int, bool&) (/home/wolthera/krita/inst/lib/x86_64-linux-gnu/libkritaimage.so.19+0x46403f) #5 0x7f55fac58008 in KisTiledDataManager::getTile(int, int, bool) /home/wolthera/krita/src/libs/image/tiles3/swap/../kis_tiled_data_manager.h:120 #6 0x7f55fac8e1e0 in KisTiledDataManager::getTilesPair(int, int, bool, KisSharedPtr*, KisSharedPtr*) /home/wolthera/krita/src/libs/image/tiles3/kis_tiled_data_manager.h:107 #7 0x7f55fac99deb in KisRandomAccessor2::fetchTileData(int, int) /home/wolthera/krita/src/libs/image/tiles3/kis_random_accessor.cc:122 #8 0x7f55fac99a0d in KisRandomAccessor2::moveTo(int, int) /home/wolthera/krita/src/libs/image/tiles3/kis_random_accessor.cc:89 #9 0x7f55fac98d74 in KisRandomAccessor2::KisRandomAccessor2(KisTiledDataManager*, int, int, int, int, bool, KisIteratorCompleteListener*) /home/wolthera/krita/src/libs/image/tiles3/kis_random_accessor.cc:38 #10 0x7f55fb482bde in KisPaintDevice::Private::KisPaintDeviceStrategy::createRandomAccessorNG(int, int) /home/wolthera/krita/src/libs/image/kis_paint_device_strategies.h:111 #11 0x7f55fb46a840 in KisPaintDevice::createRandomAccessorNG(int, int) /home/wolthera/krita/src/libs/image/kis_paint_device.cc:1786 #12 0x7f55fad185bc in KisPainter::bltFixed(QRect const&, QList) /home/wolthera/krita/src/libs/image/kis_painter_blt_multi_fixed.cpp:180 #13 0x7f55bb2e2d87 in operator() /home/wolthera/krita/src/plugins/paintops/defaultpaintops/brush/kis_brushop.cpp:318 #14 0x7f55bb2e81ae in _M_invoke /usr/include/c++/7/bits/std_function.h:316 #15 0x7f55ff391915 in std::function::operator()() const /usr/include/c++/7/bits/std_function.h:706 #16 0x7f55fb03cca2 in KisRunnableStrokeJobData::run() /home/wolthera/krita/src/libs/image/KisRunnableStrokeJobData.cpp:46 #17 0x7f55fb03ae95 in KisRunnableBasedStrokeStrategy::doStrokeCallback(KisStrokeJobData*) /home/wolthera/krita/src/libs/image/KisRunnableBasedStrokeStrategy.cpp:73 #18 0x7f55ff39848c in FreehandStrokeStrategy::doStrokeCallback(KisStrokeJobData*) /home/wolthera/krita/src/libs/ui/tool/strokes/freehand_stroke.cpp:220 #19 0x7f55fb033b0d in SimpleStrokeJobStrategy::run(KisStrokeJobData*) /home/wolthera/krita/src/libs/image/kis_simple_stroke_strategy.cpp:51 #20 0x7f55fb045aa6 in KisStrokeJob::run() /home/wolthera/krita/src/libs/image/kis_stroke_job.h:44 #21 0x7f55fb6bf27e in KisUpdateJobItem::run() /home/wolthera/krita/build/libs/image/kritaimage_autogen/EWIEGA46WW/../../../../../src/libs/image/kis_update_job_item.h:91 #22 0x7f55f85063e1 (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0xac3e1) #23 0x7f55f8501c71 (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0xa7c71) #24 0x7f55f74a46da in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x76da) #25 0x7f55f7be988e in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x12188e) 0x61145650 is located 16 bytes inside of 184-byte region [0x61145640,0x611456f8) freed by thread T801 (Thread (pooled)) here: #0 0x7f560429b7b8 in __interceptor_free (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xde7b8) #1 0x7f55fac6ac73 in Leapfrog, DefaultValueTraits > >::Table::destroy() /home/wolthera/krita/src/libs/image/3rdparty/lock_free_map/leapfrog.h:86 #2 0x7f55fac702ca in Leapfrog, DefaultValueTraits > >::TableMigration::destroy() /home/wolthera/krita/src/libs/image/3rdparty/lock_free_map/leapfrog.h:142 #3 0x7f55fac70427 in void QSBR::enqueue, DefaultValueTraits > >::TableMigration>(void (Leapfrog, DefaultValueTraits > >::TableMigration::*)(), Leapfrog, DefaultValueTraits >
[calligraplan] [Bug 412134] New: add option to specify duration in minutes
https://bugs.kde.org/show_bug.cgi?id=412134 Bug ID: 412134 Summary: add option to specify duration in minutes Product: calligraplan Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: usability Assignee: dand...@get2net.dk Reporter: jose1...@gmail.com Target Milestone: --- SUMMARY It is impossible to use minutes as units of duration. Although internally it seems calligraplan can work with minutes (when editing directly in the xml) it is currently not possible to enter minutes (e. g. "10m") via GUI. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 411958] Import fails with LANG=DE
https://bugs.kde.org/show_bug.cgi?id=411958 --- Comment #8 from Stephane MANKOWSKI --- Nothing interesting in trace file. I'm still not able to reproduce it. The problem seems to be linked to the association of the account on the operation. Could you help me to reproduce it? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412072] Multimedia Controls - VLC\Media player multiple instance out of sync
https://bugs.kde.org/show_bug.cgi?id=412072 --- Comment #5 from J --- (In reply to Matthijs Tijink from comment #4) > Turns out that this bug hasn't been reported to VLC yet (I thought it had), > so see https://trac.videolan.org/vlc/ticket/22785 Thank you for raising the issue with VLC highly appreciated -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412074] Multimedia Controls - Process Name\Multiple Instances
https://bugs.kde.org/show_bug.cgi?id=412074 --- Comment #4 from J --- (In reply to Matthijs Tijink from comment #3) > We don't have the filename, but we can add the other things. Anything is good at this point, although i think title is sufficient enough. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412093] [plasmashell][plasmashell_process] Multiple repetitive crashes
https://bugs.kde.org/show_bug.cgi?id=412093 --- Comment #2 from temptem...@gmail.com --- (In reply to David Edmundson from comment #1) > Crashes need a backtrace. > Please attach inline as an attachment. Coredumps included in original message in ADDITIONAL INFORMATION section. --- Reading symbols from /usr/bin/plasmashell... (No debugging symbols found in /usr/bin/plasmashell) [New LWP 12543] [New LWP 12551] [New LWP 12544] [New LWP 12559] [New LWP 12548] [New LWP 12562] [New LWP 12565] [New LWP 12552] [New LWP 12587] [New LWP 12579] [New LWP 12558] [New LWP 12560] [New LWP 12553] [New LWP 12625] [New LWP 12621] [New LWP 12573] [New LWP 12570] [New LWP 12563] [New LWP 12556] [New LWP 12550] [New LWP 12569] [New LWP 12546] [New LWP 12557] [New LWP 12561] [New LWP 12554] [New LWP 12564] [New LWP 12549] [New LWP 12568] [New LWP 12555] [New LWP 12588] [New LWP 12545] [New LWP 12620] [New LWP 12574] [New LWP 12547] [New LWP 12624] [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Core was generated by `plasmashell'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f5c6196f042 in QTextEngine::validate() const () from /usr/lib/libQt5Gui.so.5 [Current thread is 1 (Thread 0x7f5c5c80e880 (LWP 12543))] (gdb) bt #0 0x7f5c6196f042 in QTextEngine::validate() const () at /usr/lib/libQt5Gui.so.5 #1 0x7f5c61975d52 in QTextEngine::itemize() const () at /usr/lib/libQt5Gui.so.5 #2 0x7f5c6197856f in QTextEngine::attributes() const () at /usr/lib/libQt5Gui.so.5 #3 0x7f5c619867b6 in QTextLine::cursorToX(int*, QTextLine::Edge) const () at /usr/lib/libQt5Gui.so.5 #4 0x7f5c631ca604 in () at /usr/lib/libQt5Quick.so.5 #5 0x7f5c631cab46 in () at /usr/lib/libQt5Quick.so.5 #6 0x7f5c631cb429 in () at /usr/lib/libQt5Quick.so.5 #7 0x7f5c631d34fe in QQuickTextEdit::cursorRectangle() const () at /usr/lib/libQt5Quick.so.5 #8 0x7f5c631d92cd in () at /usr/lib/libQt5Quick.so.5 #9 0x7f5c631d9bdb in QQuickTextEdit::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib/libQt5Quick.so.5 #10 0x7f5c62d74af3 in () at /usr/lib/libQt5Qml.so.5 #11 0x7f5c62d75061 in QV4::QQmlValueTypeWrapper::lookupGetter(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value const&) () at /usr/lib/libQt5Qml.so.5 #12 0x7f5bcc848708 in () #13 0x in () -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 411599] Open/Save dialog is much too small by default
https://bugs.kde.org/show_bug.cgi?id=411599 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412113] Permanent error
https://bugs.kde.org/show_bug.cgi?id=412113 --- Comment #3 from Maik Qualmann --- I can not reproduce a problem with the official digiKam-6.3.0 packages from openSUSE Tumbleweed. I have an AMD graphics card with "radeon" driver. Which graphics card / driver do you use? Check mixing of installed packages from different repositories. Maik -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412127] "KDE-Story (1.0) - 0 B" appears each time Discover reports updates are needed, even when no other updates needed.
https://bugs.kde.org/show_bug.cgi?id=412127 --- Comment #2 from Mitchell McClure --- I'm a bit of a linux newb; sorry. Does you mean when the next new Ubuntu(LTS) is released, that I will get this fix? --- Comment #1 from Nate Graham --- This was fixed in a later version but could not be backported, sorry. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412133] New: Discover crashes if I select any node on the left side
https://bugs.kde.org/show_bug.cgi?id=412133 Bug ID: 412133 Summary: Discover crashes if I select any node on the left side Product: Discover Version: 5.16.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: luwolte...@googlemail.com CC: aleix...@kde.org Target Milestone: --- Operating System: KDE neon 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: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz Memory: 7,8 GiB --- Icon theme "elementary" not found. Icon theme "deepin" not found. Icon theme "elementary" not found. Icon theme "deepin" not found. invalid kns backend! "/usr/share/knsrcfiles/ksysguard.knsrc" because: "Config group not found! Check your KNS3 installation." adding empty sources model QStandardItemModel(0x5640c71ac280) no packages for "org.kde.plasma.quicklaunch" no packages for "org.kde.plasma.systemloadviewer" no packages for "org.kde.plasma.showActivityManager" no packages for "org.kde.plasma.grouping" no packages for "org.kde.plasma.diskquota" no packages for "org.kde.plasma.timer" no packages for "org.kde.kscreen" no packages for "org.kde.plasma.appmenu" no packages for "timeshift.desktop" no packages for "im.riot.webapp" no packages for "org.kde.plasma.kimpanel" no packages for "org.cockpit_project.cockpit" took really long to fetch KNSBackend(0x5640c7184380, name = "/usr/share/knsrcfiles/kwinscripts.knsrc") took really long to fetch KNSBackend(0x5640c7189070, name = "/usr/share/knsrcfiles/plasmoids.knsrc") took really long to fetch KNSBackend(0x5640c7178000, name = "/usr/share/knsrcfiles/cgctheme.knsrc") took really long to fetch KNSBackend(0x5640c7193a60, name = "/usr/share/knsrcfiles/cgcgtk3.knsrc") took really long to fetch KNSBackend(0x5640c7174550, name = "/usr/share/knsrcfiles/colorschemes.knsrc") took really long to fetch KNSBackend(0x5640c7187cd0, name = "/usr/share/knsrcfiles/konsole.knsrc") took really long to fetch KNSBackend(0x5640c7197c60, name = "/usr/share/knsrcfiles/icons.knsrc") took really long to fetch KNSBackend(0x5640c71ad8e0, name = "/usr/share/knsrcfiles/emoticons.knsrc") took really long to fetch KNSBackend(0x5640c7195e20, name = "/usr/share/knsrcfiles/wallpaperplugin.knsrc") took really long to fetch KNSBackend(0x5640c71b1a80, name = "/usr/share/knsrcfiles/kwineffect.knsrc") qrc:/qml/ApplicationsListPage.qml:144:16: QML ResourcesProxyModel: Binding loop detected for property "sortOrder" KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = plasma-discover path = /usr/bin pid = 2572 KCrash: Arguments: /usr/bin/plasma-discover KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 16 and type 'Read', disabling... QSocketNotifier: Invalid socket 14 and type 'Read', disabling... QSocketNotifier: Invalid socket 32 and type 'Read', disabling... QSocketNotifier: Invalid socket 30 and type 'Read', disabling... QSocketNotifier: Invalid socket 33 and type 'Read', disabling... QSocketNotifier: Invalid socket 23 and type 'Read', disabling... QSocketNotifier: Invalid socket 36 and type 'Read', disabling... QSocketNotifier: Invalid socket 37 and type 'Read', disabling... QSocketNotifier: Invalid socket 39 and type 'Read', disabling... QSocketNotifier: Invalid socket 41 and type 'Read', disabling... QSocketNotifier: Invalid socket 24 and type 'Read', disabling... QSocketNotifier: Invalid socket 38 and type 'Read', disabling... QSocketNotifier: Invalid socket 42 and type 'Read', disabling... QSocketNotifier: Invalid socket 26 and type 'Read', disabling... QSocketNotifier: Invalid socket 40 and type 'Read', disabling... [1] + 2572 suspended (signal) plasma-discover I have already unsuccessfully uninstalled the snap and flatpak backend. Even a reinstallation of the Discover was not successful. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 339160] Running signal handler with alternate stack allocated on current stack crashes callgrind
https://bugs.kde.org/show_bug.cgi?id=339160 Johannes Jordan changed: What|Removed |Added CC||k...@lanrules.de --- Comment #3 from Johannes Jordan --- It appears that because of this problem, we are still not able to run callgrind on mingw32-w64 builds with Wine. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 409575] Python plugins don't load with PySide 5.13
https://bugs.kde.org/show_bug.cgi?id=409575 Chris Hills changed: What|Removed |Added CC||c...@chaz6.com --- Comment #2 from Chris Hills --- I have the same problem loading Python plugins with PySide2 5.13, although Falkon does not crash for me. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412054] Default Sizes can't change
https://bugs.kde.org/show_bug.cgi?id=412054 --- Comment #6 from ludger --- After switching to Breeze, the default size setting is now enabled. When I activate La Capitane again afterwards, the size setting remains active. Apparently a problem with the latest update. Thank you all -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 mthw0 changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #7 from mthw0 --- I also noticed that scrollbars in apps like Thunderbird turn black during app switching, which might be related/caused by the same thing. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412132] New: Crash when switching global theme
https://bugs.kde.org/show_bug.cgi?id=412132 Bug ID: 412132 Summary: Crash when switching global theme Product: systemsettings Version: 5.16.90 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: qr...@protonmail.com Target Milestone: --- Application: systemsettings5 (5.16.90) Qt Version: 5.12.3 Frameworks Version: 5.63.0 Operating System: Linux 5.0.0-29-generic x86_64 Distribution: KDE neon Testing Edition -- Information about the crash: When changing from the default global theme to "Breeze Dark" the System Settings crashed. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb61ed44800 (LWP 1215))] Thread 9 (Thread 0x7fb5ce737700 (LWP 1232)): #0 0x7fb61a294bf9 in __GI___poll (fds=0x7fb5c8004e00, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb61371a5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb61371a6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb61abd7dcb in QEventDispatcherGlib::processEvents (this=0x7fb5c8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fb61ab7903a in QEventLoop::exec (this=this@entry=0x7fb5ce736d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fb61a9a04ca in QThread::exec (this=this@entry=0x55b8c644c2f0) at thread/qthread.cpp:531 #6 0x7fb618759115 in QQmlThreadPrivate::run (this=0x55b8c644c2f0) at qml/ftw/qqmlthread.cpp:148 #7 0x7fb61a9a1c72 in QThreadPrivate::start (arg=0x55b8c644c2f0) at thread/qthread_unix.cpp:361 #8 0x7fb615ad96db in start_thread (arg=0x7fb5ce737700) at pthread_create.c:463 #9 0x7fb61a2a188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fb5d68c7700 (LWP 1225)): #0 0x7fb61a2900b4 in __GI___libc_read (fd=13, buf=0x7fb5d68c6b70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fb61375f2d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb61371a0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb61371a570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb61371a6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb61abd7dcb in QEventDispatcherGlib::processEvents (this=0x7fb5db20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7fb61ab7903a in QEventLoop::exec (this=this@entry=0x7fb5d68c6d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7fb61a9a04ca in QThread::exec (this=this@entry=0x55b8c4ed7460) at thread/qthread.cpp:531 #8 0x7fb618759115 in QQmlThreadPrivate::run (this=0x55b8c4ed7460) at qml/ftw/qqmlthread.cpp:148 #9 0x7fb61a9a1c72 in QThreadPrivate::start (arg=0x55b8c4ed7460) at thread/qthread_unix.cpp:361 #10 0x7fb615ad96db in start_thread (arg=0x7fb5d68c7700) at pthread_create.c:463 #11 0x7fb61a2a188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fb5df325700 (LWP 1224)): #0 0x7fb61a2900b4 in __GI___libc_read (fd=12, buf=0x7fb5df324b70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fb61375f2d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb61371a0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb61371a570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb61371a6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb61abd7dcb in QEventDispatcherGlib::processEvents (this=0x7fb5d8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7fb61ab7903a in QEventLoop::exec (this=this@entry=0x7fb5df324d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7fb61a9a04ca in QThread::exec (this=this@entry=0x55b8c4c61250) at thread/qthread.cpp:531 #8 0x7fb618759115 in QQmlThreadPrivate::run (this=0x55b8c4c61250) at qml/ftw/qqmlthread.cpp:148 #9 0x7fb61a9a1c72 in QThreadPrivate::start (arg=0x55b8c4c61250) at thread/qthread_unix.cpp:361 #10 0x7fb615ad96db in start_thread (arg=0x7fb5df325700) at pthread_create.c:463 #11 0x7fb61a2a188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fb5f5421700 (LWP 1222)): #0 0x7fb615adf9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b8c4b37d5c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55b8c4b37d08, cond=0x55b8c4b37d30) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55b8c4b37d30, mutex=0x55b8c4b37d08) at
[krita] [Bug 398990] Filter layer ignores transparency when merged with layers beneath it
https://bugs.kde.org/show_bug.cgi?id=398990 Raghavendra kamath changed: What|Removed |Added Resolution|NOT A BUG |--- Status|NEEDSINFO |REPORTED Ever confirmed|1 |0 --- Comment #26 from Raghavendra kamath --- Hi Kate, Thank you very much for the images, that makes it clear to understand what you want. >From what I understand you want the filter to only applied to the selected layer and merged down, disregarding the unselected layer, that is the filter should not be applied to the unselected layer and it should be reverted to how it looked without filter. Now as we have told you in previous comment that in krita the filter layers are just like new "layers from visible + the filter applied to them" so we try to keep the output as close to what users see prior to merging. In your scenarios the merged output changes from what you have prior to merging, it might be easy to guess in simple situations like having two three layer and some adjustment layers, but It gets tricky when you'll have filters such as blur or when you'll have more than 10 or 20 layers in between with different blend modes. May I request you to also show us images what photoshop does when you have blur as filter layer, as you had in your first attachment. The design of the filter layer in Krita is different from photoshop's adjustment layers. And krita users are more accustomed to the behaviour that we have now. Changing it will lead to discomfort to many of the krita users who rely on the existing behaviour. Still if you feel like we need to change the behaviour I humbly suggest you to start a discussion topic in forum, so that we can gather more support and opinion from the artists and we will get know what they like. P.S. The bug title can be - [Wish bug] Make filter layer affect only the selected layer when merging down. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398990] Filter layer ignores transparency when merged with layers beneath it
https://bugs.kde.org/show_bug.cgi?id=398990 --- Comment #25 from katearche...@yandex.ru --- (In reply to katearcher89 from comment #23) > > https://imgur.com/a/0GjXguZ > > In photoshop there were the same steps: create a filter layer(an adjustment > layer in a adobe world), select two layers(an adjusment layer and a paint > layer) and hit ctrl-e to merge them. Notice that the adjustments were > transfered only to the layer that was merged with and no additional pixels > were added to the result. I want to note that in photoshop we get exactly what is expected: all the pixels are preserved and no other additional pixels slips in. _And that's the most important point and I can't stress that enough._ The current merging with filter layers of krita is creating new pixels and that is not expected and cannot be expected unless explicitly stated by the user. If I previously altered only color of the pixels why should I have pixels from other layers merged in that I didn't explicitly selected in the first place? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412083] Image previews scaled incorrectly on hidpi
https://bugs.kde.org/show_bug.cgi?id=412083 --- Comment #8 from Maik Qualmann --- Git commit 38c1209c7fcce424d843f3508db6bc8cc39f08a8 by Maik Qualmann. Committed on 20/09/2019 at 17:20. Pushed by mqualmann into branch 'master'. fix get capture points M +2-2core/utilities/imageeditor/widgets/imageregionitem.cpp M +2-2core/utilities/imageeditor/widgets/imageregionwidget.cpp https://invent.kde.org/kde/digikam/commit/38c1209c7fcce424d843f3508db6bc8cc39f08a8 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 412131] New: baloo_file crashes after system startup
https://bugs.kde.org/show_bug.cgi?id=412131 Bug ID: 412131 Summary: baloo_file crashes after system startup Product: frameworks-baloo Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: stefan.bru...@rwth-aachen.de Reporter: joan.herm...@pricetravel.com Target Milestone: --- Created attachment 122769 --> https://bugs.kde.org/attachment.cgi?id=122769=edit Debugger Output SUMMARY It happens on every system startup after boot. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Leap 15.0 KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.45.0 Qt Version: 5.9.4 ADDITIONAL INFORMATION Kernel Version: 4.12.14-lp150.12.70-default -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 411286] Discover crashes after opening and check for update
https://bugs.kde.org/show_bug.cgi?id=411286 David Berry changed: What|Removed |Added CC||dboy...@gmail.com --- Comment #13 from David Berry --- When I uninstalled the plasma-discover-backend-flatpak package the crash does not happen anymore. This is my first bug report. Sorry if it is incomplete. I hope it is helpful. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 106807] 'Full Screen' option should really be in the 'View' menu
https://bugs.kde.org/show_bug.cgi?id=106807
Nate Graham changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/kxm
||lgui/93455f78d78d2002ad0d00
||44036ed13cfd90fbd4
Version Fixed In||5.63
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
--- Comment #29 from Nate Graham ---
Git commit 93455f78d78d2002ad0d0044036ed13cfd90fbd4 by Nate Graham.
Committed on 20/09/2019 at 17:09.
Pushed by ngraham into branch 'master'.
Move "Full Screen Mode" item from Settings menu to View menu
Summary:
This is a pretty longstanding feature request and all the HIG and VDG people
polled
were in favor. Since those were the people requested to sign off on it, it
looks like
we can make the necessary code change now.
FIXED-IN: 5.63
Test Plan: {F7394346, size=full}
Reviewers: #vdg, #frameworks, cfeck, ndavis
Reviewed By: #vdg, ndavis
Subscribers: dfaure, kde-frameworks-devel
Tags: #frameworks
Differential Revision: https://phabricator.kde.org/D24091
M +4-4src/ui_standards.rc
https://commits.kde.org/kxmlgui/93455f78d78d2002ad0d0044036ed13cfd90fbd4
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 398990] Filter layer ignores transparency when merged with layers beneath it
https://bugs.kde.org/show_bug.cgi?id=398990 --- Comment #23 from katearche...@yandex.ru --- (In reply to Raghavendra kamath from comment #20) > @ Kate the filter masks are designed to affect everything beneath them, when > you merge it , it creates a layer similar to what "new layer from visible" > does. perhaps you need filter masks and not filter layer. Well, yes and no. The workflow is kinda the same but since it's a nondestructive workflow I don't want to immediately merge results or to restrict myself to only one layer at the time. It's usually several layers created one after the other and some filter layers in between. At certain points in time I'm merging some of them since they were temporary anyway and pretty much ad-hoc. But I want to retain the ability to tweak them in that time that passes between their creation and the eventual merging. And most certainly I don't want to loose transparency in the process or have some unexpected pixels bleeding through. > > In the scenario of your latest attachement, can you show us images of what > is expected after the merge of two layers (marked in red). Should the filter > be only applied to layer 11 and merged, but then the remaining layer won't > have the filter applied to it. > > Can you show us the resulting merged layer in your ideal case. As in a > screenshot of what the resulting layer should look like would help. Yeah. sure thing. Here is the gallery with krita expected/actual results and I've asked a friend to make the same thing in photoshop so the results of that operation there as well: https://imgur.com/a/0GjXguZ In photoshop there were the same steps: create a filter layer(an adjustment layer in a adobe world), select two layers(an adjusment layer and a paint layer) and hit ctrl-e to merge them. Notice that the adjustments were transfered only to the layer that was merged with and no additional pixels were added to the result. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398990] Filter layer ignores transparency when merged with layers beneath it
https://bugs.kde.org/show_bug.cgi?id=398990 --- Comment #24 from katearche...@yandex.ru --- (In reply to Raghavendra kamath from comment #22) > Hi Kate, > > May I request you to answer to the questions in comment 20 ? > > thank you I was in the process of writing it :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398990] Filter layer ignores transparency when merged with layers beneath it
https://bugs.kde.org/show_bug.cgi?id=398990 Raghavendra kamath changed: What|Removed |Added Status|REOPENED|NEEDSINFO Resolution|--- |NOT A BUG --- Comment #22 from Raghavendra kamath --- Hi Kate, May I request you to answer to the questions in comment 20 ? thank you -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411612] When using Tags Manager and then closing crashes digikam
https://bugs.kde.org/show_bug.cgi?id=411612 --- Comment #24 from caulier.gil...@gmail.com --- Note : under lldb is do not crash when i close tag manager but when i close application as well. So i suspect a race condition here ... Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411612] When using Tags Manager and then closing crashes digikam
https://bugs.kde.org/show_bug.cgi?id=411612 --- Comment #23 from caulier.gil...@gmail.com --- With lldb debugger, there is one interresting info : a pointer is null : 2019-09-20 18:53:04.573370+0200 digikam[49235:1645889] [digikam.general] Using 8 CPU core to run threads 2019-09-20 18:53:04.573599+0200 digikam[49235:1646311] [digikam.general] Action Thread run 1 new jobs 2019-09-20 18:53:04.577944+0200 digikam[49235:1645889] [digikam.general] One job is done 2019-09-20 18:53:04.578123+0200 digikam[49235:1645889] [digikam.general] Cancel Main Thread Process 49235 stopped * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x1) frame #0: 0x0001 error: memory read failed for 0x0 Target 0: (digikam) stopped. (lldb) bt * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x1) * frame #0: 0x0001 frame #1: 0x000103d9d16a QtGui`QGuiApplicationPrivate::processActivatedEvent(QWindowSystemInterfacePrivate::ActivatedWindowEvent*) + 144 frame #2: 0x000103d86998 QtGui`bool QWindowSystemInterfacePrivate::handleWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) + 74 frame #3: 0x000104709245 QtCore`QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) const + 843 frame #4: 0x000114283206 libqcocoa.dylib`___lldb_unnamed_symbol432$$libqcocoa.dylib + 1777 frame #5: 0x7fff430f31b8 Foundation`-[__NSObserver _doit:] + 299 frame #6: 0x7fff40e9a97a CoreFoundation`__CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12 frame #7: 0x7fff40e9a8f4 CoreFoundation`___CFXRegistrationPost_block_invoke + 63 frame #8: 0x7fff40e9a85e CoreFoundation`_CFXRegistrationPost + 404 frame #9: 0x7fff40ea2c8d CoreFoundation`___CFXNotificationPost_block_invoke + 87 frame #10: 0x7fff40e0bc9c CoreFoundation`-[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1834 frame #11: 0x7fff40e0af47 CoreFoundation`_CFXNotificationPost + 840 frame #12: 0x7fff430aeaab Foundation`-[NSNotificationCenter postNotificationName:object:userInfo:] + 66 frame #13: 0x7fff3e65911f AppKit`-[NSWindow resignKeyWindow] + 779 frame #14: 0x7fff3e6b7d5a AppKit`-[NSWindow _orderOutAndCalcKeyWithCounter:stillVisible:docWindow:] + 256 frame #15: 0x7fff3e458990 AppKit`NSPerformVisuallyAtomicChange + 132 frame #16: 0x7fff3e5ce4b3 AppKit`-[NSWindow _doWindowOrderOutWithWithKeyCalc:forCounter:orderingDone:docWindow:] + 80 frame #17: 0x7fff3e5cdf10 AppKit`-[NSWindow _reallyDoOrderWindowOutRelativeTo:findKey:forCounter:force:isModal:] + 423 frame #18: 0x7fff3e57395a AppKit`-[NSWindow _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 172 frame #19: 0x7fff3e572521 AppKit`-[NSWindow _doOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 283 frame #20: 0x7fff3e5723a5 AppKit`-[NSWindow orderWindow:relativeTo:] + 152 frame #21: 0x00011427cb92 libqcocoa.dylib`___lldb_unnamed_symbol308$$libqcocoa.dylib + 1028 frame #22: 0x000103da3926 QtGui`QWindowPrivate::setVisible(bool) + 590 frame #23: 0x0001038c99a5 QtWidgets`QWidgetPrivate::hide_sys() + 173 frame #24: 0x0001038cbd17 QtWidgets`QWidgetPrivate::hide_helper() + 165 frame #25: 0x0001038cc16d QtWidgets`QWidgetPrivate::setVisible(bool) + 377 frame #26: 0x0001038be818 QtWidgets`QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode) + 266 frame #27: 0x000101735895 libdigikamgui.6.4.0.dylib`Digikam::DigikamApp::slotExit() + 21 frame #28: 0x00010171fee7 libdigikamgui.6.4.0.dylib`Digikam::DigikamApp::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 359 frame #29: 0x000104727631 QtCore`QMetaObject::activate(QObject*, int, int, void**) + 2353 frame #30: 0x00010389588d QtWidgets`QAction::activate(QAction::ActionEvent) + 307 frame #31: 0x00010472173e QtCore`QObject::event(QEvent*) + 124 frame #32: 0x00010389cfd3 QtWidgets`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 271 frame #33: 0x00010389e369 QtWidgets`QApplication::notify(QObject*, QEvent*) + 733 frame #34: 0x000104701f40 QtCore`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 154 frame #35: 0x000104702bcd QtCore`QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 495 frame #36: 0x00011429485d libqcocoa.dylib`___lldb_unnamed_symbol715$$libqcocoa.dylib + 183 frame #37: 0x000114294eb7 libqcocoa.dylib`___lldb_unnamed_symbol727$$libqcocoa.dylib + 33 frame #38: 0x7fff40e543bb CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17 frame #39: 0x7fff40e54361
[digikam] [Bug 411612] When using Tags Manager and then closing crashes digikam
https://bugs.kde.org/show_bug.cgi?id=411612 --- Comment #22 from caulier.gil...@gmail.com --- Note : Macos 10.14.6, last updates installed. digiKam is now compiled with KF5 5.61 and Qt 5.12.5 Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411612] When using Tags Manager and then closing crashes digikam
https://bugs.kde.org/show_bug.cgi?id=411612 --- Comment #21 from caulier.gil...@gmail.com --- Fully reproducible. Here tag manager crash when i close the windows of tags manager as well: digikam.general: Using 8 CPU core to run threads digikam.general: Action Thread run 1 new jobs digikam.general: Cancel Main Thread digikam.general: One job is done digikam.general: Cancel Main Thread digikam.database: items to tag () digikam.database: Complete scan took: 4169 msecs. digikam.general: Event is dispatched to OSX desktop notifier QFSFileEngine::open: No file name specified digikam.databaseserver: Running 30 seconds... Segmentation fault: 11 The backtrace : Process: digikam [49188] Path: /opt/digikam/*/digikam.app/Contents/MacOS/./digikam Identifier:digikam Version: 6.4.0 (6.4.0-git) Code Type: X86-64 (Native) Parent Process:bash [49175] Responsible: digikam [49188] User ID: 501 Date/Time: 2019-09-20 18:46:03.896 +0200 OS Version:Mac OS X 10.14.6 (18G95) Report Version:12 Anonymous UUID:070280B9-577B-F1B8-0545-8D7E1B44173A Sleep/Wake UUID: CD79486C-17FB-496D-99AF-AE236190D4C4 Time Awake Since Boot: 18 seconds Time Since Wake: 360 seconds System Integrity Protection: enabled Crashed Thread:0 Dispatch queue: com.apple.main-thread Exception Type:EXC_BAD_ACCESS (SIGSEGV) Exception Codes: EXC_I386_GPFLT Exception Note:EXC_CORPSE_NOTIFY Termination Signal:Segmentation fault: 11 Termination Reason:Namespace SIGNAL, Code 0xb Terminating Process: exc handler [49188] Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 org.qt-project.QtCore 0x00010967e620 QMetaObject::cast(QObject*) const + 24 1 org.qt-project.QtWidgets0x000108822765 QWidget::isActiveWindow() const + 267 2 org.qt-project.QtWidgets0x00010881bd63 QWidget::palette() const + 33 3 org.qt-project.QtWidgets0x000108830184 QWidget::initPainter(QPainter*) const + 26 4 org.qt-project.QtGui0x000108e98eb7 QPainter::initFrom(QPaintDevice const*) + 37 5 org.qt-project.QtGui0x000108e9c0a8 QPainter::begin(QPaintDevice*) + 714 6 org.qt-project.QtGui0x000108e9bdd2 QPainter::QPainter(QPaintDevice*) + 78 7 libdigikamcore.6.4.0.dylib 0x0001056a9212 Digikam::DMultiTabBarTab::paintEvent(QPaintEvent*) + 66 8 org.qt-project.QtWidgets0x00010882bc15 QWidget::event(QEvent*) + 1949 9 org.qt-project.QtWidgets0x0001087fbfd3 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 271 10 org.qt-project.QtWidgets0x0001087fd369 QApplication::notify(QObject*, QEvent*) + 733 11 org.qt-project.QtCore 0x000109679f40 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 154 12 org.qt-project.QtWidgets0x000108825857 QWidgetPrivate::sendPaintEvent(QRegion const&) + 43 13 org.qt-project.QtWidgets0x0001088254ca QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 2366 14 org.qt-project.QtWidgets0x000108825cca QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 1100 15 org.qt-project.QtWidgets0x000108825b73 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 757 16 org.qt-project.QtWidgets0x000108825783 QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 3063 17 org.qt-project.QtWidgets0x000108825cca QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 1100 18 org.qt-project.QtWidgets0x000108825783 QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 3063 19 org.qt-project.QtWidgets0x000108825cca QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 1100 20 org.qt-project.QtWidgets0x000108825b73 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 757 21 org.qt-project.QtWidgets0x000108825b73 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) + 757 22 org.qt-project.QtWidgets0x000108825783 QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&,
[Skanlite] [Bug 412130] New: Can't save to PDF
https://bugs.kde.org/show_bug.cgi?id=412130 Bug ID: 412130 Summary: Can't save to PDF Product: Skanlite Version: 2.1.0.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: t...@todddailey.ca Target Milestone: --- SUMMARY The year is 2019 and skanlite can't save to PDF. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412127] "KDE-Story (1.0) - 0 B" appears each time Discover reports updates are needed, even when no other updates needed.
https://bugs.kde.org/show_bug.cgi?id=412127 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- This was fixed in a later version but could not be backported, sorry. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 411936] After upgrade to PulseAudio 13, Plasma changes the default output device to HDMI port after every login and after I wake up my monitor connected to HDMI port from power save m
https://bugs.kde.org/show_bug.cgi?id=411936 Patrick Silva changed: What|Removed |Added Summary|After upgrade to|After upgrade to PulseAudio |PulseaAudio 13, Plasma |13, Plasma changes the |changes the default output |default output device to |device to HDMI port after |HDMI port after every login |every login and after I |and after I wake up my |wake up my monitor |monitor connected to HDMI |connected to HDMI port from |port from power save mode |power save mode | Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Patrick Silva --- I solved this problem on my system by renaming pulseaudio config files and reinstalling pulseaudio. Furthermore, this problem did not occur on Void Linux running Plasma 5.16.5 after upgrade to pulseaudio 13. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 412124] Activation of application window using krunner fails
https://bugs.kde.org/show_bug.cgi?id=412124 Nate Graham changed: What|Removed |Added CC||n...@kde.org Keywords||regression Priority|NOR |HI Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Severity|normal |major --- Comment #1 from Nate Graham --- Yep, broken for me too. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 --- Comment #6 from Patrick Silva --- (In reply to mthw0 from comment #4) > @Patrick Silva, do you have this issue too? I remember you using Plasma Beta > on Arch Linux. Yes, it occurs when I hover over gtk radio buttons and checkboxes. I use breeze color scheme. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 412087] Tiny standalone plasma-pa KCM
https://bugs.kde.org/show_bug.cgi?id=412087 Nate Graham changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-pa/05fa3f20d786f2c8c135 ||f60254f9e9fe094096a2 Status|CONFIRMED |RESOLVED Version Fixed In||5.17.0 Resolution|--- |FIXED --- Comment #1 from Nate Graham --- Git commit 05fa3f20d786f2c8c135f60254f9e9fe094096a2 by Nate Graham. Committed on 20/09/2019 at 16:28. Pushed by ngraham into branch 'Plasma/5.17'. Fix kcmshell window being too small FIXED-IN: 5.17.0 M +1-0src/kcm/package/contents/ui/main.qml https://commits.kde.org/plasma-pa/05fa3f20d786f2c8c135f60254f9e9fe094096a2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 412087] Tiny standalone plasma-pa KCM
https://bugs.kde.org/show_bug.cgi?id=412087 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412086] Several Standalone KCMs have badly rendered fonts with fractional display scaling on Wayland until their windows are resized
https://bugs.kde.org/show_bug.cgi?id=412086 Nate Graham changed: What|Removed |Added CC||n...@kde.org, ||subd...@gmail.com Assignee|plasma-b...@kde.org |kdelibs-b...@kde.org Component|general |kcmshell -- You are receiving this mail because: You are watching all bug changes.
