[Bug] Pop!_OS AppCenter stuck in timeout loop causing 100% CPU usage

Resolved 💬 3 comments Opened Nov 6, 2025 by TDProServices Closed Jan 12, 2026

Bug Description

Pop!_OS AppCenter (io.elementary.appcenter) gets stuck in an infinite timeout loop on system startup, consuming 100% CPU continuously until manually killed.

System Information

  • OS: Pop!_OS 22.04 LTS
  • Kernel: Linux 6.16.3-76061603-generic
  • Claude Code Version: Latest (as of 2025-11-06)
  • AppCenter: io.elementary.appcenter

Reproduction Steps

  1. Boot Pop!_OS system
  2. AppCenter attempts to register with D-Bus search provider
  3. Registration times out
  4. AppCenter retries indefinitely
  5. Process consumes 100% CPU for extended periods (17+ minutes observed)

Evidence from System Logs

Nov 06 08:04:34 pop-os gnome-shell[2201]: Received error from D-Bus search provider io.elementary.appcenter.desktop: Gio.IOErrorEnum: Timeout was reached
Nov 06 08:04:35 pop-os io.elementary.appcenter.desktop[6095]: Failed to register: Timeout was reached
Nov 06 08:12:55 pop-os gnome-shell[2201]: Received error from D-Bus search provider io.elementary.appcenter.desktop: Gio.IOErrorEnum: Timeout was reached
Nov 06 08:12:56 pop-os io.elementary.appcenter.desktop[10418]: Failed to register: Timeout was reached
Nov 06 08:13:31 pop-os systemd[1997]: app-gnome-io.elementary.appcenter\x2ddaemon-3422.scope: Consumed 2min 17.711s CPU time.

Process Information

PID 3422: io.elementary.appcenter -s
CPU: 100% for 17:36 elapsed time
Status: Stuck in retry loop

Impact

  • System becomes unresponsive
  • High CPU usage immediately after boot
  • User unable to work until process manually killed
  • Difficult to diagnose (appears as generic "io.elem+" in process lists)

Workaround

# Kill the stuck process:
kill $(pgrep -f "io.elementary.appcenter")

# Or use pkill:
pkill -f "io.elementary.appcenter"

Expected Behavior

AppCenter should:

  1. Attempt registration with timeout
  2. Fail gracefully after reasonable retry attempts
  3. Not consume 100% CPU indefinitely
  4. Log clear error messages for debugging

Additional Context

This appears to be a Pop!_OS-specific issue where the GNOME Shell search provider interface conflicts with AppCenter's registration mechanism. Claude Code users on Pop!_OS may experience system slowdowns that appear to be Claude-related but are actually caused by this system service.

Suggested Fix

Claude Code could potentially detect and warn users about stuck system processes consuming excessive resources, helping distinguish Claude performance issues from system-level problems.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