Bug 471571
| Summary: | Strange suspend behavior | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Roman Rakus <rrakus> |
| Component: | gnome-terminal | Assignee: | Behdad Esfahbod <behdad> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 10 | CC: | behdad, daryll, fdc, rrakus, tsmetana, twaugh |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-12-18 06:50:42 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Roman Rakus
2008-11-14 11:43:37 UTC
Please discuss suspend here Response: First: True. But I'm missing point, why you want to suspend primary terminal. Second: No. F9 and F10 has the same behavior. Third: I don't see any problem in bash neither in gnome-terminal. Why you want to suspend primary shell? I really don't see any sense. Are you saying you don't understand why anyone would use suspend? Once you decide suspend is useful you obviously want to do it from a console or from a gnome-terminal. The problem is that it is trivial to accidentally type it at the primary shell and leave yourself with a hung shell. You su to another user (say postgres to work on a database), then you suspend to test it, then you forget which shell you're in (because the prompt is identical) and suspend again, and you've got a stopped shell. I don't want to suspend a primary shell, I want the primary shell under gnome-terminal to say "Can't suspend a login shell" just like the console does. Yeah, no I understand you. You can run: gnome-terminal -e "bash -l" and you are in login shell With about almost 25 years of unix experience, it's faster for me to jump between shells using only the keyboard than it is to grab a mouse, find a window that may be buried, type two commands, then go back to the first shell. I get to stay in the same shell, type fg, execute a command, and type suspend. Are you arguing that typing suspend at a gnome-terminal shell and having it hang is the right behaviour? Particularly when the shell recognizes this as a problem and has a means of handling it in a more reasonable way? OK. I change component to gnome-terminal and we will see... Can we run shell under gnome-terminal as login shell? This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Roman, Please use gconf-editor, then go to apps => gnome-terminal => profiles => Default => login_shell and check the case. Does that work for you ? For me it works :) Question is, if it works for initial reporter. Daryll does that work for you? Yes. That gives the "Can't suspend a login shell" message I expect. I'd argue it should be the default, but that's a personal choice, so if you disagree so be it. We can wrap this one up. But I've got another strange process behaviour. Start a process. Put it in the background. Then kill the shell. The subprocess dies and it shouldn't. I'll file a new bug report for that one. Setting Severity to Low since a workaround exists. Switching to ASSIGNED so that gnome-terminal maintainer can comment or change default behaviour if needed. --- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |