Bug 222651 - vino's framebuffer is corrupted
Summary: vino's framebuffer is corrupted
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: vino
Version: 5
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-01-15 14:57 UTC by Adam Tkac
Modified: 2013-04-30 23:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-02-05 13:01:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Look at this "nice" licq background (318.42 KB, image/png)
2007-01-15 14:57 UTC, Adam Tkac
no flags Details
I tried move with gnome terminal and result is really interesting... (435.37 KB, image/png)
2007-01-15 14:58 UTC, Adam Tkac
no flags Details

Description Adam Tkac 2007-01-15 14:57:26 UTC
Description of problem:
I'm using vino to export my gnome screen but some apps are really corrupted. I'm
going to attach some screenshots. I think some problem is in fc6, devel and RHEL-5

Version-Release number of selected component (if applicable):
$ rpm -q vino
vino-2.13.5-2.2

How reproducible:
always

Steps to Reproduce:
1. configure your vino session
2. join to vino session with vncviewer (from vnc package)
3. start for example licq or gnome terminal

Actual results:
some applications have corrupted background

Expected results:
apps look like in normal desktop

Additional info:
Framebuffer isn't updated correctly. I think it is caused by vino, not with
vncviewer

Comment 1 Adam Tkac 2007-01-15 14:57:26 UTC
Created attachment 145578 [details]
Look at this "nice" licq background

Comment 2 Adam Tkac 2007-01-15 14:58:26 UTC
Created attachment 145579 [details]
I tried move with gnome terminal and result is really interesting...

Comment 3 Adam Tkac 2007-02-05 13:01:37 UTC
I have upgraded my system to fc6 and output looks fine. I don't need fix this
problem in fc5 -> closing nextrelease


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