Skip to content

BUG: crash when screen resumes from screen saver #535

Closed

Description

@fcrozat

Describe the bug
When I unlock my screen (system was idle, it auto-locked), StreamController crashes

To Reproduce
Steps to reproduce the behavior:

  1. Start StreamController
  2. wait for auto-lock
  3. Unlock
  4. Crash

(this is both with resume (beta) feature turned off or on).

It is probably timing related, as I can't reproduce if I manually lock and unlock the screen.

Additional context
I'm using flatpak version

extract from logs:
2026-01-15 08:46:44.736 | SUCCESS | src.app:on_activate:125 - Finished loading app
2026-01-15 08:46:44.737 | INFO | autostart:request_background_callback:64 - request_background success=True
2026-01-15 10:23:37.862 | INFO | src.backend.LockScreenManager.LockScreenManager:lock:63 - Locking screen: True
2026-01-15 10:23:37.869 | INFO | src.backend.DeckManagement.Subclasses.ScreenSaver:show:94 - Showing screen saver
2026-01-15 10:23:37.970 | DEBUG | src.backend.DeckManagement.DeckController:update_all_inputs:434 - Updating all inputs took 0.00996541976928711 seconds
2026-01-15 10:28:06.313 | INFO | src.backend.LockScreenManager.LockScreenManager:lock:63 - Locking screen: False
2026-01-15 10:28:06.314 | INFO | src.backend.DeckManagement.Subclasses.ScreenSaver:hide:126 - Hiding screen saver
2026-01-15 10:28:06.319 | INFO | src.backend.DeckManagement.DeckController:load_page:721 - Loading page Default on deck AL46K2C70873
2026-01-15 10:28:06.392 | INFO | src.backend.DeckManagement.DeckController:load_background:571 - Loading background in thread: 140457258489536
2026-01-15 10:28:08.206 | INFO | streamcontroller_plugin_tools.BackendBase:on_disconnect:39 - Connection closed
/app/bin/launch.sh : ligne 3 : 3 segfault (core dumped)python3 /app/bin/StreamController/main.py "$@"

Activity

  1. fcrozat commented on Jan 15, 2026

    @fcrozat
    Author

    Correction, if I do a manual lock/unlock, StreamController goes into some infinite loop and use 100% of CPU

  2. fcrozat commented on Jan 19, 2026

    @fcrozat
    Author

    I'm debugging this further, from a clean configuration, it doesn't crash, so it might be related to a plugin. I'll share my findings later.

  3. Core447 commented on Aug 12, 2026

    @Core447
    Member

    Fixed with b40e8f3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    • Status
      No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions