Ubuntu QA:
BlogBrainstorm
Log in
Ubuntu QA
The Ubuntu community has contributed 10324 ideas, 46361 comments, 1015854 votes

Contributor batonac




up
80
down
Complete FreeNX Support and Integration  
[needs-packaging] FreeNX (#183801)

In : ubuntu
Status : Confirmed
Importance : Wishlist
Assignee :
3 comments, 4 subscribers and 0 duplicates
bug
Written by batonac the 31 Mar 08 at 22:52. Category: System. Related to: Nothing/Others. New
It's time for Ubuntu to get on the ball with FreeNX. FreeNX is an extremely fast and powerful screen sharing server which far surpasses any similar technology Ubuntu currently ships with.

FreeNX allows for super fast remote sessions, even over dial-up connections. FreeNX has tightly-integrated printer, file, and audio sharing. FreeNX is so light on bandwidth that it would allow for fast LTSP clients even over wireless bridges.

NX was designed with remote users in mind. It's not a technology developed for occasional remote computer desktop access. It built for everyday use.

Ubuntu should completely support and integrate this technology by the following:
1. Include it in the software repositories. (ensure that it works with all Ubuntu variations and all NX clients)
2. Set FreeNX as the default remote desktop server. (develop ability to connect to existing sessions first)
3. Integrate NX connection abilities into whatever remote desktop client is set by default.
4. Replace XDMCP with FreeNX server/client in LTSP. (see http://brainstorm.ubuntu.com/idea/5848/)
5? Creating an "access my pc from anywhere in the world" service using FreeNX.

Keywords: Dynamic remote desktop feature, SSH, X11, VNC, Free NX, XEPHYR

See the 7 comments >>

up
18
down
Ask Authors To Approve Duplicate Ideas!  
Written by batonac the 31 Mar 08 at 12:52. Category: Brainstorm. Related to: Nothing/Others. New
It seems that any new idea which is reported as a duplicate can be quickly removed and merged into another, even if the original author thought that his idea was similar, but had very important differences from the older idea.

I very recently reported a new and exciting idea for ubuntu which was becoming popular very fast (for its short lifetime). My idea has been removed from brainstorm searches because someone reported it as a duplicate of a lesser idea, and, although the other idea had a similar theme, my idea was far more specific and better documented.

I wish that members here still had the option of voting for my idea, since voting for other idea won't accomplish what I was proposing, but I seem to have no power over this process.

To get a feel for the problem, look here:

My Original idea:
http://brainstorm.ubuntu.com/idea/5848/

Other Idea:
http://brainstorm.ubuntu.com/idea/5362/

If the author doesn't respond in the time appointed, then the merge should go ahead, but otherwise, our free speech should be better protected on this site.

See the 7 comments >>

up
15
down
Protect LTSP from Session Crashes  
Written by batonac the 18 Mar 08 at 14:18. Category: Server. Related to: Nothing/Others. New
One of my biggest gripes about LTSP is the lack of thin client session protection. If you use the NX thin client system (http://www.nomachine.com/ or http://freenx.berlios.de/) and your thin client crashes, gets disconnected, or looses power, when you log back in your session is still as you left it, just waiting for you to continue your work (all your programs that were running before the crash, are still running).

If you are using Ubuntu LTSP, however, and your thin client crashes (this is not extremely unusual, albeit very annoying), the session is completely destroyed and all of the programs are shut down. A session saving feature is extremely important, especially during this time in development when not all the LTSP bugs have been completely ironed out yet. Eventually I would also like to see thin client sessions blessed with the ability to log out of the currently used thin client, without shutting down the running programs.

I recognize that this feature will probably steal more server system resources (all users could possibly have running sessions on the server, even though they are not currently logged on), and should therefore be optional, the option should, however, defiantly be available.

No comment yet. Add a comment >>