Bug 674542 - [abrt] vinagre-2.31.4-1.fc14: Process /usr/bin/vinagre was killed by signal 11 (SIGSEGV)
Summary: [abrt] vinagre-2.31.4-1.fc14: Process /usr/bin/vinagre was killed by signal 1...
Keywords:
Status: CLOSED DUPLICATE of bug 701850
Alias: None
Product: Fedora
Classification: Fedora
Component: vinagre
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ed229122e9581543578d59bce5b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-02 12:47 UTC by Rohit Sarpotdar
Modified: 2012-03-20 17:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 17:24:26 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (32.16 KB, text/plain)
2011-02-02 12:47 UTC, Rohit Sarpotdar
no flags Details

Description Rohit Sarpotdar 2011-02-02 12:47:11 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: vinagre
comment: I did not login to any server just had opened connect dialog. And while I was doing something else, like typing command on terminal, it crashed in the background
component: vinagre
crash_function: IA__gtk_action_group_list_actions
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: 1296650735
uid: 500

How to reproduce
-----
1.Remote desktop viewer was open 
2.It crashed after 5 min.
3.

Comment 1 Rohit Sarpotdar 2011-02-02 12:47:15 UTC
Created attachment 476556 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-20 17:24:26 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 #674284, bug #701850

This comment is automatically generated.

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


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