rdesktop session started with tsclient has no window borders when using compiz/emerald

Bug #194306 reported by Thomas Novin
4
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: tsclient

When I start a rdesktop session through tsclient there are no window borders. I have desktop effects enabled and emerald.

If I start rdesktop manually I don't have this problem.

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"
$ dpkg -l | grep tsclient
ii tsclient 0.150-1 front-end for viewing of remote desktops in

Revision history for this message
Thomas Novin (thomasn80) wrote :

I changed the laptops resolution to 1024x768 to better suit my LCD TV. Then I discovered this is true for all applications which has been used with a bigger window space that you currently have.

In the new scenario I had used Firefox in 1280x1024 and changed to 1024x768. Next time I started FF it was without borders. Same with tsclient, last time I had started a session I had used it in 1680x1050 and saved the session with the biggest possible to fit that resolution.

I'm changing source to unknown because I don't know if compiz-fusion or emerald is to blame (or maybe something else?).

Revision history for this message
cdiggity (craig-nzenergy) wrote :

Are you sure you haven't selected "Hide window manager's decorations" on the performance tab of tsclient? I had it checked as I thought it would disable effects on the remote machine but it in fact removed the window border and maximize/minimize/close buttons from the local window.

Revision history for this message
Caroline Ford (secretlondon) wrote :

Compiz?

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in compiz:
status: New → Incomplete
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in compiz:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.