From: "Arttu V." <arttuv69@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Ctrl+c kills KOrganizer 4.2 when it should copy text
Date: Fri, 6 Feb 2009 19:57:31 +0200 [thread overview]
Message-ID: <fecdbac60902060957o3a9c582cle049cab7f178e451@mail.gmail.com> (raw)
In-Reply-To: <33DABA24-07F8-4424-BC98-9982ED6AD553@stellar.eclipse.co.uk>
On 2/6/09, Stroller <stroller@stellar.eclipse.co.uk> wrote:
>
> On 6 Feb 2009, at 12:36, Arttu V. wrote:
>> ...
>> Any insight on where to start looking for the problem (and especially
>> solution) is most welcome, including pointing out stupid newbie
>> mistakes.
>
> Have you run revdep-rebuild?
Yes to revdep-rebuild -i and emerge --depclean and emerge
@preserved-rebuild, with revdep having run last. But yes, it's always
good to check that as we are talking about Gentoo systems. :)
--
Arttu V.
next prev parent reply other threads:[~2009-02-06 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 12:36 [gentoo-user] Ctrl+c kills KOrganizer 4.2 when it should copy text Arttu V.
2009-02-06 13:06 ` Sebastian Günther
2009-02-06 14:12 ` Arttu V.
2009-02-06 14:33 ` Peter Humphrey
2009-02-06 15:38 ` Stroller
2009-02-06 17:57 ` Arttu V. [this message]
2009-02-06 18:48 ` Willie Wong
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=fecdbac60902060957o3a9c582cle049cab7f178e451@mail.gmail.com \
--to=arttuv69@gmail.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