public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nilesh Govindrajan <contact@nileshgr.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Random segfaults with gnome
Date: Sat, 14 Jul 2012 12:04:49 +0530	[thread overview]
Message-ID: <50011309.9080406@nileshgr.com> (raw)
In-Reply-To: <5000F566.1020704@nileshgr.com>

On Sat 14 Jul 2012 09:58:22 AM IST, Nilesh Govindrajan wrote:
> On Sat 14 Jul 2012 09:54:00 AM IST, Nilesh Govindrajan wrote:
>> On Sat 14 Jul 2012 07:22:33 AM IST, Nilesh Govindrajan wrote:
>>> On Jul 13, 2012 10:37 PM, "Michael Hampicke" <gentoo-user@hadt.biz
>>> <mailto:gentoo-user@hadt.biz>> wrote:
>>> >
>>> > > Lately, ever since I installed gnome3 (3.2), a lot of things have
>>> gone
>>> > > unstable. Gnome crashes a lot and pulseaudio too, on every start
>>> (I see a
>>> > > segfault by the equalizer module).
>>> >
>>> > I had lots of graphics related problems with gnome3.2 - from render
>>> > errors to system freezes. So in a desperate move I unmasked gnome3.4
>>> > (from the overlay) and installed it. Installing (and maintaining)
>>> 3.4 is
>>> > a bit hairy, but all my problems have gone since that.
>>> >
>>> > So if recompiling with O2 does not help, and you don't mind bleeding
>>> > edge packages on your system, try 3.4
>>> >
>>>
>>> Already on gnome 3.4, unmasked from default portage, no overlay.
>>>
>>> Complete rebuild over with O2, still getting these errors:
>>>
>>> Http://bpaste.net/show/34934
>>>
>>
>> It seems I was using only gnome-shell 3.4 and did not update others.
>> Now I unmasked 3.4 completely (gnome-base/*, gnome-extra/*).
>> It's much more stable than 3.2, except for the two faults I pasted
>> above.
>>
>> Watching this thing now for crashes, will post update soon.
>>
>
> And boo.. it crashed just after writing the previous mail. Upto 3
> windows on the single workspace was good, with 4 it crashed. :|
>
> No faults reported in dmesg though.
>
> Is my video card incompetent?
>

I'm compelled to concolude that GNOME3 simply does not work on 4-5 year 
old hardware. Yeah, on a Dual Core 2 Ghz, 3 GB RAM, and i945 128 MB.

I'm back to my cozy place, KDE and alsaequal (instead of pulseaudio).

***thread closed***

-- 
Nilesh Govindrajan
http://nileshgr.com




  parent reply	other threads:[~2012-07-14  6:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13  2:34 [gentoo-user] Random segfaults with gnome Nilesh Govindrajan
2012-07-13  2:45 ` Canek Peláez Valdés
2012-07-13  2:59   ` Pandu Poluan
2012-07-13 12:41     ` Nilesh Govindrajan
2012-07-13 15:24       ` Pandu Poluan
2012-07-13 15:36         ` Hinnerk van Bruinehsen
2012-07-13 15:57           ` Nilesh Govindrajan
2012-07-13 15:55       ` Nilesh Govindrajan
2012-07-13 17:06 ` Michael Hampicke
     [not found]   ` <CAHgBc-sUqUZXRKmH2VTHrygV3FfxK5h+wMLrYaLS_65xxqGntA@mail.gmail.com>
2012-07-14  4:24     ` Nilesh Govindrajan
     [not found]       ` <5000F566.1020704@nileshgr.com>
2012-07-14  6:34         ` Nilesh Govindrajan [this message]
2012-07-14 16:55           ` Canek Peláez Valdés
2012-07-15  4:57             ` Nilesh Govindrajan
2012-07-15  5:22               ` Canek Peláez Valdés

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=50011309.9080406@nileshgr.com \
    --to=contact@nileshgr.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