Bug 521492 - vinagre freezes after double-click on one of "nearby hosts"
Summary: vinagre freezes after double-click on one of "nearby hosts"
Keywords:
Status: CLOSED NEXTRELEASE
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-06 13:49 UTC by Tomasz Torcz
Modified: 2009-09-18 20:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-18 18:37:23 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Priority Status Summary Last Updated
GNOME Bugzilla 581817 None None None Never

Description Tomasz Torcz 2009-09-06 13:49:45 UTC 
Description of problem:
When I doubleclick one of zeroconf bookmarks in left panel, Vinagre freezes and cease to accept any further input. Console output is following:

% vinagre

(vinagre:32127): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(vinagre:32127): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

** (vinagre:32127): CRITICAL **: vinagre_bookmarks_entry_get_node: assertion `VINAGRE_IS_BOOKMARKS_ENTRY (entry)' failed

** (vinagre:32127): CRITICAL **: fav_panel_activated: assertion `vinagre_bookmarks_entry_get_node (entry) == VINAGRE_BOOKMARKS_ENTRY_NODE_CONN' failed


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

How reproducible:
Always
Comment 1 Tomasz Torcz 2009-09-18 18:37:23 UTC 
According to: http://mail.gnome.org/archives/desktop-devel-list/2009-September/msg00111.html it is already fixed upstream. Should be working in Fedora with next build.
Comment 2 Bastien Nocera 2009-09-18 20:46:13 UTC 
Already built actually, see:
http://koji.fedoraproject.org/koji/buildinfo?buildID=132652
Note You need to log in before you can comment on or make changes to this bug.