I have a problem that my Krusader always starts with Terminal Emulator with 0 height. It seems that it resets sizes of splitter at the startup even though it remembers them when shutting down as observed in /home/junip/.kde4/share/config /krusaderrc.

I have KDE 4.11.5 and Krusader 2.4.0-beta3.

If you close and reopen the terminal emulator, is it given a correct height? It could be that the restore takes place before Krusader has finished loading.

Showing/hiding terminal emulator does not change anything. The same applies for fullscreen terminal emulator (Ctrl + F) . Simply if there is this "zero-height" terminal emulator then Ctrl + F just shows nothing.

But when I close Krusader (saving settings on exit ) with hidden terminal emulator the next time I start it I can show the emulator with normal size.

Is anything relevant shown in the terminal output from Krusader which might indicate why this occurs?

https://bugs.kde.org/show_bug.cgi?id=315856

luebking wrote:https://bugs.kde.org/show_bug.cgi?id=315856

I do not know what has been fixed but I still experience this problem and I even filled a bug report for it.
Am I the single person with this issue? I have reinstalled the system since reporting this and even installed recently openSUSE 13.2 on the other computerand the behaviour is the same always.

bcooksley wrote:Is anything relevant shown in the terminal output from Krusader which might indicate why this occurs?

The only output in the terminal at start is:

Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QString)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QString)

Is there a way to inspect logs of Krusader or turn on the logging to file? ( I found no Krusader log in /var/log)

krusader 2.4.0-beta3 was tagged on:
Sat, 20 Oct 2012 15:01:13 +0000 (17:01 +0200)

the fix was comitted on:
Wed, 27 Feb 2013 17:10:21 +0000 (18:10 +0100)

Spot the problem :-P

luebking wrote:krusader 2.4.0-beta3 was tagged on:
Sat, 20 Oct 2012 15:01:13 +0000 (17:01 +0200)

the fix was comitted on:
Wed, 27 Feb 2013 17:10:21 +0000 (18:10 +0100)

Spot the problem :-P

Jeez. I did not know that new versions are released so infrequently.

You might want to build Krusader directly from source in that case - it is likely releases of Krusader are not being made regularly, so other fixes could be included as well.

Yep. I will consider this option if I miss the console. Meanwhile I get used to Krusader without terminal:)