Summary: | konsole windows sometimes freeze up | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | Jesper Juhl <jesper.juhl> |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | maksim |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Slackware | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Jesper Juhl
2006-02-21 21:43:33 UTC
Are you using xine? I have xine installed and I occasionally launch xine from firefox, but I never launch xine from a konsole window. The freezing of konsole windows also happens even when I've not been running xine since powering on the computer. Make sure you did not press Ctrl+S or ScrollLock. If you did, you can unfreeze by pressing Ctrl+Q or ScrollLock again. I'm well aware of the effects of CTRL+S / CTRL+Q that's not what's going on here. This also happens to plain xterms, not just 'konsole'. The xterm process itself appears to be fine (scroll bars work, menus work, etc.). Is this a bash shell problem? I'm using KDE 3.4.2 under Slackware 10.2. A possible lead: I've noticed that it seems like these konsole/xterm/bash freezings/"lock-ups" occur soon after KDE starts up. When these annoying lock-ups occur I've had to open another konsole/xterm to kill the offending process. However, after killing the offending konsole's/xterm's and using KDE for a while, I don't seem to notice any more konsole/xterm lock-ups. One hypothesis might be that the freezings/lock-ups occur in those konsole's/xterm's that KDE automatically restores at start-up - I don't think I've had newly-created konsole's/xterm's freeze (so far at least, after several days of use); it was always the ones that were "restored" that seemed susceptible to freezing. The newly-created xterm's show up on the job list normally. The xterm's that were "restored" had some long session ID number (I don't remember exactly at the moment) as part of the arguments, as well as other "junk." Perhaps there was something in those mysterious arguments that wasn't "quite right?" Is there any update on this? Does it still happen? I've been running KDE 3.5.4 since it came out and I've not experienced the problem again since that upgrade. Problem appears to be solved. Closing. |