[krita] [Bug 408481] 'Stroke Selection' creates thick lines when the application language is set to Korean
https://bugs.kde.org/show_bug.cgi?id=408481 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/0b9fe0f1f0aa8b |krita/commit/b4eb07b7e4af46 |2b0a92b8ec1903dc29d96f9519 |a59d41b7c8c409e2ba65bd55d8 --- Comment #6 from Boudewijn Rempt --- Git commit b4eb07b7e4af46a59d41b7c8c409e2ba65bd55d8 by Boudewijn Rempt. Committed on 13/06/2019 at 05:59. Pushed by rempt into branch 'krita/4.2'. Do not compare translated and untranslated strings BACKPORT:krita/4.2 (cherry picked from commit 0b9fe0f1f0aa8b2b0a92b8ec1903dc29d96f9519) M +2-2libs/ui/dialogs/kis_dlg_stroke_selection_properties.cpp https://invent.kde.org/kde/krita/commit/b4eb07b7e4af46a59d41b7c8c409e2ba65bd55d8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408171] Filter layer properties layer name textbox not correctly themed in Windows
https://bugs.kde.org/show_bug.cgi?id=408171 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/68135ff05e583e |krita/commit/edd51c6b251158 |855aafcd5758c1fc049ece9d3a |3f0b5e3a97a0494484c94e298b --- Comment #5 from Boudewijn Rempt --- Git commit edd51c6b2511583f0b5e3a97a0494484c94e298b by Boudewijn Rempt. Committed on 13/06/2019 at 05:59. Pushed by rempt into branch 'krita/4.2'. Remove the last use of KLineEdit BACKPORT:krita/4.2 (cherry picked from commit 68135ff05e583e855aafcd5758c1fc049ece9d3a) M +2-3libs/ui/dialogs/kis_dlg_adj_layer_props.cc https://invent.kde.org/kde/krita/commit/edd51c6b2511583f0b5e3a97a0494484c94e298b -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407646] Onion skin docker minimum fixed width too wide
https://bugs.kde.org/show_bug.cgi?id=407646 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/f7971aab564673 |krita/commit/12118c1aa516d4 |85ab5348b9dca27c0bea68b189 |7e29f94bd05311f1b7d8aec311 --- Comment #5 from Boudewijn Rempt --- Git commit 12118c1aa516d47e29f94bd05311f1b7d8aec311 by Boudewijn Rempt, on behalf of Scott Petrovic. Committed on 13/06/2019 at 06:00. Pushed by rempt into branch 'krita/4.2'. M +1-0plugins/dockers/animation/kis_equalizer_widget.cpp M +15 -0plugins/dockers/animation/onion_skins_docker.cpp M +33 -1plugins/dockers/animation/onion_skins_docker.ui https://invent.kde.org/kde/krita/commit/12118c1aa516d47e29f94bd05311f1b7d8aec311 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408169] Transparent pattern fill layer renders incorrect on load
https://bugs.kde.org/show_bug.cgi?id=408169 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/92a9a440f3a987 |krita/commit/e8b0a914257ed1 |6678ea309bf984467b33157406 |5c465eba1462aeb3b6ce92ef79 --- Comment #4 from Boudewijn Rempt --- Git commit e8b0a914257ed15c465eba1462aeb3b6ce92ef79 by Boudewijn Rempt, on behalf of Ivan Yossi. Committed on 13/06/2019 at 06:00. Pushed by rempt into branch 'krita/4.2'. Remove update on creating a generator fill layer. This avoids drawing the path twice on load, update is made only from setFilter which is also called on document load. If done from the creator it draws the default pattern first and then overlays the saved pattern. M +0-1libs/image/generator/kis_generator_layer.cpp https://invent.kde.org/kde/krita/commit/e8b0a914257ed15c465eba1462aeb3b6ce92ef79 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408400] krita scripter does not work
https://bugs.kde.org/show_bug.cgi?id=408400 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/855e33784e248b |krita/commit/d13657d44e22fa |75b8f1694d2716359c71a93ebf |5cb238b81ff6724669d0ee6f49 --- Comment #6 from Boudewijn Rempt --- Git commit d13657d44e22fa5cb238b81ff6724669d0ee6f49 by Boudewijn Rempt. Committed on 13/06/2019 at 06:02. Pushed by rempt into branch 'krita/4.2'. Look up the parent by translated name This fixes loading the scripter when not everything has been translated yet. M +1-1plugins/python/scripter/uicontroller.py https://invent.kde.org/kde/krita/commit/d13657d44e22fa5cb238b81ff6724669d0ee6f49 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408177] Assert saving lab to tiff. [GDB backtrace]
https://bugs.kde.org/show_bug.cgi?id=408177 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/037a1d75ddfe00 |krita/commit/3d1a4b0c63d732 |926707abc97ab5e12c58a72f86 |5835771b4a6f01af8296250c19 --- Comment #6 from Boudewijn Rempt --- Git commit 3d1a4b0c63d7325835771b4a6f01af8296250c19 by Boudewijn Rempt, on behalf of Agata Cacko. Committed on 13/06/2019 at 06:00. Pushed by rempt into branch 'krita/4.2'. Remove wrongly placed assert in tiff export Previous version of tiff export assumed that if visitor returns false it means internal error, a bug in the code. Truth is, it can happen also if the image (or layer) has an unsupported color space. Hence deletion of the assert and replacement InternalError error code with just Failure. M +2-2plugins/impex/tiff/kis_tiff_converter.cc https://invent.kde.org/kde/krita/commit/3d1a4b0c63d7325835771b4a6f01af8296250c19 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408442] Fuzziness slider on the Magic Wand tool increases when dragging left past zero
https://bugs.kde.org/show_bug.cgi?id=408442 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/e4c9d1623ed4ee |krita/commit/dd1473ec5471ec |d5ed4f7643d603ee91cd1aad4c |ec6663618d0637ec51007c859f --- Comment #2 from Boudewijn Rempt --- Git commit dd1473ec5471ecec6663618d0637ec51007c859f by Boudewijn Rempt, on behalf of Ivan Yossi. Committed on 13/06/2019 at 06:00. Pushed by rempt into branch 'krita/4.2'. Avoid going positive on negative x with even exponentials ratios M +2-1libs/ui/widgets/kis_slider_spin_box.cpp https://invent.kde.org/kde/krita/commit/dd1473ec5471ecec6663618d0637ec51007c859f -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408441] Deleting all the text in the 'Edit Text' box returns the font to default settings. Changing font settings with no text present will revert to default settings when typing.
https://bugs.kde.org/show_bug.cgi?id=408441 --- Comment #3 from Boudewijn Rempt --- Git commit 48922b3058b2653a5053a64d517a7cf9294bd244 by Boudewijn Rempt. Committed on 13/06/2019 at 06:02. Pushed by rempt into branch 'krita/4.2'. Give the text editor a clearer window title M +1-0plugins/tools/svgtexttool/SvgTextTool.cpp https://invent.kde.org/kde/krita/commit/48922b3058b2653a5053a64d517a7cf9294bd244 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408447] Krita can't launch and do floating point exception
https://bugs.kde.org/show_bug.cgi?id=408447 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/5efcaf69c85ffb |krita/commit/86caaa72fda982 |9c16343e51fc1a37a418d6f8fa |b8a3a02da1c24a3d6cd7f34517 --- Comment #4 from Boudewijn Rempt --- Git commit 86caaa72fda982b8a3a02da1c24a3d6cd7f34517 by Boudewijn Rempt. Committed on 13/06/2019 at 05:59. Pushed by rempt into branch 'krita/4.2'. Don't divide 0 by 0 when trying to load a broken kpl file BACKPORT:krita/4.2 (cherry picked from commit 5efcaf69c85ffb9c16343e51fc1a37a418d6f8fa) M +2-2libs/pigment/resources/KoColorSet.cpp https://invent.kde.org/kde/krita/commit/86caaa72fda982b8a3a02da1c24a3d6cd7f34517 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407554] Crashed when creating a text after autosaving on a document has a selection somewhere
https://bugs.kde.org/show_bug.cgi?id=407554 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/eb61160966ddc7 |krita/commit/94065177379800 |94cfd02a9225e577f0844e51e0 |0c7fcdc7e6d811f52fe4c2a117 --- Comment #16 from Boudewijn Rempt --- Git commit 940651773798000c7fcdc7e6d811f52fe4c2a117 by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 13/06/2019 at 05:59. Pushed by rempt into branch 'krita/4.2'. Fix a crash when creating a text shape Every KoShapeController used to reset the global "shape document" in its KoDocumentResourceManager. The problem is that in Krita we have multiple KoShapeController-s, but the resource manager is the only one. It means that every shape selection or shape layer used to reset the pointer to the global "shape document" to its own one. The only reason why we didn't have too many crashes is that almost noone uses this "shape document". Ideally we should: 1) Remove KoDocumentResourceManager::GlobalShapeController resource. This resource is not global to the document, but is created per-layer. The only user of it atm is the legacy text tool, which should be deprecated. 2) Remove KoDocumentResourceManager at all. There is no much use of it anymore. Its main user is legacy text tool. M +18 -5libs/flake/KoDocumentResourceManager.cpp M +13 -3libs/flake/KoDocumentResourceManager.h M +0-3libs/flake/KoShapeController.cpp M +1-1libs/flake/KoShapeRegistry.cpp M +1-1libs/flake/tests/TestKoShapeRegistry.cpp M +2-4libs/flake/text/KoSvgTextShape.cpp M +9-6libs/ui/KisDocument.cpp M +1-1libs/ui/flake/kis_dummies_facade_base.h M +26 -0libs/ui/flake/kis_shape_controller.cpp M +6-0libs/ui/flake/kis_shape_controller.h M +1-1plugins/flake/textshape/TextShapeFactory.cpp https://invent.kde.org/kde/krita/commit/940651773798000c7fcdc7e6d811f52fe4c2a117 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408481] 'Stroke Selection' creates thick lines when the application language is set to Korean
https://bugs.kde.org/show_bug.cgi?id=408481 --- Comment #7 from Boudewijn Rempt --- Git commit 871f64c291ec585b4c68463102640e6b45a0856c by Boudewijn Rempt. Committed on 13/06/2019 at 06:01. Pushed by rempt into branch 'krita/4.2'. Convert assert to a safe assert If we know what the value should be, we can use that and not crap out. M +4-2libs/image/kis_painter.cc https://invent.kde.org/kde/krita/commit/871f64c291ec585b4c68463102640e6b45a0856c -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408459] SIGSEGV when choosing text tool
https://bugs.kde.org/show_bug.cgi?id=408459 Dmitry Kazakov changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||dimul...@gmail.com --- Comment #5 from Dmitry Kazakov --- The bug was fixed in this commit: https://invent.kde.org/kde/krita/commit/eb61160966ddc794cfd02a9225e577f0844e51e0 *** This bug has been marked as a duplicate of bug 407554 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407554] Crashed when creating a text after autosaving on a document has a selection somewhere
https://bugs.kde.org/show_bug.cgi?id=407554 Dmitry Kazakov changed: What|Removed |Added CC||epicwraths...@yandex.ru --- Comment #15 from Dmitry Kazakov --- *** Bug 408459 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408636] New: The horizontal dividing line between the timeline and the top of the kdenlive window does not save the position after dragging down in Kubuntu 18
https://bugs.kde.org/show_bug.cgi?id=408636 Bug ID: 408636 Summary: The horizontal dividing line between the timeline and the top of the kdenlive window does not save the position after dragging down in Kubuntu 18 Product: kdenlive Version: 19.04.2 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: iticdig...@disroot.org Target Milestone: --- STEPS TO REPRODUCE 1. Open kdenlive 2. Pull down the horizontal dividing line above the timeline, which determines the ratio between the height of the timeline and the project monitor. OBSERVED RESULT The dividing strip jumps back up is not. The height of the timeline does not decrease, the height of the project monitor does not increase. EXPECTED RESULT The dividing line should remain where I dragged it (lower than it was). The height of the timeline should decrease, the height of the project monitor should increase. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 64-bit (available in About System) KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 Kdenlive appimage 19.04.2d_x86-x64 ADDITIONAL INFORMATION This behavior is observed only on Kubuntu 18.04. Before that, he worked under Ubuntu Studio 04/18/1 (xfce) - the dividing line worked fine. For me, this bug is critical, as it makes it impossible to quickly view clips in a window of sufficient size. By default, the dividing line is too high (above the middle of the window) due to which the project monitor becomes too small. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408459] SIGSEGV when choosing text tool
https://bugs.kde.org/show_bug.cgi?id=408459 --- Comment #4 from Boudewijn Rempt --- No... A debug build wouldn't be more useful. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408629] Entering Audio Files for Animation doesn't play, and skips.
https://bugs.kde.org/show_bug.cgi?id=408629 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Boudewijn Rempt --- *** This bug has been marked as a duplicate of bug 385589 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385589] Audio glitching in animation
https://bugs.kde.org/show_bug.cgi?id=385589 --- Comment #7 from Boudewijn Rempt --- *** Bug 408629 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 403838] ScrollablePage should conditionally allow re-positioning the window by clicking-and-dragging on the background on desktop
https://bugs.kde.org/show_bug.cgi?id=403838 Björn Feber changed: What|Removed |Added CC||ongun.ka...@gmail.com --- Comment #3 from Björn Feber --- *** Bug 408628 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 408628] Dragging windows from empty areas doesn't work with QML/QQC2 applications.
https://bugs.kde.org/show_bug.cgi?id=408628 Björn Feber changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bfe...@protonmail.com Status|REPORTED|RESOLVED --- Comment #3 from Björn Feber --- *** This bug has been marked as a duplicate of bug 403838 *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408635] New: libc wrong version
https://bugs.kde.org/show_bug.cgi?id=408635 Bug ID: 408635 Summary: libc wrong version Product: kdenlive Version: 19.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: essj...@outlook.com Target Milestone: --- Created attachment 120837 --> https://bugs.kde.org/attachment.cgi?id=120837&action=edit Wrong libc version SUMMARY Can't install because "Error: Dependency is not satisfiable: Libc (>=2.29) SOFTWARE/OS VERSIONS Linux Mint 19.1 Cinnamon 4.0.10 ADDITIONAL INFORMATION See attachment -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408634] [Wayland] Nvidia Black Screen
https://bugs.kde.org/show_bug.cgi?id=408634 --- Comment #3 from Wyatt Childers --- Also just to rule it out, tried creating a completely new user, and seeing if I could reproduce using that user. The behavior was effectively the same with login through SDDM, and presumably though kwin_wayland --xwayland -- I did not wait for it to become responsive, but the initial error set shown in attachment 120835 was the same. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408634] [Wayland] Nvidia Black Screen
https://bugs.kde.org/show_bug.cgi?id=408634 --- Comment #2 from Wyatt Childers --- Created attachment 120836 --> https://bugs.kde.org/attachment.cgi?id=120836&action=edit output after initial screen This is the output including both the initial output, and the output presented whenever the screen unfreezes, and renders something meaningful. It always begins with "lock called" and ends with "Grab Released". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408634] [Wayland] Nvidia Black Screen
https://bugs.kde.org/show_bug.cgi?id=408634 --- Comment #1 from Wyatt Childers --- Created attachment 120835 --> https://bugs.kde.org/attachment.cgi?id=120835&action=edit text log of text before initial screen rendering This is the output when running kwin_wayland --xwayland before it renders an initial screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408634] New: [Wayland] Nvidia Black Screen
https://bugs.kde.org/show_bug.cgi?id=408634 Bug ID: 408634 Summary: [Wayland] Nvidia Black Screen Product: kwin Version: 5.16.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: dark...@nearce.com Target Milestone: --- SUMMARY I've got an nvidia 2080 running on the nvidia 430 driver. When I attempt to use the recently released kwin 5.16 I still get a black screen. It seems if I run kwin_wayland --xwayland it hangs, then after some time it will render the screen. If it sits long enough, I can enter my password, and login, however, that seems to return to a black screen. This behavior occurs with `KWIN_DRM_USE_EGL_STREAMS=2` in the environment, without nvidia-drm.modeset=1 explicitly set in the boot params. When I try via SDDM, if I have nvidia-drm.modeset=1 set, when I login, I get a mouse cursor, that's frozen and can't move on a black screen. If the nvidia-drm.modeset=1 is not present, I instead get a black screen, normally with an _ in the top right, or some seemingly random message. I'm assuming this is related to tty1's dmesg text. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Workspace Wallpapers] [Bug 408633] New: thin vertical line when wallpaper is scaled and cropped
https://bugs.kde.org/show_bug.cgi?id=408633 Bug ID: 408633 Summary: thin vertical line when wallpaper is scaled and cropped Product: Plasma Workspace Wallpapers Version: 5.16.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: susuthapa19961...@gmail.com Target Milestone: --- Created attachment 120834 --> https://bugs.kde.org/attachment.cgi?id=120834&action=edit here you can see in the left, there is a thin vertical line thin vertical line when wallpaper is scaled and cropped STEPS TO REPRODUCE 1. set the positioning of the wallpaper to "scaled and cropped" 2. select any background color other than "black" 3. OBSERVED RESULT A thin vertical line on the left side of the screen EXPECTED RESULT Wallpaper taking the entire screen width and height SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.16 KDE Frameworks Version: 5.59 Qt Version: 5.12.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408073] scroll bar is glitchy when used over the express key
https://bugs.kde.org/show_bug.cgi?id=408073 --- 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 408072] The pen pressure isnt working in this latest update, the older version before the alpha and beta had the same issue with pen pressure
https://bugs.kde.org/show_bug.cgi?id=408072 --- 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 408439] Outline selection tool not working properly
https://bugs.kde.org/show_bug.cgi?id=408439 Bug Janitor Service changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 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.
[cantor] [Bug 402176] Cantor crashes when trying to execute cell with SageMath backend
https://bugs.kde.org/show_bug.cgi?id=402176 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407995] Crash when play video with "Auto Mask" effect, after cut it
https://bugs.kde.org/show_bug.cgi?id=407995 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 408632] kde-open functions incorrectly when given a URL with a port (opens a URL with port as the line number)
https://bugs.kde.org/show_bug.cgi?id=408632 bugsh...@mailinator.com changed: What|Removed |Added Summary|kde-open functions |kde-open functions |incorrectly when given a|incorrectly when given a |URL with a port |URL with a port (opens a ||URL with port as the line ||number) -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 408632] New: kde-open functions incorrectly when given a URL with a port
https://bugs.kde.org/show_bug.cgi?id=408632 Bug ID: 408632 Summary: kde-open functions incorrectly when given a URL with a port Product: kde-cli-tools Version: 5.16.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: bugsh...@mailinator.com Target Milestone: --- SUMMARY When using `kde-open`/`xdg-open` under Plasma 5.16, giving it a url such as `http://localhost:3000` will cause it to open `http://localhost/?line=3000&column=0` in the web browser. STEPS TO REPRODUCE 1. Run `xdg-open http://localhost:3000` 2. Check the URL that was opened in the browser OBSERVED RESULT The URL `http://localhost/?line=3000&column=0` (port number translated to line number incorrectly) is opened in the web browser. EXPECTED RESULT The given URL (`http://localhost:3000`) should be opened in the web browser. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408566] Notifications Plasmoid on Latte Dock has disappearing icon
https://bugs.kde.org/show_bug.cgi?id=408566 --- Comment #16 from Michail Vourlakos --- (In reply to avlas from comment #15) > (In reply to Michail Vourlakos from comment #11) > > Git commit ec284dbfa8d7f00083e506e1f9a87eb37f835192 by Michail Vourlakos. > > Committed on 12/06/2019 at 20:39. > > Pushed by mvourlakos into branch 'v0.8'. > > > > blacklist plasma notifications in heuristics > > > > --plasma notification applet has become more complex > > lets blacklist it in order to provide the real > > plasma experience and see how it goes > > FIXED-IN: 0.8.9 > > > > M +2-1containment/package/contents/code/AppletIdentifier.js > > > > https://commits.kde.org/latte-dock/ec284dbfa8d7f00083e506e1f9a87eb37f835192 > > Mmm, after applying this change, I don't see any notification anymore :( (In reply to avlas from comment #15) > (In reply to Michail Vourlakos from comment #11) > > Git commit ec284dbfa8d7f00083e506e1f9a87eb37f835192 by Michail Vourlakos. > > Committed on 12/06/2019 at 20:39. > > Pushed by mvourlakos into branch 'v0.8'. > > > > blacklist plasma notifications in heuristics > > > > --plasma notification applet has become more complex > > lets blacklist it in order to provide the real > > plasma experience and see how it goes > > FIXED-IN: 0.8.9 > > > > M +2-1containment/package/contents/code/AppletIdentifier.js > > > > https://commits.kde.org/latte-dock/ec284dbfa8d7f00083e506e1f9a87eb37f835192 > > Mmm, after applying this change, I don't see any notification anymore :( How is this relevant to notification applet not been visible? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 386250] [Wayland] Spectacle opens anyway when you try to cancel out of the window selection UI
https://bugs.kde.org/show_bug.cgi?id=386250 --- Comment #7 from Nate Graham --- (In reply to Boudhayan Gupta from comment #6) > If you cancel out of it, no image is returned, which is why you see > Spectacle with a null image. Could we maybe have Spectacle display a nice message instead of a null image, so the user knows what happened and what do do next? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 408483] "Open containing folder" button does not work as expected
https://bugs.kde.org/show_bug.cgi?id=408483 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #3 from Nate Graham --- Ah OK, this is actually the Dolphin bug. Thankfully the bug has not been released to users yet; it's only in Dolphin from git master. *** This bug has been marked as a duplicate of bug 408244 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408244] "Open Containing Folder" feature only works when Dolphin is already running
https://bugs.kde.org/show_bug.cgi?id=408244 Nate Graham changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #5 from Nate Graham --- *** Bug 408483 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408556] In the timeline, video thumbnails are not visible by using the highest zoom level
https://bugs.kde.org/show_bug.cgi?id=408556 --- Comment #11 from Sebastian Kuhne --- Ok, tested with kdenlive-19.04.2d-x86_64.appimage again: - Used a short mp4 clip (about 8 sec, 21 Mib) - track thumbnails -> all frames - Zoom into max level somewhere in the middle of the clip --> All thumbnails are shown (OK) - Cut the clip with the razor tool somewhere in the middle --> The thumbnails to the right of the cut are again *not* displayed I just submitted three screenshots (clip loaded, max zoom level, after cut). Many thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408556] In the timeline, video thumbnails are not visible by using the highest zoom level
https://bugs.kde.org/show_bug.cgi?id=408556 --- Comment #10 from Sebastian Kuhne --- Created attachment 120833 --> https://bugs.kde.org/attachment.cgi?id=120833&action=edit Screen shot: Loading short clip with max zoom and cut -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408556] In the timeline, video thumbnails are not visible by using the highest zoom level
https://bugs.kde.org/show_bug.cgi?id=408556 --- Comment #9 from Sebastian Kuhne --- Created attachment 120832 --> https://bugs.kde.org/attachment.cgi?id=120832&action=edit Screen shot: Loading short clip with max zoom -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408556] In the timeline, video thumbnails are not visible by using the highest zoom level
https://bugs.kde.org/show_bug.cgi?id=408556 --- Comment #8 from Sebastian Kuhne --- Created attachment 120831 --> https://bugs.kde.org/attachment.cgi?id=120831&action=edit Screen shot: Loading short clip without zoom -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408631] New: Crash when sending Konversation to tray
https://bugs.kde.org/show_bug.cgi?id=408631 Bug ID: 408631 Summary: Crash when sending Konversation to tray Product: plasmashell Version: 5.14.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jsc...@posteo.net CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.14.5) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-5-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: I'm having some trouble reproducing this again, but I hope that my backtrace might shed some light on this. I was using Konversation a few hours ago, having been playing with the On-Screen Display settings. I might've kept the configuration dialog open, but anyway closing the main window made Plasma crash somehow. I'll keep playing with it and update if I can reproduce it. The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc5b6473840 (LWP 753))] Thread 13 (Thread 0x7fc5759dc700 (LWP 9053)): #0 0x7fc5bb476819 in __GI___poll (fds=0x7fc558001b30, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc5b91e6101 in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7fc5b91d7920 in pa_mainloop_poll () from /lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fc5b91d7f6e in pa_mainloop_iterate () from /lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fc5b91d8020 in pa_mainloop_run () from /lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fc5b91e6049 in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fc5b748f4f8 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so #7 0x7fc5ba6abfa3 in start_thread (arg=) at pthread_create.c:486 #8 0x7fc5bb4814cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7fc5768a9700 (LWP 5137)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x5571e5db0a04) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5571e5db09b0, cond=0x5571e5db09d8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5571e5db09d8, mutex=0x5571e5db09b0) at pthread_cond_wait.c:655 #3 0x7fc5bb79025b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x5571e5db09b0) at thread/qwaitcondition_unix.cpp:143 #4 QWaitCondition::wait (this=, mutex=0x5571e5879410, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #5 0x7fc595006d30 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fc59500aae8 in ?? () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fc595005e3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fc59500ab42 in ?? () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7fc595005e3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7fc595008bb9 in ThreadWeaver::Thread::run() () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7fc5bb78faa7 in QThreadPrivate::start (arg=0x7fc570003ce0) at thread/qthread_unix.cpp:367 #12 0x7fc5ba6abfa3 in start_thread (arg=) at pthread_create.c:486 #13 0x7fc5bb4814cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7fc5770aa700 (LWP 5136)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x5571e5db0a04) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5571e5db09b0, cond=0x5571e5db09d8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5571e5db09d8, mutex=0x5571e5db09b0) at pthread_cond_wait.c:655 #3 0x7fc5bb79025b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x5571e5db09b0) at thread/qwaitcondition_unix.cpp:143 #4 QWaitCondition::wait (this=, mutex=0x5571e5879410, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #5 0x7fc595006d30 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fc59500aae8 in ?? () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fc595005e3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fc59500ab42 in ?? () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7fc595005e3d in Thre
[kompare] [Bug 390024] "Compare" button not enabled on the initial dialog even after filling the file names
https://bugs.kde.org/show_bug.cgi?id=390024 Ashark changed: What|Removed |Added CC||ash...@linuxcomp.ru --- Comment #14 from Ashark --- Operating System: Arch Linux KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kompare version: 4.1.3 (19.04.2-1) Still reproducible. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408566] Notifications Plasmoid on Latte Dock has disappearing icon
https://bugs.kde.org/show_bug.cgi?id=408566 --- Comment #15 from avlas --- (In reply to Michail Vourlakos from comment #11) > Git commit ec284dbfa8d7f00083e506e1f9a87eb37f835192 by Michail Vourlakos. > Committed on 12/06/2019 at 20:39. > Pushed by mvourlakos into branch 'v0.8'. > > blacklist plasma notifications in heuristics > > --plasma notification applet has become more complex > lets blacklist it in order to provide the real > plasma experience and see how it goes > FIXED-IN: 0.8.9 > > M +2-1containment/package/contents/code/AppletIdentifier.js > > https://commits.kde.org/latte-dock/ec284dbfa8d7f00083e506e1f9a87eb37f835192 Mmm, after applying this change, I don't see any notification anymore :( -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 408630] Plasma NM sends connection activated notification twice
https://bugs.kde.org/show_bug.cgi?id=408630 Ongun Kanat changed: What|Removed |Added CC||ongun.ka...@gmail.com --- Comment #1 from Ongun Kanat --- Created attachment 120830 --> https://bugs.kde.org/attachment.cgi?id=120830&action=edit dbus-monitor log Command: dbus-monitor interface='org.freedesktop.Notifications' | tee dbus.log -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 408630] New: Plasma NM sends connection activated notification twice
https://bugs.kde.org/show_bug.cgi?id=408630 Bug ID: 408630 Summary: Plasma NM sends connection activated notification twice Product: plasma-nm Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: ongun.ka...@gmail.com Target Milestone: --- Created attachment 120829 --> https://bugs.kde.org/attachment.cgi?id=120829&action=edit Screenshot SUMMARY As in the title. Activating an ethernet connection sends the activation notification twice. Screenshot and dbus-monitor log is attached. OBSERVED RESULT "Connection '' Activated" notification is shown twice. EXPECTED RESULT It should be sent once. SOFTWARE/OS VERSIONS Distro: Arch Linux KDE Plasma Version: 5.16 KDE Frameworks Version: 5.59 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408629] Entering Audio Files for Animation doesn't play, and skips.
https://bugs.kde.org/show_bug.cgi?id=408629 Lindsey changed: What|Removed |Added CC||lynnj122...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385589] Audio glitching in animation
https://bugs.kde.org/show_bug.cgi?id=385589 Lindsey changed: What|Removed |Added CC||lynnj122...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408629] Entering Audio Files for Animation doesn't play, and skips.
https://bugs.kde.org/show_bug.cgi?id=408629 Lindsey changed: What|Removed |Added Alias||Audio -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 408628] Dragging windows from empty areas doesn't work with QML/QQC2 applications.
https://bugs.kde.org/show_bug.cgi?id=408628 Ongun Kanat changed: What|Removed |Added CC||ongun.ka...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 408628] Dragging windows from empty areas doesn't work with QML/QQC2 applications.
https://bugs.kde.org/show_bug.cgi?id=408628 --- Comment #2 from Ongun Kanat --- Created attachment 120828 --> https://bugs.kde.org/attachment.cgi?id=120828&action=edit Test Video 3 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408629] New: Entering Audio Files for Animation doesn't play, and skips.
https://bugs.kde.org/show_bug.cgi?id=408629 Bug ID: 408629 Summary: Entering Audio Files for Animation doesn't play, and skips. Product: krita Version: 4.2.1 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: minor Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: lynnj122...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 408628] Dragging windows from empty areas doesn't work with QML/QQC2 applications.
https://bugs.kde.org/show_bug.cgi?id=408628 --- Comment #1 from Ongun Kanat --- Created attachment 120827 --> https://bugs.kde.org/attachment.cgi?id=120827&action=edit Test Video 2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 408628] New: Dragging windows from empty areas doesn't work with QML/QQC2 applications.
https://bugs.kde.org/show_bug.cgi?id=408628 Bug ID: 408628 Summary: Dragging windows from empty areas doesn't work with QML/QQC2 applications. Product: frameworks-qqc2-desktop-style Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: ongun.ka...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: --- Created attachment 120826 --> https://bugs.kde.org/attachment.cgi?id=120826&action=edit Test Video 1 Breeze theme in QtWidgets provides a neat dragging feature. Users can drag windows by clicking on empty areas. However it isn't possible with apps written in QML. It triggers a scrolling behavior like mobile/touchscreen devices. See attached videos for a simple demo. Distro: Arch Linux KDE Plasma Version: 5.16 KDE Frameworks Version: 5.59 Qt Version: 5.12 -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 373891] Autostart option is without effect on non-KDE desktop
https://bugs.kde.org/show_bug.cgi?id=373891 Kyle Ferriter changed: What|Removed |Added CC||krferri...@protonmail.com --- Comment #3 from Kyle Ferriter --- This issue is still there, the line OnlyShowIn=KDE; needs to be added to org.kde.kgpg.desktop so it isn't started in other environments. As Stephan said this line is already present in the other KDE-specific desktop files. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408627] New: System Settings crash when trying to navigate to Touchpad configuration.
https://bugs.kde.org/show_bug.cgi?id=408627 Bug ID: 408627 Summary: System Settings crash when trying to navigate to Touchpad configuration. Product: systemsettings Version: 5.16.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: eridanired...@yahoo.com.mx Target Milestone: --- Application: systemsettings5 (5.16.0) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 4.15.0-51-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: Tried to open touchpad settings panel on system settings but it crashed inmediately when clicking said entry. The crash can be reproduced every time. -- Backtrace: Application: Preferencias del sistema (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdfdefaf680 (LWP 25393))] Thread 9 (Thread 0x7fdfa0ac8700 (LWP 25416)): #0 0x7fdfd594fed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fdfa0ac7ba0, expected=0, futex_word=0x5625802080c4) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fdfa0ac7c60, mutex=0x562580208070, cond=0x562580208098) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x562580208098, mutex=0x562580208070, abstime=0x7fdfa0ac7c60) at pthread_cond_wait.c:667 #3 0x7fdfdac3ed36 in QWaitConditionPrivate::wait_relative (this=0x562580208070, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x562580208070) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=, mutex=0x5625801562a0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7fdfdac3f096 in QWaitCondition::wait (this=this@entry=0x562580207fe0, mutex=mutex@entry=0x5625801562a0, time=) at thread/qwaitcondition_unix.cpp:209 #7 0x7fdfdac3c740 in QThreadPoolThread::run (this=0x562580207fd0) at thread/qthreadpool.cpp:139 #8 0x7fdfdac37c72 in QThreadPrivate::start (arg=0x562580207fd0) at thread/qthread_unix.cpp:361 #9 0x7fdfd59496db in start_thread (arg=0x7fdfa0ac8700) at pthread_create.c:463 #10 0x7fdfda53788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fdfa12c9700 (LWP 25415)): #0 0x7fdfd594fed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fdfa12c8ba0, expected=0, futex_word=0x562580207f54) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fdfa12c8c60, mutex=0x562580207f00, cond=0x562580207f28) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x562580207f28, mutex=0x562580207f00, abstime=0x7fdfa12c8c60) at pthread_cond_wait.c:667 #3 0x7fdfdac3ed36 in QWaitConditionPrivate::wait_relative (this=0x562580207f00, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x562580207f00) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=, mutex=0x5625801562a0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7fdfdac3f096 in QWaitCondition::wait (this=this@entry=0x562580207e70, mutex=mutex@entry=0x5625801562a0, time=) at thread/qwaitcondition_unix.cpp:209 #7 0x7fdfdac3c740 in QThreadPoolThread::run (this=0x562580207e60) at thread/qthreadpool.cpp:139 #8 0x7fdfdac37c72 in QThreadPrivate::start (arg=0x562580207e60) at thread/qthread_unix.cpp:361 #9 0x7fdfd59496db in start_thread (arg=0x7fdfa12c9700) at pthread_create.c:463 #10 0x7fdfda53788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fdfa1aca700 (LWP 25414)): #0 0x7fdfd594fed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fdfa1ac9ba0, expected=0, futex_word=0x562580207c84) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fdfa1ac9c60, mutex=0x562580207c30, cond=0x562580207c58) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x562580207c58, mutex=0x562580207c30, abstime=0x7fdfa1ac9c60) at pthread_cond_wait.c:667 #3 0x7fdfdac3ed36 in QWaitConditionPrivate::wait_relative (this=0x562580207c30, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x562580207c30) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=, mutex=0x5625801562a0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7fdfdac3f096 in QWaitCondition::wait (this=this@entry=0x562580207ba0, mutex=mutex@entry=0x5625801562a0, time=) at thread/qwaitcondition_unix.cpp:209 #7 0x7fdfdac3c740 in QThreadPoolThread::run (this=0x562580207b90) at thread/qthreadpool.cpp:139 #8
[krita] [Bug 408439] Outline selection tool not working properly
https://bugs.kde.org/show_bug.cgi?id=408439 --- Comment #3 from Pia Lorena --- (In reply to Boudewijn Rempt from comment #2) > What is the action set to? And is the mode vector or raster? You can find > those options in the tool option docker. I already tested it in both; vector and pixel modes. It does seem to have the similar issue with the different actions, excluding Add and Subtract. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 408619] Typing close parenthesis has no effect
https://bugs.kde.org/show_bug.cgi?id=408619 Matthew Woehlke changed: What|Removed |Added Resolution|DUPLICATE |FIXED --- Comment #2 from Matthew Woehlke --- Thanks... if it's fixed, I'm going to go pester downstream (Fedora), because it's fairly irritating :-). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 407852] Ktexteditor overwrites closing bracket even if automatic brackets is not enabled
https://bugs.kde.org/show_bug.cgi?id=407852 Dominik Haumann changed: What|Removed |Added CC||mwoehlke.fl...@gmail.com --- Comment #3 from Dominik Haumann --- *** Bug 408619 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 408619] Typing close parenthesis has no effect
https://bugs.kde.org/show_bug.cgi?id=408619 Dominik Haumann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Dominik Haumann --- Fixed with 5.59, unfortunately a regression that slipped in. Sorry. *** This bug has been marked as a duplicate of bug 407852 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408624] When doing panel widget adds or removes, I have had sporadic but repeated crashes.
https://bugs.kde.org/show_bug.cgi?id=408624 Danny changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|BACKTRACE |--- --- Comment #2 from Danny --- (In reply to David Edmundson from comment #1) > Crashes should have a backtrace. > > See the sad face icon in the panel after plasma restart. Unfortunately, the crash reporter failed to be able to add symbols for plasmashell, thus no backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 408626] New: Please support pinyin (chinese) input natively
https://bugs.kde.org/show_bug.cgi?id=408626 Bug ID: 408626 Summary: Please support pinyin (chinese) input natively Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: a...@polverini.org Target Milestone: --- SUMMARY I need to add pinyin input to my system and I'm unable to: it's such a mess that it's totally impossible to understand how to proceed. Every distro packaging KDE has different instructions and there are so many options that one is unable to understand what works or not, or what is better than other. EXPECTED RESULT I expect to be able to add pinyin support (needed for more than 1 billion chinese out there) in the control panel just as any other configuration. I tried ibus, fcitx, fcitx5, xim, uim and some other random packages but nothing worked: some of them are incomplete, some have no english translation, some others conflicts and so on. A complete and unusable total mess. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 18.12.3 KDE Plasma Version: 5.16 KDE Frameworks Version: 5.58 Qt Version: 5.12 -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408530] error bars not correctly shown in plots
https://bugs.kde.org/show_bug.cgi?id=408530 Alexander Semke changed: What|Removed |Added Version Fixed In||2.7 Resolution|--- |FIXED Latest Commit||https://commits.kde.org/lab ||plot/ec38c0da33083a2a4790df ||1e7cdd0959d6a4ca09 Status|CONFIRMED |RESOLVED --- Comment #3 from Alexander Semke --- Git commit ec38c0da33083a2a4790df1e7cdd0959d6a4ca09 by Alexander Semke. Committed on 12/06/2019 at 20:54. Pushed by asemke into branch 'master'. Correctly show error bars for data source columns having NANs. FIXED-IN: 2.7 M +14 -18 src/backend/worksheet/plots/cartesian/XYCurve.cpp M +1-0src/backend/worksheet/plots/cartesian/XYCurvePrivate.h https://commits.kde.org/labplot/ec38c0da33083a2a4790df1e7cdd0959d6a4ca09 -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 407712] Offset increases at edge of drawing area.
https://bugs.kde.org/show_bug.cgi?id=407712 Jason G. changed: What|Removed |Added CC||killert...@gmail.com --- Comment #1 from Jason G. --- Patch submitted to Phabricator as https://phabricator.kde.org/D21775 -- You are receiving this mail because: You are watching all bug changes.
[kxkb] [Bug 109845] Integrate KDE Keyboard tool it with skim ....
https://bugs.kde.org/show_bug.cgi?id=109845 Alex changed: What|Removed |Added CC||a...@polverini.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408623] pressure sensitivity isn't working
https://bugs.kde.org/show_bug.cgi?id=408623 Boudewijn Rempt changed: What|Removed |Added Component|General |tablet support Summary|My pressure sensitivity |pressure sensitivity isn't |isn't working at all on |working |krita specifically. it's a | |laptop with a pen I write | |right on the screen with, | |it works everywhere but | |krita and it's very | |frustrating. not sure what | |to do. | --- Comment #2 from Boudewijn Rempt --- The original title copied: "My pressure sensitivity isn't working at all on krita specifically. it's a laptop with a pen I write right on the screen with, it works everywhere but krita and it's very frustrating. not sure what to do." -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 408625] New: Kalarm unable to resume properly after suspend to ram
https://bugs.kde.org/show_bug.cgi?id=408625 Bug ID: 408625 Summary: Kalarm unable to resume properly after suspend to ram Product: kalarm Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: kalarmd Assignee: djar...@kde.org Reporter: a...@polverini.org Target Milestone: --- SUMMARY Kalarm stops showing alarms after suspension STEPS TO REPRODUCE 1. start KDE 2. sleep (suspend to ram) 3. wake up OBSERVED RESULT kalarm is still running, but no alarms are shown anymore. EXPECTED RESULT At least he should show new alarms, ideally also show past ones during the sleep. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu Disco + backports (available in About System) KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.58.0 Qt Version: 5.12 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408623] My pressure sensitivity isn't working at all on krita specifically. it's a laptop with a pen I write right on the screen with, it works everywhere but krita and it's very frustrat
https://bugs.kde.org/show_bug.cgi?id=408623 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|NEEDSINFO Severity|critical|normal Resolution|--- |WAITINGFORINFO CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Please first check https://docs.krita.org/en/reference_manual/preferences/tablet_settings.html, then check https://docs.krita.org/en/user_manual/drawing_tablets.html#where-it-can-go-wrong-windows -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408624] When doing panel widget adds or removes, I have had sporadic but repeated crashes.
https://bugs.kde.org/show_bug.cgi?id=408624 David Edmundson changed: What|Removed |Added Resolution|--- |BACKTRACE CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- Crashes should have a backtrace. See the sad face icon in the panel after plasma restart. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408566] Notifications Plasmoid on Latte Dock has disappearing icon
https://bugs.kde.org/show_bug.cgi?id=408566 --- Comment #14 from Michail Vourlakos --- (In reply to The Feren OS Dev from comment #13) > I'll be sure to check it when Latte drops in KDE neon Git Unstable and will > come back to you in case it still occurs on my side, though I'm assuming > this means you now have Plasma 5.16.0 and therefore have been able to see > the issue and have 'fixed' it. yep, I managed to build plasma master after a month of problems with kdesrc-build in my system and now the issue does not occur for me -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408566] Notifications Plasmoid on Latte Dock has disappearing icon
https://bugs.kde.org/show_bug.cgi?id=408566 --- Comment #13 from The Feren OS Dev --- I'll be sure to check it when Latte drops in KDE neon Git Unstable and will come back to you in case it still occurs on my side, though I'm assuming this means you now have Plasma 5.16.0 and therefore have been able to see the issue and have 'fixed' it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408624] New: When doing panel widget adds or removes, I have had sporadic but repeated crashes.
https://bugs.kde.org/show_bug.cgi?id=408624 Bug ID: 408624 Summary: When doing panel widget adds or removes, I have had sporadic but repeated crashes. Product: plasmashell Version: 5.16.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: dbarron...@yahoo.com Target Milestone: 1.0 SUMMARY When adding/removing widgets, I've experienced repeated crashes, but application does restart after. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Neon 5.16.0 (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.
[LabPlot2] [Bug 408309] v.2.5.0 not showing menu icons correctly in Ubuntu 19.04 (GNOME)
https://bugs.kde.org/show_bug.cgi?id=408309 --- Comment #2 from Esteban Richmond-Salazar --- (In reply to Alexander Semke from comment #1) > This looks like a packaging issue. LabPlot uses KDE's icons. Can you check > whether breeze icon set is installed on your system? > > Also, the current release is 2.6: > https://labplot.kde.org/2019/04/19/labplot-2-6-released/ > > If possible, please give the new version a try. Breeze icon theme is installed, but it doesn't solves the problem. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408566] Notifications Plasmoid on Latte Dock has disappearing icon
https://bugs.kde.org/show_bug.cgi?id=408566 --- Comment #12 from Michail Vourlakos --- blacklisted in Latte heuristics and this is fixed -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408566] Notifications Plasmoid on Latte Dock has disappearing icon
https://bugs.kde.org/show_bug.cgi?id=408566 Michail Vourlakos changed: What|Removed |Added Latest Commit|https://commits.kde.org/lat |https://commits.kde.org/lat |te-dock/ffd0bef61192ff11e3b |te-dock/ec284dbfa8d7f00083e |dee3874fba7fd3ad010d8 |506e1f9a87eb37f835192 Version Fixed In||0.8.9 --- Comment #11 from Michail Vourlakos --- Git commit ec284dbfa8d7f00083e506e1f9a87eb37f835192 by Michail Vourlakos. Committed on 12/06/2019 at 20:39. Pushed by mvourlakos into branch 'v0.8'. blacklist plasma notifications in heuristics --plasma notification applet has become more complex lets blacklist it in order to provide the real plasma experience and see how it goes FIXED-IN: 0.8.9 M +2-1containment/package/contents/code/AppletIdentifier.js https://commits.kde.org/latte-dock/ec284dbfa8d7f00083e506e1f9a87eb37f835192 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408623] My pressure sensitivity isn't working at all on krita specifically. it's a laptop with a pen I write right on the screen with, it works everywhere but krita and it's very frustrat
https://bugs.kde.org/show_bug.cgi?id=408623 Cas changed: What|Removed |Added Summary|My pressure sensitivity |My pressure sensitivity |isn't working at all on |isn't working at all on |krita specifically. it's a |krita specifically. it's a |laptop with a pen I write |laptop with a pen I write |right on the screen with, |right on the screen with, |it works everywhere but |it works everywhere but |krita and it's very |krita and it's very |frustratimg. not sure what |frustrating. not sure what |to do. |to do. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408623] New: My pressure sensitivity isn't working at all on krita specifically. it's a laptop with a pen I write right on the screen with, it works everywhere but krita and it's very fru
https://bugs.kde.org/show_bug.cgi?id=408623 Bug ID: 408623 Summary: My pressure sensitivity isn't working at all on krita specifically. it's a laptop with a pen I write right on the screen with, it works everywhere but krita and it's very frustratimg. not sure what to do. Product: krita Version: 4.2.1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: critical Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: michaelda...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408566] Notifications Plasmoid on Latte Dock has disappearing icon
https://bugs.kde.org/show_bug.cgi?id=408566 Michail Vourlakos changed: What|Removed |Added Latest Commit||https://commits.kde.org/lat ||te-dock/ffd0bef61192ff11e3b ||dee3874fba7fd3ad010d8 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #10 from Michail Vourlakos --- Git commit ffd0bef61192ff11e3bdee3874fba7fd3ad010d8 by Michail Vourlakos. Committed on 12/06/2019 at 20:31. Pushed by mvourlakos into branch 'master'. blacklist plasma notifications in heuristics --plasma notification applet has become more complex lets blacklist it in order to provide the real plasma experience and see how it goes M +2-1containment/package/contents/code/AppletIdentifier.js https://commits.kde.org/latte-dock/ffd0bef61192ff11e3bdee3874fba7fd3ad010d8 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408592] "Broken Image" cause DigiKam to crash
https://bugs.kde.org/show_bug.cgi?id=408592 --- Comment #5 from Maik Qualmann --- Created attachment 120825 --> https://bugs.kde.org/attachment.cgi?id=120825&action=edit setjmp.patch One possibility is probably the use of the built-in GCC alternative __builtin_setjmp and __builtin_longjmp. I already provide the patch. The GDB Bugtrace shows that it crashes in libpng in the longjmp() function (jump into the msvcrt.dll, also confirmed by reports in the net) So we also have to patch the libpng. Maik -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 400117] crash on exit
https://bugs.kde.org/show_bug.cgi?id=400117 avlas changed: What|Removed |Added CC||jsar...@gmail.com --- Comment #6 from avlas --- Same thing here. Also, https://bugs.kde.org/show_bug.cgi?id=407919 in Arch seems a duplicate of this one. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 408622] New: Konqueror crashed when exiting
https://bugs.kde.org/show_bug.cgi?id=408622 Bug ID: 408622 Summary: Konqueror crashed when exiting Product: konqueror Version: 5.0.97 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- Application: konqueror (5.0.97) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 5.0.0-16-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: Konqueror does not quit gracefully and crashes when the last tab is closed The crash can be reproduced every time. -- Backtrace: Application: Konqueror (konqueror), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8da16aedc0 (LWP 30895))] Thread 20 (Thread 0x7f8d44936700 (LWP 30937)): #0 0x7f8da0efb6ac in __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x7f8da0efd474 in ___fprintf_chk (fp=0x7f8da11b88b0 <_IO_stdfile_2_lock>, flag=1, format=0x7f8d691b76a8 "[%s] %s\n") at fprintf_chk.c:30 #2 0x7f8d6919f9ad in event_logv_ () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #3 0x7f8d6919fb44 in event_warn () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #4 0x7f8d691a146c in () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #5 0x7f8d69197114 in event_base_loop () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #6 0x7f8d6c39dc79 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f8d6c3382db in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f8d6c36a311 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f8d6c39a561 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8d960266db in start_thread (arg=0x7f8d44936700) at pthread_create.c:463 #11 0x7f8da0eec88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f8d45137700 (LWP 30924)): #0 0x7f8d9602c9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f8d45136c48) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f8d9602c9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f8d45136bf8, cond=0x7f8d45136c20) at pthread_cond_wait.c:502 #2 0x7f8d9602c9f3 in __pthread_cond_wait (cond=0x7f8d45136c20, mutex=0x7f8d45136bf8) at pthread_cond_wait.c:655 #3 0x7f8d6c397a49 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f8d6c398478 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f8d6c39850f in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f8d6c358fc8 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f8d6c35b7f6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f8d6c35bb34 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f8d6c39a561 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8d960266db in start_thread (arg=0x7f8d45137700) at pthread_create.c:463 #11 0x7f8da0eec88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f8d45b38700 (LWP 30923)): #0 0x7f8d9602ced9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f8d45b37a50, expected=0, futex_word=0x7f8d45b37c38) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f8d9602ced9 in __pthread_cond_wait_common (abstime=0x7f8d45b37af0, mutex=0x7f8d45b37be8, cond=0x7f8d45b37c10) at pthread_cond_wait.c:533 #2 0x7f8d9602ced9 in __pthread_cond_timedwait (cond=0x7f8d45b37c10, mutex=0x7f8d45b37be8, abstime=0x7f8d45b37af0) at pthread_cond_wait.c:667 #3 0x7f8d6c397b17 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f8d6c39846a in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f8d6c398552 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f8d6c358fb1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f8d6c35b4c7 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f8d6c35bab4 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f8d6c39a561 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8d960266db in start_thread (arg=0x7f8d45b38700) at pthread_create.c:463 #11 0x7f8da0eec88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f8d46973700 (LWP 30922)): #0 0x7f8d9602a4a7 in __pthread_mutex_unlock_full (mutex=0x55b763d2df70, decr=) at pthread_mutex_unlock.c:274 #1 0x7f8d505cc5fe in pa_mutex_unlock () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #2 0x7f8d58067473 in () at /usr/lib/x86_64-linux
[lattedock] [Bug 408566] Notifications Plasmoid on Latte Dock has disappearing icon
https://bugs.kde.org/show_bug.cgi?id=408566 --- Comment #9 from Michail Vourlakos --- (In reply to avlas from comment #6) > (In reply to Michail Vourlakos from comment #4) > > I wouldn't be surprised if Latte heuristics broke in plasma 5.16 > > Please take a look at https://bugs.kde.org/show_bug.cgi?id=407757#c21 they dont seem related but I will be sure only when plasma 5.16 reaches my system -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408566] Notifications Plasmoid on Latte Dock has disappearing icon
https://bugs.kde.org/show_bug.cgi?id=408566 --- Comment #8 from Michail Vourlakos --- (In reply to The Feren OS Dev from comment #7) > (In reply to avlas from comment #5) > > (In reply to Michail Vourlakos from comment #4) > > > I wouldn't be surprised if Latte heuristics broke in plasma 5.16 > > > > It works for my in Latte 0.8.8 after removing and re-adding notification in > > latte's system tray. > > > > However, notifications are displayed in the center of the screen. > > Try adding Notifications individually to the Latte Dock instead of inside > the System Tray applet. Probably should have mentioned that but my > notifications applet is outside of the System Tray applet and is instead its > own instance on the Latte Dock itself. When the same thing is done on a > Plasma Panel this issue does not occur, only when it's on a Latte Dock. [1] Let me give you some info. There is a MAJOR Plasma limitation concerning Icons. In Plasma Icons we have the following MAJOR Principle "Icons should NEVER look blurred". So to achieve this goal Plasma is using PlasmaCore.IconItem and I suppose in the future something in Kirigami that in order to achieve this icons are drawn ONLY from sizes provided from the active ICON THEME when the size requested is BELOW 64px. For icon sizes >=64px. there is no problem. [2] Latte on the other hand has another goal "Smoothness during Parabolic effect as FIRST GOAL and avoiding icon blurness is not mandatory". If the user chooses an Items Size that is provided from their icon theme then blurness is not appearing in Latte. To achieve this Latte is providing a fork for PlasmaCore.IconItem that is called Latte.IconItem Applets: Because applets developers and plasma applets are not considering [2] case as valid Latte is doing some automatic heuristics. Latte when a plasma applet loads searches in it to find the PlasmaCore.IconItem that is used when this applet is shown in the panel and IF that IconItem is found then Latte disables it and overlays above it a Latte.IconItem. Nasty workaround I know but it works. The heuristic mechanism can take blacklisting of applets in order to not be used or whitelisting which means that Latte has a specific way for this applet in order to reach at its PlasmaCore.IconItem So problems like this first need to be investigated from Latte side to identify if the Latte heuristics became invalid somehow... when plasma 5.16 reaches my system I will have more information. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408610] KWin shortcut "Show Desktop Grid" does not work
https://bugs.kde.org/show_bug.cgi?id=408610 Martin Flöser changed: What|Removed |Added Status|REPORTED|RESOLVED Flags||Wayland-, X11+ Resolution|--- |WORKSFORME --- Comment #2 from Martin Flöser --- Global shortcuts allow to configure parts of the system which are not active. You can configure settings for KWin even if you use i3. You can set shortcuts for applications which you don't use. This is - as much as I am aware of - not a bug but a wanted feature. It allows to fix up things. Unfortunately it's not possible to show in every setting that desktop effects are currently not active, because the components don't know it's a desktop effect. I don't see a real issue here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386271] [Wayland] Implement "Active window" mode in the KWin screenshot plugin
https://bugs.kde.org/show_bug.cgi?id=386271 --- Comment #12 from Martin Flöser --- >From a security perspective the best way would be KWin to handle the shortcut and launch spectacle (or any other tool) and pipe it the screenshot. The alternative would be spectacle asking and KWin showing the same user interaction pattern to click the window or some other way to have the user confirm that it wants a screenshot to be taken. From a security perspective having a call to take screenshots is terrible. That was one of the biggest security issues on X11 (it allowed e.g. to take over a browser instance). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404983] Spectacle cannot take screenshots in QPainter
https://bugs.kde.org/show_bug.cgi?id=404983 --- Comment #4 from Vlad Zagorodniy --- > ScreenshotEffect doesn't support QPainter: Heh, I completely forgot about that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404983] Spectacle cannot take screenshots in QPainter
https://bugs.kde.org/show_bug.cgi?id=404983 Martin Flöser changed: What|Removed |Added Component|general |effects-various Flags||Wayland+, X11- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404983] Spectacle cannot take screenshots in QPainter
https://bugs.kde.org/show_bug.cgi?id=404983
--- Comment #3 from Martin Flöser ---
ScreenshotEffect doesn't support QPainter:
bool ScreenShotEffect::supported()
{
return effects->compositingType() == XRenderCompositing ||
(effects->isOpenGLCompositing() && GLRenderTarget::supported());
}
--
You are receiving this mail because:
You are watching all bug changes.
[lattedock] [Bug 408566] Notifications Plasmoid on Latte Dock has disappearing icon
https://bugs.kde.org/show_bug.cgi?id=408566 --- Comment #7 from The Feren OS Dev --- (In reply to avlas from comment #5) > (In reply to Michail Vourlakos from comment #4) > > I wouldn't be surprised if Latte heuristics broke in plasma 5.16 > > It works for my in Latte 0.8.8 after removing and re-adding notification in > latte's system tray. > > However, notifications are displayed in the center of the screen. Try adding Notifications individually to the Latte Dock instead of inside the System Tray applet. Probably should have mentioned that but my notifications applet is outside of the System Tray applet and is instead its own instance on the Latte Dock itself. When the same thing is done on a Plasma Panel this issue does not occur, only when it's on a Latte Dock. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408615] Wayaknd doesn' work with Nvidia cards
https://bugs.kde.org/show_bug.cgi?id=408615 Martin Flöser changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Martin Flöser --- *** This bug has been marked as a duplicate of bug 408575 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408575] lack of wayland support when an Nvidia card and native drivers are used
https://bugs.kde.org/show_bug.cgi?id=408575 --- Comment #2 from Martin Flöser --- *** Bug 408615 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408621] [FEATURE] Add another behavior when switching from a grouped active application to another
https://bugs.kde.org/show_bug.cgi?id=408621 Michail Vourlakos changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408621] [FEATURE] Add another behavior when switching from a grouped active application to another
https://bugs.kde.org/show_bug.cgi?id=408621 --- Comment #1 from Michail Vourlakos --- 1. In Latte git version there in an option to configure the Left Click action for Tasks. You can choose between: Present Windows/ Cycle Through Tasks / Preview Windows . I suppose you are referring to "Cycle Through Tasks" 2. this is too messy and I am not interested adding it -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408156] screen flickering when using direct3D11 via ANGLE on 4.2.0
https://bugs.kde.org/show_bug.cgi?id=408156 --- Comment #6 from vinnie --- (In reply to Boudewijn Rempt from comment #5) > hm, and your drivers also seem to be up to date. yeah, thats why im confused on whats going on. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408485] Colors appear darker when retrieving an external picture as a File Layer
https://bugs.kde.org/show_bug.cgi?id=408485 --- Comment #9 from to...@offensivelytolerant.com --- (In reply to Boudewijn Rempt from comment #6) > Um, I am not so sure anymore. I tried 3 versions of Krita: > > 3.3.3 loads external_picture_to_import.exr and shows it washed out, like the > first layer of your test .kra file > 4.1.7 and 4.2.1: loads it "darker", but there is no difference whether I > load the exr directly, import it as a pixel layer or link to it as a file > layer: it is always rendered the same way. > > exrdisplay and imagemagick's display show the image like Krita 4.1.7 and > 4.2.0 > > How did you create the exr file? There's even simpler, in fact : 1. Create a document with Krita 4.2.1, floa1 16b, scRGB (Linear) 2. Paint a bit on it, export is as EXR 3. Import the then-created EXR file you just exported into the document you just made 4. Color appear darker and strongly different than in the original layer But actually, Krita 4.1.7 does alterate the colors too... Only with a very slight difference, which could explain why I didn't noticed it in the first place. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408621] New: [FEATURE] Add another behavior when switching from a grouped active application to another
https://bugs.kde.org/show_bug.cgi?id=408621 Bug ID: 408621 Summary: [FEATURE] Add another behavior when switching from a grouped active application to another Product: lattedock Version: 0.8.8 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: sanchez.gu...@gmail.com Target Milestone: --- Created attachment 120824 --> https://bugs.kde.org/attachment.cgi?id=120824&action=edit KWin task switcher configuration This is a copy of 407144, but since then I started using Latte Dock and I have configured it to behave as I want using middle click settings. In this way, we could have the same behavior for both Task Switcher and Latte Dock when switching apps. If you configure Latte Dock Middle Click (or Ctrl + left click) behavior to Cycle Through Tasks, whenever I click a group of windows the first thing it does is to bring up the last used window of the application and then it starts cycling. I don't know if it would be possible to make it work like this: 1. When the user left clicks an icon of an application that is not focused, Latte Dock should change to the last active window of the application (whether the application has one or more windows). 2. When the user left clicks an icon of an application that has many windows and that is focused, Latte Dock should show all windows. If the application only has one window, it could be minimized or just do nothing when clicked. Could it be configurable? In that way, the dock works the same way as the Alt-Tab of KWin task switcher when configured as in the screenshot. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.16.0 (available in About System) KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408566] Notifications Plasmoid on Latte Dock has disappearing icon
https://bugs.kde.org/show_bug.cgi?id=408566 --- Comment #6 from avlas --- (In reply to Michail Vourlakos from comment #4) > I wouldn't be surprised if Latte heuristics broke in plasma 5.16 Please take a look at https://bugs.kde.org/show_bug.cgi?id=407757#c21 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407757] Notifications from kdeconnect all display in the centre of the screen on top of each other
https://bugs.kde.org/show_bug.cgi?id=407757 avlas changed: What|Removed |Added CC||jsar...@gmail.com --- Comment #24 from avlas --- Is the location issue related to https://bugs.kde.org/show_bug.cgi?id=408566#c5? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 408590] Notification of MPRIS lagging behind the one shown in the app
https://bugs.kde.org/show_bug.cgi?id=408590 Matthijs Tijink changed: What|Removed |Added Status|REPORTED|RESOLVED CC||matthijstij...@gmail.com Resolution|--- |FIXED --- Comment #1 from Matthijs Tijink --- Unless I misunderstood, this is fixed by commit 56d01ed082a71, which should appear in the next Android release. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408566] Notifications Plasmoid on Latte Dock has disappearing icon
https://bugs.kde.org/show_bug.cgi?id=408566 avlas changed: What|Removed |Added CC||jsar...@gmail.com --- Comment #5 from avlas --- (In reply to Michail Vourlakos from comment #4) > I wouldn't be surprised if Latte heuristics broke in plasma 5.16 It works for my in Latte 0.8.8 after removing and re-adding notification in latte's system tray. However, notifications are displayed in the center of the screen. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408474] Freeze on safe assert "stroke"
https://bugs.kde.org/show_bug.cgi?id=408474 --- Comment #7 from Dmitrii Utkin --- Created attachment 120823 --> https://bugs.kde.org/attachment.cgi?id=120823&action=edit Log under Mac OS X -- You are receiving this mail because: You are watching all bug changes.
