From: o.rojon@posteo.net
To: 39527@debbugs.gnu.org
Subject: bug#39527: A new information on LXQt DE not "logging in"
Date: Thu, 07 May 2020 08:45:28 +0200 [thread overview]
Message-ID: <9a3a082d2b82ce5e39676b573edb9536@posteo.net> (raw)
In-Reply-To: <3423de52ee9dfc476d967b6ce022795a@posteo.net>
Hello guys,
I have come to realise something which might be of interest, but which
might also be something which is well known to you.
When trying to launch LXQt from the GDM login/session manager, the
screen just went blank and nothing happened. This is why I assumed "it
simply doesnt work". Now I have switched to another login manager, and
logging in to LXQt works - only that I am directly prompted to specify
which WM I wanted to use. I was unable to locate one under /usr/bin
(only /usr/bin/env seems to live there) and thus had to go to the
/gnu/store directory.
So I assume that the problem might either be a "personal one" where I
have forgotten to set some path (even though I have not received a
particular warning of sorts). Or it is a problem that, either generally
or specific to LXQt, I would call the "linking" situation -- that not
completely supported packages just dont (yet) know about the location of
the binaries.
That said, it is possible that to you guys, this is nothing noteworthy
because it is clear. It's just that to me, it wasn't because I'm
learning both guile and the linux ecosystem. Thus, if the problem at
hand is simply a general problem, it is not a bug. Which means that the
topic can be closed, if there is nothing to add :)
have a good day folks, guix rules
next prev parent reply other threads:[~2020-05-07 6:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 12:11 bug#39527: Cannot log into LXQt DE o.rojon
2020-05-07 6:45 ` o.rojon [this message]
2021-05-09 17:02 ` Brendan Tildesley via Bug reports for GNU Guix
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=9a3a082d2b82ce5e39676b573edb9536@posteo.net \
--to=o.rojon@posteo.net \
--cc=39527@debbugs.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).