Bug 186819 - cannot alt-tab task-switch when presentation is run from fullscreen mode
Summary: cannot alt-tab task-switch when presentation is run from fullscreen mode
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: unspecified
Platform: openSUSE Unspecified
: HI normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
: 226181 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-03-10 21:32 UTC by Maciej Pilichowski
Modified: 2012-09-20 20:01 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
patch for opening chm files on openSUSE (955 bytes, patch)
2012-09-20 19:57 UTC, Bogdan Cristea 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2009-03-10 21:32:57 UTC 
Version:            (using KDE 4.2.1)
Installed from:    SuSE RPMs

1. run okular
2. open doc
3. switch to fullscreen
4. run presentation mode
5. try to alt-tab task switch

Notice you made the switch, but you went nowhere -- the presentation is still visible. The only possible switch is from<->to fullscreen. So you can have 20 apps running, but you can switch between 2 okular "mode-windows".
Comment 1 lucas 2009-03-12 15:31:41 UTC 
I have a feeling that KWin's unredirect fullscreen is to blame here. Although I was able to reproduce the problem once I have yet been able to reproduce it a second time, even after a restart of both KWin and Okular.
Comment 2 Martin Flöser 2010-02-10 21:19:43 UTC 
*** Bug 226181 has been marked as a duplicate of this bug. ***
Comment 3 Martin Flöser 2011-11-13 09:01:10 UTC 
is this still an issue, if yes please provide some information about your settings.
Comment 4 Bogdan Cristea 2012-09-20 19:57:18 UTC 
Created attachment 74055 [details]
patch for opening chm files on openSUSE
Comment 5 Bogdan Cristea 2012-09-20 19:59:27 UTC 
sorry, wrong bug, please ignore the attached patch
Comment 6 Thomas Lübking 2012-09-20 20:01:53 UTC 
Nevermind.
Reminds that the bug is dead old (4.2) and we lack a response for nearly a year now.