public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: gaim problems in 2.6.0
Date: Sun, 4 Jan 2004 19:44:24 +0100	[thread overview]
Message-ID: <20040104184424.GC344@elf.ucw.cz> (raw)
In-Reply-To: <20040104183712.GT1882@matchmail.com>

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.
> 
> Are you using debian(IIRC, you are, but maybe not on this machine?)?
> 
> Are you using the old version in debian stable?  Id suggest upgrading to the
> new version available in testing, or possibly unstable (probably only
> problems compiling on non-i386 arches).

Yep, this is debian testing machiene, and it looks up-to-date (with
respect to testing):

root@amd:~# apt-get install gaim
Reading Package Lists... Done
Building Dependency Tree... Done
Sorry, gaim is already the newest version.

Anyway... I was running as normal user. I should not be able to crash
machine no matter what software I run. (And vesafb pretty much points
to kernel fault).

									Pavel
-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

  reply	other threads:[~2004-01-04 18:43 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 [this message]
2004-01-04 20:01     ` Dr. David Alan Gilbert
2004-01-04 18:51 ` Peter Zijlstra
2004-01-04 19:57   ` David Ford
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=20040104184424.GC344@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.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