/usr/local/lib/libxmlb.so.2: version LIBXMLB_0.1.0 required by /usr/local/lib/libappstream.so.4 not defined
On 18/08/2023 19:32, Thomas Covert wrote: FreeBSD 14 Aplha1 Are your packages from /latest/, or from /quarterly/? You will find one of those two words from running this command: pkg -vv | grep url FreeBSD as my main OS Always FreeBSD-CURRENT? Or did you use 13.2-RELEASE-p2 before this upgrade? file:///usr/local/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/Kickoff.qml:19:1: plugin cannot be loaded for module "org.kde.plasma.private.kicker": Cannot load library /usr/local/lib/qt5/qml/org/kde/plasma/private/kicker/libkickerplugin.so: (/usr/local/lib/libxmlb.so.2: version LIBXMLB_0.1.0 required by /usr/local/lib/libappstream.so.4 not defined) Which version of libxmlb is installed? % pkg provides /usr/local/lib/libxmlb.so.2 Name : libxmlb-0.3.11 Comment : Library to help create and query binary XML blobs Repo : FreeBSD Filename: usr/local/lib/libxmlb.so.2.0.0 usr/local/lib/libxmlb.so.2 % pkg iinfo libxmlb libxmlb-0.3.11 %
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/k...@freebsd.org.html Port| Current version | New version +-+ devel/libphonenumber| 8.13.18 | v8.13.19 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout!
[Bug 271571] x11-wm/plasma5-kwin: fails to start nested under Wayland (wlroots)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271571
--- Comment #4 from Jan Beich ---
(In reply to Jan Beich from comment #3)
Beware, until bug 253277 is fixed running multiple Xwayland instances (e.g.,
rootless + rootful, rootless parent + rootless child) is fragile. I use the
following to help recover
$ cat ~/.sway/config
[...]
# X11 sockets (real + pseudo-abstract) maybe overwritten by a compositor inside
jail
exec mkdir -p /tmp/.X11-unix/backup && ln -f /tmp/.X11-unix/X${DISPLAY#:}
/tmp/.X11-unix/X${DISPLAY#:}_ /tmp/.X11-unix/backup
For example,
$ glxgears
Error: couldn't open display :0
$ ln -f /tmp/.X11-unix/backup/* /tmp/.X11-unix/
$ glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
301 frames in 5.0 seconds = 60.000 FPS
^C
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 265505] x11/plasma5-plasma: Wayland session doesn't work since Plasma 5.22
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265505 --- Comment #8 from Gleb Popov --- (In reply to Jan Beich from comment #6) Thanks for working on this, Jan! I'm poking ConsoleKit and SDDM right now. Once I'm done and if you want to play with SDDM+Wayland I can prepare a flavorization patch. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 271571] x11-wm/plasma5-kwin: fails to start nested under Wayland (wlroots)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271571 --- Comment #3 from Jan Beich --- Workaround: use KWin's X11 backend by hiding Wayland connection and switching X11 connection to a rootful Xwayland instance. # Replace kwin_wayland with startplasma-wayland for something easier to use $ env -u WAYLAND_DISPLAY DISPLAY=:$(Xwayland -retro -geometry 1024x768 -terminate -displayfd 1 2>/dev/null &) kwin_wayland Implementation details: * -retro: classic Xwayland background to distinguish from KWin's black background * -geometry 1024x768: to match KWin's default if kwin_wayland is started by startplasma-wayland * -terminate: exit Xwayland immediately after KWin exits * -displayfd 1: output X11 connection path (dpy) to stdout -- You are receiving this mail because: You are the assignee for the bug.
