Never mind about the log -- figured that out.
Running from an xterm didn't help -- same results, i.e. initial splash
screen then hang. I see this in the log right about that time:
Found a potential client
new window 0x5000B9L
invalidating named pixmap
created corral window 0x2001ed
Missing window or missing property or wrong property type WM_TRANSIENT_FOR
(window)
Property changed on 5243065: WM_HINTS
wm_hints.input = 1
Property changed on 5243065: WM_NORMAL_HINTS
Property changed on 5243065: WM_NAME
Property changed on 5243065: _NET_WM_NAME
Property changed on 5243065: WM_ICON_NAME
Property changed on 5243065: _NET_WM_ICON_NAME
Property changed on 5243065: _NET_WM_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)
Property changed on 5243065: _NET_WM_STRUT_PARTIAL
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)
Property changed on 5243065: _NET_WM_ICON
_NET_WM_ICON changed on 5243065, re-reading
Error parsing property _NET_WM_ICON (type icon); this may be a
misbehaving application, or bug in Wimpiggy
Data:
'0\x00\x00\x000\x00\x00\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00\xff\xff\xff\x00'[...?]
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/wimpiggy/wm.py", line 275, in
do_child_map_request_event
File "/usr/lib64/python2.4/site-packages/wimpiggy/wm.py", line 220, in
_manage_client
File "/usr/lib64/python2.4/site-packages/wimpiggy/window.py", line 465,
in __init__
File "/usr/lib64/python2.4/site-packages/wimpiggy/error.py", line 98, in
call_unsynced
File "/usr/lib64/python2.4/site-packages/wimpiggy/error.py", line 86, in
_call
File "/usr/lib64/python2.4/site-packages/wimpiggy/window.py", line 452,
in setup_client
File "/usr/lib64/python2.4/site-packages/wimpiggy/window.py", line 793,
in _read_initial_properties
File "/usr/lib64/python2.4/site-packages/wimpiggy/window.py", line 616,
in _handle_property_change
File "/usr/lib64/python2.4/site-packages/wimpiggy/window.py", line 689,
in _handle_net_wm_icon
File "/usr/lib64/python2.4/site-packages/wimpiggy/prop.py", line 280, in
prop_get
File "/usr/lib64/python2.4/site-packages/wimpiggy/prop.py", line 243, in
_prop_decode
File "/usr/lib64/python2.4/site-packages/wimpiggy/prop.py", line 247, in
_prop_decode_scalar
File "/usr/lib64/python2.4/site-packages/wimpiggy/prop.py", line 144, in
NetWMIcons
File "/usr/lib64/python2.4/site-packages/wimpiggy/prop.py", line 131, in
_read_image
AttributeError: 'cairo.ImageSurface' object has no attribute 'get_data'
forwarded
ConfigureNotify event received
received event on a parent window but have no parent signal
read thread: got data 'B\x16\x07\x00\x00\x00\xff\xff'
Queueing main thread call to <bound method Protocol._handle_read of
<xpra.protocol.Protocol object at 0x2b3aff6baa50>>
read thread: waiting for data to arrive
main thread: woken to handle read data
main thread: found read data 'B\x16\x07\x00\x00\x00\xff\xff'
got ['focus', 0]
widget with focus: None
Focus -> world window
sending WM_TAKE_FOCUS: <gtk.gdk.Window object (GdkWindow) at
0x2b3aff6c1550>, 309600297L
sending message to 0x200023L
main thread: processed all read data
ClientMessage received
event was delivered to window itself
not forwarding to CompositeHelper handler, it has no
wimpiggy-client-message-event signal
not forwarding to CompositeHelper handler, it has no
wimpiggy-client-message-event signal
PropertyNotify event received
event was delivered to window itself
not forwarding to XpraServer handler, it has no
wimpiggy-property-notify-event signal
not forwarding to Wm handler, it has no wimpiggy-property-notify-event
signal
FocusIn/FocusOut received
event was delivered to window itself
not forwarding to CompositeHelper handler, it has no
wimpiggy-focus-in-event signal
not forwarding to CompositeHelper handler, it has no
wimpiggy-focus-in-event signal
Does this mean anything to you?
BTW I've tried both with Eclipse 3.5 and Eclipse 3.6.2 with same results.
-P
On Fri, 01 Apr 2011 15:00:10 -0400, Paul G. Weiss <[email protected]> wrote:
On Fri, 01 Apr 2011 14:48:36 -0400, Antoine Martin
<[email protected]> wrote:
On 04/01/2011 10:03 PM, Paul G. Weiss wrote:
On Fri, 01 Apr 2011 10:47:00 -0400, Antoine Martin
<[email protected]> wrote:
The server is a Fedora 14 system (obviously, the client is anything
you
like)
I don't think the distro should make much of a difference, unless
CentOS
ships a weird eclipse setup.
Does it work if you first launch a terminal then launch eclipse from
there?
Anything in the logs?
Antoine
I am launching it from a terminal. That's how I run it under xpra:
xpra start :7
then
DISPLAY=:7 eclipse
What I meant was that you can start a terminal:
DISPLAY=:7 xterm
Then start eclipse from that terminal once you are attached to the
session. See if that works, or if you get more helpful log messages.
You may also want to increase debugging for xpra: "xpra -d all"
Cheers
Antoine
Do I specify -d all on the start command? If so, where does the logging
go?
-P
The reason I ask about the distro is that that might have different
version of xserver. But would that make a difference to xpra?
-P
On 04/01/2011 07:46 PM, Paul G. Weiss wrote:
On what distro are you running it? I was trying on Centos 5.
-P
On Fri, 01 Apr 2011 03:55:37 -0400, Antoine Martin
<[email protected]> wrote:
Hi,
That's odd, I've just tried it and it seems to work fine.
I am using winswitch to start it, but that shouldn't make any
difference. (worth a try though)
Cheers
Antoine
On 04/01/2011 04:27 AM, Paul G. Weiss wrote:
Is anyone able to run Eclipse under xpra. I had tried earlier and
failed and just tried again with this new release. Still no
good. It
brings up the initial splash screen then hangs.
-P
On Thu, 31 Mar 2011 16:44:05 -0400, Antoine Martin
<[email protected]> wrote:
Hi,
I've just made a new release (0.0.7.18) at:
http://winswitch.org/dists/
* DEBian packages for all major debian based distros
* RPMs for Fedora, CentOS and openSUSE
* ebuilds for Gentoo
* Standalone Xpra installer for MS Windows
The only things I have not built are the Mac OS X DMGs but you can
use
the winswitch DMGs for that (it includes xpra amongst other
things)
Let me know if you have any problems.
Cheers
Antoine
On 03/27/2011 01:36 PM, Antoine Martin wrote:
Hi,
I have been making regular releases of an "enhanced xpra" here:
http://winswitch.org/src/
You can find debian packages on this site too. This is the
version
used
by FreeBSD, amongst others. I have also made ebuilds for Gentoo
and
RPMs
for a number of distributions.
Please also note that "winswitch" (the software on this site)
will not
work with xpra upstream because it lacks some required features.
Here is a short summary of the enhancements I added:
* jpeg compression support (patch was not mine)
* minor version mismatch support (only refuses clients
connections
when
protocol has actually changed)
* --password-file option (useful for securing --bind-tcp)
* compile fix for Fedora (and maybe others)
* python style fixes (from pydev lint warnings)
* forced client disconnection (prevents ghost windows)
* --no-pulseaudio option
* --no-clipboard option
* simple GUI launcher
* win32 build files
* better OSX support
etc
As for the keyboard mapping issues, I am aware of the problem and
although winswitch does try to workaround the mapping issues this
is a
hard problem to solve and I have recently found new issues caused
by the
workarounds.. Time permitting, I will take another look at this.
Cheers
Antoine
On 03/27/2011 12:29 AM, أحمد المحمودي wrote:
Hello,
I sent this email to your email address last December, but I
got no
reply yet.
I was working on preparing a Debian package for parti-all
(based on
the Ubuntu package). Yet some concerns were raised on Debian
regarding
the software:
* You mentioned that parti is not usable as an actual
day-to-day
window manager.
* xpra has problems with non-US keyboards layouts.
I had a look at the hg repository, and I see there were a
considerable
amount of changes since your last release (0.0.6), I wonder if
the
above issues got fixed then. Also, do you intend to prepare a
new
release soon ?
_______________________________________________
Parti-discuss mailing list
[email protected]
http://lists.partiwm.org/cgi-bin/mailman/listinfo/parti-discuss
_______________________________________________
Parti-discuss mailing list
[email protected]
http://lists.partiwm.org/cgi-bin/mailman/listinfo/parti-discuss
_______________________________________________
Parti-discuss mailing list
[email protected]
http://lists.partiwm.org/cgi-bin/mailman/listinfo/parti-discuss
_______________________________________________
Parti-discuss mailing list
[email protected]
http://lists.partiwm.org/cgi-bin/mailman/listinfo/parti-discuss
_______________________________________________
Parti-discuss mailing list
[email protected]
http://lists.partiwm.org/cgi-bin/mailman/listinfo/parti-discuss
_______________________________________________
Parti-discuss mailing list
[email protected]
http://lists.partiwm.org/cgi-bin/mailman/listinfo/parti-discuss
_______________________________________________
Parti-discuss mailing list
[email protected]
http://lists.partiwm.org/cgi-bin/mailman/listinfo/parti-discuss
_______________________________________________
Parti-discuss mailing list
[email protected]
http://lists.partiwm.org/cgi-bin/mailman/listinfo/parti-discuss
_______________________________________________
Parti-discuss mailing list
[email protected]
http://lists.partiwm.org/cgi-bin/mailman/listinfo/parti-discuss
_______________________________________________
Parti-discuss mailing list
[email protected]
http://lists.partiwm.org/cgi-bin/mailman/listinfo/parti-discuss
