Bug 552076

Summary: [abrt] crash in vinagre-2.28.1-1.fc12
Product: [Fedora] Fedora Reporter: Dario Castellarin <req1348>
Component: vinagreAssignee: Bastien Nocera <bnocera>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: berrange, bnocera
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:7bca096cbb7b165447333cd10e4665f113d5439c
Fixed In Version: 2.28.1-2.fc12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-01-14 01:19:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Dario Castellarin 2010-01-03 22:40:38 UTC 
abrt 1.0.2 detected a crash.

Attached file: backtrace
cmdline: vinagre
component: vinagre
executable: /usr/bin/vinagre
kernel: 2.6.31.9-174.fc12.x86_64
package: vinagre-2.28.1-1.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
Comment 1 Dario Castellarin 2010-01-03 22:40:46 UTC 
Created attachment 381442 [details]
File: backtrace
Comment 2 Fedora Update System 2010-01-05 01:53:02 UTC 
vinagre-2.28.1-2.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/vinagre-2.28.1-2.fc12
Comment 3 Fedora Update System 2010-01-05 22:46:08 UTC 
vinagre-2.28.1-2.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update vinagre'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-0169
Comment 4 Fedora Update System 2010-01-14 01:19:18 UTC 
vinagre-2.28.1-2.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.