Bug 710691 - [abrt] tsclient-2.0.2-7.fc13: strlen: Process /usr/bin/tsclient was killed by signal 11 (SIGSEGV)
Summary: [abrt] tsclient-2.0.2-7.fc13: strlen: Process /usr/bin/tsclient was killed by...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: tsclient
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b3a5ce84d687efdf94811d225f8...
: 662647 694547 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-04 04:16 UTC by HyunHo Jung
Modified: 2014-06-18 09:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-23 19:32:54 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (28.17 KB, text/plain)
2011-06-04 04:16 UTC, HyunHo Jung 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description HyunHo Jung 2011-06-04 04:16:10 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 28843 bytes
cmdline: tsclient
component: tsclient
Attached file: coredump, 31272960 bytes
crash_function: strlen
executable: /usr/bin/tsclient
kernel: 2.6.35.13-91.fc14.x86_64
package: tsclient-2.0.2-7.fc13
rating: 4
reason: Process /usr/bin/tsclient was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1307160808
uid: 501

How to reproduce
-----
1. fedora 14 + tsclient + XDMCP
2.
3.
Comment 1 HyunHo Jung 2011-06-04 04:16:12 UTC 
Created attachment 502944 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 16:39:18 UTC 
*** Bug 662647 has been marked as a duplicate of this bug. ***
Comment 3 abrt-bot 2012-03-20 16:39:26 UTC 
*** Bug 694547 has been marked as a duplicate of this bug. ***
Comment 4 Filipe Rosset 2012-04-23 19:32:54 UTC 
I'm closing this bug since tsclient was removed due to dead upstream and at least two superior alternatives (remmina and gnome-rdp)
Note You need to log in before you can comment on or make changes to this bug.