[frameworks-knewstuff] [Bug 416328] system settings crashes in KNSCore::Engine::loadProviders() when I click on "Get new scripts..." button
https://bugs.kde.org/show_bug.cgi?id=416328 --- Comment #16 from Tony --- This one can't be reproduced anymore on my end. Also, #13 shows a different issue, kwin ralated if i am not mistaken. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 440565] Copy text with crtl + c does not work
https://bugs.kde.org/show_bug.cgi?id=440565 --- Comment #2 from Armin Mohring --- This affects all PDF files, which I have tested. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423039] all version of plasma after 5.18.5 broke keyboard layout after close the session
https://bugs.kde.org/show_bug.cgi?id=423039 Cruz Enrique changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Cruz Enrique --- Seems like KDE Plasma 5.22.4 solve the problem. I have re-emerge X.org with INPUT_DEVICES="libinput" and restart the display manager and seems to be working. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440368] Color picker not working after creating a new layer
https://bugs.kde.org/show_bug.cgi?id=440368 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 439520] Latte dock 0.9.97 crashes on startup
https://bugs.kde.org/show_bug.cgi?id=439520 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.
[krita] [Bug 439383] Brush bug, the brush goes with a big delay.
https://bugs.kde.org/show_bug.cgi?id=439383 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 112663] Incoming messages that are not looked on before restart of Kopete does not show up again as new message after restart.
https://bugs.kde.org/show_bug.cgi?id=112663 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 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.
[krita] [Bug 439862] cosmetic artifacts on canvas 5.0.0-prealpha (git c75e336)
https://bugs.kde.org/show_bug.cgi?id=439862 --- Comment #7 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439830] Extreme high values of dpi make the Text Tool not work (no warning)
https://bugs.kde.org/show_bug.cgi?id=439830 --- Comment #19 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.
[ksplash] [Bug 396070] ksplashqml core dumps after recent update
https://bugs.kde.org/show_bug.cgi?id=396070 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416212] Crash when saving a document after using liquify
https://bugs.kde.org/show_bug.cgi?id=416212 --- Comment #18 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 440199] Icons in file dialog and brush preset docker are black on dark, making them less recognizable
https://bugs.kde.org/show_bug.cgi?id=440199 --- Comment #2 from Lynx3d --- I just tried the proxy style idea, but that can only solve part of the issue. The QLineEdit clear button and the top buttons of the file dialog can be overridden, but that's really more a way to provide icons the style engine itself requests, what icons really get queried differs between styles on things like QMdiArea elements. On Linux the icons for files (mime types) and folders come from the system icon theme, so you still have black folder icons on dark grey ground etc. Since you seem to be using Breeze icons, what can be done with a few lines of code is switching breeze and breeze-dark icon themes if we load a color theme, at least on Ubuntu they are bundled in the same package. We could also include them in Krita, but they'd have to be organized according to freedesktop spec for QIcon routines to find them. But then we have one more thing that doesn't fully update on color theme changes until you restart krita, I couldn't find a way to make existing QLineEdit to reload the icons yet... And if the user doesn't want to use the a fixed icon theme like Breeze, we can't really help it. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 440533] XDG Screen sharing is broken, bump portal libraries?
https://bugs.kde.org/show_bug.cgi?id=440533 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 440581] New: Language interface cannot be converted
https://bugs.kde.org/show_bug.cgi?id=440581 Bug ID: 440581 Summary: Language interface cannot be converted Product: kstars Version: 3.5.4 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: rex6...@126.com Target Milestone: --- SUMMARY Language interface cannot be converted Only English interface option Unable to convert Chinese interface（zh_TW） STEPS TO REPRODUCE 1. HELP 2. Configure Language SOFTWARE/OS VERSIONS macOS: 10.14.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 440580] New: Language interface cannot be converted
https://bugs.kde.org/show_bug.cgi?id=440580 Bug ID: 440580 Summary: Language interface cannot be converted Product: kstars Version: 3.5.4 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: rex6...@126.com Target Milestone: --- Created attachment 140500 --> https://bugs.kde.org/attachment.cgi?id=140500=edit Language interface cannot be converted SUMMARY Language interface cannot be converted Only English interface option Unable to convert Chinese interface（zh_TW） STEPS TO REPRODUCE 1. HELP 2. Configure Language SOFTWARE/OS VERSIONS macOS: 10.14.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 195470] Regional module cannot install/set system language
https://bugs.kde.org/show_bug.cgi?id=195470 REX changed: What|Removed |Added CC||rex6...@126.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 431936] Audio with multiple audio stream: playback issue when skipping to point in timeline
https://bugs.kde.org/show_bug.cgi?id=431936 farid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #12 from farid --- Would you please test the latest nightly appimage and let us know if it works now? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440467] screenlocker virtual keyboard broken on wayland
https://bugs.kde.org/show_bug.cgi?id=440467 --- Comment #5 from Cane Kostovski --- Thank you very much. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440421] Dynamic-adaptive blur in the panel (Original Text: Динамическое-адаптивное размытие в панели задач)
https://bugs.kde.org/show_bug.cgi?id=440421 Nate Graham changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REOPENED|RESOLVED --- Comment #6 from Nate Graham --- Yes, I'm sure. :) We already have per-panel adaptive opacity, so you can already accomplish what you want to do, as far as I can tell. Allowing people actually control the *amount* of opacity is super visual overkill. :) This is what we have themes for. Theme authors make those kinds of decisions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440521] When changing the global scale (in the display settings), the panel does not change its size
https://bugs.kde.org/show_bug.cgi?id=440521 Nate Graham changed: What|Removed |Added Resolution|UPSTREAM|WAITINGFORINFO --- Comment #5 from Nate Graham --- In the bottom left corner is a list of sessions. You click on it and it will show you alternatives. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440569] Virtual keyboard appears whenever an input field is activated for any reason even when a physical keyboard is attached
https://bugs.kde.org/show_bug.cgi?id=440569 --- Comment #2 from Nate Graham --- I'll be happy to test any mayhem-producing attempts :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439911] Popup virtual keyboard as a new action
https://bugs.kde.org/show_bug.cgi?id=439911 --- Comment #3 from Nate Graham --- For what it's worth, the keyboard appeared correctly with all of the apps I regularly use while testing tonight. So if you think it's too much effort for a hypothetical problem, I understand. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project
https://bugs.kde.org/show_bug.cgi?id=439592 --- Comment #11 from Eugene Shalygin --- Removing "0"s from that file allows KDevelop to finish project parsing without crashing. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 440572] Password input field shows plain text characters when the virtual keyboard is first used to enter text
https://bugs.kde.org/show_bug.cgi?id=440572 --- Comment #2 from Nate Graham --- e... lives. :) I don't know where the text field does its lovin'. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project
https://bugs.kde.org/show_bug.cgi?id=439592 --- Comment #10 from Eugene Shalygin --- Debug build crashes as well with the same backtrace as in the OP. 1. rm -fr ~/.cache/kdevduchain 2. open the cmake project and wait It crashes and at that moment the parsing progress shows "Tests/RunCMake/Syntax/NullTerminatedArgument.cmake" -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 440579] New: Crash closing Signal App
https://bugs.kde.org/show_bug.cgi?id=440579 Bug ID: 440579 Summary: Crash closing Signal App Product: plasma-systemmonitor Version: 5.22.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: wfaeh...@freenet.de CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 140499 --> https://bugs.kde.org/attachment.cgi?id=140499=edit Kcrash log file SUMMARY Crash closing Signal App STEPS TO REPRODUCE 1. Open Signal 2. Opens Plasma Systemmonitor 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385816] KDevelop has problems with multiple projects with same structure
https://bugs.kde.org/show_bug.cgi?id=385816 --- Comment #5 from Eugene Shalygin --- Also had two branches checked out in different dirs and both open in the same session. And KDevelop jumped to the source code in the second project from the first one when using "Jump to declaration" or "Jump to definition". Even after I unloaded the second project. And even after I then restarted KDevelop. And after I removed ~/.cache/kdevduchain (and restarted KDevelop once again). How is that possible? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440401] [Wayland] Huge performance drop since 5.22.3
https://bugs.kde.org/show_bug.cgi?id=440401 --- Comment #4 from Charles Bouchard-Légaré --- I don't know about KWin, I created the issue in `plasmashell` originally. What info could I provide to help? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440569] Virtual keyboard appears whenever an input field is activated for any reason even when a physical keyboard is attached
https://bugs.kde.org/show_bug.cgi?id=440569 Aleix Pol changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Aleix Pol --- Agreed. I've looked into it and have not entirely found the right hook so everything works properly. At the moment we are abusing the internal keyboard focus property also for touch and I'm afraid changing it will break mayhem (i.e. we don't want to end up with different focus surfaces for the keyboard and touch). I'm confident it can be done, I've to spend some more time with it to find the right place to change it. (Of course, if someone beats me to it, it's very welcome). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385816] KDevelop has problems with multiple projects with same structure
https://bugs.kde.org/show_bug.cgi?id=385816 Eugene Shalygin changed: What|Removed |Added CC||eugene.shalygin+bugzilla.kd ||e...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439911] Popup virtual keyboard as a new action
https://bugs.kde.org/show_bug.cgi?id=439911 Aleix Pol changed: What|Removed |Added Version|unspecified |5.22.4 Product|systemsettings |kwin Component|kcm_kwintouchscreen |virtual-keyboard --- Comment #2 from Aleix Pol --- This is not all that simple, we'd need first to have a mode for kwin to communicate with clients and send them keyboard events rather than text input which is what we generally do. This is a general requirement for XWayland applications I guess, so it probably should be done eventually. Either way, I'd say insisting on these "applications that don't behave" to behave is the only way to have a good experience overall in the long term. In the meantime, sure, we can add workarounds like that. It's not trivial though and it will require a considerable amount of effort. Moving the bug to KWin as it's not a settings issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440464] Screen rotation broken on wayland
https://bugs.kde.org/show_bug.cgi?id=440464 --- Comment #2 from log4...@gmail.com --- (In reply to Nate Graham from comment #1) > Sounds like KWin itself is crashing. Any chance you could get a backtrace of > the crash? Managed to get one. This took a few unsuccessful rotation attempts, turning second monitor on and off and moving screens around, but it happened eventually. #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x7f60fa9a792e in __GI_abort () at abort.c:100 #2 0x7f60fa9a7729 in __assert_fail_base (fmt=0x7f60fab3d588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7f60faf2b768 "0 && \"Couldn't find current GLX or EGL context.\\n\"", file=0x7f60faf2b6c0 "../src/dispatch_common.c", line=863, function=) at assert.c:92 #3 0x7f60fa9b8f36 in __GI___assert_fail (assertion=assertion@entry=0x7f60faf2b768 "0 && \"Couldn't find current GLX or EGL context.\\n\"", file=file@entry=0x7f60faf2b6c0 "../src/dispatch_common.c", line=line@entry=863, function=function@entry=0x7f60faf2b7a0 <__PRETTY_FUNCTION__.38427> "epoxy_get_proc_address") at assert.c:101 #4 0x7f60faf09a9f in epoxy_get_proc_address (name=0x7f60faf1a4d9 "glDeleteProgram") at ../src/dispatch_common.c:863 #5 epoxy_get_proc_address (name=0x7f60faf1a4d9 "glDeleteProgram") at ../src/dispatch_common.c:839 #6 0x7f60faedf6da in epoxy_glDeleteProgram_resolver () at src/gl_generated_dispatch.c:81668 #7 epoxy_glDeleteProgram_global_rewrite_ptr (program=37) at src/gl_generated_dispatch.c:49458 #8 0x7f60f402349a in QScopedPointerDeleter::cleanup (pointer=0x5606cf626e80) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qscopedpointer.h:52 #9 QScopedPointer >::~QScopedPointer (this=0x5606cf0f0bd8, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qscopedpointer.h:107 #10 KWin::LanczosFilter::~LanczosFilter (this=0x5606cf0f0bb0, __in_chrg=) at ./src/plugins/scenes/opengl/lanczosfilter.cpp:47 #11 0x7f60f40234ed in KWin::LanczosFilter::~LanczosFilter (this=0x5606cf0f0bb0, __in_chrg=) at ./src/plugins/scenes/opengl/lanczosfilter.cpp:47 #12 0x7f60f4025ef1 in KWin::SceneOpenGL2operator() (__closure=0x5606cf75fd50) at ./src/plugins/scenes/opengl/scene_opengl.cpp:1093 #13 QtPrivate::FunctorCall, QtPrivate::List<>, void, KWin::SceneOpenGL2::performPaintWindow(KWin::EffectWindowImpl*, int, const QRegion&, KWin::WindowPaintData&):: >::call (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146 #14 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256 #15 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x5606cf75fd40, r=, a=, ret=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:443 #16 0x7f60fb26377e in QtPrivate::QSlotObjectBase::call (a=0x7ffe2fb14ac0, r=0x5606ce0224f0, this=0x5606cf75fd40) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #17 doActivate (sender=0x5606cdf53f50, signal_index=4, argv=0x7ffe2fb14ac0) at kernel/qobject.cpp:3886 #18 0x7f60fb25cb47 in QMetaObject::activate (sender=, m=m@entry=0x7f60fceb8f00 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #19 0x7f60fcbf0347 in KWin::Screens::changed (this=) at ./obj-x86_64-linux-gnu/src/kwin_autogen/EWIEGA46WW/moc_screens.cpp:272 #20 0x7f60fcc2d6df in KWin::AbstractWaylandOutput::applyChanges (this=0x5606cdef89d0, changeSet=0x5606cf37e2b0) at ./src/screens.h:227 #21 0x7f60fcce4763 in KWin::Platform::requestOutputsChange (this=0x5606cdee1620, config=0x5606cf796460) at ./src/platform.cpp:133 #22 0x7f60fb26377e in QtPrivate::QSlotObjectBase::call (a=0x7ffe2fb14d80, r=0x5606cdecd6a0, this=0x5606cdedddc0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #23 doActivate (sender=0x5606cdeddc90, signal_index=3, argv=0x7ffe2fb14d80) at kernel/qobject.cpp:3886 #24 0x7f60fbc479a3 in KWaylandServer::OutputManagementInterface::configurationChangeRequested(KWaylandServer::OutputConfigurationInterface*) () from /lib/x86_64-linux-gnu/libKWaylandServer.so.5 #25 0x7f60f7fc1ff5 in ffi_call_unix64 () at ../src/x86/unix64.S:101 #26 0x7f60f7fc140a in ffi_call_int (cif=, fn=, rvalue=, avalue=, closure=) at ../src/x86/ffi64.c:669 #27 0x7f60f93d4628 in wl_closure_invoke (closure=closure@entry=0x5606cf779850, flags=flags@entry=2, target=, target@entry=0x5606ce2b1ba0, opcode=opcode@entry=5, data=, data@entry=0x5606ceee65d0) at ../src/connection.c:1018 #28 0x7f60f93d09e2 in wl_client_connection_data (fd=, mask=, data=0x5606ceee65d0) at ../src/wayland-server.c:432 #29 0x7f60f93d265a in wl_event_loop_dispatch (loop=0x5606cdeac010, timeout=) at ../src/event-loop.c:1027 #30 0x7f60fbc5a64c in KWaylandServer::Display::dispatchEvents() () from /lib/x86_64-linux-gnu/libKWaylandServer.so.5 #31 0x7f60fb26377e in
[kdeconnect] [Bug 440578] New: Device won't show up
https://bugs.kde.org/show_bug.cgi?id=440578 Bug ID: 440578 Summary: Device won't show up Product: kdeconnect Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: windows-application Assignee: piyushaggarwal...@gmail.com Reporter: shafic...@gmail.com Target Milestone: --- SUMMARY My Android device isn't showing up on my desktop application i have both devices connected on the same network but it still doesn't show up STEPS TO REPRODUCE 1. open kde windows app 2. go to configure 3. press refresh OBSERVED RESULT no devices shows up EXPECTED RESULT a android device should be detected 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.
[kdenlive] [Bug 440577] New: Clip Monitor - Extract Frame & Extract Frame To Project - Not At Playhead
https://bugs.kde.org/show_bug.cgi?id=440577 Bug ID: 440577 Summary: Clip Monitor - Extract Frame & Extract Frame To Project - Not At Playhead Product: kdenlive Version: 21.04.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: stephens...@gmail.com Target Milestone: --- SUMMARY Clip Monitor - Extract Frame & Extract Frame To Project Does Not Return Still At Playhead STEPS TO REPRODUCE 1. Activate Proxies and set Preview Resolution to 270p 2. Drag in 4K media - media is proxied 3. Set In and Out points on a clip in the Clip Monitor - drag to Timeline 4. Complete edit with subsequent clips 5. Come back to this particular clip - find a spot in the In and Out area on the Clip Monitor, uncheck Proxy Clip, set Preview Resolution to 1:1 and Extract Frame or Extract Frame To Project OBSERVED RESULT It selected a still 12s14f back from the playhead. EXPECTED RESULT Select a still at the playhead in the Clip Monitor. SOFTWARE/OS VERSIONS Windows: 10 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 (built against 5.15.2) ADDITIONAL INFORMATION The windows windowing system SOLUTION I set In and Out points at the playhead (i.e. 1 frame) in the Clip Monitor on the clip and dragged to timeline. Placed playhead at start of the single frame on the timeline (it appears in the Project Monitor). Ensuring Proxy Clip is unchecked, and Preview Resolution is 1:1, Extract Frame from Project Monitor for a successful still. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440567] Ability to change the widget icon
https://bugs.kde.org/show_bug.cgi?id=440567 Time changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439513] Klipper interferes with XWayland: Copying text works only every second time
https://bugs.kde.org/show_bug.cgi?id=439513 --- Comment #12 from Anton Kreuzkamp --- I don't always see a blank entry appear, but there is always exactly one blank entry floating around in my klipper history (and pasting doesn't work when it's the upper most). The stdout-output of klipper clearly indicates that more than one entry is created (probably afterwards filtered by some duplication removal). The bug only happens with the "Prevent empty clipboard" is activated (above I wrote "only when IgnoreSelection is set", that was by mistake) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439921] Often widgets can't be moved with touch
https://bugs.kde.org/show_bug.cgi?id=439921 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Keywords||usability, wayland Ever confirmed|0 |1 --- Comment #3 from Nate Graham --- Can reproduce by dragging a desktop widget with touch and then tapping an empty area of the wallpaper to hide the resize handles. The next time I press-and-hold-and-drag, it will fail. I need to "de-focus" it or something by touching the wallpaper a few times and then it will work again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440521] When changing the global scale (in the display settings), the panel does not change its size
https://bugs.kde.org/show_bug.cgi?id=440521 Time changed: What|Removed |Added Resolution|WAITINGFORINFO |UPSTREAM -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439513] Klipper interferes with XWayland: Copying text works only every second time
https://bugs.kde.org/show_bug.cgi?id=439513 --- Comment #11 from Anton Kreuzkamp --- Created attachment 140498 --> https://bugs.kde.org/attachment.cgi?id=140498=edit klipperrc Here is the config of klipper. The bug happens only when IgnoreSelection is set to true. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439251] Firefox does not remember window size on wayland
https://bugs.kde.org/show_bug.cgi?id=439251 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #7 from Nate Graham --- Created attachment 140497 --> https://bugs.kde.org/attachment.cgi?id=140497=edit Wayland debug log from me too, for good measure -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439251] Firefox does not remember window size on wayland
https://bugs.kde.org/show_bug.cgi?id=439251 --- Comment #6 from Nate Graham --- Can reproduce with Firefox running in native Wayland mode. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440421] Dynamic-adaptive blur in the panel (Original Text: Динамическое-адаптивное размытие в панели задач)
https://bugs.kde.org/show_bug.cgi?id=440421 Time changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INTENTIONAL |--- Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440566] Ability to change the widget icon
https://bugs.kde.org/show_bug.cgi?id=440566 Time changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424731] [Wayland] Clipboard Ctrl+C not working right click copy working XWayland
https://bugs.kde.org/show_bug.cgi?id=424731 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=424754| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439765] Clipboard is intermittently broken in the Wayland session when "Prevent Empty Clipboard" is enabled
https://bugs.kde.org/show_bug.cgi?id=439765 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=424754| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424649] Cannot paste text copied from GTK app after closing it when "Prevent empty clipboard" is turned off
https://bugs.kde.org/show_bug.cgi?id=424649 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=424754 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424754] Plasma fails to paste text copied from apps running on Xwayland (tested Firefox and Chromium) when "Prevent Empty Clipboard" is enabled
https://bugs.kde.org/show_bug.cgi?id=424754 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b |https://bugs.kde.org/show_b |ug.cgi?id=424731, |ug.cgi?id=424649 |https://bugs.kde.org/show_b | |ug.cgi?id=439765| -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 440576] New: The "Download hew global themes" window is not closed with the standard cross
https://bugs.kde.org/show_bug.cgi?id=440576 Bug ID: 440576 Summary: The "Download hew global themes" window is not closed with the standard cross Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nieskaza...@mail.ru Target Milestone: --- SUMMARY The "Download hew global themes" window is not closed with the standard cross in the upper frame of the window. The window is closed only with the "Close" button in the lower right corner, however, with the standard button in the window title (where it is possible to minimize and maximize the window), it is impossible to close the window. STEPS TO REPRODUCE 1. Trying to load a theme, app icons, or color schemes. 2. A window opens where you can select the desired elements and load them. 3. This very window is not closed in the standard way. SOFTWARE / OS VERSIONS Linux / KDE Plasma: manjaro (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424754] Plasma fails to paste text copied from apps running on Xwayland (tested Firefox and Chromium) when "Prevent Empty Clipboard" is enabled
https://bugs.kde.org/show_bug.cgi?id=424754 Nate Graham changed: What|Removed |Added Summary|Plasma fails to paste text |Plasma fails to paste text |copied from apps running on |copied from apps running on |Xwayland (tested Firefox|Xwayland (tested Firefox |and Chromium) |and Chromium) when "Prevent ||Empty Clipboard" is enabled -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424754] Plasma fails to paste text copied from apps running on Xwayland (tested Firefox and Chromium)
https://bugs.kde.org/show_bug.cgi?id=424754 --- Comment #43 from Nate Graham --- *** Bug 439765 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439765] Clipboard is intermittently broken in the Wayland session when "Prevent Empty Clipboard" is enabled
https://bugs.kde.org/show_bug.cgi?id=439765 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #7 from Nate Graham --- I think this is the same as Bug 424754 after all. *** This bug has been marked as a duplicate of bug 424754 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424754] Plasma fails to paste text copied from apps running on Xwayland (tested Firefox and Chromium)
https://bugs.kde.org/show_bug.cgi?id=424754 --- Comment #42 from Nate Graham --- Actually I think you're right; they are the same after all. Sorry for sending you on a wild goose chase. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424649] Cannot paste text copied from GTK app after closing it when "Prevent empty clipboard" is turned off
https://bugs.kde.org/show_bug.cgi?id=424649 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=439765 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439765] Clipboard is intermittently broken in the Wayland session when "Prevent Empty Clipboard" is enabled
https://bugs.kde.org/show_bug.cgi?id=439765 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=424649 Summary|Clipboard is intermittently |Clipboard is intermittently |broken in the Wayland |broken in the Wayland |session |session when "Prevent Empty ||Clipboard" is enabled CC||n...@kde.org --- Comment #6 from Nate Graham --- Cannot reproduce with current git master FWIW. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439513] Klipper interferes with XWayland: Copying text works only every second time
https://bugs.kde.org/show_bug.cgi?id=439513 Nate Graham changed: What|Removed |Added Status|REOPENED|NEEDSINFO CC||n...@kde.org Keywords||wayland Resolution|--- |WAITINGFORINFO --- Comment #10 from Nate Graham --- I think I see the issue, or at least something related. Every time I copy something in an XWayland app, two entries are created in Klipper: the text, and a seemingly blank entry. For me this is not interfering with pasting the text, but perhaps for you it is. Can you reproduce this? Also can you please take a screenshot of your Klipper settings? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440575] Suggest changing the Virtual Keyboard applet to show and the virtual keyboard, rather than enabling and disabling it
https://bugs.kde.org/show_bug.cgi?id=440575 Nate Graham changed: What|Removed |Added Keywords||wayland CC||aleix...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440575] New: Suggest changing the Virtual Keyboard applet to show and the virtual keyboard, rather than enabling and disabling it
https://bugs.kde.org/show_bug.cgi?id=440575 Bug ID: 440575 Summary: Suggest changing the Virtual Keyboard applet to show and the virtual keyboard, rather than enabling and disabling it Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: n...@kde.org CC: mate...@gmail.com Target Milestone: 1.0 After using the virtual keyboard for a while, my conclusion is that the only reason you would want an applet that enables and disables the virtual keyboard is to work around bugs where the virtual keyboard appears inappropriately, like Bug 440569. However once that and similar bugs get fixed in KDE software, the applet becomes superfluous; you will want the virtual keyboard active all the time because it will be reliably appearing on-demand. However there will still be two potential remaining annoyances with regards to the virtual keyboard 1. An app is buggy and focusing its text field with a touch does not make the virtual keyboard automatically as it should 2. The virtual keyboard correctly appeared automatically, but now you are done using it and it did not disappear on its own For both of these cases, it would be useful for the System Tray applet to show and hide the virtual keyboard when pressed. I think this would be a more useful behavior for the applet. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440554] [Wayland] Breadcrumb drop down menu "more" item hidden behind panel
https://bugs.kde.org/show_bug.cgi?id=440554 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||5.23 --- Comment #1 from Nate Graham --- Cannot reproduce with Plasma 5.23; it must have been fixed in KWin in git master code! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 439914] KRunner/Kickoff do not show results in real time while typing with virtual keyboard
https://bugs.kde.org/show_bug.cgi?id=439914 Nate Graham changed: What|Removed |Added Component|general |components Ever confirmed|0 |1 CC||n...@kde.org, ||plasma-b...@kde.org Summary|KRunner/Kickoff should |KRunner/Kickoff do not show |always show results while |results in real time while |typing with virtual |typing with virtual |keyboard|keyboard Product|frameworks-krunner |frameworks-plasma Keywords||usability, wayland Assignee|alexander.loh...@gmx.de |notm...@gmail.com Version|unspecified |5.84.0 Status|REPORTED|CONFIRMED --- Comment #1 from Nate Graham --- Can confirm the issue. Seems to be an issue with the component itself. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 440574] Memory Leak / Memory Usage For Large Feeds
https://bugs.kde.org/show_bug.cgi?id=440574
--- Comment #1 from barray ---
I'm logging the RAM usage every 300 seconds using the SO answer here:
https://unix.stackexchange.com/a/508799
The code is:
```
delay=300
pid="$1"
top -b -d $delay -p $pid | awk -v OFS="," '$1=="top"{ time=$3 } $1+0>0 { print
time,$1,$NF,$9,$10; fflush() }'
```
This gives RAM as a percentage of total memory, but should allow the
observation of memory increase to be obvious.
The purpose of doing this is to see whether it is linear (memory leak in small
loop), periodic (when feeds are pulled) or sporadic (specific feed content is
leaking memory). It also will show the extent of this problem.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 439911] Popup virtual keyboard as a new action
https://bugs.kde.org/show_bug.cgi?id=439911 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Keywords||wayland CC||aleix...@kde.org, ||n...@kde.org Status|REPORTED|CONFIRMED --- Comment #1 from Nate Graham --- Yes, I think your idea makes sense! -- You are receiving this mail because: You are watching all bug changes.
[krename] [Bug 439293] Is Krename buglist ABANDONED?
https://bugs.kde.org/show_bug.cgi?id=439293
--- Comment #4 from Rafael Linux User ---
(In reply to Méven Car from comment #3)
> > No one is replying or asking about that bug after months
>
> That is not completely true, for instance:
> https://bugs.kde.org/show_bug.cgi?id=438613
>
> You can complain the bugs are not fixed as fast I'd you wish, but the
> maintainer is still around.
>
> The most objective way to see developers activity is to see the current
> activity:
> https://invent.kde.org/utilities/krename/-/commits/master
>
> The app project would probably welcome more contributors.
>
> Please keep in mind, that's volunteer work and after a few years even the
> most motivated ones will have simply less time to devote to their app.
Well, non reproducible crashes is not a reproducible issue, like the one I
reported and the reason cause I begin THIS thread.
Anyway, Heiko answered me thru kde-level account, telling me this about my
unattended bug:
"it's just that time is a scarce resource and while krename works fine for
my purposes the codebase is not tiny and still has some cruft in need of
modernisation. For example, the bug you're likely referring to, is probably
best solved by porting to QXmlStream{Reader/Writer}, which already exists
locally but still needs some finishing touches and autotests.
That being said, any contribution to improve things would be welcome."
Personally, I hate that final sentence for USERS. Users can report and give
information about issue, they don't have and don't need to have programming
knowledgments to improve or help more. When I read that answers, I feel like
guilty for reporting bugs that for any reason are not fixed. That's my POV as
user.
--
You are receiving this mail because:
You are watching all bug changes.
[akregator] [Bug 440574] Memory Leak / Memory Usage For Large Feeds
https://bugs.kde.org/show_bug.cgi?id=440574 barray changed: What|Removed |Added CC||bar...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 440574] New: Memory Leak / Memory Usage For Large Feeds
https://bugs.kde.org/show_bug.cgi?id=440574 Bug ID: 440574 Summary: Memory Leak / Memory Usage For Large Feeds Product: akregator Version: 5.16.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: bar...@protonmail.com Target Milestone: --- SUMMARY I am currently observing ~250MB of RAM usage increase per day. This lead to a system crash. Currently Akregator is consuming 1.7GB of RAM, 4.9GB of virtual memory. Compare this to Firefox with hundreds of active tabs, consuming 1.4GB of RAM and 8.9GB of virtual memory. STEPS TO REPRODUCE 1. Large number of RSS feeds (OPML export is ~300kB and ~700 lines) 2. Set checking time to 30 minute intervals 3. Wait for 24 hours OBSERVED RESULT A ~250MB RAM increase over 24 hours. Over several weeks this will lead to a system lock-up/crash (in this case). EXPECTED RESULT A little to no RAM increase over 24 hours. SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: Ubuntu 21.04 (available in About System) KDE Plasma Version: - KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440534] On Wayland, dragging items over windows immediately makes those windows focused
https://bugs.kde.org/show_bug.cgi?id=440534 --- Comment #2 from Jacob White --- It's truly immediate for me. I don't think the screen is rendered once before the focus switch happens. My monitor is running at 144hz, but I also tested at 60hz and experienced the same behavior. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440534] On Wayland, dragging items over windows immediately makes those windows focused
https://bugs.kde.org/show_bug.cgi?id=440534 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- For me it's not *immediate* but it does happen after just like half a second. Is that what you're seeing, or is it truly immediate for you? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439905] SDDM retains 5.21 default wallpaper after upgrading
https://bugs.kde.org/show_bug.cgi?id=439905 medin changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from medin --- (In reply to Nate Graham from comment #3) > So sorry, I asked for the wrong data. :( > > Instead can you provide the contents of > /usr/share/sddm/themes/breeze/theme.conf? > > Also, you should see a "background=[something]" line, where [something] is a > file path. Can you tell me if that file path is the image you expect, or > something else? "background" property in "/usr/share/sddm/themes/breeze/theme.conf" file points to the correct image. What I found is that at certain time with 5.21 I changed SDDM Breeze background then wanted to revert back to default but I didn't find how to do it, even after selecting another SDDM theme then reapply Breeze the default image never returned, so the only solution is that I downloaded 5.21 wallpaper and selected it as background using Plasma settings, that downloaded image was copied to folder "/usr/share/sddm/themes/breeze/" and a new file called "theme.conf.user" was automatically added to the same folder with property "background" set to the copied image name, so after upgrading to 5.22 the file "theme.conf.user" still overrides the default new wallpaper and there is no way to apply it using Plasma settings UI. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435281] Making storyboards is enabled by default
https://bugs.kde.org/show_bug.cgi?id=435281 Eoin O'Neill changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/9f2a61826 ||f646407d36dbbd042bd86def60c ||b089 --- Comment #2 from Eoin O'Neill --- Git commit 9f2a61826f646407d36dbbd042bd86def60cb089 by Eoin O'Neill. Committed on 03/08/2021 at 22:19. Pushed by eoinoneill into branch 'master'. Cleanup storyboard background rendering. Reduced code repitition, added more safety to ensure that frames were never unnecessarily rendered (when storyboard docker is empty.) M +13 -24 plugins/dockers/storyboarddocker/KisStoryboardThumbnailRenderScheduler.cpp https://invent.kde.org/graphics/krita/commit/9f2a61826f646407d36dbbd042bd86def60cb089 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 429249] Sending SMS doesn't work at all
https://bugs.kde.org/show_bug.cgi?id=429249 --- Comment #9 from Piotr Mierzwinski --- (In reply to Ori B from comment #8) > I was having the same problem with the CLI and the widget for sending SMS > messages. I've installed the latest version and at first thought the issue > remains, but then realized it's silently /not/ sending messages to the > device's own phone number. It did work for sending messages other contacts. > For those with this problem, are you trying to send a message to your own > number? Sorry? I don't get you. How can I send any message to my own number if my number is assigned to device what actual sends message? Therefore no, I didn't try to send any message to my own number! or I didn't understand you As I said I tried to send SMS to any person from my contacts list what KDE Connect SMS loads from my phone, so I do following things: 1. I select one contact (history of conversation is loading in KDE Connect SMS) 2. Click into "Compose messages" 3, Enter any message and press Enter or click "Send" In result happens nothing, or actually field where I put message freezes. Clicking in other contact unfreezes it. Notice that when I try to send SMS my phone is unlocked. Let me know please what should I do to provide some logs from phone, assuming that an issue happens in Android application. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 440573] New: Plasma System monitor crash during compiling
https://bugs.kde.org/show_bug.cgi?id=440573 Bug ID: 440573 Summary: Plasma System monitor crash during compiling Product: plasma-systemmonitor Version: 5.22.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: wfaeh...@freenet.de CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 140496 --> https://bugs.kde.org/attachment.cgi?id=140496=edit Kcrash log file SUMMARY Plasma System Monitor crash STEPS TO REPRODUCE 1. Compiling lender 3D source 2. Open Plasma System Monitor 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 440572] Password input field shows plain text characters when the virtual keyboard is first used to enter text
https://bugs.kde.org/show_bug.cgi?id=440572 Nate Graham changed: What|Removed |Added Version|master |5.84.0 Assignee|visual-des...@kde.org |notm...@gmail.com Product|plasmashell |frameworks-plasma Target Milestone|1.0 |--- Summary|Password input field on |Password input field shows |lock screen shows plain |plain text characters when |text characters when the|the virtual keyboard is |virtual keyboard is first |first used to enter text |shown | Component|Theme - Breeze |components --- Comment #1 from Nate Graham --- Hmm, the text field has all of these set on it: echoMode: TextInput.Password inputMethodHints: Qt.ImhHiddenText | Qt.ImhSensitiveData | Qt.ImhNoAutoUppercase | Qt.ImhNoPredictiveText Those should be sufficient from the theme side. Moving to plasma-framework, where the text field loves. Possibly even a Qt bug... -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 438633] gwenview segfault when cropping
https://bugs.kde.org/show_bug.cgi?id=438633 --- Comment #2 from Marcel Bergeron --- The problem has gone away, I did'nt notice when. As it was, trying to crop any image produced a crash. Le mar. 3 août 2021 à 06:43, postix a écrit : > https://bugs.kde.org/show_bug.cgi?id=438633 > > postix changed: > >What|Removed |Added > > > CC||pos...@posteo.eu > > --- Comment #1 from postix --- > Do you have a sample file? I cannot reproduce it on openSUSE Tumbleweed > 20210730 > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440572] New: Password input field on lock screen shows plain text characters when the virtual keyboard is first shown
https://bugs.kde.org/show_bug.cgi?id=440572 Bug ID: 440572 Summary: Password input field on lock screen shows plain text characters when the virtual keyboard is first shown Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: n...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 Fedora 34 with Maliit virtual keyboard in a built-from-source Plasma Wayland session STEPS TO REPRODUCE 1. Lock the screen 2. Tap the Virtual Keyboard button 3. Start typing OBSERVED RESULT It types plain text characters into the text field! If I click the text field and type with my keyboard, it returns to obfuscated input. Thereafter, it remains in obfuscated input mode if I enter text with the virtual keyboard. Seems like something about being activated by the virtual keyboard did not cause the text field to enter obfuscated text mode. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440467] screenlocker virtual keyboard broken on wayland
https://bugs.kde.org/show_bug.cgi?id=440467 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #4 from Nate Graham --- We have ported away from the use of QtVirtualKeyboard which we used to use, and now require the use of the Maliit virtual keyboard, which works much better. Unfortunately, it is still not packaged on openSUSE distros. See https://bugzilla.opensuse.org/show_bug.cgi?id=1184014. Please go prod the openSUSE packagers to finally get this done. :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438305] First "scene" sometimes fails to render preview after loading. Clicking entry resolves the issue.
https://bugs.kde.org/show_bug.cgi?id=438305 Eoin O'Neill changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439926] Virtual keyboard applet should become visible in the System Tray by default when in tablet mode and/or when there is no physical keyboard
https://bugs.kde.org/show_bug.cgi?id=439926 Nate Graham changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439070] Unable to copy/paste when using Wayland
https://bugs.kde.org/show_bug.cgi?id=439070 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439926] Virtual keyboard applet should become visible in the System Tray by default when in tablet mode and/or when there is no physical keyboard
https://bugs.kde.org/show_bug.cgi?id=439926 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Keywords||usability Summary|Virtual keyboard icon |Virtual keyboard applet |should become visible when |should become visible in |user enters tablet mode by |the System Tray by default |default |when in tablet mode and/or ||when there is no physical ||keyboard CC||aleix...@kde.org Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439926] Virtual keyboard icon should become visible when user enters tablet mode by default
https://bugs.kde.org/show_bug.cgi?id=439926 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #1 from Nate Graham --- *** Bug 440570 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440570] Virtual Keyboard system tray applet should mark itself as active whenever there is a virtual keyboard available and no physical keyboard attached
https://bugs.kde.org/show_bug.cgi?id=440570 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 439926 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439191] Touch screen swiping to trigger an action not working
https://bugs.kde.org/show_bug.cgi?id=439191 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Keywords||wayland Product|plasmashell |kwin Assignee|k...@davidedmundson.co.uk|kwin-bugs-n...@kde.org Status|REPORTED|NEEDSINFO Component|general |input CC||n...@kde.org Target Milestone|1.0 |--- --- Comment #1 from Nate Graham --- Works fine for me in the Plasma Wayland session. When you say "corner", yo mean "edge", right? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440386] High CPU use of kwin_wayland when video playing in firefox
https://bugs.kde.org/show_bug.cgi?id=440386 Nate Graham changed: What|Removed |Added CC||n...@kde.org, ||xaver.h...@gmail.com --- Comment #3 from Nate Graham --- Cannot reproduce; kwin_wayland hovers at around 12.8% (single core) while a video is playing in Firefox on my 4k screen in the Plasma Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439149] Button to configure kickoff remains highlighted on reopening
https://bugs.kde.org/show_bug.cgi?id=439149 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Keywords||regression Severity|normal |minor CC||noaha...@gmail.com --- Comment #7 from Nate Graham --- Can reproduce. No visible cause in the code. Might be a generic issue in the qqc2-desktop-style or even in Qt. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 345852] krunner buttons remain highlited when reappearing.
https://bugs.kde.org/show_bug.cgi?id=345852 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||n...@kde.org Resolution|--- |FIXED --- Comment #10 from Nate Graham --- There is no longer a close button in KRunner and toolbutton focus has been fixed in genera; fixed by default now. :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402903] [Wayland] Launch feedback on taskbar does not work
https://bugs.kde.org/show_bug.cgi?id=402903 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402903] [Wayland] Launch feedback on taskbar does not work
https://bugs.kde.org/show_bug.cgi?id=402903 Nate Graham changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|1 |0 Status|RESOLVED|REPORTED --- Comment #19 from Nate Graham --- Indeed, seems to be still broken. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409798] Image copied from Spectacle appears incorrectly on Wayland
https://bugs.kde.org/show_bug.cgi?id=409798 Nate Graham changed: What|Removed |Added Priority|HI |NOR Component|General |Clipboard Ever confirmed|0 |1 Target Milestone|--- |1.0 Severity|major |normal Summary|Spectacle Copy To Clipboard |Image copied from Spectacle |Doesn't Work Properly Under |appears incorrectly on |Wayland Session |Wayland Assignee|m...@baloneygeek.com |plasma-b...@kde.org Status|REPORTED|CONFIRMED Version|20.08.1 |master Product|Spectacle |plasmashell Keywords||wayland --- Comment #31 from Nate Graham --- Let's make sure we're all discussing the same bug here. From what I can tell, clicking on the "Copy to clipboard" button works properly now, with the image making it onto the clipboard. However I can reproduce Klipper showing the wrong contents; sometimes it shows a generic image icon, and sometimes it shows two blank entries. Discord running in an XWayland Flatpak being unable to receive it would be still another bug (and please file that one). For people who are still seeing the image not even appearing on the clipboard at all, please file new separate bug reports; this one is too confused and overloaded at this point. :0 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 440565] Copy text with crtl + c does not work
https://bugs.kde.org/show_bug.cgi?id=440565 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||aa...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Albert Astals Cid --- all files or a particular file? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 421974] [Wayland] Spectacle Doesn't Copy To The Clipboard The Screenshot Automatically
https://bugs.kde.org/show_bug.cgi?id=421974 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438266] Make it clearer which mouse is being configured when multiple mouse devices are available
https://bugs.kde.org/show_bug.cgi?id=438266 --- Comment #6 from Nate Graham --- Part of the problem for me at least is that my trackpoint appears as a mouse. That's pretty unexpected. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438266] Make it clearer which mouse is being configured when multiple mouse devices are available
https://bugs.kde.org/show_bug.cgi?id=438266 Nate Graham changed: What|Removed |Added Keywords|wayland | Severity|normal |wishlist Summary|Wrong mouse is selected by |Make it clearer which mouse |default in Mouse KCM on |is being configured when |Wayland |multiple mouse devices are ||available -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424649] Cannot paste text copied from GTK app after closing it when "Prevent empty clipboard" is turned off
https://bugs.kde.org/show_bug.cgi?id=424649 Nate Graham changed: What|Removed |Added Summary|[Wayland] Cannot paste text |Cannot paste text copied |copied from GTK app after |from GTK app after closing |closing it, even if the |it when "Prevent empty |text is visibly in Klipper |clipboard" is turned off Priority|HI |NOR --- Comment #16 from Nate Graham --- I can confirm that. When "Prevent empty clipboard" is on, everything works fine. When it's off, this breaks, and (ironically) an empty entry appears in Klipper when I copy the text in Gedit. Lowering priority as there is a trivial and non-destructive workaround and also this works with the default settings. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 437062] Glitch on hover over context menu of a window decoration on Wayland when using menu blur effect
https://bugs.kde.org/show_bug.cgi?id=437062 Nate Graham changed: What|Removed |Added Keywords||wayland Severity|normal |minor Status|REOPENED|CONFIRMED --- Comment #9 from Nate Graham --- Confirmed. Just window decoration menus on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 439598] Pop-up window at the bottom not displaying in a proper way
https://bugs.kde.org/show_bug.cgi?id=439598 --- Comment #12 from Albert Astals Cid --- > Another bug I noticed is that the "lock screen" button on the popup windows > (when the popup window appears correctly) does not work. It just behaves as > the "ignore" button. Different bug -> report different bug please -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 354544] Windows move after power savings mode
https://bugs.kde.org/show_bug.cgi?id=354544 jching changed: What|Removed |Added CC||jch...@protonmail.com --- Comment #3 from jching --- can confirm this problem still persists. debian unstable, kscreen 5.20.5-1 the weird thing is that only certain programs get moved after resume. konsole window always gets moved, but for some reason, my spotify client window manages to stay on the correct monitor after resume let me know if there are any logs or anything i can contribute to this report thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440571] New: Virtual Keyboard overlaps half of my panel
https://bugs.kde.org/show_bug.cgi?id=440571 Bug ID: 440571 Summary: Virtual Keyboard overlaps half of my panel Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: virtual-keyboard Assignee: kwin-bugs-n...@kde.org Reporter: n...@kde.org Target Milestone: --- Created attachment 140494 --> https://bugs.kde.org/attachment.cgi?id=140494=edit Cover half the panel Fedora 34 with maliit-keyboard in a built-from-source Plasma Wayland session at 200% global scale. When the virtual keyboard appears, it overlaps half of my vertical left-side panel. See attached screenshot. I suspect that the goal is to avoid covering the panel, because when my panel is horizontal, it succeeds at avoiding covering it. However when my panel is vertical on either side of the screen, the virtual keyboard overlaps exactly half of it. Seems like some width calculation didn't take into account the scale factor or something. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440570] New: Virtual Keyboard system tray applet should mark itself as active whenever there is a virtual keyboard available and no physical keyboard attached
https://bugs.kde.org/show_bug.cgi?id=440570 Bug ID: 440570 Summary: Virtual Keyboard system tray applet should mark itself as active whenever there is a virtual keyboard available and no physical keyboard attached Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: n...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 Otherwise it is pretty pointless, sitting there in the expanded popup. If the goal of this applet to be able to quickly enable and disable the virtual keyboard as needed, it needs to be visible by default when conditions are appropriate--such as when there is no physical keyboard attached. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440569] Virtual keyboard appears whenever an input field is activated for any reason even when a physical keyboard is attached
https://bugs.kde.org/show_bug.cgi?id=440569 Nate Graham changed: What|Removed |Added Keywords||wayland Summary|virtual keyboard become |Virtual keyboard appears |active whenever an input|whenever an input field is |field is activated for any |activated for any reason |reason even when a keyboard |even when a physical |is attached |keyboard is attached CC||aleix...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440569] New: virtual keyboard become active whenever an input field is activated for any reason even when a keyboard is attached
https://bugs.kde.org/show_bug.cgi?id=440569 Bug ID: 440569 Summary: virtual keyboard become active whenever an input field is activated for any reason even when a keyboard is attached Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: virtual-keyboard Assignee: kwin-bugs-n...@kde.org Reporter: n...@kde.org Target Milestone: --- Fedora 34 with maliit-keyboard in a built-from-source Plasma Wayland session. Right now whenever an input field gets focus for any reason, the virtual keyboard appears. This happens for all apps--KDE, GNOME, Electron, and so on. This behavior is annoying and inappropriate for cases when there is actually a physical keyboard attached. If there is a physical keyboard attached, the virtual keyboard should only appear if an input field is explicitly tapped with a touchscreen. Only when no physical keyboard is attached does it make sense to activate the virtual keyboard for all input field activations. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 440536] Allow playing a stream on multiple outputs
https://bugs.kde.org/show_bug.cgi?id=440536 Nate Graham changed: What|Removed |Added CC||n...@kde.org Severity|normal |wishlist Summary|Audio settings don't allow |Allow playing a stream on |selecting multiple outputs |multiple outputs Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Nate Graham --- Yeah, fair enough! -- You are receiving this mail because: You are watching all bug changes.
