Bug 552111 - tsclient RDP session crash after remote login
Summary: tsclient RDP session crash after remote login
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: tsclient
Version: 14
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Christopher Brown
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-04 04:05 UTC by Matt Woelfel
Modified: 2012-04-23 19:33 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-04-23 19:33:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Matt Woelfel 2010-01-04 04:05:55 UTC
Description of problem:
tsclient will immediately crash after logging into a windows xp remote desktop

Version-Release number of selected component (if applicable):
2.0.2-5.fc12

How reproducible:
100%

Steps to Reproduce:
1. VPN into my work's Cisco VPN server with NetworkManager
2. Connect to my workstation using tsclient with all the defaults pre-entered
3. View the rdesktop session start.  At the moment windows prompts me "Your password will expire..." due to work policy settings.  After clicking "later" the session crashes. 
  
Actual results:
[matt@localhost ~]$ tsclient 
** Message: Command: rdesktop -u <username> -p - -d nam -r sound -g 1280x1024 -f -P -T work <ipaddress> 
tsclient: symbol lookup error: /usr/lib64/tsclient/plugins/libtsc-default.so: undefined symbol: notify_is_initted

Expected results:
Have my workstation RDP session continue running

Additional info:

Comment 1 Joep Jansen 2010-05-06 12:14:55 UTC
This make tsclient useless for me.
I would say that a bug that causes a program to crash in a common situation deserves a high severity.
Is there a workaround (apart from reverting to an older version)?

Comment 2 Christopher Brown 2010-07-04 18:35:39 UTC
Thanks for the bug report.

Could you test directly using rdesktop from a command line and see whether this still happens?

Thanks

Comment 3 Matt Woelfel 2010-07-04 22:01:23 UTC
I have since changed jobs and do not have access to the same configuration as when I reported this bug, but I will still provide what help I can.

At the time, I was able to successfully use rdesktop without the crash that I experienced when using tsclient.

Comment 4 Joep Jansen 2010-07-06 12:25:30 UTC
When I bypass tsclient and use rdesktop directly everything works fine.

Comment 5 Bug Zapper 2010-11-04 01:55:05 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Matt Woelfel 2010-11-04 02:50:09 UTC
I installed tsclient-2.0.2-7.fc13.x86_64 (latest in the repository) under fedora 14.  The client has improved since last time I used it, though still crashes if using the '-f' flag.  Rebuilding the srpm for fedora 14 didn't make a difference.

I used NetworkManager's VPN client to log into my work's network and connected to my work machine via RDP.  Below is the command line output.  There are notes that are not part of the normal output.

[matt@localhost data]$ tsclient 
** Message: Command: rdesktop -u mwoelfel -p - -g 1280x1024 -f -P -T work <work ip> 
tsclient: symbol lookup error: /usr/lib64/tsclient/plugins/libtsc-default.so: undefined symbol: notify_is_initted
## note: the tsclient gui crashed, but rdesktop continued to run
## note: I closed rdesktop
[matt@localhost data]$ tsclient 
** Message: Command: rdesktop -u mwoelfel -p - -g 1280x1024 -f -P -T work <work ip> 
tsclient: symbol lookup error: /usr/lib64/tsclient/plugins/libtsc-default.so: undefined symbol: notify_is_initted
## note: same results as above
[matt@localhost data]$ tsclient 
** Message: Editing connection: work
** Message: Command: rdesktop -u mwoelfel -p - -g 1024x768 -P -T work <work ip> 
# note: closed rdesktop. tsclient is still running. reconnecting to work
** Message: Command: rdesktop -u mwoelfel -p - -g 1024x768 -P -T work <work ip> 
# note: closed rdesktop. tsclient is still running. going to try full screen again
** Message: Editing connection: work
** Message: Command: rdesktop -u mwoelfel -p - -g 1024x768 -f -P -T work <work ip> 
tsclient: symbol lookup error: /usr/lib64/tsclient/plugins/libtsc-default.so: undefined symbol: notify_is_initted
## note: tsclient gui crashed. rdesktop still working
[matt@localhost data]$

Comment 7 Michal Pomorski 2011-01-04 02:15:03 UTC
I would like to confirm the bug for Fedora 14.

Comment 8 ataraxia937 2011-02-21 22:34:18 UTC
I've figured out this bug. It's actually caused by something done during the build - it's a Fedora-specific bug.

There's currently a tweak in the spec (line 76) to force the use of the "--as-needed" flag during linking. It is this optimization which breaks tsclient, and removing this line from the spec and rebuilding the package fixes it.

I'm guessing this has to do with the package containing plugin modules, and the toolchain not doing the right thing with "--as-needed" on software which does explicit dlopen() calls, but that's just speculation on my part.

For reference, the relevant spec line is this one:

sed -i -e 's/ -shared / -Wl,-O1,--as-needed\0 /g' -e 's/    if test "$export_dy
namic" = yes && test -n "$export_dynamic_flag_spec"; then/      func_append comp
ile_command " -Wl,-O1,--as-needed"\n      func_append finalize_command " -Wl,-O1
,--as-needed"\n\0/' libtool

(I'm brand new to Fedora, so I don't know if I should be attaching a patch, or this is good enough, or if the proposed fix isn't even acceptable for some reason. Let me know if you need anything more.)

Comment 9 Taunus 2011-05-05 07:52:26 UTC
This bug also present on RHEL 6 and it can be tested by pressing some scandinavian character.

tsclient immediately crashes with:

tsclient: symbol lookup error: /usr/lib64/tsclient/plugins/libtsc-default.so: undefined symbol: notify_is_initted

Comment 10 Filipe Rosset 2012-04-23 19:33:57 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.