Solved Black screen / Fresh install (KDE package is back now)

Hello,

Tried to install freeBSD last year on a Acer laptop but it was not a great idea regarding to the hardware. Lot of struggle.

I have bought a Lenovo Tiny M710q just for this OS. In order ton test it.

Everything went well during the install of the system plus startx. But what a struggle ton install kde !

First, I struggled to find a package. The doc suggests "pkg install plasma6-plasma". However it seems to be plasma6-plasma-desktop.
I installed this package and sddm.

After a reboot I was able to land on sddm window and enter my password. From there, the only thing I get is a black screen with a mouse. It occurs with Wayland and x11 (selected while log in)

Any suggestion please ?

Thank you
 
Any suggestion please ?

Thank you
When the latest updates to KDE and gnome packages are eventually fixed, I suggest you then try the excellent script described in this thread.
HTH
 
I posted this message ignoring the whole thing about missing package.s I know now that the problem is serious so I will wisely wait until it's fixed.

Thank you for your suggestion. Will bookmark it and try it. Hope the fix will come in a relatively short period.
 
Hello,

Tried to install freeBSD last year on a Acer laptop but it was not a great idea regarding to the hardware. Lot of struggle.

I have bought a Lenovo Tiny M710q just for this OS. In order ton test it.

Everything went well during the install of the system plus startx. But what a struggle ton install kde !

First, I struggled to find a package. The doc suggests "pkg install plasma6-plasma". However it seems to be plasma6-plasma-desktop.
I installed this package and sddm.

After a reboot I was able to land on sddm window and enter my password. From there, the only thing I get is a black screen with a mouse. It occurs with Wayland and x11 (selected while log in)

Any suggestion please ?

Thank you
The symptoms you describe - that's a rather predictable result if you skip the configuration steps that come before trying to log in for the first time. Did you read the Handbook Section 8.2.1 KDE Plasma completely? There's also a subsection on configuration. Section 8.2.1.3 covers the config that needs to be done. Pay attention to instructions on staring D-BUS - you're gonna need it.
 
The symptoms you describe - that's a rather predictable result if you skip the configuration steps that come before trying to log in for the first time. Did you read the Handbook Section 8.2.1 KDE Plasma completely? There's also a subsection on configuration. Section 8.2.1.3 covers the config that needs to be done. Pay attention to instructions on staring D-BUS - you're gonna need it.
I have followed this guide yes. But it's not about me. It's about the broken pkg. The whole KDE package is missing, but also Gnome amd some others environment.

I installed Lxqt for now. Hate it but it's the only DE package I found. Hope the team will fix this issue soon.
 
I have followed this guide yes. But it's not about me. It's about the broken pkg. The whole KDE package is missing, but also Gnome amd some others environment.

I installed Lxqt for now. Hate it but it's the only DE package I found. Hope the team will fix this issue soon.
https://portsfallout.com is reporting tons of failures for amd64 packages. And yes, that includes x11/plasma6-plasma. Although, looking at some of the logs provided by that site, it really looks like the build failures are getting traced to the fact that somebody updated the build jails, but not the hosts... 😲 That would be my offhand conclusion after a quick look. It's really looks like an issue on the other end of the wire, with how the repos are being built, rather than anything with the user-side installation of pkg(8)...
 
I checked some of the logs and even subscribe to a pkg build mailing list but honestly, my abilites to understand the process at this level are almost inexistent.

I come from Debian and do understand few things but anything related the building proceess is far from me. When you say "somebody updated the build jails, but not the hosts...", I honestly have no idea what that means. Would appreciate if you can exain this part.
 
Would appreciate if you can exain this part.
Well, it does take knowing what the jails are, how to set stuff up inside of them, and how to update them, for starters. The FreeBSD User Handbook does have a chapter about jails. If you follow along, you'll be able to play with jails and get a good sense of what they are for.

Also, if you have heard of Poudriere, and tried to set it up, you'll see where the jails fit into the Poudriere setup.

Jails are a pretty complex thing on their own. But they also play an important part of setting up a process for Poudriere to run.

I did play with both jails and Poudriere. Poudriere is basically the automation of a lot of details that go into building a package repo. And yep, Poudriere is the official tool to build the official, pubic package repos that FreeBSD maintains (for the rank-and-file users like us).

As a result of my playing with that stuff on my own machines (Yeah, I installed Poudriere on my own machines, grabbed a copy of the ports tree, and used Poudriere to compile my own packages), I do have an informed idea of what's going on, and what the published logs tell me.

Based on what I'm seeing, and what I know about Poudriere, I'd say the build jails need to be rebuilt. Dunno how long it will take for the Ports Management team to figure that out. Well, it's not out of question that I missed something in my assessment, and that the real problem is elsewhere.

I just think that instead of pointing fingers, it's more productive to figure out how things are supposed to work, and take note of differences between reality and the official documentation.

I came to FreeBSD because of ZFS, and Ports (The system of FreeBSD-specific Makefiles that create packages for FreeBSD) are what convinced me to stay. I do disagree with the defaults set by pre-compiled packages, so I'm grateful for the Ports being so easily available.

Comparing the current mess to the Linux alternatives (Snap/Flatpak/rpm/.deb), I personally prefer sticking with FreeBSD's Ports and wait for the situation to shake itself out. 😑
 
Regarding to the initial issue aka KDE is missing in pkg, everything works fine now.
I updated the system this morning and was able to install kde the traditional way : pkg install kde
I am still not able to understand the building process, like, when this package was built and when he was pushed to the repo.

Thank you a lot for all these information.
As a novice with this OS, I will for sure spend some time in order to figure out and learn things.
 
Back
Top