[kscreenlocker] [Bug 489896] Login screen icons misplaced after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=489896 --- Comment #2 from luc --- Additional information from my side: a safe way to reproduce this on my notebook is to enter a wrong password into the screenlocker and after the input lock time the layout is broken. This means in step by step: 1. Put the notebook into sleep 2. Wake it up again 3. Enter wrong password 4. Wait until the input field accepts input again -> All buttons etc. go up to the left corner. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 489896] Login screen icons misplaced after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=489896 luc changed: What|Removed |Added Ever confirmed|0 |1 CC||k...@murer-it-services.ch Status|REPORTED|CONFIRMED --- Comment #1 from luc --- I can confirm this, running KDE@git-master on openSUSE Tumbleweed. The issue is not always showing up after sleep for me, but regularly enough (possibly every 2nd time or so). -- You are receiving this mail because: You are watching all bug changes.
[Marknote] [Bug 490814] New: Image insertion doesn't refresh when trying to import a new image on Haiku
https://bugs.kde.org/show_bug.cgi?id=490814 Bug ID: 490814 Summary: Image insertion doesn't refresh when trying to import a new image on Haiku Classification: Applications Product: Marknote Version: 1.3.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@kaidan.im Reporter: bega...@gmail.com CC: c...@carlschwan.eu, m...@kaidan.im Target Milestone: --- Created attachment 171984 --> https://bugs.kde.org/attachment.cgi?id=171984&action=edit Different files shown with Marknote and actual content of the directory *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When working with Marknote I tend to add some screenshots to the notes, sometimes this works, but it seems that when I click on location for the image it doesn't show the latest added images in the location (mostly my home directory). STEPS TO REPRODUCE 1. Open a note with Marknote 2. click on insert image -> image location 3. it opens a tracker window (home directory) OBSERVED RESULT Tracker window doesn't show latest created images/screenshots EXPECTED RESULT Tracker window with latest created images/screenshots shown SOFTWARE/OS VERSIONS Haiku: R1B4 64bit KDE Plasma Version: 6.1.2 (partial) KDE Frameworks Version: 6.4.0 Qt Version: 6.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489949] Plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=489949 Luc Hamers changed: What|Removed |Added Summary|Kwin crash |Plasmashell crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489949] New: Kwin crash
https://bugs.kde.org/show_bug.cgi?id=489949 Bug ID: 489949 Summary: Kwin crash Classification: Plasma Product: plasmashell Version: 6.1.2 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: l...@hamers.de Target Milestone: 1.0 Application: plasmashell (6.1.2) Qt Version: 6.7.2 Frameworks Version: 6.3.0 Operating System: Linux 6.9.7-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 6.1.2 [CoredumpBackend] -- Information about the crash: Kwin crashes reproduceble when unplugging the HP thunderbolt dock. The crash can be reproduced every time. -- Backtrace: Application: plasmashell (plasmashell), signal: Segmentation fault [New LWP 10045] [New LWP 9866] [New LWP 9859] [New LWP 9858] [New LWP 10014] [New LWP 10013] [New LWP 10038] [New LWP 10040] [New LWP 10047] [New LWP 10351] [New LWP 10138] [New LWP 11936] [New LWP 9867] [New LWP 10353] [New LWP 10011] [New LWP 10037] [New LWP 9856] [New LWP 10046] [New LWP 10355] [New LWP 10039] [New LWP 10048] [New LWP 11934] [New LWP 13400] [New LWP 11933] [New LWP 13403] [New LWP 11935] [New LWP 13402] [New LWP 13401] [New LWP 13413] [New LWP 13411] [New LWP 13404] [New LWP 13410] [New LWP 10010] [New LWP 9854] [New LWP 9869] [New LWP 13155] [New LWP 1] [New LWP 9908] [New LWP 10049] [New LWP 9861] [New LWP 13399] [New LWP 13412] [New LWP 9860] [New LWP 13154] [New LWP 10012] [New LWP 10133] [New LWP 9868] [New LWP 10352] [New LWP 10036] [New LWP 11932] [New LWP 10354] [New LWP 13398] [New LWP 13409] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/bin/plasmashell --no-respawn'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fa25fa949dc in __pthread_kill_implementation () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7fa1e54006c0 (LWP 10045))] python sentry-sdk not installed :( Cannot QML trace cores :( [Current thread is 1 (Thread 0x7fa1e54006c0 (LWP 10045))] Thread 53 (Thread 0x7fa18f4006c0 (LWP 13409)): #0 0x7fa25fa8efee in __futex_abstimed_wait_common () from /lib64/libc.so.6 #1 0x7fa25fa91d30 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7fa2604f8fbb in QWaitConditionPrivate::wait (deadline=..., this=0x561455ede8d0) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/thread/qwaitcondition_unix.cpp:102 #3 QWaitCondition::wait (this=this@entry=0x56145998e1d0, mutex=mutex@entry=0x56145998e1c8, deadline=...) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/thread/qwaitcondition_unix.cpp:180 #4 0x7fa261e67167 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=) at /usr/src/debug/qtdeclarative-everywhere-src-6.7.2/src/quick/scenegraph/qsgthreadedrenderloop.cpp:197 #5 QSGRenderThread::processEventsAndWaitForMore (this=0x56145998e110) at /usr/src/debug/qtdeclarative-everywhere-src-6.7.2/src/quick/scenegraph/qsgthreadedrenderloop.cpp:868 #6 QSGRenderThread::run (this=0x56145998e110) at /usr/src/debug/qtdeclarative-everywhere-src-6.7.2/src/quick/scenegraph/qsgthreadedrenderloop.cpp:991 #7 0x7fa2604ed139 in operator() (__closure=) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/thread/qthread_unix.cpp:326 #8 (anonymous namespace)::terminate_on_exception > (t=...) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/thread/qthread_unix.cpp:262 #9 QThreadPrivate::start (arg=0x56145998e110) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/thread/qthread_unix.cpp:285 #10 0x7fa25fa92ba2 in start_thread () from /lib64/libc.so.6 #11 0x7fa25fb1400c in clone3 () from /lib64/libc.so.6 Thread 52 (Thread 0x7fa208c006c0 (LWP 13398)): #0 0x7fa25fa8efee in __futex_abstimed_wait_common () from /lib64/libc.so.6 #1 0x7fa25fa91d30 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7fa2604f8fbb in QWaitConditionPrivate::wait (deadline=..., this=0x561457ef8860) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/thread/qwaitcondition_unix.cpp:102 #3 QWaitCondition::wait (this=this@entry=0x561457f1b660, mutex=mutex@entry=0x561457f1b658, deadline=...) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/thread/qwaitcondition_unix.cpp:180 #4 0x7fa261e67167 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=) at /usr/src/debug/qtdeclarative-everywhere-src-6.7.2/src/quick/scenegraph/qsgthreadedrenderloop.cpp:197 #5 QSGRenderThread::processEventsAndWaitForMore (this=0x561457f1b5a0) at /usr/src/debug/qtdeclarative-everywhere-src-6.7.2/src/quick/scenegraph/qsgthreadedrenderloop.cpp:868 #6 QSGRenderThread::run (this=0x561457f1b5a0) at /usr/src/debug/qtdeclarative-everywhere-src-6.7.2/src/quick/scenegraph/qsgthreadedrenderloop.cpp:991 #7 0x
[palapeli] [Bug 489170] Remember sort preference
https://bugs.kde.org/show_bug.cgi?id=489170 Schrijvers Luc changed: What|Removed |Added CC||bega...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 487315] Missing dependencies? (starting from version 1.1.1 (1.1.0 seems to be fine eg no warnings)
https://bugs.kde.org/show_bug.cgi?id=487315 --- Comment #1 from Schrijvers Luc --- Output in Terminal when running cmake -Bbuild -S. -DECM_DIR=/system/data/cmake/Modules/ECM/cmake on Haiku. (started from version 1.1.1). ``` CMake Warning at /boot/system/lib/cmake/Qt6Qml/Qt6QmlMacros.cmake:3393 (message): The qml plugin 'Kirigamiplugin' is a dependency of 'haruna', but the link target it defines (Kirigamiplugin) does not exist in the current scope. The plugin will not be linked. Call Stack (most recent call first): /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:678 (qt6_import_qml_plugins) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:678 (cmake_language) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:774 (_qt_internal_finalize_executable) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:743:EVAL:1 (qt6_finalize_target) src/CMakeLists.txt:DEFERRED CMake Warning at /boot/system/lib/cmake/Qt6Qml/Qt6QmlMacros.cmake:3393 (message): The qml plugin 'qtgraphicaleffectsplugin' is a dependency of 'haruna', but the link target it defines (Qt6::qtgraphicaleffectsplugin) does not exist in the current scope. The plugin will not be linked. Call Stack (most recent call first): /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:678 (qt6_import_qml_plugins) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:678 (cmake_language) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:774 (_qt_internal_finalize_executable) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:743:EVAL:1 (qt6_finalize_target) src/CMakeLists.txt:DEFERRED CMake Warning at /boot/system/lib/cmake/Qt6Qml/Qt6QmlMacros.cmake:3393 (message): The qml plugin 'KirigamiPlatformplugin' is a dependency of 'haruna', but the link target it defines (KirigamiPlatformplugin) does not exist in the current scope. The plugin will not be linked. Call Stack (most recent call first): /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:678 (qt6_import_qml_plugins) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:678 (cmake_language) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:774 (_qt_internal_finalize_executable) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:743:EVAL:1 (qt6_finalize_target) src/CMakeLists.txt:DEFERRED CMake Warning at /boot/system/lib/cmake/Qt6Qml/Qt6QmlMacros.cmake:3393 (message): The qml plugin 'KirigamiDelegatesplugin' is a dependency of 'haruna', but the link target it defines (KirigamiDelegatesplugin) does not exist in the current scope. The plugin will not be linked. Call Stack (most recent call first): /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:678 (qt6_import_qml_plugins) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:678 (cmake_language) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:774 (_qt_internal_finalize_executable) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:743:EVAL:1 (qt6_finalize_target) src/CMakeLists.txt:DEFERRED CMake Warning at /boot/system/lib/cmake/Qt6Qml/Qt6QmlMacros.cmake:3393 (message): The qml plugin 'KirigamiPrivatePlugin' is a dependency of 'haruna', but the link target it defines (KirigamiPrivatePlugin) does not exist in the current scope. The plugin will not be linked. Call Stack (most recent call first): /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:678 (qt6_import_qml_plugins) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:678 (cmake_language) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:774 (_qt_internal_finalize_executable) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:743:EVAL:1 (qt6_finalize_target) src/CMakeLists.txt:DEFERRED CMake Warning at /boot/system/lib/cmake/Qt6Qml/Qt6QmlMacros.cmake:3393 (message): The qml plugin 'qtgraphicaleffectsprivateplugin' is a dependency of 'haruna', but the link target it defines (Qt6::qtgraphicaleffectsprivate) does not exist in the current scope. The plugin will not be linked. Call Stack (most recent call first): /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:678 (qt6_import_qml_plugins) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:678 (cmake_language) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:774 (_qt_internal_finalize_executable) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:743:EVAL:1 (qt6_finalize_target) src/CMakeLists.txt:DEFERRED ``` qtgraphicaleffectsplugin seems to be from a missing dependency for libQt6Core5Compat, for the others I'm unsure what is missing. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 487315] New: Missing dependencies? (starting from version 1.1.1 (1.1.0 seems to be fine eg no warnings)
https://bugs.kde.org/show_bug.cgi?id=487315 Bug ID: 487315 Summary: Missing dependencies? (starting from version 1.1.1 (1.1.0 seems to be fine eg no warnings) Classification: Applications Product: Haruna Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: bega...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Warning produced while building Haruna from source. STEPS TO REPRODUCE 1. Download source archive 2. run cmake in the extracted source OBSERVED RESULT Cmake produces warnings, one related to missing libQt6Core5Compat: CMake Warning at /boot/system/lib/cmake/Qt6Qml/Qt6QmlMacros.cmake:3393 (message): The qml plugin 'qtgraphicaleffectsplugin' is a dependency of 'haruna', but the link target it defines (Qt6::qtgraphicaleffectsplugin) does not exist in the current scope. The plugin will not be linked. Call Stack (most recent call first): /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:678 (qt6_import_qml_plugins) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:678 (cmake_language) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:774 (_qt_internal_finalize_executable) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:743:EVAL:1 (qt6_finalize_target) src/CMakeLists.txt:DEFERRED Other related to Kirigami, haven't found a way to fix those: CMake Warning at /boot/system/lib/cmake/Qt6Qml/Qt6QmlMacros.cmake:3393 (message): The qml plugin 'Kirigamiplugin' is a dependency of 'haruna', but the link target it defines (Kirigamiplugin) does not exist in the current scope. The plugin will not be linked. Call Stack (most recent call first): /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:678 (qt6_import_qml_plugins) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:678 (cmake_language) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:774 (_qt_internal_finalize_executable) /boot/system/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:743:EVAL:1 (qt6_finalize_target) src/CMakeLists.txt:DEFERRED EXPECTED RESULT No warning, Kirigami plugins linked into the application SOFTWARE/OS VERSIONS Haiku: Haiku R1B4 64bit (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 --- Comment #81 from Luc --- (In reply to vm from comment #73) > After a lot of debugging i think i've found at least a better workaround. > > Workaround: > > Quite simple - disable ALL effects in "Window Open/Close Animation" group. > > Details: > [...] Thank you, I appreciate your investigation and our time spent on it. The bug is not triggered anymore after disabling all effects in "Window Open -> Close Animation". In my opinion it is a step forward compared to disabling the compositor altogether. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 --- Comment #50 from Luc --- (In reply to Cristian Le from comment #35) > ## Summary Hello Cristian, good summary, thank you. I would like to add that I disabled the compositor today (System Settings -> Compositor -> Enable on startup [unchecked] -> restart KWin / reboot) and I didn't encountered the issue anymore (I was constantly and continuously using 3 Rider instances + 1 CLion instance for about 11 hours). I really don't know why I didn't try that sooner. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 --- Comment #34 from Luc --- One more thing, the title mentions "Xorg", but in reality it happens on both X and Wayland with the same occurrence probability. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 --- Comment #33 from Luc --- I noticed the Version field is 5.90.0 for this bug, but it is affecting all 6.x versions (currently I'm on 6.0.3.1 for example). It never happened for 5.x versions (not considering 5.90.x versions), basically this problem started only after updating to 6.x. To avoid having this bug fix postponed due to triage criteria (based on Version field), is it possible please to adjust the Version field accordingly? Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] With NVIDIA or AMD GPUs on X11, sometimes left or right clicking on windows of JetBrains apps or a Plasma panel instead interacts with Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=478556 Luc changed: What|Removed |Added CC||iq2...@gmail.com --- Comment #30 from Luc --- Same issue here since updated to Plasma 6. Randomly the mouse click (left and right, it doesn't matter) goes through top level window (from the z order perspective) and generates the corresponding click events on the window beneath it, so instead of focusing the desired top level window the focus is given to the window beneath it (or desktop, if no lower level window present). It is really frustrating because you cannot interact at all with the window. Changing *any* option in System Settings -> Window Management -> Window Behavior and click Apply would temporary fix the issue (for example change "Delay focus by" from default 300 ms to anything else and click Apply (the same with any option etc.). After a certain time interval (minutes, tens of minutes) or may some event (I didn't investigate for the moment), the problem manifests itself again. It happens on both X11 and Wayland. I'm using nvidia driver (470.239.06) on a GeForce GTX 765M graphics card. I tried to test on nouveau but there are so many issues with nouveau (from freezing to segfaults etc.) that I couldn't use it at all. I will get back with more information if / when I get more time to investigate it. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[analitza] [Bug 484823] analitza produces libraries with the same name and SONAME for different versions
https://bugs.kde.org/show_bug.cgi?id=484823 --- Comment #2 from Schrijvers Luc --- Commented upstream, the proposed fix fixes building kalgebra 23.08.5 with the Qt5 version and 24.02.1 with the Qt6 version. -- You are receiving this mail because: You are watching all bug changes.
[analitza] [Bug 484823] New: analitza produces libraries with the same name and SONAME for different versions
https://bugs.kde.org/show_bug.cgi?id=484823 Bug ID: 484823 Summary: analitza produces libraries with the same name and SONAME for different versions Classification: Frameworks and Libraries Product: analitza Version: 8.0.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: aleix...@kde.org Reporter: bega...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Applications wont launch with the other KF version installed. STEPS TO REPRODUCE 1. Build analitza 23.08.5 for KF5, Build analitza 24.02.1 for KF6µ OBSERVED RESULT Both provide libAnalitza*.so.8.0.0 EXPECTED RESULT At least one should provide a different SONAME SOFTWARE/OS VERSIONS Haiku: R1B4 KDE Plasma Version: KF5 (not used) KDE Frameworks Version: 5.115.0 + 6.0.0 Qt Version: 5.15.11 + 6.6.0 ADDITIONAL INFORMATION Our Cantor version is still build with KF5, hence using Analitza 23.08.5, but wanted to give a go at KAlgebra with 24.02.1 when I noticed either can't find Analitza is the other version is installed (cmake config version differ). ``` CMake Error at CMakeLists.txt:30 (find_package): By not providing "FindAnalitza6.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "Analitza6", but CMake did not find one. Could not find a package configuration file provided by "Analitza6" with any of the following names: Analitza6Config.cmake analitza6-config.cmake Add the installation prefix of "Analitza6" to CMAKE_PREFIX_PATH or set "Analitza6_DIR" to a directory containing one of the above files. If "Analitza6" provides a separate development package or SDK, be sure it has been installed. ``` -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431859] Mouse cursor should disappear whenever you are over top of the canvas.
https://bugs.kde.org/show_bug.cgi?id=431859 --- Comment #16 from Luc --- I can confirm it works! I did notice that when the cursor moves into the grey area in between the white page and the menus, there is no cursor, just the brush symbol. The problem is the cursor almost disappears since it's extremely subtle on the grey background. Not sure if it's possible, but I'd suggest the cursor should switch when off the white page instead. Because right now, you lose track of where it went. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431859] Mouse cursor should disappear whenever you are over top of the canvas.
https://bugs.kde.org/show_bug.cgi?id=431859 --- Comment #12 from Luc --- I'm an idiot. Thank you. Installed and can confirm all the icons switch as I move my cursor over each one. Clever little "app". lol -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431859] Mouse cursor should disappear whenever you are over top of the canvas.
https://bugs.kde.org/show_bug.cgi?id=431859 --- Comment #10 from Luc --- Hi again, attached is the log requested. I had a look at that github set of files, but I'm unsure how to install it since it's not an apk. I am NOT a master of Linux, ChromeOS, etc. But I can definitely do a few things with some guidance. I do have Linux installed, and was able to install an apk... but this github repository doesn't have what I'm familiar with. Note that I'm pretty sure the cursor wasn't there in an older version of Krita before pen pressure was added. But don't quote me on that... it's been a long time. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431859] Mouse cursor should disappear whenever you are over top of the canvas.
https://bugs.kde.org/show_bug.cgi?id=431859 --- Comment #9 from Luc --- Created attachment 141513 --> https://bugs.kde.org/attachment.cgi?id=141513&action=edit Wacom_strokes log -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431859] Mouse cursor should disappear whenever you are over top of the canvas.
https://bugs.kde.org/show_bug.cgi?id=431859 --- Comment #7 from Luc --- (In reply to Halla Rempt from comment #6) > Sharaf, is this still the case? Hi, original reporter of this issue. I have Krita 5.0.0 beta 1 installed on my Google Pixel Slate. I just tried the Wacom drawing pad again and same thing. Cursor is still there. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438670] Discover notifies about updates whereas there are none
https://bugs.kde.org/show_bug.cgi?id=438670 Luc Langehegermann changed: What|Removed |Added CC|l...@pt.lu | -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438670] Discover notifies about updates whereas there are none
https://bugs.kde.org/show_bug.cgi?id=438670 Luc Langehegermann changed: What|Removed |Added CC||l...@pt.lu -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 436707] System Monitor crashes in ToolBarLayoutDelegate::ensureItemVisibility() when going from Overview > Processes > back to Overview and then closing
https://bugs.kde.org/show_bug.cgi?id=436707 Luc Langehegermann changed: What|Removed |Added CC|l...@pt.lu | -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 437729] New: Crash during closing
https://bugs.kde.org/show_bug.cgi?id=437729 Bug ID: 437729 Summary: Crash during closing Product: plasma-systemmonitor Version: 5.21.5 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: l...@pt.lu CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Application: plasma-systemmonitor (5.21.5) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.8.0-53-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: KDE neon User Edition 5.21 -- Information about the crash: - What I was doing when the application crashed: This crash happened when i tried to close it. I used the process list view. Prior to closing, I selected to show all Processes The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Monitor (plasma-systemmonitor), signal: Segmentation fault [New LWP 7951] [New LWP 7952] [New LWP 7954] [New LWP 7955] [New LWP 7956] [New LWP 7957] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fd60e28aaff in __GI___poll (fds=0x7fff53b0c7a8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7fd60af2f340 (LWP 7950))] Thread 7 (Thread 0x7fd5f90a0700 (LWP 7957)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5640134bc308) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5640134bc2b8, cond=0x5640134bc2e0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5640134bc2e0, mutex=0x5640134bc2b8) at pthread_cond_wait.c:647 #3 0x7fd5fad5eb5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7fd5fad5e75b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7fd60df89609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fd60e297293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fd5f98a1700 (LWP 7956)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5640134bc308) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5640134bc2b8, cond=0x5640134bc2e0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5640134bc2e0, mutex=0x5640134bc2b8) at pthread_cond_wait.c:647 #3 0x7fd5fad5eb5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7fd5fad5e75b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7fd60df89609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fd60e297293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fd5fa0a2700 (LWP 7955)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5640134bc308) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5640134bc2b8, cond=0x5640134bc2e0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5640134bc2e0, mutex=0x5640134bc2b8) at pthread_cond_wait.c:647 #3 0x7fd5fad5eb5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7fd5fad5e75b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7fd60df89609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fd60e297293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fd5fa8a3700 (LWP 7954)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5640134bc308) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5640134bc2b8, cond=0x5640134bc2e0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5640134bc2e0, mutex=0x5640134bc2b8) at pthread_cond_wait.c:647 #3 0x7fd5fad5eb5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7fd5fad5e75b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7fd60df89609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fd60e297293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fd603fff700 (LWP 7952)): #0 0x7fd60e855d2c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7fd60d1948ef in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd60d19529b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd60d1954a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fd60e855ffb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd60e7fa1eb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fd60e614a52 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fd60eab7f4b in
[krita] [Bug 431859] Mouse cursor should disappear whenever you are over top of the canvas.
https://bugs.kde.org/show_bug.cgi?id=431859 --- Comment #5 from Luc --- And another article with some different info. https://chromeunboxed.com/one-by-wacom-graphics-tablet-chromebooks Wacom support with Krita for Android on a Chromebook really sounds it may become reasonably popular! May be worth investing more time in supporting Wacom properly on Chromebooks. Regardless, thanks to everyone making Krita awesome! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431859] Mouse cursor should disappear whenever you are over top of the canvas.
https://bugs.kde.org/show_bug.cgi?id=431859 --- Comment #4 from Luc --- In case this matters, here's what just got published. https://gizmodo.com/wacoms-cheapest-tablet-now-supports-chromebooks-for-asp-1846128080 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 430829] Pen lag / latency when on ChromeOS (Google Pixel Slate i5)
https://bugs.kde.org/show_bug.cgi?id=430829 --- Comment #5 from Luc --- (In reply to Halla Rempt from comment #4) > We were offered access as well, but it doesn't fit in with Krita's current > architecture. OK, thanks. Something to hopefully consider down the line? Chromebooks are pretty popular and from what I've seen in the tech world, getting more popular, especially in education. Krita is a wonderful program, my wife is very impressed with it after trying everything available. But the latency is sadly one of the only significant problems we've had with Krita It's obviously a huge and obvious "issue". Still workable, but when you see "what could have been"... Well thanks for responding and clarifying. I won't get my hopes up on this one. Too bad... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 430829] Pen lag / latency when on ChromeOS (Google Pixel Slate i5)
https://bugs.kde.org/show_bug.cgi?id=430829 --- Comment #3 from Luc --- (In reply to Halla Rempt from comment #2) > Google has created a special low-level, low-latency stylus api that went in > beta last year. Unfortunately, it's directly tied to the display system as > well, and we cannot use it. Fascinating... and Squid got access to it somehow? That's frustrating if it's capable but not available... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 430829] Pen lag / latency when on ChromeOS (Google Pixel Slate i5)
https://bugs.kde.org/show_bug.cgi?id=430829 --- Comment #1 from Luc --- Any chance this will get any attention? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431859] Mouse cursor should disappear whenever you are over top of the canvas.
https://bugs.kde.org/show_bug.cgi?id=431859 --- Comment #2 from Luc --- (In reply to Halla Rempt from comment #1) > Please tell us exactly which version of ChromeOS and what hardware you are > using. For sure. I'm using an official Google Pixel Slate. Latest stable version: Version 87.0.4280.142 (Official Build) (64-bit) For input, this happens using my built in trackpad, external Logitech mouse or the external Wacom Intuos 4 drawing tablet. There is NO problem if I use my official Pixelbook Pen. But the goal is to have the cursor removed when using the Wacom drawing tablet of course. At least I'm hoping this is possible. For reference, another contributor just added pen pressure sensitivity using a Wacom tablet. This is the bug where I was reporting back to the person. It JUST got resolved. https://bugs.kde.org/show_bug.cgi?id=429940 We actually have two Slates in the household. My wife (the actual artist) is currently using the Krita version from the Play Store. I (the tech guy) am using an experimental version 5.0.0-prealpha (git 21f70cc). It was given to me to test the pressure sensitivity for the Wacom tablet as per that bug report. Point is, more than happy to do any testing required. I can install these experimental versions if needed for testing. Thanks for responding. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429940] Wacom Intuos Pen Pressure Support on ChromeOS with Krita Android App
https://bugs.kde.org/show_bug.cgi?id=429940 --- Comment #23 from Luc --- Done. https://bugs.kde.org/show_bug.cgi?id=431859 Appreciate the help on this one. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431859] New: Mouse cursor should disappear whenever you are over top of the canvas.
https://bugs.kde.org/show_bug.cgi?id=431859 Bug ID: 431859 Summary: Mouse cursor should disappear whenever you are over top of the canvas. Product: krita Version: 4.4.2-beta1 Platform: Android OS: ChromeOS Status: REPORTED Severity: normal Priority: NOR Component: Brush Engine/Bristle Assignee: krita-bugs-n...@kde.org Reporter: lafreniere@gmail.com Target Milestone: --- Created attachment 135025 --> https://bugs.kde.org/attachment.cgi?id=135025&action=edit Before and after required fix When using a mouse over the canvas area, the mouse cursor remains displayed while drawing besides the actual brush symbol used. The cursor is very distracting when drawing. Although most won't use a mouse to draw, a Wacom drawing pad behaves as a mouse even when using the physical pen. Recently, Wacom was just accommodated for pen pressure (hooray!), so this is an important piece of the puzzle to fully support Wacom tablets on ChromeOS. Obviously this should only be fixed when over the canvas area since we still need a mouse cursor for menus and such. Merci. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429940] Wacom Intuos Pen Pressure Support on ChromeOS with Krita Android App
https://bugs.kde.org/show_bug.cgi?id=429940 --- Comment #21 from Luc --- Sounds good and agreed. Should I open another bug for the cursor problem? To be clear, we have Pixel Slates. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429940] Wacom Intuos Pen Pressure Support on ChromeOS with Krita Android App
https://bugs.kde.org/show_bug.cgi?id=429940 --- Comment #19 from Luc --- I am WRONG. Please don't go looking for a solution there. I was convinced it disappeared... but no, the cursor was there and is still there in your latest build. So I guess that problem needs to be resolved. I think I'm getting confused because with the Pixelbook pen it's fine. So it's just that the Wacom tablet is interpreted as a mouse. Sorry for the confusion. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429940] Wacom Intuos Pen Pressure Support on ChromeOS with Krita Android App
https://bugs.kde.org/show_bug.cgi?id=429940 --- Comment #18 from Luc --- Correct. I'd love to double check that, but my is an art teacher and is working from home with covid. She has monopoly of the tablet right now. But I will verify this at lunch time for you since she has the Android version installed. But from memory, that's correct. No cursor in Android version (correct) but no pressure. Your latest version has pressure but now has a cursor. Again, as soon as I can interrupt her, I'll verify this before you go on a wild goose chase. :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429940] Wacom Intuos Pen Pressure Support on ChromeOS with Krita Android App
https://bugs.kde.org/show_bug.cgi?id=429940 --- Comment #16 from Luc --- OK, my wife indicated that it's pretty normal for lag to increase with brush size. With that being said, once the cursor problem solved, maybe you can also have a look at bug id 430829. lol I don't know if you can improve that, but once again there are apps that do a much better job on latency. Anyways, that's another topic. Hopefully you can remove the mouse cursor correctly. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429940] Wacom Intuos Pen Pressure Support on ChromeOS with Krita Android App
https://bugs.kde.org/show_bug.cgi?id=429940 --- Comment #15 from Luc --- Just to add, the latency seems to improve if the brush size is reduced. So when I reduce it, it's much better. Somehow increasing the brush size adds lag. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429940] Wacom Intuos Pen Pressure Support on ChromeOS with Krita Android App
https://bugs.kde.org/show_bug.cgi?id=429940 --- Comment #14 from Luc --- OK, just gave it a shot. Mostly good news... So it appears that it now recognizes pen pressure! Hooray! So things seem to be working. BUT... 1. There is a huge lag, I'm hoping it's because of your comments that it's supposed to be slow and will be fixed once it's finalized properly. I've actually submitted a different request a while back (December) about pen lag but that was using the Pixelbook pen. Wacom WAS super fast but definitely isn't anymore. Anyways, just want to make sure this is expected in this prelim release. 2. The bigger issue left is that no matter what, I have a black mouse cursor present. I can see the brush, but it also has a stuck mouse cursor on top of the canvas. That mouse cursor would need to be removed when you're in the canvas area but reappear when you leave the canvas so when you access menus and such, it would work. But awesome that you got the pen pressure working! Once the basic bugs have been ironed out, I'll get my wife to actually try it. She's the actual artist and is quite proficient with Krita. She'll better be able to evaluate if everything behaves as an artist would want. I'm just the "tech brains" in the family. lol -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429940] Wacom Intuos Pen Pressure Support on ChromeOS with Krita Android App
https://bugs.kde.org/show_bug.cgi?id=429940 --- Comment #10 from Luc --- Thanks for taking this on. Obviously it's the holidays, but as you need any testing from me, don't hesitate to ask. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 430829] New: Pen lag / latency when on ChromeOS (Google Pixel Slate i5)
https://bugs.kde.org/show_bug.cgi?id=430829 Bug ID: 430829 Summary: Pen lag / latency when on ChromeOS (Google Pixel Slate i5) Product: krita Version: 4.4.2-beta1 Platform: Android OS: ChromeOS Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: lafreniere@gmail.com Target Milestone: --- Although the new Krita for Android on a Chromebook is very usable, there is significant lag when using an active stylus as compared to the best apps available. For some reason, MANY art based programs have lag issues when it comes to using the stylus. BUT there are two examples of software that has practically minimal lag. https://canvas.apps.chrome/ is a web based PWA made by Google. When drawing in this program, the lag is incredibly small. It feels practically non existent. https://www.squidnotes.com/ this Android app is not an art based program but for note taking. Regardless, it has achieved similar latency as the Canvas PWA by Google. Both of those examples are the best with pen lag. My wife, a fine arts major, art teacher and avid home artist loves Krita now that it's available on ChromeOS. But watching her draw on Krita vs. Canvas is night and day. She loves all the extra functionality of Krita but sadly the pen lag is a pretty big issue. Canvas on the other hand has no pen lag but severely lacks in features. Squid is just a note taking app, but it's an example of an Android app achieve no lag. So the question becomes, is it possible for Krita to have this level of lag? Squid proves that Android apps can achieve this... Canvas, although a PWA, also proves this. It would be awesome if Krita could have reduced pen lag matching those. More than happy to do any testing required. Merci. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429940] Wacom Intuos Pen Pressure Support on ChromeOS with Krita Android App
https://bugs.kde.org/show_bug.cgi?id=429940 --- Comment #7 from Luc --- (In reply to Sharaf from comment #6) > (In reply to Luc from comment #4) > > Ok, got it done BUT... > > > > I successfully installed it. > > > > But when I enable logging and do strokes, nothing is recorded. I tried > > multiple times using the mouse and the wacom pen. Nothing. It records > > pressing various brushes and stuff just fine. I can see those. But mouse > > clicking isn't recorded at all when drawing lines on the canvas. > > Did you press the "Enable Logging" button in the Log Viewer Docker (bottom > left button https://imgur.com/3AYcNcO.png)? > > > Furthermore, the wacom pen no longer draws at all in this beta. It was > > drawing before the beta, just no pressure. Now it doesn't draw at all. > > This is interesting and could be caused by me removing my old patch for Qt > https://invent.kde.org/graphics/krita/commit/ > 801692e4841afa3c5f1fb7b7305fda1de3b55b29 this does give me a little clue as > to where the problem might lie. Though a proper log would be more useful :) I did. Like I said, I can record other events like pressing a new brush button. But when I click, nothing is recorded at all. I can export a log of button pressing.. but that won't be very useful to you. lol Interesting indeed. Now that I know something was done, I can also tell you that in the last version, the brush was represented by the proper little circle when hovering over the canvas. But now in this beta, I have the circle but also a large mouse cursor. Presumably this mouse cursor shouldn't be there and may explain why it's not drawing. If I use the actual mouse (NOT wacom mouse), then it draws fine and the cursor disappears. So yeah, sounds like you're in the right section of code. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429940] Wacom Intuos Pen Pressure Support on ChromeOS with Krita Android App
https://bugs.kde.org/show_bug.cgi?id=429940 --- Comment #5 from Luc --- Confirmed in About it's 4.4.2-beta1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429940] Wacom Intuos Pen Pressure Support on ChromeOS with Krita Android App
https://bugs.kde.org/show_bug.cgi?id=429940 --- Comment #4 from Luc --- Ok, got it done BUT... I successfully installed it. But when I enable logging and do strokes, nothing is recorded. I tried multiple times using the mouse and the wacom pen. Nothing. It records pressing various brushes and stuff just fine. I can see those. But mouse clicking isn't recorded at all when drawing lines on the canvas. Furthermore, the wacom pen no longer draws at all in this beta. It was drawing before the beta, just no pressure. Now it doesn't draw at all. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429940] Wacom Intuos Pen Pressure Support on ChromeOS with Krita Android App
https://bugs.kde.org/show_bug.cgi?id=429940 --- Comment #3 from Luc --- (In reply to Sharaf from comment #2) > Hello! > > Someone did mention this bug in the past. Unfortunately I don't have the > right hardware to debug this. So, could you please use the beta from > https://krita.org/en/item/first-beta-of-krita-4-4-2/ and then attach the > tablet events log: > https://docs.krita.org/en/contributors_manual/user_support.html#gathering- > information > > Note: I suspect events to come as Touch Events, which we only started > recording since krita-4.4.2 Thanks for responding. I can definitely do this and more than happy to "supply the hardware" to get it working. I'll try and install that later. It's an APK and requires I do a bunch of non standard stuff to get it installed: https://chromeos.dev/en/android-environment/deploying-apps But I will do that and report back once I have the log. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429940] Wacom Intuos Pen Pressure Support on ChromeOS with Krita Android App
https://bugs.kde.org/show_bug.cgi?id=429940 --- Comment #1 from Luc --- Since I made this feature request, I've also discovered that the progressive web app (PWA) https://canvas.apps.chrome/ by Google also detects pen pressure and works really well with Wacom. They have a different problem whereby the cursor remains as an arrow when drawing for some reason. But that's beside the point. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429940] New: Wacom Intuos Pen Pressure Support on ChromeOS with Krita Android App
https://bugs.kde.org/show_bug.cgi?id=429940 Bug ID: 429940 Summary: Wacom Intuos Pen Pressure Support on ChromeOS with Krita Android App Product: krita Version: 4.4.1 Platform: Android OS: ChromeOS Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: lafreniere@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Plug in a Wacom Intuos drawing pad into a Chromebook that supports Android apps. Krita 4.4.1 installed. 2. Try to draw and make it recognize pen pressure. OBSERVED RESULT Pen pressure is completely ignored even if the pen pressure button is available and turned on. It works with the Pixel Slate pen, but not with the Wacom Intuos 4. EXPECTED RESULT What's important to note here is that another popular drawing/photo editing software Photopea (www.photopea.com), IS able to recognize this pen pressure just fine. In fact, it's a web based "app" and yet it's able to use it properly. I'm hoping that Krita would consider adding this device. Many artists use Wacom drawing tools and now with Android Krita on a Chromebook (which are getting really popular with students/school and the generic population), I think it would be worthwhile to get this feature working. SOFTWARE/OS VERSIONS Device: Google Pixel Slate (i5 model) ChromeOS: Stable 86 Android app (early access): Krita 4.4.1 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 364098] In split pane view konsole should respect focus follows mouse but doesn't
https://bugs.kde.org/show_bug.cgi?id=364098 --- Comment #13 from Luc Dufresne --- Created attachment 130951 --> https://bugs.kde.org/attachment.cgi?id=130951&action=edit patch to add terminal focus following mouse in konsole -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 364098] In split pane view konsole should respect focus follows mouse but doesn't
https://bugs.kde.org/show_bug.cgi?id=364098 Luc Dufresne changed: What|Removed |Added CC||l...@dufresne.org --- Comment #12 from Luc Dufresne --- I was missing this feature. So I wrote a quick and dirty patch. (see attachment) As in yakuake, I added a general preference : "Focus terminals when the mouse pointer is moved over them". Seems to work as intended. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419695] New: Crashed during game play that worked earlier
https://bugs.kde.org/show_bug.cgi?id=419695 Bug ID: 419695 Summary: Crashed during game play that worked earlier Product: plasmashell Version: 5.12.8 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kinetic...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.8) Qt Version: 5.9.7 Frameworks Version: 5.55.0 Operating System: Linux 4.12.14-lp151.28.44-default x86_64 Distribution (Platform): openSUSE RPMs -- Information about the crash: Playing the tutorial in WitcherII, the game locked up, not responding to keys, mouse not moving. As nothing was happening, changing to a different virtual desktop was attempted using keystrokes, but not successful. After several seconds (~15), the screen blacked, and came back up with the same content (like a video card reset). This happened twice. The third time, it reset completely, requiring me to log back with password at the login screen (computer did not reboot). -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb9ee6bf500 (LWP 2136))] Thread 11 (Thread 0x7fb8fd199700 (LWP 20693)): #0 0x7fb9e79ca69b in poll () from /lib64/libc.so.6 #1 0x7fb91cdb7861 in ?? () from /usr/lib64/libpulse.so.0 #2 0x7fb91cda9220 in pa_mainloop_poll () from /usr/lib64/libpulse.so.0 #3 0x7fb91cda98b0 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #4 0x7fb91cda9940 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #5 0x7fb91cdb77a9 in ?? () from /usr/lib64/libpulse.so.0 #6 0x7fb91c720428 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-11.1.so #7 0x7fb9e727e4f9 in start_thread () from /lib64/libpthread.so.0 #8 0x7fb9e79d4eef in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7fb8fe4a8700 (LWP 3389)): #0 0x7fb9e79ca69b in poll () from /lib64/libc.so.6 #1 0x7fb91cdb7861 in ?? () from /usr/lib64/libpulse.so.0 #2 0x7fb91cda9220 in pa_mainloop_poll () from /usr/lib64/libpulse.so.0 #3 0x7fb91cda98b0 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #4 0x7fb91cda9940 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #5 0x7fb91cdb77a9 in ?? () from /usr/lib64/libpulse.so.0 #6 0x7fb91c720428 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-11.1.so #7 0x7fb9e727e4f9 in start_thread () from /lib64/libpthread.so.0 #8 0x7fb9e79d4eef in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7fb911a79700 (LWP 2571)): #0 0x7fb9e79c6198 in read () from /lib64/libc.so.6 #1 0x7fb9e22e8c80 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb9e22a3cb8 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb9e22a4150 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fb9e22a42bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fb9e830d7fb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7fb9e82b279a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7fb9e80d0d4a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7fb91439b857 in KCupsConnection::run() () from /usr/lib64/libkcupslib.so #9 0x7fb9e80d5c8d in ?? () from /usr/lib64/libQt5Core.so.5 #10 0x7fb9e727e4f9 in start_thread () from /lib64/libpthread.so.0 #11 0x7fb9e79d4eef in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7fb927e28700 (LWP 2376)): #0 0x7fb9e79c6198 in read () from /lib64/libc.so.6 #1 0x7fb9e22e8c80 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb9e22a3cb8 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb9e22a4150 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fb9e22a42bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fb9e830d7fb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7fb9e82b279a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7fb9e80d0d4a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7fb9ec04e1a6 in ?? () from /usr/lib64/libQt5Quick.so.5 #9 0x7fb9e80d5c8d in ?? () from /usr/lib64/libQt5Core.so.5 #10 0x7fb9e727e4f9 in start_thread () from /lib64/libpthread.so.0 #11 0x7fb9e79d4eef in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7fb939092700 (LWP 2340)): #0 0x7fb9e728487d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fb93e74883b in ?? () from /usr/lib64/dri/r600_dri.so #2 0x7fb93e748547 in ?? () from /usr/lib64/dri/r600_dri.so #3 0x7fb9e727e4f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7fb9e79d4eef in clone () from /l
[kwin] [Bug 387721] "screenshotArea" dbus API needs a "selectArea" method or similar
https://bugs.kde.org/show_bug.cgi?id=387721 --- Comment #3 from Luc Lalonde --- If I launch Gimp using 'dbus-launch' I do not get this error. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387721] "screenshotArea" dbus API needs a "selectArea" method or similar
https://bugs.kde.org/show_bug.cgi?id=387721 Luc Lalonde changed: What|Removed |Added CC||luc.lalo...@polymtl.ca --- Comment #2 from Luc Lalonde --- Would this error message be related to this problem: Execution error for 'Screenshot': GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: No such object path '/Screenshot' Here's my version: gimp-2.10.12-3.module_f30+6174+bc22f659.x86_64 I'm running X11... not Wayland. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411808] Digikam quit unexpectedly
https://bugs.kde.org/show_bug.cgi?id=411808 --- Comment #2 from Luc --- I have downloaded 6.3.0 version from the link below and look like it solve the issue .. Thanx Lot and keep up the good work for that amazing software :) . -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411808] New: Digikam quit unexpectedly
https://bugs.kde.org/show_bug.cgi?id=411808 Bug ID: 411808 Summary: Digikam quit unexpectedly Product: digikam Version: 6.2.0 Platform: unspecified OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: paulins...@gmail.com Target Milestone: --- Created attachment 122594 --> https://bugs.kde.org/attachment.cgi?id=122594&action=edit Crash report from macos SUMMARY Every time I close (file/quit) the digikam app, I am getting an error message few seconds after that say "digikam quit unexpectedly. Click reopen to open the application again. Click report to see more detailed information and send a report to Apple. STEPS TO REPRODUCE Start the application.. wait a bit and then go to file/quit OBSERVED RESULT Popup saying digikam quit unexpectedly EXPECTED RESULT Digikam should close properly and popup should appear SOFTWARE/OS VERSIONS macOS: 10.14.6 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 406609] New: Problem of burning BD-RE 25 GB ISO images K3B 2.0.3
https://bugs.kde.org/show_bug.cgi?id=406609 Bug ID: 406609 Summary: Problem of burning BD-RE 25 GB ISO images K3B 2.0.3 Product: k3b Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Image Formats Assignee: k...@kde.org Reporter: photoshoot...@gmail.com CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Created attachment 119449 --> https://bugs.kde.org/attachment.cgi?id=119449&action=edit screenshot SUMMARY Problem of burning BD-RE 25 GB ISO images STEPS TO REPRODUCE 1. Insert an BD-R preformated BluRay 25 GB 2. Try to burn an iso image (for example : debian-9.8.0-amd64-BD-1.iso) OBSERVED RESULT According to the error popup window (see the pic below), it seems that K3B considers that media is already burned and it does not propose to reformat it. The inserted BluRay disc is blank and has been formatted with the same application for first use. EXPECTED RESULT Burn the media SOFTWARE/OS VERSIONS Linux Debian Wheezy, Jessie and Stretch K3B version : 2.0.3 (on the 3 distro) Media : SONY Corp. BD-RE 25 GB 1-2x Hardware used : burners : - MATSHITA BD-MLT UJ272 (via the USB port) - MATSHITA BD-MLT UJ260AF PC : - HP Pavilion g7 (SATA) - Z83II-Mini-PC (USB) - ASUS K52F (USB) ADDITIONAL INFORMATION : The K3B can format the media and I used it with Nero 4 for linux without problem to burn BluRay ISO like debian-9.8.0-amd64-BD-1.iso. (Nero doesn’t work to format the media). There is also an older burning problem of small 1.4GB DVDs. Burning fails when closing the disc. The problem only applies to 1.4GB DVD-R, not 1.4GB DVD-RE. --- Not tested with new versions of K3B 17.xx.xx or 18.xx.xx -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 401428] New: Okular Crashed While closing PDF Document
https://bugs.kde.org/show_bug.cgi?id=401428 Bug ID: 401428 Summary: Okular Crashed While closing PDF Document Product: okular Version: 1.4.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: l...@pt.lu Target Milestone: --- Application: okular (1.4.3) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.18.0-11-generic x86_64 Distribution: Ubuntu 18.10 -- Information about the crash: - What I was doing when the application crashed: I closed a PDF Document I was reading. The source of said Document is https://www.oevsv.at/export/shared/.content/.galleries/pdf-Downloads/20181114-Prasentation-Novelle-TKG-mit-Amateurfunkdienst.pdf The crash does not seem to be reproducible. -- Backtrace: Application: Okular (okular), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd6344a3800 (LWP 4231))] Thread 2 (Thread 0x7fd62bfff700 (LWP 4233)): #0 0x7fd639a116d9 in __GI___poll (fds=0x7fd6240137f0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fd63788ee46 in g_main_context_poll (priority=, n_fds=1, fds=0x7fd6240137f0, timeout=, context=0x7fd624000bf0) at ../../../../glib/gmain.c:4221 #2 g_main_context_iterate (context=context@entry=0x7fd624000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../../glib/gmain.c:3915 #3 0x7fd63788ef6c in g_main_context_iteration (context=0x7fd624000bf0, may_block=may_block@entry=1) at ../../../../glib/gmain.c:3981 #4 0x7fd639f3615b in QEventDispatcherGlib::processEvents (this=0x7fd624000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fd639ee316b in QEventLoop::exec (this=this@entry=0x7fd62bffed70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7fd639d320b6 in QThread::exec (this=this@entry=0x7fd63a269d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7fd63a1ef545 in QDBusConnectionManager::run (this=0x7fd63a269d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7fd639d3bc87 in QThreadPrivate::start (arg=0x7fd63a269d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:367 #9 0x7fd6398e4164 in start_thread (arg=) at pthread_create.c:486 #10 0x7fd639a1ddef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fd6344a3800 (LWP 4231)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7fd639925535 in __GI_abort () at abort.c:79 #8 0x7fd62a7c19c5 in pa_close_pipe (fds=fds@entry=0x559c68812b00) at pulsecore/core-util.c:2647 #9 0x7fd62a93d0a2 in pa_mainloop_free (m=0x559c68812a30) at pulse/mainloop.c:579 #10 0x7fd62a94cc8d in pa_threaded_mainloop_free (m=0x559c688129f0) at pulse/thread-mainloop.c:137 #11 0x7fd628086c7e in pulse_driver_destroy (c=0x559c68810ec0) at pulse.c:471 #12 0x7fd630d64dd7 in driver_destroy (c=c@entry=0x559c68810ec0) at dso.c:292 #13 0x7fd630d5c658 in ca_context_destroy (c=0x559c68810ec0) at common.c:186 #14 0x7fd631961d40 in NotifyByAudio::~NotifyByAudio (this=0x559c68810e60, __in_chrg=) at ./src/notifybyaudio_canberra.cpp:62 #15 0x7fd631961dd9 in NotifyByAudio::~NotifyByAudio (this=0x559c68810e60, __in_chrg=) at ./src/notifybyaudio_canberra.cpp:59 #16 0x7fd639f0b6ab in QObjectPrivate::deleteChildren (this=this@entry=0x559c6880af40) at kernel/qobject.cpp:1997 #17 0x7fd639f143a4 in QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:1025 #18 0x7fd63193ac89 in KNotificationManagerSingleton::~KNotificationManagerSingleton (this=, __in_chrg=) at ./src/knotificationmanager.cpp:73 #19 (anonymous namespace)::Q_QGS_s_self::Holder::~Holder (this=, __in_chrg=) at ./src/knotificationmanager.cpp:73 #20 0x7fd63994742c in __run_exit_handlers (status=0, listp=0x7fd639ae7718 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #21 0x7fd63994755a in __GI_exit (status=) at exit.c:139 #22 0x7fd6399270a2 in __libc_start_main (main=0x559c65ee82b0 , argc=2, argv=0x7fff969298f8, init=, fini=, rtld_fini=, stack_end=0x7fff969298e8) at ../csu/libc-start.c:342 #23 0x559c65ee9f4a in _start () at ./shell/main.cpp:66 [Inferior 1 (process 4231) detached] The reporter indicates this bug may be a duplicate of or related to bug 393478. Possible duplicates by query: bug 395158, bug 394824. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 219727] Kdevelop 4 error on file, new ( LANG=fr_CA.UTF-8 only )
https://bugs.kde.org/show_bug.cgi?id=219727 Luc Lalonde changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #10 from Luc Lalonde --- Problem seems to be solved in recent version: kdevelop-5.2.3-1.fc28.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 357573] Konsole freeze if executed on secondary dual-head (Nvidia Twinview) display
https://bugs.kde.org/show_bug.cgi?id=357573 Luc Lalonde changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Luc Lalonde --- Problems seems to be solved: Fedora release 28 kernel-4.18.13-200.fc28.x86_64 Nvidia video driver: 396.54 konsole5-18.04.3-1.fc28.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 397159] New: Kdevelop crashes when debugging.
https://bugs.kde.org/show_bug.cgi?id=397159 Bug ID: 397159 Summary: Kdevelop crashes when debugging. Product: kdevelop Version: 5.2.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: psylu...@gmail.com Target Milestone: --- Application: kdevelop (5.2.3) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.14.57-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: I was trying to debug my application. I can't reproduce the error. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3760962e00 (LWP 30361))] Thread 13 (Thread 0x7f36ef236700 (LWP 30521)): #0 0x7f375cfbdea9 in poll () at /usr/lib/libc.so.6 #1 0x7f3745134673 in () at /usr/lib/libpulse.so.0 #2 0x7f3745125990 in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #3 0x7f3745125fe0 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7f3745126091 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7f37451345ae in () at /usr/lib/libpulse.so.0 #6 0x7f373d9e89fc in () at /usr/lib/pulseaudio/libpulsecommon-12.2.so #7 0x7f375672a075 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f375cfc853f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f36eda33700 (LWP 30407)): #0 0x7f375672fffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f375d6d92fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f375213c139 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f3752140009 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f375213b1fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f375213e059 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f375d6d8b45 in () at /usr/lib/libQt5Core.so.5 #7 0x7f375672a075 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f375cfc853f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f36ee234700 (LWP 30406)): #0 0x7f375cf53470 in malloc () at /usr/lib/libc.so.6 #1 0x7f375d722e56 in QHashData::allocateNode(int) () at /usr/lib/libQt5Core.so.5 #2 0x7f3702ec1b60 in () at /usr/lib/libKDevClangPrivate.so.30 #3 0x7f3702eabb84 in () at /usr/lib/libKDevClangPrivate.so.30 #4 0x7f3702ebe92d in () at /usr/lib/libKDevClangPrivate.so.30 #5 0x7f3702be3985 in () at /usr/lib/libclang.so.6 #6 0x7f3702be68d6 in () at /usr/lib/libclang.so.6 #7 0x7f3702be9643 in () at /usr/lib/libclang.so.6 #8 0x7f3702be3463 in () at /usr/lib/libclang.so.6 #9 0x7f3702beb6a6 in clang_visitChildren () at /usr/lib/libclang.so.6 #10 0x7f3702eb3db4 in () at /usr/lib/libKDevClangPrivate.so.30 #11 0x7f3702ec067b in () at /usr/lib/libKDevClangPrivate.so.30 #12 0x7f3702be3985 in () at /usr/lib/libclang.so.6 #13 0x7f3702be5b2e in () at /usr/lib/libclang.so.6 #14 0x7f3702be5c2c in () at /usr/lib/libclang.so.6 #15 0x7f3702be3463 in () at /usr/lib/libclang.so.6 #16 0x7f3702beb6a6 in clang_visitChildren () at /usr/lib/libclang.so.6 #17 0x7f3702eab0ac in () at /usr/lib/libKDevClangPrivate.so.30 #18 0x7f3702ebc476 in () at /usr/lib/libKDevClangPrivate.so.30 #19 0x7f3702be3985 in () at /usr/lib/libclang.so.6 #20 0x7f3702be5b2e in () at /usr/lib/libclang.so.6 #21 0x7f3702be5c2c in () at /usr/lib/libclang.so.6 #22 0x7f3702be3764 in () at /usr/lib/libclang.so.6 #23 0x7f3702beb6a6 in clang_visitChildren () at /usr/lib/libclang.so.6 #24 0x7f3702ea5e26 in Builder::visit(CXTranslationUnitImpl*, void*, QHash const&, bool) () at /usr/lib/libKDevClangPrivate.so.30 #25 0x7f3702ecd7cd in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features, QHash&, ClangIndex*, std::function const&) () at /usr/lib/libKDevClangPrivate.so.30 #26 0x7f3702eccff8 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features, QHash&, ClangIndex*, std::function const&) () at /usr/lib/libKDevClangPrivate.so.30 #27 0x7f3702eccff8 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features, QHash&, ClangIndex*, std::function const&) () at /usr/lib/libKDevClangPrivate.so.30 #28 0x7f3702eccff8 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features, QHas
[krfb] [Bug 395895] New: Krfb icon does not show on top bar - though present
https://bugs.kde.org/show_bug.cgi?id=395895 Bug ID: 395895 Summary: Krfb icon does not show on top bar - though present Product: krfb Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: grundleb...@googlemail.com Reporter: luc.fruch...@u-psud.fr Target Milestone: --- I have recently installed 4.14.8 KDE package on two similar systems using Scientific Linux 7.5. On one of the systems, the grey icon on the top bar for Krfb desktop does not show. It is there, however, and I can click on topbar to open it. Otherwise, it works nicely on both systems. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 394694] New: Showfoto crashes on change picture size
https://bugs.kde.org/show_bug.cgi?id=394694 Bug ID: 394694 Summary: Showfoto crashes on change picture size Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: l...@sierens.com Target Milestone: --- Application: showfoto (4.0.0) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 4.4.0-127-generic x86_64 Distribution: Linux Mint 17.3 Rosa -- Information about the crash: Trying to chnage the size of my picture Showfoto crashes. The crash can be reproduced every time. -- Backtrace: Application: showFoto (showfoto), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcd8ea52840 (LWP 4248))] Thread 2 (Thread 0x7fcd6a01d700 (LWP 4251)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fcd8bb99816 in wait (time=18446744073709551615, this=0x28590d0) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=this@entry=0x2854e80, mutex=mutex@entry=0x2854e78, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7fcd8e4758aa in Digikam::ParkingThread::run (this=0x2854e60) at /build/buildd/digikam-4.0.0/core/libs/threads/threadmanager.cpp:119 #4 0x7fcd8bb9932f in QThreadPrivate::start (arg=0x2854e60) at thread/qthread_unix.cpp:349 #5 0x7fcd8962e184 in start_thread (arg=0x7fcd6a01d700) at pthread_create.c:312 #6 0x7fcd8b02403d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7fcd8ea52840 (LWP 4248)): [KCrash Handler] #6 Digikam::DImg::getIccProfile (this=0x0) at /build/buildd/digikam-4.0.0/core/libs/dimg/dimg.cpp:990 #7 0x7fcd8e4c994b in Digikam::ImageGuideWidget::ImageGuideWidget (this=0x2d0, parent=, spotVisible=, guideMode=0, guideColor=..., guideSize=1, blink=false, type=Digikam::ImageIface::FullImage) at /build/buildd/digikam-4.0.0/core/utilities/imageeditor/widgets/imageguidewidget.cpp:142 #8 0x7fcd6888ebf9 in DigikamTransformImagePlugin::ResizeTool::ResizeTool (this=0x28401b0, parent=) at /build/buildd/digikam-4.0.0/core/imageplugins/transform/resizetool.cpp:181 #9 0x7fcd688864f1 in DigikamTransformImagePlugin::ImagePlugin_Transform::slotResize (this=0x2d94740) at /build/buildd/digikam-4.0.0/core/imageplugins/transform/imageplugin_transform.cpp:173 #10 0x7fcd8bcaf87a in QMetaObject::activate (sender=sender@entry=0x2d9af00, m=m@entry=0x7fcd8d141de0 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffedfe5c4d0) at kernel/qobject.cpp:3539 #11 0x7fcd8c691a62 in QAction::triggered (this=this@entry=0x2d9af00, _t1=false) at .moc/release-shared/moc_qaction.cpp:276 #12 0x7fcd8c693433 in QAction::activate (this=this@entry=0x2d9af00, event=event@entry=QAction::Trigger) at kernel/qaction.cpp:1257 #13 0x7fcd8cac1509 in QMenuPrivate::activateCausedStack (this=this@entry=0x2d3d330, causedStack=..., action=action@entry=0x2d9af00, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1038 #14 0x7fcd8cac5a39 in QMenuPrivate::activateAction (this=0x2d3d330, action=0x2d9af00, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1130 #15 0x7fcd8cac9405 in QMenu::mouseReleaseEvent (this=this@entry=0x2d2cd30, e=e@entry=0x7ffedfe5cc00) at widgets/qmenu.cpp:2372 #16 0x7fcd8d45e615 in KMenu::mouseReleaseEvent (this=0x2d2cd30, e=0x7ffedfe5cc00) at ../../kdeui/widgets/kmenu.cpp:464 #17 0x7fcd8c6e751a in QWidget::event (this=this@entry=0x2d2cd30, event=event@entry=0x7ffedfe5cc00) at kernel/qwidget.cpp:8376 #18 0x7fcd8cac983b in QMenu::event (this=0x2d2cd30, e=0x7ffedfe5cc00) at widgets/qmenu.cpp:2481 #19 0x7fcd8c697e2c in QApplicationPrivate::notify_helper (this=this@entry=0x2558790, receiver=receiver@entry=0x2d2cd30, e=e@entry=0x7ffedfe5cc00) at kernel/qapplication.cpp:4567 #20 0x7fcd8c69e5dd in QApplication::notify (this=this@entry=0x7ffedfe5d580, receiver=receiver@entry=0x2d2cd30, e=e@entry=0x7ffedfe5cc00) at kernel/qapplication.cpp:4110 #21 0x7fcd8d3a7cca in KApplication::notify (this=0x7ffedfe5d580, receiver=0x2d2cd30, event=0x7ffedfe5cc00) at ../../kdeui/kernel/kapplication.cpp:311 #22 0x7fcd8bc9b4dd in QCoreApplication::notifyInternal (this=0x7ffedfe5d580, receiver=receiver@entry=0x2d2cd30, event=event@entry=0x7ffedfe5cc00) at kernel/qcoreapplication.cpp:953 #23 0x7fcd8c69dd93 in sendEvent (event=, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #24 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x2d2cd30, event=event@entry=0x7ffedfe5cc00, alienWidget=alienWidget@entry=0x0, nativeWidget=n
[kipiplugins] [Bug 369289] New: dngconverter crashes when converting Olympus (.ORF) files
https://bugs.kde.org/show_bug.cgi?id=369289 Bug ID: 369289 Summary: dngconverter crashes when converting Olympus (.ORF) files Product: kipiplugins Version: 4.12.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kde-imag...@kde.org Reporter: arzi...@gmail.com Application: dngconverter (4.12.0) KDE Platform Version: 4.14.16 Qt Version: 4.8.7 Operating System: Linux 4.4.0-38-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Crash happens after pushing "Convert" in the GUI with one or more files loaded in the window. This is on Xubuntu (dngconverter is the only KDE installed program. Xubuntu installer has also installed prereq libraries and other stuff). The crash can be reproduced every time. -- Backtrace: Application: DNG Image Converter (dngconverter), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1942e32980 (LWP 9965))] Thread 8 (Thread 0x7f1916d3a700 (LWP 9974)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f194118f3a6 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f194216dc9c in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x7f19421709a3 in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x7f194216f4ff in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #5 0x7f194118ee3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f193ffe16fa in start_thread (arg=0x7f1916d3a700) at pthread_create.c:333 #7 0x7f193f476b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f191753b700 (LWP 9973)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f194118f3a6 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f194216dc9c in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x7f19421709a3 in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x7f194216f4ff in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #5 0x7f194118ee3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f193ffe16fa in start_thread (arg=0x7f191753b700) at pthread_create.c:333 #7 0x7f193f476b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f1917d3c700 (LWP 9972)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f194118f3a6 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f194216dc9c in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x7f19421709a3 in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x7f19421709bc in ?? () from /usr/lib/libthreadweaver.so.4 #5 0x7f194216f4ff in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #6 0x7f194118ee3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f193ffe16fa in start_thread (arg=0x7f1917d3c700) at pthread_create.c:333 #8 0x7f193f476b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f192501e700 (LWP 9971)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f194118f3a6 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f194216dc9c in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x7f19421709a3 in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x7f19421709bc in ?? () from /usr/lib/libthreadweaver.so.4 #5 0x7f194216f4ff in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #6 0x7f194118ee3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f193ffe16fa in start_thread (arg=0x7f192501e700) at pthread_create.c:333 #8 0x7f193f476b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f192581f700 (LWP 9970)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f194118f3a6 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f1942615a14 in KDcrawIface::RActionThreadBase::run() () from /usr/lib/libkdcraw.so.23 #3 0x7f194118ee3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f193ffe16fa in start_thread (arg=0x7f192581f700) at pthread_create.c:333 #5 0x7f193f476b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f1926020700 (LWP 9969)): #0 __li
[Breeze] [Bug 356343] Rendering issue after upgrade to kwin 5.5
https://bugs.kde.org/show_bug.cgi?id=356343 Luc Lalonde changed: What|Removed |Added CC||luc.lalo...@polymtl.ca --- Comment #20 from Luc Lalonde --- This bug (seen on dual-head setup) reared is solved for me since I upgraded to Plasma 5.5.4. Yay! I can come back from GNOME 3 purgatory and start using KDE again ;-) Thank You! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 357388] Konsole on 2nd monitor shows only empty window-frame
https://bugs.kde.org/show_bug.cgi?id=357388 Luc Lalonde changed: What|Removed |Added CC||luc.lalo...@polymtl.ca -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 353357] kmix uses 100% cpu (with Kubuntu 15.04 and KDE5)
https://bugs.kde.org/show_bug.cgi?id=353357 Luc Lalonde changed: What|Removed |Added CC||luc.lalo...@polymtl.ca --- Comment #2 from Luc Lalonde --- I can confirm this problem: Platform: Fedora 22 Kernel: 4.2.8-200.fc22.x86_64 Kmix: 15.04 The whole Plasma 5 session becomes unuseable until I kill Kmix. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 357573] New: Konsole freeze if executed on secondary dual-head (Nvidia Twinview) display
https://bugs.kde.org/show_bug.cgi?id=357573 Bug ID: 357573 Summary: Konsole freeze if executed on secondary dual-head (Nvidia Twinview) display Product: konsole Version: 15.08.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: luc.lalo...@polymtl.ca If I try to execute Konsole on the second display (right-click, terminal), I get a frozen Konsole window. However, if there's already a Konsole active in the main display, I don't have this problem. Reproducible: Always Steps to Reproduce: 1. right-click, terminal in secondary display 2. must me first Konsole window for error to occur Actual Results: Frozen Konsole window appears. Expected Results: Should be getting a useable Konsole window. - Fedora 22 - kernel-4.2.8-200.fc22.x86_64 - Nvidia video driver: 352.63 - konsole5-15.08.3-1.fc22.x86_64 -- You are receiving this mail because: You are watching all bug changes.
