From: Daniel Troeder <daniel@admin-box.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ~amd64 : X11 (?) crashing
Date: Sun, 15 Nov 2009 09:15:43 +0100 [thread overview]
Message-ID: <1258272943.9028.6.camel@maya.local> (raw)
In-Reply-To: <4AFF45FB.4000102@xunil.at>
On Sun, 2009-11-15 at 01:06 +0100, Stefan G. Weichinger wrote:
> greets ...
>
> As mentioned lately in another thread I moved to amd64 unstable last week.
>
> So far OK ... but:
>
> I see X11 crashing repeatedly but I don't have a clue what component
> might be the reason.
>
> Sometimes my gnome-session (2.28) works for hours, sometimes for minutes.
>
> It crashes when starting a new program like opera, firefox, thunderbird,
> amarok, ... something ....
>
> I don't have a clear way to reproduce the crash and the logs don't tell
> me anything.
>
> -->
>
> I rebuilt xorg-server, xorg-drivers, xf86-input-* .... opera, etc
>
> I re-emerged @system overnight, ran revdep-rebuild, lalefixer etc (yeah,
> I know, X11 isn't @system ... but just to do the basement right)
>
> I use nvidia-drivers here, so I also did "eselect opengl ..." again.
>
> I erased xorg.conf and redid it via nvidia-xconfig ... and changed it to
> use absolute coordinates, as the xorg-server-1.7 seems to have issues
> with "LeftOf" ...
>
> Additional info:
>
> I use compiz and xinerama ... two monitors ... might add some problems.
> The two monitors are the reason for still using xorg.conf with
> xorg-server-1.7.x (maybe there's a better solution? I don't know yet).
>
> bugs.gentoo.org doesn't show anything describing my issues, I hesitate
> to file a bug as long as the symptoms are that vague ...
>
> Some clues, someone?
>
> There were NO such crashes before moving to full ~amd64, I ran
> xorg-server-1.6 before (mixing stable and unstable ...).
>
> Simply going back to xorg-server-1.6 ?
>
> Thanks a lot, Stefan.
I might have a similar problem, that is definitely related to the second
monitor and power management. If you disconnect your 2nd monitor, do the
crashes still occur? But maybe this isn't related, because I have a
Radeon card... just a lucky guess...
Daniel
next prev parent reply other threads:[~2009-11-15 10:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-15 0:06 [gentoo-user] ~amd64 : X11 (?) crashing Stefan G. Weichinger
2009-11-15 8:15 ` Daniel Troeder [this message]
2009-11-15 13:46 ` Stefan G. Weichinger
2009-11-15 8:45 ` Alan McKinnon
2009-11-15 13:54 ` Stefan G. Weichinger
2009-11-15 15:00 ` Alan McKinnon
2009-11-15 16:06 ` Stefan G. Weichinger
2009-11-17 21:07 ` Stefan G. Weichinger
2009-11-17 22:40 ` Stefan G. Weichinger
2009-11-18 16:17 ` Peter Humphrey
2009-11-22 20:59 ` Stefan G. Weichinger
2009-11-22 22:24 ` Alan McKinnon
2009-11-23 7:20 ` Stefan G. Weichinger
2009-11-23 8:46 ` Alan McKinnon
2009-11-23 11:14 ` Stefan G. Weichinger
2009-11-23 13:46 ` Stefan G. Weichinger
2009-11-24 9:17 ` Stefan G. Weichinger
2009-11-24 12:26 ` Helmut Jarausch
2009-11-24 20:54 ` Stefan G. Weichinger
2009-11-26 21:05 ` daid kahl
2009-11-26 21:44 ` Stefan G. Weichinger
2009-11-26 21:50 ` Stefan G. Weichinger
2009-11-30 16:10 ` Stefan G. Weichinger
2009-11-30 16:41 ` Alan McKinnon
2009-11-30 18:07 ` Stefan G. Weichinger
2009-11-30 18:41 ` Alan McKinnon
2009-11-30 21:53 ` Stefan G. Weichinger
2009-12-02 12:56 ` Stefan G. Weichinger
2009-12-07 13:58 ` Stefan G. Weichinger
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=1258272943.9028.6.camel@maya.local \
--to=daniel@admin-box.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