Bug 116333 - tsclient segmentation fault
Summary: tsclient segmentation fault
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: tsclient   
(Show other bugs)
Version: 1
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Mark McLoughlin
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-02-20 04:59 UTC by Christofer C. Bell
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version: 0.132-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-02-20 11:53:18 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Christofer C. Bell 2004-02-20 04:59:58 UTC
Description of problem:

tsclient segfaults when trying to open a connection using rdesktop
connecting to Windows XP using Windows Terminal Server as connection
method.  Using rdesktop by itself results in a successful connection.

Version-Release number of selected component (if applicable):

tsclient-0-0.120-1
rdesktop-1.3.1-0.1

How reproducible:

100% reproducable

Steps to Reproduce:
1. Install and patch rdesktop
2. Install tsclient
3. Run tsclient and enter in the IP address of a Windows XP machine
that has Remote Desktop Sharing enabled and otherwise works when using
rdekstop from the command line.
4. Click the 'Connect' button in tsclient and observe segmentation fault.
  
Actual results:

tsclient seg faults when attempting a connection.

Expected results:

User is presented with a Windows desktop / login.
Additional info:

Comment 1 Christofer C. Bell 2004-02-20 05:04:22 UTC
After installing tsclient-0.132-1.i386.rpm from the development tree
and then removing it, I am able to reinstall tsclient-0-0.120-1 from
the stable tree and the software works.

Comment 2 Mark McLoughlin 2004-02-20 11:53:18 UTC
Okay, marking as fixed in rawhide. Thanks


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