From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14746] Lack of management after loading
Date: Tue, 05 Apr 2022 13:17:16 +0000 [thread overview]
Message-ID: <bug-14746-163-OQLPXddAZl@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14746-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14746
--- Comment #2 from Alexander Zhirov <azhirov1991@gmail.com> ---
Created attachment 9276
--> https://bugs.busybox.net/attachment.cgi?id=9276&action=edit
Xorg.0.0.log
I was able to configure SSH and see what errors Xorg throws after startup. For
some reason, the modules are not loaded.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next parent reply other threads:[~2022-04-05 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14746-163@https.bugs.busybox.net/>
2022-04-05 13:17 ` bugzilla [this message]
2022-04-07 5:02 ` [Buildroot] [Bug 14746] Lack of management after loading bugzilla
2022-09-18 12:03 ` bugzilla
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=bug-14746-163-OQLPXddAZl@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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