Wednesday, July 17, 2013

Just a little update about new Citrix Receiver 13.0

Citrix release (2 days ago i think) a new Citrix Receiver 13.0. You can find it under "Betas and Tech Previews" download section. They release two versions: ARMEL and ARMHF.
Before you ask, please take note on Linux Tech Preview documentation here page 4 under "ARM hard float and x86 Platforms":
"ARM (armel) binaries are compiled for the ARMv5 architecture. ARM hard float (armhf) binaries are compiled for ARMv7, and hence do not support ARMv6 architectures (such as the Raspberry Pi)."

New 13.0 armel release for RPi-ThinClient will be released soon on apt repository :-)



  1. Gibbio,

    Great work on this project so far! It has some real potential.

    I was wondering if you would be willing to open up discussion on the direction a bit more with the community?

    I've recently forked the GitHub repo and have made some changes (which aren't yet pushed to my repo) that I think could be really beneficial. But, I think a joint venture could be more what the community needs.

    I've opened an IRC channel on Freenode called #RasPiTC. Hoping we could get some discussion. Are you willing? Is there a better medium for discussion? If not, I don't have any issues with doing my own project, just thought we could bounce some ideas.


    1. Hi Greg,
      yes, is a good idea, but this will need something i didnt have too much in the last months: time :)

      Sure, if you have some ideas to improve the performance or the user experience on RPi-TC, please share it! GitHub is a nice place for do that!

      RPi-TC is open to everyone, everyone can use it and everyone can do whatever they want with it. I didnt own any single line of code used in RPi-TC :)

  2. Hi Gibbio,

    Apologies for contacting you like this, but I can't find another way!

    I came by your blog and the quality of content really grabbed my attention, so I thought I’d drop you an e-mail. It's great seeing so much Raspberry Pi stuff, and that's what we're into!

    I’m currently collaborating with Premier Farnell, a top electronics tech company, and we’d love to know if you’d be interested in mentioning PF and/or some of its products on your website.

    At the moment, we are able to provide bespoke content written by Premier Farnell’s very own tech copywriters at your request. Also, in the coming weeks we will also be expanding the scope of our collaborations to include things such as product testing, reviews, organising tech/electronics networking and events, and providing you with access to experts for Q&A. We could also potentially send products for giveaways on your site or offer exclusive discounts for your readership, which could stir up some interest.

    As I say, good content is available right now, but we can do the other stuff in the near future.

    Let me know what you think, and if you have any questions, fire away!



  3. Hi Gibbo,
    Is it possible to get the Storebrowse working in this edition. I have found launching Citrix on RPITC to be slow when having to use IceWeasel to launch the StoreFront. I want to see if this process will allow me to run XenDesktop smoothly.

    1. i'll update Iceweasel soon, just a few days ago Debian team release the version 17 (from 10).

    2. Iceweasel updated to 17.0.7

  4. Hi Gibbo,

    I. Greetings: I have made two stability changes to the SPICE client running in your distro. The changes were modifications to the libspice libraries / dependencies. I have significantly increased performance and stability to virt-viewer.

    II. RAM caching the SPICE protocol on the Pi v.A/B doesn't work. SPICE is a resource hog compared to other Remote Protocols. After ~ 30 seconds the low RAM on the Pi fills and then the PID crashes / dumps the mem. The session can't stay open even when performing basic tasks like auto screen resizing.

    III. To resolve this, I modified libspice libraries to stop caching RAM at ~64MB. This allows the session to stay open and connected. While graphics remain vibrant, audio and USB redirection cause PID death.

    IV. Until I can figure a way to cache / compress the data more heavily server-side, I believe this is the best method for SPICE usability.

    V. I would like to create an UNSTABLE branch on GitHub or wherever the best location for that would be. What do you think?

    1. Hi Abraham,
      thank you very much for the time you've spent on that!
      SPICE on RaspberryPi really need some sort of tuning.
      Partially we can solve the RAM problem by rolling back to a lighter desktop than XFCE.
      Also creating a SPICE only release with LXDE, using the 512Mb board and removing the video intro will give you about 400Mb of free RAM.

      If you want we can create this "SPICE only" release with my rebuilded os package/tuning and your SPICE for RaspberryPi version. Yes GitHub will be great! If you like the idea please contact me @ gibbio AT gmail DOT com

  5. The Current Citrix 12.X build on the image should work correct? Are there any issues that downright limit this from working?


Note: Only a member of this blog may post a comment.