I have noticed for a while now that on TW and recently on Leap 42.2 alpha that some things are slower than they used to be . For example emptying the Wastebin/Trashcan after a right click on it and selecting empty the window border appears but there is a very noticeable delay before the options appear in the window and allow you to actually do the function. In Dolphin the same happens when trying to delete files but only on the first time you do a delete after starting Dolphin. Also it seems to me that both Firefox and Thunderbird are noticeably slower to open than they used to be.
Is this something anyone else has noticed? Is this a bug somewhere perhaps in Plasma 5?
I haven’t noticed something like that neither on my 13.2 system (with latest Plasma5 from additional repos), nor in a Tumbleweed VM nor the Krypton LiveCD (which is Tumbleweed with the latest unstable KDE packages).
What happens if you run the affected applications in Konsole?
Do you get some error messages?
Opening up Firefox has become exceedingly slow for me in the recent past. It takes about 4s just for the window to open up and then about another 10s before it becomes responsive to any kind of input. This sloth like behaviour is beginning to really annoy me … funny how a measly 14s can really grate on you, but it does!
Anyway, and while I haven’t checked yet myself, my first suspicion would be with one of the extensions being the culprit for the delay.
FWIW, I haven’t perceived a noticeable change with TB … though I find that I"m opening it much less often these days (as I use my phone more for quick checking of email)
QXcbConnection: XCB error: 3 (BadWindow), sequence: 3092, resource id: 37748838, major code: 40 (TranslateCoords), minor code: 0
but not until the delete window closes.
I’ll try firefox with all the plugins disabled and see if it makes any difference. Dont know how I can see what happens with the waste bin from a console though.
My programs function normally, but since the last few updates in Tumbleweed using Plasma workspace, the Cursor Themes settings won’t open (take forever) and the same with the SDDM settings in the start-up module. The CPU temp rises to over 80C every time I try to open these from the system-settings control panel. Other than that everything runs as expected.
Is there anyone might know a fix for this?
I’m using an ACER laptop with i7 processor and 16GB RAM.
ah, OK… did that, but that just kills systemsetting5 which gets rid of the temperature issue, but then I still can’t get in and change my cursor or open the SDDM settings… I still don’t know why it’s playing up like that
Try a different user to see if it is a config problem. If problem follows to different user force reinstall systemsettings5 maybe. Note not sure if systemsettings5 is in own rpm or part of another package. can check provides in Yast software management search to find correct package
I checked last night (by disabling all extensions) and, indeed, the suspicion was correct … perhaps on the weekend I’ll narrow down which one is causing the lethargy.
I don’t think this would be caused by a broken config file, but it’s probably still a good idea to try on a fresh user account (as gogalthorp suggested).
Those two modules use QML though (which relies on OpenGL), so it might be a graphics driver problem (or related to the graphics settings, compositing e.g.).
So I would investigate into this direction too.
May be the OP’s problem too, at least the BadWindow error may point to Xorg/graphics related issues.
JFYI, you can edit the settings manually with a text editor too.
The mouse cursor is set in ~/.config/kcminputrc (cursorTheme=xxx), the sddm settings are in /etc/sddm.conf.
Or try uninstalling xf86-video-intel completely and try with the generic modesetting driver (shouldn’t really make a difference with OpenGL though, as that is provided by Mesa).
I did that, Wolfi, and it made no difference either. In fact, I’ve tried every recommendation given on this thread and it still remains the same. Every time I click on cursors or SDDM themes in the settings, it locks into trying to open it, begins roasting my CPU up to 90C and then I have to kill systemsettings5 for it to settle down again . Everything else under settings works perfectly. I have no other issues running anything within Plasma. Weird, eh? Also, I have GNOME 3.20 on the same machine and not a single issue with that either. Reinstalling systemsettings5 did nothing either.
Though at least the SDDM module only reads/writes system-wide config files anyway.
Reinstalling systemsettings5 did nothing either.
Of course not.
systemsettings5 is just a shell to list and embed the configuration modules.
The actual modules are part of plasma5-desktop (in this case).
But reinstalling the software normally doesn’t solve any problems (unless the reason is that installed files got deleted or corrupted, which should not happen normally unless your harddrive is dying).
Also, I have GNOME 3.20 on the same machine and not a single issue with that either. Reinstalling systemsettings5 did nothing either.