From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 7F603158041 for ; Wed, 3 Apr 2024 18:58:26 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6A5742BC030; Wed, 3 Apr 2024 18:58:20 +0000 (UTC) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E34D42BC01A for ; Wed, 3 Apr 2024 18:58:19 +0000 (UTC) Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx1.riseup.net (Postfix) with ESMTPS id 4V8vCZ6CwnzDqWT for ; Wed, 3 Apr 2024 18:58:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1712170698; bh=CuK5RsgVwZvPoE9UX6jgV7zrJyyWViB+U9yW+pYF0BE=; h=Date:From:To:Subject:References:In-Reply-To:From; b=LHa30qJULZGwXj40kSa/9mCzsqdyFiYqwHCxPMGcSnVgaW5kn1L23JnBycHytbeWk 7QP9Bbpwr+armsDdjWlJejc7O28dOvCsf9BEt7zULlOh/YLkti8R+Mi6ihXfzeivuY VQONEEaJm1l3Og1bojl+AAQZAAN/WtGckkvcX2vk= X-Riseup-User-ID: 37470FB196B282B3B5F880B074761EABC378BDAF9B8E0958D14E7381DF6171F6 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4V8vCZ2z0vzJsmt for ; Wed, 3 Apr 2024 18:58:18 +0000 (UTC) Date: Wed, 3 Apr 2024 20:58:12 +0200 From: =?iso-8859-1?Q?Ho=EBl_B=E9zier?= To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Every other startup results in a black screen (possibly SDDM related?) Message-ID: References: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Kn4+q6fJa1r3NDoz" Content-Disposition: inline In-Reply-To: X-Archives-Salt: 85d7ac05-131a-4702-bec1-94f4d0684590 X-Archives-Hash: 9e2f11abd1433d33d51744882c4117e2 --Kn4+q6fJa1r3NDoz Content-Type: text/plain; protected-headers=v1; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Date: Wed, 3 Apr 2024 20:58:12 +0200 From: =?iso-8859-1?Q?Ho=EBl_B=E9zier?= To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Every other startup results in a black screen (possibly SDDM related?) >However, it does wake up if I switch to another TTY (e.g. ctrl+alt+F4) and= lets me log on, so it has obviously booted up. If I switch back to TTY 8 f= rom there it just shows a blinking cursor (i.e. not SDDM, which is what I'd= expect). If I reboot from the TTY that lets me log on, the boot process is= usually normal and leaves me at the SDDM login. > >Any tips on how to debug this would be much appreciated. Since you can switch ttys, this means your computer =E2=80=9Cproperly=E2=80= =9D booted. So as=20 far as we know, the only culprit is your login manager which failed to star= t,=20 or started improperly. For starters you could check, once logged in, if it is actually running or = not. ps faux | less will output the whole list of processes on your computer, check it to see i= f=20 you can find sddm in the list.=20 If not, then it failed to start, so you want to check if the service in cha= rge=20 to start it has been run. rc-service sddm status # for openrc systemctl status sddm # for systemd These commands should tell you if the process has been started and failed, = or=20 if it never started in the first place. If it started and failed, search fo= r=20 logs, or even try to start it manually. This will give you indications as t= o=20 why it won=E2=80=99t run. Otherwise, if it was never run by your service manager, this means somethin= g=20 earlier in the dependency tree failed to run. Same solution here: search fo= r=20 logs, `rc-status` will give you the list of running services on your comput= er=20 and their state for openrc. Good luck, Ho=C3=ABl --Kn4+q6fJa1r3NDoz Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEElZjiR4iQkYjVEGdt6jPCPrF3Nk0FAmYNpsQACgkQ6jPCPrF3 Nk1RFQ//Rj8DKfQo5Bi3xZc8Oz+viqjyL4lvACYCtfR5RpcrK1IaUWBZDM1pDG+C 4vp3pUrVMyLSOIzq1sttxIDd2uVuNIx3dT6MdPqSn7zVBNRewkOjqR+/I+ipQS+w ZW1pPhY7eHnsZIsOGLspSw5JJd3wRPUXVmVKeoTwcl+mhm5Edt7PFJl8Uu/hHH/2 HHKQAICTl2LIewUh1ht4tFTfyZdDFNSckIqNO9+s5XzTU+ziEbqJd7/AFQwbFrgB G1Dtli++2yY3PnY16JVipLeNydSeluhHf9kGAwuEDKiRYHZVAB3nXqrlnLNc/uQ/ VgciboF3k2Bd9uflaf8Te3LN3wWP0RoeIJ8/7Ft39kBsFCmOEPSkf/MlQqMSvKog 59HISBWOOGIXVfwv7p5qGd/KdTG2TaJqrbI/hW/zDKKg1HQDULrBGAxu8jqn9Ojq IE/c3YMt2CQ4S/FveWfQxioKF4wQr4zQYQfldaLClSRieyCywskRSyC//gem/9rb GvpZ2NAaba+1Zlk+kDHuI130g0zjdwh6+zY7rKcusTDNb57Hq64JDP5fDEHL7sZt yAFvf3sCrP4Szd+QOd2yH+EzOmkW8y8x+vk0kaltZQ16VjnpBSElFimQRul7abxD NK4CUpchlnwIO/JYQIkqhUEuCWNX5oWofNTeWmRVQ8rOOnOabV4= =ImgF -----END PGP SIGNATURE----- --Kn4+q6fJa1r3NDoz--