Bug 33423 - "click to focus" broken after sending window to new workspace
Summary: "click to focus" broken after sending window to new workspace
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kdebase   
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact: Aaron Brown
Depends On:
TreeView+ depends on / blocked
Reported: 2001-03-27 17:10 UTC by Ben Levenson
Modified: 2007-04-18 16:32 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-03-27 17:10:19 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Ben Levenson 2001-03-27 17:10:15 UTC
(wasn't sure if this went under kde-libs, kdebase, kde??)
Here is something peculiar I've noticed while using KDE:
1- Open a terminal in any workspace.
2- Open another terminal window in a different workspace.
3- Right click on the title bar of the first window and send it to the
workspace of the second window (is this making sense?)
4- Switch to the workspace that is now occupied by the both terminals.
5- The window that was just transferred will not accept keyboard focus
until you shade it and then unshade it.

This behavior isn't limited to the terminals.  It appears to be
independent of the application.  I've had it happen with the Konqueror
browser as well.  
Mouse input is not an issue.  If a web browser is sent to an occupied
workspace, it will appear to be working correctly as long
as you continue clicking on hyperlinks.  But you will not be able to
enter a URL until you shade and unshade the browser window.
It only happens when you send a window to a workspace that is occupied by
another window.  If you send it to an empty workspace, keyboard focus can
be given to the window as expected.

(The window can be focused as expected using the "window list."  
It also appears to be independent of the hardware, but I can provide info
if needed.)

Comment 1 Ben Levenson 2001-07-30 23:28:08 UTC
doing some bug housekeeping....
This was definitely an issue w/ 2.1.1-*
closing as CURRENTRELEASE since I haven't seen the 
issue in quite some time.

Note You need to log in before you can comment on or make changes to this bug.