vinagre not updating changes on desktop - jaunty

Bug #367682 reported by bingo1912
4
Affects Status Importance Assigned to Milestone
vino (Ubuntu)
Incomplete
Low
Unassigned

Bug Description

Binary package hint: vinagre

when connecting to a host the desktop is drawn ok but if i select a menu it does not show on the remote machine only on the host

-- both machines are jaunty, the host was updated when 9.04 hit the update manager, the client was a clean install from jaunty rc then updated

client:
vinagre:
  Installed: 2.26.1-0ubuntu1
  Candidate: 2.26.1-0ubuntu1
  Version table:
 *** 2.26.1-0ubuntu1 0
        500 http://us.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status
server:
vino:
  Installed: 2.26.1-0ubuntu1
  Candidate: 2.26.1-0ubuntu1
  Version table:
 *** 2.26.1-0ubuntu1 0
        500 http://us.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/vinagre
Package: vinagre 2.26.1-0ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: vinagre
Uname: Linux 2.6.28-11-generic i686

Revision history for this message
bingo1912 (travis-wenks) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your bug report, what videocard and driver do you use?

Changed in vinagre (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue is similar to bug #358586

Revision history for this message
bingo1912 (travis-wenks) wrote :

result of lspci -v

00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
 Subsystem: Gateway 2000 Device 0366
 Flags: bus master, fast devsel, latency 0, IRQ 16
 Memory at d8100000 (32-bit, non-prefetchable) [size=512K]
 I/O ports at 1800 [size=8]
 Memory at c0000000 (32-bit, prefetchable) [size=256M]
 Memory at d8200000 (32-bit, non-prefetchable) [size=256K]
 Capabilities: <access denied>
 Kernel modules: intelfb

00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
 Subsystem: Gateway 2000 Device 0366
 Flags: bus master, fast devsel, latency 0
 Memory at d8180000 (32-bit, non-prefetchable) [size=512K]
 Capabilities: <access denied>

i dont know how to check the driver
i checked /etc/X11/xorg.conf it just says "configured monitor/driver/display"

thanks

Revision history for this message
bingo1912 (travis-wenks) wrote :

ok so i checked from 2 separate computers and with tight vnc and vinegre it appears to be a problem in vino not vinegre.

i am going to install tightvnc server and try connecting from vinegre

affects: vinagre (Ubuntu) → vino (Ubuntu)
Revision history for this message
bingo1912 (travis-wenks) wrote :

from the vino server

03:16.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)
 Flags: bus master, 66MHz, medium devsel, latency 248, IRQ 18
 Memory at dd000000 (32-bit, non-prefetchable) [size=16M]
 Memory at d0000000 (32-bit, prefetchable) [size=128M]
 [virtual] Expansion ROM at de000000 [disabled] [size=128K]
 Capabilities: <access denied>
 Kernel driver in use: nvidia
 Kernel modules: nvidia, nvidiafb

the previous post was from a client

Revision history for this message
bingo1912 (travis-wenks) wrote :

i can confirm after installing and configuring x11vnc vinagre does connect and update

Revision history for this message
koshari (holto2go) wrote :

i can confirm this fault on 9.04 , running from my desktop to my notebook or the other way, both machines nvidia restricted drivers.

Revision history for this message
koshari (holto2go) wrote :

it appears to be the vino server as tightvnc from a win box has the same problem.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the nvidia refresh issue is bug #353126

Revision history for this message
Christoph Langner (chrissss) wrote :

Why is this bug a dupe of bug #372384? Bug #372384 is a duplicate of this one and is filed under the wrong package. vino is the culprit and not vinagre since other vnc clients have the same problem connecting to vino.

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.