Bug 1005000 - "Open location" hangs on non-existent host
Summary: "Open location" hangs on non-existent host
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: totem
Version: 5.10
Hardware: i386
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Bastien Nocera
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-06 02:07 UTC by Vasiliy Sharapov
Modified: 2016-05-31 13:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-02 13:23:50 UTC
Target Upstream Version:

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

Description Vasiliy Sharapov 2013-09-06 02:07:56 UTC 
Version-Release number of selected component (if applicable):
RHEL5.10-Client-20130829.0
totem-2.16.7-7.el5_6.1

Steps to Reproduce: 


 1. Open a terminal
 2. Execute xvinfo
 3. Open Totem
 4. Select the "Movie" menu
 5. Select "Open Location..."
 6. In the "Open Location" dialog, enter the following URL: http://
    intranet.corp.redhat.com/mktg/video/ImagineChoice.ogg
 7. Select "Open"
...


Actual results: 
Dialog hangs if host part of URL is not online

Expected results:
Error message or something
Comment 1 RHEL Program Management 2014-03-07 13:56:55 UTC 
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Comment 2 RHEL Program Management 2014-06-02 13:23:50 UTC 
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).
Note You need to log in before you can comment on or make changes to this bug.