Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
iterm2
iterm2
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 1,740
    • Issues 1,740
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Commits
  • Issue Boards
  • George Nachman
  • iterm2iterm2
  • Issues
  • #7497

Closed
Open
Opened Jan 26, 2019 by Mikhail Bystretsky@bmv0
  • Report abuse
  • New issue
Report abuse New issue

iTerm2 puts to sleep its child console processes while screen is locked

  • iTerm2 version: Build 3.2.7
  • OS version: MacOS 10.13.6

Detailed steps to reproduce the problem:

  1. Launch iTerm2
  2. Launch a long-running console process, better with progress indication
  3. Lock the screen using keys Cmd+Control+Q or Lock Screen command in the Apple menu
  4. Wait some time (1-2 minutes)
  5. Unlock the screen

What happened: The console process did nothing while the screen was locked. Please note the missing records on screenshot 1. The process in the terminal app worked fine at the same time (screenshot 2).

What should have happened: The console process should work without a pause during a lock.

I also have tryed to run caffeinate alongside the console process (without success). So I think the problem is in iTerm2 itself.

com.googlecode.iterm2.plist

screenshot_1

screenshot_2

debuglog.txt

Related issues

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
0
Labels
None
Assign labels
  • View project labels
Reference: gnachman/iterm2#7497