public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: mysql USE flag error
Date: Tue, 20 Oct 2009 15:48:41 +0200	[thread overview]
Message-ID: <200910201548.41375.wonko@wonkology.org> (raw)
In-Reply-To: <200910201530.03937.alan.mckinnon@gmail.com>

Alan McKinnon writes:

> KMail is fine on 4.3.2. I had issues with it randomly crashing when I
>  moved mails around, but that seems to have been sorted with the latest
>  version.

I also had some problems, when moving some thousands of IMAP mails, but I 
also had this with 3.5. I am using thunderbird for this, which is far more 
stable.

> Konqueror - well now, that's a different story:
> 
> - web shortcuts (gg:  wp:  etc) do not work. At all. Period.

They do here. I have configured them to have a blank as separator instead of 
the colon, maybe this is also set different in your setup? Oh my, I can't 
imagine to live without the shortcuts anymore. But then I said the same for 
mouse gestures, and had to live for half a year without.

> - randomly suddenly using 100% cpu when visiting forum sites (NO flash).
>  Only workaround is to kill konqueror

Did not see this (yet).

> - fish:// does not work

Had problems with 4.1 and 4.2, works with 4.3.2. What error do you get?

> - plugin support is awful. Forget AJAX, it does not work which counts out
> gmail and half the support sites I use at work

Do you have an example so I can try to reproduce this (I do not use gmail)?

	Wonko



  parent reply	other threads:[~2009-10-20 13:48 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-19  5:56 [gentoo-user] mysql USE flag error Mick
2009-10-19  6:17 ` Renat Golubchyk
2009-10-19  9:02   ` Mick
2009-10-19 11:05     ` [gentoo-user] " Remy Blank
2009-10-19 11:53       ` Mick
2009-10-19 21:42         ` Mick
2009-10-20  0:15           ` Neil Bothwick
2009-10-20  5:52             ` Mick
2009-10-20 10:24               ` Neil Bothwick
2009-10-20 10:47               ` Alex Schuster
2009-10-20 11:00                 ` Mick
2009-10-20 11:31                   ` Alex Schuster
2009-10-20 11:51                     ` Mick
2009-10-20 13:30                   ` Alan McKinnon
2009-10-20 13:44                     ` Mick
2009-10-20 13:59                       ` Alex Schuster
2009-10-20 14:02                         ` Mick
2009-10-20 14:04                         ` Dirk Heinrichs
2009-10-20 14:09                           ` Alan McKinnon
2009-10-20 14:14                             ` Neil Bothwick
2009-10-20 16:07                               ` Dirk Heinrichs
2009-10-20 14:02                       ` Alan McKinnon
2009-10-20 14:07                         ` Mick
2009-10-20 14:12                           ` Alan McKinnon
2009-10-20 14:13                           ` Neil Bothwick
2009-10-20 15:15                             ` Mick
2009-10-20 15:17                               ` Mick
2009-10-20 15:21                               ` Neil Bothwick
2009-10-20 15:54                                 ` Remy Blank
2009-10-20 13:48                     ` Alex Schuster [this message]
2009-10-20 14:06                       ` Alan McKinnon
2009-10-20 14:02                     ` Dirk Heinrichs

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=200910201548.41375.wonko@wonkology.org \
    --to=wonko@wonkology.org \
    --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