Version: 1.5 (using KDE 3.4.0%2C%2520Debian%2520Package%25204%253A3.4.0-0pre4%2520%283.1%29) Compiler: gcc%2520version%25203.3.5%2520%28Debian%25201%253A3.3.5-12%29 OS: Linux%2520%28i686%29%2520release%25202.6.11.7zing I normally have ~4 shell-tabs open, with 1-2 of them having transparent background and the others using vim-colors. When I switch from a vim-colored tab (or any non-transparent one, for that matter) to a transparent one for the first time, it not only flickers, but does a second tab-switch to the next console. If the next session is transparent as well, it will switch past that one, too. If I type anything while the background flickers, the text appears in the shell where the switching finally stops. Note that this whole bug only appears when I have freshly restored sessions(i.e. after kde-startup). I'm not sure if this really is the same as bug #66779, so I filed it as a new bug. I'm using konsole on kde 3.4 from debian alioth, but this behaviour already occured in 3.3. Cheers, Johannes
I can't reproduce. It would have been noticed if this was a bug since 3.3. How are you moving between sessions? Shortcut? This only happens on session-management?
> 21:45 ------- I can't reproduce. It would have been noticed if this was a > bug since 3.3. I tested again using a "fresh" user, and it showed up *sometimes*. My Procedure was: 1) Login 2) Open Konsole 3) Open 3 more tabs. 4) Set one tab to schema "Transparent, dark background" 5) Switch to non-transparent tab. 6) Logout 7) Login again 8) Use the keyboard-shortcut to switch to the transparent tab. The funny thing is, I could reproduce it sometimes, but not always. On my regular user, it happens every time I login. > How are you moving between sessions? Shortcut? Yes, I use the default shortcut Shift+Right/Left. > This only happens on session-management? Correct.
I tried another few times, and I could only reproduce it for certain as my regular user. Perhaps it has something to do with my config/system. It would be nice, if you could try once, if you can reproduce the bug using my previously given description. If this doesn't reproduce it, I think you can close the bug. Cheers, Johannes
Reopen if you can figure when it happens.