Your message dated Sun, 11 May 2025 17:42:56 -0400
with message-id <cbdf087e-0a9f-4243-9d08-90aa620c9...@queued.net>
and subject line Re: Bug#1104007: chromium: Chromium opens but is invisible, 
takes long to load.
has caused the Debian Bug report #1104007,
regarding chromium: long startup delay on KDE/X11
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1104007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 135.0.7049.95-1~deb12u1
Severity: important

Dear Maintainer,
Starting Chromium shows the icon in my task manager and an invisible window 
which is unusable. Apparently if I wait long enough, the program does become 
visible but I should not have to wait so long for the program to function. I 
even tried clearing out my ~/.config/chromium and this did not solve anything.
If I run Chromium in the terminal, the following output appears:
[110257:110286:0424/005604.072313:ERROR:nss_util.cc(344)] After loading Root 
Certs, loaded==false: NSS error code: -8018
Warning: loader_scanned_icd_add: Could not get 'vkCreateInstance' via 
'vk_icdGetInstanceProcAddr' for ICD libGLX_nvidia.so.0
[110853:110853:0424/010017.407435:ERROR:gpu_blocklist.cc(119)] Unable to get 
gpu adapter
[110257:110257:0424/010017.407792:ERROR:service_client.cc(36)] Unexpected 
on_device_model service disconnect: The device's GPU is not supported.

I am running Debian Bookworm. Since I see GPU errors appeared later in the 
output, I'd like to note that I am running the bookworm-backports versions of 
"firmware-amd-graphics" and "nvidia-driver-full".
I expect Chromium to start up, be visible, and be usable within a few seconds.
Instead, Chromium starts, but is invisible for a rather long time, and is 
unusable during that time. GPU errors that I seem to face only on Chromium are 
likely the cause of this.


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

Kernel: Linux 6.1.0-33-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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                                     135.0.7049.95-1~deb12u1
ii  libasound2                                          1.2.8-1+b1
ii  libatk-bridge2.0-0                                  2.46.0-5
ii  libatk1.0-0                                         2.46.0-5
ii  libatspi2.0-0                                       2.46.0-5
ii  libc6                                               2.36-9+deb12u10
ii  libcairo2                                           1.16.0-7
ii  libcups2                                            2.4.2-3+deb12u8
ii  libdav1d6                                           1.0.0-2+deb12u1
ii  libdbus-1-3                                         1.14.10-1~deb12u1
ii  libdouble-conversion3                               3.2.1-1
ii  libexpat1                                           2.5.0-1+deb12u1
ii  libflac12                                           1.4.2+ds-2
ii  libfontconfig1                                      2.14.1-4
ii  libfreetype6                                        2.12.1+dfsg-5+deb12u4
ii  libgbm1                                             22.3.6-1+deb12u1
ii  libgcc-s1                                           12.2.0-14
ii  libglib2.0-0                                        2.74.6-2+deb12u5
ii  libgtk-3-0                                          3.24.38-2~deb12u3
ii  libharfbuzz-subset0                                 6.0.0+dfsg-3
ii  libharfbuzz0b                                       6.0.0+dfsg-3
ii  libjpeg62-turbo                                     1:2.1.5-2
ii  liblcms2-2                                          2.14-2
ii  libminizip1                                         1.1-8+deb12u1
ii  libnspr4                                            2:4.35-1
ii  libnss3                                             2:3.87.1-1+deb12u1
ii  libopenh264-7                                       2.3.1+dfsg-3+deb12u2
ii  libopenjp2-7                                        2.5.0-2+deb12u1
ii  libopus0                                            1.3.1-3
ii  libpango-1.0-0                                      1.50.12+ds-1
ii  libpng16-16                                         1.6.39-2
ii  libpulse0                                           16.1+dfsg1-2+b1
ii  libstdc++6                                          12.2.0-14
ii  libudev1                                            252.36-1~deb12u1
ii  libx11-6                                            2:1.8.4-2+deb12u2
ii  libxcb1                                             1.15-1
ii  libxcomposite1                                      1:0.4.5-1
ii  libxdamage1                                         1:1.1.6-1
ii  libxext6                                            2:1.3.4-1+b1
ii  libxfixes3                                          1:6.0.0-2
ii  libxkbcommon0                                       1.5.0-1
ii  libxml2                                             2.9.14+dfsg-1.3~deb12u1
ii  libxnvctrl0                                         525.85.05-3~deb12u1
ii  libxrandr2                                          2:1.5.2-2+b1
ii  libxslt1.1                                          1.1.35-1+deb12u1
ii  libzstd1                                            1.5.4+dfsg2-5
ii  xdg-desktop-portal-gtk [xdg-desktop-portal-backend  1.14.1-1
   ]
