Giters

MrGlockenspiel / activate-linux

The "Activate Windows" watermark ported to Linux

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

KWin running, no running compositor detected

grahamperrin opened this issue · comments

commented

#109 (comment)

… EWMH compliant compositor …

Here, with KWin (with KDE Plasma):

% ./activate-bsd -t "Activate FreeBSD" -m "90 days remaining"
No running compositor detected. Program may not work as intended. 
^C
% uname -aKU
FreeBSD mowa219-gjp4-8570p-freebsd 14.0-CURRENT FreeBSD 14.0-CURRENT #12 main-n255769-f16e38162c7-dirty: Tue May 24 11:48:57 BST 2022     root@mowa219-gjp4-8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 1400059 1400059
%

Please, is this an issue with detection on FreeBSD?

Or, am I truly without a compliant compositor, and if so (apologies for the noise) how can I tell?

According to https://en.wikipedia.org/wiki/Comparison_of_X_window_managers#Features:

  • KWin is EWMH-compliant.
commented 
Operating System: FreeBSD 14.0
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.2
Kernel Version: 14.0-CURRENT (64-bit)
Graphics Platform: X11
Memory: 15.9 GiB of RAM
Graphics Processor: llvmpipe

Do either of these screenshots help?

image

		…
	VkSurfaceCapabilitiesKHR:
	-------------------------
		…
		supportedCompositeAlpha: count = 2
			COMPOSITE_ALPHA_OPAQUE_BIT_KHR
			COMPOSITE_ALPHA_INHERIT_BIT_KHR
		…

image

name of display:    :0
version number:    11.0
vendor string:    The X.Org Foundation
vendor release number:    12014000
X.Org version: 1.20.14
…
keycode range:    minimum 8, maximum 255
focus:  window 0xaa0000a, revert to PointerRoot
number of extensions:    28
    BIG-REQUESTS
    Composite
    …
commented

… Or, am I truly without a compliant compositor, and if so (apologies for the noise) how can I tell? …

https://old.reddit.com/r/freebsd/comments/uyscch/-/iaavjnv/?context=1 someone provided a screenshot to prove that transparency can be effective with KWin on FreeBSD in a VirtualBox guest.

So, presumably, not a problem with activate-linux.

I'll close this issue, and try to figure out why I'm without transparency on real hardware …

commented

The issue was transient, resolved by a simple restart of the operating system. Apologies for the noise.

Working:

image

If the underlying issue recurs, I have (from IRC) a hint to see:

~/.xsession-errors, if it exists.

It does not, at the time of writing.