Solved FreeBSD 14.2 amd64 April 2025 quarterly update KDE5 -> KDE6 issues

hexaitos said:
does this mean compilation will be re-tried at a later time or does it just mean those packages simply won't be in Quarterly until the next Quarterly release?
Click to expand...
No, you won't have to wait for the next quarterly release. Hopefully somebody will fix that build error with webkit2-gtk, then the dependencies can be met again. New builds are done quite regularly.

hexaitos said:
Should I switch back to Quarterly once the packages have successfully built or would staying on Latest also be fine?
Click to expand...
That's up to you. I personally like having the latest packages, but having a front-row seat on everything new also means things can sometimes break. I'm fine with that, as I'm experienced enough to quickly fix those issues (I build my own repositories).
 
hexaitos said:
[...] but I am fairly new to FreeBSD [...]
Should I switch back to Quarterly once the packages have successfully built or would staying on Latest also be fine?
Click to expand...
As the quarterly branch (2025Q2) is just new as it has just been branched off from the main branch, it is essentially just a copy of what the latest branch was at the moment 2025Q2 came into existance. Therefore packages of latest and quarterly are not that different now. However, this difference increases over time as the Q2 quarter advances; for more about that: here.

Note that the release scheme of supported ports (and its derived packages) differs in essential ways from the release scheme and support model of the FreeBSD base-install: LTS support and version clarifications
 
Last edited:
This is a blunder, Quarterly shouldn't get broken pushes for packages, it should be reliable and stable. I paid attention though and saw that it was uninstalling 13 packages, so I knew it was broken.
 
thedaemon said:
Quarterly shouldn't get broken pushes for packages, it should be reliable and stable.
Click to expand...
There could be some exceptions.
For example, if any of the ports that have security fixes without workarounds, it would be pushed if it's critical or severe.
But in some cases, this breaks other ports depending on it, but there should be no option not to push it to quarterly, thus, something could be broken until the causes are addressed and fixed.
 
Has anyone experienced frequent KWin crashes on the latest KDE (6.3.3 x11)? The KDE taskbar briefly flickers fully black or dark-grey, then white without transparency, then becomes semi-transparent white again, the whole desktop sometimes flickers as well. After this, it displays a "sad Mac" notification icon
1744042968542.png
, clicking on it opens this:

1744042818726.png

This crash is reproduced reliably by placing the mouse cursor exactly at the top left corner, but can happen in other situations as well.
 
siealex said:
Has anyone experienced frequent KWin crashes on the latest KDE (6.3.3 x11)? The KDE taskbar briefly flickers fully black or dark-grey, then white without transparency, then becomes semi-transparent white again, the whole desktop sometimes flickers as well. After this, it displays a "sad Mac" notification icon View attachment 22184, clicking on it opens this:

View attachment 22183
This crash is reproduced reliably by placing the mouse cursor exactly at the top left corner, but can happen in other situations as well.
Click to expand...
Not sure it's related or not, but are you using firefox?

I had crashes of compiz when my mouse cursor is over any of the tabs of firefox, not always but very often.

This started happening when firefox started to show previews of tabs.

This could be worked around by disabling preview, using about:config.
2 variables, browser.tabs.hoverPreview.enabled and browser.tabs.hoverPreview.showThumbnails needed to be disabled (made false). This makes something like alt-text to be shown instead of preview.

If you don't using firefox but something like previews are shown when you placed your mouse cursor at top-left, the preview could cause crash, if the same or looking-alike codes as firefox are used.
 
thedaemon said:
This is a blunder, Quarterly shouldn't get broken pushes for packages, it should be reliable and stable. I paid attention though and saw that it was uninstalling 13 packages, so I knew it was broken.
Click to expand...
I paid attention too, and noticed something was odd so I tried pkg upgrade on my test PC which is on the default repository. The Xfce environment was broken so I tried a clean install with the default repository and noticed that the xfce and xfce4-goodies meta-packages are missing, although lots of other xfce4 packages are present. I'm wondering whether to wait until they appear before doing any pkg upgrades on my main PC.
 
Useradd said:
I paid attention too, and noticed something was odd so I tried pkg upgrade on my test PC which is on the default repository. The Xfce environment was broken so I tried a clean install with the default repository and noticed that the xfce and xfce4-goodies meta-packages are missing, although lots of other xfce4 packages are present. I'm wondering whether to wait until they appear before doing any pkg upgrades on my main PC.
Click to expand...
I actually did a zfs snapshot and tested it on my main machine then restored my zfs snapshot. I wanted to test snapshot restoration, worked perfectly! Just do a pkg update every day until it pulls new info and check to see if it's been fixed?
 
thedaemon said:
I actually did a zfs snapshot and tested it on my main machine then restored my zfs snapshot. I wanted to test snapshot restoration, worked perfectly! Just do a pkg update every day until it pulls new info and check to see if it's been fixed?
Click to expand...
I use ufs, so I don't think I can do snapshots. I'll just keep checking to see if the missing packages have returned to the default repository. I don't use quarterly or latest on my test PC because I want stability. My main PC uses a custom repository for the amdgpu driver only, but my test PC has a nvidia card and doesn't need one.
 
Bah it's all a mess.

krunner now crashes, there seem to be a load of old kf5 packages left over. But at the same time many of them seem to be still in use.

Is there a simple way to to uninstall kde5 or plasma5-plasma and reinstall kde6?
 
Erichans said:
This may help: x11/kde6 - Notes from updating.
Click to expand...

Unfortunately it doesn't help. None of these metapackages are installed now so I can't uninstall them.

I went through all of the plasma5 packages and either installed the plasma6 version (which uninstalled the plasma5 one) or when there wasn't a plasma6 verison just removed the package.

I still have a lot of kf5 packages. As always "pkg autoremove" wants to remove over 500 packages so it's no use either.
 
I messed around for hours with kf5-kf6 and plasma installs and uninstalls and still since Februrary sometime
www/falkon at best, shows a blank falkon:restore page which only appears for about ten seconds, and usually, nothing shows at all. Toyed around with
gdb -ex=r --args /usr/local/bin/falkon www.google.com and
gdb /usr/local/lib/qt6/libQt6WebEngineCore.so.8.3 but no way forward that I know of... running the browser from a thick jail??? finding out how to setup a poudriere build of it including how long it would take beforehand???? Was/is as serious an issue here as when
www/seamonkey was dropped from the ports tree... hoping this or another KDE thread divulges a fix or workaound sometime ...
 
I have this same issue. I did pkg update and pkg upgrade last week. Now 2 days ago. I boot my computer to do some work and bam... got the window that something went wrong window for gnome. I had to use keys Ctrl + Alt+ f1 to get into the terminal. My computer boots fine but gnome just can't run. However, if I run the command
startx It then loads in a old looking GUI interface.
 
You must log in or register to reply here.
Back
Top