From owner-freebsd-questions@freebsd.org Mon Dec 14 14:02:02 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CCE634BA812 for ; Mon, 14 Dec 2020 14:02:02 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from cp160176.hpdns.net (cp160176.hpdns.net [91.238.160.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CvjkK1mZVz4tJl for ; Mon, 14 Dec 2020 14:02:00 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=milibyte.co.uk; s=default; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:To:From:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=C/1TH1ZHJTUf6UBfCZryipGD981Cu+eX0FYCqHZQijI=; b=oxMAWCI7f/A7R17/Zb6818VBR8 EYGeQX3UnDhPII0Fls/54KPWKxx78JQhaEXsZfFTH4vaTHWD7ccfoabbTg6Iasr7YBveLef9m1q1A bqeW7tCNZKjzuZ0NUzaasv5JRtJvIAyq2bTOTXZ55UqTPjrwwHulbuJbfBmjCk/w+qKJ2cAOvrR1+ 6/WopykJqvWVkC61mkL7yj6fzxbNONIlnQfSzatlh6LHYEzulVK55xDSCntaKcjJihKSwJnfMlkMo l0CuXvMDsCEvUi0Zl5vcJa2aknyoda9hNFAnYjsRF22wRYMLfpAt8u/bkr0SXV0DEUTCY2RZuOqpR LZgQ0TEg==; Received: from 82-71-56-121.dsl.in-addr.zen.co.uk ([82.71.56.121]:57198 helo=curlew.milibyte.co.uk) by cp160176.hpdns.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1kooQ4-000jy9-Ig for freebsd-questions@freebsd.org; Mon, 14 Dec 2020 14:01:44 +0000 Received: from [127.0.0.1] (helo=curlew.localnet) by curlew.milibyte.co.uk with esmtp (Exim 4.94) (envelope-from ) id 1kooQ3-0001lY-IY for freebsd-questions@freebsd.org; Mon, 14 Dec 2020 14:01:44 +0000 From: Mike Clarke To: freebsd-questions@freebsd.org Subject: Re: x11/sddm hangs with black screen Date: Mon, 14 Dec 2020 14:01:44 +0000 Message-ID: <2388513.oMScJ4UOta@curlew> In-Reply-To: References: <1612377.MsCH1bHPGx@curlew> MIME-Version: 1.0 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-SA-Exim-Scanned: No (on curlew.milibyte.co.uk); SAEximRunCond expanded to false X-YourOrg-MailScanner-Information: Please contact the ISP for more information X-YourOrg-MailScanner-ID: 1kooQ4-000jy9-Ig X-YourOrg-MailScanner: Found to be clean X-YourOrg-MailScanner-SpamCheck: X-YourOrg-MailScanner-From: jmc-freebsd2@milibyte.co.uk X-Spam-Status: No X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cp160176.hpdns.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - milibyte.co.uk X-Get-Message-Sender-Via: cp160176.hpdns.net: authenticated_id: mailpool@milibyte.co.uk X-Authenticated-Sender: cp160176.hpdns.net: mailpool@milibyte.co.uk X-Source: X-Source-Args: X-Source-Dir: X-Rspamd-Queue-Id: 4CvjkK1mZVz4tJl X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=milibyte.co.uk header.s=default header.b=oxMAWCI7; dmarc=none; spf=pass (mx1.freebsd.org: domain of jmc-freebsd2@milibyte.co.uk designates 91.238.160.176 as permitted sender) smtp.mailfrom=jmc-freebsd2@milibyte.co.uk X-Spamd-Result: default: False [-2.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; HAS_X_SOURCE(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[milibyte.co.uk:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; HAS_X_ANTIABUSE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[91.238.160.176:from]; CTE_CASE(0.50)[]; ASN(0.00)[asn:12703, ipnet:91.238.160.0/22, country:GB]; HAS_X_AS(0.00)[mailpool@milibyte.co.uk]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[milibyte.co.uk:s=default]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[milibyte.co.uk]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[91.238.160.176:from:127.0.2.255]; HAS_X_GMSV(0.00)[mailpool@milibyte.co.uk]; MID_RHS_NOT_FQDN(0.50)[]; MAILMAN_DEST(0.00)[freebsd-questions] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7Bit X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2020 14:02:02 -0000 On Sunday, 13 December 2020 12:07:37 GMT Michael Schuster wrote: > On Sun, Dec 13, 2020, 11:40 Mike Clarke wrote: > > I've just upgraded a couple of hundred packages today and > > sddm-0.19.0 goes no further than a black screen with just a > > mouse pointer. > > I'm by no means an expert where sddm is concerned, but from those who are, > you might get a quicker and better informed response if you provide such > information like: > > - Version of FreeBSD you're running > - details on your graphics adapter > - When you did the last upgrade before that > - Relevant content of. xsession-errors > - Ditto /var/log/Xorg.log Well the problem now seems to have been cleared although I'm not entirely sure what was causing it. I'm running 12.1-RELEASE-p12 and the problem started after sddm was upgraded from 0.18.1_4 to sddm-0.19.0 and plasma5-sddm-kcm was upgraded from 5.20.3 to 5.20.4 along with many other packages including lots of kf5* and plasma5* packages On first inspection there were no obvious clues in the log files so I temporarily rolled back to an earlier boot environment to see if a comparison of log files produced any useful information. I didn't find anything useful in Xorg.log or .xsession-errors but there was a significant difference in /var/log/sddm.log which showed that the sddm session was closed immediately after opening it When running the earlier sddm-0.18.1_4 I which works Ok had the following: [15:42:41.507] (II) DAEMON: Initializing... [15:42:41.533] (II) DAEMON: Starting... [15:42:41.533] (II) DAEMON: No session manager found [15:42:41.533] (II) DAEMON: Adding new display on vt 9 ... [15:42:41.536] (II) DAEMON: Loading theme configuration from "" [15:42:41.536] (II) DAEMON: Display server starting... [15:42:41.536] (II) DAEMON: Running: /usr/local/bin/X -nolisten tcp -auth /var/run/sddm/ {ea1bd841-d1db-41b0-ad28-522d55d0141e} -background none -noreset -displayfd 19 - seat seat0 vt9 [15:42:42.094] (II) DAEMON: Setting default cursor [15:42:42.095] (WW) DAEMON: Could not setup default cursor [15:42:42.095] (II) DAEMON: Running display setup script "/usr/local/share/sddm/scripts/ Xsetup" [15:42:42.116] (II) DAEMON: Display server started. [15:42:42.116] (II) DAEMON: Reading from "/usr/local/share/xsessions/plasma.desktop" [15:42:42.117] (II) DAEMON: Reading from "/usr/local/share/xsessions/plasma.desktop" [15:42:42.117] (II) DAEMON: Session "/usr/local/share/xsessions/plasma.desktop" selected, command: "/usr/local/bin/startplasma-x11" [15:42:42.117] (II) DAEMON: Adding cookie to "/var/run/sddm/{ea1bd841-d1db-41b0- ad28-522d55d0141e}" [15:42:42.127] (II) HELPER: [PAM] Starting... [15:42:42.127] (II) HELPER: [PAM] Authenticating... [15:42:42.127] (II) HELPER: [PAM] returning. [15:42:42.127] (II) DAEMON: Authenticated successfully [15:42:42.140] (II) HELPER: [PAM] Preparing to converse... [15:42:42.140] (II) HELPER: [PAM] Conversation with 1 messages [15:42:42.140] (WW) DAEMON: Authentication information: "Last login: Sun Dec 13 15:32:24 on tty-1" [15:42:42.313] (II) HELPER: Starting: "/usr/local/share/sddm/scripts/Xsession /usr/local/bin/ startplasma-x11" [15:42:42.511] (II) HELPER: Adding cookie to "/home/mike/.Xauthority" [15:42:42.916] (II) DAEMON: Session started But after upgrading to sddm-0.19.0 I had this: [16:46:06.845] (II) DAEMON: Initializing... [16:46:06.855] (II) DAEMON: Starting... [16:46:06.856] (II) DAEMON: No session manager found [16:46:06.856] (II) DAEMON: Adding new display on vt 9 ... [16:46:06.857] (II) DAEMON: Loading theme configuration from "" [16:46:06.857] (II) DAEMON: Display server starting... [16:46:06.857] (II) DAEMON: Adding cookie to "/var/run/sddm/{0c758e91-de90-42e3-b4fd- b0a0f79e847b}" [16:46:06.864] (II) DAEMON: Running: /usr/local/bin/X -nolisten tcp -auth /var/run/sddm/ {0c758e91-de90-42e3-b4fd-b0a0f79e847b} -background none -noreset -displayfd 19 -seat seat0 vt9 [16:46:07.269] (II) DAEMON: Setting default cursor [16:46:07.270] (WW) DAEMON: Could not setup default cursor [16:46:07.270] (II) DAEMON: Running display setup script "/usr/local/share/sddm/scripts/ Xsetup" [16:46:07.288] (II) DAEMON: Display server started. [16:46:07.288] (II) DAEMON: Reading from "/usr/local/share/xsessions/plasma.desktop" [16:46:07.288] (II) DAEMON: Reading from "/usr/local/share/xsessions/plasma.desktop" [16:46:07.288] (II) DAEMON: Session "/usr/local/share/xsessions/plasma.desktop" selected, command: "/usr/local/bin/startplasma-x11" [16:46:07.294] (II) HELPER: [PAM] Starting... [16:46:07.294] (II) HELPER: [PAM] Authenticating... [16:46:07.294] (II) HELPER: [PAM] returning. [16:46:07.295] (II) DAEMON: Authenticated successfully [16:46:07.295] (II) HELPER: New VT is unsupported on FreeBSD [16:46:07.295] (II) HELPER: [PAM] Preparing to converse... [16:46:07.295] (II) HELPER: [PAM] Conversation with 1 messages [16:46:07.295] (WW) DAEMON: Authentication information: "Last login: Sun Dec 13 16:44:57 on tty-1" [16:46:07.295] (II) HELPER: Starting: "/usr/local/share/sddm/scripts/wayland-session /usr/ local/bin/startplasma-x11" [16:46:07.296] (II) HELPER: Jumping to VT -1 is unsupported on FreeBSD [16:46:07.297] (II) DAEMON: Session started [16:46:07.318] (II) HELPER: [PAM] Closing session [16:46:07.319] (II) HELPER: [PAM] Ended. [16:46:07.319] (WW) DAEMON: Auth: sddm-helper exited with 1 A bit of Googling for 'sddm-helper exited with 1' came up with problems with login scripts being a possible cause. I normally use the KDE automatic login feature and the login screen doesn't appear so I disabled auto login to try to determine at what stage sddm was stopping only to find that I was then able to login without any problem. I then tried to recreate the problem by re-enabling automatic login only to discover that sddm was still working fine and I was taken straight to my KDE desktop. Checking sddm.log now shows that there is no longer any reference to wayland-session, 'New VT is unsupported on FreeBSD' or 'Jumping to VT -1 is unsupported on FreeBSD'. So disabling and re-enabling auto login might or might not have had some effect on the problem but at least everything's working OK ... for now. -- Mike Clarke