Solved Sddm fbsd13.1 dont load

Hi,
I have installed FreeBSD and KDE5 but sddm doesn't load at all when startx as root I go directly to plasma desktop Wayland but as user I get an old graphic environment whit xterm no sddm no x11 session, what I'm I missing?
 
SDDM is a display manager, it's not supposed to start with startx. You start an X session with startx OR through a display manager like SDDM.

 
in rc conf both are enable=yes but sddm dont work even if i comment xdm entry.

Code:
hostname=""
wlans_iwm0="wlan0"
ifconfig_wlan0="WPA DHCP"
sshd_enable="YES"
# Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable
dumpdev="AUTO"
zfs_enable="YES"
dbus_enable="YES"
hald_enable="YES"
#xdm_enable="YES"



# Added by auto-admin from desktop-installer
powerd_enable="YES"
# End auto-admin addition
# Added by auto-admin from desktop-installer
moused_port=/dev/psm0
# End auto-admin addition
# Added by auto-admin from desktop-installer
moused_enable="YES"
# End auto-admin addition
# Added by auto-admin from desktop-installer
ntpdate_enable="YES"
# End auto-admin addition
# Added by auto-admin from desktop-installer
ntpdate_flags="-u pool.ntp.org"
# End auto-admin addition
# Added by auto-admin from desktop-installer
ntpd_enable="YES"
# End auto-admin addition
# Added by auto-admin from desktop-installer
nfs_client_enable="YES"
# End auto-admin addition
# Added by auto-admin from desktop-installer
rpc_statd_enable="YES"
# End auto-admin addition
# Added by auto-admin from desktop-installer
rpc_lockd_enable="YES"
# End auto-admin addition
# Added by /usr/local/sbin/auto-autofs-nfs-setup
autofs_enable="YES"
# Added by auto-admin from desktop-installer
devd_enable="YES"
# End auto-admin addition
# Added by auto-admin from desktop-installer
devfs_system_ruleset="system"
# End auto-admin addition
# Added by auto-admin from /usr/local/sbin/auto-install-linux_base
linux_enable="YES"
# End auto-admin addition
kld_list="fusefs nvidia-modeset"
firewall_enable="YES"
firewall_type="client"
firewall_client_net=""
firewall_script="/etc/ipfw.rules"
# Added by auto-admin from desktop-instaler
sddm_enable="YES"
# End auto-admin addition
# Added by auto-admin from desktop-installer
cupsd_enable="YES"
# End auto-admin addition
 
it seem that i have no config file in the system for sddm


whereis sddm
sddm: /usr/local/bin/sddm /usr/local/share/man/man1/sddm.1.gz /usr/ports/x11/sddm


and /var/lib/sddm is empty


root@:/var/lib/sddm # ls
root@:/var/lib/sddm #
 
Add to /etc/rc.conf :
sddm_enable="YES"
xdm_enable="NO"

