[Bug 265505] x11/plasma5-plasma: Wayland session doesn't work since Plasma 5.22
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Aug 19 01:52:52 BST 2023
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265505
--- Comment #4 from commit-hook at FreeBSD.org ---
A commit in branch 2023Q3 references this bug:
URL:
https://cgit.FreeBSD.org/ports/commit/?id=40fe2d53bacf88e2c48282e62445f15e4a3d16b7
commit 40fe2d53bacf88e2c48282e62445f15e4a3d16b7
Author: Jessica Clarke <jrtc27 at jrtc27.com>
AuthorDate: 2022-11-19 02:36:07 +0000
Commit: Jan Beich <jbeich at FreeBSD.org>
CommitDate: 2023-08-19 00:51:37 +0000
x11/plasma5-plasma-workspace: Fix XDG_CONFIG_DIRS for Wayland
Since Plasma 5.22, setupPlasmaEnvironment adds to XDG_CONFIG_DIRS, with
a fallback for the XDG-mandated /etc/xdg default. When using X11, this
is ok, as runStartupConfig gets called before setupPlasmaEnvironment,
and so the latter uses our modified value. However, when using Wayland,
they are called in the opposite order, and so runStartupConfig sees the
variable is already set and doesn't inject our modified default. Fix
this by changing setupPlasmaEnvironment's default value instead so it's
only set in one place. This approach also matches how other ports get
patched for our non-conforming environment.
Without this, the splash screen shows but plasmashell is never started
(nor any other autostart programs), eventually timing out and fading to
a black screen.
PR: 265505
Obtained from: CheriBSD
Approved by: maintainer timeout (3 months)
(cherry picked from commit f06a1b44e85b9788c0e1ed718eca4146f102057f)
x11/plasma5-plasma-workspace/Makefile | 6 ++++-
.../files/patch-setup_xdg_environment | 28 +++++++---------------
2 files changed, 13 insertions(+), 21 deletions(-)
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the kde-freebsd
mailing list