public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david+hb@blue-labs.org>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Pavel Machek <pavel@ucw.cz>, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: gaim problems in 2.6.0
Date: Sun, 04 Jan 2004 14:57:49 -0500	[thread overview]
Message-ID: <3FF8703D.8070707@blue-labs.org> (raw)
In-Reply-To: <1073242263.3764.6.camel@twins>

# uname -r
2.6.1-rc1

# ps aux|grep gaim
david    12511  0.1  2.7 28392 14124 ?       S    Jan03   1:14 gaim

# gaim --version
Gaim 0.74

Not saying gaim is perfect... but it's at least running here.  
Notwithstanding the frequent quirks of preferences randomly changing on 
you..

-d

Peter Zijlstra wrote:

>Hi,
>
>every since I started using 2.6; currently running 2.6.1-rc1 gaim fails
>to start, all it does it dump core. I haven't spend time on looking
>where though.
>
>Peter Zijlstra
>
>On Sun, 2004-01-04 at 18:25, Pavel Machek wrote:
>  
>
>>Hi!
>>
>>I'm having bad problems with gaim... When I run gaim, my machine tends
>>to freeze hard (no blinking leds). I'm running vesafb -> that should
>>rule out X problems. Machine is rather strange pre-production athlon64
>>noteook, but I'm running 32-bit (on 32-bit kernel), and I can run gaim
>>under 2.4.X kernel.
>>
>>[Ugh, I was running with kgdb, but I recall same problem before, too.]
>>
>>Does anyone have similar problem?
>>								Pave
>>
>l
>  
>

  reply	other threads:[~2004-01-04 19:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-04 17:25 gaim problems in 2.6.0 Pavel Machek
2004-01-04 17:48 ` Justin Pryzby
2004-01-04 18:37 ` Mike Fedyk
2004-01-04 18:44   ` Pavel Machek
2004-01-04 20:01     ` Dr. David Alan Gilbert
2004-01-04 18:51 ` Peter Zijlstra
2004-01-04 19:57   ` David Ford [this message]
2004-01-04 19:55 ` Benjamin Henne
2004-01-04 20:01   ` Pavel Machek
2004-01-07 10:38   ` Matthias Urlichs

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=3FF8703D.8070707@blue-labs.org \
    --to=david+hb@blue-labs.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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