[kwin] [Bug 493208] Desktop effects stuck at 60 Hz on High Refresh Rate Monitor
https://bugs.kde.org/show_bug.cgi?id=493208 Orlando Rodriguez changed: What|Removed |Added CC||sort...@gmail.com --- Comment #1 from Orlando Rodriguez --- Same issue here. I have commented other bugs related to not smooth effects, however, I think this is a very accurate description. I just have this problem with Overview, Present Windows and Desktop Grid effects and it is replicable in X11 and Wayland (in fact is replicable since Plasma 5), but as it is described in X11 with just snaping a window, alt-tab, etc, the issue is solved until a new reboot is performed. Not the case in wayland where I've not found any workaround. Additionally, I have two 144 hz monitors and a laptop with a 60 hz screen. Effects looks perfect in the laptop monitor, but not in the high refresh screens (in a TV at 60 hz also looks great). I tested with two monitors at 60hz both and all the effects have the same feeling, but once I configure one of the monitors to 144 hz, it can be noticed that the effects looks amazing for almost all the effects, except by those three mentioned above. And yes, I realized that those 3 effects at 144hz looks the same than at 60hz. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485927] Animations in KDE Plasma 6 seem to be capped at 60hz
https://bugs.kde.org/show_bug.cgi?id=485927 Orlando Rodriguez changed: What|Removed |Added CC||sort...@gmail.com --- Comment #3 from Orlando Rodriguez --- (In reply to DT from comment #1) > I've encountered the same behavior on my 240hz display. The overview and > window snapping animations are the most noticeable, and appear (mostly) > correct on the X11 session. Peculiarly, the overview animation on the X11 > session renders at a lower framerate *until* a window is snapped to an edge, > following which it will begin rendering at the correct framerate. I found a > user on Reddit: > https://old.reddit.com/r/kde/comments/1c1lkiw/ > strange_lag_symptoms_with_the_overview_effect/ who reported similar issues > (along with the quirk in the X11 session I described). > > > Additionally, when scrolling in system settings the scrolling on the > > sidebar suddenly becomes a higher refresh rate when the "Colors and Themes" > > option is clicked. > I was able to reproduce this as well. Same here. I've had this problem with the overview effects and desktop grid since 5.XX. For X11 I created a post-login script to Alt-tab automatically as fast as possible (this brings the same effect than a windows snapped) and the animations were amazing again, however, that workaround has never worked on Wayland. It would be great if some day this issue could be solved, it looks difficult and probably the priority is low due to the effects are pretty functional as they are, but for me I have been searching for a solution, even I was thinking on thinkering the effects by myself, but in KDE6 they are not in the effects folders anymore. -- You are receiving this mail because: You are watching all bug changes.
[plasma-mediacenter] [Bug 418288] Keyboard multimedia keys are unstable
https://bugs.kde.org/show_bug.cgi?id=418288 --- Comment #9 from Orlando Rodriguez --- Update: After juggling with configurations, I noticed that the issue is related to the option: "Keep popup open during progress" in the notification settings. I just disabled that option and it looks like my issues with the volume are gone (in both cases, with Spotify and with youtube videos). -- You are receiving this mail because: You are watching all bug changes.
[plasma-mediacenter] [Bug 418288] Keyboard multimedia keys are unstable
https://bugs.kde.org/show_bug.cgi?id=418288 --- Comment #8 from Orlando Rodriguez --- Well, Just to add...after watching youtube videos for some minutes and the keys stop to work again, definitely, the media widget also has soemthing to do here. After removing it and add it again the problem stops for a longer time. This issue is very annoying in KDE, I hope this gets a better attention, because I have not found any workaround to fix it. -- You are receiving this mail because: You are watching all bug changes.
[plasma-mediacenter] [Bug 418288] Keyboard multimedia keys are unstable
https://bugs.kde.org/show_bug.cgi?id=418288 --- Comment #7 from Orlando Rodriguez --- After trying several things, I have noticed that this behavior happens everytime a notification comes and the notification is active. Once the notification is closed manually or automatically (by default 5 seconds), media buttons start to work again. I replicated the issue several times using spotify (which by default send a notification every time a song is changed) so, I just change a song and try to use my volume buttons in that exact moment when the notification is launched. In my case, the problem I see is related to the notification widget and the audio widget. I haven´t had any luck with the media widget. -- You are receiving this mail because: You are watching all bug changes.
[plasma-mediacenter] [Bug 418288] Keyboard multimedia keys are unstable
https://bugs.kde.org/show_bug.cgi?id=418288 Orlando Rodriguez changed: What|Removed |Added CC||sort...@gmail.com --- Comment #4 from Orlando Rodriguez --- Same bug here. They randomly can work or not. I have detected that the media keys usually stop working when a notification is active. After closing the notification they start to work again. There are other cases when they stop to work (when I am watching youtube videos), but in this case, I don´t have a way to replicate the issue. -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 435338] Krfb on Wayland doesn't accept remote keyboard input
https://bugs.kde.org/show_bug.cgi?id=435338 Orlando Rodriguez changed: What|Removed |Added CC||sort...@gmail.com --- Comment #14 from Orlando Rodriguez --- Same issue here. Unfortunately, no other Desktop Sharing app is working for me (Teamviewer added experimental support for Wayland but It did not work for me), so this is my only way in wayland to share desktop between computers. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448538] Overview effect runs at lower FPS
https://bugs.kde.org/show_bug.cgi?id=448538 --- Comment #8 from Orlando Rodriguez --- Quick Update: I just moved to 5.25 Wayland. The effect is still laggy, but now the workaround of the task switcher does not work anymore. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448538] Overview effect runs at lower FPS
https://bugs.kde.org/show_bug.cgi?id=448538 --- Comment #7 from Orlando Rodriguez --- Just an update. I just changed my Graphic Card for an AMD card and I am using the default open drivers and the issue is still there. I am still using the workaround to launch the Task View at start up. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448538] Overview effect runs at lower FPS
https://bugs.kde.org/show_bug.cgi?id=448538 --- Comment #6 from Orlando Rodriguez --- I am facing the exact same issue. I also use two monitors at 144 Hz and I also have an Nvidia card. The problem is just with the Overview Effect and the effect runs smoothly after launching the task viewer or after dragging and dropping a window to the left/right side. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448538] Overview effect runs at lower FPS
https://bugs.kde.org/show_bug.cgi?id=448538 Orlando Rodriguez changed: What|Removed |Added CC||sort...@gmail.com --- Comment #5 from Orlando Rodriguez --- *** Bug 452634 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452634] KDE Overview Effect is laggy until any Window is dragged to left/top/right
https://bugs.kde.org/show_bug.cgi?id=452634 Orlando Rodriguez changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Orlando Rodriguez --- I don't know how to add a duplicate, but I see this is the same bug with the number 448538 because when I launch the Task Switcher as it is suggested in bug 448538, the issue disappears. *** This bug has been marked as a duplicate of bug 448538 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450750] Plasma Wayland Crashes when Login
https://bugs.kde.org/show_bug.cgi?id=450750 Orlando Rodriguez changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #6 from Orlando Rodriguez --- After upgrading my distro(kubuntu) to 22.04, the issue is gone for my laptop with AMD iGpu. My desktop with Nvidia is not working yet, however, that's in some way expected. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452634] KDE Overview Effect is laggy until any Window is dragged to left/top/right
https://bugs.kde.org/show_bug.cgi?id=452634 --- Comment #3 from Orlando Rodriguez --- I'm using X11, not wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452634] KDE Overview Effect is laggy until any Window is dragged to left/top/right
https://bugs.kde.org/show_bug.cgi?id=452634 --- Comment #2 from Orlando Rodriguez --- (In reply to Nate Graham from comment #1) > Cannot reproduce with my Intel iGPU on either X11 or Wayland. > > Does this happen on Wayland for you as well? Or just X11? I am not sure if the issue is present in my AMD laptop with iGpu (the screen is just 60hz), I am going to test it. For the moment, I see the issue on my desktop with an Nvidia 2060 Super with Driver (510.60.02). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 424669] Transfering files not working between 2 Ubuntu 20.04 computers
https://bugs.kde.org/show_bug.cgi?id=424669 Orlando Rodriguez changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Orlando Rodriguez --- This was resolved updating the openssl and libssl libraries. In newer Ubuntu versions, issue is not present. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452634] KDE Overview Effect is laggy until any Window is dragged to left/top/right
https://bugs.kde.org/show_bug.cgi?id=452634 Orlando Rodriguez changed: What|Removed |Added Summary|KDE Overview Effect is |KDE Overview Effect is |laggy until any Windows is |laggy until any Window is |dragged to left/top/right |dragged to left/top/right -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452634] New: KDE Overview Effect is laggy until any Windows is dragged to left/top/right
https://bugs.kde.org/show_bug.cgi?id=452634 Bug ID: 452634 Summary: KDE Overview Effect is laggy until any Windows is dragged to left/top/right Product: kwin Version: 5.24.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: sort...@gmail.com Target Milestone: --- SUMMARY *** The overview effect is laggy. After the animation for drag to top edge, left, right is launched, the overview effect starts to work really smooth! *** STEPS TO REPRODUCE 1. Login to KDE 2. Launch Overview Effect 3. Open any application and drag the window to any part (just the animation is required, even the "dragged" action does not need to be completed) OBSERVED RESULT Just starting, the overview effect seems laggy, as if the FPS is lower than in the other effects or animations (I am using 144 Hz screens). Once I dragged a window to the left, right, or top and the animation of the black shadow is launched, the overview effect stops being laggy and starts to work as smooth as the other effects/animations. This is happening on my desktop with 144hz screens and Nvidia Drivers 570.60.02. EXPECTED RESULT The Overview effect should be as smooth as the other effects or animations, without any trick. SOFTWARE/OS VERSIONS Distro: Kubuntu 21.10 Linux Kernel: 5.13.0-22-generic KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450750] Plasma Wayland Crashes when Login
https://bugs.kde.org/show_bug.cgi?id=450750 --- Comment #4 from Orlando Rodriguez --- Thank you so much for your answer Nate, I'll keep updating every version and testing this. Maybe I'll try a clean install too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450750] Plasma Wayland Crashes when Login
https://bugs.kde.org/show_bug.cgi?id=450750 --- Comment #2 from Orlando Rodriguez --- No, I am not using Fish Shell. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450750] New: Plasma Wayland Crashes when Login
https://bugs.kde.org/show_bug.cgi?id=450750 Bug ID: 450750 Summary: Plasma Wayland Crashes when Login Product: plasmashell Version: 5.24.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sort...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.24.2) Qt Version: 5.15.2 Frameworks Version: 5.91.0 Operating System: Linux 5.13.0-22-generic x86_64 Windowing System: Wayland Distribution: Ubuntu 21.10 DrKonqi: 5.24.2 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Just login to the pc. - Unusual behavior I noticed: The splash appears, after that I can see the wallpaper but no panels are loaded. After some seconds the crash modal appears and the wallpaper dissapears. Just a black screen. - Custom settings of the application: I am using some widgets like inline battery, configurable button widget and Toggle Panel button widget. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140181637702848) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140181637702848) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=140181637702848, signo=signo@entry=6) at pthread_kill.c:91 #7 0x7f7e98c28476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f7e98c0e7b7 in __GI_abort () at abort.c:79 #9 0x7f7e990b3ba3 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f7e972d9354 in QtWaylandClient::QWaylandDisplay::checkError() const () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #11 0x7f7e972da06a in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #12 0x7f7e99313a88 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f7e993355db in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f7e992daa9b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f7e992e3024 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x55e00af68da9 in ?? () #17 0x7f7e98c0ffd0 in __libc_start_call_main (main=main@entry=0x55e00af67f50, argc=argc@entry=1, argv=argv@entry=0x7ffceff1e3a8) at ../sysdeps/nptl/libc_start_call_main.h:58 #18 0x7f7e98c1007d in __libc_start_main_impl (main=0x55e00af67f50, argc=1, argv=0x7ffceff1e3a8, init=, fini=, rtld_fini=, stack_end=0x7ffceff1e398) at ../csu/libc-start.c:409 #19 0x55e00af68ec5 in ?? () [Inferior 1 (process 2582) detached] Possible duplicates by query: bug 450707, bug 450663, bug 450646, bug 450320, bug 450112. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449835] Cannot switch virtual desktop using shortcut in overview effect
https://bugs.kde.org/show_bug.cgi?id=449835 Orlando Rodriguez changed: What|Removed |Added CC||sort...@gmail.com --- Comment #4 from Orlando Rodriguez --- I had this problem too with my mouse, which was launching a shortcut to next/previous desktop and it was not working in the Overview Effect. Luckily for my case, I was able to use xbind with the mouse and launch the dbus command for the Next/Previous Desktop instead of launching the shortcut, and that worked for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434368] New: Compositor crashes when a new virtual desktop is added
https://bugs.kde.org/show_bug.cgi?id=434368 Bug ID: 434368 Summary: Compositor crashes when a new virtual desktop is added Product: kwin Version: 5.18.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: sort...@gmail.com Target Milestone: --- Application: kwin_x11 (5.18.5) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-66-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: The compositor crashes if a new virtual desktop is added when there is at least one application pinned to all the desktops. I need to unpin the applications before to add a new desktop. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f898a46d800 (LWP 18267))] Thread 9 (Thread 0x7f88c5793700 (LWP 18284)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x561ce5609650) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x561ce5609600, cond=0x561ce5609628) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x561ce5609628, mutex=0x561ce5609600) at pthread_cond_wait.c:638 #3 0x7f898fa0db0f in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f898fa0dc01 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f898eaa9109 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f898eaa93ad in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f898fa079d2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f898efc5609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f8991234293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f88c5f94700 (LWP 18283)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x561ce55b5844) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x561ce55b57f0, cond=0x561ce55b5818) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x561ce55b5818, mutex=0x561ce55b57f0) at pthread_cond_wait.c:638 #3 0x7f898fa0db0f in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f898fa0dc01 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f898eaa9109 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f898eaa93ad in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f898fa079d2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f898efc5609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f8991234293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f88c6795700 (LWP 18282)): #0 0x7f8991227bf6 in __ppoll (fds=0x7f88b8000d68, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:44 #1 0x7f898fc234a9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f898fc24a14 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f898fbce4db in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f898fa06785 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f898e7381a9 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f898fa079d2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f898efc5609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f8991234293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f88c6f96700 (LWP 18281)): #0 0x7f8991227bf6 in __ppoll (fds=0x7f88cd68, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:44 #1 0x7f898fc234a9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f898fc24a14 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f898fbce4db in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f898fa06785 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f898e7381a9 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f898fa079d2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f898efc5609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f8991234293 in clone () at ../sysdeps/unix/sy
[kdeconnect] [Bug 424606] KDE Neon (rebase 20.04, testing) cannot send or receive files from another Plasma PC
https://bugs.kde.org/show_bug.cgi?id=424606 Orlando Rodriguez changed: What|Removed |Added CC||sort...@gmail.com --- Comment #5 from Orlando Rodriguez --- Thank you so much guys!! I just updated openssl and libssl and it is working!!! You're the best! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 424669] New: Transfering files not working between 2 Ubuntu 20.04 computers
https://bugs.kde.org/show_bug.cgi?id=424669 Bug ID: 424669 Summary: Transfering files not working between 2 Ubuntu 20.04 computers Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: sort...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Pair the computers with KDE 2. Transfer a file from one computer to another OBSERVED RESULT A notification will be launched of the file transfer in progress, however, the progress never starts. EXPECTED RESULT The file should be transferred. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 20.04.1 TLS KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION The pairing of the devices also dissapear after a reboot or after clickling the "Refresh" button. The devices are not stored as trusted devices. This behavior does not happen for the phone, with the Android phone everythin works fine, including the files transfer. -- You are receiving this mail because: You are watching all bug changes.
