Closing this bug as tsclient is no longer in the Ubuntu archives (starting from
Oneiric).
The default remote desktop client in Ubuntu is now Remmina.
** Changed in: tsclient (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
B
@robbert: s/Linux/Ubuntu/ ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/8422
Title:
Error message on ending VNC session
To manage notifications about this bug go to:
https://bugs.launch
Ken Sharp (kennybobs) wrote on 2011-09-27:
"Still present in Natty"
Of course it's still present. What did you expect? This bug to be fixed?
Of course not. In the Linux world bugs it's common to not fix bugs. Just
live with it or use another operating system. It's as easy as that.
--
You receive
Still present in Natty
** Changed in: tsclient (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/8422
Title:
Error message on ending VNC session
If somone could confirm this bug happens on Maverick it would be great.
I checked out the patch and it doesn't apply. Marking as patch-
needswork
** Tags added: patch-needswork
** Changed in: tsclient (Ubuntu)
Status: Confirmed => Incomplete
--
Error message on ending VNC session
https:
Same error here on ubuntu karmic, 9.10
Running on an atom system with rdesktop
This is the exact error message:
WARNING: Remote desktop does not support colour depth 24; falling back to 16
X Error of failed request: BadAtom (invalid Atom parameter)
Major opcode of failed request: 23 (X_GetSelecti
9.04 / Tsclient 0.150 still seems to produce the "error dialog" box
whenever there is any output from rdesktop.
Switching to RDPv5 reduced the number of lines being spit out by
rdesktop, but I can not reduce them to zero: "Autoselected keyboard map
en-us" still remains (connecting to a german wind
By default TSClient uses the protocol "RDP". This gives me an error
everytime. After switching the protocol from "RDP" to "RDPv5" I haven't
encountered anymore problems. I've been using "RDPv5" for more than a
month now and everything works flawlessly.
--
Error message on ending VNC session
https
Present in Ubuntu 9.04 too. Tsclient 0.150
--
Error message on ending VNC session
https://bugs.launchpad.net/bugs/8422
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
This bug is still present in Ubuntu 9.04 RC.
** Attachment added: "Error.png"
http://launchpadlibrarian.net/25830161/Error.png
--
Error message on ending VNC session
https://bugs.launchpad.net/bugs/8422
You received this bug notification because you are a member of Ubuntu
Bugs, which is a dir
Still seems to be present in tsclient 0.150 in Hardy Heron 8.0.4, as of
30-July-2008.
Thanks for looking into this.
-Kevin
--
Error message on ending VNC session
https://bugs.launchpad.net/bugs/8422
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct su
Can anyone confirm whether this problem is related to the problem in
tsclient where a custom keyboard layout sends the wrong keys to the
Windows server?
To reproduce (in Ubuntu Hardy beta using US english settings):
Go to System > Preferences > Keyboard
click Layouts tab and then click Layout Opti
** Attachment added: "vncviewer disconnect error (via tsclient)"
http://launchpadlibrarian.net/12092026/Screenshot-VNC%3A%20x11-1.png
--
Error message on ending VNC session
https://bugs.launchpad.net/bugs/8422
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Not sure about Hardy but I still encounter this issue (related to the
keyboard map) in Gutsy. It doesn't seem to be rdesktop/vncviewer
specific, as different errors (are they errors or just debug info?)
occur at disconnect. See my two attachments for rdesktop and vncviewer
sessions (via tsclient) r
** Changed in: tsclient (Ubuntu)
Assignee: Sebastien Bacher (seb128) => (unassigned)
--
Error message on ending VNC session
https://bugs.launchpad.net/bugs/8422
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing
Not fixed in hardy!
** Changed in: tsclient (Ubuntu)
Status: Fix Committed => Confirmed
--
Error message on ending VNC session
https://bugs.launchpad.net/bugs/8422
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs ma
** Changed in: tsclient (Ubuntu)
Status: Fix Released => Fix Committed
--
Error message on ending VNC session
https://bugs.launchpad.net/bugs/8422
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-
Not fixed! Hardy still has the same problem.
--
Error message on ending VNC session
https://bugs.launchpad.net/bugs/8422
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lis
Fixed: hardy has 0.150-1
** Changed in: tsclient (Ubuntu)
Status: Fix Committed => Fix Released
--
Error message on ending VNC session
https://bugs.launchpad.net/bugs/8422
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu
Sorry.
I've changed the status, because it did not appear as "fix committed" to me
(according to https://wiki.ubuntu.com/Bugs/Status).
But it's probably "For package maintainers, the changes are pending and to be
uploaded soon (it's what PENDINGUPLOAD was in Bugzilla)" then.
--
Error message on
why did you change the bug settings?
** Changed in: tsclient (Ubuntu)
Status: Confirmed => Fix Committed
--
Error message on ending VNC session
https://bugs.launchpad.net/bugs/8422
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
-
Upstream fixed it for the next version (probably 0.150).
The patch can be found at:
http://tsclient.svn.sourceforge.net/viewvc/tsclient?view=rev&revision=17
In Gutsy we now have 0.148-3ubuntu1, which should still have this error.
** Changed in: tsclient (Ubuntu)
Status: Fix Committed => Co
If all you're getting is the keyboard error (for example, Autoselected
keyboard map en-us), this can be fixed by selecting a keyboard language
in Terminal Server Client under the Local Resources tab. Worked for me.
--
Error message on ending VNC session
https://bugs.launchpad.net/bugs/8422
You re
Confirm similar behaviour when connecting to WXP Pro via RDP with
tsclient 0.148 (and rdesktop 1.5.0) on Feisty.
** (tsclient:7987): WARNING **:
Autoselected keyboard map en-us
X Error of failed request: BadAtom (invalid Atom parameter)
Major opcode of failed request: 23 (X_GetSelectionOwner)
Any idea on when this fix will be appear in the update repositories?
--
Error message on ending VNC session
https://bugs.launchpad.net/bugs/8422
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
Fixed on upstream.
** Changed in: tsclient (Ubuntu)
Status: Confirmed => Fix Committed
--
Error message on ending VNC session
https://bugs.launchpad.net/bugs/8422
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mai
Yes. I also do have this on RDP.
** (tsclient:15178): WARNING **:
X Error of failed request: BadAtom (invalid Atom parameter)
Major opcode of failed request: 23 (X_GetSelectionOwner)
Atom id in failed request: 0x0
Serial number of failed request: 7445
Current serial number in output s
** Bug watch added: SourceForge.net Tracker #1689130
http://sourceforge.net/support/tracker.php?aid=1689130
** Also affects: tsclient (upstream) via
http://sourceforge.net/support/tracker.php?aid=1689130
Importance: Unknown
Status: Unknown
--
Error message on ending VNC session
h
I can also confirm this happens on a RDC connection to a windows server.
I am using Feisty Herd 4. This isn't a show stopper - just ugly and if
easily fixed it should be. We don't error aestetics deterring new
potential Linux users.
--
Error message on ending VNC session
https://launchpad.net/bug
As illustrated on bug 74220, this also happens with a windows connection
(rdesktop client), not only vnc.
I think we should change this bug title to
'Error message on ending remote session'
It seems that tsclient captures all output generated by its child
processes (vncviewer, rdesktop) and think
vncviewer spews out lots of debug messages on stderr. The attached patch
suppresses the error message whenever vncviewer returns successfully
(exit status 0).
** Attachment added: "Suppress error message on successful exit of vncviewer"
http://librarian.launchpad.net/4260226/noerr.patch
--
Er
Still seeing this error.
[EMAIL PROTECTED]:~$ dpkg -l tsclient
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name VersionDescr
32 matches
Mail list logo
