[X2Go-Dev] Bug#422: Bug#422: Just Create the .config/pulse/ dir!
Hi Michael, On Fr 14 Mär 2014 06:24:58 CET, Michael DePaulo wrote: After spending lots of time debugging this issue, largely involving comparing the debug output from pulseaudio.exe, I believe I've determined a simple fix. I observed that if I create this directory ahead of time, the pulseaudio.exe process launched by x2goclient.exe creates the cookie file under it stays running. C:\Users\mike\.x2go\pulse\.config\pulse\ Therefore, I believe a simple fix for this bug is for x2goclient.exe, regardless of what version of pulseaudio.exe is installed, to: 1. Create that directory (if it DNE). 2. Include logic around onmainwindow.cpp:5149 to use the cookie at that path. If the cookie is not in that location, fall back to .pulse-cookie. We already have this logic for Linux. Gosh! Very good work!!! Let's go that approach. I plan to write, test, and (hopefully) commit this fix tomorrow night. Note that we cannot override the cookie location due to PulseAudio Bug 75006: https://bugs.freedesktop.org/show_bug.cgi?id=75006 Note that although I am not sure why PulseAudio.exe is incapable of creating this file when launched by x2goclient.exe, compared to when it is launched by cmd.exe, I believe this is still safe approach to solving the bug. I say this because PulseAudio devs's comments commit messages make it clear that they support both the directory already existing, and the directory not already existing. For example: http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/src/pulsecore/authkey.c?id=a91359956f166005749247eaa5f4001a4555689d Maybe the pulse directory does not get created because of .config being missing. The pulsecore/core-utils.c contains a function name pa_make_secure_dir which will create a directory for the pulse cookies, but it (AFAICT) assumes that the parent dir (.config) already exists. It also may be that we don't set XDG variables not appropriately [1]. The pulseaudio patch you mention earlier [2] alludes that, too. [1] http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html [2] http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=7fad67c46188991c04a42b190349ebb3f4a1756f I guess assuring that the .config/pulse dir exists is a simple approach and we should go that instead of playing with XDG env vars (which are part of the freedesktop specs and X2Go Client is not about being compliant with freedesktop specs if run on Windows). Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpBxJATaUkry.pgp Description: Digitale PGP-Signatur ___ X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
[X2Go-Dev] Bug#454: [X2Go-User] Buggy File Folder sharing
Package: x2goclient Tag: build-macosx Severity: important Version: 3.99.2.1 Hi Graham, hi Thierry, [I forward this bug repport to our bug tracker On Do 13 Mär 2014 15:01:42 CET, Graham Stoddart-Stones wrote: Thierry: Just to confirm that we are encountering the same problem with Mac OSX 3.5.1, X2Goclient 3.99.2.1: When you start up X2Goclient on the Mac, you get an error dialog: sshd client not started, you'll need sshd for printing and file sharing. In OSX, openssh-server is built-in, and is activated by setting Enable Remote Login in System Preferences Sharing, as many others have noted. However, this does not stop the error dialog from recurring every time. That leads to another error message File cannot be opened. If one ignores this, X2Goclient starts and runs normally, provided one wishes to neither print locally, nor share files from the Mac with the remote server. I have seen lots of other emails on this topic, suggesting that the error message does not necessarily apply to the Mac (ie sshd is in fact running, the error message simply means that the x2goclient code is looking for a response from a Linux-like file (which does not occur in the same place in OSX), similarly the File Cannot be opened again refers to a file that is either not used on a Mac, or is in a wholly different location from where that file is actually stored on a Mac. I have not seen this point formally answered anywhere. For me, the concern is that, whether sshd is running on the Mac or not, File Sharing does not appear to be working. I am not sufficiently familiar with X2Go nor with the Mac to know where to look on the server for the Mac shared folders, but I do know that there is nothing under media, as there is with Linux and a PC, which is where I normally look. Again, I have searched the bulletins and forums, and often seen this point raised - I have just not found the answer on how to get round it. So, am keen to see how you get on, and whether anybody else can please shed any light! Can you cross-check the observed problem with latest X2Go Client [1]??? Can you launch X2Go Client from a terminal on Mac OS X and use a tool like strace (if that exists) and check its output for pointers to file-not-found errors? That would be really helpful for tracking down this issue. Mike [1] http://code.x2go.org/releases/binary-macosx/x2goclient/releases/4.0.1.3/ -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgp_w0x0oZgmk.pgp Description: Digitale PGP-Signatur ___ X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
