Bug 66162

Summary: Konsole fails to start when X is 'nohupped'
Product: [Applications] konsole Reporter: Melvyn Sopacua <melvyn>
Component: generalAssignee: Konsole Developer <konsole-devel>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: FreeBSD   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Melvyn Sopacua 2003-10-17 15:10:47 UTC 
Version:           1.2 post (using KDE 3.1.92 (alpha2, CVS >= 20030921), yes)
Compiler:          gcc version 2.95.4 20020320 [FreeBSD]
OS:          FreeBSD (i386) release 4.8-STABLE

When you start 'X'  as 'nohup startx' on FreeBSD, Konsole will shutdown immediately after displaying the tip of the day. It does work, when you're in a script(1) environment and you wanna get X's output, but of course if you switch back to the terminal, you have to take another vty.
Comment 1 groot 2004-01-17 16:19:19 UTC 
Melvyn, does this still happen to you? Since you've patched all kinds of other things on your system, maybe you've dealt with this as well?
Comment 2 Melvyn Sopacua 2004-01-17 17:06:29 UTC 
No, haven't dealt with it - in fact - currently I cannot get any konsole instance running.

I've traced it to the qt method a.exec() in main.cpp line 483. From there I cannot step anymore, because gdb gives an segfault in _longjmp. However - simply letting the program run, it exists normally, so that's prolly a gdb thing.

On line 484 I've inserted:
KONSOLEDEBUG << "Eventloop returned with value" << ret << endl;

And it shows that ret is 0, which is normal.

I'm not using qt-copy, but the qt-3.2.3 version which is in the FreeBSD ports. If you feel it's relevant, I will test qt-copy.

PS: apart from the patch for db4 support in kdevelop, all patches I had have been dealt with. I only strip -O2 from relevant places and set alternate paths for the autotools.
Comment 3 Melvyn Sopacua 2004-01-20 07:16:28 UTC 
With today's sources, the problem is resolved.