Date: Mon, 14 Dec 2020 14:01:44 +0000 From: Mike Clarke <jmc-freebsd2@milibyte.co.uk> To: freebsd-questions@freebsd.org Subject: Re: x11/sddm hangs with black screen Message-ID: <2388513.oMScJ4UOta@curlew> In-Reply-To: <CADqw_gL8d5j4i%2BdLgzKYT-r6KcZM_%2B4tQqhfSVojmpM-bEqLwA@mail.gmail.com> References: <1612377.MsCH1bHPGx@curlew> <CADqw_gL8d5j4i%2BdLgzKYT-r6KcZM_%2B4tQqhfSVojmpM-bEqLwA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday, 13 December 2020 12:07:37 GMT Michael Schuster wrote:
> On Sun, Dec 13, 2020, 11:40 Mike Clarke <jmc-freebsd2@milibyte.co.uk> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2388513.oMScJ4UOta>