Bug 74726 - Konsole freezes when exiting--either "exit", "logout", ctrl-D, or hitting the close (X) button
Summary: Konsole freezes when exiting--either "exit", "logout", ctrl-D, or hitting the...
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-09 17:35 UTC by Rex
Modified: 2020-05-19 10:41 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rex 2004-02-09 17:35:46 UTC
Version:           1.2.3 (under 3.2.0) (using KDE KDE 3.2.0)
Installed from:    SuSE RPMs
OS:          Linux

(Using SuSE 9.0, with KDE 3.2.0 from the common SuSE apt repository)

Konsole starts fine, and runs just fine....however:

Konsole "locks up" on exiting, via any exiting method I know of.  The window continues to behave nicely, though the shell inside is frozen (and won't redraw).

I can use a ctrl-alt-esc to kill the window, and it disappears.  However, the process continues in the background.

14836 ?        S      0:02 kdeinit: konsole
14621 ?        T     12:49 kdeinit: konsole -session 117f000002000107625677800000025520047_1076264250_225414
14958 ?        R      3:41 kdeinit: konsole
15039 ?        R      0:05 kdeinit: konsole

Only one of these is actually runnning (has a window, shell responds).
GDB's backtrace makes some sense though:

(gdb) bt
#0  0x412a4b48 in read () from /lib/i686/libpthread.so.0
#1  0x4171ddb0 in __JCR_LIST__ () from /opt/kde3/lib/konsole.so
#2  0x416c9333 in TEPty::DataReceived(int, int&) ()
   from /opt/kde3/lib/konsole.so
#3  0x416c7929 in TEPty::qt_invoke(int, QUObject*) ()
   from /opt/kde3/lib/konsole.so
#4  0x40bf68bb in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#5  0x4077dc81 in KProcess::receivedStdout(int, int&) ()
   from /opt/kde3/lib/libkdecore.so.4
#6  0x4077c6aa in KProcess::childOutput(int) ()
   from /opt/kde3/lib/libkdecore.so.4
#7  0x4077c299 in KProcess::slotChildOutput(int) ()
   from /opt/kde3/lib/libkdecore.so.4
#8  0x4077d58c in KProcess::commClose() () from /opt/kde3/lib/libkdecore.so.4
#9  0x416c7e5f in TEPty::commClose() () from /opt/kde3/lib/konsole.so
#10 0x4077c62c in KProcess::processHasExited(int) ()
   from /opt/kde3/lib/libkdecore.so.4
...continues

So it is trying to close itself, but whatever JCR_LIST does, it is trying to read() and waits to do so.


Nice job on 3.2.0 btw,
Rex
Comment 1 Marc Heyvaert 2004-02-26 09:53:51 UTC
I have exactly the same behaviour here after installing the KDE 3.2 rpm's for suse 8.2. Starting up I get the following error message :

Font `-misc-console-medium-r-normal--16-160-72-72-c-80-iso10646-1' not found.
Check README.linux.console for help.

After clicking that away and choosing an unicode font, things are OK, however I can not quit the application in a normal way, hence my changes are lost too and the next time I start Konsole, I still have the same mistake.

The strange thing is that I installed these rpm's a second time (had too after applied some patches through YOU :-(  ). Now the first time Konsole was ok, not so now, so I think it has to do with the setup in general, not with the program Konsole as such.

I'm trying now to find some sort of configuration file for Konsole so that I can hack that directly.

Marc Heyvaert
Comment 2 Marc Heyvaert 2004-02-27 15:21:51 UTC
Hello again,

Well, I managed to change my font permanently (I failed to notice that you have to save your settings explicitly, sorry). So I don't have the error message anymore. I can use the Konsole, but when I quit the program hangs and the window stays on the screen, but nothing works anymore, so no input, no menu choice is possible. I have to kill the process (with KSysguard)

On VERY rare occasions it is possible to close Konsole normally, but I have been unable to detect a repeatable pattern.

Marc


Comment 3 Rex 2004-02-27 16:49:31 UTC
Just for some additional info,
If I kill the window with Ksysguard/ctrl-atl-esc, I get kdeinit using 100% of the cpu, so I manually kill that one afterwards.  This does not affect the rest of my KDE.

Between the two of us, this seems to be a SuSe problem.  I tried removing all the konsole config/schema files from .kde.  Konsole now has all the default options (like tip-of-the-day), but still the same freezing behaviour is seen on exit.

Rex
Comment 4 Rex 2004-02-27 18:30:55 UTC
Hrm.  I've been poking, and it seems that my problem is in read(), as called from  KWrited::block_in().  Read continues to wait for something to show up on the buffer.

So, being a good little user, I grabbed the latest cvs snapshot, and compiled konsole, all ready to do some debugging, and the problem doesn't happen on the newest version!

I would happily accept this, however block_in/TEPty/etc haven't changed from old version to new!
 
So, Marc, I would give rebuilding konsole a shot (I did not build the full kdebase, just konsole only).

Rex
Comment 5 Marc Heyvaert 2004-02-28 12:09:47 UTC
Hello Rex (and all if someone other is following this :) )

Well I try a recompile today or tomorrow.

In the mean time I have discovered that for me the problem when I su (to root) I can close Konsole !?! Also when I su to another user identity that I use for developing purposes, I can also close the application. Strange...

Like you said, it is probably some settingsproblem linked to suse

Marc
Comment 6 Brian Jonas 2004-03-13 22:57:01 UTC
Rex and Marc, I too have the same problem Rex described. Did rebuilding konsole work for both of you? If so, I (a newbie) would appreciate it if you could tell me how to do that, or point me to some documentation. I'm learning a lot, but have a long ways to go.
Thanks,
Brian
Comment 7 Rex 2004-03-13 23:05:23 UTC
Well, with 3.2.1 out, using apt or yum to get the latest of gwdg.de would be best for a newbie.  See http://linux01.gwdg.de/apt4rpm/ for the apt howto's and whatnot.  Basically, you set up apt to use gwgd.de (instructions on that page), and just do "apt install kde" (as root).
Comment 8 Brian Jonas 2004-03-13 23:12:26 UTC
On Saturday 13 March 2004 02:05 pm, you wrote:
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
>
> http://bugs.kde.org/show_bug.cgi?id=74726
>
>
>
>
> ------- Additional Comments From newbould ece arizona edu  2004-03-13 23:05
> ------- Well, with 3.2.1 out, using apt or yum to get the latest of gwdg.de
> would be best for a newbie.  See http://linux01.gwdg.de/apt4rpm/ for the
> apt howto's and whatnot.  Basically, you set up apt to use gwgd.de
> (instructions on that page), and just do "apt install kde" (as root).

Comment 9 Marc Heyvaert 2004-03-18 16:03:15 UTC
Hi,

Is this still a valid bug report. It seems that if you use the latest rpm's from SuSE Konsole is ok. Can the people who voted for this bug please confirm so that Rex (the reporter) can close the bug. As it is related to a binary release there is nothing to be fixed by the developers anyway.

Marc
Comment 10 Brian Jonas 2004-03-19 05:13:44 UTC
On Thursday 18 March 2004 07:03 am, Marc Heyvaert wrote:
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
>
> http://bugs.kde.org/show_bug.cgi?id=74726
> taiji pandora be changed:
>
>            What    |Removed                     |Added
> ---------------------------------------------------------------------------
>- CC|                            |newbould ece arizona edu
>
>
>
> ------- Additional Comments From taiji pandora be  2004-03-18 16:03 -------
> Hi,
>
> Is this still a valid bug report. It seems that if you use the latest rpm's
> from SuSE Konsole is ok. Can the people who voted for this bug please
> confirm so that Rex (the reporter) can close the bug. As it is related to a
> binary release there is nothing to be fixed by the developers anyway.
>
> Marc
Marc,
Thanks for asking. Though I have not fixed it, it is because I'm choosing to 
wait for SuSe 9.1 and do an upgrade to everything at one time. I can use the 
workarounds until then.
Brian

Comment 11 Uwe Roemers 2004-03-19 07:56:14 UTC
> Can the people who voted for this bug please confirm 

After online-updating everything available, this problem is gone on my system.
Uwe
Comment 12 Rex 2004-03-19 22:13:23 UTC
I will close this bug; Brian if it is still a problem for you after my last email let me know.
Let's chalk it up to a SuSE configuration issue in the RPM.
Comment 13 Rex 2004-03-19 22:14:14 UTC
Helps to close it when committing....sigh....