Bug 674284

Summary: [abrt] vinagre-2.31.4-1.fc14: Process /usr/bin/vinagre was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Rohit Sarpotdar <rohit.n.sarpotdar>
Component: vinagreAssignee: Bastien Nocera <bnocera>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: berrange, bnocera
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:1c66f34989eb0b84adfac44a2786dc769fcae583
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 17:24:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Rohit Sarpotdar 2011-02-01 09:48:45 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: vinagre
comment: I did not check the active session on 'remote desktop viewer' for around 5 minutes. 
component: vinagre
crash_function: IA__gtk_ui_manager_new_merge_id
executable: /usr/bin/vinagre
kernel: 2.6.35.10-74.fc14.x86_64
package: vinagre-2.31.4-1.fc14
rating: 4
reason: Process /usr/bin/vinagre was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1296553358
uid: 500

How to reproduce
-----
1.Session to vnc was open
Comment 1 Rohit Sarpotdar 2011-02-01 09:48:48 UTC 
Created attachment 476345 [details]
File: backtrace
Comment 2 Rohit Sarpotdar 2011-02-02 09:40:02 UTC 
Package: vinagre-2.31.4-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Server was unreachable
2.Tried to connect to server ip. 
3.Screen went blank for a while
4.Remote desktop viewer application crashed


Comment
-----
If you try to connect to unreachable server, it crashes.
Comment 3 abrt-bot 2012-03-20 17:24:10 UTC 
Backtrace analysis found this bug to be similar to bug #701850, closing as duplicate.

Bugs which were found to be similar to this bug: bug #656331, bug #674542, bug #701850

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 701850 ***