Bug 51477 - Strange transparency issue with multiple X servers
Summary: Strange transparency issue with multiple X servers
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 0.1
Platform: Mandrake RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-03 23:44 UTC by Vince Veselosky
Modified: 2003-11-08 21:25 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vince Veselosky 2002-12-03 23:44:31 UTC
Version:           1.1.3 (using KDE KDE 3.0.3)
Installed from:    Mandrake RPMs
OS:          Linux

This is one of those things that you will almost never see. I am running KDE 3 (Mandrake 9 w/updates) on a laptop, and KDE 2.2.2 (Mandrake 8.2 w/updates) on a desktop which is serving XDM. I start the laptop in runlevel 5 and log in to the local system on the default display :0. Then I open a new X session using "X :1 -query blah" to log into the desktop. The displays are running on vt7 and vt8 respectively, and the X servers may run as the same user or different users with the same effect.

When I set the konsole scheme to anything transparent on display :1 (the desktop being accessed remotely), the 'background' that shows through is crud from display :0 (the laptop local display). Not the background from display :0, but a garbled version of whatever is showing on the screen. (Unless the konsole window is maximized, in which case bg is black. This is a bit bizarre.)

When I reverse the relationships, logging into the laptop remotely from the desktop, the transparent background seems not to work at all, it just looks black. Hmm.

The hardware involved is ATI Rage Mobility on a Sony VAIO Laptop. Don't know if that matters.

I wonder if perhaps there are security concerns, since user2 can read (part of) the screen of user1. Probably not a big deal, but still interesting.

So there's something interesting for you guys to look at!
Comment 1 Stephan Kulow 2003-11-08 21:25:30 UTC
that was fixed somewhen before 3.1 I think