vino no longer updates screen except for XVideo fullscreen

Bug #358586 reported by Julian Lam on 2009-04-09
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-180 (Ubuntu)
Undecided
Unassigned
vino (Ubuntu)
Undecided
Unassigned
vnc4 (Ubuntu)
Undecided
Unassigned

Bug Description

After upgrading to Ubuntu Jaunty, vnc4server no longer updates the screen properly for connected clients. Oddly enough, watching VLC videos in full screen updates properly, but other than that, the screen is static.

Clients can still interact with the host computer, but they cannot see what they're doing.

Tested with both xvnc4viewer and vinagre

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: xvnc4viewer 4.1.1+xorg1.0.2-0ubuntu7
ProcEnviron:
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: vnc4
Uname: Linux 2.6.28-11-generic i686

Julian Lam (julian-lam) wrote :
Julian Lam (julian-lam) wrote :
Julian Lam (julian-lam) wrote :

Turns out I don't have vnc4server installed. Package in question is actually vino.

Changed in vnc4 (Ubuntu):
status: New → Invalid
summary: - vnc4server no longer updates screen except for XVideo fullscreen
+ vino no longer updates screen except for XVideo fullscreen
Julian Lam (julian-lam) on 2009-04-18
description: updated
summary: - vino no longer updates screen except for XVideo fullscreen
+ Regression! vino no longer refreshes screen except for XVideo fullscreen

do you have the same issue using an another server? that seems rather an xorg issue than a vino one

summary: - Regression! vino no longer refreshes screen except for XVideo fullscreen
+ vino no longer updates screen except for XVideo fullscreen
Julian Lam (julian-lam) wrote :

Thanks for the reply, Sebastien :)

Unfortunately, as I don't know how to set up a vnc server, I'm up the creek without a paddle. I rely on Ubuntu's preinstalled server, since it is setup to forward the appropriate X session upon connection.

An interesting development is that the vnc server works fine with compiz off, interestingly enough. Perhaps it is a compiz problem?

Sebastien Bacher (seb128) wrote :

could you try vncserver too?

Maciej Bęcławski (hakkatuka) wrote :

I can confirm this bug. It worked fine on Intrepid, problem started after upgrade to jaunty on a laptop with Nvidia 6150. I have not tried turning compiz off yet.

piojuls (m-cowan) wrote :

I can confirm this bug. I joined to report it. Also using Jaunty

I can confirm this too.
all Jaunty 64-bit, both nvidia 9500 & compiz enabled

Henrik Lewander (henq) wrote :

Same problem here with AMD64, Nvidia 9300 and Compiz.

Julian Lam (julian-lam) wrote :

This looks to be a bug affecting users with nvidia cards on the HOST computer. The problem seems to remain irrespective of the guest's setup...

If you're experiencing this bug report, can you re-post and tell us whether you're using the 180.xx hardware driver provided by Ubuntu, or if you've compiled the driver yourself from NVIDIA's website.

Also, please tell me whether you're running 32 or 64 bit on the host computer.

===

I am running the 180.51 driver downloaded from nvidia.com on an 8800GT. This is a 64-bit installation of Ubuntu Jaunty.

ok, additional information:
affected Host machines:
9500GT driver nvidia 180.44 prov. by ubuntu (64-bit Machine)
9600MGT driver nvidia 180.44 prov. by ubuntu (64-bit Machine)

Henrik Lewander (henq) wrote :

My host:
180.44 NVIDIA driver, ubuntu provided
64-bit installtion
Geforce 9300

Works fine with Visual Effects set to "none".
"Normal" and "Extra" give no screen updates.

Emilio Pozuelo Monfort (pochu) wrote :

Sounds like a driver bug, nvidia task added, closing the vino one.

Changed in vino (Ubuntu):
status: New → Invalid
Julian Lam (julian-lam) wrote :

Not necessarily. I vaguely remember that I ran into this problem while the host computer was still running Intrepid.

Julian Lam wrote:
> Not necessarily. I vaguely remember that I ran into this problem while
> the host computer was still running Intrepid.

Which was still nvidia? :)

Can you reproduce it if you switch to the nv driver?

Sebastien Bacher (seb128) wrote :

the issue is similar to bug #333564

Sebastien Bacher (seb128) wrote :
Julian Lam (julian-lam) wrote :

Hm, you're right. Looks like this bug is a duplicate.

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

Other bug subscribers