Bug 80116 - when pasting in konsole with shortcutkeys, pasting happens in editor window instead
Summary: when pasting in konsole with shortcutkeys, pasting happens in editor window i...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: general (show other bugs)
Version: SVN
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2004-04-22 12:05 UTC by Joffen
Modified: 2018-10-21 05:05 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joffen 2004-04-22 12:05:08 UTC
Version:           3.0.3 (using KDE KDE 3.2.0)
Compiler:          gcc 3.2.2 
OS:          Linux

To reproduce:
1. open kdevelop
2. open an arbitrary document
3. open the konsole (in kdevelop)
4. assure the the konsole has focus
5. make sure there is something in the clipboard, and press ctrl+v or shift+ins
6. watch in horror as the text is pasted in the editor window instead of the konsole

Note: Some similarities with to bug #69583
Comment 1 Jens Dagerbo 2004-04-22 12:58:20 UTC
I couldn't reproduce ctrl+v, it is always sent to the terminal on my system (it doesn't work in a standalone konsole either). I can reproduce it with shift+ins however.

I can also reproduce the problem with Kate (which also has an embedded terminal).

I have no idea where the responsibility for this problem lies.
Comment 2 Joffen 2004-04-22 15:50:16 UTC
> I couldn't reproduce ctrl+v
It seems I was to hasty with this one. ctrl+v does not paste anywhere. Instead it outputs "^V" to the konsole (when pressed twice).

Shift+ins still produces the bug, though.

Comment 3 Matt Rogers 2004-12-12 05:40:28 UTC
confirmed with KDevelop 3.1.90. I use focus follows mouse though, so i'll test to see if focus policy has anything to do with it.
Comment 4 Matt Rogers 2004-12-12 05:41:31 UTC
focus policy does nothing. probably a KMDI bug.
Comment 5 Anders Lund 2004-12-12 19:31:13 UTC
Why are kwrite-devel on the CC list for this? It is not a bug in kate, or katepart, and not valid for either (katepart have no konsole obviously, and the bug does not happen in kate.) Please remove us.
Comment 6 Jens Dagerbo 2004-12-12 20:26:24 UTC
Anders,

I added kwrite-devel because:

1. You have the same scenario in Kate: katepart in main area, konsolepart in a KMDI toolview and the bug did happen in Kate back in April (see comment #1) and still did in KDE-3.3.0

2. KMDI issues (if this is one, dunno) used to go to kwrite-devel (did this change?)

If this bug isn't in Kate-HEAD, do you know how and when you fixed it?
Comment 7 Anders Lund 2004-12-12 20:35:57 UTC
Hm I was wrong - with shift-ins the bug is inded in akte as well.
Comment 8 Anders Lund 2004-12-12 20:47:08 UTC
KateView does disable the accel for its action when it looses focus, so this is more likely a bug in KAccel or thereabout.

The code in KateView looks like this:
void KateView::slotLostFocus()
{
  m_editActions->accel()->setEnabled( false );
}
Comment 9 lexual 2010-01-23 07:31:07 UTC
Is this still relevant to recent KDE version?
If not please close the bug.

Thanks,

Lex.
Comment 10 Andrew Crouthamel 2018-09-20 22:11:30 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 11 Andrew Crouthamel 2018-10-21 05:05:21 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!