From: George Roberts <georoberts@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Xwindows stopped working. No errors in Xorg log file.
Date: Wed, 20 Jul 2005 23:27:27 -0600 [thread overview]
Message-ID: <42DF323F.6060900@gmail.com> (raw)
In-Reply-To: <200507202026.j6KKQdFS027557@robin.gentoo.org>
Daevid Vincent wrote:
>I tried to switch my window manager to Gnome and also XFCE (both worked fine
>before too) and that didn't solve the problem, so I don't think it's a KDE
>thing. But I have had KDE problems before as you suggest with other nvidia
>drivers.
>
>
>
>>-----Original Message-----
>>From: Richard Fish [mailto:bigfish@asmallpond.org]
>>Sent: Tuesday, July 19, 2005 10:18 PM
>>To: gentoo-user@lists.gentoo.org
>>Subject: Re: [gentoo-user] Xwindows stopped working. No
>>errors in Xorg log file.
>>
>>Daevid Vincent wrote:
>>
>>
>>
>>>I run a pretty stable system. I do however run ~x86 for KDE
>>>
>>>
>>and Gnome.
>>
>>
>>>Something changed recently in an "emerge -Davu world" or
>>>
>>>
>>"system" that
>>
>>
>>>causes X to not start anymore? The Xorg log below doesn't
>>>
>>>
>>have any errors or
>>
>>
>>>warnings or anything. There are no unresolved symbols as the
>>>
>>>
>>message says. I
>>
>>
>>>did notice that glib was updated, but the
>>>
>>>
>>"3242-glibc-2.3.5.log" doesn't say
>>
>>
>>>anything interesting. I ran "rm -rf /root/.revdep-rebuild.*;
>>>
>>>
>>revdep-rebuild
>>
>>
>>>-av" and that said I was golden, it didn't re-compile a
>>>
>>>
>>single thing.
>>
>>
>>>
>>>
>>>
>>>
>>One of the things we just discovered on this list is that
>>newer versions
>>of KDE are trying to use things like the Composite extension,
>>and it is
>>causing problems for some people (slowness was the previous case).
>>
>>Some things to try:
>>
>>1. Disable Composite.
>>2. Disable DRI.
>>3. Try the x.org "nv" driver instead of "nvidia".
>>
>>Depending upon whether and which one of those work, you will have a
>>place to start from on more debugging.
>>
>>-Richard
>>
>>
>>
>>
>>>I usually use 'meld' (x-windows) for my etc-update, so I do
>>>
>>>
>>have some files
>>
>>
>>>that need updating, but they don't seem that they should affect X??
>>>
>>>
>>>
>>>
>>>
>>Probably not...more likely opengl or composite is causing the
>>problem for X.
>>
>>
>>-Richard
>>
>>--
>>gentoo-user@gentoo.org mailing list
>>
>>
>>
>>
>
>
>
What login manager are you using Gdm or Xdm, I have been using Gdm
untill a while back and now after an update my X will not start using
gdm in my /etc/rc.conf. If I change it to Xdm in /etc/rc.conf or type
it in manually then X starts and I can get in Gnome. Changing the
Nvidia drivers has had no effect.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-21 5:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 21:57 [gentoo-user] Xwindows stopped working. No errors in Xorg log file Daevid Vincent
2005-07-20 2:17 ` Bob Sanders
2005-07-21 19:03 ` Daevid Vincent
2005-07-22 4:34 ` Rumen Yotov
2005-07-22 20:03 ` [gentoo-user] Xwindows stopped working. No errors in Xorg log file. [SOLVED] Daevid Vincent
2005-07-20 5:18 ` [gentoo-user] Xwindows stopped working. No errors in Xorg log file Richard Fish
2005-07-20 20:26 ` Daevid Vincent
2005-07-20 20:55 ` Daniel da Veiga
2005-07-21 5:27 ` George Roberts [this message]
2005-07-21 18:59 ` Daevid Vincent
2005-07-20 11:57 ` charlyghislain
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=42DF323F.6060900@gmail.com \
--to=georoberts@gmail.com \
--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