[kwin] [Bug 372931] New: Plasma 5 get frozen if I grab a window and move it to any edge of the screen (on wayland)
https://bugs.kde.org/show_bug.cgi?id=372931 Bug ID: 372931 Summary: Plasma 5 get frozen if I grab a window and move it to any edge of the screen (on wayland) Product: kwin Version: 5.8.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: edoantoni...@hotmail.com Target Milestone: --- In wayland if I grab a window (any window, it does not matter if a native wayland application like dolphin or something using xwayland as firefox), and move it to any edge of the screen, the PC get frozen. So I have to abruptly force a restart to continue using the PC. This on Manjaro, intel hardware, on Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372931] Plasma 5 get frozen if I grab a window and move it to any edge of the screen (on wayland)
https://bugs.kde.org/show_bug.cgi?id=372931 --- Comment #1 from eduardo --- to reproduce the bug, I have to grab the window with the mouse and (while keeping the left button pressed) move it to any edge of the screen until the cursor touch the edge. In that moment, the pc gets frozen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372931] Plasma 5 get frozen if I grab a window and move it to any edge of the screen (on wayland)
https://bugs.kde.org/show_bug.cgi?id=372931 --- Comment #3 from eduardo --- I took this while I was using wayland https://paste.kde.org/peslqxmiq -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372931] Plasma 5 get frozen if I grab a window and move it to any edge of the screen (on wayland)
https://bugs.kde.org/show_bug.cgi?id=372931 eduardo changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from eduardo --- The problem indeed was the compositing, I was using xrender (since on X11 opengl 2.0 & 3.1 has given me some issues, so on my case xrender is the best option there), but I switched to OpenGL 3.1 and now this specific bug is fixed. Here is the new output, now with opengl 3.1 http://pastebin.com/kQrGD6Wf In other words, xrender is just not compatible with wayland. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 427672] krunner is "janky" when loading new results / starting with results already loaded
https://bugs.kde.org/show_bug.cgi?id=427672 Eduardo changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #15 from Eduardo --- (In reply to Nate Graham from comment #14) > This should be fully fixed now in Plasma 5.24. This bug report addresses two issues: the frame rendering flickering and the quick crazy reordering of the results. The quick reordering is not fixed yet, the MR with the fix is here: https://invent.kde.org/plasma/milou/-/merge_requests/37 IMO it is ready to be merged, we just need somebody to review & merge it. So I'm reopening until the quick crazy reordering problem is fixed too. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 427672] krunner is "janky" when loading new results / starting with results already loaded
https://bugs.kde.org/show_bug.cgi?id=427672 --- Comment #20 from Eduardo --- We can't backport that one to plasma 5.24 because it depends on https://invent.kde.org/frameworks/krunner/-/merge_requests/82 which only got merged into krunner 5.91, and plasma 5.24 must remain compatible with frameworks 5.90. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 423945] wish: pre-buffering of images to enable faster/smoother switching
https://bugs.kde.org/show_bug.cgi?id=423945 Eduardo changed: What|Removed |Added CC||eduardo.c...@kdemail.net --- Comment #1 from Eduardo --- +1 for this, absolute must-have... even most web-based photo viewers have it. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421040] Mouse warp effect can't be disabled (wrap to opposite screen edge at drag srolling)
https://bugs.kde.org/show_bug.cgi?id=421040 --- Comment #15 from Eduardo --- Hi, I'm still very annoyed by this... I got a large monitor, sometimes when scrolling horizontally the cursor warps to the other side of the monitor which is a huge and very annoying leap. The developers had good intentions in providing this feature, but it clearly is a design flaw. No other pdf viewer in the world is following this trend. I don't think anyone in the world will miss this. If I dig into the code and just delete this feature, would a merge request be accepted? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421040] Mouse warp effect can't be disabled (wrap to opposite screen edge at drag srolling)
https://bugs.kde.org/show_bug.cgi?id=421040 --- Comment #17 from Eduardo --- If I create a checkbox in "Settings -> Configure Okular -> General -> Enable scrolling beyond screen edges", would that merge request be accepted? If so, should I make it default to on or off? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 465996] Audio Applet "Show virtual devices" broken for newly created applets after 5.27.0
https://bugs.kde.org/show_bug.cgi?id=465996 Eduardo changed: What|Removed |Added CC||eduardo.c...@kdemail.net --- Comment #4 from Eduardo --- I noticed it when I created a brand new user on my machine. Virtual devices are not shown, regardless of the "Show virtual devices" checkbox state. Also, this checkbox state does not persist upon logoff/login: it always starts unchecked. I looked into the commit history, and commit 586fb5c315d12a02f2a3e2a524a5b6bf39ba2b52 seems to be the one to blame, apparently it was migrating the applet settings into KCM, but looks like something slipped. This commit was released into 5.27, so yes, this is a 5.27 regression. I reverted into using the old KMix, a downgrade in looks, but works for me while this doesn't get fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431446] Blinking panels and window contents not refreshing
https://bugs.kde.org/show_bug.cgi?id=431446 --- Comment #39 from Eduardo --- This issue is almost 2 years old for Plasma 5.20.x, it was present even before that, now it's flagged as duplicate for issue regarding Plasma 5.25.x, which does not look exactly the right way. I hope the decision was not taken because I updated the affected version from 5.20.x to 5.25.5. If this is my mistake, I'll change it back to 5.20. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 459069] Navigating to root using location bar does not work
https://bugs.kde.org/show_bug.cgi?id=459069 Eduardo changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||eduardo.c...@kdemail.net --- Comment #1 from Eduardo --- I can confirm, and it is pretty severe IMO. It was probably introduced in a recent update. I use Arch Linux, only noticed it today. It is easier to reproduce by right clicking the address bar and setting "Text Completion" to "None". This way, actually nothing works. You can try to type "/", "/etc/", "/bin", "~" nothing works. Sometimes it starts working again, seemingly random. But if you close Dolphin and open it again, the bug is always back. It is actually not a Dolphin bug, as it also happens on the Open/Save file dialogs that use the same URL location bar all over KDE apps. I suspected KIO, however I tried compiling some old KIO commit and I could not get rid of the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457284] X11 with NVIDIA GPU: Lock screen wallpaper is all black after sleep
https://bugs.kde.org/show_bug.cgi?id=457284 --- Comment #14 from Eduardo --- Created attachment 152122 --> https://bugs.kde.org/attachment.cgi?id=152122&action=edit Bugged lock screen This is the lock screen I get when returning from sleep. Date and time label only shows a "5, that's very random, sometimes more pieces of the date and time are shown, sometimes it shows complete, sometimes it is missing at all. Background is black. Profile picture is grey. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457284] X11 with NVIDIA GPU: Lock screen wallpaper is all black after sleep
https://bugs.kde.org/show_bug.cgi?id=457284 --- Comment #15 from Eduardo --- Created attachment 152123 --> https://bugs.kde.org/attachment.cgi?id=152123&action=edit Normal lock screen This is what my lock screen should be. I get this when just locking without going to sleep. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457284] X11 with NVIDIA GPU: Lock screen wallpaper is all black after sleep
https://bugs.kde.org/show_bug.cgi?id=457284 --- Comment #16 from Eduardo --- Created attachment 152124 --> https://bugs.kde.org/attachment.cgi?id=152124&action=edit Plasma under Wayland after returning from sleep Under Wayland it is even worse. The bug lives on into plasma desktop even after I unlock the lock screen after returning from sleep. As can be seen in the picture, the desktop renders completely crazy. No icons, no labels, black background, date and time on taskbar shows only "1"... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457284] [NVIDIA] Lock screen wallpaper is all black after sleep
https://bugs.kde.org/show_bug.cgi?id=457284 --- Comment #18 from Eduardo --- (In reply to Nate Graham from comment #17) > This is starting to feel like a bug in the NVIDIA driver itself. There's a > long history of graphical glitches on suspend, unfortunately. It's possible... however In comment #7 he said he got the bug with AMD hardware. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 439417] Rethink drag scrolling with left mouse button
https://bugs.kde.org/show_bug.cgi?id=439417 Eduardo changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||eduardo.c...@kdemail.net --- Comment #2 from Eduardo --- https://invent.kde.org/graphics/okular/-/merge_requests/637 has been merged, giving an option to disable this feature. We discussed it inside MR and we decided that adding an option to disable it was the way to go, so I'm closing this bug report too. -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 468861] New: (2023) KRFB segfaults at RfbServer::updateScreen(QList const&) after a few minutes on Wayland
https://bugs.kde.org/show_bug.cgi?id=468861 Bug ID: 468861 Summary: (2023) KRFB segfaults at RfbServer::updateScreen(QList const&) after a few minutes on Wayland Classification: Applications Product: krfb Version: 22.12.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: grundleb...@googlemail.com Reporter: eduardo.b...@hotmail.com Target Milestone: --- Created attachment 158353 --> https://bugs.kde.org/attachment.cgi?id=158353&action=edit Pretty printed backtrace from GDB SUMMARY KRFB segfaults at `RfbServer::updateScreen(QList const&)` after few minutes on connection with remote client (KRDC) ``` Thread 1 "krfb" received signal SIGSEGV, Segmentation fault. 0x555750f0 in RfbServer::updateScreen(QList const&) () (gdb) bt #0 0x555750f0 in RfbServer::updateScreen(QList const&) () #1 0x555751c7 in RfbServerManager::updateScreens() () #2 0x764d0e96 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #3 0x764d421e in QTimer::timeout(QTimer::QPrivateSignal) () from /lib64/libQt5Core.so.5 #4 0x764c7fc5 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #5 0x771aed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #6 0x7649d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #7 0x764ed981 in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #8 0x764ee2a4 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #9 0x74718c7f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #10 0x7476f118 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #11 0x74715f00 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #12 0x764ee5fa in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #13 0x7649bf3a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #14 0x764a4002 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #15 0x55569798 in main () ``` STEPS TO REPRODUCE 1. Start server stream 2. Connect with remote 3. Use host normally and wait for a few minutes OBSERVED RESULT Sudden crash SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.1.18-200.fc37.x86_64 (64-bit) Graphics Platform: __Wayland__ Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 11,0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82MF System Version: IdeaPad 3 15ALC6 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469656] Dolphin cannot remember previously opened tabs
https://bugs.kde.org/show_bug.cgi?id=469656 --- Comment #25 from Eduardo --- (In reply to Bug Janitor Service from comment #23) > A possibly relevant merge request was started @ > https://invent.kde.org/system/dolphin/-/merge_requests/549 Thank you, this looks good. At least dolphin now remembers closed tabs from last time. I have not tested session restore, but I will only do it when I actually can log out and back in. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 430288] Static noise when scrolling fast on the volume tray icon
https://bugs.kde.org/show_bug.cgi?id=430288 Eduardo changed: What|Removed |Added CC||eduardo.c...@kdemail.net --- Comment #3 from Eduardo --- +1 for this, I've always found this to be annoying. My keyboard has a kind of a dial to adjust volume, it triggers many successive playbacks of this volume test tone. It surely could be better polished. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 456310] Keyboard volume control keys don't change the volume of the default sink
https://bugs.kde.org/show_bug.cgi?id=456310 Eduardo changed: What|Removed |Added CC||eduardo.c...@kdemail.net --- Comment #6 from Eduardo --- I suffer a lot from this issue. I use pipewire with a virtual sink, and I use Carla with some LSP - Linux Studio Plugins - equalizer/crossover on top of the virtual sink routing to the real sink. My default sink is the virtual sink, and that's the one that should have the volume being controlled. However, most of the times, the applet changes the volume of the real sink. Just like the OP's video. But for me it's somewhat random, sometimes it works correctly, sometimes it doesn't. Regardless of something being played back or not. I've looked into the code, in this file https://invent.kde.org/plasma/plasma-pa/-/blob/master/src/pulseaudio.cpp there is a method called "findPreferredSink()" in line 271. >From reading the code, I understand there are 2 distinct concepts: "default sink" and "preferred sink. "Default sink" is the selected sink on the applet's UI, and "preferred sink" is a guess of what sink should have the volume controlled based on the playback state. For instance, if "sink A" is the selected "default sink" in the UI but it happens to not have any playback going on, while another "sink B" does have playback going on, then the code would select "preferred sink" as "sink B", not "sink A", and volume changes would affect "sink B" and not "sink A". That seems to be with the best of intentions, however something is not working correctly in the case of virtual pipewire sinks. I don't see any obvious logic error by reading the code and running it mentally. But I haven't managed to debug it since I don't know of an easy way to compile and run this applet and see some sort of console output. Simple fix would be to just disregard this "preferred sink" concept at all and just always adjust the volume of the selected "default sink". However that feature is there for 7 years and I guess most KDE mantainers would not agree to delete an already deployed feature like this. So... maybe someone can properly debug this code and find the bug? Perhaps pipewire is guilty of not reporting the correct state of its devices, if we can debug and show that it is the case, we should file a bug report in pipewire. Or perhaps there is a logic bug in this code that I'm not seeing now. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 411729] Accented and dead keys do not work when QT_IM_MODULE is set to anything
https://bugs.kde.org/show_bug.cgi?id=411729 Eduardo changed: What|Removed |Added CC||eduardo.b...@hotmail.com Status|RESOLVED|VERIFIED --- Comment #47 from Eduardo --- Had this problem on Wayland Fedora37 some weeks ago, then fixed it with QT_IM_MODULE=ibus. One day I changed to X11 and the problem reappeared, but then vanished again when I went back to Wayland. Now I just updated to Fedora 38 (Wayland), and the issue came back, even with QT_IM_MODULE=ibus. Interesting notes: - When I launch e.g. Konsole from the launcher, I cannot type the dead keys ~´` - If I launch Konsole from itself, by running "konsole", it suddenly works - I recorded the output of `env` for both cases above and got the following diff (which I don't see anything wrong): 26c26 < KONSOLE_DBUS_SERVICE=:1.97 --- > KONSOLE_DBUS_SERVICE=:1.98 35a36 > LESS=-R 37a39 > LSCOLORS=Gxfxcxdxbxegedabagacad 41a44 > PAGER=less 56c59,60 < SHELL_SESSION_ID=458ac8224e6f49fba96d12b85f056764 --- > SHELL_SESSION_ID=9001639909854c029a48343daeac455d > SHLVL=2 84d87 < SHLVL=1 86,89d88 < PAGER=less < LESS=-R < LSCOLORS=Gxfxcxdxbxegedabagacad < LC_ALL=en_US.UTF-8 90a90 > LC_ALL=en_US.UTF-8 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 411729] Accented and dead keys do not work when QT_IM_MODULE is set to anything
https://bugs.kde.org/show_bug.cgi?id=411729 --- Comment #49 from Eduardo --- (In reply to Andrey from comment #48) > Please make sure you have no ibus daemons/packages. Search this report about > ibus. > Then retest all the env/platform combinations possible. I'm not running any process/daemon containing the keyword "ibus" (although there are some packages installed). I thought ibus was the solution, is it not? First time I solved this issue by changing from xim to ibus in the QT environment variable. I still don't get why the application would behave differently with mostly the same environment. > Also, what languages do you have configured, what order? Initially I had installed Fedora 37 in Brazilian Portuguese, but soon I changed it to American English alone. My current locale is: LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=en_US.UTF-8 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 411729] Accented and dead keys do not work when QT_IM_MODULE is set to anything
https://bugs.kde.org/show_bug.cgi?id=411729 --- Comment #50 from Eduardo --- Found a solution! 1. Launch the Input Method Selector 2. Select IBus (I'm on Wayland) and Logout Somehow mine was set to "No Input Method" after the upgrade. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 411729] Accented and dead keys do not work when QT_IM_MODULE is set to anything
https://bugs.kde.org/show_bug.cgi?id=411729 --- Comment #52 from Eduardo --- (In reply to Andrey from comment #51) > The accented symbols should work without any Input Method, though. > See the reports above. Before finding the solution, I tried to set QT_IM_MODULE to an empty string in /etc/environment, without success after restarting the session. After selecting the ibus as input method on the GUI, then QT_IM_MODULE has been redefined to "ibus" somewhere, and everything seems to be working fine now. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469656] Dolphin cannot remember previously opened tabs
https://bugs.kde.org/show_bug.cgi?id=469656 Eduardo changed: What|Removed |Added CC||ed...@inbox.lv --- Comment #15 from Eduardo --- Created attachment 158994 --> https://bugs.kde.org/attachment.cgi?id=158994&action=edit Problem investigation result sample -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469656] Dolphin cannot remember previously opened tabs
https://bugs.kde.org/show_bug.cgi?id=469656 --- Comment #16 from Eduardo --- Background --- I heavily rely on activity functionality to restore whole session and have all tabs in places where it was before logout (I have too many of them to handle manually), so I went investigating this issue as my time permitted. As a result I compiled my own version where part of this patch is reverted and it's working. Investigation results (may be useful to ones who will try to solve the issue) --- if I comment out almost all of the new solution in "Dolphin::dolphinGuiInstances" and put back the old solution in global.cpp, BUT still have "#if HAVE_KACTIVITIES" which relates to QEventLoop (the "first if"), the result was the same - it does not work for me. If I comment out "first if", leaving just the old solution, the issue is solved. So this leads to event loop issue which was there for "ensures the consumer is ready for query". Hope this helps, I'll attach a file with actual sample. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456511] VLC and Firefox freeze / stop updating their window contents after being used for a while
https://bugs.kde.org/show_bug.cgi?id=456511 --- Comment #32 from Eduardo --- Thanks for the patch, I applied this patch to 5.25.5 version of kwin, let's see whether it solves the issue. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 487698] Desktop folders move to different displays on login or when connecting a display
https://bugs.kde.org/show_bug.cgi?id=487698 --- Comment #5 from Eduardo --- I'll check whether this is an issue with Plasma 6.1.0 which will be released soon. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 487671] New: Plasma "system widgets", like "System monitor widget", "Hard Disk activity widget", etc. ar too narrow (tiny)
https://bugs.kde.org/show_bug.cgi?id=487671 Bug ID: 487671 Summary: Plasma "system widgets", like "System monitor widget", "Hard Disk activity widget", etc. ar too narrow (tiny) Classification: Plasma Product: kdeplasma-addons Version: 6.0.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: ed...@inbox.lv Target Milestone: --- Created attachment 169902 --> https://bugs.kde.org/attachment.cgi?id=169902&action=edit tiny widgets SUMMARY Plasma "System widgets" (System monitor, HDD activity, Individual Core usage, etc.) horizontal size are way too small, in the attached picture, there are 3 widgets which I separated by red lines to show the tiny width. The width is sort of ~ 2x smaller than height, which renders them very hard to see. I can not control width manually, it is set automatically. STEPS TO REPRODUCE 1. add a widget to panel OBSERVED RESULT Widget's size horizontally is too narrow. EXPECTED RESULT It is at least 2x the vertical size, otherwise it is not really useful. Ideally, I can set the size in % or otherwise. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Graphics Platform: X11 Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION I usually use just 2 widgets, just before I filed this bug, I added 3rd just to check, whether it's my "older" config or problem in general. I think the issue started when I started using Plasma 6, probably 6.0.1, but I had to recreate all of them, so they are not "very old" config. For the proportion, the picture contains neighbouring widgets too, only the "graph" widgets are affected. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 487698] New: Desktop folders move to different displays on login or when connecting a display
https://bugs.kde.org/show_bug.cgi?id=487698 Bug ID: 487698 Summary: Desktop folders move to different displays on login or when connecting a display Classification: Plasma Product: kactivitymanagerd Version: 6.0.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: ed...@inbox.lv CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Most of the time when I log in or connect / disconnect / connect a display, default folders that are displayed on desktop, move somewhere else - I mean they are supposed to be on primary display, but after login, they are not. Sometimes for some activities, they are on primary display as they should be, sometimes they just appear on secondary display and sometimes they just vanish, however if they are not displayed I can get them back by using sort option, just change it from name to size and back or the like. Laptop display resolution is 1080p, some additional displays I connect are 1080p (one at a time), then icons can move to different display. I observed that if I connect 1080p and 1440p and disable built-in display, then icons vanish (most likely move up & out of sight on primary display). In display settings, displays are arranged to have tops aligned. STEPS TO REPRODUCE 1. Use activities (I have 10 of them and 2 virtual desktops), I don't know whether this is an issue with workspaces only 2. Put some stuff on desktop 3. Use the computer as one do (log in, connect display, disconnect display, suspend / resume, log out, log in, etc. like real life usage) OBSERVED RESULT Icons change their location or just vanish. EXPECTED RESULT Icons stay in the same place. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Graphics Platform: X11 Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION This started with Plasma 6.0.1 I think, on 5.x.y was ok. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 487698] Desktop folders move to different displays on login or when connecting a display
https://bugs.kde.org/show_bug.cgi?id=487698 --- Comment #2 from Eduardo --- Icons move all together. I have the same wallpaper on every display, so I did not notice whether it changes or not. Right now after connecting / disconnecting a display, wallpaper and icons stay put, I'll check when I log out and in next time or will connect different resolution display (I can't really log out and in for couple of days). -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 487671] Plasma "system widgets", like "System monitor widget", "Hard Disk activity widget", etc. ar too narrow (tiny)
https://bugs.kde.org/show_bug.cgi?id=487671 --- Comment #4 from Eduardo --- I saw the MR and went to edit QML manually, reloaded plasma (kquitapp6 plasmashell; kstart plasmashell) and now it so so much better! Now that I actually see it, 1.75 (approx 16/9) looks better than 2 times the height, but I guess that is quite subjective. Thank you Marco Martin, this was very quick! -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 487671] Plasma "system widgets", like "System monitor widget", "Hard Disk activity widget", etc. ar too narrow (tiny)
https://bugs.kde.org/show_bug.cgi?id=487671 --- Comment #5 from Eduardo --- I see that in MR there is an idea to use golden ratio from Fibonacci, that is a great idea, looks good to me. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 487912] plasma X11 session is not restored after logout/login
https://bugs.kde.org/show_bug.cgi?id=487912 Eduardo changed: What|Removed |Added CC||ed...@inbox.lv --- Comment #9 from Eduardo --- I can confirm this, luckily I could revert to 6.0.5, heavily rely on session restore functionality. I even restored home FS to a snapshot before I logged in with broken session restore, to be sure. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 487912] plasma X11 session is not restored after logout/login
https://bugs.kde.org/show_bug.cgi?id=487912 --- Comment #10 from Eduardo --- (In reply to Kishore Gopalakrishnan from comment #7) > I can at least confirm that my iceauth file (/run/user/1000/iceauth_XX , > where XX is some apparently random string) is empty, so perhaps > ksmserver is indeed failing to write the 'magic cookie' (whatever that is) > to that file. I don't even have this file on my system with 6.0.5 where everything works just fine. So I would not be so sure that the issue is there. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 487698] Desktop folders move to different displays on login or when connecting a display
https://bugs.kde.org/show_bug.cgi?id=487698 --- Comment #3 from Eduardo --- My current observation is that when I log in and attach a display(s), every activity moves the icons to the right display except the one which are being displayed right when I log in. Additionally, I don't know for sure whether this is universally true, but the activity which has different wallpaper on each of the display, does not have this bug - icons stay put. Strange. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487912] plasma X11 session is not restored after logout/login
https://bugs.kde.org/show_bug.cgi?id=487912 --- Comment #14 from Eduardo --- (In reply to i.Dark_Templar from comment #11) > That is the issue. With new release this file is created, written, but not > flushed or closed, so it stays empty. And new env variable ICEAUTHORITY > pointing to this file is set up. Flushing or closing file fixed issue for me > with plasma workspace 5.27.11.1 as in > https://bugs.kde.org/show_bug.cgi?id=487936#c3. Good catch! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488228] New: Request the ability to toggle the connection indicator from MiB and MB
https://bugs.kde.org/show_bug.cgi?id=488228 Bug ID: 488228 Summary: Request the ability to toggle the connection indicator from MiB and MB Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: aim_less...@hotmail.com Target Milestone: --- Created attachment 170279 --> https://bugs.kde.org/attachment.cgi?id=170279&action=edit Item i am proposal the change to happenm Has we all know ISP,s advertise the connection speeds in Mbps . the ability to change the connection info from MB/s to Mbps would be a very simple QoL change -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 447115] Dolphin reports "Access denied" when moving files from ext4 to ntfs
https://bugs.kde.org/show_bug.cgi?id=447115 Eduardo changed: What|Removed |Added CC||eduardo.c...@kdemail.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480078] New: Artifacts and tearing while dragging windows only under 4k high refresh rate with UI global scale
https://bugs.kde.org/show_bug.cgi?id=480078 Bug ID: 480078 Summary: Artifacts and tearing while dragging windows only under 4k high refresh rate with UI global scale Classification: Plasma Product: kwin Version: 5.27.10 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: eduardo.c...@kdemail.net Target Milestone: --- Created attachment 165059 --> https://bugs.kde.org/attachment.cgi?id=165059&action=edit Video showing the artifacts I got a new monitor and I started experiencing visual artifacts while dragging windows, specially if the window being dragged overlaps with the taskbar. The taskbar displays some flickering, and the window displays some crazy tearing/rectangular holes. Difficult to explain in words, please see attached video for clarification. For me this only happens on the 4k resolution (3840x2160) AND using refresh rates either 144Hz or 160Hz, AND using 150% scaling factor (might happen on other scaling factor). If I put 4k 120Hz or below, the bug doesn't trigger, it needs at least 144Hz to trigger. If I lower the resolution to anything below 4k, it doesn't happen. If I use 100% scaling, it doesn't happen, even on 4k 160Hz. So you need these 3 conditions to trigger it: 4k, 144Hz+, and a scaling factor like 150%. STEPS TO REPRODUCE 1. Own a 4k+high refresh rate monitor 2. Set the resolution to 4k, the refresh rate to at least 144Hz, and the global scaling factor to 150%. 3. Drag some window overlapping the taskbar OBSERVED RESULT Crazy tearing/rectangular holes on the window being dragged, and flickering on the taskbar. EXPECTED RESULT Smooth dragging with no artifacts SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.1.71-1-lts (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 31,3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2 nVidia driver version 535.113.01 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415248] Resize handles in desktop edit mode disappear when resizing widgets
https://bugs.kde.org/show_bug.cgi?id=415248 Eduardo changed: What|Removed |Added CC||eduardo.c...@kdemail.net --- Comment #2 from Eduardo --- If I hover the cursor near the edge of the resize circle, the circle disappears, but the cursor is still displayed in its "resize" form. If I grab the resize circle by its edge (gotta click it fast, before it disappears), I can start the drag-to-resize operation, but if I wiggle the mouse around, it loses the grip as the resize circle eventually disappears during the resize operation, even though I'm still holding the left mouse button, that is pretty annoying. This feature is normally used only when setting up the desktop for the first time, so it doesn't affect much of everyday use. But since it is done on initial setup, it is perceived by first-timers and could pass a bad first impression about Plasma. I remember I saw it on my first day of use and it surely caused a bad impression for myself. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446044] New: Allow typing to locate desktop icons like in Dolphin (or Windows)
https://bugs.kde.org/show_bug.cgi?id=446044 Bug ID: 446044 Summary: Allow typing to locate desktop icons like in Dolphin (or Windows) Product: plasmashell Version: 5.22.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: eduardo.c...@kdemail.net CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY In the Desktop, if we select an icon and then start typing on the keyboard, the krunner text dialog shows up and that's what gets the keyboard input. However, for people who like to put many files/folders on the desktop, it would be desirable to type the beginning of the icon's name and the selection would jump to it, making it easy to locate the desired icon. Windows does this. Also Dolphin, and many file managers. It would be coherent for plasma desktop to do the same. And I think it should be the default behavior. That is what users migrating from Windows are expecting. STEPS TO REPRODUCE 1. Select an icon on the desktop 2. Type some text on your keyboard OBSERVED RESULT krunner dialog shows up, and you realize you are typing into it. EXPECTED RESULT The icon whose name starts with the text that you typed should be selected. Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.4-arch1-1 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 397272] Find Tool does not show total number of matches or current match number
https://bugs.kde.org/show_bug.cgi?id=397272 Eduardo changed: What|Removed |Added CC||eduardo.c...@kdemail.net --- Comment #3 from Eduardo --- I was about to open a feature request for this but found it already existed. I'm all for this, it is something I've missed since I started using KDE software. We can take Firefox's "CTRL+F" search bar as a reference. It shows a label like "1 of 12 matches" in the very search bar itself. I understand there is the "Find all" feature in Kate, but that's not the same thing. What we are requesting here is really just that label on the small & quick CTRL+F bar. I really helps to organize thoughts when editing any kind of text/code/config/script file. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443847] Joystick KCM should automatically refresh the devices list when a new game controller appears
https://bugs.kde.org/show_bug.cgi?id=443847 Eduardo changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||eduardo.c...@kdemail.net Ever confirmed|0 |1 --- Comment #1 from Eduardo --- I confirm, this happens to me too. It's minor, but pass a bad image. It should be able to detect a new /dev/js* device automatically without the user having to go back and forth to the same screen. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426230] Joystick KCM updates values and crosshair slowly
https://bugs.kde.org/show_bug.cgi?id=426230 Eduardo changed: What|Removed |Added CC||eduardo.c...@kdemail.net Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Eduardo --- It happens to me with an Xbox Elite Series 2 plugged via USB cable. I haven't looked into the code, but it feels like the controller sends events faster than the applet can process in real time, and the events get buffered in a queue, which causes the delay in the UI. It's bad to the point that this KDE applet can't be trusted to check if a controller is responding properly. jstest-gtk is an alternative which gives much better response, so we can confirm that it is an issue with this KDE module. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 409392] NetworkManager widget freezes on VPN connection issues, freezing/blocking Plasma
https://bugs.kde.org/show_bug.cgi?id=409392 Eduardo changed: What|Removed |Added CC||ed...@inbox.lv --- Comment #12 from Eduardo --- To me this still happens in 5.23.3 when there is a bad connectivity, for instance, not long ago I had a bad connection with my provider and there was 50% packet loss, anything I do on network applet, froze plasma for some time. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 440585] Tabs bar tends to scroll left and hides all tabs to the right of current tab
https://bugs.kde.org/show_bug.cgi?id=440585 Eduardo changed: What|Removed |Added CC||ed...@inbox.lv --- Comment #5 from Eduardo --- I am actually quite surprised that this behaviour is deemed to be correct. Why would tab positions change based on which documents are edited and saved, is not clear to me. There is just one solution - do not scroll / move tab positions while editing and saving documents, squeezed tabs won't work, because at the end there might be too much of them anyway. Actually I tried konsole with too much tabs, it's not right IMO there too. If there is a scrollable tab bar and I scroll to the very right and click on 3rd tab to the left, it changes the tab under! the mouse right away - I mean I just selected the tab and it already moved away, which is even more confusing. Anyhow, this is about kate and I really hope the sane (IMO) behaviour will eventually come to at least kate. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408919] "open externally called folder in new tab" feature should take virtual Desktops and Activities into account
https://bugs.kde.org/show_bug.cgi?id=408919 Eduardo changed: What|Removed |Added CC||ed...@inbox.lv --- Comment #17 from Eduardo --- I was going to create a new bug for Dolphin <-> Activities interaction, but it seems that this is the place to comment. Please suggest if new bug has to be created. So, here are my 2 issues. I have one Dolphin window opened in each of my 9 activities, when mounting external LUKS encrypted disk from "Disks & devices", KDE always change the activity and open the mounted directory in some arbitrary Dolphin instance on other activity. To me the destination activity looks random, every reboot it’s different activity (maybe first dolphin window which was started?). It should open it in the Dolphin window of the activity I’m currently on. Similar thing happens when I’m uncompressing a file in Dolphin using right click on the file. It uncompresses the file, switch the activity and focus some other Dolphin window on some other activity not even showing the contents of the uncompressed archive in original nor the wrong activity it switched to. I think that this actually worked on 5.22.x, but I'm not very sure about this. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kuserfeedback] [Bug 442296] "CMake Error: The INTERFACE_QT_MAJOR_VERSION property of "Qt5::Core" does not agree with the value of QT_MAJOR_VERSION already determined for KUserFeedbackQml /
https://bugs.kde.org/show_bug.cgi?id=442296 --- Comment #3 from Eduardo --- I just tried building it again now with kdesrc-build and now it works! I didn't do anything on my system, I guess it was some misconfiguration on the git master and somebody fixed it in the meantime. If it also works for the OP, maybe we can close this bug report. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 437258] Brightness should never be increased when battery reaches the critical level
https://bugs.kde.org/show_bug.cgi?id=437258 Eduardo changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Version|5.21.5 |5.24.4 CC||eduardo.c...@kdemail.net --- Comment #1 from Eduardo --- This just happened to me! I was using my laptop with 1% brightness on the bed with my wife sleeping beside me. Suddenly my battery reached the critical level and the brightness increased to 30% which seemed like a flash to my eyes. Luckily my wife didn't wake up. I'm confirming the bug and updating the version. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 454390] New: Kopete crash on exit (ctrl-q)
https://bugs.kde.org/show_bug.cgi?id=454390 Bug ID: 454390 Summary: Kopete crash on exit (ctrl-q) Product: kopete Version: unspecified Platform: Slackware Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kopete-bugs-n...@kde.org Reporter: solleri...@gmail.com Target Milestone: --- Application: kopete (1.13.0) Qt Version: 5.15.3 Frameworks Version: 5.90.0 Operating System: Linux 5.15.38 x86_64 Windowing System: X11 Distribution: Slackware 15.0 x86_64 DrKonqi: 5.23.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Whenever I quit the app, (Ctrl-Q or menu) the process hangs. - Custom settings of the application: It's configured a single jabber account. The crash can be reproduced every time. -- Backtrace: Application: Kopete (kopete), signal: Segmentation fault [KCrash Handler] #4 0x7fe949d4f2bb in QThreadStorageData::get() const () from /usr/lib64/libQt5Core.so.5 #5 0x7fe949df01dd in ?? () from /usr/lib64/libQt5Core.so.5 #6 0x7fe945faccb7 in pcre2_jit_match_16 () from /usr/lib64/libpcre2-16.so.0 #7 0x7fe945fadb29 in pcre2_match_16 () from /usr/lib64/libpcre2-16.so.0 #8 0x7fe949df0378 in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x7fe949df3807 in ?? () from /usr/lib64/libQt5Core.so.5 #10 0x7fe949df3bfc in QRegularExpression::match(QString const&, int, QRegularExpression::MatchType, QFlags) const () from /usr/lib64/libQt5Core.so.5 #11 0x7fe949e55134 in ?? () from /usr/lib64/libQt5Core.so.5 #12 0x7fe949e561ec in ?? () from /usr/lib64/libQt5Core.so.5 #13 0x7fe949e568af in ?? () from /usr/lib64/libQt5Core.so.5 #14 0x7fe949e56f7c in QDirIterator::QDirIterator(QString const&, QStringList const&, QFlags, QFlags) () from /usr/lib64/libQt5Core.so.5 #15 0x7fe949e50898 in QDir::entryList(QStringList const&, QFlags, QFlags) const () from /usr/lib64/libQt5Core.so.5 #16 0x7fe92e97fa7f in ChatWindowStyle::listVariants() () from /usr/lib64/libkopetechatwindow_shared.so.1 #17 0x7fe92e982dc0 in ChatWindowStyle::init(QString const&, ChatWindowStyle::StyleBuildMode) () from /usr/lib64/libkopetechatwindow_shared.so.1 #18 0x7fe92e97d655 in ChatWindowStyleManager::getStyleFromPool(QString const&) () from /usr/lib64/libkopetechatwindow_shared.so.1 #19 0x7fe92e97dcdd in ChatWindowStyleManager::getValidStyleFromPool(QString const&) () from /usr/lib64/libkopetechatwindow_shared.so.1 #20 0x7fe92e96966d in ChatMessagePart::setStyle(QString const&) () from /usr/lib64/libkopetechatwindow_shared.so.1 #21 0x7fe92e96969a in ChatMessagePart::clearStyle() () from /usr/lib64/libkopetechatwindow_shared.so.1 #22 0x7fe949f5e47d in ?? () from /usr/lib64/libQt5Core.so.5 #23 0x7fe949f57ecf in QObject::destroyed(QObject*) () from /usr/lib64/libQt5Core.so.5 #24 0x7fe949f5c9bd in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #25 0x7fe92e97f3e9 in ChatWindowStyle::~ChatWindowStyle() () from /usr/lib64/libkopetechatwindow_shared.so.1 #26 0x7fe92e97b9b7 in ChatWindowStyleManager::~ChatWindowStyleManager() () from /usr/lib64/libkopetechatwindow_shared.so.1 #27 0x7fe94975f4c7 in __run_exit_handlers () from /lib64/libc.so.6 #28 0x7fe94975f66a in exit () from /lib64/libc.so.6 #29 0x7fe949745044 in __libc_start_main () from /lib64/libc.so.6 #30 0x00416d9a in _start () [Inferior 1 (process 2733) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455679] New: Activities: window management and session restore is broken in 5.25
https://bugs.kde.org/show_bug.cgi?id=455679 Bug ID: 455679 Summary: Activities: window management and session restore is broken in 5.25 Product: kwin Version: 5.25.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: activities Assignee: kwin-bugs-n...@kde.org Reporter: ed...@inbox.lv Target Milestone: --- Created attachment 149974 --> https://bugs.kde.org/attachment.cgi?id=149974&action=edit Window management broken for activities SUMMARY Window management is broken, sending window to another activity still shows the window, which is not interactive. STEPS TO REPRODUCE 1. Please check attached video for window management issue. OBSERVED RESULT Window appears to be visible, on top but can not be interacted with. EXPECTED RESULT Window is moved to desired activity and is not shown anymore. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Graphics Platform: X11 Graphics Processor: AMD Radeon RX 570 Series ADDITIONAL INFORMATION Created a completely new user to test this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455679] Activities: window management is broken in 5.25
https://bugs.kde.org/show_bug.cgi?id=455679 Eduardo changed: What|Removed |Added Summary|Activities: window |Activities: window |management and session |management is broken in |restore is broken in 5.25 |5.25 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455679] Activities: window management / movement is broken in 5.25
https://bugs.kde.org/show_bug.cgi?id=455679 Eduardo changed: What|Removed |Added Summary|Activities: window |Activities: window |management is broken in |management / movement is |5.25|broken in 5.25 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455679] Activities: window management / movement is broken in 5.25
https://bugs.kde.org/show_bug.cgi?id=455679 Eduardo changed: What|Removed |Added Version|5.25.0 |5.25.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431446] Blinking panels and window contents not refreshing
https://bugs.kde.org/show_bug.cgi?id=431446 --- Comment #37 from Eduardo --- Created attachment 151905 --> https://bugs.kde.org/attachment.cgi?id=151905&action=edit FF won't update its contents Plasma 5.25.5 For a long time I did not encounter this bug, but now it's back again... Here is my situation. Since the bug was so annoying and prevented my work to be done, I had reset all plasma to defaults and somehow I did not encounter the bug for some time. In addition to this, for some time MESA changed the driver from i965 to iris, at first I thought that this is what helped to get rid of the bug for the most part, but now I'm not sure anymore... And I'm not sure about this, because after I updated to plasma 5.25.5, I enabled a nice feature I liked - Translucency, specifically the defaults, i.e. when moving windows, they become transparent. Soon after that I got the bug reappear, Firefox won't update its contents... The weird part is that disabling and enabling composition does NOT get the contents back as it was before! I have to restart the application... Is this really related to transparency things... I'll disable the effect will report back whether the issue reappears. The attachment shows that: 1. contents are not updated 2. even new windows of the same application (FF) inherits the same buggy behaviour 3. disabling / enabling composite won't get rid of the bug -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431446] Blinking panels and window contents not refreshing
https://bugs.kde.org/show_bug.cgi?id=431446 Eduardo changed: What|Removed |Added Version|5.20.5 |5.25.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439899] A second fixed cursor in the center of the screen on top of all sometimes appears.
https://bugs.kde.org/show_bug.cgi?id=439899 Eduardo changed: What|Removed |Added CC||zl...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441516] filter toolbar icon missing and related issues
https://bugs.kde.org/show_bug.cgi?id=441516 Eduardo changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||zl...@hotmail.com Status|REPORTED|NEEDSINFO --- Comment #2 from Eduardo --- Hi, my filter icon is displaying fine. Maybe yours got hidden for some reason? In the menus, go to "Settings -> Configure Toolbars". Find the entry "Filter" on the "Available actions" list and add it to the "Current actions" list. Click OK. Does that make it re-appear? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411878] Dolphin is not clearing prior filter view if directory is open
https://bugs.kde.org/show_bug.cgi?id=411878 Eduardo changed: What|Removed |Added Version|19.08.0 |21.08.1 CC||zl...@hotmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Eduardo --- Happens to me on current version. I'm updating the version and changing to CONFIRMED. You can actually reproduce it by simply expanding some folder before filtering, then filter by some nonsense string "asdasdasd" than should yield zero results, but the folder you expanded will show as a result. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427771] Flat/Adaptive pointer acceleration setting does nothing on wayland
https://bugs.kde.org/show_bug.cgi?id=427771 Eduardo changed: What|Removed |Added Ever confirmed|0 |1 Version|5.20.0 |5.22.5 Status|REPORTED|CONFIRMED CC||eduardo.c...@kdemail.net --- Comment #7 from Eduardo --- Happens to me under Wayland on ArchLinux. Under XOrg it works fine. I'm changing to CONFIRMED. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411878] Dolphin is not clearing prior filter view if directory is open
https://bugs.kde.org/show_bug.cgi?id=411878 Eduardo changed: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |eduardo.c...@kdemail.net Status|CONFIRMED |ASSIGNED --- Comment #2 from Eduardo --- I found the bug: void KFileItemModel::applyFilters() in the file src/kitemviews/kfileitemmodel.cpp. The algorithm creates the bug on purpose, but it doesn't have to. I'll try to fix it over the weekend. Assigning to myself. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442275] New: Creating a folder while filtering messes the filter results
https://bugs.kde.org/show_bug.cgi?id=442275 Bug ID: 442275 Summary: Creating a folder while filtering messes the filter results Product: dolphin Version: 21.08.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: filter Assignee: dolphin-bugs-n...@kde.org Reporter: eduardo.c...@kdemail.net CC: kfm-de...@kde.org Target Milestone: --- Created attachment 141451 --> https://bugs.kde.org/attachment.cgi?id=141451&action=edit Parent folder "a" is not displayed, despite being expanded and its child folders "b" and "b2" being displayed. SUMMARY While filtering on expanded details view mode, if we create a folder that satisfies the filter as a child of an expanded folder, Dolphin will mess up the file listing, making the parent folder disappear and the childs appear in a buggy state without their parent being display (see screenshot). This is a very specific bug, very difficult to explain and difficult to trigger in normal use, but it exists and I have successfully devised a simple recipe to reproduce it consistently. It is really difficult to explain in words, its better to just do the steps below and you will see the bug for yourself. STEPS TO REPRODUCE 1. Create an empty folder anywhere, named "test" (or whatever name you desire). Open it on Dolphin. 2. Make sure you are on Details View mode with expandable folders. 3. Create a folder named "a" inside "test". 4. Right click "a", Create New -> Folder, and name it "b". 5. Expand folder "a", you should see the tree: "a" as parent and "b" as child. 6. Filter for the string "b". It should not change the view at all, since folder "b" passes the filter and "a" is shown because it is its parent. 7. Now, with the filter activated, right click "a" and create another folder named "b2" (a sibling of "b"). 8. The bug is now triggered: after 1 second, folder "a" will disappear, and you will only see folders "b" and "b2", weirdly linked to no parent (screenshot). OBSERVED RESULT Folders "b" and "b2" are displayed linked to an invisible parent. EXPECTED RESULT Folder "a" should remain on display, with folders "b" and "b2" as its children passing the filter. SOFTWARE/OS VERSIONS Dolphin 21.08.1 Operating System: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.14.2-arch1-2 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION I discovered this bug while testing my solution for bug #411878. I thought I had introduced the bug, bug then I found out it was already there before my changes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439899] A second fixed cursor in the center of the screen on top of all sometimes appears.
https://bugs.kde.org/show_bug.cgi?id=439899 Eduardo changed: What|Removed |Added Version|5.22.3 |5.22.5 Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #10 from Eduardo --- I'm affected. I have a laptop with NVidia prime configuration, with both a touchpad and a connected USB mouse, if that's relevant. It happens every time when computer goes to sleep automatically due to inactivity timeout. After resuming, I always have an extra dead cursor permanently displayed. "kwin_wayland --replace" is somewhat a workaround, faster than rebooting, but it still kills the running apps. Any better (less drastic) workaround while it is not fixed? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439405] Plasma panel remains visible when I activate full screen mode of apps running natively on Wayland
https://bugs.kde.org/show_bug.cgi?id=439405 Eduardo changed: What|Removed |Added CC||eduardo.c...@kdemail.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439405] Plasma panel remains visible when I activate full screen mode of apps running natively on Wayland
https://bugs.kde.org/show_bug.cgi?id=439405 --- Comment #6 from Eduardo --- I'm affected. I think it is in someway by apps running XWayland going full screen. The XWayland apps themselves are always able to go fullscreen just fine, but they sometimes trigger the bugged state for the native Wayland apps. Ex: open both VLC (XWayland) and a native Wayland app (Gwenview). Watch a video on VLC on full screen for some seconds... exit full screen but leave VLC open, and try to put the Wayland app on full screen: it will sometimes trigger the bug, sometimes not. If I insist on trying this recipe, it will surely trigger the bug eventually. Once triggered, the bug consistently keeps happening every time the Wayland goes full screen, but immediately stops happening when I simply minimize VLC. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420966] After tab-completing to a path (or typing a trailing slash) and hitting enter, Dolphin instead navigates to the first suggested subdirectory of that path
https://bugs.kde.org/show_bug.cgi?id=420966 Eduardo changed: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |eduardo.c...@kdemail.net Version|20.04.0 |21.08.1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420966] After tab-completing to a path (or typing a trailing slash) and hitting enter, Dolphin instead navigates to the first suggested subdirectory of that path
https://bugs.kde.org/show_bug.cgi?id=420966 --- Comment #22 from Eduardo --- Git commit 764f6bd6980fd77b9730d59cbe8a7198bda04a97 by Eduardo de Souza Cruz. Committed on 19/09/2021 at 22:08. Pushed by dfaure into branch 'master'. New shouldAutoSuggest property on KCompletion. Subclasses may set its value to false to block autosuggestion in special cases. KLineEdit now reads this property before displaying the autosuggestion. It's the first step in fixing this bug: M +13 -0src/kcompletion.cpp M +18 -0src/kcompletion.h M +1-0src/kcompletion_p.h M +1-1src/klineedit.cpp https://invent.kde.org/frameworks/kcompletion/commit/764f6bd6980fd77b9730d59cbe8a7198bda04a97 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 442717] New: The URL navigator shows child directories in improper order in some cases
https://bugs.kde.org/show_bug.cgi?id=442717 Bug ID: 442717 Summary: The URL navigator shows child directories in improper order in some cases Product: frameworks-kio Version: git master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: URL navigator Assignee: kio-bugs-n...@kde.org Reporter: eduardo.c...@kdemail.net CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 141711 --> https://bugs.kde.org/attachment.cgi?id=141711&action=edit Screenshot showing the bugged ordering SUMMARY The URL navigator shows child directories in improper order in some cases. If there is a child directory named "somefolder", and another child directory named "somefolder_A", the latter is incorrectly displayed first in the list of suggestions, contrary to the order that Dolphin itself displays its directories. If using the "Automatic" or "Dropdown List & Automatic", this actually causes a very annoying behavior that makes it pretty hard to enter "somefolder". If we type in the exact full path to "somefolder" (without the trailing slash), the completion mechanism will suggest "somefolder_A" and that is where we are taken if we press ENTER. This also happens if we have a "somefolder.A" or "somefolder-A", probably even other special characters. It doesn't happen if the next character after the "somefolder" string is a letter or a number. See attached screenshot for clarification. STEPS TO REPRODUCE 1. Create a folder named "~/test" 2. Inside this new "~/test" folder, create directories "somefolder" and "somefolder_A" 3. In Dolphin, make the location bar editable, right-click it and make sure "Dropdown List & Automatic" is selected under the "Text Completion" menu. 4. Manually type "~/test/somefolder" (without quotes) into the location bar, but don't press ENTER yet. 5. Observe the bugged ordering in the dropdown list 6. Observe that it is suggesting to autocomplete to "~/test/somefolder_A" 7. Press ENTER. You will be taken to "~/test/somefolder_A". But you typed the exact path to "~/test/somefolder", your intention was likely to go to "~/test/somefolder". OBSERVED RESULT We see that special characters currently have priority over an "End-Of-String" char in this ordering EXPECTED RESULT "End-Of-String" char should have priority over any other character SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.5-arch1 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 442717] The URL navigator shows child directories in improper order in some cases
https://bugs.kde.org/show_bug.cgi?id=442717 Eduardo changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 Assignee|kio-bugs-n...@kde.org |eduardo.c...@kdemail.net --- Comment #1 from Eduardo --- Assigning to myself, I will investigate and try to fix it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 442717] The URL navigator shows child directories in improper order in some cases
https://bugs.kde.org/show_bug.cgi?id=442717 --- Comment #2 from Eduardo --- Most likely it is ordering considering the trailing "/" that it adds on the dropdown list text entries, and that is what's causing the bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420966] After tab-completing to a path (or typing a trailing slash) and hitting enter, Dolphin instead navigates to the first suggested subdirectory of that path
https://bugs.kde.org/show_bug.cgi?id=420966 Eduardo changed: What|Removed |Added Latest Commit|https://invent.kde.org/fram |https://invent.kde.org/fram |eworks/kio/-/commit/9f5f854 |eworks/kio/commit/0a10b3311 |0112e1178aa54a350f29b542c5d |aef441f748745cfc86828688052 |e7df68 |209b Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #23 from Eduardo --- Git commit 0a10b3311aef441f748745cfc86828688052209b by Eduardo de Souza Cruz. Committed on 20/09/2021 at 02:11. Pushed by dfaure into branch 'master'. KUrlCompletion blocks autosuggestion from happening if the input is an exact directory path. Before it was suggesting the first child directory and causing the following bug: M +4-0src/widgets/kurlcompletion.cpp https://invent.kde.org/frameworks/kio/commit/0a10b3311aef441f748745cfc86828688052209b -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421337] Switching Dolphin tabs or directories twice quickly causes terminal directory to desync
https://bugs.kde.org/show_bug.cgi?id=421337 Eduardo changed: What|Removed |Added Platform|Other |Archlinux Packages CC||eduardo.c...@kdemail.net Version|20.04.0 |21.08.1 --- Comment #2 from Eduardo --- It's not a minor issue if somebody is planning to run a "rm *" command while being unaware that the directory in the terminal could not be what they are seeing in dolphin. Could cause serious damage to somebody. We shouldn't overlook it and treat it as minor, it's a bug and it must be fixed. I myself have been annoyed by it enough to search for a bug report. It still happens, so I'm updating the version. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442275] Creating a folder while filtering messes the filter results
https://bugs.kde.org/show_bug.cgi?id=442275 Eduardo changed: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |eduardo.c...@kdemail.net Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Eduardo --- I mentioned this in this MR, although it doesn't solve it: https://invent.kde.org/system/dolphin/-/merge_requests/271 I intend to investigate this bug, assigning to myself. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441516] filter toolbar icon missing and related issues
https://bugs.kde.org/show_bug.cgi?id=441516 Eduardo changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450958] New: kwin_x11 crash
https://bugs.kde.org/show_bug.cgi?id=450958 Bug ID: 450958 Summary: kwin_x11 crash Product: kwin Version: 5.24.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: ed...@inbox.lv Target Milestone: --- Created attachment 147186 --> https://bugs.kde.org/attachment.cgi?id=147186&action=edit kwin crash on x11 SUMMARY this time kwin_x11 crashed while joining and using Jitsi meet, before it happened when resizing openoffice doc, but most often this is due to using Discord, Jitsi etc. This is what I can recall I was doing before crash. STEPS TO REPRODUCE I can not make it 100% reproducible, it just crashes, it does not close all apps, just every app gets switched to the activity and desktop which is currently active. OBSERVED RESULT Crash EXPECTED RESULT No crash SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION It looks like it might be related to glibc-2.33 upgrade to 2.35, but it may as well be coincidence. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450958] kwin_x11 crash
https://bugs.kde.org/show_bug.cgi?id=450958 --- Comment #1 from Eduardo --- Created attachment 147195 --> https://bugs.kde.org/attachment.cgi?id=147195&action=edit Next crash while the desktop is totally idle Here's the next crash, this happened while desktop was idle (from user perspective) for at least half a minute. Since in log files I saw kdeconnect stuff too, I can add that I picked up a phone with kdeconnect installed and somewhere about that time when I unlocked it kwin_x11 crashed. Maybe a coincidence, ofc. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450958] kwin_x11 crash
https://bugs.kde.org/show_bug.cgi?id=450958 --- Comment #2 from Eduardo --- Created attachment 147196 --> https://bugs.kde.org/attachment.cgi?id=147196&action=edit Next crash while the desktop is totally idle even longer I had another crash while sitting totally idle for at least couple of minutes. It seems that its crashing at random (from my POV). Since this is happening on work laptop every couple of hours or so, I'm switching back to 5.23.5 + whatever Manjaro has in stable. So I will not be able to test in near future. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450958] kwin_x11 crash
https://bugs.kde.org/show_bug.cgi?id=450958 --- Comment #3 from Eduardo --- If this helps: on laptop, lid closed, 2 additional displays, all in landscape mode, one 120Hz (primary), other 60Hz, Intel 530. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450958] kwin_x11 crash
https://bugs.kde.org/show_bug.cgi?id=450958 --- Comment #4 from Eduardo --- (In reply to Eduardo from comment #2) > Since this is happening on work laptop every couple of hours or so, I'm > switching back to 5.23.5 + whatever Manjaro has in stable. So I will not be > able to test in near future. Disregard this, 5.24.2 is already in stable, will try to find a workaround... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450958] kwin_x11 crash
https://bugs.kde.org/show_bug.cgi?id=450958 --- Comment #6 from Eduardo --- Thanks, will try that if nothing changes. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 432643] kdeconnect slowing down system shutdown
https://bugs.kde.org/show_bug.cgi?id=432643 --- Comment #23 from Eduardo --- That's great! Are you planning to submit a merge request? Do you know if there is a reason for plasmashell requesting another instance of kdeconnectd after the first one just died? If there is no reason, maybe we should patch this end as well. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 432643] kdeconnect slowing down system shutdown
https://bugs.kde.org/show_bug.cgi?id=432643 --- Comment #26 from Eduardo --- (In reply to Nicolas Fella from comment #24) > Since kdeconnectd is DBus-activatable it will get launched to be able to > respond to the call What happens to this new kdeconnectd when we have this patch applied? Does it keep running forever or is it killed somehow? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 456890] New: Spectacle says picture has been copied to clipboard even when option is disabled
https://bugs.kde.org/show_bug.cgi?id=456890 Bug ID: 456890 Summary: Spectacle says picture has been copied to clipboard even when option is disabled Product: Spectacle Version: 21.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: eduardo.b...@hotmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 150723 --> https://bugs.kde.org/attachment.cgi?id=150723&action=edit Screenshot of the false information side-by-side with the configuration option. SUMMARY Spectacle says picture has been copied to clipboard even when option is disabled STEPS TO REPRODUCE By default, Spectacle doesn't copy to clipboard, but says it has. OBSERVED RESULT Clipboard did not change EXPECTED RESULT Picutre should be on clipboard SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457284] X11: Lock screen wallpaper is all black on Nvidia hardware
https://bugs.kde.org/show_bug.cgi?id=457284 Eduardo changed: What|Removed |Added CC||eduardo.c...@kdemail.net --- Comment #6 from Eduardo --- I've got the same issue, background is always black, and sometimes it aggravates a little more as the current date and time information sometimes shows up incomplete, only a few of the numbers are displayed. Only happens when directly returning from sleep. If I unlock it, then just lock the screen again without sleep, the lock screen shows up fine. It wasn't always like this. It started happening a couple months back, I don't know exactly when... Hard to tell where the bug is located down the stack, could be kernel, nvidia drivers, or kde software. I would guess it's some sort of race condition, maybe something is being requested of the graphics card while it is still not ready back from sleep. It happens on my 2 computers, both with kernel 5.18.16-zen, nvidia-dkms 515.65.01-1, kwin/plasma 5.25.4 under XOrg. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 443169] New: Clicking with mouse "back" or "forward" buttons while hovering items selects and potentially drags them
https://bugs.kde.org/show_bug.cgi?id=443169 Bug ID: 443169 Summary: Clicking with mouse "back" or "forward" buttons while hovering items selects and potentially drags them Product: frameworks-kio Version: 5.86.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Open/save dialogs Assignee: kio-bugs-n...@kde.org Reporter: eduardo.c...@kdemail.net CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Many modern mice have extra buttons, some of them are used to navigate "back" and "forward", usually placed in the thumb region. When using KDE's open or save file dialog we are able to use these buttons to "back" and "forward" through our folder history. However, if we are hovering the mouse pointer above a an item (file or folder) at the dialog while we click these buttons, it actually select the items before doing the navigation. If we happen to me moving the mouse pointer even slightly, it actually starts a drag operation on the item that we were hovering. In fact, if the mouse has other extra unassigned buttons, any/all of them can be used to trigger this bug. STEPS TO REPRODUCE 1. Own a mouse with "back" and "forward" buttons 2. Open KWrite, open the "Open File" dialog 3. Click & hold with your "back" button over some file/folder shown at the dialog 4. Move your mouse while holding the "back" button OBSERVED RESULT You are now dragging them item while holding the "back" button EXPECTED RESULT It should have simply navigate "back" with the button down event (if you had a folder history) without initiating any unintended drag operation. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Graphics Platform: X11 ADDITIONAL INFORMATION In Dolphin, the behavior is correct. It can be taken as a reference behavior to be replicated in the open/save file dialogs. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431161] kwin_core: Compositing is not possible
https://bugs.kde.org/show_bug.cgi?id=431161 Eduardo changed: What|Removed |Added CC||eduardo.c...@kdemail.net --- Comment #3 from Eduardo --- I had similar issue seemingly out of nowhere. It was working fine for months, then suddenly I started getting "kwin_core: Compositing is not possible". I'm on Arch Linux, I updated some packages like I do everyday, but not kwin package itself. I don't know if the update is the root cause. > In order to be able to start Kwin properly with composition, I had to go > into ~/.config/kwinrc and set "OpenGLIsUnsafe" to "false" under [Compositing] Setting this to "false" fixed it for me. When I looked at it, it was set to "true", but I don't know how it was set when the system was working before. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 443351] New: Discover's "updates available" notification remains even after updating
https://bugs.kde.org/show_bug.cgi?id=443351 Bug ID: 443351 Summary: Discover's "updates available" notification remains even after updating Product: Discover Version: 5.22.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: eduardo.c...@kdemail.net CC: aleix...@kde.org Target Milestone: --- Created attachment 142168 --> https://bugs.kde.org/attachment.cgi?id=142168&action=edit "Updates available" notification being shown while Discover is up-to-date SUMMARY Discover's "updates available" notification remains even after updating. While running in the background, Discover realizes there are updates available and emits the "Updates available" notification to KDE's notification center. If the user runs Discover without clicking that notification and updates everything, the notification is not cleared. The user may look at it only hours later and will be fooled into thinking there are more updates to be applied when there is actually none. STEPS TO REPRODUCE 1. Wait for Discover to notify that it has updates available 2. Run Discover through other means, do not acknowledge the notification, don't click the "View Updates" button inside the notification. 3. Update everything inside Discover OBSERVED RESULT The notification will remain in the notification center, even though the system is up to date. EXPECTED RESULT The notification should have been cleared from the notification center. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.9-arch2-1 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION If the KDE notification framework doesn't provide a way for Discover to clear its own notification, then there is a bug in that framework and should be addressed there first. It should allow apps to clear their own notifications when they are no longer relevant. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443714] New: Selection doesn't change when hovering over the application categories with diagonal mouse movement
https://bugs.kde.org/show_bug.cgi?id=443714 Bug ID: 443714 Summary: Selection doesn't change when hovering over the application categories with diagonal mouse movement Product: plasmashell Version: 5.22.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: eduardo.c...@kdemail.net CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Selection doesn't change when hovering over the application categories with diagonal mouse movement STEPS TO REPRODUCE 1. Open Kickoff, you will see the application groups (categories) on the left panel. 2. Hover over some application groups with the mouse moving up/down. 3. Realize the hovered application group gets selected and its contents are displayed on the right panel. 4. Now hover while moving the mouse in up+right diagonal direction, in approximately 45 degree angle OBSERVED RESULT The category selection doesn't get updated, you are now hovering over another category but it is not selected EXPECTED RESULT The selection should get updated on hover, just like moving the mouse up/down SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.11-arch1-1 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kuserfeedback] [Bug 442296] "CMake Error: The INTERFACE_QT_MAJOR_VERSION property of "Qt5::Core" does not agree with the value of QT_MAJOR_VERSION already determined for KUserFeedbackQml /
https://bugs.kde.org/show_bug.cgi?id=442296 Eduardo changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||eduardo.c...@kdemail.net --- Comment #1 from Eduardo --- I'm getting the same error. Trying to build plasma-desktop, it fails when trying to build its dependency kuserfeedback with this error: -- Configuring done CMake Error: The INTERFACE_QT_MAJOR_VERSION property of "Qt5::Core" does not agree with the value of QT_MAJOR_VERSION already determined for "KUserFeedbackQml". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431446] Blinking panels and window contents not refreshing
https://bugs.kde.org/show_bug.cgi?id=431446 --- Comment #9 from Eduardo --- I have started using Plasma/5.21 branch for kwin, but that does not help much. The thing that is that it affects some random windows, probably those who are active at some unfortunate moment, but not everything. So, maybe, just maybe it's not the driver... Sometimes it's a panel, sometimes it's a window, last couple of times the content froze in Dolphin. I have a suspicion that it flickers sometimes because it "remembers" couple of frames and then shows them on screen. I have not got a flickering in Dolphin or other unfortunate apps which do not change content often. The good thing is that disabling / enabling composition gets rid of the issue until next time. The issue is not reproducible promptly, how to debug this? -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427123] New: CPU percentage overshoots 2e+19%
https://bugs.kde.org/show_bug.cgi?id=427123 Bug ID: 427123 Summary: CPU percentage overshoots 2e+19% Product: ksysguard Version: 5.18.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: eduardo.b...@hotmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 132011 --> https://bugs.kde.org/attachment.cgi?id=132011&action=edit Screenshot of the bug in CPU % usage plot SUMMARY Scale limit is not applied and the CPU % usage plot registers up to 2e+19% when it should obviously be limited to a 0-100% range. STEPS TO REPRODUCE Unknown. Random OBSERVED RESULT See attached screenshot EXPECTED RESULT It should not go over 100% SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 LTS KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420966] After tab-completing to a path (or typing a trailing slash) and hitting enter, Dolphin instead navigates to the first suggested subdirectory of that path
https://bugs.kde.org/show_bug.cgi?id=420966 Eduardo changed: What|Removed |Added CC||zl...@hotmail.com --- Comment #20 from Eduardo --- I too was suffering with the default "Dropdown List & Automatic" text completion behaviour. Changing it to "Dropdown list" with right-click on the address bar fixed all my problems. I'm a much happier person now! As a user I think the "Dropdown List & Automatic" being the default Text Completion method is not a good decision. If we type "/etc/" and quickly press ENTER, we expect it to go to the "/etc/" folder, not "/etc/acpi/" as is what happens with current default behviour. Alro, regarding the TAB usage: when using bash on a terminal, typing "cd /et", pressing TAB once, and pressing ENTER, it takes us to "/etc/" folder. With current Dolphin default behaviour, typing "/et" + TAB + ENTER would lead us unintuitivelly to "/etc/acpi/". Even the file picker KDialog present in many KDE Addps adopt the "Dropdown list" as the default, so Dolphin is also inconsistent with the rest of KDE environment by default. I think Dolphin should have a consistent behaviour to the terminal and other file managers by default. New users will feel way more welcomed to adopt it if the default behavior is what they are already expecting. And this desired and expected behaviour is already implemented, it is the "Dropdown List" text completion option. So here's my plea to change Dolphin's default text completion to "Dropdown List" in upcoming versions. Also, the option to change the behaviour is a little bit "hidden", I only found it after reading the comments in this bug report. I understand it is Dolphin's philosophy to not be so configurable, but since this IS configurable already, I think it deserves an entry under the "Configure Dolphin" screen, that's where users will go to look for available customizations. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441384] New: Dolphin's UI responsiveness becomes slow while counting items inside subfolders in an NTFS partition
https://bugs.kde.org/show_bug.cgi?id=441384 Bug ID: 441384 Summary: Dolphin's UI responsiveness becomes slow while counting items inside subfolders in an NTFS partition Product: dolphin Version: 21.08.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: details mode Assignee: dolphin-bugs-n...@kde.org Reporter: zl...@hotmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 140954 --> https://bugs.kde.org/attachment.cgi?id=140954&action=edit Script to create a big folder structure SUMMARY Dolphin's UI responsiveness becomes slow while counting items inside subfolders in an NTFS partition STEPS TO REPRODUCE 1. Place the attached script on a writeable NTFS partition and run it. It will create a folder named 'bigfolder' with 100 subfolders, and each of them with 100 empty files. 2. Open the newly created 'bigfolder' on Dolphin, making sure the "Details View Mode" is active (Ctrl+3). 3. As soon as Dolphin opens the folder, try to resize the Dolphin window. Try to move the scrollbar. Try to drag-select a bunch of subfolders. OBSERVED RESULT The above operations will all feel very slow and unresponsive: Dolphin window will refresh itself at very slow fps. After around 5-10 seconds, it becomes smoothly responsive again. Pressing F5 (refresh) will trigger the bug again. EXPECTED RESULT Dolphin's UI should remain perfectly responsive, even if there are background tasks running, such as counting items inside subfolders. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.22, Linux 5.11.0-27-generic (64-bit), Dolphin 21.08.0 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.13 ADDITIONAL INFORMATION On my system the bug happens only on NTFS partitions, even if running on a fast SSD. Dolphin is counting the number of items inside each of the subfolders to display in the "Size" column, which is great, but this task is slowing down the UI thread. I understand support for NTFS file system is not native to Linux, so it is expected that the actual file system operations should not work as fast. But I believe efforts can be made inside Dolphin to at least not lock the UI thread, making sure the potentially slow tasks are running in a background thread, keeping the UI responsive all the time. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441384] Dolphin's UI responsiveness becomes slow while counting items inside subfolders in an NTFS partition
https://bugs.kde.org/show_bug.cgi?id=441384 --- Comment #1 from Eduardo --- I tested this in other environments: Two completely different computers with KDE Neon 5.22 user edition up-to-date, the bug is triggered on both computers every time. However, I installed Arch Linux in one of those computers, and despite having the same Dolphin/Plasma/KDE Framework version, the bug doesn't happen under Arch Linux. The difference might be the ntfs-3g or FUSE version. This is what I have on each system: Common versions in both systems: # plasmashell --version plasmashell 5.22.4 # kf5-config --version Qt: 5.15.2 KDE Frameworks: 5.85.0 kf5-config: 1.0 # dolphin --version dolphin 21.08.0 Difference in versions: Under Neon (bug happens): root@Neon:~# fusermount -V fusermount3 version: 3.9.0 root@Neon:~# ntfs-3g --version ntfs-3g 2017.3.23AR.3 integrated FUSE 28 Under ArchLinux (bug doesn't happen): [root@ArchLinux ~]# fusermount -V fusermount version: 2.9.9 [root@ArchLinux ~]# ntfs-3g --version ntfs-3g 2017.3.23 external FUSE 29 So this may serve as clues to those who wish to investigate the bug. Or maybe it can be 'overlooked' until all distros are shipping non-bug-triggering ntfs-3g/FUSE versions. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 434199] SmsDie timeout, client "/usr/bin/kwalletd5" "/usr/lib64/libexec/kdeconnectd"
https://bugs.kde.org/show_bug.cgi?id=434199 Eduardo changed: What|Removed |Added CC||zl...@hotmail.com --- Comment #1 from Eduardo --- Created attachment 141142 --> https://bugs.kde.org/attachment.cgi?id=141142&action=edit timeout log -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 434199] SmsDie timeout, client "/usr/bin/kwalletd5" "/usr/lib64/libexec/kdeconnectd"
https://bugs.kde.org/show_bug.cgi?id=434199 --- Comment #2 from Eduardo --- I'm having the same symptom. However I only have the log entry about 'kdeconnectd'. My kwalletd5 seems to be dying just fine. I have attached my journalctl logs filtered by 'kdeconnectd'. The log starts at the moment I have requested to log out, and ends after it effectively logs out. There is a 8 second hole in the whole unfiltered log just before the 'SmsDie timeout' line. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 434199] SmsDie timeout, client "/usr/bin/kwalletd5" "/usr/lib64/libexec/kdeconnectd"
https://bugs.kde.org/show_bug.cgi?id=434199 --- Comment #3 from Eduardo --- There is a duplicate dealing about the kdeconnectd problem: https://bugs.kde.org/show_bug.cgi?id=432643 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 434199] SmsDie timeout, client "/usr/bin/kwalletd5" "/usr/lib64/libexec/kdeconnectd"
https://bugs.kde.org/show_bug.cgi?id=434199 Eduardo changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #4 from Eduardo --- And a duplicate dealing about the kwalletd5 problem: https://bugs.kde.org/show_bug.cgi?id=428903 *** This bug has been marked as a duplicate of bug 428903 *** -- You are receiving this mail because: You are watching all bug changes.