Check&verify,
/etc/ttys
for the rc.conf it make no difference, I did what you told me to do.
here is the /etc/ttys
Code:
#
# $FreeBSD$
#    @(#)ttys    5.1 (Berkeley) 4/17/89
#
# This file specifies various information about terminals on the system.
# It is used by several different programs.  Common entries for the
# various columns include:
#
# name  The name of the terminal device.
#
# getty The program to start running on the terminal.  Typically a
#       getty program, as the name implies.  Other common entries
#       include none, when no getty is needed, and xdm, to start the
#       X Window System.
#
# type The initial terminal type for this port.  For hardwired
#      terminal lines, this will contain the type of terminal used.
#      For virtual consoles, the correct type is typically xterm.
#      Other common values include dialup for incoming modem ports, and
#      unknown when the terminal type cannot be predetermined.
#
# status Must be on or off.  If on, init will run the getty program on
#        the specified port.  If the word "secure" appears, this tty
#        allows root login.
#
# name    getty                type    status        comments
#
# If console is marked "insecure", then init will ask for the root password
# when going to single-user mode.
console    none                unknown    off secure
#
ttyv0    "/usr/libexec/getty Pc"        xterm    onifexists secure
# Virtual terminals
ttyv1    "/usr/libexec/getty Pc"        xterm    onifexists secure
ttyv2    "/usr/libexec/getty Pc"        xterm    onifexists secure
ttyv3    "/usr/libexec/getty Pc"        xterm    onifexists secure
ttyv4    "/usr/libexec/getty Pc"        xterm    onifexists secure
ttyv5    "/usr/libexec/getty Pc"        xterm    onifexists secure
ttyv6    "/usr/libexec/getty Pc"        xterm    onifexists secure
ttyv7    "/usr/libexec/getty Pc"        xterm    onifexists secure
ttyv8    "/usr/local/bin/xdm -nodaemon"    xterm    off secure
# Serial terminals
# The 'dialup' keyword identifies dialin lines to login, fingerd etc.
ttyu0    "/usr/libexec/getty 3wire"    vt100    onifconsole secure
ttyu1    "/usr/libexec/getty 3wire"    vt100    onifconsole secure
ttyu2    "/usr/libexec/getty 3wire"    vt100    onifconsole secure
ttyu3    "/usr/libexec/getty 3wire"    vt100    onifconsole secure
# Dumb console
dcons    "/usr/libexec/getty std.9600"    vt100    off secure
# Xen Virtual console
xc0    "/usr/libexec/getty Pc"        xterm    onifconsole secure
# RISC-V HTIF console
rcons    "/usr/libexec/getty std.9600"    vt100    onifconsole secure
 
The only way I get to Kde somehow is by login as root and typing startx it bring me directly in plasma wayland.
 
have no file at all in my home directory only a desktop folder all my config file are in /root
You need to create that file in your user's home directory. Your user account cannot access root's home directory for, hopefully, obvious reasons.
 
You need to create that file in your user's home directory. Your user account cannot access root's home directory for, hopefully, obvious reasons.
I'm sorry files are there they were hidden forget to do ls -la
here's my .xinitrc file :

Code:
#!/bin/sh
# $Xorg: xinitrc.cpp,v 1.3 2000/08/17 19:54:30 cpqbld Exp $

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/usr/local/lib/X11/xinit/.Xresources
sysmodmap=/usr/local/lib/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then
    xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
fi

if [ -f "$userresources" ]; then
    xrdb -merge "$userresources"
fi

if [ -f "$usermodmap" ]; then
    xmodmap "$usermodmap"
fi

aa_dir=/usr/local/etc/auto-admin
for local_xsession in $aa_dir/xsession.*; do
    if [ -e  ] && /usr/local/sbin/auto-file-secure $local_xsession; then
    . $local_xsession
    fi
done

startplasma-x11
 
Ok, I forgot to add the user to the video group which I just did, now when i boot I log as user and type startx and it bring me directly to plasma desktop as user, still no sddm
 
Finally, I started again from 0. Reinstalled the sys, and this time a did it under sudo user, it work last time i did root. now everything work.
 
Finally, I started again from 0. Reinstalled the sys, and this time a did it under sudo user, it work last time i did root. now everything work.
Can you elaborate on how you did that please? The install hints at that, but I didn't understand at the time. Thanks
 
when I installed the first time plasma-desktop and KDE, I did it rooted, the second time I did it normal user whit sudo, and everything went well after that. I just reinstalled everything, because anyway there was nothing important in that fresh installation, so nothing to loose.
 
Got my installation working in the end, but it was more difficult than I remember previous fresh installations.
Probably my fault, I must have misread or misinterpreted one of the questions / choices in the installer.
For me, the mysteries of the /.xinitrc. file continue - but at least it all works.
And, I still haven't got apcupsd and gapcmon working yet! But that's another story.
Thanks to all for the various ideas put forward.
 
It's irrelevant, it doesn't matter if you use sudo(8) or use root directly. It's the same thing, sudo(8) gives you access as root.
I think I had the same experience a year ago. Sudo I presume operates in the user's directory with root permission, whereas logging in as root uses root's home directory. I presume there are config files not put in user's home directory when logging in as root. Maybe later versions of freebsd do better?

It is definitely non-trivial getting a GUI up and running, even following the handbook.

Helps to use the hotkey to access the root console <ctrl-alt-F2> and <ctrl-alt-F9> to go back to GUI, since KDE has root access disabled by default.
 
Back
Top