Re: [Evolution] Gdk-WARNING **: shmget failed!
- From: Markus Lang <mlang pp htv fi>
- To: George Farris <george gmsys com>
- Cc: Xavier Bestel <n0made free fr>, Ettore Perazzoli <ettore helixcode com>, evolution helixcode com
- Subject: Re: [Evolution] Gdk-WARNING **: shmget failed!
- Date: 20 Dec 2000 09:01:33 +0200
On 17 Dec 2000 21:41:38 -0800, George Farris wrote:
On 17 Dec 2000 12:34:23 +0100, Xavier Bestel wrote:
Le 2000.12.17 07:13:54 +0100, Ettore Perazzoli a écrit :
On 16 Dec 2000 20:35:57 -0500, Michael Rothwell wrote:
It appears to be Evolution's fault.
(Continuation to my previous post.)
In other words, I believe you can get the same result if you just run
enough GTK+/GNOME applications.
It's not the case Ettore, I'm pretty certain. And this
is no new behavior. Evo does really something weird
with shmem.
I wondering if this is related to the poor behavior of evolution on a
2.4 kernel. It takes 10 seconds just to get a compose window up and
running while under 2.2 it only takes about 2.
I've been running Evolution on a 2.4.0-test11. I had no slowdowns
running 0.6, and when I upgraded to 0.8 nothing changed.
Then I messed with the locales, edited /etc/environment, and whoops, Evo
slowed down MUCH. Every action from startup to compose took at least 5
seconds more than before... and no messages appeared in the terminal
from which I launched Evo.
And, as magically as the problem appeared, it went away. Maybe I updated
some component (libc6 2.2?) which did some bad things: Now I'm happy...
I run Debian unstable with daily "apt-get upgrade" and weekly "apt-get
dist-upgrade". I guess I've moved from woody to sid, haven't checked
that out yet..
Markus
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]