Third try! No luck.

My problem is every thing boots on the sddm but dosen't recognize user name or password.
pkg Installed kde5 sddm all went well,
but after reboot I get sddm with error no user name or password
Followed the handbook 5,7 desktop enviorments to the letter.
Tried three times to reinstall no luck
 
It could be executable permissions, or something misconfigured. The .xsession file has to be set to executable at least for group. Also, see that the home partition isn't mounted as noexec.

When a username and password don't give an error, and the screen waits for a few seconds, it's usually a permission error or a configuration error.
 
Have you installed plasma5-plasma its a meta package for the plasma desktop install this


My problem is every thing boots on the sddm but dosen't recognize user name or password.
pkg Installed kde5 sddm all went well,
but after reboot I get sddm with error no user name or password
Followed the handbook 5,7 desktop enviorments to the letter.
Tried three times to reinstall no luck
 
My problem is every thing boots on the sddm but dosen't recognize user name or password.
pkg Installed kde5 sddm all went well,
but after reboot I get sddm with error no user name or password
Please show us your /var/log/sddm.log
 
It could be executable permissions, or something misconfigured. The .xsession file has to be set to executable at least for group. Also, see that the home partition isn't mounted as noexec.

When a username and password don't give an error, and the screen waits for a few seconds, it's usually a permission error or a configuration error.
How to find noexec in what file?
 
This will lead nowhere unless you start to describe your problems correctly, which includes at least three things:
  • What did you try? Exactly? Yes, this includes for example commands typed, character by character.
  • What was your expected result? Again, in detail
  • What was your actual result? I guess it's clear now this should include literal error messages received.
 
OK tried to login without sddm through xstart and on in Kde5 it booted into plasma but my open screen froze, what next?
 
Could that be that you use the Wayland session by accident?

Try starting plasma from console with: exec ck-launch-session startplasma-x11
 
The problem may be with packages and ports on your already system. Delete the program, then remove distfiles through the make command. Make clean, make rmconfig-recursive. Update src and portsnap. Make sure they're the right ones. Then, try again. [someone pointed out ports weren't being used] -> I was thinking about another recent thread, where someone was trying to update source to compile or use a package for a graphics kmod. It could explain for any program using ports, but that wasn't the case.

But about the mounting and executive permissions, that was for this thread.

Then, it's a typo in the configuration, lack of configuration or a missing package. That or a bug.

You'll have to give more information on what's going on. It may take a little research and looking at log files, and dmesg messages etc. People here are guessing on a wide range of what it could be, and you'll have to narrow it down.

I have used Arch Linux, other Linux and program specific documentation to configure programs on FreeBSD before. KDE and SDDM independent documentation would be relevant. Then I use the documentation here for what's more specific to FreeBSD. Or for those more familiar with KDE on FreeBSD, they would be able to answer SDDM questions better.
 
OK I'm going to wipe my whole HD clean, Then reinstall freebsd13 following the handbook step by step.
Till tomorrow good night.
Thanks to all that helped.
 
You don't have to wipe your harddrive clean. If the problem is in the home directory, there's few places to look there. Maybe starting over from packages or carefully re-trying steps pertaining to the /usr/local/ directory. Don't just delete that directory.

This is likely from the KDE and SDDM aspect and configuration.
 
You don't have to wipe your harddrive clean. If the problem is in the home directory, there's few places to look there. Maybe starting over from packages or carefully re-trying steps pertaining to the /usr/local/ directory. Don't just delete that directory.

This is likely from the KDE and SDDM aspect and configuration.
I have started already, I going to use digital 60 G clean to start tomorrow.
I'll stay in touch. Thanks friend.
 
You don't have to wipe your harddrive clean. If the problem is in the home directory, there's few places to look there. Maybe starting over from packages or carefully re-trying steps pertaining to the /usr/local/ directory. Don't just delete that directory.

This is likely from the KDE and SDDM aspect and configuration.
OK Now when I started all over new Sdd 60G 8G ram all new and now gnome3-lite followed all handbook instructions, It doesn't even
start with startx command? Error Can't run in framebuffer mode. It just don't want me in freebsd.
 
OK Now when I started all over new Sdd 60G 8G ram all new and now gnome3-lite followed all handbook instructions, It doesn't even
start with startx command? Error Can't run in framebuffer mode. It just don't want me in freebsd.
Xorg logfile is /var/log/Xorg.0.log. What is in there?
 
Back
Top