Bug 521060 - Vinagre aborts when clicking on 'connect to'
Summary: Vinagre aborts when clicking on 'connect to'
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: vinagre
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-03 12:01 UTC by Espen Stefansen
Modified: 2009-09-04 00:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-04 00:46:07 UTC


Attachments (Terms of Use)

Description Espen Stefansen 2009-09-03 12:01:38 UTC
Description of problem:
Vinagre quits when clicking on 'connect to'. And it gives the following error.
** ERROR **: Could not load builder file: Duplicated object-ID «host_label» on line 371 (previously on line 65)
aborting..

When I start up vinagre, it also gives me the following errors, but the programs starts at least: 
** (vinagre:4587): CRITICAL **: vinagre_prefs_set_int: assertion `gconf_client_key_is_writable ( prefs->priv->gconf_client, key, NULL)' failed
** (vinagre:4587): CRITICAL **: vinagre_prefs_set_int: assertion `gconf_client_key_is_writable ( prefs->priv->gconf_client, key, NULL)' failed
** (vinagre:4587): CRITICAL **: vinagre_prefs_set_int: assertion `gconf_client_key_is_writable ( prefs->priv->gconf_client, key, NULL)' failed
** (vinagre:4587): CRITICAL **: vinagre_prefs_set_int: assertion `gconf_client_key_is_writable ( prefs->priv->gconf_client, key, NULL)' failed


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

How reproducible:
Every time

Steps to Reproduce:
1. Start vinagre
2. Click on 'connect to'
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Matthias Clasen 2009-09-03 12:37:25 UTC
Fixed in commit 66fbddf1528063b09e3163a2ff388c13c2b86b20 upstream. Will be fixed in the next release.


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