Package: chromium
Version: 142.0.7444.175-1~deb13u1
Severity: important
File: chromium
Tags: trixie, wayland, power-management, upstream

Dear Maintainer,

On Debian 13 (Trixie) with GNOME Shell (Wayland), Chromium fails to release
systemd / gnome-session suspend inhibitors related to “Download in progress”.
Once this state is triggered, the system cannot suspend unless Chromium is
fully
closed or the user forces suspension with 'systemctl suspend -i'.

Even when:
- no downloads are active
- the download tab has been closed
- all browser windows have been closed
- background apps are disabled
- xdg-desktop-portal and related services are restarted

…the suspend inhibitors remain.

Steps to reproduce:
1. Start Chromium on Debian 13 (Wayland + GNOME).
2. Download several files (often image files trigger this, e.g., from Gemini).
   The bug does not appear every time, but is reproducible.
3. At some point, Chromium creates multiple suspend inhibitors.
4. Even after downloads finish, the inhibitors remain indefinitely.
5. Attempt to suspend the system:
   $ systemctl suspend
6. Inspect active inhibitors:
   $ gnome-session-inhibit -l

Expected behavior:
- System should suspend normally
- 'systemctl suspend' should succeed
- 'gnome-session-inhibit -l' should show no Chromium entries unless a real
download is running
- No need to use 'systemctl suspend -i'

Actual behavior:
- Suspend is blocked:
  Operation inhibited by "user session inhibited"
- gnome-session-inhibit -l shows:
  /usr/lib/chromium/chromium: Download in progress (suspend)
  /usr/lib/chromium/chromium: Download in progress (suspend)
- These entries never disappear until Chromium is fully restarted.

Impact:
- Users cannot suspend laptops normally
- Power management is broken
- Battery drain on mobile devices
- Confusing for users who rely on expected suspend behavior

Additional information:
- The inhibitor is held by the main Chromium process, not renderers.
- Only occurs on Wayland/xdg-desktop-portal-gnome setups.
- Related upstream Google issue: https://issues.chromium.org/issues/454025651


-- System Information:
Debian Release: 13.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.57+deb13-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common                        142.0.7444.175-1~deb13u1
ii  libasound2t64                          1.2.14-1
ii  libatk-bridge2.0-0t64                  2.56.2-1
ii  libatk1.0-0t64                         2.56.2-1
ii  libatspi2.0-0t64                       2.56.2-1
ii  libc6                                  2.41-12
ii  libcairo2                              1.18.4-1+b1
ii  libcups2t64                            2.4.10-3+deb13u2
ii  libdav1d7                              1.5.1-1
ii  libdbus-1-3                            1.16.2-2
ii  libdouble-conversion3                  3.3.1-1
ii  libexpat1                              2.7.1-2
ii  libflac14                              1.5.0+ds-2
ii  libfontconfig1                         2.15.0-2.3
ii  libfreetype6                           2.13.3+dfsg-1
ii  libgbm1                                25.0.7-2
ii  libgcc-s1                              14.2.0-19
ii  libglib2.0-0t64                        2.84.4-3~deb13u1
ii  libgtk-3-0t64                          3.24.49-3
ii  libharfbuzz-subset0                    10.2.0-1+b1
ii  libharfbuzz0b                          10.2.0-1+b1
ii  libjpeg62-turbo                        1:2.1.5-4
ii  liblcms2-2                             2.16-2
ii  libminizip1t64                         1:1.3.dfsg+really1.3.1-1+b1
ii  libnspr4                               2:4.36-1
ii  libnss3                                2:3.110-1
ii  libopenh264-8                          2.6.0+dfsg-2
ii  libopenjp2-7                           2.5.3-2.1~deb13u1
ii  libopus0                               1.5.2-2
ii  libpango-1.0-0                         1.56.3-1
ii  libpng16-16t64                         1.6.48-1
ii  libpulse0                              17.0+dfsg1-2+b1
ii  libudev1                               257.9-1~deb13u1
ii  libx11-6                               2:1.8.12-1
ii  libxcb1                                1.17.0-2+b1
ii  libxcomposite1                         1:0.4.6-1
ii  libxdamage1                            1:1.1.6-1+b2
ii  libxext6                               2:1.3.4-1+b3
ii  libxfixes3                             1:6.0.0-2+b4
ii  libxkbcommon0                          1.7.0-2
ii  libxml2                                2.12.7+dfsg+really2.9.14-2.1+deb13u2
ii  libxnvctrl0                            535.171.04-1+b2
ii  libxrandr2                             2:1.5.4-1+b3
ii  libxslt1.1                             1.1.35-1.2+deb13u2
ii  libzstd1                               1.5.7+dfsg-1
ii  xdg-desktop-portal-gnome [xdg-desktop  48.0-2
    -portal-backend]
ii  xdg-desktop-portal-gtk [xdg-desktop-p  1.15.3-1
    ortal-backend]
ii  zlib1g                                 1:1.3.dfsg+really1.3.1-1+b1

Versions of packages chromium recommends:
ii  chromium-sandbox  142.0.7444.175-1~deb13u1

Versions of packages chromium suggests:
pn  chromium-driver  <none>
pn  chromium-l10n    <none>
pn  chromium-shell   <none>

Der Inhalt dieser E-Mail ist vertraulich und nur fuer den in der Nachricht 
angegebenen Empfaenger bestimmt. Es ist strengstens untersagt, irgendeinen Teil 
dieser Nachricht ohne schriftliche Zustimmung des Absenders an Dritte 
weiterzugeben. Sollten Sie diese Nachricht irrtuemlich erhalten haben, 
antworten Sie bitte auf diese Nachricht und loeschen Sie sie anschliessend, 
damit wir sicherstellen koennen, dass ein solcher Fehler in Zukunft nicht mehr 
vorkommt.

The content of this email is confidential and intended for the recipient 
specified in message only. It is strictly forbidden to share any part of this 
message with any third party, without a written consent of the sender. If you 
received this message by mistake, please reply to this message and follow with 
its deletion, so that we can ensure such a mistake does not occur in the future.

Reply via email to