Top and Bottom panels show up on a Locked Ubuntu Screen when a window pops up (e.g. Updates/aMSN chat window)

Bug #396411 reported by Georgios
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: xorg

Bug information included.

There are two aspects of the problem (and I consider it a security issue). Both happen on a Locked Screen in Jaunty 9.04. Whenever a new window needs to pop up (either an Ubuntu Update screen or an aMSN chat window...) the two panel bars show up, as they are on an unlocked screen, showing all running programs (inc. for example the currently open Firefox webpage title, or the name of the chatter).

Furthermore, whenever there is an aMSN notification (about someone logging in on msn, the whole desktop flashes (which includes the background image, the panels, but not the desktop icon contents as far as I have noticed), and after that the screen goes blank again.

The bug reveals "too much" about one's desktop. My only 'quick' workaround is going to tty1 after Locking, so that at least I get a terminal prompt, hoping people do not know how to go back to the X server screen.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: xorg 1:7.4~5ubuntu18
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-13-generic (buildd@vernadsky) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #45-Ubuntu SMP Tue Jun 30 19:49:51 UTC 2009
SourcePackage: xorg
Uname: Linux 2.6.28-13-generic i686

Revision history for this message
Georgios (g-michalakidis) wrote :
visibility: private → public
Revision history for this message
Kees Cook (kees) wrote :

Are you using compiz, metacity, KDE, or something else for your window manager?

Changed in xorg (Ubuntu):
status: New → Incomplete
Revision history for this message
Georgios (g-michalakidis) wrote :

I have all the predefined settings on gnome (i.e. compiz is enabled for my graphics adapter; happens to be ATI Mobility Radeon X1400 ) but I had the Appearance setting changed from Normal to Extra right after installing. I don't have any extras like Metacity. I do have KDE packages installed, as I have (sometimes) been using kAlarm

Bryce Harrington (bryce)
affects: xorg (Ubuntu) → xserver-xorg-video-ati (Ubuntu)
Kees Cook (kees)
affects: xserver-xorg-video-ati (Ubuntu) → compiz (Ubuntu)
Changed in compiz (Ubuntu):
importance: Undecided → Low
status: Incomplete → Confirmed
Revision history for this message
Georgios (g-michalakidis) wrote :

I can now confirm that the problem also exists on the 64-bit version of Jaunty.

I also (personally) think that is it Not a matter of Low importance; anything that could 'provide' secure data leakage to any unauthorised entity (anyone who without the account password can check out the bar contents by just looking at a locked system) is a Security matter, and ultimately, High.

Revision history for this message
Michael Imamura (zoogie) wrote :

Was just able to confirm this on Jaunty (i686) using:

sleep 10; xmessage Hello

Then locking the screen. After ten seconds, the panels emerge from the darkness.

Using compiz on Intel 915GM, so it's not just an ATI issue.

Revision history for this message
Georgios (g-michalakidis) wrote :

Did not quite expect this to be verified for NVIDIA as well... usually it's ATI + Ubuntu that have the loud bed fights.

Another reason why this is important; a Disturbing security matter, and frankly, something one would only expect from a Windows system.

Revision history for this message
Georgios (g-michalakidis) wrote :

Disabling Compiz (setting the Visual Effects to None on Appearance settings) prevents the panels from showing up on a locked terminal; this however is just a workaround and obviously not the solution...

Revision history for this message
Michael Imamura (zoogie) wrote :

Intrepid x86_64 is affected as well (just tried it using the xmessage test). ATI Radeon X1300 Pro. I guess I've never noticed it on Intrepid because the update notification window doesn't automatically open there.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Is this still an issue on Jaunty or Karmic?

Changed in compiz (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Michael Imamura (zoogie) wrote :

Yes. Just tested again (using the simple test above) on my Jaunty system.

Revision history for this message
Travis Watkins (amaranth) wrote :

Does this problem go away if you disable Unredirect Fullscreen Windows? You can do so from ccsm or by opening gconf-editor and going to /apps/compiz/general/screen0/options and unchecking unredirect_fullscreen_windows.

Revision history for this message
Michael Imamura (zoogie) wrote :

unredirect_fullscreen_windows was already turned off on my system. Toggling that option does not appear to change the outcome of the test, unfortunately.

Revision history for this message
Travis Watkins (amaranth) wrote :

Hrm, that's odd, I can only reproduce when I have unredirect fullscreen windows enabled. This is still on the X1300 card? I think the fix for this is actually DRI2 but I'm not sure if we have that for ATI even in karmic.

Revision history for this message
Michael Imamura (zoogie) wrote :

This was on my Jaunty system with the Intel 915GM. I just verified that turning off the "unredirect fullscreen windows" appears to solve the problem on my ATI X1300 system (still running Intrepid), so at least one system is fixed! :)

Kees Cook (kees)
Changed in compiz (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Travis Watkins (amaranth) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Karmic Koala. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help.

As I can no longer reproduce on karmic with this option disabled it is possible something else in the intel driver or in compiz solved the problem.

Changed in compiz (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Geomic (congogr) wrote :

Thanks for the help people, I cannot currently check this against the latest Beta as all my systems are on a very, Very specific stable installation for the next couple weeks.

Please, as some of you will probably have installed a Karmic test version (or are about to), check the bug against it BEFORE applying any changes to your system.

Just a comment: People seem to be working "blindly" on this one; meaning that we can 'assume' that something has fixed the issue with most chances being the new login system (acting as a built-in module rather than an application) [this however is just my PERSONAL view of it and might be wrong]. Let's check. I still would put this on TOP of a security-oriented bug list and would personally enjoy having an out-of-box ultimately secure system which is where Linux (and UNIXoids) get their most credits...

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to 'New'. Thanks again!

security vulnerability: yes → no
Changed in compiz (Ubuntu):
status: Incomplete → Invalid
tags: added: jaunty
Revision history for this message
Michael Imamura (zoogie) wrote :

I apologize for forgetting about this bug.

I actually upgraded to Karmic recently; I ran my test case and this bug appears to be fixed on my system. Thanks!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.