I found and joined the mailing list alluded to below, and I am attempting to
move the discussion there. I was starting to feel like I was spamming that
issue thread, anyway. I like the xpra project enough that I'll probably
stick on this email list to see if I can help.
You are correct, setting PYTHONPATH was the step I was missing, and I should
have figured that out on my own so I apologize. I've also done 'sudo
aptitude remove xpra' now, so that it is harder to make the same mistake. I
am now running 0.0.7.20.
Now to figure out why I'm having more significant problems with this
version. It appears to 'xpra start :7' ok, with some scary messages in
~/.xpra/<host>-7.log file (see [1] below).
Then if I run 'DISPLAY=:7 gnome-terminal &', more concerning messages appear
in the same log file (see [2]). But still nothing of concern outside of
that log file.
Then I try to attach with 'xpra attach :7', and nothing shows up. The log,
however, shows an actual python stack trace (see [3]). That appears to be
the problem. What I don't know is whether the scary messages before are
important or expected. Note that the stack does not give a path for the
"bindings.pyx" file. I am not family with ".pyx" files, so I don't know if
that is an indication that the wrong bindings.pyx file is still being found
somehow. I don't see an old "bindings.pyx" file anywhere under /usr. What
are your thoughts?
To address the other comments in your email:
Once I'm happy with how 0.0.7.20 is working on my linux workstation I will
install it on my Mac to keep the versions compatible, as you recommend. I
plan to just compile the same xpra-0.0.7.20 source on my Mac, though, rather
than installing the winswitch dmg. Do you foresee a problem with that?
I think I was unclear in my previous email. I was only "hesitant to
download" from the original download link you gave me *because* I did not
know of the connection between xpra and winswitch. It felt like we were
talking about application Foo and the page was for downloading application
Bar. Not a big deal. Once I looked at the FAQ page, though, it made sense.
I would still prefer to stay away from winswitch, because I want to use
xpra directly.
Thanks for the help,
Matt
REFERENCES
[1] - Content of ~/.xpra/<host>-7.log immediately after 'xpra start :7'
"""
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic,
removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic,
removing from list!
X Error of failed request: BadValue (integer parameter out of range for
operation)
Major opcode of failed request: 118 (X_SetModifierMapping)
Value in failed request: 0x17
Serial number of failed request: 21
Current serial number in output stream: 21
randr=True
xpra is ready.
"""
[2] - Additional content of ~/.xpra/<host>-7.log immediately after
'DISPLAY=:7 gnome-terminal &'
"""
Missing window or missing property or wrong property type WM_TRANSIENT_FOR
(window)
Missing window or missing property or wrong property type _NET_WM_STATE
(['atom'])
Missing window or missing property or wrong property type
_NET_WM_STRUT_PARTIAL (strut-partial)
Missing window or missing property or wrong property type _NET_WM_STRUT
(strut)
Missing window or missing property or wrong property type
_NET_WM_STRUT_PARTIAL (strut-partial)
Missing window or missing property or wrong property type _NET_WM_STRUT
(strut)
"""
[3] - Additional content of ~/.xpra/<host>-7.log immediately after 'xpra
attach :7'
"""
New connection received
Handshake complete; enabling connection
best resolution for client(2560x1600) is: (3840, 2560)
Unhandled error while processing packet from peer
Traceback (most recent call last):
File
"/home/mtennant/local/dl/xpra-0.0.7.20/install/lib/python/xpra/protocol.py",
line 207, in _process_packet
self._process_packet_cb(self, decoded)
File
"/home/mtennant/local/dl/xpra-0.0.7.20/install/lib/python/xpra/server.py",
line 818, in process_packet
self._packet_handlers[packet_type](self, proto, packet)
File
"/home/mtennant/local/dl/xpra-0.0.7.20/install/lib/python/xpra/server.py",
line 666, in _process_hello
capabilities["desktop_size"] =
self._get_desktop_size_capability(client_capabilities)
File
"/home/mtennant/local/dl/xpra-0.0.7.20/install/lib/python/xpra/server.py",
line 595, in _get_desktop_size_capability
set_screen_size(w, h)
File "bindings.pyx", line 954, in
wimpiggy.lowlevel.bindings.set_screen_size
(wimpiggy/lowlevel/bindings.c:9170)
File "bindings.pyx", line 937, in
wimpiggy.lowlevel.bindings._set_screen_size
(wimpiggy/lowlevel/bindings.c:8889)
AttributeError: 'dict' object has no attribute 'width'
"""
On Mon, May 16, 2011 at 8:24 PM, <[email protected]> wrote:
>
> Comment #15 on issue 6 by [email protected]: real keyboard support
>
> http://code.google.com/p/partiwm/issues/detail?id=6
>
> Like David responded on the mailing list (David: Matt only reads the
> bugtracker): you are not using the version you downloaded from winswitch
> (you probably still have the old copy installed first on your PYTHONPATH,
> remove it).
> The reason why you are not seeing improvements is because you aren't using
> it... As for the "hesitant to download" from my site, I am afraid I can't
> really help you with that: it's not just open-source, but every build script
> and installer files are available and documented... your call.
>
> Also, note that you will need this newer version on the Mac client, it is
> included in the DMGs available on the site. You must upgrade both the
> server(s) and clients, the v0.0.7.x branch is no longer compatible with the
> old v0.0.6.x (which is now almost 3 years old)
>
>
> --
> You received this message because you starred the issue.
> You may adjust your notification preferences at:
> https://code.google.com/hosting/settings
>
> Reply to this email to add a comment.
>
_______________________________________________
Parti-discuss mailing list
[email protected]
http://lists.partiwm.org/cgi-bin/mailman/listinfo/parti-discuss
