| Summary: | All TDE components seg fault when starttde run from freenx | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Russell Brown <russell> |
| Component: | other (any) | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | blocker | CC: | bugwatch, darrella |
| Priority: | P5 | ||
| Version: | R14.0.0 [Trinity] | ||
| Hardware: | amd64 | ||
| OS: | Kubuntu Precise | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Attachments: | Session Log | ||
Created attachment 728 [details] Session Log My server is AMD64 with a CLI install of Kubuntu Precise Pangolin, FreeNX and Trinity installed (nightly build of trinity). When I connect via NX to this server, all the TDE components seg fault when called from starttde (FWIW I've been using KDE3 on Hardy with freenx for years so this isn't a new scenario for me). Starting with a fresh user account, I connect using a KDE session (FreeNX's node.conf has got it's startkde command set to /opt/trinity/bin/starttde) and get kpersonalizer as expected. Take all the defaults and finish kpersonalizer, the screen goes black, then I get the TDE background image, the kicker panel appears, a window asking if I want to create a Documents directory pops up and then a pile of Seg Fault Crash windows (for konqueror, kicker, kmix, ksmserver, kcminit_startup, katapult, kaccess and ksplash). Clearing out the users home directory and trying again doesn't always produce identical results... sometimes the background goes back to black and there's no kicker bar but the seg fault crash windows always show up. Skipping the kpersonalizer wizard also lands me in the same Seg Fault place. If I connect with NX with a 'custom' session that merely fires up an XTerm and then run /opt/trinity/bin/starttde I again end up in the Seg Fault place. However.... doing the same thing and running /opt/trinity/bin/kicker and /opt/trinity/bin/konqueror then it all seems to work. If I login as a new user from a LTSP thin client (X-Terminal) then TDE goes through kpersonalizer and fires up as expected; so it's something to do with the NX connection and starttde. Clicking on 'Backtrace' in the Seg Fault Crash windows, they all look very similar. Here's one from kmix: passprompt [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7f9d2c94b700 (LWP 20929)] [KCrash handler] #5 0x00007f9d3a66502c in free () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x00007f9d3aef5819 in XFree () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #7 0x00007f9d372ce2ee in XRRUpdateConfiguration () from /usr/lib/x86_64-linux-gnu/libXrandr.so.2 #8 0x00007f9d3b416f40 in TQApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libtqt-mt.so.3 #9 0x00007f9d3b425c77 in TQEventLoop::processEvents(unsigned int) () from /usr/lib/libtqt-mt.so.3 #10 0x00007f9d3b47e139 in TQEventLoop::enterLoop() () from /usr/lib/libtqt-mt.so.3 #11 0x00007f9d3b47e0c2 in TQEventLoop::exec() () from /usr/lib/libtqt-mt.so.3 #12 0x00007f9d342ed2bd in kdemain () from /opt/trinity/lib/libtdeinit_kmix.so #13 0x0000000000408665 in _start () I've attached the FreeNX session log where you can see the output from starttde. What can I do to help sort this? very happy to hack scripts and recompile stuff.