Bug 295761 - sysutils/consolekit2 causes X11 to fail to start
Summary: sysutils/consolekit2 causes X11 to fail to start
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-desktop (Team)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-06-01 00:21 UTC by rkoberman
Modified: 2026-06-03 06:18 UTC (History)
1 user (show)

See Also:
arrowd: maintainer-feedback+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description rkoberman 2026-06-01 00:21:03 UTC
After updating consolekit2 to 2.0, X exit startup with some very odd messages:
scfb trace: orobe start
scfb trace: probe start
/home/oberman/.xinitrc: setenv: not found
/home/oberman/.xinitrc: setenv: not found
/home/oberman/.xinitrc: setenv: not found

** (ck-launch-session:7516): WARNING **: 12:23:54.264: Unknown option --exit-with-session
xinit: connectiob to X server lost

Since I have modeset, I don't understand the scfb probe, but I may just have not noticed.

Here is my .xinitrc:
xset fp rehash
#sudo /bin/rmdir /media/*
setenv XDG_CONFIG_HOME $HOME/.config
setenv XDG_CACHE_HOME $HOME/.cache
setenv XDG_DATA_HOME $HOME/.local/share

exec ck-launch-session dbus-launch --exit-with-session mate-session

Dropping back to the old version (1.2.6_6) of condolekit2 fixes the problem.No errors or unexpected entries in Xorg.0.log. If someone thinks it might be helpful, I can add it to the ticket.
Comment 1 Gleb Popov freebsd_committer freebsd_triage 2026-06-02 13:22:15 UTC
setenv is a csh built-in command. Startup scripts and .xinitrc are usually sourced by /bin/sh. Replace setenv's with export or even better remove them altogether as they are useless.
Comment 2 rkoberman 2026-06-03 06:18:57 UTC
Tried removing them. Still dies taking X with it and the ck-launch-session error is now the only error.