Solved KDE's Konsole is laggy after upgrade from 6.4.5 to 6.6.4

loveydovey

loveydovey

So weird. After upgrading KDE from 6.4.5 to 6.6.4 Konsole (terminal app) became so laggy all of a sudden in strange ways.

It's not laggy when you just open a tab, but after you run anything, like top for example, and get back into the shell, typing becomes super laggy for a long while...then kind of improves.

Anyone seen this? Anyone know how to fix this? It's unusable, I'm going back to 6.4.5. I know this isn't a KDE forum, but maybe, just maybe someone has any pointers please. Is it just me, does anyone else on 6.6.4 have any Konsole laggy typing issues? Thanks.
 
I'm also on Wayland. I upgrade one more time, still the same problem arises. Xterm, alacrity work good (those that don't use GPU for rendering)... wezterm works good (uses GPU for rendering)... So something screwy happened with KDE's Konsole.
 
loveydovey said:
I'm also on Wayland. I upgrade one more time, still the same problem arises. Xterm, alacrity work good (those that don't use GPU for rendering)... wezterm works good (uses GPU for rendering)... So something screwy happened with KDE's Konsole.
Click to expand...
Just to say something, these are Konsole's config files and dirs:

"$HOME/.config/konsolerc"
"$HOME/.local/share/konsole"
"$HOME/.cache/konsole"

Maybe you can try pkg delete konsole, then remove the config (better, make copies with other names so you can recover them), then reinstall the package.

Take the usual precautions not to make a bigger mess.
 
AlfredoLlaquet said:
Just to say something, these are Konsole's config files and dirs:

"$HOME/.config/konsolerc"
"$HOME/.local/share/konsole"
"$HOME/.cache/konsole"

Maybe you can try pkg delete konsole, then remove the config (better, make copies with other names so you can recover them), then reinstall the package.

Take the usual precautions not to make a bigger mess.
Click to expand...
All this didn't help, same problem afterwards. This is sort of bad because KDE is now bundled with new FreeBSD installs - and then we get this laggy stuff in Konsole??
 
Ok, I downgraded just the Konsole package by compiling an earlier Konsole version 25.08.1 from the earlier quarterly (2025Q4), and it works fine with KDE from the latest quarterly (2026Q2).

This is a workaround, not a solution. Maybe need to try to compile the latest Konsole version to see if there was a bug or something.
 
Lo and behold, I compiled the very absolute latest Konsole from source (using 'main' branch of ports), and it seems they fixed the laggy bug. The latest quarterly version 26.04.0 is buggy with laggy typing, the latest latest version 26.04.1 is fixed.

SirDice Crivens cracauer@ I have a question. Quarterly cutoffs are nice, but what if the quarterly cutoff cuts a version of a popular application in a buggy state? Is there a special mechanism to push a fix back into quarterly branches? It's just a little counterintuitive to cutoff applications in buggy states.
 
loveydovey said:
Quarterly cutoffs are nice, but what if the quarterly cutoff cuts a version of a popular application in a buggy state?
Click to expand...
Quarterly basically accepts security fixes and build fixes (as of base updates) only. These are possible without explicit approval of portmgr / pkgmgr / secteam. This is called "blanket approval" and does NOT cover anything others.

So if you really want it to be fixed on quarterly without waiting for next quarterly, you need to file a bug at Bugzilla with "merge quarterly" flag as "?" if you don't have patch to submit.

Ports maintainers are basically on latest, so cannot know whether or not later commits to other ports after the commit by themselves causes issues or not unless anyone "officially" or directly report the issue.

And currently the only official way to request fixes WITHOUT PATCH can be done via Bugzilla. Official GitHub mirror does NOT enabled "issues" functionalities (pull request that need codes to merge alone is activated), and Phabricator is for code reviews.
 
I'm glad you, loveydovey, could fix your problem. Personally, though, I find so much negativity against the FreeBSD ecosystem very undeserved. This is a FOSS project of an extreme complexity. Bugs are bound to exist, as they do in proprietary projects, but look at how many resources you had to find a workaround: the forum(s), downgrading, compiling from source... And you still had bugzilla to try. I like you as a user of the forum(s), loveydovey, you encouraged me to quit coffee (which I did), if I'm not misremembering, but I think it's a good thing to be more appreciative. Nothing is perfect.
 
You must log in or register to reply here.
Back
Top