https://bugzilla.novell.com/show_bug.cgi?id=289007#c1 --- Comment #1 from Stefan Dirsch 2007-07-02 11:03:13 MST --- See also discussion on freenx-knx mailing list. http://mail.kde.org/pipermail/freenx-knx/2007-June/005425.html -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=289007 Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|sndirsch@novell.com |eich@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=289007#c4 Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|eich@novell.com |sndirsch@novell.com Status|ASSIGNED |NEW --- Comment #4 from Egbert Eich 2007-07-02 14:51:04 MST --- Reassigning back to Stefan for further testing. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=289007#c6 --- Comment #6 from Egbert Eich 2007-07-02 22:01:41 MST --- I've been looking at this some more: the old transport selection mechanism was much more involved (and sometimes seemed to lack a general logic): with hostname == foo and DISPLAY=foo:n.m the original code tried unix sockets first. With DISPLAY=localhost:n.m it tried tcp socket on localhost. Furthermore there was a distinction between 'local' and 'unix' transport, local/:n.m as also a valid DISPLAY string. 'local' ment whatever local transport was the preferred one on the target platform while 'unix' meant "use UNIX sockets". The choice was left to libxtrans which had the platform dependent code. My patch doesn't support 'local' yet. Since xcb doesn't support any other local transport than UNIX sockets it doesn't really make sense to add code for that. On the other hand we might want to support 'local' as protocol string to avoid breaking old stuff. I'm not sure yet how far the old heuristic should be followed. Certainly existing scripts can make all sorts of assumptions based on the old heuristic which are no longer true today. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=289007#c8 Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #149271|0 |1 is obsolete| | Attachment #149328|0 |1 is obsolete| | --- Comment #8 from Egbert Eich 2007-07-03 11:32:56 MST --- Created an attachment (id=149474) --> (https://bugzilla.novell.com/attachment.cgi?id=149474) fix without artefacts from #257830 This patch should fix the problem with artefacts from but 257830 which still had been in the tree. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=289007#c9 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #9 from Stefan Dirsch 2007-07-03 14:15:04 MST --- Hmm. Applying the patch results in a Segfault. # DISPLAY=:0 xterm Segmentation fault # DISPLAY=unix:0 xterm Segmentation fault Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1213802816 (LWP 13173)] 0xb7a987b7 in xcb_popcount () from /usr/lib/libxcb.so.1 (gdb) bt #0 0xb7a987b7 in xcb_popcount () from /usr/lib/libxcb.so.1 #1 0xb7d78cd6 in _XConnectXCB () from /usr/lib/libX11.so.6 #2 0xb7d61a29 in XOpenDisplay () from /usr/lib/libX11.so.6 #3 0xb7c59aad in XtOpenDisplay () from /usr/lib/libXt.so.6 #4 0xb7c59cbb in _XtAppInit () from /usr/lib/libXt.so.6 #5 0xb7c62840 in XtOpenApplication () from /usr/lib/libXt.so.6 #6 0x08067e2a in main () (gdb) quit -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=289007#c11 --- Comment #11 from Stefan Dirsch 2007-07-05 03:35:25 MST --- Thanks. X11 applications not longer crash, but using the "unix:" notation still doesn't work. :-( # DISPLAY=unix:0 xterm xterm Xt error: Can't open display: unix:0 Hmm ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=289007#c13 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #13 from Stefan Dirsch 2007-07-05 09:54:20 MST --- Yes, this one finally works. Thanks a *lot*, Egbert! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=289007#c16 --- Comment #16 from Stefan Dirsch 2007-07-13 10:43:02 MST --- And maybe discuss it on the xcb ML first, so they get aware of such things. Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=289007#c18 --- Comment #18 from Matthias Hopf 2007-07-19 13:10:01 MST --- Pushed after Bart approved:

Weird. I was sure I caught that case when I wrote the original code. Oh well, it's moot now---thanks much to Egbert and yourself for the fix! Looks good to me. Bart

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.