Page MenuHomeFreeBSD

sysutils/consolekit2: enable drm/evdev, fix drm device recognition
Needs ReviewPublic

Authored by greg_unrelenting.technology on Sat, Jan 5, 1:55 PM.

Details

Reviewers
tcberner
Group Reviewers
gnome
Summary

This makes it possible to launch a Wayland compositor using ConsoleKit2 as the session controller.

Tested with a customized Weston. But this should make KDE's kwin_wayland work I think. (It supports CK2 already)

Diff Detail

Repository
rP FreeBSD ports repository
Lint
Lint Skipped
Unit
Unit Tests Skipped

Event Timeline

Cool, I'll try if I manage to start it.

+ fix re-plugging devices by checking if the found device is still alive

Submitted upstream, but the project isn't very active, there are three open PRs and they got no response

oh, it also didn't enable termios raw mode. That was causing Weston to crash when pressing Enter :D Fixed.

kwm added a subscriber: kwm.Sat, Jan 5, 8:36 PM

This seems to look good, but I don't have a setup to test this.

Lets poke the KDE people :-)

looks like it would need a revision bump aswell.

Tryign to ck-launch-session /usr/local/bin/startplasmacompositor leads to a segfault ck.

Tryign to ck-launch-session /usr/local/bin/startplasmacompositor leads to a segfault ck.

huh. So I tried it, ck works fine, KWin however wasn't actually ported to FreeBSD…

I made an attempt: https://reviews.freebsd.org/differential/diff/52600/ — it starts up, but

  • input devices aren't attached — I'm not seeing anywhere in the code where it would enumerate subsystem=input, how does KDE attach input devices?! o_0
  • doesn't like my GPU — after starting, there's the splash screen, then black screen for a long time (and amdgpu spam in dmesg), but after a couple minutes the lockscreen appeared! :)