Opened 18 years ago
Last modified 17 years ago
#627 closed bug
Cannot open another copy of the Terminal program — at Version 15
| Reported by: | Owned by: | axeld | |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Applications | Version: | |
| Keywords: | Cc: | diver, Niels.Reedijk@…, bonefish | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description (last modified by )
Test description:
- Click on the leaf in the Deskbar.
- Select Applications -> Terminal.
The Terminal window you have just requested does not appear.
Note: This seems to only fail periodically if it's the first action performed after starting up Haiku. From my tests I would estimate you can reproduce it 90% of the time.
After this failure I could get another Terminal window by typing "Terminal" in the original Terminal window that Haiku starts by default, but I could not get one from Deskbar or Tracker.
Test setup: VMWare image rev17582 on XP
Change History (16)
comment:1 by , 18 years ago
| Cc: | added |
|---|
comment:2 by , 18 years ago
comment:4 by , 18 years ago
Rechecked on the rev17637 image and it still happens intermittently. :-(
comment:5 by , 18 years ago
(In reply to comment #0)
From the latest (06-04-2006) Buildfactory image... click Terminal from the Be menu or double-click the icon in /boot/beos/apps and the Terminal window never shows. ... type Terminal from the open window, and a new Terminal window opens ... select Start New Terminal from the Terminal menu and the new window opens ... If I close the Terminal that opens when the system boots, I have to re-boot to open a Terminal window.
comment:6 by , 18 years ago
It seems, that you could launch Terminal from processcontroller's replicant.
comment:8 by , 18 years ago
Confirmed in hrev17923 in VMWare that closing the auto-launched Terminal and attempting to restart it from the deskbar fails as described in this bug.
comment:9 by , 18 years ago
| Owner: | changed from to |
|---|
comment:11 by , 18 years ago
More info:
if started from Terminal, the above loop does this: read returns, handshake.status is PTY_WS, write is called and returns, read returns and handshake.status is PTY_OK. The loop exits. If started from Tracker, read returns, handshake.status is PTY_WS, write is called but never returns.
comment:12 by , 18 years ago
| Cc: | added |
|---|
follow-up: 14 comment:13 by , 18 years ago
| Platform: | → All |
|---|
I think I may have found a baby-step of a solution. Somehow, the terminal depends on the filetype "application/x-vnd.Be-SHEL" (from R5) being there. I added it using FileTypes and haven't had a lick of trouble starting Terminal since. I am using 19070 and was having the same startup problems with Terminal.
follow-up: 15 comment:14 by , 18 years ago
Correction to that last post: That file type addition had absolutely NOTHING to do with it... I restarted Haiku and the crashes started again. However, I can successfully start a Terminal window via the ProcessController. Can anyone confirm this?
Replying to mthayes:
I think I may have found a baby-step of a solution. Somehow, the terminal depends on the filetype "application/x-vnd.Be-SHEL" (from R5) being there. I added it using FileTypes and haven't had a lick of trouble starting Terminal since. I am using 19070 and was having the same startup problems with Terminal.
comment:15 by , 18 years ago
| Description: | modified (diff) |
|---|
Replying to mthayes:
Correction to that last post: That file type addition had absolutely NOTHING to do with it... I restarted Haiku and the crashes started again. However, I can successfully start a Terminal window via the ProcessController. Can anyone confirm this?
Yes. Starting Terminal via ProcessController works 100% of the times, just like starting from Terminal itself. Starting from Tracker, though, only sometimes works.
Happens here too. When I launch Terminal from deskbar, a "Terminal" item appears for half a second or so in the deskbar team list, then it disappears, and the Terminal window never shows up.