GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. Recent install of Kubuntu Now on boot I get a pop-up saying sddm greeter has crashed on about 3 out of 4 boot attempts. The pop-up provides choices to restart application or just continue.
Restart produces all black screen, continue produces all white screen. Then the system is usable. I have since switched to lightdm. Had to do a complete uninstall of sddm plus a "systemctl disable sddm" to get lightdm to work.
Looks the same here. Kubuntu With nvidia card as the primary display in BIOS: I booted times without a problem before this happened for the first time. After it started happening sometimes I'm able to switch VTs as in sometimes it won't switch, it'll just hang. EDIT: Just to clarify my intention on reporting this. X isn't starting so xcbScreen will return null so that's all for the crash in sddm-greeter.
Installed some updates this afternoon and after a reboot of Kubuntu While typing this I switched my laptop on again and now things seem fine, no idea what has changed but sddm greeter isn't crashing anymore. Could it be related to nvidia-prime? We have an Xstop script now where you need to run a command: see I think I'm having the same issue on my Gentoo machine.
Sddm-greeter always crash on startup with this messages:.Links : forums. Copyright Gentoo Foundation, Inc. Hosting by Gossamer Threads Inc. Quick Search :. View unanswered posts View posts from last 24 hours.
KDE Plasma 5
View previous topic :: View next topic. Hello, I have problem with sddm after update system. Sddm on vt7 create black screen with no blinking cursor on top-left corner. Startx working fine. If I run sddm as root from console, it gives Code:. Back to top. However, by calling journalctl -b grep 'sddm' I got: Code:. Dec 01 carillon sddm: Initializing Dec 01 carillon sddm: Starting Dec 01 carillon sddm: Adding new display on vt Dec 01 carillon sddm: Display server starting Dec 01 carillon sddm: Socket server starting Dec 01 carillon sddm: Socket server started.
Dec 01 carillon sddm: Greeter starting Dec 01 carillon sddm-helper: [PAM] Authenticating Dec 01 carillon sddm-helper: [PAM] returning. Dec 01 carillon sddm: Auth: sddm-helper exited with 6 Dec 01 carillon sddm: Greeter stopped. Add sddm user to the video group. Romanujan wrote:. I have also tried this, but it didn't help me so I went back to old use flags.
On the other side, I think I didn't have the directory mentioned here back then I am not sure now. I can confirm, that adding of sddm user to video group solved the issue for me. Thank you. Hello fellow Forum users, I have the same problem after upgrading to Xorg Server 1.Gentoo Linux is available free over the Internet. Live environments and stage archives can be downloaded using the links below.
If you are unsure what you need to download, please refer to the Gentoo Handbook for the complete installation documentation. It explains how you can find the right architecture for your machine and which files you need at what stage of the installation process.
There are two builds of the x86 architecture: i and i The ia64 architecture is intended for use on Intel Itanium processors only. For all other experimental downloads including for the arm64 and mips architecturesplease refer to the complete experimental downloads archive.
Downloads Gentoo Linux is available free over the Internet. Stage 3 MiB. Stage 3 i MiB. What should I download? What do I do with these files? Gentoo Handbook If you are unsure what you need to download, please refer to the Gentoo Handbook for the complete installation documentation. Details contents, hashes, and signatures Minimal Installation CD Stage 3 Confirm processor compatibility There are two builds of the x86 architecture: i and i Details contents, hashes, and signatures Stage 3.
Stage 3 HPPA 1. Details contents, hashes, and signatures Minimal Installation CD Stage 3 Confirm processor compatibility The ia64 architecture is intended for use on Intel Itanium processors only. Other experimental architectures For all other experimental downloads including for the arm64 and mips architecturesplease refer to the complete experimental downloads archive.KDE is a free software community, producing a wide range of applications including the popular Plasma desktop environment.
Choosing an appropriate profilealthough not required, is recommended as it sets a number of global and package-specific USE flags to ease installation and ensure a smooth KDE experience.
Note that other USE flag combinations than set by the profile may technically be possible especially if selected applications are run instead of a full KDE Plasma desktop environmentbut may be unsupported, untested, or lead to unexpected loss of functionality. Default choices of these services will be pulled in automatically - by the installation steps in the following chapters - depending on the profile selection made earlier, but still need to be set up properly before starting KDE Plasma for the first time.
Follow the links for information how to set up these services.🚩 Сборка Gentoo
Read and follow the instructions in the X server article to setup the X environment. Some of these dependencies will predetermine package choices where otherwise there would be options to choose from. This is the preferred option. Also, be sure to read through the SDDM page if further issues appear. Plasma can be started the old-fashioned way with startxbut extra care needs to be taken to ensure it gets a valid session.
Plasma 5 uses the StatusNotifier specification for systray icons . As not all applications have been ported to the new system, some workarounds exist and Plasma 5 has a means to convert old xembed-based system tray icons to StatusNotifier icons. After install, the Ubuntu Indicator plugin can be found under Tools Plugins. Shutdown scripts require executable bit set because they are not sourced.
The Keychain article provides more information about this. KDE Plasma has a utility in order to start graphical programs with root privileges. This requires Xorgand only works within X. It can be used by invoking kdesu either from KRunner or a terminal emulator:. Plasma-5 and Applications are shipping their localization per-package.
Enable your localization in systemsettings. KDE PIM is a whole suite of applications to manage personal information including mail, calendar, contacts and more. It has several optional runtime dependencies to extend its functionality:. As Frameworks are mostly libraries and provide little user functionality, it's not necessary to install them manually - the required packages will be pulled in automatically as dependencies.
The most important KDE applications are in the Gentoo ebuild repository and many are located in the kde-apps and kde-misc categories. Refer to the Troubleshooting sub-article. Jump to: navigationsearch. This page contains changes which are not marked for translation. Other languages:. Note For Wayland support, a logind implementation is required, which means choosing either elogind or systemd.
Note Before proceeding, make sure to choose a Plasma profile. Warning It could be a very bad idea to start GUI applications with root privileges, versus adding the regular user to the relevant group or simply just running the command unprivileged. Only use kdesu when absolutely necessary. Note Some applications such as kwrite, dolphin etc.Links : forums.
Copyright Gentoo Foundation, Inc. Hosting by Gossamer Threads Inc. Quick Search :. View unanswered posts View posts from last 24 hours. View previous topic :: View next topic. I wished use 'sddm' as display manager but I have a problem with it When my computer start, sddm start also and the login panel is well displayed on my monitor.
But all the graphic compoent of sddm is "too big": I feel that sddm appears in a resolution of x Back to top. Sounds more like this. Can be on, off or none. If property is set to none, numlock won't be changed NOTE: Currently ignored if autologin is enabled. Total: 0 packages, Size of downloads: 0 KiB Nothing to merge; quitting. Prepare for some fun. Partial Read Try again. It's probably wise not to edit this file manually too freely.
If [ Not saying that's the problem, as the settings look the same; it's just going to make it needlessly hard to configure. It looks like you did a: cat example. I solved my problem but I do not really know how. I changed the connection theme from "Brise" to "Elarun". Then I changed from "Elarun" to "Brise" and the problem was solved Thank you everyone. All times are GMT.GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project?
Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. I hope fixes this issue.
Let's close this. If the problem still exists, please reopen this. This maybe a duplicate of and ? The issue was already fixed in the upstream, but it seems that the fix is not included in r3. Please test the latest git snapshot. I am not familiar with gentoo, but maybe systemd?
Then, if the current master does not work, please boot with systemd. So, I cannot find anything suspicious lines about udevd.
Gentoo Archives: gentoo-user
Could you test ? Even if does not fix the issue, then please also provide logs of sddm or X.
What do you mean by test ? Sorry, but I don't think this is going to be diagnosed upstream. This needs to be debugged by somebody who has gentoo and sddm. There are no errors in the logs. For sddm, we only knows that it starts:. It's really hard for me to guess where it's going wrong too, but based on the fact that it's working fine on my other two systems, one Intel the other AMD I'm guessing it's HyperV related rather than Gentoo or SDDM itself.
FireBurn If you have a situation where the problem is easily reproduced, you may be able to identify the offending commit with a git bisect.Install the sddm package. See sddm. Everything should work out of the box, since Arch Linux uses systemd and SDDM defaults to using systemd-logind for session management.
This configuration causes a KDE Plasma session to be started for user john when the system is booted. An option to autologin into KDE Plasma while simultaneously locking the session is not available .
Theme settings can be changed in the [Theme] section. If you use Plasma's system settings, themes may show previews. Set the current theme through the Current value, e.
You can add your custom made themes to that directory under a separate subdirectory. Note that SDDM requires these subdirectory names to be the same as the theme names. Study the files installed to modify or create your own theme. You can preview an SDDM theme if needed. This is especially helpful if you are not sure how the theme would look if selected or just edited a theme and want to see how it would look without logging out.
You can run something like this:. This should open a new window for every monitor you have connected and show a preview of the theme. SDDM reads the user icon a. You can change the default FacesDir location to suit your needs.
Here is an example:. The other option is to put a PNG image named. In this case, no changes to any SDDM configuration file is required. However, you need to make sure that sddm user can read the PNG image file s for the user icon s. To set proper permissions run:. You can check permissions with:. For example:. Install qt5-virtualkeyboard. SDDM works with a fingerprint reader when using fprint.
In KDE's lock screen it is also possible to use either password or fingerprint, this can be done by adding the following to the top of the auth section:. If disk space is not the issue, it may be due to a bug. See Random number generation for suggestions to increase the entropy pool. Xauthority and logging in again without rebooting.
Rebooting without logging in creates the file again and the problem will persist.
SDDM follows the systemd convention of starting the first graphical session on tty1. If you prefer the old convention where tty1 through tty6 are reserved for text consoles, change the default value of MinimumVT variable, which comes under the [X11] section:. SDDM only displays users with a UID in the range of to by default, if the UIDs of the desired users are below this value then you will have to modify this range.