From: Chris Marusich <cmmarusich@gmail.com>
To: help-guix@gnu.org
Subject: Can't log in: blank login screen after reconfigure
Date: Sat, 20 Oct 2018 12:21:51 -0700 [thread overview]
Message-ID: <87ftx0qv8w.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2211 bytes --]
Hi,
I recently ran "guix pull" and then "guix system reconfigure" on a
GuixSD installation in a VirtualBox VM. Since doing that, I can't log
in. While booting, everything proceeds as usual, with normal output,
until the SLiM login screen is supposed to appear. But instead of the
SLiM login screen, I get a blank screen with a small white cursor in the
upper left, and I can't log in.
Has anyone seen anything like this in the past? Here are some
observations I've made about the situation:
* GuixSD shuts down normally if I issue the "shutdown signal" from
VirtualBox. This indicates the OS is actually still running.
* I waited over 8 hours, and the login screen did not appear.
* I tried blind-typing my user name and password, but the blank screen
remained.
* When I boot from the previous system generation, there is no problem.
* When I replace SLiM with SDDM in my OS configuration and reconfigure,
the same problem occurs.
* However, one time only, while trying to boot using SDDM instead of
SLiM, I got to the SDDM login screen. But when I typed in my username
and password and hit enter, I received the same blank screen as before
and ultimately could not log in. Every other time I've booted the VM,
I didn't even get to the SDDM login screen, so I don't know why I was
able to reach the login screen that one time.
* I tried pressing control+alt+F2 etc. to switch to different virtual
tty, but it didn't work. The blank screen remained.
* I examined various system logs, but I could not find anything that
jumped out at me as causing the problem. It's entirely possible I
missed something important, though; I just checked a few places.
There is more that I could try - for example, I could try starting an
ssh server in my VM and logging in that way. I could also try drilling
deeper into the X server logs, since that seems like the obvious next
step, since the problem occurs for both SDDM and SLiM. I could also try
reinstalling GuixSD in a new VM. But I haven't tried any of this yet
due to lack of time.
If anyone has any advice or has seen this before, please let me know.
Thank you!
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2018-10-20 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 19:21 Chris Marusich [this message]
2018-10-21 9:11 ` Can't log in: blank login screen after reconfigure znavko
2018-10-21 20:11 ` Chris Marusich
2018-10-21 16:01 ` Björn Höfling
2018-10-21 18:33 ` Ricardo Wurmus
2018-10-24 14:19 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftx0qv8w.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=help-guix@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).