Re: [Freerdp-devel] Sound not working in 1.1 Beta1
Hi,
we added some debugging code to the alsa plugin and found out that it hangs in
the call to
snd_pcm_htimestamp(alsa-pcm_handle, frames, tstamp);
we have tried to replace all calls to this function with calls to
frames = snd_pcm_avail (alsa-pcm_handle);
That mostly solves the problem. Unfortunately sometimes there is very loud
noise, instead of normal sound. Sounds like it plays a block of uninitialized
memory. I am not an alsa expert, so maybe somebody with more knowledge of alsa
has an idea what could be wrong here.
See below for our patch (line numbers may differ, because I have removed the
debugging code from the patch)
Regards
Gerald
@@ -337,19 +346,22 @@ static void rdpsnd_alsa_close(rdpsndDevicePlugin* device)
if (!alsa-pcm_handle)
return;
+ frames = snd_pcm_avail (alsa-pcm_handle);
+/*
status = snd_pcm_htimestamp(alsa-pcm_handle, frames, tstamp);
if (status != 0)
frames = 0;
-
+*/
@@ -560,42 +576,54 @@ static void rdpsnd_alsa_wave_play(rdpsndDevicePlugin*
device, RDPSND_WAVE* wave)
if (alsa-wLocalTimeClose)
{
wCurrentTime = GetTickCount();
-
- if (snd_pcm_htimestamp(alsa-pcm_handle, frames, tstamp) == -EPIPE)
+
+ if (snd_pcm_avail (alsa-pcm_handle) == -EPIPE)
{
@@ -607,19 +635,27 @@ static void rdpsnd_alsa_wave_play(rdpsndDevicePlugin*
device, RDPSND_WAVE* wave)
}
free(data);
- snd_pcm_htimestamp(alsa-pcm_handle, frames, tstamp);
+ frames = snd_pcm_avail (alsa-pcm_handle);
Von: Marc-Andr Moreau [mailto:marcandre.mor...@gmail.com]
Gesendet: Samstag, 16. Mrz 2013 03:03
An: Gerald Richter - ECOS
Cc: freerdp-devel@lists.sourceforge.net; j...@ecos.de
Betreff: Re: [Freerdp-devel] Sound not working in 1.1 Beta1
Hi Gerald,
It turns out I had avoided closing the device every time:
https://github.com/FreeRDP/FreeRDP/blob/master/channels/rdpsnd/client/alsa/rdpsnd_alsa.c#L330
For some reason the older code was *opening* the device on a close pdu, never
understood why. Opening instead of closing was causing issues which is why I
changed the logic a bit to be more proper. This might require some further
investigation. Maybe try to add some debug output in that file and figure out
the sequence of events leading to the error?
On Fri, Mar 15, 2013 at 12:27 PM, Gerald Richter - ECOS rich...@ecos.de
mailto:rich...@ecos.de wrote:
Hi,
thanks for your feedback, could you tell me where in the code the device is
closed? Then I will try to make it a NOP and see if this changes the situation.
Thanks Regards
Gerald
Von: Marc-Andr Moreau [mailto:marcandre.mor...@gmail.com
mailto:marcandre.mor...@gmail.com ]
Gesendet: Freitag, 15. Mrz 2013 17:14
An: Gerald Richter - ECOS
Cc: freerdp-devel@lists.sourceforge.net
mailto:freerdp-devel@lists.sourceforge.net ; j...@ecos.de
mailto:j...@ecos.de
Betreff: Re: [Freerdp-devel] Sound not working in 1.1 Beta1
Hi,
One main difference is that the new code actually closes the ALSA device when
the server sends a close pdu. I have no idea why, but servers like windows 7
and windows 8 constantly open and close the sound device. Technically, we could
avoid closing the device and simply reset its state, which might fix this issue.
On Fri, Mar 15, 2013 at 8:30 AM, Gerald Richter - ECOS rich...@ecos.de
mailto:rich...@ecos.de wrote:
Hi,
We are try to use the current git build of xfreerdp (2013-03-15).
We are not able to redirect sound output properly while using alsa, we've no
pulseaudio installed. With older builds (from last year) the sound output
worked.
The sound is audible for 1-2 seconds and stops after we get a warning like
Warning: requested sound buffer size 17600, got 7526 instead. We tried to
raise up the prealloc size in /proc/asound/card0/pcm*p/sub0/prealloc to the
maximum value which had no effect. After configuring the dmix plugin for alsa
the buffer warnings disappeared, but this didn't change the behaviour at all.
There are no problems with sound while using other applications.
Maybe someone has an idea to resolve this issue.
Thanks Regards
Gerald
alsa.config:
pcm.!default {
type plug
slave.pcm dmixer
}
pcm.dsp0 {
type plug
slave.pcm dmixer
}
pcm.dmixer {
type dmix
ipc_key 1024
slave {
pcm hw:0,0
period_time 0
period_size 1024
buffer_size 32768
rate 44100
}
bindings {
0 0
1 1
}
}
ctl.mixer0 {
type hw
card 0
}
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar http://p.sf.net/sfu/appdyn_d2d_mar
___
Freerdp-devel mailing list
Freerdp-devel@lists.sourceforge.net
mailto:Freerdp-devel@lists.sourceforge.net
https
[Freerdp-devel] Sound not working in 1.1 Beta1
Hi,
We are try to use the current git build of xfreerdp (2013-03-15).
We are not able to redirect sound output properly while using alsa, we've no
pulseaudio installed. With older builds (from last year) the sound output
worked.
The sound is audible for 1-2 seconds and stops after we get a warning like
Warning: requested sound buffer size 17600, got 7526 instead. We tried to
raise up the prealloc size in /proc/asound/card0/pcm*p/sub0/prealloc to the
maximum value which had no effect. After configuring the dmix plugin for alsa
the buffer warnings disappeared, but this didn't change the behaviour at all.
There are no problems with sound while using other applications.
Maybe someone has an idea to resolve this issue.
Thanks Regards
Gerald
alsa.config:
pcm.!default {
type plug
slave.pcm dmixer
}
pcm.dsp0 {
type plug
slave.pcm dmixer
}
pcm.dmixer {
type dmix
ipc_key 1024
slave {
pcm hw:0,0
period_time 0
period_size 1024
buffer_size 32768
rate 44100
}
bindings {
0 0
1 1
}
}
ctl.mixer0 {
type hw
card 0
}
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
Freerdp-devel mailing list
Freerdp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel
Re: [Freerdp-devel] Sound not working in 1.1 Beta1
Hi,
thanks for your feedback, could you tell me where in the code the device is
closed? Then I will try to make it a NOP and see if this changes the situation.
Thanks Regards
Gerald
Von: Marc-André Moreau [mailto:marcandre.mor...@gmail.com]
Gesendet: Freitag, 15. März 2013 17:14
An: Gerald Richter - ECOS
Cc: freerdp-devel@lists.sourceforge.net; j...@ecos.de
Betreff: Re: [Freerdp-devel] Sound not working in 1.1 Beta1
Hi,
One main difference is that the new code actually closes the ALSA device when
the server sends a close pdu. I have no idea why, but servers like windows 7
and windows 8 constantly open and close the sound device. Technically, we could
avoid closing the device and simply reset its state, which might fix this issue.
On Fri, Mar 15, 2013 at 8:30 AM, Gerald Richter - ECOS rich...@ecos.de
mailto:rich...@ecos.de wrote:
Hi,
We are try to use the current git build of xfreerdp (2013-03-15).
We are not able to redirect sound output properly while using alsa, we've no
pulseaudio installed. With older builds (from last year) the sound output
worked.
The sound is audible for 1-2 seconds and stops after we get a warning like
Warning: requested sound buffer size 17600, got 7526 instead. We tried to
raise up the prealloc size in /proc/asound/card0/pcm*p/sub0/prealloc to the
maximum value which had no effect. After configuring the dmix plugin for alsa
the buffer warnings disappeared, but this didn't change the behaviour at all.
There are no problems with sound while using other applications.
Maybe someone has an idea to resolve this issue.
Thanks Regards
Gerald
alsa.config:
pcm.!default {
type plug
slave.pcm dmixer
}
pcm.dsp0 {
type plug
slave.pcm dmixer
}
pcm.dmixer {
type dmix
ipc_key 1024
slave {
pcm hw:0,0
period_time 0
period_size 1024
buffer_size 32768
rate 44100
}
bindings {
0 0
1 1
}
}
ctl.mixer0 {
type hw
card 0
}
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar http://p.sf.net/sfu/appdyn_d2d_mar
___
Freerdp-devel mailing list
Freerdp-devel@lists.sourceforge.net
mailto:Freerdp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
Freerdp-devel mailing list
Freerdp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel
Re: [Freerdp-devel] Debug/Log System
Hi, 1. If you want to be compatible with Linux syslog, you could define the levels the same: LOG_EMERG=0; LOG_ALERT=1; LOG_CRIT=2; LOG_ERR=3; LOG_WARNING=4; LOG_NOTICE=5; LOG_INFO=6; LOG_DEBUG=7. That would make it easier if someone wanted to connect it to syslog at some point. [[GR]] This make sense, I have updated the wiki page 2. Additional (deeper) levels of debug information are nice because you might include a lot of information at LOG_DEBUG level during development but then want to turn it off when things are working, without removing or commenting-out the statements, in case they're needed again some day. e.g. LOG_DEBUG_2=8; LOG_DEBUG_3=9. [[GR]] Also added to the wiki 3. There's a decision built in here: is the overall log level a statically-defined value or a variable? [[GR]] I prefer to have the current loglevel in a variable, because it's more flexible and the runtime cost are low. 5. It'd be nice to have a way to turn on and off timestamps on the log messages. Either a log_with_timestamps(bool) entrypoint or perhaps a separate LOGGER_WITH_TIMESTAMP() call? [[GR]] Yes, but this will not affect the log api in the program, but is only an additional the command line option (Added a comment on the wiki) 6. It'd be nice to be able to tell the logging system to send its messages to stderr, stdout, or an arbitrary fildes. Like a logging subscription service. Then it's just a small patch to add a new fildes and use it for a custom output-handling system. [[GR]] Yes, of course. Same as 5 7. A flush function is nice in case you're working with code that can crash the system. [[GR]] Added to the wiki 8. The idea of popping up a dialog box is tricky: 1. Such a system should really handle localization of the messages. [[GR]] should easy solvable with gettext 2. The dialog style may not match dialogs everywhere else on the system. I would lean here toward an architecture where user interaction is a pluggable module. The default version might just interact at the stderr/stdout level. But different vendors could plug in their own back-end for Qt, Gnome, Mac, Windows, whatever. Such a system would also handle things like asking for a password, verifying a certificate, etc. This is a much bigger job than just the logging question. [[GR]] For now I would be very happy if the user get an error message if something goes wrong (which is not only send to stdout = goes to nowhere). You are right, but this does not affect the logging api, so it can be implemented in a second step. 3. So... I'd just kick that can down the road for now. If it's easy to output the information to a file, people can write their own code to deal with that file. For now. [[GR]] My problem is not logging, but error handling. I already took me hours of debugging my system, until I realyized that error message (if any at all) goes to stdout and will not show up at all if I start freerdp as a gui program. They do not even go to stderr, so there is no chance to distinguish between normal output and errors. If freerdp fail it return with exit code 0. From my point of view having an error handing/reporting is so important, that should have been implemented before 1.0. That's the reason why I made a suggestion and volunteer to make a first basic implementation, which at least defines and implements the API which should be used to send log/debug/error messages. How these messages are shown to user can be easily improved at any time, without problem, but the API needs to be well defined. Regards Gerald Regards, Daryl Poe HP Thin Clients On 12/5/2012 12:17 PM, Marc-André Moreau wrote: clip As for using the mailing list, yes, it ought to be used. Another discussion for which I would really appreciate some help is the design of a better debug/log system. The current one is severely limited, and there is a large number of requirements which an ideal debug/log system would need to meet. Since this affects everyone and pretty much all the code, I need your input on this. We're currently collecting information on this wiki page: https://github.com/FreeRDP/FreeRDP/wiki/Debug-System I repeat, I need input on this. I'd rather have it before than after it's changed. It's a tough design question, and I'd rather make the change to a well designed debug system once than switch to something partially proper and still need to change it a lot later on. -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue
Re: [Freerdp-devel] version 1.0.2-rc1 / Debug Error Output
Hi Bernhard, The API looks good to me. I think starting with some basic functions and improving it when required is a good approach. But all of this should go into 1.1 or later and not into the 1.0 series. [[GR]] For me the error reporting part of that API is so important, that should have been implemented before 1.0 (see also my other mail). Of course I understand that such a change should be well thought, but it should at least in 1.0.3 (of course that might be only my opinion, but it's the result of writing and debugging programs for many years) Regards Gerald -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
Re: [Freerdp-devel] version 1.0.2-rc1 / Debug Error Output
I did a look in the proposed API and it is simple... Personally I think we need to have something like an exception system (you can take a look as GNU Parted does it) so we can even make special handlers in GUI applications and have it handled in different ways. We can offer an default exception handler that could work mostly as you designed. The log part of it, could be done exactly as you designed but error hangling is not flexible enough. [[GR]] I also like the idea of using exceptions for error handling, but I think this behind the scope of the logging API and a much bigger change. So for now I would like to stick with a simple logging/debug/error reporting API. Gerald -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
Re: [Freerdp-devel] version 1.0.2-rc1 / Debug Error Output
Hi, I had some discussion with Marc-Andre about logging and error handling about two month ago. My main problem with way it is done in freerdp at the moment, is that a GUI user will never see an error message (because it goes to stdout, which you might see on Linux if you start from a terminal, but you will never see it on windows, because there is no stdout for GUI programms). Freerdp just terminates silently if anything goes wrong. An average user will just throw freerdp away as a broken bit of software, also the reason might only be a typo on the command line, but freerdp doesn't tells about it... So Marc-Andre wrote down a few words about the needs of a logging/debugging/error handling system and I wanted to create some draft for the API. Unfortunately I was tight up will other projects, but now I have made a first start and it can be found below Marc-Andre's words on the wiki at https://github.com/FreeRDP/FreeRDP/wiki/Debug-System . I like to ask anybody to give feedback. If we can agree on an API I will implement at least a basic version of it. Regards Gerald -Original Message- From: Bernhard Miklautz [mailto:bmikla...@thinstuff.at] Sent: Wednesday, November 07, 2012 12:15 AM To: freerdp-devel@lists.sourceforge.net Subject: [Freerdp-devel] version 1.0.2-rc1 Hi all, we just tagged the first release candidate for freerdp version 1.0.2 it can be found at https://github.com/FreeRDP/FreeRDP/tree/1.0.2-rc1. Version 1.0.2 will be a maintenance release for the stable-1.0 branch containing basically bug fixes - see changelog for details. Please help us by testing and reporting issues - https://github.com/FreeRDP/FreeRDP/wiki/BugReporting. Best regards, Bernhard -- LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d ___ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel -- Keep yourself connected to Go Parallel: VERIFY Test and improve your parallel project with help from experts and peers. http://goparallel.sourceforge.net ___ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
[Freerdp-devel] win32: Cursor shape does not change
Hi, I using git master wfreerdp. The cursor shape is not changing when I move the mouse over a border or text etc. Any idea what's wrong here or were to start to dig? Gerald -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
[Freerdp-devel] PATCH: Win32 rdpdr disk support static linked plugins
Hi, attached find a patch that makes the rdpdr disk plugin working on windows. Currently not working are rename and setting of read only attribute and file times. In addition it also adds the ability to staticly link plugins into the binary, so you get one big exe and need no dlls. I have only tested this on windows (only disk plugin so far). I use the following options for cmake for static binary: cmake -DWITH_MONOLITHIC_BUILD=ON -DMSVC_RUNTIME=static -DBUILD_SHARED_LIBS=OFF -DWITH_RDPDR=ON -DOPENSSL_INCLUDE_DIR=\opensslpath\inc32 -DOPENSSL_LIBRARIES=\opensslpath\out32.dbg\ssleay32.lib;d:\path\out32.dbg\libeay32.lib -G Visual Studio 9 2008 . Important notice: Openssl need to be compiled with the same static runtime. Currently missing is a switch to link different openssl libraries for debug and release builds. Gerald -- Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html___ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
Re: [Freerdp-devel] PATCH: Fix 100% CPU load on Windows
That's the same what my patch has done, if it would have gone thru the mailing list. Anyway, it's fixed :-) Thanks Gerald -Original Message- From: Jay Sorg [mailto:jay.s...@gmail.com] Sent: Monday, October 01, 2012 8:06 PM To: Gerald Richter - ECOS Cc: Marc-André Moreau; freerdp-devel@lists.sourceforge.net Subject: Re: [Freerdp-devel] PATCH: Fix 100% CPU load on Windows I pushed a fix for this since I caused the issue. The old code was using the file descriptor as a Windows wait object which goes not work so I changed it to use the WSA object but forgot to reset it. It's a manual reset event. Sorry for the confusion Jay -- Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
Re: [Freerdp-devel] PATCH: Fix 100% CPU load on Windows
Hi Jay, Great, as far as the MsgWaitForMultipleObjects goes, we can set the timeout to INFINITE if the main loop is working right, right? I think it's 1 now because it was broke and the timeout was the only reason the loop spun. Yes, we should set the timeout to a higher value. In my patch I used 10ms, because I was not sure about the reason for the 1ms. I would suggest using 1000ms, that will not consume CPU time, but is a fallback in case something totally goes wrong, to avoid that the whole application is hanging. I have just tested with 1000ms and it works fine. Gerald Jay That's the same what my patch has done, if it would have gone thru the mailing list. Anyway, it's fixed :-) -- Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
[Freerdp-devel] PATCH: Missing #ifdef stdint
Hi, attached find a patch that is necessary for me to compile current git master on windows Gerald -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html___ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
Re: [Freerdp-devel] FreeRDP On Mac OS/X 10.6 Keyboard/Mouse issue
Thanks for your feedback. Can you send me your configure options you used to build xfreerdp on mac? Maybe I missed an option. Thanks Gerald -Original Message- From: Dorian Johnson [mailto:dor...@dorianjohnson.com] Sent: Monday, July 25, 2011 3:39 PM To: Gerald Richter - ECOS Cc: freerdp-devel@lists.sourceforge.net Subject: Re: [Freerdp-devel] FreeRDP On Mac OS/X 10.6 Keyboard/Mouse issue I can't duplicate this. Right mouse works fine for me on 10.6/10.7 and WinXP/7/2008R2 using the git edge version of 0.X On Sun, Jul 24, 2011 at 10:45 PM, rich...@ecos.de wrote: Hi, the keyboard issue is solved, I simply forgot to copy over the keymap file, but now a new issue had arisen, the right mouse button is not working on Mac OS/X. Using windows without the right mouse button, isn't fun ... Gerald -Original Message- From: Gerald Richter - ECOS Sent: Tuesday, July 19, 2011 5:02 PM To: freerdp-devel@lists.sourceforge.net Subject: Re: [Freerdp-devel] FreeRDP On Mac OS/X 10.6 Keyboard issue Hi, after doing some other stuff I am back to xfreerdp on Mac OS/x . After I resolved my keyboard issue on one machine by not compiling with xkbfile, I now have the same issue on another machine. I just copy over the binary and libfreerdp*. Everything works just fine, but when I press a key I get the message: xf_kb_send_key: unknown key down keycode=8 (X keysym=0x0061). This is when I press an 'a', so it gets the correct acsii code (0x61). I would be very happy if anybody could point me in the right direction where to search for this issue. Thanks Gerald P.S. I am using the latest git version -Original Message- From: Mads Kiilerich [mailto:m...@kiilerich.com] Sent: Tuesday, April 12, 2011 11:38 AM To: Gerald Richter - ECOS Cc: Marc-André Moreau; freerdp-devel@lists.sourceforge.net Subject: Re: [Freerdp-devel] FreeRDP On Mac OS/X 10.6 On 04/11/2011 01:36 PM, rich...@ecos.de wrote: Hi, below is what I done to get it compile on 10.6 ( It took me a while to figure out the correct options, so may it is not the best solution. Any comments are welcome before I add it to the wiki). FreeRDP is now connecting to the server and screen and mouse works, but keyboard doesn?t . I get ?xf_kb_send_key: unknown key down keycode=9 (X keysym=0x0073). Any hints are welcome. I have recently touched and refactored the keyboard handling code but have tried to not make any changes for Mac. Can you try with a 14 day old (checkout before my changes) and see if that makes a difference? I assume that Marc-André's compile fix means that it works for him, which indicates that it isn't a general problem. I hope he will comment on how he compiles it. Installation on Mac OS/X 10.6: - install macports from http://www.macports.org/ - install autoconf, etc. (NOTE some dependencies like m4 and perl are also installed!) sudo port install autoconf automake libtool pkgconfig - get FreeRDP from git git clone git://github.com/FreeRDP/FreeRDP.git cd FreeRDP - edit autogen.sh, change libtoolize to glibtoolize - run autogen.sh, configure, make, make install sh autogen.sh ./configure CFLAGS=-arch i386 PKG_CONFIG=/opt/local/bin/pkg- config PKG_CONFIG_PATH=/usr/X11/lib/pkgconfig LDFLAGS=- L/usr/X11/lib --with-debug make sudo make install Thanks for contributing your description. That could be an encouragement for me to steal a Mac and try it. I assumed it worked with Apples development tools (Xcode?) without macports, but I really don't know. If these workarounds really are needed we should build them into the build system. /Mads - - Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ ___ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel -- Storage Efficiency Calculator This modeling tool is based on patent-pending intellectual property that has been used successfully in hundreds of IBM storage optimization engage- ments, worldwide. Store less, Store more with what you own, Move data to the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/ ___ Freerdp-devel mailing list Freerdp-devel
Re: [Freerdp-devel] FreeRDP On Mac OS/X 10.6 Keyboard issue
Hi, after doing some other stuff I am back to xfreerdp on Mac OS/x . After I resolved my keyboard issue on one machine by not compiling with xkbfile, I now have the same issue on another machine. I just copy over the binary and libfreerdp*. Everything works just fine, but when I press a key I get the message: xf_kb_send_key: unknown key down keycode=8 (X keysym=0x0061). This is when I press an 'a', so it gets the correct acsii code (0x61). I would be very happy if anybody could point me in the right direction where to search for this issue. Thanks Gerald P.S. I am using the latest git version -Original Message- From: Mads Kiilerich [mailto:m...@kiilerich.com] Sent: Tuesday, April 12, 2011 11:38 AM To: Gerald Richter - ECOS Cc: Marc-André Moreau; freerdp-devel@lists.sourceforge.net Subject: Re: [Freerdp-devel] FreeRDP On Mac OS/X 10.6 On 04/11/2011 01:36 PM, rich...@ecos.de wrote: Hi, below is what I done to get it compile on 10.6 ( It took me a while to figure out the correct options, so may it is not the best solution. Any comments are welcome before I add it to the wiki). FreeRDP is now connecting to the server and screen and mouse works, but keyboard doesn?t . I get ?xf_kb_send_key: unknown key down keycode=9 (X keysym=0x0073). Any hints are welcome. I have recently touched and refactored the keyboard handling code but have tried to not make any changes for Mac. Can you try with a 14 day old (checkout before my changes) and see if that makes a difference? I assume that Marc-André's compile fix means that it works for him, which indicates that it isn't a general problem. I hope he will comment on how he compiles it. Installation on Mac OS/X 10.6: - install macports from http://www.macports.org/ - install autoconf, etc. (NOTE some dependencies like m4 and perl are also installed!) sudo port install autoconf automake libtool pkgconfig - get FreeRDP from git git clone git://github.com/FreeRDP/FreeRDP.git cd FreeRDP - edit autogen.sh, change libtoolize to glibtoolize - run autogen.sh, configure, make, make install sh autogen.sh ./configure CFLAGS=-arch i386 PKG_CONFIG=/opt/local/bin/pkg-config PKG_CONFIG_PATH=/usr/X11/lib/pkgconfig LDFLAGS=-L/usr/X11/lib --with-debug make sudo make install Thanks for contributing your description. That could be an encouragement for me to steal a Mac and try it. I assumed it worked with Apples development tools (Xcode?) without macports, but I really don't know. If these workarounds really are needed we should build them into the build system. /Mads -- Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ ___ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
Re: [Freerdp-devel] FreeRDP On Mac OS/X 10.6
Hi, I have recently touched and refactored the keyboard handling code but have tried to not make any changes for Mac. Can you try with a 14 day old (checkout before my changes) and see if that makes a difference? I have tried the version from 15.3.11 and keyboard works as expected. The obvious difference I see, is that the current version uses libxkbfile and the old version not. If I run configure without pkg-config, configure says xkbfile: no, but during compile I get an error similar like @XKBFILE_LIB@ undefined. Gerald -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
Re: [Freerdp-devel] FreeRDP On Mac OS/X 10.6
If I run configure without pkg-config, configure says xkbfile: no, but during compile I get an error similar like @XKBFILE_LIB@ undefined. How do you do that? AFAICS pkg-config is mandatory and nothing works without it. The last release version compiles with (without pkg-config installed) ./configure CFLAGS=-arch i386 LDFLAGS=-L/usr/X11/lib XCURSOR_LIBS='-lXcursor' XCURSOR_CFLAGS=' ' This is nice because, no extra installation in addition to xcode is needed. I would be even better to fix configure to find these standard paths on it own. But then I run into the semaphore problem, which causes me to switch to the git version The HEAD version did not compile with the configure options above, but gave me the @XKBFILE_LIB@ error. I just retryed serveral options today, but now I have pkg-config installed. The outcome is that the options above will now also compile, but it will compile without libxkbfile, because pkg-config does not find the corresponding .pc file. When I do ./configure CFLAGS=-arch i386 PKG_CONFIG=/opt/local/bin/pkg-config PKG_CONFIG_PATH=/usr/X11/lib/pkgconfig LDFLAGS=-L/usr/X11/lib --with-debug It does find libxkbfile and compiles fine with it. NOTE that I need to specifiy LDFLAGS and PKG_CONFIG_PATH, otherwise the compile fails. This seems something that could be fixed in autoconf (sorry, I have no knowledge of autoconf, so no patch here :-( Regarding the keyboard issue: As long as I compile without libxkbfile (either without PKG_CONFIG_PATH or by specifying --without-xkbfile) keyboard works. As soon libxkbfile is linked in, it stops working. Hope this helps Gerald -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
Re: [Freerdp-devel] FreeRDP On Mac OS/X 10.6
Hi, Can you try with a 14 day old (checkout before my changes) and see if that makes a difference? I will give it a try during the next days I assumed it worked with Apples development tools (Xcode?) without macports, but I really don't know. I was able to compile the last release version without macports (also I had to set some environment variables manualy, which would be nice to autodetect by configure), but the last release did not work on mac, so I had to switch to the lastest version from git, which requires automake, libtool etc, which is the reason why I used macports. Gerald -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
[Freerdp-devel] FreeRDP On Mac OS/X 10.6
Hi, I am trying to get FreeRDP to run on Mac OS/X 10.6. I have successfully compiled it, but when I try to start a session, I get the following output and nothing happens (only a X server is started): #xfreerdp 10.11.12.245 Couldn't find rules file (xorg) find_keyboard_layout_in_xorg_rules: 0 Found locale : de_DE detect_keyboard_layout_from_locale: 407 Using German (0x0407) Loading keymap base kbd_init: detect_and_load_keyboard returned 1031 freerdp_kbd_init: 407 starting thread 0 to 10.11.12.245:3389 freerdp_chanman_pre_connect: keyboard_layout: 407 connecting to 10.11.12.245:3389 TLS Encryption negotiated main thread, waiting for all threads to exit main thread, all threads did exit Does anybody have an idea what's going wrong here or how I can start to debug this? Gerald --- Gerald Richter Tel. +49 (6133) 939-122 -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
