RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1312427 - Vinagre segfault due memory allocation
Summary: Vinagre segfault due memory allocation
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vinagre
Version: 6.8
Hardware: i386
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Marek Kašík
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-26 16:42 UTC by Vaclav Ehrlich
Modified: 2016-11-01 10:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-01 10:33:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
vinagre segfault while connecting to VNC (6.83 KB, text/plain)
2016-02-26 16:42 UTC, Vaclav Ehrlich 		no flags Details
View All

Description Vaclav Ehrlich 2016-02-26 16:42:10 UTC 
Created attachment 1130863 [details]
vinagre segfault while connecting to VNC

Description of problem:
This was really strange segfault, because occurred in test case launched many times before. Virtual Machine had just two days uptime.
I've started Vinagre, connected to RDP machine and then I opened VNC connection to localhost (:1)
This crashed Vinagre. 
After that it was unable to connect any protocol.

Result from gdb are in attachment 

Version-Release number of selected component (if applicable):
vinagre-2.28.1-9.el6.i686

How reproducible:
Now investigating ...

Steps to Reproduce:
1.have RDP host prepared and local VNC server on port 5901
2.Open Vinagre
3.Connect to RDP host (RDP protocol, IP address, username and domain filled) 
4.Connect to VNC host (VNC procotol, :1 as 

Actual results:
Vinagre received signal SIGSEGV and ends

Expected results:
VNC connection is opened

Additional info:
Comment 2 Marek Kašík 2016-02-29 10:43:47 UTC 
It looks like the machine doesn't have enough free memory. Could you identify which application is consuming such amount of it? Is it Vinagre? (I don't see such behaviour with my quick test in a VM)
Comment 6 RHEL Program Management 2016-11-01 10:33:02 UTC 
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.
Note You need to log in before you can comment on or make changes to this bug.