Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

osx 0.16.4 has "log_both" error in hello packet #1166

Closed
totaam opened this issue Apr 14, 2016 · 13 comments
Closed

osx 0.16.4 has "log_both" error in hello packet #1166

totaam opened this issue Apr 14, 2016 · 13 comments

Comments

@totaam
Copy link
Collaborator

totaam commented Apr 14, 2016

Issue migrated from trac ticket # 1166

component: client | priority: blocker | resolution: fixed

2016-04-14 20:17:01: afarr created the issue


As a first note, to install the 0.16.4 12370.pkg (from your /beta repo) I first had to throw all the .dmg applications I'd been collecting into the trash and empty the trash.

Once that was done, I was able to install, but trying to connect (to a 0.17.0 r12385 fedora 23 server) threw a hello packet error and triggered a connection loss:

2016-04-14 12:11:21,412 error in hello packet
Traceback (most recent call last):
  File "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/client/client_base.py", line 618, in _process_hello
    self.server_connection_established()
  File "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/client/ui_client_base.py", line 1599, in server_connection_established
    if XpraClientBase.server_connection_established(self):
  File "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/client/client_base.py", line 645, in server_connection_established
    self.parse_logging_capabilities()
  File "/Applications/Xpra.app/Contents/Resources/lib/python/xpra/client/ui_client_base.py", line 1804, in parse_logging_capabilities
    if not self.log_both:
AttributeError: 'XpraClient' object has no attribute 'log_both'
2016-04-14 12:11:21,413 error processing hello packet from server: 'XpraClient' object has no attribute 'log_both'
2016-04-14 12:11:21,414 Connection lost
@totaam
Copy link
Collaborator Author

totaam commented Apr 15, 2016

2016-04-15 04:07:28: antoine changed priority from major to blocker

@totaam
Copy link
Collaborator Author

totaam commented Apr 15, 2016

2016-04-15 04:07:28: antoine changed owner from antoine to afarr

@totaam
Copy link
Collaborator Author

totaam commented Apr 15, 2016

2016-04-15 04:07:28: antoine commented


I cannot reproduce and I really don't see how that's possible.
Please include the exact command lines and/or configuration files that you used.

The log_both attribute is initialized very early in the UI client class.

@totaam
Copy link
Collaborator Author

totaam commented Apr 15, 2016

2016-04-15 21:26:06: afarr changed owner from afarr to antoine

@totaam
Copy link
Collaborator Author

totaam commented Apr 15, 2016

2016-04-15 21:26:06: afarr commented


Interesting... I can't repro it either now?

Wait... spoke too soon.

0.16.4 12370.pkg connects without a hitch with a 0.16.4 server (didn't note revision).

The above error, with the output, is triggered by connecting the 0.16.4.pkg to a 0.17.0 server.

Server is launched with a standard/habitual command of dbus-launch xpra --no-daemon --bind-tcp=0.0.0.0:1203 --start-child=xterm --start-child=xterm --mdns=no start :13 --start-new-commands=yes.

Client is launched with ./xpra attach tcp:(stuff) -d launcher (without the debug flag, there's no traceback outputted).

To be thorough, I tested the 0.16.4 12370 application as well... and found that it has the same issue as the .pkg.

@totaam
Copy link
Collaborator Author

totaam commented Apr 16, 2016

2016-04-16 03:30:04: antoine changed owner from antoine to afarr

@totaam
Copy link
Collaborator Author

totaam commented Apr 16, 2016

2016-04-16 03:30:04: antoine changed title from osx 0.16.4 r12370.pkg has error in hello packet to osx 0.16.4 has "log_both" error in hello packet

@totaam
Copy link
Collaborator Author

totaam commented Apr 16, 2016

2016-04-16 03:30:04: antoine commented


Sorry about that, I am so focused on releasing 0.17 that I missed the fact that this ticket title is about 0.16.x

Should be fixed in 12389.

@totaam
Copy link
Collaborator Author

totaam commented Apr 18, 2016

2016-04-18 22:48:55: afarr commented


Hmm... tried again with 0.16.4 12370.pkg against trunk r12432 fedora 23 server, and got the same error (as well as noticing that TRUNK is now 0.18).

I can only presume that the fix is in the client. I'll test again once I manage to get one built (and I'll also have to slap together a 0.17 tagged server build set up while I'm at it, to be thorough).

@totaam
Copy link
Collaborator Author

totaam commented Apr 19, 2016

2016-04-19 02:55:51: antoine commented


The fix is in the client, as can be seen by following the link to 12389.

@totaam
Copy link
Collaborator Author

totaam commented Apr 22, 2016

2016-04-22 00:10:08: afarr changed status from new to closed

@totaam
Copy link
Collaborator Author

totaam commented Apr 22, 2016

2016-04-22 00:10:08: afarr set resolution to fixed

@totaam
Copy link
Collaborator Author

totaam commented Apr 22, 2016

2016-04-22 00:10:08: afarr commented


Tested with 0.16.4 12444 against a 0.17.0 r12453 fedora 23 server. Connects without a hitch.

Just to satisfy a little OCD, tried against 0.18.0 r12453 fedora 23 server. Also connects without a hitch.

Closing.

@totaam totaam closed this as completed Apr 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant