Bug 208983 - With compiz enabled on a server, VNC is broken
Summary: With compiz enabled on a server, VNC is broken
Alias: None
Product: Fedora
Classification: Fedora
Component: compiz
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Kristian Høgsberg
QA Contact:
: 228063 (view as bug list)
Depends On:
Blocks: 213565
TreeView+ depends on / blocked
Reported: 2006-10-02 20:42 UTC by Zack Cerza
Modified: 2018-04-11 16:33 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 567410 (view as bug list)
Last Closed: 2009-07-14 17:08:28 UTC
Type: ---

Attachments (Terms of Use)

Description Zack Cerza 2006-10-02 20:42:33 UTC
Description of problem:
Compiz being enabled on an X server breaks VNC.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Enable compiz on machine A
2. VNC into machine A from machine B
3. Move a window, open a menu... something like that
Actual results:
Changes are reflected on the screen of machine A, but not machine B.

Expected results:
Changes are reflected on the screens of both machine A and machine B.

Additional info:
05:00.0 VGA compatible controller: ATI Technologies Inc Radeon R350 [Radeon 9800

Comment 1 Andy Lawrence 2006-10-31 17:17:01 UTC
Exact same with:


Comment 2 Bojan Smojver 2006-12-01 00:07:55 UTC
On FC6, compiz actually refuses to start inside VNC, claiming that there is no
composite extension. Is it possible to change X11 startup scripts so that if
compiz doesn't start, metacity is attempted instead?

Comment 3 Tomasz Torcz 2006-12-26 21:31:55 UTC
GNOME VNC server (vino) also doesn't work. VNC client sees only black screen.

Comment 4 Matěj Cepl 2007-10-02 18:20:53 UTC
Zack, sorry, for the silly boiler-plate message, but here we are:

Since this bugzilla report was filed, there have been several updates, which may
have resolved this issue. Users who have experienced this problem are encouraged
to upgrade their system to the latest version of their distribution available.

Please, if you experience this problem on the up-to-date system, let us now in
the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as

Comment 5 Andy Lawrence 2007-10-03 02:06:48 UTC
I have all updates loaded, this is still broken on 6 separate PCs.

Comment 6 Matěj Cepl 2007-11-01 11:20:15 UTC
*** Bug 228063 has been marked as a duplicate of this bug. ***

Comment 7 Matěj Cepl 2008-01-23 23:22:49 UTC
Zack, haven't you promised me something?

Comment 8 Bojan Smojver 2008-01-24 00:36:15 UTC
I worked around my problem by having this in ~/.vnc/xstartup:

# Uncomment the following two lines for normal desktop:
export WINDOW_MANAGER=metacity
exec /etc/X11/xinit/xinitrc

Comment 9 Matěj Cepl 2008-01-24 16:57:24 UTC
OK, you have persuaded me.

Comment 10 Zack Cerza 2008-01-24 17:04:40 UTC
Sorry Matej,

The other day I decided it was time to upgrade to rawhide, since I'd heard it
wasn't too bad.

It is. Intel driver is broken.


Comment 11 Matěj Cepl 2008-01-25 00:15:16 UTC
If only Intel driver ... :-)

Comment 12 Bug Zapper 2008-05-14 02:23:43 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:

Comment 13 Adam Gibson 2009-06-01 04:33:28 UTC
I just experienced this when upgrading from FC10 to FC11-preview and rawhide(20090531 which will become FC11.

In FC10 the 'nvidia' driver worked with vino and compiz.  Compiz works in FC11 but vino server just shows the initial screen to the client when you connect remotely (I am using RealVNC on windows to connect to FC11).

[static@leeloo ~]$ rpm -q vino compiz xorg-x11-server-Xorg

Latest nvidia driver at this time:

Comment 14 Bug Zapper 2009-06-09 22:18:39 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 15 Bug Zapper 2009-07-14 17:08:28 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 16 Walter Neumann 2010-02-22 00:11:31 UTC
I confirm this bug in FC12. Using vnc to access remote machine running vino, the screen is not updated in the vnc viewer window if remote machine has desktop effects enabled. No problem without desktop effects.

Comment 17 Matěj Cepl 2010-02-22 11:53:30 UTC
(In reply to comment #16)
> I confirm this bug in FC12. Using vnc to access remote machine running vino,
> the screen is not updated in the vnc viewer window if remote machine has
> desktop effects enabled. No problem without desktop effects.    

If both macines have supported versions of Fedora (i.e., >= 11), please file a new bug for the issue. Attach also your X server config file (/etc/X11/xorg.conf, if available), output of the dmesg command, system log (/var/log/messages), and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Note You need to log in before you can comment on or make changes to this bug.