[kde-freebsd] Re: start kde fails after reboot

[Gua Chung Lim]

Hi,

Thank you very much for your kind effort to help me.

> > I don't actually know what kdeinit4 does.
> > Both options render the rest of xterm unresponsive.
> > I have to press <Alt><Ctrl><F?>.
> > Then press <Ctrl>C to stop xterm.
> 
> What an interesting problem :)
> 
> So Xorg doesn't really crash, as xterm is still up?
I just do not understand your meaning of ``crash''.
Yes, twm and xterm (white screen) are still there.
But xterm does not respond to any keyboard input,
right after I issue the suggested command.

> If you don't have debug symbols for kdelibs, can you install them and
> then run `gdb --args kdeinit4 --no-fork', then type 'run' and get a
> backtrace with 'bt' when it crashes?
gua at bsdhost:~% gdb --args kdeinit4 --no-fork
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd"...(no debugging symbols found)...
(gdb) run
Starting program: /usr/local/kde4/bin/kdeinit4 --no-fork
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New LWP 100180]
[New Thread 2a301140 (LWP 100180)]
kdeinit4: (klauncher /usr/local/kde4/lib/kde4/libexec/klauncher) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: No such file or directory
kdeinit4: (kded4 /usr/local/kde4/bin/kded4) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: No such file or directory
kdeinit4: Communication error with launcher. Exiting!

Program exited with code 0377.
(gdb) bt
No stack.
(gdb) quit
gua at bsdhost:~%

If you want me to debug the program and submit bug report,
I am very willing to do so in normal situation.
But I also NEED to get work done. It is close to deadline.
Debugging programs and editing source code or patch are
much far beyond my knowledge, anyway. I don't know Qt.

Repeat again...
Every time after reboot, I do ``make deinstall'', ``make install''
and mostly WITHOUT ``clean'' before ``make install'' to ensure that
obj(s) are not changed, KDE will ALWAYS run fine.
Even though the binaries are not changed.
So I would INSIST that SOMETHING reside in those Makefile(s).
And it happens to trigger and render KDE to work.

Firstly, this evening I wanted to wipe out 8.2R from my hard disk,
as I already have an iso image of 7.4R. Download has just completed.
But unfortunately md5 and sha256 give me wrong checksum. :-(
So I must start over the download again.

I have to defer installation of 7.4R until next few days.
So for this time, I can do whatever you suggest.
But after 7.4R is installed, I just can not do.

Thank you.

-- 
Gua Chung Lim