From: Willie Wong <wwong@Princeton.EDU>
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 13:48:04 -0500 [thread overview]
Message-ID: <20090206184804.GA10046@princeton.edu> (raw)
In-Reply-To: <fecdbac60902060957o3a9c582cle049cab7f178e451@mail.gmail.com>
On Fri, Feb 06, 2009 at 07:57:31PM +0200, Penguin Lover Arttu V. squawked:
> 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.
I lost your original mail, so sorry if this is not threaded properly.
Question: does the bug manifest itself only in KDE apps or in others?
Ctrl+c should also copy to clipboard in, say, firefox, if you have it
installed. Does it do the same thing? If yes: do you have another WM
installed and can you try running firefox under the other WM to see if
it behaves similarly? This should help figure out whether it is a KDE
issue or an X issue.
If you open an xterm, and hit Ctrl+c, does it reboot X (a long shot,
but if it does happens, it means something else is grabbing the event
and passing it up before the xterm sees it and passes it to the shell
in it)?
Also, what is in your ~/.xinitrc?
W
--
"If your're scattering a fly off an elephant, you don't worry about the mass of
the elephant. But since we're physicists, lets consider the alternate example.
In this case, we scatter the elephant off the fly."
~DeathMech, S. Sondhi. P-town PHY 205
Sortir en Pantoufles: up 791 days, 17:26
prev parent reply other threads:[~2009-02-06 18:45 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.
2009-02-06 18:48 ` Willie Wong [this message]
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=20090206184804.GA10046@princeton.edu \
--to=wwong@princeton.edu \
--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