By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 97 - FreeNX problems with KDE3/Jaunty
Summary: FreeNX problems with KDE3/Jaunty
Status: RESOLVED INVALID
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: 3.5.10
Hardware: i386 Kubuntu Jaunty
: P5 minor
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2009-06-02 16:54 CDT by sichemist
Modified: 2012-10-19 15:48 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description sichemist 2009-06-02 16:54:23 CDT 
When I attempted to log in to my Jaunty/KDE3 desktop using the NoMachine NX client and its KDE setting, I used to get the KDE 4 desktop.  Now, it just crashes.  

In the past (in Intrepid/KDE3) I circumvented this problem by telling the NX client to run /opt/kde3/bin/startkde as the custom program upon login.

Now, with the same settings, I get the KDE3 desktop, immediately followed by the KDE 4 desktop.  The KDE3 Kicker is stacked on top of the KDE4 panel, and the KDE3 desktop is replaced by the KDE4 desktop (and plasmoids).

I'm willing to troubleshoot this problem if someone can give me a starting point.  I don't use NX too frequently, so it's not a huge disruption to my everyday activities.
Comment 1 Calvin Morrison 2011-07-09 23:25:23 CDT 
This isn't really a bug, more of a confusion with the whole rebranding process effecting our file naming. In case this is still an issue for anyone, the path for trinity is now /usr/bin/starttrinity

Calvin Morrison