Why it's so complicated


Blah blah … instead of just sitting there with a black screen and an X cursor.

In other words (without calling anyone a fool): part of making the KDE Plasma experience foolproof on FreeBSD.

Like, the opposite of "Why it's so complicated" :)

FreeBSD bug 256648 – x11/sddm enhance xinit-session for 'User Session' to work in the absence of ~/.xinitrc
  • Closed FIXED
  • the file is recommended, not required.
 
1647428850549.png
when i type :
  1. pkg install --quiet --yes kde5 sddm xorg
pkg: unrecognized option --quite
https://ibb.co/g6Bgf71
so i install xorg first
pkg install xorg
then i install kde5
pkg install kde5
https://ibb.co/HGCNwJF
after that I install sddm
pkg install sddm
https://ibb.co/3hpq93m
and I enable dbus and sddm
  1. sysrc dbus_enable="YES" && service dbus start
  1. sysrc sddm_enable="YES" && service sddm start
https://ibb.co/R0RjMsM
that's what I mean when I said above after I install xorg when I type startx twm doesn't appear or pop up
https://ibb.co/X8Nqjsk
 
https://ibb.co/R0RjMsM
that's what I mean when I said above after I install xorg when I type startx twm doesn't appear or pop up

When SDDM starts but is not visible, it is usually a sign of a problem with graphics configuration.

Please: did you attempt to manually configure a file? (Mis-typing is possible.)

Or did you run the NVIDIA-provided command (below) to automatically write the file?

nvidia-xconfig
 
When SDDM starts but is not visible, it is usually a sign of a problem with graphics configuration.

Please: did you attempt to manually configure a file? (Mis-typing is possible.)

Or did you run the NVIDIA-provided command (below) to automatically write the file?
No, i just did only the steps above nothing else for now
 
Noob Noob

Add these lines to /etc/sysctl.conf
Code:
net.local.stream.recvspace=65536
net.local.stream.sendspace=65536

If it still didn't work:
Create .xinitrc file:
# cp /usr/local/etc/X11/xinit/xinitrc ~/.xinitrc

Delete all lines and add this to .xinitrc:
exec startkde

Then log in to you desktop with:
$ startkde

Make sure you log in with a normal user, not root user.
 
Mis-typing in these two lines:
Yeah, typos are the most common reason for errors, especially the ones that only pop up later. I learned early on to put in an effort to avoid typos - that saves a LOT of time down the road. The saying 'An ounce of prevention is worth a pound of cure' is especially apt in this case. :P
 
TL;DR

May I ask you why you want to use x11-wm/awesome?

Since you are in so much trouble to install the system, I need to ask: are you aware you need at least a good understand of Lua programing just to configure Awesome properly?
 
TL;DR

May I ask you why you want to use x11-wm/awesome?

Since you are in so much trouble to install the system, I need to ask: are you aware you need at least a good understand of Lua programing just to configure Awesome properly?
Yes i know, Just to learn more and challenge myself i will install it and configure it the way I like
 
To talk quite frankly you can get away without learning Lua because the API is very well documented, but expect countless hours reading/learning it and writing hundreds (maybe several hundreds) of lines to get a personalized desktop.

This is the kind of thing you do once and use it forever because you have spent some much time configuring the thing, you don't want leave it behind.
 
I personally feel that people do themselves a disservice by jumping to login managers and desktop environments before they even have a working Xorg. Computers are often more complex than this and do require some technical steps to debug.

The problem with login managers is they *hide* useful debug information. This is almost the point of them to hide technical stuff from non-technical users.

Start with startx. Do you see any obvious error messages?
Check the Xorg log (/var/log/Xorg.0.log). Do you see any obvious error messages?

Oddly I can't see any of this necessary debugging information on this thread. Am I missing it? I have scanned through a number of times.

FreeBSD is not particularly complicated; you just need to go through the motions, not rush, aim to do things correctly and avoid taking shortcuts. Also understand that KDE isn't FreeBSD. It is a Linux-centric GUI program that happens to also run (to various degrees of brokenness) on Windows, macOS and *BSD.
 
Back
Top