From: "Markus Gustafsson" <markus@gustafsson.io>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Login manager occasionally fails to show
Date: Sun, 02 Feb 2025 12:09:09 +0100 [thread overview]
Message-ID: <8d355049-c63a-4031-a79b-7bd153014c57@app.fastmail.com> (raw)
In-Reply-To: <4986264.31r3eYUQgx@rogueboard>
This is my /var/log/sddm.log from an unsuccessful upstart:
> [11:57:20.087] (II) DAEMON: Initializing...
> [11:57:20.090] (II) DAEMON: Starting...
> [11:57:20.090] (II) DAEMON: Logind interface found
> [11:57:20.091] (II) DAEMON: Adding new display...
> [11:57:20.091] (II) DAEMON: Loaded empty theme configuration
> [11:57:20.092] (II) DAEMON: Xauthority path: "/run/sddm/xauth_LWFoRx"
> [11:57:20.092] (II) DAEMON: Using VT 7
> [11:57:20.092] (II) DAEMON: Display server starting...
> [11:57:20.092] (II) DAEMON: Writing cookie to "/run/sddm/xauth_LWFoRx"
> [11:57:20.092] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt7 -auth /run/sddm/xauth_LWFoRx -noreset -displayfd 16
> [11:57:21.377] (II) DAEMON: Setting default cursor
> [11:57:21.394] (II) DAEMON: Running display setup script "/usr/share/sddm/scripts/Xsetup"
> [11:57:21.395] (II) DAEMON: Display server started.
> [11:57:21.395] (II) DAEMON: Socket server starting...
> [11:57:21.395] (II) DAEMON: Socket server started.
> [11:57:21.395] (II) DAEMON: Loaded empty theme configuration
> [11:57:21.396] (II) DAEMON: Greeter starting...
> [11:57:21.406] (II) HELPER: [PAM] Starting...
> [11:57:21.406] (II) HELPER: [PAM] Authenticating...
> [11:57:21.406] (II) HELPER: [PAM] returning.
> [11:57:21.425] (II) HELPER: Writing cookie to "/tmp/xauth_ocMfUA"
> [11:57:21.425] (II) HELPER: Starting X11 session: "" "/usr/bin/sddm-greeter-qt6 --socket /tmp/sddm-:0-lMuEWF"
> [11:57:21.426] (II) DAEMON: Greeter session started successfully
> [11:57:21.468] (II) DAEMON: Message received from greeter: Connect
I think it looks pretty much the same as for a successful one...
I peeked into ~/.local/share/sddm/wayland-session.log as well, but I got the impression that this starts getting written later (after having logged in)?
Regards,
Markus
On Thu, Jan 30, 2025, at 09:06, Michael wrote:
> On Wednesday 29 January 2025 21:19:50 Greenwich Mean Time Markus Gustafsson
> wrote:
>> Thanks for the input. I do indeed have a pretty new CPU as well.
>>
>> I did try the rc.conf trick but no luck after trying it once. I'll keep it
>> around for a while and see if I can see an overall improvement.
>>
>> Regards,
>> Markus
>
> If your SDDM problem were the same as mine, then my solution would have an
> immediate and permanent effect. Have you looked at:
>
> ~/.local/share/sddm/xorg-session.log
>
> or,
>
> ~/.local/share/sddm/wayland-session.log
>
> and
>
> /var/log/sddm.log
>
> for any hints pointing to the cause of this?
> Attachments:
> * signature.asc
next prev parent reply other threads:[~2025-02-02 11:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 21:41 [gentoo-user] Login manager occasionally fails to show Markus Gustafsson
2025-01-26 11:18 ` Peter Humphrey
2025-01-26 12:33 ` Michael
2025-01-29 21:19 ` Markus Gustafsson
2025-01-30 8:06 ` Michael
2025-02-02 11:09 ` Markus Gustafsson [this message]
2025-02-02 13:11 ` Michael
2025-02-07 20:56 ` Markus Gustafsson
2025-02-08 10:02 ` Michael
2025-02-08 11:02 ` Michael
2025-02-11 17:20 ` Alan Grimes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8d355049-c63a-4031-a79b-7bd153014c57@app.fastmail.com \
--to=markus@gustafsson.io \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox