Opened 17 years ago
Closed 17 years ago
#1174 closed bug (fixed)
Start Terminal in UserBootscript, and no Terminal will open
| Reported by: | axeld | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Applications/Terminal | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description (last modified by )
When I launch Terminal in the UserBootscript, too, both Terminals will hang. You can then also not start any new Terminals, unless you kill them both first. They both seem to wait for a message reply (waiting on tmp_rport0), so it might be a registrar thing. Tested with hrev20793.
Change History (5)
comment:1 by , 17 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 17 years ago
comment:3 by , 17 years ago
| Component: | Servers/registrar → - Applications/Terminal |
|---|
Well, they both try to synchronously script each other to find out their window number in TermApp::FindTerminalId(), invoked by the TermApp constructor. So it's actually quite natural that they deadlock.
comment:4 by , 17 years ago
| Status: | new → assigned |
|---|
Note:
See TracTickets
for help on using tickets.
Additional info: when you kill the second Terminal, the first one pops finally up.