From: Jack <ostroffjh@users.sourceforge.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Wine problems
Date: Tue, 12 Dec 2023 17:10:18 -0500 [thread overview]
Message-ID: <LFYC7647.3ROW7JOS.JRDHLRUW@IPYVZJZL.2AVZ7MPA.UTHEVXIP> (raw)
In-Reply-To: <480c92d9db2724d7e7e9681f0e182cab@shitposting.expert>
On 2023.12.12 16:55, stefan11111@shitposting.expert wrote:
[snip...]
> Tried doing the optimus thing. Just like without optimus, I start
> xorg but I see nothing.
> Xorg and dwm properly start, I tried typing in a terminal
> 'speaker-test' and it worked.
> So the problem there isn't that xorg freezes or something, it's that
> I can't see the x server.
>
Can you please be more explicit about what you do and what you see?
How exactly do you start xorg? When you say you see nothing, do you
mean a completely black screen? If that's the case, then why do you
say that Sorg and dwm properly start. If they properly started, you
would probably see what you expected. Finally, when you say you can't
see the x server, what is it you expect to see? I don't think the
xserver displays anything of it's own, it displays stuff for other
programs. Have you looked in the X log for any relevant output?
(probably /var/log/Xorg.0.log.)
prev parent reply other threads:[~2023-12-12 22:10 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 18:31 [gentoo-user] Wine problems stefan11111
2023-12-11 19:01 ` stefan11111
2023-12-11 19:30 ` netfab
2023-12-11 20:01 ` stefan11111
2023-12-12 5:47 ` Vít Smolík
2023-12-12 14:46 ` Vít Smolík
2023-12-12 19:09 ` stefan11111
2023-12-12 19:15 ` Vít Smolík
2023-12-12 20:30 ` stefan11111
2023-12-12 20:49 ` Vít Smolík
2023-12-12 21:16 ` stefan11111
2023-12-12 21:22 ` Vít Smolík
2023-12-12 21:55 ` stefan11111
2023-12-12 22:08 ` Vít Smolík
2023-12-12 22:25 ` stefan11111
2023-12-12 22:49 ` Vít Smolík
2023-12-12 22:54 ` stefan11111
2023-12-12 22:59 ` Vít Smolík
2023-12-12 23:31 ` stefan11111
2023-12-13 5:34 ` Vít Smolík
2023-12-13 8:27 ` stefan11111
2023-12-13 14:55 ` Vít Smolík
2023-12-13 15:57 ` stefan11111
2023-12-13 16:23 ` Vít Smolík
2023-12-13 18:46 ` stefan11111
2023-12-13 18:50 ` stefan11111
2023-12-13 19:21 ` Vít Smolík
2023-12-13 19:26 ` Vít Smolík
2023-12-13 19:29 ` stefan11111
2023-12-13 19:35 ` Vít Smolík
2023-12-13 19:44 ` stefan11111
2023-12-13 19:58 ` Vít Smolík
2023-12-13 20:05 ` stefan11111
2023-12-13 20:13 ` Vít Smolík
2023-12-13 20:25 ` stefan11111
2023-12-13 20:32 ` Vít Smolík
2023-12-13 22:19 ` stefan11111
2023-12-14 9:31 ` Vít Smolík
2023-12-14 13:49 ` Vít Smolík
2023-12-19 10:27 ` stefan11111
2024-01-23 14:54 ` stefan11111
2023-12-12 22:42 ` stefan11111
2023-12-12 22:44 ` Vít Smolík
2023-12-12 22:10 ` Jack [this message]
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=LFYC7647.3ROW7JOS.JRDHLRUW@IPYVZJZL.2AVZ7MPA.UTHEVXIP \
--to=ostroffjh@users.sourceforge.net \
--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