Bug 169305 - Add warning that user needs to restart to see transparent background
Summary: Add warning that user needs to restart to see transparent background
Status: RESOLVED FIXED
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 2.1
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: junior-jobs
: 202639 320001 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-08-17 10:46 UTC by Diederik van der Boor
Modified: 2018-03-17 13:14 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.8


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Diederik van der Boor 2008-08-17 10:46:42 UTC
Version:           2.1 (using 4.1.1 (KDE 4.1.0 (4.1 >= 20080722)) "release 27.1", KDE:KDE4:Factory:Desktop / openSUSE_11.0)
Compiler:          gcc
OS:                Linux (i686) release 2.6.25.11-0.1-pae

When the background of Konsole is set to transparent, it will only appear after restarting Konsole.

Steps to reproduce:
- start with an initial KDE configuration
- start Konsole
- enable desktop effects
- change the theme of Konsole, and configure transparency.

The transparency will only be applied after restarting Konsole.
Comment 1 Robert Knight 2008-08-17 18:55:03 UTC
Hi,

The actual limitation here is that if Konsole is started without desktop effects enabled then it must be restarted after desktop effects have been enabled for transparency to become available.  This is because Konsole sets up the the application differently depending on whether or not compositing is available on startup.  Trying to use the 'compositing enabled' setup when compositing is not available causes slowdown and visual glitches.  

If Konsole is started with compositing available then any transparency settings changes will take effect immediately.

In short, this is expected behavior.  
Comment 2 Diederik van der Boor 2008-09-03 21:02:56 UTC
Hi,

From your explaination I can understand it is difficult to change this. I do find it a bug. Isn't there any way Konsole can re-initialize itself?
Comment 3 Robert Knight 2008-09-04 00:43:56 UTC
> Isn't there any way Konsole can re-initialize itself? 

By shutting down the application and restarting, yes.  This will lose any information in the current tabs though.  If I thought this was an important bug then there might be some more complicated options I could explore but I don't think it is worth the effort.
Comment 4 Diederik van der Boor 2008-09-07 14:41:42 UTC
Ok.. If you don't plan to fix this, could you add some warning message to the transparency configuration instead? (""you need to restart Konsole to see transparency").

Example situationL
* When there is no compositing support support it warns to enable desktop effects. (little wish: can you add a hyperlink to open the kwin settings directly?)
* After compositing is enabled, the warning is gone, but you still don't see transparency. That confused me, and it took a while before I figured it out.

Thank you for your time
Comment 5 Diederik van der Boor 2008-09-07 14:42:54 UTC
(the second point is also the reason why I've posted this bug report in the first place)
Comment 6 Robert Knight 2008-09-07 15:05:44 UTC
> could you add some warning message to the transparency configuration instead? 

Yes, I can do that.
Comment 7 Jekyll Wu 2011-08-02 18:36:41 UTC
*** Bug 202639 has been marked as a duplicate of this bug. ***
Comment 8 Jekyll Wu 2011-09-09 09:17:15 UTC
Git commit 7d2f153ae60cdaf52f4b2ac1fc8ff7732791c07e by Jekyll Wu.
Committed on 08/09/2011 at 19:04.
Pushed by jekyllwu into branch 'master'.

Warn users they may need to restart konsole to see transparent background.

If desktop effect is enabled only after konsole has started, then
users need to restart konsole to see transparent background.

FEATURE: 169305
FIXED-IN: 4.8

M  +25   -5    src/EditProfileDialog.cpp

http://commits.kde.org/konsole/7d2f153ae60cdaf52f4b2ac1fc8ff7732791c07e
Comment 9 Ahmad Samir 2018-03-17 13:14:21 UTC
*** Bug 320001 has been marked as a duplicate of this bug. ***