Summary: | The newly opened shell/window closes itself immediately | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | thomas <thomas.bsd> |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 1.5.2 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | FreeBSD | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
thomas
2005-09-29 12:12:22 UTC
I can't reproduce this on 5-stable with the 3.4.2 packages. Can you reproduce the problem with the kdebase binary package (rather than the port)? Does % konsole --profile=4shells work? > Answer to Philip Rodrigues Hello, I have tried to install manually the following file : ftp://ftp.kde.org/pub/kde/stable/3.4.2/src/kdebase-3.4.2.tar.bz2, but unsuccessfully : installation failed after a few lines like this one : "/usr/x11R6/lib/libqt-mt.so: undefined reference to 'pthread_[something]'" A re-install of the qt33 port did not help. > Answer to Kurt V. Hindenburg Hallo, it DOES work. I have a konsole with 4 tabs. The problem seems indeed related to my profile, since I can start root shells from the menu (Session > New Root Shell) > Additional comments --- I cannot even start a konsole with eg : "ALT+F2, konsole." The shortcut I use contains : '/usr/local/bin/bash'. --- If I do : konsole -noclose, the konsole opens but the session is terminated. The title of the window is : "<Finished> - Shell - Konsole" --- I upgraded from FreeBSD 5.4 RC3 to FreeBSD 5.4 stable and reinstalled the port kdebase3, but the problem remained. Thanks Philip & Kurt for your help. It works now! My default session in the menu Settings > Configure console > Session is the Shell one. In the field Execute, there was : "clear". I removed these damned five letters and the problem got fixed. The solution was much simpler than expected (I reinstalled kdebase3...). BUT I still do not understand why this field contained "clear" (I never filled it) and why it changed the behaviour of the konsole... I don't get the point... Anyway, it was not a real bug and the konsole now works perfectly. Bye |