Bug 489814 – Vinagre fails to enter full screen properly

Bug 489814 - Vinagre fails to enter full screen properly

Summary:	Vinagre fails to enter full screen properly

Status:	CLOSED UPSTREAM

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	vinagre (Show other bugs)
Sub Component:
Version:	10
Hardware:	All Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bastien Nocera
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2009-03-11 19:50 EDT by Jonathan Underwood
Modified:	2009-05-07 21:52 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2009-05-07 21:52:05 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
vinagree set to use full screen (220.41 KB, image/png) 2009-03-11 20:05 EDT, Jonathan Underwood	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
GNOME Desktop	580679	None	None	None	Never

Groups: None (edit)

Description Jonathan Underwood 2009-03-11 19:50:03 EDT

Description of problem:
Often when I ask vinagre to switch to full screen mode, it incorrectly sizes the window. In the attached screen shot you can still see a chunk of the local machine desktop (i.e. the top gnome bar), and the second gnome bar is the top of the remote vnc session desktop. This happens a lot.

Version-Release number of selected component (if applicable):
vinagre-2.24.2-1.fc10.x86_64

How reproducible:
intermittent.

Comment 1 Jonathan Underwood 2009-03-11 20:05:38 EDT

Created attachment 334875 [details]
vinagree set to use full screen

Comment 2 Bastien Nocera 2009-05-07 21:52:05 EDT

Apparently a known upstream bug:
http://bugzilla.gnome.org/show_bug.cgi?id=580679

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