Summary: | Slow taskbar | ||
---|---|---|---|
Product: | [Plasma] Breeze | Reporter: | Dav84 <dav00m> |
Component: | gtk theme | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | agrinev98, nate, sitter, tagwerk19, uhhadd |
Priority: | NOR | Keywords: | qt6 |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
See Also: |
https://bugs.kde.org/show_bug.cgi?id=482082 https://bugs.kde.org/show_bug.cgi?id=481870 |
||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Dav84
2024-03-01 20:20:25 UTC
It could be Bug 481870 or Bug 482082. The two both talk about delays at logon but don't seem connected.... (In reply to tagwerk19 from comment #1) > Podría ser el error 481870 o el error 482082 . Los dos hablan de > retrasos en el inicio de sesión pero no parecen conectados... In my case I rule out Bluetooth since my PC does not have it integrated, I use it via USB, it is not a laptop, it is a desktop PC... and I also rule out the welcome screen since it is the first thing I have disabled the welcome screen and as I say in plasma 5... it never happens to me, the taskbar was ready when the desktop loaded now there is a quite obnoxious or annoying delay and until it loads I can't use anything... Probably related, maybe the same thing, maybe something different. We have a number of "slow login" bugs in Plasma 6. Can you try some of the debugging steps Arjen Hiemstra suggested in 482082? (In reply to Dav84 from comment #2) > ... In my case I rule out Bluetooth since my PC does not have it integrated ... It's no problem, I don't have it either ... ... but I'm guessing something thinks I do 8-} Mind you, it's actually the absence of bluetooth that causes trouble. (In reply to Harald Sitter from comment #5) > Eso sí, en realidad es la ausencia de bluetooth lo que causa problemas. I don't think so, this computer is new, it has been used for 3 months before upgrading to Plasma 6, it was with Plasma 5 and zero problems, in fact, the Bluetooth was never connected all the time since it is via non-integrated USB and I only connect it when I need it and Most of the time I use KDE connect to transfer files between my devices and it never gave me problems with Plasma 5 and it seems illogical to me that Bluetooth interferes with something as basic in the interface as the taskbar. kdeconnect uses bluetooth. kdeconnect has a systray plugin. the systray is part of the panel. the panel is part of plasma. -> when kdeconnect talks to bluetooth that impacts all of plasma. (In reply to Harald Sitter from comment #7) > kdeconnect uses bluetooth. kdeconnect has a systray plugin. the systray is > part of the panel. the panel is part of plasma. -> when kdeconnect talks to > bluetooth that impacts all of plasma. So explain to me to understand why in Plasma 5 I did not have Bluetooth connected to any USB all the time and both KDE connect and the taskbar worked without problems, now you tell me that the solution in Plasma 6 is to have the Bluetooth device connected all the time. How long does it take for the bar to appear and not take 49 seconds in my case to appear and be able to use the PC? Because the code is different. (In reply to Harald Sitter from comment #9) > Porque el código es diferente. Yes, man, although I'm not a developer... I understand a little about the subject and I don't write it upset, rather with a smile on my face, something like that really seems absurd to me, but I'll have to wash my mouth with soap for saying this, but I don't even think Windows. What would give me that problem, so the placebo is to connect the tp-link device to the PC and then the famous taskbar will not make me wait 49 seconds to be able to use my PC? (In reply to Dav84 from comment #10) > (In reply to Harald Sitter from comment #9) > > Porque el código es diferente. > > Yes, man, although I'm not a developer... I understand a little about the > subject and I don't write it upset, rather with a smile on my face, > something like that really seems absurd to me, but I'll have to wash my > mouth with soap for saying this, but I don't even think Windows. What would > give me that problem, so the placebo is to connect the tp-link device to the > PC and then the famous taskbar will not make me wait 49 seconds to be able > to use my PC? You are right, I just did the test and if the bar enters as before, now this cannot be modified so that it does not depend on one of the other and the other query is how I activate again a single click to open files or folders I look for it in settings from Dolphin and the option does not appear, a user told me that there is an option at least because he is wrong or still using Plasma 5 or that I cannot find it. (In reply to Harald Sitter from comment #5) > Mind you, it's actually the absence of bluetooth that causes trouble. Seems true... 8-] There should really be an obvious way of disabling kdeconnect, time for a shout out for Bug 417615. (In reply to Dav84 from comment #11) > ... how I activate again a single click to open files or folders > I look for it in settings from Dolphin and the option does not appear ... You probably want System Settings > Workspace > General Behavior and there's an option for "Clicking on files of folders" with a single click "Selects them" or "Opens them" *** This bug has been marked as a duplicate of bug 481870 *** (In reply to tagwerk19 from comment #13) > (In reply to Dav84 from comment #11) > > ... how I activate again a single click to open files or folders > > I look for it in settings from Dolphin and the option does not appear ... > You probably want > System Settings > Workspace > General Behavior > and there's an option for "Clicking on files of folders" with a single click > "Selects them" or "Opens them" Thanks, it was previously in the Dolphin configuration or at least I activated it from there. The bug has been resolved... in the taskbar that took a long time to appear at the beginning of the desktop and I do not have the need to always have the Wi-Fi and Bluetooth connected to a USB port thanks to the developers, I hope to those who had the same problem has been solved. |