ii  xdg-desktop-portal-kde [xdg-desktop-portal-backend  5.27.5-2
   ]
ii  zlib1g                                              1:1.2.13.dfsg-1

Versions of packages chromium recommends:
ii  chromium-sandbox  135.0.7049.95-1~deb12u1

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

Versions of packages chromium-common depends on:
ii  libc6        2.36-9+deb12u10
ii  libgcc-s1    12.2.0-14
ii  libstdc++6   12.2.0-14
ii  libx11-6     2:1.8.4-2+deb12u2
ii  libxcb1      1.15-1
ii  libxnvctrl0  525.85.05-3~deb12u1
ii  x11-utils    7.7+5
ii  xdg-utils    1.1.3-4.1
ii  zlib1g       1:1.2.13.dfsg-1

Versions of packages chromium-common recommends:
ii  chromium-sandbox                        135.0.7049.95-1~deb12u1
ii  fonts-liberation                        1:1.07.4-11
ii  libgl1-mesa-dri                         22.3.6-1+deb12u1
ii  plasma-workspace [notification-daemon]  4:5.27.5-2+deb12u2
ii  system-config-printer                   1.5.18-1
ii  udev                                    252.36-1~deb12u1
ii  upower                                  0.99.20-2

Versions of packages chromium-sandbox depends on:
ii  libc6  2.36-9+deb12u10

-- no debconf information



--- End Message ---
--- Begin Message ---
Hi Serena,

Thanks for following up. I'm going to close this, as it really does sound like it's related to a(n unsupported) mix of kernel/userspace graphics drivers & libraries from both bookworm and trixie. That said, if you end up reproducing it when you fully upgrade your system to trixie (we officially freeze in a few days!), please reopen this bug.

Thanks,
Andres


On Sun, 27 Apr 2025 23:01:01 +0000 Serena Star <starcr...@outlook.com> wrote:
Hi Andres,
I don't know what has happened since Friday, but suddenly my Chromium is starting up 
instantly now. I looked in my apt history.log file and the only change of note in my 
packages is installing "linux-image-amd64/bookworm-backports" on Friday at 
11am. Chromium hasn't even been updated, we're still on the reported version. Sorry to 
say that the problem has been seemingly unexplainably fixed but that seems to be the 
case. It works well both on X11 and Wayland.

Thanks,
Serena
________________________________
From: Andres Salomon
Sent: Friday, April 25, 2025 1:19 PM
To: Serena Star; 1104...@bugs.debian.org
Subject: Re: Bug#1104007: chromium: Chromium opens but is invisible, takes long 
to load.

Control: retitle -1 chromium: long startup delay on KDE/X11

Hi Serena,

Oh, interesting. So roughly the same version of chromium (around
135.0.7049.95-1 or 135.0.7049.114-1) worked on your same hardware when
you were running debian testing, but doesn't work when running debian
stable.

Next steps would be to try an older version of chromium (eg,
https://snapshot.debian.org/package/chromium/131.0.6778.108-1~deb12u1/ )
to try to narrow down where the behavior started, and also to try the
official google chrome packages to see if the behavior is
debian-specific. Also, does it happen if you switch your KDE session to
wayland (and also try to run chromium with --ozone-platform-hint=auto)?

Thanks,
Andres

On 4/25/25 12:49, Serena Star wrote:
> (Resending because I did reply instead of reply all)
> Hi Andres,
> I am using KDE on X11. I can't definitively tell you if the behavior
> started on the version mentioned because I was previously using Debian
> 13 Trixie/Testing. I just recently reinstalled my OS back to Debian 12
> Bookworm/Stable.
> I have tried to upgrade my kernel to the one in bookworm-backports and
> it did seem to improve the startup time, but there is still a period of
> time where the program is invisible and unusable. Basically when the
> program is invisible, if you drag a window around over it, you get that
> weird effect like when you won Windows Solitaire on old versions
> (hopefully you know what I mean).
> Something to note, when launching Chromium through the terminal, the
> errors about a GPU do NOT appear anymore on the newer kernel.
> I hope this information helps diagnose the issue.
>
> Thanks,
> Serena
>
>
> ------------------------------------------------------------------------
> *From:* Andres Salomon
> *Sent:* Thursday, April 24, 2025 1:52 AM
> *To:* Serena Star; 1104...@bugs.debian.org
> *Subject:* Re: Bug#1104007: chromium: Chromium opens but is invisible,
> takes long to load.
>
> Hi,
>

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to