public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Bisect a problem going back months?
Date: Mon, 13 Sep 2010 07:38:10 -0700	[thread overview]
Message-ID: <AANLkTinSkXWV2raewT0pSuH--6-gHcn+GmHJDH4nMhQq@mail.gmail.com> (raw)

I'm wondering if there is a Gentoo way to bisect a bug that's crept
into my 64-bit Intel-based system (Intel process, motherboard and
graphics) over the last few months. Fundamentally when this bug
appears it generates a complete X crash back to the gdm login. My
suspicion is that it's related to the Gentoo push to use firefox-bin
and 32-bit Flash until some security issues were addressed but I don't
know that for sure.

Are there specific overlays I'd want to add using layman that would
allow me to get back to earlier versions of the Intel graphics driver,
64-bit Firefox and the now masked versions of Flash I was using say
2-3 months ago? At this point I don't know for sure that what I need
isn't in portage and just masked. I'll start reviewing that this
evening. This post was primarily just to figure out what my options
might be.

I've never used sunrise or sunset, etc. Maybe it's as easy as adding
one of those to layman and then bisecting my way through some
experiments to figure out where the problem first appeared?

Thanks,
Mark



             reply	other threads:[~2010-09-13 14:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13 14:38 Mark Knecht [this message]
2010-09-13 18:49 ` [gentoo-user] Bisect a problem going back months? Paul Hartman
2010-09-13 19:26   ` Mark Knecht
2010-09-13 19:42     ` Paul Hartman
2010-09-13 19:51       ` Mark Knecht
2010-09-13 20:44 ` [gentoo-user] " Nikos Chantziaras
2010-09-13 22:59   ` Mark Knecht

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=AANLkTinSkXWV2raewT0pSuH--6-gHcn+GmHJDH4nMhQq@mail.gmail.com \
    --to=markknecht@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